P110739WO01 PCT APPLICATION 1 of 62 Extended CSI Framework for Beam Prediction TECHNICAL FIELD [0001] The present disclosure generally relates to communication networks, and more specifically to extended channel state information (CSI) framework for indicating set A and B for user equipment (UE) side beam prediction. BACKGROUND [0002] One of the key features of new radio (NR), compared to previous generation of wireless networks, is the ability to operate in higher frequencies (e.g., above 10 Giga hertz (GHz)). The available large transmission bandwidths in these frequency ranges may potentially provide large data rates. However, as carrier frequency increases, both pathloss and penetration loss increase. To maintain the coverage at the same level, highly directional beams are used to focus the radio transmitter energy in a particular direction on the receiver. However, large radio antenna arrays – at both receiver and transmitter sides – are needed to create such highly direction beams. [0003] To reduce hardware costs, large antenna arrays for high frequencies use time-domain analog beamforming. The core idea of analog beamforming is to share a single radio frequency chain between many (or potentially all) of the antenna elements. A limitation of analog beamforming is that it is only possible to transmit radio energy using one beam (in one direction) at a given time. [0004] The above limitation requires the network and user equipment (UE) to perform beam management procedures to establish and maintain suitable transmitter (Tx)/receiver (Rx) beam- pairs. For example, beam management procedures may be used by a transmitter to sweep a geographic area by transmitting reference signals on different candidate beams, during non- overlapping time intervals, using a predetermined pattern. Thus, by measuring the quality of the reference signals at the receiver side, the best transmit and receive beams may be identified. [0005] Beam management procedures in NR are defined by a set of layer 1/layer 2 (L1/L2) procedures that establish and maintain suitable beam pairs for both transmitting and receiving data. A beam management procedure may include the following sub-procedures: beam determination, beam measurements, beam reporting, and beam sweeping. [0006] For downlink transmission from the network to the UE, P1/P2/P3 beam management procedures may be performed according to the NR technical report to overcome the challenges of establishing and maintaining the beam pairs when, for example, a UE moves or a blockage in the
P110739WO01 PCT APPLICATION 2 of 62 environment requires changing the beams. Although these scenarios are not directly mentioned in specifications, there are relevant procedures defined that enable the realization of these scenarios. Examples of such realization are depicted in the corresponding figure of each scenario. [0007] Figure 1 illustrates synchronization signal block (SSB) beam selection as part of an initial access procedure according to the P1 scenario. The P1 procedure is used to enable UE measurement on different transmission/reception point (TRP) Tx beams to support the selection of TRP Tx beams/UE Rx beam(s). During initial access, for example, the gNB transmits synchronization signal/physical broadcast channel (SS/PBCH) block (SSB) beams in different directions to cover the entire cell. The UE measures signal quality (e.g., reference signal receive power (RSRP)) on corresponding SSB signals to detect and select an appropriate SSB beam, as illustrated in Figure 1. Random access is then transmitted on the random access channel (RACH) resources indicated by the selected SSB. The corresponding beam will be used by both the UE and the network to communicate until connected mode beam management is active. The network infers which SSB beam was chosen by the UE without any explicit signaling. [0008] For beamforming at a TRP, beamforming typically includes an intra/inter-TRP Tx beam sweep from a set of different beams. For beamforming at UE, beamforming typically includes a UE Rx beam sweep from a set of different beams. [0009] Figure 2 illustrates channel state information reference signal (CSI-RS) Tx beam selection in downlink according to the P2 scenario. The P2 procedure is used to enable UE measurement on different TRP Tx beams to possibly change inter/intra-TRP Tx beam(s). The network may use the SSB beam as an indication of which (narrow) CSI-RS beams to try; that is, the selected SSB beam may be used to define a candidate set of narrow CSI-RS beams for beam management. [0010] Once CSI-RS is transmitted, the UE measures the RSRP and reports the result to the network (e.g., four highest RSRP values and corresponding CSI-RS index). If the network receives a CSI-RSRP report from the UE where a new CSI-RS beam is better than the old beam used to transmit physical downlink control channel (PDCCH)/physical downlink shared channel (PDSCH), the network updates the serving beam for the UE accordingly, and possibly also modifies the candidate set of CSI-RS beams. The network may also instruct the UE to perform measurements on SSBs. If the network receives a report from the UE where a new SSB beam is better than the previous best SSB beam, a corresponding update of the candidate set of CSI-RS beams for the UE may be motivated. [0011] The P2 procedure is performed on a possibly smaller set of beams for beam refinement than in P1. Note that P2 may be a special case of P1. For example, in connected mode, a gNB
P110739WO01 PCT APPLICATION 3 of 62 configures the UE with different CSI-RSs and transmits each CSI-RS on the corresponding beam. The UE then measures the quality of each CSI-RS beam on its current RX beam and sends feedback about the quality of the measured beams. Thereafter, based on this feedback, the gNB will decide and possibly indicate to the UE which beam will be used in future transmissions. This is shown in Figure 2. [0012] Figure 3 illustrates UE Rx beam selection for corresponding CSI-RS Tx beam in downlink according to P3 scenario. P3 is used to enable UE measurement on the same TRP Tx beam to change UE Rx beam when the UE uses beamforming. Once in connected mode, the UE is configured with a set of reference signals. Based on measurements, the UE determines which Rx beam is suitable to receive each reference signal in the set. The network then indicates which reference signals are associated with the beam that will be used to transmit PDCCH/PDSCH, and the UE uses the information to adjust its Rx beam when receiving PDCCH/PDSCH. [0013] In connected mode, P3 may be used by the UE to find the best Rx beam for the corresponding Tx beam. In this case, the gNB keeps one CSI-RS Tx beam at a time, and the UE performs the sweeping and measurements on its own Rx beams for that specific Tx beam. The UE then finds the best corresponding Rx beam based on the measurements and will use it in the future for reception when the gNB indicates the use of that Tx beam. [0014] For beam management, a UE may be configured to report RSRP or/and signal-to- interference-plus-noise ratio (SINR) for each one of up to four beams, either on CSI-RS or SSB. UE measurement reports may be sent either over physical uplink control channel (PUCCH) or physical uplink shared channel (PUSCH) to the network node, e.g., gNB. [0015] A CSI-RS is transmitted over each transmit (Tx) antenna port at the network node and for different antenna ports. The CSI-RS is multiplexed in time, frequency, and code domain such that the channel between each Tx antenna port at the network node and each receive antenna port at a UE may be measured by the UE. A time-frequency resource used for transmitting CSI-RS is referred to as a CSI-RS resource. [0016] In NR, the CSI-RS for beam management is defined as a 1 or 2-port CSI-RS resource in a CSI-RS resource set where the field repetition is present. The following three types of CSI- RS transmissions are supported. [0017] For periodic CSI-RS, CSI-RS is transmitted periodically in certain slots. The CSI-RS transmission is semi-statically configured using radio resource control (RRC) signaling with parameters such as CSI-RS resource, periodicity, and slot offset. [0018] Semi-persistent CSI-RS is similar to periodic CSI-RS. Resources for semi-persistent CSI-RS transmissions are semi-statically configured using RRC signaling with parameters such as
P110739WO01 PCT APPLICATION 4 of 62 periodicity and slot offset. However, unlike periodic CSI-RS, dynamic signaling is used to activate and deactivate the CSI-RS transmission. [0019] Aperiodic CSI-RS is a one-shot CSI-RS transmission that may happen in any slot. Here, one-shot means that CSI-RS transmission only happens once per trigger. The CSI-RS resources (i.e., the resource element (RE) locations which consist of subcarrier locations and orthogonal frequency division multiplexing (OFDM) symbol locations) for aperiodic CSI-RS are semi-statically configured. The transmission of aperiodic CSI-RS is triggered by dynamic signaling through PDCCH using the CSI request field in uplink downlink control information (UL DCI), in the same DCI where the uplink resources for the measurement report are scheduled. Multiple aperiodic CSI-RS resources may be included in a CSI-RS resource set, and the triggering of aperiodic CSI-RS is on a resource set basis. [0020] In NR, an SSB consists of a pair of synchronization signals (SSs), a physical broadcast channel (PBCH), and a demodulation reference signal (DMRS) for PBCH. An SSB is mapped to four consecutive OFDM symbols in the time domain and 240 contiguous subcarriers (20 resource blocks (RBs)) in the frequency domain. [0021] NR supports beamforming and beam-sweeping for SSB transmission by enabling a cell to transmit multiple SSBs in different narrow-beams multiplexed in time. The transmission of the SSBs is confined to a half-frame time interval (5 ms). It is also possible to configure a cell to transmit multiple SSBs in a single wide-beam with multiple repetitions. The design of beamforming parameters for each of the SSBs within a half frame is up to network implementation. The SSBs within a half frame are broadcasted periodically from each cell. The periodicity of the half frames with SS/PBCH blocks is referred to as SSB periodicity, which is indicated by system information block 1 (SIB1). [0022] The maximum number of SSBs within a half frame, denoted by L, depends on the frequency band, and the time locations for the L candidate SSBs within a half frame depends on the subcarrier spacing (SCS) of the SSBs. The L candidate SSBs within a half frame are indexed in ascending order in time from 0 to L-1. By successfully detecting PBCH and its associated DMRS, a UE knows the SSB index. A cell does not necessarily transmit SS/PBCH blocks in all L candidate locations in a half frame, and the resource of the unused candidate positions may be used for the transmission of data or control signaling instead. It is up to network implementation to decide which candidate time locations to select for SSB transmission within a half frame, and which beam to use for each SSB transmission.
P110739WO01 PCT APPLICATION 5 of 62 [0023] For measurement resource configurations in NR, a UE may be configured with N≥1 CSI reporting settings (CSI-ReportConfig) and M≥1 resource settings (CSI-ResourceConfig), where each of N and M is an integer. [0024] Each CSI reporting setting is linked to one or more resource settings for channel and/or interference measurement. The CSI framework is modular in the sense that several CSI reporting settings may be associated with the same Resource Setting. [0025] The measurement resource configurations for beam management are provided to the UE by RRC information element (IE) (CSI-ResourceConfigs). One CSI-ResourceConfig contains several NZP-CSI-RS-ResourceSets and/or CSI-SSB-ResourceSets. [0026] A UE may be configured to measure CSI-RSs using the RRC IE non-zero power channel state information reference signal (NZP-CSI-RS)-ResourceSet. A NZP CSI-RS resource set contains the configurations of Ks ≥1 CSI-RS resources. Each CSI-RS resource configuration resource includes at least the following: mapping to REs, the number of antenna ports, and time- domain behavior. [0027] Up to 64 CSI-RS resources may be grouped together in a NZP-CSI-RS-ResourceSet. A UE may be configured to measure SSBs using the RRC IE CSI-SSB-ResourceSet. Resource sets comprising SSB resources are defined in a similar manner to the CSI-RS resources defined above. [0028] For aperiodic CSI-RS and/or aperiodic CSI reporting, the network node configures the UE with ^^^^ CSI triggering states. Each triggering state contains the aperiodic CSI report setting to be triggered along with the associated aperiodic CSI-RS resource sets. [0029] Periodic and semi-persistent resource settings may only comprise a single resource set (i.e., S=1). Aperiodic resource settings may have many resource sets (S>=1), because one out of the S resource sets defined in the resource setting is indicated by the aperiodic triggering state that triggers a CSI report. [0030] Three types of CSI reporting are supported in NR, as follows. [0031] One type is periodic CSI reporting on PUCCH. CSI is reported periodically by a UE. Parameters such as periodicity and slot offset are configured semi-statically by higher layer RRC signaling from the network node to the UE. [0032] Another type is semi-persistent CSI reporting on PUSCH or PUCCH. This is similar to periodic CSI reporting where semi-persistent CSI reporting has a periodicity and slot offset that may be semi-statically configured. However, a dynamic trigger from a network node to UE may be used to enable the UE to begin semi-persistent CSI reporting. A dynamic trigger from the network node to UE is needed to request the UE to stop the semi-persistent CSI reporting.
P110739WO01 PCT APPLICATION 6 of 62 [0033] A third type is aperiodic CSI reporting on PUSCH. This type of CSI reporting involves a single-shot (i.e., one time) CSI report by a UE that is dynamically triggered by the network node using DCI. Some of the parameters related to the configuration of the aperiodic CSI report are semi-statically configured by RRC, but the triggering is dynamic. [0034] In each CSI reporting setting, the content and time-domain behavior of the report is defined, along with the linkage to the associated Resource Settings. [0035] The CSI-ReportConfig IE comprises the following configurations: ^ reportConfigType: Defines the time-domain behavior (periodic CSI reporting, semi- persistent CSI reporting, or aperiodic CSI reporting) along with the periodicity and slot offset of the report for periodic CSI reporting. ^ reportQuantity: Defines the reported CSI parameters -- the CSI content; for example, the pre-coding matrix indicator (PMI), channel quality indicator (CQI), rank indicator (RI), layer indicator (L1), CSI-RS resource index (CRI) and L1-RSRP. Only certain combinations are possible; for example, channel-related information - rank indicator - precoding matrix indicator - channel quality indicator (‘cri-RI-PMI-CQI’) is one possible value and ‘cri-RSRP’ is another) and each value of reportQuantity could be said to correspond to a certain CSI mode. ^ codebookConfig: Defines the codebook used for PMI reporting, along with possible codebook subset restriction (CBSR). NR supported the following two types of PMI codebooks: Type I CSI and Type II CSI. Additionally, the Type I and Type II codebooks each have two different variants: regular and port selection. ^ reportFrequencyConfiguration: Define the frequency granularity of PMI and CQI (wideband or subband), if reported, along with the CSI reporting band, which is a subset of subbands of the bandwidth part (BWP) to which the CSI corresponds. ^ Measurement restriction in time domain (ON/OFF) for channel and interference respectively. [0036] For beam management, a UE may be configured to report L1-RSRP for up to four different CSI-RS/SSB resource indicators. The reported RSRP value corresponding to the first more optimal channel-related information (CRI)/synchronization signal block rank indicator (SSBRI) requires 7 bits, using absolute values, while the others require 4 bits using encoding relative to the first. In NR release 16, the report of L1-SINR for beam management has already been supported. [0037] The report setting configures how the UE shall generate a certain CSI report. It is linked to one or more CSI resource configurations that configure how the UE should make
P110739WO01 PCT APPLICATION 7 of 62 measurements for the report. The gNB may configure several different types of reports simultaneously. Thus, the UE may be configured with one or more CSI report settings by the higher-layer parameter CSI-ReportConfig carried by dedicated RRC signaling. The reportConfig includes several resourceConfigs, which also may point to several resources according to Figure 4. [0038] Figure 4 illustrates a correlation between CSI reporting configurations and CSI resources. [0039] Third Generation Partnership Project (3GPP) is studying artificial intelligence/machine learning (AI/ML) based spatial beam prediction. The core idea is to predict the “best” or more optimal beam (or beams) from a Set A of beams using measurement results from another Set B of beams. [0040] Set A and Set B of beams have not been defined yet; however, the following two examples illustrate some scenarios that will likely be studied in Release 18. [0041] In a first example, Set B is a subset of a Set A. For example, Set A is a set of 8 SSB/CSI- RS beams shown in Figure 5 (both light and dark circles). The UE measures Set B (the 4 beams indicated by dark circles). The AI/ML model should predict the best beam (or beams) in Set A using only measurements from Set B. [0042] Figure 5 illustrates an example where Set B is a subset of Set A. Figure 5 illustrates a grid-of-beam type radiation pattern: Each row (resp. column) depicts a certain zenith (resp. azimuth) angle from the antenna array. Set A has 8 beams and Set B has 4 beams (indicated by dark circles). [0043] In a second example, Set A and Set B correspond to two different sets of beams. For example, Set A is a set of 30 narrow CSI-RS beams, and Set B is a set of 8 wide SSB beams. The UE measures beams in Set B and the AI/ML model should predict the best beam(s) from Set A. [0044] Figure 6 illustrates an example where Set A is a set of narrow beams and Set B is a set of wide beams. [0045] The spatial beam prediction may be performed in the gNB or the UE.3GPP is studying AI/ML model training both at the network and UE side. Which side that performs the training is expected to impact how data collection is performed, and another agreement is to study the aspect of data collection for beam management. In addition, 3GPP is studying the aspect of model monitoring and the standard impact on AI/ML model inference (e.g., reporting of predicted values). [0046] There currently exist certain challenges. For example, in the current systems, when introducing UE-sided beam-based predictions, it needs to be introduced in an efficient manner. That is, it should preferably be based on the existing CSI framework to limit the specification
P110739WO01 PCT APPLICATION 8 of 62 efforts. However, there are currently no methods for a network to indicate which beams are part of set A and set B, respectively, in the current CSI reporting framework. [0047] One possible approach/solution is to assume that set A/set B selection is completely up to the UE. However, this approach suffers from several challenges. First, set B requires certain network configurations (i.e. RS transmissions) for the UE to be able to perform those measurements for inference purposes. If each UE requests different network configuration, this would require excessive amount of additional reference signal transmissions to accommodate for different UE needs. From the network perspective, this diminishes the benefits of running an AI model on the UE side. Second, the network has a better understanding of which beams are not likely to be picked within the deployment and predictions for those beams may be sufficient, while actual measurements are preferred and wanted for certain beams. [0048] Moreover, a potential issue with a data-driven approach for learning the gNB Tx/Rx beam correlations/properties is that different sites/cells may have different antenna/beam configurations. Moreover, even within the same cell, there may be scenarios where antenna/beam configurations are semi-dynamically adjusted to better fit the current traffic load situations. To enable a trained AI/ML model at the UE-side to generalize to many different scenarios and/or antenna/beam configurations, 3GPP needs to identify a solution that may handle this ambiguity. That is, the additional condition is that different cells might have different antenna/beam configurations and that it might change over time in the same cell. There is also no method to address the consistency over time in the current CSI framework. SUMMARY [0049] As described above, certain challenges currently exist with indicating Set A and B for user equipment (UE) side beam prediction. Certain aspects of the disclosure and their embodiments may provide solutions to these or other challenges. For example, particular embodiments support and implement an extension to the existing channel state information (CSI) framework enabling the network to indicate which beams a UE may use as Set B (the input to an artificial intelligence/machine learning (AI/ML) model at the UE) and Set A (the output of the AI/ML model at the UE), so that the UE may train and perform inference steps using the extended CSI framework. [0050] More specifically, in particular embodiments Set A/B indications may be included in any of the information elements according to Figure 7. [0051] Figure 7 illustrates an example of Set A/B indications as part of CSI reporting and/or resource configurations, according to particular embodiments.
P110739WO01 PCT APPLICATION 9 of 62 [0052] Moreover, in particular embodiment, to handle the consistency issue from training to inference, an identifier (ID) is provided to the UE that identifies the used beam configuration/pattern. For example, when the UE receives the same beam configuration/pattern ID over multiple time instances, the UE may assume that the CSI resources are using the same beams/precoders. This may be achieved by using a “consistency” identifier for the CSI resources (in any of the information elements in Figure 7), that may be valid over a multiple Radio Resource Control (RRC) sessions in contrast to, e.g., a legacy nzp-CSI-RS-ResourceId or csi- ReportConfigID. Examples of implementing the consistency identifier are shown in Table 1 below. Table 1: Methods to solve consistency from training to inference Existing IE New element Comment (38.331) NZP-CSI-RS- consistency-nzp-CSI-RS- An ID that indicates whether the UE Resource ResourceId may assume that the resource is using the same spatial TX-filter (beam/precoder) across time NZP-CSI-RS- consistency-nzp-CSI-RS- An ID that indicates whether the UE ResourceSet ResourceSetId may assume that the set of resources is using the same spatial TX-filters across time CSI-ReportConfig consistency-csi- An ID that indicates whether the UE ReportConfigId may assume that reported resources are using the same spatial TX-filters across time csi- consistency-csi- An ID that indicates whether the UE ResourceConfig ResourceConfigId may assume that configured resources are using the same spatial TX-filters across time [0053] A first group of embodiments extend the current CSI framework to enable the network to indicate one or more Set A and Set B beams. A second group of embodiments include a consistency identifier for enabling the UE to train a model in one time instance, and use the trained model in a second time instance (e.g., in a separate RRC session).
P110739WO01 PCT APPLICATION 10 of 62 [0054] According to some embodiments, a method is performed by a wireless device (e.g., UE) for beam prediction in a wireless network. The method comprises receiving a first channel state information (CSI) configuration from a network node. The first CSI configuration comprises an indication of a beam Set A, an indication of a beam Set B, and a first consistency identifier associated with beam Set A and beam Set B. The method further comprises determining the wireless device supports a beam prediction model that uses one or more beams of beam Set B as input and one or more beams of beam Set A as output. The determination is based on the first consistency identifier matching a second consistency identifier associated with beam Set A and beam Set B used for training the beam prediction model. The method further comprises: measuring one or more beams of beam Set B; predicting measurements for one or more beams of beam Set A based on the measured one or more beams of beam Set B and the beam prediction model; and reporting the predicted measurements for the one or beams of beam Set A to the network node. [0055] In particular embodiments, the method further comprises receiving a second CSI configuration. The second CSI configuration comprises an indication of beam Set A, an indication of beam Set B, and the second consistency identifier associated with beam Set A and second beam Set B. The method further comprises measuring one or more beams of beam Set B; measuring one or more beams of beam Set A; and training the beam prediction model based on the measurements of the one or more beams of beam Set B and the measurements of the one or more beams of beam Set A. [0056] In particular embodiments, beam Set B is a subset of beam Set A, or beam Set B is not a subset of beam Set A (e.g., beams Set A is a set of narrow beams and beam Set B is a set of wide beams). [0057] In particular embodiments, the first consistency identifier and the second consistency identifier each comprise a pair of identifiers, one identifier of the pair associated with beam Set A and another identifier of the pair associated with beam Set B. [0058] In particular embodiments, at least one of the indication of beam Set A, the indication of beam Set B, and the first consistency identifier is included in one of: CSI-reportingConfig; CSI- resourceConfig; CSI-resourceSetList; CSI-ResourceList; or CSI-Resource. [0059] In particular embodiments, the second consistency identifier is received in a first RRC session and the first consistency identifier is received in a second RRC session, different from the first RRC session. [0060] In particular embodiments, the second consistency identifier is received in a first cell and the first consistency identifier is received in a second cell, different from the first cell.
P110739WO01 PCT APPLICATION 11 of 62 [0061] In particular embodiments, the first consistency identifier matching the second consistency identifier indicates that: CSI resources associated with the first consistency identifier are using the same beams or precoders as CSI resources associated with the second consistency identifier; or CSI resources associated with the first consistency identifier are using the same spatial transmit filters as CSI resources associated with the second consistency identifier. [0062] In particular embodiments, each of the first consistency identifier and the second consistency identifier are based on one or more of: a cell identifier; a public land mobile network identifier; a vendor identifier; an antenna tilt; an antenna direction; an antenna position; a beam pattern; and a timestamp. [0063] According to some embodiments, a wireless device comprises processing circuitry operable to perform any of the wireless device methods described above. [0064] Also disclosed is a computer program product comprising a non-transitory computer readable medium storing computer readable program code, the computer readable program code operable, when executed by processing circuitry to perform any of the methods performed by the wireless device described above. [0065] According to some embodiments, a method is performed by a network node (e.g., gNB) for beam prediction in a wireless network. The method comprises transmitting a first channel state information, CSI, configuration to a wireless device. The first CSI configuration comprises an indication of a beam Set A, an indication of a beam Set B, and a first consistency identifier associated with beam Set A and beam Set B. The first consistency identifier matches a second consistency identifier associated with beam Set A and beam Set B used for training a beam prediction model used by the wireless device. The method further comprises transmitting one or more beams of beam Set B and receiving predicted measurements for one or more beams of beam Set A from the wireless device. The predicted measurements are based on measurements of one or more beams of beam Set B and the beam prediction model. [0066] In particular embodiments, the method further comprises transmitting a second CSI configuration to the wireless device. The second CSI configuration comprises an indication of beam Set A, an indication of beam Set B, and a second consistency identifier associated with beam Set A and beam Set B. The method further comprises transmitting one or more beams of beam Set B and transmitting one or more beams of beam Set A. [0067] In particular embodiments, the second consistency identifier is transmitted in a first RRC session and the first consistency identifier is transmitted in a second RRC session, different from the first RRC session.
P110739WO01 PCT APPLICATION 12 of 62 [0068] In particular embodiments, the second consistency identifier is transmitted in a first cell and the first consistency identifier is transmitted in a second cell, different from the first cell. [0069] According to some embodiments, a network node comprises processing circuitry operable to perform any of the network node methods described above. [0070] Another computer program product comprises a non-transitory computer readable medium storing computer readable program code, the computer readable program code operable, when executed by processing circuitry to perform any of the methods performed by the network node described above. [0071] Certain embodiments may provide one or more of the following technical advantages. For example, particular embodiments extend the current CSI framework with the indication of one or more Set A/B without extensively increasing the signaling burden. [0072] As another example, particular embodiments provide a consistency identifier enabling the UE to understand whether a Set A/B received during training is the same Set A/B received during inference. For example, if the consistency-csi-ResourceConfigId is the same for two different time-instances, the UE may assume that the beams transmitted in the NZP-CSI-RS- Resources have the same properties (and the UE may use its AI/ML model). This leads to less risk of a UE using an outdated or wrong AI/ML model, which may lead to reduced performance in the beam management operation. It further reduces the amount of resources for model monitoring needed, because without the consistency the network/UE would need to spend resources (time- frequency and computational resources) in estimating whether the model is working properly. BRIEF DESCRIPTION OF THE DRAWINGS [0073] The present disclosure may be best understood by way of example with reference to the following description and accompanying drawings that are used to illustrate embodiments of the present disclosure. In the drawings: Figure 1 illustrates synchronization signal block (SSB) beam selection as part of an initial access procedure according to the P1 scenario; Figure 2 illustrates channel state information reference signal (CSI-RS) Tx beam selection in downlink according to the P2 scenario; Figure 3 illustrates user equipment (UE) Rx beam selection for corresponding CSI-RS Tx beam in downlink according to P3 scenario; Figure 4 illustrates a correlation between CSI reporting configurations and CSI resources; Figure 5 illustrates an example where Set B is a subset of Set A;
P110739WO01 PCT APPLICATION 13 of 62 Figure 6 illustrates an example where Set A is a set of narrow beams and Set B is a set of wide beams; Figure 7 illustrates an example of Set A/B indications as part of CSI reporting and/or resource configurations, according to particular embodiments; Figure 8 is a flowchart illustrating an example of a beam prediction model, according to particular embodiments; Figure 9 shows an example of a communication system, according to certain embodiments; Figure 10 shows a UE, according to certain embodiments; Figure 11 shows a network node, according to certain embodiments; Figure 12 is a block diagram illustrating a virtualization environment in which functions implemented by some embodiments may be virtualized; Figure 13 is a flowchart illustrating an example method in a wireless device, according to certain embodiments; and Figure 14 is a flowchart illustrating an example method in a network node, according to certain embodiments. DETAILED DESCRIPTION [0074] As described above, certain challenges currently exist with indicating Set A and B for user equipment (UE) side beam prediction. Certain aspects of the disclosure and their embodiments may provide solutions to these or other challenges. For example, particular embodiments support and implement an extension to the existing channel state information (CSI) framework enabling the network to indicate which beams a UE may use as Set B (the input to an artificial intelligence/machine learning (AI/ML) model at the UE) and Set A (the output of the AI/ML model at the UE), so that the UE may train and perform inference steps using the extended CSI framework. In particular embodiment, to handle the consistency issue from training to inference, an identifier (ID) is provided to the UE that identifies the used beam configuration/pattern. [0075] Particular embodiments are 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. [0076] Particular embodiments include methods on how Set A/B may be indicated as part of the current CSI framework. In particular embodiments, the network may, for example, when configuring channel state information reference signal (CSI-RS) resources indicate that the UE may use a certain configuration for Set B or Set A beams.
P110739WO01 PCT APPLICATION 14 of 62 [0077] In one example, the indication of whether the CSI-RS is used for transmitting a beam in Set B beam or Set A beam is indicated as part of the current RS resource configuration. For example, the indication may be indicated as a part of the non-zero power channel state information reference signal (NZP-CSI-RS)-Resource information element (IE) as specified in 3GPP V18.0.0. In the below example, when isSetBbeam-r19 is set to ‘True’, the CSI-RS with the corresponding resource Id (e.g., nzp-CSI-RS-ResourceId) is used for transmitting a beam in Set B. Similarly, when isSetAbeam-r19 is set to ‘True’, the CSI-RS with the corresponding resource Id (e.g., nzp- CSI-RS-ResourceId) is used for transmitting a beam in Set A. [0078] An example is illustrated with respect to 3GPP TS 38.331 V18.0.0 as follows: NZP-CSI-RS-Resource information element -- ASN1START -- TAG-NZP-CSI-RS-RESOURCE-START NZP-CSI-RS-Resource ::= SEQUENCE { nzp-CSI-RS-ResourceId NZP-CSI-RS-ResourceId, ... [[ isSetBbeam-r19 Boolean(True,False) OPTIONAL, -- Need S isSetAbeam-r19 Boolean(True,False) OPTIONAL, -- Need S ]] ... resourceMapping CSI-RS-ResourceMapping, …… [0079] In particular embodiments, the indication of whether a NZP CSI-RS is used for transmitting a beam in Set B, Set A, or both is given as follows. In the below example, when the parameter beamSet-r19 is configured with ‘isSetB’, the CSI-RS with the corresponding resource Id (e.g., nzp-CSI-RS-ResourceId) is used for transmitting a beam in Set B. Similarly, when the parameter beamSet-r19 is configured with ‘isSetA’, the CSI-RS with the corresponding resource Id (e.g., nzp-CSI-RS-ResourceId) is used for transmitting a beam in Set A. [0080] In a variant of this embodiment, the parameter beamSet-r19 may have a third value ‘isSetAandSetB’. In this case, the CSI-RS with the corresponding resource Id (e.g., nzp-CSI-RS- ResourceId) may be used for transmitting both a beam in Set B and a beam in Set A.
P110739WO01 PCT APPLICATION 15 of 62 NZP-CSI-RS-Resource information element -- ASN1START -- TAG-NZP-CSI-RS-RESOURCE-START NZP-CSI-RS-Resource ::= SEQUENCE { nzp-CSI-RS-ResourceId NZP-CSI-RS-ResourceId, ... [[ beamSet-r19 Enumerated{isSetB, isSetA} OPTIONAL, -- Need S ]] ... resourceMapping CSI-RS-ResourceMapping, …… [0081] In particular embodiments, the indication of Set A/Set B may be part of the IE NZP- CSI-RS-ResourceSet where NZP-CSI-RS-ResourceSet is a set of Non-Zero-Power (NZP) CSI-RS resources (their IDs) and set-specific parameters. This enables the network to indicate a set of resources that all are part of the Set B or Set A. In the below example, when isSetBbeam-r19 is set to ‘True’, the CSI-RS resources in the NZP CSI-RS resource set with the corresponding resource set Id (e.g., nzp-CSI-RS-ResourceSetId) are used for transmitting beams in Set B. Similarly, when isSetAbeam-r19 is set to ‘True’, the CSI-RS resources in the NZP CSI-RS resource set with the corresponding resource set Id (e.g., nzp-CSI-RS-ResourceSetId) are used for transmitting beams in Set A. NZP-CSI-RS-ResourceSet information element -- ASN1START -- TAG-NZP-CSI-RS-RESOURCESET-START NZP-CSI-RS-ResourceSet ::= SEQUENCE { nzp-CSI-ResourceSetId NZP-CSI-RS- ResourceSetId, nzp-CSI-RS-Resources SEQUENCE (SIZE (1..maxNrofNZP-CSI-RS-ResourcesPerSet)) OF NZP-CSI-RS- ResourceId, repetition ENUMERATED { on, off }
P110739WO01 PCT APPLICATION 16 of 62 ... [[ isSetBbeams-r19 Boolean(True,False) OPTIONAL, -- Need S isSetAbeams-r19 Boolean(True,False) OPTIONAL, -- Need S ]] ... …. [0082] In particular embodiments, when the parameter beamSet-r19 is configured with ‘isSetB’, the CSI-RS resources in the NZP CSI-RS resource set with the corresponding resource set Id (e.g., nzp-CSI-RS-ResourceSetId) are used for transmitting beams in Set B. Similarly, when the parameter beamSet-r19 is configured with ‘isSetA’, the CSI-RS resources in the NZP CSI-RS resource set with the corresponding resource set Id (e.g., nzp-CSI-RS-ResourceSetId) are used for transmitting beams in Set A. [0083] In particular embodiments, the parameter beamSet-r19 may have a third value ‘isSetAandSetB’. In this case, the CSI-RS resources in the NZP CSI-RS resource set with the corresponding resource set Id (e.g., nzp-CSI-RS-ResourceSetId) may be used for transmitting both beams in Set B and beams in Set A. NZP-CSI-RS-ResourceSet information element -- ASN1START -- TAG-NZP-CSI-RS-RESOURCESET-START NZP-CSI-RS-ResourceSet ::= SEQUENCE { nzp-CSI-ResourceSetId NZP-CSI-RS- ResourceSetId, nzp-CSI-RS-Resources SEQUENCE (SIZE (1..maxNrofNZP-CSI-RS-ResourcesPerSet)) OF NZP-CSI-RS- ResourceId, repetition ENUMERATED { on, off } ... [[ beamSet-r19 Enumerated{isSetB, isSetA} OPTIONAL, -- Need S
P110739WO01 PCT APPLICATION 17 of 62 ]] ... …. [0084] In particular embodiments, the indication of Set A/Set B may be part of the IE CSI- ResourceConfig. The IE CSI-ResourceConfig defines a group of one or more NZP-CSI-RS- ResourceSet, CSI-IM-ResourceSet and/or CSI-SSB-ResourceSet. If there are multiple NZP CSI- RS resource sets configured in a CSI-ResourceConfig, then each such set represents a different set of Set A or Set B beams. In the below example, when isSetBbeam-r19 is set to ‘True’, the NZP CSI-RS resource set(s) with the corresponding resource set Id’s (e.g., nzp-CSI-RS- ResourceSetId’s) configured as part of CSI-ResourceConfig are used for transmitting different sets of Set B beams. Similarly, when isSetAbeam-r19 is set to ‘True’, the NZP CSI-RS resource set(s) with the corresponding resource set Id’s (e.g., nzp-CSI-RS-ResourceSetId’s) configured as part of CSI-ResourceConfig are used for transmitting different sets of Set A beams. CSI-ResourceConfig information element -- ASN1START -- TAG-CSI-RESOURCECONFIG-START CSI-ResourceConfig ::= SEQUENCE { csi-ResourceConfigId CSI-ResourceConfigId, csi-RS-ResourceSetList CHOICE { nzp-CSI-RS-SSB SEQUENCE { nzp-CSI-RS-ResourceSetList SEQUENCE (SIZE (1..maxNrofNZP-CSI-RS- ResourceSetsPerConfig)) OF NZP-CSI-RS-ResourceSetId OPTIONAL, -- Need R csi-SSB-ResourceSetList SEQUENCE (SIZE (1..maxNrofCSI-SSB- ResourceSetsPerConfig)) OF CSI-SSB-ResourceSetId OPTIONAL -- Need R }, csi-IM-ResourceSetList SEQUENCE (SIZE (1..maxNrofCSI-IM- ResourceSetsPerConfig)) OF CSI-IM-ResourceSetId }, ...
P110739WO01 PCT APPLICATION 18 of 62 [[ isSetBbeams-r19 Boolean(True,False) OPTIONAL, -- Need S isSetAbeams-r19 Boolean(True,False) OPTIONAL, -- Need S ]] ... [0085] In particular embodiments, when the parameter beamSet-r19 is configured with ‘isSetB’, the NZP CSI-RS resource set(s) with the corresponding resource set Id’s (e.g., nzp-CSI- RS-ResourceSetId’s) configured as part of CSI-ResourceConfig are used for transmitting different sets of Set B beams. Similarly, when the parameter beamSet-r19 is configured with ‘isSetA’, the NZP CSI-RS resource set(s) with the corresponding resource set Id’s (e.g., nzp-CSI-RS- ResourceSetId’s) configured as part of CSI-ResourceConfig are used for transmitting different sets of Set A beams. [0086] In a variant of this embodiment, the parameter beamSet-r19 may have a third value ‘isSetAandSetB’. In this case, the NZP CSI-RS resource set(s) with the corresponding resource set Id’s (e.g., nzp-CSI-RS-ResourceSetId’s) configured as part of CSI-ResourceConfig may be used for transmitting both beams in Set B and beams in Set A. CSI-ResourceConfig information element -- ASN1START -- TAG-CSI-RESOURCECONFIG-START CSI-ResourceConfig ::= SEQUENCE { csi-ResourceConfigId CSI-ResourceConfigId, csi-RS-ResourceSetList CHOICE { nzp-CSI-RS-SSB SEQUENCE { nzp-CSI-RS-ResourceSetList SEQUENCE (SIZE (1..maxNrofNZP-CSI-RS-ResourceSetsPerConfig)) OF NZP-CSI-RS- ResourceSetId OPTIONAL, -- Need R
P110739WO01 PCT APPLICATION 19 of 62 csi-SSB-ResourceSetList SEQUENCE (SIZE (1..maxNrofCSI-SSB-ResourceSetsPerConfig)) OF CSI-SSB- ResourceSetId OPTIONAL -- Need R }, csi-IM-ResourceSetList SEQUENCE (SIZE (1..maxNrofCSI-IM-ResourceSetsPerConfig)) OF CSI-IM- ResourceSetId }, ... [[ beamSet-r19 Enumerated{isSetB, isSetA} OPTIONAL, -- Need S ]] ... [0087] In particular embodiments, the indication of Set A/Set B may be part of the IE CSI- ReportConfig. For example, the IE CSI-ReportConfig may be used to configure a periodic or semi- persistent report sent on a physical uplink control channel (PUCCH) on the cell in which the CSI- ReportConfig is included, or to configure a semi-persistent or aperiodic report sent on the physical uplink shared channel (PUSCH) triggered by downlink control information (DCI) received on the cell in which the CSI-ReportConfig is included (in this case, the cell on which the report is sent is determined by the received DCI). An example is shown below. When isSetBbeam-r19 is set to ‘True’, the NZP CSI-RS resource set(s) configured as part of CSI-ResourceConfig with CSI- ResourceConfigId given by resourcesForChannelMeasurement are used for transmitting different sets of Set B beams. Similarly, when isSetAbeam-r19 is set to ‘True’, the NZP CSI-RS resource set(s) configured as part of CSI-ResourceConfig with CSI-ResourceConfigId given by resourcesForChannelMeasurement are used for transmitting different sets of Set A beams. CSI-ReportConfig information element -- ASN1START -- TAG-CSI-REPORTCONFIG-START CSI-ReportConfig ::= SEQUENCE { reportConfigId CSI-ReportConfigId,
P110739WO01 PCT APPLICATION 20 of 62 carrier ServCellIndex OPTIONAL, -- Need S resourcesForChannelMeasurement CSI- ResourceConfigId, csi-IM-ResourcesForInterference CSI-ResourceConfigId OPTIONAL, -- Need R ... [[ isSetBbeams-r19 Boolean(True,False) OPTIONAL, -- Need S ….. isSetAbeams-19 Boolean(True,False) OPTIONAL, -- Need S ]] ….. [0088] In particular embodiments, instead of configuring the two fields ‘isSetBbeams’ and ‘isSetAbeams’, a single field ‘beamSet’ with enumerated values {isSetB, isSetA} may be configured as part of CSI-ReportConfig. In this example, when beamSet-r19 is configured with value ‘isSetB’, the NZP CSI-RS resource set(s) configured as part of CSI-ResourceConfig with CSI-ResourceConfigId given by resourcesForChannelMeasurement are used for transmitting different sets of Set B beams. Similarly, when beamSet-r19 is configured with value ‘isSetA’, the NZP CSI-RS resource set(s) configured as part of CSI-ResourceConfig with CSI- ResourceConfigId given by resourcesForChannelMeasurement are used for transmitting different sets of Set A beams. [0089] In a variant of this embodiment, the parameter beamSet-r19 may have a third value ‘isSetAandSetB’. In this case, the NZP CSI-RS resource set(s) configured as part of CSI- ResourceConfig with CSI-ResourceConfigId given by resourcesForChannelMeasurement may be used for transmitting both beams in Set B and beams in Set A. Similar elements may be introduced in a CSI-MeasConfig, e.g. according to the following nonlimiting example. CSI-MeasConfig information element -- ASN1START
P110739WO01 PCT APPLICATION 21 of 62 -- TAG-CSI-MEASCONFIG-START
CSI-MeasConfig ::= SEQUENCE { nzp-CSI-RS-ResourceToAddModList SEQUENCE (SIZE (1..maxNrofNZP-CSI-RS-Resources)) OF NZP-CSI-RS-Resource OPTIONAL, -- Need N nzp-CSI-RS-ResourceToReleaseList SEQUENCE (SIZE (1..maxNrofNZP-CSI-RS-Resources)) OF NZP-CSI-RS-ResourceId OPTIONAL, -- Need N nzp-CSI-RS-ResourceSetToAddModList SEQUENCE (SIZE (1..maxNrofNZP-CSI-RS-ResourceSets)) OF NZP-CSI-RS-ResourceSet OPTIONAL, -- Need N nzp-CSI-RS-ResourceSetToReleaseList SEQUENCE (SIZE (1..maxNrofNZP-CSI-RS-ResourceSets)) OF NZP-CSI-RS-ResourceSetId OPTIONAL, -- Need N csi-IM-ResourceToAddModList SEQUENCE (SIZE (1..maxNrofCSI-IM-Resources)) OF CSI-IM-Resource OPTIONAL, -- Need N csi-IM-ResourceToReleaseList SEQUENCE (SIZE (1..maxNrofCSI-IM-Resources)) OF CSI-IM-ResourceId OPTIONAL, -- Need N csi-IM-ResourceSetToAddModList SEQUENCE (SIZE (1..maxNrofCSI-IM-ResourceSets)) OF CSI-IM-ResourceSet OPTIONAL, -- Need N csi-IM-ResourceSetToReleaseList SEQUENCE (SIZE (1..maxNrofCSI-IM-ResourceSets)) OF CSI-IM-ResourceSetId OPTIONAL, -- Need N csi-SSB-ResourceSetToAddModList SEQUENCE (SIZE (1..maxNrofCSI-SSB-ResourceSets)) OF CSI-SSB-ResourceSet OPTIONAL, -- Need N csi-SSB-ResourceSetToReleaseList SEQUENCE (SIZE (1..maxNrofCSI-SSB-ResourceSets)) OF CSI-SSB-ResourceSetId OPTIONAL, -- Need N
P110739WO01 PCT APPLICATION 22 of 62 csi-ResourceConfigToAddModList SEQUENCE (SIZE (1..maxNrofCSI-ResourceConfigurations)) OF CSI-ResourceConfig OPTIONAL, -- Need N csi-ResourceConfigToReleaseList SEQUENCE (SIZE (1..maxNrofCSI-ResourceConfigurations)) OF CSI-ResourceConfigId OPTIONAL, -- Need N csi-ReportConfigToAddModList SEQUENCE (SIZE (1..maxNrofCSI-ReportConfigurations)) OF CSI-ReportConfig OPTIONAL, -- Need N csi-ReportConfigToReleaseList SEQUENCE (SIZE (1..maxNrofCSI-ReportConfigurations)) OF CSI-ReportConfigId OPTIONAL, -- Need N reportTriggerSize INTEGER (0..6) OPTIONAL, -- Need M aperiodicTriggerStateList SetupRelease { CSI- AperiodicTriggerStateList } OPTIONAL, -- Need M semiPersistentOnPUSCH-TriggerStateList SetupRelease { CSI-SemiPersistentOnPUSCH-TriggerStateList } OPTIONAL, - - Need M ..., [[ reportTriggerSizeDCI-0-2-r16 INTEGER (0..6) OPTIONAL -- Need R ]], [[ sCellActivationRS-ConfigToAddModList-r17 SEQUENCE (SIZE (1..maxNrofSCellActRS-r17)) OF SCellActivationRS-Config-r17 OPTIONAL, -- Need N
P110739WO01 PCT APPLICATION 23 of 62 sCellActivationRS-ConfigToReleaseList-r17 SEQUENCE (SIZE (1..maxNrofSCellActRS-r17)) OF SCellActivationRS-ConfigId-r17 OPTIONAL -- Need N... [[ isSetBbeams-r19 Boolean(True,False) OPTIONAL, -- Need N ….. isSetAbeams-r19 Boolean(True,False) OPTIONAL, -- Need N ]] } -- TAG-CSI-MEASCONFIG-STOP -- ASN1STOP embodiments, the Boolean indications indicating Set A/B in the above examples may instead be integers that may indicate not only whether a beam or set belongs to Set A/B, but may also indicate which Set A/B to which the beam belongs. In one example, either SetA- ID or SetB-ID or both SetA-ID and SetB-ID may be configured instead of the Boolean labeling of Set A or Set B beams. [0091] Further, in some variants of this embodiment, the indication of whether the beam is part of Set A/B is then done by another method, and the integer is only used if the beam is indicated to be part of Set A/B by the other method. [0092] In particular embodiments, the indication of Set A/B beams is done through a list in CSI-MeasConfig or CSI-ReportConfig. In one non-limiting example, it is done according to the following. CSI-MeasConfig information element -- ASN1START -- TAG-CSI-MEASCONFIG-START CSI-MeasConfig ::= SEQUENCE { nzp-CSI-RS-ResourceToAddModList SEQUENCE (SIZE (1..maxNrofNZP-CSI-RS-Resources)) OF NZP-CSI-RS-Resource OPTIONAL, -- Need N
P110739WO01 PCT APPLICATION 24 of 62 nzp-CSI-RS-ResourceToReleaseList SEQUENCE (SIZE (1..maxNrofNZP-CSI-RS-Resources)) OF NZP-CSI-RS-ResourceId OPTIONAL, -- Need N nzp-CSI-RS-ResourceSetToAddModList SEQUENCE (SIZE (1..maxNrofNZP-CSI-RS-ResourceSets)) OF NZP-CSI-RS-ResourceSet OPTIONAL, -- Need N nzp-CSI-RS-ResourceSetToReleaseList SEQUENCE (SIZE (1..maxNrofNZP-CSI-RS-ResourceSets)) OF NZP-CSI-RS-ResourceSetId OPTIONAL, -- Need N csi-IM-ResourceToAddModList SEQUENCE (SIZE (1..maxNrofCSI-IM-Resources)) OF CSI-IM-Resource OPTIONAL, -- Need N csi-IM-ResourceToReleaseList SEQUENCE (SIZE (1..maxNrofCSI-IM-Resources)) OF CSI-IM-ResourceId OPTIONAL, -- Need N csi-IM-ResourceSetToAddModList SEQUENCE (SIZE (1..maxNrofCSI-IM-ResourceSets)) OF CSI-IM-ResourceSet OPTIONAL, -- Need N csi-IM-ResourceSetToReleaseList SEQUENCE (SIZE (1..maxNrofCSI-IM-ResourceSets)) OF CSI-IM-ResourceSetId OPTIONAL, -- Need N csi-SSB-ResourceSetToAddModList SEQUENCE (SIZE (1..maxNrofCSI-SSB-ResourceSets)) OF CSI-SSB-ResourceSet OPTIONAL, -- Need N csi-SSB-ResourceSetToReleaseList SEQUENCE (SIZE (1..maxNrofCSI-SSB-ResourceSets)) OF CSI-SSB-ResourceSetId OPTIONAL, -- Need N csi-ResourceConfigToAddModList SEQUENCE (SIZE (1..maxNrofCSI-ResourceConfigurations)) OF CSI-ResourceConfig OPTIONAL, -- Need N csi-ResourceConfigToReleaseList SEQUENCE (SIZE (1..maxNrofCSI-ResourceConfigurations)) OF CSI-ResourceConfigId
P110739WO01 PCT APPLICATION 25 of 62 OPTIONAL, -- Need N csi-ReportConfigToAddModList SEQUENCE (SIZE (1..maxNrofCSI-ReportConfigurations)) OF CSI-ReportConfig OPTIONAL, -- Need N csi-ReportConfigToReleaseList SEQUENCE (SIZE (1..maxNrofCSI-ReportConfigurations)) OF CSI-ReportConfigId OPTIONAL, -- Need N reportTriggerSize INTEGER (0..6) OPTIONAL, -- Need M aperiodicTriggerStateList SetupRelease { CSI- AperiodicTriggerStateList } OPTIONAL, -- Need M semiPersistentOnPUSCH-TriggerStateList SetupRelease { CSI-SemiPersistentOnPUSCH-TriggerStateList } OPTIONAL, - - Need M ..., [[ reportTriggerSizeDCI-0-2-r16 INTEGER (0..6) OPTIONAL -- Need R ]], [[ sCellActivationRS-ConfigToAddModList-r17 SEQUENCE (SIZE (1..maxNrofSCellActRS-r17)) OF SCellActivationRS-Config-r17 OPTIONAL, -- Need N sCellActivationRS-ConfigToReleaseList-r17 SEQUENCE (SIZE (1..maxNrofSCellActRS-r17)) OF SCellActivationRS-ConfigId-r17 OPTIONAL -- Need N... [[ csi-SetAbeams SEQUENCE (SIZE (1..maxNrofCSI-RS-Resources)) OF CSI-RS-Resource OPTIONAL, -- Need N
P110739WO01 PCT APPLICATION 26 of 62 ….. csi-SetBbeams SEQUENCE (SIZE (1..maxNrofCSI-RS-Resources)) OF CSI-RS-ResourceId OPTIONAL, -- Need N ]] } -- TAG-CSI-MEASCONFIG-STOP -- ASN1STOP [0093] In particular embodiments, the indication of Set A/B beams is provided in a separated IE for AI/ML CSI report, e.g. CSI-AI-ReportConfig, similar to the example below. CSI-AI-ReportConfig ::= SEQUENCE { reportConfigId CSI-AI- ReportConfigId, carrier ServCellIndex OPTIONAL, -- Need S AI-BeamManagement:: SEQUENCE { UsageType ENUMERATED {beamPrediction, …} csi-SetAbeams SEQUENCE (SIZE (1..maxNrofCSI-RS-Resources)) OF CSI-RS-Resource OPTIONAL, -- Need N ….. csi-SetBbeams SEQUENCE (SIZE (1..maxNrofCSI-RS-Resources)) OF CSI-RS-ResourceId OPTIONAL, -- Need N } } [0094] In particular embodiments, a medium access control (MAC) control element (CE) may be used to update the CSI-RS resources in Set A/Set B associated with a report ID.
P110739WO01 PCT APPLICATION 27 of 62 [0095] Alternatively or additionally, SSB resources may be indicated as Set A/B beams in CSI-MeasConfig or CSI-ReportConfig or channel state information - assisted interference (CSI- AI)-ReportConfig. [0096] Some embodiments include configuring the consistency of Set A/B. A potential issue with a data-driven approach for training a beam prediction AI/ML model is that different sites/cells may have different antenna/beam configurations. Moreover, even within the same cell, there may be scenarios where antenna/beam configurations are semi-dynamically adjusted to better fit the current traffic load situations. To enable a trained AI/ML model at the UE-side to generalize to many different scenarios and/or antenna/beam configurations, in some embodiments, an identifier is provided to the UE indicating the beam configuration/pattern. For example, if the UE receives the same beam configuration/pattern ID over two or more cells, it may be assumed that the CSI resources are using the same beams/precoders. This may be achieved via the standard introducing a “consistency” identifier for its CSI resources, that is then valid over a longer duration than a normal ResourceID, and possibly over multiple cells. Note that the “consistency” identifier may be a set of IDs that are configured over multiple cells with different physical cell Ids while NZP- CSI-RS-Resource’s, NZP-CSI-RS-ResourceSet’s, CSI-ResourceConfig’s and CSI- ReportConfig’s are configured within each cell. This may be included via any of the options above via extending its respective IE according to Table 1. [0097] In particular embodiments, the consistency identifier may be generated using any of the following information: ^ Global Cell ID or physical Cell ID ^ public land mobile network (PLMN)-ID ^ Network Vendor info o Vendor ID ^ Deployment info o Antenna physical tilt o Antenna physical direction o Antenna Position ^ Beam pattern information o For example, a time when beam pattern or specific beam that impacts a resourceID or was changed ^ Time when the identifier was generated. [0098] In particular embodiments, the time when the identifier was generated is also part of the information element, or the consistency-identifier is only represented via a time-stamp.
P110739WO01 PCT APPLICATION 28 of 62 [0099] Figure 8 is a flowchart illustrating an example of a beam prediction model, according to the embodiments when Set A/B beams are indicated as part of the resourceConfigID. Note that the UE is done using multiple samples of A and B, possibly in a UE server. [0100] Particular steps are performed by the UE. In the beam selection step, based on the received reference signal transmissions and collected measurements, the UE selects one or more Set B beams to train one or more AI models. The one or more selected Set B beams may comprise one or more of the following beams: one or more SSB beams; one or more narrow beams, e.g. the beams configured for CSI measurements; and/or the beams that the network may activate to aid the UE prediction. [0101] For each of the Sets B, the UE may associate a Set A, wherein the Set A may be a subset of the beams listed above. For temporal beam prediction, Set B, or a subset of Set B may be included in Set A. [0102] In particular embodiments, the UE may select a Set B that is not indicated by the network, as long as the beams in the indicated Set B are a subset of a Set B provided by the network. In particular embodiments, the UE may select a combination of Set B that is used to predict a single Set A of beams. In particular embodiments, if the network provides an associated Set A for each of Set B, the UE selects one or more Set B beams to train one or more AI models to predict the associated Set A beams. [0103] Next, in the training step, the UE trains one or more beam prediction AI models corresponding to each of the selected Set (A,B) combination. If none of Set B is supported, the UE may indicate inapplicability for the indicated Set B. i.e. the UE does not have any AI/ML model that uses this Set B as an input, or is not capable of training an AL/ML model based on this specific Set B. [0104] The steps 1 and 2 (e.g., beam selection step and training step) may be performed by the UE itself, or delegated to another external entity (e.g., training server) that decides on the selection of Set B based on the reported measurements from one or more UEs. In this case, the external entity trains one or more AI models and delivers the one or more models with the additional information about Set A and B to the UE. [0105] In particular embodiments, the selection of Set A and Set B may be based on any one or more of the following: ^ Performance of the combination of Set B/Set A, for example it should be above a certain accuracy level ^ Cost of measurements; for example, when the UE is battery constrained, the UE may select to measure on less Set B beams to save energy
P110739WO01 PCT APPLICATION 29 of 62 ^ Battery type/service type/QoS target/device type ^ Estimate of achievable power savings from different omission patterns ^ UE computational capabilities, for example in terms of number of operations per second, type of processor (CPU, GPU), number of CPUs. This could be reported specifically for executing machine learning model or more generally associated to the UE [0106] Note that reducing the number of beams in Set B leads to fewer model inputs and thereby typically simpler models. [0107] Some embodiments include UE aspects for AI/ML model inference. When the UE has trained the model based on the one or more Set B/A received from the network, the UE signals in UE capability signaling support for AI-based beam prediction based on the one or more Set A/Set B alternatives. [0108] The UE may, for example, report any one or more of the following: ^ When Set B/Set A beams are indicated in the NZP-CSI-RS-Resource information element, which nzp-CSI-RS-ResourceId that are part of Set B/Set A. ^ When Set B/Set A beams are indicated in the NZP-CSI-RS-ResourceSet information element, which nzp-CSI-RS-ResourceSetIds are part of Set B/Set A. o Additionally, the UE may indicate which nzp-CSI-RS-ResourceId’s if only a subset of the beams in each NZP CSI-RS resource set are included. ^ When Set B/Set A beams are indicated in the CSI-ResourceConfig information element, which nzp-CSI-RS-ResourceConfig IDs that are part of Set B/Set A. o The UE may also include the above information on specific CSI-RS- ResourceId(s) and nzp-CSI-RS-ResourceSetId(s) that are part of Set B/Set A. ^ When Set B/Set A beams are indicated in the CSI-ReportConfig information element, which CSI-ReportConfigID that are part of Set B/Set A. o The UE may also include the above information on specific -CSI-RS- ResourceId(s) and nzp-CSI-RS-ResourceSetId(s) that are part of Set B/Set A. ^ That the UE only needs the SSB beams in Set B, and the Set A beams according to any of the above methods. ^ a consistency identifier. [0109] In particular embodiments, the UE may also report how many or which of the Set A/Set B alternatives may be supported/run simultaneously. In this step, the UE may report the information via any one or more of RRC, UL MAC CE, or UCI. The UE may further also include the performance in terms of accuracy for each of the combinations above.
P110739WO01 PCT APPLICATION 30 of 62 [0110] In particular embodiments, the information in this step is conveyed as partly in “UE Assistance Information” procedure specified in TS 38.331. The indication of the supported Set (A,B) alternatives may in this framework both support proactive and reactive reporting, where the network may request a UE to report which Sets (A, B) it may support. [0111] Some embodiments include network aspects for UE AI/ML model inference. In particular embodiments, the network may, based on the UE reported alternatives of Set (A, B), decide on one or more preferred Set (A,B). As non-limiting examples, a preferred Set (A,B) may be selected targeting: aligning Set B across different UEs, so that the network has opportunities to reduce RS transmissions by requesting the UEs to measure on the same Set B beams; aligning Set A across different UEs, so that the network has opportunities to minimize RS transmissions on non-measured Set A beams; and maximizing the alignment on non-measured beams (i.e. predicted beams) across different UEs. [0112] The network may also configure the Set A beams to predict by indicating using any of the methods described above, also with a flag that indicates that the CSI-report or CSI-resource configuration or CSI-resource or CSI-resourceSets are considered “virtual”, i.e. not physically transmitted. Other possible naming may includes that these are “predictedBeams”. For example, if the Set A beams are indicated as part of the CSI-ReportConfig. Similarly, when isSetAbeam- r19 is set to ‘True’, the NZP CSI-RS resource set(s) configured as part of CSI-ResourceConfig with CSI-ResourceConfigId given by resourcesForChannelMeasurement are used for transmitting different sets of Set A beams. CSI-ReportConfig information element -- ASN1START -- TAG-CSI-REPORTCONFIG-START CSI-ReportConfig ::= SEQUENCE { reportConfigId CSI-ReportConfigId, consistency-csi-ReportConfigId Integer(0..Max- consistency-csi-ReportConfigIDs),OPTIONAL carrier ServCellIndex OPTIONAL, -- Need S resourcesForChannelMeasurement CSI- ResourceConfigId, csi-IM-ResourcesForInterference CSI-ResourceConfigId OPTIONAL, -- Need R
P110739WO01 PCT APPLICATION 31 of 62 ... [[ isSetBbeams-r19 Boolean(True,False) OPTIONAL, -- Need S ….. isSetAbeams-19 Boolean(True,False) OPTIONAL, -- Need S ….. isVirtualSetAbeams-19 Boolean(True,False) OPTIONAL, -- Need S ]] ….. ^ isVirtualSetAbeams: A field that indicates that the associated resources in a reportConfig is not transmitted over-the-air interface. But is predicted by the UE. ^ consistency-csi-ReportConfigId: An ID that indicates whether the UE may assume that reported resources are using the same spatial TX-filters across time (as described herein.) [0113] Figure 9 shows an example of a communication system 100 in accordance with some embodiments. In the example, the communication system 100 includes a telecommunication network 102 that includes an access network 104, such as a radio access network (RAN), and a core network 106, which includes one or more core network nodes 108. The access network 104 includes one or more access network nodes, such as network nodes 110a and 110b (one or more of which may be generally referred to as network nodes 110), or any other similar 3rd Generation Partnership Project (3GPP) access node or non-3GPP access point. The network nodes 110 facilitate direct or indirect connection of user equipment (UE), such as by connecting UEs 112a, 112b, 112c, and 112d (one or more of which may be generally referred to as UEs 112) to the core network 106 over one or more wireless connections. [0114] 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 100 may include any number of wired or wireless networks, network nodes, UEs, and/or any other
P110739WO01 PCT APPLICATION 32 of 62 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 100 may include and/or interface with any type of communication, telecommunication, data, cellular, radio network, and/or other similar type of system. [0115] The UEs 112 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 110 and other communication devices. Similarly, the network nodes 110 are arranged, capable, configured, and/or operable to communicate directly or indirectly with the UEs 112 and/or with other network nodes or equipment in the telecommunication network 102 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 102. [0116] In the depicted example, the core network 106 connects the network nodes 110 to one or more hosts, such as host 116. 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 106 includes one more core network nodes (e.g., core network node 108) 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 108. 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). [0117] The host 116 may be under the ownership or control of a service provider other than an operator or provider of the access network 104 and/or the telecommunication network 102 and may be operated by the service provider or on behalf of the service provider. The host 116 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. [0118] As a whole, the communication system 100 of Figure 9 enables connectivity between the UEs, network nodes, and hosts. In that sense, the communication system may be configured to
P110739WO01 PCT APPLICATION 33 of 62 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. [0119] In some examples, the telecommunication network 102 is a cellular network that implements 3GPP standardized features. Accordingly, the telecommunications network 102 may support network slicing to provide different logical networks to different devices that are connected to the telecommunication network 102. For example, the telecommunications network 102 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)/Massive IoT services to yet further UEs. [0120] In some examples, the UEs 112 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 104 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network 104. Additionally, a UE may be configured for operating in single- or multi-RAT or multi-standard mode. For example, a UE may 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). [0121] In the example, the hub 114 communicates with the access network 104 to facilitate indirect communication between one or more UEs (e.g., UE 112c and/or 112d) and network nodes (e.g., network node 110b). In some examples, the hub 114 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs. For example, the hub 114 may be a broadband router enabling access to the core network 106 for the UEs. As another example, the hub 114 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 110, or by executable code, script, process, or other instructions in the hub 114. As another example, the hub 114 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
P110739WO01 PCT APPLICATION 34 of 62 example, the hub 114 may be a content source. For example, for a UE that is a VR headset, display, loudspeaker or other media delivery device, the hub 114 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub 114 then provides to the UE either directly, after performing local processing, and/or after adding additional local content. In still another example, the hub 114 acts as a proxy server or orchestrator for the UEs, in particular in if one or more of the UEs are low energy IoT devices. [0122] The hub 114 may have a constant/persistent or intermittent connection to the network node 110b. The hub 114 may also allow for a different communication scheme and/or schedule between the hub 114 and UEs (e.g., UE 112c and/or 112d), and between the hub 114 and the core network 106. In other examples, the hub 114 is connected to the core network 106 and/or one or more UEs via a wired connection. Moreover, the hub 114 may be configured to connect to an M2M service provider over the access network 104 and/or to another UE over a direct connection. In some scenarios, UEs may establish a wireless connection with the network nodes 110 while still connected via the hub 114 via a wired or wireless connection. In some embodiments, the hub 114 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 110b. In other embodiments, the hub 114 may be a non- dedicated hub – that is, a device which is capable of operating to route communications between the UEs and network node 110b, but which is additionally capable of operating as a communication start and/or end point for certain data channels. [0123] Figure 10 shows a UE 200 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. [0124] A UE may support device-to-device (D2D) communication, for example by implementing a 3GPP 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
P110739WO01 PCT APPLICATION 35 of 62 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). [0125] The UE 200 includes processing circuitry 202 that is operatively coupled via a bus 204 to an input/output interface 206, a power source 208, a memory 210, a communication interface 212, and/or any other component, or any combination thereof. Certain UEs may utilize all or a subset of the components shown in Figure 9. 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. [0126] The processing circuitry 202 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 210. The processing circuitry 202 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 202 may include multiple central processing units (CPUs). [0127] In the example, the input/output interface 206 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 200. 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 presence-sensitive 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.
P110739WO01 PCT APPLICATION 36 of 62 [0128] In some embodiments, the power source 208 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 208 may further include power circuitry for delivering power from the power source 208 itself, and/or an external power source, to the various parts of the UE 200 via input circuitry or an interface such as an electrical power cable. Delivering power may be, for example, for charging of the power source 208. Power circuitry may perform any formatting, converting, or other modification to the power from the power source 208 to make the power suitable for the respective components of the UE 200 to which power is supplied. [0129] The memory 210 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 210 includes one or more application programs 214, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data 216. The memory 210 may store, for use by the UE 200, any of a variety of various operating systems or combinations of operating systems. [0130] The memory 210 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 210 may allow the UE 200 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 210, which may be or comprise a device-readable storage medium. [0131] The processing circuitry 202 may be configured to communicate with an access network or other network using the communication interface 212. The communication interface 212 may comprise one or more communication subsystems and may include or be
P110739WO01 PCT APPLICATION 37 of 62 communicatively coupled to an antenna 222. The communication interface 212 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 218 and/or a receiver 220 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth). Moreover, the transmitter 218 and receiver 220 may be coupled to one or more antennas (e.g., antenna 222) and may share circuit components, software or firmware, or alternatively be implemented separately. [0132] In the illustrated embodiment, communication functions of the communication interface 212 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. [0133] Regardless of the type of sensor, a UE may provide an output of data captured by its sensors, through its communication interface 212, 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). [0134] 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. [0135] A UE, when in the form of an Internet of Things (IoT) device, may be a device for use in one or more application domains, these domains comprising, but not limited to, city wearable
P110739WO01 PCT APPLICATION 38 of 62 technology, extended industrial application and healthcare. Non-limiting examples of such an IoT 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 IoT device comprises circuitry and/or software in dependence of the intended application of the IoT device in addition to other components as described in relation to the UE 200 shown in Figure 9. [0136] As yet another specific example, in an IoT 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 3GPP context be referred to as an MTC device. As one particular example, the UE may implement the 3GPP 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. [0137] 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. [0138] Figure 11 shows a network node 300 in accordance with some embodiments. As used herein, network node refers to equipment capable, configured, arranged and/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
P110739WO01 PCT APPLICATION 39 of 62 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)). [0139] 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). [0140] Other examples of network nodes include multiple transmission point (multi-TRP) 5G access nodes, multi-standard radio (MSR) equipment such as MSR BSs, 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). [0141] The network node 300 includes a processing circuitry 302, a memory 304, a communication interface 306, and a power source 308. The network node 300 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 300 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 300 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memory 304 for different RATs) and some components may be reused (e.g., a same antenna 310 may be shared by different RATs). The network node 300 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 300, for example GSM, WCDMA, LTE, NR, WiFi, Zigbee, Z-wave, LoRaWAN, Radio Frequency Identification (RFID) or Bluetooth wireless technologies. These
P110739WO01 PCT APPLICATION 40 of 62 wireless technologies may be integrated into the same or different chip or set of chips and other components within network node 300. [0142] The processing circuitry 302 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 300 components, such as the memory 304, to provide network node 300 functionality. [0143] In some embodiments, the processing circuitry 302 includes a system on a chip (SOC). In some embodiments, the processing circuitry 302 includes one or more of radio frequency (RF) transceiver circuitry 312 and baseband processing circuitry 314. In some embodiments, the radio frequency (RF) transceiver circuitry 312 and the baseband processing circuitry 314 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 312 and baseband processing circuitry 314 may be on the same chip or set of chips, boards, or units. [0144] The memory 304 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), read-only 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 302. The memory 304 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 302 and utilized by the network node 300. The memory 304 may be used to store any calculations made by the processing circuitry 302 and/or any data received via the communication interface 306. In some embodiments, the processing circuitry 302 and memory 304 is integrated. [0145] The communication interface 306 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 306 comprises port(s)/terminal(s) 316 to send and receive data, for example to and from a network over a wired connection. The communication interface 306 also includes radio front-end circuitry 318 that may be coupled to, or in certain embodiments a part of, the antenna 310. Radio front-end circuitry 318 comprises filters 320 and amplifiers 322. The radio
P110739WO01 PCT APPLICATION 41 of 62 front-end circuitry 318 may be connected to an antenna 310 and processing circuitry 302. The radio front-end circuitry may be configured to condition signals communicated between antenna 310 and processing circuitry 302. The radio front-end circuitry 318 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 318 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 320 and/or amplifiers 322. The radio signal may then be transmitted via the antenna 310. Similarly, when receiving data, the antenna 310 may collect radio signals which are then converted into digital data by the radio front-end circuitry 318. The digital data may be passed to the processing circuitry 302. In other embodiments, the communication interface may comprise different components and/or different combinations of components. [0146] In certain alternative embodiments, the network node 300 does not include separate radio front-end circuitry 318, instead, the processing circuitry 302 includes radio front-end circuitry and is connected to the antenna 310. Similarly, in some embodiments, all or some of the RF transceiver circuitry 312 is part of the communication interface 306. In still other embodiments, the communication interface 306 includes one or more ports or terminals 316, the radio front-end circuitry 318, and the RF transceiver circuitry 312, as part of a radio unit (not shown), and the communication interface 306 communicates with the baseband processing circuitry 314, which is part of a digital unit (not shown). [0147] The antenna 310 may include one or more antennas, or antenna arrays, configured to send and/or receive wireless signals. The antenna 310 may be coupled to the radio front-end circuitry 318 and may be any type of antenna capable of transmitting and receiving data and/or signals wirelessly. In certain embodiments, the antenna 310 is separate from the network node 300 and connectable to the network node 300 through an interface or port. [0148] The antenna 310, communication interface 306, and/or the processing circuitry 302 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 310, the communication interface 306, and/or the processing circuitry 302 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. [0149] The power source 308 provides power to the various components of network node 300 in a form suitable for the respective components (e.g., at a voltage and current level needed for
P110739WO01 PCT APPLICATION 42 of 62 each respective component). The power source 308 may further comprise, or be coupled to, power management circuitry to supply the components of the network node 300 with power for performing the functionality described herein. For example, the network node 300 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 308. As a further example, the power source 308 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. [0150] Embodiments of the network node 300 may include additional components beyond those shown in Figure 11 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 300 may include user interface equipment to allow input of information into the network node 300 and to allow output of information from the network node 300. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node 300. [0151] Figure 12 is a block diagram illustrating a virtualization environment 500 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 more virtual 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 500 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. [0152] Applications 502 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) are run in the virtualization environment Q400 to implement some of the features, functions, and/or benefits of some of the embodiments disclosed herein. [0153] Hardware 504 includes processing circuitry, memory that stores software and/or instructions executable by hardware processing circuitry, and/or other hardware devices as
P110739WO01 PCT APPLICATION 43 of 62 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 506 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VMs 508a and 508b (one or more of which may be generally referred to as VMs 508), and/or perform any of the functions, features and/or benefits described in relation with some embodiments described herein. The virtualization layer 506 may present a virtual operating platform that appears like networking hardware to the VMs 508. [0154] The VMs 508 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer 506. Different embodiments of the instance of a virtual appliance 502 may be implemented on one or more of VMs 508, 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. [0155] In the context of NFV, a VM 508 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 508, and that part of hardware 504 that executes that VM, be it hardware dedicated to that VM and/or hardware shared by that VM with others of the VMs, forms separate 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 508 on top of the hardware 504 and corresponds to the application 502. [0156] Hardware 504 may be implemented in a standalone network node with generic or specific components. Hardware 504 may implement some functions via virtualization. Alternatively, hardware 504 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 510, which, among others, oversees lifecycle management of applications 502. In some embodiments, hardware 504 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 512 which may alternatively be used for communication between hardware nodes and radio units.
P110739WO01 PCT APPLICATION 44 of 62 [0157] 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. [0158] 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. [0159] FIGURE 13 is a flowchart illustrating an example method 1300 in a wireless device, according to certain embodiments. In particular embodiments, one or more steps of FIGURE 13 may be performed by UE 200 described with respect to FIGURE 10. The wireless device is operable to perform beam prediction in a wireless network.
P110739WO01 PCT APPLICATION 45 of 62 [0160] The method 1300 may begin at step 1312, where the wireless device (e.g., UE 200) receives a second CSI configuration. The second CSI configuration comprises an indication of beam Set A, an indication of beam Set B, and the second consistency identifier associated with beam Set A and second beam Set B. The wireless device may receive the CSI configuration according to any of the embodiments and examples described herein. [0161] At step 1314, the wireless device may measure one or more beams of beam Set B. At step 1316, the wireless device may measure one or more beams of beam Set A., At step 1318, the wireless device may train a beam prediction model (e.g., AI/ML model) based on the measurements of the one or more beams of beam Set B and the measurements of the one or more beams of beam Set A. [0162] After training the beam prediction model, the second consistency identifier is associated with the beam prediction model. The wireless device may compare any future received consistency identifiers with the consistency identifier associated with the beam prediction model to determine if beam sets associated with the future received consistency identifiers are compatible with the beam prediction model. [0163] The previous training steps are optional, because in some embodiments the beam prediction model may be trained elsewhere and then the trained beam prediction model is provided to the wireless device. [0164] At step 1320, the wireless device receives a first CSI configuration from a network node. The first CSI configuration comprises an indication of a beam Set A, an indication of a beam Set B, and a first consistency identifier associated with beam Set A and beam Set B. The wireless device may receive the CSI configuration according to any of the embodiments and examples described herein. [0165] At step 1322, the wireless device determines the wireless device supports a beam prediction model that uses one or more beams of beam Set B as input and one or more beams of beam Set A as output. The determination is based on the first consistency identifier matching a second consistency identifier associated with beam Set A and beam Set B used for training the beam prediction model. [0166] At step 1324, the wireless device measures one or more beams of beam Set B. At step 1326, the wireless device predicts measurements for one or more beams of beam Set A based on the measured one or more beams of beam Set B and the beam prediction model. At step 1326, the wireless device reports the predicted measurements for the one or beams of beam Set A to the network node.
P110739WO01 PCT APPLICATION 46 of 62 [0167] In particular embodiments, beam Set B is a subset of beam Set A, or beam Set B is not a subset of beam Set A (e.g., beams Set A is a set of narrow beams and beam Set B is a set of wide beams). [0168] In particular embodiments, the first consistency identifier and the second consistency identifier each comprise a pair of identifiers, one identifier of the pair associated with beam Set A and another identifier of the pair associated with beam Set B. [0169] In particular embodiments, at least one of the indication of beam Set A, the indication of beam Set B, and the first consistency identifier is included in one of: CSI-reportingConfig; CSI- resourceConfig; CSI-resourceSetList; CSI-ResourceList; or CSI-Resource. [0170] In particular embodiments, the second consistency identifier is received in a first RRC session and the first consistency identifier is received in a second RRC session, different from the first RRC session. [0171] In particular embodiments, the second consistency identifier is received in a first cell and the first consistency identifier is received in a second cell, different from the first cell. [0172] In particular embodiments, the first consistency identifier matching the second consistency identifier indicates that: CSI resources associated with the first consistency identifier are using the same beams or precoders as CSI resources associated with the second consistency identifier; or CSI resources associated with the first consistency identifier are using the same spatial transmit filters as CSI resources associated with the second consistency identifier. [0173] In particular embodiments, each of the first consistency identifier and the second consistency identifier are based on one or more of: a cell identifier; a public land mobile network identifier; a vendor identifier; an antenna tilt; an antenna direction; an antenna position; a beam pattern; and a timestamp. [0174] Modifications, additions, or omissions may be made to method 1300 of FIGURE 13. Additionally, one or more steps in the method of FIGURE 13 may be performed in parallel or in any suitable order. [0175] FIGURE 14 is a flowchart illustrating an example method 1400 in a network node, according to certain embodiments. In particular embodiments, one or more steps of FIGURE 14 may be performed by network node 300 described with respect to FIGURE 11. The network node is operable to perform beam prediction in a wireless network. [0176] The method 1400 may begin at step 1412, where the network node (e.g., network node 300) transmits a second CSI configuration to a wireless device. The second CSI configuration comprises an indication of beam Set A, an indication of beam Set B, and a second consistency identifier associated with beam Set A and beam Set B.
P110739WO01 PCT APPLICATION 47 of 62 [0177] At step 1414, the network node transmits one or more beams of beam Set B. At step 1416, the network node transmits one or more beams of beam Set A. The wireless device may use the transmitted beams for training a beam prediction model. [0178] At step 1418, the network node transmits a first CS, configuration to the wireless device. The first CSI configuration comprises an indication of a beam Set A, an indication of a beam Set B, and a first consistency identifier associated with beam Set A and beam Set B. The first consistency identifier matches a second consistency identifier associated with beam Set A and beam Set B used for training a beam prediction model used by the wireless device. [0179] At step 1420, the network node transmits one or more beams of beam Set B. [0180] At step 1422, the network node receives predicted measurements for one or more beams of beam Set A from the wireless device. The predicted measurements are based on measurements of one or more beams of beam Set B and the beam prediction model. [0181] Modifications, additions, or omissions may be made to method 1400 of FIGURE 14. Additionally, one or more steps in the method of FIGURE 14 may be performed in parallel or in any suitable order. [0182] The foregoing description sets forth numerous specific details. It is understood, however, that embodiments may be practiced without these specific details. In other instances, well-known circuits, structures and techniques have not been shown in detail in order not to obscure the understanding of this description. Those of ordinary skill in the art, with the included descriptions, will be able to implement appropriate functionality without undue experimentation. [0183] References in the specification to “one embodiment,” “an embodiment,” “an example embodiment,” etc., indicate that the embodiment described may include a particular feature, structure, or characteristic, but every embodiment may not necessarily include 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 implement such feature, structure, or characteristic in connection with other embodiments, whether or not explicitly described. [0184] Although this disclosure has been described in terms of certain embodiments, alterations and permutations of the embodiments will be apparent to those skilled in the art. Accordingly, the above description of the embodiments does not constrain this disclosure. Other changes, substitutions, and alterations are possible without departing from the scope of this disclosure, as defined by the claims below. [0185] Some example embodiments are described below.
P110739WO01 PCT APPLICATION 48 of 62 Group A Embodiments 1. A method performed by a user equipment (UE) for implementing a beam prediction model in a wireless network, the method comprising: receiving beam indication information regarding two sets of beams, wherein the two sets of beam comprise a beam set A and a beam set B, wherein the beam set A represents beams for an inference operation of a beam prediction model, and the beam set B represents beams for a training operation of the beam prediction model; receiving a first consistency identifier (ID) associated with the beam set A, wherein first the consistency ID indicates whether the beam set A is used by different or same resources on different time instances; receiving a second consistency ID associated with the beam set B, wherein second the consistency ID indicates whether the beam set B is used by different or same resources on different time instances; receiving a first signal on the beam set A; performing a measurement on the first signal; receiving a second signal on the beam set B; performing a measurement on the second signal; selecting one or more beams of the beam set B based at least on the measurement on the beam set B; and training the beam prediction model to predict the beam set A based on the selected one or more beams of the beam set B. 2. The method of embodiment 1, wherein the beam prediction model is configured to predict a beam configuration for the beam set A that leads to a signal quality that is higher than signal qualities due to other beam configurations. 3. The method of any one of the embodiments 1-2, wherein the selected one or more beams of the beam set B comprise: one or more synchronization signal block (SSB) beams; one or more narrow beams configured for channel state information (CSI) measurements; or one or more beams activated by a network. 4. The method of any one of embodiments 1-3, wherein the one or more beams of the beam
P110739WO01 PCT APPLICATION 49 of 62 set B is further selected based at least on: performance of a combination of the beam set A and beam set B; energy cost of the first and second measurements; a battery type of the UE; a service type; a target quality of service (QoS); a device type of the UE; estimated power savings for different omission patterns; or computational capability of the UE. 5. The method of any of the embodiments 1-4, wherein the beam indication information is received within a channel state information (CSI) resource, wherein the CSI resource comprises one of: CSI-reportingConfig; CSI-resourceConfig; CSI-resourceSetList; CSI-ResourceList; or CSI-Resource. 6. The method of any of the embodiments 1-5, wherein each of the first and second consistency IDs comprises one of: consistency- non-zero-power channel state information reference signal (nzp-CSI-RS)- ResourceId; consistency-nzp-CSI-RS-ResourceSetId; consistency-csi-ReportConfigId,; or and consistency-csi-ResourceConfigId. 7. The method of any one of the embodiments 1-6, wherein receiving the beam indication information is in response to transmitting a first message indicating capability of the UE for training the beam prediction model. 8. The method of any one of the embodiments 1-7, further comprising: communicating a second message indicating capability of the UE in beam prediction; receiving a second beam indication information regarding the two sets of beams;
P110739WO01 PCT APPLICATION 50 of 62 receiving the first consistency ID associated with the beam set A; receiving the second consistency ID associated with the beam set B; determining whether the beam prediction model supports the beam set A based at least on the first consistency ID; determining whether the beam prediction model supports the beam set B based at least on the second consistency ID; receiving a third signal on the beam set B; performing a measurement on the third signal; in response to determining that the beam prediction model supports the beam set A and beam set B, initiating a beam prediction operation using the trained beam prediction model based at least on the measurement on the third signal; and reporting a predicted beam from among the beam set A. 9. A method performed by a wireless device, the method comprising: − any of the wireless device steps, features, or functions described above, either alone or in combination with other steps, features, or functions described above. 10. The method of the previous embodiment, further comprising one or more additional wireless device steps, features or functions described above. 11. The method of any of the previous embodiments, further comprising: − providing user data; and − forwarding the user data to a host computer via the transmission to the base station. Group B Embodiments 12. A method performed by a network node for implementing a beam prediction model in a wireless network, the method comprising: transmitting beam indication information regarding two sets of beams, wherein the two sets of beams comprise a beam set A and a beam set B, wherein the beam set A represents beams for an inference operation of a beam prediction model, and the beam set B represents beams for a training operation of the beam prediction model; transmitting a first consistency identifier (ID) associated with the beam set A, wherein first the consistency ID indicates whether the beam set A is used by different or same resources on different time instances;
P110739WO01 PCT APPLICATION 51 of 62 transmitting a second consistency ID associated with the beam set B, wherein second the consistency ID indicates whether the beam set B is used by different or same resources on different time instances; transmitting a first signal on the beam set A; receiving a measurement on the first signal; transmitting a second signal on the beam set B; receiving a measurement on the second signal; receiving a selection of one or more beams of the beam set B based at least on the measurement on the beam set B; and receiving an indication that the beam prediction model is being trained to predict the beam set A based on the selected one or more beams of the beam set B. 13. The method of embodiment 12, wherein the beam prediction model is configured to predict a beam configuration for the beam set A that leads to a signal quality that is higher than signal qualities due to other beam configurations. 14. The method of any one of the embodiments 12-13, wherein the selected one or more beams of the beam set B comprise: one or more synchronization signal block (SSB) beams; one or more narrow beams configured for channel state information (CSI) measurements; or one or more beams activated by a network. 15. The method of any one of embodiments 12-14, wherein the one or more beams of the beam set B is further selected based at least on: performance of a combination of the beam set A and beam set B; energy cost of the first and second measurements; a battery type of the UE; a service type; a target quality of service (QoS); a device type of the UE; estimated power savings for different omission patterns; or computational capability of the UE.
P110739WO01 PCT APPLICATION 52 of 62 16. The method of any of the embodiments 12-15, wherein the beam indication information is received within a channel state information (CSI) resource, wherein the CSI resource comprises one of: CSI-reportingConfig; CSI-resourceConfig; CSI-resourceSetList; CSI-ResourceList; or CSI-Resource. 17. The method of any of the embodiments 12-16, wherein each of the first and second consistency IDs comprises one of: consistency- non-zero-power channel state information reference signal (nzp-CSI-RS)- ResourceId; consistency-nzp-CSI-RS-ResourceSetId; consistency-csi-ReportConfigId,; or and consistency-csi-ResourceConfigId. 18. The method of any one of the embodiments 12-17, wherein receiving the beam indication information is in response to transmitting a first message indicating capability of the UE for training the beam prediction model. 19. The method of any one of the embodiments 12-18, further comprising: receiving a second message indicating capability of the UE in beam prediction; transmitting a second beam indication information regarding the two sets of beams; transmitting the first consistency ID associated with the beam set A; transmitting the second consistency ID associated with the beam set B; transmitting a third signal on the beam set B; receiving a measurement on the third signal; receiving a predicted beam from among the beam set A; and determining one or more preferred beam configurations based at least on user equipment (UE)-reported beam predictions. 20. The method of any of the previous embodiments, further comprising: obtaining user data; and
P110739WO01 PCT APPLICATION 53 of 62 forwarding the user data to a host or a user equipment. Group C Embodiments 21. A user equipment for implementing a beam prediction model in a wireless network, comprising: processing circuitry configured to perform any of the steps of any of the Group A embodiments; and power supply circuitry configured to supply power to the processing circuitry. 22. A network node for implementing a beam prediction model in a wireless network, the network node comprising: processing circuitry configured to perform any of the steps of any of the Group B embodiments; power supply circuitry configured to supply power to the processing circuitry. 23. A user equipment (UE) for implementing a beam prediction model in a wireless network, the UE comprising: an antenna configured to send and receive wireless signals; radio front-end circuitry connected to the antenna and to processing circuitry, and configured to condition signals communicated between the antenna and the processing circuitry; the processing circuitry being configured to perform any of the steps of any of the Group A embodiments; an input interface connected to the processing circuitry and configured to allow input of information into the UE to be processed by the processing circuitry; an output interface connected to the processing circuitry and configured to output information from the UE that has been processed by the processing circuitry; and a battery connected to the processing circuitry and configured to supply power to the UE.