Methods and apparatus for indicating additional beams to be reported

Abstract

A method performed by a User Equipment (UE) is provided. The method includes any one or more of: receiving a configuration from a first network node (910) for transmitting a beam report wherein the beam report includes information on M≥1 beam(s) received from a second network node or from the first network node, including in the beam report an indication of whether additional or remaining beam information is available to be reported in a future beam report wherein the additional or remaining beam information is different from the information on M≥1 beam(s) and transmitting the beam report to the first network node.

Description

METHODS AND APPARATUS FOR INDICATING ADDITIONAL BEAMS TO BEREPORTEDRELATED APPLICATIONS

[0001] This application claims the benefit of U.S. Provisional Patent Application No. 63 / 680,265, filed August 7, 2024, the disclosure of which is hereby incorporated herein by reference in its entirety.TECHNICAL FIELD

[0002] The present disclosure relates to a wireless (e.g., cellular) communications system and, more particularly, to methods and apparatus for indicating additional beams to be reported in a wireless communications system.BACKGROUND

[0003] Beam management

[0004] Beam management procedure

[0005] In high frequency range (FR2), multiple RF beams may be used to transmit and receive signals at a gNB and a UE. For each DL beam from a gNB, there is typically an associated best UE Rx beam for receiving signals from the DL beam. The DL beam and the associated UE Rx beam forms a beam pair. The beam pair can be identified through a so-called beam management process in NR.

[0006] A DL beam is (typically) identified by an associated DL reference signal (RS) transmitted in the beam, either periodically, semi-persistently, or aperiodically. The DL RS for the purpose can be a Synchronization Signal (SS) and Physical Broadcast Channel (PBCH) block (SSB) or a Channel State Information RS (CSI-RS). By measuring all the DL RSs, the UE can determine and report to the gNB the best DL beam to use for DL transmissions. The gNB can then transmit a burst of DL-RS using the reported best DL beam to let the UE evaluate candidate UE RX beams.

[0007] Although not explicitly stated in the NR specification, beam management has been divided into three procedures, schematically illustrated in Figure 1 :P-1 : Purpose is to find a coarse direction for the UE using wide gNB TX beam covering the whole angular sectorP-2: Purpose is to refine the gNB TX beam by doing a new beam search around the coarse direction found in Pl .P-3 : Used for UE that has analog beamforming to let the UE find a suitable UE RX beam.

[0008] P-1 is expected to utilize beams with rather large beamwidths and where the beam reference signals are transmitted periodically and are shared between all UEs of the cell. Typically reference signal to use for P-1 are periodic CSI-RS or SSB. The UE then reports the N best beams to the gNB and their corresponding RSRP values.

[0009] P-2 is expected to use aperiodic / or semi -persistent CSI-RS transmitted in narrow beams around the coarse direction found in P-1.

[0010] P-3 is expected to use aperiodic or semi-persistent CSI-RSs repeatedly transmitted in one narrow gNB beam. One alternative way is to let the UE determine a suitable UE RX beam based on the periodic SSB transmission. Since each SSB consists of four OFDM symbols, a maximum of four UE RX beams can be evaluated during each SSB burst transmission. One benefit with using SSB instead of CSI-RS is that no extra overhead of CSI-RS transmission is needed.

[0011] Reference signal

[0012] Reference signal configurations

[0013] CSI-RS:

[0014] A CSI-RS is transmitted over each transmit (Tx) antenna port at the network node and for different antenna ports. The CSI-RS are 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 can be measured by the UE. The time-frequency resource used for transmitting CSI-RS is referred to as a CSI-RS resource.

[0015] 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:

[0016] Periodic CSI-RS: CSI-RS is transmitted periodically in certain slots. This CSI-RS transmission is semi-statically configured using RRC signaling with parameters such as CSI- RS resource, periodicity, and slot offset.

[0017] Semi -Persistent CSI-RS: Similar to periodic CSI-RS, resources for semi-persistent CSI-RS transmissions are semi-statically configured using RRC signaling with parameters such as periodicity and slot offset. However, unlike periodic CSI-RS, dynamic signaling is needed to activate and deactivate the CSI-RS transmission.

[0018] Aperiodic CSI-RS: This is a one-shot CSI-RS transmission that can happen in any slot. Here, one-shot means that CSI-RS transmission only happens once per trigger. The CSI- RS resources (i.e., the RE locations which consist of subcarrier locations and OFDM symbollocations) 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 UL DCI, in the same DCI where the UL resources for the measurement report are scheduled. Multiple aperiodic CSI-RS resources can be included in a CSI-RS resource set and the triggering of aperiodic CSI-RS is on a resource set basis.

[0019] SSB:

[0020] In NR, an SSB consists of a pair of synchronization signals (SSs), physical broadcast channel (PBCH), and DMRS for PBCH. A SSB is mapped to 4 consecutive OFDM symbols in the time domain and 240 contiguous subcarriers (20 RBs) in the frequency domain.

[0021] To support beamforming and beam-sweeping for SSB transmission, in NR, a cell can transmit multiple SSBs in different narrow-beams in a time multiplexed fashion. The transmission of these 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 SIB1.

[0022] The maximum number of SSBs within a half frame, denoted by L, depends on the frequency band, and the time locations for these L candidate SSBs within a half frame depends on the SCS of the SSBs. The L candidate SSBs within a half frame are indexed in an ascending order in time from 0 to L-l. 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 un-used candidate positions can 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.

[0023] Measurement resource configurations

[0024] In NR, a UE can be configured with N>1 CSI reporting settings (i.e., alternatively referred to as CSI-ReportConfig), M>1 resource settings (i.e., alternatively referred to as CSL ResourceConfig), where each CSI reporting setting is linked to one or more resource setting for channel and / or interference measurement. The CSI framework is modular, meaning 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 IES CSI-ResourceConfigs. One CSI-ResourceConfig contains several NZP-CSI- RS-ResourceSets and / or CSI-SSB-ResourceSets.

[0026] A UE can be configured to perform measurement on CSI-RSs. Here the RRC information element (IE) NZP-CSI-RS-ResourceSet is used. A NZP CSI-RS resource set contains the configuration of Ks >1 CSI-RS resources, where the configuration of each CSI- RS resource includes at least: mapping to REs, the number of antenna ports, time-domain behavior, etc. Up to 64 CSI-RS resources can be grouped to a NZP-CSI-RS-ResourceSet. A UE can also be configured to perform measurements on SSBs. Here, the RRC IE CSI-SSB- ResourceSet is used. Resource sets comprising SSB resources are defined in a similar manner.

[0027] In the case of aperiodic CSI-RS and / or aperiodic CSI reporting, the network node configures the UE with ScCSI triggering states. Each triggering state contains the aperiodic CSI report setting to be triggered along with the associated aperiodic CSI-RS resource sets.

[0028] Periodic and semi -persistent Resource Settings can only comprise a single resource set (i.e. S=l) while S>=1 for aperiodic Resource Settings. This is because in the aperiodic case, one out of the S resource sets comprised in the Resource Setting is indicated by the aperiodic triggering state that triggers a CSI report.

[0029] The RRC IEs described above are defined in 3GPP 38.331 V18.0.0.

[0030] Measurement Reporting

[0031] Three types of CSI reporting are supported in NR as follows:

[0032] 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

[0033] Semi -Persistent CSI Reporting on PUSCH or PUCCH: similar to periodic CSI reporting, semi-persistent CSI reporting has a periodicity and slot offset which may be semi- statically configured. However, a dynamic trigger from network node to UE may be needed to allow the UE to begin semi-persistent CSI reporting. A dynamic trigger from network node to UE is needed to request the UE to stop the semi -persistent CSI reporting.

[0034] Aperiodic CSI Reporting on PUSCH: This type of CSI reporting involves a singleshot (i.e., one time) CSI report by a UE which is dynamically triggered by the network node using DCI. Some of the parameters related to the configuration of the aperiodic CSI report is semi-statically configured by RRC but the triggering is done dynamically via DCI.

[0035] 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. The CSI-ReportConfig l comprise the following configurations:• reportConfigTypeDefines the time-domain behavior, i.e. 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.• reportQuantityDefines the reported CSI parameter(s) (i.e. the CSI content), such as PMI, CQI, RI, LI (layer indicator), CRI (CSLRS resource index) and Ll-RSRP. Only a certain number of combinations are possible (e.g. ‘cri-RI-PMI-CQL is one possible value and ‘cri-RSRP’ is another) and each value of reportQuantity could be said to correspond to a certain CSI mode.• codebookConfigDefines the codebook used for PMI reporting, along with possible codebook subset restriction (CBSR). Two “Types” of PMI codebook are defined in NR, Type I CSI and Type II CSI, each codebook type further has two variants each.• reportFrequencyConfigurationDefine 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) which the CSI corresponds to• Measurement restriction in time domain (ON / OFF) for channel and interference respectively

[0036] For beam management, a UE can be configured to report Ll-RSRP for up to four different CSI-RS / SSB resource indicators. The reported RSRP value corresponding to the first (best) CRI / 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 Ll-SINR for beam management has already been supported.

[0037] AI / ML based spatial beam prediction in NR

[0038] During the 3 GPP meeting RANl#109-e it was agreed to study AI / ML based spatial beam prediction (BM Case 1) for a set A of beams based on measurement results of Set B of beams. The Set B of beams could either be a subset of the Set A of beams, or the set A of beams could consist of different beams compared to the Set B of beams (for example Set Aconsists of narrow beams and Set B consists of wide beams). The spatial beam prediction could either be made at the gNB side or at the UE side.

[0039] During the 3GPP meeting RANl#109-e it was also agreed to study AI / ML based temporal (BM case 2) beam prediction for a Set A of beams based on measurement results of Set B of beams, where the Set A of beams and Set B of beams can be the same set of beams or different set of beams. For AI / ML based temporal beam prediction, it was also agreed that the measurement results of K (K>=1) latest measurement instances during a time window T1 of the Set B beams are used for AI / ML model input. Furthermore, it was agreed that one or more beams from the Set A beams will be used as AI / ML model output, where the AI / ML model output should be F predictions for F future time instances, where all F future time instances are located within a time window T2.

[0040] During the 3GPP meeting RAN1#115, it was also agreed to capture the Figure 1A (referred to as Figure 8.3.7-7) and the associated description below of the two sub-use cases for providing a description of the BM use case as part of the technical report 38.843.

[0041] Figure 8.3.1-1 provides an example for the inference procedure for beam management for BM-Casel and BM-Case2. Measurements based on Set B of beams are used as model input. In addition, beam ID information may be also provided as input to the AI / ML model. Based on model output (e.g., probability of each beam in Set A to be the Top-1 beam, predicted Ll- RSRPs), Top-l / N beam(s) among Set A of beams can be predicted and / or potentially with predicted Ll-RSRPs (depending on the labeling). In the evaluation, for BM-Case 1, the measurements of Set B (otherwise stated) are used as model input to predict Top-l / N beams from Set A, and for BM-Case2, the measurements from historic time instance(s) are used as model input for temporal DL beam prediction of beams from Set A. In the evaluation, the cases that Set A and Set B are different (Set B is NOT a subset of Set A), and Set B is a subset of Set A for both BM-Casel and BM-Case2, and case that Set A and Set B are the same for BM- Case 2 are considered. And the performance of DL Tx beam prediction and DL Tx-Rx beam pair prediction is evaluated.

[0042] For both BM-Casel and BM-Case 2, UE can report the prediction result to gNB based on the output of a UE-side model, or gNB can predict the Top-l / N beam(s) based on the reported measurements.

[0043] It is noted that as beam is something that is formed on the NW side the UE can only measure the result of this. This can for example be that the narrow beams are measured by CSLRS resources and the wide beams are measured by SSBs at the UE side. This would be how the UE could see the beams.

[0044] Set B is different from Set A

[0045] Figure 2 illustrates a schematic example of the Set A of beams and the Set B of beams. The top illustration shows all the narrow gNB beams, which constitutes the Set A of beams, and the lower illustrations shows all the wide gNB beams, which constitutes the Set B of beams.

[0046] Set B is a subset of Set A

[0047] Figure 3 illustrates another example of the Set A of beams and the Set B of beams, wherein Set A contains narrow gNB beams and set B is subset of Set A containing some narrows beams from the gNB.

[0048] Rel-19 status

[0049] In RAN1#116, it was decided that the UE can report Top-K beams to the NW, according to the agreement below. It is for further study the exact number of K.

[0050] Agreement• For UE-sided model, at least for BM-Casel, for content in the report of inference results, support• Opt 1 : Beam information on predicted Top K beam(s) among a set of beams• Opt 2: Beam information on predicted Top K beam(s) among a set of beams and RSRP of predicted Top K beam(s) among a set of beams• At least K=1 and more, FFS on max value• FFS on beam information• FFS on the definition of predicted Top K beam(s)• FFS on definition of reported RSRP when applicable• FFS on other information in the report with potential down selection among the following options o Opt 3: Beam information on predicted Top K beam(s) among a set of beams and probability information of predicted Top K beam(s) among a set of beams■ FFS on the quantization method of probability information■ Probability information is the probability of the beam to be the Top 1 or Top K beam o Opt 4: Beam information on predicted Top K beam(s) among a set of beams, RSRP of predicted Top K beam(s) among a set of beams, and confidence information of the RSRPFFS on definition of reported RSRPFFS on the definition and quantization method of confidence informationOther options are not precluded.

[0051] UE-initiated / event-driven beam management

[0052] Prior to NR Rel-19, beam reporting is always NW -initiated, i.e., the NW explicitly requests a beam report from the UE by indicating a CSI report configuration in DCI.

[0053] In NR Rel-19, UE initiated beam reporting will be supported in which a UE keeps monitoring the quality of a set of DL beams or associated reference signals and sends a beam report when conditions associated to one or more events are met. The possible events can be one or more of:• Event- 1 : Quality of the current beam is worse than a certain threshold.• Event-3 : Quality of a new beam is better than a certain threshold.• Event-4: Quality of the current beam is worse than a threshold 1, and quality of at least one new beam is better than a threshold 2.• Event-5: Absolute value of the difference between the quality of the current beam and the quality of at least one new beam is lower than a threshold.• Event-6: When the current beam is not in the best K>1 beams (out of configured beams for measurement and reporting).• Event-7a: Quality of at least one new beam, such as Ll-RSRP, becomes a threshold value better than the RS derived from the activated TCI state with the worst quality.• Event- 7b: Quality of at least one new beam, such as Ll-RSRP, becomes a threshold value better than the RS derived from the activated TCI state with the best quality.• Event-8: Quality of M>1 new beams, such as Ll-RSRP, become a threshold value better than the current beam.• Event-9: Quality of at least one new beam, such as Ll-RSRP, becomes a threshold value better than the configured reference RS (can be SSB or CSI-RS).

[0054] Event-2 was agreed to be supported in Rel-19. Additional events may also be supported. Regarding the triggering event determination for Event 2, it is also agreed that

[0055] Basic feature: once the Ll-RSRP of the new beam becomes a threshold value better than the current beam, UE initiated beam report occurs.

[0056] Based on the UE capability, UE can be configured with a time window where the number of Event-2 instance(s) for at least one same new beam is greater than or equal to a configurable number M, UE initiated beam report occurs.SUMMARY

[0057] According to one aspect, a method at a User Equipment (UE) is provided. The method includes receiving a configuration from a first network node for transmitting a beam report wherein the beam report includes information on > l beam(s) received from a second network node or the first network node, including in the beam report an indication of whether additional or remaining beam information is available to be reported in a future beam report wherein the additional or remaining beam information is different from the information on M> beam(s) and transmitting the beam report to the first network node.

[0058] Additionally, the configuration may include at least one of a maximum number Mmax of beams reported in a single beam report wherein M >1 beam(s).

[0059] Additionally or alternatively, a maximum number Zm x of beams may be reported over multiple consecutive beam reports wherein M< Mmax.

[0060] Additionally or alternatively, the maximum number of multiple consecutive beam reports may be configured as part of the configuration or predefined in specifications.

[0061] Additionally or alternatively, the information on MM beam(s) may includes any one or more of- identifiers of a first set of M> 1 reference signal(s) on which measurement s) corresponding to the MM beam(s) are performed;- layer 1 RSRP(s) based on measurements on the first set of MM reference signal(s);- layer 1 SINR(s) based on measurements on the first set of MM reference signal(s);- identified s) of associated event(s); and / or- an index for identifying a beam report among multiple consecutive beam reports;

[0062] Additionally or alternatively, the first set of M> l reference signal(s) may be a subset of a second set of reference signal(s).

[0063] Additionally or alternatively, the information on M> l beam(s) may include any one or more of- identifiers of MM beams(s) predicted based on measurements on a third set of reference signal(s);- predicted layer 1 RSRP(s) corresponding to the MM beams(s) based on measurements on the third set of reference signal(s);- predicted layer 1 SINR(s) based on measurements on the third set of reference signal(s);- identified s) of associated event(s); and / or- an index for identifying a beam report among multiple consecutive beam reports;

[0064] Additionally or alternatively, the indication of whether additional or remaining beam information may be available to be reported in a future beam report is a binary bit.

[0065] Additionally or alternatively, the binary bit set to a first value may indicate that there is additional or remaining information available to be reported in a future beam report.

[0066] Additionally or alternatively, the indication of whether additional or remaining beam information is available to be reported in a future beam report may be an integer number which indicates a number T 1 of additional beams for which additional or remaining beam information is available.

[0067] Additionally or alternatively, a second beam report may be transmitted containing at least part of the available additional or remaining beam information.

[0068] Additionally or alternatively, the second beam report may further include updated indication of whether additional or remaining beam information is available to be reported in a future beam report

[0069] Additionally or alternatively, the second beam report may be transmitted to the gNB according to any of the following:• In response of receiving a request from the gNB• In the next configured transmission opportunity

[0070] Additionally or alternatively, the available or remaining additional beam information reported over the multiple consecutive beam reports may be associated to measurements performed in the same measurement occasions, measurement period, or measurement interval.

[0071] Additionally or alternatively, the beam report may further contain an indication indicating whether the information on A / >1 beam(s) included in the said beam report are associated to the available additional or remaining beam information as indicated in the previous beam report.

[0072] Additionally or alternatively, the second (or Nth wherein N>1) beam report among the multiple consecutive beam reports may include only beams not included in the first beam report (or first N-l beam reports, respectively).

[0073] Additionally or alternatively, information on a total of Mtotai beams may be reported in the first N beam reports and represent the Mtotai strongest beams.

[0074] Additionally or alternatively, the method may further comprise receiving from the first network node an indication that indicates whether a first, second, or Nth beam report should be transmitted to the first network node.

[0075] Additionally or alternatively, the indication may be carried in a DCI field in PDCCH triggering aperiodic CSI report.

[0076] Additionally or alternatively, the method may further comprise the receiving an indication from the first network node that indicates which subset of beams should be included in the beam report, based on their RSRP values or other link quality measure.

[0077] According to another aspect, a method for a network node is provided. The method comprises transmitting a configuration for transmitting a beam report wherein the beam report includes information on M>1 beam(s) received from a second network node or from the first network node and receiving the beam report from the user equipment, wherein the beam report includes an indication of whether additional or remaining beam information is available to be reported in a future beam report wherein the additional or remaining beam information is different from the information on M>1 beam(s). Additionally or alternatively, the method may include any one or more of the features noted for the user equipment method.BRIEF DESCRIPTION OF THE DRAWINGS

[0078] The accompanying drawing figures incorporated in and forming a part of this specification illustrate several aspects of the disclosure, and together with the description serve to explain the principles of the disclosure.

[0079] Figure 1 A illustrates an example of beam management procedure;

[0080] Figure IB illustrates Figure 8.3.1-1 proposed in the technical report 38.843 as proposed during the 3GPP meeting RAN1#115, which illustrates an example of the inference procedure for beam management;

[0081] Figure 2 illustrates a schematic example of Set A and Set B of beams, where Set B is different from Set A. Set B of beams are wide NW beams and the Set A of beams are the narrow gNB beams;

[0082] Figure 3 illustrates a schematic example of Set A and Set B of beams, where Set B is a subset of Set A of beams. Both Set B and Set A of beams are the narrow gNB beams;

[0083] Figure 6 illustrates is a flow chart that illustrates a process performed by a User Equipment (UE), in accordance with some embodiments of the present disclosure;

[0084] Figure 7 a flow chart that illustrates a process performed by a network node, in accordance with some embodiments of the present disclosure;

[0085] Figure 8 is a first example of indicating additional beam information to be reported;

[0086] Figure 7 is a second example of indicating additional beam information to be reported;

[0087] Figure 8 is a third example of indicating additional beam information to be reported;

[0088] Figure 9 shows an example of a communication system in accordance with some embodiments of the present disclosure;

[0089] Figure 10 shows a User Equipment device (UE) in accordance with some embodiments of the present disclosure;

[0090] Figure 11 shows a network node in accordance with some embodiments of the present disclosure;

[0091] Figure 12 is a block diagram of a host, which may be an embodiment of the host of Figure 9, in accordance with various aspects of the present disclosure described herein;

[0092] Figure 13 is a block diagram illustrating a virtualization environment in which functions implemented by some embodiments of the present disclosure may be virtualized; and

[0093] Figure 14 shows a communication diagram of a host communicating via a network node with a UE over a partially wireless connection in accordance with some embodiments of the present disclosure.DETAILED DESCRIPTION

[0094] The embodiments set forth below represent information to enable those skilled in the art to practice the embodiments and illustrate the best mode of practicing the embodiments. Upon reading the following description in light of the accompanying drawing figures, those skilled in the art will understand the concepts of the disclosure and will recognize applications of these concepts not particularly addressed herein. It should be understood that these concepts and applications fall within the scope of the disclosure.

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

[0096] There currently exist certain challenge(s). In the case when the AI / ML model for beam management is at the network, the network needs to collect data from the UE, for instance, for training the model. In this case, it is beneficial for the network to collect measurements on as many beams in the set A of beams as possible. However, when the total number M A of beams in the set A of beams is very large (e.g., in the order of hundreds of beams), it may not be feasible for the UE to include beam measurements for all M A beams in a single beam reporting instance as the feedback overhead for such a beam report will be very high. Hence, it is a problem on how to efficiently collect data from the UE for a network sided AI / ML model, when the total number M A of beams in the set A of beams is very large.

[0097] A similar problem occurs in UE initiated / event driven beam management when a large number of candidate beams are measured by the UE and when multiple candidate beams satisfyan event triggering criterial. Hence, it is a related problem on how to efficiently perform beam reporting from the UE to the network when a large number of candidate beams are measured by the UE and when multiple candidate beams satisfy an event triggering criterion.

[0098] Another related problem is how to report measurement results when the UE is requested to report measurements for only beams exceeding some specific threshold (e.g., only beams that are withing 10 dB of the strongest beam).

[0099] Certain aspects of the disclosure and their embodiments may provide solutions to these or other challenges. Solutions are proposed where the UE includes an indication of additional or remaining beam information in a current beam report wherein the additional or remaining beam information is different from the beam information included in the current beam report. The beam information includes one or more of L1-RSRP / L1-SINR measurements for a finite number of beams along with an indication of beam (e.g., a beam index) for each beam for which L1-RSRP / L1-RSRQ is reported. The additional or remaining beam information included along with beam information in the current beam report may include at least one of:• The number of additional beams to be reported in a future beam report• A binary indication of whether additional or remaining beam information is available to be reported in a future beam report.

[0100] Embodiments of the present disclosure relate to methods and apparatus for indicating beam reports.

[0101] Al. Referring to Figure 4, a method at a User Equipment (UE) comprises receiving (400) a configuration from a first network node for transmitting a beam report wherein the beam report includes information on A / > l beam(s) received from a second network node or the first network node, including (402) in the beam report an indication of whether additional or remaining beam information is available to be reported in a future beam report wherein the additional or remaining beam information is different from the information on M> beam(s) and transmitting (404) the beam report to the first network node.

[0102] A2. Additionally, in the method of Al, the configuration includes at least one of a maximum number Mmax of beams reported in a single beam report wherein M >1 beam(s).

[0103] A3. Additionally or alternatively, in the method of any of A1-A2, a maximum number Zmax of beams reported over multiple consecutive beam reports wherein M< Mmax.

[0104] A4. Additionally or alternatively, in the method of any of A1-A3, the maximum number of multiple consecutive beam reports is configured as part of the configuration or predefined in specifications.

[0105] A5. Additionally or alternatively, in the method of any of A1-A4, the information on A / >1 beam(s) includes any one or more of:- identifiers of a first set of M> 1 reference signal(s) on which measurement s) corresponding to the A / > l beam(s) are performed;- layer 1 RSRP(s) based on measurements on the first set ofA / >l reference signal(s);- layer 1 SINR(s) based on measurements on the first set of A / >1 reference signal(s);- identified s) of associated event(s); and / or- an index for identifying a beam report among multiple consecutive beam reports;

[0106] A5. Additionally or alternatively, in the method of A4, the first set of M> reference signal(s) is a subset of a second set of reference signal(s).

[0107] A6. Additionally or alternatively, in the method of any of A1-A4, the information on A / >1 beam(s) includes any one or more of:- identifiers of A / >1 beams(s) predicted based on measurements on a third set of reference signal(s);- predicted layer 1 RSRP(s) corresponding to the A / > l beams(s) based on measurements on the third set of reference signal(s);- predicted layer 1 SINR(s) based on measurements on the third set of reference signal(s);- identified s) of associated event(s); and / or- an index for identifying a beam report among multiple consecutive beam reports;

[0108] A7. Additionally or alternatively, in the method of any of A1-A6, the indication of whether additional or remaining beam information is available to be reported in a future beam report is a binary bit.

[0109] A8. Additionally or alternatively, in the method of A7, the binary bit set to a first value indicates that there is additional or remaining information available to be reported in a future beam report.

[0110] A9. Additionally or alternatively, in the method of any of A1-A6, the indication of whether additional or remaining beam information is available to be reported in a future beam report is an integer number which indicates a number l of additional beams for which additional or remaining beam information is available.[OHl] A10. Additionally or alternatively, in the method of any of A1-A9, a second beam report is transmitted containing at least part of the available additional or remaining beam information.

[0112] Al l. Additionally or alternatively, in the method of A10, wherein the second beam report further includes updated indication of whether additional or remaining beam information is available to be reported in a future beam report

[0113] A12. Additionally or alternatively, in the method of A10, wherein the second beam report is transmitted to the gNB according to any of the following:• In response of receiving a request from the gNB• In the next configured transmission opportunity

[0114] A13. Additionally or alternatively, in the method of any of A1-A12, the available or remaining additional beam information reported over the multiple consecutive beam reports are associated to measurements performed in the same measurement occasions, measurement period, or measurement interval.

[0115] A14. Additionally or alternatively, in the method of any of A1-A13, the beam report further contains an indication indicating whether the information on A / > l beam(s) included in the said beam report are associated to the available additional or remaining beam information as indicated in the previous beam report.

[0116] A15. Additionally or alternatively, in the method of any of A1-A14, the second (or Nth wherein N>1) beam report among the multiple consecutive beam reports includes only beams not included in the first beam report (or first N-l beam reports, respectively).

[0117] Al 6. Additionally or alternatively, in the method of Al 5, information on a total of Mtotai beams are reported in the first N beam reports and represent the Mtotai strongest beams.

[0118] A17. Additionally or alternatively, the method of any of A1-A16, further comprises receiving from the first network node an indication that indicates whether a first, second, or Nth beam report should be transmitted to the first network node.

[0119] A18. Additionally or alternatively, in the method of A17, the indication is carried in a DCI field in PDCCH triggering aperiodic CSI report.

[0120] Al 9. Additionally or alternatively, the method of any of Al -Al 8 further comprises the receiving an indication from the first network node that indicates which subset of beams should be included in the beam report, based on their RSRP values or other link quality measure.

[0121] A20. Referring to Figure 5, a method for a network node comprises transmitting (500) a configuration for transmitting a beam report wherein the beam report includes information on M>1 beam(s) received from a second network node or from the first network node and receiving (502) the beam report from the user equipment, wherein the beam report includes an indication of whether additional or remaining beam information is available to be reported in a future beam report wherein the additional or remaining beam information is different fromthe information on M>1 beam(s). Additionally or alternatively, the method may include any one or more of the features noted for A2-19.

[0122] Beams in the above may refer to beams of a cell, RSs, SSBs, spatial filters, CSI-RS, serving cell, neighbor cell, candidate cell, etc.

[0123] The beam report may correspond to a Channel State Information (CSI) report / UCI which includes at least one beam identifier (e.g. an SSB index, a CSI-RS resource identifier, an SSB resource indicator associated to an instance of a resource configuration and an SSB index of a serving cell, an SSB resource indicator associated to an instance of a resource configuration and an SSB index of a neighbor cell, a CSI-RS resource indicator associated to an instance of a resource configuration). In some embodiments, the beam report may include at least one measured beam information (e.g., a measured value of layer 1 RSRP, Ll-RSRP, or a measured value of layer 1 SINR, Ll-SINR). In some other embodiments, the beam report may include at least one predicted beam information (e.g., a predicted value of layer 1 RSRP, Ll-RSRP, or a predicted value of layer 1 SINR, Ll-SINR).

[0124] Certain embodiments may provide one or more of the following technical advantage(s). A significant advantage is that the overhead of reporting a single beam reporting instance is limited to a manageable level. When a UE has a large total number of beams for which to report beam information, the proposed mechanisms let the gNB (or network node) collect the measurements by splitting the large total number of beams into multiple beam reporting instances.

[0125] Now, a more detailed description of embodiments of the present disclosure will be provided.

[0126] Although the terms ‘ Set A beams’ and ‘ Set B beams’ are used in this disclosure, these terms may not necessarily be captured in 3 GPP specifications. Alternative terminologies such as ‘first beams set’, ‘first spatial filters set’, ‘first measured set of reference signals (RSs)’, ‘first measured set of Synchronization Signal Block(s) (SSBs)’, or ‘first measured set of CSI- RS(s)’ may be used in place of ‘Set A beams’. Similarly, terms such as ‘second beams set’, ‘second spatial filters set’, ‘second measured set of reference signals (RSs)’, ‘second measured set of Synchronization Signal Block(s) (SSBs)’, or ‘second measured set of CSLRS(s)’ may be used in place of ‘Set B beams’. Other terms, not including the words “first” or “second”, are also possible. The term ‘beams’ is used throughout the disclosure; alternative terminologies such as ‘spatial filters’, ‘reference signals’, ‘SSBs’, or ‘CSI-RS resources’ may be used in place of ‘beams’.

[0127] Embodiments for Beam reporting for network sided AI / ML model

[0128] The UE receives configuration from the gNB of at least one set of reference signals. In one embodiment, the at least one set of reference signals is used for measuring a set A of beams, where each reference signal in the at least one set of reference signals corresponds to one beam in the set A of beams. The at least one set of reference signals can be either a set of SSBs or a set of NZP CSI-RSs. The total number of beams in the set A of beams is denoted as MA.

[0129] In the case when the AI / ML model for beam management is at the network, the network needs to collect data from the UE, for instance, for training the model. In this case, it is beneficial for the network to collect measurements on as many beams in the set A of beams as possible. However, when the total number MAof beams in the set A of beams is very large (e.g., in the order of hundreds of beams), it may not be feasible for the UE to include beam measurements for all MAbeams in a single beam reporting instance as the feedback overhead for such a beam report will be very high.

[0130] Additionally or alternatively, the UE receives signaling for reporting beam information for up to M beams in one beam reporting instance where M < MAis received by the UE from the gNB via higher layer signaling (e.g., RRC configuration). The value of M may be chosen such that the overhead of a single beam reporting instance is kept to a reasonable level.

[0131] Additionally or alternatively, Nburstbeam reporting instances comprise a beam reporting burst. Additionally or alternatively, the UE reports the number Nburstassociated with the beam reporting burst as part of the first beam report of the beam reporting burst. Additionally or alternatively, the UE reports the supported values of the number Nburstof beam reporting instances within a beam reporting burst as part of UE capability report to the gNB.

[0132] Within one beam reporting burst, it is up to the gNB to decide whether to request reporting of remaining or additional beam reporting instances. The starting time of the beam reporting burst is associated with one or multiple the following:• UE receiving an aperiodic report triggering from the gNB if the first beam reporting instance is aperiodically triggered;• UL transmission of the first beam reporting instance on PUSCH or PUCCH;• Reception of the last DL reference signal, i.e. SSB or CSI-RS that triggers the event in case the first beam reporting instance is triggered by an event.

[0133] Additionally or alternatively, the total number of beams for which beam information may be reported over one or more beam reporting instances may be determined at the UEaccording to a criterion. Let MRdenote the total number of beams for which beam information may be reported over one or more beam reporting instances where typically M < MR< MA. The UE may determine MRaccording to at least one of the following criteria:1) MRis determined as the number of beams among the measured MAbeams in set A of beams which are within a thresholdof the best beam. For instance, if the measured quantity is Ll-RSRP and the best beam among the measured MAbeams in set A of beams has an Ll-RSRP of A, then MRis determined as the number of beams among the set A of beams whose measured Ll-RSRP is higher than A — Vj-h .2) MRis determined as the number of beams among the measured MAbeams in set A of beams whose measured quantity is higher than a threshold VTh 2. For instance, if the measured quantity is Ll-RSRP, then MRis determined as the number of beams among the set A of beams whose measured Ll-RSRP is higher than VTh 2.3) MRis determined as the number of beams among the set A of beams (i.e., the MAbeams) that can be measured. This criterion can, for example, be used if none of the above said threshold is configured by the gNB.4) MRis determined as the number of beams that are hearable (i.e., above a certain Ll-RSRP), and have a unique QCL relation. That is, the number MRis the number of unique QCL sources the UE can detect. For example, consider the scenario where the gNB would like to only get the strongest narrow beam within each wide beam where the narrow beams within each wide beam share the same QCL source. In this scenario, the gNB configures the UE to report the strongest beam that share the same QCL source. For example, the UE reports the measurements for the strongest narrow beam within each wide beam. In this scenario, MRare the number of wide beams (i.e., the number of unique QCL sources).

[0134] Additionally or alternatively, the thresholds VTh lor VTh 2may be configured by the gNB to the UE. Alternatively, the thresholds VTh lor VTh 2may be predefined in 3 GPP standards. In another alternative embodiment, the thresholds VTh lor VTh 2may be left up to UE implementation.

[0135] Additionally or alternatively, the value of M is pre-configured to the UE by the gNB or predefined according to 3 GPP specifications. In a further embodiment, the gNB may configure the number Nburstof beam reporting instances within a beam reporting burst via higher layer configuration. Additionally or alternatively, MRis determined at the UE as M x Nburst.

[0136] Once the UE determines the total number MRof beams for which beam information may be reported, the UE receives one or more trigger(s) from the gNB to report one or more beam reporting instance(s) wherein each beam reporting instance carries beam information for M beams. Once the UE receives a trigger from the gNB, the UE reports a beam reporting instance carrying beam information for M beams. Furthermore, as part of the beam reporting instance, the UE includes an indication of whether additional beam information is available to be reported in a future beam reporting instance wherein the additional beam information is different from the beam information for the M beams carried in the current or any previous beam reporting instance. The indication of whether additional beam information is available to be reported in a future beam reporting instance can, for example, be in one of the following forms:• Additionally or alternatively, the UE includes a flag that indicates whether additional beam information is available to be reported in a future beam reporting instance. When the flag is set to a first value, the UE has additional beam information to be reported in a future beam reporting instance. When the flag is set to a second value, the UE does not have additional beam information to be reported in a future beam reporting instance. In one embodiment, the flag is set to a second value if all the available additional beam information are associated to measurements on configured beams in set A of beams that were not detected by the UE.• Additionally or alternatively, the UE includes a number additional beams for which beam information is available to be reported in a future beam reporting instance.• Additionally or alternatively, the current beam reporting instance includes total number of beams or total number of beam report instances associated with the beam reporting burst.• Additionally or alternatively, the current beam reporting instance includes an indication of the index associated with the current beam reporting instance within the beam reporting bursts. For instance, if the current beam reporting instance is the nth(n = 1,2, ...,Nburst) beam reporting instance within the beam reporting burst, then an indication of i is included in the current beam reporting instance.

[0137] Additionally or alternatively, the index of the beam reporting instance within a beam reporting burst is indicated in each beam reporting instance.

[0138] Additionally or alternatively, the remaining number of beam reporting instances within a beam reporting burst is indicated in each beam reporting instance.

[0139] Figure 6 shows a first example of indicating additional beam information available to be reported in a future beam reporting instance. The number of beams in set A of beams is assumed to be MA= 16 in this example for simplicity (although the value of MAwill typically be much larger). The number of beams for which beam information is to be reported in a beam reporting instance is M = 4. The measured Ll-RSRPs for the MAbeams in set A are shown in the leftmost table of Figure 6. (note that examples of beam index include CSI-RS resource indicator / index, CRI, or SSB resource indicator / index, SSBRI). As seen in the figure, the best beam among the MAbeams in set A is the beam with beam index 6 which has a measured Ll- RSRP of -49 dBm. The UE determines a total of MR= 8 beams for which beam information is to be reported. The MR= 8 beams may be determined, for example, as the beams which have a measured Ll-RSRP that is higher than a threshold of VTh 2= —100 dBm. UE then receives a trigger for a 1stbeam reporting instance from the gNB. In response to the trigger, the UE reports the first reporting instance whose reporting content is shown highlighted on a background with slanted stripes in Figure 6. The following content is reported as part of the 1stbeam reporting instance by the UE to the gNB:• beam indices 6, 3, 1, and 9 which may be given in the form of either CRI or SSBRI;• Ll-RSRPs corresponding to beam indices 6, 3, 1, and 9, respectively. In some cases, the Ll-RSRPs are reported as absolute values. In some other cases, the first Ll-RSRP (i.e., the one corresponding to beam index 6) is reported as absolute value while the remaining Ll-RSRPs are reported as differential values with respect to the first Ll-RSRP reported;• ‘ additional beam info’ set to a value of ‘ 1 ’ . Since the UE has beam information for MR= 8 total beams to report and only reports beam information for M = 4 beams in the 1stbeam reporting instance, the ‘additional beam info’ is set to a value of ‘ 1’ . The ‘additional beam info’ field / flag being set to a value of ‘ 1’ indicates to the gNB that the UE has additional beams for which it has beam information to report in future beam reporting instances.

[0140] UE then receives a trigger for a 2ndbeam reporting instance from the gNB. In response to the trigger, the UE reports the 2ndreporting instance whose reporting content is shown highlighted on a background with vertical stripes in Figure 6. The following content is reported as part of the 2ndbeam reporting instance by the UE to the gNB:• beam indices 8, 12, 15, and 14 which may be given in the form of either CRI or SSBRI;• Ll-RSRPs corresponding to beam indices 8, 12, 15, and 14, respectively. In some cases, the Ll-RSRPs are reported as absolute values. In some other cases, the first Ll-RSRP (i.e., the one corresponding to beam index 8) is reported as absolute value while the remaining Ll-RSRPs are reported as differential values with respect to the first Ll-RSRP reported;• ‘additional beam info’ set to a value of ‘0’ . Since MR= 8, and the UE has reported beam information for 4 beams in the 1stbeam reporting instance and has included beam information for another 4 beams in the 2ndbeam reporting instance, the ‘additional beam info’ is set to a value of ‘O’. The ‘additional beam info’ field / flag being set to a value of ‘0’ indicates to the gNB that the UE does not have additional beams for which it has beam information to report in future beam reporting instances.

[0141] Figure 7 shows a second example of indicating additional beam information available to be reported in a future beam reporting instance. This example is similar to the one in Figure 6 except that the format of indicating whether additional beam information is available for reporting in future beam reporting instances is different.

[0142] In the 1stbeam reporting instance, the UE indicates ‘Number of additional beams = 4’ . Since the UE has beam information for MR= 8 total beams to report and only reports beam information for M = 4 beams in the 1stbeam reporting instance, the ‘Number of additional beams’ is set to a value of ‘4’. This indicates to the gNB that the UE has 4 additional beams for which it has beam information to report in future beam reporting instances.

[0143] In the 2ndbeam reporting instance, the UE indicates ‘Number of additional beams = O’. Since MR= 8, and the UE has reported beam information for 4 beams in the 1stbeam reporting instance and has included beam information for another 4 beams in the 2ndbeam reporting instance, the ‘Number of additional beams’ is set to a value of ‘O’. This indicates to the gNB that the UE does not have additional beams for which it has beam information to report in future beam reporting instances.

[0144] Additionally or alternatively, in the nth(n = 1, . .., Nburst) beam reporting instance, the UE must only base the information on reported beams and values based on measurements that were available to the UE already when preparing the first beam reporting instance. This can ensure that information on the reported beams and values are consistent (i.e., based on measurements that are made in close proximity in time).

[0145] Additionally or alternatively, in the nth(n = 1, . .., Nburst) beam reporting instance, the UE may also report information of beams and values that are based on measurements performed after the first beam reporting instance. In some embodiments, the UE report beam related information such that the link quality (e.g. RSRP strength) decreases from one beam reporting instance to the next.

[0146] Figure 8 illustrates yet another example of reporting two beam reporting instances within a beam reporting burst. In this example, the total number of beam reporting instances within a beam reporting burst is reported as two (i.e., Nburst= 2). In some cases, the indexof the beam reporting instance within the beam reporting burst is also included in each beam reporting instance as shown in Figure 8.

[0147] Methods for triggering a beam report, and for UE actions in the absence of a trigger

[0148] In one method, the first beam reporting instance is transmitted periodically, or in response of a gNB trigger, or in response of one or more events being triggered at the UE side. In one method, the second beam reporting instance (or any successive beam reporting instances) is transmitted in response of receiving a gNB trigger based on the additional beam information included in the previous beam reporting instance(s). In another method, the second beam reporting instance (or any successive beam reporting instances) is transmitted in any successive uplink transmission occasions without a gNB trigger. Additionally or alternatively, the gNB may configure the UE to transmit any successive beam reporting instances in any successive uplink transmission occasions with a certain priority.

[0149] Additionally or alternatively, in response of not receiving any trigger for the transmission of the successive beam reporting instance(s), the UE discards the available beam information to be transmitted in the successive beam reporting instance(s). For example, if within a certain time after the transmission of a beam reporting instance indicating the availability of additional beam information, no trigger is received from the gNB, the UE discards such additional beam information. Alternatively, if at the time of performing a new beam level measurement, the UE still has additional beam information associated to previous beam level measurements which have not been yet transmitted to the gNB, the UE discards such additional beam information at the time of performing the new beam level measurement.

[0150] Additionally or alternatively, the gNB can, when triggering a beam reporting instance, indicate whether a first beam reporting instance or a successive beam reporting instance (or both, e.g. according to aforementioned methods) should be reported by the UE. In some embodiments, the trigger just includes a flag indicating whether the last reported beam reporting instance should be resent or if a new beam reporting instance should be reported.

[0151] Additionally or alternatively, the gNB can indicate which subset of beams should be reported based on the RSRP strengths (or other link quality measure(s)) of one or more of the MRbeams. For example, if the MRbeam indices in order of decreasing quality (e.g. RSRP strength) are b4, b2, b3, b4, bMR, the gNB could indicate that a specific beam reporting instance should include M beams starting at beam bN, i.e. report RSRP for beams bN, bN+1, bN+M-4. In some embodiments, the value of N is directly indicated in the report trigger. In some other embodiments, to reduce signaling overhead, the value of N may be more efficiently or indirectly / implicitly encoded, e.g. it could be specified that N should be determined by theUE as N = n ■ M, where n (which is a smaller number than N and hence can be encoded with fewer bits) is signaled by the gNB.

[0152] Additionally or alternatively, the gNB can indicate one or more beam reporting instances to be transmitted with one indication field in DCI. The beam reporting instances can be transmitted in one PUSCH transmission within a slot or multiple PUSCH transmissions in multiple slots.

[0153] UE initiated / event driven beam reporting

[0154] The UE receives configuration from the gNB of at least one set of candidate reference signals. Additionally or alternatively t, the at least one set of candidate reference signals is used for measuring a set candidate beams, where each reference signal in the at least one set of reference signals corresponds to one candidate beam. The at least one set of reference signals can be either a set of SSBs or a set of NZP CSI-RSs. The total number of candidate beams is denoted as Mc.

[0155] In addition to the candidate beams, the UE may also perform measurements on a serving / current beam. The reference signal for the serving / current beam may be defined as the Type-D QCL source RS corresponding to the indicated TCI state. Alternatively, the reference signal for the serving / current beam may be defined as the SSB which is QCLed with the Type- D QCL source RS corresponding to the indicated TCI state.

[0156] In the case when UE initiated / event driven beam reporting, each reporting configuration may be associated with an event. When the event is triggered, the UE initiates the beam reporting process. For instance, when an event associated with the reporting configuration is triggered, the UE may first send an indication (e.g., via a SR) to the gNB. The gNB may then sends a trigger (e.g., via a DCI) for a beam reporting instance. The UE then sends the beam reporting instance.

[0157] One event that may be defined is that at least one candidate beams measured quantity (e.g., Ll-RSRP) becomes a threshold value VTh 3better than the measured quantity (e.g., Ll- RSRP) of the serving / current beam. In some embodiments, the threshold VTh 3may be configured by the gNB to the UE. Alternatively, the threshold VTh 3may be predefined in 3 GPP standards. In another alternative embodiment, the thresholds VTh 3.

[0158] Additionally or alternatively, the UE receives signaling for reporting beam information for up to M beams in one beam reporting instance where M < Mcis received by the UE from the gNB via higher layer signaling (e.g., RRC configuration).

[0159] Additionally or alternatively s, the total number of beams for which beam information may be reported over one or more beam reporting instances may be determined at the UEaccording to how many candidate beams satisfy the event associated with the reporting configuration. Let MRdenote the total number of beams for which beam information may be reported over one or more beam reporting instances where typically M < MR< Mc. The UE may determine MRaccording to the following criterion:MRis determined as the number of beams among the measured Mccandidate beams whose measured quantity (e.g., Ll-RSRPs) are a threshold of VTh 3better than the measured quantity (e.g., Ll-RSRP) of the current / serving beam.

[0160] Once the UE determines the total number MRof beams for which beam information may be reported, the UE receives one or more trigger(s) from the gNB to report one or more beam reporting instance(s) wherein each beam reporting instance carries beam information for M beams. Once the UE receives a trigger from the gNB, the UE reports a beam reporting instance carrying beam information for M beams. Furthermore, as part of the beam reporting instance, the UE includes an indication of whether additional beam information is available to be reported in a future beam reporting instance wherein the additional beam information is different from the beam information for the M beams carried in the current or any previous beam reporting instance. The indication of whether additional beam information is available to be reported in a future beam reporting instance can, for example, be in one of the following forms:• in one embodiment, the UE includes a flag that indicates whether additional beam information is available to be reported in a future beam reporting instance. When the flag is set to a first value, the UE has additional beam information to be reported in a future beam reporting instance. When the flag is set to a second value, the UE does not have additional beam information to be reported in a future beam reporting instance.• in another embodiment, the UE includes a number additional beams for which beam information is available to be reported in a future beam reporting instance.

[0161] As in the previous embodiment, the first beam reporting instance can be initiated by the UE, e.g., in response to an event, whereas the second beam reporting instance (or any successive beam reporting instances) is transmitted in response to receiving a gNB trigger. In another method, the second beam reporting instance (or any successive beam reporting instances) is transmitted in any successive uplink transmission occasion without a gNB trigger.

[0162] Beam reporting for UE-sided AI / ML model

[0163] The UE receives configuration from the gNB of at least one set of beams from which the UE is to predict a subset of beams. In one embodiment, the one set of beams comprises of set A of beams, where set A is defined as a set of an NZP CSLRS resources. Alternatively, setA can be a set of SSBs. The total number of beams in the set A of beams is denoted as MApred. The subset of beams predicted from the set A of beams can also be in respect to a future time instance (this is called temporal beam prediction in 3GPP Rel-19 discussions).

[0164] The UE is requested by the gNB to report the top-K predicted beams from set A of beams. The UE might however have a larger number of beams than K that have high likelihood of being the strongest beam. The gNB can hence benefit by receiving more than K beams from the UE.

[0165] Additionally or alternatively, the UE receives signaling for reporting predicted beam information for up to K beams in one beam reporting instance where K < MApredis received by the UE from the gNB via higher layer signaling (e.g., RRC configuration). The value of K may be chosen such that the overhead of a single beam reporting instance is kept to a reasonable level.

[0166] Additionally or alternatively, the total number of beams for which beam information may be reported over one or more beam reporting instances may be determined at the UE according to a criterion. Let MRpreddenote the total number of beams for which beam information may be reported over one or more beam reporting instances where typically K < MRpred< MApred. The UE may determine MRpredaccording to one of the following criteria:1)Rpred is determined as the number of beams among the predicted MApredbeams in set A which are the best beams in set A with a certain probability p. For example, MRpredmay be determined as the number of beams that has more than 10% chance of being the strongest beam.2) MRpredis determined as the number of beams among the predicted MApredbeams in set A which are within a threshold of VTh lof the best beam. For instance, if the predicted quantity is Ll-RSRP and the best beam among the measured MApredbeams in set A has an Ll-RSRP of A, then MRpredis determined as the number of beams whose predicted Ll- RSRP is higher than A — 1 / 77^.3) MRpredis determined as the number of beams among the predicted MApredbeams in set A whose measured quantity is higher than a threshold VTh 2. For instance, if the predicted quantity is Ll-RSRP, then MRpredis determined as the number of beams whose predicted Ll-RSRP is higher than VTh 2.

[0167] Additionally or alternatively, the thresholds p, VTh lor VTh 2may be configured by the gNB to the UE. Alternatively, the thresholds p, VTh lor VTh 2may be predefined in 3 GPPstandards. Additionally or alternatively, the thresholds p, VTh lor VTh 2may be left up to UE implementation.

[0168] Once the UE determines the total number MRpredof beams for which beam information may be reported, the UE receives one or more trigger(s) from the gNB to report one or more beam reporting instance(s) wherein each beam reporting instance carries beam information for K beams. Once the UE receives a trigger from the gNB, the UE reports a beam reporting instance carrying beam information for K beams. Furthermore, as part of the beam reporting instance, the UE includes an indication of whether additional beam information is available to be reported in a future beam reporting instance wherein the additional beam information is different from the beam information for the K beams carried in the current or any previous beam reporting instance. The indication of whether additional beam information is available to be reported in a future beam reporting instance can, for example, be in one of the following forms:• the UE includes a flag that indicates whether additional beam information is available to be reported in a future beam reporting instance. When the flag is set to a first value, the UE has additional beam information to be reported in a future beam reporting instance. When the flag is set to a second value, the UE does not have additional beam information to be reported in a future beam reporting instance.• the UE includes a number additional beams for which beam information is available to be reported in a future beam reporting instance.

[0169] It is noted that the above-mentioned methods could also be applied to the beam reporting (measurement and / or inference results) for performance monitoring for both NW- sided and UE-sided AI / ML models.

[0170] Figure 9 shows an example of a communication system 900 in which embodiments of the present disclosure may be implemented.

[0171] In the example, the communication system 900 includes a telecommunication network 902 that includes an access network 904, such as a Radio Access Network (RAN), and a core network 906, which includes one or more core network nodes 908. The access network 904 includes one or more access network nodes, such as network nodes 910A and 910B (one or more of which may be generally referred to as network nodes 910), or any other similar Third Generation Partnership Project (3 GPP) access nodes or non-3GPP Access Points (APs). Moreover, as will be appreciated by those of skill in the art, a network node is not necessarily limited to an implementation in which a radio portion and a baseband portion are supplied and integrated by a single vendor. Thus, it will be understood that network nodes includedisaggregated implementations or portions thereof. For example, in some embodiments, the telecommunication network 902 includes one or more Open-RAN (ORAN) network nodes. An ORAN network node is a node in the telecommunication network 902 that supports an ORAN specification (e.g., a specification published by the O-RAN Alliance, or any similar organization) and may operate alone or together with other nodes to implement one or more functionalities of any node in the telecommunication network 902, including one or more network nodes 910 and / or core network nodes 908.

[0172] Examples of an ORAN network node include an Open Radio Unit (O-RU), an Open Distributed Unit (O-DU), an Open Central Unit (O-CU), including an O-CU Control Plane (O- CU-CP) or an O-CU User Plane (O-CU-UP), a RAN intelligent controller (near-real time or non-real time) hosting software or software plug-ins, such as a near-real time control application (e.g., xApp) or a non-real time control application (e.g., rApp), or any combination thereof (the adjective “open” designating support of an ORAN specification). The network node may support a specification by, for example, supporting an interface defined by the ORAN specification, such as an Al, Fl, Wl, El, E2, X2, Xn interface, an open fronthaul user plane interface, or an open fronthaul management plane interface. Moreover, an ORAN access node may be a logical node in a physical node. Furthermore, an ORAN network node may be implemented in a virtualization environment (described further below) in which one or more network functions are virtualized. For example, the virtualization environment may include an O-Cloud computing platform orchestrated by a Service Management and Orchestration Framework via an O-2 interface defined by the O-RAN Alliance or comparable technologies. The network nodes 910 facilitate direct or indirect connection of User Equipment (UE), such as by connecting UEs 912A, 912B, 912C, and 912D (one or more of which may be generally referred to as UEs 912) to the core network 906 over one or more wireless connections.

[0173] 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 900 may include any number of wired or wireless networks, network nodes, UEs, and / or any other components or systems that may facilitate or participate in the communication of data and / or signals whether via wired or wireless connections. The communication system 900 may include and / or interface with any type of communication, telecommunication, data, cellular, radio network, and / or other similar type of system.

[0174] The UEs 912 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 910 and other communication devices. Similarly, the network nodes 910 are arranged, capable, configured, and / or operable to communicate directly or indirectly with the UEs 912 and / or with other network nodes or equipment in the telecommunication network 902 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 902.

[0175] Note that the functionality of the network node or gNB described above may be implemented in any one of the network nodes 910, and the functionality of the UE described above may be implemented in any one of the UEs 912. In this regard, the network node 910 may be a multi-TRP network node (e.g., a gNB having multiple TRPs).

[0176] In the depicted example, the core network 906 connects the network nodes 910 to one or more hosts, such as host 916. 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 906 includes one more core network nodes (e.g., core network node 908) 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 908. 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).

[0177] The host 916 may be under the ownership or control of a service provider other than an operator or provider of the access network 904 and / or the telecommunication network 902, and may be operated by the service provider or on behalf of the service provider. The host 916 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.

[0178] As a whole, the communication system 900 of Figure 9 enables connectivity between the UEs, network nodes, and hosts. In that sense, the communication system 900 may be configured to operate according to predefined rules or procedures, such as specific standards that include, but are not limited to: Global System for Mobile Communications (GSM); Universal Mobile Telecommunications System (UMTS); Long Term Evolution (LTE), and / or other suitable Second, Third, Fourth, or Fifth Generation (2G, 3G, 4G, or 5G) standards, or any applicable future generation standard (e.g., Sixth Generation (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.

[0179] In some examples, the telecommunication network 902 is a cellular network that implements 3GPP standardized features. Accordingly, the telecommunication network 902 may support network slicing to provide different logical networks to different devices that are connected to the telecommunication network 902. For example, the telecommunication network 902 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 Internet of Things (loT) services to yet further UEs.

[0180] In some examples, the UEs 912 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 904 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network 904. Additionally, a UE may be configured for operating in single- or multi -Radio Access Technology (RAT) or multistandard mode. For example, a UE may operate with any one or combination of WiFi, New Radio (NR), and LTE, i.e. being configured for Multi -Radio Dual Connectivity (MR-DC), such as Evolved UMTS Terrestrial RAN (E-UTRAN) NR - Dual Connectivity (EN-DC).

[0181] In the example, a hub 914 communicates with the access network 904 to facilitate indirect communication between one or more UEs (e.g., UE 912C and / or 912D) and network nodes (e.g., network node 910B). In some examples, the hub 914 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs. For example, the hub 914 may be a broadband router enabling access to the core network 906 for the UEs. As another example, the hub 914 may be a controller that sendscommands or instructions to one or more actuators in the UEs. Commands or instructions may be received from the UEs, network nodes 910, or by executable code, script, process, or other instructions in the hub 914. As another example, the hub 914 may be a data collector that acts as temporary storage for UE data and, in some embodiments, may perform analysis or other processing of the data. As another example, the hub 914 may be a content source. For example, for a UE that is a Virtual Reality (VR) headset, display, loudspeaker or other media delivery device, the hub 914 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub 914 then provides to the UE either directly, after performing local processing, and / or after adding additional local content. In still another example, the hub 914 acts as a proxy server or orchestrator for the UEs, in particular if one or more of the UEs are low energy loT devices.

[0182] The hub 914 may have a constant / persistent or intermittent connection to the network node 910B. The hub 914 may also allow for a different communication scheme and / or schedule between the hub 914 and UEs (e.g., UE 912C and / or 912D), and between the hub 914 and the core network 906. In other examples, the hub 914 is connected to the core network 906 and / or one or more UEs via a wired connection. Moreover, the hub 914 may be configured to connect to a Machine-to-Machine (M2M) service provider over the access network 904 and / or to another UE over a direct connection. In some scenarios, UEs may establish a wireless connection with the network nodes 910 while still connected via the hub 914 via a wired or wireless connection. In some embodiments, the hub 914 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 910B. In other embodiments, the hub 914 may be a non-dedicated hub - that is, a device which is capable of operating to route communications between the UEs and the network node 910B, but which is additionally capable of operating as a communication start and / or end point for certain data channels.

[0183] Figure 10 shows a UE 1000 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 Internet Protocol (VoIP) phone, wireless local loop phone, desktop computer, Personal Digital Assistant (PDA), wireless camera, 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, vehicle-mounted or vehicle embedded / integrated wirelessdevice, etc. Other examples include any UE identified by the 3GPP, including a Narrowband Internet of Things (NB-IoT) UE, a Machine Type Communication (MTC) UE, and / or an enhanced MTC (eMTC) UE.

[0184] A UE may support Device-to-Device (D2D) communication, for example by implementing a 3 GPP standard for sidelink communication, Dedicated Short-Range Communication (DSRC), Vehi cl e-to- Vehicle (V2V), Vehicle-to-Infrastructure (V2I), or Vehicle-to-Everything (V2X). In other examples, a UE may not necessarily have a user in the sense of a human user who owns and / or operates the relevant device. Instead, a UE may represent a device that is intended for sale to, or operation by, a human user but which may not, or which may not initially, be associated with a specific human user (e.g., a smart sprinkler controller). Alternatively, a UE may represent a device that is not intended for sale to, or operation by, an end user but which may be associated with or operated for the benefit of a user (e.g., a smart power meter).

[0185] The UE 1000 includes processing circuitry 1002 that is operatively coupled via a bus 1004 to an input / output interface 1006, a power source 1008, memory 1010, a communication interface 1012, and / or any other component, or any combination thereof. Certain UEs may utilize all or a subset of the components shown in Figure 10. The level of integration between the components may vary from one UE to another UE. Further, certain UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

[0186] The processing circuitry 1002 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 1010. The processing circuitry 1002 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 1002 may include multiple Central Processing Units (CPUs).

[0187] In the example, the input / output interface 1006 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 anycombination thereof. An input device may allow a user to capture information into the UE 1000. 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.

[0188] In some embodiments, the power source 1008 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 1008 may further include power circuitry for delivering power from the power source 1008 itself, and / or an external power source, to the various parts of the UE 1000 via input circuitry or an interface such as an electrical power cable. Delivering power may be, for example, for charging of the power source 1008. Power circuitry may perform any formatting, converting, or other modification to the power from the power source 1008 to make the power suitable for the respective components of the UE 1000 to which power is supplied.

[0189] The memory 1010 may be or be configured to include memory such as Random Access Memory (RAM), Read Only Memory (ROM), Programmable ROM (PROM), Erasable PROM (EPROM), Electrically EPROM (EEPROM), magnetic disks, optical disks, hard disks, removable cartridges, flash drives, and so forth. In one example, the memory 1010 includes one or more application programs 1014, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data 1016. The memory 1010 may store, for use by the UE 1000, any of a variety of various operating systems or combinations of operating systems.

[0190] The memory 1010 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 RAM (SDRAM), external micro-DIMM SDRAM, smartcard memory such as a tamper resistant module in the form of a Universal Integrated Circuit Card(UICC) including one or more Subscriber Identity Modules (SIMs), such as a Universal SIM (USIM) and / or Internet Protocol Multimedia Services Identity Module (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 a ‘SIM card.’ The memory 1010 may allow the UE 1000 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 1010, which may be or comprise a device-readable storage medium.

[0191] The processing circuitry 1002 may be configured to communicate with an access network or other network using the communication interface 1012. The communication interface 1012 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna 1022. The communication interface 1012 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 1018 and / or a receiver 1020 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth). Moreover, the transmitter 1018 and receiver 1020 may be coupled to one or more antennas (e.g., the antenna 1022) and may share circuit components, software, or firmware, or alternatively be implemented separately.

[0192] In the illustrated embodiment, communication functions of the communication interface 1012 may include cellular communication, WiFi communication, LPWAN communication, data communication, voice communication, multimedia communication, short-range communications such as Bluetooth, NFC, 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 according to one or more communication protocols and / or standards, such as IEEE 802.11, Code Division Multiplexing Access (CDMA), Wideband CDMA (WCDMA), GSM, LTE, NR, UMTS, WiMax, Ethernet, Transmission Control Protocol / Intemet Protocol (TCP / IP), Synchronous Optical Networking (SONET), Asynchronous Transfer Mode (ATM), Quick User Datagram Protocol Internet Connection (QUIC), Hypertext Transfer Protocol (HTTP), and so forth.

[0193] Regardless of the type of sensor, a UE may provide an output of data captured by its sensors, through its communication interface 1012, via a wireless connection to a networknode. 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).

[0194] 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.

[0195] A UE, when in the form of an loT device, may be a device for use in one or more application domains, these domains comprising, but not limited to, city wearable technology, extended industrial application, and healthcare. Non-limiting examples of such an loT device are a device which is or which is embedded in: a connected refrigerator or freezer, a television, 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 VR, a wearable for tactile augmentation or sensory enhancement, a water sprinkler, an animal- or item-tracking device, a sensor for monitoring a plant or animal, an industrial robot, an Unmanned Aerial Vehicle (UAV), and any kind of medical device, like a heart rate monitor or a remote controlled surgical robot. A UE in the form of an loT device comprises circuitry and / or software in dependence of the intended application of the loT device in addition to other components as described in relation to the UE 1000 shown in Figure 10.

[0196] As yet another specific example, in an loT scenario, a UE may represent a machine or other device that performs monitoring and / or measurements and transmits the results of such monitoring and / or measurements to another UE and / or a network node. The UE may in this case be an M2M device, which may in a 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, an airplane, or otherequipment that is capable of monitoring and / or reporting on its operational status or other functions associated with its operation.

[0197] 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.

[0198] Figure 11 shows a network node 1100 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, APs (e.g., radio APs), Base Stations (BSs) (e.g., radio BSs, Node Bs, evolved Node Bs (eNBs), NR Node Bs (gNBs)), and 0-RAN nodes or components of an 0-RAN node (e.g., 0-RU, O- DU, O-CU).

[0199] 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, distributed units (e.g., in an 0-RAN access node), and / or Remote Radio Units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such RRUs 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).

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

[0201] The network node 1100 includes processing circuitry 1102, memory 1104, a communication interface 1106, and a power source 1108. The network node 1100 may be composed of multiple physically separate components (e.g., a NodeB component and an 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 1100 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 1100 may be configured to support multiple RATs. In such embodiments, some components may be duplicated (e.g., separate memory 1104 for different RATs) and some components may be reused (e.g., a same antenna 1110 may be shared by different RATs). The network node 1100 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 1100, for example GSM, WCDMA, LTE, NR, WiFi, Zigbee, Z-wave, Long Range Wide Area Network (LoRaWAN), Radio Frequency Identification (RFID), or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within the network node 1100.

[0202] The processing circuitry 1102 may comprise a combination of one or more of a microprocessor, controller, microcontroller, CPU, DSP, ASIC, FPGA, 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 1100 components, such as the memory 1104, to provide network node 1100 functionality.

[0203] In some embodiments, the processing circuitry 1102 includes a System on a Chip (SOC). In some embodiments, the processing circuitry 1102 includes one or more of Radio Frequency (RF) transceiver circuitry 1112 and baseband processing circuitry 1114. In some embodiments, the RF transceiver circuitry 1112 and the baseband processing circuitry 1114 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 the RF transceiver circuitry 1112 and the baseband processing circuitry 1114 may be on the same chip or set of chips, boards, or units.

[0204] The memory 1104 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, RAM, ROM, mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a CompactDisk (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 1102. The memory 1104 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 1102 and utilized by the network node 1100. The memory 1104 may be used to store any calculations made by the processing circuitry 1102 and / or any data received via the communication interface 1106. In some embodiments, the processing circuitry 1102 and the memory 1104 are integrated.

[0205] The communication interface 1106 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 1106 comprises port(s) / terminal(s) 1116 to send and receive data, for example to and from a network over a wired connection. The communication interface 1106 also includes radio front-end circuitry 1118 that may be coupled to, or in certain embodiments a part of, the antenna 1110. The radio front-end circuitry 1118 comprises filters 1120 and amplifiers 1122. The radio front-end circuitry 1118 may be connected to the antenna 1110 and the processing circuitry 1102. The radio front-end circuitry 1118 may be configured to condition signals communicated between the antenna 1110 and the processing circuitry 1102. The radio front-end circuitry 1118 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 1118 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of the filters 1120 and / or the amplifiers 1122. The radio signal may then be transmitted via the antenna 1110. Similarly, when receiving data, the antenna 1110 may collect radio signals which are then converted into digital data by the radio frontend circuitry 1118. The digital data may be passed to the processing circuitry 1102. In other embodiments, the communication interface 1106 may comprise different components and / or different combinations of components.

[0206] In certain alternative embodiments, the network node 1100 does not include separate radio front-end circuitry 1118; instead, the processing circuitry 1102 includes radio front-end circuitry and is connected to the antenna 1110. Similarly, in some embodiments, all or some of the RF transceiver circuitry 1112 is part of the communication interface 1106. In still other embodiments, the communication interface 1106 includes the one or more ports or terminals 1116, the radio front-end circuitry 1118, and the RF transceiver circuitry 1112 as part of a radiounit (not shown), and the communication interface 1106 communicates with the baseband processing circuitry 1114, which is part of a digital unit (not shown).

[0207] The antenna 1110 may include one or more antennas, or antenna arrays, configured to send and / or receive wireless signals. The antenna 1110 may be coupled to the radio front-end circuitry 1118 and may be any type of antenna capable of transmitting and receiving data and / or signals wirelessly. In certain embodiments, the antenna 1110 is separate from the network node 1100 and connectable to the network node 1100 through an interface or port.

[0208] The antenna 1110, the communication interface 1106, and / or the processing circuitry 1102 may be configured to perform any receiving operations and / or certain obtaining operations described herein as being performed by the network node 1100. Any information, data, and / or signals may be received from a UE, another network node, and / or any other network equipment. Similarly, the antenna 1110, the communication interface 1106, and / or the processing circuitry 1102 may be configured to perform any transmitting operations described herein as being performed by the network node 1100. Any information, data, and / or signals may be transmitted to a UE, another network node, and / or any other network equipment.

[0209] The power source 1108 provides power to the various components of the network node 1100 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). The power source 1108 may further comprise, or be coupled to, power management circuitry to supply the components of the network node 1100 with power for performing the functionality described herein. For example, the network node 1100 may be connectable to an external power source (e.g., the power grid or an electricity outlet) via input circuitry or an interface such as an electrical cable, whereby the external power source supplies power to power circuitry of the power source 1108. As a further example, the power source 1108 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.

[0210] Embodiments of the network node 1100 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 1100 may include user interface equipment to allow input of information into the network node 1100 and to allow output of information from the network node 1100. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node 1100.

[0211] Figure 12 is a block diagram of a host 1200, which may be an embodiment of the host 916 of Figure 9, in accordance with various aspects described herein. As used herein, the host 1200 may be or comprise various combinations of hardware and / or software including a standalone server, a blade server, a cloud-implemented server, a distributed server, a virtual machine, container, or processing resources in a server farm. The host 1200 may provide one or more services to one or more UEs.

[0212] The host 1200 includes processing circuitry 1202 that is operatively coupled via a bus 1204 to an input / output interface 1206, a network interface 1208, a power source 1210, and memory 1212. Other components may be included in other embodiments. Features of these components may be substantially similar to those described with respect to the devices of previous figures, such as Figures 10 and 11, such that the descriptions thereof are generally applicable to the corresponding components of the host 1200.

[0213] The memory 1212 may include one or more computer programs including one or more host application programs 1214 and data 1216, which may include user data, e.g. data generated by a UE for the host 1200 or data generated by the host 1200 for a UE. Embodiments of the host 1200 may utilize only a subset or all of the components shown. The host application programs 1214 may be implemented in a container-based architecture and may provide support for video codecs (e.g., Versatile Video Coding (VVC), High Efficiency Video Coding (HEVC), Advanced Video Coding (AVC), Moving Picture Experts Group (MPEG), VP9) and audio codecs (e.g., Free Lossless Audio Codec (FLAC), Advanced Audio Coding (AAC), MPEG, G.711), including transcoding for multiple different classes, types, or implementations of UEs (e.g., handsets, desktop computers, wearable display systems, and heads-up display systems). The host application programs 1214 may also provide for user authentication and licensing checks and may periodically report health, routes, and content availability to a central node, such as a device in or on the edge of a core network. Accordingly, the host 1200 may select and / or indicate a different host for Over-The-Top (OTT) services for a UE. The host application programs 1214 may support various protocols, such as the HTTP Live Streaming (HLS) protocol, Real-Time Messaging Protocol (RTMP), Real-Time Streaming Protocol (RTSP), Dynamic Adaptive Streaming over HTTP (DASH or MPEG-DASH), etc.

[0214] Figure 13 is a block diagram illustrating a virtualization environment 1300 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 relatesto 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 1300 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. In some embodiments, the virtualization environment 1300 includes components defined by the O-RAN Alliance, such as an O-Cloud environment orchestrated by a Service Management and Orchestration Framework via an O-2 interface.

[0215] Applications 1302 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) are run in the virtualization environment 1300 to implement some of the features, functions, and / or benefits of some of the embodiments disclosed herein.

[0216] Hardware 1304 includes processing circuitry, memory that stores software and / or instructions executable by hardware processing circuitry, and / or other hardware devices as described herein, such as a network interface, input / output interface, and so forth. Software may be executed by the processing circuitry to instantiate one or more virtualization layers 1306 (also referred to as hypervisors or VM Monitors (VMMs)), provide VMs 1308A and 1308B (one or more of which may be generally referred to as VMs 1308), and / or perform any of the functions, features, and / or benefits described in relation with some embodiments described herein. The virtualization layer 1306 may present a virtual operating platform that appears like networking hardware to the VMs 1308.

[0217] The VMs 1308 comprise virtual processing, virtual memory, virtual networking, or interface and virtual storage, and may be run by a corresponding virtualization layer 1306. Different embodiments of the instance of a virtual appliance 1302 may be implemented on one or more of the VMs 1308, 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.

[0218] In the context of NFV, a VM 1308 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 1308, and that part of the hardware 1304 that executes that VM, be it hardwarededicated to that VM and / or hardware shared by that VM with others of the VMs 1308, 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 1308 on top of the hardware 1304 and corresponds to the application 1302.

[0219] The hardware 1304 may be implemented in a standalone network node with generic or specific components. The hardware 1304 may implement some functions via virtualization. Alternatively, the hardware 1304 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 1310, which, among others, oversees lifecycle management of the applications 1302. In some embodiments, the hardware 1304 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 RAN or a base station. In some embodiments, some signaling can be provided with the use of a control system 1312 which may alternatively be used for communication between hardware nodes and radio units.

[0220] Figure 14 shows a communication diagram of a host 1402 communicating via a network node 1404 with a UE 1406 over a partially wireless connection in accordance with some embodiments. Example implementations, in accordance with various embodiments, of the UE (such as the UE 912A of Figure 9 and / or the UE 1000 of Figure 10), the network node (such as the network node 910A of Figure 9 and / or the network node 1100 of Figure 11), and the host (such as the host 916 of Figure 9 and / or the host 1200 of Figure 12) discussed in the preceding paragraphs will now be described with reference to Figure 14.

[0221] Like the host 1200, embodiments of the host 1402 include hardware, such as a communication interface, processing circuitry, and memory. The host 1402 also includes software, which is stored in or is accessible by the host 1402 and executable by the processing circuitry. The software includes a host application that may be operable to provide a service to a remote user, such as the UE 1406 connecting via an OTT connection 1450 extending between the UE 1406 and the host 1402. In providing the service to the remote user, a host application may provide user data which is transmitted using the OTT connection 1450.

[0222] The network node 1404 includes hardware enabling it to communicate with the host 1402 and the UE 1406. The connection 1460 may be direct or pass through a core network (like the core network 906 of Figure 9) and / or one or more other intermediate networks, suchas one or more public, private, or hosted networks. For example, an intermediate network may be a backbone network or the Internet.

[0223] The UE 1406 includes hardware and software, which is stored in or accessible by the UE 1406 and executable by the UE’s processing circuitry. The software includes a client application, such as a web browser or operator-specific “app” that may be operable to provide a service to a human or non-human user via the UE 1406 with the support of the host 1402. In the host 1402, an executing host application may communicate with the executing client application via the OTT connection 1450 terminating at the UE 1406 and the host 1402. In providing the service to the user, the UE's client application may receive request data from the host's host application and provide user data in response to the request data. The OTT connection 1450 may transfer both the request data and the user data. The UE's client application may interact with the user to generate the user data that it provides to the host application through the OTT connection 1450.

[0224] The OTT connection 1450 may extend via the connection 1460 between the host 1402 and the network node 1404 and via a wireless connection 1470 between the network node 1404 and the UE 1406 to provide the connection between the host 1402 and the UE 1406. The connection 1460 and the wireless connection 1470, over which the OTT connection 1450 may be provided, have been drawn abstractly to illustrate the communication between the host 1402 and the UE 1406 via the network node 1404, without explicit reference to any intermediary devices and the precise routing of messages via these devices.

[0225] As an example of transmitting data via the OTT connection 1450, in step 1408, the host 1402 provides user data, which may be performed by executing a host application. In some embodiments, the user data is associated with a particular human user interacting with the UE 1406. In other embodiments, the user data is associated with a UE 1406 that shares data with the host 1402 without explicit human interaction. In step 1410, the host 1402 initiates a transmission carrying the user data towards the UE 1406. The host 1402 may initiate the transmission responsive to a request transmitted by the UE 1406. The request may be caused by human interaction with the UE 1406 or by operation of the client application executing on the UE 1406. The transmission may pass via the network node 1404 in accordance with the teachings of the embodiments described throughout this disclosure. Accordingly, in step 1412, the network node 1404 transmits to the UE 1406 the user data that was carried in the transmission that the host 1402 initiated, in accordance with the teachings of the embodiments described throughout this disclosure. In step 1414, the UE 1406 receives the user data carriedin the transmission, which may be performed by a client application executed on the UE 1406 associated with the host application executed by the host 1402.

[0226] In some examples, the UE 1406 executes a client application which provides user data to the host 1402. The user data may be provided in reaction or response to the data received from the host 1402. Accordingly, in step 1416, the UE 1406 may provide user data, which may be performed by executing the client application. In providing the user data, the client application may further consider user input received from the user via an input / output interface of the UE 1406. Regardless of the specific manner in which the user data was provided, the UE 1406 initiates, in step 1418, transmission of the user data towards the host 1402 via the network node 1404. In step 1420, in accordance with the teachings of the embodiments described throughout this disclosure, the network node 1404 receives user data from the UE 1406 and initiates transmission of the received user data towards the host 1402. In step 1422, the host 1402 receives the user data carried in the transmission initiated by the UE 1406.

[0227] One or more of the various embodiments improve the performance of OTT services provided to the UE 1406 using the OTT connection 1450, in which the wireless connection 1470 forms the last segment. More precisely, the teachings of these embodiments may improve, e.g., data rate, latency, and / or power consumption and thereby provide benefits such as, e.g., reduced user waiting time, related restriction on file size, improved content resolution, better responsiveness, and / or extended battery lifetime.

[0228] In an example scenario, factory status information may be collected and analyzed by the host 1402. As another example, the host 1402 may process audio and video data which may have been retrieved from a UE for use in creating maps. As another example, the host 1402 may collect and analyze real-time data to assist in controlling vehicle congestion (e.g., controlling traffic lights). As another example, the host 1402 may store surveillance video uploaded by a UE. As another example, the host 1402 may store or control access to media content such as video, audio, VR, or AR which it can broadcast, multicast, or unicast to UEs. As other examples, the host 1402 may be used for energy pricing, remote control of non-time critical electrical load to balance power generation needs, location services, presentation services (such as compiling diagrams etc. from data collected from remote devices), or any other function of collecting, retrieving, storing, analyzing, and / or transmitting data.

[0229] In some examples, a measurement procedure may be provided for the purpose of monitoring data rate, latency, and other factors on which the one or more embodiments improve. There may further be an optional network functionality for reconfiguring the OTT connection 1450 between the host 1402 and the UE 1406 in response to variations in themeasurement results. The measurement procedure and / or the network functionality for reconfiguring the OTT connection 1450 may be implemented in software and hardware of the host 1402 and / or the UE 1406. In some embodiments, sensors (not shown) may be deployed in or in association with other devices through which the OTT connection 1450 passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or by supplying values of other physical quantities from which software may compute or estimate the monitored quantities. The reconfiguring of the OTT connection 1450 may include message format, retransmission settings, preferred routing, etc.; the reconfiguring need not directly alter the operation of the network node 1404. Such procedures and functionalities may be known and practiced in the art. In certain embodiments, measurements may involve proprietary UE signaling that facilitates measurements of throughput, propagation times, latency, and the like by the host 1402. The measurements may be implemented in that software causes messages to be transmitted, in particular empty or ‘dummy’ messages, using the OTT connection 1450 while monitoring propagation times, errors, etc.

[0230] 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.

[0231] In certain embodiments, some or all of the functionality described herein may be provided by processing circuitry executing instructions stored 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 hardwired 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.

[0232] Those skilled in the art will recognize improvements and modifications to the embodiments of the present disclosure. All such improvements and modifications are considered within the scope of the concepts disclosed herein.

[0233] Some exemplary embodiments of the present disclosure are as follows:Group A Embodiments

[0234] Embodiment 1 : A method performed by aUser Equipment, UE, the method comprising any one or more of the following: receiving a configuration from a first network node for transmitting a beam report wherein the beam report includes information on M>1 beam(s) received from a second network node or from the first network node; including in the beam report an indication of whether additional or remaining beam information is available to be reported in a future beam report wherein the additional or remaining beam information is different from the information on M>1 beam(s); and transmitting the beam report to the first network node.

[0235] Embodiment 2: The method of embodiment 0, wherein wherein the configuration includes at least one of a maximum number Mmaxof beams reported in a single beam report wherein M < Mmnx.

[0236] Embodiment 3 : The method of embodiments 0-2, wherein a maximum number Zmaxof beams reported over multiple consecutive beam reports wherein M < Mmax.

[0237] Embodiment 4: The method of embodiments 0-3, wherein the maximum number of multiple consecutive beam reports is configured as part of the configuration or predefined in specifications.

[0238] Embodiment 5: The method of any of embodiments 0 to

[0237] , wherein the information on M > 1 beam(s) includes one or more of:- identifiers of a first set of M > 1 reference signal(s) on which measurement(s) corresponding to the M > 1 beam(s) are performed;- layer 1 RSRP(s) based on measurements on the first set of M > 1 reference signal(s);- layer 1 SINR(s) based on measurements on the first set of M > 1 reference signal(s);- identified s) of associated event(s);- an index for identifying a beam report among multiple consecutive beam reports;

[0239] Embodiment 6: The method of any of embodiment 5, wherein the first set of M > 1 reference signal(s) is a subset of a second set of reference signal(s).

[0240] Embodiment 7: The method of any of embodiments 0 to

[0239] , wherein the information on M > 1 beam(s) includes one or more of:- identifiers of M > 1 beams(s) predicted based on measurements on a third set of reference signal(s);- predicted layer 1 RSRP(s) corresponding to the M > 1 beams(s) based on measurements on the third set of reference signal(s);- predicted layer 1 SINR(s) based on measurements on the third set of reference signal(s);- identified s) of associated event(s);- an index for identifying a beam report among multiple consecutive beam reports.

[0241] Embodiment 8: The method of any of embodiments 0 to 7, wherein the indication of whether additional or remaining beam information is available to be reported in a future beam report is a binary bit.

[0242] Embodiment 9: The method of any of embodiment

[0241] , wherein the binary bit set to a first value indicates that there is additional or remaining information available to be reported in a future beam report.

[0243] Embodiment 10: The method of any of embodiments 0 to 7, wherein the indication of whether additional or remaining beam information is available to be reported in a future beam report is an integer number which indicates a number M' > 1 of additional beams for which additional or remaining beam information is available.

[0244] Embodiment 11 : The method of any of embodiments 0 to

[0243] , wherein a second beam report is transmitted containing at least part of the available additional or remaining beam information.

[0245] Embodiment 12: The method of any of embodiment

[0244] , wherein the second beam report further includes updated indication of whether additional or remaining beam information is available to be reported in a future beam report.

[0246] Embodiment 13: The method of any of embodiment 11, wherein the second beam report is transmitted to the gNB according to any of the following:- In response of receiving a request from the gNB- In the next configured transmission opportunity

[0247] Embodiment 14: The method of any of embodiments 0 to

[0246] , wherein the available or remaining additional beam information reported over the multiple consecutive beam reports are associated to measurements performed in the same measurement occasions, measurement period, or measurement interval.

[0248] Embodiment 15: The method of any of embodiments 0 to

[0247] , wherein the beam report further contains an indication indicating whether the information on M > 1 beam(s) included in the said beam report are associated to the available additional or remaining beam information as indicated in the previous beam report.

[0249] Embodiment 16: The method of any of embodiments 0 to

[0248] , wherein the second (or Nth wherein N>1) beam report among the multiple consecutive beam reports includes only beams not included in the first beam report (or first N-l beam reports, respectively).

[0250] Embodiment 17: The method of any of embodiment

[0249] , wherein information on a total of Mtotaibeams are reported in the first N beam reports and represent the Mtotaistrongest beams.

[0251] Embodiment 18: The method of any of embodiments 0 to 17, further comprising receiving from the first network node an indication that indicates whether a first, second, or Nth beam report should be transmitted to the first network node.

[0252] Embodiment 19: The method of any of embodiments 0 to 18, wherein the indication is carried in a DCI field in PDCCH triggering aperiodic CSI report.

[0253] Embodiment 20: The method of any of the previous embodiments, further comprising receiving an indication from the first network node that indicates which subset of beams should be included in the beam report, based on their RSRP values or other link quality measure.

[0254] Embodiment 21 : The method of any of the previous embodiments, further comprising: providing user data; and forwarding the user data to a host via the transmission to the network node.Group B Embodiments

[0255] Embodiment 22: A method performed by a network node, the method comprising one or more of the following: transmitting a configuration for transmitting a beam report wherein the beam report includes information on M>1 beam(s) received from a second network node or from the first network node; receiving the beam report from the user equipment, wherein the beam report includes an indication of whether additional or remaining beam information is available to be reported in a future beam report wherein the additional or remaining beam information is different from the information on M>1 beam(s).

[0256] Embodiment 23: The method of embodiment

[0255] , further comprising any one or more of the features of embodiments 2-21.

[0257] Embodiment 24: The method of any of the previous embodiments, further comprising: obtaining user data; and forwarding the user data to a host or a user equipment.Group C Embodiments

[0258] Embodiment 25: A user equipment 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.

[0259] Embodiment 25: A network node comprising: processing circuitry configured to perform any of the steps of any of the Group B embodiments; and power supply circuitry configured to supply power to the processing circuitry.

[0260] Embodiment 27: A user equipment (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; anda battery connected to the processing circuitry and configured to supply power to the UE.

[0261] Embodiment 28: A host configured to operate in a communication system to provide an over-the-top (OTT) service, the host comprising: processing circuitry configured to provide user data; and a network interface configured to initiate transmission of the user data to a network node in a cellular network for transmission to a user equipment (UE), the network node having a communication interface and processing circuitry, the processing circuitry of the network node configured to perform any of the operations of any of the Group B embodiments to transmit the user data from the host to the UE.

[0262] Embodiment 29: The host of the previous embodiment, wherein: the processing circuitry of the host is configured to execute a host application that provides the user data; and the UE comprises processing circuitry configured to execute a client application associated with the host application to receive the transmission of user data from the host.

[0263] Embodiment 30: A method implemented in a host configured to operate in a communication system that further includes a network node and a user equipment (UE), the method comprising: providing user data for the UE; and initiating a transmission carrying the user data to the UE via a cellular network comprising the network node, wherein the network node performs any of the operations of any of the Group B embodiments to transmit the user data from the host to the UE.

[0264] Embodiment 31 : The method of the previous embodiment, further comprising, at the network node, transmitting the user data provided by the host for the UE.

[0265] Embodiment 32: The method of any of the previous 2 embodiments, wherein the user data is provided at the host by executing a host application that interacts with a client application executing on the UE, the client application being associated with the host application.

[0266] Embodiment 33: A communication system configured to provide an over-the-top (OTT) service, the communication system comprising: a host comprising: processing circuitry configured to provide user data for a user equipment (UE), the user data being associated with the over-the-top service; and a network interface configured to initiate transmission of the user data toward a cellular network node for transmission to the UE, the network node having a communicationinterface and processing circuitry, the processing circuitry of the network node configured to perform any of the operations of any of the Group B embodiments to transmit the user data from the host to the UE.

[0267] Embodiment 34: The communication system of the previous embodiment, further comprising: the network node; and / or the UE.

[0268] Embodiment 35: A method implemented by a host configured to operate in a communication system that further includes a network node and a user equipment (UE), the method comprising: at the host, initiating receipt of user data from the UE, the user data originating from a transmission which the network node has received from the UE, wherein the network node performs any of the steps of any of the Group B embodiments to receive the user data from the UE for the host.

[0269] Embodiment 36: The method of the previous embodiment, further comprising at the network node, transmitting the received user data to the host.

Claims

CLAIMS1. A method performed by a User Equipment, UE, (912) the method comprising any one or more of the following: receiving (400) a configuration from a first network node (910) for transmitting a beam report wherein the beam report includes information on M>1 beam(s) received from a second network node or from the first network node; including (402) in the beam report an indication of whether additional or remaining beam information is available to be reported in a future beam report wherein the additional or remaining beam information is different from the information on M>1 beam(s); and transmitting (404) the beam report to the first network node.

2. The method of claim 1, wherein wherein the configuration includes at least one of a maximum number Mmaxof beams reported in a single beam report wherein M < Mmax.

3. The method of claims 1-2, wherein a maximum number Zmaxof beams reported over multiple consecutive beam reports wherein M < Mmax.

4. The method of claims 1-3, wherein the maximum number of multiple consecutive beam reports is configured as part of the configuration or predefined in specifications.

5. The method of any of claims 1 to 4, wherein the information on M > 1 beam(s) includes one or more of- identifiers of a first set of M > 1 reference signal(s) on which measurement(s) corresponding to the M > 1 beam(s) are performed;- layer 1 RSRP(s) based on measurements on the first set of M > 1 reference signal(s);- layer 1 SINR(s) based on measurements on the first set of M > 1 reference signal(s);- Identifier(s) of associated event(s);- an index for identifying a beam report among multiple consecutive beam reports;6. The method of claim 5, wherein the first set of M > 1 reference signal(s) is a subset of a second set of reference signal(s).

7. The method of any of claims 1 to 6, wherein the information on M > 1 beam(s) includes one or more of:- identifiers of M > 1 beams(s) predicted based on measurements on a third set of reference signal(s);- predicted layer 1 RSRP(s) corresponding to the M > 1 beams(s) based on measurements on the third set of reference signal(s);- predicted layer 1 SINR(s) based on measurements on the third set of reference signal(s);- Identifier(s) of associated event(s);- an index for identifying a beam report among multiple consecutive beam reports.

8. The method of any of claims 1 to 7, wherein the indication of whether additional or remaining beam information is available to be reported in a future beam report is a binary bit.

9. The method of any of claim 8, wherein the binary bit set to a first value indicates that there is additional or remaining information available to be reported in a future beam report.

10. The method of any of claims 1 to 7, wherein the indication of whether additional or remaining beam information is available to be reported in a future beam report is an integer number which indicates a number M' > 1 of additional beams for which additional or remaining beam information is available.

11. The method of any of claims 1 to 10, wherein a second beam report is transmitted containing at least part of the available additional or remaining beam information.

12. The method of claim 11, wherein the second beam report further includes updated indication of whether additional or remaining beam information is available to be reported in a future beam report.

13. The method of claim 11, wherein the second beam report is transmitted to the gNB according to any of the following:In response of receiving a request from the gNB In the next configured transmission opportunity14. The method of any of claims 1 to 13, wherein the available or remaining additional beam information reported over the multiple consecutive beam reports are associated to measurements performed in the same measurement occasions, measurement period, or measurement interval.

15. The method of any of claims 1 to 14, wherein the beam report further contains an indication indicating whether the information on M > 1 beam(s) included in the said beam report are associated to the available additional or remaining beam information as indicated in the previous beam report.

16. The method of any of claims 1 to 15, wherein the second (or Nth wherein N>1) beam report among the multiple consecutive beam reports includes only beams not included in the first beam report (or first N-l beam reports, respectively).

17. The method of claim 16, wherein information on a total of Mtotaibeams are reported in the first N beam reports and represent the Mtotaistrongest beams.

18. The method of any of claims 1 to 17, further comprising receiving from the first network node an indication that indicates whether a first, second, or Nth beam report should be transmitted to the first network node.

19. The method of any of claims 1 to 18, wherein the indication is carried in a DCI field in PDCCH triggering aperiodic CSI report.

20. The method of any of the previous claims, further comprising receiving an indication from the first network node that indicates which subset of beams should be included in the beam report, based on their RSRP values or other link quality measure.

21. The method of any of the previous claims, further comprising: providing user data; and forwarding the user data to a host via the transmission to the network node.

22. A method performed by a network node (910) , the method comprising one or more of the following: transmitting (500) a configuration for transmitting a beam report wherein the beam report includes information on M>1 beam(s) received from a second network node or from the first network node;receiving (502) the beam report from the user equipment, wherein the beam report includes an indication of whether additional or remaining beam information is available to be reported in a future beam report wherein the additional or remaining beam information is different from the information on M>1 beam(s).

23. The method of claim 22, further comprising any one or more of the features of claims 2- 21.

24. The method of any of the previous claims, further comprising: obtaining user data; and forwarding the user data to a host or a user equipment.

25. A user equipment (1000) comprising: processing circuitry (1002) configured to perform any of the steps of any of claims 1-21; and power supply circuitry (1008) configured to supply power to the processing circuitry.

26. A network node (1100) comprising: processing circuitry (1102) configured to perform any of the steps of any of claims 22-24; and power supply circuitry (1108) configured to supply power to the processing circuitry.

27. A user equipment (UE) (1000) comprising: an antenna (1022) 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 claims 1-21; 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.

28. A host configured to operate in a communication system to provide an over-the-top (OTT)service, the host comprising: processing circuitry configured to provide user data; and a network interface configured to initiate transmission of the user data to a network node in a cellular network for transmission to a user equipment (UE), the network node having a communication interface and processing circuitry, the processing circuitry of the network node configured to perform any of the operations of any of claims 22-24 to transmit the user data from the host to the UE.

29. The host of the previous claim, wherein: the processing circuitry of the host is configured to execute a host application that provides the user data; and the UE comprises processing circuitry configured to execute a client application associated with the host application to receive the transmission of user data from the host.

30. A method implemented in a host configured to operate in a communication system that further includes a network node and a user equipment (UE), the method comprising: providing user data for the UE; and initiating a transmission carrying the user data to the UE via a cellular network comprising the network node, wherein the network node performs any of the operations of any of claims 22- 24 to transmit the user data from the host to the UE.

31. The method of the previous claim, further comprising, at the network node, transmitting the user data provided by the host for the UE.

32. The method of any of the previous 2 claims, wherein the user data is provided at the host by executing a host application that interacts with a client application executing on the UE, the client application being associated with the host application.

Images