Patent Description:
For example, for future generations of mobile communications networks, frequency bands at many different carrier frequencies could be needed. For example, low such frequency bands could be needed to achieve sufficient network coverage for wireless devices and higher frequency bands (e.g. at millimeter wavelengths (mmW), i.e. near and above <NUM>) could be needed to reach required network capacity. In general terms, at high frequencies the propagation properties of the radio channel are more challenging and beamforming both at the network node of the network and at the wireless devices might be required to reach a sufficient link budget.

Narrow beam transmission and reception schemes might be needed at such high frequencies to compensate the expected high propagation loss. For a given communication link, a respective beam can be applied at both the network-end (as represented by a network node or its transmission and reception point, TRP) and at the terminal-end (as represented by a terminal device), which typically is referred to as a beam pair link (BPL). One task of the beam management procedure is to discover and maintain beam pair links. A BPL (i.e. both the beam used by the network node and the beam used by the terminal device) is expected to be discovered and monitored by the network using measurements on downlink reference signals, such as channel state information reference signals (CSI-RS) or synchronization signal block (SSB) signals, used for beam management.

The CSI-RS for beam management can be transmitted periodically, semi-persistently or aperiodically (event triggered) and they can be either shared between multiple terminal devices or be device-specific. The SSB are transmitted periodically and are shared for all terminal devices. In order for the terminal device to find a suitable network node beam, the network node transmits the reference signal in different transmission (TX) beams on which the terminal device performs measurements, such as reference signal received power (RSRP), and reports back the M best TX beams (where M can be configured by the network). Furthermore, the transmission of the reference signal on a given TX beam can be repeated to allow the terminal device to evaluate a suitable reception (RX) beam. Reference signals that are shared between all terminal devices served by the TRP might be used to determine a first coarse direction for the terminal devices. It could be suitable for such a periodic TX beam sweep at the TRP to use SSB as the reference signal. One reason for this is that SSB are anyway transmitted periodically (for initial access/synchronization purposes) and SSBs are also expected to be beamformed at higher frequencies to overcome the higher propagation losses noted above.

In the term spatial quasi-location (QCL) generally refers to a relationship between the antenna port(s) of two different downlink reference signals (RSs). If two transmitted downlink RSs are configured by the network to be spatially QCL at the receiver of the terminal device, then the terminal device might assume that these two reference signals are transmitted with approximately the same spatial filter configuration at the TRP. Thus, the terminal device might then use approximately the same spatial filter configuration at its receiver to receive the second of these reference signals as it used to receive the first of these reference signals. In this way, spatial QCL is a term that assists in the use of analog beamforming and formalizes the notion of same receive beam at the terminal device over different time instances.

TRPs having an analog beamforming implementation are enabled to only transmit in one beam at a time. If the beams are narrow, this reduces the possibility to serve multiple terminal devices simultaneously (by e.g. using frequency multiplexing) since it is rather unlikely that two terminal devices to which data is to be transmitted are served in the same beam. Further, the transmission (as well as reception) of data might be bursty and dominated by small packets. Particularly when the TRP has an analog beamforming implementation and serves terminal devices that transmit/receive small packets in a bursty fashion, the TRP will soon run out of capacity since the communication with each terminal device will require transmission/reception of packets in its own beam and thereby also require its own time unit for this transmission/reception.

<CIT> relates to a method, a network node, a computer program, and a computer program product for evaluating co-scheduling of terminal devices, and to a method, a terminal device, a computer program, and a computer program product for facilitating co-scheduling of terminal devices.

<CIT> relates to a device and method of allocating and selecting a transmission beam index with a priority.

<CIT> relates to wireless communications and is directed to systems and methods for retransmission of contention-free random access (CFRA) beam failure recovery (BFR) (CFRA-BFR) cross-component carrier (CC) beam failure detection (BFD).

<CIT> relates to a method and apparatus for performing unified beam management (BM).

Hence, there is still a need for an improved scheduling of terminal devices in communication networks using beamformed transmission.

An object of embodiments herein is to provide efficient scheduling of terminal devices in communication networks using beamformed transmission not suffering from the issues noted above, or at least where the above noted issues are mitigated or reduced.

According to a first aspect there is presented a method for scheduling communication with terminal devices, according to appended claim <NUM>.

According to a second aspect there is presented network node for scheduling communication with terminal devices, according to appended claim <NUM>.

According to a fourth aspect there is presented a computer program for scheduling communication with terminal devices, the computer program comprising computer program code which, when run on a network node, causes the network node to perform a method according to the first aspect.

According to a fifth aspect there is presented a computer program product comprising a computer program according to the fourth aspect and a computer readable storage medium on which the computer program is stored. The computer readable storage medium could be a non-transitory computer readable storage medium.

Advantageously these aspects provide efficient scheduling of terminal devices in communication networks using beamformed transmission.

Advantageously, the proposed scheduling does not suffer from the issues noted above.

Advantageously, these aspects enable improvement of the cell capacity in cells serving a large amount of terminal devices (e.g., transmitting/receiving small packets), especially for a network node having a TRP that implements analog beamforming.

Advantageously, these aspects enable increased probability of performing simultaneous scheduling of terminal devices when using frequency multiplexing.

All references to "a/an/the element, apparatus, component, means, module, action, etc." are to be interpreted openly as referring to at least one instance of the element, apparatus, component, means, module, action, etc., unless explicitly stated otherwise. The actions of any method disclosed herein do not have to be performed in the exact order disclosed, unless explicitly stated.

Any action or feature illustrated by dashed lines should be regarded as optional.

<FIG> is a schematic diagram illustrating a communication network <NUM> where embodiments presented herein can be applied. The communication network <NUM> could be a third generation (<NUM>) telecommunications network, a fourth generation (<NUM>) telecommunications network, or a fifth (<NUM>) telecommunications network and support any 3GPP telecommunications standard, where applicable.

The communication network <NUM> comprises a network node <NUM> configured to provide network access to terminal devices 150a, 150b in a radio access network <NUM>. The radio access network <NUM> is operatively connected to a core network <NUM>. The core network <NUM> is in turn operatively connected to a service network <NUM>, such as the Internet. The terminal devices 150a, 150b are thereby enabled to, via the network node <NUM>, access services of, and exchange data with, the service network <NUM>.

The network node <NUM> comprises, is collocated with, is integrated with, or is in operational communications with, a transmission and reception point (TRP) <NUM>. The network node <NUM> (via its TRP <NUM>) and the terminal devices 150a, 150b are configured to communicate with each other in beams 160a, 160b.

Examples of network node <NUM> are radio access network nodes, radio base stations, base transceiver stations, Node Bs, evolved Node Bs, g NBs, access points, access nodes, and backhaul nodes. Examples of terminal devices 150a, 150b are wireless devices, mobile stations, mobile phones, handsets, wireless local loop phones, user equipment (UE), smartphones, laptop computers, tablet computers, network equipped sensors, network equipped vehicles, and so-called Internet of Things devices.

Assume that the TRP <NUM> is configured to generate X><NUM> different narrow beams, where, for example X is in the order of <NUM>, <NUM>, <NUM> or more, and that each terminal device 150a, 150b is configured to, in a beam report, report at least the beam out of the X beams in which a reference signal (such as a channel state information reference signal; CSI-RS) was best received according to some quality criterion, such as highest received power (such as reference signal received power; RSRP) or highest signal to interference plus noise ratio (SINR). This beam will, for any given terminal device, hereinafter be denoted as the top ranked beam for that given terminal device. Assume further that the same X beams are to be used for transmitting data to the terminal devices 150a, 150b. The network node <NUM> thus needs to schedule which beam is to be used for transmitting data to which terminal device 150a, 150b. In the illustrative example of <FIG>, terminal device 150a is best scheduled in beam 160a and terminal device 150b is best scheduled in beam 160b.

As noted above, there is a need improved scheduling of terminal devices 150a, 150b in communication networks <NUM> using beamformed transmission.

The embodiments disclosed herein therefore relate to mechanisms for scheduling communication with terminal devices 150a, 150b. In order to obtain such mechanisms there is provided a network node <NUM>, a method performed by the network node <NUM>, a computer program product comprising code, for example in the form of a computer program, that when run on a network node <NUM>, causes the network node <NUM> to perform the method.

At least some of the herein disclosed embodiments are based on scheduling a terminal device in a beam that has not been reported as the top ranked beam for that terminal device. This enables the terminal device to be co-scheduled with another terminal device in one and the same beam. For this to be possible it might in some embodiments be required that the performance of the terminal device that is not scheduled in its top ranked beam is still acceptable. Further aspects of how this might be ensured will be disclosed below.

In <FIG> is given an illustrative example of how the maximum difference, or drop, in antenna gain between five different beams B1-B5 can be determined. In particular, <FIG> schematically illustrates the antenna gain pattern as modeled for an example antenna array. As seen in the figure, the maximum drop in antenna gain if using beam B1 instead of beam B2 is <NUM> dB. Further, if using beam B4 instead of beam B2 the maximum drop is infinity (it is noted that in reality, calibration errors in the antenna and mutual coupling contribute to make the maximum drop to be less than infinity); and if using beam B5 instead of beam B2 the maximum drop is <NUM> dB. The maximum difference, or drop, in antenna gain if using beam B5 instead of beam B2 is thus <NUM> dB although these beams are pointing in very different directions. This is because one of the sidelobes of beam B5 is pointing in the direction of the main lobe of beam B2. Mutual coupling might create even larger side lobes compared to the perfectly modelled antenna array without mutual coupling (as assumed in <FIG>).

<FIG> is a flowchart illustrating embodiments of methods for scheduling communication with terminal devices 150a, 150b. The methods are performed by the network node <NUM>. The methods are advantageously provided as computer programs <NUM>.

It is assumed that a beam management procedure has been performed by the network node <NUM> and that the terminal devices 150a, 150b in response thereto sends beam reports to the network node <NUM>. In particular, the network node <NUM> is configured to perform action S102:
S102: The network node <NUM> receives, in response to having performed a beam management procedure involving transmission of reference signals in a set of beams 160a, 160b; B1:B9, a beam report from each of the terminal devices 150a, 150b. Each beam report indicates one of the beams as top ranked.

In this respect, the beam report might either explicitly identify which beam is the top ranked one, or implicitly identify which beam is the top ranked one by providing a performance value, such as reference signal received power (RSRP) or signal to interference plus noise ratio (SINR) for each reported beam. That is, the beam report from terminal device 150a indicates the beam as top ranked by this terminal device 150a. Since the terminal devices 150a, 150b might be geographically spread with respect to each other, it might therefore be that different ones of the terminal devices 150a, 150b report different ones of the beams as top ranked. Examples thereof will be disclosed below with reference to <FIG>. However, the network node <NUM> might still serve two or more of the terminal devices 150a, 150b in one and the same beam despite some of these two or more of the terminal devices 150a, 150b not having reported that beam as the top tanked one. In particular, the network node <NUM> is configured to perform action S104:
S104: The network node <NUM> schedules communication for the terminal devices 150a, 150b in beams of the set of beams 160a, 160b; B1:B9. At least a first terminal device 150a of the terminal devices 150a, 150b and a second terminal device 150b of the terminal devices 150a, 150b are both scheduled in a first beam 160a, B2, B3 of the beams not indicated as top ranked in the beam report of the second terminal device 150b.

Two or more terminal devices 150a, 150b might thereby be frequency-multiplexed in one beam, despite one or more of those terminal devices 150a, 150b not having reported that beam as the top ranked one. That is, in some embodiments, the communication is scheduled to, in the first beam 160a, B2, B3, use frequency multiplexed communication for at least the first terminal device 150a and the second terminal device 150b, where the terminal devices 150a, 150b thus are multiplexed in different parts of the frequency band. That is, the frequency multiplexed communication is scheduled in a frequency band, and each of the at least the first terminal device 150a and the second terminal device 150b is allocated its own part of the frequency band. This is feasible at least for terminal devices 150a, 150b that have a link budget good enough to be served by a beam that is not the best beam. This is feasible, for example, for terminal devices 150a, 150b located geographically close to the TRP <NUM>, for terminal devices 150a, 150b having low data rate requirements, and/or depending on radio propagation conditions (for example if there is line of sight (LOS) or no line of sight (NLOS) between the TRP <NUM> and the terminal devices 150a, 150b.

Embodiments relating to further details of scheduling communication with terminal devices 150a, 150b as performed by the network node <NUM> will now be disclosed.

In some examples, the network node <NUM> has access to information of the maximum difference in antenna gain between the different beams that could be generated by the TRP <NUM>. Values of the maximum difference in antenna gain might be obtained from embedded radiation pattern measurements (including mutual coupling) on the antenna architecture that is used for that type of TRP. Values of the maximum difference in antenna gain might additionally or alternatively be based on measurements as obtained when designing the TRP <NUM>, from simulations, from measurements in an anechoic chamber when testing the TRP <NUM>, and/or from measurements in the field where the TRP <NUM> is deployed. The network node <NUM> might use such information together with the received beam reports from the terminal devices 150a, 150b to determine which terminal devices 150a, 150b that could be scheduled simultaneously in one and the same beam. Values of the maximum difference in antenna gain might be tabulated, for example as in Table <NUM>.

Table <NUM> gives an illustrative example of values of maximum drop in antenna gain between two beams based on the five beams illustrated in <FIG>. That is, if beam <NUM> is reported by one of the terminal devices as the top ranked, or best, beam, a performance drop of at most <NUM> dB is to be expected for this terminal device if instead this terminal device is scheduled in beam <NUM>. According to the table, the values are not symmetrical. For example, if beam <NUM> is reported by one of the terminal devices, a performance drop of ><NUM> dB might be expected for this terminal device if instead this terminal device is scheduled in beam <NUM>. one reason for this is that beam <NUM> and beam <NUM> are edge beams, i.e., beams having only one single neighboring beam. For an actual deployment of the TRP <NUM>, due to, for example angular spread in the radio propagation channel, the actual difference in antenna gain between two beams might be much less than the values given in the table.

In some embodiments, the beams in the set of beams 160a, 160b; B1:B9 are generated by means of analog beamforming. Thus, per time instant, only one of the beams is active for communicating with the terminal devices 150a, 150b.

There could be different ways for the terminal devices 150a, 150b to select which beam to be the top ranked one. In some aspects, the terminal devices 150a, 150b perform measurements on signals as transmitted in beams from the TRP <NUM> of the network node <NUM>. Examples of such measurements relate to received power and signal to interference plus noise ratio. That is, according to an embodiment, the beam report of the second terminal device 150b indicated a second beam 160b, B4, B7 of the beams as top ranked, and the second beam 160b, B4, B7 corresponds to that beam in the set of beams 160a, 160b; B1:B9 in which one of the reference signals was by the second terminal device 150b received with highest received power (such as RSRP) or highest SINR. Further, the first beam might be the beam that was reported as top ranked by the first terminal device 150a. However, in some examples the first terminal device <NUM> and the second terminal device 150b are co-scheduled with a third terminal device in the first beam where it is the third terminal device that has reported the first beam as top ranked.

In some examples the terminal devices 150a, 150b report only the top ranked beam.

However, in other examples the terminal devices 150a, 150b each report two or more beams, where thus one beam per report is the top ranked one. Reporting only the top ranked beam might minimize the overhead signaling for beam management whereas reporting two or more beams might enable the network node <NUM> to better select which two or more terminal devices 150a, 150b to co-schedule in the same beam. Further, there might be different criteria that the network node <NUM> uses, or at least considers, when determining which at least two terminal devices 150a, 150b to co-schedule in the same beam, and thus to determine whether or not it is possible to schedule at least the first terminal device 150a of the terminal devices 150a, 150b and the second terminal device 150b of the terminal devices 150a, 150b in the first beam 160a, where this first beam 160a is not indicated as top ranked in the beam report of the second terminal device 150b.

In particular, according to the invention, the beam report of the second terminal device 150b indicated a second beam 160b, B4, B7 of the beams as top ranked. A performance value for communicating data with the second terminal device 150b as scheduled in the first beam 160a, B2, B3 might then be estimated as less than a threshold value worse than if the second terminal device 150b instead is scheduled in the second beam 160b, B4, B7 (in order for the second terminal device 150b to be co-scheduled in the first beam 160a). The performance values are: antenna gain, link budget, throughput. Thus, the second terminal device 150b is only co-scheduled with the first terminal device 150a in the first beam if the estimated performance drop in terms of antenna gain, link budget, and/or throughput for the second terminal device 150b not being scheduled in its reported top ranked beam (i.e., in the second beam 160b) is less than a threshold value.

Further details the criteria used, or at least considered, by the network node <NUM> when determining which at least two terminal devices 150a, 150b to co-schedule in the same beam will now be disclosed.

In some aspects, the criteria relates to the maximum antenna gain differences between the different beams. That is, according to an embodiment, whether to schedule communication for the second terminal device 150b in the first beam 160a, B2, B3 or not is based on a maximum drop in antenna gain as resulting if data is communicated with the second terminal device 150b in the first beam 160a, B2, B3 instead of in the second beam 160b, B4, B7. Further in this respect, according to an embodiment, the network node <NUM> is configured to perform (optional) action S104a as part of the scheduling in action S104:
S104a: The network node <NUM> verifies that the maximum drop in antenna gain for the second terminal device 150b is not larger than a first threshold value.

In some aspects, the criteria relates to the link budget, throughput, and/or bandwidth, being good enough for the terminal device to be served by a beam that is not reported as the top ranked one for that terminal device. That is, according to an embodiment, whether to schedule communication for the second terminal device 150b in the first beam 160a, B2, B3 or not is based on a maximum drop in link budget, throughput, and/or bandwidth as resulting if data is communicated with the second terminal device 150b in the first beam 160a, B2, B3 instead of in the second beam 160b, B4, B7. Further in this respect, according to an embodiment, the network node <NUM> is configured to perform (optional) action S104b as part of the scheduling in action S104:
S104b: The network node <NUM> verifies that the maximum drop in link budget, and/or throughput for the second terminal device 150b is not larger than a second threshold value.

In some examples both actions S104a and S104b are performed as part of action S104.

Further, before using the first beam 160a for communicating data with the second terminal device 150b, the network node <NUM> might perform further testing of the first beam, for example by considering reportings from the second terminal device 150b of signals as received by the second terminal device 150b from the TRP <NUM> in the first beam 160a. That is, in some embodiments, the verifying in action S104a and/or S104b is based on reporting from the second terminal device 150b of a reference signal in the first beam 160a, B2, B3. When two or more terminal devices 150a, 150b have been identified as candidates for being co-scheduled in the same beam, the network node <NUM> might thus transmit CSI-RS for CSI acquisition for each respective terminal device scheduled in the same beam and based on the corresponding CSI reports make a final decision regarding whether the terminal devices 150a, 150b can be co-scheduled in the same beam or not, and also determine a suitable modulation and coding scheme (MCS), rank, and precoding matrix index (PMI) for each respective terminal device 150a, 150b.

In some aspects, for example when the terminal devices 150a, 150b utilizes analog beamforming, the network node <NUM> might signal to the terminal devices 150a, 150b which beams are used for scheduling the terminal devices 150a, 150b. That is, according to an embodiment, the network node <NUM> is configured to perform (optional) action S106:
S106: The network node <NUM> transmits, before communicating data with at least the first terminal device 150a and the second terminal device 150b in the first beam 160a, B2, B3, information of in which of the beams the terminal devices 150a, 150b are scheduled.

In this respect, the information might not explicitly identify which beam is used. Rather, the information might be provided in terms of a pointer to a previously transmitted reference signal which was transmitted in the scheduled beam, or a beam with similar spatial characteristics as the scheduled beam. The information might be conveyed within a spatial QCL framework. This could be done for a downlink data channel, such as the physical downlink shared channel (PDSCH) by signaling a Transmission Configuration Indicator (TCI) state (where the TCI state includes a spatial QCL reference to an earlier transmitted downlink reference signal) in the DCI triggering the PDSCH transmission. The indicated TCI state should thus point at the first beam 160a for both the first terminal device 150a and the second terminal device 150b. Further aspects relating to the use of TCI states for this purpose will be disclosed below.

Reference is now made to <FIG> that schematically illustrates a TRP <NUM> controlled by a network node <NUM> and that is configured to serve two terminal devices 150a, 150b in beams B1, B2, B3, B4, B5 in accordance with the herein disclosed embodiments. For illustrative purposes it is assumed that the RSRP measured and reported for beam B2 by terminal device 150a was -<NUM> dBm, and that the RSRP measured and reported for beam B4 by terminal device is -<NUM> dBm. Assume for illustrative purposes further that both these terminal devices 150a, 150b are to receive data. Assume for illustrative purposes further that a minimum RSRP of -100dBm is required for reliable data communication with any of the terminal devices 150a, 150b. In order to communicate with terminal device 150a, the full antenna gain of B2 thus is needed. Assume for illustrative purposes further that the maximum drop in antenna gain between beam B2 and beam B4 is <NUM> dB in the angular interval corresponding to where B2 is the strongest beam. In case data communication with terminal device 150b utilizes beam B2 instead of B4, the antenna gain for terminal device 150b would thus be reduced to -<NUM> dBm which is still more than -100dBm. Therefore, the network node <NUM> might co-schedule terminal devices 150a, 150b for simultaneous downlink data transmitted in beam B2 whilst still maintaining a sufficient link budget for both these terminal devices 150a, 150b.

Further aspects of the information of in which of the beams the terminal devices 150a, 150b are scheduled will now be disclosed. In some aspects, the information is conveyed by means of TCI state information. That is, according to an embodiment, the information is in S106 transmitted by signalling of a TCI state. Further, in some embodiments the network node <NUM> configures each of the terminal devices 150a, 150b to simultaneously have more than one active TCI state. Further in this respect, when selecting spatial QCL using DCI, the network node <NUM> might commonly only select between <NUM> different active TCI states, whilst the number of beams used by the TRP <NUM> might be much larger than that. To address this issue, in some embodiments, the terminal devices 150a, 150b are by the network node <NUM> configured with active TCI states that take the maximum drop in antenna gain between the different beams into account. With reference again to the illustrative example of <FIG>, terminal device 150b as served by beam B4, can have one active TCI state corresponding to each of beams B4, B3, B5, and B2. B4 is the top ranked beam by this terminal device. Beam B3 and beam B5 are the beams located adjacent the currently reported top ranked beam and information thereof might be useful if the terminal device 150b is moved and the drop in antenna gain between beam B4 and beam B3 and between B4 and B5 is low, which could facilitate co-scheduling of terminal device 150b one or more other terminal devices that has reported beam B3 or B5 as the top ranked one. Beam B2 is included in case it has a low drop in antenna gain compared to beam B4 and could therefore potentially be used for co-scheduling this terminal device with one or more other terminal devices in this beam. Hence, in some embodiments, each TCI state corresponds to one of the beams in the set of beams 160a, 160b; B1:B9.

In other embodiments, when the beam management procedure further involves transmission of other reference signals in another set of beams SSB1:SSB3, each TCI state might correspond to one beam in the further set of beams SSB1:SSB3. As will be further disclosed below, the beams in this another set of beams SSB1:SSB3 might then be wider than the beams in the set of beams 160a, 160b; B1:B9.

Reference is now made to <FIG> that schematically illustrates a TRP <NUM> controlled by a network node <NUM> and that is configured to serve two terminal devices 150a, 150b in beams B1, B2, B3, B4, B5, B6, B7, B8, B9, SSB1, SSB2, SSB3 in accordance with the herein disclosed embodiments. According to the illustrative example of <FIG>, the TRP <NUM> is configured to generate three wide beams SSB1, SSB2, SSB3 that are used for transmission of synchronization signal blocks (SSBs), and nine narrow beams B1, B2, B3, B4, B5, B6, B7, B8, B9 that are used for transmission of CSI-RS as well as data. The antenna beam pattern of SSB1 covers beams B1, B2, B3, the antenna beam pattern of SSB2 covers beams B4, B5, B6, and the antenna beam pattern of SSB3 covers beams B7, B8, B9. It is thereby possible that each TCI state is related to one SSB beam (i.e., one of beams SSB1, SSB2, SSB3) each. Since the number of SSB beams generally is much smaller than the number of narrow beams, the network node <NUM> might signal the spatial QCL for different terminal device 150a, 150b using DCI in the SSB beams since there are then also fewer TCI states that are needed to cover the whole cell (as defined by the coverage of all SSB beams). For example, even if the TRP <NUM> is configured to generate only <NUM> SSB beams, then <NUM> active TCI states can correspond to these <NUM> SSB beams. In this case, the network node <NUM> might co-schedule its served terminal devices 150a, 150b and then signal the spatial QCL by indicating one of the <NUM> active TCI states.

One particular embodiment for scheduling communication with terminal devices 150a, 150b as performed by the network node <NUM> based on at least some of the above embodiments, aspects, and examples will now be disclosed with reference to the signalling diagram of <FIG>.

S201: The network node <NUM> obtains information of the maximum drop in antenna gain between the beams that could be generated by its TRP <NUM>.

S202: The network node <NUM> performs a beam sweep where reference signals (such as SSB or CSI-RS) are transmitted in beams.

S203a, S203b: Each terminal device 150a, 150b receives the reference signals as transmitted in one or more of the beams, determines therefrom at least the top ranked beam, and reports in a beam report at least the top ranked beam (and, optionally, the corresponding RSRP of the top ranked beam).

S204: The network node <NUM>, based on the beam reports and the information of the maximum drop in antenna gain, determines in which beam to schedule each terminal device 150a, 150b it has received a beam report from. Terminal device 150a and terminal device 150b are both scheduled in the beam reported as top ranked by terminal device 150a but not by terminal device <NUM>. One of the beams is thus selected for scheduling terminal device 150a and terminal device 150b.

S205: The network node <NUM>, for acquiring channel state information (CSI) from the terminal devices 150a, 150b, triggers and transmits CSI-RS in the selected beam.

S206: The network node <NUM> triggers transmission of the data and transmits the data, for example by means of PDSCH signalling, towards the terminal devices 150a, 150b in the selected beam. When transmission is triggered the network node <NUM> might transmit a spatial QCL reference to the selected beam.

<FIG> schematically illustrates, in terms of a number of functional units, the components of a network node <NUM> according to an embodiment. Processing circuitry <NUM> is provided using any combination of one or more of a suitable central processing unit (CPU), multiprocessor, microcontroller, digital signal processor (DSP), etc., capable of executing software instructions stored in a computer program product <NUM> (as in <FIG>), e.g. in the form of a storage medium <NUM>. The processing circuitry <NUM> may further be provided as at least one application specific integrated circuit (ASIC), or field programmable gate array (FPGA).

Particularly, the processing circuitry <NUM> is configured to cause the network node <NUM> to perform a set of operations, or actions, as disclosed above. For example, the storage medium <NUM> may store the set of operations, and the processing circuitry <NUM> may be configured to retrieve the set of operations from the storage medium <NUM> to cause the network node <NUM> to perform the set of operations.

Thus the processing circuitry <NUM> is thereby arranged to execute methods as herein disclosed. The network node <NUM> may further comprise a communications interface <NUM> at least configured for communications with other entities, functions, nodes, and devices of the communication network <NUM> of <FIG>, as well as with terminal devices 150a, 150b. As such the communications interface <NUM> may comprise one or more transmitters and receivers, comprising analogue and digital components. The processing circuitry <NUM> controls the general operation of the network node <NUM> e.g. by sending data and control signals to the communications interface <NUM> and the storage medium <NUM>, by receiving data and reports from the communications interface <NUM>, and by retrieving data and instructions from the storage medium <NUM>. Other components, as well as the related functionality, of the network node <NUM> are omitted in order not to obscure the concepts presented herein.

<FIG> schematically illustrates, in terms of a number of functional modules, the components of a network node <NUM> according to an embodiment. The network node <NUM> of <FIG> comprises a number of functional modules; a receive module 210a configured to perform action S102, and a schedule module 210b configured to perform action S104. The network node <NUM> of <FIG> may further comprise a number of optional functional modules, such as any of a first verify module 210c configured to perform action S104a, a second verify module 210d configured to perform action S104b, and a transmit module 210e configured to perform action S106. In general terms, each functional module 210a-210e may in one embodiment be implemented only in hardware and in another embodiment with the help of software, i.e., the latter embodiment having computer program instructions stored on the storage medium <NUM> which when run on the processing circuitry makes the network node <NUM> perform the corresponding actions mentioned above in conjunction with <FIG>. It should also be mentioned that even though the modules correspond to parts of a computer program, they do not need to be separate modules therein, but the way in which they are implemented in software is dependent on the programming language used. Preferably, one or more or all functional modules 210a-210e may be implemented by the processing circuitry <NUM>, possibly in cooperation with the communications interface <NUM> and/or the storage medium <NUM>. The processing circuitry <NUM> may thus be configured to from the storage medium <NUM> fetch instructions as provided by a functional module 210a-210e and to execute these instructions, thereby performing any actions as disclosed herein.

The network node <NUM> may be provided as a standalone device or as a part of at least one further device. For example, the network node <NUM> may be provided in a node of the radio access network or in a node of the core network. Alternatively, functionality of the network node <NUM> may be distributed between at least two devices, or nodes. These at least two nodes, or devices, may either be part of the same network part (such as the radio access network or the core network) or may be spread between at least two such network parts. In general terms, instructions that are required to be performed in real time may be performed in a device, or node, operatively closer to the cell than instructions that are not required to be performed in real time.

Thus, a first portion of the instructions performed by the network node <NUM> may be executed in a first device, and a second portion of the of the instructions performed by the network node <NUM> may be executed in a second device; the herein disclosed embodiments are not limited to any particular number of devices on which the instructions performed by the network node <NUM> may be executed. Hence, the methods according to the herein disclosed embodiments are suitable to be performed by a network node <NUM> residing in a cloud computational environment. Therefore, although a single processing circuitry <NUM> is illustrated in <FIG> the processing circuitry <NUM> may be distributed among a plurality of devices, or nodes. The same applies to the functional modules 210a-210e of <FIG> and the computer program <NUM> of <FIG>.

The computer program <NUM> and/or computer program product <NUM> may thus provide means for performing any actions as herein disclosed.

<FIG> is a schematic diagram illustrating a telecommunication network connected via an intermediate network <NUM> to a host computer <NUM> in accordance with some embodiments. In accordance with an embodiment, a communication system includes telecommunication network <NUM>, such as a 3GPP-type cellular network, which comprises access network <NUM>, such as radio access network <NUM> in <FIG>, and core network <NUM>, such as core network <NUM> in <FIG>. Access network <NUM> comprises a plurality of radio access network nodes 412a, 412b, 412c, such as NBs, eNBs, gNBs (each corresponding to the network node <NUM> of <FIG>) or other types of wireless access points, each defining a corresponding coverage area, or cell, 413a, 413b, 413c. Each radio access network nodes 412a, 412b, 412c is connectable to core network <NUM> over a wired or wireless connection <NUM>. A first UE <NUM> located in coverage area 413c is configured to wirelessly connect to, or be paged by, the corresponding network node 412c. A second UE <NUM> in coverage area 413a is wirelessly connectable to the corresponding network node 412a. While a plurality of UE <NUM>, <NUM> are illustrated in this example, the disclosed embodiments are equally applicable to a situation where a sole UE is in the coverage area or where a sole terminal device is connecting to the corresponding network node <NUM>. The UEs <NUM>, <NUM> correspond to the terminal devices 150a, 150b of <FIG>.

For example, network node <NUM> may not or need not be informed about the past routing of an incoming downlink communication with data originating from host computer <NUM> to be forwarded (e.g., handed over) to a connected UE <NUM>. Similarly, network node <NUM> need not be aware of the future routing of an outgoing uplink communication originating from the UE <NUM> towards the host computer <NUM>.

<FIG> is a schematic diagram illustrating host computer communicating via a radio access network node with a UE over a partially wireless connection in accordance with some embodiments. Example implementations, in accordance with an embodiment, of the UE, radio access network node and host computer discussed in the preceding paragraphs will now be described with reference to <FIG>. The UE <NUM> corresponds to the terminal devices 150a, 150b of <FIG>.

Communication system <NUM> further includes radio access network node <NUM> provided in a telecommunication system and comprising hardware <NUM> enabling it to communicate with host computer <NUM> and with UE <NUM>. The radio access network node <NUM> corresponds to the network node <NUM> of <FIG>. Hardware <NUM> may include communication interface <NUM> for setting up and maintaining a wired or wireless connection with an interface of a different communication device of communication system <NUM>, as well as radio interface <NUM> for setting up and maintaining at least wireless connection <NUM> with UE <NUM> located in a coverage area (not shown in <FIG>) served by radio access network node <NUM>. In the embodiment shown, hardware <NUM> of radio access network node <NUM> further includes processing circuitry <NUM>, which may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions. Radio access network node <NUM> further has software <NUM> stored internally or accessible via an external connection.

Its hardware <NUM> may include radio interface <NUM> configured to set up and maintain wireless connection <NUM> with a radio access network node serving a coverage area in which UE <NUM> is currently located.

It is noted that host computer <NUM>, radio access network node <NUM> and UE <NUM> illustrated in <FIG> may be similar or identical to host computer <NUM>, one of network nodes 412a, 412b, 412c and one of UEs <NUM>, <NUM> of <FIG>, respectively.

In <FIG>, OTT connection <NUM> has been drawn abstractly to illustrate the communication between host computer <NUM> and UE <NUM> via network node <NUM>, without explicit reference to any intermediary devices and the precise routing of messages via these devices.

Wireless connection <NUM> between UE <NUM> and radio access network node <NUM> is in accordance with the teachings of the embodiments described throughout this disclosure. One or more of the various embodiments improve the performance of OTT services provided to UE <NUM> using OTT connection <NUM>, in which wireless connection <NUM> forms the last segment. More precisely, the teachings of these embodiments may reduce interference, due to improved classification ability of airborne UEs which can generate significant interference.

The reconfiguring of OTT connection <NUM> may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not affect network node <NUM>, and it may be unknown or imperceptible to radio access network node <NUM>. In certain embodiments, measurements may involve proprietary UE signaling facilitating host computer's <NUM> measurements of throughput, propagation times, latency and the like.

Claim 1:
A method for scheduling communication with terminal devices (150a, 150b), the method being performed by a network node (<NUM>), the method comprising:
receiving (S102), in response to having performed a beam management procedure involving transmission of reference signals in a set of beams (160a, 160b; B1:B9), a beam report from each of the terminal devices (150a, 150b), each beam report indicating one of the beams as top ranked; and
scheduling (S104) communication for the terminal devices (150a, 150b) in beams of the set of beams (160a, 160b; B1:B9), wherein at least a first terminal device (150a) of the terminal devices (150a, 150b) and a second terminal device (150b) of the terminal devices (150a, 150b) are both scheduled in a first beam (160a, B2, B3) of the beams not indicated as top ranked in the beam report of the second terminal device (150b),
wherein the beam report of the second terminal device (150b) indicated a second beam (160b, B4, B7) of the beams as top ranked, and wherein a performance value, pertaining to at least one of: antenna gain, link budget, throughput, for communicating data with the second terminal device (150b) as scheduled in the first beam (160a, B2, B3) is estimated by the network node as less than a threshold value worse than if the second terminal device (150b) instead is scheduled in the second beam (160b, B4, B7).