Method for supporting new network element software versions in an element management system without upgrading

A machine-readable volatile or non-volatile storage medium storing one or more sequences of instructions for configuring a device, wherein execution of the one or more sequences of instructions by one or more processors causes the one or more processors to perform the steps of:

• storing, at a server, base version data that describes a first data model, wherein the first data model is for a first version of a software application hosted on a network element;
• using, by server software on the server, the base version data to communicate with the first version of the software application to provision a service on the network element;
• receiving, at the server, incremental version data that describes changes between the first data model and a second data model for a second version of the software application;
• correlating, at the server, the incremental version data with the base version data;
• and at least initially, overlaying the incremental version data with the base version data to form merged version data that describes the second data model;
• and
• without upgrading the server software on the server, using, by the server software on the server, the merged version data to communicate with the second version of the software application to provision a new service on the network element.

An apparatus for configuring a device, comprising:

• one or more processors;
• and
• a machine-readable volatile or non-volatile medium carrying one or more sequences of instructions for configuring a device, wherein execution of the one or more sequences of instructions by one or more processors causes the one or more processors to perform the steps of:
• storing, at a server, base version data that describes a first data model, wherein the first data model is for a first version of a software application hosted on a network element;
• using, by server software on the server, the base version data to communicate with the first version of the software application to provision a service on the network element;
• receiving, at the server, incremental version data that describes changes between the first data model and a second data model for a second version of the software application;
• correlating, at the server, the incremental version data with the base version data;
• and at least initially, overlaying the incremental version data with the base version data to form merged version data that describes the second data model;
• and
• without upgrading the server software on the server, using, by the server software on the server, the merged version data to communicate with the second version of the software application to provision a new service on the network element.