ORU forward power scaling system suitable for ORAN equipment

Abstract

The invention discloses an ORU forward transmission power scaling system suitable for ORAN equipment. The ORAN system comprises a digital unit (DU), a data processing unit (DU) and a data processing unit (DU), wherein the digital unit (DU) is responsible for IQ data generation, M plane parameter configuration and a multi-carrier power distribution strategy; the radio frequency unit (RU) comprises a processor, a memory and a radio frequency module; the processor is used for executing a power scaling algorithm and analyzing an M-plane message; the memory is used for storing the HWDB and the SWDB; and the radio frequency module realizes analog signal conditioning and digital signal conversion through DSA, PA and ADC / DAC. According to the invention, the compatibility is improved: two IQ formats of fixed RE power of the DU and ORAN standard normalization are supported, and flexible adaptation is realized through FSOffset parameters; the power control precision is as follows: the downlink power adjustment error is less than or equal to + / -0.5 dB, and the noise coefficient of an uplink is optimized to be more than 3dB; multi-carrier reliability: hardware overload is avoided through a total power verification mechanism, and a scene of at most 8 carrier aggregation is supported; and dynamic adaptability: the M plane can adjust gain correction parameters in real time to adapt to link budget changes in different environments.

Description

TECHNICAL FIELD

[0001] The application relates to the technical field of communication base stations, in particular to an ORU front-end power scaling system suitable for ORAN equipment. BACKGROUND

[0002] ORAN promotes the virtualization and interoperability of wireless access networks through open interfaces and standardized protocols, but in actual deployment, the radio unit (RU) faces the following challenges:

[0003] Power definition difference: IQ power in ORAN specifications is normalized in units of symbols (0 dBFS corresponds to the maximum root mean square power), while power is usually defined based on resource elements (REs) or time domain samples inside the RU, resulting in complex gain conversion;

[0004] Multi-carrier power management: traditional single-carrier power control methods cannot be directly applied to multi-carrier scenarios, and the lack of dynamic allocation mechanisms may lead to overloading or insufficient power of radio branches;

[0005] Analog and digital gain coordination: the coordination control of analog gain (such as DSA) and digital gain (such as DUC / DDC) in existing technologies relies on manual calibration and is difficult to adapt to real-time dynamic adjustment requirements.

[0006] Therefore, a standardized power scaling method is needed to improve the compatibility and power control accuracy of ORAN systems. SUMMARY

[0007] The purpose of the present application is to provide an ORU front-end power scaling system suitable for ORAN equipment to solve the problems raised in the background art.

[0008] To achieve the above-mentioned purpose, the present application provides the following technical scheme: an ORU front-end power scaling system suitable for ORAN equipment, comprising an ORAN system, characterized in that: the ORAN system comprises:

[0009] Digital unit (DU): responsible for IQ data generation, M-plane parameter configuration and multi-carrier power allocation strategy;

[0010] Radio frequency unit (RU): contains a processor, a memory and a radio frequency module:

[0011] Processor: executes power scaling algorithm, parses M-plane message;

[0012] Memory: stores HWDB and SWDB;

[0013] Radio frequency module: realizes analog signal conditioning and digital signal conversion through DSA, PA, ADC / DAC.

[0014] Preferably, the radio frequency unit digital domain power adjustment implementation steps are as follows:

[0015] S1: Configure the exponent offset register of the FPGA according to the FS_Offset carried by the M-Plane or the FS_Offset negotiated by the digital unit and the radio frequency unit;

[0016] S2: For each carrier of each channel, calculate the average power P of each RE of the carrier in

[0017] P in [dBFS] = 0 - 10 * log10 (N RB * 12)

[0018] S3: If the DL Gain parameter carried in the carrier parameter is used by the M-Plane, calculate the DUC Gain value required for compensation for each carrier according to the formula in S5, otherwise, calculate the DUC Gain value required for compensation for each carrier according to the formula in S4;

[0019] S4: According to the number of carriers existing on the current channel and the corresponding carrier bandwidth, calculate the DUC Gain value required for compensation for each carrier on the current channel.

[0020] Preferably, the step S4 specifically comprises:

[0021] S41: Determine the maximum configurable PowerClass on the corresponding RF branch according to the capability of the RU;

[0022] PowerClass max [dBm] = 10 * log10 (PowerClass[W] * 1000)

[0023] IfPowerClass max [W] = 40, PowerClass max [dBm] = 46;

[0024] S42: Calculate the required DL gain of each CC, which corresponds to the maximum power level on the RF branch;

[0025]

[0026] IfPowerClass max [dBm] = 46,

[0027] S43: Calculate ScaleFactor value, where OFDM output power is -25dBFS by default, and the maximum PowerClass on this RF leg;

[0028] P outOFDM = -25dBFS

[0029] S44 Calculate final DUC gain per CC on the corresponding RF leg;

[0030] Note:

[0031] Indicate DL gain in M-plane DL carrier setup message

[0032] PowerClass configured [dBm] Indicate configured PowerClass on the corresponding RF leg, see S43, P tranfer The yield of the filtering module can be found in the SWDB:

[0033] / Band_Nx / ducConvertGain

[0034] S45: Configure analog DSA via HWDB, the notch value can be looked up via carrier center frequency;

[0035] / oru / pa_db / tx:x / powerclass / dsaCaliTab

[0036] Note:

[0037]

[0038] S46: Configure analog FB DSA via HWDB, read zero reference point for different power classes;

[0039] / oru / fb_db / fb:x / powerclass / drudsaCaliTab

[0040] S47: Configure analog PA bias via HWDB

[0041]

[0042] Preferably, the step S43 specifically comprises the following steps:

[0043] S43-1: Calculate total power on the corresponding RF leg according to the DL gain of each CC in the M-plane DL carrier setup message;

[0044]

[0045] S43-2: Calculate the difference between the maximum power class supported on the corresponding RF branch and the total power calculated in S43-1;

[0046]

[0047] It should be noted that the total power of each CC on the branch should not exceed the maximum power class supported, if it exceeds, the radio software should return a carrier setup failure;

[0048] S43-3: Determine the configured power class PowerClass on the corresponding RF branch according to the total power in step S43-1 and the maximum power class supported by the RU configured [dBm];

[0049] Assume that the product supports three PowerClass:

[0050] if

[0051] PowerClass configured [dBm] = PowerClass max [dBm]

[0052] elseif

[0053] PowerClass configured [dBm] = PowerClass medium [dBm]

[0054] else

[0055] PowerClass configured [dBm] = PowerClass low [dBm].

[0056] Preferably, assuming that the DL gain of each carrier is completely controlled by the digital unit (DU), especially the power spectral density (PSD) distribution of different bandwidth carriers, the radio frequency unit (RU) adjusts the internal gain according to the DL gain configuration of the M plane to achieve the nominal power, for some Internet of Things scenarios without M plane or the DU supplier does not control the DL gain distribution of each carrier on the DU, the calculation of DL gain and PSD will be carried out on the RU, the specific steps are as follows:

[0057] The RU should calculate the target DUC gain of each CC based on the number of carriers and carrier bandwidth of the corresponding RF channel;

[0058] According to the carrier bandwidth and the carrier subcarrier spacing, the number of RBs of each carrier on the current channel is obtained

[0059] The sum of the number of RBs of all carriers on the current channel is calculated, and M represents the number of carriers on the current channel

[0060]

[0061] The proportion of the effective bandwidth of each carrier to the sum of all carrier bandwidths is calculated

[0062]

[0063] The final required compensation DUC Gain of each carrier is calculated

[0064]

[0065] Wherein, Gain trans Indicates the internal IQ processing conversion gain of the current carrier FPGA, P BO Indicates the fallback power required during debugging.

[0066] Compared with the prior art, the beneficial effects of the present application are:

[0067] Compatibility is improved: the fixed RE power of DU and the IQ format of ORAN specification normalization are supported, and flexible adaptation is realized through the FS_Offset parameter

[0068] Power control accuracy: downlink power adjustment error ≤±0.5dB, uplink noise coefficient optimization is more than 3dB

[0069] Multi-carrier reliability: avoid hardware overload through total power checking mechanism, support up to 8 carrier aggregation scenarios

[0070] Dynamic adaptability: M plane can adjust gain correction parameters in real time to adapt to link budget changes in different environments. BRIEF DESCRIPTION OF DRAWINGS

[0071] Figure 1 The figure is a schematic diagram of the gain adjustment architecture of the RU platform of the present application

[0072] Figure 2 The figure is a downlink gain definition model of the present application

[0073] Figure 3 The figure is an uplink gain definition model of the present application

[0074] Figure 4 The figure is a downlink power scaling diagram of the present application DETAILED DESCRIPTION

[0075] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0076] Please see Figures 1-4 This invention provides a technical solution: an ORU fronthaul power scaling system suitable for ORAN equipment, comprising an ORAN system, wherein the ORAN system includes:

[0077] Digital Unit (DU): Responsible for IQ data generation, M-plane parameter configuration, and multi-carrier power allocation strategy;

[0078] Radio Frequency Unit (RU): Contains a processor, memory, and radio frequency module.

[0079] Processor: Executes power scaling algorithms and parses M-plane messages;

[0080] Memory: Stores HWDB and SWDB;

[0081] RF module: Implements analog signal conditioning and digital signal conversion through DSA, PA, ADC / DAC.

[0082] In this invention, the specific implementation steps for adjusting the digital domain power of the radio frequency unit are as follows:

[0083] S1: Configure the FPGA's exponentoffset register according to the FS_Offset carried by the M-Plane or the FS_Offset negotiated between the digital unit and the RF unit;

[0084] S2: For each carrier of each channel, calculate the average power P of each RE for that carrier. in

[0085] P in [dBFS] = 0 - 10 * log10(N) RB *12)

[0086] S3: If the DL Gain parameter carried in the M-Plane carrier construction parameters is used, calculate the required DUCGain value for each carrier according to the formula in S5; otherwise, calculate the required DUC Gain value for each carrier according to the formula in S4.

[0087] S4: Based on the number of carriers and the corresponding carrier bandwidth in each channel, calculate the DUC Gain value that needs to be compensated for each carrier in the current channel.

[0088] In this invention, step S4 specifically includes:

[0089] S41: Determine the maximum configurable PowerClass on the corresponding RF branch based on the capabilities of the RU;

[0090] PowerClass max [dBm]=10*log10(PowerClass[W]*1000)

[0091] If PowerClass max [W] = 40, PowerClass max [dBm] = 46;

[0092] S42: Calculate the required DL gain for each CC, which corresponds to the maximum power level on that RF branch;

[0093]

[0094] If PowerClass max [dBm] = 46,

[0095] S43: Calculate the ScaleFactor value, where the OFDM output power is -25dBFS by default, and the maximum PowerClass on this RF branch;

[0096] P outOFDM = -25dBFS

[0097]

[0098] S44 calculates the final DUC gain for each CC on the corresponding RF branch;

[0099] Note:

[0100] Indicates DL gain in M-plane DL carrier setting message

[0101] PowerClass configured [dBm] indicates the PowerClass configuration on the corresponding RF branch. See S43, P tranfer The benefits generated by the filtering module can be found in SWDB:

[0102] / Band_Nx / ducConvertGain

[0103] S45: By configuring analog DSA via HWDB, the gear value can be found through the carrier center frequency;

[0104] / oru / pa_db / tx:x / powerclass / dsaCaliTab

[0105] Note:

[0106]

[0107] S46: Configure the simulated FB DSA via HWDB to read the zero reference point for different power levels;

[0108] / oru / fb_db / fb:x / powerclass / drudsaCaliTab

[0109] S47: Configure simulated PA bias via HWDB

[0110]

[0111] In this invention, step S43 specifically includes the following steps:

[0112] S43-1: Calculate the total power on the corresponding RF branch based on the DL gain of each CC in the M-plane DL carrier setting message;

[0113]

[0114] S43-2: Calculate the difference between the maximum power level supported on the corresponding RF branch and the total power calculated in S43-1;

[0115]

[0116] It should be noted that the total power of each CC on the branch must not exceed the maximum supported power level; if it does, the radio software should return a carrier setting failure.

[0117] S43-3: Based on the total power and the maximum power level supported by the RU in step S43-1, determine the configuration power class (PowerClass) on the corresponding RF branch. configured [dBm];

[0118] Assume this product supports three PowerClasses:

[0119] if

[0120] PowerClass configured [dBm] = PowerClass max [dBm]

[0121] elseif

[0122] PowerClass configured [dBm] = PowerClass medium [dBm]

[0123] else

[0124] PowerClass configured [dBm] = PowerClass low [dBm].

[0125] In this invention, it is assumed that the DL gain of each carrier is completely controlled by the digital unit (DU), especially the power spectral density (PSD) distribution of carriers with different bandwidths. The radio frequency unit (RU) adjusts its internal gain according to the DL gain configured on the M-plane to achieve the nominal power. For some IoT scenarios where there is no M-plane or the DU supplier does not control the DL gain allocation of each carrier on the DU, the calculation of DL gain and PSD will be performed on the RU. The specific steps are as follows:

[0126] The RU should calculate the target DUC gain for each CC based on the number of carriers and the carrier bandwidth of the corresponding RF channel;

[0127] Based on the carrier bandwidth and carrier-subcarrier spacing, obtain the number of RBs for each carrier in the current channel.

[0128] Calculate the sum of the number of RBs for all carriers on the current channel, where M represents the number of carriers on the current channel;

[0129]

[0130] Calculate the proportion of the effective bandwidth of each carrier to the sum of the bandwidths of all carriers;

[0131]

[0132] Calculate the DUC Gain that is ultimately required to compensate for each carrier;

[0133]

[0134] Where Gaintrans represents the IQ processing conversion gain of the current carrier FPGA, and PBO represents the back-off power required during debugging.

[0135] Uplink power scaling example:

[0136] PUSCH Digital Domain Power Adjustment Implementation

[0137] Uplink power scaling for each carrier is achieved through the following steps:

[0138] Step 1: Based on the uplink gain adjustment function, adjust the gains of RFSoc RX DSA and ULVCA through radio software (SW) to keep the uplink gain from the RF port to the ULVCA gain module constant. The target gain is defined in the hardware database ( / oru / rx_db / rx:x / analogGainTarget).

[0139] Step 2: Based on the ORAN specification and FPGA implementation, obtain the internal configuration UL gain for each carrier;

[0140] Step 3: Use analogGainTarget to calculate the gain difference of the internally configured UL gain [dB].

[0141] digitGainTarget[dB]=internalConfigedULGain[dB]-analogGainTarget[dB]…(F-1)

[0142] The analogGainTarget can be found in HWDB: / oru / rx_db / rxx / analogGainTarget

[0143] adc2ExternalGain[dB]=digitGainTargget[dB]+adcConventGain[dB]…(F-2)

[0144] Note:

[0145] adcConventGain can be found in SWDB: / Band_Nx / ddcConvertGain

[0146] digitGain2ExternalGain[dB]=adc2ExternalGain[dB]+ddcCCGain[dB])+P tranfer [dB]

[0147] Note:

[0148] P tranfer The gain generated by the filtering module can be found in SWDB: / Band_Nx / ddcConvertGain

[0149] Therefore, we can obtain the CC gain value:

[0150]

[0151] Note:

[0152] P ofdm =ABS(-3.01-10*LOG10(N) re / N fft ))

[0153] Mathematical calculation values ​​can be positive or negative, indicating the direction of decay. Please consider the consistency of the API direction when configuring the software.

[0154] The gain difference should then be compensated after the ULVCA gain module (DDC channel filter coefficients or DDC gain), depending on the FPGA implementation; the radio software does not need to consider this.

[0155] Steps 2 and 3 above are implemented in the FPGA; the radio software only needs to execute step 1 to perform UL power scaling.

[0156] PRACH power scaling is achieved through PRACH channel filter coefficients or PRACH gain in the PRACH module, depending on the FPGA implementation; the radio software does not need to concern itself with it.

[0157] For example:

[0158] internalConfigedULGain=30.64613019[db]

[0159] analogGainTarget = 40 [dB]

[0160] digitGainTarget=internalConfigedULGain-analogGainTarget=-9.35[dB]

[0161] This means we need to attenuate by 9.35 dB in the digital domain;

[0162] There is a natural attenuation of 6dB during ADC conversion, so the attenuation can be adjusted to 3.35dB;

[0163] Through OFDM technology, we have almost eliminated We obtain the integer value of the scale factor through mathematical formulas, and indirectly calculate the actual attenuation value.

[0164] During the DDC process, there is a constant conversion gain, which is measured and updated to the SWDB;

[0165] Using the formula and the above definitions, we can finally calculate the scaling factor and CC gain value that the software needs to be configured with.

[0166] PRACH digital domain power adjustment implementation;

[0167] According to the ORAN protocol, the definition of UL Gain does not distinguish between PUSCH / PUCCH and PRACH. Therefore, the uplink digital domain power scaling adjustment of PRACH is the same as the uplink steps. The PRACH gain reservation provided in the FPGA PRACH module is configured to 0dB by default.

[0168] This invention, ORAN (Open Radio Access Network), as a next-generation wireless communication architecture, achieves interoperability between devices from multiple vendors through open interfaces and standardized protocols. In an ORAN system, the Radio Unit (RU) needs to dynamically adjust uplink and downlink power based on the configuration of the Digital Unit (DU) to meet the requirements of different carrier bandwidths, modulation schemes, and deployment scenarios. However, existing technologies suffer from the following problems:

[0169] The differences between the ORAN specification and the internal power definition of the RU lead to complex gain conversion.

[0170] In multi-carrier scenarios, the lack of a flexible dynamic adjustment mechanism for power allocation may lead to power overload or insufficient power.

[0171] The imperfect collaborative control mechanism of analog and digital gain in uplink and downlink affects signal quality and system stability.

[0172] This invention provides an uplink and downlink power scaling method and apparatus for an ORAN-based wireless communication system. Through a standardized gain conversion algorithm and a dynamic power allocation mechanism, it achieves coordinated power control between the RU and DU, thereby improving signal power accuracy and system stability.

[0173] Core steps of the downlink power scaling method:

[0174] According to the definition of ORA, the formula for calculating DL Gain for each carrier is as follows:

[0175] DLgain[dB]=RF output level[dBm]-IQ input level[dBFS]

[0176] For example, on a channel, if the desired downlink carrier output power is 46dBm (40W), then the DL gain carried by DU in the carrier establishment message should be:

[0177] DL gain[dB]=RF output level[dBm]-IQ input level[dBFS]=46[dBm]-0[dBFS]=46

[0178] The Oran protocol defines the IQ input level [dBFS] as follows:

[0179] 'IQ inputlevel[dBFS]'and'IQ outputlevel[dBFS]'are10·log10(average(I 2 +Q 2 ))normalized such that 0dBFS is the maximum nominal(rms)power levelwhich can be achieved with a constant IQ signal with arbitrary phase(ie,forfrequency-domain IQ signal for one sub-carrier,constantover time).

[0180] The configuration parameters for M-Plane downlink carrier establishment are listed below:

[0181]

[0182] Assuming the FS_Offset configured via M-Plane is 16, meaning the IQ data is 16 bits, then FullScale = 2^30.

[0183] According to the ORAN protocol definition, the maximum normalized power of each symbol of each carrier on each RU channel of the DU is 0 dBFS. Since the number of RBs is different for different carrier bandwidths, the average power of REs for carriers with different bandwidths is also different.

[0184] According to LTE and NR protocols, the maximum number of redundancies (RBs) is 273 (corresponding to 100MHz@30kHz), and the minimum number of RBs is 6 (corresponding to 1.4MHz LTE). Therefore, the average power range of each redundancy resonator (RE) in the frequency domain is:

[0185] [0dBFs-10*log10(273*12),0dBFs-10*log10(6*12)]=[-18.5733dBFs,-35.1534dBFs]

[0186] Assuming the product supports a maximum bandwidth of 50MHz and a minimum bandwidth of 5MHz, the average power range of each RE in the frequency domain is:

[0187] [0dBFs-10*log10(270*12),0dBFs-10*log10(11*12)]=[-21.2057dBFs,-35.1055dBFs]

[0188] ·Table 5.3.2-1:Transmission bandwidth configuration N RB for FR1

[0189]

[0190] Table 5.6-1 Transmission bandwidth configuration N RB in E-UTRA channel bandwidths

[0191]

[0192] Inside the FPGA, IQ data is transmitted to the DUC module via the adapter. The IQ data undergoes truncation and time-frequency conversion, which causes changes in gain. To ensure that the data truncation and time-frequency conversion operations do not affect the original average IQ power, a certain power compensation is required in the DUC module. The specific gain compensation values ​​are shown in the table below:

[0193] Assuming the product supports all carrier types and carrier bandwidths, the corresponding FPGA internal IQ data processing conversion gain...

[0194] During product debugging, it is necessary to manually adjust the power in the digital domain, either by backing down or boosting the digital domain power. BO The recommended range is [-12dB, 0dB].

[0195] DUC Gain Dynamic Range Analysis

[0196] The required carrier bandwidth and average power range per RE are:

[0197] [-21.2057dBFs, -35.1055dBFs]

[0198] The FPGA's internal IQ data processing conversion gain range is: [0.39dB, 5.51dB]

[0199] The required digital domain power adjustment range for debugging is: [-12dB, 0dB]

[0200] To adjust the digital domain average power to -15 dBFs of the RU internal calibration, the maximum adjustment range required for DUC Gain is:

[0201] -15dBFs-(-35.1055dBFs)+5.51dB=25.6155dB

[0202] The core steps of the uplink power scaling method of this invention are as follows:

[0203] According to the definition of ORA, the formula for calculating UL Gain for each carrier is as follows:

[0204] UL gain[dB]=IQ output level[dBFS]-RF input level[dBm]

[0205]

[0206] In the ORAN protocol, the minimum power for each uplink RE is defined as -152dBm.

[0207] The-152dBm is considered as the smallestlevel that can be measured by a narrow subcarrier of 1.25kHz (ie, CW tone) for a system with 3dB ofequivalentnoise figure and without being impacted by the interface noise.

[0208] On the RU, the required UL Gain definition is as follows:

[0209] Configured UL gain[dB]=Interface resolution[dBFs]–(-152dBm)+gain_correction[dB]

[0210] in,

[0211] Interface resolution [dBFs] depends on the compression method and the number of compressed bits. The formula for calculating interface resolution [dBFs] is as follows:

[0212] Interface resolution[dBFs]=-20*log10[2^(mantissa-1)*2^(2^exponent-1)]

[0213] For BFP9 compression, mantissa=9, exponent=4, therefore,

[0214] Interface resolution[dBFS]=-20*log10[2^(9-1)*2^(2^4-1)]=-138.4738dBFs

[0215] The gain_correction[dB] is determined by the parameter carried by the M-Plane when establishing the carrier. If this parameter is not configured by the M-Plane, the RU considers gain_correction = 0dB.

[0216] The configuration parameters for M-Plane uplink carrier establishment are listed below:

[0217]

[0218] If the default gain correction value is set to 0dB, then,

[0219] Configured UL gain[dB]=-90.3090[dBFs]–(-152dBm)+0[dB]=61.6910

[0220] It should be noted that the configured UL gain [dB] is based on the RE level of each CC and is calculated based on the 16-bit IQ.

[0221] Taking a 100MHz@30kHz NR carrier as an example:

[0222] In a 100MHz, 30kHz NR carrier, there are a total of 3276 resource elements (273RBs multiplied by 12REs). Therefore, the digital IQ power of each symbol in the frequency domain is:

[0223] -90.3090[dBFs]+10*log10(3276)=-55.1556dBFs

[0224] In the RU, the IQ bit width is fixed at 16, therefore the total digital IQ power of each symbol in the frequency domain is:

[0225] -55.1556dBFs+10*log10(2^30 / 2^30)=-55.1556dBFs

[0226] The formula for calculating the time-domain average IQ power (corresponding to the time-domain power meter in the RU) is as follows:

[0227] -55.1556dBFs-10*log10(4096)+10*log10(4096 / 3276)=-90.3090dBFs

[0228] The RF input power is equal to -152dBm + 10*log10(3276) = -116.8466dBm. Typically, the IQ power is indicated by a digital power meter in the RU, therefore the UL gain inside the RU can be expressed as:

[0229] Internal Configured UL gain[dB]=-90.3090dBFs–(-116.8466dBm)=26.5376dB

[0230] The internally configured UL gain represents the RU UL gain, which comes from the RF port to the fronthaul.

[0231] Different bandwidths may have different RE numbers and IFFT points, therefore, the internally configured UL gain [dB] may be different for different carriers.

[0232] The contents not described in detail in this specification are prior art known to those skilled in the art. Although embodiments of the present invention have been shown and described, it will be understood by those skilled in the art that various changes, modifications, substitutions and variations can be made to these embodiments without departing from the principles and spirit of the present invention. The scope of the present invention is defined by the appended claims and their equivalents.

Claims

1. An ORU fronthaul power scaling system for ORAN equipment, comprising an ORAN system, characterized in that: The ORAN system includes: Digital Unit (DU): Responsible for IQ data generation, M-plane parameter configuration, and multi-carrier power allocation strategy; Radio Frequency Unit (RU): Contains a processor, memory, and radio frequency module. Processor: Executes power scaling algorithms and parses M-plane messages; Memory: Stores HWDB and SWDB; RF module: Implements analog signal conditioning and digital signal conversion through DSA, PA, ADC / DAC.

2. The ORU fronthaul power scaling system for ORAN equipment according to claim 1, characterized in that: The specific implementation steps for adjusting the digital domain power of the radio frequency unit are as follows: S1: Configure the FPGA's exponent offset register according to the FS_Offset carried by the M-Plane or the FS_Offset negotiated between the digital unit and the radio frequency unit; S2: For each carrier of each channel, calculate the average power P of each RE for that carrier. in P in [dBFS]=0-10*log10(N RB *12) S3: If the DL Gain parameter carried in the M-Plane carrier construction parameters is used, calculate the required DUC Gain value for each carrier according to the formula in S5; otherwise, calculate the required DUC Gain value for each carrier according to the formula in S4. S4: Based on the number of carriers and the corresponding carrier bandwidth in each channel, calculate the DUC Gain value that needs to be compensated for each carrier in the current channel.

3. The ORU fronthaul power scaling system for ORAN equipment according to claim 2, characterized in that: Step S4 specifically includes: S41: Determine the maximum configurable PowerClass on the corresponding RF branch based on the capabilities of the RU; PowerClass max [dBm]=10*log10(PowerClass[W]*1000) IfPowerClass max [W]=40,PowerClass max [dBm]=46; S42: Calculate the required DL gain for each CC, which corresponds to the maximum power level on that RF branch; If S43: Calculate the ScaleFactor value, where the OFDM output power is -25dBFS by default, and the maximum PowerClass on this RF branch; P outOFDM =-25dBFS S44 calculates the final DUC gain for each CC on the corresponding RF branch; Note: Indicates DL gain in M-plane DL carrier setting message PowerClass configured [dBm] indicates the PowerClass configuration on the corresponding RF branch. See S43, P tranfer The benefits generated by the filtering module can be found in SWDB: / Band_Nx / ducConvertGain S45: Simulated DSA can be configured via HWDB, allowing the gear value to be found through the carrier center frequency; / oru / pa_db / tx:x / powerclass / dsaCaliTab Note: S46: Configure the simulated FB DSA via HWDB to read the zero reference point for different power levels; / oru / fb_db / fb:x / powerclass / drudsaCaliTab S47: Configure simulated PA bias via HWDB MPA bias: / oru / pa_db / GMpa:xx / powerclass / offset DPA bias: / oru / pa_db / GDpa:xx / powerclass / offset.

4. The ORU fronthaul power scaling system for ORAN equipment according to claim 3, characterized in that: Step S43 specifically includes the following steps: S43-1: Calculate the total power on the corresponding RF branch based on the DL gain of each CC in the M-plane DL carrier setting message; S43-2: Calculate the difference between the maximum power level supported on the corresponding RF branch and the total power calculated in S43-1; It should be noted that the total power of each CC on the branch must not exceed the maximum supported power level; if it does, the radio software should return a carrier setting failure. S43-3: Based on the total power and the maximum power level supported by the RU in step S43-1, determine the configuration power class (PowerClass) on the corresponding RF branch. configured [dBm]; Assume this product supports three PowerClasses: if PowerClass configured [dBm]=PowerClass max [dBm] elseif PowerClass configured [dBm]=PowerClass medium [dBm] else PowerClass configured [dBm]=PowerClass low [dBm]。 5. The ORU fronthaul power scaling system for ORAN equipment according to claim 1, characterized in that: Assuming the DL gain of each carrier is fully controlled by the digital unit (DU), especially considering the power spectral density (PSD) distribution of carriers with different bandwidths, the radio frequency unit (RU) adjusts its internal gain according to the DL gain configured on the M-plane to achieve the nominal power. For some IoT scenarios where there is no M-plane or the DU supplier does not control the DL gain allocation for each carrier on the DU, the calculation of DL gain and PSD will be performed on the RU, with the specific steps as follows: The RU should calculate the target DUC gain for each CC based on the number of carriers and the carrier bandwidth of the corresponding RF channel; Based on the carrier bandwidth and carrier-subcarrier spacing, obtain the number of RBs for each carrier in the current channel. Calculate the sum of the number of RBs for all carriers on the current channel, where M represents the number of carriers on the current channel; Calculate the proportion of the effective bandwidth of each carrier to the sum of the bandwidths of all carriers; Calculate the DUC Gain that is ultimately required to compensate for each carrier; Among them, Gain trans P represents the IQ conversion gain of the current carrier within the FPGA's internal I / Q processing. BO This indicates the backoff power required during the commissioning process.

Images