Efficient SINR report for o-ran open fronthaul interface

Abstract

Methods and systems are described for SINR reporting, such as a method performed by an O-RU for enabling SINR reporting of a single value for a PRB range containing two or more PRBs per layer for DFT-s-OFDM. Certain embodiments may provide one or more of the following technical advantages. This disclosure supports efficient SINR reporting when DFT-s-OFDM is scheduled for some UEs in UL. For UE layers scheduled to use DFT-s-OFDM, the O-RU can only report one aggregated SINR value per PRB range per layer for these layers instead of per PRB per layer, which reduces fronthaul bitrate. According to certain embodiments, the aggregated SINR value which is based on the effective channel gain and is averaged over multiple REs in the PRB range is calculated by the O-RU, avoiding unnecessary conversion between SINR value and effective channel representation, which saves processing resources.

Description

EFFICIENT SINK REPORT FOR O-RAN OPEN FRONTHAUL INTERFACECROSS REFERENCE TO RELATED INFORMATION

[0001] This application claims the benefit of United States of America priority application No. 63 / 654,547 filed on May 31, 2024, titled “Efficient SINR Report for O-RAN Open Fronthaul Interface.”TECHNICAL FIELD

[0002] The present disclosure generally relates to systems and methods for enabling SINR reporting.BACKGROUND

[0003] Massive MIMO techniques were first adopted to practice in LTE. In 5G, it becomes one key technology component, which has been deployed on a much larger scale than in LTE. It features a large number of antennas used on the base-station side, where the number of antennas is typically much larger than the number of user layers, for example, 64 antennas serving 8 or 16 user layers in frequency range 1 (FR1), which comprises sub-6 GHz frequency bands, and 256 / 512 antennas serving 2 or 4 layers in FR2, which comprises frequency bands from 24.25 GHz to 71 GHz. A user layer when used herein e.g., means an independent downlink (DL) or uplink (UL) data stream intended for one user. One user or user equipment (UE) may have one or multiple user layers. User layer is often denoted as layer for simplicity reason. Massive MIMO is also referred to as massive beamforming, which is able to form narrow beams focusing on different directions to counteract against the increased path loss at higher frequency bands. It also benefits multi-user MIMO (MU-MIMO) which allows for transmissions from / to multiple users simultaneously over separate spatial channels resolved by the massive MIMO technologies, while keeping high capacity for each user. Therefore, it can significantly increase the spectrum efficiency and cell capacity.

[0004] At the base-station side, the interface between the distributed unit (DU) (also sometimes referred to as digital unit) and the radio unit (RU) is the fronthaul interface. Thegreat benefits of massive MIMO at the air-interface also introduce new challenges at the basestation side. The legacy CPRI-type fronthaul transports time-domain in-phase and quadrature (IQ) samples per antenna branch. As the number of antennas scales up in massive MIMO systems, the required fronthaul capacity also increases proportionally, which significantly drives up the fronthaul costs. To address this challenge, the fronthaul interface evolves from CPRI (Common Public Radio Interface) to eCPRI (enhanced CPRI), a packet-based fronthaul interface. In eCPRI, other functional split options between DU and RU are supported, referred to as different lower- layer split (LLS) options. In eCPRI terminologies, DU and RU are referred to as eREC (eCPRI Radio Equipment Control) and eRE (eCPRI Radio Equipment), respectively. The basic idea of LLS is to move the frequency-domain beamforming function from BBU to RU so that frequency samples or data of user-layers are transported over the fronthaul interface. Note that the frequencydomain beamforming is sometimes also referred to as precoding in the DL direction and equalizing or pre-equalizing in UL direction. By doing this, the required fronthaul capacity and thereby the fronthaul costs are significantly reduced, as the number of user layers is typically much fewer than the number of antennas in massive MIMO. In O-RAN (Open Radio Access Network), DU is referred to as O-DU while RU is referred to as O-RU, see e.g., O-RAN Control, User and Synchronization Plane Specification 14.0, February 2024, available at:radio unit defined by the O-RAN Alliance and the O-RAN abbreviation means (or at least originally meant) Open RAN, where RAN means Radio Access Network.

[0005] The present disclosure focuses on the UL of the fronthaul interface. O-RAN WG4 is going to standardize a new beamforming scheme referred to as DMRS (Demodulation Reference Signal) based beamforming (DMRS-BF) to achieve the best UL performance using the minimum fronthaul bit rate, i.e., reducing the number of streams over the fronthaul interface to the number of layers. There are two implementation variants of DMRS-BF solutions that are to be standardized in O-RAN WG4. The first variant is referred to as DMRS based beamforming with equalization (DMRS-BF-EQ), where equalization is performed in O-RU. The second variant is referred to as DMRS based beamforming without equalization (DMRS-BF-NEQ), where equalization is not performed in O-RU.

[0006] In wireless communication, an equalizer performs an equalization operation on the input signal, which reverses the distortion caused by the end-to-end channel including thetransmitter chain, the over-the-air channel (including the wanted channel and the interference channel), and the receiver chain. After the equalization, the equalized symbols can be demodulated by a demodulator. When the input signal is from multiple transmitters which send different data, the equalizer may also mitigate the interferences between them. Equalizers can be linear or nonlinear. Examples of linear equalizers are zero-forcing equalizer, MMSE (Minimum Mean Square Error) equalizer etc. Examples of non-linear equalizers are decision-feedback equalizer (DFE), successive interference cancellation (SIC) receiver etc.

[0007] One focus of the present disclosure is the DMRS-BF-EQ variant in O-RAN.A typical implementation of DMRS-BF-EQ is shown in Figure 1. Specifically, the equalization is performed by the O-RU which then sends the equalized symbols from O-RU to O-DU. In addition to that, the O-RU also sends the post-equalization signal to interference and noise ratio (SINR) measurement from the O-RU to the O-DU which are used by the O-DU to demodulate the equalized symbols. The SINR measurement represents the measured / estimated SINR values, e.g., per physical resource block (PRB) or finer frequency resolution per layer, which is used by the demodulator for demodulation of the symbols of each RE per layer, e.g., using the demodulation algorithm based on log likelihood ratio (LLR). Further, O-RU also sends to O-DU radio resource management (RRM) measurements which are calculated or measured before equalization and therefore cannot be measured by the O-DU. Some examples of RRM measured quantities include: timing advance offset (TAO), estimate of received signal power of UE layer, interference plus noise (IpN) power measurement, delay spread, frequency offset, doppler shift, angle of arrive (Ao A).

[0008] The new beamforming scheme DMRS-BF-EQ also has an impact on the UL C-plane and U-plane data flows, as shown in Figure 2, because of the support of measurement transferring. For DMRS-BF-EQ, new C-plane signaling is defined to provide necessary information from O-DU to O-RU for the O-RU to perform DMRS-based beamforming. For example, in addition to the information regarding the scheduled REs, the scheduling information also contains demodulation reference signal (DMRS) configuration and other UE-related information the scheduled UEs and UE layers, as well as the measurement control information. Meanwhile, new C-plane signaling is also defined for necessary measurements in the O-RU sent to the O-DU for assisting O-DU PUSCH (Physical Uplink Shared Channel) processing (e.g., demodulation) and RRM operations.

[0009] From O-RU to O-DU, the RRM measurements are transferred in C-plane messages, in addition to the U-plane messages. One or more SINR measurement reports are also sent from the O-RU to the O-DU if sending of (equalized) DMRS symbols is not enabled. Each SINR measurement report contains the SINR values for the scheduled PRBs and a set of consecutive symbols, which are used by O-DU for demodulation. When SINR reporting is configured, the O-RU is required to report SINRs to the O-DU for each layer, PRB, and slot where DMRS-BF-EQ reception was requested. In the latest CR (Change Request) draft in 0-RAN WG4, The SINR values are conveyed by the O-RU to the O-DU through layer-specific reports in C-plane message Section Type 9 (ST9). One ST9 message carries SINR reports for a range of symbols. One ST9 message contains one or more sections. And each section contains a SINR report for a range of PRBs, where each PRB contains one or more SINR values. These are shown in Figure 3, which shows a table of existing C-plane ST9 for SINR reporting, which is proposed in a draft change request (“Section Type 9 for SINR data”, 0-RAN. WG4.CUS.0 ver 14.00 CR NOK-0161 rev. 8, edited by Nokia, April 22, 2024, available in non-confidential area of 0-RAN WG4 wiki), for the not yet published vl5 of e.g., 0-RAN Control, User and Synchronization Plane Specification 14.0, February 2024.SUMMARY

[0010] One embodiment under the present disclosure comprises a method performed by an O-RU for enabling SINR reporting to an O-DU. The method comprises: calculating one or more SINR values for one or more PRB ranges per layer for one or more symbols; and transmitting the one or more SINR values to the O-DU.

[0011] Another embodiment comprises a method performed by an O-RU for enabling SINR reporting of a single value for a PRB range containing one or more PRBs per layer for DFT-s-OFDM. The method comprises declaring, by the O-RU, a capability for sending one SINR value for more than one PRB for one or more symbols.

[0012] Another embodiment comprises a method performed by an O-RU for enabling SINR reporting. The method comprises reporting, with an existing numSinrPerPrb field, a single SINR value for a PRB range containing two or more PRBs for DFT-s-OFDM; wherein the single SINR value comprises an aggregated SINR value for a full PRB range per layer.

[0013] Another embodiment comprises a method performed by an O-DU for enabling SINR reporting. The method comprises receiving, from the O-RU a single SINR value for a PRB range containing one or more PRBs per layer for DFT-s-OFDM; wherein the single SINR value comprises an aggregated SINR, wherein the O-RU calculated the aggregated SINR for the PRB range per layer when DFT-s-OFDM is used and attached only one aggregated SINR value per section of ST9 for each layer.

[0014] Another embodiment comprises a method performed by an O-DU for enabling SINR reporting of a single value for a PRB range containing one or more PRBs per layer for DFT-s-OFDM. The method comprises receiving a declaration, from the O-RU, a capability for sending one SINR value for more than one PRB.

[0015] Another embodiment comprises a method performed by an O-DU for enabling SINR reporting of a single value for a PRB range per layer for DFT-s-OFDM. The method comprises receiving, from the O-RU, a single SINR value for two or more PRB ranges per layer, so that DFT-s-OFDM and CP-OFDM use the same frequency resolution; wherein the O-RU reports the single SINR value per PRB per layer for DFT-s-OFDM wherein the single SINR value comprises an aggregated SINR value for the full PRB range per layer.

[0016] Another embodiment comprises a method performed by an O-DU for enabling SINR reporting. The method comprises receiving an indication, from an O-RU of a single SINR value for two or more PRB ranges per layer DFT-s-OFDM.

[0017] Another embodiment comprises a method performed by an O-RU for enabling SINR reporting to an O-DU. The method comprises: calculating a single SINR value for two or more PRB ranges per layer; and transmitting an indication of the single SINR value to the O-DU.

[0018] Another embodiment comprises a method performed by an O-DU for enabling SINR reporting. The method comprises receiving, from the O-RU, an indication of a single SINR value for two or more PRB ranges containing one or more PRBs per layer for DFT- s-OFDM; wherein the single SINR value comprises an aggregated SINR, wherein the O-RU calculated the aggregated SINR for the PRB range per layer.

[0019] Another possible embodiment under the present disclosure is a method performed by an O-RU for enabling SINR reporting. The method comprises calculating a single SINR value for a PRB range containing two or more PRBs for DFT-s-OFDM and for CP-OFDM;and transmitting, to an O-DU, the single SINR value; wherein the layers using DFT-s-OFDM and the layers using CP-OFDM use different SINR frequency resolutions for SINR reporting per layer.

[0020] Another possible embodiment under the present disclosure is a method performed by an O-DU for enabling SINR reporting. The method comprises receiving, from the O-RU, a single SINR value for a PRB range containing two or more PRBs per layer for DFT-s- OFDM and for CP-OFDM; wherein the layers using DFT-s-OFDM and the layers using CP- OFDM use different SINR frequency resolutions for SINR reporting per layer.

[0021] Another embodiment comprises a network node for enabling SINR reporting. The network node comprises: processing circuitry; and a memory storing instructions whereby the processing circuitry is operable to perform any of the steps of; calculating one SINR value for a PRB, range containing two or more PRBs per layer for one or more symbols; and transmitting the one SINR value to an O-DU.

[0022] Another embodiment comprises a network node for enabling SINR reporting. The network node comprises: processing circuitry; and a memory storing instructions whereby the processing circuitry is operable to perform any of the steps of; declaring, to an O-DU, a capability for sending one SINR value for a PRB, range containing two or more PRBs per layer for one or more symbols.

[0023] Another embodiment comprises a network node for enabling SINR reporting. The network node comprises: processing circuitry; and a memory storing instructions whereby the processing circuitry is operable to perform any of the steps of; reporting, to an O-DU, with an existing numSinrPerPrb field, a single SINR value for a PRB, range containing two or more PRBs for DFT-s-OFDM; wherein the single SINR value comprises an aggregated SINR value for a full PRB range per layer.

[0024] Another embodiment comprises a network node for enabling SINR reporting. The network node comprises: processing circuitry; and a memory storing instructions whereby the processing circuitry is operable to perform any of the steps of; receiving, from the O- RU, a single SINR value for a PRB, range containing two or more PRBs per layer for DFT-s- OFDM; wherein the single SINR value comprises an aggregated SINR, wherein the O-RU calculated the aggregated SINR for the PRB range per layer when DFT-s-OFDM is used and attached only one aggregated SINR value per section of ST9, for each layer.

[0025] Another embodiment comprises a network node for enabling SINK reporting. The network node comprises: processing circuitry; and a memory storing instructions whereby the processing circuitry is operable to perform any of the steps of; receiving a declaration, from the 0-RU, a capability for sending one SINR value for a PRB, range containing two or more PRBs.

[0026] Another embodiment comprises a network node for enabling SINR reporting. The network node comprises: processing circuitry; and a memory storing instructions whereby the processing circuitry is operable to perform any of the steps of; receiving, from the O- RU, one SINR value for a PRB, range containing two or more PRBs per layer, so that DFT-s- OFDM and CP-OFDM, use the same frequency resolution; wherein the O-RU reports the one SINR value per PRB per layer for DFT-s-OFDM wherein the one SINR value comprises an aggregated SINR value for the full PRB range per layer.

[0027] Another embodiment comprises a network node for enabling SINR reporting. The network node comprises: processing circuitry; and a memory storing instructions whereby the processing circuitry is operable to perform any of the steps of; receiving an indication, from an OO-RU, of a single SINR value for a PRB, range containing two or more PRBs per layer for DFT-s-OFDM.

[0028] Another embodiment comprises a network node for enabling SINR reporting. The network node comprises: processing circuitry; and a memory storing instructions whereby the processing circuitry is operable to perform any of the steps of; calculating one SINR value for a PRB, range containing two or more PRBs per layer; and transmitting an indication of the one SINR value to an O-DU.

[0029] Another embodiment comprises a network node for enabling SINR reporting. The network node comprises: processing circuitry; and a memory storing instructions whereby the processing circuitry is operable to perform any of the steps of; receiving, from the O- RU, an indication of a single SINR value for a PRB, range containing two or more PRBs per layer for DFT-s-OFDM; wherein the single SINR value comprises an aggregated SINR, wherein the O- RU calculated the aggregated SINR for the PRB range per layer when DFT-s-OFDM is used.

[0030] Another embodiment comprises a network node for enabling SINR reporting. The network node comprises: processing circuitry; and a memory storing instructions whereby the processing circuitry is operable to perform any of the steps of: calculating a singleSINK value for a PRB range containing two or more PRBs for DFT-s-OFDM, and for CP-OFDM; and transmitting, to an O-DU, the single SINR value; wherein the layers using DFT-s-OFDM and the layers using CP-OFDM use different SINR frequency resolutions for SINR reporting per layer.

[0031] Another embodiment comprises a network node for enabling SINR reporting. The network node comprises: processing circuitry; and a memory storing instructions whereby the processing circuitry is operable to perform any of the steps of receiving, from the O- RU, a single SINR value for a PRB range containing two or more PRBs per layer for DFT-s- OFDM and for CP-OFDM; wherein the layers using DFT-s-OFDM and the layers using CP- OFDM use different SINR frequency resolutions for SINR reporting per layer.

[0032] This summary is provided to introduce a selection of concepts in a simplified form that are further described below in the detailed description. This summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used as an indication of the scope of the claimed subject matter.BRIEF DESCRIPTION OF THE DRAWINGS

[0033] For a more complete understanding of the present disclosure, reference is now made to the following descriptions taken in conjunction with the accompanying drawings, in which:

[0034] Fig. 1 illustrates an example of DMRS-BF-EQ architecture;

[0035] Fig. 2 illustrates an example of UL C-Plane and U-plane data flows;

[0036] Fig. 3 illustrates an Table of existing C-Plane ST9 for SINR reporting;

[0037] Fig. 4 illustrates an example of DMRS-BF-EQ architecture;

[0038] Fig. 5 illustrates an example of DMRS-BF-EQ architecture;

[0039] Fig. 6 illustrates a new Table of C-Plane ST9 supporting sending aggregated SINR for DFT-s-OFDM;

[0040] Fig. 7 illustrates a flow-chart of a method embodiment under the present disclosure;

[0041] Fig. 8 illustrates a flow-chart of a method embodiment under the present disclosure;

[0042] Fig. 9 illustrates a flow-chart of a method embodiment under the present disclosure;

[0043] Fig. 10 illustrates a flow-chart of a method embodiment under the present disclosure;

[0044] Fig. 11 illustrates a flow-chart of a method embodiment under the present disclosure;

[0045] Fig. 12 illustrates a flow-chart of a method embodiment under the present disclosure;

[0046] Fig. 13 illustrates a flow-chart of a method embodiment under the present disclosure;

[0047] Fig. 14 illustrates a flow-chart of a method embodiment under the present disclosure;

[0048] Fig. 15 illustrates a flow-chart of a method embodiment under the present disclosure;

[0049] Fig. 16 illustrates a flow-chart of a method embodiment under the present disclosure;

[0050] Fig. 17 illustrates a flow-chart of a method embodiment under the present disclosure;

[0051] Fig. 18 shows a schematic of a communication system embodiment under the present disclosure;

[0052] Fig. 19 shows a schematic of a user equipment embodiment under the present disclosure;

[0053] Fig. 20 shows a schematic of a network node embodiment under the present disclosure;

[0054] Fig. 21 shows a schematic of a virtualization environment embodiment under the present disclosure.DETAILED DESCRIPTION

[0055] Before describing various embodiments of the present disclosure in detail, it is to be understood that this disclosure is not limited to the parameters of the particularlyexemplified systems, methods, apparatus, products, processes, and / or kits, which may, of course, vary. Thus, while certain embodiments of the present disclosure will be described in detail, with reference to specific configurations, parameters, components, elements, etc., the descriptions are illustrative and are not to be construed as limiting the scope of the claimed embodiments. In addition, the terminology used herein is for the purpose of describing the embodiments and is not necessarily intended to limit the scope of the claimed embodiments. Some of the embodiments contemplated herein will now be described more fully with reference to the accompanying drawings. Embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art.

[0056] As described above regarding the prior art, there currently exist certain challenges. In the 0-RAN WG4 open-fronthaul CUS specification being drafted for version 16, the frequency resolution of SINR reporting is configured by the 0-DU based on the O-RU’s reported capability via management (M)-plane by “sinr-per-prb” indicating the number of SINR values reporting per physical resource block (PRB). It means at least one SINR value is reported per scheduled PRB.

[0057] In UL, 5GNR supports both Cyclic Prefix - Orthogonal Frequency Division Multiplexing (CP-OFDM) and discrete Fourier transform - spread - OFDM (DFT-s-OFDM) waveforms, while 4G LTE only supports DFT-s-OFDM waveform. DFT-s-OFDM waveform has low peak-to-average power ratio (PAPR) compared to CP-OFDM, and thereby improves the efficiency of UE power amplifier. So, UEs can transmit with higher power using DFT-s-OFDM, which is important for UL coverage improvement. For 5G NR, UEs supports both CP-OFDM and DFT-s-OFDM. UEs can be scheduled to use either CP-OFDM or DFT-s-OFDM under different circumstances. The SINR reporting using ST9 described above can be used for both CP-OFDM and DFT-s-OFDM. No matter which waveform a UE is scheduled to use, the O-RU will send the same number of SINR values per PRB, i.e., “sinr-per-prb” number of SINR values per PRB to the O-DU. One focus of the present disclosure is to improve SINR reports for DFT-s-OFDM. DFT-s- OFDM uses DFT to spread the data symbols (e.g., quadrature amplitude modulation, QAM, modulated) of a UE layer across multiple REs of multiple PRBs. Then, the REs are transformed by a larger inverse fast Fourier transform (IFFT) (i.e., OFDM IFFT) to generate an OFDM symbol. Essentially, the DFT spreading operation makes the data symbols being transmitted using a single carrier waveform, which has lower PAPR than a multi-carrier waveform, like CP-OFDM withoutDFT spreading. At the receiver side, the process is reversed where IDFT de-spreading is performed to convert data symbols back for demodulation. In DMRS-BF-EQ, the IDFT de-spreading is done in the O-DU.

[0058] Note that the DFT spreading is also referred to as transform precoding. Therefore, DFT-s-OFDM is also referred to as OFDM with transform precoding and CP-OFDM is also referred to as OFDM without transform precoding. Basically, DFT-s-OFDM and CP- OFDM share most parts of the transceiver design. The only difference is that transform precoding is enabled for DFT-s-OFDM while transform precoding is disabled for CP-OFDM.

[0059] As described above, the O-RU reports to the O-DU “sinr-per-prb” number of SINR values per PRB per layer calculated in frequency domain in the O-RU. For a layer using DFT-s-OFDM, if multiple SINR values are reported from the O-RU for the scheduled PRB(s), the O-DU will calculate an aggregated SINR value for the scheduled PRB(s) (i.e., the whole PRB range scheduled) for the layer using the SINR values received. Then, the aggregated SINR value will be used to demodulate the DFT-s-OFDM data symbols of the layer. This is because DFT-s- OFDM is essentially a single carrier transmission scheme, where the data are modulated using a single carrier waveform using the whole scheduled bandwidth. In this case, the SINR used for demodulation is the SINR value for the whole scheduled bandwidth (or PRB range). So, only one SINR value is needed for one or more DFT-s-OFDM symbols. Therefore, when multiple SINR values are reported for the scheduled bandwidth of a UE layer, the O-DU needs to calculate an aggregated SINR value before using it for demodulation. Figure 4 shows DMRS-BF-EQ implementation for DFT-s-OFDM in O-RAN with SINR measurements per PRB.

[0060] The current way of sending SINR reports wastes fronthaul bandwidth since it requires to report multiple values for obtaining one value in the O-DU. It also takes some extra processing resources of O-DU, since O-DU needs to calculate the aggregated SINR value from the multiple received values. Block floating point (BFP) format is usually used to represent SINR values per PRB in ST9 where the SINR values share a common exponent. O-RU needs to convert the SINR values per PRB in BFP format before sending them Using ST9. Converting the SINR values to their BFP representation is not trivial, which consumes a lot of processing resources in O-RU, e.g., DSP cycles. After receiving the SINR report, the O-DU needs to convert the SINR values in BFP format to its own native format for processing, e.g., fixed point format. Convertingthe SINR values in BFP format to other format consumes a lot of processing resources in O-DU, e.g., DSP cycles.

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

[0062] For 5G NR, one proposal is that the layers using DFT-s-OFDM and the layers using CP-OFDM use different SINR frequency resolutions for SINR reporting per layer. The layers using DFT-s-OFDM use lower frequency resolution per layer for one or more symbols than that used by the layers using CP-OFDM. The best resolution for the latter case is to use one aggregated SINR value per PRB range per layer for one or more symbols, which is not supported today.

[0063] In one possible embodiment, 0-RU can optionally declare support for feature EFFICZENT-SINR-REPORT-FOR-DFTSOFDM (Discrete Fourier Transform-spread- Orthogonal Frequency Division Multiplexing) via M-plane. If the 0-RU supports the feature and the O-DU configures “efficient-sinr-report-for-dftsofdm-enabled = true”, 0-RU reports one aggregated SINR value per PRB range for each layer using DFT-s-OFDM. Figure 5 shows an implementation example of DMRS-BF-EQ for DFT-s-OFDM with aggregated SINR measurement per PRB range per layer for one or more symbols, depending on the time resolution configured. The PRB range is described in the section description for the layers in the C-plane message. It usually covers the full PRB range scheduled for a layer. If the full scheduled PRB range is split into multiple PRB ranges for a layer for some reason, 0-RU reports the same SINR value per PRB range for one or more symbols where the same SINR value is the aggregated SINR value for the full PRB range for the layer and the one or more symbols. O-DU can use any reported SINR value as the aggregated SINR for the full PRB range for the layer for the one or more symbols. Alternatively, O-RU reports the aggregated SINR per individual PRB range and O-DU needs to calculate the one aggregated SINR value for the full PRB range using the aggregated SINR values reported for multiple individual PRB ranges for the layer. In this case, O-DU still needs to do some extra calculation (but less calculation than the existing method in current 0-RAN open fronthaul specification). So, it is better to calculate the aggregated SINR value for the full PRB range for a layer and report the same value for multiple PRB ranges.

[0064] In a second embodiment, 0-RU declares a capability of SINR-FREQ- RESOLUTION-FOR-DFTSOFDM, which is a list of SINR frequency resolutions supported bythe O-RU. For example, SINR resolution = 0 means reporting one aggregated SINR value per PRB range per layer, while SINR resolution = X where X >0 means reporting X SNR values per PRB per layer. If O-RU supports SINR resolution = 0 and 0-DU configures “sinr-freq-resolution-for- dftsofdm = 0”, O-RU will report the aggregated SINR value per PRB range for a layer using DFT- s-OFDM. If O-RU is not able to support SINR resolution = 0 but can support other values, it is still beneficial that 0-DU can configure a lower SINR resolution to be used by the layers using DFT-s-OFDM than that to be used by the layers using CP-OFDM. For this embodiment, as described previously, O-RU reports the same SINR value(s) per PRB per layer for DFT-s-OFDM where the same SINR value is the aggregated SINR value for the full PRB range. This will reduce the 0-DU complexity.

[0065] In yet another third embodiment, O-RU uses the existing sinr-per-prb and report one or more SINR values per PRB. So, DFT-s-OFDM and CP-OFDM use the same frequency resolution. In this embodiment O-RU reports the same SINR value(s) per PRB per layer for DFT-s-OFDM where the same SINR value is the aggregated SINR value for the full PRB range for a layer. This will reduce the O-DU complexity.

[0066] In a further fourth embodiment, one more field is added in ST9, e.g., numSinrPerPrbForDftsofdm, to indicate the frequency resolution for DFT-s-OFDM. Then, the existing field of numSinrPerPrb is used to indicate the frequency resolution for CP-OFDM.

[0067] In a further fifth embodiment, the SINR reports of DFT-s-OFDM UE layers and the SINR reports of CP-OFDM UE layers are sent in separate C-Plane ST9 messages. In each message, the existing field of numSinrPerPrb in ST9 is used to indicate the frequency resolution used for the SINR reports of DFT-s-OFDM UE layers or the SINR reports of CP-OFDM UE layers in the message. In ST9, numSinrPerPrb is a 3 -bit field. Each numSinrPerPrb value (0-7) represents a frequency resolution. Currently, 6 values (0-5) are specified, while 2 values (6 and 7) are reserved. For example, numSinrPerPrb = 0 indicates 1 SINR value per PRB and numSinrPerPrb = 5 indicates 12 SINR value per PRB. To support the new frequency resolution 1 SINR value per PRB range for DFT-s-OFDM, a reserved value of numSinrPerPrb (6 or 7) may be used to indicate 1 SINR value per PRB range. In this way, the data structure of each SINR report per UE layer is deterministic in each message, i.e., the number of SINR values per PRB in each report is fixed. This facilitates 0-DU to parse the message with same number of SINR values per PRB in each section in the message. If O-RU sends the SINR reports of DFT-s-OFDM UE layers and CP-OFDM UE layers in separate sections of one message, O-DU needs to use sectionld to distinguish if a section is for DFT-s-OFDM UE layers or CP-OFDM UE layers and / or a new field may need to be added in each section to indicate if the section is for DFT-s-OFDM UE layers or CP-OFDM UE layers.

[0068] In 0-RAN protocol, 0-RU gets the C-plane message which indicates which layer(s) use DFT-s-OFDM and which layer(s) use CP-OFDM. Then, the 0-RU knows to use the corresponding SINR frequency resolution for the layers using DFT-s-OFDM and CP-OFDM, respectively. It should be noted that for 4G LTE, UL signal only uses DFT-s-OFDM, which may also be referred to as Single Carrier - Frequency Division Multiple Access, SC-FDMA. So, the present disclosure is also applicable to 4G LTE.

[0069] Certain embodiments may provide one or more of the following technical advantages. This disclosure supports efficient SINR reporting when DFT-s-OFDM is scheduled for some UEs in UL. For UE layers scheduled to use DFT-s-OFDM, the 0-RU only reports one aggregated SINR value per PRB range per layer for these layers instead of per PRB per layer, which reduces fronthaul bitrate. According to certain embodiments, the aggregated SINR value which is based on the effective channel gain and is averaged over multiple REs in the PRB range is calculated by the 0-RU, which has direct access to the individual effective channel representation per PRB (even per resource element, RE). It avoids unnecessary conversion between SINR value and effective channel representation, which saves processing resources. This disclosure also avoids converting many SINR values to BFP format in 0-RU which saves 0-RU processing, while it also avoids converting many SINR values from BFP format to its native format in O-DU which saves O-DU processing. The teachings of certain embodiments may improve the data rate, latency, power consumption, or other metrics.

[0070] As mentioned above, DFT-s-OFDM is essentially a single-carrier modulation scheme due to its transmission characteristics, despite the implementation reuses OFDM transmitter structure. An aggregated SINR value for the whole scheduled PRB range is used for demodulation of DFT-s-OFDM symbols.

[0071] For DMRS-BF-EQ scheme, the post-equalization SINR for a certain RE of a layer is defined as the power of signal of interest (S) divided by the sum of the interference power (I) (the inter-cell and intra-cell interreferences) plus the power of background noise (N) for the RE,i.e., SINRi = — where i represents the i-th layer. Consider the scenario with K user layers, the channel estimate is denoted as H G CNxKwhere N is the number of antennas. In case of MMSE-IRC equalization, the equalization weights on certain RE can be calculated as:W = (H' Q 'H + I)-1HHQ-1where Q G CNxNdenotes the covariance matrix of interference plus noise, and H / zdenotes the Hermitian transpose of matrix H. Accordingly, the SINR value on the RE in question for the i-th layer may be calculated as:1 SINRi = - - — - 11l ~ Gi where Gtis the i-th element of vector G which is obtained by the diagonal elements of the effective channels, i.e.,G = diag[WH]

[0072] For DMRS-BF-EQ, H per RE is obtained from DMRS channel estimation and W per RE is obtained from equalization weights calculation based on DMRS channel estimates. Therefore, multiple SINR values can be obtained per PRB per layer from channel estimation. For DFT-s-OFDM, one aggregated SINR value of the entire PRB range per layer needs to be calculated, which will be applied for demodulation of one or more symbols. As SINR is a division between S and I+N, which is typically frequency variant over frequency, the aggregated SINR value, denoted by SINR^, cannot be calculated by an arithmetic average of SINRi(l) for1=1, ... ,L, where SINRi(l) represents the SINR value of layer i of frequency point 1 (e.g., for a certain RE used) and where L denotes the total number of the frequency points of which the SINR values are available within the scheduled frequency range.

[0073] Instead, below are shown several methods calculating the aggregated SINR per layer, SINR^. The first method is listed below that SINR^ is calculated as the ratio between the total signal power and the total interference plus noise power of all frequency points, as shown by the following equations.2 2 where S£(Z) = (G£(Z)) and [I + TV]£(Z) = G£(Z) - (G£(Z)) .

[0074] The second method calculates the average effective channel gain over all frequency points as the effective channel gain of the single carrier channel of DFT-s-OFDM and then calculates the aggregated SINR, SINR^, according to the equation shown previously, as shown by the following equations.

[0075] To enable SINR reporting of a single value per layer for DFT-s-OFDM, the following methods can be utilized.

[0076] Below are given several possible, though non-limiting, examples of embodiments under the present disclosure.Embodiment A

[0077] In this embodiment, O-RU can declare support for feature EFFICIENT- SINR-REPORT-FOR-DFTSOFDM via M-plane. If the feature is supported, O-DU may configure the O-RU to report one aggregated SINR value per PRB range for each layer applying DFT-s- OFDM for UL by configuring “efficient-sinr-report-for-dftsofdm-enabled = true” via M-plane. In this case, O-RU calculates the aggregated SINR for the PRB range for each layer when DFT-s- OFDM is used and attaches only one aggregated SINR value in ST9 for each layer, irrespective of the configured parameter “sinr-per-prb”, which are applicable to one or more symbols, depending on the time resolution configured for SINR reporting. It means “sinr-per-prb” is only applicable to the layers using CP-OFDM. The PRB range for each layer in question is listed in the section description, which typically cover the entire scheduled PRB range of a layer. Figure 6 shows an example ST9 table, where the first section for a certain PRB range corresponds to a layer of one UE using DFT-s-OFDM and the second section for another PRB range corresponds to a layer of another UE using CP-OFDM. In the first section, there is only one aggregated SINR value reported since O-RU knows the first section is for a layer using DFT-s-OFDM. In the second section, there are 12 SINR values per PRB reported since O-RU knows the second section is for a layer using CP-OFDM, where the frequency resolution is configured to 12 values per PRB.

[0078] If efficient-sinr-report-for-dftsofdm-enabled is not declared, the frequency resolution of SINR reporting of all layers is determined by the configured “sinr-per-prb”.Embodiment B

[0079] In this embodiment, 0-RU declares a capability of sinr- freq-resolution-for- dftsofdm-supported, which is a list of SINR frequency resolutions supported by the 0-RU. For example, SINR frequency resolution = 0 means that the 0-RU supports reporting one aggregated SINR value per PRB range per layer for one or more symbols, while SINR resolution = x where x >0 means that the 0-RU supports reporting x SNR values per PRB per layer. In response to this capability, 0-DU may configure the 0-RU to report one aggregated SINR value per PRB range for each layer using DFT-s-OFDM for UL transmission by configuring “sinr-for-dftsofdm-freq- resolution” = 0 via M-plane. When “sinr-for-dftsofdm-freq-resolution = x” for x>0, the 0-RU reports x SINR values per PRB per layer in case of DFT-s-OFDM. The existing M-plane parameter “sinr-per-prb” can be used specifically for CP-OFDM case. This embodiment enables the use of different frequency resolutions in SINR reporting for CP-OFDM and DFT-s-OFDM. For example, CP-OFDM may be configured to send 3 SINR values per PRB with “sinr-per-prb = 3” while DFT- s-OFDM is configured to send 1 SINR value per PRB with “sinr-for-dftsofdm-freq-resolution = 1”. It is beneficial that 0-DU can configure a lower frequency resolution for SINR reporting for the layers using DFT-s-OFDM than that to be used by the layers using CP-OFDM. In this case, O- RU reports the same SINR value(s) per PRB per layer for DFT-s-OFDM where the same SINR value is the aggregated SINR value for the full PRB range per layer. This will reduce the 0-DU complexity.

[0080] The scheduled usage of UL waveform in terms of CP-OFDM or DFT-s- OFDM is conveyed from 0-DU to 0-RU by Section Extension 24 (SE24) used with Section Type 5 (ST5), possibly together with Section Extension 10 (SE10). In SE24, there is a field of entryType per layer. When 0-DU sets entryType = 2 for a layer, it indicates this layer uses CP-OFDM which doesn’t use transform precoding. When 0-DU sets entryType = 3 for a layer, it indicates this layer uses DFT-s-OFDM which uses transform precoding.

[0081] In section header of each section in ST9, as shown in Figure 3 and Figure 6, the PRB range is defined by “startPrbu” and “numPrbu”. As “numPrbu” is an 8-bit field, the maximum number of PRBs covered by one section is 256. If one layer of a UE is scheduled witha frequency range larger than 256 PRBs, for example, 273 PRBs for 100MHz, the corresponding SINR report would contain at least 2 sections for the layer. In some other examples, the whole scheduled PRB range for a layer may also be divided into multiple PRB ranges for the layer. In those cases, if the O-RU is configured to report one aggregated SINR value per layer:• The first embodiment is to repeat the same aggregated SINR value for the entire scheduled PRB range in all sections for the same UE layer using DFT-s-OFDM. For efficient reporting, each section should cover as many PRBs as possible.• The second embodiment is to report one aggregated SINR value for the PRBs defined by “startPrbu” and “numPrbu” in respective section for a layer. In this case, O-DU needs to calculate one aggregated SINR value for the entire scheduled PRB range of a layer using the aggregated SINR value of the layer reported for multiple individual PRB ranges of multiple sections.• The third embodiment is to set a special flag (e.g., sinrForPrbRange) in ST9. If “sinrForPrbRange” = 1, only one section is used irrespective of the number of scheduled PRBs and only one aggregated SINR value for the whole PRB range of the layer is attached in this section. With this flag on, the O-DU understands that the reported SINR value is for the entire scheduled PRB range, so it will ignore the field “numPrbu” but refer to the whole scheduled PRB range for the layer of the UE in the scheduling information instead, conveyed in other C-plane messages.Additional Embodiments

[0082] In yet another embodiment, O-RU uses the existing sinr-per-prb and report one or more SINR values per PRB. So, DFT-s-OFDM and CP-OFDM use the same frequency resolution. In this embodiment O-RU reports the same SINR value(s) per PRB per layer for DFT- s-OFDM where the same SINR value is the aggregated SINR value for the full PRB range of the layer. This will reduce the O-DU complexity.

[0083] In a further embodiment, one more field is added in ST9, e.g., numSinrPerPrbForDftsofdm, to indicate the frequency resolution for DFT-s-OFDM. Then, the existing field of numSinrPerPrb is used to indicate the frequency resolution for CP-OFDM.

[0084] In one more embodiment, the SINK reports of DFT-s-OFDM UE layers and the SINR reports of CP-OFDM UE layers are sent in separate C-Plane ST9 messages. In each message, the existing field of numSinrPerPrb in ST9 is used to indicate the frequency resolution used for the SINR reports of DFT-s-OFDM UE layers or the SINR reports of CP-OFDM UE layers in the message. In ST9, numSinrPerPrb is a 3 -bit field. Each numSinrPerPrb value (0-7) represents a frequency resolution. Currently, 6 values (0-5) are specified, while 2 values (6 and 7) are reserved. For example, numSinrPerPrb = 0 indicates 1 SINR value per PRB and numSinrPerPrb = 5 indicates 12 SINR value per PRB. To support the new frequency resolution 1 SINR value per PRB range for DFT-s-OFDM, a reserved value of numSinrPerPrb (6 or 7) may be used to indicate 1 SINR value per PRB range. In this way, the data structure of each SINR report per UE layer is deterministic in each message, i.e., the number of SINR values per PRB in each report is fixed. This facilitates 0-DU to parse the message with same number of SINR values per PRB in each section in the message. If 0-RU sends the SINR reports of DFT-s-OFDM UE layers and CP- OFDM UE layers in separate sections of one message, 0-DU needs to use sectionld to distinguish if a section is for DFT-s-OFDM UE layers or CP-OFDM UE layers and / or a new field may need to be added in each section to indicate if the section is for DFT-s-OFDM UE layers or CP-OFDM UE layers.

[0085] Another possible method embodiment under the present disclosure is shown in Figure 7. Method 1000 comprises a method performed by an 0-RU for enabling SINR reporting to an 0-DU. Step 1010 is calculating one SINR value for a plurality of PRBs per layer for one or more symbols. Step 1020 is transmitting the one SINR value for the plurality of PRBs per layer for one or more symbols to the 0-DU. Method 1000 can comprise multiple variations and embodiments and / or additional and / or alternative steps. For example, some embodiments can further comprise receiving, from the 0-DU, a configuration to report the one SINR value for a plurality of PRBs per layer for one or more symbols. In some variations, transmitting the one SINR value for the plurality of PRBs comprises transmitting the same SINR value for different PRB ranges in the plurality of PRBs. In some embodiments the plurality of PRBs comprises one or more PRB ranges. In some embodiments, each layer applies transform precoded multi-carrier modulation for UL. In some variations, each layer applies DFT-s-OFDM, for uplink. In some variations, the calculating comprises calculating a single SINR value; and / or the transmitting comprises transmitting the single SINR value one or multiple times. In some embodiments,equalization is performed by the O-RU. Some embodiments can further comprise declaring, to the O-DU, support for one or more capabilities and / or features via M-Plane regarding SINR reporting for DFT-s-OFDM.

[0086] Another possible method embodiment under the present disclosure is shown in Figure 8. Method 1200 comprises a method performed by an O-RU for enabling SINR reporting of a single value for a PRB range containing two or more PRBs per layer for DFT-s-OFDM. Step 1210 is declaring, by the O-RU, a capability for sending one SINR value for more than one PRB for one or more symbols. Method 1200 can comprise multiple variations and embodiments and / or additional and / or alternative steps. For example, in some embodiments, if SINR frequency resolution = 0, then the O-RU supports reporting one aggregated SINR value per PRB range per layer; and if SINR frequency resolution = x, where x >0, then the O-RU supports reporting x SINR values per PRB per layer. Some embodiments can further comprise receiving, from an O-DU, a configuration to report one aggregated SINR value per PRB range for each layer using DFT-s- OFDM for UL transmission. In some embodiments, the O-RU reports the same SINR value per PRB per layer for DFT-s-OFDM where the same SINR value comprises an aggregated SINR value for a full PRB range per layer.

[0087] Another possible method embodiment under the present disclosure is shown in Figure 9. Method 1400 comprises a method performed by an O-RU for enabling SINR reporting. Step 1410 is reporting, with an existing numSinrPerPrb field, a single SINR value for a PRB range containing two or more PRBs for DFT-s-OFDM; wherein the single SINR value comprises an aggregated SINR value for a full PRB range per layer. Method 1400 can comprise multiple variations and embodiments and / or additional and / or alternative steps. For example, some embodiments can further comprise indicating, to an O-DU, a frequency resolution for CP-OFDM with an existing numSinrPerPrb field, wherein ST9 adds one more field to indicate frequency resolution for DFT-s-OFDM. In some embodiments, a specific value of the existing numSinrPerPrb field is used to indicate the single SINR value report for DFT-s-OFDM, while other values are used to indicate frequency resolution for CP-OFDM.

[0088] Another possible method embodiment under the present disclosure is shown in Figure 10. Method 1600 comprises a method performed by an O-DU for enabling SINR reporting. Step 1610 is receiving, from the O-RU, a single SINR value for a PRB range containing two or more PRBs per layer for DFT-s-OFDM; wherein the single SINR value comprises anaggregated SINR, wherein the O-RU calculated the aggregated SINR for the PRB range per layer when DFT-s-OFDM is used and attached only one aggregated SINR value per section of ST9 for each layer. Method 1600 can comprise multiple variations and embodiments and / or additional and / or alternative steps. For example, in some embodiments the receiving is performed irrespective of a configured sinr-per-prb parameter in M-Plane. Some embodiments can further comprise receiving a declaration, from the O-RU, for support for one or more capabilities and / or features via M-Plane regarding SINR reporting for DFT-s-OFDM. Some variations can further comprise transmitting, to the O-RU, a configuration to report one aggregated SINR value per PRB range for each layer applying DFT-s-OFDM for UL.

[0089] Another possible method embodiment under the present disclosure is shown in Figure 11. Method 1800 comprises a method performed by an O-DU for enabling SINR reporting of a single value for a PRB range containing two or more PRBs per layer for DFT-s- OFDM. Step 1810 receiving a declaration, from the O-RU, a capability for sending one SINR value for more than one PRB. Method 1800 can comprise multiple variations and embodiments and / or additional and / or alternative steps.

[0090] Another possible method embodiment under the present disclosure is shown in Figure 12. Method 2000 comprises a method performed by an O-DU for enabling SINR reporting of a single value for a PRB range containing two or more PRBs per layer for DFT-s- OFDM. Step 2010 is receiving, from the O-RU, a single SINR value for a PRB range containing two or more PRBs per layer, so that DFT-s-OFDM and CP-OFDM, use the same frequency resolution; wherein the O-RU reports the single SINR value per PRB range per layer for DFT-s- OFDM wherein the single SINR value comprises an aggregated SINR value for the full PRB range per layer. Method 2000 can comprise multiple variations and embodiments and / or additional and / or alternative steps.

[0091] Another possible method embodiment under the present disclosure is shown in Figure 13. Method 2200 comprises a method performed by an O-DU for enabling SINR reporting. Step 2210 is receiving an indication, from an O-RU, of a single SINR value for a PRB range containing two or more PRBs per layer for DFT-s-OFDM. Method 2200 can comprise multiple variations and embodiments and / or additional and / or alternative steps. For example, some embodiments can further comprise: receiving, from the O-RU, a frequency resolution for CP-OFDM, in an existing numSinrPerPrb field; wherein ST9 adds one more field to indicate frequency resolution for DFT-s-OFDM.

[0092] Another possible method embodiment under the present disclosure is shown in Figure 14. Method 2400 comprises a method performed by an O-RU for enabling SINK reporting to an O-DU. Step 2410 is calculating a single SINR value for a PRB range containing two or more PRBs per layer for one or more symbols. Step 2420 is transmitting an indication of the single SINR value to the O-DU. Method 2400 can comprise multiple variations and embodiments and / or additional and / or alternative steps. For example, in some embodiments the indication is at least one of implicit; explicit.

[0093] Another possible method embodiment under the present disclosure is shown in Figure 15. Method 2600 comprises a method performed by an O-DU for enabling SINR reporting. Step 2610 is receiving, from the O-RU, an indication of a single SINR value for a PRB range containing two or more PRBs per layer for DFT-s-OFDM; wherein the single SINR value comprises an aggregated SINR, wherein the O-RU calculated the aggregated SINR for the PRB range per layer. Method 2600 can comprise multiple variations and embodiments and / or additional and / or alternative steps. For example, in some embodiments the indication is at least one of implicit; explicit.

[0094] Another possible method embodiment under the present disclosure is shown in Figure 16. Method 2800 is a method performed by an O-RU for enabling SINR reporting. Step 2810 is calculating a single SINR value for a PRB range containing two or more PRBs for DFT- s-OFDM and for CP-OFDM. Step 2820 is transmitting, to an O-DU, the single SINR value; wherein the layers using DFT-s-OFDM and the layers using CP-OFDM use different SINR frequency resolutions for SINR reporting per layer. Method 2800 can comprise multiple variations and embodiments and / or additional and / or alternative steps. For example, in some embodiments the layers using DFT-s-OFDM use lower frequency resolution per layer for one or more symbols than that used by the layers using CP-OFDM. In some embodiments one aggregated SINR value is used per PRB range per layer for one or more symbols.

[0095] Another possible method embodiment under the present disclosure is shown in Figure 17. Method 2900 is a method performed by an O-DU for enabling SINR reporting. Step 2910 is receiving, from the O-RU, a single SINR value for a PRB range containing two or more PRBs per layer for DFT-s-OFDM and for CP-OFDM; wherein the layers using DFT-s-OFDM andthe layers using CP-OFDM use different SINR frequency resolutions for SINR reporting per layer. Method 2900 can comprise multiple variations and embodiments and / or additional and / or alternative steps. For example, in some embodiments the layers using DFT-s-OFDM use lower frequency resolution per layer for one or more symbols than that used by the layers using CP- OFDM. In some embodiments one aggregated SINR value is used per PRB range per layer for one or more symbols.

[0096] Figure 18 shows an example of a communication system 3100 in accordance with some embodiments. In the example, the communication system 3100 includes a telecommunication network 3102 that includes an access network 3104, such as a radio access network (RAN), and a core network 3106, which includes one or more core network nodes 3108. The access network 3104 includes one or more access network nodes, such as network nodes 3110a and 3110b (one or more of which may be generally referred to as network nodes 3110), or any other similar 3rd Generation Partnership Project (3GPP) access nodes or non-3GPP access points. Moreover, as will be appreciated by those of skill in the art, a network node is not necessarily limited to an implementation in which a radio portion and a baseband portion are supplied and integrated by a single vendor. Thus, it will be understood that network nodes include disaggregated implementations or portions thereof. For example, in some embodiments, the telecommunication network 3102 includes one or more Open-RAN (ORAN) network nodes. An ORAN network node is a node in the telecommunication network 3102 that supports an ORAN specification (e.g., a specification published by the O-RAN Alliance, or any similar organization) and may operate alone or together with other nodes to implement one or more functionalities of any node in the telecommunication network 3102, including one or more network nodes 3110 and / or core network nodes 3108.

[0097] Examples of an ORAN network node include an O-RAN radio unit (O-RU), an O-RAN distributed unit (O-DU), an O-RAN central unit (O-CU), including an O-CU control plane (O-CU-CP) or an O-CU user plane (O-CU-UP), a RAN intelligent controller (near-real time or non-real time) hosting software or software plug-ins, such as a near-real time control application (e.g., xApp) or a non-real time control application (e.g., rApp), or any combination thereof (the adjective “open” designating support of an ORAN specification). The network node may support a specification by, for example, supporting an interface defined by the ORAN specification, suchas an Al, Fl, Wl, El, E2, X2, Xn interface, an open fronthaul user plane interface, or an open fronthaul management plane interface. Moreover, an ORAN access node may be a logical node in a physical node. Furthermore, an ORAN network node may be implemented in a virtualization environment (described further below) in which one or more network functions are virtualized. For example, the virtualization environment may include an O-Cloud computing platform orchestrated by a Service Management and Orchestration Framework via an 0-2 interface defined by the 0-RAN Alliance or comparable technologies. The network nodes 3110 facilitate direct or indirect connection of user equipment (UE), such as by connecting UEs 3112a, 3112b, 3112c, and 3112d (one or more of which may be generally referred to as UEs 3112) to the core network 3106 over one or more wireless connections.

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

[0099] The UEs 3112 may be any of a wide variety of communication devices, including wireless devices arranged, configured, and / or operable to communicate wirelessly with the network nodes 3110 and other communication devices. Similarly, the network nodes 3110 are arranged, capable, configured, and / or operable to communicate directly or indirectly with the UEs 3112 and / or with other network nodes or equipment in the telecommunication network 3102 to enable and / or provide network access, such as wireless network access, and / or to perform other functions, such as administration in the telecommunication network 3102.[000100] In the depicted example, the core network 3106 connects the network nodes 3110 to one or more host computing systems, such as host 3116. These connections may be direct or indirect via one or more intermediary networks or devices. In other examples, network nodes may be directly coupled to hosts. The core network 3106 includes one more core network nodes (e.g., core network node 3108) that are structured with hardware and software components.Features of these components may be substantially similar to those described with respect to the UEs, network nodes, and / or hosts, such that the descriptions thereof are generally applicable to the corresponding components of the core network node 3108. Example core network nodes include functions of one or more of a Mobile Switching Center (MSC), Mobility Management Entity (MME), Home Subscriber Server (HSS), Access and Mobility Management Function (AMF), Session Management Function (SMF), Authentication Server Function (AUSF), Subscription Identifier De-concealing function (SIDF), Unified Data Management (UDM), Security Edge Protection Proxy (SEPP), Network Exposure Function (NEF), and / or a User Plane Function (UPF).[000101] The host 3116 may be under the ownership or control of a service provider other than an operator or provider of the access network 3104 and / or the telecommunication network 3102. The host 3116 may host a variety of applications to provide one or more service. Examples of such applications include live and pre-recorded audio / video content, data collection services such as retrieving and compiling data on various ambient conditions detected by a plurality of UEs, analytics functionality, social media, functions for controlling or otherwise interacting with remote devices, functions for an alarm and surveillance center, or any other such function performed by a server.[000102] As a whole, the communication system 3100 of Figure 18 enables connectivity between the UEs, network nodes, and hosts. In that sense, the communication system may be configured to operate according to predefined rules or procedures, such as specific standards that include, but are not limited to: Global System for Mobile Communications (GSM); Universal Mobile Telecommunications System (UMTS); Long Term Evolution (LTE), and / or other suitable 2G, 3G, 4G, 5G standards, or any applicable future generation standard (e.g., 6G); wireless local area network (WLAN) standards, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards (WiFi); and / or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z- Wave, Near Field Communication (NFC) ZigBee, LiFi, and / or any low-power wide-area network (LPWAN) standards such as LoRa and Sigfox.[000103] In some examples, the telecommunication network 3102 is a cellular network that implements 3 GPP standardized features. Accordingly, the telecommunications network 3102 may support network slicing to provide different logical networks to different devices that are connected to the telecommunication network 3102. For example, thetelecommunications network 3102 may provide Ultra Reliable Low Latency Communication (URLLC) services to some UEs, while providing Enhanced Mobile Broadband (eMBB) services to other UEs, and / or Massive Machine Type Communication (mMTC) / Massive loT services to yet further UEs.[000104] In some examples, the UEs 3112 are configured to transmit and / or receive information without direct human interaction. For instance, a UE may be designed to transmit information to the access network 3104 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network 3104. Additionally, a UE may be configured for operating in single- or multi-RAT or multi -standard mode. For example, a UE may operate with any one or combination of Wi-Fi, NR (New Radio) and LTE, i.e. being configured for multi-radio dual connectivity (MR-DC), such as E-UTRAN (Evolved-UMTS Terrestrial Radio Access Network) New Radio - Dual Connectivity (EN-DC).[000105] In the example, the hub 3114 communicates with the access network 3104 to facilitate indirect communication between one or more UEs (e.g., UE 3112c and / or 3112d) and network nodes (e.g., network node 3110b). In some examples, the hub 3114 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs. For example, the hub 3114 may be a broadband router enabling access to the core network 3106 for the UEs. As another example, the hub 3114 may be a controller that sends commands or instructions to one or more actuators in the UEs. Commands or instructions may be received from the UEs, network nodes 3110, or by executable code, script, process, or other instructions in the hub 3114. As another example, the hub 3114 may be a data collector that acts as temporary storage for UE data and, in some embodiments, may perform analysis or other processing of the data. As another example, the hub 3114 may be a content source. For example, for a UE that is a VR device, display, loudspeaker, or other media delivery device, the hub 3114 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub 3114 then provides to the UE either directly, after performing local processing, and / or after adding additional local content. In still another example, the hub 3114 acts as a proxy server or orchestrator for the UEs, in particular if one or more of the UEs are low energy loT devices.[000106] The hub 3114 may have a constant / persistent or intermittent connection to the network node 3110b. The hub 3114 may also allow for a different communication schemeand / or schedule between the hub 3114 and UEs (e.g., UE 3112c and / or 3112d), and between the hub 3114 and the core network 3106. In other examples, the hub 3114 is connected to the core network 3106 and / or one or more UEs via a wired connection. Moreover, the hub 3114 may be configured to connect to an M2M service provider over the access network 3104 and / or to another UE over a direct connection. In some scenarios, UEs may establish a wireless connection with the network nodes 3110 while still connected via the hub 3114 via a wired or wireless connection. In some embodiments, the hub 3114 may be a dedicated hub - that is, a hub whose primary function is to route communications to / from the UEs from / to the network node 3110b. In other embodiments, the hub 3114 may be a non-dedicated hub - that is, a device which is capable of operating to route communications between the UEs and network node 3110b, but which is additionally capable of operating as a communication start and / or end point for certain data channels.[000107] Figure 19 shows a UE 3200 in accordance with some embodiments. The UE 3200 presents additional details of some embodiments of the UE 3112 of Figure 18. As used herein, a UE refers to a device capable, configured, arranged and / or operable to communicate wirelessly with network nodes and / or other UEs. Examples of a UE include, but are not limited to, a smart phone, mobile phone, cell phone, voice over IP (VoIP) phone, wireless local loop phone, desktop computer, personal digital assistant (PDA), wireless cameras, gaming console or device, music storage / playback device, wearable terminal device, wireless endpoint, mobile station, tablet, laptop, laptop-embedded equipment (LEE), laptop-mounted equipment (LME), an Augmented Reality (AR) or Virtual Reality (VR) device, wireless customer-premise equipment (CPE), vehicle, vehicle-mounted or vehicle embedded / integrated wireless device, etc. Other examples include any UE identified by the 3rd Generation Partnership Project (3GPP), including a narrow band internet of things (NB-IoT) UE, a machine type communication (MTC) UE, and / or an enhanced MTC (eMTC) UE.[000108] A UE may support device-to-device (D2D) communication, for example by implementing a 3 GPP standard for sidelink communication, Dedicated Short-Range Communication (DSRC), vehi cl e-to- vehicle (V2V), vehicle-to-infrastructure (V2I), or vehicle-to- everything (V2X). In other examples, a UE may not necessarily have a user in the sense of a human user who owns and / or operates the relevant device. Instead, a UE may represent a device that is intended for sale to, or operation by, a human user but which may not, or which may not initially,be associated with a specific human user (e.g., a smart sprinkler controller). Alternatively, a UE may represent a device that is not intended for sale to, or operation by, an end user but which may be associated with or operated for the benefit of a user (e.g., a smart power meter).[000109] The UE 3200 includes processing circuitry 3202 that is operatively coupled via a bus 3204 to an input / output interface 3206, a power source 3208, a memory 3210, a communication interface 3212, and / or any other component, or any combination thereof. Certain UEs may utilize all or a subset of the components shown in Figure 19. The level of integration between the components may vary from one UE to another UE. Further, certain UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.[000110] The processing circuitry 3202 is configured to process instructions and data and may be configured to implement any sequential state machine operative to execute instructions stored as machine-readable computer programs in the memory 3210. The processing circuitry 3202 may be implemented as one or more hardware-implemented state machines (e.g., in discrete logic, field-programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), etc.); programmable logic together with appropriate firmware; one or more stored computer programs, general -purpose processors, such as a microprocessor or digital signal processor (DSP), together with appropriate software; or any combination of the above. For example, the processing circuitry 3202 may include multiple central processing units (CPUs).[000111] In the example, the input / output interface 3206 may be configured to provide an interface or interfaces to an input device, output device, or one or more input and / or output devices. Examples of an output device include a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smartcard, another output device, or any combination thereof. An input device may allow a user to capture information into the UE 3200. Examples of an input device include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a web camera, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smartcard, and the like. The presencesensitive display may include a capacitive or resistive touch sensor to sense input from a user. A sensor may be, for instance, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, a biometric sensor, etc., or any combinationthereof. An output device may use the same type of interface port as an input device. For example, a Universal Serial Bus (USB) port may be used to provide an input device and an output device.[000112] In some embodiments, the power source 3208 is structured as a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic device, or power cell, may be used. The power source 3208 may further include power circuitry for delivering power from the power source 3208 itself, and / or an external power source, to the various parts of the UE 3200 via input circuitry or an interface such as an electrical power cable. Delivering power may be, for example, for charging of the power source 3208. Power circuitry may perform any formatting, converting, or other modification to the power from the power source 3208 to make the power suitable for the respective components of the UE 3200 to which power is supplied.[000113] The memory 3210 may be or be configured to include memory such as random access memory (RAM), read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disks, optical disks, hard disks, removable cartridges, flash drives, and so forth. In one example, the memory 3210 includes one or more application programs 3214, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data 3216. The memory 3210 may store, for use by the UE 3200, any of a variety of various operating systems or combinations of operating systems.[000114] The memory 3210 may be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, high-density digital versatile disc (HD- DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, holographic digital data storage (HDDS) optical disc drive, external mini-dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), external micro-DIMM SDRAM, smartcard memory such as tamper resistant module in the form of a universal integrated circuit card (UICC) including one or more subscriber identity modules (SIMs), such as a USIM and / or ISIM, other memory, or any combination thereof. The UICC may for example be an embedded UICC (eUICC), integrated UICC (iUICC) or a removable UICC commonly known as ‘SIM card.’ The memory 3210 may allow the UE 3200 to access instructions, application programs and thelike, stored on transitory or non-transitory memory media, to off-load data, or to upload data. An article of manufacture, such as one utilizing a communication system may be tangibly embodied as or in the memory 3210, which may be or comprise a device-readable storage medium.[000115] The processing circuitry 3202 may be configured to communicate with an access network or other network using the communication interface 3212. The communication interface 3212 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna 3222. The communication interface 3212 may include one or more transceivers used to communicate, such as by communicating with one or more remote transceivers of another device capable of wireless communication (e.g., another UE or a network node in an access network). Each transceiver may include a transmitter 3218 and / or a receiver 3220 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth). Moreover, the transmitter 3218 and receiver 3220 may be coupled to one or more antennas (e.g., antenna 3222) and may share circuit components, software or firmware, or alternatively be implemented separately.[000116] In the illustrated embodiment, communication functions of the communication interface 3212 may include cellular communication, Wi-Fi communication, LPWAN communication, data communication, voice communication, multimedia communication, short-range communications such as Bluetooth, near-field communication, location-based communication such as the use of the global positioning system (GPS) to determine a location, another like communication function, or any combination thereof. Communications may be implemented in according to one or more communication protocols and / or standards, such as IEEE 802.11, Code Division Multiplexing Access (CDMA), Wideband Code Division Multiple Access (WCDMA), GSM, LTE, New Radio (NR), UMTS, WiMax, Ethernet, transmission control protocol / internet protocol (TCP / IP), synchronous optical networking (SONET), Asynchronous Transfer Mode (ATM), QUIC, Hypertext Transfer Protocol (HTTP), and so forth.[000117] Regardless of the type of sensor, a UE may provide an output of data captured by its sensors, through its communication interface 3212, via a wireless connection to a network node. Data captured by sensors of a UE can be communicated through a wireless connection to a network node via another UE. The output may be periodic (e.g., once every 15 minutes if it reports the sensed temperature), random (e.g., to even out the load from reporting from several sensors), in response to a triggering event (e.g., when moisture is detected an alert issent), in response to a request (e.g., a user initiated request), or a continuous stream (e.g., a live video feed of a patient).[000118] As another example, a UE comprises an actuator, a motor, or a switch, related to a communication interface configured to receive wireless input from a network node via a wireless connection. In response to the received wireless input the states of the actuator, the motor, or the switch may change. For example, the UE may comprise a motor that adjusts the control surfaces or rotors of a drone in flight according to the received input or to a robotic arm performing a medical procedure according to the received input.[000119] A UE, when in the form of an Internet of Things (loT) device, may be a device for use in one or more application domains, these domains comprising, but not limited to, city wearable technology, extended industrial application and healthcare. Non-limiting examples of such an loT device are a device which is or which is embedded in: a connected refrigerator or freezer, a TV, a connected lighting device, an electricity meter, a robot vacuum cleaner, a voice controlled smart speaker, a home security camera, a motion detector, a thermostat, a smoke detector, a door / window sensor, a flood / moisture sensor, an electrical door lock, a connected doorbell, an air conditioning system like a heat pump, an autonomous vehicle, a surveillance system, a weather monitoring device, a vehicle parking monitoring device, an electric vehicle charging station, a smart watch, a fitness tracker, a wearable for tactile augmentation or sensory enhancement, a water sprinkler, an animal- or item-tracking device, a sensor for monitoring a plant or animal, an industrial robot, an Unmanned Aerial Vehicle (UAV), and any kind of medical device, like a heart rate monitor or a remote controlled surgical robot. A UE in the form of an loT device comprises circuitry and / or software in dependence of the intended application of the loT device in addition to other components as described in relation to the UE 3200 shown in Figure 19.[000120] As yet another specific example, in an loT scenario, a UE may represent a machine or other device that performs monitoring and / or measurements, and transmits the results of such monitoring and / or measurements to another UE and / or a network node. The UE may in this case be an M2M device, which may in a 3GPP context be referred to as an MTC device. As one particular example, the UE may implement the 3GPP NB-IoT standard. In other scenarios, a UE may represent a vehicle, such as a car, a bus, a truck, a ship and an airplane, or other equipmentthat is capable of monitoring and / or reporting on its operational status or other functions associated with its operation.[000121] In practice, any number of UEs may be used together with respect to a single use case. For example, a first UE might be or be integrated in a drone and provide the drone’s speed information (obtained through a speed sensor) to a second UE that is a remote controller operating the drone. When the user makes changes from the remote controller, the first UE may adjust the throttle on the drone (e.g. by controlling an actuator) to increase or decrease the drone’s speed. The first and / or the second UE can also include more than one of the functionalities described above. For example, a UE might comprise the sensor and the actuator, and handle communication of data for both the speed sensor and the actuators.[000122] Figure 20 shows a network node 3300 in accordance with some embodiments. As used herein, network node refers to equipment capable, configured, arranged and / or operable to communicate directly or indirectly with a UE and / or with other network nodes or equipment, in a telecommunication network. Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs) and NR NodeBs (gNBs)), 0-RAN nodes or components of an 0-RAN node (e.g., 0-RU, 0-DU, O-CU).[000123] Base stations may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and so, depending on the provided amount of coverage, may be referred to as femto base stations, pico base stations, micro base stations, or macro base stations. A base station may be a relay node or a relay donor node controlling a relay. A network node may also include one or more (or all) parts of a distributed radio base station such as centralized digital units, distributed units (e.g., in an 0-RAN access node) and / or remote radio units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such remote radio units may or may not be integrated with an antenna as an antenna integrated radio. Parts of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS).[000124] Other examples of network nodes include multiple transmission point (multi-TRP) 5G access nodes, multi-standard radio (MSR) equipment such as MSR BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), base transceiver stations (BTSs), transmission points, transmission nodes, multi-cell / multicastcoordination entities (MCEs), Operation and Maintenance (O&M) nodes, Operations Support System (OSS) nodes, Self-Organizing Network (SON) nodes, positioning nodes (e.g., Evolved Serving Mobile Location Centers (E-SMLCs)), and / or Minimization of Drive Tests (MDTs).[000125] The network node 3300 includes a processing circuitry 3302, a memory 3304, a communication interface 3306, and a power source 3308. The network node 3300 may be composed of multiple physically separate components (e.g., a NodeB component and a RNC component, or a BTS component and a BSC component, etc.), which may each have their own respective components. In certain scenarios in which the network node 3300 comprises multiple separate components (e.g., BTS and BSC components), one or more of the separate components may be shared among several network nodes. For example, a single RNC may control multiple NodeBs. In such a scenario, each unique NodeB and RNC pair, may in some instances be considered a single separate network node. In some embodiments, the network node 3300 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memory 3304 for different RATs) and some components may be reused (e.g., a same antenna 3310 may be shared by different RATs). The network node 3300 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 3300, for example GSM, WCDMA, LTE, NR, WiFi, Zigbee, Z-wave, LoRaWAN, Radio Frequency Identification (RFID) or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within network node 3300.[000126] The processing circuitry 3302 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software and / or encoded logic operable to provide, either alone or in conjunction with other network node 3300 components, such as the memory 3304, to provide network node 3300 functionality.[000127] In some embodiments, the processing circuitry 3302 includes a system on a chip (SOC). In some embodiments, the processing circuitry 3302 includes one or more of radio frequency (RF) transceiver circuitry 3312 and baseband processing circuitry 3314. In some embodiments, the radio frequency (RF) transceiver circuitry 3312 and the baseband processing circuitry 3314 may be on separate chips (or sets of chips), boards, or units, such as radio units anddigital units. In alternative embodiments, part or all of RF transceiver circuitry 3312 and baseband processing circuitry 3314 may be on the same chip or set of chips, boards, or units.[000128] The memory 3304 may comprise any form of volatile or non-volatile computer-readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), readonly memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and / or any other volatile or non-volatile, non-transitory device-readable and / or computer-executable memory devices that store information, data, and / or instructions that may be used by the processing circuitry 3302. The memory 3304 may store any suitable instructions, data, or information, including a computer program, software, an application including one or more of logic, rules, code, tables, and / or other instructions capable of being executed by the processing circuitry 3302 and utilized by the network node 3300. The memory 3304 may be used to store any calculations made by the processing circuitry 3302 and / or any data received via the communication interface 3306. In some embodiments, the processing circuitry 3302 and memory 3304 is integrated.[000129] The communication interface 3306 is used in wired or wireless communication of signaling and / or data between a network node, access network, and / or UE. As illustrated, the communication interface 3306 comprises port(s) / terminal(s) 3316 to send and receive data, for example to and from a network over a wired connection. The communication interface 3306 also includes radio front-end circuitry 3318 that may be coupled to, or in certain embodiments a part of, the antenna 3310. Radio front-end circuitry 3318 comprises filters 3320 and amplifiers 3322. The radio front-end circuitry 3318 may be connected to an antenna 3310 and processing circuitry 3302. The radio front-end circuitry may be configured to condition signals communicated between antenna 3310 and processing circuitry 3302. The radio front-end circuitry 3318 may receive digital data that is to be sent out to other network nodes or UEs via a wireless connection. The radio front-end circuitry 3318 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 3320 and / or amplifiers 3322. The radio signal may then be transmitted via the antenna 3310. Similarly, when receiving data, the antenna 3310 may collect radio signals which are then converted into digital data by the radio front-end circuitry 3318. The digital data may be passed to the processingcircuitry 3302. In other embodiments, the communication interface may comprise different components and / or different combinations of components.[000130] In certain alternative embodiments, the network node 3300 does not include separate radio front-end circuitry 3318, instead, the processing circuitry 3302 includes radio frontend circuitry and is connected to the antenna 3310. Similarly, in some embodiments, all or some of the RF transceiver circuitry 3312 is part of the communication interface 3306. In still other embodiments, the communication interface 3306 includes one or more ports or terminals 3316, the radio front-end circuitry 3318, and the RF transceiver circuitry 3312, as part of a radio unit (not shown), and the communication interface 3306 communicates with the baseband processing circuitry 3314, which is part of a digital unit (not shown).[000131] The antenna 3310 may include one or more antennas, or antenna arrays, configured to send and / or receive wireless signals. The antenna 3310 may be coupled to the radio front-end circuitry 3318 and may be any type of antenna capable of transmitting and receiving data and / or signals wirelessly. In certain embodiments, the antenna 3310 is separate from the network node 3300 and connectable to the network node 3300 through an interface or port.[000132] The antenna 3310, communication interface 3306, and / or the processing circuitry 3302 may be configured to perform any receiving operations and / or certain obtaining operations described herein as being performed by the network node. Any information, data and / or signals may be received from a UE, another network node and / or any other network equipment. Similarly, the antenna 3310, the communication interface 3306, and / or the processing circuitry 3302 may be configured to perform any transmitting operations described herein as being performed by the network node. Any information, data and / or signals may be transmitted to a UE, another network node and / or any other network equipment.[000133] The power source 3308 provides power to the various components of network node 3300 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). The power source 3308 may further comprise, or be coupled to, power management circuitry to supply the components of the network node 3300 with power for performing the functionality described herein. For example, the network node 3300 may be connectable to an external power source (e.g., the power grid, an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry of the power source 3308. As a further example, the power source 3308 maycomprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry. The battery may provide backup power should the external power source fail.[000134] Embodiments of the network node 3300 may include additional components beyond those shown in Figure 20 for providing certain aspects of the network node’s functionality, including any of the functionality described herein and / or any functionality necessary to support the subject matter described herein. For example, the network node 3300 may include user interface equipment to allow input of information into the network node 3300 and to allow output of information from the network node 3300. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node 3300. In some embodiments providing a core network node, such as core network node 3108 of Figure 18 some components, such as the radio front-end circuitry 3318 and the RF transceiver circuitry 3312 may be omitted.[000135] Figure 21 is a block diagram illustrating a virtualization environment 3400 in which functions implemented by some embodiments may be virtualized. In the present context, virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices and networking resources. As used herein, virtualization can be applied to any device described herein, or components thereof, and relates to an implementation in which at least a portion of the functionality is implemented as one or more virtual components. Some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines (VMs) implemented in one or more virtual environments 3400 hosted by one or more of hardware nodes, such as a hardware computing device that operates as a network node, UE, core network node, or host. Further, in embodiments in which the virtual node does not require radio connectivity (e.g., a core network node or host), then the node may be entirely virtualized. In some embodiments, the virtualization environment 3400 includes components defined by the O-RAN Alliance, such as an O-Cloud environment orchestrated by a Service Management and Orchestration Framework via an O-2 interface. Virtualization may facilitate distributed implementations of a network node, UE, core network node, or host.[000136] Applications 3402 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) are run in thevirtualization environment 3400 to implement some of the features, functions, and / or benefits of some of the embodiments disclosed herein.[000137] Hardware 3404 includes processing circuitry, memory that stores software and / or instructions executable by hardware processing circuitry, and / or other hardware devices as described herein, such as a network interface, input / output interface, and so forth. Software may be executed by the processing circuitry to instantiate one or more virtualization layers 3406 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VMs 3408a and 3408b (one or more of which may be generally referred to as VMs 3408), and / or perform any of the functions, features and / or benefits described in relation with some embodiments described herein. The virtualization layer 3406 may present a virtual operating platform that appears like networking hardware to the VMs 3408.[000138] The VMs 3408 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer 3406. Different embodiments of the instance of a virtual appliance 3402 may be implemented on one or more of VMs 3408, and the implementations may be made in different ways. Virtualization of the hardware is in some contexts referred to as network function virtualization (NFV). NFV may be used to consolidate many network equipment types onto industry standard high volume server hardware, physical switches, and physical storage, which can be located in data centers, and customer premise equipment.[000139] In the context of NFV, a VM 3408 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non-virtualized machine. Each of the VMs 3408, and that part of hardware 3404 that executes that VM, be it hardware dedicated to that VM and / or hardware shared by that VM with others of the VMs, forms separate virtual network elements. Still in the context of NFV, a virtual network function is responsible for handling specific network functions that run in one or more VMs 3408 on top of the hardware 3404 and corresponds to the application 3402.[000140] Hardware 3404 may be implemented in a standalone network node with generic or specific components. Hardware 3404 may implement some functions via virtualization. Alternatively, hardware 3404 may be part of a larger cluster of hardware (e.g. such as in a data center or CPE) where many hardware nodes work together and are managed via management and orchestration 3410, which, among others, oversees lifecycle management of applications 3402. Insome embodiments, hardware 3404 is coupled to one or more radio units that each include one or more transmitters and one or more receivers that may be coupled to one or more antennas. Radio units may communicate directly with other hardware nodes via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station. In some embodiments, some signaling can be provided with the use of a control system 3412 which may alternatively be used for communication between hardware nodes and radio units.[000141] Although the computing devices described herein (e.g., UEs, network nodes) may include the illustrated combination of hardware components, other embodiments may comprise computing devices with different combinations of components. It is to be understood that these computing devices may comprise any suitable combination of hardware and / or software needed to perform the tasks, features, functions and methods disclosed herein. Determining, calculating, obtaining or similar operations described herein may be performed by processing circuitry, which may process information by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and / or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination. Moreover, while components are depicted as single boxes located within a larger box, or nested within multiple boxes, in practice, computing devices may comprise multiple different physical components that make up a single illustrated component, and functionality may be partitioned between separate components. For example, a communication interface may be configured to include any of the components described herein, and / or the functionality of the components may be partitioned between the processing circuitry and the communication interface. In another example, non-computationally intensive functions of any of such components may be implemented in software or firmware and computationally intensive functions may be implemented in hardware.[000142] In certain embodiments, some or all of the functionality described herein may be provided by processing circuitry executing instructions stored on in memory, which in certain embodiments may be a computer program product in the form of a non-transitory computer-readable storage medium. In alternative embodiments, some or all of the functionality may be provided by the processing circuitry without executing instructions stored on a separate ordiscrete device-readable storage medium, such as in a hard-wired manner. In any of those particular embodiments, whether executing instructions stored on a non-transitory computer- readable storage medium or not, the processing circuitry can be configured to perform the described functionality. The benefits provided by such functionality are not limited to the processing circuitry alone or to other components of the computing device, but are enjoyed by the computing device as a whole, and / or by end users and a wireless network generally.Example Embodiments[000143] Below are given, for illustrative purposes only, and not limiting to the uses of the current disclosure, several possible example embodiments of certain teachings of the present disclosure.Group A Embodiments:[000144] Embodiment 1: A method performed by an 0-RU for enabling SINR reporting of a single value for a PRB range containing one or more PRBs per layer for DFT-s- OFDM, the method comprising: declaring, by the 0-RU, support for one or more features via M- plane; receiving, from the 0-DU, a configuration to report one aggregated SINR value per PRB range for each layer applying DFT-s-OFDM for UL by configuring the one or more features via M-plane; calculating, by the 0-RU, the aggregated SINR for the PRB range per layer when DFT- s-OFDM is used and attaches only one aggregated SINR value in ST9 for each layer, irrespective of the configured parameter “sinr-per-prb”; and transmitting the aggregated SINR to the 0-DU.[000145] Embodiment 2: The method of embodiment 1, wherein the one or more features comprise at least one of: EFFICIENT-SINR-REPORT-FOR-DFTSOFDM; “efficient- sinr-report-for-dftsofdm-enabled = true”[000146] Embodiment 3 : The method of embodiment 1 or 2, wherein if efficient-sinr- report-for-dftsofdm-enabled is not declared, then the frequency resolution of SINR reporting of each layer is determined by the configured “sinr-per-prb”.[000147] Embodiment 4: A method performed by an O-RU for enabling SINR reporting of a single value for a PRB range containing one or more PRBs per layer for DFT-s- OFDM, the method comprising: declaring, by the O-RU, a capability of sinr-freq-resolution-for- dftsofdm-supported, which is a list of SINR frequency resolutions supported by the 0-RU;[000148] Embodiment 5: The method of embodiment 4, wherein SINK frequency resolution = 0 means that the O-RU supports reporting one aggregated SINR value per PRB range per layer, while SINR resolution = x where x >0 means that the O-RU supports reporting x SINR values per PRB per layer.[000149] Embodiment 6: The method of embodiment 4 or 5, further comprising: receiving, from an O-DU, a configuration to report one aggregated SINR value per PRB range for each layer using DFT-s-OFDM for UL transmission by configuring “sinr-for-dftsofdm-freq- resolution” = 0 via M-plane.[000150] Embodiment 7: The method of any of embodiments 4 to 6, wherein when “sinr-for-dftsofdm-freq-resolution = x” for x>0, the O-RU reports x SINR values per PRB per layer in case of DFT-s-OFDM.[000151] Embodiment 8: The method of any of embodiments 4 to 7, wherein the existing M-plane parameter “sinr-per-prb” can be used specifically for CP-OFDM case.[000152] Embodiment 9: The method of any of embodiments 4 to 8, wherein the use of different frequency resolutions in SINR reporting for each layer using CP-OFDM and DFT-s- OFDM is enabled.[000153] Embodiment 10: The method of any of embodiments 4 to 9, wherein the frequency resolution configured for DFT-s-OFDM is lower than that for CP-OFDM, i.e., fewer SINR values per PRB are reported for DFT-s-OFDM than for CP-OFDM.[000154] Embodiment 11: The method of any of embodiments 4 to 10, wherein the O-RU reports the same SINR value(s) per PRB per layer for DFT-s-OFDM where the same SINR value is the aggregated SINR value for the full PRB range per layer.[000155] Embodiment 12: The method of any of embodiments 1 to 11, wherein a scheduled usage of UL waveform in terms of CP-OFDM or DFT-s-OFDM is conveyed from O- DU to O-RU by Section Extension 24 (SE24) used with Section Type 5 (ST5), possibly together with Section Extension 10 (SE10).[000156] Embodiment 13: The method of any of embodiments 1 to 12, wherein the whole scheduled PRB range of a layer may also be divided into multiple PRB ranges.[000157] Embodiment 14: The method of embodiment 13, wherein if the O-RU is configured to report one aggregated SINR value for a PRB range per layer, then the O-RU performs at least one of: repeating the same aggregated SINR value for the entire scheduled PRBrange in all sections for the same UE layer using DFT-s-OFDM (for efficient reporting, each section should cover as many PRBs as possible); reporting one aggregated SINR value for the PRBs defined by “startPrbu” and “numPrbu” in respective section (e.g., in one case, O-DU needs to calculate one aggregated SINR value for the entire scheduled PRB range using the aggregated SINR values reported for multiple individual PRB ranges of multiple sections); or setting a special flag (e.g., sinrForPrbRange) in ST9 (if “sinrForPrbRange” = 1, only one section is used irrespective of the number of scheduled PRBs and only one aggregated SINR value is attached in this section. With this flag on, the O-DU understands that the reported SINR value is for the entire scheduled PRB range, so it will ignore the field “numPrbu” but refer to the scheduled PRB range for the layer of a UE in the scheduling information instead).[000158] Embodiment 15: A method performed by an 0-RU for enabling SINR reporting of a single value for a PRB range containing one or more PRBs for DFT-s-OFDM, the method comprising: using the existing sinr-per-prb; and reporting one or more SINR values per PRB per layer, so that DFT-s-OFDM and CP-OFDM use the same frequency resolution, wherein the 0-RU reports the same SINR value(s) per PRB per layer for DFT-s-OFDM where the same SINR value is the aggregated SINR value for the full PRB range per layer.[000159] Embodiment 16: A method performed by an 0-RU for enabling SINR reporting of a single value for a PRB range containing one or more PRBs for DFT-s-OFDM per layer, the method comprising: indicating, to an O-DU, a frequency resolution for CP-OFDM with the existing field of numSinrPerPrb, wherein ST9 adds one more field to indicate frequency resolution for DFT-s-OFDM, e.g., numSinrPerPrbForDftsofdm.[000160] Embodiment 17: A method performed by an O-DU for enabling SINR reporting of a single value for a PRB range containing one or more PRBs per layer for DFT-s- OFDM, the method comprising: receiving a declaration, from the O-RU, for support for one or more features via M-plane; transmitting, to the O-RU, a configuration to report one aggregated SINR value per PRB range for each layer applying DFT-s-OFDM for UL by configuring the one or more features via M-plane; and receiving, from the O-RU, the aggregated SINR to the O-DU, wherein the O-RU calculated the aggregated SINR for the PRB range per layer when DFT-s- OFDM is used and attached only one aggregated SINR value in ST9 for each layer, irrespective of the configured parameter “sinr-per-prb”;[000161] Embodiment 18: The method of embodiment 17, wherein the one or more features comprise at least one of: EFFICIENT-SINR-REPORT-FOR-DFTSOFDM; “efficient- sinr-report-for-dftsofdm-enabled = true”.[000162] Embodiment 19: The method of embodiment 17 or 18, wherein if efficient- sinr-report-for-dftsofdm-enabled is not declared, then the frequency resolution of SINR reporting of each layer is determined by the configured “sinr-per-prb”.[000163] Embodiment 20: A method performed by an O-DU for enabling SINR reporting of a single value for a PRB range containing one or more PRBs per layer for DFT-s- OFDM, the method comprising: receiving a declaration, from the O-RU, a capability of sinr-freq- resolution-for-dftsofdm-supported, which is a list of SINR frequency resolutions supported by the O-RU; wherein SINR frequency resolution = 0 means that the O-RU supports reporting one aggregated SINR value per PRB range per layer, while SINR resolution = x where x >0 means that the O-RU supports reporting x SNR values per PRB per layer.[000164] Embodiment 21 : The method of embodiment 20, further comprising: transmitting, by the O-DU, a configuration to report one aggregated SINR value per PRB range for each layer using DFT-s-OFDM for UL transmission by configuring “sinr-for-dftsofdm-freq- resolution” = 0 via M-plane.[000165] Embodiment 22: The method of any of embodiments 20 to 21, wherein when “sinr-for-dftsofdm-freq-resolution = x” for x>0, the O-RU reports x SINR values per PRB per layer in case of DFT-s-OFDM.[000166] Embodiment 23: The method of any of embodiments 20 to 22, wherein the existing M-plane parameter “sinr-per-prb” can be used specifically for CP-OFDM case.[000167] Embodiment 24: The method of any of embodiments 20 to 23, wherein the use of different frequency resolutions in SINR reporting for layers using CP-OFDM and DFT-s- OFDM is enabled.[000168] Embodiment 25: The method of any of embodiments 20 to 24, wherein the frequency resolution configured for DFT-s-OFDM is lower than that for CP-OFDM, i.e., fewer SINR values per PRB per layer are reported for DFT-s-OFDM than for CP-OFDM.[000169] Embodiment 26: The method of any of embodiments 17 to 25, wherein the O-RU reports the same SINR value(s) per PRB per layer for DFT-s-OFDM where the same SINR value is the aggregated SINR value for the full PRB range per layer.[000170] Embodiment 27: The method of any of embodiments 17 to 26, wherein a scheduled usage of UL waveform in terms of CP-OFDM or DFT-s-OFDM is conveyed from O- DU to O-RU by Section Extension 24 (SE24) used with Section Type 5 (ST5), possibly together with Section Extension 10 (SE10).[000171] Embodiment 28: The method of any of embodiments 17 to 27, wherein the whole scheduled PRB range for a layer may also be divided into multiple PRB ranges.[000172] Embodiment 29: The method of embodiment 28, wherein if the O-RU is configured to report one aggregated SINR value for a PRB range per layer, then the O-RU performs at least one of: repeating the same aggregated SINR value for the entire scheduled PRB range in all sections for the same UE layer using DFT-s-OFDM (for efficient reporting, each section should cover as many PRBs as possible); reporting one aggregated SINR value for the PRBs defined by “startPrbu” and “numPrbu” in respective section (in this case, 0-DU needs to calculate one aggregated SINR value for the entire scheduled PRB range using the aggregated SINR values reported for multiple individual PRB ranges of multiple sections); or setting a special flag (e.g., sinrForPrbRange) in ST9 (if “sinrForPrbRange” = 1, only one section is used irrespective of the number of scheduled PRBs and only one aggregated SINR value is attached in this section, with this flag on, the 0-DU understands that the reported SINR value is for the entire PRB range, so it will ignore the field “numPrbu” but refer to the scheduled PRB range for the layer of a UE in the scheduling information instead).[000173] Embodiment 30: The method of embodiment 29, wherein if the 0-DU configures the O-RU to report one aggregated SINR value, the 0-DU performs at least one of: calculating one aggregated SINR value for the entire scheduled PRB range using the reported aggregated SINR values received for multiple individual PRB ranges of multiple sections; or using the reported aggregated SINR value in the first section containing “sinrForPrbRange” = 1 in ST9 as the aggregated SINR for the entire scheduled PRB range.[000174] Embodiment 31 : A method performed by an 0-DU for enabling SINR reporting of a single value for a PRB range per layer for DFT-s-OFDM, the method comprising: receiving, from the O-RU, one or more SINR values per PRB per layer, so that DFT-s-OFDM and CP-OFDM use the same frequency resolution, wherein the O-RU uses the existing sinr-per-prb, wherein the O-RU reports the same SINR value(s) per PRB per layer for DFT-s-OFDM where the same SINR value is the aggregated SINR value for the full PRB range per layer.[000175] Embodiment 32: A method performed by an O-DU for enabling SINK reporting of a single value for a PRB range per layer for DFT-s-OFDM, the method comprising: receiving an indication, from the O-RU, of a frequency resolution for CP-OFDM with the existing field of numSinrPerPrb, wherein ST9 adds one more field to indicate frequency resolution for DFT-s-OFDM, e.g., numSinrPerPrbForDftsofdm.Group B Embodiments:[000176] Embodiment 33: A network node for enabling SINR reporting of a single value for a PRB range per layer for DFT-s-OFDM, the network node comprising: processing circuitry configured to perform any of the steps of any of the Group A embodiments; and power supply circuitry configured to supply power to the processing circuitry.

Claims

CLAIMSWhat is claimed is:

1. A method (1000) performed by an O-RAN Radio Unit, O-RU, for enabling signal to interference and noise ratio, SINR, reporting to an O-RAN Distributed Unit, 0-DU, the method comprising: calculating (1010) one SINR value for a plurality of physical resource block, PRBs, per layer for one or more symbols; and transmitting (1020) the one SINR value for the plurality of PRBs per layer for one or more symbols to the 0-DU.

2. The method of claim 1, further comprising receiving, from the O-DU, a configuration to report the one SINR value for a plurality of PRBs per layer for one or more symbols.

3. The method of claim 1 or 2, wherein transmitting the one SINR value for the plurality of PRBs comprises transmitting the same SINR value for different PRB ranges in the plurality of PRBs.

4. The method of any of claims 1 to 3, wherein the plurality of PRBs comprises one or more PRB ranges.

5. The method of any of claims 1 to 4, wherein each layer applies transform precoded multicarrier modulation for uplink, UL.

6. The method of any of claims 1 to 5, wherein each layer applies Discrete Fourier Transformspread-Orthogonal Frequency Division Multiplexing, DFT-s-OFDM, for uplink.

7. The method of any of claims 1 to 6, wherein: the transmitting comprises transmitting the single SINR value one or multiple times.

8. The method of any of claims 1 to 7, wherein equalization is performed by the O-RU.

9. The method of any of claims 1 to 8, further comprising declaring, to the O-DU, support for one or more capabilities and / or features via M-Plane regarding SINR reporting for DFT-s-OFDM.

10. A method (1200) performed by an 0-RAN Radio Unit, 0-RU, for enabling signal to interference and noise ratio, SINR, reporting of a single value for a physical resource block, PRB, range containing one or more PRBs per layer for Discrete Fourier Transform-spread-Orthogonal Frequency Division Multiplexing, DFT-s-OFDM, the method comprising: declaring (1210), by the 0-RU, a capability for sending one SINR value for more than one PRB for one or more symbols.

11. The method of claim 10, wherein; if SINR frequency resolution = 0, then the O-RU supports reporting one aggregated SINR value per PRB range per layer; and if SINR frequency resolution = x, where x >0, then the 0-RU supports reporting x SINR values per PRB per layer.

12. The method of claim 10 or 11, further comprising: receiving, from an 0-RAN Distributed Unit, O-DU, a configuration to report one aggregated SINR value per PRB range for each layer using DFT-s-OFDM for uplink, UL, transmission.

13. The method of any of claims 10 to 12, wherein the 0-RU reports the same SINR value per PRB per layer for DFT-s-OFDM where the same SINR value comprises an aggregated SINR value for a full PRB range per layer.

14. A method (1400) performed by an 0-RAN Radio Unit, 0-RU, for enabling signal to interference and noise ratio, SINR, reporting, the method comprising: reporting (1410), with an existing numSinrPerPrb field, a single SINR value for a physical resource block, PRB, range containing two or more PRBs for Discrete Fourier Transform-spread- Orthogonal Frequency Division Multiplexing, DFT-s-OFDM; wherein the single SINR value comprises an aggregated SINR value for a full PRB rangeper layer.

15. The method of claim 14, further comprising: indicating, to an 0-RAN Distributed Unit, 0-DU, a frequency resolution for Cyclic Prefix - Orthogonal Frequency Division Multiplexing, CP-OFDM, with an existing numSinrPerPrb field, wherein Section Type 9, ST9, adds one more field to indicate frequency resolution for DFT-s- OFDM.

16. The method of claim 14 or 15, wherein a specific value of the existing numSinrPerPrb field is used to indicate the single SINR value report for DFT-s-OFDM, while other values are used to indicate frequency resolution for Cyclic Prefix - Orthogonal Frequency Division Multiplexing, CP-OFDM17. A method (1600) performed by an 0-RAN Distributed Unit, 0-DU, for enabling signal to interference and noise ratio, SINR, reporting, the method comprising: receiving (1610), from the 0-RAN Radio Unit, 0-RU, a single SINR value for a physical resource block, PRB, range containing two or more PRBs per layer for Discrete Fourier Transform-spread-Orthogonal Frequency Division Multiplexing, DFT-s-OFDM; wherein the single SINR value comprises an aggregated SINR, wherein the 0-RU calculated the aggregated SINR for the PRB range per layer when DFT-s-OFDM is used and attached only one aggregated SINR value per section of Section Type 9, ST9, for each layer.

18. The method of claim 17, wherein the receiving is performed irrespective of a configured sinr-per-prb parameter in M-Plane.

19. The method of claim 17 or 18, further comprising: receiving a declaration, from the 0-RU, for support for one or more capabilities and / or features via M-Plane regarding SINR reporting for DFT-s-OFDM.

20. The method of any of claims 17 to 19, further comprising: transmitting, to the 0-RU, a configuration to report one aggregated SINR value per PRBrange for each layer applying DFT-s-OFDM for uplink, UL.

21. A method (1800) performed by an 0-RAN Distributed Unit, 0-DU, for enabling signal to interference and noise ratio, SINR, reporting of a single value for a physical resource block, PRB, range containing one or more PRBs per layer for Discrete Fourier Transform-spread-Orthogonal Frequency Division Multiplexing, DFT-s-OFDM, the method comprising: receiving (1810) a declaration, from the 0-RAN Radio Unit, 0-RU, a capability for sending one SINR value for more than one PRB.

22. A method (2000) performed by an O-RAN Distributed Unit, O-DU, for enabling signal to interference and noise ratio, SINR, reporting of a single value for a physical resource block, PRB, range containing two or more PRBs per layer for Discrete Fourier Transform-spread-Orthogonal Frequency Division Multiplexing, DFT-s-OFDM, the method comprising: receiving (2010), from the O-RAN Radio Unit, O-RU, a single SINR value for a PRB range containing two or more PRBs per layer, so that DFT-s-OFDM and Cyclic Prefix - Orthogonal Frequency Division Multiplexing, CP-OFDM, use the same frequency resolution; wherein the O-RU reports the single SINR value per PRB range per layer for DFT-s- OFDM wherein the single SINR value comprises an aggregated SINR value for the full PRB range per layer.

23. A method (2200) performed by an O-RAN Distributed Unit, O-DU, for enabling signal to interference and noise ratio, SINR, reporting, the method comprising: receiving (2210) an indication, from an O-RAN Radio Unit, O-RU, of a single SINR value for a physical resource block, PRB, range containing two or more PRBs per layer for Discrete Fourier Transform-spread-Orthogonal Frequency Division Multiplexing, DFT-s-OFDM.

24. The method of claim 23, further comprising: receiving, from the O-RU, a frequency resolution for Cyclic Prefix - Orthogonal Frequency Division Multiplexing, CP-OFDM, in an existing numSinrPerPrb field; wherein Section Type 9, ST9, adds one more field to indicate frequency resolution forDFT-s-OFDM.

25. The method of claim 23 or 24, wherein a specific value of the existing numSinrPerPrb field is used to indicate the single SINR value report for DFT-s-OFDM, while other values are used to indicate frequency resolution for Cyclic Prefix - Orthogonal Frequency Division Multiplexing, CP-OFDM26. A method (2400) performed by an 0-RAN Radio Unit, 0-RU, for enabling signal to interference and noise ratio, SINR, reporting to an 0-RAN Distributed Unit, 0-DU, the method comprising: calculating (2410) a single SINR value for a physical resource block, PRB, range containing two or more PRBs per layer for one or more symbols; and transmitting (2420) an indication of the single SINR value to the 0-DU.

27. A method (2600) performed by an 0-RAN Distributed Unit, 0-DU, for enabling signal to interference and noise ratio, SINR, reporting, the method comprising: receiving (2610), from the 0-RAN Radio Unit, 0-RU, an indication of a single SINR value for a physical resource block, PRB, range containing two or more PRBs per layer for Discrete Fourier Transform-spread-Orthogonal Frequency Division Multiplexing, DFT-s-OFDM; wherein the single SINR value comprises an aggregated SINR, wherein the 0-RU calculated the aggregated SINR for the PRB range per layer.

28. The method of either claim 26 or 27, wherein the indication is at least one of: implicit; explicit.

29. A method performed by an 0-RAN Radio Unit, 0-RU, for enabling signal to interference and noise ratio, SINR, reporting, the method comprising:Calculating SINR values for SINR reporting per layer, one or more layers using Discrete Fourier Transform-spread-Orthogonal Frequency Division Multiplexing, DFT-s-OFDM, and one or more layers using Cyclic Prefix - Orthogonal Frequency Division Multiplexing, CP-OFDM; and transmitting , to an 0-RAN Distributed Unit, 0-DU, the SINR values;wherein the layers using DFT-s-OFDM and the layers using CP-OFDM use different SINR frequency resolutions for SINR reporting per layer.

30. The method of claim 29, wherein the layers using DFT-s-OFDM use lower frequency resolution per layer for one or more symbols than that used by the layers using CP-OFDM.

31. The method of claim 29 or 30, wherein one aggregated SINR value is used per PRB range per layer for layers using DFT-s-OFDM.

32. A method performed by an O-RAN Distributed Unit, O-DU, for enabling signal to interference and noise ratio, SINR, reporting, the method comprising: receiving , from an O-RAN Radio Unit, O-RU, SINR values for SINR reporting per layer, one or more layers using Discrete Fourier Transform-spread-Orthogonal Frequency Division Multiplexing, DFT-s-OFDM, and one or more layers using Cyclic Prefix - Orthogonal Frequency Division Multiplexing, CP-OFDM; wherein the layers using DFT-s-OFDM and the layers using CP-OFDM use different SINR frequency resolutions for SINR reporting per layer.

33. The method of claim 32, wherein the layers using DFT-s-OFDM use lower frequency resolution per layer for one or more symbols than that used by the layers using CP-OFDM.

34. The method of claim 32 or 33, wherein one aggregated SINR value is used per PRB range per layer for layers using DFT-s-OFDM.

35. A network node (3300) for enabling signal to interference and noise ratio, SINR, reporting, the network node comprising: processing circuitry (3302) configured to perform any of the steps of any of claims 1 to 34; power supply circuitry (3308) configured to supply power to the processing circuitry.

36. A network node (3300) for enabling signal to interference and noise ratio, SINR, reporting, the network node comprising:processing circuitry (3302); and a memory (3304) storing instructions whereby the processing circuitry is operable to perform any of the steps of; calculating one SINR value for a physical resource block, PRB, range containing two or more PRBs per layer for one or more symbols; and transmitting the one SINR value to an O-RAN Distributed Unit, O-DU.

37. A network node (3300) for enabling signal to interference and noise ratio, SINR, reporting, the network node comprising: processing circuitry (3302); and a memory (3304) storing instructions whereby the processing circuitry is operable to perform any of the steps of; declaring, to an O-RAN Distributed Unit, O-DU, a capability for sending one SINR value for a physical resource block, PRB, range containing two or more PRBs per layer for one or more symbols.

38. A network node (3300) for enabling signal to interference and noise ratio, SINR, reporting, the network node comprising: processing circuitry (3302); and a memory (3304) storing instructions whereby the processing circuitry is operable to perform any of the steps of; reporting, to an O-RAN Distributed Unit, O-DU, with an existing numSinrPerPrb field, a single SINR value for a physical resource block, PRB, range containing two or more PRBs for Discrete Fourier Transform-spread-Orthogonal Frequency Division Multiplexing, DFT-s-OFDM; wherein the single SINR value comprises an aggregated SINR value for a full PRB range per layer.

39. A network node (3300) for enabling signal to interference and noise ratio, SINR, reporting, the network node comprising: processing circuitry (3302); anda memory (3304) storing instructions whereby the processing circuitry is operable to perform any of the steps of; receiving, from the 0-RAN Radio Unit, 0-RU, a single SINR value for a physical resource block, PRB, range containing two or more PRBs per layer for Discrete Fourier Transform-spread-Orthogonal Frequency Division Multiplexing, DFT-s-OFDM; wherein the single SINR value comprises an aggregated SINR, wherein the O-RU calculated the aggregated SINR for the PRB range per layer when DFT-s-OFDM is used and attached only one aggregated SINR value per section of Section Type 9, ST9, for each layer.

40. A network node (3300) for enabling signal to interference and noise ratio, SINR, reporting, the network node comprising: processing circuitry (3302); and a memory (3304) storing instructions whereby the processing circuitry is operable to perform any of the steps of; receiving a declaration, from the 0-RAN Radio Unit, 0-RU, a capability for sending one SINR value for a physical resource block, PRB, range containing two or more PRBs.

41. A network node (3300) for enabling signal to interference and noise ratio, SINR, reporting, the network node comprising: processing circuitry (3302); and a memory (3304) storing instructions whereby the processing circuitry is operable to perform any of the steps of; receiving, from the 0-RAN Radio Unit, 0-RU, one SINR value for a physical resource block, PRB, range containing two or more PRBs per layer, so that DFT-s-OFDM and Cyclic Prefix - Orthogonal Frequency Division Multiplexing, CP-OFDM, use the same frequency resolution; wherein the O-RU reports the one SINR value per PRB per layer for DFT-s-OFDM wherein the one SINR value comprises an aggregated SINR value for the full PRB range per layer.

42. A network node (3300) for enabling signal to interference and noise ratio, SINR, reporting, the network node comprising: processing circuitry (3302); and a memory (3304) storing instructions whereby the processing circuitry is operable to perform any of the steps of; receiving an indication, from an 0-RAN Radio Unit, 0-RU, of a single SINR value for a physical resource block, PRB, range containing two or more PRBs per layer for Discrete Fourier Transform-spread-Orthogonal Frequency Division Multiplexing, DFT-s- OFDM.

43. A network node (3300) for enabling signal to interference and noise ratio, SINR, reporting, the network node comprising: processing circuitry (3302); and a memory (3304) storing instructions whereby the processing circuitry is operable to perform any of the steps of; calculating one SINR value for a physical resource block, PRB, range containing two or more PRBs per layer; and transmitting an indication of the one SINR value to an 0-RAN Distributed Unit, O- DU.

44. A network node (3300) for enabling signal to interference and noise ratio, SINR, reporting, the network node comprising: processing circuitry (3302); and a memory (3304) storing instructions whereby the processing circuitry is operable to perform any of the steps of; receiving, from the 0-RAN Radio Unit, 0-RU, an indication of a single SINR value for a physical resource block, PRB, range containing two or more PRBs per layer for Discrete Fourier Transform-spread-Orthogonal Frequency Division Multiplexing, DFT-s- OFDM; wherein the single SINR value comprises an aggregated SINR, wherein the 0-RU calculated the aggregated SINR for the PRB range per layer when DFT-s-OFDM is used.

45. A network node (3300) for enabling signal to interference and noise ratio, SINR, reporting, the network node comprising: processing circuitry (3302); and a memory (3304) storing instructions whereby the processing circuitry is operable to perform any of the steps of; calculating a single SINR value for a physical resource block, PRB, range containing two or more PRBs for Discrete Fourier Transform-spread-Orthogonal Frequency Division Multiplexing, DFT-s-OFDM, and for Cyclic Prefix - Orthogonal Frequency Division Multiplexing, CP-OFDM; and transmitting (2820), to an 0-RAN Distributed Unit, 0-DU, the single SINR value; wherein the layers using DFT-s-OFDM and the layers using CP-OFDM use different SINR frequency resolutions for SINR reporting per layer.

46. A network node (3300) for enabling signal to interference and noise ratio, SINR, reporting, the network node comprising: processing circuitry (3302); and a memory (3304) storing instructions whereby the processing circuitry is operable to perform any of the steps of; receiving, from the 0-RAN Radio Unit, 0-RU, a single SINR value for a physical resource block, PRB, range containing two or more PRBs per layer for Discrete Fourier Transform-spread-Orthogonal Frequency Division Multiplexing, DFT-s-OFDM, and for Cyclic Prefix - Orthogonal Frequency Division Multiplexing, CP-OFDM; wherein the layers using DFT-s-OFDM and the layers using CP-OFDM use different SINR frequency resolutions for SINR reporting per layer.

Images