Patent ID: 12188976

DETAILED DESCRIPTION

Overview

In modern 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.

An ability to capture and derive key performance data from a radio sub-systems can be tantamount to facilitating direct measurement and analysis of sub-system performance. Analogous to a signal analyzer or spectrum analyzer, an ability to read, record and recall data for further analysis can facilitate deeper understanding of metrics such as system performance and can be further used to determine improved performance aspects of system operation, long-term reliability, and customer satisfaction.

Signal data storage can be used for both near and long-term historical and statistical performance evaluation, such as a digital twin (where a computer program model of a hardware radio system is maintained), health assessments, early failure, no fault found (NFF) event capture, black box flight recorder, soft failure indicators, and/or aging assessments. Signal data storage can also facilitate autonomous operations of a radio network, such as by network efficiency management through artificial intelligence (AI)/machine learning (ML). In some examples, stored and streaming real-time data of a radio system can be used to train such an AI/ML component.

The present techniques can be implemented to use custom tap points designed into a digital front end path of a radio unit, and capture signal data. In some digital front ends, custom tap points are not a part of an operational signal path of a normal digital front end data path, and can be added according to the present techniques to support capture and storage from signal tap points in a radio.

In some examples, a signal can be captured from a tap point in a time domain, and transformed into a frequency domain. In some examples, the signal can be captured from the tap point in the time domain, and preserved in the time domain.

Data that is captured from a tap point in a digital front end can be stored and made available for further analysis.

In some examples, capture and storage of signals from tap points in a digital front end chain of a radio unit can be performed to capture a signal at certain digital front end blocks, such as a crest factor reduction output signal (CFR_OUT_Signal), a digital pre-distortion output signal (DPD_OUT_Signal), an error signal (Error_Signal), or a feedback receiver (FBRX_IN_Signal).

Signal data storage can be used for both near- and long-term historical and statistical performance evaluation. Examples of statistical performance evaluation can include a digital twin, a health assessment, early failure, no fault found (NFF) event capture, a black box flight recorder, soft failure indicators, and an aging assessment.

As described above, signal data storage can also facilitate autonomous operations of a radio network, such as by network efficiency management through artificial intelligence (AI)/machine learning (ML).

In some examples, signal capture can be performed in both a down link and an up link of a digital front end.

In some examples, with regard to capturing a signal at a tap point, a tap point can be considered to be a form of multiplexing, where a signal follows the normal path in a digital front end, and a copy of the signal splits off to another path, where it can be captured, stored, analyzed, and used to engage an actuator (that changes an operational parameter of the radio system).

In some examples, signal capture, storage, and analysis can be implemented in parts of a radio system other than a radio unit (which can generally convert signals sent to and from and an antenna to a digital signal that can be transmitted to a distributed unit), such as a distributed unit (which can be responsible for real time L1 and L2 scheduling functions), or a central unit (which can be responsible for non-real time, higher L2 and L3 scheduling functions).

In some examples, tap points can encompass analog aspects of a radio unit and routing for analysis.

Actuator blocks can be implemented in a radio system to derive and perform system performance modifications based on an analysis of captured signals.

In some examples, signals can be captured from multiple antenna branches of a radio system. In some examples, data can be captured from multiple different antenna branches simultaneously.

In some examples, frequency domain selectivity can be implemented with the present techniques. A specific area of a frequency domain can be zoomed to that is relevant to a regulatory specification. In some examples, time domain can be more generalized to root mean square (RMS) and peak power over specific periods of time. In some examples, a large portion of a digital front end can operate in a time domain.

In some examples, a signal can be captured from a transmission (Tx) signal path, a receiver (Rx) signal path, or a feedback receiver (FBRx) signal path.

For dimensioning, 1 inphase and quadrature (I+Q, or I/Q) value pair can be equivalent to 1 resource element (RE)/sub-carrier in a frequency domain. In some examples, dimensioning can comprise up to 4,096 REs of I+Q, 16 bit (signed) data pairs. Data can be triggered and time aligned with system timing on a symbol-by-symbol basis. In some examples, data can be time aligned with other relevant system time boundaries (such as via hardware-accelerated pre-conditioning of the signal).

Data can be captured in a variety of forms, and processed in a variety of ways. Data can be purely live-air traffic data (which can sometimes be referred to as mission mode data). Data can be from purely non-live-air traffic sources (where non-live-air traffic is sometimes referred to as non mission mode). Data can be a hybrid of live-air traffic and non-live-air traffic sources.

Captured data can be processed with or without cyclic prefix (CP) removal. Data can be captured and stored to memory over a single time boundary or multiple time boundaries.

Data analysis can be performed on current data, or contrasted with historical data that is stored in a database. Data can be stored in a raw data form, or an analyzed form. Data can be aligned on a symbol or other system time boundaries.

Data can be purely from sources internal to a radio unit's digital front end chain, or a combination of a digital front end chain and an analog chain.

Signal data storage can be used for both near- and long-term historical statistical performance evaluation. Similar to as described above, this performance evaluation can comprise a digital twin, health assessments, early failure, NFF event capture, black box flight recorder, soft failure indicators, and/or aging assessments. Signal data storage can also facilitate autonomous operations of a radio network, such as by network efficiency management through AI/ML.

In examples according to the present techniques, a flow of reading signal data can be started and stopped at key radio time elements (which can sometimes be referred to as “gating”). This selective filtering can be performed based on time (that is, a signal can be read for a certain time period), or frequency (that is, certain frequencies of the signal can be read). This can be viewed in contrast to prior approaches that can involve a broad capture of data on a non-dynamic time frame.

Starting and stopping a flow of data that is read, as well as selecting frequency data can comprise preselecting data so that it can be efficiently analyzed.

Data at a tap point that can be read can be synchronized, or time aligned, with a system timing function of a radio unit.

In some examples, a tap point is disposed in a time domain portion of a radio system. In such examples, a fast Fourier transform can be performed on read data to convert it from a time domain to a frequency domain.

A tap point according to these present techniques can be time aligned relative to the radio system, and provide an ability to extract data in a time domain or a frequency domain. In some examples, hardware acceleration can perform initial processing of data captured at a tap point through time grating, frequency selection, peak and root mean square (RMS) power detection, statistical accumulation, etc. After initial processing, the data can be stored, and the stored data can be made available for analysis.

In some examples, the analysis can include real time training and analysis (such as through ML/AI techniques), and longer-term analysis (such as a centralized database modeling a digital twin of the radio system, or performing predictive modeling).

This analysis can be used, for example, to adjust operational parameters of the radio system to increase the radio system's performance.

Radio timing elements that can be utilized in implementing the present techniques can include time-division duplexing (TDD) timing, transmitter (Tx) blanking, power amplifier (PA) ON/OFF, gate start/stop/pause timing offset, symbol/slot/frame boundaries, glitch triggering, time boundary transitions triggering, accumulated/processed data event triggering, fault event triggering, pipeline delay, etc.

Example Architectures

FIG.1A,FIG.1B, andFIG.1Cillustrate an example system architecture100for capture and storage of a signal from tap points in a down link chain of a radio system, and that can facilitate capture and storage from signal tap points, in accordance with an embodiment of this disclosure;

System architecture100can function as a down link signal path of a radio. As depicted, system architecture100comprises custom signal data memory, generation, masking, and buffer102(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 alignment116, custom symbol resource blocks/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/RE122, iFFT/CP124, digital front end (DFE) block1126, DFE block2128, crest factor reduction (CFR)130, digital pre-distortion (DPD)132, delta-time-phase (ΔTΘ)134, adaptation and correlation136, feedback receiver analog-to-digital converter (FBRx ADC)138, transmitter digital to-analog converter (Tx ADC)140, capture142, power amplifier144, signal coupler146, tap point148A, tap point148B, tap point148C, tap point148D, tap point148E, tap point148F (which can be accessed to capture a FBRx_Signal_IN), tap point148G (which can be accessed to capture a CFR_OUT_Signal), tap point select150, select152, signal data154, AND/OR156, hardware accelerated signal data pre-conditioning and memory158, optional FFT and CP removal162, analysis and fault detection164, radio optimization control and actuation166, select168, storage170, U-plane172, and C-plane, M-plane, and S-plane174.

In different examples, different blocks of system architecture100can be implemented and/or used. For example, optional FFT and CP removal162can 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).

In system architecture100, each tap point (e.g., tap point148A) 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 alignment116can align a signal at each tap point with a system time of the down link chain.

A copy of a signal that is split at a tap point can be sent to capture142, 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.

Once captured, the captured signal can proceed through hardware accelerated signal data pre-conditioning and memory158. Hardware accelerated signal data pre-conditioning and memory158can 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.

FIG.2AandFIG.2Billustrate an example system architecture200for capture and storage of a signal from tap points in an up link chain of a radio system, and that can facilitate capture and storage from signal tap points, in accordance with an embodiment of this disclosure. In some examples, system architecture200can be implemented in conjunction with system architecture100ofFIGS.1A,1B, and1C, where system architecture200implements an up link chain of a radio system, and system architecture100implements a corresponding down link chain.

As depicted, system architecture200comprises custom symbol RBs/REs202; time alignment204; FFT/CP206; DFE block N+1208; DFE block N210; DFE block1212; DFE block0214; Rx ADC216; capture218; optional FFT and CP removal220; hardware accelerated signal data pre-conditioning and memory222; power detection, analysis, and fault detection224; radio optimization control and actuation226; storage228; C-plane, M-plane, S-plane232; U-plane234; tap point248A (which can be similar to an instance of tap point148A); tap point248B (which can be similar to an instance of tap point148A); tap point248C (which can be similar to an instance of tap point148A); and tap point248D (which can be similar to an instance of tap point148A).

In system architecture200, each tap point (e.g., tap point248A) 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 alignment204can align a signal at each tap point with a system time of the down link chain.

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 point248A, tap point248B, tap point248C, and tap point248D). In some examples, some tap points can be positioned in a frequency domain portion of the down link chain.

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.

FIG.3AandFIG.3Billustrate an example system architecture300for a radio unit, and that can facilitate capture and storage from signal tap points in a radio system, in accordance with an embodiment of this disclosure. In some examples, system architecture300can comprise a radio unit that comprises part(s) of system architecture100ofFIGS.1A,1B, and1Cas a down link chain, and part(s) of system architecture200as an up link chain.

As depicted, system architecture300comprises distributed unit (DU) control user synchronization management (CUSM) plane interface (I/F)302, live-air traffic signals from DU304, live-air traffic signals to DU306, optional iFFT and CP308, iFFT and CP310, radio unit (RU) originated custom non-live-air traffic signals312, DL DFE chain314, radio optimization controller316, optional FFT and optional CP removal318, FFT and CP removal320, waveform/RB/RE signal data storage322A and waveform/RB/RE signal data storage322B, Rx port324, UL DFE chain326, measurement block328, transceiver330, transmission (Tx) blocks332, feedback receiver (FBRx) blocks334, receiver (Rx) blocks336, Tx or transceiver (TRx) port338, and antenna calibration (AntCal) and built-in self-test (BIST) calibration port340.

Down link (DL) DFE chain314can include CFR and DPD. Measurement block328can comprise signal (data) generation, power (data) detectors, statistical counters, injection tap points, capture tap points, and/or hardware accelerated signal data pre-selection.

Tx blocks332can include Tx low, pre-drivers and drivers, power amplifier (PA) final stage, signal feedback, and non-live-air traffic alternate analog path options. FBRx blocks334can include a live-air traffic FBRx path, voltage standing wave ratio (VSWR) mode switching, and non-live-air traffic alternate analog path options. Rx blocks336can include a live-air traffic low noise amplifier (LNA) path, VSWR switching, and non-live-air traffic analog path options. Rx port324can include a separate port for the case of frequency-division duplexing (FDD) radio architectures.

These above components of system architecture300can be part of radio unit (RU)342. System architecture300also comprises distributed unit (DU)344, scheduler346, custom symbol resource blocks/resource elements (RBs/REs)348, custom signal data memory, generation, masking, and buffer350, time alignment352, hardware accelerated signal data pre-conditioning and memory354, analysis and fault detection356, radio optimization control and actuation358, and storage360.

In system architecture300, signals can be captured and stored at measurement block328.

FIG.4A,FIG.4B,FIG.4C, andFIG.4Dillustrate an example system architecture400for a radio system, and that can facilitate capture and storage from signal tap points in a radio system, 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 architecture100ofFIGS.1A,1B, and1C, system architecture200, and/or system architecture300.

As depicted, system architecture400comprises custom signal data memory, generation, masking, and buffer402A and custom signal data memory, generation, masking, and buffer402B; time alignment404A and time alignment404B; custom symbol RBs/REs406; from timing system source408; distributed unit410; hardware accelerated signal data, pre-conditioning and memory412A, hardware accelerated signal data, pre-conditioning and memory412B, and hardware accelerated signal data, pre-conditioning and memory412C; analysis414A, analysis414B, and analysis414C; control and activation416A, control and activation416B, and control and activation416C; data storage418; RU420; custom symbol RBs/REs422; inverse Fast Fourier Transform (iFFT)424(which can also perform A gain, cyclic prefix insertion, and time alignment); cavity filter426; radiofrequency (RF) front end (RFFE)428(which can include low noise amplifiers (LNAs), switches, attenuators, filters, PAs, couplers, and power supplies); transceiver430(which can include Tx, FBRx, and Rx); digital front end432(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 path434(which can bypass CP injection and iFFT); frequency domain path436; time domain path438(which can bypass CP removal and FFT); CP removal or bypass440; FFT442; temporal frequency domain (FD) data stream444; temporal time domain (TD) data stream446; DU C/M-plane448A and DU C/M-plane448B; control system aggregation450A and control system aggregation450B; analysis database452A and analysis database452B; and radio resources454.

Hardware accelerated signal data, pre-conditioning and memory412A, and hardware accelerated signal data, pre-conditioning and memory412C 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.

Hardware accelerated signal data, pre-conditioning and memory412B can perform time domain signal data detection. It can perform binning and storage operations, which can be akin to an oscilloscope digitizer.

Custom signal data memory, generation, masking, and buffer402A and custom signal data memory, generation, masking, and buffer402B 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.

Analysis414A, analysis414B, and analysis414C 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.

Control and activation416A, control and activation416B, and control and activation416C 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.

In some examples, respective outputs of control and activation416B and control and activation416C can be aggregated to affect change on a radio and radio performance.

FIG.5illustrates an example system architecture500that can facilitate capture and storage from signal tap points in a radio system, in accordance with an embodiment of this disclosure. In some examples, part(s) of system architecture500can be used to implement part(s) of system architecture100ofFIGS.1A,1B, and1C, and/or system architecture200.

System architecture500comprises radio unit502(which comprises a digital front end chain); tap point disposed within the digital front end chain504; first hardware component that is configured to selectively read a signal at the tap point to produce a read signal506; and second hardware component that is configured to store the read signal508.

First hardware component506can selectively read a signal where first hardware component506reads the signal for a defined time period or a defined frequency or frequencies.

In some examples, radio unit can be similar to a combination of system architecture100ofFIGS.1A,1B, and1C(which generally depicts a down link chain of a radio system) and system architecture200(which generally depicts an up link (UL) chain of a radio system).

Tap point disposed within the digital front end chain504can be similar to tap point148A or tap point248A. In some examples, tap point disposed within the digital front end chain504can be configured to time align a signal at the tap point with a system time of the radio unit. This time alignment can be effectuated by a component similar to time alignment116or time alignment204.

First hardware component that is configured to selectively read the signal at the tap point to produce a read signal506can be similar to capture142or capture218. Second hardware component that is configured to store the read signal508can be similar to storage170, or storage228.

In some examples, the read signal is represented in a time domain of the radio unit. That is, the read signal can be captured at a tap point in a time domain (e.g., tap point148A or tap point248A). In such examples, the read signal can also be stored in a time domain representation. That is, the read signal can be stored without conversion to a frequency domain such as with a Fast Fourier Transform conversion.

FIG.6illustrates another example system architecture600that can facilitate capture and storage from signal tap points in a radio system, in accordance with an embodiment of this disclosure. In some examples, part(s) of system architecture600can be used to implement part(s) of system architecture100, and/or system architecture200.

System architecture600comprises radio unit602(which can be similar to radio unit502ofFIG.5); tap point disposed within the digital front end chain604(which can be similar to tap point disposed within the digital front end chain504); first hardware component that is configured to selectively read the signal at the tap point to produce a read signal606(which can be similar to first hardware component that is configured to selectively read the signal at the tap point to produce a read signal506); second hardware component that is configured to store the read signal608(which can be similar to second hardware component that is configured to store the read signal508); and third hardware component that is configured to transform the read signal from a time domain of the radio unit to a frequency domain of the radio unit before the second hardware component stores the read signal610.

In some examples, third hardware component configured to transform the read signal from a time domain of the radio unit to a frequency domain of the radio unit before the second hardware component stores the read signal610can be similar to a functionality provided by optional FFT and CP removal162or optional FFT and CP removal.

In some examples, third hardware component610is further configured to selectively filter frequencies of the read signal in the frequency domain from the read signal before the second hardware component stores the read signal.

FIG.7illustrates another example system architecture700that can facilitate capture and storage from signal tap points in a radio system, in accordance with an embodiment of this disclosure. In some examples, part(s) of system architecture700can be used to implement part(s) of system architecture100, and/or system architecture200.

System architecture700comprises radio unit702(which can be similar to radio unit502ofFIG.5); tap point disposed within the digital front end chain704(which can be similar to tap point disposed within the digital front end chain504); first hardware component that is configured to selectively read the signal at the tap point to produce a read signal706(which can be similar to first hardware component that is configured to selectively read the signal at the tap point to produce a read signal506); second hardware component that is configured to store the read signal708(which can be similar to second hardware component that is configured to store the read signal508); and third hardware component that is configured to determine a performance metric of the radio unit based on the stored signal712.

In some examples, third hardware component that is configured to determine a performance metric of the radio unit based on the stored signal712can be similar to analysis and fault detection164or power detection, analysis, and fault detection224.

In some examples, the performance metric comprises a health assessment metric, an early failure metric, a no fault found event capture, a black box flight recorder metric, a soft failure metric, or an aging metric.

FIG.8illustrates another example system architecture that can facilitate capture and storage from signal tap points in a radio system, in accordance with an embodiment of this disclosure. In some examples, part(s) of system architecture800can be used to implement part(s) of system architecture100, and/or system architecture200.

System architecture800comprises radio unit802(which can be similar to radio unit502ofFIG.5); tap point disposed within the digital front end chain804(which can be similar to tap point disposed within the digital front end chain504); first hardware component that is configured to selectively read the signal at the tap point to produce a read signal806(which can be similar to first hardware component that is configured to selectively read the signal at the tap point to produce a read signal506); second hardware component that is configured to store the read signal808(which can be similar to second hardware component that is configured to store the read signal508); third hardware component that is configured to determine a performance metric of the radio unit based on the stored signal812(which can be similar to third hardware component that is configured to determine a performance metric of the radio unit based on the stored signal712ofFIG.7); and fourth hardware component that is configured to alter operation of the radio unit814.

In some examples, fourth hardware component that is configured to alter operation of the radio unit814can be configured to alter operation of the radio unit based on the performance metric.

In some examples, fourth hardware component that is configured to alter operation of the radio unit814can be configured to increase an efficiency of the radio unit based on using artificial intelligence to determine network efficiency management based on the performance metric

In some examples, fourth hardware component that is configured to alter operation of the radio unit814can be similar to analysis and fault detection164, or power detection, analysis, and fault detection224.

FIG.9illustrates another example system architecture900that can facilitate capture and storage from signal tap points in a radio system, in accordance with an embodiment of this disclosure. In some examples, part(s) of system architecture900can be used to implement part(s) of system architecture100, and/or system architecture200.

System architecture900comprises first hardware component that is configured to selectively read a signal from a tap point that is disposed within a digital front end chain of a radio unit to produce a read signal902; and second hardware component that is configured to store the read signal904.

In some examples, first hardware component that is configured to selectively read a signal from a tap point that is disposed within a digital front end chain of a radio unit to produce a read signal902can be similar to capture142. In some examples, second hardware component that is configured to store the read signal904can be similar to storage170.

In some examples, the signal read by first hardware component902is time aligned at the tap point on a system time of the radio unit. This time alignment can be effectuated by a component similar to time alignment116or time alignment204.

In some examples, second hardware component904is configured to remove a cyclic prefix from the read signal before storing the read signal. In some examples, second hardware component904is configured to store the read signal with a cyclic prefix preserved. That is, part(s) of second hardware component904can be similar to optional FFT and CP removal162or optional FFT and CP removal220.

In some examples, the read signal spans one or more time boundaries of the radio unit. That is, data can be captured and stored to memory over a single time boundary or multiple time boundaries. In some examples, the read signal is aligned to a symbol or a system time boundary of the radio unit. That is, data can be aligned on a symbol or other system time boundaries.

Example Process Flows

FIG.10illustrates an example process flow1000that can facilitate capture and storage from signal tap points in a radio system, in accordance with an embodiment of this disclosure. In some examples, one or more embodiments of process flow1000can be implemented by system architecture100or system architecture200.

It can be appreciated that the operating procedures of process flow1000are 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 flow1000can be implemented in conjunction with one or more embodiments of process flow1100ofFIG.11.

Process flow1000begins with1002, and moves to operation1004.

Operation1004depicts identifying a tap point disposed within a digital front end chain of a radio unit, wherein the tap point is configured to perform time align a signal at the tap point with a system time of the radio unit. This can comprise identifying a tap point of system architecture100(e.g., tap point148A) or a tap point of system architecture200(e.g., tap point248A) to read a signal from.

In some examples, the tap point is disposed at an output of a crest factor reduction output signal block of the digital front end chain. That is, a tap point can be placed to read a CFR_OUT_Signal. This can be similar to tap point148C.

In some examples, the tap point is disposed at an output of a digital pre-distortion output signal block of the digital front end chain. That is, tap point148D can be placed to read a DPD_OUT_Signal.

In some examples, the tap point is disposed to capture an error signal transmitted through the digital front end chain. That is, a tap point can be placed to read an Error_Signal. This can be similar to tap point148F.

In some examples, the tap point is disposed at an output of a feedback received signal analog-to-digital converter of the digital front end chain. That is, a tap point can be placed to read a FBRX_IN_Signal. This can be similar to tap point148E.

After operation1004, process flow1000moves to operation1006.

Operation1006depicts selectively reading a signal from the tap point to produce a read signal. This can comprise capturing a signal that passes through a tap point, such as with capture142or capture218.

After operation1006, process flow1000moves to operation1008.

Operation1008depicts storing the read signal. This can comprise storing the read signal at storage170, or storage228.

After operation1008, process flow1000moves to1010, where process flow1000ends.

FIG.11illustrates another example process flow1100that can facilitate capture and storage from signal tap points in a radio system, in accordance with an embodiment of this disclosure. In some examples, one or more embodiments of process flow1100can be implemented by system architecture100or system architecture200.

It can be appreciated that the operating procedures of process flow1100are 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 flow1100can be implemented in conjunction with one or more embodiments of process flow1000ofFIG.10.

Process flow1100begins with1102, and moves to operation1104.

Operation1104depicts reading a first signal from a first tap point that is disposed within a digital front end chain and that corresponds to a first antenna of a radio unit. In some examples, a radio system can comprise multiple antennas, each having a corresponding radio unit (which can comprise a combination of an instance of system architecture100and system architecture200). In such examples, each signal chain for each antenna can have one or more tap points (e.g., similar to tap point148A, or tap point248A). In operation1104a digital front end chain of a first antenna can have a tap point from which a signal is read.

After operation1104, process flow1100moves to operation1106.

Operation1106depicts reading a second signal from a second tap point that is disposed within the digital front end chain and that corresponds to a second antenna of the radio unit. As described, a ratio system can comprise multiple antennas, such as a first antenna and a second antenna. With regard to the second antenna, in operation1106a digital front end chain of a first antenna can have a tap point from which a signal is read.

In some examples, operation1106comprises reading the first signal concurrently with reading the second signal. That is, multiple tap points in a radio system can be read at the same time, and this can include multiple tap points across multiple antennas.

After operation1106, process flow1100moves to1108, where process flow1100ends.

Example Architecture

FIG.12illustrates an example system architecture1200for using capture and storage of a signal from tap points for a digital twin and/or predictive modeling, and that can facilitate capture and storage from signal tap points, in accordance with an embodiment of this disclosure.

In some examples, system architecture1200can utilize signals captured in tap points in system architecture100, and/or system architecture200to produce a digital twin of a corresponding radio system and/or perform predictive modeling of the radio system.

System architecture1200comprises models1202, storage and analysis1204, distributed unit1206, radio unit1208, waveform/analysis/data storage1210A, waveform/analysis/data storage1210B, waveform/analysis/data storage1210C, waveform/analysis/data storage1210D, and central unit (CU)1212.

Tap points disposed in radio unit1208and/or distributed unit1206can be used to capture signals. This information can be transmitted to central unit1210for storage and analysis1204. Storage and analysis1204can produce models1202. Models1202can be digital twins of radio systems, including a radio system comprising distributed unit1206and radio unit1208. Models1202can also be other forms of modeling of a radio system to be used in predictive modeling of how the radio system will behave in the future (e.g., how it will perform, or whether it will need repair).

A digital twin can generally comprise a computer model of a radio system (rather than an actual physical radio system), and can be used to estimate how the corresponding physical radio system will behave.

Captured signals can also be stored and/or analyzed in various locations at waveform/analysis/data storage1210A, waveform/analysis/data storage1210B, waveform/analysis/data storage1210C, and/or waveform/analysis/data storage1210D.

CONCLUSION

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.

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.

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.

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.

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.

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.

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.

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.