Browse Prior Art Database

Method for Efficiently Validating 'Completeness' of Changes in a Provisioning System

IP.com Disclosure Number: IPCOM000019002D
Original Publication Date: 2003-Aug-25
Included in the Prior Art Database: 2003-Aug-25
Document File: 4 page(s) / 60K

Publishing Venue

Motorola

Related People

Timothy Sherburne: INVENTOR [+2]

Abstract

Within a Network Management Provisioning System it is required that provisioning changes be validated before distribution of those changes into the network. It is the provisioning system's responsibility to make sure that Network Elements are configured with correct and complete configuration information.

This text was extracted from a Microsoft Word document.
At least one non-text object (such as an image or picture) has been suppressed.
This is the abbreviated version, containing approximately 64% of the total text.

Method for Efficiently Validating ‘Completeness’ of Changes in a Provisioning System

By Timothy Sherburne, Ibrahima Niass

Motorola, Inc.

Global Telecom Solutions Sector

ABSTRACT

Within a Network Management Provisioning System it is required that provisioning changes be validated before distribution of those changes into the network. It is the provisioning system’s responsibility to make sure that Network Elements are configured with correct and complete configuration information.

In a typical provisioning system the ‘completeness’ validation rules are executed as a batch operation before submission of any changes into the network.

This paper proposes a more efficient alternative to batch ‘completeness’ validation checking via the maintenance of a ‘completeness violations log’.

PROBLEM

Within a Network Management Provisioning System it is required that provisioning changes be validated before distribution of those changes into the network. It is the provisioning system’s responsibility to make sure that Network Elements are configured with correct and complete configuration information. An examples of ‘completeness’ validation may be that “Every ‘Cell Site’ must contain at lease one ‘Base Radio’”. In a typical provisioning system the ‘completeness’ validation rules are executed as a batch operation before submission of any changes into the network.

Batch ‘completeness’ validation has the following drawbacks:

·        The Provisioner does not receive immediate feedback to provisioning changes which cause completeness violations.

·        When attempting to submit a set of provisioning changes to the network, it is very time consuming to determine if the set of changes produce a ‘complete’ network configuration.

SOLUTION

This paper proposes a more efficient alternative to batch ‘completeness’ validation checking via the maintenance of a ‘completeness violations log’.

The completeness violations log is updated as individual provisioning changes are proposed and has the following advantages over bulk validation:

·        The Provisioner receives immediate feedback, to provisioning changes which cause completeness violation, by allowing the provisioner to simply view the log.

·        When attempting to submit a set of provisioning changes to the network, it is very efficient to determine if the current set of changes produce a ‘complete’ network configuration by allowing a simple check to see if the completeness violations log is empty.

OPERATION

Figures 1, 2 and 3 describe the mechanisms for maintaining a ‘Completeness Violations Log’.

                       
       
     
 
 
         
     

2. Create Draft Workspace

 
 
 

Figure 1. – Prepare

 

  1. The Provisioner makes a request to prepare the provisioning system for a set of provisioning changes.
  2. The Provisioning System creates a draft workspace to store and validate a set of provisioning changes.

Figure 2. – Change

 

  1. The Provisi...