CAPABILITY MANAGEMENT FOR NETWORK ELEMENTS

• US 20090328133A1
• Filed: 06/27/2008
• Published: 12/31/2009
• Est. Priority Date: 06/27/2008
• Status: Abandoned Application

• Current Assignee: Motorola Solutions, Inc.
• Original Assignee: Motorola, Inc. (Motorola Solutions, Inc.)
• Inventors: Raymer, David L. JR., Liu, Yan, Strassner, John C., Fu, Zhi, Cox, Gregory W.
• Application Number:
  US12/163,343
• Publication Number:
  US 20090328133A1
• Time in Patent Office: Days
• US Class Current: 726/1
• CPC Class Codes: H04L 41/0853 by actively collecting configuration information or by backing up configuration information
• CPC Class Codes: H04L 41/12 Discovery or management of network topologies
• CPC Class Codes: H04L 67/303 Terminal profiles
• CPC Class Codes: H04L 69/24 Negotiation of communication capabilities

Abstract

A method, information processing system, and system manage network entities. At least a portion of at least one information model (120) for a first managed entity (104) and at least a second managed entity (106) is accessed. The portion of the at least one information model (120) includes a set of capabilities (542) associated with the first managed entity (104) and second managed entity (106), respectively. A first set of capabilities (708) supported by the first managed entity (104) and a second set of capabilities (710) supported by the second managed entity (106) are identified based on the portion of the at least one information model (120). A set of common capabilities (712) from the first set of capabilities (708) and the second set of capabilities (710) that is supported by both of the first managed entity (104) and the second managed entity (106) is determined.

Claims

1. A method for managing entities, the method comprising:

accessing at least a portion of at least one information model for a first managed entity and at least a second managed entity, wherein the portion of the at least one information model includes a set of capabilities associated with the first managed entity and the at least second managed entity, respectively, wherein a capability is at least one of i) a feature;

ii) a resource;

or iii) a service associated with a managed entity and is externally visible by a given entity for external monitoring by the given entity and wherein each information model represents at least one of characteristics and static behavior of each capability in the set of capabilities;

identifying, based on the portion of the at least one information model, a first set of capabilities supported by the first managed entity and a second set of capabilities supported by the at least second managed entity; and

determining, in response to identifying the first set of capabilities and the second set of capabilities, a set of common capabilities from the first set of capabilities and the second set of capabilities that is supported by both of the first managed entity and the at least second managed entity.

2. The method of claim 1, further comprising:

augmenting the portion of the at least one information model with metadata associated with at least one capability in the set of capabilities associated with at least one of the first managed entity and the at least second managed entity, wherein the metadata describes data and concepts that aid in human and/or machine-based understanding of the capability associated with each of the at least one of the first managed entity and the at least one of the second managed entity.

3. The method of claim 2, wherein the metadata is determined based on a capability type associated with the at least one capability, wherein a capability type is one of:

a declarative capability,

a functional capability, and

an imperative capability

4. The method of claim 2, wherein the metadata is a role that indicates a function of the at least one capability.

5. The method of claim 1, further comprising:

building at least one ontology associated with at least one of the first managed entity and the second managed entity, wherein the at least one ontology specifies semantics associated with at least one capability in the set of capabilities associated with one of the first managed entity and the second managed entity.

6. The method of claim 5, further comprising:

augmenting at least one capability in the set of capabilities within the portion of at the least one first information model that is substantially similar to the at least one capability associated with the semantics specified in the at least one ontology.

7. The method of claim 6, further comprising:

building a linguistic relationship associated with the first managed entity and the at least second managed entity based on the at least one ontology; and

determining that at least one capability in associated with the first managed entity is semantically similar to at least one capability associated with the at least second managed entity.

8. The method of claim 6, further comprising:

building a linguistic relationship associated with the first managed entity and the at least second managed entity based on the at least one ontology; and

determining that at least one capability in associated with the first managed entity fails to be semantically similar to at least one capability associated with the at least second managed entity.

9. The method of claim 6, further comprising:

dynamically constructing at least one additional capability in the portion of at the least one first information model based at least in part on the semantic information associated with the at least one capability; and

storing the semantic information as metadata and/or links to one or more ontologies.

10. The method of claim 5, further comprising:

associating the at least one capability associated with the semantics specified by the ontology with at least one capability in the set of capabilities included in the portion of at the least one first information model.

11. The method of claim 10, wherein the associating further comprises:

adding at least one additional field in metadata associated with the at least one capability in the set of capabilities included in the portion of at the least one first information model that has been associated with the at least one capability associated with the semantics specified by the ontology, wherein the metadata indicates that the at least one ontology is associated with the at least one capability included in the portion of at the least one first information model.

12. The method of claim 1, further comprising:

selecting a set of policies for managing the first managed entity and the at least second managed entity; and

selecting a set of capabilities from the set of common capabilities based on the set of policies that have been selected.

13. The method of claim 12, wherein selecting a set of policies further comprises:

selecting the set of policies based on a context associated with each of the first managed entity and the at least second managed entity, respectively.

14. An information processing system for managing entities, the system comprising:

a memory;

a processor communicatively coupled to the memory; and

a network element manager communicatively coupled to the memory and the processor, wherein the network element manager is adapted to;

access at least a portion of at least one information model for a first managed entity and at least a second managed entity, wherein the portion of the at least one information model includes a set of capabilities associated with the first managed entity and the at least second managed entity, respectively, wherein a capability is at least one of i) a feature;

ii) a resource;

or iii) a service associated with a managed entity and is externally visible by a given entity for external monitoring by the given entity and wherein the portion of the at least one information model represents at least one of characteristics and static behavior of each capability in the set of capabilities;

identify, based on the portion of the at least one information model, a first set of capabilities supported by the first managed entity and a second set of capabilities supported by the at least second managed entity; and

determine, in response to identifying the first set of capabilities and the second set of capabilities, a set of common capabilities from the first set of capabilities and the second set of capabilities that is supported by both of the first managed entity and the at least second managed entity.

15. The information processing system according to claim 14, wherein the network element manager is further adapted to:

augment the portion of the at least one information model with metadata associated with at least one capability in the set of capabilities associated with at least one of the first managed entity and the at least second managed entity, wherein the metadata describes data and concepts that aid in human and/or machine-based understanding of the capability associated with each of the at least one of the first managed entity and the at least one of the second managed entity.

16. The information processing system of claim 14, wherein the network element manager is further adapted to:

build at least one ontology associated with at least one of the first managed entity and the second managed entity, wherein the at least one ontology specifies semantics associated with at least one capability in the set of capabilities associated with one of the first managed entity and the second managed entity;

augment at least one capability in the set of capabilities within the portion of at the least one first information model that is substantially similar to the at least one capability associated with the semantics specified in the at least one ontology;

build a linguistic relationship associated with the first managed entity and the at least second managed entity based on the at least one ontology; and

determine at least one of

that at least one capability in associated with the first managed entity is semantically similar to at least one capability associated with the at least second managed entity; and

that at least one capability in associated with the first managed entity fails to be semantically similar to at least one capability associated with the at least second managed entity.

17. The information processing system of claim 14, wherein the network element manager is further adapted to:

select a set of policies for managing the first managed entity and the at least second managed entity; and

select a set of capabilities from the set of common capabilities based on the set of policies that have been selected.

18. A system for managing entities, the system comprising:

at least one network;

at least a first managed entity communicatively coupled to the network;

at least a second managed entity communicatively coupled to the network; and

at least one information processing system communicatively coupled to the network and the first managed entity and the at least second managed entity, wherein the information processing system includes;

a memory;

a processor communicatively coupled to the memory; and

a network element manager communicatively coupled to the memory and the processor, wherein the network element manager is adapted to;

access at least a portion of at least one information model for a first managed entity and at least a second managed entity, wherein the portion of the at least one information model includes a set of capabilities associated with the first managed entity and the at least second managed entity, respectively, wherein a capability is at least one of i) a feature;

ii) a resource;

or iii) a service associated with a managed entity and is externally visible by a given entity for external monitoring by the given entity and wherein the portion of the at least one information model represents at least one of characteristics and static behavior of each capability in the set of capabilities;

identify, based on the portion of the at least one information model, a first set of capabilities supported by the first managed entity and a second set of capabilities supported by the at least second managed entity; and

determine, in response to identifying the first set of capabilities and the second set of capabilities, a set of common capabilities from the first set of capabilities and the second set of capabilities that is supported by both of the first managed entity and the at least second managed entity.

19. The system of claim 18, wherein the network element manager is further adapted to:

build at least one ontology associated with at least one of the first managed entity and the second managed entity, wherein the at least one ontology specifies semantics associated with at least one capability in the set of capabilities associated with one of the first managed entity and the second managed entity;

augment at least one capability in the set of capabilities within the portion of at the least one first information model that is substantially similar to the at least one capability associated with the semantics specified in the at least one ontology;

build a linguistic relationship associated with the first managed entity and the at least second managed entity based on the at least one ontology; and

determine at least one of

that at least one capability in associated with the first managed entity is semantically similar to at least one capability associated with the at least second managed entity; and

that at least one capability in associated with the first managed entity fails to be semantically similar to at least one capability associated with the at least second managed entity.

20. The system of claim 18, wherein the network element manager is further adapted to:

select a set of policies for managing the first managed entity and the at least second managed entity; and

select a set of capabilities from the set of common capabilities based on the set of policies that have been selected.