Ue feedback of downlink frequency differences between trps

Abstract

Systems and methods for User Equipment (UE) feedback on downlink frequency differences between Transmission and Reception Points (TRPs) are disclosed. In one embodiment, a method performed by a UE for providing feedback to a network node regarding a frequency difference between each of a plurality of TRPs and a reference TRP comprises receiving a configuration of a channel state information (CSI) report for frequency difference feedback, determining the frequency difference between each of the plurality of TRPs and the reference TRP, and determining a quantized frequency difference value indicative of the determined frequency difference between each of the plurality of TRPs and the reference TRP according to one or more parameters related to quantization of the determined frequency difference. The method further comprises transmitting, to a network node, the quantized frequency difference value for each of the plurality of TRPs.

Description

UE FEEDBACK OF DOWNLINK FREQUENCY DIFFERENCES BETWEEN TRPs RELATED APPLICATIONS

[0001] This application claims the benefit of provisional patent application serial number 63 / 516,159, filed July 28, 2023, the disclosure of which is hereby incorporated herein by reference in its entirety. TECHNICAL FIELD

[0002] The present disclosure relates to multi-Transmission and Reception Point (TRP) operation in a cellular communications network and, more specifically, to compensating for a frequency difference between TRPs such as, e.g., TRPs used for Coherent Joint Transmission (CJT). BACKGROUND NR Frame Structure

[0003] 3rdGeneration Partnership Project (3GPP) New Radio (NR) uses Orthogonal Frequency Division Multiplexing (OFDM) in the downlink (i.e., from a network node, next generation NodeB (gNB), or base station, to a User Equipment (UE)). In the uplink (i.e., from UE to gNB), both OFDM and Discrete Fourier Transform (DFT)-spread OFDM (DFT-S- OFDM), also known as Single Carrier Frequency Division Multiple Access (SC-FDMA) in Long Term Evolution (LTE), will be supported. The basic NR physical resource can thus be seen as a time-frequency grid as illustrated in Figure 1, where a Resource Block (RB) in a 14-symbol slot is shown. A resource block corresponds to twelve (12) contiguous subcarriers in the frequency domain. Resource blocks are numbered in the frequency domain, starting with 0 from one end of the system bandwidth. Each resource element corresponds to one OFDM subcarrier during one OFDM symbol interval.

[0004] Different subcarrier spacing values are supported in NR. The supported subcarrier spacing values (also referred to as different numerologies) are given by ∆^ = (15 × 2^) kilohertz (kHz) where ^ is a non-negative integer and can be one of {0,1,2,3,4}. ∆^ = 15^^^ (e.g., ^ = 0) is the basic (or reference) subcarrier spacing that is also used in LTE. ^ is also referred to as the numerology.

[0005] In the time domain, downlink and uplink transmissions in NR will be organized into equally sized subframes of 1 millisecond (ms) each, similar to LTE. A subframe is further divided into multiple slots of equal duration. The slot length is dependent on the subcarrierspacing or numerology and is given by^^^ms. Each slot consists of 14 OFDM symbols for normal Cyclic Prefix (CP).

[0006] It is understood that data scheduling in NR can be on a slot basis. An example is shown in Figure 2 with a 14-symbol slot, where the first two symbols contain control channel (i.e., a Physical Downlink Control Channel (PDCCH)) and the rest contains data channel (i.e., Physical Downlink Shared Channel (PDSCH)). For convenience, a subframe is referred to throughout the following description.

[0007] Downlink transmissions can be dynamically scheduled, i.e., in each slot the gNB transmits Downlink Control Information (DCI) about which UE data is to be transmitted to and which resource blocks in the current downlink slot the data is transmitted on. This control signaling is typically transmitted in the first one or two OFDM symbols in each slot in NR. The control information is carried on PDCCH and data is carried on PDSCH. A UE first detects and decodes PDCCH and, if a PDCCH is decoded successfully, the UE then decodes the corresponding PDSCH based on the decoded control information in the PDCCH.

[0008] Uplink data transmission can also be dynamically scheduled using PDCCH. Similar to downlink, a UE first decodes uplink grants in PDCCH and then transmits data over the Physical Uplink Shared Channel (PUSCH) based on decoded control information in the uplink grant such as modulation order, coding rate, uplink resource allocation, and etc. Coherent Joint PDSCH Transmission from Multiple TRPs

[0009] In NR Release 18, coherent joint PDSCH transmission from up to four Transmission and Reception Points (TRPs) was introduced in which each data layer of a PDSCH is transmitted from multiple TRPs. An example is shown in Figure 3, where ^ layers of PDSCH data ^ = ^^^, ^^, … , ^^^^ are transmitted jointly from two TRPs after being precoded by a precoding matrix ^^at TRP1 and ^^at TRP2. The precoding is aimed for achieving coherent signal combining at the UE for each data layer. CSI Framework in NR

[0010] In NR, a UE can be configured with multiple Channel State Information (CSI) report configurations and multiple CSI resource configurations. For each CSI report configuration, a UE feeds back a CSI report when requested.

[0011] Each CSI report configuration contains at least the following information: • A CSI resource for channel measurement • Time-domain behavior, i.e., periodic, semi-persistent, or aperiodic reporting• CSI parameters to be reported such as a Rank Indicator (RI), a Precoding Matrix Indicator (PMI), and Channel Quality Indicator (CQI), SUMMARY

[0012] Systems and methods for User Equipment (UE) feedback on downlink frequency differences between Transmission and Reception Points (TRPs) are disclosed. In one embodiment, a method performed by a UE for providing feedback to a network node regarding a frequency difference between each of a plurality of TRPs and a reference TRP comprises receiving a configuration of a channel state information (CSI) report for frequency difference feedback, determining the frequency difference between each of the plurality of TRPs and the reference TRP, and determining a quantized frequency difference value indicative of the determined frequency difference between each of the plurality of TRPs and the reference TRP according to one or more parameters related to quantization of the determined frequency difference, wherein values of the one or more parameters related to quantization of the determined frequency difference to provide the quantized frequency difference value are configured by the network node. The method further comprises transmitting, to a network node, the quantized frequency difference value for each of the plurality of TRPs. Using the one or more parameters, feedback overhead can be optimized based on deployment scenarios.

[0013] In one embodiment, the values of the one or more parameters related to quantization of the determined frequency difference to provide the quantized frequency difference value are a function of any one or more of the following: carrier frequency on which the plurality of TRPs operate, CSI reporting period, base station type, maximum frequency error of the plurality of TRPs.

[0014] In one embodiment, the one or more parameters related to quantization of the determined frequency difference to provide the quantized frequency difference value comprise any one or more of the following: a frequency step size used for quantization of the determined frequency difference, a frequency range used for quantization of the determined frequency difference, a number of bits, N, used for quantization of the determined frequency difference, a maximum frequency quantization error.

[0015] In one embodiment, the one or more parameters related to quantization of the determined frequency difference to provide the quantized frequency difference value comprise a frequency step size used for quantization of the determined frequency difference. In one embodiment, the frequency step size used for quantization of the determined frequency difference is a function of Coherent Joint Transmission, CJT, Channel State Information, CSI,reporting period. In one embodiment, the frequency step size used for quantization of the determined frequency difference is configured to the UE from a network node.

[0016] In one embodiment, the one or more parameters related to quantization of the determined frequency difference to provide the quantized frequency difference value further comprise a number of bits, N, used for quantization of the determined frequency difference.

[0017] In one embodiment, the quantization is uniform quantization in which quantization levels are uniformly spaced within the frequency range used for quantization of the determined frequency difference.

[0018] In one embodiment, the number of bits, N, used for quantization of the determined frequency difference is configured to the UE from a network node.

[0019] In one embodiment, the frequency range used for quantization of the determined frequency difference is configured to the UE from a network node.

[0020] In one embodiment, the frequency range and the number of bits, N, used for quantization of the determined frequency difference are configured to the UE from a network node.

[0021] In one embodiment, the one or more parameters related to quantization of the determined frequency difference to provide the quantized frequency difference value further comprise a maximum frequency quantization error.

[0022] In one embodiment, the one or more parameters related to quantization of the determined frequency difference to provide the quantized frequency difference value comprise a number of bits, N, used for quantization of the determined frequency difference and a maximum frequency quantization error.

[0023] In one embodiment, the one or more parameters related to quantization of the determined frequency difference to provide the quantized frequency difference value comprise a frequency step size used for quantization of the determined frequency difference and a frequency range of a range of values used for quantization of the determined frequency difference.

[0024] In one embodiment, a value of at least one of the one or more parameters related to quantization of the determined frequency difference to provide the quantized frequency difference value is predefined.

[0025] In one embodiment, the values of the one or more parameters related to quantization of the determined frequency difference to provide the quantized frequency difference value are predefined.

[0026] In one embodiment, the method further comprises receiving, from the network node, information that explicitly or implicitly indicates the value of at least one of the one or moreparameters related to quantization of the determined frequency difference to provide the quantized frequency difference value.

[0027] In one embodiment, the method further comprises receiving, from the network node, information that explicitly or implicitly indicates the values of the one or more parameters related to quantization of the determined frequency difference to provide the quantized frequency difference value. In one embodiment, the one or more parameters related to quantization of the determined frequency difference to provide the quantized frequency difference value comprise two or more parameters that are separately configured via the information received from the network node. In one embodiment, the one or more parameters related to quantization of the determined frequency difference to provide the quantized frequency difference value comprise two or more parameters that are jointly configured via the information received from the network node.

[0028] In one embodiment, the CSI report configuration received from the network node further comprises information of a plurality of reference signals wherein each of the plurality of reference signals is transmitted from either the reference TRP or one of the plurality of TRPs. In one embodiment, determining the frequency difference between each of the plurality of TRPs and the reference TRP comprises measuring the frequency difference based on the corresponding reference signals. In one embodiment, the transmitting to the network node the quantized frequency difference value is according to the CSI report configuration.

[0029] In one embodiment, the information received from the network node comprises a serving cell configuration.

[0030] In one embodiment, one or more of the plurality of TRPs and the reference TRP are TRPs used for coherent joint transmission to the UE.

[0031] Corresponding embodiments of a UE are also disclosed. In one embodiment, a UE for providing feedback to a network node regarding a frequency difference between each of a plurality of TRPs and a reference TRP is adapted to receive a configuration of a channel state information, CSI, report for frequency difference feedback, determine the frequency difference between each of the plurality of TRPs and the reference TRP, and determine a quantized frequency difference value indicative of the determined frequency difference between each of the plurality of TRPs and the reference TRP according to one or more parameters related to quantization of the determined frequency difference, wherein values of the one or more parameters related to quantization of the determined frequency difference to provide the quantized frequency difference value are configured by the network node. The UE is furtheradapted to transmit, to a network node, the quantized frequency difference value for each of the plurality of TRPs.

[0032] Embodiments of a method performed by a network node are also disclosed. In one embodiment, a method performed by a network node for compensating for a frequency difference between a plurality of TRPs and a reference TRP based on feedback from a UE comprises transmitting, to the UE, a configuration of a CSI report for frequency difference feedback and receiving, from the UE, a quantized frequency difference value indicative of a frequency difference between each of a plurality of TRPs and a reference TRP, wherein values of one or more parameters related to quantization of the frequency difference is configured by the network node or determined by the UE. The method further comprises performing one or more actions based on the quantized frequency difference value.

[0033] Corresponding embodiments of a network node are also disclosed. In one embodiment, a network node for compensating for a frequency difference between a plurality of TRPs and a reference TRP based on feedback from a UE is adapted to transmit, to the UE, a configuration of a CSI report for frequency difference feedback and receive, from the UE, a quantized frequency difference value indicative of a frequency difference between each of a plurality of TRPs and a reference TRP, wherein values of one or more parameters related to quantization of the frequency difference is configured by the network node or determined by the UE. The network node is further adapted to perform one or more actions based on the quantized frequency difference value. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0035] Figure 1 illustrates NR physical resources;

[0036] Figure 2 illustrates a NR time-domain structure with 15kHz subcarrier spacing;

[0037] Figure 3 illustrates an example of coherent joint PDSCH transmission over two TRPs;

[0038] Figure 4 is a reproduction of Table 6.5.1.2-1 of 3GPP Technical Specification (TS) 38.104 (see, e.g., V18.2.0);

[0039] Figure 5 illustrates an example of associating or configuring different N values for different carrier frequencies;

[0040] Figure 6 illustrates an example of residual phase variation during each CJT CSI reporting period;

[0041] Figure 7 illustrates an example of configuring ^ and ∆^^ !"separately;

[0042] Figure 8 illustrates an example of configuring ^ and ∆^^ !"jointly;

[0043] Figure 9 illustrates an example of different frequency difference reporting tables pre- defined in 3GPP specifications;

[0044] Figure 10 illustrates the operation of a User Equipment (UE) and a network node in accordance with at least some of the embodiments described herein;

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

[0046] Figure 12 shows a UE in accordance with some embodiments of the present disclosure;

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

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

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

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

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

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

[0053] Even though the term “base station” is used herein, this terminology is non-limiting, and the term “base station” may be used interchangeably with terms such as gNodeB (gNB),eNodeB (eNB), or an equivalent term referring to a network node used in 6thGeneration (6G) and beyond.

[0054] There currently exist certain challenge(s). Even though a same nominal transmit frequency may be used at different Transmission and Reception Points (TRPs), due to different local oscillators used in the TRPs, there will be transmit frequency differences between TRPs. In 3rdGeneration Partnership Project (3GPP) New Radio (NR), the maximum transmit frequency error for a base station (e.g., a next generation NodeB (gNB)) is specified in Table 6.5.1.2-1 of 3GPP Technical Specification (TS) 38.104 (see, e.g., V18.2.0), which is reproduced herein as Figure 4. For the most stringent + / -0.05 parts per million (ppm) requirement, there will be some residual frequency errors. These frequency errors mean that the relative phase of the signals received from different TRPs will change over time. Hence, in multi-TRP Coherent Joint Transmission (CJT), how to reduce and mitigate the impact of transmit frequency differences between the TRPs is an open problem.

[0055] One possible solution is User Equipment (UE) assisted feedback of frequency differences between TRPs, in which a UE measures the frequency difference between each TRP and a reference TRP based on reference signals transmitted from the TRPs. With the feedback information, the gNB can pre-compensate for the frequency difference between TRPs before data transmission.

[0056] One issue when providing feedback of frequency differences between TRPs is how to determine the feedback frequency resolution, e.g., 1 Hertz (Hz) or 5Hz, and frequency range. A better frequency compensation or correction can be achieved with finer frequency resolution. On the other hand, finer frequency resolution means larger feedback overhead.

[0057] Certain aspects of the disclosure and their embodiments may provide solutions to these or other challenges. Embodiments of systems and methods are disclosed for UE feedback of downlink frequency differences between TRPs, in which the frequency step size and range (i.e., the number of bits used in quantization) are configurable and can be optimized, or adapted, based on one or more factors. In some embodiments, the one or more factors include any one or more of the following factors: • carrier frequency, • Channel State Information (CSI) reporting period, • base station type (e.g., wide area, medium area, or local area base stations), • maximum frequency error of each of the TRPs.

[0058] In some embodiments, a configurable frequency step size and / or number of quantization bits is used for feedback, from a UE to a network node (e.g., gNB), of downlinkfrequency differences between TRPs. The step size and / or the number of quantization bits can be adapted based on one or more factors, which, in some embodiments, includes any one or more of the following factors: • carrier frequency, • CSI reporting period, • base station type (e.g., wide area, medium area, or local area base stations), • maximum frequency error of each of the TRPs.

[0059] In some embodiments, the step size and / or the number of quantization bits are configured by the network node (e.g., gNB) to a UE. The step size and the number of quantization bits are, in one embodiment, configured jointly together (e.g., with a configuration index) or, in another embodiment, configured separately.

[0060] Certain embodiments may provide one or more of the following technical advantage(s). With configurable frequency step size and / or number of quantization bits, feedback overhead and CJT performance can be optimized based on deployment scenarios. Feedback overhead can be reduced at lower carrier frequencies, for CSI report with smaller CSI reporting period, and for base stations with tighter frequency stability specifications.

[0061] For a given frequency stability specification, e.g., 0.1 parts per million (ppm), the maximum frequency error of a wireless base station depends on the operating carrier frequency. For example, for 0.1ppm, the maximum frequency error is + / - 100 Hertz (Hz) for carrier frequency of 1 Gigahertz (GHz) and + / -1000 Hz for a carrier frequency of 10 GHz. The same applies to Doppler frequency, i.e., for a given UE mobility speed, the Doppler frequency associated to a higher carrier frequency is larger than that associated to a lower carrier frequency.

[0062] Therefore, in one embodiment, the frequency resolution and range for feedback of frequency differences between TRPs may be optimized for different carrier frequencies.

[0063] Let ^ be the number of bits used for reporting a frequency difference ∆^ = ^^− ^^between two TRPs with a step size, ∆^^ !", then the frequency difference ∆^ is reported by an index value $%∈ (0,1, … , 2'− 1), where ∆(^ =($%− 2')^)∆^^ !". ^ may be optimized for different carrier frequencies. The optimized ^ may be either signaled to the UE or may be pre- determined, e.g., predefined in 3GPP specifications, so that both the gNB and the UE know what value of ^ is to be used in the report.

[0064] For example, ^ = 6 bits may be used for a system with 1GHz carrier frequency, and ^ = 9 bits may be used for a system with 10GHz carrier frequency. This is illustrated in Figure 5. In this example, ∆^^ !"= 5^^ is used in both cases.

[0065] The frequency resolution or step size ∆^^ !"determines the residual frequency differences between TRPs. A residual frequency difference between two TRPs would cause a linear time varying phase between the two TRPs, i.e., -.^ / ∆%0123as illustrated in Figure 6. It is assumed that the phase difference between two TRPs at each CSI reporting instance is reported by the UE to the gNB. The phase difference between the two TRPs can thus be corrected / compensated by the gNB. The uncompensated phase difference is due to the residual frequency difference between two TRPs. The longer the CJT CSI reporting period, the larger the residual phase difference between two TRPs will grow and, thus, the larger performance degradation of coherent joint transmission will be. Therefore, a smaller frequency resolution ∆^^ !"is desirable when a longer CSI reporting period is configured.

[0066] Hence, in another embodiment, ∆^^ !"may be configured by the gNB based on the CJT CSI reporting period. For example, ∆^^ !"= 5^^ may be used when the CSI report period is 10ms, while ∆^^ !"= 10^^ may be used when the CSI report period is 5ms. This would keep the maximum residual phase difference the same within each CSI period in both cases. For a same frequency range, a smaller number of bits (i.e., a smaller N value) are required for CSI reporting with smaller reporting periods (e.g., 5ms in this example) and, thus, the feedback overhead is reduced.

[0067] In general, the frequency stability requirement can be different for different types of base stations. For example, for base stations covering a small area, + / -0.1ppm is required; while for base stations covering a wide area, + / -0.05ppm is required. Hence the maximum frequency difference between two TRPs can be different for different types of base stations. Therefore, it is desirable to have configurable ^ and ∆^^ !".

[0068] In one embodiment, ^ and ∆^^ !"are separately configured as part of a CSI report configuration for reporting the frequency differences between TRPs. An example is shown in Figure 7.

[0069] In another embodiment, ^ and ∆^^ !"may be jointly configured. An example is shown in Figure 8.

[0070] When knowing the step size ∆^^ !"and the number of bits ^, as in the above examples, the maximum correctable frequency error ∆^456can be calculated according to ∆^456= 2')^∆^^ !". In some cases, instead of configuring ∆^^ !"and ^, the gNB can alternatively configure ∆^^ !"and ∆^456, or ^ and ∆^456. For the former alternative, the UE can determine the number of bits ^ based on ∆^^ !"and ∆^456; while for the latter, the UE can determine ∆^^ !"based on ^ and ∆^456. ∆^456can be configured as a fraction of the carrierfrequency or some reference frequency. Configuration of ∆^^ !"and ∆^456, or ^ and ∆^456, can also be done either separately or jointly.

[0071] In one embodiment, the values of ^ and ∆^^ !"may be configured as part of the serving cell configuration (e.g., as part of ServingCellConfig information element defined in 3GPP TS 38.331 V17.5.0). This means that any CSI reporting configuration that is used to configure reporting of one or more frequency differences that is within the serving cell uses the values of ^ and ∆^^ !"that are configured as part of the respective serving cell configuration.

[0072] In another embodiment, the values of ∆^^ !"and ∆^456may be configured as part of the serving cell configuration (e.g., as part of ServingCellConfig information element defined in 3GPP TS 38.331 V17.5.0). This means that any CSI reporting configuration that is used to configure reporting of one or more frequency differences that is within the serving cell uses the values of ∆^^ !"and ∆^456that are configured as part of the respective serving cell configuration.

[0073] In yet another embodiment, the values of ^ and ∆^456may be configured as part of the serving cell configuration (e.g., as part of ServingCellConfig information element defined in 3GPP TS 38.331 V17.5.0). This means that any CSI reporting configuration that is used to configure reporting of one or more frequency differences that is within the serving cell uses the values of ^ and ∆^456that are configured as part of the respective serving cell configuration.

[0074] In another embodiment, different tables may be predefined in 3GPP specifications. The different tables may correspond to different frequency resolution and / or different frequency ranges for the feedback of frequency difference(s) between TRPs. An example is shown in Figure 9. In this embodiment, the step size ∆^^ !", the number of bits, ^, used to report a frequency difference, and the maximum frequency difference ∆^456are implicitly given by the table that is selected for reporting of frequency difference(s) between TRPs. One of the predefined tables may be configured by the gNB to the UE. Which table is configured may be configured as part of the CSI reporting configuration or the serving cell configuration.

[0075] The feedback of frequency difference between each TRP and a reference TRP is done as a standalone CSI report configured by a CSI report configuration. In one embodiment, ^ and ∆^^ !"are configured as part of the CSI report configuration. Thus, different values of ^ and ∆^^ !"may be configured in different CSI report configurations.

[0076] Note that although the above examples use uniform quantization in linear scale to simplify demonstrating the solution, the same methods can also be applied to other quantization approaches, such as uniform in log scale.

[0077] Figure 10 illustrates the operation of a UE 1000 and a network node 1002 (e.g., a base station such as, e.g., a gNB) in accordance with at least some of the embodiments described above. Optional steps are represented by dashed lines / boxes. As illustrated, the network node 1002 optionally (i.e., in some embodiments) determines and transmits, to the UE 1000, information that explicitly or implicitly indicates values of one or more parameters (or for at least one of the parameters) related to quantization of a determined frequency difference between TRPs to provide a quantized frequency difference value (step 1004). As described above, in some embodiments, the values for two or more of the parameters may be jointly or separately configured. In one example embodiment, the information of step 1004 is included in a CSI report configuration. In another embodiment, the information of step 1004 is included in a serving cell configuration. In one embodiment, the network node 1002 determines the values of the one or more parameters based on carrier frequency on which the first and second TRPs transmit. The values of the one or more parameters (or at least one of them) may be determined further based on reporting period of the UE feedback of the frequency difference and / or a maximum frequency error of each of the first and second TRPs.

[0078] The UE 1000 determines a frequency difference between a transmit frequency of a first TRP and a transmit frequency of a second TRP (e.g., based on measurements on reference signals received from the first and second TRPs) (step 1006) and transmits, to the network node 1002, a quantized frequency difference value that is indicative of (i.e., is a quantized version of) the determined frequency difference (step 1008). In accordance with embodiments of the present disclosure, values of one or more parameters related to quantization of the determined frequency difference to provide the quantized frequency difference value are either configured by the network node 1002 (e.g., in step 1004) or determined by the UE 1000 and are a function of: (a) carrier frequency on which the first TRP and the second TRP transmit, (b) a Channel State Information, CSI, reporting period of an associated CSI report configuration, (c) a base station type of an associated base station, or (d) a combination of any two or more of (a)-(c). In the illustrated example embodiment of Figure 10, the values of the one or more parameters are a function of the carrier frequency. In one embodiment, the one or more values (or at least one of them) for the parameters are further a function for base station type and / or CSI reporting period. In some embodiments, the value(s) of at least one of (and potentially all of) the one or more parameters used for quantization are explicitly or implicitly indicated by the information received from the network node 1002 in step 1004. In some embodiments, the value(s) of at least one of (and potentially all of) the one or more parameters used for quantization are predefined (e.g., by 3GPP specification).

[0079] As described above, the one or more parameters related to quantization of the determined frequency difference to provide the quantized frequency difference value comprise any one or more of the following: • a frequency step size used for quantization of the determined frequency difference, • a frequency range of a range of values used for quantization of the determined frequency difference, • a number of bits, N, used for quantization of the determined frequency difference, • a maximum correctable frequency error. Note, however, that additional or alternative parameter(s) may be used.

[0080] In one example embodiment, the one or more parameters related to quantization of the determined frequency difference to provide the quantized frequency difference value comprise a frequency step size used for quantization of the determined frequency difference and a frequency range of a range of values used for quantization of the determined frequency difference. In another example embodiment, the one or more parameters related to quantization of the determined frequency difference to provide the quantized frequency difference value comprise a frequency step size used for quantization of the determined frequency difference and a frequency range of a range of values used for quantization of the determined frequency difference. In another example embodiment, the one or more parameters related to quantization of the determined frequency difference to provide the quantized frequency difference value comprise a number of bits, N, used for quantization of the determined frequency difference. In another example embodiment, the one or more parameters related to quantization of the determined frequency difference to provide the quantized frequency difference value comprise a frequency step size used for quantization of the determined frequency difference. In another example embodiment, the one or more parameters related to quantization of the determined frequency difference to provide the quantized frequency difference value comprise a number of bits, N, used for quantization of the determined frequency difference and a frequency step size used for quantization of the determined frequency difference. In another example embodiment, the one or more parameters related to quantization of the determined frequency difference to provide the quantized frequency difference value comprise a frequency step size used for quantization of the determined frequency difference and a maximum correctable frequency error. In another example embodiment, the one or more parameters related to quantization of the determined frequency difference to provide the quantized frequency difference value comprise a number of bits, N, used for quantization of the determined frequency difference and a maximum correctable frequency error.

[0081] In one example embodiment, the first TRP and the second TRP for which the frequency difference is determined are TRPs used for CJT to the UE 1000.

[0082] The network node 1002 performs one or more actions based on the quantized frequency difference value received from the UE 1000 (step 1010). In one embodiment, the one or more actions include one or more actions related to compensating for the frequency difference between the first and second TRPs, e.g., by pre-compensating a signal(s) transmitted by the first TRP and / or by pre-compensating a signal(s) transmitted by the second TRP, e.g., when performing CJT transmission to the UE 1000.

[0083] Figure 11 shows an example of a communication system 1100 in accordance with some embodiments.

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

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

[0086] Example wireless communications over a wireless connection include transmitting and / or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and / or other types of signals suitable for conveying information without the use of wires, cables, or other material conductors. Moreover, in different embodiments, the communication system 1100 may include any number of wired or wireless networks, network nodes, UEs, and / or any other components or systems that may facilitate or participate in the communication of data and / or signals whether via wired or wireless connections. The communication system 1100 may include and / or interface with any type of communication, telecommunication, data, cellular, radio network, and / or other similar type of system.

[0087] The UEs 1112 may be any of a wide variety of communication devices, including wireless devices arranged, configured, and / or operable to communicate wirelessly with the network nodes 1110 and other communication devices. Similarly, the network nodes 1110 are arranged, capable, configured, and / or operable to communicate directly or indirectly with the UEs 1112 and / or with other network nodes or equipment in the telecommunication network 1102 to enable and / or provide network access, such as wireless network access, and / or to perform other functions, such as administration in the telecommunication network 1102.

[0088] In the depicted example, the core network 1106 connects the network nodes 1110 to one or more hosts, such as host 1116. These connections may be direct or indirect via one or more intermediary networks or devices. In other examples, network nodes may be directly coupled to hosts. The core network 1106 includes one more core network nodes (e.g., core network node 1108) that are structured with hardware and software components. Features of these components may be substantially similar to those described with respect to the UEs, network nodes, and / or hosts, such that the descriptions thereof are generally applicable to the corresponding components of the core network node 1108. Example core network nodes include functions of one or more of a Mobile Switching Center (MSC), Mobility Management Entity(MME), Home Subscriber Server (HSS), Access and Mobility Management Function (AMF), Session Management Function (SMF), Authentication Server Function (AUSF), Subscription Identifier De-Concealing Function (SIDF), Unified Data Management (UDM), Security Edge Protection Proxy (SEPP), Network Exposure Function (NEF), and / or a User Plane Function (UPF).

[0089] The host 1116 may be under the ownership or control of a service provider other than an operator or provider of the access network 1104 and / or the telecommunication network 1102, and may be operated by the service provider or on behalf of the service provider. The host 1116 may host a variety of applications to provide one or more service. Examples of such applications include live and pre-recorded audio / video content, data collection services such as retrieving and compiling data on various ambient conditions detected by a plurality of UEs, analytics functionality, social media, functions for controlling or otherwise interacting with remote devices, functions for an alarm and surveillance center, or any other such function performed by a server.

[0090] As a whole, the communication system 1100 of Figure 11 enables connectivity between the UEs, network nodes, and hosts. In that sense, the communication system 1100 may be configured to operate according to predefined rules or procedures, such as specific standards that include, but are not limited to: Global System for Mobile Communications (GSM); Universal Mobile Telecommunications System (UMTS); Long Term Evolution (LTE), and / or other suitable Second, Third, Fourth, or Fifth Generation (2G, 3G, 4G, or 5G) standards, or any applicable future generation standard (e.g., Sixth Generation (6G)); Wireless Local Area Network (WLAN) standards, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards (WiFi); and / or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave, Near Field Communication (NFC) ZigBee, LiFi, and / or any Low Power Wide Area Network (LPWAN) standards such as LoRa and Sigfox.

[0091] In some examples, the telecommunication network 1102 is a cellular network that implements 3GPP standardized features. Accordingly, the telecommunication network 1102 may support network slicing to provide different logical networks to different devices that are connected to the telecommunication network 1102. For example, the telecommunication network 1102 may provide Ultra Reliable Low Latency Communication (URLLC) services to some UEs, while providing enhanced Mobile Broadband (eMBB) services to other UEs, and / or massive Machine Type Communication (mMTC) / massive Internet of Things (IoT) services to yet further UEs.

[0092] In some examples, the UEs 1112 are configured to transmit and / or receive information without direct human interaction. For instance, a UE may be designed to transmit information to the access network 1104 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network 1104. Additionally, a UE may be configured for operating in single- or multi-Radio Access Technology (RAT) or multi-standard mode. For example, a UE may operate with any one or combination of WiFi, New Radio (NR), and LTE, i.e. being configured for Multi-Radio Dual Connectivity (MR-DC), such as Evolved UMTS Terrestrial RAN (E-UTRAN) NR - Dual Connectivity (EN-DC).

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

[0094] The hub 1114 may have a constant / persistent or intermittent connection to the network node 1110B. The hub 1114 may also allow for a different communication scheme and / or schedule between the hub 1114 and UEs (e.g., UE 1112C and / or 1112D), and between the hub 1114 and the core network 1106. In other examples, the hub 1114 is connected to the core network 1106 and / or one or more UEs via a wired connection. Moreover, the hub 1114 may be configured to connect to a Machine-to-Machine (M2M) service provider over the access network 1104 and / or to another UE over a direct connection. In some scenarios, UEs may establish a wireless connection with the network nodes 1110 while still connected via the hub 1114 via awired or wireless connection. In some embodiments, the hub 1114 may be a dedicated hub – that is, a hub whose primary function is to route communications to / from the UEs from / to the network node 1110B. In other embodiments, the hub 1114 may be a non-dedicated hub – that is, a device which is capable of operating to route communications between the UEs and the network node 1110B, but which is additionally capable of operating as a communication start and / or end point for certain data channels.

[0095] Figure 12 shows a UE 1200 in accordance with some embodiments. As used herein, a UE refers to a device capable, configured, arranged, and / or operable to communicate wirelessly with network nodes and / or other UEs. Examples of a UE include, but are not limited to, a smart phone, mobile phone, cell phone, Voice over Internet Protocol (VoIP) phone, wireless local loop phone, desktop computer, Personal Digital Assistant (PDA), wireless camera, gaming console or device, music storage device, playback appliance, wearable terminal device, wireless endpoint, mobile station, tablet, laptop, Laptop Embedded Equipment (LEE), Laptop Mounted Equipment (LME), smart device, wireless Customer Premise Equipment (CPE), vehicle, vehicle-mounted or vehicle embedded / integrated wireless device, etc. Other examples include any UE identified by the 3GPP, including a Narrowband Internet of Things (NB-IoT) UE, a Machine Type Communication (MTC) UE, and / or an enhanced MTC (eMTC) UE.

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

[0097] The UE 1200 includes processing circuitry 1202 that is operatively coupled via a bus 1204 to an input / output interface 1206, a power source 1208, memory 1210, a communication interface 1212, and / or any other component, or any combination thereof. Certain UEs may utilize all or a subset of the components shown in Figure 12. The level of integration between the components may vary from one UE to another UE. Further, certain UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

[0098] The processing circuitry 1202 is configured to process instructions and data and may be configured to implement any sequential state machine operative to execute instructions stored as machine-readable computer programs in the memory 1210. The processing circuitry 1202 may be implemented as one or more hardware-implemented state machines (e.g., in discrete logic, Field Programmable Gate Arrays (FPGAs), Application Specific Integrated Circuits (ASICs), etc.); programmable logic together with appropriate firmware; one or more stored computer programs, general purpose processors, such as a microprocessor or Digital Signal Processor (DSP), together with appropriate software; or any combination of the above. For example, the processing circuitry 1202 may include multiple Central Processing Units (CPUs).

[0099] In the example, the input / output interface 1206 may be configured to provide an interface or interfaces to an input device, output device, or one or more input and / or output devices. Examples of an output device include a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smartcard, another output device, or any combination thereof. An input device may allow a user to capture information into the UE 1200. Examples of an input device include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a web camera, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smartcard, and the like. The presence-sensitive display may include a capacitive or resistive touch sensor to sense input from a user. A sensor may be, for instance, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, a biometric sensor, etc., or any combination thereof. An output device may use the same type of interface port as an input device. For example, a Universal Serial Bus (USB) port may be used to provide an input device and an output device.

[0100] In some embodiments, the power source 1208 is structured as a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic device, or power cell, may be used. The power source 1208 may further include power circuitry for delivering power from the power source 1208 itself, and / or an external power source, to the various parts of the UE 1200 via input circuitry or an interface such as an electrical power cable. Delivering power may be, for example, for charging of the power source 1208. Power circuitry may perform any formatting, converting, or other modification to the power from the power source 1208 to make the power suitable for the respective components of the UE 1200 to which power is supplied.

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

[0102] The memory 1210 may be configured to include a number of physical drive units, such as Redundant Array of Independent Disks (RAID), flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, High Density Digital Versatile Disc (HD- DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, Holographic Digital Data Storage (HDDS) optical disc drive, external mini Dual In-line Memory Module (DIMM), Synchronous Dynamic RAM (SDRAM), external micro-DIMM SDRAM, smartcard memory such as a tamper resistant module in the form of a Universal Integrated Circuit Card (UICC) including one or more Subscriber Identity Modules (SIMs), such as a Universal SIM (USIM) and / or Internet Protocol Multimedia Services Identity Module (ISIM), other memory, or any combination thereof. The UICC may for example be an embedded UICC (eUICC), integrated UICC (iUICC) or a removable UICC commonly known as a ‘SIM card.’ The memory 1210 may allow the UE 1200 to access instructions, application programs, and the like stored on transitory or non-transitory memory media, to off-load data, or to upload data. An article of manufacture, such as one utilizing a communication system, may be tangibly embodied as or in the memory 1210, which may be or comprise a device-readable storage medium.

[0103] The processing circuitry 1202 may be configured to communicate with an access network or other network using the communication interface 1212. The communication interface 1212 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna 1222. The communication interface 1212 may include one or more transceivers used to communicate, such as by communicating with one or more remote transceivers of another device capable of wireless communication (e.g., another UE or a network node in an access network). Each transceiver may include a transmitter 1218 and / or a receiver 1220 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth). Moreover, the transmitter 1218 and receiver 1220 may be coupled to one or more antennas (e.g., the antenna 1222) and may share circuit components, software, or firmware, or alternatively be implemented separately.

[0104] In the illustrated embodiment, communication functions of the communication interface 1212 may include cellular communication, WiFi communication, LPWANcommunication, data communication, voice communication, multimedia communication, short- range communications such as Bluetooth, NFC, location-based communication such as the use of the Global Positioning System (GPS) to determine a location, another like communication function, or any combination thereof. Communications may be implemented according to one or more communication protocols and / or standards, such as IEEE 802.11, Code Division Multiplexing Access (CDMA), Wideband CDMA (WCDMA), GSM, LTE, NR, UMTS, WiMax, Ethernet, Transmission Control Protocol / Internet Protocol (TCP / IP), Synchronous Optical Networking (SONET), Asynchronous Transfer Mode (ATM), Quick User Datagram Protocol Internet Connection (QUIC), Hypertext Transfer Protocol (HTTP), and so forth.

[0105] Regardless of the type of sensor, a UE may provide an output of data captured by its sensors, through its communication interface 1212, via a wireless connection to a network node. Data captured by sensors of a UE can be communicated through a wireless connection to a network node via another UE. The output may be periodic (e.g., once every 15 minutes if it reports the sensed temperature), random (e.g., to even out the load from reporting from several sensors), in response to a triggering event (e.g., when moisture is detected an alert is sent), in response to a request (e.g., a user initiated request), or a continuous stream (e.g., a live video feed of a patient).

[0106] As another example, a UE comprises an actuator, a motor, or a switch related to a communication interface configured to receive wireless input from a network node via a wireless connection. In response to the received wireless input the states of the actuator, the motor, or the switch may change. For example, the UE may comprise a motor that adjusts the control surfaces or rotors of a drone in flight according to the received input or to a robotic arm performing a medical procedure according to the received input.

[0107] A UE, when in the form of an IoT device, may be a device for use in one or more application domains, these domains comprising, but not limited to, city wearable technology, extended industrial application, and healthcare. Non-limiting examples of such an IoT device are a device which is or which is embedded in: a connected refrigerator or freezer, a television, a connected lighting device, an electricity meter, a robot vacuum cleaner, a voice controlled smart speaker, a home security camera, a motion detector, a thermostat, a smoke detector, a door / window sensor, a flood / moisture sensor, an electrical door lock, a connected doorbell, an air conditioning system like a heat pump, an autonomous vehicle, a surveillance system, a weather monitoring device, a vehicle parking monitoring device, an electric vehicle charging station, a smart watch, a fitness tracker, a head-mounted display for Augmented Reality (AR) or VR, a wearable for tactile augmentation or sensory enhancement, a water sprinkler, an animal- oritem-tracking device, a sensor for monitoring a plant or animal, an industrial robot, an Unmanned Aerial Vehicle (UAV), and any kind of medical device, like a heart rate monitor or a remote controlled surgical robot. A UE in the form of an IoT device comprises circuitry and / or software in dependence of the intended application of the IoT device in addition to other components as described in relation to the UE 1200 shown in Figure 12.

[0108] As yet another specific example, in an IoT scenario, a UE may represent a machine or other device that performs monitoring and / or measurements and transmits the results of such monitoring and / or measurements to another UE and / or a network node. The UE may in this case be an M2M device, which may in a 3GPP context be referred to as an MTC device. As one particular example, the UE may implement the 3GPP NB-IoT standard. In other scenarios, a UE may represent a vehicle, such as a car, a bus, a truck, a ship, an airplane, or other equipment that is capable of monitoring and / or reporting on its operational status or other functions associated with its operation.

[0109] In practice, any number of UEs may be used together with respect to a single use case. For example, a first UE might be or be integrated in a drone and provide the drone’s speed information (obtained through a speed sensor) to a second UE that is a remote controller operating the drone. When the user makes changes from the remote controller, the first UE may adjust the throttle on the drone (e.g., by controlling an actuator) to increase or decrease the drone’s speed. The first and / or the second UE can also include more than one of the functionalities described above. For example, a UE might comprise the sensor and the actuator and handle communication of data for both the speed sensor and the actuators.

[0110] Figure 13 shows a network node 1300 in accordance with some embodiments. As used herein, network node refers to equipment capable, configured, arranged, and / or operable to communicate directly or indirectly with a UE and / or with other network nodes or equipment in a telecommunication network. Examples of network nodes include, but are not limited to, APs (e.g., radio APs), Base Stations (BSs) (e.g., radio BSs, Node Bs, evolved Node Bs (eNBs), NR Node Bs (gNBs)), and O-RAN nodes or components of an O-RAN node (e.g., O-RU, O-DU, O- CU).

[0111] Base stations may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and so, depending on the provided amount of coverage, may be referred to as femto base stations, pico base stations, micro base stations, or macro base stations. A base station may be a relay node or a relay donor node controlling a relay. A network node may also include one or more (or all) parts of a distributed radio base station such as centralized digital units, distributed units (e.g., in an O-RAN access node), and / orRemote Radio Units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such RRUs may or may not be integrated with an antenna as an antenna integrated radio. Parts of a distributed radio base station may also be referred to as nodes in a Distributed Antenna System (DAS).

[0112] Other examples of network nodes include multiple Transmission Point (multi-TRP) 5G access nodes, Multi-Standard Radio (MSR) equipment such as MSR BSs, network controllers such as Radio Network Controllers (RNCs) or BS Controllers (BSCs), Base Transceiver Stations (BTSs), transmission points, transmission nodes, Multi-Cell / Multicast Coordination Entities (MCEs), Operation and Maintenance (O&M) nodes, Operations Support System (OSS) nodes, Self-Organizing Network (SON) nodes, positioning nodes (e.g., Evolved Serving Mobile Location Centers (E-SMLCs)), and / or Minimization of Drive Tests (MDTs).

[0113] The network node 1300 includes processing circuitry 1302, memory 1304, a communication interface 1306, and a power source 1308. The network node 1300 may be composed of multiple physically separate components (e.g., a NodeB component and an RNC component, or a BTS component and a BSC component, etc.), which may each have their own respective components. In certain scenarios in which the network node 1300 comprises multiple separate components (e.g., BTS and BSC components), one or more of the separate components may be shared among several network nodes. For example, a single RNC may control multiple NodeBs. In such a scenario, each unique NodeB and RNC pair may in some instances be considered a single separate network node. In some embodiments, the network node 1300 may be configured to support multiple RATs. In such embodiments, some components may be duplicated (e.g., separate memory 1304 for different RATs) and some components may be reused (e.g., a same antenna 1310 may be shared by different RATs). The network node 1300 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 1300, for example GSM, WCDMA, LTE, NR, WiFi, Zigbee, Z-wave, Long Range Wide Area Network (LoRaWAN), Radio Frequency Identification (RFID), or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within the network node 1300.

[0114] The processing circuitry 1302 may comprise a combination of one or more of a microprocessor, controller, microcontroller, CPU, DSP, ASIC, FPGA, or any other suitable computing device, resource, or combination of hardware, software, and / or encoded logic operable to provide, either alone or in conjunction with other network node 1300 components, such as the memory 1304, to provide network node 1300 functionality.

[0115] In some embodiments, the processing circuitry 1302 includes a System on a Chip (SOC). In some embodiments, the processing circuitry 1302 includes one or more of Radio Frequency (RF) transceiver circuitry 1312 and baseband processing circuitry 1314. In some embodiments, the RF transceiver circuitry 1312 and the baseband processing circuitry 1314 may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units. In alternative embodiments, part or all of the RF transceiver circuitry 1312 and the baseband processing circuitry 1314 may be on the same chip or set of chips, boards, or units.

[0116] The memory 1304 may comprise any form of volatile or non-volatile computer- readable memory including, without limitation, persistent storage, solid state memory, remotely mounted memory, magnetic media, optical media, RAM, ROM, mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD), or a Digital Video Disk (DVD)), and / or any other volatile or non-volatile, non-transitory device-readable, and / or computer-executable memory devices that store information, data, and / or instructions that may be used by the processing circuitry 1302. The memory 1304 may store any suitable instructions, data, or information, including a computer program, software, an application including one or more of logic, rules, code, tables, and / or other instructions capable of being executed by the processing circuitry 1302 and utilized by the network node 1300. The memory 1304 may be used to store any calculations made by the processing circuitry 1302 and / or any data received via the communication interface 1306. In some embodiments, the processing circuitry 1302 and the memory 1304 are integrated.

[0117] The communication interface 1306 is used in wired or wireless communication of signaling and / or data between a network node, access network, and / or UE. As illustrated, the communication interface 1306 comprises port(s) / terminal(s) 1316 to send and receive data, for example to and from a network over a wired connection. The communication interface 1306 also includes radio front-end circuitry 1318 that may be coupled to, or in certain embodiments a part of, the antenna 1310. The radio front-end circuitry 1318 comprises filters 1320 and amplifiers 1322. The radio front-end circuitry 1318 may be connected to the antenna 1310 and the processing circuitry 1302. The radio front-end circuitry 1318 may be configured to condition signals communicated between the antenna 1310 and the processing circuitry 1302. The radio front-end circuitry 1318 may receive digital data that is to be sent out to other network nodes or UEs via a wireless connection. The radio front-end circuitry 1318 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of the filters 1320 and / or the amplifiers 1322. The radio signal may then be transmitted via the antenna 1310. Similarly, when receiving data, the antenna 1310 may collect radio signals whichare then converted into digital data by the radio front-end circuitry 1318. The digital data may be passed to the processing circuitry 1302. In other embodiments, the communication interface 1306 may comprise different components and / or different combinations of components.

[0118] In certain alternative embodiments, the network node 1300 does not include separate radio front-end circuitry 1318; instead, the processing circuitry 1302 includes radio front-end circuitry and is connected to the antenna 1310. Similarly, in some embodiments, all or some of the RF transceiver circuitry 1312 is part of the communication interface 1306. In still other embodiments, the communication interface 1306 includes the one or more ports or terminals 1316, the radio front-end circuitry 1318, and the RF transceiver circuitry 1312 as part of a radio unit (not shown), and the communication interface 1306 communicates with the baseband processing circuitry 1314, which is part of a digital unit (not shown).

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

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

[0121] The power source 1308 provides power to the various components of the network node 1300 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). The power source 1308 may further comprise, or be coupled to, power management circuitry to supply the components of the network node 1300 with power for performing the functionality described herein. For example, the network node 1300 may be connectable to an external power source (e.g., the power grid or an electricity outlet) via input circuitry or an interface such as an electrical cable, whereby the external power source supplies power to power circuitry of the power source 1308. As a further example, the power source 1308 may comprise a source of power in the form of a battery or battery packwhich is connected to, or integrated in, power circuitry. The battery may provide backup power should the external power source fail.

[0122] Embodiments of the network node 1300 may include additional components beyond those shown in Figure 13 for providing certain aspects of the network node’s functionality, including any of the functionality described herein and / or any functionality necessary to support the subject matter described herein. For example, the network node 1300 may include user interface equipment to allow input of information into the network node 1300 and to allow output of information from the network node 1300. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node 1300.

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

[0124] The host 1400 includes processing circuitry 1402 that is operatively coupled via a bus 1404 to an input / output interface 1406, a network interface 1408, a power source 1410, and memory 1412. Other components may be included in other embodiments. Features of these components may be substantially similar to those described with respect to the devices of previous figures, such as Figures 12 and 13, such that the descriptions thereof are generally applicable to the corresponding components of the host 1400.

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

[0126] Figure 15 is a block diagram illustrating a virtualization environment 1500 in which functions implemented by some embodiments may be virtualized. In the present context, virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices, and networking resources. As used herein, virtualization can be applied to any device described herein, or components thereof, and relates to an implementation in which at least a portion of the functionality is implemented as one or more virtual components. Some or all of the functions described herein may be implemented as virtual components executed by one or more Virtual Machines (VMs) implemented in one or more virtual environments 1500 hosted by one or more of hardware nodes, such as a hardware computing device that operates as a network node, UE, core network node, or host. Further, in embodiments in which the virtual node does not require radio connectivity (e.g., a core network node or host), then the node may be entirely virtualized. In some embodiments, the virtualization environment 1500 includes components defined by the O-RAN Alliance, such as an O-Cloud environment orchestrated by a Service Management and Orchestration Framework via an O-2 interface.

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

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

[0129] The VMs 1508 comprise virtual processing, virtual memory, virtual networking, or interface and virtual storage, and may be run by a corresponding virtualization layer 1506.Different embodiments of the instance of a virtual appliance 1502 may be implemented on one or more of the VMs 1508, and the implementations may be made in different ways. Virtualization of the hardware is in some contexts referred to as Network Function Virtualization (NFV). NFV may be used to consolidate many network equipment types onto industry standard high volume server hardware, physical switches, and physical storage, which can be located in data centers and customer premise equipment.

[0130] In the context of NFV, a VM 1508 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non-virtualized machine. Each of the VMs 1508, and that part of the hardware 1504 that executes that VM, be it hardware dedicated to that VM and / or hardware shared by that VM with others of the VMs 1508, forms separate virtual network elements. Still in the context of NFV, a virtual network function is responsible for handling specific network functions that run in one or more VMs 1508 on top of the hardware 1504 and corresponds to the application 1502.

[0131] The hardware 1504 may be implemented in a standalone network node with generic or specific components. The hardware 1504 may implement some functions via virtualization. Alternatively, the hardware 1504 may be part of a larger cluster of hardware (e.g., such as in a data center or CPE) where many hardware nodes work together and are managed via management and orchestration 1510, which, among others, oversees lifecycle management of the applications 1502. In some embodiments, the hardware 1504 is coupled to one or more radio units that each include one or more transmitters and one or more receivers that may be coupled to one or more antennas. Radio units may communicate directly with other hardware nodes via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a RAN or a base station. In some embodiments, some signaling can be provided with the use of a control system 1512 which may alternatively be used for communication between hardware nodes and radio units.

[0132] Figure 16 shows a communication diagram of a host 1602 communicating via a network node 1604 with a UE 1606 over a partially wireless connection in accordance with some embodiments. Example implementations, in accordance with various embodiments, of the UE (such as the UE 1112A of Figure 11 and / or the UE 1200 of Figure 12), the network node (such as the network node 1110A of Figure 11 and / or the network node 1300 of Figure 13), and the host (such as the host 1116 of Figure 11 and / or the host 1400 of Figure 14) discussed in the preceding paragraphs will now be described with reference to Figure 16.

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

[0134] The network node 1604 includes hardware enabling it to communicate with the host 1602 and the UE 1606. The connection 1660 may be direct or pass through a core network (like the core network 1106 of Figure 11) and / or one or more other intermediate networks, such as one or more public, private, or hosted networks. For example, an intermediate network may be a backbone network or the Internet.

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

[0136] The OTT connection 1650 may extend via the connection 1660 between the host 1602 and the network node 1604 and via a wireless connection 1670 between the network node 1604 and the UE 1606 to provide the connection between the host 1602 and the UE 1606. The connection 1660 and the wireless connection 1670, over which the OTT connection 1650 may be provided, have been drawn abstractly to illustrate the communication between the host 1602 and the UE 1606 via the network node 1604, without explicit reference to any intermediary devices and the precise routing of messages via these devices.

[0137] As an example of transmitting data via the OTT connection 1650, in step 1608, the host 1602 provides user data, which may be performed by executing a host application. In some embodiments, the user data is associated with a particular human user interacting with the UE 1606. In other embodiments, the user data is associated with a UE 1606 that shares data with the host 1602 without explicit human interaction. In step 1610, the host 1602 initiates a transmission carrying the user data towards the UE 1606. The host 1602 may initiate the transmissionresponsive to a request transmitted by the UE 1606. The request may be caused by human interaction with the UE 1606 or by operation of the client application executing on the UE 1606. The transmission may pass via the network node 1604 in accordance with the teachings of the embodiments described throughout this disclosure. Accordingly, in step 1612, the network node 1604 transmits to the UE 1606 the user data that was carried in the transmission that the host 1602 initiated, in accordance with the teachings of the embodiments described throughout this disclosure. In step 1614, the UE 1606 receives the user data carried in the transmission, which may be performed by a client application executed on the UE 1606 associated with the host application executed by the host 1602.

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

[0139] One or more of the various embodiments improve the performance of OTT services provided to the UE 1606 using the OTT connection 1650, in which the wireless connection 1670 forms the last segment.

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

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

[0142] Although the computing devices described herein (e.g., UEs, network nodes, hosts) may include the illustrated combination of hardware components, other embodiments may comprise computing devices with different combinations of components. It is to be understood that these computing devices may comprise any suitable combination of hardware and / or software needed to perform the tasks, features, functions, and methods disclosed herein. Determining, calculating, obtaining, or similar operations described herein may be performed by processing circuitry, which may process information by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and / or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination. Moreover, while components are depicted as single boxes located within a larger box or nested within multiple boxes, in practice computing devices may comprise multiple different physical components that make up a single illustrated component, and functionality may be partitioned between separate components. For example, a communication interface may be configured to include any of the components described herein, and / or the functionality of the components may be partitioned between the processing circuitry and the communicationinterface. In another example, non-computationally intensive functions of any of such components may be implemented in software or firmware and computationally intensive functions may be implemented in hardware.

[0143] In certain embodiments, some or all of the functionality described herein may be provided by processing circuitry executing instructions stored in memory, which in certain embodiments may be a computer program product in the form of a non-transitory computer- readable storage medium. In alternative embodiments, some or all of the functionality may be provided by the processing circuitry without executing instructions stored on a separate or discrete device-readable storage medium, such as in a hardwired manner. In any of those particular embodiments, whether executing instructions stored on a non-transitory computer- readable storage medium or not, the processing circuitry can be configured to perform the described functionality. The benefits provided by such functionality are not limited to the processing circuitry alone or to other components of the computing device, but are enjoyed by the computing device as a whole and / or by end users and a wireless network generally.

[0144] Some example embodiments of the present disclosure are as follows: Group A Embodiments

[0145] Embodiment 1: A method performed by a User Equipment, UE, for providing feedback to a network node regarding a frequency difference between Transmission and Reception Points, TRPs, the method comprising any one or more of the following: determining (1006) a frequency difference between a transmit frequency of a first TRP and a transmit frequency of a second TRP; transmitting (1008), to a network node, a quantized frequency difference value indicative of the determined frequency difference between the transmit frequency of the first TRP and the transmit frequency of the second TRP; wherein values of one or more parameters related to quantization of the determined frequency difference to provide the quantized frequency difference value are either configured by the network node or determined by the UE as a function of carrier frequency on which the first TRP and the second TRP transmit .

[0146] Embodiment 2: The method of embodiment 1, wherein the one or more parameters related to quantization of the determined frequency difference to provide the quantized frequency difference value comprise any one or more of the following: • a frequency step size used for quantization of the determined frequency difference, • a frequency range of a range of values used for quantization of the determined frequency difference, • a number of bits, N, used for quantization of the determined frequency difference, • a maximum correctable frequency error.

[0147] Embodiment 3: The method of embodiment 1, wherein the one or more parameters related to quantization of the determined frequency difference to provide the quantized frequency difference value comprise a frequency step size used for quantization of the determined frequency difference and a frequency range of a range of values used for quantization of the determined frequency difference.

[0148] Embodiment 4: The method of embodiment 1, wherein the one or more parameters related to quantization of the determined frequency difference to provide the quantized frequency difference value comprise a frequency step size used for quantization of the determined frequency difference and a frequency range of a range of values used for quantization of the determined frequency difference.

[0149] Embodiment 5: The method of embodiment 1, wherein the one or more parameters related to quantization of the determined frequency difference to provide the quantized frequency difference value comprise a number of bits, N, used for quantization of the determined frequency difference.

[0150] Embodiment 6: The method of embodiment 1, wherein the one or more parameters related to quantization of the determined frequency difference to provide the quantized frequency difference value comprise a frequency step size used for quantization of the determined frequency difference.

[0151] Embodiment 7: The method of embodiment 1, wherein the one or more parameters related to quantization of the determined frequency difference to provide the quantized frequency difference value comprise a number of bits, N, used for quantization of the determined frequency difference and a frequency step size used for quantization of the determined frequency difference.

[0152] Embodiment 8: The method of embodiment 1, wherein the one or more parameters related to quantization of the determined frequency difference to provide the quantized frequency difference value comprise a frequency step size used for quantization of the determined frequency difference and a maximum correctable frequency error.

[0153] Embodiment 9: The method of embodiment 1, wherein the one or more parameters related to quantization of the determined frequency difference to provide the quantized frequency difference value comprise a number of bits, N, used for quantization of the determined frequency difference and a maximum correctable frequency error.

[0154] Embodiment 10: The method of any of embodiments 1 to 9, wherein a value of at least one of the one or more parameters related to quantization of the determined frequency difference to provide the quantized frequency difference value is predefined.

[0155] Embodiment 11: The method of any of embodiments 1 to 9, wherein the values of the one or more parameters related to quantization of the determined frequency difference to provide the quantized frequency difference value are predefined.

[0156] Embodiment 12: The method of any of embodiments 1 to 9, further comprising receiving (1004), from the network node, information that explicitly or implicitly indicates the value of at least one of the one or more parameters related to quantization of the determined frequency difference to provide the quantized frequency difference value.

[0157] Embodiment 13: The method of any of embodiments 1 to 9, further comprising receiving (1004), from the network node, information that explicitly or implicitly indicates the values of the one or more parameters related to quantization of the determined frequency difference to provide the quantized frequency difference value.

[0158] Embodiment 14: The method of embodiment 12 or 13, wherein the one or more parameters related to quantization of the determined frequency difference to provide the quantized frequency difference value comprise two or more parameters that are separately configured via the information received from the network node.

[0159] Embodiment 15: The method of embodiment 12 or 13, wherein the one or more parameters related to quantization of the determined frequency difference to provide the quantized frequency difference value comprise two or more parameters that are jointly configured via the information received from the network node.

[0160] Embodiment 16: The method of any of embodiments 12 to 15, wherein the information received from the network node comprises a CSI report configuration comprising information of a first reference signal transmitted from the first TRP and a second reference signal transmitted from the second TRP.

[0161] Embodiment 17: The method of embodiment 16, wherein determining (1006) the frequency difference between the transmit frequency of the first TRP and the transmit frequency of the second TRP comprises measuring the frequency difference based on the first and the second reference signals.

[0162] Embodiment 18: The method of embodiment 16 or 17, wherein the transmitting (1008) to the network node the quantized frequency difference value is according to the CSI report configuration.

[0163] Embodiment 19: The method of any of embodiments 12 to 15, wherein the information received from the network node comprises a serving cell configuration.

[0164] Embodiment 20: The method of any of embodiments 1 to 19, wherein the first TRP and the second TRP are TRPs used for coherent joint transmission to the UE.

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

[0166] Embodiment 22: A method performed by a network node for compensating for a frequency difference between Transmission and Reception Points, TRPs, based on feedback from User Equipment, UE, the method comprising: receiving (1008), from a UE, a quantized frequency difference value indicative of a frequency difference between a transmit frequency of a first TRP and a transmit frequency of a second TRP, wherein values of one or more parameters related to quantization of the frequency difference are either configured by the network node or determined by the UE as a function of carrier frequency on which the first TRP and the second TRP transmit; and performing (1010) one or more actions based on the quantized frequency difference value.

[0167] Embodiment 23: The method of embodiment 22, further comprising determining and configuring(1004) the UE with the values of one or more parameters related to quantization of the frequency difference.

[0168] Embodiment 24: The method of embodiment 23, wherein the determining can be based on one or more of a carrier frequency on which the first TRP and the second TRP transmit, a reporting period of the UE feedback of the frequency difference, and a maximum frequency error of each of the first TRP and the second TRP.

[0169] Embodiment 25: The method of embodiment 22, wherein the one or more parameters related to quantization of the determined frequency difference to provide the quantized frequency difference value comprise any one or more of the following: • a frequency step size used for quantization of the determined frequency difference, • a frequency range of a range of values used for quantization of the determined frequency difference, • a number of bits, N, used for quantization of the determined frequency difference, • a maximum correctable frequency error.

[0170] Embodiment 26: The method of embodiment 22, wherein the one or more parameters related to quantization of the determined frequency difference to provide the quantized frequency difference value comprise a frequency step size used for quantization of the determined frequency difference and a frequency range of a range of values used for quantization of the determined frequency difference.

[0171] Embodiment 27: The method of embodiment 22, wherein the one or more parameters related to quantization of the determined frequency difference to provide the quantized frequency difference value comprise a frequency step size used for quantization of the determined frequency difference and a frequency range of a range of values used for quantization of the determined frequency difference.

[0172] Embodiment 28: The method of embodiment 22, wherein the one or more parameters related to quantization of the determined frequency difference to provide the quantized frequency difference value comprise a number of bits, N, used for quantization of the determined frequency difference.

[0173] Embodiment 29: The method of embodiment 22, wherein the one or more parameters related to quantization of the determined frequency difference to provide the quantized frequency difference value comprise a frequency step size used for quantization of the determined frequency difference.

[0174] Embodiment 30: The method of embodiment 22, wherein the one or more parameters related to quantization of the determined frequency difference to provide the quantized frequency difference value comprise a number of bits, N, used for quantization of the determined frequency difference and a frequency step size used for quantization of the determined frequency difference.

[0175] Embodiment 31: The method of embodiment 22, wherein the one or more parameters related to quantization of the determined frequency difference to provide the quantized frequency difference value comprise a frequency step size used for quantization of the determined frequency difference and a maximum correctable frequency error.

[0176] Embodiment 32: The method of embodiment 22, wherein the one or more parameters related to quantization of the determined frequency difference to provide the quantized frequency difference value comprise a number of bits, N, used for quantization of the determined frequency difference and a maximum correctable frequency error.

[0177] Embodiment 33: The method of any of embodiments 22 to 32, wherein a value of at least one of the one or more parameters related to quantization of the determined frequency difference to provide the quantized frequency difference value is predefined.

[0178] Embodiment 34: The method of any of embodiments 22 to 32, wherein the values of the one or more parameters related to quantization of the determined frequency difference to provide the quantized frequency difference value are predefined.

[0179] Embodiment 35: The method of any of embodiments 22 to 32, further comprising transmitting (1004), to the UE, information that explicitly or implicitly indicates the value of atleast one of the one or more parameters related to quantization of the determined frequency difference to provide the quantized frequency difference value.

[0180] Embodiment 36: The method of any of embodiments 22 to 32, further comprising transmitting (1004), to the UE, information that explicitly or implicitly indicates the values of the one or more parameters related to quantization of the determined frequency difference to provide the quantized frequency difference value.

[0181] Embodiment 37: The method of embodiment 35 or 36, wherein the one or more parameters related to quantization of the determined frequency difference to provide the quantized frequency difference value comprise two or more parameters that are separately configured via the information transmitted to the UE.

[0182] Embodiment 38: The method of embodiment 35 or 36, wherein the one or more parameters related to quantization of the determined frequency difference to provide the quantized frequency difference value comprise two or more parameters that are jointly configured via the information transmitted to the UE.

[0183] Embodiment 39: The method of any of embodiments 35 to 38, wherein the information transmitted to the UE comprises a CSI report configuration comprising information of a first reference signal transmitted from the first TRP and a second reference signal transmitted from the second TRP.

[0184] Embodiment 40: The method of embodiments 20 and 39, wherein the receiving the quantized frequency difference value is according to the CSI report configuration.

[0185] Embodiment 41: The method of any of embodiments 35 to 40, wherein the information transmitted to the UE comprises a serving cell configuration.

[0186] Embodiment 42: The method of any of embodiments 22 to 41, wherein the first TRP and the second TRP are TRPs used for coherent joint transmission to the UE.

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

[0188] Embodiment 44: A user equipment comprising: processing circuitry configured to perform any of the steps of any of the Group A embodiments; and power supply circuitry configured to supply power to the processing circuitry.

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

[0190] Embodiment 46: A user equipment (UE) comprising: an antenna configured to send and receive wireless signals; radio front-end circuitry connected to the antenna and to processing circuitry, and configured to condition signals communicated between the antenna and the processing circuitry; the processing circuitry being configured to perform any of the steps of any of the Group A embodiments; an input interface connected to the processing circuitry and configured to allow input of information into the UE to be processed by the processing circuitry; an output interface connected to the processing circuitry and configured to output information from the UE that has been processed by the processing circuitry; and a battery connected to the processing circuitry and configured to supply power to the UE.

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

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

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

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

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

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

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

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

[0199] Embodiment 55: The host of the previous 2 embodiments, wherein: the processing circuitry of the host is configured to execute a host application that receives the user data; and the host application is configured to interact with a client application executing on the UE, the client application being associated with the host application.

[0200] Embodiment 56: The host of the any of the previous 2 embodiments, wherein the initiating receipt of the user data comprises requesting the user data.

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

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

[0203] Embodiment 59: A host configured to operate in a communication system to provide an over-the-top (OTT) service, the host comprising: processing circuitry configured to provide user data; and a network interface configured to initiate transmission of the user data to a cellular network for transmission to a user equipment (UE), wherein the UE comprises a communication interface and processing circuitry, the communication interface and processing circuitry of theUE being configured to perform any of the operations of any of the Group A embodiments to receive the user data from the host.

[0204] Embodiment 60: The host of the previous embodiment, wherein the cellular network further includes a network node configured to communicate with the UE to transmit the user data to the UE from the host.

[0205] Embodiment 61: The host of the previous 2 embodiments, wherein: the processing circuitry of the host is configured to execute a host application, thereby providing the user data; and the host application is configured to interact with a client application executing on the UE, the client application being associated with the host application.

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

[0207] Embodiment 63: The method of the previous embodiment, further comprising: at the host, executing a host application associated with a client application executing on the UE to receive the user data from the host application.

[0208] Embodiment 64: The method of the previous embodiment, further comprising: at the host, transmitting input data to the client application executing on the UE, the input data being provided by executing the host application, wherein the user data is provided by the client application in response to the input data from the host application.

[0209] Embodiment 65: A host configured to operate in a communication system to provide an over-the-top (OTT) service, the host comprising: processing circuitry configured to provide user data; and a network interface configured to initiate transmission of the user data to a cellular network for transmission to a user equipment (UE), wherein the UE comprises a communication interface and processing circuitry, the communication interface and processing circuitry of the UE being configured to perform any of the steps of any of the Group A embodiments to transmit the user data to the host.

[0210] Embodiment 66: The host of the previous embodiment, wherein the cellular network further includes a network node configured to communicate with the UE to transmit the user data from the UE to the host.

[0211] Embodiment 67: The host of the previous 2 embodiments, wherein: the processing circuitry of the host is configured to execute a host application, thereby providing the user data;and the host application is configured to interact with a client application executing on the UE, the client application being associated with the host application.

[0212] Embodiment 68: A method implemented by a host configured to operate in a communication system that further includes a network node and a user equipment (UE), the method comprising: at the host, receiving user data transmitted to the host via the network node by the UE, wherein the UE performs any of the steps of any of the Group A embodiments to transmit the user data to the host.

[0213] Embodiment 69: The method of the previous embodiment, further comprising: at the host, executing a host application associated with a client application executing on the UE to receive the user data from the UE.

[0214] Embodiment 70: The method of the previous 2 embodiments, further comprising: at the host, transmitting input data to the client application executing on the UE, the input data being provided by executing the host application, wherein the user data is provided by the client application in response to the input data from the host application.

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

Claims

CLAIMS 1. A method performed by a User Equipment, UE, for providing feedback to a network node regarding a frequency difference between each of a plurality of Transmission and Reception Points, TRPs, and a reference TRP, the method comprising: receiving a configuration of a channel state information, CSI, report for frequency difference feedback; determining (1006) the frequency difference between each of the plurality of TRPs and the reference TRP; determining (1008) a quantized frequency difference value indicative of the determined frequency difference between each of the plurality of TRPs and the reference TRP according to one or more parameters related to quantization of the determined frequency difference, wherein values of the one or more parameters related to quantization of the determined frequency difference to provide the quantized frequency difference value are configured by the network node; and transmitting (1008), to a network node, the quantized frequency difference value for each of the plurality of TRPs.

2. The method of claim 1, wherein the values of the one or more parameters related to quantization of the determined frequency difference to provide the quantized frequency difference value are a function of any one or more of the following: • carrier frequency on which the plurality of TRPs operate, , • Channel State Information (CSI) reporting period, • base station type, • maximum frequency error of the plurality of TRPs.

3. The method of claim 1, wherein the one or more parameters related to quantization of the determined frequency difference to provide the quantized frequency difference value comprise any one or more of the following: • a frequency step size used for quantization of the determined frequency difference, • a frequency range used for quantization of the determined frequency difference, • a number of bits, N, used for quantization of the determined frequency difference, • a maximum frequency quantization error.

4. The method of claim 1, wherein the one or more parameters related to quantization of thedetermined frequency difference to provide the quantized frequency difference value comprise a frequency step size used for quantization of the determined frequency difference.

5. The method of claim 4, wherein the frequency step size used for quantization of the determined frequency difference is a function of Coherent Joint Transmission, CJT, Channel State Information, CSI, reporting period.

6. The method of claim 4, wherein the frequency step size used for quantization of the determined frequency difference is configured to the UE from a network node.

7. The method of any of claims 4 to 6, wherein the one or more parameters related to quantization of the determined frequency difference to provide the quantized frequency difference value further comprise a number of bits, N, used for quantization of the determined frequency difference.

8. The method of any of claims 1 to 7, wherein the quantization is uniform quantization in which quantization levels are uniformly spaced within the frequency range used for quantization of the determined frequency difference.

9. The method of any of claims 1 to 7, wherein the number of bits, N, used for quantization of the determined frequency difference is configured to the UE from a network node.

10. The method of any of claims 1 to 7, wherein the frequency range used for quantization of the determined frequency difference is configured to the UE from a network node.

11. The method of any of claims 1 to 7, wherein the frequency range and the number of bits, N, used for quantization of the determined frequency difference are configured to the UE from a network node.

12. The method of any of claims 4 to 6, wherein the one or more parameters related to quantization of the determined frequency difference to provide the quantized frequency difference value further comprise a maximum frequency quantization error.

13. The method of claim 1, wherein the one or more parameters related to quantization of thedetermined frequency difference to provide the quantized frequency difference value comprise a number of bits, N, used for quantization of the determined frequency difference and a maximum frequency quantization error.

14. The method of claim 1, wherein the one or more parameters related to quantization of the determined frequency difference to provide the quantized frequency difference value comprise a frequency step size used for quantization of the determined frequency difference and a frequency range of a range of values used for quantization of the determined frequency difference.

15. The method of any of claims 1 to 14, wherein a value of at least one of the one or more parameters related to quantization of the determined frequency difference to provide the quantized frequency difference value is predefined.

16. The method of any of claims 1 to 14, wherein the values of the one or more parameters related to quantization of the determined frequency difference to provide the quantized frequency difference value are predefined.

17. The method of any of claims 1 to 14, further comprising receiving (1004), from the network node, information that explicitly or implicitly indicates the value of at least one of the one or more parameters related to quantization of the determined frequency difference to provide the quantized frequency difference value.

18. The method of any of claims 1 to 14, further comprising receiving (1004), from the network node, information that explicitly or implicitly indicates the values of the one or more parameters related to quantization of the determined frequency difference to provide the quantized frequency difference value.

19. The method of claim 17 or 18, wherein the one or more parameters related to quantization of the determined frequency difference to provide the quantized frequency difference value comprise two or more parameters that are separately configured via the information received from the network node.

20. The method of claim 17 or 18, wherein the one or more parameters related to quantization of the determined frequency difference to provide the quantized frequencydifference value comprise two or more parameters that are jointly configured via the information received from the network node.

21. The method of any of claims 1 to 20, wherein the CSI report configuration received from the network node further comprises information of a plurality of reference signals wherein each of the plurality of reference signals is transmitted from either the reference TRP or one of the plurality of TRPs.

22. The method of claim 21, wherein determining (1006) the frequency difference between each of the plurality of TRPs and the reference TRP comprises measuring the frequency difference based on the corresponding reference signals.

23. The method of claim 21 or 22, wherein the transmitting (1008) to the network node the quantized frequency difference value is according to the CSI report configuration.

24. The method of any of claims 17 to 20, wherein the information received from the network node comprises a serving cell configuration.

25. The method of any of claims 1 to 24, wherein one or more of the plurality of TRPs and the reference TRP are TRPs used for coherent joint transmission to the UE.

26. A User Equipment, UE, for providing feedback to a network node regarding a frequency difference between each of a plurality of Transmission and Reception Points, TRPs, and a reference TRP, the UE adapted to: receive a configuration of a channel state information, CSI, report for frequency difference feedback; determine (1006) the frequency difference between each of the plurality of TRPs and the reference TRP; determine (1008) a quantized frequency difference value indicative of the determined frequency difference between each of the plurality of TRPs and the reference TRP according to one or more parameters related to quantization of the determined frequency difference, wherein values of the one or more parameters related to quantization of the determined frequency difference to provide the quantized frequency difference value are configured by the network node; andtransmit (1008), to a network node, the quantized frequency difference value for each of the plurality of TRPs.

27. The UE of claim 26, further adapted to perform the method of any of claims 2 to 25.

28. A User Equipment, UE, (1200) for providing feedback to a network node regarding a frequency difference between Transmission and Reception Points, TRPs, the UE (1200) comprising: a communication interface (1212) comprising a transmitter (1218) and a receiver (1220); and processing circuitry (1202) associated with the communication interface (1212), the processing circuitry (1202) configured to cause the UE (1200) to: receive a configuration of a channel state information, CSI, report for frequency difference feedback; determine (1006) the frequency difference between each of the plurality of TRPs and the reference TRP; determine (1008) a quantized frequency difference value indicative of the determined frequency difference between each of the plurality of TRPs and the reference TRP according to one or more parameters related to quantization of the determined frequency difference, wherein values of the one or more parameters related to quantization of the determined frequency difference to provide the quantized frequency difference value are configured by the network node; and transmit (1008), to a network node, the quantized frequency difference value for each of the plurality of TRPs.

29. The UE (1200) of claim 28, further adapted to perform the method of any of claims 2 to 25.

30. A method performed by a network node for compensating for a frequency difference between a plurality of Transmission and Reception Points, TRPs, and a reference TRP based on feedback from User Equipment, UE, the method comprising: transmitting, to a UE, a configuration of a channel state information, CSI, report for frequency difference feedback; receiving (1008), from the UE, a quantized frequency difference value indicative of afrequency difference between each of a plurality of TRPs and a reference TRP, wherein values of one or more parameters related to quantization of the frequency difference is configured by the network node or determined by the UE; and performing (1010) one or more actions based on the quantized frequency difference value.

31. The method of claim 30, wherein the values of the one or more parameters related to quantization of the determined frequency difference to provide the quantized frequency difference value are a function of any one or more of the following: • carrier frequency on which the plurality of TRPs operate, • Channel State Information (CSI) reporting period, • base station type, • maximum frequency error of the plurality of TRPs.

32. The method of claim 30, further comprising determining and configuring (1004) the UE with the values of one or more parameters related to quantization of the frequency difference.

33. The method of claim 32, wherein the determining can be based on one or more of a carrier frequency on which the plurality of TRPs operate, a reporting period of the UE feedback of the frequency difference, and a maximum frequency error of each of the plurality of TRPs.

34. The method of claim 30, wherein the one or more parameters related to quantization of the determined frequency difference to provide the quantized frequency difference value comprise any one or more of the following: • a frequency step size used for quantization of the determined frequency difference, • a frequency range used for quantization of the determined frequency difference, • a number of bits, N, used for quantization of the determined frequency difference, • a maximum frequency quantization error.

35. The method of claim 30, wherein the one or more parameters related to quantization of the determined frequency difference to provide the quantized frequency difference value comprise a frequency step size used for quantization of the determined frequency difference.

36. The method of claim 35, wherein the frequency step size used for quantization of thedetermined frequency difference is a function of Coherent Joint Transmission, CJT, Channel State Information, CSI, reporting period.

37. The method of claim 35, wherein the frequency step size used for quantization of the determined frequency difference is configured to the UE from a network node based on a Coherent Joint Transmission, CJT, Channel State Information, CSI, reporting period.

38. The method of any of claims 35 to 37, wherein the one or more parameters related to quantization of the determined frequency difference to provide the quantized frequency difference value further comprise a number of bits, N, used for quantization of the determined frequency difference.

39. The method of any of claims 30 to 38, wherein the quantization is uniform quantization in which quantization levels are uniformly spaced within the frequency range used for quantization of the determined frequency difference.

40. The method of any of claims 30 to 38, wherein the number of bits, N, used for quantization of the determined frequency difference is configured to the UE from a network node.

41. The method of any of claims 30 to 38, wherein the frequency range used for quantization of the determined frequency difference is configured to the UE from a network node.

42. The method of any of claims 30 to 38, wherein the frequency range and the number of bits, N, used for quantization of the determined frequency difference are configured to the UE from a network node.

43. The method of any of claims 35 to 37, wherein the one or more parameters related to quantization of the determined frequency difference to provide the quantized frequency difference value further comprise a maximum frequency quantization error.

44. The method of claim 30, wherein the one or more parameters related to quantization of the determined frequency difference to provide the quantized frequency difference value comprise a number of bits, N, used for quantization of the determined frequency difference and amaximum frequency quantization error.

45. The method of any of claims 30 to 44, wherein a value of at least one of the one or more parameters related to quantization of the determined frequency difference to provide the quantized frequency difference value is predefined.

46. The method of any of claims 30 to 44, wherein the values of the one or more parameters related to quantization of the determined frequency difference to provide the quantized frequency difference value are predefined.

47. The method of any of claims 30 to 44, further comprising transmitting (1004), to the UE, information that explicitly or implicitly indicates the value of at least one of the one or more parameters related to quantization of the determined frequency difference to provide the quantized frequency difference value.

48. The method of any of claims 30 to 44, further comprising transmitting (1004), to the UE, information that explicitly or implicitly indicates the values of the one or more parameters related to quantization of the determined frequency difference to provide the quantized frequency difference value.

49. The method of claim 47 or 48, wherein the one or more parameters related to quantization of the determined frequency difference to provide the quantized frequency difference value comprise two or more parameters that are separately configured via the information transmitted to the UE.

50. The method of claim 47 or 48, wherein the one or more parameters related to quantization of the determined frequency difference to provide the quantized frequency difference value comprise two or more parameters that are jointly configured via the information transmitted to the UE.

51. The method of any of claims 47 to 50, wherein the CSI report configuration further comprises information of a plurality of reference signals wherein each of the plurality of reference signals is transmitted from either the reference TRP or one of the plurality of TRPs.

52. The method of claim 51, wherein the receiving the quantized frequency difference value is according to the CSI report configuration.

53. The method of any of claims 47 to 52, wherein the information transmitted to the UE comprises a serving cell configuration.

54. The method of any of claims 30 to 53, wherein one or more of the plurality of TRPs and the reference TRP are TRPs used for coherent joint transmission to the UE.

55. A network node for compensating for a frequency difference between a plurality of Transmission and Reception Points, TRPs, and a reference TRP based on feedback from User Equipment, UE, the network node adapted to: transmit, to a UE, a configuration of a channel state information, CSI, report for frequency difference feedback; receive (1008), from the UE, a quantized frequency difference value indicative of a frequency difference between each of a plurality of TRPs and a reference TRP, wherein values of one or more parameters related to quantization of the frequency difference is configured by the network node or determined by the UE; and perform (1010) one or more actions based on the quantized frequency difference value.

56. The network node of claim 55, further adapted to perform the method of any of claims 31 to 54.

57. A network node for compensating for a frequency difference between a plurality of Transmission and Reception Points, TRPs, and a reference TRP based on feedback from User Equipment, UE, the network node comprising processing circuitry configured to cause the network node to: transmit, to a UE, a configuration of a channel state information, CSI, report for frequency difference feedback; receive (1008), from the UE, a quantized frequency difference value indicative of a frequency difference between each of a plurality of TRPs and a reference TRP, wherein values of one or more parameters related to quantization of the frequency difference is configured by the network node or determined by the UE; and perform (1010) one or more actions based on the quantized frequency difference value.

58. The network node of claim 57, wherein the processing circuitry is further configured to cause the network node to perform the method of any of claims 31 to 54.

Images