User-defined network congestion monitoring system

Abstract

The method includes causing a processor to output a graphical user interface (GUI) on a display. The GUI includes a first user input field identifying a target key performance indicator (KPI) associated with the network. A second user input field identifies a KPI peak usage frequency. A third user input field identifies a peak usage relationship. The method also includes creating a first monitoring profile based on a target KPI of the KPI peak usage frequency for the peak usage relationship. Storing the first monitoring profile. Monitoring a target KPI of the KPI peak usage frequency based on the first monitoring profile. Collecting target KPI data over a period defined by the KPI peak usage frequency. Determining peak usage in a period defined by the KPI peak usage frequency based on the collected target KPI data. Periodically reporting the peak usage data based on the first monitoring profile.

Description

[Technical Field]

[0001] Priority Claims and Cross-References This application claims priority to U.S. Non-Provisional Application No. 17 / 564,046, filed December 28, 2021, which is incorporated herein by reference in its entirety. [Background technology]

[0002] Network service providers (e.g., wireless, cellular, fiber, etc.) are continually challenged to deliver value and convenience to consumers by, for example, providing network services that are dependable, flexibly architected, scalable, diverse, and economically operable. To deliver such network services, service providers often track key performance indicators (KPIs) that describe the health of their networks.

[0003] A performance indicator, or KPI, is a type of performance measurement. KPIs allow the success of a particular activity to be evaluated. Often, success is simply the repeated and regular achievement of a level of operational objectives (e.g., no defects, 10 / 10 customer satisfaction, etc.); sometimes, success is defined in terms of progress toward strategic goals. Therefore, selecting the right KPIs to monitor depends on a thorough understanding of what is important to the organization or user assigned to evaluate network performance. What is considered important often depends on the organization or user assigned to evaluate network performance that measures performance. Performance indicators are routinely linked to performance improvement efforts, as evaluation often leads to the identification of potential improvements. [Brief explanation of the drawings]

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

[0005] [Figure 1] FIG. 1 illustrates a network monitoring system that facilitates time-based network monitoring and generation of one or more KPI management profiles, according to one or more embodiments. [Figure 2A] 1 is a diagrammatic representation of a graphical user interface (GUI) according to one or more embodiments. [Figure 2B] 1 is a diagrammatic representation of a GUI warning message according to one or more embodiments. [Figure 3] FIG. 1 is a diagram of a GUI according to one or more embodiments. [Figure 4] 1 is a diagrammatic representation of a GUI watchlist, according to one or more embodiments. [Figure 5] 1 is a flowchart of a process for targeted KPI network monitoring and generation of one or more KPI management profiles, according to one or more embodiments. [Figure 6] FIG. 1 is a functional block diagram of a computer or processor-based system in which some embodiments may be implemented. DETAILED DESCRIPTION OF THE INVENTION

[0006] 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 and arrangements are described below. Of course, these are merely examples and are not intended to be limiting. For example, the formation or location of a first feature above or on a second feature in the following description includes embodiments in which the first and second features are formed or arranged in direct contact with each other, and also includes embodiments in which an additional feature is formed or arranged between the first and second features such that the first and second features are in direct contact with each other. Additionally, the present disclosure repeats 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.

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

[0008] In some embodiments, the system includes a processor and memory storing instructions that, when executed by the processor, cause a display to output a graphical user interface (GUI). In some embodiments, the GUI includes a user input field configured to receive user input identifying a target KPI associated with the network. In some embodiments, the GUI includes a user input field configured to receive user input identifying a KPI peak usage frequency. In some embodiments, the GUI includes a user input field configured to receive user input identifying a peak usage relationship. In some embodiments, execution of the instructions further includes creating a monitoring profile based on a target KPI of the KPI peak usage frequency for the peak usage relationship. In some embodiments, execution of the instructions further includes storing the monitoring profile. In some embodiments, execution of the instructions further includes monitoring the target KPI for the KPI peak usage frequency based on the monitoring profile. In some embodiments, execution of the instructions further includes collecting target KPI data over a period of time defined by the KPI peak usage frequency. In some embodiments, execution of the instructions further includes determining peak usage over a period of time defined by the KPI peak usage frequency. In some embodiments, execution of the instructions further includes periodically reporting peak usage data based on the monitoring profile.

[0009] Implementations include one or more of the following features. In some embodiments, the GUI further includes a user input field configured to receive user input identifying one or more networks for monitoring a goal KPI associated with the one or more networks. In some embodiments, the GUI further includes a user input field configured to receive user input identifying a communications technology for monitoring a goal KPI associated with the one or more networks. In some embodiments, the GUI further includes a user input field configured to receive user input identifying a vendor of a communications technology for monitoring a goal KPI associated with the one or more networks. In some embodiments, the GUI further includes a user input field configured to receive user input identifying a node included in the one or more networks for monitoring a goal KPI related to the one or more networks. In some embodiments, the first monitoring profile includes a first goal KPI during a first KPI peak usage frequency for a first peak usage relationship. In some embodiments, the instructions stored in the memory further cause the processor to create a second monitoring profile including a user input identifying a second goal KPI associated with the one or more networks. In some embodiments, the instructions stored in the memory further cause the processor to create a second monitoring profile including a user input identifying a second KPI peak usage frequency. In some embodiments, the instructions stored in the memory further cause the processor to create a second monitoring profile including user input identifying a second peak usage relationship. In some embodiments, the instructions stored in the memory further cause the processor to determine whether a stored monitoring profile matches the first monitoring profile and was previously created before the first monitoring profile is created. In some embodiments, the instructions stored in the memory further cause the processor, in response to the first monitoring profile being previously created, to further include in the GUI a warning message field configured to present information indicating that the first monitoring profile was previously created.In some embodiments, the user input field is configured to receive user input selecting a stored monitoring profile that matches the first monitoring profile. In some embodiments, the instructions stored in the memory further cause the processor to determine whether user permission exists to allow monitoring of the stored monitoring profiles. In some embodiments, the instructions stored in the memory further cause the processor to create a watch list that includes each user-created and / or user-selected monitoring profile.

[0010] Network services are often provided by static or inflexible systems that are difficult to configure, scale, and deploy across various target areas. Dependable network systems and / or network services that are flexibly built, scalable, and diverse often rely on the collection, analysis, and reporting of information about multiple network functions, network services, network devices, etc. that affect the performance, accessibility, configuration, scale, and / or deployment of the communications network, various network functions, network services, etc.

[0011] Network service providers often deploy network monitoring systems that track KPIs of aspects of the network to determine aspects of the network and / or how well the network is performing, such KPIs including, but not limited to, network availability (uptime), network mean time between failures, network mean time to repair, network unplanned availability, network unplanned downtime, network mean time to repair, etc.

[0012] For example, when a peak usage KPI value for a particular network function is below a threshold, the KPI value indicates that the network is operating normally. On the other hand, when the KPI peak usage value is equal to or greater than the threshold, the KPI value indicates that the network is operating below expectations, which in turn indicates that some unexpected event (e.g., hardware failure, capacity overload, cyber attack, etc.) has occurred. Therefore, a series of actions may be taken by the monitoring system, such as alerting a network operator, migrating network functions from a problematic server to a healthy server, temporarily shutting down the network, or some other appropriate action.

[0013] For example, a network developer may want to develop a network service in a new location. By determining the peak usage times of the network service in the different location, the network developer can effectively plan the network infrastructure in the new location. In another example, by monitoring the peak usage times of KPIs, a network traffic engineer can determine and plan the network capacity required for the network service to ensure network stability. In another example, by monitoring the peak usage times of network elements, a network security administrator can determine irregular usage on the network elements and take preventative measures against any potential security threats. In another example, by knowing the peak usage times of network elements in a particular location, a business unit can determine the data usage trends of the particular location and customize a business strategy for that particular location (e.g., presenting online advertisements associated with the particular location during peak data usage times).

[0014] A network system is constructed from multiple network elements, each of which contains multiple functions. Each function of each network element is configured to be presented in the form of a KPI. Monitoring peak usage times of KPIs of network elements is an aspect of network monitoring, because such information provides important insights into the telecommunications network system from both an engineering and business perspective.

[0015] In other approaches, monitoring peak usage times in telecommunications network systems has two basic types, one size fits all: Bouncing Busy Hour (BBH) is the peak usage time of a KPI over a 24-hour period or a day. It is the time during which the highest usage is measured over any given day or 24-hour period. Readings are in hours. The time of day chosen varies from day to day depending on the usage measured.

[0016] Network busy hour (NBH) is the peak usage time of the entire network system during a one-day or 24-hour period. In a conventional telecommunications network system, the entire network system is controlled by a network operator, and network elements are dedicated or optimized by a specific vendor. Network information (including the peak usage busy hours of network elements) is monitored by a small number of parties involved in the network system. The network operator and / or a specific vendor monitor and collect network information. When someone requests busy hour information for a specific KPI, the monitoring party extracts the requested information from the collected network information and provides the peak usage information to the requester.

[0017] Both BBH and NBH provide a peak usage KPI that represents the busiest hour per day or a moving average over a 24-hour period. Other approaches are therefore limited to peak usage times (at a node or network) over a 24-hour period. Thus, in the worst case, a requester waits 24 hours; in the best case, a requester waits one hour for information on the peak usage KPI.

[0018] As telecommunication network systems evolve and improve, the number of parties involved in a single network system increases significantly. There is a single network service available from multiple vendors. A single vendor provides multiple network services, and a single network operator partially or fully operates multiple network systems in one or more locations. Users are free to choose from which vendor their network services are provided based on their preferences. Vendors want to monitor the busy times (peak usage) of network services to propose changes to current services or to plan new services that are more attractive to users. Network operators want to monitor the busy times to ensure sufficient network traffic to maintain network stability or to plan the development of new network systems in other locations. The number of requests for busy time and peak usage information has increased significantly, and the requests are quite different from each other because different KPIs have different impacts on different vendors.

[0019] Furthermore, due to the fact that network conditions change dynamically, monitoring peak usage according to a reference time or a reference 60-minute period is limited and insufficient for some users. For example, in network security-related matters, it is desirable to detect and resolve security threats as soon as possible. Therefore, the KPI indicates the time of peak usage at the earliest one hour later, and monitoring BBH and NBH is not appropriate because by the time BBH and NBH are detected, it is too late to resolve the security threat.

[0020] When monitoring the status of a network, a single user often simultaneously monitors multiple KPIs, such as KPIs for similar aspects of the network for different locations, KPIs for different aspects of the network for one location, or a combination thereof. In some cases, a user may wish to monitor a single KPI differently for different locations (e.g., monitoring busy hours in Tokyo and busy days in Hokkaido).

[0021] Additionally, when multiple users are involved in monitoring KPIs for a network system, the definition of normal and abnormal may vary depending on the user or their role in monitoring the network. While some users monitor the same KPIs, each user may want to configure monitoring of a particular KPI for a different time frame (e.g., busy seconds, busy minutes, busy hours, busy days, busy weeks, busy months, busy years, etc.). Furthermore, each user may want to configure monitoring of a particular KPI for different time frames contained within a time frame (e.g., busy seconds within a 5-minute period, busy minutes every 30 minutes, busy hours on weekends, busy days on work days, busy weeks prior to holidays, busy months in a year, busy years in a 10-year period, etc.). Other approaches do not provide a network monitoring system that allows users to customize multiple KPIs over various time periods and across various networks.

[0022] FIG. 1 is an illustration of a network monitoring system 100 that facilitates time-based network monitoring and generation of one or more KPI management profiles, according to one or more embodiments.

[0023] The dynamic time-based network monitoring system 100 described with respect to Figure 1 helps solve the problems mentioned above. In some embodiments, the system 100 is configured so that the user is no longer dependent on the network operator and / or vendor to provide the requested KPIs. In contrast, a monitoring configuration profile (e.g., a "KPI monitoring profile") defines the KPIs, networks, periodicity, etc. intended by the user to be monitored and creates time values ​​associated with the monitoring profile for one or more KPIs.

[0024] In some embodiments, system 100 is spared from storing any pre-defined KPI monitoring profiles. Instead, system 100 is configured to maintain user-defined KPI management profiles that define the target KPIs to be monitored and various parameters for the monitored target KPIs. In some embodiments, system 100 is configured to maintain a master list of user-defined KPI management profiles that define the target KPIs to be monitored and various parameters for the monitored target KPIs. In some embodiments, system 100 is configured to maintain user-specific KPI management profiles that define the target KPIs to be monitored and various parameters for the monitored target KPIs specifically for a specified user.

[0025] During network monitoring, system 100 is configured to compare current KPI data over a selected period based on a user-defined peak usage period according to the monitoring settings specified in the KPI management profile. In some embodiments, system 100 stores a temporary peak usage KPI value until a new peak usage value is discovered within the user-defined time period. System 100 retains this temporary peak usage KPI for comparison and determines whether the difference between the temporary peak usage KPI data and the entire KPI history data is replaced with temporary peak usage KPI data that meets the conditions defined by one or more parameters set in the KPI management profile. In some embodiments, once the comparison and determination are complete, the temporary peak usage KPI data is replaced with a new peak usage KPI and stored as a new peak usage value for periodic comparison.

[0026] In some embodiments, system 100 does not include a network operator and / or vendor monitor, but rather collects information for KPIs to allow a user to create and update KPI monitoring profiles for each KPI, network, network vendor, network operator, periodicity, etc. System 100 includes a network management platform 101, a database 103, one or more network nodes 105, and one or more network devices 107.

[0027] The network management platform 101 is configured to generate one or more KPI management profiles based on one or more parameters input by a user to track and / or identify the performance of the network. In some embodiments, the network management platform 101 receives KPI data from one or more of the network devices 107, such as network nodes 105, radio stations, radio frequency (RF) emitters, radio access networks (RANs), and user equipment 109, or other suitable network components configured to communicate data to the network management platform 101 via a network protocol stack, corresponding protocol layer logs, or direct communication, upon identifying the current operating state of the network based on, for example, the KPI data stored in the database 103.

[0028] In some embodiments, the network node 105 is a fourth-generation (4G) evolved Node B (eNB), a fifth-generation (5G) logical node (gNB), a new radio (NR) base station, and an edge device (such as a router, routing switch, integrated access device, multiplexer, metropolitan area network (MAN) device, wide area network (WAN) device, etc.) or other suitable node. In some embodiments, the network management platform 101 includes a set of computer-readable instructions that, when executed by a processor, such as processor 603 (FIG. 6), cause the network management platform 101 to perform a process discussed according to one or more embodiments or methods, such as method 500 (FIG. 5). In some embodiments, the network management platform 101 is separate from the network node 105 and the network device 107. In some embodiments, the network management platform 101 is part of one or more of the network node 105 or the network device 107. In some embodiments, one or more processes of the network management platform 101 are configured to be split between one or more of the network nodes 105 or network devices 107 and a processor, such as processor 603, that is separate from the network nodes 105 and / or network devices 107. In some embodiments, the network management platform 101 is at least partially implemented by the UE 109.

[0029] In some embodiments, database 103 is a centralized network repository of searchable information including historical KPI data, rules defining various KPIs, master KPI monitoring profiles, KPI monitoring profiles by particular users, network usage, timing, connected devices, location, network resource consumption, cost data, example network KPIs, KPI management profiles corresponding to one or more users, predefined KPI management templates accessible to be applied by one or more registered users, or other suitable elements or information from which a peak usage KPI management profile can be defined, and / or network functions that can be implemented in the network including one or more of the one or more KPIs that can be defined. Database 103 is a memory, such as memory 605 (FIG. 6), that can be queried or that can have data stored therein, according to one or more embodiments.

[0030] In some embodiments, the network management platform 101 generates a GUI 200 (FIG. 2A) that is output to a display 611 (FIG. 6) by a terminal, such as a UE 109 or a network device 107, associated with the network management platform 101 for a user (e.g., a network operator, a network vendor, or any personnel responsible for monitoring the network). The GUI 200 allows the user to input or select parameters of one or more target KPIs. The network management platform 101 generates a user-specified KPI management profile based on the one or more parameters input or selected by the user and causes the KPI management profile to be stored in the database 103. In some embodiments, the network management platform 101 causes the KPI management profile to be stored on a server, in the memory of the UE 109, or in some other suitable location.

[0031] In some embodiments, the UE 109 is a computer or computing system. Additionally or alternatively, the UE 109 has a liquid crystal display (LCD), light emitting diode (LED), or organic light emitting diode (OLED) screen interface, such as user interface (UI) 607 (FIG. 6), and provides a touchscreen interface with digital buttons and a keyboard or physical buttons, along with a physical keyboard. In some embodiments, the UE 109 connects to the Internet and interconnects with other devices. Additionally or alternatively, the UE 109 incorporates an integrated camera, the ability to make and receive voice and video phone calls, video games, and global positioning system (GPS) functionality. Additionally or alternatively, the UE runs an operating system (OS) that allows for the installation and execution of feature-specific third-party applications. In some embodiments, the UE 109 is a computer (such as a tablet computer, netbook, digital media player, digital assistant, graphing calculator, handheld game console, handheld personal computer (PC), laptop, mobile internet device (MID), personal digital assistant (PDA), pocket calculator, portable medical player, or ultra-mobile PC), a mobile phone (such as a camera phone, feature phone, smartphone, phablet), a digital camera (such as a digital camcorder, or digital still camera (DSC), digital video camera (DVC), or front-facing camera), a pager, a personal navigation device (PND), a wearable computer (such as a calculator watch, smartwatch, head-mounted display, earphones, or biometric device), or a smart card.

[0032] Subsequently, the network management platform 101 generates peak usage values ​​from the historical KPI values ​​of one or more selected target KPIs based on the settings specified in the KPI management profile. The network management platform 101 then compares the current KPI data for the target KPIs with the peak usage values ​​to determine whether the difference between the current KPI peak usage data is greater than the previous peak usage value for a period set by the user. The network management platform 101 then takes appropriate action according to the KPI management profile.

[0033] When a new objective KPI monitoring profile is received by the network management platform 101, the network management platform 101 considers whether a previous objective KPI monitoring profile currently exists that matches the new objective KPI monitoring profile. The network management platform 101 determines whether the desired KPI management profile already exists within the database 103, creates a new objective KPI management profile if the profile does not already exist, allows the user to access the already existing objective KPI management profile if the user has security access to the KPI, and adds the KPI management profile to the user's KPI watchlist. In some embodiments, once the objective KPI management profile is created, the network management platform 101 is configured to continuously monitor the objective KPI on behalf of the user. In some embodiments, the network management platform 101 periodically reports the results of the monitored objective KPIs to the user. In some embodiments, the periodic reporting is based on a periodicity selected by the user. In a non-limiting example, if a user desires to know the node's peak hour usage over a three-day period, the network management platform 101 presents the user with a report every hour when a new 72-hour period is completed.

[0034] In some embodiments, network management platform 101 is configured to allow a user to create multiple KPI management profiles for one objective KPI, one KPI management profile for multiple objective KPIs, or multiple KPI management profiles for multiple objective KPIs. Thus, network management platform 101 monitors multiple objective KPIs in multiple networks and / or nodes over different time periods and with different time or periodicity reporting parameters.

[0035] In some embodiments, network management platform 101 is configured to allow multiple users to create corresponding goal KPI management profiles. In such a configuration, network management platform 101 simultaneously monitors the goal KPIs of multiple users and performs actions, such as periodic reporting, corresponding to each user's KPI management profile.

[0036] In some embodiments, the network management platform 101 is configured to identify target KPIs based on a 3rd Generation Partnership Project (3GPP®) protocol or similar protocol log in the communications network. The network node 105, for example, captures the protocol log, counter information, or traffic pattern schema of live communications traffic in the communications system. In this example, the network node 105 is the first entity to capture the protocol log or traffic pattern using the 3GPP protocol stack and extracts call process messages, such as L1, L2, L3, non-access stratum (NAS) layers, communications network intelligence messages, counter or KPI data, or other suitable protocol messages for a user-defined time session or rollover period (ROP). The protocol log is communicated to the network management platform 101 via an open operations and maintenance (O&M) interface, such as an O-RAN interface, or other suitable interface for processing by the network management platform 101 and for storage in the database 103.

[0037] In some embodiments, network monitoring system 100 is configured to allow a user to monitor, determine, and receive reports of peak usage (e.g., busy seconds, busy minutes, busy hours, busy days, busy weeks, busy months, busy years, etc.) of multiple target KPIs for multiple networks and / or network elements in a manner preferred by the user. In some embodiments, network monitoring system 100 is configured to implement a user interface (UI) 607 ( FIG. 6 ) that allows a user to select one or more target KPIs based on desired information (e.g., vendor, domain type, technology type, KPI type, peak usage over a selected time period, and other suitable information according to some embodiments). In some embodiments, the user-selected settings are stored as a monitoring profile, and based on the monitoring profile, network monitoring system 100 continuously monitors, collects, determines, and periodically reports peak usage of the selected target KPIs to the user.

[0038] In other approaches, monitoring only peak usage in one-hour increments over a 24-hour period is limiting and insufficient for some users due to the fact that network status changes dynamically. For example, in network security-related matters, it is useful to detect and resolve security threats as soon as possible. Therefore, since BBH and NBH operate essentially in one-hour increments for peak usage, monitoring BBH and NBH alone is insufficient to resolve security threats by the time BBH and NBH are detected.

[0039] Therefore, other approaches for peak usage monitoring are ineffective and inappropriate for use. In some embodiments, the centralized network peak usage monitoring system 100 enables multiple users, regardless of their location and requirements, to effectively monitor peak usage user-determined periods of desired KPIs. The user-determined periods monitor peak usage of the target KPIs in terms of seconds, minutes, hours, days, weeks, months, years, etc. In some embodiments, peak usage monitoring of the target KPIs is monitored by multiple users. In some embodiments, to avoid creating multiple monitoring profiles for a single target KPI (e.g., resulting in wasted network resources), safeguards are incorporated to ensure that only one monitoring profile with the same settings is created for a single KPI.

[0040] FIG. 2A is an illustration of a graphical user interface (GUI) 200 according to one or more embodiments.

[0041] The network management platform 101 is configured to output a GUI 200 to a display 611 (FIG. 6). The GUI 200 is a form of a UI, such as UI 607, that allows a user to interact with an electronic device through graphical icons and audio indicators, such as primary notation, in addition to a text-based user interface, typed command labels, or text navigation. Actions in a GUI are typically performed by direct manipulation of graphical elements. The GUI 200 is used in any handheld mobile device, such as a UE 109, a network device 107, an MP3 player, a portable media player, a gaming device, a smartphone, and smaller home, office, and industrial control devices.

[0042] The GUI 200 includes a domain field 202 configured to receive user input identifying a target domain for the desired KPI monitoring profile. In some embodiments, the user may select from any suitable domain, for example, the RAN, the core network, or the telecommunications network.

[0043] GUI 200 includes a technology field 204 configured to receive user input identifying a technology for the desired KPI monitoring profile. In some embodiments, a user can select from Long Term Evolution (LTE), LTE Advanced, LTE Advanced Pro, 4G (Fourth Generation), 5G (Fifth Generation), 5G NR (New Radio), IP Multimedia Subsystem (IMS), Universal Mobile Telecommunications System (UMTS), 3G (Third Generation), Global System for Mobile Communications (GSM), 2G (Second Generation), and any suitable telecommunications technology.

[0044] The GUI 200 includes a vendor field 206 configured to receive user input identifying a vendor-provided service via technology in the domain. In some embodiments, the user can select this parameter from any available vendor.

[0045] The GUI 200 includes a node field 208 configured to receive user input identifying a node within the domain. In some embodiments, a user may select a network node, such as a network node 105, which may be a fourth generation (4G) evolved Node B (eNB), a fifth generation (5G) logical node (gNB), a new radio (NR) base station, an edge device, or other suitable node.

[0046] GUI 200 includes a target KPI input field 210 configured to receive user input identifying a target KPI associated with network 100. In some embodiments, a user may select from KPIs such as peak data rate, peak spectral efficiency, peak data rate experienced by a user, peak area traffic, peak latency, peak connection density, peak energy efficiency, peak reliability, peak mobility, peak mobility interruption time, peak bandwidth, or any other suitable KPI.

[0047] In some embodiments, in addition to creating a monitoring profile, such as at operation 503, for each selected KPI, a target KPI is automatically selected based on input in user input fields 202-210. In a non-limiting example, a target KPI is selected by receiving a first user input in user input field 202. Based on the user input in user input field 202, possible parameters are presented to the user as user recommendations (e.g., in the form of a drop-down list or other suitable presentation) in user input field 204 based on the user input in user input field 202. Based on the user input in user input field 204 or user input fields 202 and 204, process 500 determines possible parameters for input field 206 and presents the possible parameters as user recommendations (e.g., in the form of a drop-down list or other suitable presentation) in user input field 206. Based on the user input in user input field 206 or user input fields 202, 204, and 206, process 500 determines possible parameters for input field 208 and presents such possible parameters as recommendations (e.g., in the form of a drop-down list or other suitable presentation) to the user in user input field 208. Based on the user input in user input field 208 or user input fields 202, 204, 206, and 208, process 500 determines possible parameters for input field 210 and presents such possible parameters as recommendations (e.g., in the form of a drop-down list or other suitable presentation) to the user in user input field 210. Thus, in some embodiments, process 500 determines a goal KPI based on user input in user input field 210 based on previous user input in user input fields 202, 204, 206, and 208.

[0048] The GUI 200 includes a frequency field 212 configured to receive user input identifying how often the user desires to monitor peak usage of the KPI. In some embodiments, in response to the user selecting the frequency field 212, a periodicity field 214 is presented to the user. For example, the user has the ability to select a KPI peak usage by second field 216a, a KPI peak usage by minute field 216b, a KPI peak usage by hour field 216c, a KPI BBH field 216d, a KPI BBH weekly field 216e, a KPI NBH field 216f, and a KPI NBH weekly field 216g, or any other suitable parameter that identifies the frequency of peak usage of the KPI. In some embodiments, the periodicity field 214 allows the user to input / select a parameter associated with a type of peak usage time. In addition to daily BBH and weekly BBH, the periodicity field 214 further allows the user to input / select peak usage seconds in a minute, peak usage minutes in an hour, peak usage hours in a day, peak usage days in a week, peak usage weeks in a month, peak usage months in a year, etc. In some embodiments, the default selection of peak usage is the time domain above the selected KPI monitoring time domain. In a non-limiting example, when a user selects the peak usage seconds field 216a, the default KPI reporting time domain is over the course of one minute (e.g., the next unit of time domain above the selected monitoring domain, seconds). Thus, continuing the example, the user receives a KPI report presenting peak usage seconds for every minute.

[0049] The network management platform 101 processes the selected parameters (eg, domain, technology, vendor, node, KPI, frequency, periodicity, and other suitable parameters) to generate a KPI management profile.

[0050] In some embodiments, network monitoring system 100 includes a processor 603 (FIG. 6) and a database 103 or memory 605 (FIG. 6) storing instructions 609 (FIG. 6) that, when executed by processor 603, cause display 607 (FIG. 6) to output GUI 200. GUI 200 includes user input field 210 configured to receive user input identifying a target key performance indicator (KPI) associated with the network. User input field 212 is configured to receive user input identifying a KPI peak usage frequency. User input field 214 is configured to receive user input identifying a peak usage relationship. Execution of the processor further includes creating a monitoring profile based on a target KPI of KPI peak usage frequency (e.g., periodicity) to peak usage relationship; storing the monitoring profile in database 103 or memory 605, etc.; monitoring the target KPI of KPI peak usage frequency based on the monitoring profile; collecting target KPI data over a period defined by the KPI peak usage frequency; determining peak usage for the period defined by the KPI peak usage frequency based on the collected target KPI data; and periodically reporting the peak usage data based on the monitoring profile.

[0051] In some embodiments, network monitoring system 100 includes UI 607, which allows multiple users, regardless of their location, to access GUI 200 and select one or more desired KPIs, for example, from target KPI field 210. A monitoring profile is then created for each selected KPI, domain, technology, vendor, node, and frequency. In some embodiments, during the creation of the monitoring profile, network monitoring system 100 presents message 250 ( FIG. 2B ) to the user if a monitoring profile with the same settings as the user-selected KPI monitoring profile has already been created. In response to determining that a KPI monitoring profile has already been created and the user is authorized to monitor the KPI monitoring profile, network monitoring system 100 presents a message to inform the user (e.g., a profile with the same settings has been created. Do you want to add the existing setting profile to your watchlist?) and then directs the user to the already created monitoring profile.

[0052] In some embodiments, the user selects the Add button 252 to add a created monitoring profile, or selects the Cancel button 254 to reject an existing KPI monitoring profile. In some embodiments, the user double-clicks a displayed existing KPI monitoring profile, or drags and drops an already created monitoring profile into a watch list (FIG. 4), or the like.

[0053] In response to the network monitoring system 100 determining that the user is not authorized to monitor the KPI monitoring profile, the network monitoring system 100 presents a message (e.g., "You are not authorized to monitor this KPI. Please contact your network administrator to request authorization") to inform the user.

[0054] In some embodiments, in response to network monitoring system 100 determining that a KPI monitoring profile has not yet been created, network monitoring system 100 creates a new targeted KPI monitoring profile and adds the targeted KPI monitoring profile to the user's watchlist without presenting a message to inform the user. In some embodiments, in response to network monitoring system 100 determining that a KPI monitoring profile has not yet been created, network monitoring system 100 presents a message to inform the user (e.g., "No existing monitoring profile found. Create a new monitoring profile?"). Thereafter, in response to the user wishing to create a new monitoring profile, the user can click add button 218. In response, network monitoring system 100 creates a new targeted KPI monitoring profile and adds the targeted KPI monitoring profile to the user's watchlist (FIG. 4).

[0055] In some embodiments, to add monitoring profiles, such as monitoring profiles 402a, 402b, 402c, 402d, 402e, 402f, and 402g, to watchlist 400 (FIG. 4), a user accesses monitoring profile dashboard 404, which includes the monitoring profiles available to the user (e.g., for security and / or privacy reasons, some users may not be able to monitor peak usage of some particular KPIs from some vendors, locations, technologies, etc.).

[0056] In some embodiments, a user enters targeted KPI monitoring profile parameters (e.g., keywords, full terms, ID, etc.) to search for a targeted KPI monitoring profile (e.g., in search window 406, search bar, etc.). In some embodiments, network monitoring system 100 searches for the requested targeted KPI monitoring profile based on the user's input. In response to network monitoring system 100 identifying a monitoring profile of interest and determining that the user has permission to view KPIs, the user can add the targeted KPI monitoring profile to the user's watchlist, such as watchlist 400, such that network monitoring system 100 periodically reports to the user peak usage times for the selected targeted KPI monitoring profile.

[0057] 3 is a diagram of a GUI 300, according to one or more embodiments. GUI 300 is an exemplary embodiment of GUI 200 (FIG. 2A), with like features having corresponding reference numbers increased by 100.

[0058] A non-transitory computer-readable medium, such as database 103 or memory 605, includes stored instructions 609 that cause a display 611 to output a GUI 300. The GUI 300 includes a user input field 302 configured to receive user input identifying a domain. The GUI 300 includes a user input field 304 configured to receive user input identifying a technology. The GUI 300 includes a user input field 306 configured to receive user input identifying a vendor. The GUI 300 includes a user input field 308 configured to receive user input identifying a node. The GUI 300 includes a user input field 310 configured to receive user input identifying a goal KPI. The GUI 300 includes a user input field 312 configured to receive user input identifying a KPI peak usage frequency for a selected KPI. The GUI 300 includes a user input field 314 configured to receive user input identifying a peak usage relationship or periodicity to the KPI peak usage frequency.

[0059] In a non-limiting example, in response to a user selecting weekly BBH in user input field 312, user input field 314 is displayed. User input field 314 allows the user to select which days of the week the user wants to monitor for weekly BBH. Continuing the example, the user is not interested in the target KPIs in user input field 310 for Saturdays and Sundays, but rather the target KPIs during work days. Hence the user selection of input fields 316a-316e. In some embodiments, user input field 314 is contingent on the selection in user input field 312. For example, if the user selects a weekly BBH frequency in user input field 312, user input field 314 suggests which days of the week the user wants to select for weekly BBH. In some embodiments, the user has the option to select which weeks the user wants to monitor monthly BBH. For example, the user may select the first and third week of the month to perform monthly BBH, or the user may want monthly BBH over the course of a month (i.e., which week had the highest peak usage during the month).

[0060] In some embodiments, the user selects the aggregation user input field 318 to select the type of aggregation (e.g., maximum, minimum, average, etc.) within the periodicity of user input field 314 and the frequency of user input field 312. In a non-limiting example, if a user wants to know the maximum BBH of a node over three weekday days, Monday through Friday, the user selects the desired three days (e.g., Monday, Tuesday, Wednesday, or other suitable selected days) in user input field 314 and selects "maximum" as the type of aggregation in user input field 318. Thus, the system determines the candidate BBH for each of the three selected days and then determines which of the three candidates has the maximum value among the three candidates. Thus, the user has a nearly unlimited amount of target KPI monitoring profiles available. That is, within network monitoring system 100, the user has several KPIs to choose from (based on the user's input in input fields 302, 304, 306, 308, and / or 310). Among these multiple KPIs, GUI 300 is configured to allow the user to select from several monitoring frequencies in user input field 312. Among these multiple monitoring frequencies, GUI 300 is configured to allow the user to select which time period to monitor in user input field 314. Among these multiple monitoring periods, GUI 300 is configured to allow the user to select aggregated sub-periods in user input field 318. The flexibility of targeted KPI monitoring is substantially increased by network monitoring system 100.

[0061] In some embodiments, each of the user inputs into fields 302, 304, 306, 308, 310, 312, 314, 316a-e, and 318 is stored in database 103 or memory 605 as a monitoring profile.

[0062] In some embodiments, network monitoring system 100 accesses database 103 and retrieves target KPI data based on the monitoring profile. In a non-limiting example, in response to a monitoring profile being daily BBH of KPI X on day Y, network monitoring system 100 retrieves and collects all data for KPI X available on day Y and determines from the collected data time Z when KPI X has peak usage (e.g., highest value, etc.).

[0063] In some embodiments, network monitoring system 100 extracts data for KPI X collected at time Z on day Y, and then reports or presents the extracted data as a daily BBH for KPI X on day Y. In another non-limiting example, a weekly BBH is performed (i.e., the time during the week when the targeted KPI has the highest usage). Thus, peak hour usage over a seven-day period is determined and reported or presented to the user. In other non-limiting examples, BBH is reported monthly, quarterly, yearly, etc.

[0064] In some embodiments, peak usage of any target KPI is monitored. In a non-limiting example, daily NBH, weekly NBH, monthly NBH, yearly BBH, etc. are selected by the user. In some embodiments, peak usage is configured to be reported or presented based on the relationship of peak usage of KPI X during period Y over period Z. In a non-limiting example, KPI X is monitored for peak usage seconds over every minute. In another non-limiting example, KPI X is monitored for peak usage minutes over an hour for each hour. In another non-limiting example, KPI X is monitored for peak usage hours over a day for each day. In a non-limiting example, KPI X is monitored for peak usage days over a week for each week. In a non-limiting example, KPI X is monitored for peak usage weeks over a month for each month. In a non-limiting example, KPI X is monitored for peak usage months over a year for each year.

[0065] In some embodiments, peak usage is examined over various lengths of time. In a non-limiting example, KPI X is monitored for peak usage seconds over 5 minutes for each 5-minute period. In a non-limiting example, KPI X is monitored for peak usage hours over 3 days for each 3-day period. In a non-limiting example, KPI X is monitored for peak usage days of Saturday and Sunday. In a non-limiting example, KPI X is monitored for peak usage months of September through December.

[0066] In some embodiments, to add a monitoring profile to a watchlist, such as watchlist 400, a user accesses a monitoring profile dashboard, such as dashboard 404, that includes the monitoring profiles available to the user (e.g., restrictions due to security and / or privacy reasons, some users may not be able to monitor peak usage / busy times for some particular KPIs from some vendors, locations, technologies, etc.). In some embodiments, in response to creating a monitoring profile that the user does not have access to, the user will not be able to see the targeted KPIs and will receive a warning message as described above.

[0067] In some embodiments, the user enters parameters (e.g., keywords, full terms, ID, etc.) of the desired KPI into search bar 406. In some embodiments, network monitoring system 100 searches for possible monitoring profiles based on the user's input into search bar 406. In response to determining that the monitoring profile already exists and that the user is authorized to monitor the desired KPI, network monitoring system 100 notifies the user by presenting message 250 (e.g., a matching configuration profile has been created. Would you like to add the configuration profile to your watchlist?) and then directs the user to the created monitoring profile. In some embodiments, this allows the user to add the created monitoring profile (e.g., by double-clicking the created monitoring profile, dragging and dropping the created monitoring profile to your watchlist, clicking add button 252, etc.). In response to network monitoring system 100 determining that the user is not authorized to monitor the KPI, the system presents a warning message (e.g., you are not authorized to monitor this KPI. Contact your network administrator to request authorization) to inform the user.

[0068] In some embodiments, in response to network monitoring system 100 determining that a monitoring profile has not yet been created, network monitoring system 100 presents a message to inform the user (e.g., "No existing monitoring profile found. Create a new monitoring profile?"). In some embodiments, in response to the user deciding to create a new monitoring profile, the user is directed to a GUI such as GUI 200 or GUI 300 (e.g., via a pop-up window, etc.).

[0069] In some embodiments, GUIs 200 and 300 are configured to allow users to create monitoring profiles for targeted KPI monitoring of different types of peak usage. In some embodiments, user input fields Domain (202, 302), Technology (204, 304), Vendor (206, 306), Node (208, 308), and KPI (210, 310) are configured to allow users to input / select parameters related to the target KPI. In some embodiments, user input fields (212, 312) are configured to allow users to input / select parameters related to the type of KPI peak usage. In some embodiments, user input field 312 is configured to allow users to select daily BBH, weekly BBH, monthly BBH, quarterly BBH, yearly BBH, daily NBH, weekly NBH, monthly NBH, yearly BBH, busy seconds in a minute, busy minutes in an hour, busy hours in a day, busy days in a week, busy weeks in a month, busy months in a year, etc. In some embodiments, GUIs 200 and 300 include input fields in addition to input fields 202-212 and 302-318 to allow a user to further specify parameters for monitoring the profile. In some embodiments, GUIs 200 and 300 include only input fields to allow a user to select a target KPI and select a type of KPI peak usage.

[0070] In some embodiments, additional user input fields are presented in response to particular inputs or selected parameters. In a non-limiting example, in response to weekly BBH being selected in user input field 312, additional user input fields 314 and 318 are presented. In some embodiments, user input field 314 is configured to allow the user to select a desired time period, such as day, week, month, etc. In some embodiments, user input field 318 is configured to allow the user to enter an aggregation method (e.g., max, min, average, sum, etc.). In a non-limiting example, in response to Monday (user input field 316a), Tuesday (user input field 316b), and Wednesday (user input field 316c) being selected in user input field 314 and Max being selected in user input window 318, network monitoring system 100 monitors the maximum BBH for each of Monday, Tuesday, and Wednesday, and then determines which maximum BBH among the three has the highest value. In some embodiments, the network monitoring system 100 extracts the BBH with the highest value and reports the highest value to the user as the weekly BBH.

[0071] In some embodiments, a user can select a wide variety of peak usage KPI combinations based on the user's own preferences and requirements, such as busy seconds in 5 minutes, busy hours in 3 days, busy days between Saturday and Sunday, busy months between September and December, etc. In some embodiments, after creating a monitoring profile, the monitoring profile is added to the user's watchlist, such as watchlist 400, and network monitoring system 100 begins monitoring and reporting peak usage / busy times for the desired KPIs based on the monitoring profile. In some embodiments, network monitoring system 100 is configured to allow multiple users to monitor desired peak usage for the desired KPIs in the manner desired by the users. In some embodiments, network monitoring system 100 provides flexibility in configuring network monitoring system 100 to improve the user's experience in monitoring peak usage for the desired KPIs. In some embodiments, flexibility is achieved by allowing users to add existing monitoring profiles and / or create desired monitoring profiles via GUIs 200 and 300.

[0072] 5 is a flowchart of a process 500 for facilitating targeted KPI monitoring and generating one or more KPI management profiles, according to one or more embodiments. In some embodiments, the network management platform 101 (FIG. 1) performs the process 500, and is implemented, for example, in or by a chipset including a processor and memory, as shown in FIG.

[0073] In operation 501, a GUI is output by a display. The GUI includes one or more user input fields configured to receive user input identifying a target KPI. The GUI also includes a user input field configured to receive user input identifying a KPI peak usage frequency. The GUI further includes one or more other user input fields configured to receive user input identifying a peak usage relationship and / or KPI frequency periodicity monitoring. The process flows from operation 501 to operation 503.

[0074] A first monitoring profile is created in operation 503. In a non-limiting example, a monitoring profile is created for each selected KPI, such as user input fields 210, 310, domain, such as user input fields 202, 302, technology, such as user input fields 204, 304, vendor, such as user input fields 206, 306, node, such as user input fields 208, 308, and frequency, such as user input fields 212, 312. The process flows from operation 503 to 505.

[0075] In operation 505, the created monitoring profile is saved (stored). For example, the monitoring profile is stored in database 103 and / or memory 605. The process flows from operation 505 to operation 507.

[0076] At operation 507, the network monitoring system 100 collects target KPI data for a defined period of time. For example, the network monitoring system 100 collects target KPI data for the KPI data specified in the user input fields 210, 310 for a period of time specified in the user input fields 212, 312. The process flows from operation 507 to 509.

[0077] In operation 509, the network monitoring system 100 determines the peak usage of the selected KPI in the monitoring profile over the selected time period specified in the monitoring profile. For example, the data collected in operation 507 for the time period specified in the user input fields 212, 312 is filtered for the highest value representing the peak usage over the defined time period. In some examples, a sliding window method is used to reduce latency. The process flows from operation 509 to 511.

[0078] In operation 511, peak usage tracked in the monitoring profile is reported periodically. In some embodiments, peak usage is reported at the end or monitoring period or frequency specified in user input fields 212, 312. In some embodiments, the user can specify the reporting periodicity.

[0079] FIG. 6 is a functional block diagram of a computer or processor-based system 600 in which embodiments may be implemented.

[0080] The processor-based system 600 is programmed to facilitate targeted KPI network monitoring and generation of one or more targeted KPI management profiles as described herein and includes components such as a bus 601, a processor 603, and a memory 605.

[0081] In some embodiments, the processor-based system is implemented as a single "system on a chip." The processor-based system 600, or portions thereof, constitutes a mechanism for performing one or more steps to facilitate targeted KPI network monitoring and generate one or more KPI management profiles.

[0082] In some embodiments, processor-based system 600 includes a communication mechanism, such as bus 601, for transferring information and / or instructions between components of processor-based system 600. Processor 603 is connected to bus 601 to retrieve instructions for execution and process information stored, for example, in memory 605. In some embodiments, processor 603 also includes one or more specialized components for performing specific processing functions and tasks, such as one or more digital signal processors (DSPs) or one or more application-specific integrated circuits (ASICs). DSPs are typically configured to process real-world signals (e.g., sound) in real time, independently of processor 603. Similarly, ASICs can be configured to perform specialized functions not easily performed by more general-purpose processors. Other specialized components that assist in performing the functions described herein optionally include one or more field-programmable gate arrays (FPGAs), one or more controllers, or one or more other specialized computer chips.

[0083] In one or more embodiments, the processor(s) 603 performs a series of operations on information specified by a set of instructions stored in memory 605 in connection with facilitating targeted KPI network monitoring and generating one or more KPI management profiles. Execution of the instructions causes the processor to perform the specified functions.

[0084] The processor 603 and associated components are connected to memory 605 via bus 601. Memory 605 includes one or more of dynamic memory (e.g., RAM, magnetic disk, writable optical disk, etc.) and static memory (e.g., ROM, CD-ROM, etc.) for storing executable instructions that, when executed, perform the steps described herein to facilitate targeted KPI network monitoring and generation of one or more KPI management profiles. Memory 605 also stores data associated with or generated by the execution of the steps.

[0085] In one or more embodiments, memory 605, such as random access memory (RAM) or any other dynamic storage device, stores information, including processor instructions, for facilitating dynamic, time-based network monitoring and generating one or more KPI management profiles. Dynamic memory can change the information it stores. RAM allows units of information stored at locations called memory addresses to be stored and retrieved independently of information at adjacent addresses. Memory 605 is also used by processor 603 to store temporary values ​​while the processor is executing instructions. In various embodiments, memory 605 is read-only memory (ROM) or any other static storage device coupled to bus 601 for storing static information, including instructions, that cannot be changed by processor 603. Some memory consists of volatile storage, which loses stored information when power is lost. In some embodiments, memory 605 is a non-volatile (persistent) storage device, such as a magnetic disk, optical disk, or flash card, for storing information, including instructions, that persists even when system 600 is turned off or otherwise loses power.

[0086] As used herein, the term "computer-readable medium" refers to any medium that participates in providing information to the processor 603, including instructions 609 for execution. Such media take many forms, including, but not limited to, computer-readable storage media (e.g., non-volatile media, volatile media). Non-volatile media include, for example, optical or magnetic disks. Volatile media include, for example, dynamic memory. Common forms of computer-readable media include, for example, floppy disks, flexible disks, hard disks, magnetic tape, other magnetic media, CD-ROMs, CDRWs, DVDs, other optical media, punch cards, paper tape, optical mark sheets, other physical media having a pattern of holes or other optically recognizable indicia, RAM, PROM, EPROM, FLASH-EPROM, EEPROM, flash memory, other memory chips or cartridges, or other media readable by a computer. The term computer-readable storage medium is used herein to refer to computer-readable media.

[0087] In some embodiments, the system includes a processor and memory storing instructions that, when executed by the processor, cause the display 611 to output a graphical user interface (GUI). The display 611 is an output device for presenting information in visual or tactile form (the latter being used, for example, in tactile electronic displays for the blind). If the input information provided comprises electrical signals, the display is called an electronic display. In some embodiments, the display 611 is part of the UI 607.

[0088] The UI 607 ​​enables a user to effectively operate and control the system 600. In some embodiments, the user interface is composed of one or more layers, including a human-machine interface (HMI) that interfaces the machine with physical input hardware, such as a keyboard, mouse, or gamepad, and output hardware, such as a computer monitor, speakers, printer, etc., as well as other suitable user interfaces within the contemplated scope of the present disclosure. Additional user interface layers interact with one or more of the human senses, including a haptic user interface (touch), a visual user interface (vision), an auditory user interface (sound sense), an olfactory user interface (olfaction), a balance user interface (balance sense), a gustatory user interface (taste), and other suitable user interface layers within the contemplated scope of the present disclosure.

[0089] In some embodiments, the system includes a processor and memory storing instructions that, when executed by the processor, cause a display to output a graphical user interface (GUI). In some embodiments, the GUI includes a user input field configured to receive user input identifying a target KPI associated with the network. In some embodiments, the GUI includes a user input field configured to receive user input identifying a KPI peak usage frequency. In some embodiments, the GUI includes a user input field configured to receive user input identifying a peak usage relationship. In some embodiments, execution of the instructions further includes creating a monitoring profile based on a target KPI of the KPI peak usage frequency for the peak usage relationship. In some embodiments, execution of the instructions further includes storing the monitoring profile. In some embodiments, execution of the instructions further includes monitoring the target KPI for the KPI peak usage frequency based on the monitoring profile. In some embodiments, execution of the instructions further includes collecting target KPI data over a period of time defined by the KPI peak usage frequency. In some embodiments, execution of the instructions further includes determining peak usage over a period of time defined by the KPI peak usage frequency based on the collected target KPI data. In some embodiments, execution of the instructions further includes periodically reporting the peak usage data based on the monitoring profile.

[0090] Implementations include one or more of the following features. The system further includes a fourth user input field where the GUI is configured to receive a fourth user input identifying one or more networks for monitoring a target KPI associated with the one or more networks. The GUI further includes a fifth user input field where the GUI is configured to receive a fifth user input identifying a communications technology for monitoring a target KPI associated with the one or more networks. The GUI further includes a sixth user input field where the GUI is configured to receive a sixth user input identifying a vendor of the communications technology for monitoring a target KPI associated with the one or more networks. The GUI further includes a seventh user input field where the GUI is configured to receive a seventh user input identifying a node included in the one or more networks for monitoring a target KPI related to the one or more networks. The first monitoring profile includes a first target KPI between a first KPI peak usage frequency to a first peak usage relationship. The instructions stored in the memory further cause the processor to create a second monitoring profile including: a fourth user input identifying a second target KPI associated with the one or more networks; a fifth user input identifying a second KPI peak usage frequency; and a sixth user input identifying a second peak usage relationship. The instructions stored in the memory further cause the processor to determine whether a stored monitoring profile matching the first monitoring profile has been previously created before the first monitoring profile is created. The instructions stored in the memory further cause the processor to, in response to the first monitoring profile being previously created, further include in the GUI a warning message field configured to present information indicating that the first monitoring profile has been previously created. A fourth user input field is configured to receive a fourth user input selecting a stored monitoring profile matching the first monitoring profile. The instructions stored in the memory further cause the processor to determine whether user permission exists to allow the stored monitoring profile to be monitored.The instructions stored in the memory further cause the processor to create a watchlist that includes each user-created and user-selected monitoring profile. Implementations of the described techniques include hardware, methods or processes, or computer software on a computer-accessible medium.

[0091] One or more computer systems are configured to perform specific operations or actions by installing software, firmware, hardware, or a combination thereof on the system that, when operated, causes the system to perform the action. One or more computer programs are configured to perform specific operations or actions by including instructions that, when executed by the data processing system, cause the system to perform the action. In some embodiments, the method causes the processor to cause a display to output a graphical user interface (GUI). The GUI includes a first user input field configured to receive a first user input identifying a target key performance indicator (KPI) associated with the network. The second user input field is configured to receive a second user input identifying a KPI peak usage frequency. The third user input field is configured to receive a third user input identifying a peak usage relationship. The method further includes creating a first monitoring profile based on a target KPI of the KPI peak usage frequency for the peak usage relationship. Storing the first monitoring profile. Monitoring the target KPI of the KPI peak usage frequency based on the first monitoring profile. Collecting the target KPI data over a period defined by the KPI peak usage frequency.

[0013] Based on the collected target KPI data, determine peak usage for a time period defined by the KPI peak usage frequency. Based on the first monitoring profile, periodically report the peak usage data. Other embodiments of this aspect include corresponding computer systems, systems, and computer programs recorded on one or more computer storage devices, each configured to perform the actions of the method.

[0092] Implementations include one or more of the following features. A method, wherein a first monitoring profile includes a first target KPI during a first KPI peak usage frequency to a first peak usage relationship. The method includes creating a second monitoring profile including a fourth user input identifying a second target KPI associated with one or more networks. A fifth user input identifying the second KPI peak usage frequency. A sixth user input identifying the second peak usage relationship. The method includes determining whether a stored monitoring profile matching the first monitoring profile was previously created before the first monitoring profile is created. The method includes causing a display to output a GUI in response to the first monitoring profile being previously created. The GUI includes a warning message field configured to present information indicating that the first monitoring profile was previously created. A fourth user input field is configured to receive a fourth user input selecting a stored monitoring profile matching the first monitoring profile. The method includes determining whether user permission exists to enable monitoring of the stored monitoring profile in response to the stored monitoring profile being selected. The method includes creating a watchlist that includes each user-created monitoring profile and user-selected monitoring profile. Implementations of the described techniques include hardware, a method or process, or computer software on a computer-accessible medium.

[0093] Some embodiments include a non-transitory computer-readable medium having stored thereon instructions that cause a display to output a GUI. The GUI includes a first user input field configured to receive a first user input identifying a target key performance indicator (KPI) associated with the network. The second user input field is configured to receive a second user input identifying a KPI peak usage frequency. The third user input field is configured to receive a third user input identifying a peak usage relationship. The instructions further include creating a first monitoring profile based on a target KPI of the KPI peak usage frequency for the peak usage relationship; storing the first monitoring profile; monitoring a target KPI of the KPI peak usage frequency based on the first monitoring profile; collecting target KPI data over a period defined by the KPI peak usage frequency; determining peak usage for a period defined by the KPI peak usage frequency based on the collected target KPI data; and periodically reporting the peak usage data based on the first monitoring profile. Other embodiments of this aspect include a corresponding computer system, a system, and a computer program recorded on one or more computer storage devices, each configured to perform the actions of the method.

[0094] Implementations include one or more of the following features: The non-transitory computer-readable medium, wherein the GUI further includes a fourth user input field configured to receive a fourth user input identifying one or more networks for monitoring the target KPIs associated with the one or more networks; The GUI further includes a fifth user input field configured to receive a fifth user input identifying a communications technology for monitoring the target KPIs associated with the one or more networks; The GUI further includes a sixth user input field configured to receive a sixth user input identifying a vendor of the communications technology for monitoring the target KPIs associated with the one or more networks. Implementations of the described technologies include hardware, methods or processes, or computer software on a computer-accessible medium.

[0095] The foregoing outlines features of several embodiments so that those skilled in the art may better understand aspects of the present disclosure. Those skilled in the art will readily appreciate that they may 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 will also appreciate that such equivalent constructions do not depart from the spirit and scope of the present disclosure, and that those skilled in the art will be able to make various changes, substitutions, and alterations herein without departing from the spirit and scope of the present disclosure.

Claims

1. 1. A system comprising: processor, and When executed by the processor, the system: causing a display to output a graphical user interface (GUI), said GUI comprising: a first user input field configured to receive a first user input identifying a target key performance indicator (KPI) associated with the network; a second user input field configured to receive a second user input identifying a KPI peak usage frequency, the KPI peak usage frequency being a frequency at which peak usage of the KPI is monitored; and a third user input field configured to receive a third user input identifying a peak usage relationship, the peak usage relationship being a time period defined by the KPI peak usage frequency; creating a first monitoring profile based on the first user input field, the second user input field, and the third user input field; storing the first monitoring profile; monitoring the target KPI for the KPI peak usage frequency based on the first monitoring profile; collecting target KPI data over the time period defined by the KPI peak usage frequency; determining peak usage for the time period defined by the KPI peak usage frequency based on the collected target KPI data; The system includes a memory storing instructions that cause peak usage data to be periodically reported based on the first monitoring profile.

2. The GUI comprises:

10. The system of claim 1, further comprising a fourth user input field configured to receive a fourth user input identifying one or more networks for monitoring the target KPI associated with the one or more networks.

3. The GUI comprises:

3. The system of claim 2, further comprising a fifth user input field configured to receive a fifth user input identifying a communication technology for monitoring the target KPI associated with the one or more networks.

4. The GUI comprises:

4. The system of claim 3, further comprising a sixth user input field configured to receive a sixth user input identifying a vendor of the communications technology that monitors the target KPIs associated with the one or more networks.

5. The GUI comprises:

5. The system of claim 4, further comprising a seventh user input field configured to receive a seventh user input identifying nodes included in the one or more networks for monitoring the target KPIs associated with the one or more networks.

6. The instructions stored in the memory may cause the system to:

10. The system of claim 1, further comprising determining whether a stored monitoring profile matching the first monitoring profile was previously created before the first monitoring profile was created.

7. The instructions stored in the memory may cause the system to: In response to the first monitoring profile having been previously created, the GUI: a warning message field configured to provide information indicating that the first monitoring profile was previously created; and 7. The system of claim 6, further comprising: a fourth user input field configured to receive a fourth user input selecting the stored monitoring profile that matches the first monitoring profile.

8. The instructions stored in the memory may cause the system to: The system of claim 7 , further comprising determining whether a user is authorized to monitor the stored monitoring profile.

9. The instructions stored in the memory may cause the system to: The system of claim 8 , further comprising creating a watchlist that includes each user-created and user-selected monitoring profile.

10. 1. A method comprising: causing a processor to cause a display to output a graphical user interface (GUI), said GUI comprising: a first user input field configured to receive a first user input identifying a target key performance indicator (KPI) associated with the network; a second user input field configured to receive a second user input identifying a KPI peak usage frequency, the KPI peak usage frequency being a frequency at which peak usage of the KPI is monitored; and a third user input field configured to receive a third user input identifying a peak usage relationship, the peak usage relationship being a time period defined by the KPI peak usage frequency; creating a first monitoring profile based on the first user input field, the second user input field, and the third user input field; storing the first monitoring profile; monitoring the target KPI for the KPI peak usage frequency based on the first monitoring profile; collecting target KPI data over the time period defined by the KPI peak usage frequency; determining peak usage for the time period defined by the KPI peak usage frequency based on the collected target KPI data; periodically reporting peak usage data based on the first monitoring profile.

11. 11. The method of claim 10, further comprising determining whether a stored monitoring profile matching the first monitoring profile was previously created before the first monitoring profile was created.

12. In response to the first monitoring profile having been previously created, causing the display to output the GUI, the GUI comprising: a warning message field configured to provide information indicating that the first monitoring profile was previously created; and 12. The method of claim 11, further comprising: including a fourth user input field configured to receive a fourth user input selecting the stored monitoring profile that matches the first monitoring profile.

13. 13. The method of claim 12, further comprising, in response to the stored monitoring profile being selected, determining whether a user is authorized to monitor the stored monitoring profile.

14. The method of claim 13 , further comprising creating a watchlist that includes each user-created and user-selected monitoring profile.

15. A non-transitory computer-readable medium that, when executed by a processor, causes a system to cause a display to output a graphical user interface (GUI), the GUI comprising: a first user input field configured to receive a first user input identifying a target key performance indicator (KPI) associated with the network; a second user input field configured to receive a second user input identifying a KPI peak usage frequency, the KPI peak usage frequency being a frequency at which peak usage of the KPI is monitored; and a third user input field configured to receive a third user input identifying a peak usage relationship, the peak usage relationship being a time period defined by the KPI peak usage frequency; creating a first monitoring profile based on the first user input field, the second user input field, and the third user input field; storing the first monitoring profile; monitoring the target KPI for the KPI peak usage frequency based on the first monitoring profile; collecting target KPI data over the time period defined by the KPI peak usage frequency; determining peak usage for the time period defined by the KPI peak usage frequency based on the collected target KPI data; A non-transitory computer-readable medium storing instructions for causing peak usage data to be periodically reported based on the first monitoring profile.

16. The GUI comprises:

16. The non-transitory computer-readable medium of claim 15, further comprising a fourth user input field configured to receive a fourth user input identifying one or more networks to monitor for the target KPI associated with the one or more networks.

17. The GUI comprises:

17. The non-transitory computer-readable medium of claim 16, further comprising a fifth user input field configured to receive a fifth user input identifying a communication technology for monitoring the target KPI associated with the one or more networks.

18. The GUI comprises:

20. The non-transitory computer-readable medium of claim 17, further comprising a sixth user input field configured to receive a sixth user input identifying a vendor of the communications technology that monitors the target KPIs associated with the one or more networks.

Images