System and method for visualizing data in a cellular network

Abstract

A system and method for visualizing data in a cellular network are disclosed. In one embodiment, the method includes presenting a network topology using a graphical user interface (GUI), the network topology being a representation of at least a portion of the cellular network. A network topology selection associated with the network topology is received. Further, parameter configuration data associated with the network topology selection is generated. A parameter audit is performed on network elements of the cellular network according to the parameter configuration data. Finally, a report of the audit is transmitted to a user device, and a visual representation of the report is presented using the GUI.

Description

[Technical Field]

[0001] Priority Claims and Cross-References This application claims priority to U.S. Non-Provisional Application No. 17 / 701,597, filed March 22, 2022, which is incorporated herein by reference in its entirety. To retrieve data from network elements in a cellular network, a user learns the routing and setup of the cellular network to route the appropriate queries and retrieve the appropriate information. The user manually inputs routing information to find the information. The user also uses learned knowledge about the cellular network to perform tasks in the cellular network once the data is retrieved. The user operates the system by manually inputting instructions to have the system perform these tasks.

[0002] Aspects of the present disclosure are best understood from the following detailed description when read in conjunction with the accompanying drawings. It should be noted that, according to standard industry practice, various features have not been drawn to scale. In fact, the dimensions of various features may be arbitrarily increased or decreased for clarity of discussion. [Brief explanation of the drawings]

[0003] [Figure 1A] 1 is a block diagram of a computer system according to an embodiment.

[0004] [Figure 1B] FIG. 1 is a block diagram of a user device, according to an embodiment.

[0005] [Figure 2] FIG. 1 is a block diagram of cellular network monitoring software and a cellular network 106 according to an embodiment.

[0006] [Figure 3]1 is an example of a graphical user interface (GUI) according to an embodiment.

[0007] [Figure 4] 10 illustrates a selection screen for an MS management system from a panel, according to an embodiment.

[0008] [Figure 5] 5 is a table containing parameter configuration data generated in response to the network topology selections described above with respect to FIG. 3 and the configuration details selections of FIG. 4, according to one embodiment.

[0009] [Figure 6] 1 is a panel using a GUI according to an embodiment.

[0010] [Figure 7] 1 is a GUI-based panel presenting a configuration history of a parameter, according to one embodiment.

[0011] [Figure 8] 10 is a panel with parameter filtering options for different characteristics of a parameter using a GUI, according to one embodiment.

[0012] [Figure 9] 1 is a flowchart of a method for visualizing data in a cellular network, according to an embodiment.

[0013] [Figure 10] 1 is a flowchart relating to a method for generating parameter configuration data related to network topology selection, according to an embodiment.

[0014] [Figure 11] 1 is a flowchart of a method for resetting parameters to historical values, according to an embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0015] The following disclosure provides many different embodiments or examples for implementing different features of the provided subject matter. To simplify the disclosure, specific examples of components, values, operations, materials, arrangements, etc. are described below. Of course, these are merely examples and are not intended to be limiting. Other components, values, operations, materials, arrangements, etc. are contemplated. For example, the formation of a first feature on or above a second feature in the following description may include embodiments in which the first and second features are formed in direct contact with each other, and may also include embodiments in which an additional feature may be formed between the first and second features such that the first and second features are not in direct contact with each other. Additionally, the present disclosure may repeat reference numbers and / or letters in various examples. This repetition is for the purposes of brevity and clarity and does not in itself dictate a relationship between the various embodiments and / or configurations described.

[0016] (Optional, used where applicable) Additionally, spatially relative terms such as beneath, below, lower, above, upper, etc. may be used herein for ease of description to describe the relationship of one element or feature, as shown in the figures, to one or more other elements or features. Spatially relative terms are intended to encompass different orientations of the device in use or operation in addition to the orientation shown in the figures. The device may be otherwise oriented (rotated 90 degrees or at other orientations) and the spatially relative descriptors used herein may likewise be interpreted accordingly.

[0017] A system and method for visualizing data from a cellular network is disclosed. In one embodiment, a graphical user interface (GUI) is presented to allow a user to make selections regarding parameters and network elements of interest and to view the parameters. For example, the GUI presents a network topology, which is a representation of a hierarchy of components within the cellular network, for at least a portion of the cellular network. In one embodiment, the network topology is hierarchical such that a user can make a network selection within the hierarchy to select a network element within the cellular network. Parameter configuration data is generated based on the network selection. In one embodiment, the parameter configuration data includes data for locating and obtaining parameters associated with the network element. A parameter audit is performed based on the parameter configuration data, and a report of the audit is generated. The report is sent to a user device, and a visual representation of the report is presented using the GUI. In one embodiment, a user can take action regarding the parameters and network elements based on the report. For example, a user can select to roll back the value of a parameter to a previous historical value if a network outage occurs after the parameter value was changed.

[0018] FIG. 1A is a block diagram of a computer system 100 according to one embodiment.

[0019] The computer system 100 includes a cellular network monitoring device 102, at least one database 104, and a cellular network 106. The cellular network monitoring device 102 and the cellular network 106 are connected to each other through an Internet Protocol (IP) network 108. In one embodiment, the IP network 108 includes a wide area network (WAN) (i.e., the Internet), a local area network (LAN), a wide area local area network (WLAN), etc. In one embodiment, the cellular network 106 includes a wireless WAN (WWAN).

[0020] The cellular network 106 includes a Radio Access Network (RAN) 160. The RAN 160 is the wireless element of the cellular network 106. The RAN 160 includes network elements 162, such as base stations, which include one or more radio transceivers. A base station covers a land area called a cell. User equipment, such as a mobile phone, smartphone, or laptop, connects to each of the base stations that cover the cell. The RAN 160 connects to the Core 170 via a backhaul link.

[0021] The Core 170 is the central part of the entire cellular network 106. The Core 170 allows mobile subscribers to access services (e.g., international calling, text messaging, local cellular calling). In one embodiment, the Core 170 is responsible for important functions such as maintaining subscriber profile information, subscriber location, service authentication, and switching functions required for voice and data sessions. The Core 170 includes network elements 172. In one embodiment, the network elements 172 include a Mobility Management Entity (MME), a Serving Gateway 166, a Multimedia Broadcast Multicast Service (MBMS) Gateway, a Broadcast Multicast Service Center (BM-SC), and a Packet Data Network (PDN) Gateway. In one embodiment, the MME is in communication with a Home Subscriber Server (HSS). The MME is a control node that handles signaling between user equipment and the Core 170. Generally, the MME provides bearer and connection management. In one embodiment, Internet Protocol (IP) packets are forwarded through the Serving Gateway 166, which is itself connected to the IP network 108.

[0022] Transport 180 refers to the transport network connecting Core 170 and RAN 160 of cellular network 106. Transport 180 includes network elements 182, such as backhaul links, connectors, relays, voice over IP devices, etc. In one embodiment, Transport 180 includes fronthaul, which connects macro cells to small cells, radio units, digital units, etc. In one embodiment, RAN 160, Core 170, and Transport 180 are referred to as different domains of cellular network 106.

[0023] The cellular network monitoring device 102 (in one embodiment, the server 102) is a computing device that includes at least one processor 126 and a non-transitory computer-readable medium 128. The non-transitory computer-readable medium 128 stores computer-executable instructions 124. In one embodiment, the non-transitory computer-readable medium 128 includes random access memory (RAM), read-only memory (ROM), electrically erasable programmable ROM (EEPROM), optical disk storage, magnetic disk storage, other magnetic storage devices, combinations of the aforementioned types of computer-readable media, or any other medium that can be used to store computer-executable code in the form of instructions or data structures that can be accessed by a computing device. When the processor 126 executes the computer-executable instructions 124, the processor 126 executes the cellular network monitoring software 127.

[0024] The cellular network monitoring software 127 is configured to visualize the data 110 in the cellular network 106. The cellular network monitoring software 127 is configured to capture values ​​of parameters from the cellular network 106 and store the parameters as data 110 in the non-transitory computer-readable medium 116 in the database 104. The parameters are captured from NEs 162, 172, 182 in different domains of the cellular network 106. The cellular network monitoring software 127 is configured to generate a graphical user interface (GUI) that allows a user to visualize the data 110. Thus, rather than forcing a user to search through the cellular network 106 based on personal knowledge of the cellular network 106, which can be a time-consuming task, the cellular network monitoring software 127 provides the ability to easily monitor parameters from NEs 162, 172, 182 in different domains of the cellular network 106.

[0025] The cellular network monitoring software 127 is configured to present a network topology using a GUI. The network topology is a visual representation of at least a portion of the cellular network 106. In one embodiment, the network topology is a visual representation that generalizes characteristics of the cellular network such that a user can make selections within the network topology to select NEs 162, 172, 182 that match the selected characteristics.

[0026] The cellular network monitoring software 127 is configured to receive a network topology selection from a user device relating to the network topology. In one embodiment, the network topology includes a selection of a domain, a vendor, a service provider, and network characteristics such as technology, geographic region, and device type. In one embodiment, the network topology is hierarchical. For example, the domain of the cellular network 106 is at the top of the hierarchy in one embodiment. Once one of the domains is selected, the technology type (4G, 5G, LTE, etc.) of the cellular network 106 becomes selectable. In one embodiment, other hierarchical levels are provided below the technology type.

[0027] The cellular network monitoring software 127 is configured to generate parameter configuration data 129 related to network topology selection. In one embodiment, the parameter configuration data 129 includes the location of the parameter to be captured and / or obtained, the time slot for capturing and / or obtaining the parameter, the NEs 162, 172, 182 associated with the parameter, routing data for locating the parameter, etc. In one embodiment, the captured value of the parameter is stored as data 110 because the value is a historical value. In one embodiment, the value of the parameter is captured in real time directly from the NEs 162, 172, 182. Thus, in situations where the capture is performed in real time, the parameter configuration data 129 includes routing data for capturing the value of the parameter directly from the NEs 162, 172, 182.

[0028] The cellular network monitoring software 127 is configured to perform an audit on the NEs 162, 172, 182 of the cellular network 106. In one embodiment, the cellular network monitoring software 127 sends one or more requests 150 for parameters according to the parameter configuration data 129 to perform the audit. In one embodiment, the requests 150 are sent by the cellular network monitoring software 127 to the database 104 to obtain historical values ​​of the parameters from the data 110. In one embodiment, the requests 150 are sent directly by the cellular network monitoring software 127 to specific NEs 162, 172, 182 to obtain values ​​of the parameters in real time. In one embodiment, the parameter configuration data 129 defines the NEs 162, 172, 182 in the cellular network 106 that will receive the parameters. The requests 150 for the parameters are sent such that the parameters in the visual representation are captured from the NEs 162, 172, 182 as defined in the parameter configuration data 129.

[0029] The cellular network monitoring software 127 is configured to generate and transmit a report 112 of the audit to the user device. The report 112 includes the values ​​of the parameters captured according to the parameter configuration data 129. Once the report 112 is captured by the user device, the cellular network monitoring software 127 is configured to present a visual representation of the report using a GUI. In one embodiment, the GUI presents a panel having a visual representation of the parameters along with details about the NEs 162, 172, 182 for which the parameter values ​​were captured. In one embodiment, the audit is performed periodically in real time or scheduled for a future time slot. In one embodiment, several other operations are provided via the GUI, including options related to changing parameter values ​​for specific NEs 162, 172, 182, configuration change history for NEs 162, 172, 182, configuration audit information for NEs 162, 172, 182, layered views, and rollback to base configuration.

[0030] FIG. 1B is a block diagram of a user device 190, according to one embodiment.

[0031] User device 190 is configured to communicate with cellular network monitoring software 127 over IP network 108. User device 190 includes one or more processors 196 and computer-executable instructions 194 stored on non-transitory computer-readable medium 195. In an embodiment, non-transitory computer-readable medium 195 includes random access memory (RAM), read-only memory (ROM), electrically erasable programmable ROM (EEPROM), optical disk storage, magnetic disk storage, other magnetic storage devices, combinations of the aforementioned types of computer-readable media, or any other medium that can be used to store computer-executable code in the form of instructions or data structures that can be accessed by a computing device. Examples of user device 190 include mobile phones, smartphones, desktops, session initiation protocol (SIP) phones, laptops, smart watches, personal digital assistants (PDAs), satellite radios, global positioning systems, multimedia devices, video devices, game consoles, tablets, smart devices, and wearable communication devices.

[0032] When the computer-executable instructions are executed by the processor 196, the processor 196 is configured to implement a GUI 198. The GUI 198 is configured to present a network topology using the GUI 198. The network topology represents at least a portion of the cellular network 106. In one embodiment, a user 192 inputs user input via the GUI 198 to make a selection related to the network topology. In one embodiment, the user 192, through the selection, selects the network elements 162, 172, 182 for which the user 192 wants to audit parameters. Furthermore, in one embodiment, the GUI 198 presents parameter filtering options related to different characteristics of the parameters using the GUI 198. The user 192 inputs user input via the GUI 198, the user input being a selection of a parameter filtering option. Based on the selection related to the network topology and / or the selection of the parameter filtering option, parameter configuration data is generated such that parameters to be searched are provided according to the network topology selection and / or according to the parameter filtering option and from the network elements defined according to the network topology selection.

[0033] Once the audit is performed, a report 112 of the audit is sent to the user device 190. In one embodiment, the report 112 includes the parameter values ​​along with other relevant data. In one embodiment, the parameter values ​​are obtained from selected network elements 162, 172, 182. In one embodiment, the parameter values ​​are obtained from data 110 in database 104. In one embodiment, the parameter values ​​are obtained periodically according to a defined time period. For example, the defined time period may be daily, weekly, monthly, or any other type of defined time period. In one embodiment, the audit is performed at a future time such that the report includes parameter values ​​from the future time. In one embodiment, the parameter values ​​in the report 122 were captured in real time.

[0034] The GUI 198 presents a visual representation of the report. In one embodiment, the GUI 198 allows the user 192 to provide user input related to actions related to parameters in the report. For example, in one embodiment, the report 112 includes status information related to violations associated with the parameters. For example, the parameter value indicates a problem with the cellular network 106. In one embodiment, the user 192 is allowed to change the parameter value via the GUI 198 in an attempt to correct the violation. In one embodiment, the GUI 198 presents selectable options regarding the execution of a script or task that is to be executed on the cellular network 106.

[0035] It should be noted that in one embodiment, changes to parameter values ​​may result in problems (e.g., outages) in the cellular network 106. Therefore, the database 104 stores historical values ​​of parameters as data 110. In one embodiment, the GUI 198 presents basic configuration options using the GUI 198. In response to receiving a selection of a basic configuration option via the GUI 198, the cellular network monitoring software 127 resets selected parameters associated with one or more network elements 162, 172, 182 in the cellular network 106 to their historical values.

[0036] FIG. 2 is a block diagram of cellular network monitoring software 200 and cellular network 106 according to one embodiment.

[0037] Cellular network monitoring software 200 corresponds to cellular network monitoring software 127 of FIG. 1A, according to one embodiment.

[0038] The cellular network monitoring software 200 includes an orchestrator 202, a controller 204, a configuration manager 206, and an OBF 208. The orchestrator 202 is configured to automatically configure the monitoring agents to communicate with the cellular network 106. More specifically, the orchestrator 202 is configured to generate pushes to the configuration manager 206 to generate parameter configuration data 129 (see FIG. 1A). In one embodiment, the orchestrator 202 is configured to trigger obtaining dynamic values ​​of parameters and providing appropriate data to the configuration manager 206. The configuration manager 206 sends and obtains values ​​of parameters from the cellular network 106 or the database 104 (see FIG. 1A).

[0039] The controller 204 is configured to generate routing data for the parameter configuration data 129. The configuration manager 206 is connected to the cellular network 106 for sending requests based on the parameter configuration data 129 to the RAN 160, the core 170, and the transport 180. The OBF 208 is configured to generate a log and visualization of the parameters, and the configuration manager 206 is configured to check the log and obtain the visualization.

[0040] In one embodiment, the configuration manager 206 is divided into two categories: CMaaS and SDNC. In one embodiment, CMaaS and SDNC are loosely operatively associated. In one embodiment, CMaaS includes Netconf GW, CM Micro FE, backup and restore, Livy, My SQL, a gRPC plugin, and SOAP. CM Micro FE provides an entry point to the configuration manager 206 for the NEs 162, 172, and 182 configured by the configuration manager 206. CM Micro FE is a micro front-end service of CMaaS that displays a GUI and other details. Backup and restore is configured to maintain backup data. My SQL is relational with the database 104 and has persistence capabilities. The RPC plugin connects based on the gRPC protocol. SOAP exchanges information with 4G EMS network devices according to the gRPC protocol.

[0041] Regarding SDNC, SDNC includes NBI, Transformer, CLI Plugin, Netconf SSH, ASIC Plugin, My SQL, BGP-LS Topology, BGP-LS Demon, Graph DB, and eSON. SDNC-NBI is the SDNC northbound service that exposes APIs consumed by other RCP applications such as CMAAS, database inventory, and orchestrator 202. Transformer is a microservice responsible for generating device-specific configuration payloads to be provisioned to user devices 190. Transformer also has device response parsing capabilities. CLI Plugin is a microservice that provides CLI access to network elements 162, 172, and 182 via SSH. This is used in scenarios where the network elements 162, 172, and 182 do not support standard API access such as Netconf, Rest, or Restconf for configuration provisioning. Netconf SSH is a microservice that provides standard Netconf API access to Netconf-supported devices. APIC Plugin supports pushing configuration to Cisco ACI via the Rest interface. MySQL® provides persistence capabilities for SDNC. BGP-LS Topology is a service that provides the ability to build BGP-LS topologies, which are used while generating paths in transport slicing. PCE is a path computation engine that generates paths using given slicing parameters. BGP-LS Demon registers BGP-LS Demons as BGP peers in the network and collects peer information across the network. Graph DB is used to store the BGP-LS topology built by the BGP-LS Topology Service. eSON is a self-observing network through gRPC plugins, smart functions, auto-learning, and automatic functions.

[0042] FIG. 3 is an example of a GUI 300 according to one embodiment.

[0043] The GUI 300 is implemented by the cellular network monitoring software 127 of Figure 1A and the user device 190 of Figure 1B. The GUI 300 is an example of the GUI 198 of Figure 1.

[0044] GUI 300 presents panel 302 with network topology 304. In Figure 3, panel 302 with network topology 304 is the left panel. GUI 300 also presents panel 306. Panel 306 presents a report of parameters and identification information associated with a selection from network topology 304.

[0045] Network topology 304 includes domain selections 308A, 308B, and 308C. Domain selection 308A allows a user to select and view parameters and other information for NEs 162 in RAN 160 (see FIGS. 1A and 2). Domain selection 308B allows a user to select and view parameters and other information for NEs 172 in Core 170 (see FIGS. 1A and 2). Domain selection 308C allows a user to select and view parameters and other information for NEs 182 in Transport 180 (see FIGS. 1A and 2).

[0046] In Figure 3, domain selection 308A for RAN 160 is selected. Accordingly, service provider selections 310A, 310B, 310C are presented using GUI 300. Service provider selection 310A is to view NEs 162 (i.e., RAN NEs) associated with service provider 1. Service provider selection 310B is to view NEs 162 associated with service provider 2. Service provider selection 310C is to view NEs 162 associated with service provider 3. In Figure 3, service provider selection 310A is selected. Accordingly, parameters and other information associated with NEs 162 within RAN 160 and served by service provider 2 are shown in panel 306.

[0047] Under service provider selection 310A, network topology 304 includes technology type selections 312A and 312B. Technology type selection 312A is a selection of 4G technology. Technology type selection 312B is a selection of 5G technology. In this case, neither technology type selection 312A nor technology type selection 312B is selected. Thus, parameters and other information related to NE 162, which is within RAN 160, served by service provider 2, and is either 4G technology or 5G technology, are shown in panel 306. In this manner, network topology 304 is hierarchical.

[0048] Panel 306 is a visual representation of report 112. Panel 306 includes parameters and other data related to the network topology selection described above. The left side of panel 306 (shown in FIG. 3 ) displays data such as “Status,” “Domain,” “NE Name,” “Configuration Conflict,” “Golden Conflict,” and “MS Name.” The “Status” field indicates whether the parameter is being captured in real time (i.e., on air), is a historical parameter value (including the date and time of capture), or is to be captured in a future time slot. The “Domain” field indicates the domain of the NE from which the parameter is being captured. The “NE Name” field indicates the name of the NE 162 from which the parameter is being captured. The “Configuration Conflict” field indicates whether the parameter has a value that indicates a configuration conflict. Thus, if a parameter value exists for a parameter of an NE 162 with a configuration conflict, the “Configuration Conflict” field has a value of “Violation.” If a parameter value does not exist for a parameter of an NE 162 with a configuration conflict, the “Configuration Conflict” field has a value of “In Sync.” The “Golden Conflict” field indicates whether the parameter has an out-of-range value for a critical system configuration. Parameters considered "golden parameters" are particularly important to the cellular network 106 because violations can result in network outages or degraded network performance. If there is a parameter value for a parameter in the NE 162 that has a conflict with the golden parameter, the "Golden Conflict" field has a value of "Violation." If there is no parameter value for a parameter in the NE 162 that has a conflict with the golden parameter, the "Golden Conflict" field has a value of "Synchronized." The "Golden Conflict" field indicates whether the parameter has an out-of-range value for a critical system configuration. The "MS Name" field indicates the name of the element management system (MS) that manages the NE 162.

[0049] FIG. 4 is a selection screen 400 for an MS management system from panel 306, according to one embodiment.

[0050] As shown in Figure 4, configuration details selection 402 is indicated by parameter information for the MS management system. When configuration details selection 402 is selected, parameter configuration data is generated in association with the network topology selection described above with respect to Figure 3 and configuration details selection 402 in Figure 4. Selection screen 400 includes fields related to NE 162 named UHN10SK100400163. NE 162 named UHN10SK100400163 is within the RAN, is served by service provider 1, and implements either 4G or 5G technology.

[0051] FIG. 5 is a table containing parameter configuration data 500 generated in response to the network topology selection described above with respect to FIG. 3 and the configuration details selection 402 of FIG. 4, according to one embodiment.

[0052] Parameter configuration data 500 is an example of parameter configuration data 129 shown in FIG. 1A. Thus, because of the network topology selection described above with respect to FIG. 3, parameter configuration data 500 includes a field named "Domain," a field named "Service Provider," and a field named "Technology Type." In FIG. 5, the "Domain" field has a value of RAN, the "Service Provider" field has a value of Service Provider 1, and "Technology Type" has a value of 4G, 5G. Because of the configuration details selection 402 described above with respect to FIG. 4, parameter configuration data 500 includes a field for "NE Name" and a field for "Parameter Path." In FIG. 5, the "NE Name" field has a value of UHN10SK100400163, and the "Parameter Path" field has a value of / bulkCMConfigData. In FIG. 5, the "Parameter Path" field indicates where the parameter value can be captured or obtained, either on cellular network 106 or in database 104.

[0053] Parameter configuration data 500 has a "time slot" field. The "time slot" field indicates when the parameter will be captured. In FIG. 5, parameter configuration data 500 indicates a value "on air," meaning that the parameter value of the parameter will be captured in real time. In one embodiment, the "time slot" field indicates a past time slot for obtaining a historical value of the parameter from data 110. In one embodiment, the "time slot" field indicates a future time slot for receiving the parameter. In one embodiment, the "time slot" field indicates that the parameter will be captured periodically based on a defined time period (e.g., daily, weekly, monthly). Audits are performed based on parameter configuration data 500. Request 150 (see FIG. 1A) is generated by cellular network monitoring software 127 based on parameter configuration data 500. In this manner, parameters are obtained by GUI 300 and presented in a visual representation as defined in parameter configuration data 129.

[0054] FIG. 6 is a panel 600 that uses the GUI 300, according to one embodiment.

[0055] The panel includes a visual representation of a report resulting from the audit. The report is an example of report 112 of FIG. 1A. The report includes parameters for an NE named UHN10SK100400163 as a result of parameter configuration data 500 of FIG. 5. As shown in FIG. 6, the visual representation in panel 600 includes fields named "NE Name," "eNodeB ID," "Parameter Type," "Equipment Type," "Category," "Parameter," "X-Path," and "Current Value." The field named "NE Name" is the name of the NE 162 from which the parameters are captured. The field named "eNodeB ID" identifies the name of the cell from which the parameters are captured. The field named "Parameter Type" indicates the type of parameter (including whether the parameter is a golden parameter). "Equipment Type" identifies the equipment type of the NE 162 from which the parameters were captured. The field named "Category" identifies the category of the captured parameter. The field named "Parameter" indicates the name of the captured parameter. The field named "X-Path" identifies the routing data for capturing the parameter. The field named "Current Value" indicates the current value of the parameter.

[0056] Note that in other embodiments, parameter configuration data 500 includes past time slots instead of requesting live data. For example, data 110 of FIG. 1A stores historical values ​​of a subset of parameters associated with one or more NEs 162, 172, 182 in cellular network 106. Thus, a request 150 is sent to database 104 for previously captured values ​​in data 110 of parameters for an NE named UHN10SK100400163. Request 150 is sent to database 104 to obtain parameter values ​​captured in past time slots.

[0057] Note that in another embodiment, parameter configuration data 500 includes a time period. Thus, a request 150 is sent to database 104 for captured values ​​in data 110 of parameters of an NE named UHN10SK100400163 according to the time period. According to one embodiment, the resulting report is sent to user device 190 according to the time period. In one embodiment, GUI 300 presents a menu indicating that the resulting report is ready to be viewed. If the user selects to view, a visual representation of the report is provided using GUI 300.

[0058] In one embodiment, GUI 300 is used to present a basic configuration option, which is an option that resets parameters to their previous values. Thus, in one embodiment, a subset of parameters associated with an NE named UHN10SK100400163 in cellular network 106 are reset to their historical values ​​in response to receiving a selection of the basic configuration option. Instead of a field named "Current Value," panel 600 would include a field named "Value" that contains the historical values ​​of the parameters.

[0059] Note that in other embodiments, parameter configuration data 500 requests live data or includes future time slots instead of requesting live data. In one embodiment, request 150 is sent to obtain parameter values ​​captured during those future time slots. Thus, parameters are sent to capture the parameters in the visual representation during future time slots defined in parameter configuration data 500. Instead of a field named "Current Value," panel 600 would include a field named "Value" that contains the value of the parameter captured during the future time slot.

[0060] FIG. 4 also shows a configuration history selection 404 .

[0061] FIG. 7 is a panel 700 using GUI 300 to present a configuration history of a parameter, according to one embodiment.

[0062] Panel 700 is displayed in response to selecting configuration history selection 404 in FIG. 4. Panel 700 includes fields for "Device Type," "Category," "Parameter," "X Path," "Previous Date," "Previous Value," "Update Date," and "Update Value." The "Device Type" field describes the type of device associated with the parameter. The "Category" field describes the category of the parameter. The "Parameter" field identifies the parameter. The "X Path" field identifies the routing data for the parameter. The "Previous Date" field describes the date the parameter was captured before the current entry. The "Previous Date" field describes the value of the parameter before the current entry. The "Update Value" field is the value of the parameter for the current entry. The "Update Date" field is the date the parameter's value was captured for the current entry.

[0063] Thus, panel 700 shows historical values ​​of parameters for one or more NEs 162, 172, 182 that are stored as part of data 110 in database 104. Panel 700 lists historical values ​​of parameters for different dates. In one embodiment, the GUI presents basic configuration option 406 (see FIG. 4). In response to selecting basic configuration option 406, parameters associated with one or more NEs 162, 172, 182 in cellular network 106 become historical values. In one embodiment, in response to selecting basic configuration option 406, various parameters are reset to their historical values.

[0064] FIG. 8 is a panel 800 with parameter filtering options for different characteristics of parameters using GUI 300, according to one embodiment.

[0065] A user 192 (see FIG. 1B) inputs a selection of a parameter filtering option into panel 800. According to one embodiment, a visual representation of the parameter selected as a result of the selection of the filtering parameter option is presented in panel 802.

[0066] The panel 800 includes parameter filtering options for "Parameter Type," "Device Type," "Category," "Parameter," "X Path," and "Current Value." The "Parameter Type" field includes filtering options for different parameter types. The "Device Type" field includes filtering options for parameters associated with different device types. The "Category" field includes filtering options for parameters associated with different categories of parameters. The "Parameter" field includes filtering options related to the parameter. The "X Path" field includes filtering options for parameters having values ​​originating from different locations in the cellular network 106. The "Current Value" field includes filtering options for the value range and / or value type of the parameter's value.

[0067] FIG. 9 is a flowchart 900 of a method for visualizing data in a cellular network, according to one embodiment.

[0068] Flowchart 900 is implemented by computer system 100 of Figures 1A-1B or cellular network monitoring software 200 of Figure 1, according to one embodiment. Flowchart 900 includes blocks 902-912. The flow begins at block 902.

[0069] At block 902, a network topology is presented in a graphical user interface (GUI), where the network topology is a representation of at least a portion of a cellular network. An example of a GUI is GUI 300 of Figures 3, 4, 6, 7, and 8. An example of a network topology is shown in panel 302 of Figure 3. An example of a cellular network is cellular network 106 of Figures 1 and 2. Flow then proceeds to block 904.

[0070] At block 904, a network topology selection associated with a network topology is received. Examples of network topology selections are network topology selections made for domains 308A-308C, service providers 310A-310C, and technologies 312A, 312B. Flow then proceeds to block 906.

[0071] Parameter configuration data related to the network topology selection is generated in block 906. Examples of parameter configuration data are parameter configuration data 129 of Figure 1 and parameter configuration data 500 of Figure 5. Flow then proceeds to block 908.

[0072] At block 908, a parameter audit is performed on the network elements of the cellular network according to the parameter configuration data. Thereafter, flow proceeds to block 910.

[0073] A report of the audit is sent to the user device at block 910. An example of the report is shown as report 112 in Figure 1. Flow then proceeds to block 912.

[0074] A visual representation of the report is presented using a GUI at block 912. An example of a visual representation of a report is panel 600 of FIG.

[0075] FIG. 10 is a flowchart 1000 relating to a method for generating parameter configuration data related to network topology selection, according to one embodiment.

[0076] Flowchart 1000 is an example of a portion of block 906 of Figure 9, according to one embodiment. Flowchart 1000 includes blocks 1002 through 1006. The flow begins at block 1002.

[0077] At block 1002, parameter filtering options for different characteristics of the parameter are presented using a GUI. The parameter filtering options are shown in panel 800 of Figure 8. The parameter filtering options in panel 800 include parameter filtering options for "Parameter Type," "Device Type," "Category," "Parameter," "XPath," and "Current Value." Flow then proceeds to block 1004.

[0078] A selection of a parameter filtering option is received at block 1004. Flow then proceeds to block 1006.

[0079] At block 1006, parameter configuration data is generated such that the parameters to be searched are provided from the network elements defined according to the parameter filtering options and according to the network topology selection.

[0080] FIG. 11 is a flowchart 1100 of a method for resetting parameters to historical values, according to one embodiment.

[0081] In one embodiment, flowchart 1100 takes place after block 912 of Figure 9. Flowchart 1100 includes blocks 1102 through 1106. The flow begins at block 1102.

[0082] At block 1102, historical values ​​are stored for a subset of parameters associated with one or more network elements in the cellular network. An example of historical values ​​for the subset of parameters is shown in panel 700 of Figure 7. Flow then proceeds to block 1104.

[0083] At block 1104, basic configuration options are presented using a GUI, an example of which is shown in Figure 4 as basic configuration options 406. Flow then proceeds to block 1106.

[0084] At block 1106, a subset of parameters associated with one or more network elements in the cellular network are reset to historical values ​​in response to receiving a selection of the basic configuration option.

[0085] In one embodiment, a method for visualizing data in a cellular network includes presenting a network topology, which is a representation of at least a portion of the cellular network, using a graphical user interface (GUI), receiving a network topology selection related to the network topology, generating parameter configuration data related to the network topology selection, performing an audit of parameters related to network elements of the cellular network according to the parameter configuration data, transmitting a report of the audit to a user device, and presenting a visual representation of the report using the GUI. In one embodiment, the parameter configuration data indicates that the audit should be performed at a future time, and the audit of the parameters is performed during the future time. In one embodiment, the parameter configuration data indicates that the audit should be performed in real time, and the audit of the parameters is performed in real time. In one embodiment, the parameter configuration data indicates that the audit should be performed periodically based on a defined time period, and the audit of the parameters is performed periodically based on the defined time period. In an embodiment, the method further includes storing historical values ​​of a subset of parameters associated with one or more network elements in the cellular network, presenting a basic configuration option using a GUI, and resetting the subset of parameters associated with the one or more network elements in the cellular network to the historical values ​​in response to receiving a selection of the basic configuration option. In an embodiment, presenting the network topology using the GUI includes presenting a domain level of the network topology enabling selection of different domains within the cellular network. In an embodiment, presenting the network topology using the GUI includes presenting a cellular network technology level of the network topology enabling selection of different cellular network technologies within the cellular network.In one embodiment, generating parameter configuration data associated with the network topology selection includes presenting parameter filtering options related to different characteristics of the parameters using a GUI, receiving a selection of the parameter filtering options, and generating the parameter configuration data such that parameters to be retrieved from network elements defined in accordance with the parameter filtering options and in accordance with the network topology selection are provided.

[0086] In one embodiment, a computing device for visualizing data in a cellular network includes a non-transitory computer-readable medium storing computer-executable instructions; and at least one processor, the at least one processor being configured, when the at least one processor executes the computer-executable instructions, to: present a network topology, which is a representation of at least a portion of the cellular network, using a graphical user interface (GUI); receive a network topology selection related to the network topology; generate parameter configuration data related to the network topology selection; perform an audit of parameters related to network elements of the cellular network according to the parameter configuration data; send a report of the audit to a user device; and present a visual representation of the report using the GUI. In one embodiment, the parameter configuration data indicates that the audit should be performed at a future time, and the audit of the parameters is performed during the future time. In one embodiment, the parameter configuration data indicates that the audit should be performed in real time, and the audit of the parameters is performed in real time. In one embodiment, the parameter configuration data indicates that the audit should be performed periodically based on a defined time period, and the audit of the parameters is performed periodically based on the defined time period. In an embodiment, the processor is further configured to store historical values ​​of a subset of parameters associated with one or more network elements in the cellular network, present a basic configuration option using the GUI, and, in response to receiving a selection of the basic configuration option, reset the subset of parameters associated with the one or more network elements in the cellular network to the historical values. In an embodiment, the at least one processor is configured to present the network topology using the GUI by presenting a domain level of the network topology that enables selection of different domains in the cellular network.In an embodiment, the at least one processor is configured to present a network topology using a GUI by presenting a cellular network technology level of the network topology that enables selection of different cellular network technologies within the cellular network. In an embodiment, the at least one processor is configured to generate parameter configuration data associated with the network topology selection by presenting parameter filtering options related to different characteristics of the parameters using the GUI, receiving a selection of the parameter filtering option, and generating parameter configuration data such that parameters to be retrieved are provided from network elements defined in accordance with the parameter filtering option and in accordance with the network topology selection.

[0087] In one embodiment, a non-transitory computer-readable medium storing computer-executable instructions, which, when executed by at least one processor, are configured to: present a network topology, the network topology being a representation of at least a portion of a cellular network, using a graphical user interface (GUI); receive a network topology selection related to the network topology; generate parameter configuration data related to the network topology selection; perform an audit of parameters associated with network elements of the cellular network according to the parameter configuration data; transmit a report of the audit to a user device; and present a visual representation of the report using the GUI. In one embodiment, the parameter configuration data indicates that the audit should be performed at a future time, and the audit of the parameters is performed during the future time. In one embodiment, the at least one processor is further configured to: store historical values ​​of a subset of parameters associated with one or more network elements in the cellular network; present a basic configuration option using the GUI; and, in response to receiving a selection of the basic configuration option, reset the subset of parameters associated with the one or more network elements in the cellular network to the historical values. In an embodiment, the at least one processor is configured to generate parameter configuration data associated with the network topology selection by presenting, using a GUI, parameter filtering options related to different characteristics of the parameters, receiving a selection of the parameter filtering options, and generating the parameter configuration data such that parameters to be retrieved are provided from network elements defined in accordance with the parameter filtering options and in accordance with the network topology selection.

[0088] The foregoing outlines features of certain embodiments so that those skilled in the art may better understand aspects of the present disclosure. Those skilled in the art should appreciate that they may readily use this disclosure as a basis for designing or modifying other processes and structures to carry out the same purposes and / or achieve the same advantages of the embodiments presented herein. Those skilled in the art should also appreciate that such equivalent constructions do not depart from the spirit and scope of the present disclosure, and that various changes, substitutions, and alterations may be made herein without departing from the spirit and scope of the present disclosure.

[0089] Aspects of the present disclosure are best understood from the following detailed description when read in conjunction with the accompanying drawings. It should be noted that, according to standard industry practice, various features have not been drawn to scale. In fact, the dimensions of various features may be arbitrarily increased or decreased for clarity of illustration.

Claims

1. 1. A method for providing data visualization in a cellular network, comprising: presenting a representation of at least a portion of a cellular network, the domain level in a network topology including one or more selectable domains, using a graphical user interface (GUI) of the user device; receiving, by a processor, a network topology selection on the GUI of the user device that is associated with the domain level in the network topology; generating, by the processor, parameter configuration data associated with the domain level of the network topology selection; generating, by the processor, a report including a violation usable to indicate that one or more parameters associated with one or more network elements of the cellular network associated with the parameter configuration data are out of range; transmitting, by the processor, the report to the user device; presenting a visual representation of the report on the user device using the GUI; and Including, generating parameter configuration data associated with the domain level of the network topology selection; presenting parameter filtering options for different characteristics of the parameters using the GUI; receiving a selection of the parameter filtering option; generating the parameter configuration data to provide the parameters to be retrieved from the one or more network elements defined according to the selected parameter filtering option and according to the network topology selection; A method comprising:

2. the parameter configuration data indicates that the report should be generated at a future time; the report is generated during the future time; The method of claim 1.

3. the parameter configuration data indicates that the report should be generated in real time; The report is generated in real time. The method of claim 1.

4. the parameter configuration data indicates that the report should be generated periodically based on a defined time period; the report is generated periodically based on the defined time period; The method of claim 1.

5. storing historical values ​​of the one or more parameters associated with at least one network element within the cellular network; presenting basic configuration options using said GUI; resetting the parameters associated with the at least one network element in the cellular network to the historical values ​​in response to receiving a selection of the basic configuration option; The method of claim 1 further comprising:

6. presenting the domain level in the network topology using the GUI, presenting domain levels in the network topology that allow selection of different domains within the cellular network; The method of claim 1 , comprising:

7. presenting the domain level in the network topology using the GUI, presenting the domain-level cellular network technology types in the network topology to enable selection of different cellular network technologies within the cellular network; The method of claim 1 , comprising:

8. 1. A computer device for visualizing data in a cellular network, comprising: using a graphical user interface (GUI) of the user device to cause the user device to present a representation of at least a portion of the cellular network, the domain level in the network topology including one or more selectable domains; receiving a network topology selection on the GUI of the user device, the selection relating to the domain level in the network topology; generating, by a processor, parameter configuration data associated with the domain level of the network topology selection; generating, by the processor, a report including a violation usable to indicate that one or more parameters associated with one or more network elements of the cellular network associated with the parameter configuration data are out of range; transmitting, by the processor, the report to the user device; causing the user device to present a visual representation of the report on the user device using the GUI; It is structured as follows: generating parameter configuration data associated with the domain level of the network topology selection; presenting parameter filtering options for different characteristics of the parameters using the GUI; receiving a selection of the parameter filtering option; generating the parameter configuration data to provide the parameters to be retrieved from the one or more network elements defined according to the selected parameter filtering option and according to the network topology selection; a computing device,

9. the parameter configuration data indicates that the report should be generated at a future time; the report is generated during the future time; The computing device of claim 8.

10. the parameter configuration data indicates that the report should be generated in real time; The report is generated in real time. The computing device of claim 8.

11. the parameter configuration data indicates that the report should be generated periodically based on a defined time period; the report is generated periodically based on the defined time period; The computing device of claim 8.

12. the processor: storing historical values ​​of the one or more parameters associated with at least one network element within the cellular network; causing the user device to present basic configuration options using the GUI; resetting the parameters associated with the at least one network element in the cellular network to the historical values ​​in response to receiving a selection of the basic configuration option; The computing device of claim 8 , further configured to:

13. the processor: presenting domain levels in the network topology that allow selection of different domains within the cellular network; 9. The computing device of claim 8, wherein the computing device is configured to use the GUI to present the domain level in the network topology by:

14. the processor: presenting the domain-level cellular network technology types in the network topology to enable selection of different cellular network technologies within the cellular network; 9. The computing device of claim 8, wherein the computing device is configured to use the GUI to present the domain level in the network topology by:

15. A computer comprising: presenting a representation of at least a portion of a cellular network, the domain level in a network topology including one or more selectable domains, using a graphical user interface (GUI) of the user device; receiving a network topology selection on the GUI of the user device associated with the domain level in the network topology; generating parameter configuration data associated with the domain level of the network topology selection; generating a report including violations usable to indicate that one or more parameters associated with one or more network elements of the cellular network associated with the parameter configuration data are out of range; and transmitting the report to a user device; presenting a visual representation of the report on the user device using the GUI; and Let them do this, generating parameter configuration data associated with the domain level of the network topology selection; presenting parameter filtering options for different characteristics of the parameters using the GUI; receiving a selection of the parameter filtering option; generating the parameter configuration data to provide the parameters to be retrieved from the one or more network elements defined according to the selected parameter filtering option and according to the network topology selection; Including, Computer program.

16. the parameter configuration data indicates that the report should be generated at a future time; the report is generated during the future time; 16. A computer program according to claim 15.

17. The computer, storing historical values ​​of the one or more parameters associated with at least one network element within the cellular network; causing the user device to present basic configuration options using the GUI; resetting the parameters associated with the at least one network element in the cellular network to the historical values ​​in response to receiving a selection of the basic configuration option; 16. The computer program of claim 15, further comprising:

Images