EMS Server Version Support via Incremental Data Merging

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing element management systems (EMS) require full software upgrades to support new network element software versions, leading to downtime and resource inefficiencies, as they cannot provision services on elements running unsupported versions without upgrading their own software.

Innovation Solution

The EMS server stores base version data and incremental changes to construct merged version data, allowing it to support new or older service application versions without a full software upgrade by correlating data models and providing necessary provisioning capabilities.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If the EMS server performs a full software upgrade to support new service application versions, then the EMS server can provision services on network elements running new software versions, but the EMS server becomes unavailable during the upgrade process causing service downtime

Engineering Contradiction:
Improvesupport for new service application versionsVSAvoidservice downtime during upgrade
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The patent segments the service application version support capability from the core EMS server software. Instead of upgrading the entire EMS server software stack, the system selectively loads only the necessary service application version support components (SAs) that correspond to the required service application versions. This allows the EMS server to gain support for new service application versions without performing a full software upgrade, thereby avoiding service downtime.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent implements preliminary action by pre-compiling and storing service application support packages (SAs) that contain all necessary information about different service application versions. These SAs are prepared in advance and can be selectively loaded onto the EMS server when needed. This preliminary preparation eliminates the need for time-consuming full software upgrades, as the EMS server can immediately load the required service application version support when a new version needs to be supported.

Inventive Principle:
Principle #10Preliminary action

2Adaptability or versatility

If the EMS server performs a full software upgrade to support new service application versions, then the EMS server can manage network elements with new software versions, but significant resources are consumed during the upgrade process

Engineering Contradiction:
Improvesupport for new service application versionsVSAvoidresources consumed during upgrade
Core Design Contradiction:
Adaptability or versatilityVSLoss of energy

Solution Approach 1:

The patent segments the resource-intensive upgrade process into selective component loading. Instead of consuming resources to upgrade the entire EMS server software stack, the system only loads the specific service application support components (SAs) that correspond to the required service application versions. This segmentation dramatically reduces the computational resources, time, and effort required to add support for new service application versions.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent uses copying by creating and storing service application support packages (SAs) that are self-contained copies of all necessary information about different service application versions. These SAs can be replicated and distributed to EMS servers as needed without requiring the server to undergo a full software upgrade process. The EMS server simply copies and loads the relevant SA files, consuming minimal resources compared to a full upgrade.

Inventive Principle:
Principle #26Copying

3Productivity

If the EMS server waits for periodic software updates to support new service application versions, then the EMS server software can be upgraded efficiently, but the EMS server cannot provision services using newly available service application versions until the next scheduled upgrade

Engineering Contradiction:
Improveefficiency of EMS server software upgradesVSAvoidability to provision services with new service application versions
Core Design Contradiction:
ProductivityVSAdaptability or versatility

Solution Approach 1:

The patent implements dynamics by making the service application version support capability dynamic and on-demand. Instead of being locked into periodic upgrade cycles, the EMS server can dynamically load new service application support packages (SAs) at any time when a new service application version becomes available. This dynamic capability allows the system to adapt immediately to new service application versions without waiting for scheduled upgrades, while still maintaining the efficiency of selective, targeted updates rather than full periodic regrades.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The patent introduces an intermediary mechanism in the form of service application support packages (SAs) that act as mediators between the EMS server and new service application versions. These SAs serve as the intermediary layer that allows the EMS server to support new service application versions without requiring a full software upgrade. The SAs contain all necessary information about service application versions and can be selectively loaded, enabling the EMS server to bridge the gap between its current software version and new service application requirements.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS7926033B2Method for supporting new network element software versions in an element management system without upgrading
Publication Date: 2011.04.12 CISCO TECHNOLOGY INC
  • US7926033B2 patent drawing
  • US7926033B2 patent drawing
  • US7926033B2 patent drawing

AI summary

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.