MANAGED OBJECT VERSION IDENTIFICATION

• US 20130339508A1
• Filed: 06/13/2013
• Published: 12/19/2013
• Est. Priority Date: 06/13/2012
• Status: Active Grant

• Current Assignee: Telefonaktiebolaget LM Ericsson
• Original Assignee: Telefonaktiebolaget LM Ericsson
• Inventors: Tse, Edwin
• Granted Patent: US 9,253,022 B2
• Time in Patent Office: Days
• US Class Current: 709/223
• CPC Class Codes: H04L 41/0233 Object-oriented techniques, for representation of network management data, e.g. common object request broker architecture [CORBA]
• CPC Class Codes: H04L 41/044 comprising hierarchical management structures
• CPC Class Codes: H04L 41/0853 by actively collecting configuration information or by backing up configuration information
• CPC Class Codes: H04L 41/0873 Checking configuration conflicts between network elements

Abstract

Systems and methods for determining a version of a standard publication that is supported by a network element are provided. Version map information is requested and received from an external node in a managed network, including publication identifiers for at least one of the network elements. Each network element identified in the version map has an associated publication version and an indication of if the publication can be applicable to its directly or indirectly inferior nodes in the hierarchical instance tree. If a particular network element does not have a corresponding publication identifier in the received version map information, it can be determined if the network element can use the publication identifiers of a superior network element in the hierarchy.

Claims

1. A method for determining a publication version supported by a network element, for execution by a Network Management System entity managing a hierarchical arrangement of network elements, comprising the steps of:

receiving a version map message from an external node;

selecting a first network element from the hierarchical arrangement for processing;

in response to determining that the selected first network element does not have a corresponding entry in the received version map message, identifying a second network element that is superior to the first network element in the hierarchical arrangement; and

determining that the first network element supports a version of a standard publication associated with the second network element.

2. The method of claim 1, further comprising:

identifying a third network element that is superior to the first network element in the hierarchical arrangement; and

determining that the first network element does not support a version of a standard publication associated with the third network element.

3. The method of claim 2, wherein the steps of identifying the third network element and determining that the first network element does not support the version of the standard publication associated with the third network element are performed prior to the step of identifying the second network element.

4. The method of claim 1, wherein the version map message is received in response to sending a request to the external node.

5. The method of claim 1, wherein the version map message contains a list of entries, each entry specifying a network element and a version of a standard publication supported by the network element, the version map message also including an inheritability indicator for each entry.

6. The method of claim 5, wherein the inheritability indicator indicates that the version of the standard publication supported by the specified network element is also supported by network elements that are inferior to the specified network element in the hierarchical arrangement.

7. The method of claim 5, further comprising comparing the selected first network element with the list of entries in the received version map message.

8. The method of claim 1, further comprising determining that the identified second network element has a corresponding entry in the received version map message.

9. The method of claim 1, wherein the step of determining that the first network element supports the version of the standard publication associated with the second network element includes checking an inheritability indicator associated with the second network element in the received version map message.

10. The method of claim 1, wherein the step of determining that the first network element supports the version of the standard publication associated with the second network element includes determining that the version of the standard publication contains a class definition corresponding to the first network element.

11. The method of claim 1, wherein the second network element is identified by selecting a nearest superior network element in the hierarchical arrangement of network elements.

12. The method of claim 1, further comprising, in response to determining that at least one network element in the hierarchical arrangement does not have an associated publication identifier, selecting a fourth network element for processing.

13. A Network Management System node comprising a communication interface, a processor and a memory, the memory containing instructions executable by the processor whereby the Network Management System node is operative to:

receive, at the communication interface, a version map message from an external node;

select a first network element from a hierarchical arrangement of network elements;

in response to determining that the selected first network element does not have a corresponding entry in the received version map message, identify a second network element that is superior to the first network element in the hierarchical arrangement; and

determine that the first network element supports a version of a standard publication associated with the second network element.

14. The Network Management System node of claim 13, wherein the communication interface is configured to send a request to the external node for the version map message.

15. The Network Management System node of claim 13, wherein the version map message contains a list of entries, each entry specifying a network element and a version of a standard publication supported by the network element, the version map message also including an inheritability indicator for each entry.

16. The Network Management System node of claim 15, wherein the inheritability indicator indicates that the version of the standard publication supported by the specified network element is also supported by network elements that are inferior to the specified network element in the hierarchical arrangement.

17. The Network Management System node of claim 15, wherein the processor is configured to compare the selected first network element with the list of entries in the received version map message.

18. The Network Management System node of claim 13, wherein the processor is configured to determine that the identified second network element has a corresponding entry in the received version map message.

19. The Network Management System node of claim 13, wherein the processor is configured to determine that the first network element supports the version of the standard publication associated with the second network element by checking an inheritability indicator associated with the second network element in the received version map message.

20. The Network Management System node of claim 13, wherein the processor is configured to determine that the first network element supports the version of the standard publication associated with the second network element by determining that the version of the standard publication contains a class definition corresponding to the first network element.

21. The Network Management System node of claim 13, wherein the processor is configured to identify the second network element by selecting a nearest superior network element in the hierarchical arrangement of network elements.

22. The Network Management System node of claim 13, wherein the determined version of the standard publication is stored with an identifier of the first network element in the memory.