UE initiated beam report trigger condition for separate DL UL tci

Abstract

Methods and systems are described for initiating, or configuring a UE for, a beam report, where the UE has been indicated with a DL serving link for DL reception and an UL serving link for UL transmission One aspect of the present disclosure is a UE calculating one quality per each of two different serving links, one DL serving link and one UL serving link, and wherein the one or more of the two qualities are used as input to one or more events which may trigger one or more beam reports to the network if an associated trigger condition is fulfilled.

Description

UE INITIATED BEAM REPORT TRIGGER CONDITION FOR SEPARATE DL UL TCICROSS REFERENCE TO RELATED INFORMATION

[0001] This application claims the benefit of United States of America priority application No. 63 / 529,869, filed on July 31, 2023, titled “UE Initiated Beam Report Trigger Condition for Separate DL UL TCI.”TECHNICAL FIELD

[0002] The present disclosure generally relates to systems and methods for initiating or configuring a beam report from a user equipment.BACKGROUND

[0003] QCL (quasi co-located) and TCI (Transmission Configuration Indicator) states are states in NR (New Radio). In NR, several signals can be transmitted from different antenna ports of a same base station. These signals can have the same large-scale properties such as Doppler shift / spread, average delay spread, or average delay. These antenna ports are then said to be QCL. If the UE knows that two antenna ports are QCL with respect to a certain parameter (e.g., Doppler spread), the UE can estimate that parameter based on one of the antenna ports and apply that estimate for receiving signal on the other antenna port. For example, there may be a QCL relation between a CSI-RS (Channel State Information - Reference Signal) for tracking RS (TRS) and the PDSCH (Physical Downlink Shared Channel) DMRS (Demodulation Reference Signal). When UE receives the PDSCH DMRS it can use the measurements already made on the TRS to assist the DMRS reception. Information about what assumptions can be made regarding QCL is signaled to the UE from the network. In NR, four types of QCL relations between a transmitted source RS and transmitted target reference signal (RS) were defined:• Type A: {Doppler shift, Doppler spread, average delay, delay spread}• Type B: {Doppler shift, Doppler spread}• Type C: {average delay, Doppler shift}• Type D: {Spatial Rx parameter}

[0004] QCL type D was introduced to facilitate beam management with analog beamforming and is known as spatial QCL. There is currently no strict definition of spatial QCL, but the understanding is that if two transmitted antenna ports are spatially QCL, the UE can use the same Rx (reception) beam to receive them. This is helpful for a UE that uses analog beamforming to receive signals, since the UE needs to adjust its RX beam in some direction prior to receiving a certain signal. If the UE knows that the signal is spatially QCL with some other signal it has received earlier, then it can safely use the same RX beam to receive also this signal. Note that for beam management, the discussion mostly revolves around QCL Type D, but it is also necessary to convey a Type A QCL relation for the RSs to the UE, so that it can estimate all the relevant large-scale parameters.

[0005] Typically, this is achieved by configuring the UE with a CSLRS for tracking (TRS) for time / frequency offset estimation. To be able to use any QCL reference, the UE would have to receive it with a sufficiently good SINR (signal to interference and noise ratio). In many cases, this means that the TRS must be transmitted in a suitable beam to a certain UE.

[0006] To introduce dynamics in beam and transmission point (TRP) selection, the UE can be configured through RRC (Radio Resource Control) signaling with up to 128 TCI (Transmission Configuration Indicator) states. The TCI state information element is shown in Figure 1 (Extracted from 3GPP TS 38.331).

[0007] Each TCI state contains QCL information related to one or two RSs. For example, a TCI state may contain CSLRS 1 associated with QCL Type A and CSLRS2 associated with QCL TypeD. If a third RS, e.g., the PDCCH (Physical Downlink Control Channel) DMRS, has this TCI state as QCL source, it means that the UE can derive Doppler shift, Doppler spread, average delay, delay spread from CSLRS 1 and Spatial Rx parameter (i.e. the RX beam to use) from CSLRS2 when performing the channel estimation for the PDCCH DMRS.

[0008] A first list of available TCI states is configured for PDSCH, and a second list of TCI states is configured for PDCCH. Each TCI state contains a pointer, known as TCI State ID, which points to the TCI state. The network then activates via MAC CE (Medium Access Control Control Element) one TCI state for PDCCH (i.e. provides a TCI for PDCCH) and up to eight TCI states for PDSCH. The number of active TCI states the UE support is a UE capability, but the maximum is 8.

[0009] Assume a UE has 4 activated TCI states (from a list of 64 total configured TCI states). Hence, 60 TCI states are inactive for this particular UE and the UE needs not be prepared to have large scale parameters estimated for those inactive TCI states. But the UE continuously tracks and updates the large scale parameters for the RSs in the 4 active TCI states. When scheduling a PDSCH to a UE, the DCI (Downlink Control Information) contains a pointer to one activated TCI state. The UE then knows which large scale parameter estimate to use when performing PDSCH DMRS channel estimation and thus PDSCH demodulation.

[0010] As long as the UE can use any of the currently activated TCI states, it is sufficient to use DCI signaling. However, at some point in time, none of the source RSs in the currently activated TCI states can be received by the UE, i.e., when the UE moves out of the beams in which the source RSs in the activated TCI states are transmitted. When this happens (or actually before this happens), the gNB (base station in NR) would have to activate new TCI states. Typically, since the number of activated TCI states is fixed, the gNB would also have to deactivate one or more of the currently activated TCI states.

[0011] The two-step procedure 100 related to TCI state update is depicted in Figure2. At 105, it is determined if a current TCI state needs to be updated. At 110, the selected TCI state is selected from the activated set of TCI states using DCI. At 115, it is determined if a ndw set of TCI states needs to be activated. At 120, the set of activated TCI states is updated using MAC CE.TCI states Activation / Deactivation for UE-specific PDSCH via MAC CE

[0012] Now more details can be provided of the MAC CE signaling that is used to activate / deactivate TCI states for UE specific PDSCH. The structure of the MAC CE for activating / deactivating TCI states for UE specific PDSCH is given in Figure 3. As shown in Figure3, the MAC CE contains the following fields:• Serving Cell ID: This field indicates the identity of the Serving Cell for which the MAC CE applies. The length of the field is 5 bits;• BWP ID: This field contains the ID corresponding to a downlink bandwidth part for which the MAC CE applies. The BWP ID is given by the higher layer parameter BWP -Id as specified in 3GPP TS 38.331. The length of the BWP ID field is 2 bits since a UE can be configured with up to 4 BWPs for DL;• A variable number of fields E: If the UE is configured with a TCI state with TCI State ID i, then the field Ti indicates the activation / deactivation status of the TCI state with TCI State ID i. If the UE is not configured with a TCI state with TCI State ID i, the MAC entity shall ignore the Ti field. The Ti field is set to "1" to indicate that the TCI state with TCI State ID i shall be activated and mapped to a codepoint of the DCI Transmission Configuration Indication field, as specified in 3GPP TS 38.214 / 38.321. The E field is set to "0" to indicate that the TCI state with TCI State ID i shall be deactivated and is not mapped to any codepoint of the DCI Transmission Configuration Indication field. It should be noted that the codepoint to which the TCI State is mapped is determined by the ordinal position among all the TCI States with Ti field set to "1". That is the first TCI State with Ti field set to " 1 " shall be mapped to the codepoint value 0 of DCI Transmission Configuration Indication field, the second TCI State with Ti field set to " 1 " shall be mapped to the codepoint value 1 of DCI Transmission Configuration Indication field, and so on. In NR Rel-15, the maximum number of activated TCI states is 8;• A Reserved bit R: this bit is set to ‘0’ in NR Rel-15.

[0013] Note that the TCI States Activation / Deactivation for UE-specific PDSCH MAC CE is identified by a MAC PDU (Protocol Data Unit) subheader with logical channel ID (LCID) as specified in Table 6.2.1-1 of 3GPP TS 38.321 (this table is reproduced in Figure 7). The MAC CE for Activation / Deactivation of TCI States for UE-specific PDSCH has variable size.TCI State Indication for UE-specific PDSCH Via DCI

[0014] The gNB can use DCI format 1 1 or 1 2 to indicate to the UE that it shall use one of the activated TCI states for the subsequent PDSCH reception. The field being used in the DCI is transmission configuration indication, which is 3 bits if tci-PresentlnDCI is “enabled” or tci-PresentForDCI-Formatl-2-rl6 is present respectively for DCI format 1 1 and DCI 1 2 by higher layer. Figure 4 shows an example of DCI indication of a TCI state. The DCI gives a pointer into the ordered list of activated TCI states. DCI code point 0 indicates the first TCI state index in the list of TCI states, DCI code point 1 indicates the second TCI state index in the list, and so on.Overview of NR Rel-15 / Rel-16 TCI State Framework

[0015] The NR Rel-15 / 16 framework for beam management is based on the framework of spatial QCL assumptions and spatial relations in order to support, e.g., analog beamforming implementations at the UE and / or the network. The framework allows great flexibility for the network (e.g., the gNB) to instruct the UE to receive signals from several directions and to transmit signals in several directions. In this framework, the uplink and downlink configurations are decoupled, e.g., there is no direct relation between the configured spatial QCL assumptions and the spatial relations.

[0016] In theRel-15 / Rel-16 framework, downlink beam management is performed by conveying spatial QCL (‘Type D’) assumptions to the UE, which are conveyed in TCI states. One TCI state contains one or two RSs, and each RS is associated with a QCL type.• PDCCH beam management: The network configures the UE with a set of PDCCH TCI states by RRC, and then activates one TCI state per CORESET using MAC CE.• PDSCH beam management: The network configures the UE with a set of PDSCH TCI states by RRC, and then activates up to 8 TCI states by MAC CE. After activation, the network dynamically indicates one of these activated TCI states using a TCI field in DCI when scheduling PDSCH. Alternatively, the network may simplify the beam management by not setting the RRC parameter tci- PresentlnDCI (which is configured per CORESET) to enabled. In this case, the UE uses the same TCI state for PDSCH as for PDCCH.

[0017] In the Rel-15 / Rel-16 framework, uplink beam management is performed using configuration of spatial relations. A spatial relation is defined at the UE side between a source RS and a target RS. The source RS can be a received DL RS (SSB or CSI-RS) or an SRS (Sounding Reference Signal). The target RS can be a transmitted PUCCH DMRS or an SRS. Note that there is no direct configuration of the spatial relation for a PUSCH: the PUSCH follows the spatial relation of a PUCCH or an SRS.• PUCCH beam management: For PUCCH, the network configures the UE with a set of 8 spatial relations using RRC, and subsequently activates one of these spatial relations using MAC CE. The spatial relation is defined per PUCCH resource. In Rel-16, enhancements were made such that spatial relation could be updated for a group of PUCCH resources using a single MAC-CE. In addition,default spatial relation for PUCCH was introduced in Rel-16, such that when no spatial relation is configured / activated for a PUCCH resource, the UE uses the TCI state / QCL assumption of the CORESET with lowest ID, both to derive spatial relation and to derive path loss reference signal.• PUS CH beam management: A PUS CH scheduled by DCI Format 0 1 is transmitted over the ports where a configured SRS resource may also be transmitted. Either two (codebook-based) or four (non-codebook-based) SRS resources can be defined in the SRS resource set. The network selects which SRS resource in the set should correspond to the PUSCH transmission (i.e., PUSCH is transmitted on the same ports as the selected SRS and using the spatial relation of the selected SRS) using the SRS resource indicator (SRI) field in DCI. The spatial relation for the SRS resources in the set is provided either by RRC (for periodic or aperiodic SRS) or MAC-CE (for aperiodic or semi-persistent SRS). For PUSCH scheduled by DCI Format 0 0, there is no SRI and the spatial relation instead follows that of a PUCCH resource. In Rel-16, default spatial relation for SRS was introduced, such that when no spatial relation is configured / activated for an SRS resource, the UE uses the TCI state / QCL assumption of the CORESET with lowest ID, both to derive spatial relation and to derive path loss reference signal.• SRS beam management: Spatial relations for SRS are configured by RRC (for periodic and aperiodic) or by MAC CE (aperiodic or semi-persistent).Issues with the Rel-15 / Rel-16 TCI State Framework

[0018] The Rel-15 / Rel-16 framework provides the NW with great flexibility in some areas, at the cost of quite a bit of signalling. In some other areas, the specification is overly restrictive and prohibits efficient (low signalling overhead) and rapid beam management. These limitations are particularly noticeable and costly when UE movement is considered. One example is that beam update using DCI can only be performed for PDSCH, and MAC-CE and / or RRC is required to update the beam for other reference signals / channels, with cause extra overhead and latency.

[0019] Furthermore, in the overwhelming majority of cases, the specified beam management flexibility is not really needed since the network will transmit to and receive fromthe UE using the same beam for both data and control. Hence, using TCI state for DL (downlink) signals / channels and spatial relations for UL (uplink) signals / channels complicates the implementations.

[0020] Another issue is related to the path loss reference signal used for UL power control. In NR, only up to four path loss reference signals can be configured for a UE, which typically is significantly less than the number of beams a TRP at FR2 (frequency range 2) uses to cover the cell. Hence, when a UE moves around in the cell, the path loss reference signal needs to be updated using MAC-CE and / or RRC, which introduces extra latency and overhead.Rel-17 TCI State Framework

[0021] In 3 GPP Rel-17, a new unified TCI state framework is specified, which aims to streamline the indication of transmit / receive spatial filter (and other QCL properties) to the UE by letting a single TCI state indicate QCL properties for multiple different DL and / or UL signals / channels.

[0022] The unified TCI state framework of Rel-17 can be RRC configured in one out of two modes of operation “Joint DL / UL TCI” or “Separate DL / UL TCI”. For “Joint DL / UL TCI” operation, one common Joint TCI state is used for both DL and UL signals / channels. For “Separate DL / UL TCI” operation, one common DL-only TCI state is used for DL channels / signals, and one common UL-only TCI state is used for UL signals / channels.

[0023] It is expected that “Joint DL / UL TCI” operation will be the most common use case, but “Separate DL / UL TCI” operation can be useful in specific scenarios where the optimal DL beam differs from optimal UL beam, for example in case a UE panel associated with the best DL beam is affected by P-MPR (power management - maximum power reduction), and hence need to reduce the maximum allowed output power.Beam Indication Using Rel-17 TCI State Framework

[0024] The common TCI state ID can be updated in a similar way as the TCI state ID is update for PDSCH in Rel-15 / 16, i.e., with one of two alternatives:• Two-stage: RRC signaling is used to configure a number of TCI states in PDSCH-config, and MAC-CE is used to activate a single TCI state (that TCI state will then be applied); and• Three-stage: RRC signaling is used to configure a number of TCI states in PDSCH-config, MAC-CE is used to activate up to 8 TCI states, and a 3 -bit TCI state bitfield (comprising up to 8 codepoints) in DCI is used to indicate one of the activated TCI states (that TCI state will then be applied).

[0025] For “Joint DL / UL TCI” operation, a maximum of one Joint TCI state can be activated per TCI codepoint. One schematic example of how this may look is illustrated in Figure 5. Figure 5 shows an example of activated TCI states and their mapping to TCI field codepoints for “Joint DL / UL TCI.” In case the indicated TCI codepoint is “1””, the UE should apply “Joint TCI state 7” as common QCL source for both DL and UL signals / channels.

[0026] For “Separate DL / UL TCI” operation, up to two TCI states can be activated per TCI codepoint, one for DL signals / channels (DL-only TCI state) and one for UL signals / channels (UL-only TCI state). One schematic example of how this may look is illustrated in Figure 6. Figure 6 shows an example of activated TCI states and their mapping to TCI field codepoints for “Joint DL / UL TCI.” In case the TCI codepoint is “0”, the UE should apply “DL- only TCI state 3” as common QCL source for DL signals / channels, and not update the QCL source for UL signals channel. In case the TCI codepoint is “7”, the UE should apply “UL-only TCI state 57” as QCL source for UL signals / channels, and not update the QCL source for DL signals / channel. In case the TCI codepoint is “2”, the UE should apply “DL-only TCI state 9” as QCL source for DL signals / channels and apply “UL-only TCI state 1” as QCL source for UL signals / channels.

[0027] The existing DCI formats 1 1 and 1 2 in NR are reused (as in Rel-15 / 16 beam management framework) for beam indication, both with and without DL assignment. For DCI formats 1 1 and 1_2 with DL assignment, ACK / NACK (acknowledgement / no acknowledgment) of the PDSCH can be used as indication of successful reception of beam indication. For DCI formats 1 1 and 1 2 without DL assignment, a new ACK / NACK mechanism analogous to that for SPS (semi-persistent scheduling) PDSCH release with both type-1 and type- 2 HARQ-ACK codebook is used, where upon a successful reception of the beam indication DCI, the UE reports an ACK.

[0028] For DCLbased beam indication, the first slot to apply the indicated TCI state is at least Y symbols after the last symbol of the acknowledgment of the joint or separateDL / UL beam indication. The Y symbols are configured by the gNB based on UE capability, which is also reported in units of symbols. and UL Spatial Relation Rules

[0029] For both “Joint DL / UL TCI” operation and “Separate DL / UL TCI” operation, the large scale QCL properties are inferred from one source RS (qcl-Typel only) or two source RSs (qcl-Typel and qcl-Type2) analogous to Rel-15 / 16 beam management framework. For “Joint DL / UL TCI” operation, the UL spatial filter is derived from that corresponding to the source RS of DL QCL Type D, analogous to default beam operation for Rel-15 / 16 beam management framework.

[0030] In DL, the Joint / DL-only TCI state can provide common QCL information at least for:• UE-dedicated PDCCH;• PDSCH;• Aperiodic CSLRS for CSI; and• Aperiodic CSLRS for beam management. It should be noted that CSLRS for other time domain behaviors has not been agreed.

[0031] RRC configuration is used to indicate if a non-UE dedicated PDCCH / PDSCH, AP (application protocol) CSLRS for CSI and BM (beam management) should follow the common beam or not. Common beam here means that the same beam is used for receiving DL signals / channels that are indicated to follow the common beam. For DL signal / channels that do not follow the common beam, a Rel-17 TCI state can be indicated as QCL source in a similar way as for Rel-15 / 16 beam management framework. As an example, for a periodic CSLRS that does not follow the common beam, a ReL17 TCI state can be configured in the parameter “qcLInfoPeriodicCSLRS” in “NZP-CSLRS-Resource information element” as specified in 3GPP TS 38.331 V16.7.0. The possible target and source RS and corresponding QCL properties for that are supported for Joint / DL-only TCI state indication are summarized in Figure 7.

[0032] In UL, the Joint / UL-only TCI state can provide common QCL information as least for:All or a subset of all PUCCH resources;• Dynamic-grant / configured-grant PUS CH; and• SRS for all usages (except for usage ‘positioning’).

[0033] RRC configuration is used to indicate if a SRS and PUCCH resource should follow the common beam or not. Common beam here means that the same beam is used for receiving UL signals / channels that are indicated to follow the common beam. For UL signal / channels that do not follow the common beam, a Rel-17 TCI state can be used to indicate spatial relation instead of a DL / UL-RS which is used to indicate spatial relation for Rel-15 / 16 beam management framework. As an example, for a periodic SRS resource that does not follow the common beam, a new RRC parameter in an SRS resource can be configured with a Rel- 17 TCI state, and the UE will use that Rel-17 TCI state to determine the spatial relation for that SRS resource. Any of the following reference signals can be used to indicate spatial relation for a UL signal / channel in Rel-17 TCI state framework:• SSB;• TRS (tracking reference signal);• CSLRS for beam management;• SRS with usage set to beam management.Inter-Cell Beam Management

[0034] Inter-cell beam management has been included in the Rel-17 TCI state framework to facilitate L1 / L2 (layer 1 / layer 2) inter-cell mobility (to be specified for higher layers in NR Rel- 18) as well as inter-cell multi-TRP operation.

[0035] For inter-cell beam management, a UE can be configured to measure and report Rel-15 Ll-RSRP (Reference Signal Received Power) for SSB(s) associated with nonserving cells. Which serving cell an SSB is associated with is indicated by RRC signaling, where each SSB is paired with a PCI. The maximum number of PCIs different from the serving cell that could be used for SSB measurement / reporting is up to UE capability and can be one of 0, 1,2,3 and 7. The beam indication for inter-cell beam management will work in the same way as for intra-cell Rel-17 unified TCI state framework, as described above, e.g., regarding beam indications.

[0036] The DL QCL and UL spatial relation rules for inter-cell beam management will work in the same way as for intra-cell Rel-17 unified TCI state framework, as described above, e.g., in relation to Figures 5 and 6.Mobility Measurements in LTE and NR

[0037] The UE can be configured by the network to perform measurements of serving and neighbor cells, by sending a measurement configuration, provided in an RRCReconfiguration message (in case of NR) or an RRCConnectionReconfiguration RRC message (for LTE), or as part of broadcasted system information. In accordance with this measurement configuration provided by the network, the UE also reports measurement information, using a Measurement Report RRC message, to the network. The network then typically uses the measurement reports to trigger handover of the UE to a neighbor cell.

[0038] The neighbor cell measurements are classified into intra-frequency, interfrequency or inter-RAT measurements.

[0039] The UE measures what is defined as a measurement object, which is part of the measurement configuration. A measurement object is:• for LTE: a carrier frequency;• for NR: frequency / time location and subcarrier spacing of reference signals.

[0040] The measurement object may be refined by listed cells (such as allowed cells, and / or excluded cells) as well as listed cell-specific offsets. Excluded cells (also called blacklisted cells) are not considered in event evaluation or measurement reporting. The allowed (also called whitelisted) cells may be the only ones considered for event evaluation and measurement reporting if so configured. If neither allowed nor excluded cells are configured, the UE considers all detect cells in event evaluation and measurement reporting.

[0041] The measurement configuration also includes a reporting configuration, comprising a reporting criterion (used to trigger the report) and reporting format (which quantities to include in the report). The reporting criterion is either “periodic” or “single event”. The reporting quantity may be RSRP for example.

[0042] The measurement configuration also includes a list of measurement identities where each measurement identity links one measurement object with one reporting configuration. By configuring multiple measurement identities, it is possible to link more than one measurement object to the same reporting configuration, as well as to link more than one reporting configuration to the same measurement object. The measurement identity is also included in the measurement report that triggered the reporting, serving as a reference to the network.

[0043] The measurement configuration also includes a quantity configuration, which defines the measurement filtering configuration used for all event evaluation and related reporting, and for periodical reporting of that measurement.

[0044] Finally, the measurement configuration includes Measurement gaps, which are periods that the UE may use to perform measurements.

[0045] In the case of a single event reporting criterion, there are a number of event types defined to trigger measurement reports, see e.g., TS 38.331 Section 5.5.4. Examples of two event types are the following:• Event A3 (see Figure 8): For LTE it is also known as “Neighbour becomes offset better than SpCell”. In case of NR it is also known as “Neighbour becomes offset better than PCell / PSCell”. The offset is the cell specific offset part of the measurement object corresponding to the particular neighbor cell.• Event A5 (see also Figure 9): For LTE it is also known as “SpCell becomes worse than thresholdl and neighbour becomes better than threshold2”. In case of NR it is also known as “PCell / PSCell becomes worse than thresholdl and neighbour becomes better than threshold2”. The thresholds are part of the reporting configuration.

[0046] As part of the configuration for events A3, A5 and also other type of events, a hysteresis may also be included. The hysteresis is useful in combination with configuration of “reportOnLeave”, where the UE transmits a report when a trigger quantity of a measurement object ceases to fulfil the criterion (and taking the hysteresis into account) for reporting. For example, as also illustrated in Figure 8, when using the “reportOnLeave” applied on event A3 for a neighbor cell, the UE transmits a measurement report when the neighbor cell falls below the serving cell plus offset minus the hysteresis.Power Management UE Maximum Power Reduction (P-MPR)

[0047] Power Management UE Maximum Power Reduction (P-MPR) is the power reduction the UE may need to perform to comply with regulatory restricted MPE (Maximum Permissible Exposure). P-MPR has been introduced in the PCMAX,f,c equation such that the UE can report to the gNB the available maximum output transmit power, which can be used by the gNB for scheduling decisions. In Rel-16, an event-triggered enhanced power head room (PHR) reportwas specified which could indicate if a P-MPR value has been applied by the UE to meet the MPE requirements.

[0048] An MPE event is typically UE panel specific and can for example depend on if a finger is in close vicinity of a UE panel or not. This means that different UE panels might experience different P-MPR situations, and hence be associated with different available output powers.

[0049] Due to beam correspondence at UEs, it is expected that both DL and UL beam selections in commercial products mainly will be based on measured DL performance metrics (RSRP or SINR) from DL beam management procedures using SSB and / or CSI-RS. However, since P-MPR is not included in DL performance measurements, the gNB is unaware if an UL beam is associated with a UE panel suffering from P-MPR, which if selected could cause UL coverage problems.

[0050] To mitigate this issue, the Rel-16 event-triggered P-MPR-based reporting (which is included in a PHR report when a threshold is reached) was further enhanced in Rel-17. This Rel-17 further enhanced PHR report is signaled via MAC-CE, and in addition to the existing fields in the existing PHR MAC-CE, N>1 P-MPR values can be reported, where N can be 1 ,2,3 or 4 (depending on UE capability). In addition, for each of the reported N P-MPR values (which for example can be associated to N different UE panels), the UE can indicate a new preferred beam (SSBRI / CRI).Prior Art

[0051] Legacy NR beam reporting is either configured periodically with a certain periodicity or requested aperiodically from the network; this can cause, especially in high mobility FR2 scenarios, either a delay in reporting with a loss in performance due to non-updated measurements or a high overhead. In WO 2024033844A1, titled “Trigger Condition for Event- Driven UE Beam Reporting,” different solutions on how to perform trigger condition for such UE initiated beam report for Joint DL / UL TCI operation for unified TCI state framework was disclosed. However, how to trigger a UE initiated beam report when a UE is configured with separate DL / UL TCI for unified TCI state framework is not addressed and hence is an open issue.SUMMARY

[0052] One embodiment under the present disclosure comprises a method performed by a UE for initiating a beam report, where the UE has been indicated with a DL serving link for DL reception and an UL serving link for UL transmission. The method comprises receiving, from a network node, a UE initiated beam report configuration, wherein the UE initiated beam report configuration contains a configuration of one or more trigger events and a configuration of one or more DL-RSs; performing one or more measurements on the one or more DL reference signals; and evaluating, based at least in part on the one or more measurements, if the one or more trigger events has happened associated with the DL serving link or the UL serving link.

[0053] Another embodiment under the present disclosure comprises a method performed by a network node for configuring a UE for initiating a beam report, where the UE has been indicated with a DL serving link for DL reception and an UL serving link for UL transmission. The method comprises transmitting, to the UE, a UE initiated beam report configuration, wherein the UE initiated beam report configuration contains a configuration of one or more trigger events and a configuration of one or more DL-RSs.

[0054] Another embodiment under the present disclosure comprises a UE for initiating a beam report, where the UE has been indicated with a DL serving link for DL reception and an UL serving link for UL transmission. The UE comprises processing circuitry; and a memory. The memory containing instructions executable by the processing circuitry whereby the UE is operative to perform the steps of: receiving, from a network node, a UE initiated beam report configuration, wherein the UE initiated beam report configuration contains a configuration of one or more trigger events and a configuration of one or more DL-RSs; performing one or more measurements on the one or more DL reference signals; and evaluating, based at least in part on the one or more measurements, if the one or more trigger events has happened associated with the DL serving link or the UL serving link.

[0055] Another embodiment under the present disclosure comprises a network node for configuring a UE for initiating a beam report, where the UE has been indicated with a DL serving link for DL reception and an UL serving link for UL transmission. The network node comprises processing circuitry; and a memory. The memory containing instructions executable by the processing circuitry whereby the network node is operative to perform the steps of transmitting,to the UE, a UE initiated beam report configuration, wherein the UE initiated beam report configuration contains a configuration of one or more trigger events and a configuration of one or more DL-RSs.

[0056] This summary is provided to introduce a selection of concepts in a simplified form that are further described below in the detailed description. This summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used as an indication of the scope of the claimed subject matter.BRIEF DESCRIPTION OF THE DRAWINGS

[0057] For a more complete understanding of the present disclosure, reference is now made to the following descriptions taken in conjunction with the accompanying drawings, in which:

[0058] Fig. 1 illustrates a TCI state information element extracted from 3GPP TS 38.331;

[0059] Fig. 2 illustrates an example two-step procedure related to TCI state update;

[0060] Fig. 3 illustrates structure of a MAC CE for activating / deactivating TCI states for UE specific PDSCH;

[0061] Fig. 4 illustrates an example of DCI indication of a TCI state;

[0062] Fig. 5 illustrates an example of activated TCI states and their mapping toTCI field codepoints for “Joint DL / UL TCI;”

[0063] Fig. 6 illustrates shows an example of activated TCI states and their mapping to TCI field codepoints for “Joint DL / UL TCI;”

[0064] Fig. 7 illustrates possible target and source RS and corresponding QCL properties that are supported for Joint / DL-only TCI state indication;

[0065] Fig. 8 illustrates an Event A3 example;

[0066] Fig. 9 illustrates an Event A5 example;

[0067] Fig. 10 illustrates a flow-chart of a method embodiment under the present disclosure;

[0068] Fig. 11 illustrates an example of how an evaluation window can be applied for UE initiated beam reporting;

[0069] Fig. 12 illustrates a flow-chart of a method embodiment under the present disclosure;

[0070] Fig. 13 illustrates a flow-chart of a method embodiment under the present disclosure;

[0071] Fig. 14 shows a schematic of a communication system embodiment under the present disclosure;

[0072] Fig. 15 shows a schematic of a user equipment embodiment under the present disclosure;

[0073] Fig. 16 shows a schematic of a network node embodiment under the present disclosure;

[0074] Fig. 17 shows a schematic of a host embodiment under the present disclosure; and

[0075] Fig. 18 shows a schematic of a virtualization environment embodiment under the present disclosure.DETAILED DESCRIPTION

[0076] Before describing various embodiments of the present disclosure in detail, it is to be understood that this disclosure is not limited to the parameters of the particularly exemplified systems, methods, apparatus, products, processes, and / or kits, which may, of course, vary. Thus, while certain embodiments of the present disclosure will be described in detail, with reference to specific configurations, parameters, components, elements, etc., the descriptions are illustrative and are not to be construed as limiting the scope of the claimed embodiments. In addition, the terminology used herein is for the purpose of describing the embodiments and is not necessarily intended to limit the scope of the claimed embodiments.

[0077] As discussed above, there currently exist certain challenges. Legacy NR beam reporting is either configured periodically with a certain periodicity or requested aperiodically from the network; this can cause, especially in high mobility FR2 scenarios, either a delay in reporting with a loss in performance due to non-updated measurements or a high overhead. To mitigate these problems, UE initiated beam report can be specified, where the UE detects that a non-serving beam is better than the serving beam and indicates this to the network.

[0078] Certain aspects of the disclosure and their embodiments may provide solutions to these or other challenges. One aspect of the present disclosure is a UE calculating one quality per each of two different serving links, one DL serving link and one UL serving link, and wherein the one or more of the two qualities are used as input to one or more events which may trigger one or more beam reports to the network if an associated trigger condition is fulfilled.

[0079] Certain embodiments may provide one or more of the following technical advantages. One advantage of certain embodiments is that it enables the UE to monitor two serving links (DL vs UL, respectively) with common and / or separate triggering criteria and can trigger one or both UE initiated beam reports as needed. In order to improve the reliability of the UE initiated beam report, the triggering criterion may include time-domain requirement for the measurement results. Thereby the flexibility and reliability of the UE initiated beam report are significantly improved.

[0080] Some of the embodiments contemplated herein will now be described more fully with reference to the accompanying drawings. Embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art.

[0081] UE initiated beam management procedure is being discussed as one of the candidate work items for release 19 in 3GPP. In this disclosure, the term UE initiated beam report is used to refer to a beam report that is initiated by the UE based on one or more trigger conditions. It should be noted that other terms can also be used to refer to the UE initiated beam report (e.g., “beam update”, “beam suggestion”).

[0082] Figure 10 describes the steps of one possible method embodiment 900 under the present disclosure of a UE initiated beam report procedure. Please note that not all the steps might be needed and may be optional in certain variations and embodiments. At step 910, the UE indicates during UE capability signaling that it supports UE initiated beam reporting. At 920, the network configures the UE with the UE initiated beam report, for example setting different parameters on how to perform the trigger of the UE initiated beam report events, how to do the UE initiated beam report etc. At step 930, the network transmits downlink reference signals (DLRS), e.g. CSI-RSs, SSBs or new DL-RSs in 6G. At 940, the UE performs measurements on these DL-RSs and evaluate if a UE initiated beam reporting trigger event has occurred. At 950, if such UE initiated beam report trigger event has occurred, the UE indicates to the network that the UE will transmit a UE initiated beam report to the network. At 960, the UE transmits the UE initiatedbeam report. At 970, the network receives the UE initiated beam report and transmits a UE initiated beam report response to the UE. At step 980, the UE receives the response and updates / applies the spatial filter corresponding to a beam in the UE initiated beam report. At step 990, the network and the UE communicate using the new beam pair link determined during the UE initiated beam report procedure.

[0083] Certain embodiments can focus on step 940, where the UE is configured with separate DL / UL TCI for the unified TCI state framework (or similar configuration for a new QCL and / or spatial filter related framework in 6G), indicated with bold text and lines in Figure 10.

[0084] For certain embodiments, it is assumed that the UE has two applied (indicated) unified TCI states, one Unified DL TCI state and one Unified UL TCI state (or similar setup in 6G, where a first TCI state or similar QCL and / or spatial filter related information element is associated with one or more DL signals / channels, e.g., PDCCH, PDSCH, CSI-RS, and a second TCI state or similar QCL and / or spatial filter related information element is associated with one or more UL signals / channels, e.g., PUCCH, PUSCH, SRS).

[0085] In one embodiment, when determining if a UE initiated beam reporting event has occurred the UE considers two separate serving links, where a first serving link is associated with the applied Unified DL TCI state and a second serving link is associated with the applied Unified UL TCI state. The UE can then determine if a UE initiated beam reporting event has occurred for the first serving link (i.e., for the DL signals / channels) and / or if a UE initiated beam reporting event has occurred for the second serving link (i.e., for UL signals / channels). Depending on which serving link the UE detects a UE initiated beam report triggering event for, the UE will perform different actions, for example if the trigger condition is met for the first (DL) serving link the UE might indicate in the UE initiate beam report that the UE has found a better beam for the first (DL) serving link, and vice versa.

[0086] When determining if a UE initiated beam reporting event has occurred for a serving link the UE can for example perform RSRP measurements on a DL-RS associated with the applied unified TCI state for that serving link, and compare that RSRP measurements with RSRP measurements of another set of DL-RSs (referred to as candidate DL-RSs, henceforth). For example, considering the first serving link, the Unified DL TCI state might be associated with SSB2, the UE can then compare the RSRP measured on SSB2 with the RSRP measured on anotherset of SSBs (which are the candidate SSBs), and if one or more of the candidate SSBs have higher RSRP, the UE can trigger a UE initiated beam report event for the first serving link.

[0087] In one embodiment, the UE can be configured with more than one set of candidate DL-RSs, wherein:• at least one set of candidate DL-RSs is used as source reference signals (e.g., source reference signal for QCL properties or source reference signal used to derive receive spatial filters at the UE) for Unified DL TCI states for DL beam evaluation; and / or• at least one set of candidate DL-RSs is used as source reference signals (e.g., source reference signal used to derive transmit spatial filters at the UE) for Unified UL TCI states for UL beam evaluation.

[0088] Note that DL beam evaluation above refers to the process of determining if a candidate DL-RS serving as source reference signal for another Unified DL TCI state is better than the DL-RS associated with the applied Unified DL TCI state. Similarly, UL beam evaluation above refers to the process of determining if a candidate DL-RS serving as source reference signal for another Unified UL TCI state is better than the DL-RS associated with the applied Unified UL TCI state.

[0089] In addition to, or other than RSRP, other performance metrics such as RSRQ (reference signal received quality) and SINR (signal to interference and noise ratio) may be used. To prevent “pin-pong” effect, a threshold may also be used for each of the metrics, where a beam reporting event is triggered only when the difference between a metric associated to a new candidate beam associated with a candidate DL-RS and a metric associated to the current beam (i.e. associated with the DL-RS associated with the applied Unified DL / UL TCI state) exceeds the threshold. For example, a beam report is triggered only when the RSRP associated to a new candidate beam is X dB better than the RSRP associated to the current beam, where X dB is the threshold. The threshold can be pre-determined or configured. In another embodiment, a beam reporting event is triggered only when the conditions of more than one of the configured metrics are met, e.g., RSRP of the current beam is below Z dBm and RSRP of a new candidate beam is X dB better (i.e., greater) than the current beam, or RSRQ of a new candidate beam is Y dB better (i.e., greater) than the current beam. In a further embodiment, a beam reporting event is triggered only when a condition is met in multiple consecutive measurements, e.g., a new candidate beamis X dB better than the RSRP associated to the current beam in two consecutive measurements. Note that in some embodiments, the RSRP, RSRQ, and SINR metrics used to determine a beam reporting event may be measured as follows:• RSRP metric may be measured using either SS-RSRP (SS reference signal received power as defined in clause 5.1.1 of 3GPP TS 38.215 V17.3.0) or CSI- RSRP (CSI reference signal received power as defined in clause 5.1.2 of 3 GPP TS 38.215 V17.3.0);• SINR metric may be measured using either SS-SINR (SS signal -to-noise and interference ratio as defined in clause 5.1.5 of 3 GPP TS 38.215 VI 7.3.0) or CSI-SINR (CSI signal-to-noise and interference ratio as defined in clause 5.1.6 of 3GPP TS 38.215 V17.3.0); or• RSRQ metric may be measured using either SS-RSRQ (SS reference signal received quality as defined in clause 5.1.3 of 3GPP TS 38.215 V17.3.0) or CSI- RSRQ (SS reference signal received quality as defined in clause 5.1.4 of 3 GPP TS 38.215 V17.3.0).

[0090] In one embodiment, the UE can be configured with separate trigger conditions for the first and second serving links. In one related embodiment, the same type(s) of trigger condition(s) is / are used for the first and second serving links but with different threshold levels. For example, for the first serving link, the trigger condition might be that the RSRP of the DL-RS associated with the applied Unified DL TCI state falls below -90 dBm, while for the second serving link, the trigger condition might be that the RSRP of the DL-RS associated with the applied Unified UL TCI state falls below -80 dBm. One reason for having different trigger conditions for DL and UL can for example be that UL output power typically is lower than DL output power, and therefore UL is more sensitive to poor link budget than DL. In one embodiment, different types of trigger conditions are used for the first and second serving link. For example, for the first serving link, the trigger condition may be that the RSRP of the DL-RS associated with the applied Unified DL TCI state is X dB lower than (offset from) the RSRP of the best candidate DL-RS (i.e. a relative performance measure is used as triggering condition), while for the second serving link, the trigger condition may be that the RSRP of the DL-RS associated with the applied Unified UL TCI state falls below -80 dBm (i.e. an absolute performance measure is used as triggering condition).

[0091] In another embodiment, the UE may be configured to report NDL candidate DL-RSs for the first serving link as part of a UE initiated beam report. In this embodiment, a trigger condition may be defined for example as one or a combination of the following:• the RSRPs of each of at least NDL candidate DL-RSs for the first serving link are X dB better (i.e., greater) than the RSRP of the DL-RS associated with the applied Unified DL TCI state;• the RSRP of the DL-RS associated with the applied Unified DL TCI state falls below Y dB and the RSRPs of each of at least NDL candidate DL-RSs for the first serving link are X dB better (i.e., greater) than the RSRP of the DL-RS associated with the applied Unified DL TCI state.

[0092] Note that other metrics such as SINR or RSRQ and other triggering conditions can be used in the above embodiments. One aspect of the above embodiment is that the triggering condition is met on at least NDL candidate DL-RSs such that the UE can report the configured number of NDL candidate DL-RSs as part of the UE initiated beam report. In some embodiments, the NDL candidate DL-RSs may be from more than one DL-RS sets where each of the DL-RS sets may be associated with a different transmission / reception point (e.g., different TRPs). These embodiments are beneficial in case the network wants the UE to perform UE initiated beam reporting in case of scenarios involving multiple transmission / reception points.

[0093] In another embodiment, the UE may be configured to report NUL candidate DL-RSs for the second serving link as part of a UE initiated beam report. In this embodiment, a trigger condition may be defined for example as one or a combination of the following:• the RSRPs of each of at least NUL candidate DL-RSs for the second serving link are X dB better (i.e., greater) than the RSRP of the DL-RS associated with the applied Unified UL TCI state;• the RSRP of the DL-RS associated with the applied Unified UL TCI state falls below Y dB and the RSRPs of each of at least NUL candidate DL-RSs for the second serving link are X dB better (i.e., greater) than the RSRP of the DL-RS associated with the applied Unified UL TCI state.

[0094] Note that other metrics such as SINR or RSRQ and other triggering conditions can be used in the above embodiments. One aspect of the above embodiment is that the triggering condition is met on at least NUL candidate DL-RSs such that the UE can report theconfigured number of NUL candidate DL-RSs as part of the UE initiated beam report. In some embodiments, the NDL candidate DL-RSs may be from more than one DL-RS sets where each of the DL-RS sets may be targeted towards a different reception point (e.g., different TRPs). These embodiments are beneficial in case the network wants the UE to perform UE initiated beam reporting in case of scenarios involving multiple transmission / reception points.

[0095] Note that in the above embodiments, the number of candidate beams to report in UE initiated beam report may be different (i.e., NDL is different from NUL). This is because the beam widths may be different in the first serving link (associated with DL channels / signals) and the second serving link (associated with UL channels / signals) hence necessitating different number of candidate beams to be reported for the two serving links. Another reason is that different number of transmission / reception points may be associated with the first serving link and the second serving link thus necessitating different number of candidate beams to be reported for the two serving links.

[0096] In one embodiment, the second serving link handling the UL signals / channels can be configured with an UL performance metric as a trigger condition. The UL performance metric can for example include one or more of the following metrics:• P-MPR associated with the spatial filter used to receive the DL-RS associated with the applied Unified UL TCI state;• Maximum output power (e.g. Pcmax) associated with the spatial filter used to receive the DL-RS associated with the applied Unified UL TCI state;• Maximum EIRP (Effective Isotropic Radiated Power) associated with the UE panel used to receive the DL-RS associated with the applied Unified UL TCI state;• Power head room (e.g. assuming a default PUSCH transmission) for the spatial filter used to receive the DL-RS associated with the applied Unified UL TCI state.

[0097] In one embodiment the trigger condition for the second serving link can comprise a DL performance metric (e.g. DL RSRP, DL SINR) combined with one of the listed UL performance metrics above. For example, a type of “UL-RSRP” might be used as metric for the trigger condition, where “UL-RSRP” for example can be calculated as the DL-RSRP + one of the UL output power metrics listed above.

[0098] In one embodiment, the UE can be configured with trigger condition comprising a list of different types of triggering events. Each one of the triggering event types may include time-domain information such as: “number of occurrences”, and / or “beam report ratio”, and / or “evaluation window” which for example contains a time period or a number of DL-RS occasions associated with the beam measurement etc. One purpose of including time-domain requirement in the triggering condition is to ensure a qualified reliability of the UE initiated report, since the measurement is performed over a certain number of DL-RS measurement occasions and / or period of time and is thus more reliable. In one example, “number of occurrences” refers to the number of times an event is met, e.g. the RSRP of DL-RS associated with serving link is below a threshold, and / or RSRP of a DL-RS is above a threshold. The performance metric can also be an average of a number of measurement results. In another example, a “ratio” is configured which specifies the number of times s the event being met over total number of measurement occasions during evaluation window, e.g. the RSRP of service link is below the threshold 3 times out of the 5 measurement occasions within the evaluation window.

[0099] Figure 11 shows a simple example of how an evaluation window can be applied for UE initiated beam reporting. RSRP SSB1 is below a threshold A, and the evaluation window starts. Next, RSRP SSB1 is still below threshold A, which means that two occurrences have happened within the evaluation time window, which causes, the beam report to be initiated. Figure 11 may help in providing background for various embodiments with evaluation windows.[000100] In another embodiment, the UE can be configured with a time duration over which the triggering conditions have to be met before a UE initiated beam report is triggered. This time duration may be referred to as time before trigger (TBT) or time to trigger (TTT). In one embodiment, different TBTs or TTTs may be configured for the first serving link and the second serving link. The reason for this is because the beam widths may be different in the first serving link (associated with DL channels / signals) and the second serving link (associated with UL channels / signals). When the beamwidth of the candidate beam is smaller a larger TBT or TTT may be needed as the metric being measured may vary faster due to UE mobility when compared to the case when the beamwidth of the candidate beam is larger.[000101] In one embodiment, the evaluation time window which is associated to one or multiple triggering conditions for a service link comprises one or more of: a start time, a duration, and an end time. Various embodiments of these are described below.[000102] A start time can be set e.g., according to one or more of the following methods:• The start time is configured by the network node (e.g., via RRC signaling) for a list of triggering conditions (per service link): a. An example of the triggering condition can be receiving DL-RS associated with the UL / DL service link with measured RSRP below a configured threshold; b. The UE can be configured with a timer T1 (or a counter) which will start immediately when the triggering condition(s) are met. According to the timer T1 (or the counter), the UE should perform measurements according to the configuration and prepare the UE initiated beam report.• Implicitly decided by UE, and some examples are: a. After UE has switched to a new beam; b. When UE experiences e.g., low RSRP / SINR / RSRQ / panel blocking (i.e. a UE panel is blocked by a an object which quickly increase the path loss to that panel).[000103] A duration can be determined by e.g., one or more of following factors:• Explicitly configured by the network node via e.g., RRC signaling. In one example, the network configured timer has an associated duration, where the duration can be in terms of a number of ms / symbols / slots etc. The duration is configured by the network node based on e.g., the deployment scenario, the traffic load, the propagation environment etc. In one detailed embodiment, the value range of the duration can include 0 which means the UE will send the beam report immediately if the measurement result fulfills the event criteria.• Associated to the periodicity of DL-RS configured to the serving link. In one example, denote T as the periodicity of the DL-RS, N is an integer, the duration of the evaluation window can be N*T. E.g., SSB2 has periodicity of T= 40ms, N is configured as 10 in RRC signaling or per-determined in the specification, the duration is 400ms.• Associated to the TDD pattern, and / or numerology (subcarrier spacing), and / or bandwidth part etc.[000104] An end time can comprise a time after which the UE will generate a beam report if the conditions are met for both link quality and evaluation window, and can be determined by e.g.,• Accumulated timer has reached the configured duration and expires;• A number K of occurring occasions when the measured quality fulfills one or multiple triggering condition(s), e.g., lower than a DL-RS RSRP / SINR threshold; or• The evaluation window may count backward, i.e., from the latest SSB / C SIRS or a set of SSB / CSI-RS being received before the slot a UE initiated a beam report is sent, if the number of occurring occasions or ratio fulfill the triggering condition within the duration of the window.[000105] In one embodiment, the timer / counter is reset after each beam report, regardless of UE initiated or gNB requested.[000106] In one embodiment, a timer / counter can be configured by the network to avoid two similar UE initiated beam reports within a short time. In this case, a timer starts immediately when a UE initiated beam report is transmitted. Before the timer is expired, the UE cannot transmit another UE initiated beam report with same information.UE Capability Signaling[000107] In one embodiment, a UE capability message is used to indicate the support of UE initiated beam report and where the UE capability message contains one or more of the following types of information related to the trigger condition:• Support of separate trigger conditions for first serving link and second serving link, where the first serving link is associated with an applied Unified DL TCI state and where the second serving link is associated with an applied Unified UL TCI state• Support of maximum number of DL and / or UL evaluation links.• Supported maximum number or DL and / or UL evaluation links for reporting Support of UL performance metrics for the trigger condition of second serving link associated with an applied Unified UL TCI state, where ethe ULperformance metric for example can include one or more of the following UL output power performance metrics a. P-MPR associated with the spatial filter used to receive the DL-RS associated with the applied Unified UL TCI state; b. Maximum output power (e.g. Pcmax) associated with the spatial filter used to receive the DL-RS associated with the applied Unified UL TCI state; c. Maximum EIRP associated with the UE panel used to receive the DLRS associated with the applied Unified UL TCI state; d. Power headroom (e.g. assuming a default PUSCH transmission) for the spatial filter used to receive the DL-RS associated with the applied Unified UL TCI state.[000108] In one embodiment, a UE capability message is used to indicate the support of the measurement window for UE initiated beam report, e.g. :• Supported timer / counter and / or maximum number of measurement occasions for measurement window;• Supported maximum number of evaluated beams within measurement window;• Supported triggering event Types with time-domain requirement.Additional Embodiments[000109] Figure 12 shows a possible method embodiment under the present disclosure. Method 1400 is a method performed by a UE for initiating a beam report, where the UE has been indicated with a DL serving link for DL reception and an UL serving link for UL transmission. Step 1410 is receiving, from a network node, a UE initiated beam report configuration, wherein the UE initiated beam report configuration contains a configuration of one or more trigger events and a configuration of one or more DL-RSs. Step 1420 is performing one or more measurements on the one or more DL reference signals. Step 1430 is evaluating, based at least in part on the one or more measurements, if the one or more trigger events has happened associated with the DL serving link or the UL serving link. Method 1400 can comprise a variety of alternative, optional, or additional steps. For example, certain embodiments can comprise theUE signaling to a network node an indication of beam reporting capability. In some embodiments, if a beam report trigger event has happened, then the UE indicates to the network node that the UE will send a beam report. Embodiments can comprise transmitting the beam report to the network node. Some embodiments can include receiving from the network node a response to the beam report. Certain embodiments can further comprise applying a spatial filter associated with a beam identified in the beam report. Other embodiments can include communicating with the network node on an identified beam.[000110] Figure 13 illustrates another possible method embodiment under the present disclosure. Method 1600 is a method performed by a network node for configuring a UE for initiating a beam report, where the UE has been indicated with a DL serving link for DL reception and an UL serving link for UL transmission. Step 1610 is transmitting, to the UE, a UE initiated beam report configuration, wherein the UE initiated beam report configuration contains a configuration of one or more trigger events and a configuration of one or more DL-RSs. Method 1600 can comprise a variety of alternative, optional, or additional steps. For example, method 1600 can in some embodiments further comprise receiving from the UE an indication of beam reporting capability. Certain embodiments can include receiving from the UE an indication that a beam report based at least in part on measurements of the one or more downlink reference signals will be sent. Other embodiments can comprise receiving from the UE the beam report. Some embodiments further comprise transmitting to the UE a response to the beam report, or communicating with the UE on the identified beam.[000111] Figure 14 shows an example of a communication system 2100 in accordance with some embodiments. In the example, the communication system 2100 includes a telecommunication network 2102 that includes an access network 2104, such as a RAN, and a core network 2106, which includes one or more core network nodes 2108. The access network 2104 includes one or more access network nodes, such as network nodes 2110a and 2110b (one or more of which may be generally referred to as network nodes 2110), or any other similar 3rd Generation Partnership Project (3GPP) access node or non-3GPP access point. The network nodes 2110 facilitate direct or indirect connection of UE, such as by connecting UEs 2112a, 2112b, 2112c, and 2112d (one or more of which may be generally referred to as UEs 2112) to the core network 2106 over one or more wireless connections.[000112] Example wireless communications over a wireless connection include transmitting and / or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and / or other types of signals suitable for conveying information without the use of wires, cables, or other material conductors. Moreover, in different embodiments, the communication system 1100 may include any number of wired or wireless networks, network nodes, UEs, and / or any other components or systems that may facilitate or participate in the communication of data and / or signals whether via wired or wireless connections. The communication system 2100 may include and / or interface with any type of communication, telecommunication, data, cellular, radio network, and / or other similar type of system.[000113] The UEs 2112 may be any of a wide variety of communication devices, including wireless devices arranged, configured, and / or operable to communicate wirelessly with the network nodes 2110 and other communication devices. Similarly, the network nodes 2110 are arranged, capable, configured, and / or operable to communicate directly or indirectly with the UEs 2112 and / or with other network nodes or equipment in the telecommunication network 2102 to enable and / or provide network access, such as wireless network access, and / or to perform other functions, such as administration in the telecommunication network 2102.[000114] In the depicted example, the core network 2106 connects the network nodes 2110 to one or more hosts, such as host 2116. These connections may be direct or indirect via one or more intermediary networks or devices. In other examples, network nodes may be directly coupled to hosts. The core network 2106 includes one more core network nodes (e.g., core network node 2108) that are structured with hardware and software components. Features of these components may be substantially similar to those described with respect to the UEs, network nodes, and / or hosts, such that the descriptions thereof are generally applicable to the corresponding components of the core network node 2108. Example core network nodes include functions of one or more of a Mobile Switching Center (MSC), Mobility Management Entity (MME), Home Subscriber Server (HSS), Access and Mobility Management Function (AMF), Session Management Function (SMF), Authentication Server Function (AUSF), Subscription Identifier De-concealing function (SIDF), Unified Data Management (UDM), Security Edge Protection Proxy (SEPP), Network Exposure Function (NEF), and / or a User Plane Function (UPF).[000115] The host 2116 may be under the ownership or control of a service provider other than an operator or provider of the access network 2104 and / or the telecommunicationnetwork 2102, and may be operated by the service provider or on behalf of the service provider. The host 2116 may host a variety of applications to provide one or more service. Examples of such applications include live and pre-recorded audio / video content, data collection services such as retrieving and compiling data on various ambient conditions detected by a plurality of UEs, analytics functionality, social media, functions for controlling or otherwise interacting with remote devices, functions for an alarm and surveillance center, or any other such function performed by a server.[000116] As a whole, the communication system 2100 of Figure 14 enables connectivity between the UEs, network nodes, and hosts. In that sense, the communication system may be configured to operate according to predefined rules or procedures, such as specific standards that include, but are not limited to: Global System for Mobile Communications (GSM); Universal Mobile Telecommunications System (UMTS); Long Term Evolution (LTE), and / or other suitable 2G, 3G, 4G, 5G standards, or any applicable future generation standard (e.g., 6G); wireless local area network (WLAN) standards, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards (WiFi); and / or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z- Wave, Near Field Communication (NFC) ZigBee, LiFi, and / or any low-power wide-area network (LPWAN) standards such as LoRa and Sigfox.[000117] In some examples, the telecommunication network 2102 is a cellular network that implements 3GPP standardized features. Accordingly, the telecommunications network 2102 may support network slicing to provide different logical networks to different devices that are connected to the telecommunication network 2102. For example, the telecommunications network 2102 may provide Ultra Reliable Low Latency Communication (URLLC) services to some UEs, while providing Enhanced Mobile Broadband (eMBB) services to other UEs, and / or Massive Machine Type Communication (mMTC)ZMassive loT services to yet further UEs.[000118] In some examples, the UEs 2112 are configured to transmit and / or receive information without direct human interaction. For instance, a UE may be designed to transmit information to the access network 2104 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network 2104. Additionally, a UE may be configured for operating in single- or multi-RAT or multi-standard mode. For example, a UEmay operate with any one or combination of Wi-Fi, NR (New Radio) and LTE, i.e. being configured for multi-radio dual connectivity (MR-DC), such as E-UTRAN (Evolved-UMTS Terrestrial Radio Access Network) New Radio - Dual Connectivity (EN-DC).[000119] In the example, the hub 2114 communicates with the access network 2104 to facilitate indirect communication between one or more UEs (e.g., UE 2112c and / or 2112d) and network nodes (e.g., network node 2110b). In some examples, the hub 2114 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs. For example, the hub 2114 may be a broadband router enabling access to the core network 2106 for the UEs. As another example, the hub 2114 may be a controller that sends commands or instructions to one or more actuators in the UEs. Commands or instructions may be received from the UEs, network nodes 2110, or by executable code, script, process, or other instructions in the hub 2114. As another example, the hub 2114 may be a data collector that acts as temporary storage for UE data and, in some embodiments, may perform analysis or other processing of the data. As another example, the hub 2114 may be a content source. For example, for a UE that is a VR headset, display, loudspeaker or other media delivery device, the hub 2114 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub 2114 then provides to the UE either directly, after performing local processing, and / or after adding additional local content. In still another example, the hub 2114 acts as a proxy server or orchestrator for the UEs, in particular in if one or more of the UEs are low energy loT devices.[000120] The hub 2114 may have a constant / persistent or intermittent connection to the network node 2110b. The hub 2114 may also allow for a different communication scheme and / or schedule between the hub 2114 and UEs (e.g., UE 2112c and / or 2112d), and between the hub 2114 and the core network 2106. In other examples, the hub 2114 is connected to the core network 2106 and / or one or more UEs via a wired connection. Moreover, the hub 2114 may be configured to connect to an M2M service provider over the access network 1104 and / or to another UE over a direct connection. In some scenarios, UEs may establish a wireless connection with the network nodes 2110 while still connected via the hub 2114 via a wired or wireless connection. In some embodiments, the hub 2114 may be a dedicated hub - that is, a hub whose primary function is to route communications to / from the UEs from / to the network node 2110b. In other embodiments, the hub 2114 may be a non-dedicated hub - that is, a device which is capable ofoperating to route communications between the UEs and network node 2110b, but which is additionally capable of operating as a communication start and / or end point for certain data channels.[000121] Figure 15 shows a UE 2200 in accordance with some embodiments. As used herein, a UE refers to a device capable, configured, arranged and / or operable to communicate wirelessly with network nodes and / or other UEs. Examples of a UE include, but are not limited to, a smart phone, mobile phone, cell phone, voice over IP (VoIP) phone, wireless local loop phone, desktop computer, personal digital assistant (PDA), wireless cameras, gaming console or device, music storage device, playback appliance, wearable terminal device, wireless endpoint, mobile station, tablet, laptop, laptop-embedded equipment (LEE), laptop-mounted equipment (LME), smart device, wireless customer-premise equipment (CPE), vehicle-mounted or vehicle embedded / integrated wireless device, etc. Other examples include any UE identified by the 3rd Generation Partnership Project (3GPP), including a narrow band internet of things (NB-IoT) UE, a machine type communication (MTC) UE, and / or an enhanced MTC (eMTC) UE.[000122] A UE may support device-to-device (D2D) communication, for example by implementing a 3 GPP standard for sidelink communication, Dedicated Short-Range Communication (DSRC), vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), or vehicle-to- everything (V2X). In other examples, a UE may not necessarily have a user in the sense of a human user who owns and / or operates the relevant device. Instead, a UE may represent a device that is intended for sale to, or operation by, a human user but which may not, or which may not initially, be associated with a specific human user (e.g., a smart sprinkler controller). Alternatively, a UE may represent a device that is not intended for sale to, or operation by, an end user but which may be associated with or operated for the benefit of a user (e.g., a smart power meter).[000123] The UE 2200 includes processing circuitry 2202 that is operatively coupled via a bus 2204 to an input / output interface 2206, a power source 2208, a memory 2210, a communication interface 2212, and / or any other component, or any combination thereof. Certain UEs may utilize all or a subset of the components shown in Figure 10. The level of integration between the components may vary from one UE to another UE. Further, certain UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.[000124] The processing circuitry 2202 is configured to process instructions and data and may be configured to implement any sequential state machine operative to execute instructions stored as machine- readable computer programs in the memory 2210. The processing circuitry 2202 may be implemented as one or more hardware-implemented state machines (e.g., in discrete logic, field-programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), etc.); programmable logic together with appropriate firmware; one or more stored computer programs, general-purpose processors, such as a microprocessor or digital signal processor (DSP), together with appropriate software; or any combination of the above. For example, the processing circuitry 2202 may include multiple central processing units (CPUs).[000125] In the example, the input / output interface 2206 may be configured to provide an interface or interfaces to an input device, output device, or one or more input and / or output devices. Examples of an output device include a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smartcard, another output device, or any combination thereof. An input device may allow a user to capture information into the UE 2200. Examples of an input device include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a web camera, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smartcard, and the like. The presencesensitive display may include a capacitive or resistive touch sensor to sense input from a user. A sensor may be, for instance, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, a biometric sensor, etc., or any combination thereof. An output device may use the same type of interface port as an input device. For example, a Universal Serial Bus (USB) port may be used to provide an input device and an output device.[000126] In some embodiments, the power source 2208 is structured as a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic device, or power cell, may be used. The power source 2208 may further include power circuitry for delivering power from the power source 2208 itself, and / or an external power source, to the various parts of the UE 2200 via input circuitry or an interface such as an electrical power cable. Delivering power may be, for example, for charging of the power source 2208. Power circuitry may perform any formatting, converting, or other modification to the power from the power source 2208 to make the power suitable for the respective components of the UE 2200 to which power is supplied.[000127] The memory 2210 may be or be configured to include memory such as random access memory (RAM), read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disks, optical disks, hard disks, removable cartridges, flash drives, and so forth. In one example, the memory 2210 includes one or more application programs 2214, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data 2216. The memory 2210 may store, for use by the UE 2200, any of a variety of various operating systems or combinations of operating systems.[000128] The memory 2210 may be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, high-density digital versatile disc (HD- DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, holographic digital data storage (HDDS) optical disc drive, external mini-dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), external micro-DIMM SDRAM, smartcard memory such as tamper resistant module in the form of a universal integrated circuit card (UICC) including one or more subscriber identity modules (SIMs), such as a USIM and / or ISIM, other memory, or any combination thereof. The UICC may for example be an embedded UICC (eUICC), integrated UICC (iUICC) or a removable UICC commonly known as ‘SIM card.’ The memory 2210 may allow the UE 2200 to access instructions, application programs and the like, stored on transitory or non-transitory memory media, to off-load data, or to upload data. An article of manufacture, such as one utilizing a communication system may be tangibly embodied as or in the memory 2210, which may be or comprise a device-readable storage medium.[000129] The processing circuitry 2202 may be configured to communicate with an access network or other network using the communication interface 2212. The communication interface 2212 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna 2222. The communication interface 2212 may include one or more transceivers used to communicate, such as by communicating with one or more remote transceivers of another device capable of wireless communication (e.g., another UE or a network node in an access network). Each transceiver may include a transmitter 2218 and / or a receiver 2220 appropriate to provide network communications (e.g., optical, electrical, frequencyallocations, and so forth). Moreover, the transmitter 2218 and receiver 2220 may be coupled to one or more antennas (e.g., antenna 2222) and may share circuit components, software or firmware, or alternatively be implemented separately.[000130] In the illustrated embodiment, communication functions of the communication interface 2212 may include cellular communication, Wi-Fi communication, LPWAN communication, data communication, voice communication, multimedia communication, short-range communications such as Bluetooth, near-field communication, location-based communication such as the use of the global positioning system (GPS) to determine a location, another like communication function, or any combination thereof. Communications may be implemented in according to one or more communication protocols and / or standards, such as IEEE 802.11, Code Division Multiplexing Access (CDMA), Wideband Code Division Multiple Access (WCDMA), GSM, LTE, New Radio (NR), UMTS, WiMax, Ethernet, transmission control protocol / internet protocol (TCP / IP), synchronous optical networking (SONET), Asynchronous Transfer Mode (ATM), QUIC, Hypertext Transfer Protocol (HTTP), and so forth.[000131] Regardless of the type of sensor, a UE may provide an output of data captured by its sensors, through its communication interface 2212, via a wireless connection to a network node. Data captured by sensors of a UE can be communicated through a wireless connection to a network node via another UE. The output may be periodic (e.g., once every 15 minutes if it reports the sensed temperature), random (e.g., to even out the load from reporting from several sensors), in response to a triggering event (e.g., when moisture is detected an alert is sent), in response to a request (e.g., a user initiated request), or a continuous stream (e.g., a live video feed of a patient).[000132] As another example, a UE comprises an actuator, a motor, or a switch, related to a communication interface configured to receive wireless input from a network node via a wireless connection. In response to the received wireless input the states of the actuator, the motor, or the switch may change. For example, the UE may comprise a motor that adjusts the control surfaces or rotors of a drone in flight according to the received input or to a robotic arm performing a medical procedure according to the received input.[000133] A UE, when in the form of an Internet of Things (loT) device, may be a device for use in one or more application domains, these domains comprising, but not limited to, city wearable technology, extended industrial application and healthcare. Non-limiting examplesof such an loT device are a device which is or which is embedded in: a connected refrigerator or freezer, a TV, a connected lighting device, an electricity meter, a robot vacuum cleaner, a voice controlled smart speaker, a home security camera, a motion detector, a thermostat, a smoke detector, a door / window sensor, a flood / moisture sensor, an electrical door lock, a connected doorbell, an air conditioning system like a heat pump, an autonomous vehicle, a surveillance system, a weather monitoring device, a vehicle parking monitoring device, an electric vehicle charging station, a smart watch, a fitness tracker, a head-mounted display for Augmented Reality (AR) or Virtual Reality (VR), a wearable for tactile augmentation or sensory enhancement, a water sprinkler, an animal- or item-tracking device, a sensor for monitoring a plant or animal, an industrial robot, an Unmanned Aerial Vehicle (UAV), and any kind of medical device, like a heart rate monitor or a remote controlled surgical robot. A UE in the form of an loT device comprises circuitry and / or software in dependence of the intended application of the loT device in addition to other components as described in relation to the UE 2200 shown in Figure 10.[000134] As yet another specific example, in an loT scenario, a UE may represent a machine or other device that performs monitoring and / or measurements, and transmits the results of such monitoring and / or measurements to another UE and / or a network node. The UE may in this case be an M2M device, which may in a 3 GPP context be referred to as an MTC device. As one particular example, the UE may implement the 3 GPP NB-IoT standard. In other scenarios, a UE may represent a vehicle, such as a car, a bus, a truck, a ship and an airplane, or other equipment that is capable of monitoring and / or reporting on its operational status or other functions associated with its operation.[000135] In practice, any number of UEs may be used together with respect to a single use case. For example, a first UE might be or be integrated in a drone and provide the drone’s speed information (obtained through a speed sensor) to a second UE that is a remote controller operating the drone. When the user makes changes from the remote controller, the first UE may adjust the throttle on the drone (e.g. by controlling an actuator) to increase or decrease the drone’s speed. The first and / or the second UE can also include more than one of the functionalities described above. For example, a UE might comprise the sensor and the actuator, and handle communication of data for both the speed sensor and the actuators.[000136] Figure 16 shows a network node 3300 in accordance with some embodiments. As used herein, network node refers to equipment capable, configured, arrangedand / or operable to communicate directly or indirectly with a UE and / or with other network nodes or equipment, in a telecommunication network. Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs) and NR NodeBs (gNBs)).[000137] Base stations may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and so, depending on the provided amount of coverage, may be referred to as femto base stations, pico base stations, micro base stations, or macro base stations. A base station may be a relay node or a relay donor node controlling a relay. A network node may also include one or more (or all) parts of a distributed radio base station such as centralized digital units and / or remote radio units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such remote radio units may or may not be integrated with an antenna as an antenna integrated radio. Parts of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS).[000138] Other examples of network nodes include multiple transmission point (multi-TRP) 5G access nodes, multi-standard radio (MSR) equipment such as MSRBSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), base transceiver stations (BTSs), transmission points, transmission nodes, multi-cell / multicast coordination entities (MCEs), Operation and Maintenance (O&M) nodes, Operations Support System (OSS) nodes, Self-Organizing Network (SON) nodes, positioning nodes (e.g., Evolved Serving Mobile Location Centers (E-SMLCs)), and / or Minimization of Drive Tests (MDTs).[000139] The network node 3300 includes a processing circuitry 3302, a memory 3304, a communication interface 3306, and a power source 3308. The network node 3300 may be composed of multiple physically separate components (e.g., a NodeB component and a RNC component, or a BTS component and a BSC component, etc.), which may each have their own respective components. In certain scenarios in which the network node 3300 comprises multiple separate components (e.g., BTS and BSC components), one or more of the separate components may be shared among several network nodes. For example, a single RNC may control multiple NodeBs. In such a scenario, each unique NodeB and RNC pair, may in some instances be considered a single separate network node. In some embodiments, the network node 1300 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memory 3304 for different RATs) and somecomponents may be reused (e.g., a same antenna 3310 may be shared by different RATs). The network node 3300 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 1300, for example GSM, WCDMA, LTE, NR, WiFi, Zigbee, Z-wave, LoRaWAN, Radio Frequency Identification (RFID) or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within network node 1300.[000140] The processing circuitry 3302 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software and / or encoded logic operable to provide, either alone or in conjunction with other network node 3300 components, such as the memory 3304, to provide network node 3300 functionality.[000141] In some embodiments, the processing circuitry 3302 includes a system on a chip (SOC). In some embodiments, the processing circuitry 3302 includes one or more of radio frequency (RF) transceiver circuitry 3312 and baseband processing circuitry 3314. In some embodiments, the radio frequency (RF) transceiver circuitry 3312 and the baseband processing circuitry 3314 may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units. In alternative embodiments, part or all of RF transceiver circuitry 3312 and baseband processing circuitry 3314 may be on the same chip or set of chips, boards, or units.[000142] The memory 3304 may comprise any form of volatile or non-volatile computer-readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), readonly memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and / or any other volatile or non-volatile, non-transitory device-readable and / or computer-executable memory devices that store information, data, and / or instructions that may be used by the processing circuitry 3302. The memory 3304 may store any suitable instructions, data, or information, including a computer program, software, an application including one or more of logic, rules, code, tables, and / or other instructions capable of being executed by the processing circuitry 3302 and utilized by the network node 3300. The memory 3304 may be used to store any calculations madeby the processing circuitry 3302 and / or any data received via the communication interface 3306. In some embodiments, the processing circuitry 3302 and memory 3304 is integrated.[000143] The communication interface 3306 is used in wired or wireless communication of signaling and / or data between a network node, access network, and / or UE. As illustrated, the communication interface 3306 comprises port(s) / terminal(s) 3316 to send and receive data, for example to and from a network over a wired connection. The communication interface 3306 also includes radio front-end circuitry 3318 that may be coupled to, or in certain embodiments a part of, the antenna 3310. Radio front-end circuitry 3318 comprises filters 3320 and amplifiers 3322. The radio front-end circuitry 3318 may be connected to an antenna 3310 and processing circuitry 3302. The radio front-end circuitry may be configured to condition signals communicated between antenna 3310 and processing circuitry 3302. The radio front-end circuitry 3318 may receive digital data that is to be sent out to other network nodes or UEs via a wireless connection. The radio front-end circuitry 3318 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 3320 and / or amplifiers 3322. The radio signal may then be transmitted via the antenna 3310. Similarly, when receiving data, the antenna 3310 may collect radio signals which are then converted into digital data by the radio front-end circuitry 3318. The digital data may be passed to the processing circuitry 3302. In other embodiments, the communication interface may comprise different components and / or different combinations of components.[000144] In certain alternative embodiments, the network node 3300 does not include separate radio front-end circuitry 3318, instead, the processing circuitry 3302 includes radio frontend circuitry and is connected to the antenna 3310. Similarly, in some embodiments, all or some of the RF transceiver circuitry 3312 is part of the communication interface 3306. In still other embodiments, the communication interface 3306 includes one or more ports or terminals 3316, the radio front-end circuitry 3318, and the RF transceiver circuitry 3312, as part of a radio unit (not shown), and the communication interface 3306 communicates with the baseband processing circuitry 3314, which is part of a digital unit (not shown).[000145] The antenna 3310 may include one or more antennas, or antenna arrays, configured to send and / or receive wireless signals. The antenna 3310 may be coupled to the radio front-end circuitry 3318 and may be any type of antenna capable of transmitting and receiving dataand / or signals wirelessly. In certain embodiments, the antenna 3310 is separate from the network node 3300 and connectable to the network node 3300 through an interface or port.[000146] The antenna 3310, communication interface 3306, and / or the processing circuitry 3302 may be configured to perform any receiving operations and / or certain obtaining operations described herein as being performed by the network node. Any information, data and / or signals may be received from a UE, another network node and / or any other network equipment. Similarly, the antenna 3310, the communication interface 3306, and / or the processing circuitry 3302 may be configured to perform any transmitting operations described herein as being performed by the network node. Any information, data and / or signals may be transmitted to a UE, another network node and / or any other network equipment.[000147] The power source 3308 provides power to the various components of network node 3300 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). The power source 3308 may further comprise, or be coupled to, power management circuitry to supply the components of the network node 3300 with power for performing the functionality described herein. For example, the network node 3300 may be connectable to an external power source (e.g., the power grid, an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry of the power source 3308. As a further example, the power source 3308 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry. The battery may provide backup power should the external power source fail.[000148] Embodiments of the network node 3300 may include additional components beyond those shown in Figure 16 for providing certain aspects of the network node’s functionality, including any of the functionality described herein and / or any functionality necessary to support the subject matter described herein. For example, the network node 3300 may include user interface equipment to allow input of information into the network node 3300 and to allow output of information from the network node 3300. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node 3300.[000149] Figure 17 is a block diagram of a host 4400, which may be an embodiment of the host 2116 of Figure 14, in accordance with various aspects described herein. As used herein, the host 4400 may be or comprise various combinations hardware and / or software, including astandalone server, a blade server, a cloud-implemented server, a distributed server, a virtual machine, container, or processing resources in a server farm. The host 4400 may provide one or more services to one or more UEs.[000150] The host 4400 includes processing circuitry 4402 that is operatively coupled via a bus 4404 to an input / output interface 4406, a network interface 4408, a power source 4410, and a memory 4412. Other components may be included in other embodiments. Features of these components may be substantially similar to those described with respect to the devices of previous figures, such as Figures 15 and 16, such that the descriptions thereof are generally applicable to the corresponding components of host 4400.[000151] The memory 4412 may include one or more computer programs including one or more host application programs 4414 and data 4416, which may include user data, e.g., data generated by a UE for the host 4400 or data generated by the host 4400 for a UE. Embodiments of the host 4400 may utilize only a subset or all of the components shown. The host application programs 4414 may be implemented in a container-based architecture and may provide support for video codecs (e.g., Versatile Video Coding (WC), High Efficiency Video Coding (HEVC), Advanced Video Coding (AVC), MPEG, VP9) and audio codecs (e.g., FLAC, Advanced Audio Coding (AAC), MPEG, G.711), including transcoding for multiple different classes, types, or implementations of UEs (e.g., handsets, desktop computers, wearable display systems, heads-up display systems). The host application programs 4414 may also provide for user authentication and licensing checks and may periodically report health, routes, and content availability to a central node, such as a device in or on the edge of a core network. Accordingly, the host 4400 may select and / or indicate a different host for over-the-top services for a UE. The host application programs 4414 may support various protocols, such as the HTTP Live Streaming (HLS) protocol, Real-Time Messaging Protocol (RTMP), Real-Time Streaming Protocol (RTSP), Dynamic Adaptive Streaming over HTTP (MPEG-DASH), etc.[000152] Figure 18 is a block diagram illustrating a virtualization environment 5500 in which functions implemented by some embodiments may be virtualized. In the present context, virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices and networking resources. As used herein, virtualization can be applied to any device described herein, or components thereof, and relates to an implementation in which at least a portion of the functionality is implemented as one or morevirtual components. Some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines (VMs) implemented in one or more virtual environments 5500 hosted by one or more of hardware nodes, such as a hardware computing device that operates as a network node, UE, core network node, or host. Further, in embodiments in which the virtual node does not require radio connectivity (e.g., a core network node or host), then the node may be entirely virtualized.[000153] Applications 5502 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) are run in the virtualization environment 5500 to implement some of the features, functions, and / or benefits of some of the embodiments disclosed herein.[000154] Hardware 5504 includes processing circuitry, memory that stores software and / or instructions executable by hardware processing circuitry, and / or other hardware devices as described herein, such as a network interface, input / output interface, and so forth. Software may be executed by the processing circuitry to instantiate one or more virtualization layers 5506 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VMs 5508a and 5508b (one or more of which may be generally referred to as VMs 5508), and / or perform any of the functions, features and / or benefits described in relation with some embodiments described herein. The virtualization layer 5506 may present a virtual operating platform that appears like networking hardware to the VMs 5508.[000155] The VMs 5508 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer 5506. Different embodiments of the instance of a virtual appliance 5502 may be implemented on one or more of VMs 5508, and the implementations may be made in different ways. Virtualization of the hardware is in some contexts referred to as network function virtualization (NFV). NFV may be used to consolidate many network equipment types onto industry standard high volume server hardware, physical switches, and physical storage, which can be located in data centers, and customer premise equipment.[000156] In the context of NFV, a VM 5508 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non-virtualized machine. Each of the VMs 5508, and that part of hardware 5504 that executes that VM, be it hardware dedicated to that VM and / or hardware shared by that VM with others of the VMs, formsseparate virtual network elements. Still in the context of NFV, a virtual network function is responsible for handling specific network functions that run in one or more VMs 5508 on top of the hardware 5504 and corresponds to the application 5502.[000157] Hardware 5504 may be implemented in a standalone network node with generic or specific components. Hardware 5504 may implement some functions via virtualization. Alternatively, hardware 5504 may be part of a larger cluster of hardware (e.g., such as in a data center or CPE) where many hardware nodes work together and are managed via management and orchestration 5510, which, among others, oversees lifecycle management of applications 5502. In some embodiments, hardware 5504 is coupled to one or more radio units that each include one or more transmitters and one or more receivers that may be coupled to one or more antennas. Radio units may communicate directly with other hardware nodes via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station. In some embodiments, some signaling can be provided with the use of a control system 5512 which may alternatively be used for communication between hardware nodes and radio units.[000158] Although the computing devices described herein (e.g., UEs, network nodes, hosts) may include the illustrated combination of hardware components, other embodiments may comprise computing devices with different combinations of components. It is to be understood that these computing devices may comprise any suitable combination of hardware and / or software needed to perform the tasks, features, functions and methods disclosed herein. Determining, calculating, obtaining or similar operations described herein may be performed by processing circuitry, which may process information by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and / or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination. Moreover, while components are depicted as single boxes located within a larger box, or nested within multiple boxes, in practice, computing devices may comprise multiple different physical components that make up a single illustrated component, and functionality may be partitioned between separate components. For example, a communication interface may be configured to include any of the components described herein, and / or the functionality of the components may be partitioned between the processing circuitry and the communication interface.In another example, non-computationally intensive functions of any of such components may be implemented in software or firmware and computationally intensive functions may be implemented in hardware.[000159] In certain embodiments, some or all of the functionality described herein may be provided by processing circuitry executing instructions stored on in memory, which in certain embodiments may be a computer program product in the form of a non-transitory computer-readable storage medium. In alternative embodiments, some or all of the functionality may be provided by the processing circuitry without executing instructions stored on a separate or discrete device-readable storage medium, such as in a hard-wired manner. In any of those particular embodiments, whether executing instructions stored on a non-transitory computer- readable storage medium or not, the processing circuitry can be configured to perform the described functionality. The benefits provided by such functionality are not limited to the processing circuitry alone or to other components of the computing device, but are enjoyed by the computing device as a whole, and / or by end users and a wireless network generally.[000160] It will be appreciated that computer systems are increasingly taking a wide variety of forms. In this description and in the claims, the terms “controller,” “computer system,” or “computing system” are defined broadly as including any device or system — or combination thereof — that includes at least one physical and tangible processor and a physical and tangible memory capable of having thereon computer-executable instructions that may be executed by a processor. By way of example, not limitation, the term “computer system” or “computing system,” as used herein is intended to include personal computers, desktop computers, laptop computers, tablets, hand-held devices (e.g., mobile telephones, PDAs, pagers), microprocessor-based or programmable consumer electronics, minicomputers, mainframe computers, multi-processor systems, network PCs, distributed computing systems, datacenters, message processors, routers, switches, and even devices that conventionally have not been considered a computing system, such as wearables (e.g., glasses).[000161] The computing system also has thereon multiple structures often referred to as an “executable component.” For instance, the memory of a computing system can include an executable component. The term “executable component” is the name for a structure that is well understood to one of ordinary skill in the art in the field of computing as being a structure that can be software, hardware, or a combination thereof. For instance, when implemented in software, oneof ordinary skill in the art would understand that the structure of an executable component may include software objects, routines, methods, and so forth, that may be executed by one or more processors on the computing system, whether such an executable component exists in the heap of a computing system, or whether the executable component exists on computer-readable storage media. The structure of the executable component exists on a computer-readable medium in such a form that it is operable, when executed by one or more processors of the computing system, to cause the computing system to perform one or more functions, such as the functions and methods described herein. Such a structure may be computer-readable directly by a processor — as is the case if the executable component were binary. Alternatively, the structure may be structured to be interpretable and / or compiled — whether in a single stage or in multiple stages — so as to generate such binary that is directly interpretable by a processor.[000162] The terms “component,” “service,” “engine,” “module,” “control,” “generator,” or the like may also be used in this description. As used in this description and in this case, these terms — whether expressed with or without a modifying clause — are also intended to be synonymous with the term “executable component” and thus also have a structure that is well understood by those of ordinary skill in the art of computing.[000163] In terms of computer implementation, a computer is generally understood to comprise one or more processors or one or more controllers, and the terms computer, processor, and controller may be employed interchangeably. When provided by a computer, processor, or controller, the functions may be provided by a single dedicated computer or processor or controller, by a single shared computer or processor or controller, or by a plurality of individual computers or processors or controllers, some of which may be shared or distributed. Moreover, the term “processor” or “controller” also refers to other hardware capable of performing such functions and / or executing software, such as the example hardware recited above.[000164] In general, the various exemplary embodiments may be implemented in hardware or special purpose chips, circuits, software, logic, or any combination thereof. For example, some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software which may be executed by a controller, microprocessor, or other computing device, although the disclosure is not limited thereto. While various aspects of the exemplary embodiments of this disclosure may be illustrated and described as block diagrams, flow charts, or using some other pictorial representation, it is well understood that these blocks,apparatus, systems, techniques, or methods described herein may be implemented in, as nonlimiting examples, hardware, software, firmware, special purpose circuits or logic, general purpose hardware or controller or other computing devices, or some combination thereof.[000165] While not all computing systems require a user interface, in some embodiments a computing system includes a user interface for use in communicating information from / to a user. The user interface may include output mechanisms as well as input mechanisms. The principles described herein are not limited to the precise output mechanisms or input mechanisms as such will depend on the nature of the device. However, output mechanisms might include, for instance, speakers, displays, tactile output, projections, holograms, and so forth. Examples of input mechanisms might include, for instance, microphones, touchscreens, projections, holograms, cameras, keyboards, stylus, mouse, or other pointer input, sensors of any type, and so forth.Abbreviations and Defined Terms[000166] To assist in understanding the scope and content of this written description and the appended claims, a select few terms are defined directly below. Unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which the present disclosure pertains.[000167] The terms “approximately,” “about,” and “substantially,” as used herein, represent an amount or condition close to the specific stated amount or condition that still performs a desired function or achieves a desired result. For example, the terms “approximately,” “about,” and “substantially” may refer to an amount or condition that deviates by less than 10%, or by less than 5%, or by less than 1%, or by less than 0.1%, or by less than 0.01% from a specifically stated amount or condition.[000168] Various aspects of the present disclosure, including devices, systems, and methods may be illustrated with reference to one or more embodiments or implementations, which are exemplary in nature. As used herein, the term “exemplary” means “serving as an example, instance, or illustration,” and should not necessarily be construed as preferred or advantageous over other embodiments disclosed herein. In addition, reference to an “implementation” of the present disclosure or embodiments includes a specific reference to one or more embodiments thereof, and vice versa, and is intended to provide illustrative examples without limiting the scopeof the present disclosure, which is indicated by the appended claims rather than by the present description.[000169] As used in the specification, a word appearing in the singular encompasses its plural counterpart, and a word appearing in the plural encompasses its singular counterpart, unless implicitly or explicitly understood or stated otherwise. Thus, it will be noted that, as used in this specification and the appended claims, the singular forms “a,” “an” and “the” include plural referents unless the context clearly dictates otherwise. For example, reference to a singular referent (e.g., “a widget”) includes one, two, or more referents unless implicitly or explicitly understood or stated otherwise. Similarly, reference to a plurality of referents should be interpreted as comprising a single referent and / or a plurality of referents unless the content and / or context clearly dictate otherwise. For example, reference to referents in the plural form (e.g., “widgets”) does not necessarily require a plurality of such referents. Instead, it will be appreciated that independent of the inferred number of referents, one or more referents are contemplated herein unless stated otherwise.[000170] References in the specification to "one embodiment," "an embodiment," "an example embodiment," and the like indicate that the embodiment described may include a particular feature, structure, or characteristic, but it is not necessary that every embodiment includes the particular feature, structure, or characteristic. Moreover, such phrases are not necessarily referring to the same embodiment. Further, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is submitted that it is within the knowledge of one skilled in the art to affect such feature, structure, or characteristic in connection with other embodiments whether or not explicitly described.[000171] It shall be understood that although the terms "first" and "second" etc. may be used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another. For example, a first element could be termed a second element, and similarly, a second element could be termed a first element, without departing from the scope of example embodiments. As used herein, the term "and / or" includes any and all combinations of one or more of the associated listed terms.[000172] It will be further understood that the terms "comprises", "comprising", "has", "having", "includes" and / or "including", when used herein, specify the presence of statedfeatures, elements, and / or components etc., but do not preclude the presence or addition of one or more other features, elements, components and / or combinations thereof.Conclusion[000173] The present disclosure includes any novel feature or combination of features disclosed herein either explicitly or any generalization thereof. Various modifications and adaptations to the foregoing exemplary embodiments of this disclosure may become apparent to those skilled in the relevant arts in view of the foregoing description, when read in conjunction with the accompanying drawings. However, any and all modifications will still fall within the scope of the non-limiting and exemplary embodiments of this disclosure.[000174] It is understood that for any given component or embodiment described herein, any of the possible candidates or alternatives listed for that component may generally be used individually or in combination with one another, unless implicitly or explicitly understood or stated otherwise. Additionally, it will be understood that any list of such candidates or alternatives is merely illustrative, not limiting, unless implicitly or explicitly understood or stated otherwise.[000175] In addition, unless otherwise indicated, numbers expressing quantities, constituents, distances, or other measurements used in the specification and claims are to be understood as being modified by the term “about,” as that term is defined herein. Accordingly, unless indicated to the contrary, the numerical parameters set forth in the specification and attached claims are approximations that may vary depending upon the desired properties sought to be obtained by the subject matter presented herein. At the very least, and not as an attempt to limit the application of the doctrine of equivalents to the scope of the claims, each numerical parameter should at least be construed in light of the number of reported significant digits and by applying ordinary rounding techniques. Notwithstanding that the numerical ranges and parameters setting forth the broad scope of the subject matter presented herein are approximations, the numerical values set forth in the specific examples are reported as precisely as possible. Any numerical values, however, inherently contain certain errors necessarily resulting from the standard deviation found in their respective testing measurements.[000176] Any headings and subheadings used herein are for organizational purposes only and are not meant to be used to limit the scope of the description or the claims. The terms and expressions which have been employed herein are used as terms of description and not oflimitation, and there is no intention in the use of such terms and expressions of excluding any equivalents of the features shown and described or portions thereof, but it is recognized that various modifications are possible within the scope of the present disclosure. Thus, it should be understood that although the present disclosure has been specifically disclosed in part by certain embodiments, and optional features, modification and variation of the concepts herein disclosed may be resorted to by those skilled in the art, and such modifications and variations are considered to be within the scope of this present description.[000177] It will also be appreciated that systems, devices, products, kits, methods, and / or processes, according to certain embodiments of the present disclosure may include, incorporate, or otherwise comprise properties or features (e.g., components, members, elements, parts, and / or portions) described in other embodiments disclosed and / or described herein. Accordingly, the various features of certain embodiments can be compatible with, combined with, included in, and / or incorporated into other embodiments of the present disclosure. Thus, disclosure of certain features relative to a specific embodiment of the present disclosure should not be construed as limiting application or inclusion of said features to the specific embodiment. Rather, it will be appreciated that other embodiments can also include said features, members, elements, parts, and / or portions without necessarily departing from the scope of the present disclosure.[000178] Moreover, unless a feature is described as requiring another feature in combination therewith, any feature herein may be combined with any other feature of a same or different embodiment disclosed herein. Furthermore, various well-known aspects of illustrative systems, methods, apparatus, and the like are not described herein in particular detail in order to avoid obscuring aspects of the example embodiments. Such aspects are, however, also contemplated herein.[000179] It will be apparent to one of ordinary skill in the art that methods, devices, device elements, materials, procedures, and techniques other than those specifically described herein can be applied to the practice of the described embodiments as broadly disclosed herein without resort to undue experimentation. All art-known functional equivalents of methods, devices, device elements, materials, procedures, and techniques specifically described herein are intended to be encompassed by this present disclosure.[000180] When a group of materials, compositions, components, or compounds is disclosed herein, it is understood that all individual members of those groups and all subgroupsthereof are disclosed separately. When a Markush group or other grouping is used herein, all individual members of the group and all combinations and sub-combinations possible of the group are intended to be individually included in the disclosure.[000181] The above-described embodiments are examples only. Alterations, modifications, and variations may be effected to the particular embodiments by those of skill in the art without departing from the scope of the description, which is defined solely by the appended claims.

Claims

CLAIMSWhat is claimed is:

1. A method (1400) performed by a user equipment, UE (2200), for initiating a beam report, where the UE has been indicated with a downlink, DL, serving link for DL reception and an uplink, UL, serving link for UL transmission, the method comprising: receiving (1410), from a network node (3300), a UE initiated beam report configuration, wherein the UE initiated beam report configuration contains a configuration of one or more trigger events and a configuration of one or more DL reference signals, DL-RSs; performing (1420) one or more measurements on the one or more DL reference signals; and evaluating (1430), based at least in part on the one or more measurements, if the one or more trigger events has happened associated with the DL serving link or the UL serving link.

2. The method of claim 1, wherein the DL serving link is associated with an indicated DL Transmission Configuration Indicator, TCI, state and the UL serving link is associated with an indicated UL TCI state.

3. The method of any of claims 1 to 2, wherein the DL serving link is associated with the one or more DL-RSs, and wherein the one or more DL-RSs are used by the UE to evaluate a performance characteristic of the corresponding DL serving link.

4. The method of any of claims 1 to 3, wherein the one or more trigger events comprise separate first one or more trigger events for the DL serving link and second one or more trigger events for the UL serving link.

5. The method of any of claims 1 to 4, wherein: the one or more trigger events comprise a first trigger event associated with the DL serving link and a second trigger event associated with the UL serving link; and the one or more measurements related to the first and second trigger events comprise atleast one of: the same measurement; two different measurements.

6. The method of any of claims 1 to 5, wherein the one or more measurements for a trigger event associated with the UL serving link is based at least in part on one or more of: power management - maximum power reduction, P-MPR, associated with a spatial filter used to receive at least one DL-RS associated with the UL serving link; maximum output power associated with a spatial filter used to receive at least one DL-RS associated with the UL serving link; maximum Effective Isotropic Radiated Power, EIRP, associated with a UE panel used to receive at least one DL-RS associated with the UL serving link; power head room for the spatial filter used to receive the DL-RS associated with the applied UL serving link.

7. The method of any of claims 1 to 6, wherein the UE is configured with separate DL / UL TCI operation.

8. The method of any of claims 1 to 7, wherein a trigger event associated with the DL serving link initiates a separate action for the UE compared to a trigger event associated with the UL serving link.

9. The method of any of claims 1 to 8, wherein the one or more trigger events includes timedomain information.

10. The method of claim 9, wherein the time-domain information comprises at least one of: a number of occurrences an event occurs; an evaluation window comprising a time window of a number of DL-RS occasions associated with a beam measurement; a number of times a Reference Signal Received Power, RSRP of a DL-RS is below a minimum threshold value; a number of times a Reference Signal Received Power, RSRP of a DL-RS is above a maximum threshold value.

11. The method of any of claims 1 to 10, further comprising: signaling to a network node an indication of beam reporting capability.

12. The method of claim 11, wherein the signaling is completed via Radio Resource Control,RRC, messaging.

13. The method of any of claims 1 to 12, further comprising: transmitting the beam report to the network node; receiving from the network node a response to the beam report; applying a spatial filter associated with a beam identified in the beam report; and communicating with the network node on the identified beam.

14. The method of any of claims 1 to 13, wherein the evaluating comprises: performing first one or more Reference Signal Received Power, RSRP, measurements on a first at least one DL-RS; performing second one or more RSRP measurements on a second at least one DL-RS; and comparing the first and second RSRP measurements.

15. The method of any of claims 1 to 14, further comprising, if a beam report trigger event has happened, indicating to the network node that the UE will send a beam report.

16. A method (1600) performed by a network node (3300) for configuring a user equipment, UE (2200), for initiating a beam report, where the UE has been indicated with a downlink, DL, serving link for DL reception and an uplink, UL, serving link for UL transmission, the method comprising: transmitting (1610), to the UE, a UE initiated beam report configuration, wherein the UE initiated beam report configuration contains a configuration of one or more trigger events and a configuration of one or more DL reference signals, DL-RSs.

17. The method of claim 16, wherein at least one of: a first at least one of the one or more trigger events are associated with the DL serving link; or a second at least one of the one or more trigger events are associated with the UL serving link.

18. The method of claim 16 or 17, further comprising receiving, from the UE, an indication of beam reporting capability.

19. The method of any of claims 16 to 18, further comprising receiving, from the UE, an indication that the UE will send a beam report.

20. The method of any of claims 16 to 19, further comprising receiving, from the UE, a beam report.

21. The method of any of claims 16 to 20, further comprising transmitting, to the UE, a response to one or more beam reports.

22. The method of any of claims 16 to 21, further comprising communicating with the UE on a beam identified in one or more beam reports.

23. A user equipment, UE (2200), for initiating a beam report, where the UE has been indicated with a downlink, DL, serving link for DL reception and an uplink, UL, serving link for UL transmission, comprising: processing circuitry (2202); and a memory (2210), the memory containing instructions executable by the processing circuitry whereby the UE is operative to perform the steps of: receiving (1410), from a network node (3300), a UE initiated beam report configuration, wherein the UE initiated beam report configuration contains a configuration of one or more trigger events and a configuration of one or more DL reference signals, DL- RSs; performing (1420) one or more measurements on the one or more DL reference signals; and evaluating (1430), based at least in part on the one or more measurements, if the one or more trigger events has happened associated with the DL serving link or the UL serving link.

24. A user equipment, UE (2200), for initiating a beam report, where the UE has been indicated with a downlink, DL, serving link for DL reception and an uplink, UL, serving link for UL transmission, comprising: processing circuitry (2202); and a memory (2210), the memory containing instructions executable by the processing circuitry whereby the UE is operative to perform any of the steps of any of claims 1 to 15.

25. A network node (3300) for configuring a user equipment, UE (2200), for initiating a beam report, where the UE has been indicated with a downlink, DL, serving link for DL reception and an uplink, UL, serving link for UL transmission, comprising: processing circuitry (3302); and a memory (3304), the memory containing instructions executable by the processing circuitry whereby the network node is operative to perform the steps of: transmitting (1610), to the UE, a UE initiated beam report configuration, wherein the UE initiated beam report configuration contains a configuration of one or more trigger events and a configuration of one or more DL reference signals, DL-RSs.

26. A network node (3300) for configuring a user equipment, UE (2200), for initiating a beam report, where the UE has been indicated with a downlink, DL, serving link for DL reception and an uplink, UL, serving link for UL transmission, comprising: processing circuitry (3302); and a memory (3304), the memory containing instructions executable by the processing circuitry whereby the network node is operative to perform any of the steps of any of claims 16 to 22.

27. A non-transitory computer-readable storage medium (2210, 3304) having stored thereon instructions executable by processing circuitry to perform any of the steps of any of claims 1 to 22.

Images