Database Migration Service for Network Element Circuit Data

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current methods for migrating circuit provisioning data from one network element (NE) to another are inefficient, prone to data omission or duplication, and can cause conflicts due to differences in database formats and vendor-specific information, especially when aggregating multiple systems or migrating older NEs to newer ones with increased circuit capacity.

Innovation Solution

A system and method that extracts raw circuit data from a first NE, formats it into data files, filters to verify uniqueness and integrity, and creates a migration file using Structured Query Language (SQL) and Perl scripts to ensure no data is omitted or duplicated, and imports this file into a second NE's database, thereby ensuring compatibility with the new NE's conventions.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If traditional SQL commands or scripts are used to export and import database data during NE migration, then the migration process can be performed with basic tools, but data verification is difficult and data conflicts may occur

Engineering Contradiction:
Improvedata integrityVSAvoidmigration system complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent introduces a migration verification service as an intermediary component between the source and target database systems. This service extracts data from the source database, verifies its completeness and uniqueness, and then imports it to the target database. The intermediary performs verification operations including checking for duplicate entries, ensuring all required data is present, and validating data format compatibility, thereby resolving the contradiction between maintaining data integrity and avoiding complex migration systems.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The migration verification service implements feedback mechanisms by continuously monitoring the migration process and providing verification results. It checks whether data has been correctly extracted, verifies uniqueness constraints, and provides feedback on any data conflicts or duplicates detected. This feedback loop ensures data integrity without requiring overly complex manual verification procedures.

Inventive Principle:
Principle #23Feedback

2Productivity

If multiple older NEs are aggregated onto a single new NE with increased circuit capacity, then network consolidation is achieved, but data conflicts and duplicate entries may occur

Engineering Contradiction:
Improvenetwork consolidation efficiencyVSAvoiddata uniqueness
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The migration verification service acts as an intermediary that processes data from multiple source NEs before importing to the target NE. It performs verification operations including detecting duplicate circuit entries, validating unique identifiers, and ensuring data consistency across aggregated systems. This intermediary layer enables network consolidation while maintaining data uniqueness through automated verification.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system performs preliminary verification actions before the actual data import to the target database. It pre-checks for duplicate entries, validates data format compatibility, and identifies potential conflicts between aggregated NEs. By performing these verification actions in advance, the system prevents data conflicts rather than detecting them after import, thereby maintaining data uniqueness during network consolidation.

Inventive Principle:
Principle #10Preliminary action

3Measurement precision

If comprehensive verification of all NE data is performed during migration, then data accuracy is improved, but migration time increases

Engineering Contradiction:
Improvedata verification accuracyVSAvoidmigration time
Core Design Contradiction:
Measurement precisionVSLoss of time

Solution Approach 1:

The migration verification service performs targeted verification operations on critical data elements rather than exhaustive verification of all data. It focuses verification efforts on unique identifiers, circuit configurations, and essential provisioning data that require high accuracy. By applying partial verification to the most critical fields, the system achieves sufficient data accuracy without the time cost of comprehensive verification of every data element.

Inventive Principle:
Principle #16Partial or excessive action

Solution Approach 2:

The verification process is segmented into distinct phases and operations. It separates verification of data extraction completeness, uniqueness validation, and format compatibility checking into sequential steps. This segmentation allows the system to perform necessary verification operations efficiently without redundant checks, thereby maintaining data accuracy while minimizing migration time.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS7634489B2Methods and systems for a network element database migration service
Publication Date: 2009.12.15 CIENA CORP
  • US7634489B2 patent drawing
  • US7634489B2 patent drawing
  • US7634489B2 patent drawing

AI summary

In various exemplary embodiments, the present invention provides methods and systems of extracting a database from one NE and importing a recreated database into another NE. The database includes NE circuit provisioning data and the like. The present invention is utilized when rolling traffic from one or more NEs to another NE. For example, a decommissioning of one or more older NEs to a new NE can utilize the present invention to migrate the circuit database from the one or more older NEs to the new NE. Advantageously, the present invention verifies that all NE data is extracted and that no data is omitted or duplicated and that the migrated data does not conflict with the new NE's database conventions.