UE feedback of downlink frequency difference between TRPs

Abstract

A system and method for user equipment (UE) feedback regarding the downlink frequency difference between transmit / receive points (TRPs) are disclosed. In one embodiment, a method performed by the UE to provide feedback to a network node regarding the frequency difference between each of a plurality of TRPs and a reference TRP includes receiving a setting 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 representing the determined frequency difference between each of the plurality of TRPs and the reference TRP according to one or more parameters relating to the quantization of the determined frequency difference. The method further includes transmitting the quantized frequency difference value to the network node for each of the plurality of TRPs.

Description

[Technical Field]

[0001] Related applications This application claims the benefit of Provisional Patent Application No. 63 / 516,159, filed on 28 July 2023, the disclosure thereof, which is incorporated herein by reference in its entirety.

[0002] This disclosure relates to multiple transmission / reception point (TRP) operation in a cellular communication network, and more specifically to compensating for frequency differences between TRPs, such as TRPs used in coherent joint transmission (CJT). [Background technology]

[0003] NR frame structure The New Radio (NR) of the Third Generation Partnership Project (3GPP®) uses orthogonal frequency division multiplexing (OFDM) in the downlink (i.e., from network nodes, next-generation NodeBs (gNBs), or base stations to user equipment (UEs)). In the uplink (i.e., from UEs to gNBs), 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), are supported. The basic NR physical resources can therefore be viewed as a time-frequency grid, as shown in Figure 1, where resource blocks (RBs) in 14 symbol slots are shown. Each resource block corresponds to 12 consecutive subcarriers in the frequency domain. The resource blocks are numbered in the frequency domain starting from 0 at one end of the system bandwidth. Each resource element corresponds to one OFDM subcarrier between one OFDM symbol intervals.

[0004] NR supports different subcarrier spacing values. The supported subcarrier spacing values ​​(also called different neurology) are Δf = (15 × 2 μΔf is given in kilohertz (kHz), where μ is a non-negative integer and can be one of {0, 1, 2, 3, 4}. Δf = 15 kHz (e.g., μ = 0) is the basic (or reference) subcarrier interval used in LTE as well. μ is also called the neurology.

[0005] In the time domain, downlink and uplink transmissions in NR, like in LTE, are organized into subframes of equal size, each 1 millisecond (ms). These subframes are further divided into multiple slots of equal duration. The slot length depends on the subcarrier interval or neurology, and is 1 / 2 μ Provided by ms. Each slot consists of 14 OFDM symbols in the case of a normal cyclic prefix (CP).

[0006] It is understood that data scheduling in NR can be slot-based. An example is shown in Figure 2 with 14 symbol slots, where the first two symbols include control channels (i.e., physical downlink control channels (PDCCH)) and the rest include data channels (i.e., physical downlink shared channels (PDSCH)). For convenience, subframes will be referred to throughout the following explanation.

[0007] Downlink transmissions can be dynamically scheduled; that is, in each slot, the gNB transmits downlink control information (DCI) regarding which UE the data will be sent to and which resource block within the current downlink slot the data will be sent to. This control signaling is typically transmitted in the first one or two OFDM symbols of each slot in the NR. The control information is carried in a PDCCH, and the data is carried in a PDSCH. The UE first detects and decodes the PDCCH, and if the PDCCH is successfully decoded, 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 the downlink, the UE first decodes the uplink grant in the PDCCH and then transmits data via the Physical Uplink Shared Channel (PUSCH) based on the decoded control information in the uplink grant, such as modulation order, coding rate, and uplink resource allocation.

[0009] Coherent joint PDSCH transmission from multiple TRPs In NR Release 18, coherent joint PDSCH transmission from up to four transmit-receive points (TRPs) is introduced, and each data layer of the PDSCH is transmitted from multiple TRPs. An example is shown in Figure 3, where the PDSCH data s = [s1, s2, …, sr] for r layers T is precoded by the precoding matrix W1 at TRP1 and W2 at TRP2 and then jointly transmitted from two TRPs. The precoding aims to achieve coherent signal combining at the UE for each data layer.

[0010] CSI framework in NR In NR, the UE can be configured with multiple channel state information (CSI) report settings and multiple CSI resource settings. For each CSI report setting, the UE feeds back a CSI report when requested.

[0011] Each CSI report setting includes at least the following information: · CSI resources for channel measurement · Behavior in the time domain, i.e., periodic, semi-persistent, or aperiodic reporting · CSI parameters to be reported, such as rank indicator (RI), precoding matrix indicator (PMI), and channel quality indicator (CQI). Summary of the Invention

[0012] A system and method for user equipment (UE) feedback regarding downlink frequency differences between transmit and receive points (TRPs) are disclosed. In one embodiment, a method performed by a UE to provide feedback to a network node regarding the frequency difference between each of a plurality of TRPs and a reference TRP includes 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 for providing the quantized frequency difference value are set by the network node. The method further includes transmitting the quantized frequency difference value to the network node for each of the plurality of TRPs. By using one or more parameters, feedback overhead can be optimized based on the deployment scenario.

[0013] In one embodiment, values of the one or more parameters related to quantization of the determined frequency difference for providing the quantized frequency difference value are a function of any one or more of the carrier frequencies at which the plurality of TRPs operate, the CSI report period, the base station type, the 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 for providing the quantized frequency difference value include any one or more of the frequency step size used for quantization of the determined frequency difference, the frequency range used for quantization of the determined frequency difference, the number of bits N used for quantization of the determined frequency difference, the maximum frequency quantization error.

[0015] In one embodiment, one or more parameters related to the quantization of the determined frequency difference for providing a quantized frequency difference value include the frequency step size used for quantizing the determined frequency difference. In one embodiment, the frequency step size used for quantizing the determined frequency difference is a function of the coherent co-transmission (CJT) channel state information (CSI) report period. In one embodiment, the frequency step size used for quantizing the determined frequency difference is set from the network node to the UE.

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

[0017] In one embodiment, the quantization is uniform quantization in which the quantization levels are arranged at equal intervals within the frequency range used to quantize the determined frequency difference.

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

[0019] In one embodiment, the frequency range used for quantizing the determined frequency difference is set from the network node to the UE.

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

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

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

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

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

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

[0026] In one embodiment, the method further includes receiving from a network node information that explicitly or implicitly indicates a value for at least one of one or more parameters related to the quantization of a determined frequency difference in order to provide a quantized frequency difference value.

[0027] In one embodiment, the method further includes receiving information from a network node that explicitly or implicitly indicates the values ​​of one or more parameters related to the quantization of a determined frequency difference for providing a quantized frequency difference value. In one embodiment, the one or more parameters related to the quantization of a determined frequency difference for providing a quantized frequency difference value include two or more parameters that are set individually via the information received from the network node. In one embodiment, the one or more parameters related to the quantization of a determined frequency difference for providing a quantized frequency difference value include two or more parameters that are set collectively via the information received from the network node.

[0028] In one embodiment, the CSI report configuration received from the network node further includes information on a plurality of reference signals, where each of the plurality of reference signals is transmitted from a 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 includes measuring the frequency difference based on the corresponding reference signal. In one embodiment, the transmission of the quantized frequency difference value to the network node is in accordance with the CSI report configuration.

[0029] In one embodiment, the information received from the network node includes the serving cell settings.

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

[0031] Corresponding embodiments of the UE are also disclosed. In one embodiment, a UE for providing feedback to a network node regarding the frequency difference between each of a plurality of TRPs and a reference TRP is adapted to receive a setting 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 representing the determined frequency difference between each of the plurality of TRPs and the reference TRP according to one or more parameters relating to the quantization of the determined frequency difference, where the values ​​of one or more parameters relating to the quantization of the determined frequency difference for providing the quantized frequency difference value are set by the network node. The UE is further adapted to transmit the quantized frequency difference value to the network node for each of the plurality of TRPs.

[0032] Embodiments of methods performed by network nodes are also disclosed. In one embodiment, a method performed by network nodes to compensate for frequency differences between a plurality of TRPs and a reference TRP based on feedback from a UE includes sending a CSI report setting for frequency difference feedback to the UE and receiving a quantized frequency difference value from the UE indicating the frequency difference between each of the plurality of TRPs and a reference TRP, where the values ​​of one or more parameters related to the quantization of the frequency difference are set by the network node or determined by the UE. The method further includes performing one or more actions based on the quantized frequency difference value.

[0033] Corresponding embodiments of the network node are also disclosed. In one embodiment, a network node for compensating for frequency differences between multiple TRPs and a reference TRP based on feedback from a UE is adapted to send a CSI report setting for frequency difference feedback to the UE and to receive from the UE a quantized frequency difference value indicating the frequency difference between each of the multiple TRPs and the reference TRP, where the values ​​of one or more parameters related to the quantization of the frequency difference are set 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 explanation of the drawing]

[0034] The accompanying drawings incorporated herein and forming part thereof illustrate several aspects of this disclosure and serve to illustrate the principles of this disclosure together with the description.

[0035] [Figure 1] Figure 1 shows the NR physical resources.

[0036] [Figure 2] Figure 2 shows the NR time-domain structure with a subcarrier spacing of 15 kHz.

[0037] [Figure 3] Figure 3 shows an example of coherent joint PDSCH transmission via two TRPs.

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

[0039] [Figure 5] Figure 5 shows an example of associating or setting different N values ​​for different carrier frequencies.

[0040] [Figure 6] Figure 6 shows an example of residual phase variation during each CJT CSI report cycle.

[0041] [Figure 7] Figure 7 shows an example of setting N and Δfstep individually.

[0042] [Figure 8] Figure 8 shows an example of setting N and Δfstep together.

[0043] [Figure 9] Figure 9 shows examples of different frequency difference report tables predefined in the 3GPP specification.

[0044] [Figure 10] Figure 10 shows the operation of the user equipment (UE) and network node according to at least some of the embodiments described herein.

[0045] [Figure 11] Figure 11 shows examples of communication systems according to several embodiments of the present disclosure.

[0046] [Figure 12]Figure 12 shows a UE according to several embodiments of the present disclosure.

[0047] [Figure 13] Figure 13 shows a network node according to several embodiments of the present disclosure.

[0048] [Figure 14] Figure 14 is a block diagram of a host that may be an embodiment of the host of Figure 11, according to various aspects of the present disclosure described herein.

[0049] [Figure 15] Figure 15 is a block diagram showing a virtualized environment in which the functions implemented by some embodiments of this disclosure can be virtualized.

[0050] [Figure 16] Figure 16 shows a communication diagram of a host communicating with a UE via a network node, partially via a wireless connection, according to some embodiments of the present disclosure. [Modes for carrying out the invention]

[0051] The embodiments described below are intended to provide information that will enable those skilled in the art to carry out the embodiments and represent the best mode of carrying out the embodiments. By reading the following description with reference to the accompanying drawings, those skilled in the art will understand the concepts of this disclosure and recognize applications of these concepts that are not specifically addressed herein. It should be understood that these concepts and applications are included within the scope of this disclosure.

[0052] Some of the embodiments contemplated herein are described more fully with reference to the accompanying drawings. Embodiments are provided as examples to convey the scope of the subject to those skilled in the art.

[0053] In this specification, the term “base station” is used, but this term is not limiting, and the term “base station” may be used interchangeably with terms such as gNodeB (gNB), eNodeB (eNB), or equivalent terms referring to network nodes used in sixth generation (6G) and later.

[0054] Currently, a specific challenge exists. Even if the same nominal transmit frequency is used at different transmit / receive points (TRPs), a transmit frequency difference will occur between TRPs due to the different local oscillators used at each TRP. In the Third Generation Partnership Project (3GPP) New Radio (NR), the maximum transmit frequency error of a base station (e.g., 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, some residual frequency error will be present. These frequency errors mean that the relative phase of signals received from different TRPs changes over time. Therefore, how to reduce and mitigate the effects of transmit frequency differences between TRPs in multi-TRP coherent co-transmission (CJT) remains an unresolved issue.

[0055] One possible solution is user-assisted feedback of the frequency difference between TRPs, where the UE measures the frequency difference between each TRP and the reference TRP based on a reference signal transmitted from the TRP. Using the feedback information, the gNB can pre-compensate for the frequency difference between TRPs before data transmission.

[0056] One problem when providing feedback for frequency differences between TRPs is how to determine the feedback frequency resolution, e.g., 1 Hz or 5 Hz, and the frequency range. A finer frequency resolution can achieve better frequency compensation or correction. On the other hand, a finer frequency resolution means a larger feedback overhead.

[0057] Certain aspects and embodiments of this disclosure may provide solutions to these or other problems. Embodiments of a system and method for UE feedback of the downlink frequency difference between transmit and receive points (TRPs) are disclosed, where the frequency step size and range (i.e., the number of bits used for quantization) are configurable and can be optimized or adapted based on one or more factors. In some embodiments, one or more factors include one or more of the following factors: Carrier frequency, • Channel Status Information (CSI) report cycle, • Base station type (e.g., wide-area, medium-range, or local-area base station) • Maximum frequency error for each TRP.

[0058] In some embodiments, a configurable frequency step size and / or quantization bit count is used for feedback of the downlink frequency difference between TRPs from the UE to the network node (e.g., gNB). The step size and / or quantization bit count can be adapted based on one or more factors, which in some embodiments include one or more of the following factors: Carrier frequency, • CSI report cycle, • Base station type (e.g., wide-area, medium-range, or local-area base station) • Maximum frequency error for each TRP.

[0059] In some embodiments, the step size and / or quantization bit depth are set to the UE by a network node (e.g., a gNB). The step size and quantization bit depth are set jointly in one embodiment (e.g., using a configuration index) or individually in another embodiment.

[0060] Certain embodiments may offer one or more of the following technical advantages: Configurable frequency step size and / or quantization bit count allow for optimization of feedback overhead and CJT performance based on the deployment scenario. Feedback overhead can be reduced for CSI reports with lower carrier frequencies, smaller CSI report periods, and base stations with stricter frequency stability specifications.

[0061] Given a 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, at 0.1 ppm, the maximum frequency error is + / -100 Hz for a carrier frequency of 1 gigahertz (GHz) and + / -1000 Hz for a carrier frequency of 10 GHz. The same applies to the Doppler frequency; that is, for a given UE travel speed, the Doppler frequency associated with a higher carrier frequency is greater than that associated with a lower carrier frequency.

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

[0063] N is the step size Δf step If the number of bits used to report the frequency difference Δf = f2 - f1 between two TRPs is nf ∈ (0, 1, ..., 2), then the frequency difference Δf is given by the index value nf ∈ (0, 1, ..., 2 N-1 ) is reported by, where (Δf)~=(nf-2 N-1 )Δf step Therefore, N can be optimized for different carrier frequencies. The optimized N is either signaled to the UE or predetermined, for example, by being predefined in the 3GPP specification, so that both the gNB and the UE know which value of N will be used in the report.

[0064] For example, N = 6 bits can be used in a system with a carrier frequency of 1 GHz, and N = 9 bits can be used in a system with a carrier frequency of 10 GHz. This is shown in Figure 5. In this example, Δf step = 5 Hz is used in both cases.

[0065] The frequency resolution or step size Δf step determines the residual frequency difference between the TRPs. The residual frequency difference between two TRPs will cause a linear time-varying phase difference, that is, e j2πΔfstept between the two TRPs, as shown in Figure 6. The phase difference between two TRPs in each CSI report instance is assumed to be reported by the UE to the gNB. Therefore, the phase difference between two TRPs can be corrected / compensated by the gNB. The uncompensated phase difference is due to the residual frequency difference between the two TRPs. The longer the CJT CSI report period, the greater the residual phase difference between the two TRPs, and thus the greater the performance degradation of coherent co-transmission. Therefore, when a longer CSI report period is set, a smaller frequency resolution Δf step is desirable.

[0066] Therefore, in another embodiment, Δf step can be set by the gNB based on the CJT CSI report period. For example, when the CSI report period is 10 ms, Δf step = 5 Hz is used, and when the CSI report period is 5 ms, Δf step = 10 Hz can be used. This ensures that the maximum residual phase difference within each CSI period is kept the same in both cases. For the same frequency range, CSI reports with a smaller report period (e.g., 5 ms in this example) require fewer bits (i.e., a smaller N value), and thus the feedback overhead is reduced.

[0067] Generally, frequency stability requirements can vary depending on the type of base station. For example, a base station covering a small area may require + / - 0.1 ppm; on the other hand, a base station covering a large area may require + / - 0.05 ppm. Therefore, the maximum frequency difference between two TRPs can vary depending on the type of base station. Thus, the configurable N and Δf step It is desirable to stop.

[0068] In one embodiment, N and Δf step This is configured separately as part of the CSI report settings for reporting the frequency difference between TRPs. An example is shown in Figure 7.

[0069] In another embodiment, N and Δf step These can be set jointly. An example is shown in Figure 8.

[0070] As in the example above, step size Δf step And if the number of bits N is known, the maximum correctable frequency error Δf max is Δf max =2 N-1 Δf step It can be calculated according to Δf. In some cases, step And instead of setting N, gNB can alternatively use Δf step and Δf max , or N and Δf max This can be set. In the former alternative, UE is Δf step and Δf max The number of bits N can be determined based on this; on the other hand, in the latter case, UE is N and Δf max Based on Δf step It is possible to determine Δf max Δf can be set as a percentage of the carrier frequency or a certain reference frequency. step and Δf max , or N and Δf max These settings can also be configured individually or collectively.

[0071] In one embodiment, N and Δf step The value of can be set as part of the serving cell configuration (for example, as part of the ServingCellConfig information element defined in 3GPP TS 38.331 V17.5.0). This is used to configure the reporting of one or more frequency differences within a serving cell, and any CSI reporting configurations set as part of their respective serving cell configurations for N and Δf step This means using the value of [the specified value].

[0072] In another embodiment, Δf step and Δf max The value of can be set as part of the serving cell configuration (for example, as part of the ServingCellConfig information element defined in 3GPP TS 38.331 V17.5.0). This is used to configure the reporting of one or more frequency differences within a serving cell, and any CSI reporting configuration is set as part of the respective serving cell configuration for Δf step and Δf max This means using the value of [the specified value].

[0073] In yet another embodiment, N and Δf max The value of can be set as part of the serving cell configuration (for example, as part of the ServingCellConfig information element defined in 3GPP TS 38.331 V17.5.0). This is used to configure the reporting of one or more frequency differences within a serving cell, and any CSI reporting configurations set as part of their respective serving cell configurations for N and Δf max This means using the value of [the specified value].

[0074] In another embodiment, different tables may be predefined in the 3GPP specification. These different tables may correspond to different frequency resolutions and / or different frequency ranges for feedback of frequency differences between TRPs. An example is shown in Figure 9. In this embodiment, the step size Δf step, the number of bits N used to report the frequency difference, and the maximum frequency difference Δf max This is implicitly provided by the table selected for reporting the frequency difference between TRPs. One of the predefined tables may be set by the gNB for the UE. Which table is set may be configured as part of the CSI report configuration or the serving cell configuration.

[0075] Feedback of the frequency difference between each TRP and a reference TRP is performed as a standalone CSI report, which is set by the CSI report settings. In one embodiment, N and Δf step This is configured as part of the CSI report settings. Therefore, in different CSI report settings, N and Δf step Different values ​​can be set.

[0076] Note that while the above example uses uniform quantization on a linear scale to simplify the demonstration of the solution, the same method can be applied to other quantization techniques, such as uniform quantization on a logarithmic scale.

[0077] Figure 10 illustrates the operation of UE 1000 and network node 1002 (e.g., a base station such as a gNB) according to at least some of the embodiments described above. Any step is represented by a dashed line / box. As shown in the figure, network node 1002 optionally (i.e., in some embodiments) determines information that explicitly or implicitly indicates the value of one or more parameters (or at least one value of a parameter) related to the quantization of the determined frequency difference between TRPs for providing a quantized frequency difference value, and transmits it to UE 1000 (step 1004). As described above, in some embodiments, the values ​​of two or more parameters may be set jointly or individually. In one example embodiment, the information in step 1004 is included in the CSI report configuration. In another embodiment, the information in step 1004 is included in the serving cell configuration. In one embodiment, network node 1002 determines the value of one or more parameters based on the carrier frequencies transmitted by the first and second TRPs. The values ​​of one or more parameters (or at least one of them) may be further determined based on the reporting period of the frequency difference UE feedback and / or the respective maximum frequency errors of the first and second TRPs.

[0078] UE1000 determines the frequency difference between the transmission frequency of the first TRP and the transmission frequency of the second TRP (for example, based on measurements of reference signals received from the first and second TRPs) (step 1006), and transmits a quantized frequency difference value representing the determined frequency difference (i.e., a quantized version of the determined frequency difference) to the network node 1002 (step 1008). According to embodiments of the present disclosure, the values ​​of one or more parameters related to the quantization of the determined frequency difference for providing the quantized frequency difference value are set by the network node 1002 (for example, in step 1004) or determined by UE1000, and are a function of (a) the carrier frequencies transmitted by the first and second TRPs, (b) the channel state information (CSI) report period of the associated CSI report setting, (c) the base station type of the associated base station, or (d) a combination of any two or more of (a) to (c). In the exemplary embodiment shown in Figure 10, the values ​​of one or more parameters are a function of the carrier frequency. In one embodiment, one or more values ​​(or at least one of them) of the parameters are further a function of the base station type and / or CSI report period. In some embodiments, the values ​​of at least one (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 values ​​of at least one (and potentially all) of the one or more parameters used for quantization are predefined (e.g., by the 3GPP specification).

[0079] As described above, one or more parameters related to the quantization of the determined frequency difference for providing the quantized frequency difference value include one or more of the following: • Frequency step size used for quantizing the determined frequency difference, • The frequency range of the value range used for quantizing the determined frequency difference. • Number of bits N used for quantizing the determined frequency difference, ·Maximum correctable frequency error. However, please note that additional or alternative parameters may be used.

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

[0081] In one example embodiment, the first and second TRPs, which determine the frequency difference, are TRPs used for CJT to UE1000.

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

[0083] Figure 11 shows an example of a communication system 1100 according to several embodiments.

[0084] In this example, the communication system 1100 includes a telecommunications network 1102 which 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 generally be referred to as network nodes 1110), or any other similar Third Generation Partnership Project (3GPP) access nodes or non-3GPP access points (APs). Furthermore, as will be understood by those skilled in the art, a network node is not necessarily limited to an implementation in which the radio portion and the baseband portion are supplied and integrated by a single vendor. Thus, it will be understood that a network node includes a subdivided implementation or a part thereof. For example, in some embodiments, the telecommunications network 1102 includes one or more open RAN (ORAN) network nodes. An ORAN network node is a node in a telecommunications network 1102 that supports ORAN standards (e.g., standards published by the O-RAN Alliance or any similar organization) and can operate alone or in conjunction with other nodes to implement one or more functions of any node in the telecommunications network 1102, including one or more network nodes 1110 and / or core network node 1108.

[0085] Examples of ORAN network nodes include open central units (O-CUs) including open radio units (O-RUs), open distributed units (O-DUs), O-CU control planes (O-CU-CPs), or O-CU user planes (O-CU-UPs), RAN intelligent controllers (near-real-time or non-real-time) hosting software or software plugins such as quasi-real-time control applications (e.g., xApps) or non-real-time control applications (e.g., rApps), or any combination thereof (the adjective "open" specifies support for ORAN standards). Network nodes can support ORAN standards by supporting interfaces defined by ORAN standards, such as A1, F1, W1, E1, E2, X2, Xn interfaces, open fronthaul user plane interfaces, or open fronthaul management plane interfaces. Furthermore, ORAN access nodes may be logical nodes within physical nodes. In addition, ORAN network nodes may be implemented in a virtualized environment (described further later) in which one or more network functions are virtualized. For example, the virtualization environment may include an O-Cloud computing platform organized by a service management and orchestration framework via an O-2 interface defined by the O-RAN Alliance or equivalent technology. Network node 1110 facilitates direct or indirect connectivity of user equipment (UEs) by connecting UEs 1112A, 1112B, 1112C, and 1112D (one or more of which may be generally referred to as UE1112) to the core network 1106 over one or more wireless connections.

[0086] Exemplary wireless communication on a wireless connection includes transmitting and / or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and / or other types of signals suitable for carrying information without using wires, cables, or other physical conductors. Furthermore, in various 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 can facilitate or participate in the communication of data and / or signals, whether wired or wireless. The communication system 1100 may include and / or interface with any type of communication, telecommunications, data, cellular, wireless network, and / or other similar types of systems.

[0087] UE1112 may be any of a broad range of communication devices, including wireless devices that are arranged, configured, and / or operable to communicate wirelessly with network node 1110 and other communication devices. Similarly, network node 1110 is arranged, can communicate, is configured, and / or operable to communicate directly or indirectly with UE1112 and / or other network nodes or devices in telecommunications network 1102 in order to enable and / or provide network access, such as wireless network access, and / or to perform other functions, such as management within telecommunications network 1102.

[0088] In the illustrated example, the core network 1106 connects network node 1110 to one or more hosts, such as host 1116. These connections may be direct or indirect, via one or more intermediate networks or devices. In other examples, network nodes may be directly connected to hosts. The core network 1106 includes one or more core network nodes (e.g., core network node 1108) structured by hardware and software components. The functions of these components may be substantially the same as those described for the UE, network nodes, and / or hosts, and therefore those descriptions are generally applicable to the corresponding components of core network node 1108. An exemplary core network node includes one or more of the following functions: 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 Decryption Function (SIDF), Unified Data Management (UDM), Security Edge Protected Proxy (SEPP), Network Exposure Function (NEF), and / or User Plane Function (UPF).

[0089] Host 1116 may be owned by or under the control of a service provider other than the operator or provider of the access network 1104 and / or the telecommunications network 1102, and may be operated by or on behalf of such service provider. Host 1116 may host a variety of applications and provide one or more services. Examples of such applications include live and pre-recorded audio / video content, data collection services such as acquisition and editing of data on a variety of ambient conditions detected by multiple UEs, analytical functionality, social media, functions for controlling or otherwise interacting with remote devices, functions for alarm and monitoring centers, or any other such functions performed by a server.

[0090] Overall, the communication system 1100 in Figure 11 enables connectivity between the UE, network nodes, and hosts. In that sense, the communication system 1100 may be configured to operate in accordance with predefined rules or procedures, such as certain standards, including, but not limited to, the following: GSM (Global System for Mobile Communications), UMTS (Universal Mobile Telecommunications System), LTE (Long Term Evolution), and / or other suitable second, third, fourth, or fifth generation (2G, 3G, 4G, or 5G) standards, or any applicable future generation standards (e.g., sixth generation (6G)), WLAN (wireless local area network) standards such as the IEEE (Institute of Electrical and Electronics Engineers) 802.11 standard (WiFi), and / or any other suitable wireless communication standards such as WiMax (Worldwide Interoperability for Microwave Access), Bluetooth, Z-Wave, NFC (Near Field Communication), ZigBee, LiFi, and / or any LPWAN (low-power wide-area network) standards such as LoRa and Sigfox.

[0091] In some examples, the telecommunications network 1102 is a cellular network implementing functions standardized by 3GPP. Therefore, the telecommunications network 1102 may support network slicing to provide various logical networks to various devices connected to the telecommunications network 1102. For example, the telecommunications network 1102 may provide ultra-high reliability low latency communication (URLLC) services to some UEs while providing extended mobile broadband (eMBB) services to other UEs, and / or provide massive machine type communication (mMTC) / massive Internet of Things (IoT) services to further UEs.

[0092] In some examples, UE1112 is configured to transmit and / or receive information without direct human interaction. For example, the UE may be designed to transmit information to access network 1104 on a predetermined schedule, triggered by internal or external events, or in response to a request from access network 1104. Additionally, the UE may be configured to operate with single or multiple radio access technologies (RATs) or in multiple standard modes. For example, the UE may be configured to operate with any one or a combination of Wi-Fi, New Radio (NR), and LTE, i.e., for multi-radio dual connectivity (MR-DC) such as Evolutionary UMTS Terrestrial Radio Access Network (E-UTRAN) New Radio-Dual Connectivity (EN-DC).

[0093] In the above example, the hub 1114 communicates with the access network 1104 to facilitate indirect communication between one or more UEs (e.g., UE1112C and / or 1112D) and a network node (e.g., network node 1110B). In some examples, the hub 1114 may be a controller, router, content source and analytics, or any other communication device described herein with respect to the UE. For example, the hub 1114 may be a broadband router that enables the UE to access the core network 1106. In another example, the hub 1114 may be a controller that sends commands or instructions to one or more actuators within the UE. Commands or instructions may be received from the UE or network node 1110, or accepted by executable code, scripts, processes, or other instructions within the hub 1114. In yet another example, the hub 1114 may be a data collector acting as temporary storage for the UE's data, which in some embodiments may perform analysis or other processing on that data. In yet another example, the hub 1114 may be a content source. For example, with respect to a UE that is a virtual reality (VR) headset, display, loudspeaker, or other media delivery device, the hub 1114 may acquire media or data related to VR assets, video, audio, or other sensory information via network nodes, in which case the hub 1114 provides it to the UE either directly, after performing local processing, and / or after adding additional local content. In another example, the hub 1114 acts as a proxy server or orchestrator for the UE, in particular when one or more of the UEs are low-energy IoT devices.

[0094] Hub 1114 may have a steady / persistent or intermittent connection to network node 1110B. Furthermore, Hub 1114 may enable different communication methods and / or schedules between Hub 1114 and UEs (e.g., UE 1112C and / or 1112D), and between Hub 1114 and the core network 1106. In another example, Hub 1114 is connected to the core network 1106 and / or one or more UEs via a wired connection. Additionally, Hub 1114 may be configured to connect to a machine-to-machine (M2M) service provider on the access network 1104 and / or to other UEs via a direct connection. In some scenarios, a UE may establish a wireless connection with network node 1110 while still being connected via Hub 1114 via a wired or wireless connection. In some embodiments, Hub 1114 may be a dedicated hub, i.e., a hub whose primary function is to route communication between UEs and network node 1110B. In other embodiments, the hub 1114 may be a non-dedicated hub, i.e., a device capable of routing communication between the UE and the network node 1110B, but also capable of acting as the source and / or destination of communication for some data channel.

[0095] Figure 12 shows UE1200 according to several embodiments. As used herein, UE refers to a device that is capable of, configured, deployed, and / or operating wirelessly with network nodes and / or other UEs. Examples of UEs include, but are not limited to, smartphones, mobile phones, cell phones, Voice over Internet Protocol (VoIP) phones, wireless local loop phones, desktop computers, personal digital assistants (PDAs), wireless cameras, game consoles or devices, music storage devices, playback appliances, wearable terminal devices, wireless endpoints, mobile stations, tablets, laptops, laptop embedded devices (LEEs), laptop-mounted devices (LMEs), smart devices, wireless customer premises equipment (CPEs), vehicles, in-vehicle or vehicle-embedded / integrated wireless devices, etc. Other examples include any UE identified by 3GPP, including Narrowband Internet of Things (NB-IoT) UEs, Machine Type Communications (MTC) UEs, and / or Enhanced MTC (eMTC) UEs.

[0096] A UE may support device-to-device (D2D) communication, for example, by implementing 3GPP standards for side-link communication, dedicated short-range communication (DSRC), vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), or vehicle-to-everything (V2X). In other examples, a UE does not necessarily have a user in the sense of a person who owns and / or operates the device in question. Instead, a UE may represent a device (e.g., a smart sprinkler controller) that is intended to be sold to or operated by a human user, but may not be associated with a particular human user, at least initially. Alternatively, a UE may represent a device (e.g., a smart power meter) that is not intended to be sold to or operated by an end user, but may be associated with a user or operated for the benefit of a user.

[0097] The UE1200 includes an input / output interface 1206, a power supply 1208, memory 1210, a communication interface 1212, and / or any other components, or any combination thereof, and processing circuitry 1202 operably connected via bus 1204. A given UE may utilize all or a subset of the components shown in Figure 12. The level of integration between components may vary between one UE and another. Furthermore, a given UE may include multiple instances of a component, such as multiple processors, memory, transceivers, transmitters, receivers, etc.

[0098] The processing circuit 1202 is configured to process instruction sets and data, and may be configured to implement some sequential state machine capable of executing instruction sets stored in memory 1210 as machine-readable computer programs. The processing circuit 1202 may be implemented as one or more hardware-implemented state machines (e.g., discrete logic, field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), etc.), programmable logic with appropriate firmware, one or more stored computer programs, a general-purpose processor such as a microprocessor or digital signal processor (DSP) with appropriate software, or any combination of the above. For example, the processing circuit 1202 may include multiple central processing units (CPUs).

[0099] In the above example, the input / output interface 1206 may be configured to provide an input device, an output device, or one or more interfaces to one or more input and / or output devices. Examples of output devices include speakers, sound cards, video cards, displays, monitors, printers, actuators, emitters, smart cards, other output devices, or any combination thereof. Input devices may allow a user to capture information to the UE1200. Examples of input devices include touch-sensitive or presence-sensitive displays, cameras (e.g., digital cameras, digital video cameras, webcams, etc.), microphones, sensors, mice, trackballs, directional pads, trackpads, scroll wheels, and smart cards. Presence-sensitive displays may include capacitive or resistive touch sensors for sensing user input. Sensors may include, for example, accelerometers, gyroscopes, tilt sensors, force sensors, magnetic sensors, optical sensors, proximity sensors, biosensors, or any combination thereof. Output devices may use the same type of interface port as input devices. For example, a Universal Serial Bus (USB) port may be used to provide input and output devices.

[0100] In some embodiments, the power supply 1208 is structured as a battery or battery pack. Other types of power sources may be used, such as an external power source (e.g., an electrical outlet), a solar power device, or a battery. The power supply 1208 may further include power circuits for transmitting power from the power supply 1208 itself and / or an external power source to various parts of the UE 1200 via interfaces such as input circuits or power cables. Power transmission may be, for example, for charging the power supply 1208. The power circuits may perform some shaping, conversion, or other modification on the power from the power supply 1208 to suit the power of each component of the UE 1200 to which the power is supplied.

[0101] Memory 1210 may be, or may be configured to include, random access memory (RAM), read-only memory (ROM), programmable ROM (PROM), erasable PROM (EPROM), electrical EPROM (EEPROM), magnetic disk, optical disk, hard disk, removable cartridge, and flash drive. In one example, memory 1210 includes one or more application programs 1214, such as an operating system, a web browser application, a widget, a gadget engine, or other application, and corresponding data 1216. Memory 1210 may store any of a wide variety of operating systems or combinations of multiple operating systems for use by UE 1200.

[0102] The memory 1210 may be configured to include multiple physical drive units such as smart card memory, other memories, or any combination thereof, including smart card memory such as a 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 disk (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 microDIMM SDRAM, and tamper-resistant modules in the form of a universal integrated circuit card (UICC) containing one or more subscriber identification modules (SIMs) such as a universal SIM (USIM) and / or an Internet Protocol Multimedia Services Identification Module (ISIM). The UICC may be, for example, an embedded UICC (eUICC), an integrated UICC (iUICC), or a removable UICC commonly known as a "SIM card". The memory 1210 may enable the UE 1200 to access instruction sets and application programs stored in temporary or non-temporary storage media to offload or upload data. Product items, such as those utilizing communication systems, may be tangibly embodied as a device-readable storage medium or containing one, or within the memory 1210.

[0103] The processing circuit 1202 may be configured to communicate with an access network or other network using a communication interface 1212. The communication interface 1212 may include one or more communication subsystems, and may include or be communicatively connected to an antenna 1222. The communication interface 1212 may include one or more transceivers used to perform communication, such as by communicating with one or more remote transceivers of other wirelessly communicable devices (e.g., other UEs or network nodes in the access network). Each transceiver may include a transmitter 1218 and / or receiver 1220 appropriate for providing network communication (e.g., optical, electrical, frequency-allocated, etc.). Furthermore, the transmitter 1218 and receiver 1220 may be connected to one or more antennas (e.g., antenna 1222), and they may share circuit components, software, or firmware, or alternatively, be implemented separately.

[0104] In the illustrated embodiment, the communication functions of the communication interface 1212 may include cellular communication, Wi-Fi communication, LPWAN communication, data communication, voice communication, multimedia communication, near-field communication such as Bluetooth, NFC, location-based communication such as the use of a global positioning system (GPS) for location determination, other similar communication functions, or any combination thereof. The communication may be implemented in accordance with one or more communication protocols and / or standards, such as IEEE 802.11, Code Division Multiple 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), and Hypertext Transfer Protocol (HTTP).

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

[0106] Other examples include actuators, motors, or switches associated with a communication interface configured to receive wireless input from a network node via a wireless connection. The state of the actuator, motor, or switch may change in response to the received wireless input. For example, the UE may include a motor that adjusts the control surface or rotor of a drone in flight according to the received input, or a robotic arm that performs a medical procedure according to the received input.

[0107] If a UE is in the form of an IoT device, it may be a device for use in one or more application domains, which include, but are not limited to, wearable technology in urban environments, augmented industrial applications, and healthcare. Non-exclusive examples of such IoT devices include, or are incorporated into, devices such as, connected refrigerators or freezers, televisions, connected lighting fixtures, electric meters, robotic vacuum cleaners, voice-controlled smart speakers, home security cameras, motion detectors, thermostats, smoke detectors, door / window sensors, moisture detectors (flood / moisture sensors), electric door locks, connected doorbells, air conditioning systems such as heat pumps, autonomous vehicles, surveillance systems, weather monitoring devices, vehicle parking monitoring devices, electric vehicle charging stations, smartwatches, fitness trackers, head-mounted displays for augmented reality (AR) or virtual reality, wearables for haptic enhancement or sensory enhancement, water sprinklers, animal or object tracking devices, sensors for monitoring plants or animals, industrial robots, unmanned aerial vehicles (UAVs), and any type of medical device such as heart rate monitors or remotely controlled surgical robots. The UE in the form of an IoT device comprises, in addition to circuitry and / or software that depends on the intended application of the IoT device, other components such as those described in relation to the UE1200 shown in Figure 12.

[0108] In another specific example, in an IoT scenario, the UE may represent a machine or other device that performs monitoring and / or measurement and transmits the results of such monitoring and / or measurement to other UEs and / or network nodes. In this case, the UE may be an M2M device and may be referred to as an MTC device in the context of 3GPP. In one particular example, the UE may implement the 3GPP NB-IoT standard. In other scenarios, the UE may represent a vehicle such as a passenger car, bus, truck, ship or aircraft, or other equipment 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 for a single use case. For example, the first UE may be a drone or integrated into a drone and provide speed information of the drone (obtained through a speed sensor) to a second UE, which is a remote controller operating the drone. When the user makes a change from the remote controller, the first UE may adjust the drone's throttle (for example, by controlling an actuator) to increase or decrease the drone's speed. The first and / or second UE may include more than one of the functionalities described above. For example, the UE may include sensors and actuators and handle data communication for both the speed sensor and the actuator.

[0110] Figure 13 shows network node 1300 according to several embodiments. As used herein, network node means equipment that is capable of communicating directly or indirectly with the UE and / or other network nodes or equipment in the telecommunications network, and is configured, positioned and / or operational in such a manner. Examples of network nodes include, but are not limited to, APs (e.g., radio access points), base stations (BS) (e.g., radio BS, node B, evolved node B (eNB), NR node B (gNB)), O-RAN nodes and components of O-RAN nodes (e.g., O-RU, O-DU, O-CU).

[0111] Base stations may be categorized based on the amount of coverage they provide (or, in other words, their transmit power level), and therefore may be referred to as femto base stations, pico base stations, micro base stations, or macro base stations, depending on the amount of coverage they provide. A base station may also be a relay node or a relay donor node controlling a relay device. Network nodes may also include one or all of the parts of a distributed radio base station, such as a centralized digital unit, a distributed unit (e.g., in an O-RAN access node), and / or a remote radio unit (RRU) sometimes called a remote radio head (RRH). Such RRUs may or may not be integrated with an antenna, such as in an antenna-integrated radio. Some parts of a distributed radio base station may also be referred to as nodes within a distributed antenna system (DAS).

[0112] Other examples of network nodes include multi-transmitting point (multi-TRP) 5G access nodes, multi-standard radio (MSR) equipment such as MSR BS, network controllers such as radio network controllers (RNCs) or BS controllers (BSCs), base stations (BTSs), transmit points, transmit nodes, multi-cell / multicast cooperative entities (MCEs), operation and maintenance (O&M) nodes, operation support system (OSS) nodes, self-organizing network (SON) nodes, and positioning nodes (e.g., including evolved serving mobile location centers (E-SMLCs) and / or drive test minimization (MDTs)).

[0113] Network node 1300 includes a processing circuit 1302, memory 1304, communication interface 1306, and power supply 1308. Network node 1300 may consist of multiple physically separate components (e.g., node B component and RNC component, or BTS component and BSC component), each of which may have its own respective components. In a scenario in which network node 1300 has multiple separate components (e.g., BTS and BSC components), one or more of these separate components may be shared among several network nodes. For example, a single RNC may control multiple node Bs. In such a scenario, each unique pair of node B and RNC may, in some examples, be considered a single separate network node. In some embodiments, network node 1300 may be configured to support multiple RATs. In such embodiments, some components may be redundant (e.g., separate memory 1304 for different RATs), and some components may be reused (e.g., the same antenna 1310 may be shared by multiple different RATs). Furthermore, the network node 1300 may include multiple sets of diverse exemplary components for various wireless technologies to be integrated into the network node 1300, such as GSM, WCDMA, LTE, NR, WiFi, Zigbee, Z-wave, long-range wide-area networking (LoRaWAN), radio frequency identification (RFID), or Bluetooth wireless technology. These wireless technologies may be integrated into the same or different chips or sets of chips and other components within the network node 1300.

[0114] The processing circuit 1302 may include one or more combinations of microprocessors, controllers, microcontrollers, CPUs, DSPs, ASICs, FPGAs, or other suitable computing devices, resources, or hardware, software, and / or coding logic, which can operate independently or in conjunction with other network node 1300 components such as memory 1304 to provide the functionality of the network node 1300.

[0115] In some embodiments, the processing circuit 1302 includes a system-on-a-chip (SOC). In some embodiments, the processing circuit 1302 includes one or more of the radio frequency (RF) transceiver circuit 1312 and the baseband processing circuit 1314. In some embodiments, the RF transceiver circuit 1312 and the baseband processing circuit 1314 may be on separate chips (or sets of chips), substrates, or units, such as a radio unit and a digital unit. In alternative embodiments, some or all of the RF transceiver circuit 1312 and the baseband processing circuit 1314 may be on the same chip or set of chips, substrate, or unit.

[0116] Memory 1304 may include, but is not limited to, any form of volatile or non-volatile computer-readable memory, including persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, RAM, ROM, large storage media (e.g., hard disk), removable storage media (e.g., flash drive, compact disc (CD) or digital video disc (DVD)), and / or any other volatile or non-volatile non-temporary device-readable and / or computer-executable memory device for storing information, data and / or instructions that can be used by the processing circuit 1302. Memory 1304 may store any suitable instructions, data or information, including applications, and / or other instructions, which can be executed by the processing circuit 1302 and are available to the network node 1300, including one or more computer programs, software, logic, rules, code, and tables. Memory 1304 may also be used to store any calculation results produced by the processing circuit 1302 and / or any data received via the communication interface 1306. In some embodiments, the processing circuit 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 network nodes, access networks, and / or UEs. As illustrated, the communication interface 1306 includes, for example, a port / terminal 1316 for sending and receiving data to and from the network over a wired connection. The communication interface 1306 also includes a wireless front-end circuit 1318, which is connected to or, in some embodiments, part of the antenna 1310. The wireless front-end circuit 1318 includes a filter 1320 and an amplifier 1322. The wireless front-end circuit 1318 may be connected to the antenna 1310 and the processing circuit 1302. The wireless front-end circuit may be configured to adjust signals communicated between the antenna 1310 and the processing circuit 1302. The wireless front-end circuit 1318 may receive digital data to be sent to other network nodes or UEs via the wireless connection. The wireless front-end circuit 1318 can convert its digital data into a radio signal with appropriate channel and bandwidth parameters using a combination of the filter 1320 and / or amplifier 1322. The radio signal can then be transmitted via the antenna 1310. Similarly, when data is received, the antenna 1310 collects the radio signal, which can then be converted into digital data by the wireless front-end circuit 1318. The digital data can then be passed to the processing circuit 1302. In other embodiments, the communication interface 1306 may include different components and / or different combinations of components.

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

[0119] Antenna 1310 may include one or more antennas or antenna arrays configured to transmit and / or receive wireless signals. Antenna 1310 may be connected to a wireless front-end circuit 1318 and may be any type of antenna capable of wirelessly transmitting and receiving data and / or signals. In one embodiment, antenna 1310 is separate from the network node 1300 and can be connected to the network node 1300 through an interface or port.

[0120] The antenna 1310, communication interface 1306, and / or processing circuit 1302 may be configured to perform any receiving operations and / or acquisition operations described herein as being performed by the network node 1300. Any information, data, and / or signals may be received from the UE, other network nodes, and / or any other network equipment. Similarly, the antenna 1310, communication interface 1306, and / or processing circuit 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 the UE, other network nodes, and / or any other network equipment.

[0121] Power supply 1308 provides power to the various components of network node 1300 in a format suitable for each component (for example, at the voltage and current levels required for each component). Power supply 1308 may further include, or be connected to, a power management circuit for supplying power to the components of network node 1300 to perform the functions described herein. For example, network node 1300 may be connectable to an external power source (e.g., a power grid, an electrical outlet) via an input circuit or interface such as an electrical cable, thereby allowing the external power source to supply power to the power circuit of power supply 1308. As a further example, power supply 1308 may include a power source in the form of a battery or battery pack connected to or integrated into the power circuit. The battery may provide backup power in case of failure of the external power source.

[0122] Embodiments of network node 1300 may include additional components other than those shown in Figure 13 to provide a functional view of the network node, including any functionality necessary to support any of the functionalities described herein and / or any functionality necessary to support the subject matter described herein. For example, network node 1300 may include user interface equipment that enables input of information to and output of information from network node 1300. This may enable a user to perform diagnostic, maintenance, repair, and other management functions on network node 1300.

[0123] Figure 14 is a block diagram of a host 1400 that may be an embodiment of host 1116 in Figure 11, relating to the various perspectives described herein. Where used herein, host 1400 may be, or include, a variety of hardware and / or software, including standalone servers, blade servers, cloud-implemented servers, distributed servers, virtual machines, containers, or processing resources within a server farm. Host 1400 may provide one or more services to one or more UEs.

[0124] The host 1400 includes an input / output interface 1406, a network interface 1408, a power supply 1410, and a processing circuit 1402 operably connected via a bus 1404 to a memory 1412. In other embodiments, other components may be included. The functions of these components may be substantially the same as those described for the devices in previous drawings such as Figures 12 and 13, and thus those descriptions are generally applicable to the corresponding components of the host 1400.

[0125] 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, such as data generated by the UE for the host 1400 or data generated by the host 1400 for the UE. Embodiments of the host 1400 may utilize only a subset or all of the illustrated components. The host application program 1414 may be implemented in a container-based architecture and may provide support for video codecs (e.g., VVC (Versatile Video Coding), HEVC (High Efficiency Video Coding), AVC (Advanced Video Coding), Video Expert Group (MPEG), VP9) and audio codecs (e.g., FLAC (Free Lossless Audio Codec), AAC (Advanced Audio Coding), MPEG, G.711), including transcoding for multiple different classes, types, or implementations of UEs (e.g., handsets, desktop computers, wearable display systems, heads-up display systems). Furthermore, the host application program 1414 may provide user authentication and license checks, and may periodically report health, route, and content availability to central nodes such as devices within or at the edge of the core network. Thus, host 1400 may select and / or point to different hosts for over-the-top (OTT) services for the UE. The host application program 1414 may support a variety of protocols, such as HLS (HTTP Live Streaming) protocol, RTMP (Real-Time Messaging Protocol), RTSP (Real-Time Streaming Protocol), DASH or MPEG-DASH (Dynamic Adaptive Streaming over HTTP).

[0126] Figure 15 is a block diagram showing a virtualization environment 1500 in which functions implemented by several embodiments may be virtualized. In this context, virtualization means generating a device or a virtual version of a device, which may include a virtualization hardware platform, storage devices, and networking resources. As used herein, virtualization can be applied to any of the devices or components thereof described herein and relates to implementation examples in which at least some of its 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 within one or more virtualization environments 1500 hosted by one or more hardware nodes, such as network nodes, UEs, core network nodes, or hardware computing devices acting as hosts. Furthermore, in embodiments in which the virtual nodes do not require radio connectivity (e.g., core network nodes or hosts), the nodes as a whole may be virtualized. In some embodiments, the virtualization environment 1500 includes a set of components defined by the O-RAN Alliance, such as an O-Cloud environment organized by a service management and orchestration framework via an O-2 interface.

[0127] Application 1502 (which may alternatively be called a software instance, virtual appliance, network function, virtual node, virtual network function, etc.) runs in a virtualized environment 1500 to implement some of the features, functions and / or benefits of some of the embodiments disclosed herein.

[0128] Hardware 1504 includes a processing circuit, memory for storing software and / or instruction sets executable by the hardware processing circuit, and / or hardware devices as described herein, such as network interfaces and input / output interfaces. The software is executed by the processing circuit to instantiate one or more virtualization layers 1506 (also referred to as a hypervisor or VM monitor (VMM)), provide VM1508A and VM1508B (one or more of which may generally be referred to as VM1508), and / or perform any of the functions, features and / or benefits described herein in relation to some of the embodiments described herein. The virtualization layer 1506 may present a virtual operating platform that appears to VM1508 as networking hardware.

[0129] VM1508 includes virtual processing, virtual memory, virtual networking or interfaces, and virtual storage, and may be run by the corresponding virtualization layer 1506. Various embodiments of instances of the virtual appliance 1502 may be implemented in one or more of VM1508, and such implementation may be carried out in various ways. Hardware virtualization is referred to as network function virtualization (NFV) in several contexts. NFV can be used to consolidate many types of network equipment into industry-standard, high-capacity server hardware, physical switches, and physical storage that can reside in data centers and customer premises equipment.

[0130] In the context of NFV, VM1508 may be a software implementation of a physical machine that runs a program as if it were running on a physical, non-virtualized machine. Each VM1508, and the portion of hardware 1504 on which the VM runs, whether dedicated hardware for that VM or hardware shared by that VM with other VM1508s, forms a separate virtual network element. In the context of NFV, the virtual network function is further responsible for handling the specific network functions running in one or more VM1508s operating on hardware 1504, and corresponds to application 1502.

[0131] Hardware 1504 may be implemented in a standalone network node with general-purpose or specific components. Hardware 1504 may implement some functions through virtualization. Alternatively, hardware 1504 may be part of a larger hardware cluster (such as one in a data center or CPE) in which multiple hardware nodes cooperate and are managed via management and orchestration 1510, which oversees, among other things, the lifecycle management of application 1502. In some embodiments, hardware 1504 is coupled to one or more radio units, each including one or more transmitters and one or more receivers, which can be coupled to one or more antennas. The radio units may communicate directly with other hardware nodes via one or more suitable network interfaces, or they may be used in combination with virtual components to provide radio capabilities to virtual nodes, such as in a RAN or base station. In some embodiments, some signaling can be provided in conjunction 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 with a UE 1606 via a network node 1604 over a partially wireless connection, according to one of several embodiments. Exemplary implementations of various embodiments of the UEs (UE 1112A in Figure 11 and / or UE 1200 in Figure 12), network nodes (network node 1110A in Figure 11 and / or network node 1300 in Figure 13), and hosts (host 1116 in Figure 11 and / or host 1400 in Figure 14) discussed in the preceding paragraphs will now be described with reference to Figure 16.

[0133] Similar to host 1400, embodiments of host 1602 include hardware such as a communication interface, processing circuitry, and memory. Host 1602 also includes software stored within or accessible by host 1602, which is executable by the processing circuitry. This software may include a host application that can operate to provide services to remote users, such as UE 1606 connected via an OTT connection 1650 extending between UE 1606 and host computer 1602. While providing services to remote users, the host application may provide user data transmitted using the OTT connection 1650.

[0134] Network node 1604 includes hardware that enables communication with host 1602 and UE 1606. Connection 1660 is direct or can pass through one or more other intermediate networks, such as a core network (like core network 1106 in Figure 11) and / or one or more public, private, or hosted networks. For example, the intermediate network may be a backbone network or the internet.

[0135] UE1606 includes hardware and software stored within or accessible by UE1606, which is executable by the UE's processing circuitry. This software may include a client application, such as a web browser or a service provider-specific “app,” which, with the support of host 1602, may operate to provide services to human or non-human users via UE1606. On host 1602, the host application to be executed may communicate with the client application to be executed via an OTT connection 1650 terminating at UE1606 and host 1602. While providing services to a user, the UE's client application may receive request data from the host's host application and provide user data in response to that request data. The OTT connection 1650 may transport both the request data and the user data. The UE's client application may interact with the user to generate user data that it provides to the host application via the OTT connection 1650.

[0136] The OTT connection 1650 extends via connection 1660 between host 1602 and network node 1604, and via wireless connection 1670 between network node 1604 and UE 1606, and may provide connectivity between host 1602 and UE 1606. To illustrate the communication between host 1602 and UE 1606 via network node 1604, without any explicit reference to any intermediate devices and the precise routing of messages through those devices, the connections 1660 and wireless connection 1670, which may be provided by the OTT connection 1650, are depicted abstractly.

[0137] As an example of transmitting data via the OTT connection 1650, in step 1608, host 1602 provides user data, which may be done by running a host application. In some embodiments, the user data is associated with a specific human user interacting with UE 1606. In other embodiments, the user data is associated with UE 1606 sharing data with host 1602 without explicit human interaction. In step 1610, host 1602 initiates a transmission to UE 1606 carrying the user data. Host 1602 may initiate such a transmission in response to a request transmitted by UE 1606. Such a request may be triggered by human interaction with UE 1606 or by the operation of a client application running on UE 1606. Such a transmission may pass through network node 1604 in accordance with the teachings of the embodiments described through this disclosure. Accordingly, in step 1612, the network node 1604 transmits the user data carried in the transmission initiated by host 1602 to UE 1606 in accordance with the teachings of the embodiments described through this disclosure. In step 1614, UE 1606 receives the user data carried in the transmission, which may be done by a client application running on UE 1606 associated with a host application running on host 1602.

[0138] In some examples, UE1606 runs a client application, thereby providing user data destined for host 1602. User data may be provided in reaction to or in response to receiving data from host 1602. Accordingly, in step 1616, UE1606 may provide user data, which may be done by running a client application. While providing user data, the client application may further consider user input received from the user via the input / output interface of UE1606. Regardless of the specific way in which the user data is provided, in step 1618, UE1606 initiates transmission of the user data to host 1602 via network node 1604. In step 1620, in accordance with the teachings of the embodiments described through this disclosure, network node 1604 receives user data from UE1606 and initiates transmission of the received user data to host 1602. In step 1622, host 1602 receives the user data carried in the transmission initiated by UE1606.

[0139] One or more of the various embodiments improve the performance of the OTT service provided to the UE 1606 using the OTT connection 1650, with the wireless connection 1670 forming the final segment.

[0140] In an exemplary scenario, Host 1602 may collect and analyze factory status information. In another example, Host 1602 may process audio and video data, which may be acquired from the UE, for use in generating maps. In yet another example, Host 1602 may collect and analyze real-time data to assist in controlling vehicle congestion (e.g., traffic light control). In yet another example, Host 1602 may store surveillance video uploaded by the UE. In yet another example, Host 1602 may store or control access to media content such as video, audio, VR, or AR that can be broadcast, multicast, or unicast to the UE. In yet another example, Host 1602 may be used for energy pricing, remote control of non-time-critical power loads for balancing power generation needs, location services, presentation services (such as editing diagrams from data collected from remote devices), or any other function of collecting, acquiring, storing, analyzing, and / or transmitting data.

[0141] In some examples, measurement procedures may be provided for the purpose of monitoring data rate, latency, and other factors that are improved by one or more embodiments. Further network functionality may exist as an option for reconfiguring the OTT connection 1650 between host 1602 and UE 1606 in response to variations in the measurement results. The above measurement procedures and / or network functionality for reconfiguring the OTT connection 1650 may be implemented in the software and hardware of host 1602 and / or UE 1606. In some embodiments, sensors (not shown) may be deployed in or associated with other devices through which the OTT connection 1650 passes, and these sensors may participate in the measurement procedures by supplying values ​​of the monitored quantities exemplified above or values ​​of other physical quantities, from which the monitored quantities may be calculated or estimated by software. Reconfiguration of the OTT connection 1650 may include message format, retransmission settings, preferred routing, etc., and the reconfiguration does not need to directly change the operation of network node 1604. Such procedures and functionalities may be known or in use in the art. In one embodiment, the measurement may include proprietary UE signaling that facilitates the measurement of throughput, propagation time, and latency by the host 1602. The measurement may be implemented by the software monitoring propagation time, errors, etc., while sending messages that are specifically empty or "dummy" messages using the OTT connection 1650.

[0142] While the computing devices described herein (e.g., UEs, network nodes, hosts) may include combinations of illustrated hardware components, other embodiments may include computing devices with different combinations of components. It should be understood that these computing devices may include any suitable combination of hardware and / or software required to perform the tasks, features, functions, and methods disclosed herein. The decisions, calculations, acquisitions, or similar operations described herein may be performed by processing circuits, which may process information by, for example, converting acquired information to other information, comparing acquired or converted information with information stored in the network node, and / or performing one or more operations based on the acquired or converted information, and making decisions as a result of the processing. Furthermore, while components are depicted as single boxes located within larger boxes or nested within multiple boxes, in practice, computing devices may include multiple different physical components that make up the illustrated single component, and functionality may be separated between distinct components. For example, a communication interface may be configured to include any of the components described herein, and the functionality of those components may be separated between the processing circuit and the communication interface. In other examples, computationally intensive functions of any of these components may be implemented in software or firmware, while computationally intensive functions may be implemented in hardware.

[0143] In some embodiments, some or all of the functionalities described herein may be provided by a processing circuit executing a set of instructions stored in memory, which may be a computer program product in the form of a non-temporary computer-readable storage medium. In alternative embodiments, some or all of the functionalities may be provided by the processing circuit, such as in a hardwired manner, without executing instructions stored in separate or discrete device-readable storage mediums. In any of these specific embodiments, the processing circuit can be configured to perform the functionalities described, whether or not it executes instructions stored in a non-temporary computer-readable storage medium. The benefits provided by such functionalities are not limited to the processing circuit alone or other components of the computing device, but are enjoyed by the computing device as a whole, and / or by the end user and the wireless network in general.

[0144] Some exemplary embodiments of this disclosure are as follows:

[0145] Group A Embodiment Embodiment 1: A method performed by a user device, UE, to provide feedback to a network node regarding the frequency difference between transmitting and receiving points (TRPs), the method comprising one or more of the following: determining the frequency difference between the transmission frequency of a first TRP and the transmission frequency of a second TRP (1006); transmitting a quantized frequency difference value to the network node representing the determined frequency difference between the transmission frequency of the first TRP and the transmission frequency of the second TRP (1008); where the values ​​of one or more parameters related to the quantization of the determined frequency difference for providing the quantized frequency difference value are set by the network node or determined by the UE as a function of the carrier frequencies transmitted by the first and second TRPs.

[0146] Embodiment 2: The method according to Embodiment 1, wherein one or more parameters related to the quantization of the determined frequency difference for providing a quantized frequency difference value include one or more of the following: • Frequency step size used for quantizing the determined frequency difference, • The frequency range of the value range used for quantizing the determined frequency difference. • Number of bits N used for quantizing the determined frequency difference, ·Maximum correctable frequency error.

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

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

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

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

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

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

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

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

[0155] Embodiment 11: The method according to any one of Embodiments 1 to 9, wherein the values ​​of one or more parameters related to the quantization of a determined frequency difference for providing a quantized frequency difference value are predefined.

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

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

[0158] Embodiment 14: The method according to Embodiment 12 or 13, wherein one or more parameters related to the quantization of a determined frequency difference for providing a quantized frequency difference value include two or more parameters that are individually set via information received from a network node.

[0159] Embodiment 15: The method according to Embodiment 12 or 13, wherein one or more parameters related to the quantization of a determined frequency difference for providing a quantized frequency difference value include two or more parameters that are jointly set via information received from a network node.

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

[0161] Embodiment 17: The method according to Embodiment 16, wherein determining the frequency difference between the transmission frequency of a first TRP and the transmission frequency of a second TRP (1006) includes measuring the frequency difference based on first and second reference signals.

[0162] Embodiment 18: The method according to Embodiment 16 or 17, wherein the transmission of quantized frequency difference values ​​(1008) to the network node is in accordance with the CSI report settings.

[0163] Embodiment 19: The method according to any one of Embodiments 12 to 15, wherein the information received from the network node includes serving cell settings.

[0164] Embodiment 20: The method according to any one of Embodiments 1 to 19, wherein the first TRP and the second TRP are TRPs used for coherent cotransmission to the UE.

[0165] Embodiment 21: A method according to any of the prior embodiments, further comprising providing user data and transferring user data to a host via transmission to a network node.

[0166] Group B Embodiment Embodiment 22: A method performed by a network node to compensate for a frequency difference between transmitting and receiving points (TRPs) based on feedback from a user device, UE, the method comprising receiving a quantized frequency difference value from the UE that represents the frequency difference between the transmission frequency of a first TRP and the transmission frequency of a second TRP (1008), wherein the value of one or more parameters related to the quantization of the frequency difference is set by the network node or determined by the UE as a function of the carrier frequencies transmitted by the first and second TRPs; and performing one or more actions based on the quantized frequency difference value (1010).

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

[0168] Embodiment 24: The method according to Embodiment 23, wherein the determination can be based on one or more of the carrier frequencies transmitted by the first TRP and the second TRP, the reporting period of the frequency difference UE feedback, and the maximum frequency error of the first TRP and the second TRP, respectively.

[0169] Embodiment 25: The method according to Embodiment 22, wherein one or more parameters related to the quantization of a determined frequency difference for providing a quantized frequency difference value include one or more of the following: • Frequency step size used for quantizing the determined frequency difference, • The frequency range of the value range used for quantizing the determined frequency difference. • Number of bits N used for quantizing the determined frequency difference, ·Maximum correctable frequency error.

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

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

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

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

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

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

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

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

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

[0179] Embodiment 35: The method of any one of Embodiments 22 to 32, further comprising transmitting information to the UE (1004) that explicitly or implicitly indicates a value of at least one parameter related to the quantization of a determined frequency difference for providing a quantized frequency difference value.

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

[0181] Embodiment 37: The method according to Embodiment 35 or 36, wherein one or more parameters related to the quantization of a determined frequency difference for providing a quantized frequency difference value include two or more parameters that are individually set via information transmitted to the UE.

[0182] Embodiment 38: The method according to Embodiment 35 or 36, wherein one or more parameters related to the quantization of a determined frequency difference for providing a quantized frequency difference value are set together via information transmitted to the UE, wherein one or more parameters are set together via information transmitted to the UE.

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

[0184] Embodiment 40: The method according to Embodiments 20 and 39, wherein the reception of the quantized frequency difference value is in accordance with the CSI report settings.

[0185] Embodiment 41: The method according to any one of Embodiments 35 to 40, wherein the information transmitted to the UE includes serving cell settings.

[0186] Embodiment 42: The method according to any one of Embodiments 22 to 41, wherein the first TRP and the second TRP are TRPs used for coherent cotransmission to the UE.

[0187] Embodiment 43: A method according to any of the prior embodiments, further comprising acquiring user data and transferring user data to a host or user device.

[0188] Group C Embodiment Embodiment 44: User equipment comprising a processing circuit configured to perform any step of the embodiment of Group A; and a power supply circuit configured to supply power to the processing circuit.

[0189] Embodiment 45: A network node comprising a processing circuit configured to perform any step of the embodiment of Group B; and a power supply circuit configured to supply power to the processing circuit.

[0190] Embodiment 46: User equipment (UE) comprising: an antenna configured to transmit and receive wireless signals; a wireless front-end circuit connected to the antenna and a processing circuit and configured to adjust signals communicated between the antenna and the processing circuit; a processing circuit configured to perform any step of the embodiment of Group A; an input interface connected to the processing circuit and configured to allow input of information to be processed by the processing circuit to the UE; an output interface connected to the processing circuit and configured to output information processed by the processing circuit from the UE; and a battery connected to the processing circuit 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: a processing circuit configured to provide user data; and a network interface configured to initiate the transmission of 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 a processing circuit, the processing circuit of the network node configured to perform any operation of the embodiments of Group B in order to transmit user data from the host to the UE.

[0192] Embodiment 48: The host according to the prior embodiment, wherein the host processing circuit is configured to run a host application that provides user data; and the UE is configured to run a client application associated with the host application in order to receive user data transmissions from the host.

[0193] Embodiment 49: A method implemented on a host configured to operate in a communication system further including network nodes and user equipment (UEs), the method comprising: providing user data for the UEs; and initiating a transmission to carry the user data to the UEs over a cellular network including network nodes, wherein the network nodes perform any operation of the embodiments of Group B to transmit the user data from the host to the UEs.

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

[0195] Embodiment 51: The method according to either of the two preceding embodiments, wherein user data is provided on the host by running a host application that interacts with a client application running on the UE, and the client application is associated with the host application.

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

[0197] Embodiment 53: A communication system according to a prior embodiment, further comprising a network node; and / or UE.

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

[0199] Embodiment 55: The host according to the two preceding embodiments, wherein the host processing circuit is configured to run a host application that receives user data; and the host application is configured to interact with a client application running on the UE, and the client application is associated with the host application.

[0200] Embodiment 56: A host according to any of the two preceding embodiments, wherein initiating the reception of user data includes requesting user data.

[0201] Embodiment 57: A method implemented by a host configured to operate in a communication system further including network nodes and user equipment (UEs), the method comprising the host initiating the reception of user data from the UE, the user data originating from a transmission received by the network node from the UE, wherein the network node performs any step of the embodiment of Group B in order to receive user data from the UE for the host.

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

[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 user data to a cellular network for transmission to a user device (UE), wherein the UE comprises a communication interface and processing circuitry, the communication interface and processing circuitry of the UE configured to perform any operation of the embodiments of Group A in order to receive user data from the host.

[0204] Embodiment 60: The host according to the prior embodiment, further comprising network nodes configured to communicate with the UE in order to transmit user data from the host to the UE.

[0205] Embodiment 61: A host according to the two preceding embodiments, wherein the host processing circuit is configured to execute a host application and thereby provide user data; and the host application is configured to interact with a client application running on the UE, and the client application is associated with the host application.

[0206] Embodiment 62: A method implemented by a host operating in a communication system further including network nodes and user equipment (UEs), the method comprising: providing user data for the UEs; and initiating a transmission to carry the user data to the UEs over a cellular network including network nodes, wherein the UEs perform any of the actions of the Group A embodiments to receive the user data from the host.

[0207] Embodiment 63: The method according to the preceding embodiment, further comprising running a host application associated with a client application running on the UE in order to receive user data from the host application on the host.

[0208] Embodiment 64: The method of the preceding embodiment, further comprising the host sending input data to a client application running on the UE, wherein the input data is provided by running the host application, and 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 user data to a cellular network for transmission to a user device (UE), wherein the UE comprises a communication interface and processing circuitry, the communication interface and processing circuitry of the UE configured to perform any step of the embodiment of Group A in order to transmit user data to the host.

[0210] Embodiment 66: The host according to the prior embodiment, further comprising a cellular network node configured to communicate with the UE to transmit user data from the UE to the host.

[0211] Embodiment 67: A host according to the two preceding embodiments, wherein the host processing circuit is configured to execute a host application and thereby provide user data; and the host application is configured to interact with a client application running on the UE, and the client application is associated with the host application.

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

[0213] Embodiment 69: The method according to the preceding embodiment, further comprising running a host application associated with a client application running on the UE in order to receive user data from the UE.

[0214] Embodiment 70: The method according to the two preceding embodiments, further comprising the host sending input data to a client application running on the UE, wherein the input data is provided by running the host application, and 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 embodiments of the present disclosure. All such improvements and modifications are deemed to fall within the scope of the concepts disclosed herein.

Claims

1. A method performed by user equipment (UE) for providing feedback to a network node regarding the frequency difference between each of a plurality of transmission / reception points (TRPs) and a reference TRP, Receiving the channel status information (CSI) report settings for frequency difference feedback, (1006) Determining the frequency difference between each of the plurality of TRPs and the reference TRP, Determining (1008) a quantized frequency difference value representing the determined frequency difference between each of the plurality of TRPs and the reference TRP, according to one or more parameters relating to the quantization of the determined frequency difference, wherein the values ​​of the one or more parameters relating to the quantization of the determined frequency difference for providing the quantized frequency difference value are set by the network node. For each of the plurality of TRPs, the quantization frequency difference value is transmitted to the network node (1008), Methods that include...

2. The values ​​of one or more parameters related to the quantization of the determined frequency difference for providing the quantized frequency difference value are: - The carrier frequency in which the multiple TRPs operate, Channel status information (CSI) report cycle, • Base station type, - Maximum frequency error of the multiple TRPs One or more of the following functions The method according to claim 1.

3. The one or more parameters related to the quantization of the determined frequency difference for providing the quantized frequency difference value are: - Frequency step size used for quantizing the determined frequency difference, - The frequency range used for quantizing the determined frequency difference, - Number of bits N used for quantizing the determined frequency difference, - Maximum frequency quantization error Includes one or more of the following: The method according to claim 1.

4. The one or more parameters relating to the quantization of the determined frequency difference for providing the quantized frequency difference value include the frequency step size used for quantizing the determined frequency difference. The method according to claim 1.

5. The frequency step size used for quantizing the determined frequency difference is a function of the coherent co-transmission (CJT) channel state information (CSI) report period. The method according to claim 4.

6. The frequency step size used for quantizing the determined frequency difference is set from the network node to the UE. The method according to claim 4.

7. The one or more parameters relating to the quantization of the determined frequency difference for providing the quantized frequency difference value further include the number of bits N used for the quantization of the determined frequency difference. The method according to any one of claims 4 to 6.

8. The quantization is uniform quantization in which the quantization levels are equally spaced within the frequency range used to quantize the determined frequency difference. The method according to any one of claims 1 to 7.

9. The number of bits N used for quantizing the determined frequency difference is set from the network node to the UE. The method according to any one of claims 1 to 7.

10. The frequency range used for quantizing the determined frequency difference is set from the network node to the UE. The method according to any one of claims 1 to 7.

11. The frequency range and the number of bits N used for quantizing the determined frequency difference are set from the network node to the UE. The method according to any one of claims 1 to 7.

12. The one or more parameters related to the quantization of the determined frequency difference for providing the quantized frequency difference value further include the maximum frequency quantization error. The method according to any one of claims 4 to 6.

13. The one or more parameters relating to the quantization of the determined frequency difference for providing the quantized frequency difference value include the number of bits N used for quantizing the determined frequency difference and the maximum frequency quantization error. The method according to claim 1.

14. The one or more parameters relating to the quantization of the determined frequency difference for providing the quantized frequency difference value include the frequency step size used for the quantization of the determined frequency difference and the frequency range of the range of values ​​used for the quantization of the determined frequency difference. The method according to claim 1.

15. At least one of the one or more parameters related to the quantization of the determined frequency difference for providing the quantized frequency difference value is predefined. The method according to any one of claims 1 to 14.

16. The values ​​of the one or more parameters related to the quantization of the determined frequency difference for providing the quantized frequency difference value are predefined. The method according to any one of claims 1 to 14.

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

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

19. The one or more parameters related to the quantization of the determined frequency difference for providing the quantized frequency difference value include two or more parameters that are individually set via the information received from the network node. The method according to claim 17 or 18.

20. The one or more parameters related to the quantization of the determined frequency difference for providing the quantized frequency difference value include two or more parameters that are jointly set via the information received from the network node. The method according to claim 17 or 18.

21. The CSI report settings received from the network node further include information on a plurality of reference signals, each of which is transmitted from the reference TRP or one of the plurality of TRPs. The method according to any one of claims 1 to 20.

22. Determining the frequency difference between each of the plurality of TRPs and the reference TRP (1006) includes measuring the frequency difference based on a corresponding reference signal. The method according to claim 21.

23. Transmitting the quantization frequency difference value to the network node (1008) in accordance with the CSI report settings. The method according to claim 21 or 22.

24. The information received from the network node includes serving cell settings. The method according to any one of claims 17 to 20.

25. One or more of the aforementioned TRPs and the reference TRP are TRPs used for coherent cotransmission to the UE. The method according to any one of claims 1 to 24.

26. User equipment (UE) for providing feedback to network nodes regarding the frequency difference between each of multiple transmission / reception points (TRPs) and a reference TRP, Receive the channel status information (CSI) report settings for frequency difference feedback. The frequency difference between each of the plurality of TRPs and the reference TRP is determined (1006), A quantized frequency difference value is determined that represents the determined frequency difference between each of the plurality of TRPs and the reference TRP, according to one or more parameters related to the quantization of the determined frequency difference (1008), and the values ​​of the one or more parameters related to the quantization of the determined frequency difference for providing the quantized frequency difference value are set by the network node. For each of the plurality of TRPs, the quantization frequency difference value is transmitted to the network node (1008). It is adapted to the UE.

27. The UE according to claim 26, further adapted to carry out the method described in any one of claims 2 to 25.

28. A user device (UE) (1200) for providing feedback to a network node regarding the frequency difference between multiple transmission / reception points (TRPs), A communication interface (1212) including a transmitter (1218) and a receiver (1220), A processing circuit (1202) associated with the communication interface (1212), wherein the processing circuit (1202) provides the UE (1200) to Receive the channel status information (CSI) report settings for frequency difference feedback. Determine the frequency difference between each of the plurality of TRPs and the reference TRP. A quantized frequency difference value representing the determined frequency difference between each of the plurality of TRPs and the reference TRP is determined according to one or more parameters related to the quantization of the determined frequency difference (1008), and the values ​​of the one or more parameters related to the quantization of the determined frequency difference for providing the quantized frequency difference value are set by the network node. For each of the plurality of TRPs, the quantization frequency difference value is transmitted to the network node (1008). The processing circuit (1202) is configured as follows, UE (1200) equipped with...

29. The UE (1200) according to claim 28, further adapted to carry out the method described in any one of claims 2 to 25.

30. A method performed by a network node for compensating for frequency differences between multiple transmission / reception points (TRPs) and a reference TRP based on feedback from user equipment (UE), Sending the settings for the Channel State Information (CSI) report for frequency difference feedback to the UE, Receiving (1008) a quantized frequency difference value from the UE that indicates the frequency difference between each of a plurality of TRPs and a reference TRP, wherein the value of one or more parameters related to the quantization of the frequency difference is set by the network node or determined by the UE, Performing one or more actions based on the quantization frequency difference (1010), Methods that include...

31. The values ​​of one or more parameters related to the quantization of the determined frequency difference for providing the quantized frequency difference value are: - The carrier frequency in which the multiple TRPs operate, Channel status information (CSI) report cycle, • Base station type, - Maximum frequency error of the multiple TRPs One or more of the following functions The method according to claim 30.

32. (1004) further includes determining the values ​​of one or more parameters related to the quantization of the frequency difference and setting them in the UE. The method according to claim 30.

33. The determination may be based on one or more of the carrier frequencies in which the plurality of TRPs operate, the reporting period of the UE feedback of the frequency difference, and the maximum frequency error of each of the plurality of TRPs. The method according to claim 32.

34. The one or more parameters related to the quantization of the determined frequency difference for providing the quantized frequency difference value are: - Frequency step size used for quantizing the determined frequency difference, - The frequency range used for quantizing the determined frequency difference, - Number of bits N used for quantizing the determined frequency difference, - Maximum frequency quantization error Includes one or more of the following: The method according to claim 30.

35. The one or more parameters relating to the quantization of the determined frequency difference for providing the quantized frequency difference value include the frequency step size used for quantizing the determined frequency difference. The method according to claim 30.

36. The frequency step size used for quantizing the determined frequency difference is a function of the coherent co-transmission (CJT) channel state information (CSI) report period. The method according to claim 35.

37. The frequency step size used for quantizing the determined frequency difference is set from the network node to the UE based on the coherent co-transmission (CJT) channel state information (CSI) report period. The method according to claim 35.

38. The one or more parameters relating to the quantization of the determined frequency difference for providing the quantized frequency difference value further include the number of bits N used for the quantization of the determined frequency difference. The method according to any one of claims 35 to 37.

39. The quantization is uniform quantization in which the quantization levels are equally spaced within the frequency range used to quantize the determined frequency difference. The method according to any one of claims 30 to 38.

40. The number of bits N used for quantizing the determined frequency difference is set from the network node to the UE. The method according to any one of claims 30 to 38.

41. The frequency range used for quantizing the determined frequency difference is set from the network node to the UE. The method according to any one of claims 30 to 38.

42. The frequency range and the number of bits N used for quantizing the determined frequency difference are set from the network node to the UE. The method according to any one of claims 30 to 38.

43. The one or more parameters related to the quantization of the determined frequency difference for providing the quantized frequency difference value further include the maximum frequency quantization error. The method according to any one of claims 35 to 37.

44. The one or more parameters relating to the quantization of the determined frequency difference for providing the quantized frequency difference value include the number of bits N used for quantizing the determined frequency difference and the maximum frequency quantization error. The method according to claim 30.

45. At least one of the one or more parameters related to the quantization of the determined frequency difference for providing the quantized frequency difference value is predefined. The method according to any one of claims 30 to 44.

46. The values ​​of the one or more parameters related to the quantization of the determined frequency difference for providing the quantized frequency difference value are predefined. The method according to any one of claims 30 to 44.

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

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

49. The one or more parameters related to the quantization of the determined frequency difference for providing the quantized frequency difference value include two or more parameters that are individually set via the information transmitted to the UE. The method according to claim 47 or 48.

50. The one or more parameters related to the quantization of the determined frequency difference for providing the quantized frequency difference value include two or more parameters that are jointly set via the information transmitted to the UE. The method according to claim 47 or 48.

51. The CSI report configuration further includes information on multiple reference signals, each of which is transmitted from the reference TRP or one of the multiple TRPs. The method according to any one of claims 47 to 50.

52. Receiving the aforementioned quantization frequency difference value is in accordance with the CSI report settings. The method according to claim 51.

53. The information transmitted to the UE includes serving cell settings. The method according to any one of claims 47 to 52.

54. One or more of the aforementioned TRPs and the reference TRP are TRPs used for coherent cotransmission to the UE. The method according to any one of claims 30 to 53.

55. A network node for compensating for frequency differences between multiple transmission / reception points (TRPs) and a reference TRP based on feedback from user equipment (UE), Send the channel status information (CSI) report settings for frequency difference feedback to the UE. A quantized frequency difference value indicating the frequency difference between each of the multiple TRPs and a reference TRP is received from the UE (1008), and the values ​​of one or more parameters related to the quantization of the frequency difference are set by the network node or determined by the UE. Based on the quantization frequency difference value, one or more actions are performed (1010). Network nodes that are adapted to this purpose.

56. A network node according to claim 55, further adapted to perform the method described in any one of claims 31 to 54.

57. A network node for compensating for frequency differences between multiple transmission / reception points (TRPs) and a reference TRP based on feedback from user equipment (UE), A processing circuit, wherein the network node, Send the settings for the Channel State Information (CSI) report for frequency difference feedback to the UE. A quantized frequency difference value indicating the frequency difference between each of the multiple TRPs and a reference TRP is received from the UE (1008), and the values ​​of one or more parameters related to the quantization of the frequency difference are set by the network node or determined by the UE. One or more actions are performed based on the quantization frequency difference (1010), The processing circuit is configured as follows: A network node equipped with these features.

58. The network node according to claim 57, wherein the processing circuit is further configured to cause the network node to perform the method described in any one of claims 31 to 54.

Images