The invention relates to connection resource management in telecommunication systems, and more particularly to monitoring and display of node resources in such systems.
Connection oriented network elements such as Asynchronous Transfer Mode switches have a number of resources. Resources have a maximum capacity and a utilization. Examples of resources are: traffic limited call admission control resources, such as bandwidth within an OC3 link or internal capacity within a line card; connection limited call admission control resources, such as the number of connection end points per line card; path identifications, such as VPI, VCI, and MPLS label ranges; and system limits, such as memory within the switch, number of leafs per system, number of connections per system, and number of connections in a connecting state (i.e. connections being set-up). Each of these and other resources are limited within a switch, each having a maximum capacity. The maximum capacity can be further limited when interfacing with other vendors' switches which support a lower number of connections. For example, a lower range of VPIs may be required that would otherwise be supportable by the switch.
Traffic through a connection oriented switch, both in terms volume of traffic and number of connections, is limited by the capacity of the various resources. It is therefore important for diagnostic and monitoring purposes that an operator be able to determine utilization of the resources. Typically, the operator issues a command line interface (CLI) command to a management layer within the network element, asking for the utilization of a particular resource. The management layer queries a connection resource tracker, which determines the utilization of the resource. The connection resource tracker may determine the utilization by querying other components within the network element. The connection resource tracker reports the utilization of the resource to the management layer, which relays the utilization to the operator.
When a problem arises within a network, such as repeated call connection blockage or unwanted call cancellations, the operator typically queries each network element for resource utilization. Even in the absence of such a problem, the operator may want to monitor resource utilization to identify potential bottlenecks. The operator issues a separate CLI command for each resource in turn for each network element. Given the large number of resources used by a network element, this is a time consuming and inefficient process. Even if a script is used to retrieve the utilization of all resources, the amount of information which the operator must then process is cumbersome. Furthermore, by the time the operator queries utilization of the problematic resource, or even begins searching for the problem, the resource utilization may have changed and the source of the problem may no longer be apparent. A system which allowed resource shortages to be flagged to an operator automatically, or to alert an operator of resources approaching their maximum capacity, would allow speedier diagnostics and more convenient monitoring of connection oriented switches.
In accordance with one aspect of the invention, a method is provided for monitoring resource utilization within a connection oriented switch, comprising the steps of: providing at least one utilization threshold; for each of a plurality of resources, each corresponding to one of the at least one utilization threshold, determining whether a utilization of the resource is above the corresponding utilization threshold; and identifying each resource for which the utilization is above the corresponding utilization threshold. A report may be generated including any identified resources, and the report may be presented to an operator. Upon identification of a resource for which the utilization is above the corresponding utilization threshold, an alarm may be generated identifying the resource, and the alarm may be presented to the operator. In one embodiment, receipt of call connection establishment signals is monitored, and determination of a resource for which utilization is above the corresponding utilization threshold is only made upon receipt of a call connection establishment signal, as is identification of each such resource.
In accordance with another aspect of the invention, a method is provided for monitoring resource utilization within a connection oriented switch, comprising the steps of: providing at least one utilization threshold; for each of a plurality of resources, each corresponding to one of the at least one utilization threshold, determining whether a utilization of the resource is below the corresponding utilization threshold; and identifying each resource for which the utilization is below the corresponding utilization threshold. A report may be generated including any identified resources, and the report may be presented to an operator.
Processors and computer readable media are provided for implementing the methods summarized above.
The method and network elements of the present invention allow resource utilization to be monitored in a timely manner that is useful to an operator. The operator can determine quickly which resources are approaching maximum capacity, or alternatively which resources are being underutilized, without having to sift through an overwhelming amount of information. An alarm system can also be implemented, alerting an operator when utilization of any resource is approaching a critical level.
The features and advantages of the invention will become more apparent from the following detailed description of the preferred embodiment(s) with reference to the attached figures, wherein:
It will be noted that in the attached figures, like features bear similar labels.
Referring to
Associated with each network element 10 is a plurality of resources. Examples of resources are bandwidth, line card capacity, number of connection end points supportable per line card, Virtual Path Identifier (VPI) ranges, Virtual Channel Identifier ranges, MultiProtocol Label Switching (MPLS) label ranges, memory within the switch, number of supportable leaf endpoints per system, number of supportable connections in a connecting state, number of MPLS state blocks, and number of connections stored in a database. Each resource has a utilization and a capacity. The utilization of a resource measures how much of the resource is currently in use or reserved for use. The capacity of a resource measures the total availability of the resource. The utilization is expressible as a percentage of the capacity. As an example of a utilization and a capacity, VPIs in some switches may be take values within a range of 0 to 255. If 205 virtual paths have been set up through the switch, the VPI utilization would be 80%.
Referring to
The connection resource tracker 32 maintains a partial database of resource utilization, the contents of which are changed upon receipt of call clear messages 34 and call connection attempt messages 36. When the management layer 30 receives an operator request 38, for example from an operator via the network management tool 18, the management layer 30 generates a query 40 in response thereto. The management layer 30 sends the query 40 to the connection resource tracker 32, which then consults its database and queries other standard components (not shown in
Referring to
At step 52 the connection resource tracker reads a list of resources. The list of resources may be read in a number of ways. As examples, the connection resource tracker could read the list of resources from a database, could access the list of resources from memory (including hardcoded values), or could read the list of resources from a signal sent by an operator. In the latter case, the steps 50, 51, and 52 could be combined into a single step of prompting the connection resource tracker by sending a utilization threshold and a list of resources. Alternatively, the steps 50 and 52 could be combined into a single step of prompting the connection resource tracker by sending a list of resources, the utilization threshold being received at step 51 by some other means.
At step 53 the connection resource tracker attempts to select a next resource in the list of resources, which in the case of the first iteration will be a first resource in the list of resources. If a next resource exists at step 53, the connection resource tracker 32 determines at step 54 whether the utilization of that resource expressed as a percentage of the capacity of that resource is above the utilization threshold received at step 51. Determining the capacity and utilization of each resource is a capability already present in existing ATM switches and other connection oriented network elements.
If at step 54 the connection resource tracker 32 determines that the utilization of the resource is above the utilization threshold, then at step 56 the connection resource tracker 32 identifies the resource and adds an identification of the resource to a report. The connection resource tracker 32 may also add the actual utilization of the resource, either in absolute terms or as a percentage of capacity, to the report. Once an identification of the resource has been added to the report, or if the connection resource tracker 32 determines at step 54 that the utilization of the resource is not above the utilization threshold, then the connection resource tracker 32 attempts to select a next resource at step 53. The connection resource tracker 32 determines whether the utilization of each resource in turn is above the utilization threshold, until no more resources are found at step 53. At step 58, the connection resource tracker sends the report to the management layer 30.
Referring to
At step 72 the connection resource selects a first resource in the list of resources. The connection resource tracker 32 determines at step 74 whether the utilization of the selected resource expressed as a percentage of the capacity of that resource is above the utilization threshold. If the utilization is above the utilization threshold, the connection resource tracker 32 generates an alarm identifying the resource and possibly indicating the actual utilization of the resource. The alarm is a particular example of a report. Generation of the alarm at step 76 is similar to the steps 56 and 58 of
Once an alarm has been generated, or if the utilization of the resource was not above the utilization threshold at step 74, then the connection resource tracker 32 attempts to select a next resource at step 78. If a next resource exists at step 78, the connection resource tracker 32 determines at step 74 whether the utilization of that resource expressed as a percentage of the capacity of that resource is above the utilization threshold. The connection resource tracker 32 determines whether the utilization of each resource in turn is above the utilization threshold, until no more resources are found at step 78. Once the connection resource tracker 32 has determined the utilization of each resource, the connection resource tracker 32 pauses at step 80 for a configured length of time before beginning again with the first resource at step 72. The configured length of time will depend on how often an administrator or operator wishes the utilization of resources to be checked, and may in fact be equal to zero.
Referring to
Referring to
The timer need not be used, in which case the steps of determining whether a timer has expired and of resetting the timer are omitted from
Referring to
If the connection resource tracker determines at step 74 that the utilization of a resource is above the specified threshold, the resource tracker determines at step 90 whether a flag associated with the resource indicates that an alarm has recently been generated for that resource. If the flag does not indicate that the alarm has recently been set, then the connection resource tracker generates an alarm at step 76 as described above, and sets the flag at step 92 to indicate that an alarm has recently been generated for the resource. If the connection resource tracker determines at step 90 that the flag does indicate that the alarm has recently been set, then an alarm is not generated. If the connection resource tracker determines at step 74 that the utilization of the resource is not above the specified threshold, then at step 94 the connection resource tracker clears the flag so that the flag indicates that an alarm has not recently been generated for the resource. In this way, the connection resource tracker will not repeatedly generate alarms for a resource as new call connections are established, but rather will wait until the utilization of the resource falls below the threshold before considering whether to generate a new alarm.
The method described above with reference to
The method has been described as monitoring for resource utilization which exceeds a utilization threshold. Alternatively, the connection resource tracker can be configured to monitor for resource utilization which falls below a utilization threshold by changing the steps 54 and 74 to determination of whether the utilization of a resource falls below a specified threshold. If this threshold is set at a low value, an operator can locate any resources which are being underutilized. This embodiment is particularly applicable to the method described above with reference to
The invention has been described as using a single threshold, expressed as a percentage of capacity, for all connection resources being monitored. Alternatively, each connection resource being monitored may have a respective utilization threshold. This allows different thresholds to be set for different connection resources, and also allows the thresholds to be expressed in absolute terms rather than as a percentage of capacity of the resource. However, the step 51 of receiving the threshold must then receive a threshold for each connection resource being monitored.
The invention has been described as considering whether the utilization of each resource is above or below a threshold. Alternatively, the connection resource tracker could determine whether the utilization of each resource is greater than or equal to a threshold, or whether the utilization of each resource is less than or equal to a threshold.
The embodiments presented are exemplary only and persons skilled in the art would appreciate that variations to the above described embodiments may be made without departing from the spirit of the invention. For example, methods which are logically equivalent or similar to the methods shown in
Number | Name | Date | Kind |
---|---|---|---|
5063523 | Vrenjak | Nov 1991 | A |
5223827 | Bell et al. | Jun 1993 | A |
5673253 | Shaffer | Sep 1997 | A |
5796633 | Burgess et al. | Aug 1998 | A |
6026440 | Shrader et al. | Feb 2000 | A |
6088688 | Crooks et al. | Jul 2000 | A |
6097722 | Graham | Aug 2000 | A |
6260062 | Davis et al. | Jul 2001 | B1 |
6289017 | Shani et al. | Sep 2001 | B1 |
6834304 | Nisbet et al. | Dec 2004 | B1 |
7000013 | Mei et al. | Feb 2006 | B2 |
7143153 | Black et al. | Nov 2006 | B1 |
7434109 | Stabile et al. | Oct 2008 | B1 |
20020039352 | El-Fekih et al. | Apr 2002 | A1 |
20020138599 | Dilman | Sep 2002 | A1 |
20020147759 | Ranganathan | Oct 2002 | A1 |
20020178385 | Dent et al. | Nov 2002 | A1 |
20030046396 | Richter et al. | Mar 2003 | A1 |
20040024859 | Bloch et al. | Feb 2004 | A1 |
20040030537 | Barnard | Feb 2004 | A1 |
20040044757 | Baker | Mar 2004 | A1 |
20050027842 | Kline | Feb 2005 | A1 |
20060153174 | Towns-von Stauber et al. | Jul 2006 | A1 |
Number | Date | Country |
---|---|---|
1244248 | Sep 2002 | EP |
9829984 | Jul 1998 | WO |
9732448 | Sep 2007 | WO |
Entry |
---|
European Search Report dated Dec. 15, 2010. |
Number | Date | Country | |
---|---|---|---|
20050091363 A1 | Apr 2005 | US |