Patent Publication Number: US-2022217626-A1

Title: Facilitation of fast aiding radio access network intelligent controllers for 5g or other next generation network

Description:
RELATED APPLICATION 
     The subject patent application is a continuation of, and claims priority to, U.S. patent application Ser. No. 17/101,697, filed Nov. 23, 2020, and entitled “FACILITATION OF FAST AIDING RADIO ACCESS NETWORK INTELLIGENT CONTROLLERS FOR 5G OR OTHER NEXT GENERATION NETWORK,” the entirety of which application is hereby incorporated by reference herein. 
    
    
     TECHNICAL FIELD 
     This disclosure relates generally to facilitating fast aiding of radio access network intelligent controllers. For example, this disclosure relates to facilitating fast aiding of radio access network intelligent controllers for a 5G, or other next generation network, air interface. 
     BACKGROUND 
     5th generation (5G) wireless systems represent a next major phase of mobile telecommunications standards beyond the current telecommunications standards of 4 th  generation (4G). Rather than faster peak Internet connection speeds, 5G planning aims at higher capacity than current 4G, allowing a higher number of mobile broadband users per area unit, and allowing consumption of higher or unlimited data quantities. This would enable a large portion of the population to stream high-definition media many hours per day with their mobile devices, when out of reach of wireless fidelity hotspots. 5G research and development also aims at improved support of machine-to-machine communication, also known as the Internet of things, aiming at lower cost, lower battery consumption, and lower latency than 4G equipment. 
     The above-described background relating to facilitating fast aiding of radio access network intelligent controllers is merely intended to provide a contextual overview of some current issues, and is not intended to be exhaustive. Other contextual information may become further apparent upon review of the following detailed description. 
    
    
     
       BRIEF DESCRIPTION OF THE DRAWINGS 
       Non-limiting and non-exhaustive embodiments of the subject disclosure are described with reference to the following figures, wherein like reference numerals refer to like parts throughout the various views unless otherwise specified. 
         FIG. 1  illustrates an example wireless communication system in which a network node device (e.g., network node) and user equipment (UE) can implement various aspects and embodiments of the subject disclosure. 
         FIG. 2  illustrates an example schematic system block diagram of a fast aiding radio network intelligent controller. according to one or more embodiments. 
         FIG. 3  illustrates an example schematic system block diagram of fast aiding radio access network intelligent controllers according to one or more embodiments. 
         FIG. 4  illustrates an example schematic system block diagram of fast aiding radio access network intelligent controllers according to one or more embodiments. 
         FIG. 5  illustrates an example schematic system block diagram of a system of fast aiding radio network intelligent controllers. 
         FIG. 6  illustrates an example flow diagram for a method for fast aiding radio access network intelligent controllers for a 5G network according to one or more embodiments. 
         FIG. 7  illustrates an example flow diagram for a system for fast aiding radio access network intelligent controllers for a 5G network according to one or more embodiments. 
         FIG. 8  illustrates an example flow diagram for machine-readable medium for fast aiding radio access network intelligent controllers for a 5G network according to one or more embodiments. 
         FIG. 9  illustrates an example block diagram of an example mobile handset operable to engage in a system architecture that facilitates secure wireless communication according to one or more embodiments described herein. 
         FIG. 10  illustrates an example block diagram of an example computer operable to engage in a system architecture that facilitates secure wireless communication according to one or more embodiments described herein. 
     
    
    
     DETAILED DESCRIPTION 
     In the following description, numerous specific details are set forth to provide a thorough understanding of various embodiments. One skilled in the relevant art will recognize, however, that the techniques described herein can be practiced without one or more of the specific details, or with other methods, components, materials, etc. In other instances, well-known structures, materials, or operations are not shown or described in detail to avoid obscuring certain aspects. 
     Reference throughout this specification to “one embodiment,” or “an embodiment,” means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment. Thus, the appearances of the phrase “in one embodiment,” “in one aspect,” or “in an embodiment,” in various places throughout this specification are not necessarily all referring to the same embodiment. Furthermore, the particular features, structures, or characteristics may be combined in any suitable manner in one or more embodiments. 
     As utilized herein, terms “component,” “system,” “interface,” and the like are intended to refer to a computer-related entity, hardware, software (e.g., in execution), and/or firmware. For example, a component can be a processor, a process running on a processor, an object, an executable, a program, a storage device, and/or a computer. By way of illustration, an application running on a server and the server can be a component. One or more components can reside within a process, and a component can be localized on one computer and/or distributed between two or more computers. 
     Further, these components can execute from various machine-readable media having various data structures stored thereon. The components can 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, e.g., the Internet, a local area network, a wide area network, etc. 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; the electric or electronic circuitry can be operated by a software application or a firmware application executed by one or more processors; the one or more processors can be internal or external to the apparatus and can execute 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 include one or more processors therein to execute software and/or firmware that confer(s), at least in part, the functionality of the electronic components. In an aspect, a component can emulate an electronic component via a virtual machine, e.g., within a cloud computing system. 
     The words “exemplary” and/or “demonstrative” are used herein to mean serving as an example, instance, or illustration. For the avoidance of doubt, the subject matter disclosed herein is not limited by such examples. In addition, any aspect or design described herein as “exemplary” and/or “demonstrative” is not necessarily to be construed as preferred or advantageous over other aspects or designs, nor is it meant to preclude equivalent exemplary structures and techniques known to those of ordinary skill in the art. Furthermore, to the extent that the terms “includes,” “has,” “contains,” and other similar words are used in either the detailed description or the claims, such terms are intended to be inclusive—in a manner similar to the term “comprising” as an open transition word—without precluding any additional or other elements. 
     As used herein, the term “infer” or “inference” refers generally to the process of reasoning about, or inferring states of, the system, environment, user, and/or intent from a set of observations as captured via events and/or data. Captured data and events can include user data, device data, environment data, data from sensors, sensor data, application data, implicit data, explicit data, etc. Inference can be employed to identify a specific context or action, or can generate a probability distribution over states of interest based on a consideration of data and events, for example. 
     Inference can also refer to techniques employed for composing higher-level events from a set of events and/or data. Such inference results in the construction of new events or actions from a set of observed events and/or stored event data, whether the events are correlated in close temporal proximity, and whether the events and data come from one or several event and data sources. Various classification schemes and/or systems (e.g., support vector machines, neural networks, expert systems, Bayesian belief networks, fuzzy logic, and data fusion engines) can be employed in connection with performing automatic and/or inferred action in connection with the disclosed subject matter. 
     In addition, the disclosed subject matter 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 the disclosed subject matter. The term “article of manufacture” as used herein is intended to encompass a computer program accessible from any computer-readable device, machine-readable device, computer-readable carrier, computer-readable media, or machine-readable media. For example, computer-readable media can include, but are not limited to, a magnetic storage device, e.g., hard disk; floppy disk; magnetic strip(s); an optical disk (e.g., compact disk (CD), a digital video disc (DVD), a Blu-ray Disc™ (BD)); a smart card; a flash memory device (e.g., card, stick, key drive); and/or a virtual device that emulates a storage device and/or any of the above computer-readable media. 
     As an overview, various embodiments are described herein to facilitate fast aiding of radio access network intelligent controllers for a 5G air interface or other next generation networks. For simplicity of explanation, the methods are depicted and described as a series of acts. It is to be understood and appreciated that the various embodiments are not limited by the acts illustrated and/or by the order of acts. For example, acts can occur in various orders and/or concurrently, and with other acts not presented or described herein. Furthermore, not all illustrated acts may be desired to implement the methods. In addition, the methods could alternatively be represented as a series of interrelated states via a state diagram or events. Additionally, the methods described hereafter are capable of being stored on an article of manufacture (e.g., a machine-readable medium) to facilitate transporting and transferring such methodologies to computers. The term article of manufacture, as used herein, is intended to encompass a computer program accessible from any computer-readable device, carrier, or media, including a non-transitory machine-readable medium. 
     It should be noted that although various aspects and embodiments have been described herein in the context of 5G, Universal Mobile Telecommunications System (UMTS), and/or Long Term Evolution (LTE), or other next generation networks, the disclosed aspects are not limited to 5G, a UMTS implementation, and/or an LTE implementation as the techniques can also be applied in 3G, 4G or LTE systems. For example, aspects or features of the disclosed embodiments can be exploited in substantially any wireless communication technology. Such wireless communication technologies can include UMTS, Code Division Multiple Access (CDMA), Wi-Fi, Worldwide Interoperability for Microwave Access (WiMAX), General Packet Radio Service (GPRS), Enhanced GPRS, Third Generation Partnership Project (3GPP), LTE, Third Generation Partnership Project 2 (3GPP2) Ultra Mobile Broadband (UMB), High Speed Packet Access (HSPA), Evolved High Speed Packet Access (HSPA+), High-Speed Downlink Packet Access (HSDPA), High-Speed Uplink Packet Access (HSUPA), Zigbee, or another IEEE 802.12 technology. Additionally, substantially all aspects disclosed herein can be exploited in legacy telecommunication technologies. 
     Described herein are systems, methods, articles of manufacture, and other embodiments or implementations that can facilitate fast aiding of radio access network intelligent controllers for a 5G network. Facilitating a fast aiding of radio access network intelligent controllers for a 5G network can be implemented in connection with any type of device with a connection to the communications network (e.g., a mobile handset, a computer, a handheld device, etc.) any Internet of things (JOT) device (e.g., toaster, coffee maker, blinds, music players, speakers, etc.), and/or any connected vehicles (cars, airplanes, space rockets, and/or other at least partially automated vehicles (e.g., drones)). In some embodiments the non-limiting term user equipment (UE) is used. It can refer to any type of wireless device that communicates with a radio network node in a cellular or mobile communication system. Examples of UE are target device, device to device (D2D) UE, machine type UE or UE capable of machine to machine (M2M) communication, PDA, Tablet, mobile terminals, smart phone, IOT device, laptop embedded equipped (LEE), laptop mounted equipment (LME), USB dongles, etc. The embodiments are applicable to single carrier as well as to multicarrier (MC) or carrier aggregation (CA) operation of the UE. The term carrier aggregation (CA) is also called (e.g., interchangeably called) “multi-carrier system”, “multi-cell operation”, “multi-carrier operation”, “multi-carrier” transmission and/or reception. 
     In some embodiments, the non-limiting term radio network node or simply network node is used. It can refer to any type of network node that serves a UE or network equipment connected to other network nodes or network elements or any radio node from where UE receives a signal. Non-exhaustive examples of radio network nodes are Node B, base station (BS), multi-standard radio (MSR) node such as MSR BS, eNode B, gNode B, network controller, radio network controller (RNC), base station controller (BSC), relay, donor node controlling relay, base transceiver station (BTS), edge nodes, edge servers, network access equipment, network access nodes, a connection point to a telecommunications network, such as an access point (AP), transmission points, transmission nodes, RRU, RRH, nodes in distributed antenna system (DAS), etc. 
     Cloud radio access networks (RAN) can enable the implementation of concepts such as software-defined network (SDN) and network function virtualization (NFV) in 5G networks. This disclosure can facilitate a generic channel state information framework design for a 5G network. Certain embodiments of this disclosure can include an SDN controller that can control routing of traffic within the network and between the network and traffic destinations. The SDN controller can be merged with the 5G network architecture to enable service deliveries via open application programming interfaces (“APIs”) and move the network core towards an all internet protocol (“IP”), cloud based, and software driven telecommunications network. The SDN controller can work with, or take the place of policy and charging rules function (“PCRF”) network elements so that policies such as quality of service and traffic management and routing can be synchronized and managed end to end. 
     5G, also called new radio (NR) access, networks can support the following: data rates of several tens of megabits per second supported for tens of thousands of users; 1 gigabit per second can be offered simultaneously to tens of workers on the same office floor; several hundreds of thousands of simultaneous connections can be supported for massive sensor deployments; spectral efficiency can be enhanced compared to 4G; improved coverage; enhanced signaling efficiency; and reduced latency compared to LTE. In multicarrier systems such as OFDM, each subcarrier can occupy bandwidth (e.g., subcarrier spacing). If the carriers use the same bandwidth spacing, then it can be considered a single numerology. However, if the carriers occupy different bandwidth and/or spacing, then it can be considered a multiple numerology. 
     This disclosure can enable quick and intelligent “aiding” (provision of help) of a radio access network intelligent controller (RIC), provided by other RICs, which can exist in a group of RICs operating together. The RICs can be close together or widely distributed, and in practice (for 5G) are expected to be distributed, where each individual RIC can help manage its local radio access network (RAN). That local RAN can be limited in extent, or it can cover a fairly broad area in which 5G RAN elements are distributed across. The type of help can be related to overloads in general, and/or can relate to specific tasks (e.g., performed by various disparate elements of a RIC such as different xAPPs, where each xAPP has a particular scope of action). Thus, the aid or help can be provided in a general sense, but more likely can be provided in a very intelligent sense depending on which RIC component or xAPP is experiencing an overload or other problem. This can enable a faster reaction to a RIC that is in trouble than traditional cloud techniques such as scaling or additional orchestration of instantiated capacity. Enabling more efficient and less-costly reactions to a RIC in trouble, can take into account the fact that multiple other RICs will potentially be available, and can be leveraged to provide needed aid via this disclosure. Fast-aiding RICs can add flexibility in terms of ways that a RIC in trouble can be helped/aided, and provide opportunities to leverage and expand future artificial intelligence (AI)/machine learning (ML) capabilities planned to be incorporated into RICs. Multiple RICs cooperatively working together can provide synergies and allow differentiated RICs to operate in “teams” both predefined and/or dynamically (e.g., under policy or AI/ML control) defined. 
     RICs can manage RANs, in which events and conditions change rapidly. As the tasks performed by RICs become more important over time, the loss of RIC functionality will become more and more critical. Traditional failover techniques can help restore operations when RICs fail but are costly. Traditional load balancing techniques can help, but become too complex and too costly when applied to or are superimposed upon a widely distributed set of many RICs, each of which is doing different types of tasks (e.g., running different sets of applications using different data). A set of multiple RICs can be considered as a distributed system in its own right, where that set can be defined and re-defined, which can be advantageous for re-grouping RICs in various ways as needed. Solving problems with each RIC treated independently (e.g., as operating alone) is a simple approach, but is not optimal for scaling. A more intelligent, efficient, and effective approach can take into account the available capabilities at each moment from a group of RICs operating together. 
     What is needed is a way, in a multiple RIC situation, to determine when a particular RIC is experiencing difficulty and then help that RIC in a more intelligent manner very quickly. Consequently, events in the RAN (which happen fast in large number) do not continue without RIC oversight and control and accumulate so quickly that considerable negative consequences occur. “Fast aiding” technology can ensure that a RIC needing help receives help from one or more RICs able to provide portions of that help, ideally providing all the help that is needed without negatively impacting their own responsibilities and performance. 
     Fast aiding among RICs (FAAR) can use policy, workflow, AI/ML, and other mechanisms in to enable multiple RICs to very quickly provide various types of aid to each other, acting together as one entity. Groups of RICs can operate together as a means to being prepared to offer help, and then provide such help when needed. There are several FAAR help determination patterns. For instance, a RIC needing help (RNH) can initiate a help request. Based on policies, the RIC can request help from one or more other RICs, or simply generate/publish a general request for help. In another embodiment, a first RIC and/or other RICs in the same group can jointly determine that the first particular RIC needs help, or likely needs help, and designate it as an RNH. Other RICs in the same group as a first RIC can independently determine that the first RIC needs help, or likely needs help, and designate the first RIC as an RNH. If a correlation of multiple RIC (CMRIC) is configured, functions in the CMRIC called “help determination” submodules can determine which RIC/RICs need help, or likely need help, and designate those RICs as RNHs. For example, an CMRIC can be hosted in the cloud and provide negotiation assistance and/or aid processes with one RIC on behalf of the RIC that needs help. 
     With regards to FAAR help implementation patterns, a RIC can forward a request to another RIC(s) to get help or the RIC needing help can work with the requestor(s) and the helping RIC(s) to establish a new relationship and the requestor(s) and helping RIC(s) will assume that part of the function. It should be noted that the request and/or forwarding of the request can be based on a distance between the fast aiding radio access network intelligent controllers. In conjunction with any of the above, a chain migration concept can be utilized. The chain migration concept can allow the helping RIC to move some of its non-core functions to another RIC and start helping the RIC that needs its help. The chaining help mechanism can go on within the same group and sometimes be extended to other groups. A grasp control concept can be utilized when one RIC fails to communicate to the group, which can prompt other RICs in the group to take control to help the troubled RIC. The helping RIC can communicate to “some requestors” of the troubled RIC and grasp control for those tasks. 
     A help determine module can determine what “help” is needed by a RIC, and is possible. For example, the help determination module can determine tasks that can be temporarily moved, moved in full, or in part (e.g., 100% moved or can be 75% moved, including designating an RNH). There are multiple types of help comprising general RIC platform help (% load), particular parts/functions of RIC platform help, particular xAPPs (e.g., software programs written as a simple function), various different types of “overloads” (e.g., networking, processing power, security aspects, or the like. A helping group determination module (HGDM) can determine a RIC group for a specific helping instance (e.g., breakup &amp; transfer of tasks). The HGDM can be configured, dynamic, based on the specific type of help needed, and/or which RIC and where it is relative to the RNH. A database of capabilities can detail the functions available in potential helping RICs (e.g., view of utilization and current status, capability to help, each helping RIC&#39;s current ability to help). Additionally, policies can be used, and as ML/AI experience and data become available, the data can be used to train ML models over time. 
     A mechanism determination module (MDM) can be used for a specific helping instance. The mechanisms can be different for each helping RIC (e.g., what technical mechanisms can be used) or conditional upon the particular situation. Mechanisms to determine helpers can include; a variety of algorithms, policies, heuristics, and/or AI/ML which can be selected. Mechanisms for determining a best routing to a help the RIC taking on tasks (e.g., helping RICs given configuration updates and any needed policies to accomplish tasks moved from RNH. Functionality/load splitting can assist helping RICs to assume part of the processing load from the RNH functionality splitting (e.g., helping RICs divide up the help, which might be xAPP or functionality/task-based, among them). Selected mechanism can be used to select heling RICs to perform tasks that need to be moved, or do the helping. 
     A task assignment module (TAM) can use policies and/or ML/AI to train ML models over time to categorize tasks (e.g., ping latency, info needed to process can it be moved to the helping RIC, cost of moving, cost of simply not doing the task, and the like). 
     Additionally, a responsibility transfer module (RTM) can transfer responsibility for the moved tasks to each of the RICs that will help. The RTM can later be triggered by the HDM to undo the responsibility transfer (e.g., move tasks back to original RIC). The RTM can orchestrate transfer responsibility, provide needed info such as enrichment information to helping RICs, and provide any associated information needed to process the transferred task (e.g., the helped RIC&#39;s local RAN data). 
     An enrichment data module (EDM) can host info needed for each task and current source and specifics. The info can be routed (e.g., by the first RIC, aiding RIC, middlebox, bus, etc.) to helping RICs. A local RAN can be prompted to communicate with helping RICs, in whole or via specific filters to direct partial communications. The helping RIC can be given specific customizations for helping tasks as needed to ensure consistent processing per how the first RIC was performing the task. 
     When the aided RIC has been helped, transferred responsibilities can be deactivated (for each helping RIC), which can restore tasks to the aided RIC, until eventually the aided RIC is no longer being helped (e.g., is replaced, restarted, and/or re-instantiated). Temporarily moved tasks (e.g., being performed by the various helping RICs) can be processed, and results from the helping RICs can be received and sent to their appropriate destinations/consumer (e.g., to the original helped RIC/RNH/aided RIC). The original helped RIC/RNH/aided RIC can now use those results directly in another task, or can operate as a “proxy” for another destination). The above steps can be performed recursively as a function of time, policies, trigger events, or the like as things change on any of the RICs. 
     In one embodiment, described herein is a method comprising receiving, by a first radio access network intelligent controller comprising a processor, processing transfer request data representative of a processing transfer request from a second radio access network intelligent controller. In response to receiving the processing transfer request, the method can comprise determining, by the first radio access network intelligent controller, a third radio access network intelligent controller to transfer a processing capability to facilitate the processing request from the second radio access network intelligent controller. Furthermore, in response to determining the third radio access network intelligent controller to transfer the processing capability, the method can comprise transferring, by the first radio access network intelligent controller, the processing capability to the third radio access network intelligent controller. Additionally, in response to transferring the processing capability, the method can comprise undertaking, by the first radio access network intelligent controller, a processing function on behalf of the second radio access network intelligent controller. 
     According to another embodiment, a system can facilitate, the in response to a threshold amount of time being determined to have elapsed, wherein the threshold amount of time is associated with a failed communication of a first radio access network intelligent controller, prompting a second radio access network intelligent controller to initiate an undertaking of a first task of the first radio access network intelligent controller. In response to prompting of the second radio access network intelligent controller, the system can facilitate offloading a second task of the second radio access network intelligent controller to a third radio access network intelligent controller. Furthermore, in response to offloading the second task to the third radio access network intelligent controller, the system can facilitate the undertaking of the first task of the first radio access network intelligent controller by the second radio access network intelligent controller. 
     According to yet another embodiment, described herein is a machine-readable medium that can perform the operations comprising determining an anticipated processing failure associated with a first radio access network intelligent controller. In response to determining the anticipated processing failure, the machine-readable medium can perform the operations comprising prompting a second radio access network intelligent controller to initiate performance of a first task that was to be performed by the first radio access network intelligent controller. In response to prompting the second radio access network intelligent controller, the machine-readable medium can perform the operations comprising facilitating offloading a second task that was to be performed by the second radio access network intelligent controller to a third radio access network intelligent controller. Additionally, in response to offloading the second task, the machine-readable medium can perform the operations comprising facilitating the performance of the first task that was to be performed by the first radio access network intelligent controller by the second radio access network intelligent controller. 
     These and other embodiments or implementations are described in more detail below with reference to the drawings. 
     Referring now to  FIG. 1 , illustrated is an example wireless communication system  100  in accordance with various aspects and embodiments of the subject disclosure. In one or more embodiments, system  100  can include one or more user equipment UEs  102 . The non-limiting term user equipment can refer to any type of device that can communicate with a network node in a cellular or mobile communication system. A UE can have one or more antenna panels having vertical and horizontal elements. Examples of a UE include a target device, device to device (D2D) UE, machine type UE or UE capable of machine to machine (M2M) communications, personal digital assistant (PDA), tablet, mobile terminals, smart phone, laptop mounted equipment (LME), universal serial bus (USB) dongles enabled for mobile communications, a computer having mobile capabilities, a mobile device such as cellular phone, a laptop having laptop embedded equipment (LEE, such as a mobile broadband adapter), a tablet computer having a mobile broadband adapter, a wearable device, a virtual reality (VR) device, a heads-up display (HUD) device, a smart car, a machine-type communication (MTC) device, and the like. User equipment UE  102  can also include IOT devices that communicate wirelessly. 
     In various embodiments, system  100  is or includes a wireless communication network serviced by one or more wireless communication network providers. In example embodiments, a UE  102  can be communicatively coupled to the wireless communication network via a network node  104 . The network node (e.g., network node device) can communicate with user equipment (UE), thus providing connectivity between the UE and the wider cellular network. The UE  102  can send transmission type recommendation data to the network node  104 . The transmission type recommendation data can include a recommendation to transmit data via a closed loop MIMO mode and/or a rank-1 precoder mode. 
     A network node can have a cabinet and other protected enclosures, an antenna mast, and multiple antennas for performing various transmission operations (e.g., MIMO operations). Network nodes can serve several cells, also called sectors, depending on the configuration and type of antenna. In example embodiments, the UE  102  can send and/or receive communication data via a wireless link to the network node  104 . The dashed arrow lines from the network node  104  to the UE  102  represent downlink (DL) communications and the solid arrow lines from the UE  102  to the network nodes  104  represents an uplink (UL) communication. 
     System  100  can further include one or more communication service provider networks  106  that facilitate providing wireless communication services to various UEs, including UE  102 , via the network node  104  and/or various additional network devices (not shown) included in the one or more communication service provider networks  106 . The one or more communication service provider networks  106  can include various types of disparate networks, including but not limited to: cellular networks, femto networks, picocell networks, microcell networks, internet protocol (IP) networks Wi-Fi service networks, broadband service network, enterprise networks, cloud based networks, and the like. For example, in at least one implementation, system  100  can be or include a large scale wireless communication network that spans various geographic areas. According to this implementation, the one or more communication service provider networks  106  can be or include the wireless communication network and/or various additional devices and components of the wireless communication network (e.g., additional network devices and cell, additional UEs, network server devices, etc.). The network node  104  can be connected to the one or more communication service provider networks  106  via one or more backhaul links  108 . For example, the one or more backhaul links  108  can include wired link components, such as a T1/E1 phone line, a digital subscriber line (DSL) (e.g., either synchronous or asynchronous), an asymmetric DSL (ADSL), an optical fiber backbone, a coaxial cable, and the like. The one or more backhaul links  108  can also include wireless link components, such as but not limited to, line-of-sight (LOS) or non-LOS links which can include terrestrial air-interfaces or deep space links (e.g., satellite communication links for navigation). 
     Wireless communication system  100  can employ various cellular systems, technologies, and modulation modes to facilitate wireless radio communications between devices (e.g., the UE  102  and the network node  104 ). While example embodiments might be described for 5G new radio (NR) systems, the embodiments can be applicable to any radio access technology (RAT) or multi-RAT system where the UE operates using multiple carriers e.g., LTE FDD/TDD, GSM/GERAN, CDMA2000 etc. 
     For example, system  100  can operate in accordance with global system for mobile communications (GSM), universal mobile telecommunications service (UMTS), long term evolution (LTE), LTE frequency division duplexing (LTE FDD, LTE time division duplexing (TDD), high speed packet access (HSPA), code division multiple access (CDMA), wideband CDMA (WCMDA), CDMA2000, time division multiple access (TDMA), frequency division multiple access (FDMA), multi-carrier code division multiple access (MC-CDMA), single-carrier code division multiple access (SC-CDMA), single-carrier FDMA (SC-FDMA), orthogonal frequency division multiplexing (OFDM), discrete Fourier transform spread OFDM (DFT-spread OFDM) single carrier FDMA (SC-FDMA), Filter bank based multi-carrier (FBMC), zero tail DFT-spread-OFDM (ZT DFT-s-OFDM), generalized frequency division multiplexing (GFDM), fixed mobile convergence (FMC), universal fixed mobile convergence (UFMC), unique word OFDM (UW-OFDM), unique word DFT-spread OFDM (UW DFT-Spread-OFDM), cyclic prefix OFDM CP-OFDM, resource-block-filtered OFDM, Wi Fi, WLAN, WiMax, and the like. However, various features and functionalities of system  100  are particularly described wherein the devices (e.g., the UEs  102  and the network node  104 ) of system  100  are configured to communicate wireless signals using one or more multi carrier modulation schemes, wherein data symbols can be transmitted simultaneously over multiple frequency subcarriers (e.g., OFDM, CP-OFDM, DFT-spread OFMD, UFMC, FMBC, etc.). The embodiments are applicable to single carrier as well as to multicarrier (MC) or carrier aggregation (CA) operation of the UE. The term carrier aggregation (CA) is also called (e.g., interchangeably called) “multi-carrier system”, “multi-cell operation”, “multi-carrier operation”, “multi-carrier” transmission and/or reception. Note that some embodiments are also applicable for Multi RAB (radio bearers) on some carriers (that is data plus speech is simultaneously scheduled). 
     In various embodiments, system  100  can be configured to provide and employ 5G wireless networking features and functionalities. 5G wireless communication networks are expected to fulfill the demand of exponentially increasing data traffic and to allow people and machines to enjoy gigabit data rates with virtually zero latency. Compared to 4G, 5G supports more diverse traffic scenarios. For example, in addition to the various types of data communication between conventional UEs (e.g., phones, smartphones, tablets, PCs, televisions, Internet enabled televisions, etc.) supported by 4G networks, 5G networks can be employed to support data communication between smart cars in association with driverless car environments, as well as machine type communications (MTCs). Considering the drastic different communication demands of these different traffic scenarios, the ability to dynamically configure waveform parameters based on traffic scenarios while retaining the benefits of multi carrier modulation schemes (e.g., OFDM and related schemes) can provide a significant contribution to the high speed/capacity and low latency demands of 5G networks. With waveforms that split the bandwidth into several sub-bands, different types of services can be accommodated in different sub-bands with the most suitable waveform and numerology, leading to an improved spectrum utilization for 5G networks. 
     To meet the demand for data centric applications, features of proposed 5G networks may include: increased peak bit rate (e.g., 20 Gbps), larger data volume per unit area (e.g., high system spectral efficiency—for example about 3.5 times that of spectral efficiency of long term evolution (LTE) systems), high capacity that allows more device connectivity both concurrently and instantaneously, lower battery/power consumption (which reduces energy and consumption costs), better connectivity regardless of the geographic region in which a user is located, a larger numbers of devices, lower infrastructural development costs, and higher reliability of the communications. Thus, 5G networks may allow for: data rates of several tens of megabits per second should be supported for tens of thousands of users, 1 gigabit per second to be offered simultaneously to tens of workers on the same office floor, for example; several hundreds of thousands of simultaneous connections to be supported for massive sensor deployments; improved coverage, enhanced signaling efficiency; reduced latency compared to LTE. 
     The 5G access network may utilize higher frequencies (e.g., &gt;6 GHz) to aid in increasing capacity. Currently, much of the millimeter wave (mmWave) spectrum, the band of spectrum between 30 gigahertz (GHz) and 300 GHz is underutilized. The millimeter waves have shorter wavelengths that range from 10 millimeters to 1 millimeter, and these mmWave signals experience severe path loss, penetration loss, and fading. However, the shorter wavelength at mmWave frequencies also allows more antennas to be packed in the same physical dimension, which allows for large-scale spatial multiplexing and highly directional beamforming. 
     Performance can be improved if both the transmitter and the receiver are equipped with multiple antennas. Multi-antenna techniques can significantly increase the data rates and reliability of a wireless communication system. The use of multiple input multiple output (MIMO) techniques, which was introduced in the third-generation partnership project (3GPP) and has been in use (including with LTE), is a multi-antenna technique that can improve the spectral efficiency of transmissions, thereby significantly boosting the overall data carrying capacity of wireless systems. The use of multiple-input multiple-output (MIMO) techniques can improve mmWave communications, and has been widely recognized a potentially important component for access networks operating in higher frequencies. MIMO can be used for achieving diversity gain, spatial multiplexing gain and beamforming gain. For these reasons, MIMO systems are an important part of the 3rd and 4th generation wireless systems, and are planned for use in 5G systems. 
     Referring now to  FIG. 2 , illustrated is an example schematic system block diagram of a fast aiding radio network intelligent controller  200 . Repetitive description of like elements employed in other embodiments described herein is omitted for sake of brevity. 
     In the embodiment shown in  FIG. 2 , a fast aiding radio access network intelligent controller  200  can comprise a help determination component  202  a help group determination component  204 , a mechanism determination component  206 , a task assignment component  208 , a responsibility transfer component  210 , an enrichment data component  212 , a processor  216 , and a memory  214 . It should be noted that any of the aforementioned components or their sub-components, processor  216 , and memory  214  can bi-directionally communicate with each other. It should also be noted that in alternative embodiments that other components including, but not limited to the sub-components, processor  216 , and/or memory  214 , can be external to the fast aiding radio access network intelligent controller  200 , as shown in  FIG. 2 . 
     Aspects of the processor  216  can constitute machine-executable component(s) embodied within machine(s), e.g., embodied in one or more computer readable mediums (or media) associated with one or more machines. Such component(s), when executed by the one or more machines, e.g., computer(s), computing device(s), virtual machine(s), etc. can cause the machine(s) to perform the operations described by the fast aiding radio access network intelligent controller  200 . In an aspect, the fast aiding radio access network intelligent controller  200  can also include memory  214  that stores computer executable components and instructions. 
     The help determination component  202  can determine what “help” is needed by a RIC, and the help determination component  202  can determine what help is possible for the fast aiding radio access network intelligent controller  200  to provide. For example, the help determination component  202  can determine tasks that can be temporarily moved (for a defined period of time), moved fully, or moved in part (e.g., 100% moved or only 75% moved, including designating an RNH). There are multiple types of help including general RIC platform help (% load), particular parts/functions of RIC platform help, particular xAPP (e.g., software programs written as a simple function) assistance, various different types of “overloads” (e.g., networking, processing power, security aspects, or the like). The help group determination component  204  can determine a RIC group for a specific helping instance (e.g., breakup &amp; transfer of tasks). The help group determination component  204  can be configured, dynamic, based on the specific type of help needed, and/or which RIC and where it is relative to the RNH. A database of capabilities can detail the functions available in potential helping RICs (e.g., view of utilization and current status, capability to help, each helping RIC&#39;s current ability to help). Additionally, policies can be used, and as ML/AI experience and data become available, the data can be used to train ML models over time. 
     The mechanism determination component  206  can be used for a specific helping instance. The mechanisms can be different for each helping RIC (e.g., what technical mechanisms can be used) or conditional upon the particular situation. Mechanisms to determine helper RICs can include: a variety of algorithms, policies, heuristics, and/or AI/ML which can be selected. Mechanisms for determining a best route to a help the RIC taking on tasks (e.g., helping RICs given configuration updates and any needed policies to accomplish tasks moved from RNH. Functionality/load splitting can assist helping RICs to assume part of the processing load from the RNH functionality splitting (e.g., helping RICs can divide up the help, which might be xAPP or functionality/task-based, among them). The selected mechanism can be used to select helping RICs to perform tasks that need to be moved from the RNH, or do the helping. 
     The task assignment component  208  can use policies and/or ML/AI to train ML models over time to categorize tasks based on the following: ping latency, can the info needed to process be moved to the helping RIC, cost of moving, cost of simply not performing the task, and the like. 
     Additionally, the responsibility transfer component  210  can transfer responsibility for the moved tasks to each of the RICs that will help. The responsibility transfer component  210  can later be triggered by the help determination component  202  to undo the responsibility transfer (e.g., move tasks back to original RIC). The responsibility transfer component  210  can orchestrate transfer of responsibility, provide needed info such as enrichment information to helping RICs, and provide any associated information needed to process the transferred task (e.g., the helped RIC&#39;s local RAN data). 
     The enrichment data component  212  can host info needed for each task and current source and specifics. The info can be routed (e.g., by the first RIC, aided RIC, middlebox, bus, etc.) to helping RICs. A local RAN can be prompted to communicate with helping RICs, in whole or via specific filters to direct partial communications. The helping RIC can be given specific customizations for helping tasks as needed to ensure consistent processing per how the first RIC was performing the task. 
     Referring now to  FIG. 3  and  FIG. 4 , illustrated is an example schematic system block diagrams of fast aiding radio access network intelligent controllers according to one or more embodiments. 
     Two local clusters of gNodeBs  302 ,  304 ,  306  are depicted in  FIG. 3  and  FIG. 4 .  FIG. 3  illustrates the first group forms an edge cloud  308  with gNodeBs  302 ,  304 ,  306 . The second group of  FIG. 4  forms an edge cloud  308 , wherein the edge cloud  308  comprises a fast aiding radio access network intelligent controller  402  (e.g., CMRIC) in the edge cloud  308 . It should be noted that in some scenarios, gNodeBs can be a part of one edge cloud that does not comprise a CMRIC while also being a part of another edge cloud that does comprise a CMRIC. As depicted in  FIG. 4 , the fast aiding radio access network intelligent controller  402  (e.g., CMRIC) can be hosted in the cloud and provide negotiation assistance and/or facilitate resources from the fast aiding radio access network intelligent controller  200   b  on behalf of the troubled gNodeB  302  (via the fast aiding radio access network intelligent controller  200   a ) that needs help. Each gNodeB s  302 ,  304 ,  306  can be enhanced with a set of core fast aiding radio access network intelligent controller  200   a ,  200   b ,  200   c  and a set of support modules. As depicted in  FIG. 3 , it should be noted that if a fast aiding radio access network intelligent controller (e.g., CMRIC) does not exist within the edge cloud  308 , then the fast aiding radio access network intelligent controllers  200   a ,  200   b ,  200   c  can be responsible for negotiating resources between each other without the supervision of the cloud-hosted fast aiding radio access network intelligent controller  402  (e.g., CMRIC). 
     If the CMRIC concept is used, as depicted in  FIG. 4 , the fast aiding radio access network intelligent controller  402 , residing in the edge cloud  308 , can support multiple gNodeBs  302 ,  304 ,  306 . Two basic ways to detect if a NR-RIC needs help are: (a) self-help-aware (SHA) model where the fast aiding radio access network intelligent controller  200   a  of the troubled gNodeB  302  detects it needs help from another fast aiding radio access network intelligent controller  200   c . In this case, it will go through its own core modules with the support from the supporting modules to determine how to get help from others; and (b) external-initiated-help (EIH) model where the neighboring fast aiding radio access network intelligent controller  200   c  in the same edge cloud using a voting mechanism to determine if a non-responding fast aiding radio access network intelligent controller  200   a  of a particular gNodeB  302  may need help. 
     This disclosure also supports more complicated cascading-help-extension (CHE) models. In the CHE model, if the fast aiding radio access network intelligent controller  200   b  of gNodeB  304  needs to help, gNodeB  302  may provide help, but if gNodeB  302  is overloaded, the fast aiding radio network intelligent controller  200   a  can initiate an action using the task assignment component  208  and the responsibility transfer component  210  to offload non-essential workload to gNodeB  306 . After that, gNodeB  302  will be able to meet the gNodeB  304  latency requirements when providing needed help to it. 
     Other processes can enable the fast aiding radio access network intelligent controller  200   a  to learn what are the neighboring fast aiding radio access network intelligent controller  200   b ,  200   c  that it needs to keep in communication with. A request latency estimator module (RLEM) can contain necessary policies and algorithms to estimate the latency requirements for each tasks running in xAPP or other software modules. Additionally, a consensus based voting module (CBVM) can provide policies driven by machine learning models to dynamically come up with a unified consensus if a particular neighboring fast aiding radio access network intelligent controller is in a situation where it may need external help. The consensus is shared among all fast aiding radio access network intelligent controller neighbors in an edge cloud so that a final consensus can be reached. Once a consensus is reached, the external fast aiding radio access network intelligent controllers can make a decision to take control and split up the tasks of the presumed troubled fast aiding radio access network intelligent controller. 
     Referring now to  FIG. 5  illustrates an example schematic system block diagram of a system of fast aiding radio network intelligent controllers. 
     As depicted in  FIG. 5 , the fast aiding radio network intelligent controller  200   b  can request assistance for gNodeB  304  from the fast aiding radio access network intelligent controller  200   a . However, at block  502 , the fast aiding radio access network intelligent controller  200   a  can evaluate its capabilities and determine that it does not have the necessary resources to share with the fast aiding radio access network intelligent controller  200   b . In this case, the fast aiding radio access network intelligent controller  200   a  can forward the request for assistance to the fast aiding radio access network intelligent controller  200   c . The fast aiding radio access network intelligent controller  200   c  can evaluate its capabilities at block  504 , and upon a determination that it will have the needed capabilities if it offloads a non-core function to the fast aiding radio access network intelligent controller  200   a , then the fast aiding radio access network intelligent controller  200   c  can begin assisting fast aiding radio access network intelligent controller  200   b  after the fast aiding radio access network intelligent controller  200   c  has offloaded its non-core functions to the fast aiding radio access network intelligent controller  200   a.    
     Referring now to  FIG. 6 , illustrated is an example flow diagram for a method for fast aiding radio access network intelligent controllers for a 5G network according to one or more embodiments. 
     At element  600 , the method can comprise receiving, by a first radio access network intelligent controller comprising a processor, processing transfer request data representative of a processing transfer request from a second radio access network intelligent controller. In response to receiving the processing transfer request, at element  602 , the method can comprise determining, by the first radio access network intelligent controller, a third radio access network intelligent controller to transfer a processing capability to facilitate the processing request from the second radio access network intelligent controller. Furthermore, in response to determining the third radio access network intelligent controller to transfer the processing capability, at element  604 , the method can comprise transferring, by the first radio access network intelligent controller, the processing capability to the third radio access network intelligent controller. Additionally, at element  606 , in response to transferring the processing capability, the method can comprise undertaking, by the first radio access network intelligent controller, a processing function on behalf of the second radio access network intelligent controller. 
     Referring now to  FIG. 7 , illustrated is an example flow diagram for a system for fast aiding radio access network intelligent controllers for a 5G network according to one or more embodiments. 
     At element  700 , the system can facilitate performance of the operations comprising prompting a second radio access network intelligent controller to initiate an undertaking of a first task of the first radio access network intelligent controller in response to a threshold amount of time being determined to have elapsed, wherein the threshold amount of time is associated with a failed communication of a first radio access network intelligent controller. At element  702 , in response to prompting of the second radio access network intelligent controller, the system can facilitate offloading a second task of the second radio access network intelligent controller to a third radio access network intelligent controller. Furthermore, at element  704 , in response to offloading the second task to the third radio access network intelligent controller, the system can facilitate the undertaking of the first task of the first radio access network intelligent controller by the second radio access network intelligent controller. 
     Referring now to  FIG. 8 , illustrated is an example flow diagram for machine-readable medium for fast aiding radio access network intelligent controllers for a 5G network according to one or more embodiments. 
     At element  800 , the machine-readable medium can perform the operations comprising determining an anticipated processing failure associated with a first radio access network intelligent controller. In response to determining the anticipated processing failure, at element  802 , the machine-readable medium can perform the operations comprising prompting a second radio access network intelligent controller to initiate performance of a first task that was to be performed by the first radio access network intelligent controller. In response to prompting the second radio access network intelligent controller, at element  804 , the machine-readable medium can perform the operations comprising facilitating offloading a second task that was to be performed by the second radio access network intelligent controller to a third radio access network intelligent controller. Additionally, at element  806 , in response to offloading the second task, the machine-readable medium can perform the operations comprising facilitating the performance of the first task that was to be performed by the first radio access network intelligent controller by the second radio access network intelligent controller. 
     Referring now to  FIG. 9 , illustrated is a schematic block diagram of an exemplary end-user device such as a mobile device  900  capable of connecting to a network in accordance with some embodiments described herein. Although a mobile handset  900  is illustrated herein, it will be understood that other devices can be a mobile device, and that the mobile handset  900  is merely illustrated to provide context for the embodiments of the various embodiments described herein. The following discussion is intended to provide a brief, general description of an example of a suitable environment  900  in which the various embodiments can be implemented. While the description includes a general context of computer-executable instructions embodied on a machine-readable medium, those skilled in the art will recognize that the innovation also can be implemented in combination with other program modules and/or as a combination of hardware and software. 
     Generally, applications (e.g., program modules) can 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 methods described herein can be practiced with other system configurations, including single-processor or multiprocessor systems, minicomputers, mainframe computers, 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. 
     A computing device can typically include a variety of machine-readable media. Machine-readable media can be any available media that can be accessed by the computer and includes both volatile and non-volatile media, removable and non-removable media. By way of example and not limitation, computer-readable media can include computer storage media and communication media. Computer storage media can include volatile and/or non-volatile media, removable and/or non-removable media implemented in any method or technology for storage of information, such as computer-readable instructions, data structures, program modules or other data. Computer storage media can include, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD ROM, digital video disk (DVD) or other optical disk storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can be accessed by the computer. 
     Communication media typically embodies computer-readable instructions, data structures, program modules or other data in a modulated data signal such as a carrier wave or other transport mechanism, and includes any information delivery media. The term “modulated data signal” means a signal that has one or more of its characteristics set or changed in such a manner as to encode information in the signal. By way of example, and not limitation, communication media includes wired media such as a wired network or direct-wired connection, and wireless media such as acoustic, RF, infrared and other wireless media. Combinations of the any of the above should also be included within the scope of computer-readable media. 
     The handset  900  includes a processor  902  for controlling and processing all onboard operations and functions. A memory  904  interfaces to the processor  902  for storage of data and one or more applications  906  (e.g., a video player software, user feedback component software, etc.). Other applications can include voice recognition of predetermined voice commands that facilitate initiation of the user feedback signals. The applications  906  can be stored in the memory  904  and/or in a firmware  908 , and executed by the processor  902  from either or both the memory  904  or/and the firmware  908 . The firmware  908  can also store startup code for execution in initializing the handset  900 . A communications component  910  interfaces to the processor  902  to facilitate wired/wireless communication with external systems, e.g., cellular networks, VoIP networks, and so on. Here, the communications component  910  can also include a suitable cellular transceiver  911  (e.g., a GSM transceiver) and/or an unlicensed transceiver  913  (e.g., Wi-Fi, WiMax) for corresponding signal communications. The handset  900  can be a device such as a cellular telephone, a PDA with mobile communications capabilities, and messaging-centric devices. The communications component  910  also facilitates communications reception from terrestrial radio networks (e.g., broadcast), digital satellite radio networks, and Internet-based radio services networks. 
     The handset  900  includes a display  912  for displaying text, images, video, telephony functions (e.g., a Caller ID function), setup functions, and for user input. For example, the display  912  can also be referred to as a “screen” that can accommodate the presentation of multimedia content (e.g., music metadata, messages, wallpaper, graphics, etc.). The display  912  can also display videos and can facilitate the generation, editing and sharing of video quotes. A serial I/O interface  914  is provided in communication with the processor  902  to facilitate wired and/or wireless serial communications (e.g., USB, and/or IEEE 1394) through a hardwire connection, and other serial input devices (e.g., a keyboard, keypad, and mouse). This supports updating and troubleshooting the handset  900 , for example. Audio capabilities are provided with an audio I/O component  916 , which can include a speaker for the output of audio signals related to, for example, indication that the user pressed the proper key or key combination to initiate the user feedback signal. The audio I/O component  916  also facilitates the input of audio signals through a microphone to record data and/or telephony voice data, and for inputting voice signals for telephone conversations. 
     The handset  900  can include a slot interface  918  for accommodating a SIC (Subscriber Identity Component) in the form factor of a card Subscriber Identity Module (SIM) or universal SIM  920 , and interfacing the SIM card  920  with the processor  902 . However, it is to be appreciated that the SIM card  920  can be manufactured into the handset  900 , and updated by downloading data and software. 
     The handset  900  can process IP data traffic through the communication component  910  to accommodate IP traffic from an IP network such as, for example, the Internet, a corporate intranet, a home network, a person area network, etc., through an ISP or broadband cable provider. Thus, VoIP traffic can be utilized by the handset  900  and IP-based multimedia content can be received in either an encoded or decoded format. 
     A video processing component  922  (e.g., a camera) can be provided for decoding encoded multimedia content. The video processing component  922  can aid in facilitating the generation, editing and sharing of video quotes. The handset  900  also includes a power source  924  in the form of batteries and/or an AC power subsystem, which power source  924  can interface to an external power system or charging equipment (not shown) by a power I/O component  926 . 
     The handset  900  can also include a video component  930  for processing video content received and, for recording and transmitting video content. For example, the video component  930  can facilitate the generation, editing and sharing of video quotes. A location tracking component  932  facilitates geographically locating the handset  900 . As described hereinabove, this can occur when the user initiates the feedback signal automatically or manually. A user input component  934  facilitates the user initiating the quality feedback signal. The user input component  934  can also facilitate the generation, editing and sharing of video quotes. The user input component  934  can include such conventional input device technologies such as a keypad, keyboard, mouse, stylus pen, and/or touch screen, for example. 
     Referring again to the applications  906 , a hysteresis component  936  facilitates the analysis and processing of hysteresis data, which is utilized to determine when to associate with the access point. A software trigger component  938  can be provided that facilitates triggering of the hysteresis component  938  when the Wi-Fi transceiver  913  detects the beacon of the access point. A SIP client  940  enables the handset  900  to support SIP protocols and register the subscriber with the SIP registrar server. The applications  906  can also include a client  942  that provides at least the capability of discovery, play and store of multimedia content, for example, music. 
     The handset  900 , as indicated above related to the communications component  910 , includes an indoor network radio transceiver  913  (e.g., Wi-Fi transceiver). This function supports the indoor radio link, such as IEEE 802.11, for the dual-mode GSM handset  900 . The handset  900  can accommodate at least satellite radio services through a handset that can combine wireless voice and digital radio chipsets into a single handheld device. 
     In order to provide additional context for various embodiments described herein,  FIG. 10  and the following discussion are intended to provide a brief, general description of a suitable computing environment  1000  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. 
     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 disclosed 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 media, machine-readable media, and/or communications media, which two terms are used herein differently from one another as follows. Computer-readable media or machine-readable media can be any available 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 media or machine-readable 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, 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. 
     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. 
     With reference again to  FIG. 10 , the example environment  1000  for implementing various embodiments of the aspects described herein includes a computer  1002 , the computer  1002  including a processing unit  1004 , a system memory  1006  and a system bus  1008 . The system bus  1008  couples system components including, but not limited to, the system memory  1006  to the processing unit  1004 . The processing unit  1004  can be any of various commercially available processors. Dual microprocessors and other multi-processor architectures can also be employed as the processing unit  1004 . 
     The system bus  1008  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  1006  includes ROM  1010  and RAM  1012 . 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  1002 , such as during startup. The RAM  1012  can also include a high-speed RAM such as static RAM for caching data. 
     The computer  1002  further includes an internal hard disk drive (HDD)  1014  (e.g., EIDE, SATA), one or more external storage devices  1016  (e.g., a magnetic floppy disk drive (FDD)  1016 , a memory stick or flash drive reader, a memory card reader, etc.) and an optical disk drive  1020  (e.g., which can read or write from a CD-ROM disc, a DVD, a BD, etc.). While the internal HDD  1014  is illustrated as located within the computer  1002 , the internal HDD  1014  can also be configured for external use in a suitable chassis (not shown). Additionally, while not shown in environment  1000 , a solid state drive (SSD) could be used in addition to, or in place of, an HDD  1014 . The HDD  1014 , external storage device(s)  1016  and optical disk drive  1020  can be connected to the system bus  1008  by an HDD interface  1024 , an external storage interface  1026  and an optical drive interface  1028 , respectively. The interface  1024  for external drive implementations can include at least one or both of Universal Serial Bus (USB) and Institute of Electrical and Electronics Engineers (IEEE) 1394 interface technologies. Other external drive connection technologies are within contemplation of the embodiments described herein. 
     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  1002 , 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. 
     A number of program modules can be stored in the drives and RAM  1012 , including an operating system  1030 , one or more application programs  1032 , other program modules  1034  and program data  1036 . All or portions of the operating system, applications, modules, and/or data can also be cached in the RAM  1012 . The systems and methods described herein can be implemented utilizing various commercially available operating systems or combinations of operating systems. 
     Computer  1002  can optionally include emulation technologies. For example, a hypervisor (not shown) or other intermediary can emulate a hardware environment for operating system  1030 , and the emulated hardware can optionally be different from the hardware illustrated in  FIG. 10 . In such an embodiment, operating system  1030  can include one virtual machine (VM) of multiple VMs hosted at computer  1002 . Furthermore, operating system  1030  can provide runtime environments, such as the Java runtime environment or the .NET framework, for applications  1032 . Runtime environments are consistent execution environments that allow applications  1032  to run on any operating system that includes the runtime environment. Similarly, operating system  1030  can support containers, and applications  1032  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. 
     Further, computer  1002  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  1002 , 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 computer  1002  through one or more wired/wireless input devices, e.g., a keyboard  1038 , a touch screen  1040 , and a pointing device, such as a mouse  1042 . 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  1004  through an input device interface  1044  that can be coupled to the system bus  1008 , 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 monitor  1046  or other type of display device can be also connected to the system bus  1008  via an interface, such as a video adapter  1048 . In addition to the monitor  1046 , a computer typically includes other peripheral output devices (not shown), such as speakers, printers, etc. 
     The computer  1002  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)  1050 . The remote computer(s)  1050  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  1002 , although, for purposes of brevity, only a memory/storage device  1052  is illustrated. The logical connections depicted include wired/wireless connectivity to a local area network (LAN)  1054  and/or larger networks, e.g., a wide area network (WAN)  1056 . 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 computer  1002  can be connected to the local network  1054  through a wired and/or wireless communication network interface or adapter  1058 . The adapter  1058  can facilitate wired or wireless communication to the LAN  1054 , which can also include a wireless access point (AP) disposed thereon for communicating with the adapter  1058  in a wireless mode. 
     When used in a WAN networking environment, the computer  1002  can include a modem  1060  or can be connected to a communications server on the WAN  1056  via other means for establishing communications over the WAN  1056 , such as by way of the Internet. The modem  1060 , which can be internal or external and a wired or wireless device, can be connected to the system bus  1008  via the input device interface  1044 . In a networked environment, program modules depicted relative to the computer  1002  or portions thereof, can be stored in the remote memory/storage device  1052 . 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. 
     When used in either a LAN or WAN networking environment, the computer  1002  can access cloud storage systems or other network-based storage systems in addition to, or in place of, external storage devices  1016  as described above. Generally, a connection between the computer  1002  and a cloud storage system can be established over a LAN  1054  or WAN  1056  e.g., by the adapter  1058  or modem  1060 , respectively. Upon connecting the computer  1002  to an associated cloud storage system, the external storage interface  1026  can, with the aid of the adapter  1058  and/or modem  1060 , manage storage provided by the cloud storage system as it would other types of external storage. For instance, the external storage interface  1026  can be configured to provide access to cloud storage sources as if those sources were physically connected to the computer  1002 . 
     The computer  1002  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. 
     The computer is 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, restroom), and telephone. This includes at least 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. 
     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, 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 2.4 and 5 GHz radio bands, at an 11 Mbps (802.11a) or 54 Mbps (802.11b) 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. 
     The above description of illustrated embodiments of the subject disclosure, including what is described in the Abstract, is not intended to be exhaustive or to limit the disclosed embodiments to the precise forms disclosed. While 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 subject matter has been described herein in connection with various embodiments and corresponding FIGs, where applicable, it is to be understood that 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 disclosed subject matter without deviating therefrom. Therefore, the disclosed 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.