Proactive service request management and measurement

• US 20020087680A1
• Filed: 08/01/2001
• Published: 07/04/2002
• Est. Priority Date: 08/01/2000
• Status: Active Grant

• Current Assignee: Qwest Communications International Incorporated (Lumen Technologies, Inc.)
• Original Assignee: Qwest Communications International Incorporated (Lumen Technologies, Inc.)
• Inventors: Storaasli, Roxanna, Figueroa, Timothy, Cerami, Richard S.
• Granted Patent: US 7,032,016 B2
• Time in Patent Office: Days
• US Class Current: 709/224
• CPC Class Codes: G06Q 10/087 Inventory or stock management, e.g. order filling, procurement or balancing against orders
• CPC Class Codes: H04L 12/66 Arrangements for connecting between networks having differing types of switching systems, e.g. gateways
• CPC Class Codes: H04L 41/06 Management of faults, events, alarms or notifications
• CPC Class Codes: H04L 41/0631 using root cause analysis; using analysis of correlation between notifications, alarms or events based on decision criteria, e.g. hierarchy, tree or time analysis
• CPC Class Codes: H04L 41/0654 using network fault recovery ring fault isolation or reconfiguration in loop networks without recovery actions by a network management system H04L12/437
• CPC Class Codes: H04L 41/0896 Bandwidth or capacity management, i.e. automatically increasing or decreasing capacities flow or congestion control using dynamic resource allocation, e.g. in-call renegotiation, H04L47/76
• CPC Class Codes: H04L 41/12 Discovery or management of network topologies
• CPC Class Codes: H04L 41/32 Specific management aspects for broadband networks
• CPC Class Codes: H04L 41/40 using virtualisation of network functions or resources, e.g. SDN or NFV entities
• CPC Class Codes: H04L 41/5003 Managing SLA; Interaction between SLA and QoS
• CPC Class Codes: H04L 41/5009 Determining service level performance parameters or violations of service level contracts, e.g. violations of agreed response time or mean time between failures [MTBF]
• CPC Class Codes: H04L 41/5025 by proactively reacting to service quality change, e.g. by reconfiguration after service quality degradation or upgrade
• CPC Class Codes: H04L 41/5032 Generating service level reports
• CPC Class Codes: H04L 41/5061 characterised by the interaction between service providers and their network customers, e.g. customer relationship management
• CPC Class Codes: H04L 41/5067 Customer-centric QoS measurements
• CPC Class Codes: H04L 41/507 Filtering out customers affected by service problems
• CPC Class Codes: H04L 41/5074 Handling of user complaints or trouble tickets
• CPC Class Codes: H04L 41/509 wherein the managed service relates to media content delivery, e.g. audio, video or TV
• CPC Class Codes: H04L 43/00 Arrangements for monitoring or testing data switching networks
• CPC Class Codes: H04L 43/0811 by checking connectivity
• CPC Class Codes: H04L 43/0817 : by checking functioning
• CPC Class Codes: H04L 43/0823 : Errors, e.g. transmission errors
• CPC Class Codes: H04L 43/0882 : Utilisation of link capacity
• CPC Class Codes: H04L 43/091 : Measuring contribution of individual network components to actual service level
• CPC Class Codes: H04L 43/10 : Active monitoring, e.g. heartbeat, ping or trace-route
• CPC Class Codes: H04L 43/16 : Threshold monitoring
• CPC Class Codes: H04L 43/20 : the monitoring system or the monitored elements being virtualised, abstracted or software-defined entities, e.g. SDN or NFV
• CPC Class Codes: H04L 43/50 : Testing arrangements
• CPC Class Codes: H04L 69/40 : for recovering from a failure of a protocol instance or entity, e.g. service redundancy protocols, protocol state redundancy or protocol service redirection management of faults, events, alarms or notifications in data switching networks H04L41/06
• CPC Class Codes: H04M 11/062 : using different frequency bands for speech and other data
• CPC Class Codes: H04N 21/6125 : involving transmission via Internet transmission by internet of broadcast information H04H60/82
• CPC Class Codes: H04N 21/6473 : Monitoring network processes errors for recovering from a failure of a protocol instance or entity H04L69/40
• CPC Class Codes: H04N 21/64738 : Monitoring network characteristics, e.g. bandwidth, congestion level data switched network analysis H04L41/14; monitoring functioning in data switched networks H04L43/0817; flow control in packet networks H04L47/10
• CPC Class Codes: Y10S 707/99931 : Database or file accessing

Abstract

A method for managing a repair process for a fault between a proactive network repair system and customer service system using a repair ticketing system is provided. The method includes detecting the fault in the proactive network repair system. Once detected, an indication of the fault is sent to the repair ticketing system and a repair ticket is created. The repair ticketing system then correlates one or more customers affected by the fault to the repair ticket and communicates the repair ticket and the one or more customers affected by the fault to customer service system before a call is received by the one or more customers affected by the fault.

Claims

1. A method for managing a repair process for a fault between a proactive network repair system and customer service system using a repair ticketing system, the method comprising:

detecting the fault in the proactive network repair system;

sending an indication of the fault to the repair ticketing system;

creating a repair ticket;

correlating one or more customers affected by the fault to the repair ticket; and

communicating the repair ticket and the one or more customers affected by the fault to customer service system before a call is received by the one or more customers affected by the fault.

2. The method of claim 1, wherein the video and data network comprises a Digital Subscriber Line (xDSL) network.

3. The method of claim 1, wherein the video and data network comprises a Very high bit rate DSL (VDSL) network.

4. The method of claim 1, wherein the proactive network repair system comprises a fault management system, proactive repair system, and performance management system.

5. The method of claim 4, further comprising communicating the repair ticket to the fault management system, proactive repair system, and performance management system.

6. The method of claim 1, further comprising sending an indication that the fault is resolved to the repair ticketing system.

7. The method of claim 1, further comprising closing the repair ticket.

8. The method of claim 7, further comprising communicating the resolution of the repair ticket to the customer service system and proactive network repair system.

9. A method for managing a repair process for a fault between a fault management system, proactive repair system, performance management system, and customer service system using a repair ticketing system, the method comprising:

detecting the fault in at least one of the fault management system, proactive repair system, and performance management system;

sending an indication of the fault to the repair ticketing system;

creating a repair ticket;

correlating a list of customers affected by the fault to the repair ticket;

communicating the repair ticket and the list of customers to the customer service system before a call is received by a customer in the list of customers; and

communicating the repair ticket to the fault management system, proactive repair system, and performance management system.