Patent ID: 12191928

OVERVIEW

Detailed Description

The technology described herein is generally directed towards a process to collect, synchronize and/or analyze data, such as power data, in the frequency domain of a radio system. The technology described herein can perform such operations in a hardware accelerated manner. That is, radio system reliability, serviceability and manageability are all aspects of a functioning radio system of a cellular system that are important both to the user and the provider. These aspects can benefit from knowledge, information and/or data/metadata gained from tracking, collecting, mapping and/or analyzing performance of a radio system. That is, there is a desire to measure radio performance, and/or to generate and/or store data in one or more ways that allow for comparative analysis of such data (including metadata) that is collected from different sources, at different time points, and/or relative to one or more other dynamic and/or changing variables.

The data collected and/or statistically accumulated, and/or the results of analysis of the data, can allow for real-time, immediate, short term and/or long term improvements, troubleshooting and/or predictive modeling regarding radio system performance, failures, issues, continuity and/or other aspects. For example, the resulting statistically accumulated data, such as telemetry, radio frequency (e.g., analog data) and/or digital performance and/or comparative data, and/or underlying infrastructure utilization statistics can be used to improve network performance, plan network capacity, and/or identify new service opportunities, relative to the radio system. Various types of data can be collected, such as, but not limited to, data represented in a frequency domain (FD) and/or data represented in a time domain (TD).

Relative to data collection in the frequency domain, in existing radio systems, a highest system resolution is generally 1 subcarrier (SC). The data obtained from such resolution can be limiting.

Generally, one or more embodiments described herein are directed to detection, statistical analysis, and storage of radio system power data in the frequency domain. The power data can be synchronized along system timing boundaries. Generally, the power data can be employed to provide proactive and reactive responses, updates and/or troubleshooting of a respective radio system of a cellular system. More particularly, one or more embodiments here can facilitate an ability of a service provider (of a radio system) to precisely extract power of a signal at a predetermined frequency and/or multiple frequencies, and to resolve that data on a subcarrier by subcarrier (SC/SC) basis. In one or more embodiments, power of an SC, multiple SC's, between an SC and one or more SC's, and/or between multiple SC's can be measured, which data can be used, as mentioned above, relative to managing performance, system operation, maintenance and customer experience of the respective radio system.

That is, in one or more embodiments, power detector data can be accumulated (e.g., read and recorded, and selectively binned) on a SC by SC basis over time, such as gathering power data of every symbol going into the power amplifier (PA) at one or more frequencies. Simultaneously and/or synchronously, power data can be gathered that is fed back from the PA. Additionally and/or alternatively, such power data can be looped to an uplink (UL) path for forwarding to an analysis block and simultaneously and/or synchronously gathered.

Using the one or more embodiments described herein, such statistically analyzed data can not only be collected and measured, but also recorded, stored and recalled, such as automatically and/or employing artificial intelligence, machine learning, deep learning and/or the like to proactively and/or reactively address the performance, system operation, maintenance and customer experience of the respective radio system.

To provide these one or more operations and/or features, reference throughout this specification to “one embodiment,” “an embodiment,” “one implementation,” “an implementation,” etc. means that a particular feature, structure, or characteristic described in connection with the embodiment/implementation can be included in at least one embodiment/implementation. Thus, the appearances of such a phrase “in one embodiment,” “in an implementation,” etc. in various places throughout this specification are not necessarily all referring to the same embodiment/implementation. Furthermore, the particular features, structures, or characteristics may be combined in any suitable manner in one or more embodiments/implementations.

As used herein, with respect to any aforementioned and below mentioned uses, the term “in response to” can refer to any one or more states including, but not limited to: at the same time as, at least partially in parallel with, at least partially subsequent to and/or fully subsequent to, where suitable.

As used herein, the term “entity” can refer to a machine, device, smart device, component, hardware, software and/or human.

As used herein, the term “cost” can refer to power, money, memory, processing power, thermal power, size, weight and/or the like.

As used herein, the term “resource” can refer to power, money, memory, processing power and/or the like.

Example Radio System Architectures

One or more embodiments are now described with reference to the drawings, where like referenced numerals are used to refer to like elements throughout. In the following description, for purposes of explanation, numerous specific details are set forth to provide a more thorough understanding of the one or more embodiments. It is evident, however, in various cases, that the one or more embodiments can be practiced without these specific details.

Further, the embodiments depicted in one or more figures described herein are for illustration only, and as such, the architecture of embodiments is not limited to the systems, devices and/or components depicted therein, nor to any particular order, connection and/or coupling of systems, devices and/or components depicted therein. For example, in one or more embodiments, the non-limiting system architecture100as illustrated atFIG.1, and/or systems thereof, can further comprise one or more computer and/or computing-based elements described herein with reference to an operating environment, such as the operating environment900illustrated atFIG.9. In one or more described embodiments, computer and/or computing-based elements can be used in connection with implementing one or more of the systems, devices, components and/or computer-implemented operations shown and/or described in connection withFIG.1and/or with other figures described herein.

Turning now toFIG.1, a high-level radio system architecture is illustrated at100. The radio system100can comprise a distributed unit (DU) signal injection portion104(also herein referred to as a DU portion104) and a radio unit (RU)101. The RU101can comprise a radio unit (RU) signal injection portion106(also herein referred to as an RU signal injection portion106), the radio control108, and an RU signal capture portion110. Generally, the DU portion104can provide both baseband processing and RF functions. The RU signal capture portion110can take signals from a respective antenna120and convert the RF signal into a data signal, and vice versa. The RU signal capture portion110can have one or more statistical counters, accumulators, counter circuits and/or the like.

In one or more embodiments, the RU signal capture portion110can analyze data captured, such as via historical information. This analysis and data gathering can be performed at least partially autonomously, such as majoratively and/or fully autonomously, such as absent input from the DU portion104and/or any centralized unit (CU). In one or more embodiments, the radio control108, in view of information received from the RU signal capture portion110, can place an order for service, maintenance, hardware and/or firmware to a core data center112. In one or more embodiments, the radio control108, in view of information received from the RU signal capture portion110, can at least partially autonomously request or request and receive one or more software, firmware and/or other system updates. Together, the DU portion104and RU portion106can provide data to, and receive data from, the core datacenter112.

Turning next toFIG.2, an example of a radio data analysis system architecture is illustrated at200, with description being provided below. The radio data analysis system200can be part of the radio system100(e.g., ofFIG.1) or can be at least partially external to the radio system100. For purposes of brevity, additional aspects of the radio system100(e.g., as illustrated atFIG.1) are not illustrated atFIG.2. While referring here to one or more processes, operations, facilitations and/or uses of the non-limiting system architecture200, description provided herein, both above and below, also can be relevant to one or more other non-limiting system architectures described herein.

FIG.2illustrates a schematic of the radio data analysis system200for detecting, reading and gathering power data in the frequency domain relative to one or more subcarriers and relative to time aligned relative to time boundaries of the radio system100. Generally, the power data in the frequency domain can be read and collected at various tap points of the radio system, where the power data is natively in the frequency domain.

Generally, the radio data analysis system200can comprise any suitable computing devices, hardware, software, operating systems, drivers, network interfaces and/or so forth. However, for purposes of brevity, only components generally relevant to frequency domain power data detection, collection and/or analysis are illustrated inFIG.2. For example, the radio data analysis system200can comprise a processor207, memory209, power detector210, read circuit211, identification circuit212, fast Fourier transform/frequency offset (FFT/FO) component216, analysis component218and/or accumulator/counter circuit220.

Discussion first turns to the processor207, memory209and bus205of the radio data analysis system200.

In one or more embodiments, radio data analysis system200can comprise the processor207(e.g., computer processing unit, microprocessor, classical processor and/or like processor). In one or more embodiments, a component associated with radio data analysis system200, as described herein with or without reference to the one or more figures of the one or more embodiments, can comprise one or more computer and/or machine readable, writable and/or executable components and/or instructions that can be executed by processor207to facilitate performance of one or more processes defined by such component(s) and/or instruction(s). In one or more embodiments, the processor207can comprise the identification circuit212, fast Fourier transform/frequency offset (FFT/FO) component216, analysis component218and/or accumulator/counter circuit220.

The processor207can be configured to control one or more components/elements of the radio data analysis system200, such as the power detector210, read circuit211, identification circuit212, fast Fourier transform/frequency offset (FFT/FO) component216, analysis component218and/or accumulator/counter circuit220. That is, the processor207can be configured to control collection of power data relative to the radio system100, such as relative to a subcarrier250of the radio system100. For example, the processor207can be configured to control collection of power data in the frequency domain at a frequency of a subcarrier250and/or at a frequency, sub-frequency or frequency range between subcarriers. As used herein, “between subcarriers” can refer to being between a subcarrier and another subcarrier other than the subcarrier, where the another subcarrier is a next higher or next lower subcarrier of the radio system (e.g., according to the subcarrier spacing of the radio system100, such as 30 KHz spacing or numerology 1 spacing).

In one or more embodiments, the radio data analysis system200can comprise the machine-readable memory209that can be operably connected to the processor207. The memory209can store computer-executable instructions that, upon execution by the processor207, can cause the processor207and/or one or more other components of the radio data analysis system200(e.g., power detector210, read circuit211, identification circuit212, fast Fourier transform/frequency offset (FFT/FO) component216, analysis component218and/or accumulator/counter circuit220) to perform one or more actions. In one or more embodiments, the memory209can store one or more computer-executable components.

Radio data analysis system200and/or a component thereof as described herein, can be communicatively, electrically, operatively, optically and/or otherwise coupled to one another via a bus205to perform functions of non-limiting system architecture200, radio data analysis system200and/or one or more components thereof and/or coupled therewith. Bus205can comprise one or more of a memory bus, memory controller, peripheral bus, external bus, local bus and/or another type of bus that can employ one or more bus architectures. One or more of these examples of bus205can be employed to implement one or more embodiments described herein.

In one or more embodiments, radio data analysis system200can be coupled (e.g., communicatively, electrically, operatively, optically and/or like function) to one or more external systems (e.g., a system management application), sources and/or devices (e.g., classical communication devices and/or like devices), such as via a network. In one or more embodiments, one or more of the components of the non-limiting system architecture200can reside in the cloud, and/or can reside locally in a local computing environment (e.g., at a specified location(s)).

In addition to the processor207and/or memory209described above, radio data analysis system200can comprise one or more computer and/or machine readable, writable and/or executable components and/or instructions that, when executed by processor207, can facilitate performance of one or more operations defined by such component(s) and/or instruction(s).

Turning now to additional elements of the radio data analysis system200, frequency domain (FD) power detection can be performed on data within a data stream of a digital front end (DFE) of a radio system, where such data is natively in frequency domain. Ability to detect power in the frequency domain can allow for the ability to precisely extract the power of a signal at a predetermined frequency or set of frequencies. Power detection can be implemented at a location coupled to, but spaced from, such as coupled near, an input to the radio system, such as at a DFE's inverse fast Fourier transform (iFFT) block, or coupled to, such as coupled near, an output of the radio system at a DFE's FFT block. Time alignment of this data can enable input to output data comparison.

At the native sampling rate, frequency resolution can be equal to the highest system resolution of 1 subcarrier (SC) per frequency bin. However, data can be initially captured and/or subsequently resolved, such as at the FFT/FO component216, at a granularity below that of 1 sub carrier, thus allowing inspection of energy between frequency bins. In one or more examples, such inspection can be useful for system performance phase noise measurements.

As used herein, a subcarrier is a sideband of a radio frequency carrier wave, which can be modulated. An operating radio system, such as the radio system100, can have a plurality of subcarriers, such as subcarriers250numbered from 0, 1, 2 . . . to j. Subcarrier spacing at the radio system100can be based on the numerology configuration of the system. Accordingly, FD power data gathered can be in the format signed 16 bit I+Q for each subcarrier, one, some, or all of the available subcarrier frequencies may be selected for detection and ultimately for storage.

Additionally, generally at a radio system, the more subcarriers that can be packed into a frequency range (i.e., the narrow subcarrier spacing used), the more data that can be transmitted and/or received. In one example, the radio system100can have subcarrier spacing of about 30 KHz or numerology 1. Based on physics (e.g., anti-proportional relationship between subcarrier spacing and orthogonal frequency division multiplexing—OFDM—symbol length), narrow subcarrier spacing can correspond to longer OFDM symbol length. Longer OFDM symbol length can correspond to additional spacing for CP (cyclic prefix). With longer CP, the signal can be more tolerable to a fading channel.

Turning now to the identification circuit212, such circuit can be communicatively coupled to the processor207and can be controlled by the processor207to identify and/or detect one or more frequencies of the radio107of the radio system100. For example, the identification circuit212can be configured to identify power data of one subcarrier separately from power data relative to or from one or more other subcarriers. In one or more embodiments, the identification circuit212can be part of and/or comprised by the power detector210, and thus the aforementioned operations can be performed by the read circuit211. In one or more embodiments, the identification circuit can be part of the read circuit211, and thus the aforementioned operations can be performed by the read circuit211.

Turning next to the power detector210, which can be a frequency domain (FD) power detector, while the FD PD210is shown as part of the radio data analysis system200the power detector210can be additionally and/or alternatively part of the RU signal capture portion110.

Power detectors are RF components that can convert an RF input signal into an output DC voltage and/or a digital and/or digitized representation thereof that can be proportional to the incident RF power. Power detectors can be employed for operations relative to automatic gain control circuits, transmit antenna power monitoring, and/or protecting sensitive circuits from pulses and/or power spikes.

The power detector210can be any suitable power detector, such as conventionally known by those having skill in the art. In one or more embodiments, the power detector210can be capable of reading frequency domain power data. In one or more embodiments, the power detector210can be capable of also reading time domain power data. In one or more embodiments, the power detector210can be configured to read and/or detect RMS current data and/or peak current data. That is, the power detector210can be both RMS and peak, temporally and/or over frequency.

The power detector210can be coupled to a digital front end (DFE) uplink (UL) or downlink (DL) chain, such as of the radio107, for accessing the plurality of subcarriers250of the radio107. For example, as illustrated atFIGS.4and6, the power detector210can be comprised by and/or separate from the power detectors409and609, to thereby access a subcarrier250at the DL chain400(FIGS.4and5) and/or UL chain600(FIGS.6and7).

These schematics ofFIGS.4to7show an additional layer of detail as compared to the schematic illustration ofFIG.3. It is noted that the DL chain400and UL chain600have are separately shown, and also are split into portions for purposes of detailed illustration. For example, DL chain portions400aand400band UL chain portions600aand600bare coupled to one another at connection points402,404,406,406,502,602,604and606.

The power detector210can comprise a read circuit211. The read circuit211can be communicatively coupled to the processor207and can be at least partially controlled by the processor207to read, at the radio system100, such as at the fronthaul, UL chain600and/or DL chain400, power data in a frequency domain. This power data can be native power data at the fronthaul, UL chain600and/or DL chain400. The power data can be read by the read circuit211relative to a subcarrier.

As illustrated atFIG.3, one or more power detectors210, and thus also respective read circuits211, can read data from a temporal FD data stream302. The power detectors210can be coupled at a respective DFE chain304near an FFT component306. Briefly, as shown atFIGS.4and6, and also as indicated above, one or more power detectors210for detecting power data in the frequency domain can be coupled following the FFT component612(FIG.6) and/or preceding the iFFT component412(FIG.4). The power detectors210can be configured to employ one or more databases, such as a waveform/RB/RE database308to therefore detect, recognize and/or convert data from the temporal FD data stream302to power data in the frequency domain.

The power data can be read by the read circuit211/power detector210at a frequency of a subcarrier250and/or at a frequency, sub-frequency or frequency range between subcarriers. As used herein, “between subcarriers” can refer to being between a subcarrier and another subcarrier other than the subcarrier, where the another subcarrier is a next higher or next lower subcarrier of the radio system (e.g., according to the subcarrier spacing of the radio system100, such as 30 KHz spacing or numerology 1 spacing). That is, the read circuit can be configured to read the power data at a sub-subcarrier granularity of the radio system100.

As illustrated atFIGS.4and7, frequencies of and/or between subcarriers of the respective DL chain400and UL chain600, e.g., over a known time range relative to symbols in the frequency domain420and620, can be read/detected by the read circuits211/power detectors210of the radio data analysis system250. That is, each symbol can represent and/or comprise an entire array of unique subcarriers, such as 0 to N or 0 to 4095 as depicted inFIG.8.

In one or more embodiments, a fast Fourier transform component or a frequency offset (FFT/FO) component216can be communicatively coupled to the processor207and configured to resolve power data collected between one subcarrier and another subcarrier into a bin defined at least partially by the frequency range. In this way, sub-subcarrier granularity frequencies can be analyzed. Indeed, periodic temporal data may not be enough resolution and higher resolution may be desired and, in such case, a higher sampling rate can be employed to resolve power data in the desired sampling bins, such as higher resolution sampling bins. It is noted that the FFT/FO component216atFIG.2can be the same as the FFT component612atFIG.6, and/or the FFT component atFIG.6likewise can be communicatively coupled to the processor207and configured to resolve power data collected between one subcarrier and another subcarrier into a bin defined at least partially by the frequency range. In this way, sub-subcarrier granularity frequencies can be analyzed. When referring to bins, such bins can be storage, portions of storage, memory, portions of memory and/or the like, such as memory209, storage702, and/or signal data storage414.

In one or more embodiments, the read circuit211can perform one or more calculations directed to determining the power data in the frequency domain from information, signals and/or the like detected by the power detector210.

For example one or more of the below Equations 1 to 3 can be employed.
Power_n(dB)=10 Log 10(In/327682Qn/327682);  Equation 1
SymbolJ_Power_Subcarrier_nRMS(dB)=10 Log 10(Σ0J10((Symbolj_Power_n)/10)/J);  Equation 2

Equation 3: SymbolJ_Power_Subcarrier_n peak (dB)=|JMax(10 Log 10(In/327682+Qn/327682)). As noted above, FD power data can be gathered based on RMS current or peak current specifications. As such, the power detectors210can be configured for RMS power and/or peak power applications.

In one or more embodiments, TD data can be frequency shifted (DDC or DUC), filtered (FIR, HB), and/or decimated (/x) to select a sub-band, or lessen the amount of data collected as a requirement. An alternative desirable data processing option can be to sub-band (filter) the TD data and over sample before transformation to FD thus increasing the frequency bin resolution to that less than 1 SC.

In one or more embodiments, a read circuit211of the respective read circuits211, can be configured to identify and/or to separately record peaks of power data that exceed one or more selected power data unit thresholds in the frequency domain. For example, this identification can be performed prior to initial storage and/or after initial storage. This “pre-conditioning” of data can allow for rapid analysis of bulk data, such as in a relatively real time fashion and/or at any other subsequent point in time, to thereby determine one or more current and/or historical characteristics of the radio system100, such as radio system100operation, relative to the FD power data.

Furthermore, the power detector210and read circuit211can be configured to read the power data in the frequency domain relative to a selected and/or known time range of the radio system100and or gateable event (e.g., defined by a selected and/or known time range of the radio system100) of the radio system100.

That is, the FD power data can be detected within a known time boundary over which respective measurement conditions are known and understood. In this way, capturing data across these time boundaries, and thus provision of an undetermined set of information, from one or more different symbols, can be avoided. Instead, synchronization of FD power data, such as between UL and DL chains can be performed and/or otherwise provided.

For example, referring briefly toFIG.8and the graph800, in one or more embodiments of the radio system100, FD power data can be read/gathered/collected at defined time ranges along the time domain. This can thus allow for defined collection of the various frequency domain data sets802, based on known increments or symbols in the time domain. For example, the time range can be defined by an upper limit of time and a lower limit of time of the radio system100. The upper limit of time and the lower limit of time of the time range can be aligned at inherent and/or generated time boundaries of the radio system. An increment of the selected time range can a period of one symbol of time, such as is illustrated atFIG.8. In one or more embodiments, power data can be detected along time boundaries as narrow as, but not limited to a signal symbol-time in the context of 5G cellular.

For example, as illustrated briefly atFIG.9, various PD data, e.g., from the labeled power detectors409,609can be gathered relative to various subcarriers (and/or relative to sub-subcarrier granularity) at defined time ranges, such as the symbol periods of time illustrated atFIG.9.

In one or more embodiments, one or more gathered/read sets of power data can be time aligned relative to one or more other gathered/read sets of power data (e.g., data from UL chain600vs data from DL chain400). For example, as shown atFIGS.4to7, time alignment can be performed on the collected data, such as relative to430and/or630. For example, blocks430and630can be blocks that collect information for time alignment (e.g., gating and/or markers) that can subsequently be used to accelerate processing of the data. It will be appreciated that such time alignment can be performed during power data collection before initial power data storage and/or after power data is initially stored.

Indeed, FD power detection can be desirable over TD power detection as the FFT portion of the analysis heavy lifting can performed in the DFE using DFE blocks, and therefore would not need to be performed in SW or be further post-processed.

Also, indeed, such symbol/symbol alignment can ensure that the power data being compared/contrasted captured from different tap points can produce relevant and comparable results. Such comparison can be between UL and DL data and/or between data at different historical points in time. For example, DFE data in the FD prior to iFFT on the DL and following the FFT block on the UL can be only valid within the radio system's time boundary of a symbol.

Via collecting valid FD power data over time, some or all of the subcarriers (SCs) can be collected along a symbol period in a single instant in time. It is briefly noted that further data manipulation can be performed such as, but not limited to, averaging, and statistical counting and/or accumulation and/or analysis of in-band and/or out of band performance directly from the data and/or as selectively as down to a single SC.

Discussion now turns to statistical accumulation (e.g., statistical analysis of the FD power data and storage thereof) by the radio data analysis system200.

The analysis component218can be communicatively coupled to the processor207and can be configured to compare the power data in the frequency domain to a power threshold. Such power threshold can be a root-mean-square (RMS) threshold or a peak value threshold. Based on a result of the power data being compared to the power threshold, the analysis component218can thus sort the power data into bins at a storage component communicatively coupled to and/or accessible to the processor207. That is, the power threshold can be applied to separate the power data into root-mean-square or a peak values.

An advantage of the threshold counters can be to measure long term traffic load distribution by “binning” as shown in a typical Histogram, based on the settable threshold or thresholds. The result of the RMS and peak power detector measurements over a temporal period can then be stored in a suitable storage medium. It is noted that binning may be of a dimension covering many power ranges.

For purposes of illustration, turning again toFIG.3, one or more thresholds314can be applied by the analysis component218to thereby sort power data in the frequency domain into various bins, such as upper threshold bin316and lower threshold bin318. Indeed, as illustrated atFIG.9, additional bins can be employed, such as employing different bins for different thresholds or threshold types. This can include different RMS thresholds, different peak thresholds, different thresholds for different subcarriers250, for different groups of subcarriers250, and/or for any combination thereof.

For example, if a power detector measurement is above the prescribed or programed threshold a “RMS_UpperCounter” can incremented. If the measurement is below the threshold a “RMS_LowerCounter” can be incremented.

For another example, if a power detector measurement is above the prescribed or programed threshold a “Peak_UpperCounter” can be incremented. If the measurement is below the programed threshold a “Peak_LowerCounter” can be incremented.

Furthermore, in one or more embodiments, such bins910(FIG.9) can be temporary wherein the accumulator circuit or the counter circuit220can be configured to generate an interrupt signal triggering a copying or transferring of the power data from one or more of the bins910to one or more other bins, such as long-term storage bins or historical analysis bins. That is, put another way, an exemplary result of an interrupt may be to trigger a capture or data dump to more permanent memories or flight recorder.

Additionally, in one or more embodiments, the analysis component218can be configured to compare the power data in the frequency domain prior to stored power data in the frequency domain at a suitable storage component, such as the bins910, memory209, storage702, storage414and/or the like. For example, based on the known time ranges of the data, and thus such datas being time aligned relative to one another, one or more current datas can be compared to one or more historical datas, such as automatically, such as at any suitable comparison frequency. One or more thresholds can be employed for such comparison, with one or more triggers being initiated, such as by the analysis component218, in response to one or more of such thresholds being met and/or exceeded. These operations can allow for automatic “pre-conditioning” of statistical data based on previously gathered data, which “pre-conditioned” data can be used in real time and/or at any subsequent time thereafter. In one or more embodiments, analysis of statistical data captured can be employed to generate, such as by the analysis component218, a histogram distribution of power data detected. That is, data can be analyzed over time to determine radio system performance or beneficial system performance modifications.

It is noted that in one or more embodiments, frequency domain power data prior to any analysis operations (e.g., “pre-conditioning” operations”) also can be stored, such as separately from analyzed data. This “clean” data can be stored at any suitable storage component, such as the bins910, memory209, storage702, storage414and/or the like. This “clean” data can be used in connection with and/or separately from the “pre-conditioned” data. The “clean” data can be recalled at any suitable time for analysis and/or other use.

Next, an accumulator or counter circuit220can be communicatively coupled to the processor207and can be configured to record power data quantities stored at one or more of the bins at the suitable storage component. That is, power detector data can pass through a threshold filter where the output can further be counted and the count accumulated in an accumulator for ease of statistical analysis over time. It is noted that the power detector data can be assessed by the accumulator or counter circuit200before being binned and/or after being binned, such as where the data is recalled to the accumulator or counter circuit200after being binned.

Different counter circuits200can be employed for different subcarriers and/or for different analysis components218. Thus, different analysis components218can be employed for different subcarriers and/or power detectors, where suitable.

Counter width can be dimensioned to capture sufficient information (e.g., a selected quantity) on performance parameters. For example, 15 minute intervals/histograms at 60 kHz subcarrier spacing (SCs) can be an exemplary temporal setting. Counter circuits200can be gateable in synchronization with radio system timing and states. An exemplary case can be Tx_ON/Rx_ON states, where Tx refers to “transmit” and Rx refers to “receive”.

In one or more embodiments, the aforementioned “clean” frequency domain power data likewise can be submitted, transmitted and/or otherwise sent to the accumulator or counter circuit200prior to and/or after initial storage. For example, mere quantity of “clean” data can be “counted” and/or otherwise tracked. Storage of such counted “clean” data can be separate any of the aforementioned datas.

In one or more embodiments, threshold measurements can also be used for measuring occurrence of extreme conditions or “spikes” in the power data detected. In one or more embodiments, the analysis component218and/or the counter circuit200can generate an interrupt or flag based on meeting and/or exceeding one or more of the sorting thresholds or based on one or more separate interrupt thresholds. In an exemplary case, detection can involve triggering a system event that affects system performance. In one or more embodiments, a trigger may not be generated by the analysis component218and/or the counter circuit200until a selected quantity of threshold interrupt events are statistically counted.

In one or more embodiments, the analysis component218can enhance accuracy of the power data in the frequency domain that is detected by using information from the C-plane of the radio system (e.g.,FIG.7). In one or more embodiments, information from the C-Plane can be employed to accumulate data in a more precise fashion. For example, operation boost and reduction of power can not be considered for Tx-blanking info and therefore can be a possible source of error in power detection or traffic estimation applications. For another example, such data from the C-plane can be employed to further enhance the accuracy of power detected associated with data for reduced resource block (RB) count, which power can be not necessarily reduced due to boost.

As used herein, a resource block can comprise a collection of sequential subcarriers in frequency domain, such as 12 sequential subcarriers in frequency domain, and thus an RB can be a dimension of a chunk(s) of subcarriers. Additionally, a resource element (RE) can be equal to a single subcarrier. Resource blocks can thus be comprised of resource elements.

Again referringFIGS.4to7, and alsoFIG.2, collected/read/gathered/statistically analyzed data can be stored. As indicated above, one or more calculations and/or analysis can be performed during collection, prior to initial storage and/or after initial storage. Storage employed can be configured for recall of data for subsequent use and/or analysis. For example, the power data can be stored at a memory (e.g., memory209) communicatively coupled to the processor207and configured to receive and store the power data in the frequency domain from the read circuit211. The memory and/or other storage can initially be short-term memory, and thus a long-term memory230can be employed to which power data can be moved from the temporary or short-term memory. The long-term memory can be configured to store data longer than the temporary or short-term memory.

Referring next toFIG.10, additional detail is provided relative to the power detectors409,609, at which a power detector210can be located and/or coupled, as indicated above. As illustrated, one or more additional operations can be performed, such as by one or more components of the radio data analysis system200, prior to or via recall from storage1010. It is noted that store1010can be any of memory209, storage414, storage702and/or other storage. The one or more operations can comprise (and/or be employed for) a frequency mask, buffering, CP removal, applying a frequency domain mask, fault and flag analysis for interrupt instantaneous peak, power monitoring, analysis and fault detection, radio optimization control and actuation, and/or the like.

Referring now again toFIG.2, in one or more embodiments, a group of power detectors210, as illustrated atFIG.2, can be collectively configured to control collection of power data from a group of subcarriers250of the radio system100. The power detectors210of the group of power detectors can comprise respective read circuits211that can be configured to read the power data in a frequency domain, of a single subcarrier250of the group of subcarriers, or of a single frequency range between a successive pair of subcarriers250of the group of subcarriers, along a common selected time range having boundaries that are aligned at time boundaries of the radio system100. The respective read circuits211can be further configured to read the power data in the frequency domain to a memory (e.g., memory209or other storage) communicatively coupled to and configured to receive and store power data from at least one subcarrier250of the group of subcarriers. In such case, one or more identification circuits212can be communicatively coupled to power detectors210of the group of power detectors and configured to identify power data in the frequency domain for respective subcarriers250or a frequency range separately from power data in the frequency domain for one or more other subcarriers or frequency ranges of the radio system. In an exemplary case a radio data analysis system200can record power for one, some, or all subcarriers250, such as simultaneously.

The power detectors210of the group of power detectors can comprise statistical counters200that can be configured to receive the respective frequency domain power data having been sorted according to a power threshold, such as by the analysis component218. In one or more embodiments, the statistical counters can be configured to accumulate respective counts of power data values at bins of a group of suitable data storage components. For example, a first number of the statistical counters can be set relative to a second number of the bins to result in the system200comprising at least one statistical counter per bin of the data storage component.

In one or more embodiments, a group of radio data analysis system200can be provided at a radio system (e.g., radio system100). Each radio data analysis system200of the group of systems can be configured to read and record power data in the frequency domain along respective different selected time ranges that are each aligned at the radio system's (e.g., radio system100) time boundaries.

In one or more embodiments, any of the aforementioned detecting and reading can be implemented at plural radio antenna branches of a same radio system, a different radio system, or relative to two or more carriers employing at least the radio system. In an exemplary case a radio data analysis system200can record power for one, some, or all antenna branches, such as simultaneously.

In one or more embodiments, the radio data analysis systems200, such as the processor207, can combine, such as at the memory209and/or other storage first power data in the frequency domain with second power data in a time domain of the same radio system100, wherein the time domain can comprise the defined time ranges of the radio system100. In an exemplary case, signals when combined with TD (time domain) power detect and/or combined with open radio access network (ORAN) blocks and/or transmit (Tx) blanking information can enable aspects of determination of performance aspects of the radio system100not limited to system operations and/or maintenance.

Turning now toFIG.11, a process flow comprising a set of operations is illustrated relative toFIG.2for detecting, statistically analyzing, and storing time-aligned frequency domain power data, such as where the power data is natively in the frequency domain. One or more elements, objects and/or components referenced in the process flow1100can be those of system100and/or system200. Repetitive description of like elements and/or processes employed in respective embodiments is omitted for sake of brevity.

At operation1102, the process flow1100can comprise reading, by a system comprising a processor (e.g., read circuit211), power data in a frequency domain relative to a subcarrier of a radio system of a radio system (e.g., radio system100).

At operation1104, the process flow1100can comprise reading, by the system (e.g., read circuit211), the power data in the frequency domain at a frequency of the subcarrier of the radio system or at a frequency range spaced between the subcarrier and another subcarrier of the radio system other than the subcarrier, wherein the subcarrier and the other subcarrier are successive ones of subcarriers of the radio system.

At operation1106, the process flow1100can comprise resolving, by the system at the radio system (e.g., FFT/frequency offset component216), power data collected between the subcarrier and the other subcarrier into a bin defined at least partially by the frequency range.

At operation1108, the process flow1100can comprise analyzing, by the system (e.g., analysis component218), at the radio system, power data in a frequency domain, relative to a subcarrier of the radio system, and according to a power threshold.

At operation1110, the process flow1100can comprise conducting, by the system (e.g., analysis component218), the analyzing prior to storage at the storage component of the power data in the frequency domain or after initial recording to the storage component of the power data in the frequency domain.

At operation1112, the process flow1100can comprise, based on a result of the power data being compared to the power threshold, sorting, by the system (e.g., accumulator/counter circuit220), the power data as root-mean-square power data or peak power data into bins at a storage component communicatively coupled to the processor.

At operation1114, the process flow1100can comprise enhancing, by the system (e.g., analysis component218), accuracy of the power data in the frequency domain that is detected by using, by the system, information from the C-plane of the radio system.

At operation1116, the process flow1100can comprise storing, by the system (e.g., memory209and/or read circuit211), the power data in the frequency domain at a storage component, wherein the power data in the frequency domain is stored into a group of bins based on the analysis of the power data in the frequency domain.

At operation1118, the process flow1100can comprise counting, by the system (e.g., accumulator/counter circuit220), respective quantities of power data values at respective bins of the group of bins.

At operation1120, the process flow1100can comprise triggering, by the system (e.g., accumulator/counter circuit220), a copying of or transferring of the power data from at least one of the group of bins, based on a counter threshold of a specified count of power values binned being reached or exceeded.

At operation1122, the process flow1100can comprise triggering, by the system (e.g., analysis component218and/or accumulator/counter circuit220), based on a power value threshold being met or exceeded, an interrupt flag to trigger a system modification event in response to the triggering of the interrupt flag.

For simplicity of explanation, the computer-implemented methodologies and/or processes provided herein are depicted and/or described as a series of acts. The subject innovation is not limited by the acts illustrated and/or by the order of acts, for example acts can occur in one or more orders and/or concurrently, and with other acts not presented and described herein. The operations of process flows of diagrams1100are example operations, and there can be one or more embodiments that implement more or fewer operations than are depicted.

Furthermore, not all illustrated acts can be utilized to implement the computer-implemented methodologies in accordance with the described subject matter. In addition, the computer-implemented methodologies could alternatively be represented as a series of interrelated states via a state diagram or events. Additionally, the computer-implemented methodologies described hereinafter and throughout this specification are capable of being stored on an article of manufacture to facilitate transporting and transferring the computer-implemented methodologies to computers. The term article of manufacture, as used herein, is intended to encompass a computer program accessible from any machine-readable device or storage media.

In summary, technology described herein can detect and statistically analyze frequency domain power data for enabling real-time adjustment of one or more parameters of a radio system. In an embodiment, a system can comprise a processor and a read circuit communicatively coupled to the processor, wherein the processor controls the read circuit to read power data in a frequency domain from a radio system, and an analysis component communicatively coupled to the processor and that compares the power data in the frequency domain to a power threshold, wherein, based on a result of the power data being compared to the power threshold, the analysis component sorts the power data into bins at a storage component communicatively coupled to the processor. In one or more embodiments, power data in the frequency domain is collected at a frequency of a subcarrier and/or at a frequency between subcarriers.

As a result, a method can be provided to read, collect, statistically analyze, and store power data information for immediate and/or later analysis. One or more actions can be taken relative to the data, to assist with radio system frequency, maintenance, customer experience and/or the like. In one or more embodiments, one or more actions can be triggered, such as relative to a quantity, quality and/or other aspect of the data read, collected and/or stored. A practical application of one or more techniques performed by one or more embodiments described herein can be collection of datas being time-aligned to one another relative to a plurality of subcarriers of a radio system.

Another practical application can be collecting statistics of current traffic of DL and UL on the RU side instead of the DU side of a respective radio system, such as where frequency domain data is native (e.g., on the DL/UL side). In this way, information can be gathered “upfront” to allow for any parameter adjustment. Such practical application can comprise the gather and collecting of FD power data, and thus the building of FD power data statistics over time. Furthermore, in view of statistical analysis performed, one or more triggers can be implemented, such as for review and/or for automatic conditioning, modification, adjustment and/or the like of one or more aspects, parameters and/or characteristics of a respective radio system.

Such comparable data can be beneficial for a variety of applications, as described herein. For example, radio systems typically employ large quantities of power, and the one or more embodiments described herein can, through data collection and storage, facilitate reducing power consumption of a respective radio system. This can be facilitated through performance enhancements, firmware changes and/or upgrades, and/or over the air updates to customer equipment in the field (e.g., which are employing and/or can employ the respective radio system). Particular advantages can comprise, but are not limited to, reduction of occurrence/rate of no fault found (NFF) returns, cost of field returns, and/or customer outage occurrences/times.

The systems and/or devices have been (and/or will be further) described herein with respect to interaction between one or more components. Such systems and/or components can include those components or sub-components specified therein, one or more of the specified components and/or sub-components, and/or additional components. Sub-components can be implemented as components communicatively coupled to other components rather than included within parent components. One or more components and/or sub-components can be combined into a single component providing aggregate functionality. The components can interact with one or more other components not specifically described herein for the sake of brevity, but known by those of skill in the art.

One or more embodiments described herein are inherently and/or inextricably tied to computer technology and cannot be implemented outside of a computing environment. For example, one or more processes performed by one or more embodiments described herein can more efficiently, and even more feasibly, provide data collection, such as time-aligned data collection in the frequency domain, as compared to existing systems and/or techniques. Systems, computer-implemented methods and/or computer program products facilitating performance of these processes are of great utility in the field of data storage and/or radio system management and cannot be equally practicably implemented in a sensible way outside of a computing environment.

One or more embodiments described herein can employ hardware and/or software to solve problems that are highly technical, that are not abstract, and that cannot be performed as a set of mental acts by a human. For example, a human, or even thousands of humans, cannot efficiently, accurately and/or effectively collect and statistically analyze frequency domain data in the time that one or more embodiments described herein can facilitate this process. And, neither can the human mind nor a human with pen and paper electronically collect and statistically analyze frequency domain data as conducted by one or more embodiments described herein.

In one or more embodiments, one or more of the processes described herein can be performed by one or more specialized computers (e.g., a specialized processing unit, a specialized classical computer, and/or another type of specialized computer) to execute defined tasks related to the one or more technologies describe above. One or more embodiments described herein and/or components thereof can be employed to solve new problems that arise through advancements in technologies mentioned above, employment of cloud computing systems, computer architecture and/or another technology.

One or more embodiments described herein can be fully operational towards performing one or more other functions (e.g., fully powered on, fully executed and/or another function) while also performing the one or more operations described herein.

Example Operating Environment

FIG.12is a schematic block diagram of an operating environment1200with which the described subject matter can interact. The system1200comprises one or more remote component(s)1210. The remote component(s)1210can be hardware and/or software (e.g., threads, processes, computing devices). In some embodiments, remote component(s)1210can be a distributed computer system, connected to a local automatic scaling component and/or programs that use the resources of a distributed computer system, via communication framework1240. Communication framework1240can comprise wired network devices, wireless network devices, mobile devices, wearable devices, radio access network devices, gateway devices, femtocell devices, servers, etc.

The system1200also comprises one or more local component(s)1220. The local component(s)1220can be hardware and/or software (e.g., threads, processes, computing devices). In some embodiments, local component(s)1220can comprise an automatic scaling component and/or programs that communicate/use the remote resources1210and1220, etc., connected to a remotely located distributed computing system via communication framework1240.

One possible communication between a remote component(s)1210and a local component(s)1220can be in the form of a data packet adapted to be transmitted between two or more computer processes. Another possible communication between a remote component(s)1210and a local component(s)1220can be in the form of circuit-switched data adapted to be transmitted between two or more computer processes in radio time slots. The system1200comprises a communication framework1240that can be employed to facilitate communications between the remote component(s)1210and the local component(s)1220, and can comprise an air interface, e.g., interface of a UMTS network, via a long-term evolution (LTE) network, etc. Remote component(s)1210can be operably connected to one or more remote data store(s)1250, such as a hard drive, solid state drive, SIM card, device memory, etc., that can be employed to store information on the remote component(s)1210side of communication framework1240. Similarly, local component(s)1220can be operably connected to one or more local data store(s)1230, that can be employed to store information on the local component(s)1220side of communication framework1240.

Example Computing Environment

In order to provide additional context for various embodiments described herein,FIG.13and the following discussion are intended to provide a brief, general description of a suitable computing environment1300in which the various embodiments of the embodiment described herein can be implemented. While the embodiments have been described above in the general context of computer-executable instructions that can run on one or more computers, those skilled in the art will recognize that the embodiments can be also implemented in combination with other program modules and/or as a combination of hardware and software.

Generally, program modules include routines, programs, components, data structures, etc., that perform particular tasks or implement particular abstract data types. Moreover, the methods can be practiced with other computer system configurations, including single-processor or multiprocessor computer systems, minicomputers, mainframe computers, Internet of Things (IoT) devices, distributed computing systems, as well as personal computers, hand-held computing devices, microprocessor-based or programmable consumer electronics, and the like, each of which can be operatively coupled to one or more associated devices.

The illustrated embodiments of the embodiments herein can be also 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.

Computing devices typically include a variety of media, which can include computer-readable storage media, machine-readable storage media, and/or communications media, which two terms are used herein differently from one another as follows. Computer-readable storage media or machine-readable storage media can be any available storage media that can be accessed by the computer and includes both volatile and nonvolatile media, removable and non-removable media. By way of example, and not limitation, computer-readable storage media or machine-readable storage media can be implemented in connection with any method or technology for storage of information such as computer-readable or machine-readable instructions, program modules, structured data or unstructured data.

Computer-readable storage media can include, but are not limited to, random access memory (RAM), read only memory (ROM), electrically erasable programmable read only memory (EEPROM), flash memory or other memory technology, compact disk read only memory (CD-ROM), digital versatile disk (DVD), Blu-ray disc (BD) or other optical disk storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, solid state drives or other solid state storage devices, or other tangible and/or non-transitory media which can be used to store desired information. In this regard, the terms “tangible” or “non-transitory” herein as applied to storage, memory or computer-readable media, exclude only propagating transitory signals per se as modifiers and do not relinquish rights to all standard storage, memory or computer-readable media that are not only propagating transitory signals per se.

Computer-readable storage media can be accessed by one or more local or remote computing devices, e.g., via access requests, queries or other data retrieval protocols, for a variety of operations with respect to the information stored by the medium.

Communications media typically embody computer-readable instructions, data structures, program modules or other structured or unstructured data in a data signal such as a modulated data signal, e.g., a carrier wave or other transport mechanism, and includes any information delivery or transport media. The term “modulated data signal” or signals refers to a signal that has one or more of its characteristics set or changed in such a manner as to encode information in one or more signals. By way of example, and not limitation, communication media include wired media, such as a wired network or direct-wired connection, and wireless media such as acoustic, RF, infrared and other wireless media.

Referring still toFIG.13, the example computing environment1300which can implement one or more embodiments described herein includes a computer1302, the computer1302including a processing unit1304, a system memory1306and a system bus1308. The system bus1308couples system components including, but not limited to, the system memory1306to the processing unit1304. The processing unit1304can be any of various commercially available processors. Dual microprocessors and other multi-processor architectures can also be employed as the processing unit1304.

The system bus1308can be any of several types of bus structure that can further interconnect to a memory bus (with or without a memory controller), a peripheral bus, and a local bus using any of a variety of commercially available bus architectures. The system memory1306includes ROM1310and RAM1312. A basic input/output system (BIOS) can be stored in a nonvolatile memory such as ROM, erasable programmable read only memory (EPROM), EEPROM, which BIOS contains the basic routines that help to transfer information between elements within the computer1302, such as during startup. The RAM1312can also include a high-speed RAM such as static RAM for caching data.

The computer1302further includes an internal hard disk drive (HDD)1314(e.g., EIDE, SATA), and can include one or more external storage devices1316(e.g., a magnetic floppy disk drive (FDD)1316, a memory stick or flash drive reader, a memory card reader, etc.). While the internal HDD1314is illustrated as located within the computer1302, the internal HDD1314can also be configured for external use in a suitable chassis (not shown). Additionally, while not shown in environment1300, a solid state drive (SSD) could be used in addition to, or in place of, an HDD1314.

Other internal or external storage can include at least one other storage device1320with storage media1322(e.g., a solid state storage device, a nonvolatile memory device, and/or an optical disk drive that can read or write from removable media such as a CD-ROM disc, a DVD, a BD, etc.). The external storage1316can be facilitated by a network virtual machine. The HDD1314, external storage device(s)1316and storage device (e.g., drive)1320can be connected to the system bus1308by an HDD interface1324, an external storage interface1326and a drive interface1328, respectively.

The drives and their associated computer-readable storage media provide nonvolatile storage of data, data structures, computer-executable instructions, and so forth. For the computer1302, the drives and storage media accommodate the storage of any data in a suitable digital format. Although the description of computer-readable storage media above refers to respective types of storage devices, other types of storage media which are readable by a computer, whether presently existing or developed in the future, could also be used in the example operating environment, and further, that any such storage media can contain computer-executable instructions for performing the methods described herein.

A number of program modules can be stored in the drives and RAM1312, including an operating system1330, one or more application programs1332, other program modules1334and program data1336. All or portions of the operating system, applications, modules, and/or data can also be cached in the RAM1312. The systems and methods described herein can be implemented utilizing various commercially available operating systems or combinations of operating systems.

Computer1302can optionally comprise emulation technologies. For example, a hypervisor (not shown) or other intermediary can emulate a hardware environment for operating system1330, and the emulated hardware can optionally be different from the hardware illustrated inFIG.13. In such an embodiment, operating system1330can comprise one virtual machine (VM) of multiple VMs hosted at computer1302. Furthermore, operating system1330can provide runtime environments, such as the Java runtime environment or the .NET framework, for applications1332. Runtime environments are consistent execution environments that allow applications1332to run on any operating system that includes the runtime environment. Similarly, operating system1330can support containers, and applications1332can be in the form of containers, which are lightweight, standalone, executable packages of software that include, e.g., code, runtime, system tools, system libraries and settings for an application.

Further, computer1302can be enabled with a security module, such as a trusted processing module (TPM). For instance, with a TPM, boot components hash next in time boot components, and wait for a match of results to secured values, before loading a next boot component. This process can take place at any layer in the code execution stack of computer1302, e.g., applied at the application execution level or at the operating system (OS) kernel level, thereby enabling security at any level of code execution.

A user can enter commands and information into the computer1302through one or more wired/wireless input devices, e.g., a keyboard1338, a touch screen1340, and a pointing device, such as a mouse1342. Other input devices (not shown) can include a microphone, an infrared (IR) remote control, a radio frequency (RF) remote control, or other remote control, a joystick, a virtual reality controller and/or virtual reality headset, a game pad, a stylus pen, an image input device, e.g., camera(s), a gesture sensor input device, a vision movement sensor input device, an emotion or facial detection device, a biometric input device, e.g., fingerprint or iris scanner, or the like. These and other input devices are often connected to the processing unit1304through an input device interface1344that can be coupled to the system bus1308, but can be connected by other interfaces, such as a parallel port, an IEEE 1394 serial port, a game port, a USB port, an IR interface, a BLUETOOTH® interface, etc.

A monitor1346or other type of display device can be also connected to the system bus1308via an interface, such as a video adapter1348. In addition to the monitor1346, a computer typically includes other peripheral output devices (not shown), such as speakers, printers, etc.

The computer1302can operate in a networked environment using logical connections via wired and/or wireless communications to one or more remote computers, such as a remote computer(s)1350. The remote computer(s)1350can be a workstation, a server computer, a router, a personal computer, portable computer, microprocessor-based entertainment appliance, a peer device or other common network node, and typically includes many or all of the elements described relative to the computer1302, although, for purposes of brevity, only a memory/storage device1352is illustrated. The logical connections depicted include wired/wireless connectivity to a local area network (LAN)1354and/or larger networks, e.g., a wide area network (WAN)1356. Such LAN and WAN networking environments are commonplace in offices and companies, and facilitate enterprise-wide computer networks, such as intranets, all of which can connect to a global communications network, e.g., the Internet.

When used in a LAN networking environment, the computer1302can be connected to the local network1354through a wired and/or wireless communication network interface or adapter1358. The adapter1358can facilitate wired or wireless communication to the LAN1354, which can also include a wireless access point (AP) disposed thereon for communicating with the adapter1358in a wireless mode.

When used in a WAN networking environment, the computer1302can include a modem1360or can be connected to a communications server on the WAN1356via other means for establishing communications over the WAN1356, such as by way of the Internet. The modem1360, which can be internal or external and a wired or wireless device, can be connected to the system bus1308via the input device interface1344. In a networked environment, program modules depicted relative to the computer1302or portions thereof, can be stored in the remote memory/storage device1352. The network connections shown are example and other means of establishing a communications link between the computers can be used.

When used in either a LAN or WAN networking environment, the computer1302can access cloud storage systems or other network-based storage systems in addition to, or in place of, external storage devices1316as described above. Generally, a connection between the computer1302and a cloud storage system can be established over a LAN1354or WAN1356e.g., by the adapter1358or modem1360, respectively. Upon connecting the computer1302to an associated cloud storage system, the external storage interface1326can, with the aid of the adapter1358and/or modem1360, manage storage provided by the cloud storage system as it would other types of external storage. For instance, the external storage interface1326can be configured to provide access to cloud storage sources as if those sources were physically connected to the computer1302.

The computer1302can be operable to communicate with any wireless devices or entities operatively disposed in wireless communication, e.g., a printer, scanner, desktop and/or portable computer, portable data assistant, communications satellite, any piece of equipment or location associated with a wirelessly detectable tag (e.g., a kiosk, news stand, store shelf, etc.), and telephone. This can include Wireless Fidelity (Wi-Fi) and BLUETOOTH® wireless technologies. Thus, the communication can be a predefined structure as with a conventional network or simply an ad hoc communication between at least two devices.

CONCLUSION

The above description of illustrated embodiments of the one or more embodiments described herein, comprising what is described in the Abstract, is not intended to be exhaustive or to limit the described embodiments to the precise forms described. While one or more specific embodiments and examples are described herein for illustrative purposes, various modifications are possible that are considered within the scope of such embodiments and examples, as those skilled in the relevant art can recognize.

In this regard, while the described subject matter has been described in connection with various embodiments and corresponding figures, where applicable, other similar embodiments can be used or modifications and additions can be made to the described embodiments for performing the same, similar, alternative, or substitute function of the described subject matter without deviating therefrom. Therefore, the described subject matter should not be limited to any single embodiment described herein, but rather should be construed in breadth and scope in accordance with the appended claims below.

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. Additionally, a processor can refer to an integrated circuit, an application specific integrated circuit, a digital signal processor, a field programmable gate array, a programmable logic controller, a complex programmable logic device, 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 to optimize space usage or enhance performance of user equipment. A processor can also be implemented as a combination of computing processing units.

As used in this application, the terms “component,” “system,” “platform,” “layer,” “selector,” “interface,” and the like are intended to refer to a computer-related entity or an entity related to an operational apparatus with one or more specific functionalities, wherein the entity can be either hardware, a combination of hardware and software, software, or software in execution. As an example, a component may be, but is not limited to being, a process running on a processor, a processor, an object, an executable, a thread of execution, a program, and/or a computer. By way of illustration and not limitation, both an application running on a server and the server 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. In addition, these components can execute from various computer readable media having various data structures stored thereon. The components may communicate via local and/or remote processes such as in accordance with a signal having one or more data packets (e.g., data from one component interacting with another component in a local system, distributed system, and/or across a network such as the Internet with other systems via the signal). As another example, a component can be an apparatus with specific functionality provided by mechanical parts operated by electric or electronic circuitry, which is operated by a software or a firmware application executed by a processor, wherein the processor can be internal or external to the apparatus and executes at least a part of the software or firmware application. As yet another example, a component can be an apparatus that provides specific functionality through electronic components without mechanical parts, the electronic components can comprise a processor therein to execute software or firmware that confers at least in part the functionality of the electronic components.

In addition, 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.

While the embodiments are susceptible to various modifications and alternative constructions, certain illustrated implementations thereof are shown in the drawings and have been described above in detail. However, there is no intention to limit the various embodiments to the one or more specific forms described, but on the contrary, the intention is to cover all modifications, alternative constructions, and equivalents falling within the spirit and scope.

In addition to the various implementations described herein, other similar implementations can be used or modifications and additions can be made to the described implementation(s) for performing the same or equivalent function of the corresponding implementation(s) without deviating therefrom. Still further, multiple processing chips or multiple devices can share the performance of one or more functions described herein, and similarly, storage can be effected across a plurality of devices. Accordingly, the various embodiments are not to be limited to any single implementation, but rather are to be construed in breadth, spirit and scope in accordance with the appended claims.