← Back to Patent Explorer
US6556659B1 Expired / Lapsed US ⏱️ 0.0 years remaining

Service level management in a hybrid network architecture

Assignee: Accenture Global Services Ltd
•
Filing: 1999-06-02
•
Granted: 2003-04-29
•
Expires: 2019-06-02
📄 Original PDF 🌐 Google Patents 🔄 Sync Now

Abstract

Abstract A Service Level Management system is provided. A notification of a service level problem within a combination packet-switching and circuit-switching hybrid network is received by the system. The service level agreement is retrieved and the problem is checked against the agreement to determine if the agreement has been met. The notification of the problem is prioritized with a second notification of a second service level problem based on a number of times the agreement has not been met. Next, a resolution for the service level problem within the hybrid network is determined. The resolution may include a status report, resolution notification, problem reports, service reconfiguration, trouble notification, service level agreement violations, and/or outage notification. The progress of the implementation of the resolution is tracked. Finally, the hybrid network is managed based on the future predicted behavior of the network.

Inventors

  • 👤 Michel K. Bowman-Amuah

Bibliographic Details

Application Number —
Jurisdiction US
Data Source google_patents
Last Synchronized 2026-10-25 05:22
CPC Classifications
H; H04; H04L; H04L12/00; H04L12/64; H04L12/6418; H04L12/02; H04L12/14; H04L12/1403; H04L12/1432; H04L12/1439; H04L12/1453; H04L12/1482; H04L12/1485; H04L12/1496; H04L41/00; H04L41/06; H04L41/0654; H04L41/50; H04L41/5003; H04L41/5009; H04L43/00; H04L43/08; H04L43/0805; H04L43/0817; H04M; H04M15/00; H04M15/41; H04M15/49; H04M15/58; H04Q; H04Q3/00; H04Q3/0016; H04Q3/0062; H04Q3/0075; H04L43/0876; H04L43/10; H04L43/16; H04M2215/00; H04M2215/01; H04M2215/0164; H04M2215/0188; H04M2215/46

Claims Analysis

Total Claims: 15
Claim 1
Independent Claim 175 words
A method for service level management in a hybrid network architecture, comprising the steps of: a) receiving notification of a service level problem within a hybrid network, wherein the hybrid network is a combination packet-switching and circuit-switching network; b) retrieving a service level agreement; c) checking the service level problem against the service level agreement to determine if the service level agreement has been met; d) prioritizing the notification of the service level problem with a second notification of a second service level problem based on a number of times the service level agreement has not been met; e) determining a resolution for the service level problem within the hybrid network if the service level agreement has not been met, wherein the resolution is selected from the group of resolutions consisting essentially of: status reporting, resolution notification, problem reporting, service reconfiguration, trouble notification, service level agreement violations, and outage notification; f) tracking a progress of the implementation of the resolution; and g) managing the hybrid network based on future predicted behavior of the hybrid network.
Claim 2
Independent Claim 175 words
A method for service level management in a hybrid network architecture, comprising the steps of: a) receiving notification of a service level problem within a hybrid network, wherein the hybrid network is a combination packet-switching and circuit-switching network; b) retrieving a service level agreement; c) checking the service level problem against the service level agreement to determine if the service level agreement has been met; d) prioritizing the notification of the service level problem with a second notification of a second service level problem based on a number of times the service level agreement has not been met; e) determining a resolution for the service level problem within the hybrid network if the service level agreement has not been met, wherein the resolution is selected from the group of resolutions consisting essentially of: status reporting, resolution notification, problem reporting, service reconfiguration, trouble notification, service level agreement violations, and outage notification; f) tracking a progress of the implementation of the resolution; and g) managing the hybrid network based on future predicted behavior of the hybrid network.
Claim 3
Dependent Claim 15 words
A method as recited in claim 1 , wherein the resolution is a trouble notification.
Claim 4
Dependent Claim 19 words
A method as recited in claim 2 , wherein the trouble notification includes the delivery of a trouble ticket.
Claim 5
Dependent Claim 22 words
A method as recited in claim 1 , further comprising the step of notifying a customer upon the completion of the resolution.
Claim 6
Independent Claim 187 words
A system for service level management in a hybrid network architecture, comprising: a) logic that receives notification of a service level problem within a hybrid network, wherein the hybrid network is a combination packet-switching and circuit-switching network; b) logic that retrieves a service level agreement; c) logic that checks the service level problem against the service level agreement to determine if the service level agreement has been met; d) logic that prioritizes the notification of the service level problem with a second notification of a second service level problem based on a number of times the service level agreement has not been met; e) logic that determines a resolution for the service level problem within the hybrid network when the service level agreement has not been met, wherein the resolution is selected from the group of resolutions consisting essentially of: status reporting, resolution notification, problem reporting, service reconfiguration, trouble notification, service level agreement violations, and outage notification; and f) logic that tracks a progress of the implementation of the resolution; and g) logic that manages the hybrid network based on future predicted behavior of the hybrid network.
Claim 7
Independent Claim 187 words
A system for service level management in a hybrid network architecture, comprising: a) logic that receives notification of a service level problem within a hybrid network, wherein the hybrid network is a combination packet-switching and circuit-switching network; b) logic that retrieves a service level agreement; c) logic that checks the service level problem against the service level agreement to determine if the service level agreement has been met; d) logic that prioritizes the notification of the service level problem with a second notification of a second service level problem based on a number of times the service level agreement has not been met; e) logic that determines a resolution for the service level problem within the hybrid network when the service level agreement has not been met, wherein the resolution is selected from the group of resolutions consisting essentially of: status reporting, resolution notification, problem reporting, service reconfiguration, trouble notification, service level agreement violations, and outage notification; and f) logic that tracks a progress of the implementation of the resolution; and g) logic that manages the hybrid network based on future predicted behavior of the hybrid network.
Claim 8
Dependent Claim 15 words
A system as recited in claim 5 , wherein the resolution is a trouble notification.
Claim 9
Dependent Claim 19 words
A system as recited in claim 6 , wherein the trouble notification includes the delivery of a trouble ticket.
Claim 10
Dependent Claim 21 words
A system as recited in claim 5 , further comprising logic that notifies a customer upon the completion of the resolution.
Claim 11
Dependent Claim 208 words
A computer program embodied on a computer readable medium for service level management in a hybrid network architecture, comprising: a) a code segment that receives notification of a service level problem within a hybrid network, wherein the hybrid network is a combination packet-switching and circuit-switching network; b) a code segment that retrieves a service level agreement; c) a code segment that checks the service level problem against the service level agreement to determine if the service level agreement has been met; d) a code segment that prioritizes the notification of the service level problem with a second notification of a second service level problem based on a number of times the service level agreement has not been met; e) a code segment that determines a resolution for the service level problem within the hybrid network when the service level agreement has not been met, wherein the resolution is selected from the group of resolutions consisting essentially of: status reporting, resolution notification, problem reporting, service reconfiguration, trouble notification, service level agreement violations, and outage notification; and f) a code segment that tracks a progress of the implementation of the resolution; and g) a code segment that manages the hybrid network based on future predicted behavior of the hybrid network.
Claim 12
Dependent Claim 208 words
A computer program embodied on a computer readable medium for service level management in a hybrid network architecture, comprising: a) a code segment that receives notification of a service level problem within a hybrid network, wherein the hybrid network is a combination packet-switching and circuit-switching network; b) a code segment that retrieves a service level agreement; c) a code segment that checks the service level problem against the service level agreement to determine if the service level agreement has been met; d) a code segment that prioritizes the notification of the service level problem with a second notification of a second service level problem based on a number of times the service level agreement has not been met; e) a code segment that determines a resolution for the service level problem within the hybrid network when the service level agreement has not been met, wherein the resolution is selected from the group of resolutions consisting essentially of: status reporting, resolution notification, problem reporting, service reconfiguration, trouble notification, service level agreement violations, and outage notification; and f) a code segment that tracks a progress of the implementation of the resolution; and g) a code segment that manages the hybrid network based on future predicted behavior of the hybrid network.
Claim 13
Dependent Claim 16 words
A computer program as recited in claim 9 , wherein the resolution is a trouble notification.
Claim 14
Dependent Claim 20 words
A computer program as recited in claim 10 , wherein the trouble notification includes the delivery of a trouble ticket.
Claim 15
Dependent Claim 24 words
A computer program as recited in claim 9 , further comprising a code segment that notifies a customer upon the completion of the resolution.

References Cited (Backward Citations)

US4464543A Cited
US4529842A Cited
US4608693A Cited
US4999833A Cited
US4935956A Cited
US4972453A Cited
US5014267A Cited
US4987538A Cited
US5287270A Cited
US5325290A Cited
US5347305A Cited
US5341377A Cited
US5333183A Cited
US5285494A Cited
US5357564A Cited
US5966698A Cited
US5684965A Cited
US5515425A Cited
US5666481A Cited
US5559527A Cited
US5652787A Cited
US6052447A Cited
US5694548A Cited
US5917898A Cited
US5881131A Cited
US5953389A Cited
US5987107A Cited
WO1995024094A1 Cited
US5943657A Cited
US5907607A Cited
US5978855A Cited
US5461611A Cited
US5905715A Cited
US5835081A Cited
FR2728367A1 Cited
WO1996024210A2 Cited
US5878130A Cited
US5696906A Cited
US5995606A Cited
US5774532A Cited
US5790642A Cited
US5650994A Cited
US5742762A Cited
WO1996038018A1 Cited
US5629938A Cited
US5799073A Cited
US5799072A Cited
US5862203A Cited
US5790634A Cited
US5893077A Cited
US5915008A Cited
US5828737A Cited
US5842183A Cited
US5933425A Cited
US5918213A Cited
US5852659A Cited
US5761650A Cited
US5802160A Cited
US5896445A Cited
US6101481A Cited
US5809120A Cited
JPH09231277A Cited
US5862329A Cited
US5867653A Cited
US5898688A Cited
US5982362A Cited
US5745883A Cited
US5892754A Cited
US6026379A Cited
US5913036A Cited
US5822744A Cited
US5991378A Cited
US6134223A Cited
US5930333A Cited
US6119109A Cited
US5940471A Cited
US6070150A Cited
US6031904A Cited
US5867494A Cited
US5867495A Cited
US5999525A Cited
US5917817A Cited
US6034950A Cited
US5956720A Cited
US5970065A Cited
US5960416A Cited
US6006205A Cited
US5970403A Cited
US6157648A Cited
US5950174A Cited
US6011838A Cited
US5991806A Cited
US6055240A Cited
US5864823A Cited
US5933489A Cited
US6044355A Cited
US5987430A Cited
US6005926A Cited
US6044362A Cited
US6216169B1 Cited

USPTO Annuity & Maintenance Windows

Annuity Stage Window Opens Payment Deadline Surcharge Period Until Estimated Fee Status
3.5 Years (Year 4) 2006-04-28 2006-10-28 2007-04-29 $2000.00 Window Closed / Lapsed
7.5 Years (Year 8) 2010-04-28 2010-10-28 2011-04-29 $3760.00 Window Closed / Lapsed
11.5 Years (Year 12) 2014-04-28 2014-10-28 2015-04-29 $7700.00 Window Closed / Lapsed

Assigned Categories & Tags

No categories assigned to this patent yet.

Assign Category Tag