Capacity dashboard for network management systems

[0001] A high-level overview of various aspects of the invention is provided here for that reason, to provide an overview of the disclosure and to introduce a selection of concepts that are further described in the detailed-description section below. This summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used as an aid in isolation to determine the scope of the claimed subject matter. The present disclosure is directed, in part, to technology associated with a capacity dashboard for a multi-network management system, substantially as shown in and/or described in connection with at least one of the figures, and as set forth more completely in the claims.

[0002] In aspects set forth herein, and at a high level, the technology described herein relates to capacity dashboards for a multi-network management system that is in communication with a plurality of network managers that are each in communication with one or more radio access network (RAN) nodes. In some embodiments, the multi-network management system is in communication with over forty network managers. The multi-network management system can be configured to perform operations comprising receiving at least one key performance indicator (KPI) for each of the plurality of RAN nodes and identifying a network manager of the plurality of network managers for each of the plurality of RAN nodes. The multi-network management system can also determine a capacity for each of the plurality of network managers based on the at least one KPI received for each of the plurality of RAN nodes and based on identifying the network manager for each of the plurality of RAN nodes.

[0003] In some embodiments, a capacity for a network manager can also be determined based on identifying RAN node capabilities and operating configurations for each of the plurality of RAN nodes for each of the plurality of network managers. In some embodiments, the multi-network management system can determine a first capacity for a first network manager of the plurality of network managers is above a threshold. In embodiments, the multi-network management system can determine that the first capacity is increasing at a rate above a predetermined threshold rate. In some embodiments, the multi-network management system can determine a second capacity for a second network manager of the plurality of network managers is within a predetermined range that is approaching the threshold. In embodiments, the threshold can be determined based on historical KPIs of each of the plurality of network managers, RAN node capabilities, RAN node operating configurations for each of the plurality of RAN nodes that correspond to each network manager of the plurality of network managers, another threshold indicator, or one or more combinations thereof.

[0004] As such, the multi-network management system can display (or cause the display of) a dashboard, via a user interface, the dashboard comprising a capacity icon for the capacity determined for one or more of the plurality of network managers. Each capacity icon displayed on the dashboard can be organized on the dashboard based on at least one identifier for each of the plurality of network managers (e.g., a network manager location identifier, a RAN node identifier for each of the RAN nodes in communication with a network manager, another type of network manager identifier). In some embodiments, the capacity icon for each of the plurality of network managers is displayed on the dashboard in an ascending order from a highest capacity utilization to a lowest capacity utilization. In some embodiments, the capacity icon for the highest capacity utilization is visually different from the capacity icon for the lowest capacity utilization. In some embodiments, an alert is provided for the first capacity on the dashboard based on determining the first capacity for the first network manager is above the threshold.

[0005] This summary is provided to introduce a selection of concepts in a simplified form that are further described below in the detailed description. This summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used in isolation as an aid in determining the scope of the claimed subject matter.

[0011] The subject matter of embodiments of the invention is described with specificity herein to meet statutory requirements. However, the description itself is not intended to limit the scope of this patent. Rather, the inventors have contemplated that the claimed subject matter might be embodied in other ways, to include different steps or combinations of steps similar to the ones described in this document, in conjunction with other present or future technologies. Moreover, although the terms “step” and/or “block” may be used herein to connote different elements of methods employed, the terms should not be interpreted as implying any particular order among or between various steps herein disclosed unless and except when the order of individual steps is explicitly described.

[0012] Throughout this disclosure, several acronyms and shorthand notations are employed to aid the understanding of certain concepts pertaining to the associated system and services. These acronyms and shorthand notations are intended to help provide an easy methodology of communicating the ideas expressed herein and are not meant to limit the scope of embodiments described in the present disclosure. The following is a list of these acronyms:

• • [0013] 3G Third-Generation Cellular Communication System
  • [0014] 4G Fourth-Generation Cellular Communication System
  • [0015] 5G Fifth-Generation Cellular Communication System
  • [0016] CD-ROM Compact Disk Read Only Memory
  • [0017] CDMA Code Division Multiple Access
  • [0018] CQI Channel Quality Information
  • [0019] CS Circuit Switch
  • [0020] CSF Channel State Feedback
  • [0021] CSI Channel State Information
  • [0022] D2D Device-to-Device
  • [0023] eNB Evolved Node B
  • [0024] gNB Next Generation Node B
  • [0025] GPRS General Packet Radio Service
  • [0026] GSM Global System for Mobile communications
  • [0027] DVD Digital Versatile Discs
  • [0028] EEPROM Electrically Erasable Programmable Read Only Memory
  • [0029] eMBB enhanced Mobile Broadband
  • [0030] EMS Enhanced Messaging Service
  • [0031] E-RAB E-UTRAN Radio Access Bearer
  • [0032] E-UTRAN Evolved Universal Terrestrial Radio Access Network
  • [0033] FD-MIMO Full-Dimension Multiple-Input Multiple-Output
  • [0034] GPS Global Positioning System
  • [0035] GSM Global Standards for Mobile communications
  • [0036] IoT Internet of Things
  • [0037] KPI Key Performance Indicator
  • [0038] LAN Local Area Network
  • [0039] LTE Long Term Evolution
  • [0040] MCS Modulation Coding Scheme
  • [0041] MIMO Multiple-Input Multiple-Output
  • [0042] mm wave Millimeter wave
  • [0043] MME Mobility Management Entity
  • [0044] MMS Multimedia Messaging Service
  • [0045] mMTC massive Machine Type Communications
  • [0046] MU-MIMO Multi-User Multiple-Input Multiple-Output
  • [0047] NR New Radio
  • [0048] P2P Peer-to-Peer
  • [0049] PC Personal Computer
  • [0050] PDA Personal Digital Assistant
  • [0051] PDP Packet Data Protocol
  • [0052] QOS Quality of Service
  • [0053] RAM Random Access Memory
  • [0054] RAN Radio Access Network
  • [0055] RAT Radio Access Technology
  • [0056] RBS Radio Base Station
  • [0057] RF Radio-Frequency
  • [0058] ROM Read Only Memory
  • [0059] RRC Radio Resource Control
  • [0060] RSRP Reference Signal Received Power
  • [0061] RSRQ Reference Transmission Receive Quality
  • [0062] RSSI Received Signal Strength Indicator
  • [0063] SDCCH Stand-alone Dedicated Control Channel
  • [0064] SINR Signal to Interference and Noise Ratio
  • [0065] SMS Short Message Service
  • [0066] SNR Signal-to-Noise Ratio
  • [0067] SRS Sound Reference Signal
  • [0068] TCH Traffic Channel
  • [0069] TDMA Time Division Multiple Access
  • [0070] UE User Equipment
  • [0071] UMTS Universal Mobile Telecommunications System
  • [0072] URLLC Ultra-Reliable Low Latency Communications
  • [0073] VLAN Virtual Local Area Network

[0074] In addition, words such as “a” and “an,” unless otherwise indicated to the contrary, may also include the plural as well as the singular. Thus, for example, the constraint of “a feature” is satisfied where one or more features are present. Furthermore, the term “or” includes the conjunctive, the disjunctive, and both (a or b thus includes either a or b, as well as a and b).

[0075] Unless specifically stated otherwise, descriptors such as “first,” “second,” and “third,” for example, are used herein without imputing or otherwise indicating any meaning of priority, physical order, arrangement in a list, or ordering in any way, but are merely used as labels to distinguish elements for ease of understanding the disclosed examples. In some examples, the descriptor “first” may be used to refer to an element in the detailed description, while the same element may be referred to in a claim with a different descriptor such as “second” or “third.” In such instances, it should be understood that such descriptors are used merely for identifying those elements distinctly that might, for example, otherwise share a same name.

[0076] Further, the term “some” may refer to “one or more.” Additionally, an element in the singular may refer to “one or more.”

[0077] The term “combination” (e.g., one or more combinations thereof) may refer to, for example, “at least one of A, B, or C”; “at least one of A, B, and C”; “at least two of A, B, or C” (e.g., AA, AB, AC, BB, BA, BC, CC, CA, CB); “each of A, B, and C”; and may include multiples of A, multiples of B, or multiples of C (e.g., CCABB, ACBB, ABB, etc.). Other combinations may include more or less than three options associated with the A, B, and C examples.

[0078] As used herein, the phrase “based on” shall be construed as a reference to an open set of conditions. For example, an example step that is described as “based on X” may be based on both X and additional conditions, without departing from the scope of the present disclosure. In other words, as used herein, the phrase “based on” shall be construed in the same manner as the phrase “based at least in part on.”

[0079] The term “mm wave,” as used herein, may refer to the extremely high frequency band (e.g., from 30 GHz to 300 GHz). Additionally or alternatively, in some embodiments, a mm wave transmission includes one or more frequency ranges of 24 GHZ, 26 GHZ, 28 GHZ, 39 GHZ, and 52.6-71 GHz.

[0080] Additionally, a “user device,” as used herein, is a device that has the capability of using a wireless communications network, and may also be referred to as a “computing device,” “mobile device,” “user equipment,” “wireless communication device,” or “UE.” A user device, in some aspects, may take on a variety of forms, such as a PC, a laptop computer, a tablet, a mobile phone, a PDA, a server, or any other device that is capable of communicating with other devices (e.g., by transmitting or receiving a signal) using a wireless communication. A user device may be, in some embodiments, similar to user devices 102A-102D described herein with respect to FIG. 1 or similar to user device 1200 described herein with respect to FIG. 12.

[0081] In embodiments, a user device may include internet-of-things devices, such as one or more of the following: a sensor, controller (e.g., a lighting controller, a thermostat), appliances (e.g., a smart refrigerator, a smart air conditioner, a smart alarm system), other internet-of-things devices, or one or more combinations thereof. Internet-of-things devices may be stationary, mobile, or both. In some aspects, the user device is associated with a vehicle (e.g., a video system in a car capable of receiving media content stored by a media device in a house when coupled to the media device via a local area network). In some aspects, the user device comprises a medical device, a location monitor, a clock, other wireless communication devices, or one or more combinations thereof. In some aspects, the user device is a wearable device having a camera, microphone, RFID, GPS, another sensor, or one or more combinations thereof, to capture data in real-time or near real-time (e.g., one or more strings of text, image data, video data, audio data, location data, other types of data, or one or more combinations thereof).

[0082] The wearable devices and other user devices, for example, can transmit the data obtained by their corresponding sensors to other user devices. For example, the sensor data obtained by a user device can be further transmitted for another user device to perform positional tracking (e.g., six degrees of freedom positional tracking) associated with the user device capturing the sensor data in real-time. In embodiments, a user device can access sensors, application data, tracking data, map data, other user device data, or one or more combinations thereof, for packet transmissions to a user device. In some embodiments, a wearable device can be a watch-type electronic device, a glasses-type wearable device, an upper-torso wearable device (e.g., a shirt having sensors affixed on or within the material of the shirt or a device that is attachable to the shirt), another type of wearable device, or one or more combinations thereof.

[0083] In aspects, a user device discussed herein may be configured to communicate using one or more of 4G (e.g., LTE), 5G, 6G, another generation communication system, or one or more combinations thereof. In some aspects, the user device has components to establish a 5G connection with a 5G gNB, and to be served according to 5G over that connection. In some aspects, the user device may be an E-UTRAN New Radio-Dual Connectivity (ENDC) device. ENDC allows a user device to connect to an LTE eNB that acts as a master node and a 5G gNB that acts as a secondary node. As such, in these aspects, the ENDC device may access both LTE and 5G simultaneously, and in some cases, on the same spectrum band.

[0084] “Telecommunication service” refers to the transfer of information (e.g., without the use of an electrical conductor as the transferring medium). Telecommunication services may be provided by one or more telecommunication network providers. Telecommunication services may include, but are not limited to, the transfer of information via radio waves (e.g., Bluetooth®), satellite communication, infrared communication, microwave communication, Wi-Fi, mm wave communication, and mobile communication. Embodiments of the present technology may be used with different telecommunication technologies or standards, including, but not limited to, CDMA 1xAdvanced, GPRS, Ev-DO, TDMA, GSM, WiMAX technology, LTE, LTE Advanced, other technologies and standards, or one or more combinations thereof.

[0085] A “network” providing the telecommunication services (e.g., network 108 of FIG. 1) may be one or more telecommunications networks, or a portion thereof. The telecommunications network might include an array of devices or components (e.g., one or more base stations). The network can include multiple networks, and the network can be a network of networks. In embodiments, the network or a portion thereof is a core network, such as an evolved packet core, which may include at least one MME, at least one serving gateway, and at least one Packet Data Network gateway. The MME may manage non-access stratum (e.g., control plane) functions such as mobility, authentication, and bearer management for other devices associated with the evolved packet core.

[0086] In some aspects, a network can connect one or more user devices to a corresponding immediate service provider for services such as 5G and LTE, for example. In aspects, the network provides telecommunication services comprising one or more of a voice service, a message service (e.g., SMS messages, MMS messages, instant messaging messages, an EMS service messages), a data service, other types of telecommunication services, or one or more combinations thereof, to user devices or corresponding users that are registered or subscribed to a telecommunication service provider to utilize the one or more services. The network can comprise any communication network providing voice, message, or data service(s), such as, for example, a 1x circuit voice, a 3G network (e.g., CDMA, CDMA2000, WCDMA, GSM, UMTS), a 4G network (WiMAX, LTE, HSDPA), a 5G network, a 6G network, another generation network, or one or more combinations thereof.

[0087] Components of the telecommunications network, such as terminals, links, and nodes (as well as other components), can provide connectivity in various implementations. For example, components of the network may include core network nodes, relay devices, integrated access and backhaul nodes, macro eNBs, small cell eNBs, gNBs, relay base stations, other network components, or one or more combinations thereof. The network may interface with one or more base stations through one or more wired or wireless backhauls. As such, the one or more base stations may communicate to devices via the network or directly. Furthermore, user devices can utilize the network to communicate with other devices (e.g., a user device(s), a server(s), etc.) through the one or more base stations.

[0088] As used herein, the term “base station” (used for providing UEs with access to the telecommunication services) generally refers to one or more base stations, nodes, RRUs control components, and the like (configured to provide a wireless interface between a wired network and a wirelessly connected user device). A base station may comprise one or more RAN nodes (e.g., eNB, gNB, and the like) that are configured to communicate with user devices. In some aspects, the base station may include one or more band pass filters, radios, antenna arrays, power amplifiers, transmitters/receivers, digital signal processors, control electronics, GPS equipment, and the like. In some embodiments, a RAN node is a base station. A base station may be, in some embodiments, similar to base stations 114A-114F described herein with respect to FIG. 1.

[0089] In embodiments, the “RAN node” may refer to a base transceiver station, a radio base station, an access point, a radio transceiver, a NodeB, an eNB, a gNB, a Home NodeB, a Home eNodeB, another type base station, or one or more combinations thereof. The RAN node may comprise one or more of a macro base station, a small cell or femtocell base station, a relay base station, another type of base station, or one or more combinations thereof. In aspects, the RAN node may be configured as FD-MIMO, massive MIMO, MU-MIMO, cooperative MIMO, 3G, 4G, 5G, another generation communication system, or one or more combinations thereof. In addition, the RAN node may operate in an extremely high frequency region of the spectrum (e.g., from 30 GHz to 300 GHz), also known as the millimeter band.

[0090] In embodiments, RAN node capabilities and RAN node operating configurations for a RAN node may correspond to the FD-MIMO, massive MIMO, MU-MIMO, cooperative MIMO, 3G, 4G, 5G, another generation communication system, or one or more combinations thereof. Additionally or alternatively, RAN node capabilities and RAN node operating configurations may correspond to operations in the extremely high frequency region of the spectrum (e.g., from 30 GHz to 300 GHz), also known as the millimeter band.

[0091] Embodiments of the technology described herein may be embodied as, among other things, a method, system, or computer-program product. Accordingly, the embodiments may take the form of a hardware embodiment, or an embodiment combining software and hardware. An embodiment that takes the form of a computer-program product can include computer-useable instructions embodied on one or more computer-readable media.

[0092] Computer-readable media include both volatile and nonvolatile media, removable and non-removable media, and contemplate media readable by a database, a switch, and various other network devices. Network switches, routers, and related components are conventional in nature, as are means of communicating with the same. By way of example, and not limitation, computer-readable media comprise computer-storage media and communications media.

[0093] Computer-storage media, or machine-readable media, include media implemented in any method or technology for storing information. Examples of stored information include computer-useable instructions, data structures, program modules, and other data representations. Computer-storage media include, but are not limited to RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile discs (DVD), holographic media or other optical disc storage, magnetic cassettes, magnetic tape, magnetic disk storage, and other magnetic storage devices. These memory components can store data momentarily, temporarily, or permanently.

[0094] Communications media typically store computer-useable instructions—including data structures and program modules—in a modulated data signal (e.g., a modulated data signal referring to a propagated signal that has one or more of its characteristics set or changed to encode information in the signal). Communications media include any information-delivery media. By way of example but not limitation, communications media include wired media, such as a wired network or direct-wired connection, and wireless media such as acoustic, infrared, radio, microwave, spread-spectrum, and other wireless media technologies. Combinations of the above are included within the scope of computer-readable media.

[0095] By way of background, prior relevant technologies have had drawbacks associated with managing telecommunication services provided by base station nodes. For example, prior relevant technologies have not provided a multi-network management system capable of communicating with a plurality of network operation systems and base station nodes corresponding to the network operation systems. As another example, these prior relevant technologies have not provided recommendations, alerts, or notifications for particular operations of particular network operations systems and particular base station nodes based on receiving particular network performance data, such as an indication to modify an operation associated with a rate at which the network operation system receives the network performance data. As such, these prior relevant technologies have had challenges that involve base station node degradation that has been undetected or that has not been remedied. Accordingly, these prior relevant technologies can involve signal fading, decreased throughput, and decreases in quality of service and user device experiences.

[0096] The technology provided herein can alleviate the problems discussed above. For example, the technology disclosed herein enhances network resource utilization, decreases signal fading, increases uplink and downlink throughput, and improves communications between or among user devices by improving quality of service and user device experience. Further, the technology and corresponding techniques can enhance the reliability and functionality of communications. In an embodiment, a method is provided for a capacity management dashboard. The method comprises receiving, via a multi-network management system in communication with a plurality of network managers, at least one KPI for each RAN node of each of the plurality of network managers, wherein each of the plurality of network managers are managing a plurality of RAN nodes. The method also comprises identifying, via the multi-network management system, RAN node capabilities and operating configurations for each of the plurality of RAN nodes for each of the plurality of network managers. The method also comprises determining, via the multi-network management system, a capacity for each of the plurality of network managers based on the at least one KPI received and based on identifying the RAN node capabilities and the operating configurations. The method also comprises displaying, via a user interface, a dashboard comprising a capacity icon for the capacity determined for each of the plurality of network managers, wherein the capacity icon for each of the plurality of network managers is displayed on the dashboard based on an identifier for each of the plurality of network managers.

[0097] In another embodiment, a system is provided for a capacity management dashboard. The system comprises a plurality of radio access network (RAN) nodes. The system also comprises a plurality of network managers that are each in communication with one or more of the plurality of RAN nodes. The system also comprises a multi-network management system capable of communicating with the plurality of network managers for capacity management of the plurality of RAN nodes based on key performance indicators (KPIs), the multi-network management system configured to perform operations. Those operations include receiving at least one KPI for each of the plurality of RAN nodes. The operations also include identifying a network manager of the plurality of network managers for each of the plurality of RAN nodes. The operations also include determining a capacity for each of the plurality of network managers based on the at least one KPI received for each of the plurality of RAN nodes and based on identifying the network manager for each of the plurality of RAN nodes. The operations also include displaying, via a user interface, a dashboard comprising a capacity icon for the capacity determined for each of the plurality of network managers, wherein the capacity icon for each of the plurality of network managers is displayed on the dashboard based on at least one identifier for each of the plurality of network managers.

[0098] In yet another embodiment, computer storage media is provided for capacity management. For example, one or more non-transitory computer storage media having computer-executable instructions embodied thereon, that when executed by at least one processor, cause the at least one processor to perform a method. The method includes receiving, via a multi-network management system in communication with a plurality of network managers, at least one KPI for each RAN node of each of the plurality of network managers, wherein each of the plurality of network managers are managing a plurality of RAN nodes, and wherein the at least one KPI for each RAN node is received in real-time. The method also includes identifying, via the multi-network management system, each network manager of the plurality of network managers. The method also includes storing the at least one KPI received in real-time for each of the identified network managers. The method also includes determining, via the multi-network management system, a capacity for each of the plurality of network managers based on the at least one KPI received and based on identifying each network manager. The method also includes causing to display, on a user interface, a dashboard comprising a capacity icon for the capacity determined for each of the plurality of network managers, wherein the capacity icon for each of the plurality of network managers is displayed on the dashboard based on an identifier for each of the plurality of network managers.

[0099] Those skilled in the art will appreciate that the computing devices described herein need not be limited to conventional personal computers, and can include other computing configurations, including servers, hand-held devices, multi-processor systems, a microprocessor based or programmable consumer electronics, network PCs, minicomputers, mainframe computers, other computing devices, or one or more combinations thereof. Similarly, the computing devices need not be limited to stand-alone computing devices, as the mechanisms may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a wireless telecommunications network. In a distributed computing environment, program modules may be located in both local and remote memory storage devices.

[0100] Turning now to FIG. 1, example operating environment 100 supports the multi-network management system within one or more telecommunications networks, in accordance with one or more embodiments disclosed herein. Example environment 100 is but one example of a suitable environment for the multi-network management system and the associated techniques disclosed herein, and is not intended to suggest any limitation as to the scope of use or functionality of the invention. Neither should the environment 100 be interpreted as having any dependency or requirement relating to any one or combination of components illustrated. For example, in some embodiments, the example operating environment 100 can include additional components not depicted.

[0101] Example operating environment 100 includes user devices 102A-102D, network 108, coverage areas 110A-110E, base stations 114A-114F, network managers 116A-116C, satellites 120A and 120B, communication link 124 corresponding to satellite 120B and base station 114A, communication link 122 corresponding to satellite 120A and base station 114B, communication link 126 between satellites 120A and 120B, and multi-network management system 130. Example operational environment 100 is but one example environment for the multi-network management system 130. For example, another embodiment may include additional base stations.

[0102] Example operating environment 100 having network 108 and coverage area 110A may be associated with one or more of a non-terrestrial network, an LTE network, an LTE-A network, an LTE-A Pro network, an NR network, a mm wave network, another type of network, or one or more combinations thereof. In some embodiments, the example operating environment 100 may support enhanced broadband communications, ultra-reliable (e.g., mission critical) communications, low latency communications, communications with low-cost and low-complexity devices, another type of communication, or one or more combinations thereof. In some embodiments, one or more communications between one or more devices in example operating environment 100 may correspond to the enhanced broadband communication, ultra-reliable communication, low latency communication, another type of communication, or one or more combinations thereof.

[0103] In embodiments, example environment 100 can utilize both licensed and unlicensed radio frequency bands. For example, the example environment 100 may employ License Assisted Access, LTE-Unlicensed radio access technology, or NR technology in an unlicensed band (e.g., 5 GHz industrial, scientific, and medical band). When operating in unlicensed radio frequency bands, base stations, satellites, or user devices may employ carrier sensing for collision avoidance and detection. In some examples, operations in unlicensed bands may be based on a carrier aggregation configuration and component carriers operating in a licensed band. Operations in unlicensed spectrum may include downlink transmissions, uplink transmissions, P2P transmissions, D2D transmissions, another type of unlicensed spectrum operation, or one or more combinations thereof. As such, one or more communications corresponding to the multi-network management system 130 may correspond to a licensed or unlicensed radio frequency band, a 5 GHz industrial band, a 5 GHz scientific band, a 5 GHz medical band, a particular carrier aggregation configuration of a licensed band, a P2P transmission, a D2D transmission, another type of spectrum operation, or one or more combinations thereof.

[0104] In embodiments, user devices 102A-102D may wirelessly communicate via one or more wireless telecommunication services provided by one or more base stations (e.g., user device 102B may wireless communicate via a wireless telecommunication service provided by base station 114E or 114F), one or more satellites (e.g., user device 102A may wireless communicate via a wireless telecommunication service provided by satellite 120A, 120B another satellite, or one or more combinations thereof), other types of wireless telecommunication devices, or one or more combinations thereof. In example environment 100, network 108, base stations 114A-114F, and satellites 120A-120B can provide coverage area 110A for supporting communication signals according to one or more radio access technologies. Supported communication signals within coverage area 110A can include MU-MIMO and SU-MIMO transmissions, for example. As such, one or more communications corresponding to the multi-network management system 130 may correspond to the wireless telecommunication services provided within coverage area 110A.

[0105] In embodiments, the user devices 102A-102D can be stationary, mobile, or one or more combinations thereof at different times. The user devices 102A-102D may be able to communicate with various types of devices, such as other UEs, various types of base stations, or various types of network components (e.g., one or more RAN nodes including one or more core network nodes, relay devices, integrated access and backhaul nodes, other types of RAN nodes, or one or more combinations thereof). In embodiments, one or more of the user devices 102A-102D may have different capabilities. For instance, a user device can be wearable devices having a camera, microphone, RFID, GPS, another sensor, or one or more combinations thereof. In some embodiments, a user device is a wearable device can be a watch-type electronic wearable device, a glasses-type wearable device, an upper-torso wearable device (e.g., a shirt having sensors affixed on or within the material of the shirt or a device that is attachable to the shirt), another type of wearable device, or one or more combinations thereof.

[0106] In embodiments, one or more of the user devices 102A-102D may include one or more of a unit, a station, a terminal, or a client, for example. The user devices 102A-102D may also include a wireless local loop station, an IoT device, an Internet of Everything device, a machine type communication device, an evolved or enhanced machine type communication device, another type of user device, or one or more combinations thereof. The machine type communication device or the evolved or enhanced machine type communication device may include, for example, one or more robots, drones, remote devices, sensors, meters, monitors, location tags, etc., that may communicate with a base station, another device (e.g., remote device), or some other entity. In some embodiments, a user device may be implemented in various objects such as appliances, vehicles, meters, or other objects. In some embodiments, one or more of the user devices 102A-102D may, at one time or another, act as a relay, base station, (e.g., a UAV acting as an aerial base station), or the network equipment (e.g., macro eNBs or gNBs, small cell eNBs or gNBs, or relay base stations). As such, in some embodiments, one or more signals transmitted from the unit, station, terminal, client, wireless local loop station, IoT device, Internet of Everything device, machine type communication device, evolved or enhanced machine type communication device, user device implemented in an object, another type of user device, or one or more combinations thereof, can be received by the multi-network management system 130 (e.g., through network managers 116A-116C).

[0107] Coverage area 110A can provide services from network 108, such as network provider services including the Internet, Intranet, Internet Protocol Multimedia Subsystem, Packet-Switched Streaming Service, another type of network provider service, or one or more combinations thereof. In embodiments, one or more of the user devices 102A-102D, base stations 114A-114F, satellites 120A-120B, multi-network management system 130, or one or more combinations thereof, can be configured to support ultra-reliable communications, low-latency communications, mission critical communications, ultra-reliable low-latency communications, ultra-reliable functions, low-latency functions, critical functions, mission critical push-to-talk functions, mission critical video functions, other types of communications, or one or more combinations thereof, associated with the multi-network management system 130. In embodiments, one or more RAN node capabilities and RAN node operating configurations (e.g., a RAN node corresponding to one or more of base stations 114A-114F or one or more of satellites 120A-120B) are associated with one or more of ultra-reliable communications, low-latency communications, mission critical communications, ultra-reliable low-latency communications, ultra-reliable functions, low-latency functions, critical functions, mission critical push-to-talk functions, mission critical video functions, other types of communications, or one or more combinations thereof. In some embodiments, one or more RAN node capabilities and RAN node operating configurations correspond to a network provider service (e.g., Internet, Intranet, Internet Protocol Multimedia Subsystem, Packet-Switched Streaming Service).

[0108] In embodiments, one or more of the multi-network management system 130, base stations 114A-114F, satellites 120A-120B, or one or more combinations thereof, can communicate with the telecommunications network 108 via a core network, one or more network components (e.g., a core network node, a relay device, an MME, an integrated access and backhaul node, a macro eNB, a small cell eNB, a gNB, a relay base station), or one or more combinations thereof. In some embodiments, one or more of base stations 114A-114F, satellite 120A, satellite 120B, or one or more combinations thereof, communicate with the telecommunications network 108 over one or more backhaul links (e.g., via an X2, Xn, or other interface) either directly (e.g., directly between base stations), or indirectly (e.g., via core network), or one or more combinations thereof. The backhaul links may be or include one or more wireless links, for example.

[0109] In embodiments, RAN nodes including base stations 114A-114F may operate using MIMO transmissions. For example, one or more of the RAN nodes including base stations 114A-114F can be configured as FD-MIMO, massive MIMO, MU-MIMO, cooperative MIMO, 4G, 5G, another generation communication system, or one or more combinations thereof, for providing telecommunication services to one or more of user devices 102A-102D. In embodiments, RAN node capabilities and RAN node operating configurations of a RAN node correspond to one or more FD-MIMO transmissions, massive MIMO transmissions, MU-MIMO transmissions, cooperative MIMO transmissions, 4G transmissions, 5G transmissions, another generation communication system transmission, or one or more combinations thereof.

[0110] In embodiments, one or more of the RAN nodes including base stations 114A-114F can perform one or more of the following functions: transfer user data, radio channel ciphering and deciphering, integrity protection, header compression, mobility control functions (e.g., handover, dual connectivity), inter-cell interference coordination, connection setup and release, load balancing, distribution for a non-access stratum message or node selection, a synchronization, radio access network sharing, multimedia broadcast multicast service, subscriber and equipment trace, radio access network information management, paging, positioning, delivery of warning messages, other functions, or one or more combinations thereof. In embodiments, RAN node capabilities and RAN node operating configurations of a RAN node correspond to one or more of these functions.

[0111] In some embodiments, one or more RAN node antennas (or antenna arrays) having antenna elements may be co-located at an antenna assembly, such as an antenna tower. In some examples, antennas or antenna arrays associated with the RAN nodes including base stations 114A-114F can be located in diverse geographic locations. In embodiments, antenna elements of one or more antennas may each be within a threshold distance from at least one of the other antenna elements. In some aspects, one or more nodes corresponding to base station 114 may comprise one or more macro cells, one or more small cells, one or more relay base stations, one or more repeaters, one or more femtocells, other types of cells, or one or more combinations thereof. In other embodiments, one or more of the RAN nodes including base stations 114A-114F can be movable, thereby providing communication coverage for a moving geographic coverage area (e.g., coverage area 110D). In some embodiments, one or more antennas of RAN nodes including base stations 114A-114F can use MIMO antenna technology, including spatial multiplexing, beamforming, transmit diversity, other MIMO functions, or one or more combinations thereof.

[0112] In embodiments, one of more RAN nodes can include one or more of the satellites 120A-120B, which may communicate with other types of RAN nodes (e.g., the base stations 114A-114F, user devices 102A-102D, or other high altitude or terrestrial RAN nodes). “Satellite” may also be referred to as a space vehicle or communication satellite. Satellites 120A-120B may be any suitable type of communication satellite configured to relay communications between different RAN nodes or RAN end nodes in a wireless communication system. Satellites 120A-120B may be or include a space satellite, a balloon, a dirigible, an airplane, a drone, an unmanned aerial vehicle, another type of satellite, or one or more combinations thereof. In some examples, the satellites 120A-120B may be in a geosynchronous or geostationary earth orbit, a low earth orbit, a medium earth orbit, another type of orbit, or one or more combinations thereof. In some embodiments, satellites 120A-120B may be a multi-beam satellite configured to provide service for multiple service beam coverage areas in a predefined geographical service area (e.g., coverage area 110). The satellites 120A-120B may be any distance away from the surface of the earth. In one non-limiting example, a RAN node may correspond to a geosynchronous earth orbiting satellite with a RAN node capability or a RAN node operating configuration corresponding to multiple service beam coverage areas in a predefined geographical service area.

[0113] In some embodiments, the multi-network management system 130 can receive network performance data (e.g., a KPI) from one or more of the satellites 120A and 120B based on the connection between the multi-network management system 130 and one or more of network managers 116A, 116B, and 116C. The multi-network management system 130 may interface with one or more of network managers 116A, 116B, and 116C through one or more wired or wireless backhauls (e.g., via an X2, Xn, or other interface) either directly (e.g., directly between the multi-network management system 130 and network manager 116B), or indirectly (e.g., via core network), or one or more combinations thereof. In some embodiments, the multi-network management system 130 can receive the network performance data (e.g., KPIs) associated with one or more of satellites 120A and 120B (e.g., the space satellite, balloon, dirigible, airplane, drone, unmanned aerial vehicle, multi-beam satellite, other type of satellite, or one or more combinations thereof). For example, the network performance data corresponding to satellite 120A or 120B may include packet metrics including queue length, round trip time between satellite 120A and satellite 120B, round trip time between satellite 120A and base station 114B, round trip time between satellite 120B and base station 114A, round trip time between satellite 120A and user device 102C, round trip time between satellite 120A or satellite 120B and network manager 116A, retry ration, path loss, other types of network performance data, or one or more combinations thereof.

[0114] In some embodiments, satellites 120A-120B may be deployed at an altitude of 18 km to 25 km (e.g., a geostationary balloon satellite), wherein the stratosphere has low wind speeds (e.g., 5 m/s to 40 m/s) and low turbulence. In embodiments, satellites 120A and 120B may be configured to communicate with each other (e.g., via communication link 126). As such, the communication link 126 may include a free space optical link, a microwave link, electromagnetic wave signals via mm wave signals, optical signals via a laser, another type of communication link, or one or more combinations thereof. In embodiments, satellites 120A-120B may be configured to communicate via a wireless common public radio interface protocol, a dedicated wireless front haul protocol developed for high-altitude-to-high-altitude, another protocol, or one or more combinations thereof. As such, in some embodiments, the network performance data (e.g., KPIs) corresponding to satellite 120A or 120B and received by multi-network management system 130 may correspond to a measurement of the free space optical link, microwave link, electromagnetic wave signals via mm wave signals, optical signals via laser, wireless common public radio interface protocol, a dedicated wireless front haul protocol developed for high-altitude-to-high-altitude, the other type of communication link, or one or more combinations thereof.

[0115] In some embodiments, one or more portions of coverage area 110A (e.g., encompassing coverage areas 110B-110E) may be provided or established by satellites 120A-120B as part of a non-terrestrial network. Satellites 120A-120B may, in some cases, perform the functions of a base station or may act as a bent-pipe satellite, act as a regenerative satellite, act as another type of satellite, or one or more combinations thereof. In other cases, satellites 120A-120B may be a smart satellite, or a satellite with intelligence. For example, a smart satellite may be configured to perform more functions than a regenerative satellite (e.g., may be configured to perform particular algorithms beyond those used in regenerative satellites or to be reprogrammed, for example). A bent-pipe transponder or satellite may be configured to receive signals from ground base stations (e.g., base station 114) and transmit those signals to different ground base stations. In some embodiments, a bent-pipe transponder or satellite may amplify signals or shift from uplink frequencies to downlink frequencies. A regenerative transponder or satellite may be configured to relay signals like the bent-pipe transponder or satellite, but may also use on-board processing to perform other functions. Examples of these other functions may include demodulating a received signal, decoding a received signal, re-encoding a signal to be transmitted, or modulating the signal to be transmitted, another type of satellite or regenerative transponder function, or one or more combinations thereof. For example, a bent-pipe satellite may receive a signal from a base station and may relay the signal to a user device or base station, or vice-versa. As such, in some embodiments, the multi-network management system 130 can receive the network performance data associated with one or more of these types of satellites (e.g., bent-pipe satellite, regenerative satellite, smart satellite, other type of satellite, or one or more combinations thereof). In some embodiments, the network performance data (e.g., a KPI) corresponds to the demodulated signal, decoded signal, re-encoded signal, modulated signal, another type of satellite or regenerative transponder function, or one or more combinations thereof.

[0116] Multi-network management system 130 can be configured to communicate with network managers 116A-116C, as well as other network managers or other network components across a plurality of various geographical regions and coverage areas. In some embodiments, the multi-network management system 130 can be located in a core network corresponding to network 108. The multi-network management system 130 can analyze network performance data (e.g., KPIs), determine network performance data outliers, determine a capacity for each of the plurality of network managers based on the network performance data received for each of the plurality of RAN nodes, provide a dashboard, via a graphical user interface, comprising a capacity icon for the capacity determined for each of the network managers, make other types of determinations, provide end-to-end optimization for RAN nodes within a plurality of coverage areas, transmit RAN node operation instructions, transmit alerts, notifications, and recommendations associated with particular RAN nodes within a plurality of coverage areas, provide other operations, or one or more combinations thereof.

[0117] In some embodiments, the multi-network management system 130 receives KPIs from each of a plurality of radio access networks that each have a plurality of RAN nodes. In some embodiments, the KPIs received include one or more KPI types. The five tables provided below include several non-exhaustive example KPI types:

[0118]

TABLE 1
KPIs for the GSM network
	Key
	performance
KPI	indicators		Measurement
category	(KPIs)	Definition	approach	Considerations
Availability	Radio	Mobile coverage can	Theoretical	This parameter can
	coverage-	represents the strength or	calculation or	measure the
	RxLev	power level of signal or	Drive test	geographic reach of
		reception in a given area in		a mobile GSM
		which a user device can		network.
		have access to both data
		and voice services (e.g.,
		radio coverage
		measurements [ITU-T
		E.806]).
Accessibility	Stand-alone	The proportion of user	Real traffic	Secondary
	dedicated	devices which successfully		This KPI can indicate
	control	access resources, having		accessibility for
	channel	requested an appropriate		several procedures like
	(SDCCH)	service on accessing the		call setup, SMS
	assignment	SDCCH (e.g., clause 5.6 of		delivery and location
	success rate	[b-ETSI TR 32.814]).		update and can also be
				used to troubleshoot
				circuit switch (CS)
				access issues.
	Stand-alone	The proportion of all	Real traffic	Secondary
	dedicated	SDCCH resource requests		This KPI can indicate
	control	and failed due to no		accessibility for
	channel	SDCCH resource available		several procedures in
	(SDCCH)	(e.g., clause 5.7 of		circuit service. It can
	congestion	[b-ETSI TR 32.814]).		show the status of the
				SDCCH resource
				utilization. It can also
				show resource
				dimensions. When
				SDCCH is highly
				congested, TCH
				utilization can
				degrade.
	Traffic	The proportion of all	Real traffic	Primary
	channel	requests for TCH resources		TCH congestion often
	(TCH)	(call origination and		increases when traffic
	congestion	incoming handover) and		demand increases.
		fail due non available TCH
		resources (e.g., clause 5.8
		of
		[b-ETSI TR 32.814]).
	Call setup	Measures the proportion of	Real traffic or	Primary
	success rate	user devices which	test traffic	The preceding KPIs on
		successfully access a TCH		SDCCH and TCH are
		(e.g., clause 5.5 of		sub KPIs of Call Setup
		[b-ETSI TR 32.814]).		Success Rate.
				Any of the
				TCH/SDCCH KPIs
				listed above can
				impact the call setup
				success rate. Call setup
				success rate gives an
				overview of a call,
				from initiation to
				setup.
	Packet data	Describes the ratio of all	Real traffic or	Secondary
	protocol	successful PDP context	test traffic	Before data is
	(PDP) context	activation to PDP context		transferred to and from
	activation	activation attempts (e.g.,		a base station, a PDP
	success rate	clause 7.5 of		context can be
		[ETSI TS 132 410]).		activated. With a low
				or worse PDP context
				activation, access to
				data could be a
				challenge.
Retainability	Traffic	The proportion of user	Real traffic or	Primary
	channel	devices which, having	test traffic	TCH drop can be
	(TCH) drop	successfully accessed the		perceived by a user as
	rate	TCH, subsequently suffer		it directly translates to
		an abnormal release (e.g.,		call drop.
		clause 5.3 of
		[b-ETSI TR 32.814]).
	Handover	The percent of handovers	Real traffic or	Secondary
	success rate	that were attempted from	test traffic	Handover can
		the source cell (cell for		guarantee call
		which the statistic is		continuity and can
		presented) that succeeded in		indicate influencing
		making it to the destination		factors that include
		cell (e.g., clause 5.4 of		among other things,
		[b-ETSI TR 32.814]).		congestion, coverage,
				interference, and
				clocking problems.
				A poor/low handover
				success rate could
				influence other KPIs
				(e.g., TCH drop).

[0119]

TABLE 2
Example KPIs for UMTS Network
	Key
	performance
	indicators		Measurement
Category	(KPIs)	Definition	approach	Considerations
Availability	Radio coverage-	User device coverage can	Theoretical	This parameter can
	Received signal	represent the RSCP level	calculation or	estimate the
	code power	of signal or reception in a	Drive test	geographic reach of a
	(RSCP)	given area in which a user		mobile UMTS
		device can have		network.
		successfully access both
		for data and voice services
		(e.g., [ITU-T E.806]).
Accessibility	Circuit switch	Describes the ratio of all	Real traffic or	Primary
	(CS) radio	successful RRC	test traffic	This KPI can indicate
	resource control	establishments to RRC		the signalling
	(RRC) setup	establishment attempts		functions that
	success rate	(e.g., clause 7.2 of [ETSI		configures the UE and
		TS 132 410]).		control planes to allow
				other functions (e.g.,
				calls, handover, etc.)
				and resource
				management to be
				implemented. This
				KPI can be used for
				troubleshooting and
				dimension purposes. It
				can be used to
				determine RNC or cell
				admission capacity or
				system load.
	Radio access	The ratio of successful		Primary
	bearer (RAB)	conversational speech		Can be used to
	establishment	related RAB		evaluate speech
	success rate for	establishments to		service accessibility.
	circuit switch	conversational speech		This KPI can be used
	(CS)	related RAB		to determine planning
		establishment attempts		and dimension, speech
		(e.g., clause 7.1.1 of		calls redirected to gsm,
		[ETSI TS 132 410]).		or calls unto the 3G
				network via incoming
				IRAT handover.
	Radio access	Describes the ratio of all	Real traffic	Primary
	bearer (RAB)	successful PS RAB		Can be used to
	establishment	establishments to PS		evaluate packet-based
	success rate for	related RAB		service accessibility.
	packet switch	establishment attempts
	(PS)	(e.g., clause 7.1 of [ETSI
		TS 132 410]).
Retainability	Radio access	Describes the ratio of	Real traffic or	Primary
	bearer (RAB)	number of RAB release	test traffic	Any RAB abnormal
	abnormal release	requests to number of the		release after RAB
	rate	successful RAB		establishment and
		establishments (e.g.,		alerting can be
		clause 8.1 of [ETSI TS		considered a drop call.
		132 410]).
	Soft handover	Describes the ratio of	Real traffic or	Secondary
	success rate	number of successful	test traffic	Measures the
		radio link additions to the		simultaneous
		total number of radio link		establishment of links
		addition attempts (e.g.,		to two base stations. It
		clause 9.1 of		can indicate that this
		[ETSI TS 132 410]).		handover success is
				high because issues
				can result in a dropped
				call.
	Circuit switch	Describes the ratio of	Real traffic or	Secondary
	(CS) inter radio	number of successful inter	test traffic	This KPI can be used
	access	RAT handover to the total		to evaluate whether
	technology	number of the attempted		the capacity on the cell
	(RAT) handover	inter RAT handover from		(i.e., on the GSM
	success rate	UMTS to GSM for CS		network) that the UE
		domain (e.g., clause 9.3 of		is trying to enter for
		[ETSI TS 132 410]).		CS may be insufficient
				or not.
	Packet switch	Describes the ratio of	Real traffic or	Secondary
	(PS) inter RAT	number of successful inter	test traffic	This KPI can be used
	handover success	RAT handover to the total		to evaluate whether
	rate	number of the attempted		the capacity on the cell
		inter RAT handover from		(i.e., on the GSM
		UMTS to GSM for PS		network) that the UE
		domain (e.g., clause 9.4 of		is trying to enter for
		[ETSI TS 132 410]).		PS may be insufficient
				or not.

[0120]

TABLE 3
Example KPIs for LTE Network
	Key
	performance
	indicators		Measurement
Category	(KPIs)	Definition	approach	Considerations
Availability	Radio coverage-	Mobile coverage	Theoretical	This parameter is
	RSRP reference	essentially represents	calculation/	important for the
	signal received	the strength/power level	Drive test	estimation of the
	power	of signal or reception in		geographic reach of a
		a given area in which an		mobile LTE network.
		end user can have
		successfully access both
		for data and voice
		services (e.g.,
		[ITU-T E.806]).
Accessibility	E-UTRAN radio	Probability for an end-	Real traffic	Primary
	access bearer (E-	user to be provided with	or test traffic	It is a major KPI in LTE
	RAB)	an E-RAB at request		for measuring
	accessibility	(e.g., clause 6.1.1 of		accessibility. For the
		[ETSI TS 132 450]).		purposes of optimisation,
				it helps understand the
				common failures that
				usually cause E-RAB
				setup failures.
Retainability	Evolved-UMTS	A measurement that	Real traffic	Primary
	terrestrial radio	shows how often an	or test traffic	E-RAB is an important
	access network	end-user abnormally		parameter in LTE KPI
	(E-UTRAN)	loses an E-RAB during		analysis. An E-RAB
	Radio access	the time the E-RAB is		abnormal release means
	bearer (E-RAB)	used (e.g., clause 6.2.1.2		that an ongoing session is
	abnormal release	of [ETSI TS 132 450]).		dropped requiring the user
	rate			to initiate a new
				connection to resume the
				services.
Integrity	Latency	A measurement	Test traffic	Primary
		that shows how		Latency impacts the
		E-UTRAN impacts on		network's throughput and
		the delay experienced		thus the user's experience.
		by an end-user. Time		The higher the latency,
		from reception of IP		the higher the delays and
		packet to transmission		the poorer the user's
		of first packet over the		experience
		air interface (e.g., clause
		6.3.2 of [ETSI TS 132
		450]).

[0121]

TABLE 4
Example KPIs for LTE Network
LTE KPI	Test Case
Accessibility	RRC Connection Establishment
	Random Access
	Initial E-RAB Establishment Success Rate
	RRC Connection Establishment Counters
	Initial E-RAB Establishment Success Rate Counters
	Added E-RAB Establishment Success Rate Counters
	Added E-RAB Establishment Success Rate
	S1 Signaling Connection Establishment
Retainability	MME Initiated E-RAB & UE Context Release with
	counters Description
	UE Session Time
	RBS Initiated E-RAB & UE Context Release with
	counters Description
	MME & RBS Initiated UE Context Release Flow
	Chart
	MME & RBS Initiated E-RAB Release Flow Chart
Integrity	E-UTRAN Throughput KPIs
	E-UTRAN Latency KPIs
	E-UTRAN Packet Loss KPIs
Mobility	X2 Based Handover Preparation & Execution
	Intra RBS Handover Preparation & Execution
	Intra Frequency Handover Preparation & Execution
	Counters
	S1 Based Handover Preparation & Execution
	Intra-frequency intra-LTE S1 & X2 Handover
	Flowchart
	Inter Frequency Handover Preparation & Execution
	Counters
	Inter-frequency intra-LTE S1 & X2 Handover
	Flowchart
Availability	Partial cell availability (node restarts excluded)

[0122]

TABLE 5
Example KPIs for 5G Network
5G performance
requirement type	Minimum KPI requirement	category
Peak Data Rate	Downlink: 20 Gbps	eMBB
	Uplink: 10 Gbps
Peak Spectral Efficiency	Downlink: 30 bits/sec/Hz	eMBB
	Uplink: 15 bits/sec/Hz
Data rate experienced by	Downlink: 100 Mbps	eMBB
User	Uplink: 50 Mbps
Area Traffic Capacity	Downlink: 10 Mbits/sec/m2	eMBB
	in indoor hotspot
	(eMBB test environment)
Latency (User Plane)	4 ms for eMBB	eMBB, URLLC
	1 ms for URLLC
Latency (User Plane)	20 ms	eMBB,
	(10 ms encouraged)	URLLC
Connection Density	1 × 106 devices/Km2	mMTC
Average Spectral Efficiency	(All the below figures are in units of	eMBB
	bits/sec/Hz/TRxP)
	Indoor hotspot: DL:9/UL 6.75
	Dense Urban:DL:7.8/UL:5.4
	Rural: DL: 3.3/UL:1.6
Energy Efficiency	Efficient data transmission (Loaded case):	eMBB
	To be demonstrated by “average spectral
	efficiency”.
	Low energy consumption (no data case):
	This test case should support high sleep
	ratio/long sleep duration.
Reliability	1 × 10−5 probability of transmitting layer-2	URLLC
	Power Distribution Unit (PDU) of 32 bytes
	in size within 1 ms (in channel quality of
	coverage edge for Urban Macro-URLLC test
	environment.)
Mobility	Dense Urban: up to 30 Km/h	eMBB
	Rural: up to 500 Km/h
Mobility Interruption Time	0 ms	eMBB,
		URLLC
Bandwidth (Maximum	At least 100 MHZ	IMT-2020
Aggregated System)	Up to 1 GHz for operation in high
	frequency bands i.e. above 6 GHz

[0123] The multi-network management system 130 can receive one or more of the example KPIs in the tables above, or one or more combinations of these example KPIs. Additionally, the multi-network management system 130 can process each KPI received (e.g., via a network interface) using one or more processors via computer storage media having computer-executable instructions embodied thereon. In some embodiments, at least one KPI for each RAN node is received in real-time.

[0124] In some embodiments, the multi-network management system 130 can transmit interface self-configuration and optimization. In some embodiments, the multi-network management system 130 can shift one or more operations or one or more loads between network domains corresponding to the network managers 116A-116C and based on receiving the network performance data (e.g., one or more KPI types) from each of the network managers 116A-116C. For example, the multi-network management system 130 can allocate various resources or resource usages corresponding to the plurality of RAN nodes within a plurality of coverage areas. In some embodiments, the multi-network management system 130 can be integrated with operations support systems or customer experience management tools corresponding to each of the network managers 116A-116C. In some embodiments, the multi-network management system 130 can connect to one or more transport provisioning tools (e.g., a software defined networking controller) of the network managers 116A-116C via a standard measurement and configuration interface or can act as a user of one or more of the transport provisioning tools.

[0125] In some embodiments, each of network managers 116A-116C are above a threshold distance from each other. In some embodiments, one or more of the network managers 116A-116C include self-organizing network technology that can apply true plug-and-play, self-configuration, and self-optimization. In some embodiments, one or more of the network managers 116A-116C are deployed at an eNB, a signaling gateway, or a system architecture evolution gateway. For example, the network manager 116A can be a software entity running on the eNB or attached to the eNB as a site device. As another example, the network manager 116A can configure transport connectivity of base station 114A and base station 114B. In some embodiments, the network managers 116A-116C can extract real-time quality of experience and QoS measurements (e.g., one or more KPIs) from control plane traffic of the base station 114A and 114B. In some embodiments, one or more of the network managers 116A-116C can implement a closed control loop.

[0126] In embodiments, the multi-network management system 130 can receive network performance data (e.g., from network managers 116A-116C) corresponding to one or more of user devices 102A-102D, the base stations 114A-114F, satellites 120A-120B, another network component (e.g., an MME), or one or more combinations thereof. As one example, the network performance data can correspond to communications between user device 102D and base station 114D over coverage area 110D. As another example, the network performance data can correspond to communications between user device 102B and one or more of base stations 114E and 114F (or a handover between base stations 114E and 114F) over coverage area 110E. As another example, the network performance data can correspond to communications between user device 102C and one or more of base stations 114A and 114B (or a handover between base stations 114A and 114B) over coverage areas 110B or 110C. In another example, the network performance data can correspond to communications between user device 102C and satellite 120A, or a handover between satellite 120A and base station 114B.

[0127] In yet another example, the network performance data can correspond to an enhanced broadband communication, an ultra-reliable communication, a low latency communication, another type of communication, or one or more combinations thereof, within one or more portions of coverage area 110A. In some embodiments, the network performance data can correspond to a License Assisted Access communication, an LTE-Unlicensed radio access technology communication, an unlicensed band communication, a carrier sensing operation for collision avoidance and detection, a downlink transmission, an uplink transmission, a P2P transmission, a D2D transmission, another type of unlicensed spectrum operation, an FD-MIMO communication, a massive MIMO communication, an MU-MIMO communication, a cooperative MIMO communication, a 4G communication, a 5G communication, another generation communication, another type of communication, or one or more combinations thereof. In some embodiments, the network performance data can correspond to ultra-reliable communications, low-latency communications, mission critical communications, ultra-reliable low-latency communications, RAN node ultra-reliable functions, RAN node low-latency functions, RAN node critical functions, mission critical push-to-talk functions, mission critical imaging functions, another type of coverage area 110A device communication or function, or one or more combinations thereof.

[0128] In embodiments, one or more of the user devices 102A-102D, the base stations 114A-114F, satellites 120A-120B, the multi-network management system 130, another network component (e.g., an MME), or one or more combinations thereof, may have one or processors capable of processing network performance data (e.g., KPIs), user device location data, weather data (e.g., humidity data, ultraviolet data, temperature data), ultra-reliable data, low-latency data, critical data, other types of data, or one or more combinations thereof. In some embodiments, the multi-network management system 130 has one or more processors, which may include one or more of a system-on-a-chip, a processor core, a graphics processor unit, a central processing unit, an accelerator (e.g., a digital signal processor, a graphics accelerator, a compression accelerator, an artificial intelligence accelerator), a chipset processor, a general-purpose processor, a general-purpose graphics processor unit, an accelerated processing unit, a field-programmable gate array, a neural network processing unit, a data processor unit, a controller, another type of processor or processor unit, or one or more combinations thereof. In some embodiments, a processor unit of the multi-network management system 130 may be located in a single integrated circuit component (e.g., multi-chip module) or in separate integrated circuit components.

[0129] In embodiments, the one or more processors of the multi-network management system 130 can determine a capacity for each of the plurality of network managers based on the at least one KPI received for a RAN node (e.g., base station 114A, satellite 120A, another network component of coverage area 110A, an antenna element or antenna array of base station 114C, an antenna element or antenna array of satellite 120B). In one non-limiting example, the one or more processors of multi-network management system 130 can analyze network performance data received in real-time, wherein the network performance data includes a first set of KPIs received during a first predetermined time range at a first predetermined rate, and wherein the KPIs correspond to one or more downlinks from base station 114C to user device 102C. Continuing this example, the KPIs can include measurements of the downlink by user device 102C (e.g., SINR). Additionally or alternatively, the KPIs can correspond to antenna elements of the base station 114C (e.g., antenna tilt and antenna angle).

[0130] In embodiments, the multi-network management system 130 can cause the display, via a user interface (e.g., of a user device 102A-102D or another user device in communication with or part of the multi-network management system 130), a dashboard comprising a capacity icon for the capacity determined for each of the plurality of network managers. The capacity icon for each of the plurality of network managers can displayed on the dashboard based on an identifier for each of the plurality of network managers (e.g., a network manager location identifier, a RAN node identifier for each of the RAN nodes in communication with a network manager, another type of network manager identifier). In an embodiment, the multi-network management system 130 can identify a first network manager having a first plurality of RAN nodes managed by the first network manager and a second network manager having a second plurality of RAN nodes managed by the second network manager. Based on identifying the first network manager and the second network manager, the multi-network management system 130 can determine that a first capacity of the first network manager is above a first threshold and that a second capacity for the second network manager is below a second threshold, wherein the first threshold corresponds to the first plurality of RAN nodes and the second threshold corresponds to the second plurality of RAN nodes. Based on these determinations, the multi-network management system 130 can provide an indication on the dashboard for resource reallocation from the first network manager to the second network manager. In an aspect, the resource reallocation corresponds to a rate at which the first network manager receives at least one KPI for a first RAN node in communication with the first network manager and a rate at which the second network manager receives at least one KPI for a second RAN node in communication with the second network manager.

[0131] In some embodiments, the multi-network management system 130 can collect, retrieve, parse, or extract the network performance data from one or more of the network managers 116A, 116B and 116C (e.g., the multi-network management system 130 can collect, retrieve, parse, or extract JSON files), transmit the network performance data (e.g., the JSON files) to one or more servers associated with the multi-network management system 130. For example, the multi-network management system 130 can interpret the network performance data, apply a uniform formatting to the network performance data from each of the network managers 116A, 116B and 116C, and create scripts using the network performance data. In addition, the multi-network management system 130 can save the interpretations, formatting, scripts, other operations, or one or more combinations thereof to one or more databases (e.g., a MariaDB) associated with the multi-network management system and also display these in the dashboard (e.g., a Grafana dashboard).

[0132] FIG. 2 provides example capacity dashboard 200 provided by multi-network management system (e.g., the multi-network management system 130 of FIG. 1), in accordance with one or more embodiments disclosed herein. Example capacity dashboard 200 is but one example of a capacity dashboard and is not intended to suggest a particular limitation as to the scope of use or functionality of the invention. Neither should the capacity dashboard 200 be interpreted as having any particular dependency or requirement relating to any one or combination of components illustrated. For example, in some embodiments, the example capacity dashboard 200 can include capacity icons not depicted.

[0133] Example capacity dashboard 200 includes a plurality of capacity icons determined using one or more KPIs corresponding to Configuration Change Notification (CCN) utilization in %, each of the capacity icons being associated with a network manager (e.g., network manager 116A of FIG. 1). A first capacity icon “CROSS” (a “CR” Operations Support System, wherein CR corresponds to a first network manager) depicts a first capacity utilization of a first network manager. For example, the first capacity icon provides an indication of the first utilization of the first network manager having 149% capacity. In addition, the first capacity icon is visually different from a second capacity icon “SROSS” (a “SR” Operations Support System, wherein SR corresponds to a second network manager), since the first capacity is higher than the second capacity for the second capacity icon, which provides an indication of the second utilization of the second network manager having 70% capacity utilization. The first capacity icon in this example does not have available capacity, and the second capacity icon has 30% available capacity remaining.

[0134] In some embodiments, one or more thresholds can be determined for each capacity icon for each network manager. For example, in some embodiments, the threshold is 80% utilization with 20% or less available capacity. In some embodiments, a second threshold may be 100%. In some embodiments, the dashboard can automatically update capacity icons as the multi-network management system continuously receives KPIs from RAN nodes for each network manager. For example, “T3OSS” capacity icon can increase or decrease from the illustrated 39% as KPIs are being received. As such, the dashboard can provide an alert for capacity icons that have capacity utilization increasing at a rate above a predetermined threshold rate. In some embodiments, the dashboard can provide an alert for capacity icons that have capacity availability decreasing at a rate above a predetermined threshold rate. In some embodiments, the dashboard can provide notifications for capacity icons that have capacity availability that is increasing at a predetermined rate.

[0135] FIG. 3 provides example capacity dashboard 300 provided by multi-network management system (e.g., the multi-network management system 130 of FIG. 1), in accordance with one or more embodiments disclosed herein. Example capacity dashboard 300 is but one example of a capacity dashboard and is not intended to suggest a particular limitation as to the scope of use or functionality of the invention. Neither should the capacity dashboard 300 be interpreted as having any particular dependency or requirement relating to any one or combination of components illustrated. For example, in some embodiments, the example capacity dashboard 300 can include capacity icons not depicted.

[0136] Example capacity dashboard 300 includes a plurality of capacity icons determined using one or more KPIs corresponding to Millions Counters Per Hour (MCPH) Utilization in %, each of the capacity icons being associated with a network manager (e.g., network manager 116A of FIG. 1). A first capacity icon “CROSS” (a “CR” Operations Support System, wherein CR corresponds to a first network manager) depicts a first capacity utilization of a first network manager. For example, the first capacity icon provides an indication of the first utilization of the first network manager having 165% capacity. In addition, the first capacity icon is visually different from a second capacity icon “SROSS” (a “SR” Operations Support System, wherein SR corresponds to a second network manager), since the first capacity is higher than the second capacity for the second capacity icon, which provides an indication of the second utilization of the second network manager having 66% capacity utilization. The first capacity icon in this example does not have available capacity, and the second capacity icon has 24% available capacity remaining.

[0137] The capacity icon for each of the plurality of network managers is displayed on the dashboard based on at least one identifier for each of the plurality of network managers. For example, the identifiers in this example include “CR,” “C5,” “SR,” etc., and the example capacity dashboard 300 has displayed the capacity icons based on at least this identifier for each of the plurality of network managers (e.g., alphabetically by identifier). In some embodiments, “CR” corresponds to a location of the network manager. In other embodiments, the capacity icons can be displayed on the dashboard in an ascending order from a highest capacity utilization to a lowest capacity utilization, or in a descending order from a lowest capacity utilization (e.g., the “TKOSS” capacity icon) to the highest capacity utilization (e.g., the “CROSS” capacity icon). In some embodiments, each capacity icon can correspond to each RAN node that is in communication with each network manager.

[0138] FIG. 4 provides example overall capacity dashboard 400 provided by multi-network management system (e.g., the multi-network management system 130 of FIG. 1), in accordance with one or more embodiments disclosed herein. Example capacity dashboard 400 is but one example of a capacity dashboard and is not intended to suggest a particular limitation as to the scope of use or functionality of the invention. Neither should the capacity dashboard 400 be interpreted as having any particular dependency or requirement relating to any one or combination of components illustrated. For example, in some embodiments, the example capacity dashboard 400 can include capacity icons not depicted.

[0139] Example capacity dashboard 400 includes a plurality of capacity icons determined using one or more KPIs corresponding to OSS Overall Capacity Utilization in %, each of the capacity icons being associated with a network manager (e.g., network manager 116A of FIG. 1). A first capacity icon “CROSS” (a “CR” Operations Support System, wherein CR corresponds to a first network manager) depicts a first capacity utilization of a first network manager. For example, the first capacity icon provides an indication of the first utilization of the first network manager having 63% capacity. In addition, the first capacity icon is visually different from a second capacity icon “TKOSS” (a “TK” Operations Support System, wherein TK corresponds to a second network manager), since the first capacity is higher than the second capacity for the second capacity icon, which provides an indication of the second utilization of the second network manager having 0% capacity utilization. The first capacity icon in this example has 27% available capacity, and the second capacity icon has 100% available capacity remaining. In this example embodiment of the capacity dashboard, example capacity dashboard 400 does not have any capacity icons at 100% capacity utilization, and each of the capacity icons depict capacity availability associated with each corresponding network manager.

[0140] Example capacity dashboard 500 depicted in FIG. 5 includes network manager identifiers (e.g., “cross,” “c5oss,” “sross,” “s2oss,” etc.), numeric network manager identifiers (e.g., 1611, 16112, 16113, 16114, etc.), network manager size indicators (e.g., XXL+, 3XL+100K, etc.), as well as other network cell capacity data. In some embodiments, the capacity dashboard 500 provides each of the capacity rows based on a particular technology. In some embodiments, the one or more KPIs used to generate example capacity dashboard 500 may include one or more of TRX/2G Cell, TRX/2G Normalized Cell, WCDMA/3G Cell, WCDMA/3G Normalized Cell, LTE Cell, NRCEL/5G Cell, NBIOT Cell, Normalized Total Cell, Normalized Cell Capacity, Normalized Cell Total Utilization in %, another KPI, or one or more combinations thereof.

[0141] Additionally, FIG. 6 provides example capacity dashboard 600 having capacity rows that are displayed based on a particular identifier (e.g., alphabetically based on network manager identifiers (e.g., “cross,” “c5oss,” “sross,” “s2oss,” etc.)). In some embodiments, the one or more KPIs used to generate example capacity dashboard 600 may include one or more of BSC object count, BTS object count, RNC object count, WBTS object count, LNBTS object count, Nrbts object count, Total object count, another KPI, or one or more combinations thereof. In addition, FIG. 7 provides example capacity dashboard 700 having capacity rows that are displayed based on a particular identifier (e.g., alphabetically based on network manager identifiers (e.g., “cross,” “c5oss,” “s5oss,” “s2oss,” etc.)). Further, example capacity dashboard 700 displays normalized total utilizations, which can be determined by the multi-network management system. Example capacity dashboard 700 also displays a plurality of thresholds (e.g., a normalized cap, a CCN event cap, etc.), which can be determined by the multi-network management system. In some embodiments, the one or more KPIs used to generate example capacity dashboard 700 may include one or more of NetAct Utilization, Normalized Cell Total, Normalized Capacity, Normalized Total Utilization, CCN Event Per Min, CCN Event per Min Capacity, CCN Event per Min Utilization, MCPH, MCPH Capacity, MCPH Utilization, FM Event per Second, FM Event per Second Capacity, FM Event per Second Utilization, another KPI, or one or more combinations thereof. Furthermore, example capacity dashboard 800 of FIG. 8 displays a plurality of capacity rows that are displayed based on numeric network manager identifiers (e.g., 408, 409, 410, 411, etc.). In some embodiments, the one or more KPIs used to generate example capacity dashboard 800 may include one or more of NetAct Utilization, MCPH, MCPH Capacity, MCPH Utilization, PM file count, PM file capacity, PM file utilization, CCN Event Per Min, CCN Event per Min Capacity, CCN Event per Min Utilization, FM Event per Second, FM Event per Second Capacity, FM Event per Second Utilization, another KPI, or one or more combinations thereof.

[0142] FIG. 9 illustrates example capacity dashboard 900 and FIG. 10 provides example capacity dashboard 1000. In some embodiments, the one or more KPIs used to generate example capacity dashboard 900 may include one or more of RAN Normalized Network Utilization, another KPI, or one or more combinations thereof. In some embodiments, the one or more KPIs used to generate example capacity dashboard 1000 may include one or more of USD/PaCo Normalized Network Utilization, another KPI, or one or more combinations thereof. In embodiments, example capacity dashboard 1000 displays a first capacity icon having a highest capacity utilization (e.g., D5OSS PM Files Utilization icon having 85% capacity utilization) and a plurality of capacity icons having the lowest capacity utilization (e.g., D2OSS PM Files Utilization having 0% capacity utilization, P2OSS PM Files Utilization having 0% capacity utilization, etc.). The D5OSS MCPH Utilization icon having 3% capacity utilization is visually different from the D5OSS PM Files Utilization Icon, wherein the 3% capacity utilization is displayed having a different pattern from the 85% capacity utilization having a pattern that is more visually prominent. In some embodiments, the example capacity dashboard 1000 provides an alert for the D5OSS PM Files Utilization icon having 85% capacity utilization, which may be above a first threshold. In some embodiments, the example capacity dashboard 1000 provides another type of notification for when the capacity utilization moves below the threshold based on KPIs from a corresponding RAN node.

Example Flowchart

[0143] Having described the example embodiments discussed above, an example flowchart is described below with respect to FIG. 11. Example flowchart 1100 begins at Step 1102 with establishing a connection, via a multi-network management system, with a plurality of network managers, wherein each of the plurality of network managers are in communication with one or more RAN nodes. In some embodiments, the multi-network management system is connected with the plurality of network managers over one or more backhaul links (e.g., via an X2, Xn, or other interface) either directly (e.g., directly between base stations), or indirectly (e.g., via core network), or one or more combinations thereof. The backhaul links may be or include one or more wireless links, for example.

[0144] Step 1104 includes receiving network performance data (e.g., at least one KPI) for each of the plurality of RAN nodes that are in connection with one or more network managers. In some embodiments, the multi-network management system receives a first set of KPIs from a first RAN node corresponding to a first network manager, a second set of network performance data from a second RAN node corresponding to a second network manager, a third set of network performance data from a third RAN node corresponding to the second network manager, a fourth set of network performance data from a fourth RAN node corresponding to the second network manager, a fifth set of network performance data from a fifth RAN node corresponding to a third network manager, and a sixth set of network performance data from a sixth RAN node corresponding to a fourth network manager. In one aspect, the first RAN node and the second RAN node are different types of RAN nodes. In some embodiments, the fourth RAN node and the fifth RAN node implement different generation communication systems. In some embodiments, the first network manager and the second network manager have one or more different network manager components. In some embodiments, the first node and the third node are above a threshold distance from each other. In some embodiments, the first network manager and the second network manager are above a threshold distance from each other.

[0145] In some embodiments, the multi-network management system receives historical KPIs for each of the RAN nodes in communication with each of the plurality of network managers. In some embodiments, each of the KPIs or each of the historical KPIs correspond to RAN node capabilities or RAN node operating configurations of the respective RAN node. In some embodiments, one or more KPIs are received in real-time. In some embodiments, one or more KPIs correspond to one or more of the following categories: accessibility, retainability, integrity, mobility, availability, another type of category, or one or more combinations thereof. In some embodiments, one or more KPIs correspond to a peak data rate for a downlink associated with a RAN node, a peak data rate for an uplink associated with a RAN node, a peak spectral efficiency corresponding to a downlink, a peak spectral efficiency corresponding to an uplink, an area traffic capacity associated with an indoor hotspot and a downlink from a RAN node to a 5G communication component (e.g., an eMBB), a connection density, or another type of KPI.

[0146] At Step 1106, a capacity is determined for each network manager in communication with the multi-network management system. In some embodiments, the capacity is determined based on one or more KPIs received for each of the plurality of RAN nodes in communication with a particular network manager. In some embodiments, the capacity for each network manager is determined based on identifying a network manager for each RAN node in communication with the network manager. In some embodiments, a first capacity is determined for a first network manager having the highest capacity utilization and a second capacity is determined for a second network manager having the lowest capacity utilization. In some embodiments, one or more capacities for one or more network managers are updated based on receiving additional KPIs. In some embodiments, a total capacity associated with each of the network managers in communication with the multi-network management system is determined.

[0147] Step 1108 includes displaying, via a user interface, a dashboard comprising a capacity icon for the capacity determined for each of the plurality of network managers, wherein the capacity icon for each of the plurality of network managers is displayed on the dashboard based on at least one identifier for each of the plurality of network managers. In some embodiments, a capacity icon for each of the plurality of network managers is displayed on the dashboard in an ascending order from a highest capacity utilization to a lowest capacity utilization. In some embodiments, the capacity icon for each of the plurality of network managers is displayed on the dashboard in a descending order from a lowest capacity utilization to a highest capacity utilization. In some embodiments, the capacity icon for the highest capacity utilization is visually different from the capacity icon for the lowest capacity utilization.

[0148] Step 1110 includes determining a first capacity for a first network manager of the plurality of network managers is above a threshold. In some embodiments, a threshold for one or more of each network managers is determined based on historical KPIs associated with one or more RAN nodes in communication with a network manager. In some embodiments, the threshold is determined based on RAN node capabilities and RAN node operating configurations for each RAN node in communication with the network manager. Based on this, the dashboard can be updated at Step 1112. For example, an alert can be provided for the first capacity on the dashboard. Additionally, a second capacity can be determined for a second network manager of the plurality of network managers, the second capacity being within a predetermined range that is approaching the threshold. Based on this, an indication for the second capacity can be provided on the dashboard. In some embodiments, a threshold for each of the plurality of network managers can be determined based on historical KPIs of each of the plurality of network managers and based on RAN node capabilities and RAN node operating configurations for each of the plurality of RAN nodes that correspond to each network manager of the plurality of network managers. Based on this, the capacity for each of the plurality of network managers can be determined.

[0149] In some embodiments, a first capacity for a first network manager and a second capacity for a second network manager is determined to be above a threshold. Based on this, an alert for the first capacity and the second capacity can be provided on the dashboard. In some embodiments, a first network manager of the plurality of network managers is identified, wherein the first network manager corresponds to the highest capacity utilization and a second network manager of the plurality of network managers is identified that corresponds to the lowest capacity utilization. Based on this, it is determined that a first capacity of the first network manager is above a threshold and that a second capacity for the second network manager is below the threshold. Based on this, an indication for resource reallocation from the first network manager to the second network manager is provided. In embodiments, the resource allocation corresponds to a rate at which the first network manager receives the at least one KPI for each RAN node of the first network manager and a rate at which the second network manager receives the at least one KPI for each RAN node of the second network manager.

[0150] In some embodiments, based on identifying a first network manager and a second network manager, it is determined that a first capacity of the first network manager is above a first threshold and that a second capacity for the second network manager is below a second threshold, the first threshold corresponding to the plurality of RAN nodes managed by the first network manager, the second threshold corresponding to the plurality of RAN nodes managed by the second network manager. Based on this, an indication is provided on the dashboard for resource reallocation from the first network manager to the second network manager. In some embodiments, a third network manager of the plurality of network managers is identified. Based on this, it is determined that a third capacity of the third network manager is below a third threshold, the third threshold corresponding to the plurality of RAN nodes managed by the third network manager. Based on this, an indication on the dashboard for resource reallocation from the first network manager to the third network manager is provided. In embodiments, the resource allocation corresponds to increasing a rate at which the first network manager receives the at least one KPI for each RAN node of the first network manager and decreasing the rate at which the second network manager and the third network manager receive the at least one KPI for each RAN node.

[0151] In some embodiments, it is determined that the second capacity of the second network manager is closer to the second threshold for the second network manager than the third capacity for the third network manager is to the third threshold. Based on this, the multi-network management system can cause the rate at which the third network manager receives the at least one KPI for each RAN node to decrease to a lower rate than the rate for the second network manager. In some embodiments, it is determined that a fourth capacity corresponding to a fourth network manager is closer to a fourth threshold than the third capacity is to the third threshold. Based on this, the multi-network management system can cause the rate at which the third network manager receives the at least one KPI for each RAN node to decrease to a lower rate than the rate for the fourth network manager.

Example User Device

[0152] Having described the example embodiments discussed above of the presently disclosed technology, an example operating environment of an example user device (e.g., user device 102A of FIG. 1) is described below with respect to FIG. 12. User device 1200 is but one example of a suitable computing environment, and is not intended to suggest any particular limitation as to the scope of use or functionality of the technology disclosed. Neither should user device 1200 be interpreted as having any dependency or requirement relating to any particular component illustrated, or a particular combination of the components illustrated in FIG. 12.

[0153] As illustrated in FIG. 12, example user device 1200 includes a bus 1202 that directly or indirectly couples the following devices: memory 1204, one or more processors 1206, one or more presentation components 1208, one or more input/output (I/O) ports 1210, one or more I/O components 1212, a power supply 1214, and one or more radios 1216.

[0154] Bus 1202 represents what may be one or more busses (such as an address bus, data bus, or combination thereof). Although the various blocks of FIG. 12 are shown with lines for the sake of clarity, in reality, these blocks represent logical, not necessarily actual, components. For example, one may consider a presentation component, such as a display device, to be an I/O component. Also, processors have memory. Accordingly, FIG. 12 is merely illustrative of an exemplary user device that can be used in connection with one or more embodiments of the technology disclosed herein.

[0155] User device 1200 can include a variety of computer-readable media. Computer-readable media can be any available media that can be accessed by user device 1200 and may include both volatile and nonvolatile media, removable and non-removable media. By way of example, and not limitation, computer-readable media may comprise computer storage media and communication media. Computer storage media includes both volatile and nonvolatile, removable and 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 includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disks (DVDs) 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 user device 1200. Computer storage media does not comprise signals per se. 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. One or more combinations of any of the above should also be included within the scope of computer-readable media.

[0156] Memory 1204 includes computer storage media in the form of volatile and/or nonvolatile memory. The memory 1204 may be removable, non-removable, or a combination thereof. Example hardware devices of memory 1204 may include solid-state memory, hard drives, optical-disc drives, other hardware, or one or more combinations thereof. As indicated above, the computer storage media of the memory 1204 may include RAM, Dynamic RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, a cache memory, DVDs or other optical disk storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, a short-term memory unit, a long-term memory unit, any other medium which can be used to store the desired information and which can be accessed by user device 1200, or one or more combinations thereof.

[0157] The one or more processors 1206 of user device 1200 can read data from various entities, such as the memory 1204 or the I/O component(s) 1212. The one or more processors 1206 may include, for example, one or more microprocessors, one or more CPUs, a digital signal processor, one or more cores, a host processor, a controller, a chip, a microchip, one or more circuits, a logic unit, an integrated circuit (IC), an application-specific IC (ASIC), any other suitable multi-purpose or specific processor or controller, or one or more combinations thereof. In addition, the one or more processors 1206 can execute instructions, for example, of an operating system of the user device 1200 or of one or more suitable applications.

[0158] The one or more presentation components 1208 can present data indications via user device 1200, another user device, or a combination thereof. Example presentation components 1208 may include a display device, speaker, printing component, vibrating component, another type of presentation component, or one or more combinations thereof. In some embodiments, the one or more presentation components 1208 may comprise one or more applications or services on a user device, across a plurality of user devices, or in the cloud. The one or more presentation components 1208 can generate user interface features, such as graphics, buttons, sliders, menus, lists, prompts, charts, audio prompts, alerts, vibrations, pop-ups, notification-bar or status-bar items, in-app notifications, other user interface features, or one or more combinations thereof.

[0159] The one or more I/O ports 1210 allow user device 1200 to be logically coupled to other devices, including the one or more I/O components 1212, some of which may be built in. Example I/O components 1212 can include a microphone, joystick, game pad, satellite dish, scanner, printer, wireless device, and the like. The one or more I/O components 1212 may, for example, provide a natural user interface (NUI) that processes air gestures, voice, or other physiological inputs generated by a user. In some instances, the inputs the user generates may be transmitted to an appropriate network element for further processing. An NUI may implement any combination of speech recognition, touch and stylus recognition, facial recognition, biometric recognition, gesture recognition both on screen and adjacent to the screen, air gestures, head and eye tracking, and touch recognition associated with the one or more presentation components 1208 on the user device 1200. In some embodiments, the user device 1200 may be equipped with one or more imaging devices, such as one or more depth cameras, one or more stereoscopic cameras, one or more infrared cameras, one or more RGB cameras, another type of imaging device, or one or more combinations thereof, (e.g., for gesture detection and recognition). Additionally, the user device 1200 may, additionally or alternatively, be equipped with accelerometers or gyroscopes that enable detection of motion. In some embodiments, the output of the accelerometers or gyroscopes may be provided to the one or more presentation components 1208 of the user device 1200 to render immersive augmented reality or virtual reality.

[0160] The power supply 1214 of user device 1200 may be implemented as one or more batteries or another power source for providing power to components of the user device 1200. In embodiments, the power supply 1214 can include an external power supply, such as an AC adapter or a powered docking cradle that supplements or recharges the one or more batteries. In aspects, the external power supply can override one or more batteries or another type of power source located within the user device 1200.

[0161] Some embodiments of user device 1200 may include one or more radios 1216 (or similar wireless communication components). The one or more radios 1216 can transmit, receive, or both transmit and receive signals for wireless communications. In embodiments, the user device 1200 may be a wireless terminal adapted to receive communications and media over various wireless networks. User device 1200 may communicate using the one or more radios 1216 via one or more wireless protocols, such as code division multiple access (“CDMA”), global system for mobiles (“GSM”), time division multiple access (“TDMA”), another type of wireless protocol, or one or more combinations thereof. In embodiments, the wireless communications may include one or more short-range connections (e.g., a Wi-Fi® connection, a Bluetooth connection, a near-field communication connection), a long-range connection (e.g., CDMA, GPRS, GSM, TDMA, 802.16 protocols), or one or more combinations thereof. In some embodiments, the one or more radios 1216 may facilitate communication via radio frequency signals, frames, blocks, transmission streams, packets, messages, data items, data, another type of wireless communication, or one or more combinations thereof. The one or more radios 1216 may be capable of transmitting, receiving, or both transmitting and receiving wireless communications via mm waves, FD-MIMO, massive MIMO, 3G, 4G, 5G, 6G, another type of Generation, 802.11 protocols and techniques, another type of wireless communication, or one or more combinations thereof.

[0162] Having identified various components utilized herein, it should be understood that any number of components and arrangements may be employed to achieve the desired functionality within the scope of the present disclosure. For example, the components in the embodiments depicted in the figures are shown with lines for the sake of conceptual clarity. Other arrangements of these and other components may also be implemented. For example, although some components are depicted as single components, many of the elements described herein may be implemented as discrete or distributed components or in conjunction with other components, and in any suitable combination and location. Some elements may be omitted altogether. Moreover, various functions described herein as being performed by one or more entities may be carried out by hardware, firmware, and/or software. For instance, various functions may be carried out by a processor executing instructions stored in memory. As such, other arrangements and elements (for example, machines, interfaces, functions, orders, and groupings of functions, and the like) can be used in addition to, or instead of, those shown.

[0163] Embodiments of the present disclosure have been described with the intent to be illustrative rather than restrictive. Embodiments described in the paragraphs above may be combined with one or more of the specifically described alternatives. In particular, an embodiment that is claimed may contain a reference, in the alternative, to more than one other embodiment. The embodiment that is claimed may specify a further limitation of the subject matter claimed. Alternative embodiments will become apparent to readers of this disclosure after and because of reading it. Alternative means of implementing the aforementioned can be completed without departing from the scope of the claims below. Certain features and sub-combinations are of utility and may be employed without reference to other features and sub-combinations and are contemplated within the scope of the claims.

[0164] Many different arrangements of the various components depicted, as well as components not shown, are possible without departing from the scope of the claims below. Embodiments in this disclosure are described with the intent to be illustrative rather than restrictive. Alternative embodiments will become apparent to readers of this disclosure after and because of reading it. Alternative means of implementing the aforementioned can be completed without departing from the scope of the claims below. Certain features and subcombinations are of utility and may be employed without reference to other features and subcombinations and are contemplated within the scope of the claims

[0165] In the preceding detailed description, reference is made to the accompanying drawings which form a part hereof wherein like numerals designate like parts throughout, and in which is shown, by way of illustration, embodiments that may be practiced. It is to be understood that other embodiments may be utilized and structural or logical changes may be made without departing from the scope of the present disclosure. Therefore, the preceding detailed description is not to be taken in the limiting sense, and the scope of embodiments is defined by the appended claims and their equivalents.