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.

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.

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.

Abstract: A method and apparatus for deploying EMS provisioning services is provided. A communication to administer a particular service on a network element is transmitted from an EMS client to an EMS server. The communication contains service data that describes a particular service to be administered on the network element. The EMS server constructs an instance of a generic record that stores the service data. The EMS server selects a service module to process the instance based on which service is associated with the service data stored in the instance. The instance is processed to produce result data that describes the result of processing the service data at the network element. The EMS server stores the result data in a persistent store. This generic framework enables communications between EMS clients and the EMS server involving different services to be processed similarly. New services are added without modification to the generic framework.

Abstract: A method for decomposing a service activation request (SAR) into sub-requests for specific network resources and classifying the SAR with an adaptive bucket value based on the dynamic performance characteristics of the corresponding network resources. Each SAR has a virtual bucket value whose size is determined by the bucket values of its constituent sub-requests. Over time, as multiple SARs are processed, the bucket values associated with each requested resource are adjusted to reflect system resource loading and availability. If the bucket value of a constituent sub-request is adaptively decreased down to a zero value, for instance due to an overflow condition or an excess of requests for that particular service, any new SAR requesting the same resource will be prevented from decomposition and processing. This will happen even if the sub-request is mature, i.e., due to be executed in the very near-term.

Abstract: An automated method and apparatus for classifying a customer service activation request (SAR) according to whether repeatable, schedulable, or scaleable elements are present. When the request has no repeating elements, a traditional SAR is forwarded and serviced by the network management system according to provisions well-known in the art. In the more complex case, however, a SAR comprises elements that are both repeatable and schedulable and is thus classified as a service activation module (SAM). An automated process first determines the starting quality of service (QoS) level at the beginning of the service life cycle requested by the customer. The process next determines the life cycle ending time as well as the trigger times at which elements repeat or are reinitiated. In some embodiments of the present invention, the SAM is examined for resource availability. If one or more resources are not available during the service life cycle, the process generates a report.