Normalization engine and method of requesting a key or performing an operation pertaining to an end point

• US 8,468,237 B2
• Filed: 11/21/2008
• Issued: 06/18/2013
• Est. Priority Date: 11/21/2007
• Status: Expired due to Fees

• Current Assignee: WSOU Investments, LLC (WSOU Holdings, LLC)
• Original Assignee: Alcatel-Lucent SA (Nokia Corporation)
• Inventors: Palkot, Thomas A., Tacker, Bryan P., Pelley, Edward S., Singh, Amarjit
• Primary Examiner(s): Shin, Kyung H
• Application Number:
  US12/276,260
• Publication Number:
  US 20090132684A1
• Time in Patent Office: 1,670 Days
• Field of Search: 709/224, 709/223, 709/220
• US Class Current: 709/224
• 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 normalization engine and a method of requesting a key or performing an operation pertaining to an end point. In one embodiment, the normalization engine includes: (1) a data manager configured to receive a request to execute an operation or obtain a key/value pair pertaining to an end point and determine a normalized version of the key in the key/value pair and (2) a normalization mapping repository configured to contain normalization mechanisms, the data manager further configured to employ the normalized version to obtain one of the normalization mechanisms from the normalization mapping repository, carry out the normalization mechanism and employ a data source corresponding to the end point to retrieve a device-specific value corresponding to the normalized version.

Claims

1. A normalization engine, comprising:

a data manager configured to receive a request to execute an operation or obtain a key/value pair pertaining to an end point and determine a normalized version of said key in said key/value pair; and

a normalization mapping repository configured to contain normalization mechanisms, said data manager further configured to employ said normalized version to obtain one of said normalization mechanisms from said normalization mapping repository, carry out said normalization mechanism to retrieve a device-type specific value employing a data source corresponding to said end point, said device-type specific value corresponding to said normalized version of said key, said normalization mechanism having implicit knowledge of said key/value pair and how to map said key/value pair to said normalized version of said key/value pair for data retrieval or operation execution;

wherein said normalization engine is executed by a processor of a computer system from non-transitory computer-readable media, and said normalization mapping repository has a data structure such that device types can inherit normalization mechanisms from one another, and said data manager is further configured to employ an attribute and a role of said end point to identify said data source, wherein said role defines actions to be taken with respect to said end point to provision a service, and select functions, alerts, and key/value pair of interest from said end point to perform said actions.

2. The normalization engine as recited in claim 1 wherein said role is based on at least some of descriptions, capabilities and attributes of said end point.

3. The normalization engine as recited in claim 1 wherein said normalization engine is further configured to employ one of a script engine, a transformation engine and another normalization mechanism to carry out said normalization mechanism.

4. The normalization engine as recited in claim 1 wherein said normalization mechanism is based upon meta data provided in a query to said normalization mapping repository.

5. The service management system as recited in claim 4 wherein said data manager evaluates said meta data against hierarchical configuration data.

6. The service management system as recited in claim 1 wherein said data manager is further configured to normalize said key, a value and meta-rules and relationships that said key/value pair have with other key/value pairs.

7. The service management system as recited in claim 1 wherein said data manager is further configured to allow an application to query to determine what values are available for a given type of key.

8. The service management system as recited in claim 1 wherein said data manager is further configured logically to determine a value of a key/value pair during a set operation using values of other key/value pairs.

9. A method of requesting a key pertaining to a key/value pair of an end point, comprising:

determining a normalized version of said key of said key/value pair wherein said key/value pair has additional concepts beyond what device description documents convey;

employing said normalized version to obtain a normalization mechanism from a normalization mapping repository, said normalization mechanism having implicit knowledge of said key/value pair and how to map said key/value pair to said normalized version of said key/value pair for data retrieval or operation execution; and

carrying out said normalization mechanism, including;

employing an attribute and a role of said end point to identify a data source, said role defining actions to be taken with respect to said end point to provision a service and selecting functions, alerts, and key/value pair of interest from said end point to perform said actions, and

employing said data source to retrieve a device-type specific value corresponding to said normalized version of said key;

wherein said normalization mapping repository has a data structure such that device types can inherit normalization mechanisms from one another.

10. The method as recited in claim 9 further comprising converting said device-type specific value to a normalized data type.

11. The method as recited in claim 9 further comprising returning said device-type specific value to an application in normalized form.

12. The method as recited in claim 9 wherein said normalization mechanism is selected from the group consisting of:

an execution script, and

a transformation.

13. The method as recited in claim 9 further comprising evaluating said normalization mechanism is evaluated to determine how said normalization mechanism should be carried out.

14. The method as recited in claim 9 wherein said carrying out comprises executing said normalization mechanism in a script engine.

15. The method as recited in claim 9 further comprising basing said normalization mechanism upon meta data provided in a query to said normalization mapping repository.

16. The method as recited in claim 9 further comprising evaluating said meta data against hierarchical configuration data.

17. The method as recited in claim 9 further comprising normalizing said key, a value and meta-rules and relationships that said key/value pair have with other key/value pairs.