Identity Index for Distributed Data Management

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current systems management methods for enterprise computer networks face inefficiencies due to data centralization, leading to increased administrative overhead, inconsistencies, and high bandwidth demands, particularly in heterogeneous environments where synchronizing data across different systems is challenging.

Innovation Solution

A system and method using an identity index to manage distributed information, where a software program maintains virtual identities for users, connecting to multiple resources and mapping attributes across different systems without replicating data, thereby reducing storage and bandwidth requirements and enhancing scalability.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If data is centralized in a centralized database, then data consistency is improved, but storage requirements and bandwidth demands increase significantly

Engineering Contradiction:
Improvedata consistencyVSAvoidstorage requirements
Core Design Contradiction:
ReliabilityVSQuantity of substance

Solution Approach 1:

The patent extracts only the essential indexing information (identifiers, relationships, and metadata) from the distributed data sources, storing this minimal subset in the centralized database. The actual data remains distributed at its original locations, eliminating the need to replicate entire data sets while maintaining the ability to track and manage data relationships centrally.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent introduces an intermediary indexing layer that sits between the distributed data sources and the centralized database. This index acts as a mediator that references distributed objects without requiring their full replication, enabling centralized management of data relationships while preserving data distribution and reducing storage requirements.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Productivity

If data is replicated at a centralized database, then data access efficiency is improved, but bandwidth consumption increases due to continuous synchronization

Engineering Contradiction:
Improvedata access efficiencyVSAvoidbandwidth consumption
Core Design Contradiction:
ProductivityVSLoss of energy

Solution Approach 1:

The patent extracts only the essential indexing information (identifiers, relationships, and metadata) from the distributed data sources, storing this minimal subset in the centralized database. The actual data remains distributed at its original locations, eliminating the need to replicate entire data sets while maintaining the ability to track and manage data relationships centrally.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent performs preliminary indexing of distributed data sources, creating reference structures in advance that enable efficient data access without requiring continuous data replication. The index is built once and maintained through incremental updates, avoiding the need for continuous bandwidth-intensive synchronization of full data sets.

Inventive Principle:
Principle #10Preliminary action

3Ease of operation

If data is centralized for management, then administrative control is improved, but system complexity increases due to synchronization challenges across heterogeneous systems

Engineering Contradiction:
Improveadministrative controlVSAvoidsystem complexity
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The patent introduces an intermediary indexing layer that sits between the distributed data sources and the centralized database. This index acts as a mediator that references distributed objects without requiring their full replication, enabling centralized management of data relationships while preserving data distribution and reducing storage requirements.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent segments the data management system into two distinct components: a centralized index for management and control, and distributed data sources for storage and processing. This segmentation allows administrative control to be exercised over the index structure and relationships while leaving the actual data sources independent and heterogeneous, reducing synchronization complexity.

Inventive Principle:
Principle #1Segmentation

4Reliability

If distributed data sources are synchronized, then data consistency is improved, but political tensions arise from resource favoritism in heterogeneous environments

Engineering Contradiction:
Improvedata consistencyVSAvoidresource neutrality
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The patent introduces an intermediary indexing layer that sits between the distributed data sources and the centralized database. This index acts as a mediator that references distributed objects without requiring their full replication, enabling centralized management of data relationships while preserving data distribution and reducing storage requirements.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent inverts the traditional synchronization approach by not synchronizing the actual data between heterogeneous systems. Instead, it synchronizes only the index references and metadata, allowing each distributed data source to maintain its own data independently while the index provides a unified view, thereby eliminating resource favoritism.

Inventive Principle:
Principle #13The other way round (Inversion)

Data Source

PatentUS7941785B2System and method for managing information objects
Publication Date: 2011.05.10 SUN MICROSYSTEMS INC
  • US7941785B2 patent drawing
  • US7941785B2 patent drawing
  • US7941785B2 patent drawing

AI summary

A system and method for managing information on a network using an identity index may include a software program stored on a computer-readable medium which is operable to associate one or more users with the information objects that define the user. The software program can maintain a “virtual identity” for each user, the virtual identity comprising a list of information objects (e.g., accounts) associated with the user and the identities of resources at which the information objects can be found. The list of information objects may include an information object identifier for each information object. The software program may maintain a resource definition for each identified resource. The resource definition may include a set of connection parameters that can be used by the software program to connect to the corresponding resource.