Network node, communication device and methods for handling beam prediction reporting in wireless communication system

Abstract

Network node (311) and user equipment (330) and methods therein for handling beam prediction reporting in a wireless communication network (300). The network node 311 sends a configuration message to one or more UEs (330, 331) for configuring beam prediction reporting for the one or more UEs (330, 331). The configuration message comprises one or more indications indicating whether one or more beams in a set of beams are allowed to be reported or not. The network node 311 receives one or more beam prediction reports from the one or more UEs (330, 331).

Description

NETWORK NODE, COMMUNICATION DEVICE AND METHODS FOR HANDLINGBEAM PREDICTION REPORTING IN WIRELESS COMMUNICATION SYSTEMTECHNICAL FIELD

[0001] Embodiments herein relate to network nodes, communication devices and methods therein for handling beam prediction reporting in a wireless communication system.BACKGROUND

[0002] A Universal Mobile Telecommunications System (UMTS) is a third generation (3G) telecommunication network, which evolved from the second generation (2G) Global System for Mobile Communications (GSM). Specifications for the Evolved Packet System (EPS), also called a Fourth Generation (4G) network or Long Term Evolution (LTE) have been completed within the 3rd Generation Partnership Project (3GPP) and this work continues in the coming 3GPP releases, for example to specify a Fifth Generation (5G) New Radio (NR) network, Next Generation (NG) and upcoming releases.

[0003] In a typical wireless communication network or system, wireless devices, also known as wireless communication devices, mobile stations, and / or user equipment (UE), communicate via a Radio Access Network (RAN) to one or more core networks (CN). The RAN covers a geographical area which is divided into service areas or cell areas, which may also be referred to as a beam or a beam group, with each service area or cell area being served by a radio network node such as a radio access node e.g., a Wi-Fi access point or a radio base station (RBS), which in some networks may also be denoted, for example, a “NodeB” or “eNodeB” or “eNB” or “gNB”. A radio network node communicates via downlink (DL) transmissions over an air interface operating on radio frequencies with one or more wireless communication devices within a range of the radio network node.

[0004] In some deployment scenarios, to reduce potential inter-cell interference, it may be desirable to avoid DL transmissions at certain spatial directions such as at or around the horizontal directions. In 5G NR, this can be achieved via codebook subset restriction (CBSR) that is specified for Channel State Information (CSI) feedback. The general idea is to restrict certain precoders in a CSI codebook that would cause interference in certain directions, for example to control interference generated towards other cells, or due to coexistence issue with satellites etc. In NR, there is a possibility for the gNB to restrict the UE to select only a subset of precoders within a codebook and / or a subset of the ranks. This isknown as CBSR for CSI feedback and can be used if the network node knows that it wants to avoid transmission in a certain direction e.g., since this direction interferes heavily with users in an adjacent cell. Hence the precoders associated with this direction are restricted.

[0005] In 3GPP standard TS 38.214, the following is captured which shows how codebook subset restriction is specified for different codebooks:-The CodebookConfig in CSI-ReportConfig can be configured with two Codebook Subset Restrictions. The first restriction applies to a reported PMI associated to a CSI-RS resource in Group 1. The second restriction applies to a reported PMI associated to a CSI-RS resource in Group 2.5.2.2.2 Precoding matrix indicator (PMI)5.2.2.2.1 Type I Single-Panel CodebookFor 2 antenna ports {3000, 3001 } and the UE configured with higher layer parameter codebookType set to 'typel-SinglePanef each PMI value corresponds to a codebook index given in Table 5.2.2.2.1-1. The UE is configured with the higher layer parameter twoTX- CodebookSubsetRestriction. The bitmap parameter twoTX-CodebookSubsetRestriction forms the bit sequence a5,..., aj , a0where a0is the LSB and a5is the MSB and where a bit value of zero indicates that PMI reporting is not allowed to correspond to the precoder associated with the bit. Bits 0 to 3 are associated respectively with the codebook indices 0 to 3 for u = 1 layer, and bits 4 and 5 are associated respectively with the codebook indices 0 and 1 for o = 2 layers.5.2.2.2.3 Type II CodebookFor 4 antenna ports {3000, 3001, . . 3003}, 8 antenna ports {3000, 3001, . . 3007}, 12 antenna ports {3000, 3001, ..., 3011 }, 16 antenna ports {3000, 3001, ..., 3015}, 24 antenna ports {3000, 3001, . . ., 3023}, and 32 antenna ports {3000, 3001, . . ., 3031 }, and the UE configured with higher layer parameter codebookType set to 'typell'The values of and are configured with the higher layer parameter nl-n2- codebookSubsetRestriction. The supported configurations of for a given number of CSI-RS ports and the corresponding values of are given in Table 5.2.2.2.1-2. The number of CSI-RS ports, , is .

[0006] The standard thus supports the UE to only choose the precoders within a codebook that are not restricted via codebook subset restriction by the network (NW) node.

[0007] During the 3GPP meeting RANl#109-e it was agreed to study Artificial Intelligence and Machine Learning (AI / ML) based spatial beam prediction, the core idea of which is as follows: Predict the “best” beam or beams from a Set A of beams using measurement results from another Set B of beams.

[0008] The following two examples illustrate some scenarios:-Set B is a subset of a Set A. For example, Set A is a set of 8 Synchronization Signal Block (SSB) / Channel State Information Reference Signal (CSLRS) beams shown in Figure 1 with both light and dark circles. The figure illustrates a grid- of-beam type radiation pattern: Each row (resp. column) depicts a certain zenith (resp. azimuth) angle from the antenna array. Set A has 8 beams and Set B has 4 beams indicated by dark circles. The UE measures Set B, i.e. the 4 beams indicated by dark circles. The AI / ML model should predict the best beam or beams in Set A using only measurements from Set B.-Set A and Set B correspond to two different sets of beams. For example, as shown in Figure 2, Set A is a set of 30 narrow CSLRS beams as shown in (b), and Set B is a set of 8 wide SSB beams, as shown in (a). The UE measures beams in Set B and the AI / ML model should predict the best beam(s) from Set A.

[0009] The spatial beam prediction can be performed in gNB or UE. The number of beams to be predicted by the UE might be large. Currently, for beam reporting, there is no method for UE to understand which beams that it predicts that are temporarily undesirable from a NW-side, for example due to current hardware restrictions of the gNB, due to interference generation towards other cells and / or interference generation towards satellite etc. Hence, how to restrict certain beams from being predicted / reported is a challenge that needs to be solved.SUMMARY

[0010] Certain aspects of this disclosure and their embodiments may provide solutions to these or other challenges.

[0011] It is an object of embodiments herein to provide methods for enabling UE to apply beam prediction subset restriction for predicted beams and / or determine which beams that are more undesirable than others.

[0012] In this disclosure, a UE beam prediction subset restriction concept is proposed to the beam prediction use case. The disclosure includes various methods for a network node to indicate to the UE which beams to be restricted during beam predictions / reporting whicheffectively translates into beams "not allowed to be reported" for the UE, or beams that are more undesirable than others.

[0013] According to one aspect of embodiments herein, the object is achieved by a network node and method therein for configuring beam prediction reporting for one or more user equipment (UEs) in a wireless communication network. The network node sends a configuration message to one or more UEs for configuring beam prediction reporting for the one or more UEs. The configuration message comprises one or more indications indicating whether one or more beams in a set of beams are allowed to be reported or not. The network node receives one or more beam prediction reports from the one or more UEs.

[0014] According to some embodiments, the network node may configure a subset of Set A beams or Set B beams as restricted beams which are not allowed to be reported as a predicted beam or not to be included in a beam prediction report.

[0015] According to one aspect of embodiments herein, the object is achieved by a user equipment (UE) and method therein for reporting beam prediction in a wireless communication network. The UE receives a configuration message from a network node. The configuration message comprises one or more indications indicating whether one or more beams in a set of beams are allowed to be reported or not. The UE sends one or more beam prediction reports to the network node based on the configuration message.

[0016] The configuration message may be sent using Radio Resource Control (RRC) and / or Medium Access Control Control Element (MAC-CE) message or as part of CSI- ReportConfig or CSI-ResurceConfig information element, or as part of NZP-CSI-RS- ResourceSet information element.

[0017] The configuration message may comprise one or more of the following:• a N-bit bitmap or vector corresponding to N different beams in set A of the network node, wherein each bit in the bitmap / vector is set to a value to indicate whether the corresponding beam is allowed or not to be reported as a predicted beam in a beam prediction report;• a sequence or multiple sequences of beam Identifiers (IDs) for indicating whether beams having corresponding beam IDs in the sequence or multiple sequences of beam IDs are allowed or not to be reported as a predicted beam in a beam prediction report;• a set or range of angles for indicating whether beams having their corresponding angles in the set or range of angles are allowed or not to be reported as a predicted beam in a beam prediction report;• one or more indices representing rows and / or columns of 2D horizontal / azimuth grid for indicating whether beams having their corresponding rows and / or columns represented by the one or more indices are allowed or not to be reported as a predicted beam in a beam prediction report;• a set of tuples for indicating whether beams having their corresponding horizontal / vertical tuples included in the set of tuples are allowed or not to be reported as a predicted beam in a beam prediction report;• a list of Transmission Configuration Indicator (TCI) states for indicating whether beams associated with their corresponding TCI states in the list of TCI states are allowed or not to be reported as a predicted beam in a beam prediction report;• a MAC-CE containing N number of single -bit bitfields, where each of the single-bit bitfields indicates whether the associated beam is allowed or not to be reported as a predicted beam in a beam prediction report;• a MAC-CE containing X number of single-bit bitfields, wherein X is less than or equal to N different beams in set A of the network node, wherein each of the singlebit bitfields indicates whether the associated beam is allowed or not to be reported as a predicted beam in a beam prediction report;• Reference Signal Received Power (RSRP) offset for one or more beams for UE to determine which beams to include in the beam prediction report;• a list of 32 bitfields, where each bitfield is used to indicate RSRP offset for a corresponding beam;• a MAC-CE containing X pairs of bitfields, where each pair of bitfields indicates a beam index and an RSRP offset associated with indicated beam index.

[0018] The proposed solution provides some benefits such as:Avoiding interference in the network node specified directions.Avoiding UEs predict beams that are not feasible to transmit at the network node, e.g. due to hardware impairments.Reduce the risk that the UE to report beams that generate strong interference to other cells and / or to satellites.- Efficient signaling for restricted predicted beams.BRIEF DESCRIPTION OF THE DRAWINGS

[0019] Examples of embodiments herein are described in more detail with reference to attached drawings in which:

[0020] Figure 1 is a schematic diagram depicting an example of a grid-of-beam type radiation pattern where Set B beams are a subset of Set A beams;

[0021] Figure 2 is a schematic diagram depicting examples of Set B beams and Set A beams;

[0022] Figure 3 is a schematic block diagram depicting a wireless communication system;

[0023] Figure 4 is a signal flow diagram depicting example signaling between a network node and UE according to embodiments herein;

[0024] Figure 5 is a flowchart illustrating a method performed in a network node according to an embodiment herein;

[0025] Figure 6 is a flowchart illustrating a method performed in a UE according to an embodiment herein;

[0026] Figure 7 is a schematic block diagram illustrating an example embodiment of a network node; and

[0027] Figure 8 is a schematic block diagram illustrating an example embodiment of a communication device.DETAILED DESCRIPTION

[0028] It should be understood by the skilled in the art that “communication device” is a non-limiting term which means any terminal, wireless communication terminal, user equipment, Machine Type Communication (MTC) device, Device to Device (D2D) terminal, or node e.g. smart phone, laptop, mobile phone, sensor, relay, mobile tablets or even a small base station communicating within a cell.

[0029] The terms “communication device”, “wireless device”, “UE”, “user equipment”, “terminal equipment”, “wireless terminal” and “terminal” may be used interchangeably herein.

[0030] A network node may be a RAN node, a gNB, an eNB, an en-gNB, a ng-eNB, a gNB-CU, a gNB-CU-CP, a gNB-CU-UP, an eNB-CU, an eNB-CU-CP, an eNB-CU-UP, an lAB-node, an lAB-donor DU, an lAB-donor-CU, an IAB-DU, an IAB-MT, an O-CU, an O- CU-CP, an O-CU-UP, an O-DU, an O-RU, an O-eNB, a Non-Real Time RAN Intelligent Controller (Non-RT RIC), a Real-Time RAN Intelligent Controller (RT-RIC), an 0AM node,a Core Network node / function, a Cloud-based network function, a Cloud-based centralized training node, a node hosting NR PDCP etc.

[0031] Embodiments herein relate to communication networks in general. Figure 3 is a schematic overview depicting a communication network or system 300. The communication network 300 may be a wireless communication network comprising one or more RANs, and one or more CNs. The communication network 300 may use a number of different RATs, such as Wi-Fi, Long Term Evolution (LTE), LTE-Advanced, NR, Wideband Code Division Multiple Access (WCDMA), Global System for Mobile communications / enhanced Data rate for GSM Evolution (GSM / EDGE), Worldwide Interoperability for Microwave Access (WiMax), or Ultra Mobile Broadband (UMB), NR etc. just to mention a few possible implementations .

[0032] In the wireless communication network 300, one or more wireless communication devices 330, 331 such as a UE, a mobile station or a wireless terminal communicates via one or more Radio Access Networks (RANs) to one or more core networks (CNs).

[0033] Network nodes operate in the wireless communication network 300 such as a first network node 311, a second network node 312. The first and second network nodes 311, 312 may be any of RAN node, such as gNB, eNB, en-gNB, ng-eNB, gNB etc. The first network node 311 provides radio coverage over a geographical area, a service area 11, which may also be referred to as a beam or a beam group where the group of beams is covering the service area of a first radio access technology (RAT), such as 5G, LTE, Wi-Fi or similar. The second network node 312 provides radio coverage over a geographical area, a service area 12, which may also be referred to as a beam or a beam group where the group of beams is covering the service area of a second radio access technology (RAT), such as 5G, LTE, Wi-Fi or similar. It should be noted that a network node may be a RAN node, a CN node or an 0AM node.

[0034] The first / second network nodes 311 / 312 may be a transmission and reception point e.g. a radio access network node such as a Wireless Local Area Network (WLAN) access point or an Access Point Station (AP STA), an access controller, a base station, e.g. a radio base station such as a NodeB, a gNB, an evolved Node B (eNB, eNode B), a base transceiver station, a radio remote unit, an Access Point Base Station, a base station router, a transmission arrangement of a radio base station, a stand-alone access point or any other network unit capable of communicating with a wireless communication device within the service area served by the respective first / second network nodes 311 / 312 depending e.g. on the radio access technology and terminology used. The first and the second network nodes311 / 312 may be referred to as a source and a target network node, respectively, and may communicate with the wireless communication device 330, 331 with Downlink (DL) transmissions to the wireless communication device 330, 331 and Uplink (UL) transmissions from the wireless communication device 330, 331.

[0035] The network node 311 could refer to the gNB, e.g. the gNB-CU or the gNB-DU, the 0AM, or a core network node, e.g. the NWDAF. In the following the term network node can refer to any of the aforementioned entity.

[0036] Methods for enabling a UE, e.g. UE 330, to apply beam prediction subset restriction for predicted beams and / or determine which beams that are more undesirable than others may be implemented in a network node, e.g. the first or second network node 311 / 312.

[0037] Beam prediction capability reporting

[0038] In one embodiment, the network node 311 first needs to understand whether the UE 330 is capable of supporting the beam prediction subset restriction feature and apply the restrictions on beams that the UE can predict. This may be part of the capability report, for example the UE supports beam prediction subset restriction while predicting a set A of beams.

[0039] Representation of Set A of beams for UE reporting

[0040] According to some embodiments, UE may report the predicted beams within Set A using one of the following ways:

[0041] Each of the beams in the Set A of beams may be identified via an ID, for example having a unique ID for a certain global cell identifier. The ID may in one example comprise the nzp-CSI-RS-Resourceld defined in 3GPP standard TS38.331.

[0042] Another alternative is that set A are indicated via pointing angles, for example the horizontal and azimuth direction of the beam, as signaled from the network node to the UE during UE-sided model training.

[0043] Another alternative is that the beams are indexed as a 2D-grid of beams, for example the network node configures a UE with a horizontal beam index and vertical beam index, and the index is then reported as a tuple representation of a horizontal and vertical dimensions. Note that this assumes that the network node transmits beams in certain directions, where e,g, the azimuth pointing direction of a beam column index 0, is lower or higher, based on the definition, than a beam with column index 1. The UE can in this example indicate which horizontal and vertical index it supports, together with the time stamp of when the UE trained it.

[0044] Network Node indication of restricted beam prediction

[0045] In one embodiment, the network node may indicate using RRC and / or MAC-CE the set of beams the UE is not allowed to include in a beam prediction report. For example, assume the network node has N different beams in set A. Then, one or more of the following embodiments may be applicable.

[0046] In one embodiment, the network node may configure a N-bit bitmap or vector, wherein when the ithbit in the bitmap is set to a first value e.g., ‘ 1 ’ then the ithbeam among the N beams in set A is not allowed to be reported as a predicted beam in a beam prediction report, and when the ithbit in the bitmap is set to a second value e.g., ‘0’ then the ithbeam among the N beams in set A is allowed to be reported as a predicted beam in a beam prediction report.

[0047] In another embodiment, the network node may configure a sequence or multiple sequences of beam IDs wherein if the network node configures a given beam ID in the sequence or multiples sequences of beam IDs, then the beam corresponding to that beam ID is not allowed to be reported as a predicted beam in a beam prediction report. This means that beams corresponding to beam IDs that are not included in the sequence are allowed to be reported as a predicted beam in the beam prediction report. Alternatively, if the network node configures a given beam ID in the sequence or multiple sequences of beam IDs, then the beam corresponding to that beam ID is allowed to be reported as a predicted beam in the beam prediction report. This means that beams corresponding to beam IDs that are not included in the sequence are not allowed to be reported as a predicted beam in the beam prediction report.

[0048] In another embodiment, in case of beams in set A being represented by angles, the network node may configure a set or range of angles that are restricted, wherein the UE is not allowed to report beams in the beam prediction report that have their corresponding angles in the restricted set or range of angles. In an alternative embodiment, in case of beams in set A being represented by angles, the network node may configure a set or range of angles that are allowed, wherein the UE is allowed to report beams in the beam prediction report that have their corresponding angles in the allowed set or range of angles.

[0049] In another embodiment, in case of beams in set A being represented as a 2D horizontal / azimuth grid, the network node may configure one or more indices representing rows and / or columns that are restricted, wherein the UE is not allowed to report beams in the beam prediction report that correspond to the indices representing rows and / or columns that are restricted. In an alternative embodiment, in case of beams in set A being represented as a2D horizontal / azimuth grid, the network node may configure one or more indices representing rows and / or columns that are allowed, wherein the UE is allowed to report beams in the beam prediction report that correspond to the indices representing rows and / or columns that are restricted. The network node may also configure a set of tuples that the UE can or cannot include beams in the beam prediction report from, in case the beams are defined as a horizontal, vertical tuple.

[0050] In another embodiment, in case the Set A of beams are associated with Transmission Configuration Indicator (TCI) states, the network node may indicate a list of TCI states that are to be restricted, and where the Set A of beams associated with the indicated restricted TCI state(s) are not allowed to be included as predicted beam(s) in a beam prediction report. In an alternative embodiment, in case the Set A of beams are associated with TCI states, the network node may indicate a list of TCI states that are to be allowed, and where the Set A of beams associated with the indicated restricted TCI state(s) are allowed to be included as predicted beam(s) in a beam prediction report.

[0051] In another embodiment, the network node may indicate a MAC-CE containing, among other potential bitfields in the MAC-CE, N number of single-bit bitfields, where each of the single-bit bitfields can indicate if the associated beam is allowed to be included as a predicted beam in a beam prediction report or not, e.g. by setting it to a ‘0’ or a ‘ 1’ . For example, when the ithsingle-bit field in the MAC CE is set to a first value, e.g., ‘ 1’, then the ithbeam among the N beams in set A is not allowed to be reported as a predicted beam in a beam prediction report, and when the ithbit in the bitmap is set to a second value, e.g., ‘O’, then the ithbeam among the N beams in set A is allowed to be reported as a predicted beam in a beam prediction report.

[0052] In another embodiment, the network node may indicate a MAC-CE containing, among other potential bitfields in the MAC-CE, X number of bitfields where X can be less than or equal to N, where each bitfield indicate a beam index associated with a beam that is restricted. This means that the UE is not allowed to report beams corresponding to the indicated beam index(es) as predicted beams in the beam prediction report. In an alternative embodiment, the network node may indicate a MAC-CE containing, among other potential bitfields in the MAC-CE, X number of bitfields where X can be less than or equal to N, where each bitfield indicate a beam index associated with a beam that is allowed. This means that the UE is allowed to report beams corresponding to the indicated beam index(es) as predicted beams in the beam prediction report.

[0053] In another embodiment, the network node may configure a set of Set A beams that the UE can or cannot include in a beam prediction report based on the TCI state configuration. For example, the UE cannot include any set A beams that have a Quasi Co Location (QCL) relation to a certain set B beam, where the QCL relations are indicated via the TCI state configurations. In this embodiment, the network node indicates the one or more beams in set B, and the UE filters out the associated set A beams in the predicted set. This may be beneficial in case the network node would like to avoid transmitting all narrow beams that are pointing in the same direction as one or more wide set B beams.

[0054] In another related example, the network node may configure a set of Set A beams that the UE can or cannot include in a beam prediction report based on the TCI state configuration. For example, the UE cannot include any set A beams where it has not received any QCL relation to a certain set of B beams, or if it has not received any QCL relation to any other reference signal in the NW. This can be used by the network node to avoid receiving predictions on set A beams that have no TCI state defined and cannot be transmitted by the network node.

[0055] According to some embodiments, instead of totally restricting some beams of a beam prediction report, the UE may be configured to prioritize or de-prioritize some beams.

[0056] In one embodiment, for a beam prediction report where the UE predicts reference signal received power (RSRP) for the Set A of beams, the UE may be configured with a RSRP offset for one or more of the Set A of beams, and the UE should add this offset to the predicted RSRP when determining which beams to include in the beam prediction report. For example, after the RSRP offset has been added to the predicted RSRP, the UE can report the M beams with highest total RSRP, where the total RSRP is the predicted RSRP + the RSRP offset. In one embodiment, the RSRP offset can only be a zero or have negative values, which means that the beams configured with a RSRP offset should be de-prioritized by the UE. The network node may for example configure beams directed towards other cells and / or towards satellites with a negative RSRP offset value to reduce the chance that the UE reports these beams.

[0057] The network node may indicate using RRC and / or MAC-CE the set of beams the UE shall de-prioritize for a beam prediction report. For example, assume the network node has 32 different beams in Set A, the network node may:Configure a list of 32 bitfields, where each bitfield is used to indicate the RSRP offset for a corresponding beam;• Configure a MAC-CE containing, among other potential bitfields in the MAC- CE, X pairs of bitfields, where each pair of bitfields indicates a beam index and an RSRP offset associated with the indicated beam index.

[0058] In some embodiments, the network node may after having received a beam prediction report from the UE decide that the predicted beam is not good for transmission and request the UE to report a new beam, possibly based on the same original measurements as the first beam prediction report was based on. The network node may then provide instructions to the UE how the new beam prediction should be derived, e.g.• simply state that the UE must report a new beam;• state that the UE must report N additional beams, e.g. the N-l beams ranked 2. . . N best by the prediction algorithm;• state that it must be a beam which “belongs to” a different Set B beam and / or different SSB beam, where “belongs to” is defined e.g. as having had the same TCI state during training. The idea is that the new beam would then be significantly different from the first beam, which is likely desirable, since if the first beam was not suitable for transmission, then other beams with similar direction are probably also not good for transmission.

[0059] In one embodiment, for temporal beam prediction, the network node may configure the same or different Set A of beams prediction subset restrictions in different prediction time instance.

[0060] Differently from the above embodiments which focus on the restriction on UE beam prediction within Set A, some restrictions may be indicated to the UE on the Set B measurement. The network node may configure different RSRP offsets for some or all measured Set B beams. For example, when the network node finds some directions causing strong interference to other cells and / or satellites and some of Set B of beams are overlapped with such directions, the network node may indicate different RSRP offset to some or all Set B of beams. In one embodiment, - X dB may be applied to those Set B of beams causing interference and 0 dB to other “normal” Set B of beams. In another embodiment, during the training phase, in order to increase the model generalization at UE, the network node may also indicate negative RSRP offset to some Set A and Set B of beams which are overlapping with some directions causing strong interference to other cells and / or satellites. Then, the network node may do a similar indication to the UE during the inference phase, which also increases the consistency between training and inference.

[0061] In one embodiment, for temporal beam prediction, the network node may configure same or different RSRP offsets for Set B beam measurement in different time instances, where such Set B of beams in each time instance are partially or heavily overlapping with the directions causing strong interference to other cells and / or satellites.

[0062] Some optional embodiments on restricted beams conditioned on certain events.

[0063] Predicted strength: In case none of the predicted beams that are not restricted is above a certain signal quality threshold. The UE can indicate a beam that is part of the restricted beams.

[0064] Confidence of prediction: In case the UE is uncertain on the prediction for the non-restricted beams. The UE can include predictions of the restricted beams, the network node can use this information to configure another beam in vicinity of such beam that are valid.

[0065] Past events: If a certain beam has led to significant events, e.g., link-failure for a UE when communicating from a specific geographical location, a certain number of times taken over a certain number of recent prediction windows, both of which may be preconfigured, the beam is added to the restricted set of the UEs approaching this geographical area.

[0066] Network node’s cell-level knowledge: It is likely that the restricted set of beams is different across UEs. By optimizing cell-level metrics, e.g., cell-level throughput, the network node can add / remove one or more beams for a UE in its restricted set of beams.These beams can in principle belong to the UE’s non-restricted set of beams, but due to the network strategy, e.g., avoid high interference for collocated Multi-User Multiple Input Multiple Output (MU-MIMO) UEs, they are placed in the restricted set.

[0067] Temporary event: If a temporary event is held in a stadium, the network node may apply the beam prediction of Set A beams pointing to the directions towards the stadium for few hours in order to avoid strong interference. But after a few hours, such restriction should be removed once the temporary event disappeared. Under such temporary event, it is not good for the network to apply the restricted set during the whole training phase and do the same restriction in the inference phase. Instead, the network node may indicate the RSRP offset on Set B measurements as described in the previous section during the training phase to enhance the model generalization. Then, in the inference phase, the network node may do the similar indication for Set B measurement to solve the restricted set caused by temporary event.

[0068] Signaling examples

[0069] In one example embodiment, the UE beam prediction restriction may be signaled via RRC from the network node to the UE. Figure 4 shows an example of signaling between a network node, e.g. the network node 311 and a UE e.g. UE 330 for handling beam prediction reporting, which may comprise the following steps.

[0070] 400: The network node 311 configures the restricted beams. The network node311 may have N different beams in set A of beams. The network node 311 may configure a subset of Set A beams or Set B beams as restricted beams which are not allowed to be reported as a predicted beam or not to be included in the beam prediction report.

[0071] 401: The network node 311 may send a first request to the UE to request information on capability of supporting and applying beam prediction restriction on a set of beams.

[0072] 402: The network node 311 may receive one or more indications from the UE 330 indicating the capability of supporting and applying beam prediction restriction on a set of beams.

[0073] 403: The network node 311 sends a configuration message to one or more UEs330, 331 for configuring beam prediction reporting for the one or more UEs 330, 331, wherein the configuration message comprises one or more indications indicating whether one or more beams in a set of beams are allowed to be reported or not.

[0074] 404: UE 330 performs beam prediction and prepares beam prediction reports based on the configuration message for beam prediction reporting.

[0075] 405: The network node 311 receives one or more beam prediction reports from the one or more UEs 330, 331.

[0076] 406: The network node 311 may send a second request to UE 330 to request a beam prediction report on one or more additional beams different from previously reported beams.

[0077] 407: The network node 311 may receive one or more beam prediction reports from the one or more UEs 330, 33 Ion the one or more additional beams.

[0078] The UE beam prediction restriction may be signaled as part of the CSI- ReportConfig information element where the changes needed to introduce the beam prediction restriction field, i.e., Beam-Prediction-Restriction-rl9 over the CSI- ReportConfig information element currently specified in 3GPP TS 38.331 V18.0.0 are given in bold face font. This example corresponds to the case where Beam-Prediction- Restriction-rl9 is a bitmap and there are 64 beams in set A and each bit in Beam-Prediction-Restriction-rl9 is used to indicate whether or not a corresponding beam in set A is allowed to be reported as discussed in the above embodiments.CSI-ReportConfig information element— — ASN1START— — TAG-CSI -REPORTCONFIG-START CSI -ReportConfig : : = SEQUENCE { re ortConfigld CS I-ReportConfig Id , carrier ServCell lndex OPT IONAL , -- Need S resources ForChannelMeasurement CS I -Re sourceConfig Id , csi-IM-esources Forlnterference CS I-ResourceConf igld OPT IONAL ,-- Need R nzp-CS I -RS -Re sources For Interference CSI -ResourceConf igld OPTIONAL ,-- Need R• • • r[ [Beam-Prediction-Restriction-rl9 BIT STRING (SIZE ( 64 ) ) OPT IONAL , -- Need R ] 1 ,• • • r— TAG-CS I-REPORTCONFIG-STOP— ASN1 STOP

[0079] A method performed by a network node e.g. the first network node 311 for configurating beam prediction reporting for a UE 330 to report beam prediction report in a wireless communication system 300 will be described with reference to Figure 5. The method comprises the following actions which may be performed in any suitable order and some of the actions are optional.

[0080] Action 500

[0081] The network node 311 may configure a subset of Set A beams or Set B beams as restricted beams which are not allowed to be reported as a predicted beam or not to be included in the beam prediction report. The network node 311 may have N different beams in set A of beams.

[0082] For temporal beam prediction, the network node 311 may configure, in Action 501, same or different subset of restricted or allowed beams for Set A beams in different prediction time instance; or configure, in Action 502, different RSRP offsets for some or all measured Set B beams during training and / or inference phase; or configure, in Action 503, same or different RSRP offsets for Set B beams measurement in different time instances, in case Set B beams in each time instance are partially or heavily overlapping with the directions causing strong interference to other cells and / or satellites.

[0083] When a certain beam has caused significant events or link-failures to happen a certain number of times taken over a certain number of recent prediction windows for a UE communicating from a specific geographical location, the network node 311 may configure, in Action 504, the beam as restricted beams not to be included in the beam prediction report for one or more UEs 330, 331 approaching this geographical area.

[0084] The network node 311 may configure, in Action 505, different sets of beams as restricted beams not to be included in the beam prediction report for different UEs 330, 331. It is likely that the restricted set is different across UEs. By optimizing cell-level metrics e.g., cell-level throughput, the network node 311 may add or remove one or more beams for a UE in its restricted set. These beams can in principle belong to the UE’s non-restricted set, but due to the NW’s strategy e.g., avoid high interference for collocated MU-MIMO UEs, they are placed in the restricted set.

[0085] Action 510

[0086] In order to let the network node 311 understands whether a UE 330, 331 is capable to support the beam prediction subset restriction feature and apply the restrictions on beams that the UE can predict, the network node 311 may send a first request to one or more UEs 330, 331 to request information on capability of supporting and applying beam prediction restriction on a set of beams.

[0087] Action 520

[0088] The network node 311 may receive one or more indications from the UE 330, 331 indicating the capability of supporting and applying beam prediction restriction on a set of beams.

[0089] Action 530

[0090] The network node 311 sends a configuration message to one or more UEs 330, 331 for configuring beam prediction reporting for the one or more UEs 330, 331, wherein the configuration message comprises one or more indications indicating whether one or more beams in a set of beams are allowed to be reported or not.

[0091] Action 540

[0092] The network node 311 receives one or more beam prediction reports, e.g. a first report, from the one or more UEs 330, 331.

[0093] Action 550

[0094] In some embodiments, the network node 311 may, after having received a beam prediction report from the UE 330, 331, decide that the predicted beam is not good for transmission and request the UE 330, 331 to report a new beam, possibly based on the sameoriginal measurements as the first beam prediction report was based on. The network node 311 may then provide instructions to the UE 330, 331 on how the new beam prediction should be derived. Therefore, the network node 331 may send a second request to the UE 330, 331 to request a beam prediction report on one or more additional beams different from previously reported beams. The second request may comprise any one of the following:• simply state that the UE 330, 331 must report a new beam;• state that the UE 330,331 must report N additional beams, e.g. the N-l beams ranked 2. . . N best by the prediction algorithm;• state that it must be a beam which “belongs to” a different Set B beams and / or different SSB beams, where “belongs to” is defined as having had the same TCI state during training. The idea is that the new beam would then be significantly different from the first beam, which is likely desirable, since if the first beam was not suitable for transmission, then other beams with similar direction are probably also not good for transmission.

[0095] Action 560

[0096] The network node 311 may receive one or more beam prediction reports, e.g. a 2ndreport, from the one or more UEs 330, 331 on the one or more additional beams.

[0097] The configuration message may be sent using at least one of RRC and MAC-CE messages. The configuration message may be sent as part of Channel State Information Report Configuration, CSI-ReportConfig, information element. For each CSI Resource Configuration, csi-ResourceConfig, information element which is part of the CSI- ReportConfig information element, a bit is set to a value to indicate whether all beams in the corresponding CSI Resource Configuration identifier, csi-ResourceConfigID, information element are allowed or not to be reported as a predicted beam in a beam prediction report.

[0098] The configuration message may be sent as part of CSI-ResurceConfig information element, wherein for each Resource Set, resourceSet, information element which is part of the CSI-ResouceConfig information element, a bit is set to a value to indicate whether all beams in the corresponding Resource Set identifier, resourceSetID, information element are allowed or not to be reported as a predicted beam in a beam prediction report.

[0099] The configuration message may be sent as part of Non-Zero Power Channel State Information Reference Signal Resource Set, NZP-CSI-RS-ResourceSet, information element, wherein for each NZP-CSI-RS-Resource information element, a bit is set to a value toindicate whether a beam with the corresponding NZP-CSI-RS-Resource Identifier, NZP-CSI- RS-ResourcelD, is allowed or not to be reported as a predicted beam in a beam prediction report.

[0100] The configuration message may comprise one or more of the following:• a N-bit bitmap or vector corresponding to N different beams in set A beams of the network node 311, wherein each bit in the bitmap or vector is set to a value to indicate whether the corresponding beam is allowed or not to be reported as a predicted beam in a beam prediction report;• a sequence or multiple sequences of beam IDs for indicating whether beams having corresponding beam IDs in the sequence or multiple sequences of beam IDs are allowed or not to be reported as a predicted beam in a beam prediction report;• a set or range of angles for indicating whether beams having their corresponding angles in the set or range of angles are allowed or not to be reported as a predicted beam in a beam prediction report;• one or more indices representing rows and / or columns of 2D horizontal / azimuth grid for indicating whether beams having their corresponding rows and / or columns represented by the one or more indices are allowed or not to be reported as a predicted beam in a beam prediction report;• a set of tuples for indicating whether beams having their corresponding horizontal / vertical tuples included in the set of tuples are allowed or not to be reported as a predicted beam in a beam prediction report;• a list of Transmission Configuration Indicator (TCI) states for indicating whether beams associated with their corresponding TCI states in the list of TCI states are allowed or not to be reported as a predicted beam in a beam prediction report;• a MAC-CE containing N number of single -bit bitfields, where each of the single-bit bitfields indicates whether the associated beam is allowed or not to be reported as a predicted beam in a beam prediction report;• a MAC-CE containing X number of single-bit bitfields, wherein X is less than or equal to the N different beams in set A beams of the network node, wherein each of the single-bit bitfields indicates whether the associated beam is allowed or not to be reported as a predicted beam in a beam prediction report;• RSRP offset for one or more beams for UE to determine which beams to include in the beam prediction report;• a list of 32 bitfields, where each bitfield is used to indicate RSRP offset for a corresponding beam;• a MAC-CE containing X pairs of bitfields, where each pair of bitfields indicates a beam index and an RSRP offset associated with indicated beam index.

[0101] A method performed by a UE, e.g. UE 330, for beam prediction reporting in a wireless communication system 300 will be described with reference to Figure 6. The method comprises the following actions which may be performed in any suitable order and some of the actions are optional.

[0102] Action 610

[0103] The UE 330 may receive a first request from the network node 311 for reporting capability of supporting and applying beam prediction restriction on a set of beams.

[0104] Action 620

[0105] The UE 330 may send one or more indications to the network node 311 for indicating the capability of supporting and applying beam prediction restriction on a set of beams.

[0106] Action 630

[0107] The UE 330 receives a configuration message from the network node 311, wherein the configuration message comprises one or more indications indicating whether one or more beams in a set of beams are allowed to be reported or not.

[0108] Action 640

[0109] The UE 330 sends one or more beam prediction reports, e.g. a 1streport, to the network node 311 based on the configuration message.

[0110] Action 650

[0111] The UE 330 may receive a second request from the network node 311 for reporting a beam prediction on one or more additional beams different from previously reported beams.

[0112] Action 660

[0113] The UE 330 may send one or more beam prediction reports, e.g. a second report, to the network node 311 based on the second request.

[0114] To perform the method in the network node, e.g. the network node 311, the network node 311 may comprise modules or functions as shown in Figure 7. The network node 311 may comprise a receiving module 710, a transmitting module 720, a determining module 730, a processing module 740, a memory 750 etc.

[0115] The network node 311 is configured to perform any one of the Actions 500-560 described above.

[0116] For example, the network node 311 is configured to send a configuration message to one or more UEs 330, 331, for configuring beam prediction reporting for the one or more UEs 330, 331. The configuration message comprises one or more indications indicating whether one or more beams in a set of beams are allowed to be reported or not.

[0117] The network node 311 is further configured to receive one or more beam prediction reports from the one or more UEs 330, 331.

[0118] The methods according to embodiments herein may be implemented through one or more processors, such as the processor 760 in the network node 311 together with computer program code for performing the functions and actions of the embodiments herein. The program code mentioned above may also be provided as a computer program product, for instance in the form of computer readable medium or a data carrier 780 carrying computer program code 770, as shown in Figure 7, for performing the embodiments herein when being loaded into the network node 311. One such carrier may be in the form of a CD ROM disc. It is however feasible with other data carriers such as a memory stick. The computer program code may furthermore be provided as pure program code on a server or a cloud and downloaded to the network node 311.

[0119] To perform the method in a communication device, e.g. UE 330, the UE 330 may comprise modules or functions as shown in Figure 8. The UE 330 may comprise a receiving module 810, a transmitting module 820, a determining module 830, a processing module 840, a memory 850 etc.

[0120] The UE 330 is configured to perform any one of the Actions 610-660 described above.

[0121] For example, the UE 330 is configured to receive a configuration message from a network node 311. The configuration message comprises one or more indications indicating whether one or more beams in a set of beams are allowed to be reported or not.

[0122] The UE 330 is further configured to send one or more beam prediction reports to the network node 311 based on the configuration message.

[0123] The methods according to embodiments herein may be implemented through one or more processors, such as the processor 860 in the communication device UE 330 together with computer program code for performing the functions and actions of the embodiments herein. The program code mentioned above may also be provided as a computer program product, for instance in the form of computer readable medium or a data carrier 880 carryingcomputer program code 870, as shown in Figure 8, for performing the embodiments herein when being loaded into the communication device UE 330. One such carrier may be in the form of a CD ROM disc. It is however feasible with other data carriers such as a memory stick. The computer program code may furthermore be provided as pure program code on a server or a cloud and downloaded to the communication device UE 330.EXAMPLE EMBODIMENTS1. A method performed in a network node (311) for configuring beam prediction reporting for one or more user equipment, UE, in a wireless communication network, the method comprising: sending (530) a configuration message to one or more UEs for configuring beam prediction reporting for the one or more UEs, wherein the configuration message comprises one or more indications indicating whether one or more beams in a set of beams are allowed to be reported or not; receiving (540, 560) one or more beam prediction reports from the one or more UEs.2. The method according to Embodiment 1, further comprising configuring (500) a subset of Set A beams or Set B beams as restricted beams which are not allowed to be reported as a predicted beam or not to be included in the beam prediction report.3. The method according to any one of Embodiments 1-2, further comprising: sending (510) a first request to one or more UEs to request information on capability of supporting and applying beam prediction restriction on a set of beams; receiving (520) one or more indications from the one or more UEs indicating the capability of supporting and applying beam prediction restriction on a set of beams.4. The method according to any one of Embodiments 1-3, further comprising: sending (550) a second request to one or more UEs to request a beam prediction report on one or more additional beams different from previously reported beams; receiving (560) one or more beam prediction reports from the one or more UEs on the one or more additional beams.5. A method performed in a user equipment, UE, for reporting beam prediction in a wireless communication network, the method comprising: receiving (630) a configuration message from a network node, wherein the configuration message comprises one or more indications indicating whether one or more beams in a set of beams are allowed to be reported or not; sending (640, 660) one or more beam prediction reports to the network node based on the configuration message.6. The method according to Embodiment 5, further comprising: receiving (610) a first request from the network node for reporting capability of supporting and applying beam prediction restriction on a set of beams; sending (620) one or more indications to the network node for indicating the capability of supporting and applying beam prediction restriction on a set of beams.7. The method according to any one of Embodiments 5-6, further comprising: receiving (650) a second request from the network node for reporting a beam prediction on one or more additional beams different from previously reported beams; sending (660) one or more beam prediction reports to the network node based on the second request.8. The method according to any one of Embodiments 5-7, further comprising any one or more of the following: sending a beam prediction report indicating a beam that is part of the restricted beams when none of the predicted beams that are not restricted is above a certain signal quality threshold; sending a beam prediction report including predictions of the restricted beams when the UE is uncertain on the prediction for the non-restricted beams.9. The method according to any one of preceding Embodiments, wherein the configuration message is sent using RRC and / or MAC-CE message.The method according to any one of preceding Embodiments, wherein the configuration message is sent as part of CSI-ReportConfig information element. The method according to Embodiment 10, wherein for each csi-ResourceConfig which is part of the CSI-ReportConfig information element, a bit is set to a value to indicate whether all beams in the corresponding csi-ResourceConfigID are allowed or not to be reported as a predicted beam in a beam prediction report. The method according to any one of preceding Embodiments, wherein the configuration message is sent as part of CSI-ResurceConfig information element, wherein for each resourceSet which is part of CSI-ResouceConfig information element, a bit is set to a value to indicate whether all beams in the corresponding resourceSetID are allowed or not to be reported as a predicted beam in a beam prediction report. The method according to any one of preceding Embodiments, wherein the configuration message is sent as part of NZP-CSI-RS-ResourceSet information element, wherein for each NZP-CSI-RS-Resource, a bit is set to a value to indicate whether beam with the corresponding NZP-CSI-RS-ResourcelD is allowed or not to be reported as a predicted beam in a beam prediction report. The method according to any one of preceding Embodiments, wherein the configuration message comprises one or more of the following: a N-bit bitmap or vector corresponding to N different beams in set A of the network node, wherein each bit in the bitmap / vector is set to a value to indicate whether the corresponding beam is allowed or not to be reported as a predicted beam in a beam prediction report; a sequence or multiple sequences of beam IDs for indicating whether beams having corresponding beam IDs in the sequence or multiple sequences of beam IDs are allowed or not to be reported as a predicted beam in a beam prediction report; a set or range of angles for indicating whether beams having their corresponding angles in the set or range of angles are allowed or not to be reported as a predicted beam in a beam prediction report; one or more indices representing rows and / or columns of 2D horizontal / azimuth grid for indicating whether beams having their corresponding rowsand / or columns represented by the one or more indices are allowed or not to be reported as a predicted beam in a beam prediction report; a set of tuples for indicating whether beams having their corresponding horizontal / vertical tuples included in the set of tuples are allowed or not to be reported as a predicted beam in a beam prediction report; a list of Transmission Configuration Indicator, TCI, states for indicating whether beams associated with their corresponding TCI states in the list of TCI states are allowed or not to be reported as a predicted beam in a beam prediction report; an indication that the UE cannot use any beams in set A of beams where it have not received a QCL relation as part of the TCI configurations; a MAC-CE containing N number of single -bit bitfields, where each of the single-bit bitfields indicates whether the associated beam is allowed or not to be reported as a predicted beam in a beam prediction report; a MAC-CE containing X number of single -bit bitfields, wherein X is less than or equal to the N different beams in set A of the network node, wherein each of the single-bit bitfields indicates whether the associated beam is allowed or not to be reported as a predicted beam in a beam prediction report;RSRP offset for one of more beams for UE to determine which beams to include in the beam prediction report; a list of 32 bitfields, where each bitfield is used to indicate RSRP offset for a corresponding beam; a MAC-CE containing X pairs of bitfields, where each pair of bitfields indicates a beam index and an RSRP offset associated with indicated beam index. The method according to any one of preceding Embodiments, wherein for temporal beam prediction, the method further comprises one or more of the following: configuring same or different subset of restricted or allowed beams for Set A of beams in different prediction time instance; configuring different RSRP offsets for some or all measured Set B beams during training and / or inference phase; configuring same or different RSRP offsets for Set B beam measurement in different time instances.The method according to any one of preceding Embodiments, wherein when a certain beam has caused significant events or link-failures to happen a certain number of times taken over a certain number of recent prediction windows for a UE communicating from a specific geographical location, the network node configures the beam as restricted beams not to be included in the beam prediction report for one or more UEs approaching this geographical area. The method according to any one of preceding Embodiments, wherein the network node configures different set of beams as restricted beams not to be included in the beam prediction report for different UEs. The method according to any one of preceding Embodiments, wherein predicted beams are reported by one of the following ways: beams ID, where each of the beams in the set A of beams is identified via an ID, for example via a NZP-CSI-RS-ResourcelD;CSI-RS Resource Indicator, CRI, where each of the beams in the set A of beams is identified via a CRI, and the CRI indicates the best resource in the network node configured resources in NZP-CSI-RS-ResourceSet; pointing angles or horizontal and azimuth directions, wherein the set A of beams are indicated via pointing angles or the horizontal and azimuth directions; a horizontal beam index and vertical beam index, wherein the set A of beams are indexed as a 2D-grid of beams with horizontal and vertical indexes.

Claims

Claims1. A method performed in a network node (311) for configuring beam prediction reporting for one or more user equipment, UE (330, 331), in a wireless communication network (300), the method comprising: sending (530) a configuration message to one or more UEs (330, 331), for configuring beam prediction reporting for the one or more UEs (330, 331), wherein the configuration message comprises one or more indications indicating whether one or more beams in a set of beams are allowed to be reported or not; receiving (540, 560) one or more beam prediction reports from the one or more UEs (330, 331).

2. The method according to Claim 1, further comprising configuring (500) a subset of Set A beams or Set B beams as restricted beams which are not allowed to be reported as a predicted beam or not to be included in a beam prediction report.

3. The method according to Claim 1, wherein for temporal beam prediction, configuring (500) a subset of Set A beams or Set B beams as restricted beams comprises one or more of the following: configuring (501) the same or different subset of restricted or allowed beams for Set A beams in different prediction time instance; configuring (502) different Reference Signal Received Power, RSRP, offsets for some or all measured Set B beams during training and / or inference phase; configuring (503) the same or different Reference Signal Received Power, RSRP, offsets for Set B beams measurement in different time instances.

4. The method according to Claim 1, wherein configuring (500) a subset of Set A beams or Set B beams as restricted beams comprises configuring (504) a beam as restricted beams not to be included in the beam prediction report for one or more UEs (330, 331) approaching a geographical area, when this beam has caused events or linkfailures to happen a certain number of times taken over a certain number of recent prediction windows for a UE (330, 331) communicating from the geographical area.

5. The method according to Claim 1, configuring (500) a subset of Set A beams or Set B beams as restricted beams comprises configuring (505) different sets of beams asrestricted beams not to be included in the beam prediction report for different UEs (330, 331).

6. The method according to any one of Claims 1-5, further comprising: sending (510) a first request to one or more UEs (330, 331), to request information on capability of supporting and applying beam prediction restriction on a set of beams; receiving (520) one or more indications from the one or more UEs (330, 331) indicating the capability of supporting and applying beam prediction restriction on a set of beams.

7. The method according to any one of Claims 1-6, further comprising: sending (550) a second request to one or more UEs (330, 331) to request a beam prediction report on one or more additional beams different from previously reported beams; receiving (560) one or more beam prediction reports from the one or more UEs (330, 331) on the one or more additional beams.

8. The method according to any one of Claims 1-7, wherein the configuration message is sent using at least one of a Radio Resource Control, RRC message and a Medium Access Control Control Element, MAC-CE, message.

9. The method according to any one of any one of Claims 1-7, wherein the configuration message is sent as part of Channel State Information Report Configuration, CSI- ReportConfig, information element.

10. The method according to Claim 9, wherein for each CSI Resource Configuration, csi- ResourceConfig, information element which is part of the CSI-ReportConfig information element, a bit is set to a value to indicate whether all beams with the corresponding CSI Resource Configuration identifier, csi-ResourceConfigID, are allowed or not to be reported as a predicted beam in a beam prediction report.

11. The method according to any one of any one of Claims 1-7, wherein the configuration message is sent as part of CSI Resource Configuration, CSI-ResurceConfig,information element, wherein for each Resource Set, resourceSet, information element which is part of CSI-ResouceConfig information element, a bit is set to a value to indicate whether all beams with the corresponding Resource Set identifier, resourceSetID, are allowed or not to be reported as a predicted beam in a beam prediction report.

12. The method according to any one of Claims 1-7, wherein the configuration message is sent as part of Non-Zero Power Channel State Information Reference Signal Resource Set, NZP-CSI-RS-ResourceSet, information element, wherein for each NZP-CSI-RS- Resource information element, a bit is set to a value to indicate whether a beam with the corresponding NZP-CSI-RS-Resource Identifier, NZP-CSI-RS-ResourcelD, is allowed or not to be reported as a predicted beam in a beam prediction report.

13. The method according to any one of preceding Claims, wherein the configuration message comprises one or more of the following: a) a N-bit bitmap or vector corresponding to N different beams in set A beams of the network node (311), wherein each bit in the bitmap or vector is set to a value to indicate whether the corresponding beam is allowed or not to be reported as a predicted beam in a beam prediction report; b) a sequence or multiple sequences of beam identifiers, IDs, for indicating whether beams having corresponding beam IDs in the sequence or multiple sequences of beam IDs are allowed or not to be reported as a predicted beam in a beam prediction report; c) a set or range of angles for indicating whether beams having their corresponding angles in the set or range of angles are allowed or not to be reported as a predicted beam in a beam prediction report; d) one or more indices representing rows and / or columns of two- dimensional, 2D, horizontal / azimuth grid for indicating whether beams having their corresponding rows and / or columns represented by the one or more indices are allowed or not to be reported as a predicted beam in a beam prediction report; e) a set of tuples for indicating whether beams having their corresponding horizontal / vertical tuples included in the set of tuples are allowed or notto be reported as a predicted beam in a beam prediction report; f) a list of Transmission Configuration Indicator, TCI, states for indicating whether beams associated with their corresponding TCI states in the list of TCI states are allowed or not to be reported as a predicted beam in a beam prediction report; g) an indication that the UE (330, 331) cannot use any beams in set A of beams where it have not received a Quasi Co-Location, QCL, relation as part of the TCI configurations; h) a Medium Access Control Control Element, MAC-CE, containing N number of single-bit bitfields, where each of the single -bit bitfields indicates whether the associated beam is allowed or not to be reported as a predicted beam in a beam prediction report; i) a Medium Access Control Control Element, MAC-CE, containing X number of single-bit bitfields, wherein X is less than or equal to the N different beams in set A beams of the network node (311), wherein each of the single-bit bitfields indicates whether the associated beam is allowed or not to be reported as a predicted beam in a beam prediction report; j) Reference Signal Received Power, RSRP, offset for one or more beams for UE (330, 331) to determine which beams to include in the beam prediction report; k) a list of 32 bitfields, where each bitfield is used to indicate a Reference Signal Received Power, RSRP, offset for a corresponding beam; l) a Medium Access Control Control Element, MAC-CE, containing X pairs of bitfields, where each pair of bitfields indicates a beam index and a Reference Signal Received Power, RSRP, offset associated with indicated beam index.

14. A method performed in a user equipment, UE (330, 331), for reporting beam prediction in a wireless communication network (300), the method comprising: receiving (630) a configuration message from a network node (311), wherein the configuration message comprises one or more indications indicating whether one or more beams in a set of beams are allowed to be reported or not; sending (640, 660) one or more beam prediction reports to the network node(311) based on the configuration message.

15. The method according to Claim 14, further comprising: receiving (610) a first request from the network node (311) for reporting capability of supporting and applying beam prediction restriction on a set of beams; sending (620) one or more indications to the network node (311) for indicating the capability of supporting and applying beam prediction restriction on a set of beams.

16. The method according to any one of Claims 14-15, further comprising: receiving (650) a second request from the network node (311) for reporting a beam prediction on one or more additional beams different from previously reported beams; sending (660) one or more beam prediction reports to the network node (311) based on the second request.

17. The method according to any one of Claims 14-16, further comprising any one or more of the following: sending (670) a beam prediction report indicating a beam that is part of the restricted beams when none of the predicted beams that are not restricted is above a certain signal quality threshold; sending (680) a beam prediction report including predictions of the restricted beams when the UE (330) is uncertain on the prediction for the non-restricted beams.

18. The method according to any one of Claims 14-17, wherein the configuration message comprises one or more of the following: a) a N-bit bitmap or vector corresponding to N different beams in set A of beams of the network node (311), wherein each bit in the bitmap or vector is set to a value to indicate whether the corresponding beam is allowed or not to be reported as a predicted beam in a beam prediction report; b) a sequence or multiple sequences of beam identifiers, IDs, for indicating whether beams having corresponding beam IDs in the sequence or multiple sequences of beam IDs are allowed or not to bereported as a predicted beam in a beam prediction report; c) a set or range of angles for indicating whether beams having their corresponding angles in the set or range of angles are allowed or not to be reported as a predicted beam in a beam prediction report; d) one or more indices representing rows and / or columns of two- dimensional, 2D, horizontal / azimuth grid for indicating whether beams having their corresponding rows and / or columns represented by the one or more indices are allowed or not to be reported as a predicted beam in a beam prediction report; e) a set of tuples for indicating whether beams having their corresponding horizontal / vertical tuples included in the set of tuples are allowed or not to be reported as a predicted beam in a beam prediction report; f) a list of Transmission Configuration Indicator, TCI, states for indicating whether beams associated with their corresponding TCI states in the list of TCI states are allowed or not to be reported as a predicted beam in a beam prediction report; g) an indication that the UE (330, 331) cannot use any beams in set A of beams where it have not received a Quasi Co-Location, QCL, relation as part of the TCI configurations; h) a Medium Access Control Control Element, MAC-CE, containing N number of single-bit bitfields, where each of the single -bit bitfields indicates whether the associated beam is allowed or not to be reported as a predicted beam in a beam prediction report; i) a Medium Access Control Control Element, MAC-CE, containing X number of single-bit bitfields, wherein X is less than or equal to the N different beams in set A beams of the network node (311), wherein each of the single-bit bitfields indicates whether the associated beam is allowed or not to be reported as a predicted beam in a beam prediction report; j) Reference Signal Received Power, RSRP, offset for one or more beams for UE (330, 331) to determine which beams to include in the beam prediction report; k) a list of 32 bitfields, where each bitfield is used to indicate a Reference Signal Received Power, RSRP, offset for a corresponding beam;1) a Medium Access Control Control Element, MAC-CE, containing X pairs of bitfields, where each pair of bitfields indicates a beam index and a Reference Signal Received Power, RSRP, offset associated with indicated beam index.

19. The method according to any one of Claims 14-18, wherein sending (640, 660) one or more beam prediction reports comprises sending predicted beams by one of the following: a) beams identifier, ID, where each of the beams in the set A of beams is identified via an ID; b) Channel State Information Reference Signal Resource Indicator, CRI, where each of the beams in the set A of beams is identified via a CRI, and the CRI indicates the best resource in the network node (311) configured resources in Non-Zero Power Channel State Information Reference Signal Resource Set, NZP-CSI-RS-ResourceSet; c) pointing angles or horizontal and azimuth directions, wherein each of the beams in the set A of beams are indicated via pointing angles or the horizontal and azimuth directions; d) a horizontal beam index and vertical beam index, wherein each of the beams in the set A of beams are indexed as a 2D-grid of beams with horizontal and vertical indexes.

20. A network node (311) configured to perform the method for configuring beam prediction reporting according to any one of Claims 1-13.

21. A user equipment, UE (330, 331), configured to perform the method for reporting beam prediction according to any one of Claims 14-19.

Images