Method for supporting new network element software versions in an element management system without upgrading
First Claim
1. A method comprising:
- 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 the server;
without upgrading software of the server, receiving, at the server, incremental version data that describes changes between the first data model for the first version of the software application and a second data model for a second version of the software application;
wherein the second data model is a data representation schema for the second version of the software application;
correlating and overlaying the incremental version data with the base version data to form merged version data that describes the second data model, and which comprises at least one element that is present in the incremental version data and not present in the base version data; and
the server using the merged version data, without upgrading the server to the second version of the software application, to communicate with the second data model associated with the second version of the software application hosted on a network element to provision a new service on the network element, and using the base version data to communicate with the first data model to provision services on another network element;
wherein the method is performed by one or more computing devices.
0 Assignments
0 Petitions
Accused Products
Abstract
A method and apparatus for configuring an element management system server (an EMS server) to support new network element service application versions without upgrading the EMS server software is provided. The EMS stores base version data that describes the data model of a first version of a service application installed on a network element. When a second version of the service application is available, incremental version data describing changes to the data model from the first version to the second version is obtained and stored. In response to receiving a client request involving a service application on a particular network element, the EMS may apply incremental version data, associated with the version of the service application installed on the particular network element, to the base version data to form merged version data that describes the data model of the version of the service application installed on the particular network element.
-
Citations
20 Claims
-
1. A method comprising:
-
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 the server; without upgrading software of the server, receiving, at the server, incremental version data that describes changes between the first data model for the first version of the software application and a second data model for a second version of the software application; wherein the second data model is a data representation schema for the second version of the software application; correlating and overlaying the incremental version data with the base version data to form merged version data that describes the second data model, and which comprises at least one element that is present in the incremental version data and not present in the base version data; and the server using the merged version data, without upgrading the server to the second version of the software application, to communicate with the second data model associated with the second version of the software application hosted on a network element to provision a new service on the network element, and using the base version data to communicate with the first data model to provision services on another network element; wherein the method is performed by one or more computing devices. - View Dependent Claims (2, 3, 4, 5, 6)
-
-
7. A method comprising:
-
storing, at a server, base version data that describes a first data model, wherein the first data model is for a version of a first software application hosted on the server; storing, 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 first software application; correlating and overlaying the incremental version data with the base version data to form merged version data that describes the second data model and which comprises at least one element that is present in the incremental version data, but not in the base version data; storing, at the server, merged version data; collecting, at the server, second base version data about a service application hosted by a second network element; based on the second base version data, determining that the second network element is executing an unknown software application version of the service application for which the server is not storing incremental version data, or merged version data; in response to determining that the second network element is executing the unknown software application version of the service application, without upgrading the server to the unknown software application version of the service application, requesting and receiving from an incremental version source, second incremental version data and not the unknown software application version of the service application, wherein the second incremental version data describes changes between a base data model for base data and a third data model associated with the unknown software application version, and is used, at least in part, to communicate with the second network element, hosting the unknown software application version of the service application, to provision the second network element; wherein the third data model is a data representation schema for the unknown software application version. - View Dependent Claims (8, 9, 10, 11, 12)
-
-
13. A non-transitory computer-readable volatile or non-volatile storage medium storing one or more sequences of instructions which, when executed by one or more processors, cause the one or more processors to perform:
-
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 the server; without upgrading software of the server, receiving, at the server, incremental version data that describes changes between the first data model for the first version of the software application and a second data model for a second version of the software application; wherein the second data model is a data representation schema for the second version of the software application; correlating and overlaying the incremental version data with the base version data to form merged version data that describes the second data model, and which comprises at least one element that is present in the incremental version data and not in the base version data; and the server using the merged version data without upgrading the server to the second version of the software application to communicate with the second data model associated with the second version of the software application hosted on a network element to provision a new service on the network element, and using the base version data to communicate with the first data model to provision services on another network element. - View Dependent Claims (14, 15)
-
-
16. A non-transitory computer-readable volatile or non-volatile storage medium storing one or more sequences of instructions which, when executed by one or more processors, cause the one or more processors to perform:
-
storing, at a server, base version data that describes a first data model, wherein the first data model is for a version of a first software application hosted on the server; correlating and overlaying the incremental version data with the base version data to form merged version data that describes the second data model and which comprises at least one element that is present in the incremental version data and not in the base version data; storing, at the server, merged version data; storing, at the server, merged version data that describes the second data model by correlating and overlaying the incremental version data with the base version data; collecting, at the server, second base version data about applications hosted by a second network element; based on the second base version data, determining that the second network element is executing an unknown software application version of the service application for which the server is not storing incremental version data, or merged version data; in response to determining that the second network element is executing the unknown software application version of the service application, without upgrading the server to the unknown software application version of the service application, requesting and receiving from an incremental version source, second incremental version data and not the unknown software application, wherein the second incremental version data describes changes between a base data model for base data and a third data model associated with the unknown software application version, and is used, at least in part, to communicate with the second network element, hosting the unknown software application version of the service application, to provision the second network element; wherein the third data model is a data representation schema of the unknown software application version. - View Dependent Claims (17, 18, 19, 20)
-
Specification