Inventors: Tommy Ivarsson, Sewvanda Don, and John Bradley Deforge

RELATED APPLICATION

[0001] This application claims priority to U. S. Non- Provisional Application Number 17/660,360, filed April 22, 2022, and entitled “MODIFYING RADIO UNIT OPERATIONAL PARAMETERS”, the entirety of which priority application is hereby incorporated by reference herein.

BACKGROUND

[0002] A radio can comprise a receiver and a transmitter that are used to receive and transmit, respectively, data.

SUMMARY

[0003] The following presents a simplified summary of the disclosed subject matter in order to provide a basic understanding of some of the various embodiments. This summary is not an extensive overview of the various embodiments. It is intended neither to identify key or critical elements of the various embodiments nor to delineate the scope of the various embodiments. Its sole purpose is to present some concepts of the disclosure in a streamlined form as a prelude to the more detailed description that is presented later.

[0004] An example system can operate as follows. The system can comprise a distributed unit that is configured to process traffic and traffic load scheduling to produce processed traffic, and to communicate the processed traffic and traffic load scheduling to the radio unit. The system can further comprise a radio unit that is configured to modify operational parameters of the radio unit based on the processed traffic and traffic load scheduling received from the distributed unit.

[0005] An example method can comprise processing, by a system comprising a processor, traffic and traffic load scheduling at a distributed unit produce processed traffic. The method can further comprise modifying, by the system, operational parameters of a radio unit based on the processed traffic and traffic load scheduling. [0006] An example apparatus can comprise a processing component that is configured to process traffic and traffic load scheduling at a distributed unit of a radio system to produce processed traffic. The apparatus can further comprise a modifying component that is configured to modify operational parameters of a radio unit of the radio system based on the processed traffic and traffic load scheduling.

BRIEF DESCRIPTION OF THE DRAWINGS

[0007] Numerous embodiments, objects, and advantages of the present embodiments will be apparent upon consideration of the following detailed description, taken in conjunction with the accompanying drawings, in which like reference characters refer to like parts throughout, and in which:

[0008] FIG. 1A, FIG. IB, and FIG. 1C illustrate an example system architecture of a down link chain of a radio system, and that can facilitate modifying radio unit operational parameters, in accordance with an embodiment of this disclosure;

[0009] FIG. 2A and FIG. 2B illustrate an example system architecture for an up link chain of a radio system, and that can facilitate modifying radio unit operational parameters;

[0010] FIG. 3 A, FIG. 3B, FIG. 3C, and FIG. 3D illustrate an example system architecture for a radio system, and that can facilitate modifying radio unit operational parameters, in accordance with an embodiment of this disclosure;

[0011] FIG. 4 illustrates an example system architecture that can facilitate modifying radio unit operational parameters, in accordance with an embodiment of this disclosure;

[0012] FIG. 5 illustrates another example system architecture that can facilitate modifying radio unit operational parameters, in accordance with an embodiment of this disclosure;

[0013] FIG. 6 illustrates another example system architecture that can facilitate modifying radio unit operational parameters, in accordance with an embodiment of this disclosure;

[0014] FIG. 7 illustrates an example process flow that can facilitate modifying radio unit operational parameters, in accordance with an embodiment of this disclosure;

[0015] FIG. 8 illustrates another example process flow that can facilitate modifying radio unit operational parameters, in accordance with an embodiment of this disclosure;

[0016] FIG. 9 illustrates another example process flow that can facilitate modifying radio unit operational parameters, in accordance with an embodiment of this disclosure; [0017] FIG. 10 illustrates another example process flow that can facilitate modifying radio unit operational parameters, in accordance with an embodiment of this disclosure;

[0018] FIG. 11 illustrates another example process flow that can facilitate modifying radio unit operational parameters, in accordance with an embodiment of this disclosure;

[0019] FIG. 12 illustrates another example process flow that can facilitate modifying radio unit operational parameters, in accordance with an embodiment of this disclosure;

[0020] FIG. 13 illustrates another example process flow that can facilitate modifying radio unit operational parameters, in accordance with an embodiment of this disclosure;

[0021] FIG. 14 illustrates another example process flow that can facilitate modifying radio unit operational parameters, in accordance with an embodiment of this disclosure;

[0022] FIG. 15 illustrates another example process flow that can facilitate modifying radio unit operational parameters, in accordance with an embodiment of this disclosure;

[0023] FIG. 16 illustrates another example process flow that can facilitate modifying radio unit operational parameters, in accordance with an embodiment of this disclosure.

DETAILED DESCRIPTION

OVERVIEW

[0024] In modem wireless communications deployments, aspects and impacts of radio development engineering and system design tradeoffs can have far-reaching implications into customer capital expenditures, operating expenditures and overall completeness of a vendor’s radio offerings. These engineering and systems design tradeoffs can result in what can be generally characterized as overall radio size, weight, thermal dissipation, reliability, complexity, and cost.

[0025] In some radio systems, amplifiers can consume greater than 50% of the power consumed by the radio system, and produce approximately 50% of the heat to be dissipated within the physical dimensions of the radio. In some examples, a key driver of radio design can therefore be amplifier design and an ability to derive efficiency improvements.

[0026] In some examples according to the present techniques, a distributed unit of a radio system can communicate with a radio unit of the radio system regarding traffic and traffic load scheduling to improve performance of the radio unit. This improved performance of the radio unit can benefit a user of the radio system.

[0027] The present techniques can be implemented to modify radio unit operational parameters based on distributed unit messaging relating to a dynamicity of traffic. Actuators in a radio unit can be accessible for modification through techniques such as direct access by distributed unit messaging, deterministic approaches, and/or prescriptive approaches to affect operational efficiency performance in a timely manner.

[0028] In some examples, operational efficiency can be improved through a priori knowledge of traffic dynamics and distributed unit messaging with direct access to actuators on a radio unit.

[0029] In some examples, a radio unit operates to modify actuator values based on messaging received from a distributed unit, thus modifying parameters based on a dynamicity of traffic.

[0030] Traffic dynamics or traffic loading can be communicated by a distributed unit to a radio unit a priori for a purpose of improving radio system efficiency.

[0031] In some examples, operational parameter modifications can be timed and synchronized with a dynamic load of signal data received by a radio unit.

[0032] The present techniques can be implemented to improve radio unit efficiency through modifying configurable operational parameters as a result of messaging from a distributed unit. Reconfiguration of operational parameters can be controlled by actuators, where control of the actuators can be facilitated by direct messaging from a distributed unit, deterministic, or prescriptive approaches.

[0033] In some examples, the present techniques can provide coverage for all antenna branches in a radio system. In some examples, actuators in a radio unit are accessible for modification through deterministic or prescriptive approaches to affect operational efficiency performance in a timely manner.

[0034] In some cases, a radio unit can perform a change to a power amplifier (PA) bias via actuators to control PA source voltage (Vdd) and gate biases for a purpose of improving (e.g., lessening) power consumption of a radio.

[0035] A radio unit and a distributed unit can communicate for a purpose of radio unit parameter modification via c-plane messaging. In some examples, signal timing and synchronization with actuator control can be employed to ensure proper alignment of signals with actuator control and parameter modification.

[0036] In some examples, a radio unit’s actuators can be directly modified by interpretation of c-plane messaging from a distributed unit. In some examples, a radio unit’s actuators can be modified by a radio unit through deterministic or prescriptive approaches within a domain of a radio unit following c-plane messaging from a distributed unit. [0037] In some examples, a radio unit can communicate to a distributed unit that, due to system performance measurements, the radio unit needs the distributed to rapidly lessen traffic load. The distributed unit can then message the radio unit regarding having lessened the loading.

[0038] The present techniques can be implemented to facilitate distributed unit and radio unit interaction. A distributed unit scheduler can have knowledge of traffic levels in advance of transmission. The distributed unit can communicate with the radio unit regarding forthcoming traffic a priori. The radio unit can communicate with the distributed unit for a purpose of an expressed need for traffic load reduction or traffic dynamicity reduction.

[0039] The distributed unit can comprise a scheduler with configurable thresholds based on forthcoming traffic load utilization and modeling. A distributed unit can have direct access to radio unit actuators, and an ability to reconfigure key performance parameters via messages on a radio unit’s c-plane to optimize for upcoming traffic load.

[0040] In some examples, a radio unit can reconfigure key performance parameters via actuators to optimize for upcoming traffic load resulting from a priori traffic information messaging received from a distributed unit.

[0041] In some examples where a distributed unit autonomously withholds scheduling of traffic, either partially or wholly, to an advantage of lessening radio unit power consumption by lessening or modification of a duty cycle of a traffic load, a radio unit can respond in kind with a commensurate lessening of power amplifier bias parameters. In some examples, a priori knowledge of traffic load can be leveraged to modify radio unit parameters and realize energy savings in a user’ s network deployment.

EXAMPLES / ARCHITECTURES

[0042] In an example embodiment, a system comprises a distributed unit that is configured to process traffic and traffic load scheduling to produce processed traffic, and to communicate the processed traffic and traffic load scheduling to the radio unit. The system can further comprise a radio unit that is configured to modify operational parameters of the radio unit based on the processed traffic and traffic load scheduling received from the distributed unit.

[0043] The system can further comprise at least one actuator of the radio unit that is configured to engage to modify the operational parameters. The modifying of the operational parameters by the actuator can be timed and synchronized with a dynamic load of signal data received by the radio unit.

[0044] The modifying of the operational parameters of the radio unit can improve (increase) an operational efficiency of the radio unit, e.g., according to a defined efficiency metric or criterion.

[0045] In another example embodiment, a method comprises processing, by a system comprising a processor, traffic and traffic load scheduling at a distributed unit to produce processed traffic. The method can further comprise modifying, by the system, operational parameters of a radio unit based on the processed traffic and traffic load scheduling.

[0046] The modifying of the operational parameters of the radio unit can comprise changing, by the system, a power amplifier bias of the radio unit with an actuator. The modifying of the operational parameters of the radio unit can comprise changing, by the system, a supply voltage of the radio unit with an actuator.

[0047] The modifying of the operational parameters of the radio unit can comprise changing, by the system, a gate bias of the radio unit with an actuator.

[0048] The modifying of the operational parameters of the radio unit can comprise receiving, by the system and at the radio unit, messaging from the distributed unit, and modifying, by the system, the operational parameters based on the messaging.

[0049] The modifying of the operational parameters based on the messaging can comprise deterministically modifying, by the system, the operational parameters based on the messaging. The deterministically modifying of the operational parameters based on the messaging can comprise modifying, by the system, the operational parameters via use of a feedback mechanism in orchestration with distributed unit messaging.

[0050] The modifying of the operational parameters based on the messaging can comprise passing, by the system, the messaging to a block that is configured to determine a response based on an input that conditions a deterministic outcome to at least a predetermined threshold amount.

[0051] The modifying of the parameters of the radio unit can comprise modifying, by the system, the operational parameters based on information that is determined at the radio unit, independently of messaging from the distributed unit.

[0052] The modifying of the operational parameters of the radio unit can comprise receiving, by the system and at the radio unit, messaging from the distributed unit, determining, by the system and internal to the radio unit, information, and modifying, by the system, the operational parameters based on a combination of the messaging and the information.

[0053] In another example embodiment, an apparatus comprises a processing component that is configured to process traffic and traffic load scheduling at a distributed unit of a radio system to produce processed traffic. The apparatus can further comprise a modifying component that is configured to modify operational parameters of a radio unit of the radio system based on the processed traffic and traffic load scheduling.

[0054] The modifying component can be configured to modify the operational parameters by engaging an actuator of the radio unit, and the modifying component can be configured to modify signal timing and synchronization associated with an actuator component relative to the radio unit.

[0055] The modifying component can be configured to modify the operational parameters by engaging an actuator of the radio unit, and the modifying component can be configured to modify performance of the radio unit to facilitate increasing a traffic load, to facilitate lessening the traffic load, based on determining that the traffic load has decreased, to facilitate lowering a thermal stress, or based on a modulation coding scheme level.

[0056] The radio unit can be configured to communicate to the distributed unit a request to lessen the traffic load, and the distributed unit can be configured to communicate to the radio unit an indication that the traffic load has been lessened.

[0057] The distributed unit can be configured to withhold scheduling of the traffic independent of the radio unit, the withholding of the scheduling of the traffic can comprise modifying a duty cycle of the traffic, and the withholding of the scheduling of the traffic reduces a power consumption of the radio unit.

[0058] The radio unit can be configured to reduce a power amplifier bias parameter in response to the distributed unit withholding scheduling of the traffic.

[0059] FIG. 1A, FIG. IB, and FIG. 1C illustrate an example system architecture 100 of a down link chain of a radio system, and that can facilitate modifying radio unit operational parameters, in accordance with an embodiment of this disclosure.

[0060] System architecture 100 can function as a down link signal path of a radio. As depicted, system architecture 100 comprises custom signal data memory, generation, masking, and buffer 102 (which can comprise a combination of some or all of a look up table, a pseudo-random look up table generator, a generator, a memory, an OR gate to combine data sources, masking, and a buffer), time alignment 116, custom symbol resource bands/resource elements (RBs/REs) 118, inverse Fast Fourier Transform (iFFT) 120 (which can also perform A gain, time alignment, and optional cyclic prefix (CP) insertion), RB/RE 122, iFFT/CP 124, digital front end (DFE) block 1 126, DFE block 2 128, crest factor reduction (CFR) 130, digital pre-distortion (DPD) 132, delta-time-phase (AT0) 134, adaptation and correlation 136, feedback receiver analog-to-digital converter (FBRx ADC) 138, transmitter digital to- analog converter (Tx ADC) 140, capture 142, power amplifier 144, signal coupler 146, tap point 148A, tap point 148B, tap point 148C, tap point 148D, tap point 148E, tap point 148F (which can be accessed to capture a FBRx_Signal_IN), tap point 148G (which can be accessed to capture a CFR_OUT_Signal), tap point select 150, select 152, signal data 154, AND/OR 156, hardware accelerated signal data pre-conditioning and memory 158, optional FFT and CP removal 162, analysis and fault detection 164, radio optimization control and actuation 166, select 168, storage 170, U-plane 172, and C-plane, M-plane, and S-plane 174. [0061] In different examples, different blocks of system architecture 100 can be implemented and/or used. For example, optional FFT and CP removal 162 can be selectively implemented and/or used to provide a time domain full signal (no FFT, and no CP removal); to provide time domain data only (no FFT, with CP removal); to provide frequency domain of a whole signal (with FFT, no CP removal); and/or frequency domain data only (with FFT, with CP removal).

[0062] In system architecture 100, each tap point (e.g., tap point 148 A) can serve as a multiplexer where one copy of the signal is sent through the signal chain as it would be if there were no tap point, and another copy of the signal is sent to be selectively captured. Time alignment 116 can align a signal at each tap point with a system time of the down link chain.

[0063] A copy of a signal that is split at a tap point can be sent to capture 142, where the signal can be captured. As depicted, each tap point is in the time domain of the down link chain, and there can be examples where a tap point is positioned in a frequency domain portion of the down link chain.

[0064] Once captured, the captured signal can proceed through hardware accelerated signal data pre-conditioning and memory 158. Hardware accelerated signal data preconditioning and memory 158 can perform operations such as optional FFT and optional CP removal, analysis, and storage. A result of this analysis can be used to cause actuators to change operational parameters of the radio system. [0065] FIG. 2A and FIG. 2B illustrate an example system architecture 200 for an up link chain of a radio system, and that can facilitate modifying radio unit operational parameters. In some examples, system architecture 200 can be implemented in conjunction with system architecture 100, where system architecture 200 implements an up link chain of a radio system, and system architecture 100 implements a corresponding down link chain.

[0066] As depicted, system architecture 200 comprises custom symbol RBs/REs 202; time alignment 204; FFT/CP 206; DFE block N+l 208; DFE block N 210; DFE block 1 212; DFE block 0 214; Rx ADC 216; capture 218; optional FFT and CP removal 220; hardware accelerated signal data pre-conditioning and memory 222; power detection, analysis, and fault detection 224; radio optimization control and actuation 226; storage 228; C-plane, M- plane, S-plane 232; U-plane 234; tap point 248A (which can be similar to an instance of tap point 148A); tap point 248B (which can be similar to an instance of tap point 148A); tap point 248C (which can be similar to an instance of tap point 148A); and tap point 248D (which can be similar to an instance of tap point 148A).

[0067] In system architecture 200, each tap point (e.g., tap point 248 A) can serve as a multiplexer where one copy of the signal is sent through the signal chain as it would be if there were no tap point, and another copy of the signal is sent to be selectively captured.

Time alignment 204 can align a signal at each tap point with a system time of the down link chain.

[0068] A copy of a signal that is split at a tap point can be captured. Some tap points can be positioned in the time domain of the up link chain (e.g., tap point 248A, tap point 248B, tap point 248C, and tap point 248D). In some examples, some tap points can be positioned in a frequency domain portion of the down link chain.

[0069] Once captured, the captured signal can be processed with hardware accelerated signal data pre-conditioning and memory (which can include operations such as optional FFT and optional CP removal, analysis, and storage. A result of this analysis can be used to cause actuators to change operational parameters of the radio system.

[0070] FIG. 3 A, FIG. 3B, FIG. 3C, and FIG. 3D illustrate an example system architecture 300 for a radio system, and that can facilitate modifying radio unit operational parameters, in accordance with an embodiment of this disclosure. In some examples, system architecture can comprise a radio system that can comprise part(s) of system architecture 100, and/or system architecture 200. [0071] As depicted, system architecture 300 comprises custom signal data memory, generation, masking, and buffer 302A and custom signal data memory, generation, masking, and buffer 302B; time alignment 304A and time alignment 304B; custom symbol RBs/REs 306; from timing system source 308; distributed unit 310; hardware accelerated signal data, pre-conditioning and memory 312A, hardware accelerated signal data, pre-conditioning and memory 312B, and hardware accelerated signal data, pre-conditioning and memory 312C; analysis 314A, analysis 314B, and analysis 314C; control and activation 316A, control and activation 316B, and control and activation 316C; data storage 318; RU 320; custom symbol RBs/REs 322; inverse Fast Fourier Transform (iFFT) 324 (which can also perform A gain, cyclic prefix insertion, and time alignment); cavity filter 326; radiofrequency (RF) front end (RFFE) 328 (which can include low noise amplifiers (ENAs), switches, attenuators, filters, PAs, couplers, and power supplies); transceiver 330 (which can include Tx, FBRx, and Rx); digital front end 332 (which can include filters, CFR, DPD, a digital to analog converter (DACs), an analog to digital converter (ADC), a digital down converters (DDC), a digital up converter (DUC), and iFFT/FFT, CP, and multiplexing); time domain path 334 (which can bypass CP injection and iFFT); frequency domain path 336; time domain path 338 (which can bypass CP removal and FFT); CP removal or bypass 340; FFT 342; temporal frequency domain (FD) data stream 344; temporal time domain (TD) data stream 346; DU C/M-plane 348A and DU C/M-plane 348B; control system aggregation 350A and control system aggregation 350B; analysis database 352A and analysis database 352B; and radio resources 354.

[0072] Hardware accelerated signal data, pre-conditioning and memory 312A, and hardware accelerated signal data, pre-conditioning and memory 312C can perform frequency domain signal data detection. They can perform a binning operation, which can be akin to a functionality performed by a spectrum analyzer digitizer.

[0073] Hardware accelerated signal data, pre-conditioning and memory 312B can perform time domain signal data detection. It can perform binning and storage operations, which can be akin to an oscilloscope digitizer.

[0074] Custom signal data memory, generation, masking, and buffer 302A and custom signal data memory, generation, masking, and buffer 302B can perform signal generation at a distributed unit or a radio unit, respectively. They can perform local synchronized custom and live-air data stimulus with known characteristics. In some examples, they can operate in a frequency domain. [0075] Analysis 314A, analysis 314B, and analysis 314C can perform signal capture data analysis. In some examples, they can implement artificial intelligence/machine learning ( AI/ML) with training (such as live and stored real-time data, and statistical data). They can provide an output of a response to actuators to change operational parameters of a radio system.

[0076] Control and activation 316A, control and activation 316B, and control and activation 316C can take inputs that augment information available to an AI/ML component and output an affect to actuators of the radio system to change operational parameters.

[0077] In some examples, respective outputs of control and activation 316B and control and activation 316C can be aggregated to affect change on a radio and radio performance.

[0078] In some examples, a distributed unit portion of system architecture 300 can send messaging to a radio unit portion of system architecture 300 to cause the radio unit portion to modify operational parameters. In some examples, the radio unit portion of system architecture 300 can determine to modify radio unit operational parameters independently of messaging from the distributed unit portion. In some examples, the radio unit can modify radio unit operational parameters based on a combination of messaging received from the distributed unit portion and determinations made by the radio unit portion independent of the messaging received from the distributed unit portion.

[0079] FIG. 4 illustrates an example system architecture 400 that can facilitate modifying radio unit operational parameters, in accordance with an embodiment of this disclosure.

[0080] System architecture 400 comprises distributed unit that is configured to process traffic and traffic load scheduling to produce processed traffic, and to communicate the processed traffic and traffic load scheduling to the radio unit 402; and radio unit that is configured to modify operational parameters of the radio unit based on the processed traffic and traffic load scheduling received from the distributed unit 404.

[0081] In some examples, distributed unit 402 can be similar to a distributed unit of system architecture 400, and can handle traffic scheduling, and communicate about traffic to radio unit 404. In some examples, radio unit 404 can use this traffic information to change its operational parameters (e.g., reduce power consumption where appropriate).

[0082] In some examples, modifying the operational parameters of the radio unit improves an operational efficiency of the radio unit. That is, system architecture 400 can be implemented to improve radio unit efficiency through modification of configurable operational parameters as a result of messaging from a distributed unit.

[0083] FIG. 5 illustrates another example system architecture 500 that can facilitate modifying radio unit operational parameters, in accordance with an embodiment of this disclosure.

[0084] System architecture 500 comprises distributed unit that is configured to process traffic and traffic load scheduling to produce processed traffic, and to communicate the processed traffic and traffic load scheduling to the radio unit 502 (which can be similar to distributed unit that is configured to process traffic and traffic load scheduling to produce processed traffic, and to communicate the processed traffic and traffic load scheduling to the radio unit 402 of FIG. 4); radio unit that is configured to modify operational parameters of the radio unit based on the processed traffic and traffic load scheduling received from the distributed unit 504 (which can be similar to radio unit that is configured to modify operational parameters of the radio unit based on the processed traffic and traffic load scheduling received from the distributed unit 404); and at least one actuator of the radio unit that is configured to engage to modify the operational parameters 506.

[0085] In some examples, at least one actuator of the radio unit that is configured to engage to modify the operational parameters 506 can be similar to control and actuation 160. Regarding at least one actuator 506, actuators in a radio unit can be accessible for modification through such techniques as direct access by distributed unit messaging, deterministic, or prescriptive techniques to affect operational efficiency performance in a timely manner.

[0086] In some examples, modifying the operational parameters by at least one actuator 506 can be timed and synchronized with a dynamic load of signal data received by the radio unit. That is, operational parameter modifications can be timed and synchronized with a dynamic load of signal data received by radio unit 504.

[0087] FIG. 6 illustrates another example system architecture 600 that can facilitate modifying radio unit operational parameters, in accordance with an embodiment of this disclosure.

[0088] System architecture 600 comprises processing component that is configured to process traffic and traffic load scheduling at a distributed unit of a radio system to produce processed traffic 602; and modifying component that is configured to modify operational parameters of a radio unit of the radio system based on the processed traffic and traffic load scheduling 604.

[0089] In some examples, processing component that is configured to process traffic and traffic load scheduling at a distributed unit of a radio system to produce processed traffic 602 can be similar to distributed unit that is configured to process traffic and traffic load scheduling to produce processed traffic, and to communicate the processed traffic and traffic load scheduling to the radio unit 402 of FIG. 4. In some examples, modifying component that is configured to modify operational parameters of a radio unit of the radio system based on the processed traffic and traffic load scheduling 604 can be similar to radio unit that is configured to modify operational parameters of the radio unit based on the processed traffic and traffic load scheduling received from the distributed unit 404.

[0090] In some examples, modifying component 602 is configured to modify the operational parameters by engaging an actuator of the radio unit, and modifying component 602 is configured to modify signal timing and synchronization associated with an actuator component relative to the radio unit. That is, in some examples, signal timing and synchronization with actuator control can be employed to ensure proper alignment of signals with actuator control and parameter modification.

[0091] In some examples modifying component 602 is configured to modify the operational parameters by engaging an actuator of the radio unit, and modifying component 602 is configured to modify performance of the radio unit to facilitate increasing a traffic load, to facilitate lessening the traffic load, based on determining that the traffic load has decreased, to facilitate lowering a thermal stress, or based on a modulation coding scheme level. That is, in some examples, the following operational parameter modifications can be effectuated: reverting back to normal operation (e.g., supporting increased traffic load after reducing a supported traffic load); modifying performance based on performance metrics gathered from a front end of a radio system, such as via tap points; modifying performance based on monitoring and/or determining modulation coding scheme levels; lowering a thermal stress of a radio system; and/or modifying performance based on lessening traffic. [0092] In some examples, the radio unit is configured to communicate to the distributed unit a request to lessen the traffic load, and the distributed unit is configured to communicate to the radio unit an indication that the traffic load has been lessened. That is, in some examples, the radio unit can communicate to the distributed unit that, due to system performance measurements, the radio unit needs the distributed unit to rapidly lessen traffic load. The distributed unit can then message the radio unit regarding the distributed unit having lessened the traffic load.

[0093] In some examples, the distributed unit is configured to withhold scheduling of the traffic independent of the radio unit, where the withholding scheduling of the traffic comprises modifying a duty cycle of the traffic, and where the withholding scheduling of the traffic reduces a power consumption of the radio unit. In some examples, the radio unit is configured to reduce a power amplifier bias parameter in response to the distributed unit withholding scheduling of the traffic. That is, in some examples where a distributed unit can autonomously withhold scheduling or traffic, either partially or wholly, to an advantage of lessening radio unit power consumption by lessening or modifying a duty cycle of a traffic load, a radio unit can respond with a commensurate lessening of power amplifier bias parameters. In some cases, a priori knowledge of traffic load can be leveraged to modify radio unit parameters and realize energy savings in a user’s network deployment.

EXAMPLE PROCESS FLOWS

[0094] FIG. 7 illustrates an example process flow 700 that can facilitate modifying radio unit operational parameters, in accordance with an embodiment of this disclosure. In some examples, one or more embodiments of process flow 700 can be implemented by system architecture 300.

[0095] It can be appreciated that the operating procedures of process flow 700 are example operating procedures, and that there can be embodiments that implement more or fewer operating procedures than are depicted, or that implement the depicted operating procedures in a different order than as depicted. In some examples, process flow 700 can be implemented in conjunction with one or more embodiments of process flow 800 of FIG. 8, process flow 900 of FIG. 9, process flow 1000 of FIG. 10, process flow 1100 of FIG. 11, process flow 1200 of FIG. 12, process flow 1300 of FIG. 13, process flow 1400 of FIG. 14, process flow 1500 of FIG. 15, and/or process flow 1600 of FIG. 16.

[0096] Process flow 700 begins with 702, and moves to operation 704. Operation 704 depicts processing traffic and traffic load scheduling at a distributed unit to produce processed traffic. In some examples, this can be performed by a distributed unit of system architecture 300. In some examples, operation 704 can be performed by distributed unit that is configured to process traffic and traffic load scheduling to produce processed traffic, and to communicate the processed traffic and traffic load scheduling to the radio unit 402 of FIG. 4. [0097] After operation 704, process flow 700 moves to operation 706.

[0098] Operation 706 depicts modifying operational parameters of a radio unit based on the processed traffic and traffic load scheduling. In some examples, this can be performed by a radio unit of system architecture 300. In some examples, operation 706 can be performed by radio unit that is configured to modify operational parameters of the radio unit based on the processed traffic and traffic load scheduling received from the distributed unit 404

[0099] After operation 706, process flow 700 moves to 708, where process flow 700 ends.

[00100] FIG. 8 illustrates another example process flow 800 that can facilitate modifying radio unit operational parameters, in accordance with an embodiment of this disclosure. In some examples, one or more embodiments of process flow 800 can be implemented by system architecture 300.

[00101] It can be appreciated that the operating procedures of process flow 800 are example operating procedures, and that there can be embodiments that implement more or fewer operating procedures than are depicted, or that implement the depicted operating procedures in a different order than as depicted. In some examples, process flow 800 can be implemented in conjunction with one or more embodiments of process flow 700 of FIG. 7, process flow 900 of FIG. 9, process flow 1000 of FIG. 10, process flow 1100 of FIG. 11, process flow 1200 of FIG. 12, process flow 1300 of FIG. 13, process flow 1400 of FIG. 14, process flow 1500 of FIG. 15, and/or process flow 1600 of FIG. 16.

[00102] Process flow 800 begins with 802, and moves to operation 804. Operation 804 depicts processing traffic and traffic load scheduling at a distributed unit produce processed traffic. In some examples, operation 804 can be implemented in a similar manner as operation 704 of FIG. 7.

[00103] After operation 804, process flow 800 moves to operation 806.

[00104] Operation 806 depicts changing a power amplifier bias of the radio unit with an actuator based on the processed traffic and traffic load scheduling. That is, a radio unit can perform a change to power amplifier bias via actuators to improve (e.g., lessen power consumption) of a radio.

[00105] After operation 806, process flow 800 move to 808, where process flow 800 ends. [00106] FIG. 9 illustrates another example process flow 900 that can facilitate modifying radio unit operational parameters, in accordance with an embodiment of this disclosure. In some examples, one or more embodiments of process flow 900 can be implemented by system architecture 300.

[00107] It can be appreciated that the operating procedures of process flow 900 are example operating procedures, and that there can be embodiments that implement more or fewer operating procedures than are depicted, or that implement the depicted operating procedures in a different order than as depicted. In some examples, process flow 900 can be implemented in conjunction with one or more embodiments of process flow 700 of FIG. 7, process flow 800 of FIG. 8, process flow 1000 of FIG. 10, process flow 1100 of FIG. 11, process flow 1200 of FIG. 12, process flow 1300 of FIG. 13, process flow 1400 of FIG. 14, process flow 1500 of FIG. 15, and/or process flow 1600 of FIG. 16.

[00108] Process flow 900 begins with 902, and moves to operation 904. Operation 904 depicts processing traffic and traffic load scheduling at a distributed unit produce processed traffic. In some examples, operation 904 can be implemented in a similar manner as operation 704 of FIG. 7.

[00109] After operation 904, process flow 900 moves to operation 906.

[00110] Operation 906 depicts changing a supply voltage of the radio unit with an actuator based on the processed traffic and traffic load scheduling. That is, a radio unit can perform a change to supply voltage (Vdd) via actuators to improve (e.g., lessen power consumption) of a radio.

[00111] After operation 906, process flow 900 moves to 908, where process flow 900 ends.

[00112] FIG. 10 illustrates another example process flow 1000 that can facilitate modifying radio unit operational parameters, in accordance with an embodiment of this disclosure. In some examples, one or more embodiments of process flow 1000 can be implemented by system architecture 300.

[00113] It can be appreciated that the operating procedures of process flow 1000 are example operating procedures, and that there can be embodiments that implement more or fewer operating procedures than are depicted, or that implement the depicted operating procedures in a different order than as depicted. In some examples, process flow 1000 can be implemented in conjunction with one or more embodiments of process flow 700 of FIG. 7, process flow 800 of FIG. 8, process flow 900 of FIG. 9, process flow 1100 of FIG. 11, process flow 1200 of FIG. 12, process flow 1300 of FIG. 13, process flow 1400 of FIG. 14, process flow 1500 of FIG. 15, and/or process flow 1600 of FIG. 16.

[00114] Process flow 1000 begins with 1002, and moves to operation 1004. Operation 1004 depicts processing traffic and traffic load scheduling at a distributed unit produce processed traffic. In some examples, operation 1004 can be implemented in a similar manner as operation 704 of FIG. 7.

[00115] After operation 1004, process flow 1000 moves to operation 1006.

[00116] Operation 1006 depicts changing a gate bias of the radio unit with an actuator based on the processed traffic and traffic load scheduling. That is, a radio unit can perform a change to gate biases via actuators to improve (e.g., lessen power consumption) of a radio.

[00117] After operation 1006, process flow 1000 moves to 1008, where process flow 1000 ends.

[00118] FIG. 11 illustrates another example process flow 1100 that can facilitate modifying radio unit operational parameters, in accordance with an embodiment of this disclosure. In some examples, one or more embodiments of process flow 1100 can be implemented by system architecture 300.

[00119] It can be appreciated that the operating procedures of process flow 1100 are example operating procedures, and that there can be embodiments that implement more or fewer operating procedures than are depicted, or that implement the depicted operating procedures in a different order than as depicted. In some examples, process flow 1100 can be implemented in conjunction with one or more embodiments of process flow 700 of FIG. 7, process flow 800 of FIG. 8, process flow 900 of FIG. 9, process flow 1000 of FIG. 10, process flow 1200 of FIG. 12, process flow 1300 of FIG. 13, process flow 1400 of FIG. 14, process flow 1500 of FIG. 15, and/or process flow 1600 of FIG. 16.

[00120] Process flow 1100 begins with 1102, and moves to operation 1104. Operation 1104 depicts receiving, at the radio unit, messaging from the distributed unit.

[00121] In some examples this messaging can be sent via a c-plane of C-plane, M- plane, and S-plane 174. After operation 1104, process flow 1100 moves to operation 1106. [00122] Operation 1106 depicts modifying operational parameters based on the messaging. Using the example of FIGS. 1A-1C, this can comprise engaging control and actuation 160 to change operational parameters such as a power amplifier bias. That is, messaging from the distributed unit and to the radio unit can be used to modify operational parameters in the radio unit. [00123] After operation 1106, process flow 1100 moves to 1108, where process flow 1100 ends.

[00124] FIG. 12 illustrates another example process flow 1200 that can facilitate modifying radio unit operational parameters, in accordance with an embodiment of this disclosure. In some examples, one or more embodiments of process flow 1200 can be implemented by system architecture 300.

[00125] It can be appreciated that the operating procedures of process flow 1200 are example operating procedures, and that there can be embodiments that implement more or fewer operating procedures than are depicted, or that implement the depicted operating procedures in a different order than as depicted. In some examples, process flow 1200 can be implemented in conjunction with one or more embodiments of process flow 700 of FIG. 7, process flow 800 of FIG. 8, process flow 900 of FIG. 9, process flow 1000 of FIG. 10, process flow 1100 of FIG. 11, process flow 1300 of FIG. 13, process flow 1400 of FIG. 14, process flow 1500 of FIG. 15, and/or process flow 1600 of FIG. 16.

[00126] Process flow 1200 begins with 1202, and moves to operation 1204. Operation 1204 depicts receiving, at the radio unit, messaging from the distributed unit. In some examples, operation 1204 can be implemented in a manner similar to operation 1104 of FIG. 11.

[00127] After operation 1204, process flow 1200 moves to operation 1206.

[00128] Operation 1206 depicts deterministically modifying the operational parameters based on the messaging. That is, the operational parameters can be modified based on predetermined operations on an input of messaging from the distributed unit.

[00129] After operation 1206, process flow 1200 moves to 1208, where process flow 1200 ends.

[00130] FIG. 13 illustrates another example process flow 1300 that can facilitate modifying radio unit operational parameters, in accordance with an embodiment of this disclosure. In some examples, one or more embodiments of process flow 1300 can be implemented by system architecture 300.

[00131] It can be appreciated that the operating procedures of process flow 1300 are example operating procedures, and that there can be embodiments that implement more or fewer operating procedures than are depicted, or that implement the depicted operating procedures in a different order than as depicted. In some examples, process flow 1300 can be implemented in conjunction with one or more embodiments of process flow 700 of FIG. 7, process flow 800 of FIG. 8, process flow 900 of FIG. 9, process flow 1000 of FIG. 10, process flow 1100 of FIG. 11, process flow 1200 of FIG. 12, process flow 1400 of FIG. 14, process flow 1500 of FIG. 15, and/or process flow 1600 of FIG. 16.

[00132] Process flow 1300 begins with 1302, and moves to operation 1304. Operation 1304 depicts receiving, at the radio unit, messaging from the distributed unit. In some examples, operation 1304 can be implemented in a manner similar to operation 1104 of FIG. 11.

[00133] After operation 1304, process flow 1300 moves to operation 1306.

[00134] Operation 1306 depicts modifying the operational parameters via use of a feedback mechanism in orchestration with distributed unit messaging. That is, a radio unit can have a feedback mechanism that receives information about how modifying the operational parameters has affected function of the radio unit, and can use this information in conjunction with messaging from the distributed unit to determine how to further modify (e.g., fine tune) operational parameters.

[00135] After operation 1306, process flow 1300 moves to 1308, where process flow 1300 ends.

[00136] FIG. 14 illustrates another example process flow 1400 that can facilitate modifying radio unit operational parameters, in accordance with an embodiment of this disclosure. In some examples, one or more embodiments of process flow 1400 can be implemented by system architecture 300.

[00137] It can be appreciated that the operating procedures of process flow 1400 are example operating procedures, and that there can be embodiments that implement more or fewer operating procedures than are depicted, or that implement the depicted operating procedures in a different order than as depicted. In some examples, process flow 1400 can be implemented in conjunction with one or more embodiments of process flow 700 of FIG. 7, process flow 800 of FIG. 8, process flow 900 of FIG. 9, process flow 1000 of FIG. 10, process flow 1100 of FIG. 11, process flow 1200 of FIG. 12, process flow 1300 of FIG. 13, process flow 1500 of FIG. 15, and/or process flow 1600 of FIG. 16.

[00138] Process flow 1400 begins with 1402, and moves to operation 1404. Operation 1404 depicts receiving, at the radio unit, messaging from the distributed unit 1404. In some examples, operation 1404 can be implemented in a manner similar to operation 1104 of FIG. 11.

[00139] After operation 1404, process flow 1400 moves to operation 1406. [00140] Operation 1406 depicts passing the messaging to a block that is configured to determine a response based on an input that conditions a deterministic outcome to at least a predetermined threshold amount. That is, operational parameters can be modified prescriptively based on messaging from the distributed unit. In some examples, messaging from the distributed unit can be received by the radio unit and passed to a block (e.g., a digital front end chain block) that is configured to determine operational parameters to modify, and create a response based on the input that further conditions a deterministic outcome to a desired degree. In some examples, this can be performed by logic of an AND gate.

[00141] After operation 1406, process flow 1400 moves to 1408, where process flow 1400 ends.

[00142] FIG. 15 illustrates another example process flow 1500 that can facilitate modifying radio unit operational parameters, in accordance with an embodiment of this disclosure. In some examples, one or more embodiments of process flow 1500 can be implemented by system architecture 300.

[00143] It can be appreciated that the operating procedures of process flow 1500 are example operating procedures, and that there can be embodiments that implement more or fewer operating procedures than are depicted, or that implement the depicted operating procedures in a different order than as depicted. In some examples, process flow 1500 can be implemented in conjunction with one or more embodiments of process flow 700 of FIG. 7, process flow 800 of FIG. 8, process flow 900 of FIG. 9, process flow 1000 of FIG. 10, process flow 1100 of FIG. 11, process flow 1200 of FIG. 12, process flow 1300 of FIG. 13, process flow 1400 of FIG. 14, and/or process flow 1600 of FIG. 16.

[00144] Process flow 1500 begins with 1502, and moves to operation 1504. Operation 1504 depicts modifying operational parameters of a radio unit based on processed traffic and traffic load scheduling 1504. This can be similar to processed traffic and traffic load scheduling in operation 706 of FIG. 7. In some examples, operation 1504 can be implemented by modifying component that is configured to modify operational parameters of a radio unit of the radio system based on the processed traffic and traffic load scheduling 604 of FIG. 6.

[00145] After operation 1504, process flow 1500 moves to operation 1506.

[00146] Operation 1506 depicts modifying the operational parameters based on information that is determined at the radio unit, independently of messaging from a distributed unit 1506. That is, the radio unit can make determinations about operation of the radio unit, and use these determinations to further modify operational parameters.

[00147] After operation 1506, process flow 1500 moves to 1508, where process flow 1500 ends.

[00148] FIG. 16 illustrates another example process flow 1600 that can facilitate modifying radio unit operational parameters, in accordance with an embodiment of this disclosure. In some examples, one or more embodiments of process flow 1600 can be implemented by system architecture 300.

[00149] It can be appreciated that the operating procedures of process flow 1600 are example operating procedures, and that there can be embodiments that implement more or fewer operating procedures than are depicted, or that implement the depicted operating procedures in a different order than as depicted. In some examples, process flow 1600 can be implemented in conjunction with one or more embodiments of process flow 700 of FIG. 7, process flow 800 of FIG. 8, process flow 900 of FIG. 9, process flow 1000 of FIG. 10, process flow 1100 of FIG. 11, process flow 1200 of FIG. 12, process flow 1300 of FIG. 13, process flow 1400 of FIG. 14, and/or process flow 1500 of FIG. 15.

[00150] Process flow 1600 begins with 1602, and moves to operation 1604. Operation 1604 depicts receiving, at the radio unit, messaging from the distributed unit. In some examples, operation 1604 can be implemented in a similar manner as operation 1104 of FIG. 11.

[00151] After operation 1604, process flow 1600 moves to operation 1606.

[00152] Operation 1606 depicts determining, internal to the radio unit, information. This can be information about operation of the radio unit that is determined by the radio unit. [00153] After operation 1606, process flow 1600 moves to operation 1608.

[00154] Operation 1608 depicts modifying the operational parameters based on a combination of the messaging and the information. That is, in some examples, a hybrid of both messaging from the distributed unit and information determined by the radio unit that is internal to the radio unit (and independent of distributed unit messaging) can be used to modify operational parameters.

[00155] After operation 1608, process flow 1600 moves to 1610, where process flow 1600 end.

CONCLUSION [00156] As it employed in the subject specification, the term “processor” can refer to substantially any computing processing unit or device comprising, but not limited to comprising, single-core processors; single-processors with software multithread execution capability; multi-core processors; multi-core processors with software multithread execution capability; multi-core processors with hardware multithread technology; parallel platforms; and parallel platforms with distributed shared memory in a single machine or multiple machines. Additionally, a processor can refer to an integrated circuit, a state machine, an application specific integrated circuit (ASIC), a digital signal processor (DSP), a programmable gate array (PGA) including a field programmable gate array (FPGA), a programmable logic controller (PLC), a complex programmable logic device (CPLD), a discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. Processors can exploit nano-scale architectures such as, but not limited to, molecular and quantum-dot based transistors, switches and gates, in order to optimize space usage or enhance performance of user equipment. A processor may also be implemented as a combination of computing processing units. One or more processors can be utilized in supporting a virtualized computing environment. The virtualized computing environment may support one or more virtual machines representing computers, servers, or other computing devices. In such virtualized virtual machines, components such as processors and storage devices may be virtualized or logically represented. For instance, when a processor executes instructions to perform “operations”, this could include the processor performing the operations directly and/or facilitating, directing, or cooperating with another device or component to perform the operations.

[00157] In the subject specification, terms such as “datastore,” data storage,” “database,” “cache,” and substantially any other information storage component relevant to operation and functionality of a component, refer to “memory components,” or entities embodied in a “memory” or components comprising the memory. It will be appreciated that the memory components, or computer-readable storage media, described herein can be either volatile memory or nonvolatile storage, or can include both volatile and nonvolatile storage. By way of illustration, and not limitation, nonvolatile storage can include ROM, programmable ROM (PROM), EPROM, EEPROM, or flash memory. Volatile memory can include RAM, which acts as external cache memory. By way of illustration and not limitation, RAM can be available in many forms such as synchronous RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), Synchlink DRAM (SLDRAM), and direct Rambus RAM (DRRAM). Additionally, the disclosed memory components of systems or methods herein are intended to comprise, without being limited to comprising, these and any other suitable types of memory.

[00158] The illustrated embodiments of the disclosure can be practiced in distributed computing environments where certain tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules can be located in both local and remote memory storage devices.

[00159] The systems and processes described above can be embodied within hardware, such as a single integrated circuit (IC) chip, multiple ICs, an ASIC, or the like. Further, the order in which some or all of the process blocks appear in each process should not be deemed limiting. Rather, it should be understood that some of the process blocks can be executed in a variety of orders that are not all of which may be explicitly illustrated herein.

[00160] As used in this application, the terms “component,” “module,” “system,” “interface,” “cluster,” “server,” “node,” or the like are generally intended to refer to a computer-related entity, either hardware, a combination of hardware and software, software, or software in execution or an entity related to an operational machine with one or more specific functionalities. For example, a component can be, but is not limited to being, a process running on a processor, a processor, an object, an executable, a thread of execution, computer-executable instruction(s), a program, and/or a computer. By way of illustration, both an application running on a controller and the controller can be a component. One or more components may reside within a process and/or thread of execution and a component may be localized on one computer and/or distributed between two or more computers. As another example, an interface can include input/output (I/O) components as well as associated processor, application, and/or application programming interface (API) components.

[00161] Further, the various embodiments can be implemented as a method, apparatus, or article of manufacture using standard programming and/or engineering techniques to produce software, firmware, hardware, or any combination thereof to control a computer to implement one or more embodiments of the disclosed subject matter. An article of manufacture can encompass a computer program accessible from any computer-readable device or computer-readable storage/communications media. For example, computer readable storage media can include but are not limited to magnetic storage devices (e.g., hard disk, floppy disk, magnetic strips...), optical discs (e.g., CD, DVD...), smart cards, and flash memory devices (e.g., card, stick, key drive...). Of course, those skilled in the art will recognize many modifications can be made to this configuration without departing from the scope or spirit of the various embodiments.

[00162] In addition, the word “example” or “exemplary” is used herein to mean serving as an example, instance, or illustration. Any embodiment or design described herein as “exemplary” is not necessarily to be construed as preferred or advantageous over other embodiments or designs. Rather, use of the word exemplary is intended to present concepts in a concrete fashion. As used in this application, the term “or” is intended to mean an inclusive “or” rather than an exclusive “or.” That is, unless specified otherwise, or clear from context, “X employs A or B” is intended to mean any of the natural inclusive permutations. That is, if X employs A; X employs B; or X employs both A and B, then “X employs A or B” is satisfied under any of the foregoing instances. In addition, the articles “a” and “an” as used in this application and the appended claims should generally be construed to mean “one or more” unless specified otherwise or clear from context to be directed to a singular form.

[00163] What has been described above includes examples of the present specification. It is, of course, not possible to describe every conceivable combination of components or methods for purposes of describing the present specification, but one of ordinary skill in the art may recognize that many further combinations and permutations of the present specification are possible. Accordingly, the present specification is intended to embrace all such alterations, modifications and variations that fall within the spirit and scope of the appended claims. Furthermore, to the extent that the term “includes” is used in either the detailed description or the claims, such term is intended to be inclusive in a manner similar to the term “comprising” as “comprising” is interpreted when employed as a transitional word in a claim.