Multi-Tenant Identifier Mapping for Conflict Resolution

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing systems face challenges in managing unique identifiers across different systems, leading to conflicts when data is moved or accessed between systems.

Innovation Solution

The creation and management of multi-tenant identifiers in a multi-tenant environment, where unique identifiers from single-tenant systems are replaced with multi-tenant identifiers to ensure uniqueness within the multi-tenant environment.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If unique identifiers from single-tenant systems are used directly in multi-tenant environment, then system simplicity is maintained, but identifier conflicts occur between different systems

Engineering Contradiction:
Improveidentifier compatibilityVSAvoididentifier uniqueness
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent introduces a mapping table as an intermediary component that stores the correspondence between source system identifiers and multi-tenant environment identifiers. When data is accessed or transferred, the mapping table mediates the identifier translation, ensuring that identifiers from different single-tenant systems do not conflict in the multi-tenant environment while maintaining the original identifiers' meaning and functionality.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If multi-tenant identifiers are created by combining source system identifier and identity provider, then identifier uniqueness is ensured, but system complexity increases

Engineering Contradiction:
Improveidentifier uniquenessVSAvoididentifier management complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent performs preliminary actions by pre-establishing the mapping between source system identifiers and multi-tenant identifiers in a mapping table before actual data access or transfer occurs. This preliminary setup includes storing the source system identifier, identity provider, and corresponding multi-tenant identifier relationships in advance, so that during runtime, the system only needs to perform simple lookups rather than complex identifier generation and conflict resolution.

Inventive Principle:
Principle #10Preliminary action

3Reliability

If source system identifiers are replaced with multi-tenant identifiers, then identifier conflicts are prevented, but lookup and translation overhead increases

Engineering Contradiction:
Improveidentifier conflict preventionVSAvoididentifier translation time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent creates a copy of the identifier mapping relationship in a dedicated mapping table that can be quickly queried. Instead of performing complex real-time identifier generation and conflict checking, the system copies the pre-determined mapping relationships into the mapping table, allowing for fast lookup operations. The mapping table stores ready-made identifier pairs that can be retrieved through simple key-based searches.

Inventive Principle:
Principle #26Copying

Data Source

PatentUS20250190415A1Managing Multi-Tenant Keys in Multi-Tenant Computing Environments
Publication Date: 2025.06.12 JIVE SOFTWARE LLC
  • US20250190415A1 patent drawing
  • US20250190415A1 patent drawing
  • US20250190415A1 patent drawing

AI summary

Technologies are described for managing multi-tenant identifiers (e.g., multi-tenant keys or multi-tenant database keys). Creating multi-tenant identifiers can comprise receiving a source system identifier from a source system, determining a source identity provider of the source system, creating a multi-tenant identifier representing a combination of the source system identifier and the source identity provider, and storing the created multi-tenant identifier. Using multi-tenant identifiers can comprise receiving a request to lookup a source system identifier, associated with a source system, in a multi-tenant identifier mapping table, determining a source identity provider of the source system, identifying an entry in the table with the source system identifier and the source identity provider, and returning a multi-tenant identifier associated with the identified entry in the table.