Open RAN radio unit power saving on per-symbol basis using transmission blanking

[0001] The open radio access network (O-RAN) Alliance defines the specifications for all Open RAN (also referred to as O-RAN) components and the interfaces between them. Founded in 2018, the O-RAN Alliance is a progressive, global community comprising mobile network operators, manufacturers, vendors, and research and academic organizations working in telecommunications spaces all over the world. Typically, Open RAN refers to a disaggregated RAN with open interfaces between network components sourced from multiple suppliers.

[0002] In this regard, Open RAN represents an ongoing shift in mobile network architectures that enables service providers the use of non-proprietary subcomponents from a variety of vendors. An Open RAN is made possible by a set of industry-wide standards that telecom suppliers can follow when producing related equipment. Open RAN enables programmable, intelligent, disaggregated, virtualized, and interoperable functions. Specifically, the proprietary remote radio head (RRH) and baseband units (BBUs) are now disaggregated to radio units (RUs), distributed units (DUs), and centralized units (CUs), many of which can be virtualized or containerized. The interfaces between these new components are open and interoperable. Hence, a service provider is not locked in to a single proprietary vendor for any given component, and all vendor-supplied components that are O-RAN compliant are able to communicate with any other O-RAN compliant component, regardless of the particular vendor.

[0018] The disclosed subject matter is now described with reference to the drawings, wherein like reference numerals are used to refer to like elements throughout. In the following description, for purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of the disclosed subject matter. It may be evident, however, that the disclosed subject matter may be practiced without these specific details. In other instances, well-known structures and devices are shown in block diagram form in order to facilitate describing the disclosed subject matter.

[0019] The present application relates generally to identifying power saving opportunities on a symbol-by-symbol basis based on transmission blanking and, more particularly, to identifying those opportunities in the context of an Open RAN (radio access network) radio unit (O-RU).

[0020] In order to better understand the subject matter detailed herein, it can be instructive to consider an example Open RAN architecture. FIG. 1 depicts a schematic block diagram 100 that illustrates an example disaggregated Open RAN in accordance with some example embodiments of this disclosure. In this example, the Open RAN network comprises packet core 102 configured to communicate via backhaul 104 with one or more centralized unit (O-CU) 106. Typically, backhaul 104 transports data according to Internet protocol (IP).

[0021] O-CU 106 can communicate via open midhaul interface 108 with one or more distributed unit (O-DU) 110. Open midhaul interface 108 can communicate according to IP, but it is noted that because open midhaul interface 108 is an open standard, it is no longer expected that equipment comprising O-CU 106 and O-DU 110 communicate in a proprietary way or be from the same vendor.

[0022] In some embodiments, packet core 102, O-CU 106, or O-DU 110 can be virtualized and operate, respectively, as a virtual packet core 102, a virtual centralized unit (vCU) 106, or a virtual distributed unit (vDU) 110.

[0023] O-DU 110 can communicate via open fronthaul interface 112 with one or more radio unit (O-RU) 114. Open fronthaul interface 112 can communicate according to an enhanced common public radio interface (eCPRI) protocol or a radio-over-Ethernet (ROE) protocol.

[0024] It is noted that until Open RAN, the interfaces between conventional BBU and RRH were proprietary, meaning that only one vendor could provide both BBU and RRH equipment. Open RAN disaggregated this architecture and introduced open interfaces (e.g., open midhaul interface 108, open fronthaul interface 112, . . . ). Moreover, instead of relying on conventional RRH and BBU architectures, associated functions are disaggregated into elements depicted herein, namely, the radio unit (e.g., O-RU 114), the distributed unit (e.g., O-DU 110), and the centralized unit (e.g., O-CU 106) with open interfaces between them and with the potential that radio unit, distributed unit, or centralized unit functions can be virtualized or containerized.

[0025] One challenge that confronts modern networks, including Open RANs, is power consumption, particularly in radio units such as O-RU 114. Because open fronthaul interface 112 operates according to an open standard, O-DU 110 and O-RU 114 can be from different vendors. While this represents a significant benefit to service providers, such also means that any interaction between O-DU 110 and O-RU 114 that is not part of the O-RAN specification cannot be presumed. Therefore, certain proprietary techniques relied upon to reduce power consumption and/or extend battery life for a given radio unit 114 may not be suitable for deployment in an Open RAN implementation, particularly techniques that relied upon computations performed upstream from the radio unit 114 or extra commands or signals, since that particular upstream component (e.g., O-DU 110) might be a different vendor that is not programmed to perform those computations or to perform the computations in the same way, or not programmed to send the extra commands or signals.

[0026] To these and other related ends, the disclosed subject matter can identify power saving opportunities for O-RU 114. These power saving opportunities can be identified by the O-RU 114 itself without relying on any computations or intelligence assumed from another component of the Open RAN (e.g., O-DU 110, O-CU 106, . . . ), but rather relying (potentially entirely) on information that is available to O-RU 114 as part of ordinary Open RAN operation.

[0027] In particular, techniques detailed herein can enable an O-RU to save power or increase energy efficiency on a symbol-by-symbol basis. For example, techniques detailed herein can operate to identify orthogonal frequency division multiplexing (OFDM) symbols that have no data allocated to be transmitted or to be received over the air, which are referred to herein as blank symbols.

[0028] By identifying blank symbols within a given transmission of data, some devices of O-RU 114 relating to transmitting, receiving, processing, and so forth can be powered down for any time that coincides with a blank symbol instead of remaining in a power-consuming state. Such operation, even for time periods as short as a single symbol, can result in significant power consumption reduction by an associated O-RU 114. Advantageously, said power saving opportunities can be identified by O-RU 114 for any communication over open fronthaul interface 112 that is Open RAN-compliant, regardless of whether or not O-RU 114 and O-DU 110 are from the same vendor.

[0029] FIG. 2 depicts a schematic block diagram 200 that illustrates an example O-RU 114 architecture in accordance with some example embodiments of this disclosure. It is appreciated that O-RU 114 can be any suitable device or circuit that is capable of being Open RAN compliant. Non-limiting examples include a field programmable gate array (FPGA) device, an application-specific integrated circuit (ASIC), a microcontroller, and so. In this particular example, O-RU 114 is implemented as a FPGA, though it is understood such is not intended to be limiting, but rather to provide one concrete example in the context of the disclosed subject matter.

[0030] O-RU 114 can be configured to communicate, for example, via open fronthaul interface 112, with O-DU 110, which can be any suitable distributed unit that is Open RAN-compliant. Open RAN specifications define four different communication planes over open fronthaul interface 112, namely a control plane (C-plane), a user plane (U-plane), a synchronization plane (S-plane), and a management plane (M-plane). The control plane is used for communication of C-plane data 212, which is generally related to control plane messages that define the scheduling and coordination utilized for data transfer, beam forming, or the like. The user plane is used for communication of U-plane data 214, which is generally related to user plane message for efficient data transfer within the strict time limits of related communication specifications such as 5G numerologies. The synchronization plane is used for communication of S-plane data 216, which is generally responsible for timing and synchronization parameters between the O-DU 110 and the O-RU 114. The management plane is used for communication of M-plane data 218, which is used to manage the O-RU 114.

[0031] O-RU 114 can comprise a processor and a memory, in this case respectively illustrated as FPGA processing core 202 and internal memory 204. Internal memory 204 can comprise data 206 relating to operating system data, driver data, software stack data, and so forth. As noted previously, an objective of the disclosed techniques is to identify blank symbols. Information relating to blank symbols (e.g., in the form of bitmaps detailed subsequently) can be generated by FPGA processing core 202 and potentially stored to internal memory 204. Based on these bitmaps (or other suitable identification of blank or non-blank symbols), various devices can be instructed to power down during a time corresponding to the blank symbols and/or power back up for non-blank symbols. Such can be effectuated via general purpose input/output (GPIO) 208 that facilitates instructions to, e.g., a hardware controller 210 to power down/up associated devices or equipment according to the bitmap.

[0032] Open RAN-compliant devices typically communicate via OFDM protocols or techniques in which OFDM symbols are communicated between the two devices, generally via U-plane data 214. However, prior to such communication, PRBs can be scheduled or allocated to a given symbol via C-plane data 212 that is required by Open RAN specification for processing of U-plane data 214.

[0033] Techniques detailed herein can utilize existing control plane message (e.g., C-plane data 212) sent from O-DU 110 to O-RU 114 over open fronthaul interface 112. Such C-plane data 212 can be examined to identify OFDM symbols that are blank and therefore carry no information (e.g., no PRBs are allocated or scheduled to be transmitted or received over those symbols over the air). Such identification of blank symbols can be performed in the context of each slot, subframe, radio frame, and antenna (including separate component carriers for a given antenna branch) for both downlink and uplink directions. In other words, individual bitmaps can be constructed for uplink traffic and downlink traffic as well as for each separate antenna or component carrier of O-RU 114. The individual bitmaps can be constructed for any duration, including for one or more slots, one or more subframes, one or more radio frames and so forth. Bitmaps related to different slots (or other duration) can be combined with other bitmaps to form a longer duration (e.g., several slot bitmaps can be combined to form a subframe bitmap). Bitmaps related to different component carriers can be combined to form a combined bitmap for a particular antenna branch. Implementation of such can be based on available storage space of internal memory 204.

[0034] Based on transmission blanking concepts that can be parsed from C-plane messages, the disclosed techniques can detect blank symbols among symbols scheduled by O-DU 110 dynamically in each time slot (or other duration) via C-plane messages.

[0035] Thus, blank symbols can be detected in resource block allocations for all physical downlink channels, including but not limited to: a physical downlink shared channel (PDSCH), a physical downlink control channel (PDCCH), demodulated reference signal (DMRS) PDSCH, phase tracking reference signal (PTRS)-PDSCH, DMRS-PDCCH, DRMS-physical broadcast channel (PBCH), channel state information reference signal (CSI-RS), primary synchronization signals (PSS), secondary synchronization signals (SSS), or synchronization signal (SS) block; and all physical uplink channels, including but not limited to: physical uplink shared channel (PUSCH), physical uplink control channel (PUCCH), PRACH, DMRS-PUSCH, PTRS-PUSCH, DMRS-PUCCH, or SRS.

[0036] Referring now to FIG. 3, a schematic block diagram is depicted illustrating an example O-RU 300 that can determine blank and/or non-blank symbols that are scheduled or allocated in accordance with some example embodiments of this disclosure. A ‘blank’ symbol can be a symbol in which no physical resource block (PRB) is allocated or scheduled. Conversely, a ‘non-blank’ symbol can be a symbol in which at least one PRB is allocated or scheduled. Device 300 can comprise a processor 352 that can be specifically configured to identify blank or non-blank symbols in accordance with blank/non-blank identification procedure 356. Device 300 can also comprise memory 354 that stores executable instructions that, when executed by processor 352, can facilitate performance of operations. Processor 352 can be a hardware processor having structural elements known to exist in connection with processing units or circuits, with various operations of processor 352 being represented by functional elements shown in the drawings herein that can require special-purpose instructions, for example, stored in memory 354 and/or a blank/non-blank identification procedure 356 component or circuit. Along with these special-purpose instructions, processor 352 and/or device 300 can be a special-purpose device. One non-limiting example of processor 352 and memory 354 can be FPGA processing core 202 and internal memory 204 of FIG. 2. Further examples of memory 354 and processor 352 can be found with reference to FIG. 11. It is to be appreciated that device 300 or computer 1102 can represent a network device, a client device, or other device that can be used in connection with implementing one or more of the systems, devices, or components shown and described in connection with FIG. 3 and other figures disclosed herein.

[0037] O-RU 300 can be configured to receive signal 302. Signal 302 can be formatted according to an open radio access network (Open RAN) standard or specification. Signal 302 can comprise at least C-plane data 212, which can be responsible scheduling or allocating OFDM symbols within a slot or other duration.

[0038] Each OFDM symbol can consist of several PRBs depending on the channel bandwidth and subcarrier spacing that is employed, various examples of which are illustrated with reference to diagram 500C of FIG. 5C. For example, an OFDM symbol with 100 megaHertz (MHz) of channel bandwidth and a subcarrier spacing (SCS) of 30 kiloHertz (kHz) has 273 PRBs in total, whereas an OFDM symbol with 50 MHz of channel bandwidth and a SCS of 60 kHz has a total configured number of PRBs of 65.

[0039] The full PRB allocation scheme for a particular symbol can depend on a number of parameters, including, for example, how O-DU 110 schedules different users by assigning different time and frequency resources to each user (e.g., each O-RU 114 that is served by O-DU 110). Another example parameter can be the location of control and reference signals in a time-frequency grid.

[0040] C-plane data 212 generally carry data-associated control information from O-DU 110 to O-RU 114, which is required for subsequently processing U-plane data at O-RU 114. This data-associated control information can include, e.g., scheduling and PRB allocations in both downlink and uplink communications.

[0041] However, C-plane message granularity is not necessarily based on a symbol-by-symbol definition. Rather, the information utilized to identify different resource elements inside a particular PRB to construct an associated OFDM symbol can be described by different sections of a given C-plane message, as well as by many different C-plane messages. In other words, C-plane messages can, for a given slot (or other duration), describe PRB allocations for many different symbols that are scattered all over the time-frequency grid over the duration of a slot (or other duration).

[0042] Hence, in order to identify blank symbols O-RU 114 can determine locations of fully blank symbols (or, conversely non-blank symbols) on a symbol-by-symbol basis, which is not a trivial determination, due at least in part to the arrangement of PRB allocations within typical C-plane messages.

[0043] In that regard, O-RU 114 can initialize bitmap 304. Bitmap 304 can comprise a number of bits (e.g., length or bit length) corresponding to a number of symbols that are allocated or scheduled, via the Open RAN, for transport between O-DU 110 and O-RU 114, as illustrated in connection with reference numeral 306. Hence, the actual number of bits of bitmap 304, as with the number of symbols, can depend on numerous factors, such as duration 308 and cyclic prefix 310. Duration 308, in this context, refers to an amount of time of a time-frequency grid or the like such as, e.g., a slot, subframe (e.g., composed of one or more slots), radio frame (e.g., composed of one or more subframes), or the like.

[0044] Additionally, multiple counters 322 can be initialized, which can take place prior to or during a parsing procedure 318. Counters 322 can be used in connection with the transmission blanking concepts to track or identify blank and/or non-blank symbols on a per-symbol basis. More particularly, while bits of bitmap 304 can indicate whether a given symbol is blank or non-blank, counters 322 can track the number of blank or non-blank PRBs for each symbol, which, in the aggregate can produce the information necessary to populate bitmap 304. Thus, in some embodiments, a separate counter 322 can be initialized for each bit of bitmap 304.

[0045] While still referring to FIG. 3, but turning now as well to FIGS. 4A and 4B, two example bitmaps 304 and counters 322 are depicted. In that regard, diagram 400A illustrates a first example in the context of one slot with normal cyclic prefix in accordance with some example embodiments of this disclosure. Diagram 400B illustrates a second example in the context of one slot with extended cyclic prefix in accordance with some example embodiments of this disclosure.

[0046] Since each bit of bitmap 304 can indicate whether a corresponding symbol is blank, the number of bits in bitmap 304 can match the number of symbols. Thus, for a single slot with normal cyclic prefix, 14 symbols can be transported. As such, bitmap 304 can be generated or initialized in that case with 14 bits, as illustrated by diagram 400A. Likewise, since counters 322 can be used to determine which value to assign to a given bit of bitmap 304, 14 different counters 322 can be initialized, one for each symbol and/or bit of bitmap 304.

[0047] In contrast, for a single slot with extended cyclic prefix, 12 symbols can be transported. Hence, bitmap 304, in that case can be generated or initialized with 12 bits, as illustrated by diagram 400B. Similarly, in the case of extended prefix, 12 different counters 322 can be initialized, again, one for each symbol and/or bit of bitmap 304. It is noted that while bitmap 304 can be represented by a group of 1-bit elements, counters 322 can increment up to (or decrement down from) the maximum number of configured PRBs for a given symbol. Such can vary, but based on FIG. 5C, will not tend to be above 273 given current implementations. Hence, as 8 bits are needed to count up to (or down from) 256, counters 322 would likely need to be more than an 8-bit element, for example, 9-bits, which can distinguish between 512 values (or more, e.g., 16-bits), which would be sufficient in current implementations.

[0048] While both of these examples relate to a single slot, other durations 308 are possible. For example, if a subframe comprises two slots, then bitmap 304 for that subframe (as opposed to a single slot) can have a length of 28 bits (and 28 counters 322) in the case of normal cyclic prefix or 24 bits (and 24 counters 322) in the case of extended cyclic prefix.

[0049] If a given bit is set to a first value, such can indicate that a corresponding symbol has at least one PRB described by C-plane messages. As illustrated in the legend, in this example, the first value is “0”. Examples of this are show for symbol numbers 1, 3-5, 7, 9, 10, 12, and 14. If a given bit is set to a second value, such can indicate that a corresponding symbol has no PRBs described by C-plane messages. As illustrated in the legend, in this example, the second value is “1”. Examples of this are show for symbol numbers 2, 6, 8, 11, and 13. It is appreciated that in other embodiments, the first value could instead be indicated by “1” while the second value is indicated by “0”.

[0050] As will be further detailed below, whether to assign a given bit to the first value (e.g., “0”) to indicate the symbol is not blank, or to the second value (e.g., “1”) to indicate the symbol is fully blank can be determined based on the final value of an associated counter 322, which is further detailed below. In this example, channel bandwidth is assumed to be 100 MHz with a subcarrier spacing of 30. As indicated at FIG. 5C, that means there is a maximum of 273 PRBs per symbol. Thus, if a given counter 322 counts 273 blank PRBs then it is known that no PRBs transmitted for that symbol will have data and can thus be considered blank. Examples of this case are symbol numbers 2, 6, 8, 11, and 13 that have counter values of 273, and corresponding bitmap bits set to the second value indicting the symbol is blank. It is appreciated that if even one PRB is not blank, then the symbol is not blank, an example is shown at symbol number 4.

[0051] It is appreciated that a distinct bitmap 304 and a distinct group of counters 322 can be created for uplink scheduling and downlink scheduling for each antenna of O-RU 300, wherein each distinct bitmap can relate to a variety of durations 308. For instance, a first bitmap 304 can be created for uplink traffic over antenna A for a given slot, a second bitmap 304 created for downlink traffic over antenna A for the given slot, a third bitmap 304 created for uplink traffic over antenna B for the given slot, and a fourth bitmap 304 created for downlink traffic over antenna B for the given slot. Any of said bitmaps 304 can cover any suitable duration 308 (e.g., expanded or appended to other bitmaps to yield a subframe bitmap 304, a frame bitmap 304, and so on). Moreover, different bitmaps 304 and counters 322 can be used for different component carriers of the same antenna branch. These different counters 322 can be subsequently combined (e.g., via a logical AND operation) to generate a valid bitmap 304 for the antenna branch.

[0052] Still referring to FIG. 3, once bitmap 304 is initialized having a length or number of bits corresponding to the number of symbols to be transported over a given duration 308 (e.g., slot, subframe, radio frame, . . . ), a given bitmap 304 can be used to identify which symbols scheduled for transport (e.g., via subsequent U-plane data 214) are not empty (or, conversely, empty) by setting each bit appropriately to either the first value or the second value. In order to determine which symbols scheduled for transport are empty or not empty, O-RU 300 can examine C-plane data 212 and increment counters 322 accordingly.

[0053] C-plane data 212 can comprise many C-plane messages that use a common frame format consisting of a transport layer and an application layer. FIG. 5A depicts diagram 500A illustrating an example transport header format structure in accordance with some example embodiments of this disclosure. It is appreciated that Open RAN supports multiple different transport headers within the Ethernet payload to further describe how the application data is to be handled in the C-plane and U-plane. The provided example relates to an eCPRI transport header format, but it is appreciated that other types of transport header formats are known. The transport header is eight bytes in length and provides numerous basic data routing capabilities. For example, these data routing capabilities can comprise: description of the data flow type, sending and receiving port identifiers, an ability to support concatenation, sequence numbering, or the like.

[0054] It is noted that the ecpriRtcid/ecpriPcid parameter (e.g., octets 5 and 6, illustrated at reference numeral 502, is an eAxC identifier (e.g., eAxC ID) and identifies the specific data flow associated with each C-plane (e.g., ecpriRtcid) or U-plane (e.g., ecpriPcid) message. A given eAxC identifier (e.g., eAxC ID) comprises several ID fields. These ID fields can include a Distributed Unit identifier (e.g., DU_Port_ID), a band and sector identifier (e.g., BandSector_ID), a component-carrier identifier (e.g., CC_ID), and a spatial stream identifier (e.g., RU_Port_ID). The bitwidth of each of the above fields is variable and set via M-plane data 218. FIG. 5B depicts diagram 500B illustrating an example bit allocation for an eAxC identifier in accordance with some example embodiments of this disclosure.

[0055] As noted above, a C-plane messages using a common frame format can consist of a transport layer and an application layer. The application layer consists of a common header followed by parameters specific to a C-plane section type that is being used. A ‘section type’ defines the characteristics of U-plane data to be transmitted or received from a beam with one pattern ID within the application common header. According to Open RAN specifications, there are currently several section types being used, out of a possible 256 section types that can be supported.

[0056] However, based on current implementations, only one section type is relevant to the techniques disclosed herein, namely, C-plane messages of section type 0. Messages of section type 0 are used for indicting idle or guard periods from O-DU (e.g., O-DU 110) and O-RU (e.g., O-RU 114). FIG. 6 illustrates diagram 600 describing a structure of section type 0 messages in accordance with some example embodiments of this disclosure. It is to be understood that FIGS. 5A, 5B, and 6 have portions that are sourced from O-RAN ALLIANCE and are subject to copyright law. Specifically, O-RAN.WG4. CUS.0-v8.00 technical specification. O-RAN ALLIANCE prohibits the copying or incorporation into any other work of part or all of the material available in that specification in any form without the prior written permission of O-RAN ALLIANCE e.V and requires that O-RAN ALLIANCE be acknowledged as the source of the material that is copied.

[0057] Still referring to FIG. 3, in order to determine which scheduled symbols are in fact blank, one can, in some embodiments in accordance with the disclosed techniques, limit examination of C-plane messages to examining only a subset of C-plane messages comprising only those C-plane messages that are of section type 0. This subset is referred to herein as target messages 312, which can be identified by O-RU 300, as illustrated at reference numeral 314. In other words, target messages 312 can consist of only messages of section type 0 and exclude other messages, e.g., messages of section types 1-8 or the like.

[0058] However, it is understood that future changes to Open RAN specifications such as the introduction of additional section types, can result in changes to the current implementation. For example, future changes to Open RAN specifications may result in interest in other section types, other than section type 0, without departing from the scope or spirit of the disclosed techniques. Therefore, in some embodiments, target messages 312 can include other section types in addition to, or instead of, section type 0.

[0059] As illustrated at reference numeral 316, O-RU 300 can perform parsing procedure 318. Parsing procedure 318 can parse all or a subset of messages included in C-plane data 212, which is further detailed according to some embodiments in connection with FIG. 7. In some embodiments, as illustrated here at reference numeral 324, parsing procedure 318 can parse only target messages 312 (e.g., only C-plane message of section type 0) to determine a symbol status (e.g., blank or not blank) of a given symbol. In other words, parsing procedure 318 can determine whether a given symbol allocates or schedules a PRB.

[0060] To these and related ends, parsing procedure can utilize counters 322 to count the number of blank or non-blank PRBs within a given symbol, and do so for all possible symbols. As shown at reference numeral 320, counters 322 can be initialized (or such can be done elsewhere), and those counters can be updated as section type 0 messages are received and processed. Thus, for example, if all of the PRBs of a given symbol are blank, which can be determined by comparing the final result of an associated counter to a total number of PRBs per symbol, then the symbol is blank. Otherwise, if at least one PRB of a symbol is not blank (e.g., the counter value is less than the total number of PRBs per symbol), then the associated symbol is not blank.

[0061] At reference numeral 326, parsing procedure 318 can comprise updating bits of bitmap 304 on a per-symbol basis. For instance, if the symbol status of the given symbol is blank (e.g., does not allocate any PRB) then an associated bit of bitmap 304 can be set to the first value (e.g., “1”). On the other hand, if the symbol status of the given symbol is not blank (e.g., allocates at least one PRB) then an associated bit of bitmap 304 can be set to the second value (e.g., “0”). As noted, updating bitmap 304 can be based on the result of a comparison between an associated counter value and the total number of PRBs per symbol. In some embodiments, bitmap 304 can be stored to memory 354 for subsequent access or recall such as in connection with subsequent processing of U-plane data 214.

[0062] At reference numeral 330, O-RU 300 can instruct a device or circuit to power down during communication of any symbol in which a corresponding bit of bitmap 304 is set to the first value. It is understood that in a typical O-RU 300, most of the power is consumed at the radio frequency (RF) and analog signal processing blocks, such as high-power amplifiers (HPA) (e.g., in the downlink path) and low noise amplifiers (LNA) (e.g., in the uplink path) and data converters such as analog to digital converters (ADC) or digital to analog converters (DAC). Hence, shutting down transceiver chains during time periods in which there is no data scheduled to be transmitted or received can significantly impact total consumed power in O-RU 300 and substantially improve the overall energy efficiency.

[0063] It is to be appreciated that, in some embodiments, parsing procedure 318 can operate by internally tracking symbol identifiers within the target messages 312 and section identifiers within a given message, which is explained in greater detail with reference to FIG. 7. For example, in some embodiments, parsing procedure 318 can determine whether a given symbol does not allocate or schedule the physical resource block in response to processing each section of a message by successively decrementing a number of sections field (e.g., numOfSections) until all sections of the target message are processed.

[0064] Similarly, parsing procedure 318 can determine whether a given symbol does not allocate or schedule a physical resource block in response to processing each message by successively decrementing a symbol number field (e.g., numSymbol) until all symbols have been processed, while tracking a current symbol parameter that is incremented in response to an increment symbol field (e.g., symInc) being set to 1.

[0065] Further, in some embodiments, when bitmap 304 is initialized or created (e.g., reference numeral 306), all (or a portion of) the bits can be set to an initial value, such as the first value (e.g., “1”) or the second value (e.g., “0”). In that case, it is only necessary to update those bits that are determined to have a different symbol status (e.g., blank vs not blank). While the initial setting can be either the first value or the second value, it can be advantageous to initially set all bits to the second value initially, namely to a value that indicates the corresponding symbol is not blank.

[0066] Since, in general, C-plane messages arrive ahead of corresponding U-plane messages, bitmap 304 can be completed with significant time margins with respect to over the air (OTA) deadlines. Naturally this margin is a function of spacing between C-plane and U-plane messages for each symbol.

[0067] If a particular C-plane message of section type 0 is lost or dropped after reception for any reason (e.g., too early, too late, . . . ) bitmap 304, in the case where bits have been set to the second value, still represents a valid status for all symbols, even those with lost descriptions.

[0068] FIGS. 7-10 illustrate various methods in accordance with the disclosed subject matter. While, for purposes of simplicity of explanation, the methods are shown and described as a series of acts, it is to be understood and appreciated that the disclosed subject matter is not limited by the order of acts, as some acts may occur in different orders and/or concurrently with other acts from that shown and described herein. For example, those skilled in the art will understand and appreciate that a method could alternatively be represented as a series of interrelated states or events, such as in a state diagram. Moreover, not all illustrated acts may be required to implement a method in accordance with the disclosed subject matter. Additionally, it should be further appreciated that the methods disclosed hereinafter and throughout this specification are capable of being stored on an article of manufacture to facilitate transporting and transferring such methods to computers.

[0069] Turning now to FIG. 7, exemplary method 700 is depicted. Method 700 can update counters to identify PRB allocation in accordance with some example embodiments of this disclosure. At process block 702, a device comprising a processor can create or initialize counters (e.g., counters 322). Each group of counters can be for dataDirection, frameId, subframeId, slotId, and eAxCId. In other words, there can be a different group of counters for uplink communication than for downlink communication (e.g., dataDirection), different groups for different durations (e.g., frameId, subframeId, slotId) and a different group of counters for different common carriers of a given antenna branch (e.g., which can be identified by eAxCId).

[0070] Initially, all counters can be set to “0” to allow counters to increment up to the maximum amount of PRBs per symbol based on the parsing of the section type 0 messages. However, it is appreciated that other techniques can be used. For example, all counters could be initially set to the maximum amount of PRBs per symbol, and decremented based on the parsing.

[0071] At data block 704, the first or next C-plane message received can be selected for processing. For that selected message, the following parameters can be retrieved at process block 706: eAxCId, dataDirection, frameId, subframeId, slotId, startSymbolId numOfSections sectionType.

[0072] At decision block 708, the section type of the selected message can be examined. If, no, the section type is not zero (e.g., section type 0), then method 700 can loop back to data block 704. If, yes, the section type is zero, then method 700 can proceed to process block 710.

[0073] At process block 710, the first section description of the current C-plane message being analyzed can be examined to retrieve values for the following fields: symInc, numPrbc, numSymbol, ef. It is noted that a data section description may include an extension flag (ef) that indicates one or more section extensions may be included within a data section, which is further detailed in connection with blocks 718 and 722, below. Method 700 can proceed to decision block 712.

[0074] At decision block 712, it can be determined whether symInc=1, recalling that symInc is a symbol number increment field that is used to track which symbol the data refers to and therefore allows the identification which particular counter is to be accessed in subsequent processing. If, yes, symInc=1, then at process block 714 the current symbol is incremented to reference the next symbol. If, no, then at process block 716, the current symbol is set to the startSymbolId field of the current message. In either case, method 700 proceeds from the process block branches of 714 and 716 to decision block 718.

[0075] At decision block 718, it is determined whether the extension flag, ef=1. It is appreciated that when section type 0 is used for transmission blanking, section extension 7 can be used to allow a specific C-plane message to be applied to multiple eAxC_Id, for instance to address all component carriers at once.

[0076] When a C-plane section type 0 message with section extension 7 is received, the O-RU shall interpret it as if multiple C-plane messages were received for all the eAxC_Id values permitted by the eAxCmask. Thus, if no, ef does not equal one, then extension types and masking elements can be ignored and method 700 can proceed to process block 724.

[0077] Otherwise, if, yes, ef=1, then at process block 720, the next section extension(s) can be selected and extType, eAxCmask can be read. At decision block 722, if it is determined that extType is not 0x07, then method 700 can proceed to process block 724. However, if extType=0x07, then method 700 can proceed to process block 726.

[0078] In either case, counters are incremented by an amount indicated by numPrbc, which indicates the number of contiguous PRBs per data section description, and numSymbol is decremented by 1. At process block 724, this can be done for the counter associated with the current eAxCId. On the other hand, At process block 726, such can be done in connection with all counters associated with eAxCIds addressed by eAxCmask.

[0079] For either branch of processing, it is next determined (e.g., at decision block 728 or, alternatively at decision block 730) whether numSymbol is greater than or equal to 1. If so, then the current symbol is incremented by one at either process block 732 or process block 734 and the method loops back to a previous process block, either 724 in one case or 726 in the other. Once numSymbol is no longer greater than or equal to one at decision blocks 728 or 730, the process block reconverges at process block 736, where the number of sections is decremented and method 700 proceeds to decision block 738.

[0080] At decision block 738, it is determined whether the number of sections is greater than or equal to 1. If not, then method 700 proceeds to data block 742 and, since all sections of the message have now been processed, the next C-plane message received can be selected, causing the method can proceed to process block 706 or end if there are no further C-plane messages received that are to be processed.

[0081] Otherwise, if at decision block 738, the number of sections is greater than or equal to one, the method 700 proceeds to process block 742. At process block 742, the next section description can be selected and symInc, numPrbc, numSymbol, ef read. Method 700 can then proceed to decision block 744, which again checks whether symInc is equal to one, similar to decision block 712, which handles the symInc value for the first section (e.g., process block 710), whereas decision block 744 handles the symInc value for subsequent sections. If, at decision block 744, symInc is equal to one, then at process block 746 the current symbol is set to the previous section's last symbol plus one. If, at decision block 744, symInc is not equal to one, then at process block 748, the current symbol is set to the previous section's start symbol. In either case, method 700 proceeds from the process block branches of 746 and 748 to decision block 718.

[0082] Referring now to FIG. 8, exemplary method 800 is depicted. Method 800 can finalize the counters and update a bitmap to indicate PRB allocation in accordance with some example embodiments of this disclosure. At process block 802, a device comprising a processor can create or initialize a bitmap for a given data direction (e.g., uplink or downlink), a given antenna, a given component carrier, and a given duration (e.g., frame, subframe, slot, . . . ). Initially, all bits of the bitmap can be set to “0”. In this example, a bit value of “1” indicates that a given symbol does not allocate any PRB, and is therefore blank. Likewise, in this example, a bit value of “0” indicates that the symbol allocates at least one PRB and is therefore not blank.

[0083] At data block 804, an o-ran-uplane-conf.yang can be read and the total number of PRBs per symbol can thus be determined for each eAxCId. It is noted that in other embodiments, the total number of PRBs per symbol can be determined in other ways, e.g., as a function of subcarrier spacing and channel bandwidth, examples of which are indicated at FIG. 5C.

[0084] At process block 806 bitmaps corresponding to each eAxCId can be updated by examining the associated counter. For example, if the associated counter is equal to the total number of PRBs per symbol, then that indicates that the counter counted every single PRB as blank and therefore the symbol is blank. Otherwise, if the counter is not equal to the total number of PRBs per symbol, then that indicates that at least some (or one) PRB was not counted as blank by the counter and the associated symbol is therefore not blank.

[0085] At process block 808, individual bitmaps associated with a given eAxCId can be combined on each transceiver in order to generate a valid bitmap for the entire antenna branch. In more detail, a first bitmap for a first eAxCId can be logically ANDed with a second bitmap for a second eAxCId belonging to the same antenna branch, where the first and second eAxCId can represent respective component carriers of that antenna branch. If there are more than two component carriers and or eAxCIds, then additional AND operations to combine can be performed.

[0086] Referring now to FIG. 9, exemplary method 900 is depicted. Method 900 can identify non-blank symbols that are scheduled or allocated in accordance with some example embodiments of this disclosure. While method 900 describes a complete method, in some embodiments, method 900 can include one or more elements of method 1000, as illustrated by insert A.

[0087] At reference numeral 902, a device comprising a processor can receive control plane data. The control plane data can describe allocation of physical resource blocks to be subsequently communicated between a distributed unit and a radio unit via user plane data during a defined slot.

[0088] At reference numeral 904, the device can initialize a bitmap having a respective bit corresponding to a respective symbol that is to be communicated during the defined slot. At reference 906, the device can set respective bits of the bitmap to either a first value or to a second value. The first value can indicate that a corresponding symbol does not comprise any of the physical resource blocks to be subsequently communicated during the defined slot. Hence, the first value can indicate that the symbol associated with that bit of the bitmap is blank. The second value can indicate that the corresponding symbol comprises at least one physical resource block to be subsequently communicated during the defined slot. Hence, the second value can indicate that the associated symbol is not blank.

[0089] At reference numeral 908, the device can identify a group of target messages that satisfy a criterion of being of section type 0. Thus, membership to the group of target messages can be a function of the message type, where in this case, the group of target messages includes only those messages of section type 0 and/or excludes other C-plane messages.

[0090] At reference numeral 910, parse the group of target messages to determine whether the respective symbol to be subsequently communicated during the defined slot comprises at least one physical resource block. Method 900 can proceed to insert A, which gives additional detail regarding the parsing procedure and is further described in connection with FIG. 10, or continue to reference numeral 912.

[0091] At reference numeral 912, the device can set the respective bit, of the respective bits, corresponding to the respective symbol, to the first value or the second value. Whether the respective bit is set to the first value or the second value can be based on results of the parsing of the group of target messages of section type 0 detailed at reference numeral 910. For example, such can depend on counter values that count the number of blank PRBs associated with a given symbol, as further detailed with reference to FIG. 10. Thereafter, method 900 can terminate.

[0092] Turning now to FIG. 10, exemplary method 1000 is depicted. Method 1000 can provide for utilizing blank PRB counters in connection with identifying non-blank symbols that are scheduled or allocated in accordance with some example embodiments of this disclosure.

[0093] At reference numeral 1002, the device introduced at reference numeral 902 comprising a processor can perform the parsing procedure, as indicated at reference numeral 910. As part of this parsing procedure or another procedure, the device can initialize a respective counter that corresponds to the respective bit of the bitmap to zero. It is appreciated that a different counter can be initialized for each bit of the bitmap as well as for each bit of many different bitmaps. Hence, a given bitmap of 14 bits that characterizes blank/non-blank symbols of a normal prefix slot can correspond to a group of counters having 14 counters.

[0094] At reference numeral 1004, the device can, in response to identification of the respective symbol within a message of the group of target messages, increment the respective counter by an amount of contiguous physical resource blocks per data section description. The amount of continuous physical resource blocks per data section description can be found in the data section descriptions numPrbc field.

[0095] At reference numeral 1006, the device can, in response to a determination that all of the group of target messages has been parsed, set the respective bit to the first value or to the second value based on a defined condition being determined to be satisfied. The defined condition can be satisfied if a counter value indicated by the counter is determined to equal a configured number of physical resource blocks for the symbol. In operation, the device can set the respective bit to the first value, e.g., when the counter value equals the total number of physical resource blocks configured for the symbol since, in that case, the condition is satisfied and satisfying the condition essentially means that all PRBs of a given symbol were counted to be blank. Otherwise, the device can set the respective bit to the second value, e.g., when the counter value does not equal or is less than the total number of physical resource blocks configured for the symbol since, in that case, the condition is not satisfied, essentially indicating that not all PRBs of a given symbol were counted to be blank.

[0096] In order to provide additional context for various embodiments described herein, FIG. 11 and the following discussion are intended to provide a brief, general description of a suitable computing environment 1100 in 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.

[0097] Generally, program modules include routines, programs, components, data structures, etc., that perform particular tasks or implement particular abstract data types. Moreover, those skilled in the art will appreciate that the various 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.

[0098] 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.

[0099] 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.

[0100] 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, are to be understood to 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.

[0101] 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.

[0102] 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.

[0103] With reference again to FIG. 11, the example environment 1100 for implementing various embodiments described herein includes a computer 1102, the computer 1102 including a processing unit 1104, a system memory 1106 and a system bus 1108. The system bus 1108 couples system components including, but not limited to, the system memory 1106 to the processing unit 1104. The processing unit 1104 can be any of various commercially available processors. Dual microprocessors and other multi-processor architectures can also be employed as the processing unit 1104.

[0104] The system bus 1108 can 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 memory 1106 includes ROM 1110 and RAM 1112. A basic input/output system (BIOS) can be stored in a non-volatile 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 computer 1102, such as during startup. The RAM 1112 can also include a high-speed RAM such as static RAM for caching data.

[0105] The computer 1102 further includes an internal hard disk drive (HDD) 1114 (e.g., EIDE, SATA), one or more external storage devices 1116 (e.g., a magnetic floppy disk drive (FDD) 1116, a memory stick or flash drive reader, a memory card reader, etc.) and an optical disk drive 1120 (e.g., which can read or write from a CD-ROM disc, a DVD, a BD, etc.). While the internal HDD 1114 is illustrated as located within the computer 1102, the internal HDD 1114 can also be configured for external use in a suitable chassis (not shown). Additionally, while not shown in environment 1100, a solid state drive (SSD) could be used in addition to, or in place of, an HDD 1114. The HDD 1114, external storage device(s) 1116 and optical disk drive 1120 can be connected to the system bus 1108 by an HDD interface 1124, an external storage interface 1126 and an optical drive interface 1128, respectively. The interface 1124 for external drive implementations can include at least one or both of Universal Serial Bus (USB) and Institute of Electrical and Electronics Engineers (IEEE) 1194 interface technologies. Other external drive connection technologies are within contemplation of the embodiments described herein.

[0106] The drives and their associated computer-readable storage media provide nonvolatile storage of data, data structures, computer-executable instructions, and so forth. For the computer 1102, 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, it should be appreciated by those skilled in the art that 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.

[0107] A number of program modules can be stored in the drives and RAM 1112, including an operating system 1130, one or more application programs 1132, other program modules 1134 and program data 1136. All or portions of the operating system, applications, modules, and/or data can also be cached in the RAM 1112. The systems and methods described herein can be implemented utilizing various commercially available operating systems or combinations of operating systems.

[0108] Computer 1102 can optionally comprise emulation technologies. For example, a hypervisor (not shown) or other intermediary can emulate a hardware environment for operating system 1130, and the emulated hardware can optionally be different from the hardware illustrated in FIG. 11. In such an embodiment, operating system 1130 can comprise one virtual machine (VM) of multiple VMs hosted at computer 1102. Furthermore, operating system 1130 can provide runtime environments, such as the Java runtime environment or the .NET framework, for applications 1132. Runtime environments are consistent execution environments that allow applications 1132 to run on any operating system that includes the runtime environment. Similarly, operating system 1130 can support containers, and applications 1132 can 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.

[0109] Further, computer 1102 can be enable 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 computer 1102, 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.

[0110] A user can enter commands and information into the computer 1102 through one or more wired/wireless input devices, e.g., a keyboard 1138, a touch screen 1140, and a pointing device, such as a mouse 1142. 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 unit 1104 through an input device interface 1144 that can be coupled to the system bus 1108, 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.

[0111] A monitor 1146 or other type of display device can be also connected to the system bus 1108 via an interface, such as a video adapter 1148. In addition to the monitor 1146, a computer typically includes other peripheral output devices (not shown), such as speakers, printers, etc.

[0112] The computer 1102 can 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) 1150. The remote computer(s) 1150 can 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 computer 1102, although, for purposes of brevity, only a memory/storage device 1152 is illustrated. The logical connections depicted include wired/wireless connectivity to a local area network (LAN) 1154 and/or larger networks, e.g., a wide area network (WAN) 1156. 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.

[0113] When used in a LAN networking environment, the computer 1102 can be connected to the local network 1154 through a wired and/or wireless communication network interface or adapter 1158. The adapter 1158 can facilitate wired or wireless communication to the LAN 1154, which can also include a wireless access point (AP) disposed thereon for communicating with the adapter 1158 in a wireless mode.

[0114] When used in a WAN networking environment, the computer 1102 can include a modem 1160 or can be connected to a communications server on the WAN 1156 via other means for establishing communications over the WAN 1156, such as by way of the Internet. The modem 1160, which can be internal or external and a wired or wireless device, can be connected to the system bus 1108 via the input device interface 1144. In a networked environment, program modules depicted relative to the computer 1102 or portions thereof, can be stored in the remote memory/storage device 1152. It will be appreciated that the network connections shown are example and other means of establishing a communications link between the computers can be used.

[0115] When used in either a LAN or WAN networking environment, the computer 1102 can access cloud storage systems or other network-based storage systems in addition to, or in place of, external storage devices 1116 as described above. Generally, a connection between the computer 1102 and a cloud storage system can be established over a LAN 1154 or WAN 1156 e.g., by the adapter 1158 or modem 1160, respectively. Upon connecting the computer 1102 to an associated cloud storage system, the external storage interface 1126 can, with the aid of the adapter 1158 and/or modem 1160, manage storage provided by the cloud storage system as it would other types of external storage. For instance, the external storage interface 1126 can be configured to provide access to cloud storage sources as if those sources were physically connected to the computer 1102.

[0116] The computer 1102 can 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.

[0117] Wi-Fi, or Wireless Fidelity, allows connection to the Internet from a couch at home, a bed in a hotel room, or a conference room at work, without wires. Wi-Fi is a wireless technology similar to that used in a cell phone that enables such devices, e.g., computers, to send and receive data indoors and out; anywhere within the range of a base station. Wi-Fi networks use radio technologies called IEEE 802.11 (a, b, g, n, etc.) to provide secure, reliable, fast wireless connectivity. A Wi-Fi network can be used to connect computers to each other, to the Internet, and to wired networks (which use IEEE 802.3 or Ethernet). Wi-Fi networks operate in the unlicensed 5 GHz radio band at a 54 Mbps (802.11a) data rate, and/or a 2.4 GHz radio band at an 11 Mbps (802.11b), a 54 Mbps (802.11g) data rate, or up to a 600 Mbps (802.11n) data rate for example, or with products that contain both bands (dual band), so the networks can provide real-world performance similar to the basic “10BaseT” wired Ethernet networks used in many offices.

[0118] 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. In this regard, 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.

[0119] In the subject specification, terms such as “data store,” 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 memory, or can include both volatile and nonvolatile memory. By way of illustration, and not limitation, nonvolatile memory can include read only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable ROM (EEPROM), or flash memory. Volatile memory can include random access memory (RAM), which acts as external cache memory. By way of illustration and not limitation, RAM is 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.

[0120] The illustrated example 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.

[0121] The systems and processes described above can be embodied within hardware, such as a single integrated circuit (IC) chip, multiple ICs, an application specific integrated circuit (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.

[0122] 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 API components.

[0123] 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 disks (e.g., compact disk (CD), digital versatile disk (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.

[0124] 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” and it therefore interchangeable with the term “and/or”. That is, unless specified otherwise, or clear from context, “X employs A or B” (or any like example) 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.

[0125] 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.