US5488715A
Expired / Lapsed
US
⏱️ 0.0 years remaining
Process for integrated traffic data management and network surveillance in communications networks
Assignee: AT&T Inc
•
Filing: 1994-08-01
•
Granted: 1996-01-30
•
Expires: 2014-08-01
Abstract
Abstract The dual operations of traffic data analysis and network surveillance in a telecommunications network are integrated to allow maintenance personnel to readily assess the impact of network element problems on the level of service. More specifically, the present invention utilizes traffic data measurements to monitor the level of service provided by various network components. By utilizing real-time or near real-time traffic data in this manner, switch maintenance activities may be prioritized so that, for example, equipment malfunctions having the greatest impact on the level of service may receive attention before those having little or no impact on service.
Inventors
- 👤 Paul F. Wainwright
Bibliographic Details
Application Number
—
Jurisdiction
US
Data Source
google_patents
Last Synchronized
2026-10-28 14:14
CPC Classifications
H; H04; H04Q; H04Q3/00; H04Q3/0016; H04Q3/0062; H04Q3/0075; H04L; H04L41/00; H04L41/14; H04L41/142; H04L43/00; H04L43/08; H04L43/0876; H04M; H04M3/00; H04M3/22; H04M3/2254; H04M3/36; H04L41/02; H04L41/024; H04L41/50; H04L41/5003; H04L41/508; H04L41/5087; H04Q2213/00; H04Q2213/13521; H04Q2213/13522; H04Q2213/13525; H04Q2213/13543; H04Q2213/13545
Claims Analysis
Total Claims: 12
Claim 1
Independent Claim
221 words
A method for prioritizing maintenance problems in a communications network having a plurality of network elements, comprising: interfacing with the network elements to gather in real-time and at predetermined time intervals, traffic data corresponding to measured levels of utilization of the plural network elements; storing said gathered traffic data in a database for subsequent analysis by network planners; processing said stored traffic data by comparing utilization level measurements obtained during said interfacing step with a predetermined range of acceptable values in order to detect first and second measurements outside of said predetermined range; said processing step generating first and second traffic data exception messages corresponding to first and second detected measurements outside of said range, said first traffic data exception message indicative of a first traffic abnormality having a first traffic affecting severity level, and said second traffic data exception message indicative of a second traffic abnormality having a second traffic affecting severity level; comparing, in said processing step, said first traffic affecting severity level to said second traffic affecting severity level and generating a comparison output; and outputting to a message center said first and second traffic data exception messages along with a representation of the traffic affecting severity levels associated therewith and said comparison output, so as to provide maintenance personnel with a priority of maintenance problems requiring repair.
Claim 2
Independent Claim
221 words
A method for prioritizing maintenance problems in a communications network having a plurality of network elements, comprising: interfacing with the network elements to gather in real-time and at predetermined time intervals, traffic data corresponding to measured levels of utilization of the plural network elements; storing said gathered traffic data in a database for subsequent analysis by network planners; processing said stored traffic data by comparing utilization level measurements obtained during said interfacing step with a predetermined range of acceptable values in order to detect first and second measurements outside of said predetermined range; said processing step generating first and second traffic data exception messages corresponding to first and second detected measurements outside of said range, said first traffic data exception message indicative of a first traffic abnormality having a first traffic affecting severity level, and said second traffic data exception message indicative of a second traffic abnormality having a second traffic affecting severity level; comparing, in said processing step, said first traffic affecting severity level to said second traffic affecting severity level and generating a comparison output; and outputting to a message center said first and second traffic data exception messages along with a representation of the traffic affecting severity levels associated therewith and said comparison output, so as to provide maintenance personnel with a priority of maintenance problems requiring repair.
Claim 3
Dependent Claim
47 words
The method according to claim 1, wherein said processing step further comprises: utilizing one of said first and second traffic data exception messages to identify in at least one of the network elements, at least one malfunction having an impact upon service to subscribers of the network.
Claim 4
Dependent Claim
72 words
The method according to claim 1, wherein said processing step comprises: utilizing, one of said first and second traffic data exception messages to identify at least one malfunctioning network element; and associating one of said first and second traffic data exception messages with the malfunctioning network element for use in evaluating an impact on subscriber service as a result of a malfunctioning network element and maintenance activities on plural malfunctioning network elements.
Claim 5
Dependent Claim
21 words
The method of claim 3, wherein said processing step further comprises receiving network element failure messages indicative of detected equipment malfunctions.
Claim 6
Dependent Claim
35 words
The method of claim 4, wherein said outputting step includes displaying an alarm in response to at least one of a network element failure message and said first and said second traffic data exception messages.
Claim 7
Dependent Claim
38 words
The method of claim 1, wherein said interfacing step comprises gathering summary data collected during said predetermined intervals by at least one of the network elements said summary data being indicative of subscriber usage of a telecommunication service.
Claim 8
Dependent Claim
14 words
The method of claim 1, wherein said predetermined time intervals are thirty minute intervals.
Claim 9
Dependent Claim
25 words
The method of claim 1, wherein one of said measured levels of utilization is a number of failures encountered by at least one network element.
Claim 10
Dependent Claim
25 words
The method of claim 1, wherein one of said measured levels of utilization is a number of events encountered by at least one network element.
Claim 11
Dependent Claim
30 words
The method of claim 1, wherein one of said measured levels of utilization is an amount of time that at least one network element is in use during an interval.
Claim 12
Dependent Claim
21 words
The method of claim 1, wherein said outputting step includes displaying an alarm in response to a traffic data exception message.
References Cited (Backward Citations)
US4200771A
Cited
US4319090A
Cited
US4456788A
Cited
US4464543A
Cited
US4669113A
Cited
US4959849A
Cited
US5042064A
Cited
US5223827A
Cited
US5285494A
Cited
USPTO Annuity & Maintenance Windows
| Annuity Stage | Window Opens | Payment Deadline | Surcharge Period Until | Estimated Fee | Status |
|---|---|---|---|---|---|
| 3.5 Years (Year 4) | 1999-01-29 | 1999-07-31 | 2000-01-30 | $2000.00 | Window Closed / Lapsed |
| 7.5 Years (Year 8) | 2003-01-29 | 2003-07-31 | 2004-01-30 | $3760.00 | Window Closed / Lapsed |
| 11.5 Years (Year 12) | 2007-01-29 | 2007-07-31 | 2008-01-30 | $7700.00 | Window Closed / Lapsed |