Beam measurement

Abstract

An apparatus comprising means for determining a real measurement for a downlink beam from a network; determining a current threshold configured by the network; comparing a real metric dependent upon a real measurement for a downlink beam and a predictive metric dependent upon a predicted measurement for the downlink beam; determining when a difference between the real metric and the predictive metric exceeds a threshold; in dependence upon determining that the difference between the real metric and the predictive metric exceeds a threshold, initiating a report to the network.

Description

[0001] BEAM MEASUREMENT

[0002] CROSS-REFERENCE TO RELATED APPLICATION

[0003]

[0001] This application claims priority from, and the benefit of, EP Application No. 25156332.6, filed February 6, 2025, the contents of which are hereby incorporated by reference in their entirety.

[0004] TECHNOLOGICAL FIELD

[0005]

[0002] Examples of the disclosure relate to beam measurement, and in particular preditcing beam measurement.

[0006] BACKGROUND

[0007]

[0003] Modern telecommunication systems and the standards that define them are complex and evolving.

[0008]

[0004] A transmission configuration indicator (TCI) state, in this document, relates to an association between an identifier of the TCI state and a signal used for beam management.

[0009]

[0005] A network can configured TCI states, and can indicate a TCI state to a user equipment (UE). A TCI switching procedure can be used to change the indicated state, from an old TCI state to a target TCI state.

[0010]

[0006] There is a trend in modern telecommunications toward UE initiated reporting,

[0011]

[0007] The inventors have identified a potential problem arising from overlap of UE initiated reporting procedure and TCI switching procedure.

[0012] BRIEF SUMMARY

[0013]

[0008] According to various, but not necessarily all, embodiments there is provided examples as claimed in the appended claims.

[0014]

[0009] While the above examples of the disclosure and optional features are described separately, it is to be understood that their provision in all possible combinations and permutations is contained within the disclosure. It is to be understood that various examples of the disclosure can comprise any or all the features described in respect of other examples of the disclosure, and vice versa. Also, it is to be appreciated that any one or more or all the features, in any combination, may be implemented by / comprised in / performable by an apparatus, a method, and / or instructions as desired, and as appropriate. The description of a function should additionally be considered to also disclose any means suitable for performing that function

[0015] BRIEF DESCRIPTION

[0016]

[0010] Some examples will now be described with reference to the accompanying drawings in which FIGs.

[0017] 1 to 11 show examples of the subject matter described herein.

[0018] [Oil] The figures are not necessarily to scale. Certain features and views of the figures can be shown schematically or exaggerated in scale in the interest of clarity and conciseness. For example, the dimensions of some elements in the figures can be exaggerated relative to other elements to aidexplication. Similar reference numerals are used in the figures to designate similar features. For clarity, all reference numerals are not necessarily displayed in all figures.

[0019] DETAILED DESCRIPTION

[0020]

[0012] FIG. 1 illustrates an example of a network 100 comprising a plurality of network entities including terminal apparatus 110, node apparatus 120 and one or more network apparatus 130. The terminal apparatus 110 and node apparatus 120 communicate 124 with each other. The one or more network apparatus 130 communicate 128 with the node apparatus 120.

[0021]

[0013] In some examples the one or more network apparatus 130 communicate with the terminal apparatus 110. The one or more network apparatus 130 can, in some examples, communicate with each other. The one or more node apparatus 120 can, in some examples, communicate 126 with each other.

[0022]

[0014] The network 100 can be a cellular network comprising a plurality of cells 122 each served by a node apparatus 120. In this example, the interface between the terminal apparatus 110 and a node apparatus 120 defining a cell 122 is a wireless interface 124.

[0023]

[0015] The node apparatus 120 comprises one or more cellular radio transceivers. The terminal apparatus 110 comprises one or more cellular radio transceivers.

[0024]

[0016] In the example illustrated the cellular network 100 is a third generation Partnership Project (3GPP) network in which the terminal apparatus 110 are user equipment (UE) and the node apparatus 120 can be access nodes such as base stations.

[0025]

[0017] A user equipment comprises a mobile equipment. Where reference is made to user equipment that reference includes and encompasses, wherever possible, a reference to mobile equipment.

[0026]

[0018] In some examples, during operation, a user equipment 110 comprises a mobile equipment comprising a smart card for authentication / encryption etc. such as a Subscriber Identity Module (SIM). In some examples, during operation, a user equipment 110 comprises mobile equipment comprising circuitry embedded as part of the user equipment 110 for authentication / encryption such as software SIM.

[0027]

[0019] The node apparatus 120 can be any suitable access node such as a base station or transmission reception point. The node apparatus 120 can be a network element responsible for radio transmission and reception in one or more cells 122, to or from the UE 110. The node apparatus 120 can be a network element in a Radio Access Network (RAN), an Open-Radio Access Network (O-RAN) or any other suitable type of network.

[0028]

[0020] The network apparatus 130 can be part of a core network. The network apparatus 130 can be configured to manage functions relating to connectivity for the UEs 110. For example, the network apparatus 130 can be configured to manage functions such as connectivity, mobility, authentication, authorization, and / or other suitable functions. In some examples the network apparatus 130 can comprise an Access and Mobility management Function (AMF) and / or a User Plane Function (UPF) or any other suitable entities.

[0021] In the example of Fig. 1 the network apparatus 130 is shown as a single entity. In some examples the network apparatus 130 could be distributed across a plurality of entities. For example, the network apparatus 130 could be cloud based or distributed in any other suitable manner. The network apparatus 130 can be a core network node.

[0029]

[0022] The network 100 can be a 4G or 5G network, for example. It can for example be a New Radio (NR) network that uses gNB or eNB as access nodes 120. New Radio is the 3GPP name for 5G technology. In such cases the node apparatus 120 can comprise gNodeBs (gNBs) 120 configured to provide user plane and control plane protocol terminations towards the UE 110 and / or to perform any other suitable functions. The gNBs 120 are interconnected with each other by means of an X2 / Xn interface 126. The gNBs are also connected by means of the N2 interface 128 to the network apparatus 130. The gNBs can be connected to an AMF or any other suitable network apparatus 130. Other types of networks and interfaces could be used in other examples. Other types of network could comprise next generation mobile and communication network, for example, a 6G network.

[0030]

[0023] The term ‘beam’ refers to directional transmission or reception of signals using beamforming techniques. It is sometime referred to as spatial filtering.

[0031]

[0024] FIG 2 illustrates beams 20 used for transmission (Tx) and / or reception (Rx) at a network node. In this example at a transmission reception point (TRP) 2 of a network node 120. In this example, there are two TRPs 2 . These may be TRPs for the same network node or TRPs for different network nodes 120.

[0032]

[0025] FIG 2 also illustrates beams 20 used for reception (Rx) and / or transmission (Tx) at a terminal node 110, which in this example is a user equipment (UE). In some examples a UE has a capability for reception beam forming . Some but not necessarily all UE 110 also have a capability for transmission beam forming

[0026] Beam-forming can for example be achieved by introducing phase, and optionally amplitude adjustments to signals transmitted / received by different antenna elements. This can be achieved in an analogue domain, in a digital domain or in both analogue domain and digital domain, and is sometimes referred to as spatial filtering.

[0033]

[0027] From Rel-15 of 5G NR, beam management has been specified in 3 procedures controlled by the network: Procedure#! (P1), Procedure#2 (P2) and Procedure#3 (P3). These are described in 3GPP TS 38.214 Section 5.1.5 (TCI and QCL framework) and 5.1.6 (CSI-RS reception procedures).

[0034]

[0028] The following beam management procedures are supported within one or multiple TRPs 2 of the serving cell:

[0035]

[0029] P1 is used to enable UE measurement on different TRP Tx beams to support selection of TRP Tx beams / UE Rx beam(s), and it typically includes an intra / inter-TRP Tx beam sweep with e.g. synchronization signal block (SSB) beams.

[0030] P2 is used to enable UE measurement on different TRP Tx beams to possibly change inter / intra-TRP Tx beam(s), e.g. for beam refinement than in P1 by using narrower Channel State Information (CSI) beams compared to SSB beams.

[0036]

[0031] P3 is used to enable UE measurement on the same TRP Tx beam to change UE Rx beam in the case UE uses beamforming (e.g. mmW arrays on UEs for Frequency Range (FR) 2 operation). P3 may use aperiodic Channel State Information-reference signal (CSI-RS).

[0037]

[0032] Rel-15 to Rel-18 has then specified periodic, semi-persistent and aperiodic CSI reporting.

[0038]

[0033] TCI (Transmission Configuration Indicator) is used to indicate a transmission configuration for a given Physical Downlink Control Channel (PDCCH) or Physical Downlink Shared Channel (PDSCH). It helps the User Equipment (UE) determine which beamforming configuration to use for receiving data transmitted by the network.

[0039]

[0034] A TCI state 30 is associated with a beam 20. The TCI state informs a UE 110 about the specific beamforming configuration to use, which in turn determines a beam direction for data transmission and / or for data reception. This helps improve the link budget and overall performance of the communication system.

[0040]

[0035] The network provides the UE 110 with multiple TCI states 30, each corresponding to a specific beamforming configuration. A TCI state 30 is associated with a signal used for controlling beamforming via beam id 34 (beam index) and the TCI state can be identified via TCI id 32 (TCI index).

[0041]

[0036] When the network schedules data transmission to the UE, it includes the TCI id the control signaling. The TCI id 32 points to one of the pre-configured TCI states 30. Based on the TCI id 32 in a downlink indication 42 , the UE 110 can select the indicated TCI state 30_c (the current TCI state) and its associated beamforming configuration for the indicated / current beam 20_c. This ensures that the UE 110 uses the best possible beam direction for receiving (and / or transmitting) data.

[0042]

[0037] The network can dynamically adjust the indicated TCI state 30_c based on real-time conditions such as UE movement, channel conditions, and interference. This helps maintain optimal communication performance.

[0043]

[0038] 3GPP TS 38.331 (RRC Protocol Specification) defines an information element for configuring a TCI state 30. The IE CandidateTCI-State IE defines a TCI state configuration which associates one or more reference-type signals with a corresponding quasi-colocation (QCL) type. The TCI state configuration comprises at least a TCI id 32 ( tci-x-Stateld-r18) and at least a beam id 34 (ssb-lndex, csi-RS-lndex)

[0044]

[0039] QCL (Quasi Co-Location) refers to a concept used in 5G NR (New Radio) to describe the relationship between different reference signals. This relationship helps the User Equipment (UE) to make certain assumptions about the channel properties, which can improve the accuracy of channel estimation and overall communication performance. There are different types of QCL, each specifying different assumptions about the channel properties.

[0040] Rel-17 introduced the “unified” TCI framework, meaning that TCI states providing QCL assumptions for the reception of DL signals and channels can be used for the transmission of UL signals and channels to determine UL TX spatial filter (beamforming configuration).

[0045]

[0041] There is a pool of TCI states configured via RRC and a subset of these configured TCI states is activated via MAC-CE with up to 8 TCI codepoints, each codepoint pointing to either separate or joint DL / UL active TCI states. This subset of the configured TCI states, which are active, can be referred to as a list of active TCI states

[0046]

[0042] The unified TCI framework defines the concept of indicated TCI state. That means that one or multiple (in case of multi-TRP for instance) of the active configured TCI states is / are an indicated TCI state(s) at a time. The indicated TCI state can be joint DL and UL TCI state, or separate DL and separate UL TCI states.

[0047]

[0043] The indicated TCI state is the current, in use TCI state.

[0048]

[0044] Rel-17 introduced the unified TCI framework for s-TRP, with one indicated joint DL and UL at a time, or one indicated DL and one indicate UL TCI state at a time for the UE. Rel-18 then extended the unified TCI framework for m-TRP, with N>1 (e.g. 2) indicated joint TCI states at a time, or N>1 (e.g. 2) indicated DL TCI states and N>1 (e.g. 2) indicated UL TCI states at a time for the UE.

[0049]

[0045] The pool of configured states is provided via 'tci-StatesToAddModList' , defined in PDSCH-Config. The max size of the pool is 128 TCI states.

[0050]

[0046] The Llist of active TCI states are a subset o from tci-StatesToAddModList specified by a (unified) TCI States Activation / Deactivation MAC CE. The max size of this list is 8.

[0051]

[0047] For each PDSCH scheduling, the TCI field in downlink control information (DCI) indicates a specific index of the list of active TCI states as the indicated state.

[0052]

[0048] FIG 4 illustrates an example of a beam / TCI switch procedure 40. signal 42 indicating a target TCI state 30_2, switching 44 the indicated (current, in use) TCI state 30_c from an old TCI state 30_1 to a target TCI state 30_2. Switching the TCI state, switches the current beam 20_c from a beam 20_1 associated with an old TCI state 30_1 to a target TCI state 30_2. .

[0053]

[0049] An example of the signal 42 indicating a target TCI state 30_2 is the Unified TCI States Activation / Deactivation MAC CE which includes an identifier 32 of a target TCI state (see Figure 6.1.3.47-1 of 3GPP TS 38.321)

[0054]

[0050] The identifier 32 of a target TCI state is TCI state ID. This field indicates the TCI state identified by TCI-Stateld as specified in 3GPP TS 38.331

[0055]

[0051] The signal 42 indicating a target TCI state 30_2 can also be called a switch command in the specifications. It commands a switch of the indicated (current, in use) TCI state 30_c from being an old TCI state 30_1 to being a target TCI state 30_2. At least the target TCI state 30_2 is expressly indicated in the signal 42.

[0052] When a signal 42 indicating a target TCI state 30_2 (a TCI switching command) is received by the UE 110, the switch should be performed within a maximum time period. There is a timing (T) 46 after which the TCI switching is required to be completed. The UE will complete the switch 44 at or before the timing (T) 46 after which the TCI switching is required to be completed

[0056]

[0053] The a timing (T) 46 after which the TCI switching is required to be completed. Is defined by the standards (and therefore ‘known’ to UE 110 and the network).

[0057]

[0054] The value depends on several parameters including ‘known’ / ’unknown’ conditions of the target TCI state (see 8.15.2-8.16.2 of TS 38.133)

[0058] The downlink TCI state is known if the following conditions are met:

[0059] During the period from the last transmission of the RS resource used forthe L1-RSRP measurement reporting for the target downlink TCI state to the completion of active downlink TCI state switch, where the RS resource forL1-RSRP measurement is the RS in target downlink TCI state or QCLed to the target downlink TCI state

[0060] Downlink TCI state switch command is received within 1280 ms upon the last transmission of the RS resource for beam reporting or measurement

[0061] The UE has sent at least 1 L1-RSRP report forthe target downlink TCI state before the downlink TCI state switch command

[0062] The target downlink TCI state remains detectable during the downlink TCI state switching period The SSB associated with the downlink TCI state remain detectable during the downlink TCI switching period

[0063] SNR of the downlink TCI state > -3 dB

[0064] The SSB can be associated with either the serving cell PCI ora PCI different from serving cell PCI. Otherwise, the downlink TCI state is unknown.

[0065] The uplink TCI state is known if the following conditions are met:

[0066] During the period from the last transmission of the RS resource used forthe L1-RSRP measurement reporting forthe target DL / UL TCI state to the completion of active DL / UL TCI state switch, where the RS resource for L1-RSRP measurement is the RS in target DL / UL TCI state or QCLed to the target DL / UL TCI state

[0067] DL / UL TCI state switch command is received within 1280 ms upon the last transmission of the RS resource for beam reporting or measurement

[0068] The UE has sent at least 1 L1-RSRP report for the target DL / UL TCI state before the DL / UL TCI state switch command

[0069] The target DL / UL TCI state remains detectable during the DL / UL TCI state switching period The RS configured in target uplink TCI state remains detectable during the uplink TCI state switching periodSNR of the RS configured in target uplink TCI state > -3 dB

[0070] The SSB associated with the uplink TCI state remain detectable during the uplink TCI switching period

[0071] SNR of the uplink TCI state > -3 dB

[0072] The SSB can be associated with either the serving cell PCI ora PCI different from serving cell PCI. Otherwise, the uplink TCI state is unknown.

[0073] FIG 5 illustrates an example of a use equipment-initiated (UEI) reporting procedure 50, for example a UEI beam management (UEIBM) reporting procedure.

[0074]

[0055] The UE 110 is configured with at least one e vent / cond ition 51 , and then the UE 110 initiates reporting if this at least one event / condition 51 occurs or is satisfied. The report 60 can only be transmitted if the UE has configured UL resources for the transmission. The report 60 is sent by the UE 110 only when needed, avoiding unnecessary beam reports.

[0075]

[0056] Rel-19 MIMO work item description (RP-234007) defines different trigger events 51.

[0076]

[0057] Event-2: If the quality of at least one new beam becomes a “threshold value” better than the current beam, a UEI report 60 is triggered. For example, the network may configure the UE with a certain threshold, for example 3 dB, and when the UE measures a new beam to have a L1 -RSRP which is 3 dB better than the L1-RSRP of the current beam, then a UEI report is triggered.

[0077]

[0058] L1-RSRP refers to layer one (physical layer), reference signal received power.

[0078]

[0059] Other agreed events include:

[0079]

[0060] Event-1 , where the quality of the current beam is worse than a certain threshold.

[0080]

[0061] Event-7, where the quality (e.g. , such as L1-RSRP) of at least one new beam, becomes a threshold value better than the RS derived from the activated TCI state with the Q-th best quality, may be used to update the active TCI state list. The new event may be based on when a quality of K new beams becomes a threshold (r) value better than the reference signal (RS) derived from the activated TCI state 30 with the Q-th best quality. Thus, the UE 110 may be configured to evaluate whether the quality of the K-th strongest non-active TCI state / beam becomes a threshold value better than the quality of the Q-th strongest activated TCI state / beam. K and Q may be integers for example, but in alternate examples one or more of the parameters may be relative values.

[0081]

[0062] The strength or quality of a beam may be measured, for example, with RSRP (such as L1 or L3-type for example) or SINR or other metric.

[0082]

[0063] The parameters, such as M, K and the threshold, may be configured in the UE 110 based upon a message or signal from the gNB.

[0083]

[0064] The UE may use the parameters and beam strengths (such as L1-RSRP or L1-SINR for example) to compare a single active beam relative to a single non-active beam to determine if or when a report should be sent to the gNB.

[0065] As used herein, a beam is a configured beam when the beam corresponds to a configured TCI state, a beam is an active beam when the beam corresponds to a TCI state on the list of active TCL states and a beam is a current beam when the beam corresponds to an indicated TCI state (current, in use TCI state).

[0084]

[0066] The UEI UL report procedure 50 comprises: the UE sends a first uplink (report procedure) signal 54_1 which

[0085]

[0067] precedes sending a second uplink (report procedure) signal 54_2 which comprises the UEI report 60. The 1stUL report procedure signal 54_1 is transmitted in a first UL channel, e.g. a 1stphysical uplink control channel (PUCCH) . The 2ndUL report procedure signal 54_2 is transmitted in a second UL channel, at a later time.

[0086]

[0068] Two examples of the UEI UL report procedure 50 are currently agreed:

[0087]

[0069] In Mode A, the UL channel for the UEI report is dynamically scheduled by the gNB 120. The UL indication requests configuration of resources for UL of the UEI report 60.

[0088]

[0070] In Mode B, the UL channel for the UEI report is pre-configured by the gNB 120. The UL indication notifies the use of pre-configured resources for UL of the UEI report 60..

[0089]

[0071] In more detail, for Mode A:

[0090]

[0072] The UE 110 sends in a first UL channel (1st PUCCH) an indication 54_1 to request to the gNB resources in a second UL channel to carry the UEI report 60. The gNB indicates 53 via DCI to the UE 110 a resource in a second UL channel to carry the UEI report 60. The UE sends the UEI report 60 on the second UL channel 54_2.

[0091]

[0073] In more detail, for Mode B:

[0092]

[0074] The UE 110 sends in a first UL channel (1st PUCCH) an indication 54_1 to notify to the gNB 120 that a UEI report 60 will be transmitted in a second UL channel 54_2I; the UE sends the UEI report 60 on the second UL channel 54_2.

[0093]

[0075] Mode A (DCI) is expected to be the baseline, supported by all UEs capable of UEI reporting. Mode B is expected to be optional and may be supported only by some UEs.

[0094]

[0076] In the context of which reference signals (RS) should be monitored / measured for current and new beams by the UE, for Event-2, the UE is supposed to monitor / measure the current beam 20_c and a certain number of new beams ( “new” beams are sometimes referred to as well as “candidate beams” or “candidate new beams”).

[0095]

[0077] The RS for the current beam 20_c is associated to the indicated TCI state 30_c. In some examples, the RS is the RS in the indicated TCI state. In some examples, the RS is the SSB which is QCLed with the actual RS in the indicated TCI state. In some examples, current and new beams are of the same “type”, e.g., either all SSBs or all CSI-RSs. The RS(s) for the new beam(s) are explicitly configured by the network via RRC.

[0078] The UEI report 60 can depend upon the triggering event 51.

[0096]

[0079] In at least some examples, the UEI report for Event-2 with L1-RSRP as quality metric, reports N beams, for example the top N beams, with N>1 configured by the network via RRC, and at least one of those N beams satisfies the triggering event. Then, in addition to those N beams, the network may configure via RRC the UE to also report the current beam (the beam associated with the indicated TCI state).

[0097]

[0080] In terms of structure of the UEI report, the following is currently agreed:

[0098]

[0099]

[0081] As illustrated in FIG. 5, the UEI beam management (BM) report 60, reports 64 N beams, with their beam index (CRI or SSBRI) and their (differential) RSRP. In addition to that, the UE may be configured to report 62 the RSRP of current beam 20_c without its beam index.

[0100]

[0082] It has not yet been finalized how the UEIBM report 60 will be with Event-1 and Event-7, but the current assumption is that Event-2 design will be reused as much as possible, with a few modifications:

[0101]

[0083] e.g.For Event-1 , the current beam measurement is always reported 62;

[0102] For Event-7, instead of reporting the current beam measurement the UE reports the beam associated to the activated TCI state 30_q with the Q-th best quality.

[0103]

[0084] As illustrated at Fig 6, in at least some examples, a method 200 comprises:

[0104]

[0085] determining 207 a real measurement (m) 24 for a downlink beam 28 from a network 120;

[0105]

[0086] determining 207 a current threshold (t) 10 configured by the network 120;

[0106]

[0087] comparing 208 a real metric dependent upon a real measurement (m) 24 for a downlink beam 28 and a predictive metric dependent upon a predicted measurement (p) 22 for the downlink beam 28;

[0107]

[0088] determining 209 when a difference between the real metric and the predictive metric exceeds a threshold (t) 10;

[0108]

[0089] in dependence upon determining that the difference between the real metric and the predictive metric exceeds a threshold (t) 10, initiating 210 a report 26 to the network 120.

[0109]

[0090] The method can be performed by an apparatus 110, for example a user equipment.

[0110]

[0091] The apparatus 110 comprises:

[0111]

[0092] means for determining a real measurement (m) 24 for a downlink beam 28 from a network 120;

[0112]

[0093] determining a current threshold (t) 10 configured by the network 120;

[0113]

[0094] comparing a real metric dependent upon a real measurement (m) 24 for a downlink beam 28 and a predictive metric dependent upon a predicted measurement (p) 22 for the downlink beam 28;

[0114]

[0095] determining when a difference between the real metric and the predictive metric exceeds a threshold (t) 10;

[0115]

[0096] in dependence upon determining that the difference between the real metric and the predictive metric exceeds a threshold (t) 10, initiating a report 26 to the network 120

[0116]

[0097] The comparison is a comparison between reality and prediction as regards the downlink beam 28, and the comparison can be achieved in many different ways.

[0117]

[0098] In at least some examples, the comparison between the real metric and the predictive metric, compares like-for-like metrics.

[0118]

[0099] In at least some examples, the real metric is based upon a real measurement (m) 24 and the predictive metric is an equivalent metric, implicitly or explicitly dependent upon a predicted measurement (p) 22. That is, in some examples, a prediction engine produces the predicted measurement (p) 22 which is then converted to the predicted metric for comparison. In other examples, a prediction engine produces the predicted metric directly without the intermediate stage of producing predicted measurement (p).

[0119]

[0100] In at least some examples, the real metric is the real measurement (m) 24 and the predictive metric is the predicted measurement (p) 22.

[0101] The comparison of like-for-like can require that the metrics compared are contemporaneous. The term contemporaneous does not necessarily imply simultaneity, although that is not excluded, and connotes that the metrics are close enough in time for a comparison to be valid.

[0120]

[0102] In at least some examples, the comparison can be time-sensitive. The time-sensitivity can vary based on dynamic conditions. In at least some examples, the prediction engine produces a measure of expected variation of the prediction over time and this can be used to assess time-sensitivity and the time period over which the metrics being compared are contemporaneous.

[0121]

[0103] In some examples, the comparing of real metric / measurement (m) 24 for the downlink beam 28 and the predicted metric / measurement (p) 22 for the downlink beam 28 is performed for contemporaneous real and predicted metrics / measurements (m) 24.

[0122]

[0104] In some examples, the comparison comprises comparing a metric dependent upon a real measurement (m) 24, at a first time, for a downlink beam 28 and a metric dependent upon a predicted measurement (p) 22, at the first time, for the downlink beam 28.

[0123]

[0105] In some examples, the comparison comprises comparing the real measurement (m) 24, at a first time, for the downlink beam 28 and the predicted measurement (p) 22, at the first time, for the downlink beam 28

[0124]

[0106] When it is determined that the difference between the real metric / measurement and the predictive metric / measurement exceeds a threshold (t) 10, the method initiates sending a report 26 to the network 120.

[0125]

[0107] When it is determined that the difference between the real metric / measurement and the predictive metric / measurement does not exceed the threshold (t) 10, the method does not initiate sending a report 26 to the network 120. The method instead resets, and at a future time, will repeat, as indicated by the return loop 31.

[0126]

[0108] Thus the method 200 comprises: in dependence upon determining that the difference between the real metric and the predictive metric does not exceed the threshold (t) 10, not initiating a report 26 to the network 120, and enabling (via the return loop 31): determining 207 a real measurement (m) 24 for a downlink beam 28 from a network 120; determining 207 a current threshold (t) 10 configured by the network 120; comparing 208 a real metric dependent upon a real measurement (m) 24 for a downlink beam 28 and a predictive metric dependent upon a predicted measurement (p) 22 for the downlink beam 28; determining 209 when a difference between the real metric and the predictive metric exceeds a threshold (t) 10; in dependence upon determining that the difference between the real metric and the predictive metric exceeds a threshold (t) 10, initiating 210 a report 26 to the network 120. in dependence upon determining that the difference between the real metric and the predictive metric does not exceed the threshold (t) 10, not initiating a report 26 to the network 120, and repeating the method via the return loop 31.

[0109] In at least some examples, the real measurement (m) 24 for the downlink beam 28 and / or the predicted measurement (p) 22 for the downlink beam 28 and / or the threshold (t) 12 are updated (or a decision is made whether or not to update them) before performing the comparing 208.

[0127]

[0110] In at least some examples, the determining 207 determines an updated real measurement (m) 24 for the downlink beam 28 and / or an updated predicted measurement (p) 22 for the downlink beam 28 and / or an updated threshold (t) 12.

[0128]

[0111] In at least some examples, a prediction engine at the apparatus 110 determines a predictive measurement for the downlink beam 28 using one or more of historical performance analysis and machine learning based predictions.

[0129]

[0112] In at least some examples, a downlink beam 28 is a reference signal for a downlink beam 20. Examples of beams, and reference signals for beams, have previously been described. An example of a reference signal for a downlink beam is SSB or CSI-RS. An example of a downlink beam is illustrated in FIG 7.

[0130]

[0113] In at lest some examples, the real metric / measurement and the predictive metric / measurement that are compared, are dependent upon radio quality. Examples of radio quality metrics / measurements include but are not limited to any one or more of the following or any combination of the following: RSRP (Reference Signal Received Power); CQI (Channel Quality Indicator) for downlink.

[0131]

[0114] In at lest some examples, the real metric / measurement (and the equivalent predictive metric / measurement) are dependent on RSRP (Reference Signal Received Power) of the reference beam for the downlink beam 28.

[0132]

[0115] A beam metric for a downlink beam 28 can be dependent upon a real measurement

[0133]

[0116] (m) 24 for the downlink beam 28 and, optionally, be dependent upon real measurements (m) 24 for other downlink beams. In some examples, a beam metric for a downlink beam 28 can be dependent upon the top-K real measurements (m) 24 including the real measurement (m) 24 for the downlink beam 28. The top-K real measurements are the top K entries in an ordered list of real measurements for different beams, where the list is ordered by beam quality with the best beam quality being at the top.

[0134]

[0117] In at least some examples, the threshold (t) 10 is dynamically updated.

[0135]

[0118] In at least some examples, the threshold (t) 10 is dynamically updated by the network via downlink signaling. In at least some examples, the threshold (t) 10 is dynamically updated by the network via radio resource control (RRC) message or by medium access control (MAC) control element (CE) or otherwise.

[0136]

[0119] In at least some examples, the threshold (t) 10 is dynamically updated by the apparatus 110.

[0137]

[0120] In some example, dynamic updating of the threshold (t) 10, used for the comparison, is based on one or more of: historical performance data, network conditions (load, interference), user profiles, intended use.

[0121] In at least some examples, a plurality of thresholds (t) 10 are configured by the network via higher layer signaling and a threshold (t) 10 for the comparison is selected by the network via lower layer signaling. For example a plurality of thresholds (t) 10 are configured by the network via a radio resource control message, and a threshold is selected, for use in the comparison evaluation, via lower layer (L1 / L2) signaling, for example, using a medium access control information element.

[0138]

[0122] In at least some examples, a plurality of thresholds (t) 10 are configured by the network via higher layer signaling and a threshold (t) 10 for the comparison is selected by the apparatus 110. For example a plurality of thresholds (t) 10 are configured by the network via a radio resource control message.

[0139]

[0123] In at least some examples, the threshold (t) 10 is one of a plurality of thresholds (t) 10 selected based on an intended use case e.g. network conditions (load, interference), user profiles, required services etc.

[0140]

[0124] In at least some examples, the threshold (t) 10, used for the comparison, is a semi-static configurable threshold (t) 10 . For example, a configurable fixed numerical or percentage-based difference (e.g., “Trigger a report 26 if RSRP difference > 3 dB”).

[0141]

[0125] In at least some examples, the threshold (t) 10, used for the comparison, is a dynamic threshold (t) 10 - where the threshold (t) 10 is adjusted in real time or periodically, for example, based on network 120 conditions (load, interference), user profiles, or historical performance.

[0142]

[0126] I n at least some examples, the threshold (t) 10, used for the comparison, is a UE Autonomously adjusted Threshold (t) 10 .The UE 110 calculates and updates the threshold (t) 10, used for the comparison, based on local observations (e.g., local ML model) without waiting for the network 120.

[0143]

[0127] FIG 7 illustrates another example of the method 200.

[0144]

[0128] The method 200, from the UE 110 perspective comprises the following.

[0145]

[0129] The UE 110 receives 202 a downlink message. In at least some examples, the downlink message configures one or more thresholds 10. In at least some examples, the downlink message additionally, or alternatively comprises a configuration 12. In some examples the configuration 12 is a measurement configuration for configuring measurement (or measurement reporting) of the downlink beam 28. In some examples the configuration 12 is a prediction configuration for configuring prediction for the downlink beam 28.

[0146]

[0130] The UE 110 applies 204 the received threshold(s) 10 and / or the received measurement configuration 12 and / or the received prediction configuration 12.

[0147]

[0131] The UE 110 performs a real measurement (m) 24 for the downlink reference signal 28 for the beam 20.

[0148]

[0132] The UE 110 determines 207, for example obtains from memory, a current threshold (t) 10 (previously configured by the network 120), a real metric dependent upon the real measurement (m) 24 for a downlink beam 28 and a predictive metric for the downlink beam 28;

[0133] The UE 110 compares 208 the real metric and the predictive metric to determine a difference.

[0149]

[0134] The UE 110 determines 209 when a difference between the real metric and the predictive metric exceeds the threshold (t) 10. The UE 110, in dependence upon determining 209 that the difference between the real metric and the predictive metric exceeds the threshold (t) 10, initiates 210 a report 26 to the network 120.

[0150]

[0135] The UE 110 receives 202 a downlink message, and the process can repeat. The triggering of the repetition of the process may be initiated by the network or the UE 110, for example, using a UE initiated, event-based trigger.

[0151]

[0136] When it is determined 209 that the difference between the real metric and the predictive metric does not exceed exceeds the threshold (t) 10, the method does not initiate sending a report 26 to the network 120. The method instead resets, and at a future time, will repeat, as indicated by the return loop 31.

[0152]

[0137] In at least some examples, sending 210 the report 26 comprises sending a UE initiated, eventbased, measurement report 60 to the network 120.

[0153]

[0138] In this example, the threshold (t) 10 used in the comparison 208 is received in a downlink configuration 12 transmitted 220 by the network 120 and received 202 by the UE 110. The configuration 12 comprises a measurement configuration for reporting measurement of downlink beams transmitted 222 by the network 120, that is used by the apparatus 110 to adjust measurement and / or reporting measurement of downlink beams transmitted 222 by the network 120 and / or the configuration 12 comprises a prediction configuration for UE-based prediction that produces at least a predicted measurement (p) 22 for a downlink beam 28, that is used by the apparatus 110 to adjust prediction.

[0154]

[0139] The measurement configuration 12 can relate to real measurement (m) 24 and / or predictive measurement. A predictive configuration is used by the apparatus 110 to adjust prediction after evaluation of applicable functionality.

[0155]

[0140] In this example, the downlink configuration is initially network initiated. However, in other examples, the downlink configuration is transmitted in dependence upon a UE initiated report 26 to the network 120.

[0156]

[0141] In at least some example, the network 120, after receiving 224 the report 26, analyzes 226 the report 26 and determines a change in configuration for the UE 110. This could be a change in indicated TCI state, a change in measurement (report) configuration and / or a change in a predictive configuration. For example, in some examples the report 26 is a UE initiated report 26 to the network 120 and a downlink configuration is transmitted in dependence upon the UE initiated report 60.

[0157]

[0142] In some examples, the report 26 includes predicted measurements (p) 22 (for future times).

[0158]

[0143] FIG 8 illustrates an example of a report 26, In this example, the report 26 comprises the real metric / measurement and the predictive metric / measurement for the downlink beam 28, used in the comparison 209 that initiated the sending of the report 26.

[0144] In some examples, the report 26 comprises multiple real metrics / measurements and multiple predictive metrics / measurements for the downlink beam 28, used in the comparison 209 that initiated the sending of the report 26.

[0159]

[0145] In some examples, the report 26 comprises real metric(s) / measurement(s) and predictive metric(s) / measurement(s) for the downlink beam 28, and also for other downlink beams 20, for example, the TOP-K beams.

[0160]

[0146] In some examples, the report 28, is a UE initiated report 60.

[0161]

[0147] FIG 9 illustrates an example of a UE initiated report 60 that functions as the report 26. The description above for FIG 8 is also relevant for FIG 9. The UE initiated report 60 additionally includes a beam identifier 34 for each beam. The UE initiated report is sent via layer one, physical layer.

[0162]

[0148] In at least some examples, the report 26 comprises additional information 38.

[0163]

[0149] In some examples, an output of the prediction engine for a prediction for the associated beam is included in information 38. For example, one output parameter of the prediction engine, at the apparatus 110, could be a measure of uncertainty for the prediction, and this parameter could be included in information 38. In at least some examples an output parameter of the prediction engine, the apparatus 110, is a measure of expected variation of the prediction overtime, and this parameter could be included in information 38.

[0164]

[0150] In some examples, there may be an additional condition that needs to be satisfied before sending the report 26, that is additional to the difference between the real metric / measurement and the predicted metric / measurement for the downlink beam exceeding the threshold 10. In at least some examples, the report 26 indicates the additional condition (or conditions). In at least some examples, the report 26 provides information on the additional condition (or conditions).

[0165]

[0151] For example, the additional condition, may restrict reports to situations where specific prediction performance conditions are met, such as low prediction accuracy.

[0166]

[0152] For example, the additional condition, may restrict reports to situations where a likelihood that a difference reported by the report 26 will trigger a reconfiguration of the UE 110 by the network.

[0167]

[0153] A metric can be defined by a comparisons between the Top 1 / K predicted beam per report and the Top 1 / K measured beam from a resource set for monitoring. In particular, a metric can be determined based on the comparisons of the inference result for each of X (X>1 ) CSI reports of a given CS I -ReportConfig and the associated measurement(s). For example, a new report quantity for beam accuracy, namely, beam accuracy indicator (BAI) can be introduced in CSI report. The value of BAI k (0<k<X) is the number of CSI reports with comparison results as “true” from the X CSI reports. The prediction accuracy associated with the BAI is T and the size of CSI field associated with the BAI is Hog-i 1.

[0168]

[0154] The BAI represents the number of CSI reports 26 with comparison results as “true” from the ( X ) CSI reports 26 One or more of the following can be used to define "true":

[0155] Top-1 : The predicted beam matches the Top-1 beam of the resource set.

[0169]

[0156] Top-K / 1 : The predicted beam is one of the Top-K beams.

[0170]

[0157] 1 dB Margin: The predicted beam's measured L1-RSRP is within 1 dB of the Top-1 beam's measured L1-RSRP.

[0171]

[0158] In a report 26 to the network 120 which includes actual measurements and N predicted measurements (p) 22 for a beam, a BAI associated with that beam can be included. The BAI refers to the past predictions and measurements, so in the context of the report 26 from the UE to the network 120 it would be indicating how good the beam actually is (i.e. if in the nearest past it has been in the Top-1, Top-K / 1).

[0172]

[0159] In some examples the threshold additional conditions is based on a beam accuracy indicator (BAI). For example, the beam accuracy indicator (BAI) is above (or below) a BAI threshold.

[0173]

[0160] In at least some examples, the additional information 38 is the beam accuracy indicator (BAI) or is an indication that the beam accuracy indicator (BAI) is above(re below) a BAI threshold.

[0174]

[0161] A beam accuracy indicator is a measure of accurate prediction of the downlink beam 28 as best, or one of best beams, in recent past.

[0175]

[0162] In some examples, if both the threshold (t) 10 between the predicted metric / measurement and the real metric / measurement is exceeded and the BAI is above a second threshold then the report 26 is triggered and sent to the network.

[0176]

[0163] The second threshold is used to only trigger reports 26 for beams or sets of beams which actually are going to be used in the connection between the UE and NW.

[0177]

[0164] A standardization document may define: the real metric dependency upon the real measurement (m) 24 for a downlink beam 28, the predictive metric dependency upon a predicted measurement (p) 22 for a downlink beam 28, the determination of difference between the real metric and the predictive metric; and the threshold (t) 10.

[0178]

[0165] A standardization document may define: the requirements for changing a current threshold (t) 10 used for the comparison are standardized by the telecommunications standard

[0179]

[0166] A standardization document may define: the requirements for transmitting the report 26 to the network 120.

[0180]

[0167] A standardization document may define: the conditions for triggering report 26 based on anomalies between measured and predicted metrics / measurement.

[0181]

[0168] In at least some examples, some or all of the operations described as carried out by the apparatus (UE) 110 can be performed autonomously. That is the decision of when to perform the operation is taken by the apparatus (UE) 110.

[0182]

[0169] In at least some examples, the apparatus (UE) 100 can autonomously determine a real measurement (m) 24 for a downlink beam 28.

[0170] In at least some examples, the apparatus (UE) 100 can autonomously determine a predictive measurement for the downlink beam 28

[0183]

[0171] In at least some examples, the apparatus (UE) 100 can autonomously determine a current threshold (t) 10.

[0184]

[0172] In at least some examples, the apparatus (UE) 100 can autonomously perform comparing a real metric (based on at least the real measurement (m) 24 for the downlink beam 28) and a predictive metric (based on at least the predictive measurement for the downlink beam 28).

[0185]

[0173] In at least some examples, the apparatus (UE) 100 can autonomously perform determining when a difference between the real metric and the predictive metric exceeds the current threshold (t) 10.

[0186]

[0174] In at least some examples, the apparatus (UE) 100 can autonomously perform, in dependence upon determining that the difference between the real metric and the predictive metric exceeds a threshold (t) 10, initiating a report 26 to the network 120.

[0187]

[0175] It should be appreciated that in at least some examples, the report 26 can only be sent by the apparatus (UE) 110 when uplink (UL) resources are available. These may have been preconfigured by the network 120 or the UE 110 may need to request configuration of UL resources.

[0188]

[0176] The real metric / measurement and the predictive metric / measurement have a first specification for network-side performance monitoring in which the UE measures and reports 26 to the network 120 for performance calculations at the network 120 and have a second specification for UE-side performance monitoring in which the UE measures and performs performance calculations.

[0189]

[0177] The above described methods can be used across all operational modes, including Type 1 Option 2 and Option 1 scenarios.

[0190]

[0178] Option 1 : network-side performance monitoring in which the UE measures and reports 26 to the network 120 for performance calculations at the network 120;

[0191]

[0179] Option 2: UE-side performance monitoring in which the UE measures and performs performance calculations.

[0192]

[0193]

[0194]

[0180] Advantages of the proposed solution include:

[0195]

[0181] The adaptable threshold (t) 10 (and autonomous reporting) provide improved responsiveness. In some examples, real-time detection and reporting of performance anomalies, is achieved and the network 120 can respond more swiftly to degradation events.

[0196]

[0182] The adaptable threshold (t) 10 provides for enhanced optimization opportunities. The adaptable / dynamic thresholding allows for more accurate detection of performance issues, leading to better optimization of network resources.

[0197]

[0183] The use of standardized event definitions provides consistency and clarity. The standardized event definitions and CSI configurations provide clarity and consistency, facilitating easier interpretation of performance metrics.

[0198]

[0184] The coverage across operational modes provides for broader applicability. The framework's comprehensive coverage ensures that it can be applied across various scenarios and operational modes.

[0199]

[0185] The need for effective event-triggered reporting mechanisms is important in the context of Beam Management (BM) and associated reporting procedures in particular for performance monitoring. Without clear definitions and configurations for events that trigger reports, the NW may fail to capture critical performance data. This includes discrepancies between predicted and measured values, which can hinder timely network responses.

[0200]

[0186] The current state of performance monitoring mechanisms for BM lacks a robust event-triggered reporting framework, which is critical for timely network responses to performance degradation. Specifically, there is an absence of clear definitions and configurations for events that should trigger reports, particularly in scenarios where the prediction accuracy of performance metrics, such as RSRP and Top-K beam measurements, falls below established thresholds. This deficiency can lead to missed opportunities for optimization, as the User Equipment (UE) may fail to accurately detect significant discrepancies between measured and predicted values, such as L1-RSRP differences.

[0201]

[0187] Moreover, the existing methodologies for event-triggered monitoring are inconsistent, particularly regarding the configuration of the Channel State Information (CSI) field associated with the BeamAllocation Indicator (BAI) and its variability with the parameter N. This inconsistency complicates the interpretation of performance metrics and undermines the effectiveness of monitoring.

[0202]

[0188] To address these issues, it is desirable to establish a comprehensive framework that defines specific events for triggering performance reports, particularly in Type 1 Option 2 monitoring scenarios. This framework should enable the UE to autonomously detect and report critical performance metrics based on predefined thresholds, ensuring that the network can respond promptly to performance anomalies.

[0203] Additionally, clarity is needed on how the UE can trigger reports in Option 1, where it does not calculate performance metrics, to ensure that all operational modes are adequately supported. Without these enhancements, the overall efficiency and effectiveness of performance monitoring within the 3GPP ecosystem will remain compromised.

[0204]

[0189] To address the deficiencies in the current 3GPP performance monitoring mechanisms, there is proposed a novel event-triggered reporting framework that integrates a (dynamic) threshold-based reporting system with a standardized event definition protocol. This framework will enable User Equipment (UE) to autonomously detect and report performance anomalies based on real-time analysis of performance metrics, such as RSRP and Top-K beam measurements, while ensuring consistency across all operational modes, including Type 1 Option 2 and Option 1 scenarios.

[0205]

[0190] Example features of the framework include:

[0206] 1. Dynamic Threshold Configuration: Instead of static thresholds, the framework allows for dynamic adjustment of thresholds based on historical performance data and network conditions. This adaptability ensures that the UE can respond to varying network environments and user demands.

[0207] 2. Standardized Event Definition Protocol: A comprehensive set of standardized events is defined, including specific conditions for triggering reports based on discrepancies between measured and predicted values, i.e. if the difference between measured and predicted values goes above a threshold.

[0208] 3. Autonomous Reporting Mechanism: The UE will be allowed to determine autonomously when to trigger reports based on the defined events and thresholds, reducing reliance on network-side calculations and improving response times.

[0209] 4. Comprehensive Coverage Across Operational Modes: The proposed framework ensures that all operational modes, including those where the UE does not calculate performance metrics, are adequately supported, thus enhancing the overall robustness of the monitoring system.

[0210]

[0191] Advantages of the proposed solution include:

[0211] • Improved Responsiveness: By enabling real-time detection and reporting of performance anomalies, the network can respond more swiftly to degradation events.• Enhanced Optimization Opportunities: The dynamic thresholding allows for more accurate detection of performance issues, leading to better optimization of network resources.

[0212] • Consistency and Clarity: The standardized event definitions and CSI configurations provide clarity and consistency, facilitating easier interpretation of performance metrics.

[0213] • Broader Applicability: The framework's comprehensive coverage ensures that it can be applied across various scenarios and operational modes, addressing the limitations of existing proposals.

[0214]

[0192] An example:

[0215] • UE-UE:

[0216] a. The UE begins by collecting relevant performance metrics (e.g., RSRP, beam measurements).

[0217] b. UE compares measured values to predictions and checks if a predefined discrepancy threshold is exceeded.

[0218] • If Path:

[0219] UE-NW:

[0220] a. If (and only if) the discrepancy exceeds the threshold, the UE sends a Measurement Report to the network node.

[0221] NW-NW:

[0222] b. The network node analyzes the report to identify the nature of the anomaly and decide on next steps.

[0223] NW-UE:

[0224] c. The network node sends any necessary updates (e.g., new thresholds or configuration parameters) back to the UE.

[0225] UE-UE:

[0226] d. The UE applies these configuration updates, improving subsequent monitoring.

[0227] • Else Path:

[0228] a. If the threshold was not exceeded, the UE simply continues monitoring without triggering any report.

[0229] • NW-UE:

[0230] a. Feedback loop for continuous improvement of the UE-triggered reporting.

[0231]

[0193] Additional aspects:

[0232]

[0194] Resource set definition: There is a set of resource configurations specifically for performance monitoring, including a clear specification of subsets of Set A. Each subset will be characterized by its intended use case (e.g., urban, rural, high mobility) and will include parameters such as the maximumnumber of beams (M) and the dB gap (X) to the largest measured L1-RSRP. This will ensure that the resource sets are tailored to the specific conditions of the network environment, reducing ambiguity in their application.

[0233] On performance metrics: The following can be considered as potential metrics to monitor for the beam quality:

[0234] ■ Radio quality metrics:

[0235] o RSRP (Reference Signal Received Power) - where the average received power of specific reference signals (e.g., CSI-RS or SSB);

[0236] o CQI (Channel Quality Indicator) - UE-reported index representing channel quality for the downlink, however this would only be applicable for the downlink;

[0237] ■ Beam specific metrics:

[0238] o Top-K Beam Measurements - The UE periodically reports the best K beams ranked by RSRP, SNR, etc;

[0239] o PMI (Precoding Matrix Indicator) - UE feedback that indicates preferred precoding vectors for downlink transmissions.

[0240] o Beam Blockage Detection - which measures sudden drops in beam quality due to obstacles (e.g., user’s hand, building corners).

[0241]

[0195] Prediction of the quality (e.g. RSRP related metric) beam: The prediction of the beam quality can be achieved via different methods such as:

[0242] • Historical performance analysis:

[0243] o Time-Series Analysis - Use historical beam metrics (e.g., RSRP, SINR) to establish trends and seasonalities and then apply techniques such as ARIMA (AutoRegressive Integrated Moving Average), Holt-Winters exponential smoothing, etc.

[0244] o Contextual Aggregation - Group and analyze performance data based on location, time of day, or other contextual factors (e.g., user speed). By clustering historical data, you can extract typical beam-quality patterns in specific regions or under certain mobility patterns.

[0245] • Machine Learning-Based Predictions:

[0246] o Supervised Learning

[0247] ■ Regression Models (e.g., Random Forest, XGBoost): Predict future RSRP / SINR given current measurements, user location, and mobility vectors;

[0248] ■ Neural Networks (e.g., Multi-Layer Perceptrons): Learn non-linear relationships between UE context (location, speed, direction, neighbor cells) and beam quality.

[0249] o Time-Series Deep Learning■ RNN / LSTM Models or Temporal Convolutional Networks (TCN) for sequential data. The model learns patterns in how beam quality evolves over time under user mobility and varying interference.

[0250] o Reinforcement Learning (RL)

[0251] ■ An RL agent (UE or network controller) learns to pick the best beam or beam pattern by trial and error, receiving feedback (reward) from real-world performance metrics.

[0252] o Hybrid Approaches:

[0253] ■ Rule-Based + ML - Combine a rule-based system for coarse beam selection (based on location, neighbors, or geometry) with a machine-learning model that refines choices.

[0254] ■ Kalman Filters with ML Components - Use a Kalman filter or Extended / Unscented Kalman filter to track and predict beam metrics. Enhance the prediction model or the observation model using machine-learning to handle non-linearities or context updates.

[0255]

[0196] Discrepancy threshold: The determination and configuration of the discrepancy threshold 10 can be as follows:

[0256] ■ On determination:

[0257] o Static threshold - Where a fixed numerical or percentage-based difference (e.g., “Trigger a report if RSRP difference > 3 dB”).

[0258] o Dynamic threshold - where the is adjusted in real time or periodically, based on network conditions (load, interference), user profiles, or historical performance. o Machine learning based:

[0259] ■ Supervised Approach: Train a model (e.g., regression or classification) to identify the level of discrepancy that correlates with actual performance problems (e.g., packet loss, throughput drops).

[0260] ■ Anomaly Detection: Use unsupervised learning (e.g., isolation forests, autoencoders) to detect out-of-band discrepancies.

[0261] ■ On configuration:

[0262] o Network-Controlled Threshold (Control Plane Signaling):

[0263] ■ The network (e.g., gNB) communicates threshold settings to the UE via RRC signaling or higher-layer management messages.

[0264]

[0197] Beam management can comprise DL Tx beam prediction for both UE-sided model and NW-sided model, encompassing:o Spatial-domain DL Tx beam prediction for Set A of beams based on measurement results of Set B of beams (“BM-Case1”)

[0265] o Temporal DL Tx beam prediction for Set A of beams based on the historic measurement results of Set B of beams (“BM-Case2”)

[0266]

[0198] The UE 110 can autonomously report when specific performance conditions are met, such as low prediction accuracy.

[0267]

[0199] FIG. 10 illustrates an example of a controller 400 suitable for use in an apparatus 110, 120.

[0268] Implementation of a controller 400 may be as controller circuitry. The controller 400 may be implemented in hardware alone, have certain aspects in software including firmware alone or can be a combination of hardware and software (including firmware).

[0269]

[0200] As illustrated in FIG. 10 the controller 400 may be implemented using instructions that enable hardware functionality, for example, by using executable instructions 406 in a general-purpose or specialpurpose processor 402 that may be stored on a machine readable storage medium (disk, memory etc.) to be executed by such a processor 402.

[0270]

[0201] The processor 402 is configured to read from and write to the memory 404. The processor 402 may also comprise an output interface via which data and / or commands are output by the processor 402 and an input interface via which data and / or commands are input to the processor 402.

[0271]

[0202] The memory 404 stores instructions, program, or code 406 that controls the operation of the apparatus 110, 120 when loaded into the processor 402. The instructions, program, or code 406, provide the logic and routines that enables the apparatus 110, 120 to perform the methods illustrated in the accompanying FIGs. The processor 402 by reading the memory 404 is configured to load and execute the instructions, program, or code 406.

[0272]

[0203] The apparatus 110, 120 comprises: at least one processor 402; and at least one memory 404 storing instructions that, when executed by the at least one processor 402, cause the apparatus at least to:

[0273]

[0204] determining a current threshold (t) 10 configured by the network 120; comparing a real metric dependent upon a real measurement (m) 24 for a downlink beam 28 and a predictive metric dependent upon a predicted measurement (p) 22 for the downlink beam 28; determining when a difference between the real metric and the predictive metric exceeds a threshold (t) 10; in dependence upon determining that the difference between the real metric and the predictive metric exceeds a threshold (t) 10, initiating a report 26 to the network 120

[0274]

[0205] As illustrated in FIG. 11, the instructions, program, or code 406 may arrive at the apparatus 110, 120 via any suitable delivery mechanism 408. The delivery mechanism 408 may be, for example, a machine readable medium, a computer-readable medium, a non-transitory computer-readable storage medium, a computer program product, a memory device, a record medium such as a solid-state memory, an article of manufacture that comprises or tangibly embodies the instructions 406. The deliverymechanism may be a signal configured to reliably transfer the instructions 406. The apparatus 110, 120 may propagate or transmit the instructions406 as a data signal.

[0275]

[0206] The term “non-transitory” as used herein, is a limitation of the medium itself (i.e., tangible, not a signal ) as opposed to a limitation on data storage persistency (e.g., RAM vs. ROM).

[0276]

[0207] The instructions 406 cause an apparatus to perform at least the following: determining a current threshold (t) 10 configured by the network 120; comparing a real metric dependent upon a real measurement (m) 24 for a downlink beam 28 and a predictive metric dependent upon a predicted measurement (p) 22 for the downlink beam 28; determining when a difference between the real metric and the predictive metric exceeds a threshold (t) 10; in dependence upon determining that the difference between the real metric and the predictive metric exceeds a threshold (t) 10, initiating a report 26 to the network 120.

[0277]

[0208] The instructions 406 may be comprised in a computer program, a non-transitory computer readable medium, a computer program product, a machine readable medium. In some but not necessarily all examples, the instructions 406 may be distributed over more than one computer program.

[0278]

[0209] Although the memory 404 is illustrated as a single component / circuitry it may be implemented as one or more separate components / circuitry some or all of which may be integrated / removable and / or may provide permanent / semi-permanent / dynamic / cached storage.

[0279]

[0210] Although the processor 402 is illustrated as a single component / circuitry it may be implemented as one or more separate components / circuitry some or all of which may be integrated / removable. The processor 402 may be a single core or multi-core processor.

[0280]

[0211] References to ‘computer-readable storage medium’, ‘computer program product’, ‘tangibly embodied computer program’ etc. or a ‘controller’, ‘computer’, ‘processor’ etc. should be understood to encompass not only computers having different architectures such as single / multi- processor architectures and sequential (Von Neumann) / parallel architectures but also specialized circuits such as field-programmable gate arrays (FPGA), application specific circuits (ASIC), signal processing devices and other processing circuitry including quantum processing circuitry. References to computer program, instructions, code etc. should be understood to encompass software for a programmable processor or firmware such as, for example, the programmable content of a hardware device whether instructions for a processor, or configuration settings for a fixed-function device, gate array or programmable logic device etc.

[0281]

[0212] As used in this application, the term ‘circuitry’ may refer to one or more or all the following: hardware-only circuitry implementations (such as implementations in analog, digital and / or quantum circuitry) or

[0282] combinations of hardware circuit(s) and software, such as (as applicable):

[0283]

[0213] a combination of analog, digital and / or quantum hardware circuit(s) with software / firmware and

[0214] any or all portions of hardware processor(s) (including digital and / or quantum processor(s)) with software, and memory(ies) that work together to cause an apparatus, such as a mobile device, computing device or server, to perform various functions and

[0284]

[0215] (c) any or all portions of hardware circuit(s), such as a microprocessor(s) and / or quantum processors , that requires software (for example, firmware) for operation, but the software may not be present when it is not needed for operation.

[0285]

[0216] This definition of circuitry applies to all uses of this term in this application, including in any claims. As a further example, as used in this application, the term circuitry also covers an implementation of merely a hardware circuit or processor (or multiple processors) or portion of a hardware circuit or processor and its (or their) accompanying software and / or firmware. The term circuitry also covers, for example and if applicable to the claim element, a baseband integrated circuit or processor integrated circuit for a mobile device or a similar integrated circuit in a server, a cellular network device, or other computing or network device.

[0286]

[0217] The blocks illustrated in the accompanying Figs may represent steps in a method and / or sections of code in the instructions 406. The illustration of a particular order to the blocks does not necessarily imply that there is a required or preferred order for the blocks and the order and arrangement of the block may be varied. Furthermore, it may be possible for some blocks to be omitted.

[0287]

[0218] As used here ‘module’ refers to a unit or apparatus that excludes certain parts / components that would be added by an end manufacturer or a user. The apparatus 110, 120 can, for example be a module. A controller 400 of the apparatus 110, 120 can, for example be a module.

[0288]

[0219] Where a structural feature has been described, it may be replaced by means for performing one or more of the functions of the structural feature whether that function or those functions are explicitly or implicitly described.

[0289]

[0220] The above-described examples find application as enabling components of: automotive systems; telecommunication systems; electronic systems including consumer electronic products; distributed computing systems; media systems for generating or rendering media content including audio, visual and audio visual content and mixed, mediated, virtual and / or augmented reality; personal systems including personal health systems or personal fitness systems; navigation systems; user interfaces also known as human machine interfaces; networks including cellular, non-cellular, and optical networks; ad-hoc networks; the internet; the internet of things; virtualized networks; and related software and services.

[0290]

[0221] The apparatus can be provided in an electronic device, for example, a mobile terminal, according to an example of the present disclosure. It should be understood, however, that a mobile terminal is merely illustrative of an electronic device that would benefit from examples of implementations of the present disclosure and, therefore, should not be taken to limit the scope of the present disclosure to the same. While in certain implementation examples, the apparatus can be provided in a mobile terminal, other typesof electronic devices, such as, but not limited to: mobile communication devices, hand portable electronic devices, wearable computing devices, portable digital assistants (PDAs), pagers, mobile computers, desktop computers, televisions, gaming devices, laptop computers, cameras, video recorders, GPS devices and other types of electronic systems, can readily employ examples of the present disclosure. Furthermore, devices can readily employ examples of the present disclosure regardless of their intent to provide mobility.

[0291]

[0222] The term ‘comprise’ is used in this document with an inclusive not an exclusive meaning. That is any reference to X comprising Y indicates that X may comprise only one Y or may comprise more than one Y. If it is intended to use ‘comprise’ with an exclusive meaning then it will be made clear in the context by referring to ‘comprising only one...’ or by using ‘consisting.’

[0292]

[0223] In this description, the wording ‘connect’, ‘couple’ and ‘communication’ and their derivatives mean operationally connected / coupled / in communication. It should be appreciated that any number or combination of intervening components can exist (including no intervening components), i.e., to provide direct or indirect connection / coupling / communication. Any such intervening components can include hardware and / or software components.

[0293]

[0224] As used herein, the term "determine / determining" (and grammatical variants thereof) can include, not least: calculating, computing, processing, deriving, measuring, investigating, identifying, looking up (for example, looking up in a table, a database, or another data structure), ascertaining and the like. Also, "determining" can include receiving (for example, receiving information), accessing (for example, accessing data in a memory), obtaining and the like. Also, " determine / determining" can include resolving, selecting, choosing, establishing, and the like.

[0294]

[0225] In this description, reference has been made to various examples. The description of features or functions in relation to an example indicates that those features or functions are present in that example. The use of the term ‘example’ or ‘for example’ or ‘can’ or ‘may’ in the text denotes, whether explicitly stated or not, that such features or functions are present in at least the described example, whether described as an example or not, and that they can be, but are not necessarily, present in some of or all other examples. Thus ‘example’, ‘for example’, ‘can’, or ‘may’ refers to a particular instance in a class of examples. A property of the instance can be a property of only that instance or a property of the class or a property of a sub-class of the class that includes some but not all the instances in the class. It is therefore implicitly disclosed that a feature described with reference to one example but not with reference to another example, can where possible be used in that other example as part of a working combination but does not necessarily have to be used in that other example.

[0295]

[0226] As used herein, “at least one of the following: ” and “at least one of ” and similar wording, where the list of two or more elements are joined by “and” or “or” mean at least any one of the elements, or at least any two or more of the elements, or at least all the elements.

[0227] Although examples have been described in the preceding paragraphs with reference to various examples, it should be appreciated that modifications to the examples given can be made without departing from the scope of the claims.

[0296]

[0228] Features described in the preceding description may be used in combinations other than the combinations explicitly described above.

[0297]

[0229] Although functions have been described with reference to certain features, those functions may be performable by other features whether described or not.

[0298]

[0230] The description of a feature, such as an apparatus or a component of an apparatus, configured to perform a function, or for performing a function, should additionally be considered to also disclose a method of performing that function. For example, description of an apparatus configured to perform one or more actions, or for performing one or more actions, should additionally be considered to disclose a method of performing those one or more actions with or without the apparatus.

[0299]

[0231] Although features have been described with reference to certain examples, those features may also be present in other examples whether described or not.

[0300]

[0232] The term ‘a’, ‘an’ or ‘the’ is used in this document with an inclusive not an exclusive meaning. That is any reference to X comprising a / an / the Y indicates that X may comprise only one Y or may comprise more than one Y unless the context clearly indicates the contrary. If it is intended to use ‘a’, ‘an’ or ‘the’ with an exclusive meaning then it will be made clear in the context. In some circumstances the use of ‘at least one’ or ‘one or more’ may be used to emphasis an inclusive meaning but the absence of these terms should not be taken to infer any exclusive meaning.

[0301]

[0233] The presence of a feature (or combination of features) in a claim is a reference to that feature or (combination of features) itself and to features that achieve substantially the same technical effect (equivalent features). The equivalent features include, for example, features that are variants and achieve substantially the same result in substantially the same way. The equivalent features include, for example, features that perform substantially the same function, in substantially the same way to achieve substantially the same result.

[0302]

[0234] In this description, reference has been made to various examples using adjectives or adjectival phrases to describe characteristics of the examples. Such a description of a characteristic in relation to an example indicates that the characteristic is present in some examples exactly as described and is present in other examples substantially as described.

[0303]

[0235] As used herein, the terms “the at least one” and “the one or more” mean “any one of the at least one” and “any one of the one or mor” respectively.

[0304]

[0236] The above description describes some examples of the present disclosure however those of ordinary skill in the art will be aware of possible alternative structures and method features which offer equivalent functionality to the specific examples of such structures and features described herein aboveand which for the sake of brevity and clarity have been omitted from the above description. Nonetheless, the above description should be read as implicitly including reference to such alternative structures and method features which provide equivalent functionality unless such alternative structures or method features are explicitly excluded in the above description of the examples of the present disclosure.

[0305]

[0237] Whilst endeavoring in the foregoing specification to draw attention to those features believed to be of importance the Applicant may seek protection via the claims in respect of any patentable feature or combination of features hereinbefore referred to and / or shown in the drawings whether or not emphasis has been placed thereon.

Claims

CLAIMS1. An apparatus comprising at least one processor; andat least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to perform:determining a real measurement for a downlink beam from a network;determining a current threshold configured by the network;comparing a real metric dependent upon a real measurement for a downlink beam and a predictive metric dependent upon a predicted measurement for the downlink beam;determining when a difference between the real metric and the predictive metric exceeds a threshold; in dependence upon determining that the difference between the real metric and the predictive metric exceeds a threshold, initiating a report to the network.

2. The apparatus as claimed in claim 1, wherein the apparatus further caused to perform:in dependence upon determining that the difference between the real metric and the predictive metric does not exceed the threshold, not initiating a report to the network, and enabling:determining a real measurement for a downlink beam from a network;determining a current threshold;comparing a real metric dependent upon a real measurement for a downlink beam and a predictive metric dependent upon a predicted measurement for the downlink beamdetermining when a difference between the real metric and the predictive metric exceeds a threshold in dependence upon determining that the difference between the real metric and the predictive metric exceeds a threshold, initiating a report to the network.

3. The apparatus as claimed in claim 1 or 2, wherein the threshold is dynamically updated.

4. The apparatus as claimed in any preceding claim, wherein the threshold is one of a plurality of thresholds selected based on an intended use case.

5. The apparatus as claimed in any preceding claim, wherein the plurality of thresholds are configured by the network.

6. The apparatus as claimed in any preceding claim, wherein the threshold is received in a configuration transmitted by the network ,wherein the configuration comprises a measurement configuration for reporting measurement of downlink beams transmitted by the network, that is used by the apparatus to adjust measurement and / or reporting measurement of downlink beams transmitted by the network,and / orwherein the configuration comprises a prediction configuration for UE-based prediction that produces at least a predicted measurement for a downlink beam, that is used by the apparatus to adjust prediction.

7. The apparatus as claimed in any preceding claim, wherein the real metric and the predictive metric are dependent upon radio quality.

8. The apparatus as claimed in any preceding claim, wherein the real metric and the predictive metric are or are dependent upon RSRP (Reference Signal Received Power) of reference beams.

9. The apparatus as claimed in any preceding claim, wherein initiating the report to the network requires satisfaction of at lest one additional condition in addition to the difference between the real metric and the predicted metric for the downlink beam exceeding the threshold.

10. The apparatus as claimed in claim 9, wherein the additional condition is dependent upon expected variation in accuracy of prediction, over time, for the downlink beam or a beam accuracy indicator (BAI) for the downlink beam.

11. The apparatus as claimed in any preceding claim, wherein the report comprises one or more of: a real measurement or a real metric for the downlink beam;a predicted measurement or a predicted metric for the downlink beam;real measurement or real measurements for each downlink beam in a set of one or more downlink beams; predictive measurement or predictive measurements for each downlink beam in a set of one or more downlink beams;a measure of uncertainty for a prediction,a measure of expected variation of a prediction over timean indication of the additional condition, or information relating to the additional condition;a beam accuracy indicator (BAI) or is an indication that a beam accuracy indicator (BAI) is above a BAI threshold.

12. The apparatus as claimed in any preceding claim, wherein the report is a UE initiated report.

13. A method comprising:determining a real measurement for a downlink beam from a network;determining a current threshold configured by the network;comparing a real metric dependent upon a real measurement for a downlink beam and a predictive metric dependent upon a predicted measurement for the downlink beam;determining when a difference between the real metric and the predictive metric exceeds a threshold; in dependence upon determining that the difference between the real metric and the predictive metric exceeds a threshold, initiating a report to the network.

14. A computer program comprising instructions that, when executed by an apparatus, cause the apparatus to perform at least the following:determining a real measurement for a downlink beam from a network;determining a current threshold configured by the network;comparing a real metric dependent upon a real measurement for a downlink beam and a predictive metric dependent upon a predicted measurement for the downlink beam;determining when a difference between the real metric and the predictive metric exceeds a threshold; in dependence upon determining that the difference between the real metric and the predictive metric exceeds a threshold, initiating a report to the network.

Images