System and method for network capacity engineering

A system for managing network capacities is disclosed. The system comprises a processor implementing a data collection module configured to collect a plurality of capacity utilization data. The processor also implements a capacity analysis module configured to produce an actual capacity utilization map using the plurality of capacity utilization data. The capacity analysis module is also configured to produce a projected capacity utilization map using a plurality of designed node and link capacities, and a plurality of capacity engineering constraints. The processor also implements a simulation module configured to simulate a network management action and to produce simulated capacity utilization maps. The processor also implements a network management action module configured to suggest network management actions based on the actual capacity utilization map and the projected capacity utilization map and to rank the one or more network management actions based on the one or more simulated capacity utilization maps.

CROSS-REFERENCE TO RELATED APPLICATIONS

Not applicable.

Not applicable.

REFERENCE TO A MICROFICHE APPENDIX

Not applicable.

BACKGROUND

A network operator may operate multiple networks, including fixed networks and wireless networks. A network may include a large number of network nodes and network links. Examples of the network nodes may include a switch in a public switched telephone network (PSTN), a router in an IP network, a mobile switching center (MSC) in a wireless network, a base station in a wireless access network, and an application server in any of the mentioned networks, among many others. Examples of the network links may include copper wire, fiber lines and air interface for the wireless network. A network node may have a design capacity. For example, the capacity of a switch in the PSTN network may be a maximum number of calls the switch may carry during a fixed period of time. The capacity of a router in an IP network may be a throughput of packets. A link may have a design capacity. For example, a T-carrier 1 (T1) of copper wire may have a transmission capacity of about 1.55 mbps, and an optical carrier 3 (OC3) may have a transmission capacity of about 155 mbps.

Network nodes and links may be expensive investments for a network operator. It may happen from time to time that some of the nodes and links are over utilized and other nodes and links are underutilized. This may happen because network traffic patterns may change over time, and a current network configuration may change over time as well. The network traffic pattern changes may include a shift of traffic from one part of the network to another part of the network, and an addition of new traffic to some part of the network, for reasons such as an offering of new wireless service. The network configuration change may include addition of new nodes or links and decommissioning of existing nodes or links, among others. In addition to large investment in the network nodes and network links, a specialized group of engineering staff may be dedicated to operating, monitoring and maintaining a network node or part of the network.

SUMMARY

In one embodiment, a system for managing network capacities is provided that comprises a processor implementing a data collection module and a capacity analysis module. The data collection module is configured to collect a plurality of capacity utilization data. The capacity analysis module is configured to produce an actual capacity utilization map using the plurality of capacity utilization data. The capacity analysis module is also configured to produce a projected capacity utilization map using a plurality of designed node capacities, a plurality of designed link capacities, and a plurality of capacity engineering constraints. The processor also implements a simulation module and a network management action module. The simulation module is configured to simulate a network management action and to produce one or more simulated capacity utilization maps. The network management action module is configured to suggest one or more network management actions based on the actual capacity utilization map and the projected capacity utilization map. The network management action module is also configured to rank the one or more network management actions based on the one or more simulated capacity utilization maps.

In a second embodiment, a method for managing network resources is provided that comprises collecting a plurality of capacity utilization data from a plurality of network nodes, producing and displaying one or more actual capacity utilization maps using the plurality of capacity utilization data. The method also comprises producing and displaying one or more projected capacity utilization maps using one or more link design capacities, one or more node design capacities, and one or more network capacity engineering constraints. The method also includes suggesting one or more network management actions based on the one or more actual capacity utilization maps and one or more projected capacity utilization maps, simulating the one or more network management actions to produce one or more simulated capacity utilization maps, and ranking the one or more network management actions.

In a third embodiment, a system is provided that comprises a plurality of network nodes configured with one or more capacity reporting modules (CRMs). The system also includes a network capacity management system that is configured to receive a plurality of capacity utilization data from the one or more CRMs and to produce one or more actual capacity utilization maps using the plurality of capacity utilization data. The network capacity management system is also configured to produce one or more projected capacity utilization maps using one or more design network capacities and one or more capacity engineering constraints. The network capacity management system is also configured to suggest one or more network management actions based on the one or more actual capacity utilization maps and the one or more projected capacity utilization maps. The network capacity management system is also configured to evaluate a network management action by simulating the network management action and by producing one or more simulated capacity utilization maps. The network capacity management system is further configured to take one or more network management actions based on the simulated capacity utilization maps.

DETAILED DESCRIPTION

The method and system of the present disclosure may provide one or more network-wide views of traffic load and capacity utilizations. The method and system may promote trending the capacity utilization data, simulating a network management action to evaluate the effect of the action before the action is actually taken, and suggesting and ranking one or more network management actions based on the results of the trending and the simulation. The method and system of the present disclosure may promote a self-healing network management by allowing a management system to take a network management action proactively based on the simulation results or in response to a network event such as detecting an over utilized network node or network link. In some embodiments, the system may take the network management action without human intervention.

FIG. 1illustrates an embodiment of multiple networks100. The networks100comprise a wireless network110, a fixed network120, an interconnecting network112, and a network traffic management system200. The wireless network110and fixed network120may belong to one carrier and may be managed by the network capacity network management system200. In other embodiments, the wireless network110, the fixed network120, and the network capacity network management system200may belong to different carriers.

The wireless network110may include a set of network nodes125, which may in turn include a capacity reporting module (CRM)127, and a set of network links129. The examples of the network nodes125may include mobile switching center (MSC), wireless media gateways (WMGs), and base stations. The network nodes may be interconnected by the network links129. Examples of the network links129may include transmission links T-carriers such as T1, and T3, and optical carriers such as OC1 and OC3 with varying capacities. T1, for example, may have about a 1.5 megabit per second (mbps) transmission capacity, and OC3 may have about a 155.5 mbps transmission capacity.

The fixed network120may also include network nodes125, which in turn may include one or more CRM127, and network links129. The examples of the fixed network nodes may include routers, switches, and transmission nodes, among others. The network nodes125, similar to the wireless network nodes, are interconnected by the network links129. Examples of the network links may include the transmission link T1, T3, OC1, OC3, and OC12, among others. The fixed network nodes may form a hierarchy or may have a flat organization, depending on the network technology in use. A PSTN network, for example, may have a hierarchical organization including a local access network at the bottom of the hierarchy, and a number of tandem switching nodes interconnecting local access network nodes. An IP network, on the other hand, may have a flat organization, with routers interconnecting with each other at one level.

Network nodes125of the wireless network110and the fixed network120may both have capacity reporting modules (CRM)127. Each of the CRMs127may report to the network traffic management system200the node capacity utilization data and link capacity utilization data. The interconnecting network112may interconnect more than one managed networks, but may not be managed itself by the same network management system such as the network traffic management system200.

The network traffic management system200is a network management system that may be centrally located and may connect to or be in communication with the managed wireless network110and the fixed network120via direct lines or the interconnecting network112. The network traffic management system200may monitor the managed networks110and120, collect capacity utilization data from the network nodes125by communicating with the CRMs127on the network nodes125, analyze and trend the capacity utilization data, suggest network management actions based on the analysis, and simulate a network management action on the network110or120before the network management action is taken.

FIG. 2illustrates an embodiment of the network traffic management system200. The network traffic management system200may include a network monitoring module201, a data collection module203, a capacity analysis module205, a simulation module207, a network management action module209, and a network resource database220.

The network monitoring module201may be configured to monitor of the network nodes125and the network links129of the managed wireless network110and the managed fixed network120. The network monitoring module201may monitor network events such as alarms, network resource usages, traffic reporting, among others, without taking an action. The monitoring may be done in a real time manner, a non-real-time manner, or a combination of the two. Real time monitoring refers to the monitoring that is performed in a time frame that typically has negligible perceivable delay. Non-real-time monitoring may be done offline or at a scheduled time, for example in batches.

The data collection module203, coupled with the network monitoring module201, may collect, filter, organize, and store into the network resource database220the network capacity utilization data. The data collection may take place at the same time as the network monitoring module201and may be done in a real-time manner or a non-real-time manner. The data collection module203may communicate with one of the CRMs127to collect the capacity utilization data of one of the network nodes125and one of the network links129. The data collection module203may obtain traffic load data first in order to get the capacity utilization. The capacity utilization may be obtained as a ratio of a measured traffic load to the design capacity of the network node125or the network link129. The capacity utilization for a switch in the fixed network120, for example, is the ratio of the measured busy hour call attempts (BHCA) to the design capacity of BHCA. The data collection module203may get a traffic load data directly from a CRM127in some cases, and in some other cases, may calculate the measured traffic load. In case of a traffic load for a switch in the fixed network120, the data collection module203may need to accumulate the call numbers for a specified period of time in order to obtain the BHCA, if the BHCA data is not directly available from the switch node.

The simulation module207may be configured to simulate one or more network management actions. The simulation module207may first use a simulator to simulate the wireless network110and the fixed network120. The simulated network nodes and network links may have design capacities and actual capacity utilizations. The simulation module207may then take one or more network management actions in the simulated network, collect simulated capacity utilization data on the simulated network, and produce a simulated capacity utilization map. The simulated capacity utilization map may represent a network-wide view of capacity utilizations in the simulated network after the network management actions are taken.

The network management action module209may suggest one or more network management actions based on the actual capacity utilization map and the projected capacity utilization map. The network management action module209may compare the actual capacity utilization map with the projected capacity utilization map to identify potential areas for network management actions. For example, the comparison may reveal that some network nodes125and network links129may be over utilized, and some other nodes125and links129may be underutilized. Some nodes125or links129may be a bottleneck for the overall traffic flows. Then one or more network management actions may be suggested based on the comparison. For example, some network trunks may be reallocated among one or more nodes. The network management action module209may collaborate with the network simulation module207to evaluate the overall impact and effectiveness of one or more network management actions by producing one or more simulated capacity utilization maps. Based on the simulated capacity utilization maps, the network management action module209may rank alternative network management actions to help an operator make a decision on which network management action to take.

The network management action module209may have a dashboard211to present to the operator the actual capacity utilization map, the projected capacity utilization map, one or more simulated capacity utilization maps, and the set of alternative network actions ranked in an order of preference. The dashboard211may provide the operator with a one-glance view of the actual capacity utilization map (ACUM)217, the projected capacity utilization map (PCUM)219, and the simulated capacity utilization map (SCUM)215. The network management action module209may have a user interface (UI) to allow the operator to take management actions such as adding a link129, decommissioning a link129, and moving a network node125. The dashboard211may present information to the operator by displaying the information or by printing the information to the operator or by some other presentation mechanism.

The network resource database220may be configured to store network node records and network link records. A record or an entry for the network node125, for example, may include a node ID field, a node design capacity field, a node actual capacity utilization field, a node location field, a neighboring nodes field, and a capacity engineering constraint field, among others. A record or an entry for the network link129may include a link ID field, a link design capacity field, a link actual capacity utilization field, a link location field, a connecting nodes field, and a capacity engineering constraint field, among others. The network resource database220may be implemented using an object-oriented database, a relational database, or other current or future database technologies.

FIG. 3illustrates an embodiment of a method300for managing network-wide capacities. The method300may include monitoring network nodes125and network links129for capacity utilization data at block303, collecting the capacity utilization data125at block305, and producing one or more actual capacity utilization maps at block307. The method also includes modeling and projecting capacity utilization by producing one or more projected capacity utilization maps at block309, suggesting one or more network management actions at block311, evaluating the network management actions at block313, and ranking the network management actions at block315.

The block303shows monitoring the network nodes125and the network links129for capacity utilization data. This may include watching for network events and initiating data collection when a capacity utilization related event is detected. The monitoring may be done in real time or non-real-time manner. Real time monitoring may be done on a periodic basis with negligible delay. Non-real-time monitoring may be done offline or at a scheduled time.

The block305shows collecting the plurality of capacity utilization data. The type of capacity utilization data depends on type of the capacity. This may include collecting the capacity utilization data for the network nodes125and the network links129, and filtering, organizing, and storing the capacity utilization data. Collecting the capacity utilization data may involve polling or receiving the data from a capacity reporting module, such as a CRM127on a network node125. Filtering the collected data may involve identifying and discarding the data noise such as a sudden, abnormal spike of data points. Organizing the collected data may involve collapsing multiple data points into an aggregate data point by averaging the data points over a specified period of time. For example, in order to obtain the capacity utilization for a switch in the fixed network120, a ratio of the measured BHCA to the design capacity of BHCA may be obtained. A number of traffic load data points may be obtained first and then averaged over the specified period of time to get measured BHCA. Then ratio of the measured BHCA to the design capacity of BHCA may be calculated. Storing the data may involve storing the data into a database such as the network resource database220. The data collection may take place at the same time as the network monitoring and may be done in either a real-time or a non-real-time fashion.

The block307shows producing one or more actual capacity utilization maps. This may include analyzing the collected capacity utilization data and generating one or more actual capacity utilization maps. Analyzing the collected utilization data may involve mapping a utilization data to a network node125or a network link129, and detecting those nodes or links that have capacity utilizations going over a normal range. Generating an actual capacity utilization map involves connecting the network nodes125and network links129together to provide a network-wide view of the capacity utilization for a specified date. An additional actual capacity utilization map may be generated using a set of capacity utilization data of a different date. The actual capacity utilization map may be represented as a graph, a table or other forms, depending on the design choice. The actual capacity utilization maps may be displayed to an operator or manager, for example using the dashboard211. The displaying may take the form of showing the actual capacity utilization maps on a display screen, by printing the capacity utilization maps, or by some other presentation mechanism.

The block309shows modeling and projecting network-wide capacity utilization. This may include using network node design capacities and network link design capacities, applying capacity engineering constraints, and generating and/or producing one or more projected capacity utilization maps. Using a node design capacity may involve mapping the design capacity to a network node125or a network link129. Applying network capacity engineering constraints may involve applying one or more capacity engineering constraints to the network node125or the network link, if applicable to obtain an ideal or theoretically optimal capacity utilization for the network node125or the network link129. Generating and/or producing a projected capacity utilization map may involve connecting together the network nodes125and network links129along with projected capacity utilization to produce a network-wide view of the projected capacity utilization. Generating a projected capacity utilization map may also involve using historical capacity utilization data to verify and revise the projected utilization map as described above. The historical capacity utilization data may be obtained from the network resource database220or from another source. The projected capacity utilization maps may be displayed to an operator or manager, for example using the dashboard211. The displaying may take the form of showing the projected capacity utilization maps on a display screen, by printing the projected capacity utilization maps, or by some other presentation mechanism.

The block311shows suggesting one or more network management actions. Suggesting one or more network management actions may include comparing the actual capacity utilization map with a projected capacity utilization map and identifying the area for network management actions. Comparing the actual capacity utilization map with the projected capacity utilization map may reveal that some network nodes and network links are over utilized, and some other nodes and links are underutilized. Some links or nodes may be a bottleneck of the overall traffic flows. Identifying the area for network management actions may involve identifying the over utilized and underutilized network nodes and links and suggesting alternative network management actions. The alternative network management actions may include that the underutilized nodes or links may be moved to the area where the node or links are over utilized and some over utilized nodes or links may be replaced with nodes or links with larger capacities.

The block313shows evaluating a network management action by simulation. This may include simulating a network, taking a network management action on the simulated network, and generating a simulated capacity utilization map. Simulating a network may involve using a network simulator to build a network such as the wireless network110and the fixed network120. The simulated network nodes and network links may have design capacities and actual capacity utilizations. Taking the network management action on the simulated network may involve carrying out the network management action on the simulated network to produce simulated capacity utilizations for the network nodes and network links in the simulated network. Generating a simulated capacity utilization map may involve collecting the simulated capacity utilization data and connecting together the simulated network nodes and network links, along with the simulated capacity utilization data, to produce a network-wide view of the simulated capacity utilizations. The simulated capacity utilization map may represent a network-wide view of capacity utilizations in the simulated network after the network management actions are taken.

The block315shows ranking the alternative network management actions. The suggested network management actions may be evaluated as described earlier, and then ranked in an order of preference to help a network operator make a decision. Ranking the network management actions may involve identifying a set of evaluation criteria that may be defined by the operator, obtaining one or more simulated capacity utilization maps by running the simulation module207, and prioritizing the alternative network management actions according to the operator-defined criteria and the simulated capacity utilization maps. Identifying a set of evaluation criteria may include assigning weights to one or more network management actions to accommodate some special circumstances. For example, when cost of leased links are favorable to the network operator because of a special discount offer, the management action of adding leased links may have more weight than moving some underutilized links from one part of the network to another part of the network for a specified period of time. Other criteria may include maintaining a quality of service, satisfying reliability requirements, and others.

The system described above may be implemented on any general-purpose computer with sufficient processing power, memory resources, and network throughput capability to handle the necessary workload placed upon it.FIG. 4illustrates a typical, general-purpose computer system suitable for implementing one or more embodiments disclosed herein. The computer system480includes a processor482(which may be referred to as a central processor unit or CPU) that is in communication with memory devices including secondary storage484, read only memory (ROM)486, random access memory (RAM)488, input/output (I/O) devices490, and network connectivity devices492. The processor may be implemented as one or more CPU chips.

The secondary storage484is typically comprised of one or more disk drives or tape drives and is used for non-volatile storage of data and as an over-flow data storage device if RAM588is not large enough to hold all working data. Secondary storage584may be used to store programs which are loaded into RAM488when such programs are selected for execution. The ROM486is used to store instructions and perhaps data which are read during program execution. ROM486is a non-volatile memory device which typically has a small memory capacity relative to the larger memory capacity of secondary storage. The RAM488is used to store volatile data and perhaps to store instructions. Access to both ROM486and RAM488is typically faster than to secondary storage484.

The processor482executes instructions, codes, computer programs, scripts which it accesses from hard disk, floppy disk, optical disk (these various disk based systems may all be considered secondary storage484), ROM486, RAM488, or the network connectivity devices492.