SYSTEM AND METHOD FOR REMOTELY REPAIRING AND MAINTAINING A TELECOMMUNICATION SERVICE USING SERVICE RELATIONSHIPS AND SERVICE MANAGEMENT SYSTEM EMPLOYING THE SAME

• US 20090132324A1
• Filed: 11/21/2008
• Published: 05/21/2009
• Est. Priority Date: 11/21/2007
• Status: Active Grant

• Current Assignee: WSOU Investments, LLC (WSOU Holdings, LLC)
• Original Assignee: Motive Incorporated (Nokia Corporation)
• Inventors: Shah, Bipin H., Pelley, Edward S.
• Granted Patent: US 8,533,021 B2
• Time in Patent Office: Days
• US Class Current: 705/8
• CPC Class Codes: G06Q 10/063 Operations research, analysis or management
• CPC Class Codes: G06Q 10/06313 Resource planning in a project environment
• CPC Class Codes: H04L 41/5054 Automatic deployment of services triggered by the service manager, e.g. service implementation by automatic configuration of network components
• 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 67/125 involving control of end-device applications over a network
• CPC Class Codes: H04L 67/306 User profiles

Abstract

A service management system and method. In one embodiment, the service management system includes: (1) a service description repository configured to contain service descriptions that define services in terms of a set of systems and devices that assume roles based on at least one of capabilities and attributes thereof and (2) a service management engine coupled to the service description repository and configured to employ one of the service descriptions to repair a corresponding one of the services using a predefined relationship among a subscriber, at least one of the systems and devices and optimal values.

Claims

1. A service management system, comprising:

a service description repository configured to contain service descriptions that define services in terms of a set of systems and devices that assume roles based on at least one of capabilities and attributes thereof; and

a service management engine coupled to said service description repository and configured to employ one of said service descriptions to repair a corresponding one of said services using a predefined relationship among a subscriber, at least one of said systems and devices and optimal values.

2. The service management system as recited in claim 1 wherein said service description repository associates at least some of operations, alerts, and key/value pairs with said roles.

3. The service management system as recited in claim 1 wherein said roles are based on at least some of descriptions, capabilities and attributes of said devices.

4. The service management system as recited in claim 1 wherein said service descriptions contain service descriptions expressed in a selected one of:

a human readable markup language, and

binary data representations.

5. The service management system as recited in claim 1 wherein said service descriptions contain descriptions of arbitrary relationships between said roles using one of predefined rules, dynamically obtained rules and logic.

6. A service management system, comprising:

a service description repository configured to contain service descriptions that define services in terms of a set of systems and devices that assume roles based on at least one of capabilities and attributes thereof; and

a service management engine coupled to said service description repository and configured to respond to a received event by employing one of said service descriptions to maintain a telecommunication service on at least one of said systems and devices using a predefined relationship among a subscriber and at least one of said systems and devices.

7. The service management system as recited in claim 6 wherein said service description repository associates at least some of operations, alerts, and key/value pairs with said roles.

8. The service management system as recited in claim 6 wherein said roles are based on at least some of descriptions, capabilities and attributes of said devices.

9. The service management system as recited in claim 6 wherein said service descriptions contain service descriptions expressed in a selected one of:

a human readable markup language, and

binary data representations.

10. The service management system as recited in claim 6 wherein said service descriptions contain descriptions of arbitrary relationships between said roles using one of predefined rules, dynamically obtained rules and logic.

11. A method of remotely repairing a telecommunication service, comprising:

receiving information identifying a subscriber and said service;

identifying end points associated with said subscriber;

mapping said end points into roles in said service; and

repeating, for each of said end points;

determining attributes regarding said each of said end points,

retrieving said attributes and optimal values corresponding thereto, and

reprovisioning ones of said attributes based on a comparison therebetween and ones of said optimal values.

12. The method as recited in claim 11 wherein said receiving comprises retrieving data reflecting said information from a service description of a service management system.

13. The method as recited in claim 12 wherein said data comprises key/value pairs based on a particular context.

14. The method as recited in claim 11 further comprising retrieving said optimal values from an optimal settings block of a service management system.

15. The method as recited in claim 11 wherein said reprovisioning comprises retrieving a provision function from a service description of a service management system.

16. A method of remotely maintaining a telecommunication service, comprising:

receiving an alert;

associating a subscriber with said alert;

retrieving service descriptions corresponding to subscriptions associated with said subscriber; and

repeating, for each of said service descriptions;

determining whether said alert matches an alert type in said each of said service descriptions, and

causing a function associated with said alert to be executed.

17. The method as recited in claim 16 wherein said receiving comprises receiving said alert from one of said end points.

18. The method as recited in claim 16 wherein said retrieving comprises retrieving said service descriptions from a service description repository of a service management system.

19. The method as recited in claim 16 wherein said repeating comprises retrieving said function from one of said service descriptions to which said alert corresponds.

20. The method as recited in claim 16 wherein said executing comprises passing said function to a script engine of a service management system.