Federated Query Processing for Network Management System Migration

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Migrating a network device deployment from one NMS cluster to another is costly and time-consuming, and is hindered by jurisdictional privacy regulations that restrict the movement of data related to identified or identifiable natural persons.

Innovation Solution

Implementing a federated query processing architecture that allows for the retention of most NMS cluster information data in the original cluster for a data retention period, with minimal data migration of non-transitory network artifact data, and intelligently directing queries based on query time and data retention status.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If complete data migration is performed from the first NMS cluster to the second NMS cluster, then the network device deployment can be fully migrated to the new cluster, but the migration time and cost increase significantly

Engineering Contradiction:

Improvemigration completenessVSAvoidmigration time

Core Design Contradiction:

ReliabilityVSLoss of time

Solution Approach 1:

The patent segments the NMS cluster data into two categories: network artifact data (which is migrated) and network telemetry metric data (which is retained in the original cluster). This segmentation allows selective migration of only critical data, reducing migration time and cost while maintaining operational reliability through federated query processing that can access data from both clusters.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The patent introduces a federated query processing layer that acts as an intermediary between the NMS cluster and the data sources. This intermediary enables seamless access to data across multiple clusters without requiring complete data migration, thereby reducing migration time and cost while maintaining data accessibility.

Inventive Principle:

Principle #24Intermediary (Mediator)

2Reliability

Engineering Contradiction:

Improvemigration completenessVSAvoidmigration cost

Core Design Contradiction:

ReliabilityVSEase of manufacture

Solution Approach 1:

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

Instead of migrating all data, the patent creates a federated view that copies only the necessary network artifact data to the new cluster while maintaining references to the original telemetry data in the source cluster, significantly reducing migration costs while preserving data accessibility.

Inventive Principle:

Principle #26Copying

3Adaptability or versatility

If data is migrated to a different NMS cluster, then the network device deployment can be relocated, but jurisdictional privacy regulations may be violated

Engineering Contradiction:

Improvecluster relocation capabilityVSAvoidprivacy regulation compliance

Core Design Contradiction:

Adaptability or versatilityVSObject-affected harmful factors

Solution Approach 1:

The patent segments data into network artifacts (migrated) and network telemetry metrics (retained in original cluster), ensuring that personally identifiable information remains in the original jurisdictional cluster while allowing the NMS deployment to relocate to a different cluster for operational flexibility.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The federated query processing layer acts as an intermediary that enables the NMS cluster to relocate while maintaining compliance with jurisdictional privacy regulations by keeping sensitive telemetry data in the original cluster and only migrating non-sensitive network artifact data.

Inventive Principle:

Principle #24Intermediary (Mediator)

4Loss of time

If minimal data migration is performed, then migration time and cost are reduced, but data accessibility across clusters may be compromised

Engineering Contradiction:

Improvemigration timeVSAvoiddata accessibility

Core Design Contradiction:

Loss of timeVSLoss of information

Solution Approach 1:

The federated query processing layer acts as an intermediary that provides seamless data accessibility across clusters without requiring complete data migration. It enables queries to be routed to the appropriate cluster based on data location, maintaining full data accessibility while minimizing migration requirements.

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The federated query processing architecture provides universal access to data across multiple clusters through a single interface, enabling the system to function as if all data were locally available while actually distributing data across clusters to reduce migration requirements.

Inventive Principle:

Principle #6Universality (Multi-functionality)

Data Source

PatentUS20250139117A1Network management system clusters having federated query processing

Publication Date: 2025.05.01 HEWLETT PACKARD ENTERPRISE DEV LP

AI summary

A process includes, responsive to a migration of a network device deployment from a first network management system cluster to a second network management system cluster, retaining first data in the first network management system cluster for a retention period. The data represents information about the network device deployment. The process includes receiving, by a federation layer engine of the second network management system cluster, a given query directed to information associated with the network device deployment. The process includes determining, by the federation layer engine, whether a query time that is associated with the given query is within the retention period and processing, by the federation layer engine, the given query responsive to the determination of whether the query time is within the retention period.