In-service software upgrade utilizing metadata-driven state translation

• US 20090089774A1
• Filed: 01/18/2008
• Published: 04/02/2009
• Est. Priority Date: 09/27/2007
• Status: Active Grant

• Current Assignee: Ericsson AB (Telefonaktiebolaget LM Ericsson)
• Original Assignee: Ericsson AB (Telefonaktiebolaget LM Ericsson)
• Inventors: Daudt, Christian Stabel, Mordock, Scott R., Lynch, Timothy J.
• Granted Patent: US 8,806,472 B2
• Time in Patent Office: Days
• US Class Current: 717/173
• CPC Class Codes: G06F 8/60 Software deployment
• CPC Class Codes: G06F 8/61 Installation
• CPC Class Codes: G06F 8/65 Updates security arrangements therefor G06F21/57
• CPC Class Codes: G06F 8/656 while running
• CPC Class Codes: H04L 41/082 the condition being updates or upgrades of network functionality

Abstract

A method and apparatus for a metadata-driven upgrade of a network element is described. A network element comprises an active and backup controller card and receives new software to be installed on that network element. In addition, the network element installs the software on the backup controller card and synchronizes the active state of the network element to the backup controller card. Furthermore, the network element uses metadata to translate the active state to the format used by the new software.

Claims

1. A computerized method, comprising:

receiving new software to be installed on a network element having an active and backup controller card, wherein the new software comprises metadata describing a format used by the new software to store and access critical state information of the network element;

installing the new software on the backup controller card;

synchronizing an active state of the network element on the backup controller card, wherein the active state comprises the critical state information, and wherein the active state is associated with an old software running on the network element; and

translating the active state using the metadata to the format used by the new software.

2. The computerized method of claim 1, wherein the metadata represents a description of the format of the structure and fields of the active state associated with the new software.

3. The computerized method of claim 1, wherein the new software is one of a network element operating system and a service running on the network element.

4. The computerized method of claim 1, wherein the translating further uses an old set of metadata associated with the old software.

5. The computerized method of claim 1, further comprising:

switching over control from the active controller card to the backup controller, wherein the backup controller card is running the new software; and

running the new software in the active controller card.

6. The computerized method of claim 1, further comprising:

generating the metadata from state data defined in a data definition language.

7. The computerized method of claim 1, wherein the translating supports one or more of adding a field to an active state data structure, removing a field, modifying a field, rearranging two or more fields, assigning a new field a default value, and changing a literal value associated with an enumerated constant.

8. A machine-readable medium that stores instructions, which when executed by a set of one or more processors, cause said set of processors to perform operations comprising:

receive new software to be installed on a network element having an active and backup controller card, wherein the new software comprises metadata that describes a format used by the new software to store and access critical state information of the network element;

install the new software on the backup controller card;

synchronize an active state of the network element on the backup controller card, wherein the active state comprises the critical state information, and wherein the active state is associated with an old software that runs on the network element; and

translate the active state using the metadata to the format used by the new software.

9. The machine-readable medium of claim 8, wherein the metadata represents a description of the format of the structure and fields of the active state associated with the new software.

10. The machine-readable medium of claim 8, wherein the new software is one of a network element operating system and a service running on the network element.

11. The machine-readable medium of claim 8, wherein the translate further uses an old set of metadata associated with the old software.

12. The machine-readable medium of claim 8, wherein the machine-readable medium further causes the set of processors to:

run the new software in the backup controller card;

switch over control from the active controller card to the backup controller; and

run the new software in the active controller card.

13. The machine-readable medium of claim 8, wherein the machine-readable medium further causes the set of processors to:

generate the metadata from state data defined in a data definition language.

14. The machine-readable medium of claim 8, wherein the translate supports one or more of adding a field to an active state data structure, removing a field, modifying a field, rearranging two or more fields, assigning a new field a default value, and changing a literal value associated with an enumerated constant.

15. An apparatus comprising:

a software management module to receive new software to be installed on a network element having an active and backup controller card, wherein the new software comprises metadata that describes a format used by the new software to store and access critical state information of the network element, and wherein the software management module installs the new software on the backup controller card;

a state synchronization module to synchronize an active state of the network element on the backup controller card, wherein the active state comprises the critical state information, and wherein the active state is associated with an old software running on the network element; and

a state translation module to translate the active state using the metadata to the format used by the new software.

16. The apparatus of claim 15, wherein the metadata represents a description of the format of the structure and fields of the active state associated with the new software.

17. The apparatus of claim 15, wherein the new software is one of a network element operating system and a service running on the network element.

18. The apparatus of claim 15, wherein the state translation module further uses an old set of metadata associated with the old software.

19. The apparatus of claim 15, wherein the state translation module supports one or more of adding a field to an active state data structure, removing a field, modifying a field, rearranging two or more fields, assigning a new field a default value, and changing a literal value associated with an enumerated constant.

20. The apparatus of claim 15, wherein further comprising:

a control module to switch over control from the active controller card to the backup controller, wherein the backup controller card runs the new software.

21. A network element comprising:

an active controller card that controls functions of the network element;

a backup controller card, wherein the backup controller card is configured to,

receive new software to be installed on the network element, wherein the new software comprises metadata that describes a format used by the new software to store and access critical state information of the network element,

install the new software on the backup controller card,

synchronize an active state of the network element on the backup controller card, wherein the active state comprises the critical state information, and wherein the active state is associated with an old software running on the network element, and

translate the active state using the metadata to the format used by the new software; and

a set of one or more line cards, the line cards to process and forward traffic.

22. The network element of claim 21, wherein the metadata represents a description of the format of the structure and fields of the active state associated with the new software.

23. The network element of claim 21, wherein the backup controller card is configured to switch control over from the active controller card to the backup controller, wherein the backup controller card runs the new software.

24. The network element of claim 21, wherein the backup controller card is configured to further translate the active state using an old set of metadata associated with the old software.

25. The network element of claim 21, wherein the backup controller card is configured to support translation of one or more of adding a field to an active state data structure, removing field, modifying a field, rearranging two or more fields, assigning a new field a default value, and changing a literal value associated with an enumerated constant.

26. The network element of claim 21, therein the active controller card is configured to:

receive the new software;

install the new software on active controller card; and

synchronize the active state of the network element with the backup controller card.