Mapping Account Information Across User and Identity Pools

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current software applications lack a searchable mapping between user account information stored in a user pool and identity information stored in an identity pool, limiting control and accessibility for users and application providers.

Innovation Solution

Implementing a data mapping protocol that securely associates user account information in a user pool with corresponding identity information in an identity pool, creating a searchable data structure that allows any uniquely identifying parameter to look up account information regardless of the pool it belongs to.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Loss of information

If login credentials and account identifier are stored in separate pools without mapping, then system architecture is simplified and security strategies are maintained, but account information searchability and user control are limited

Engineering Contradiction:
Improveaccount information searchabilityVSAvoidsystem architecture complexity
Core Design Contradiction:
Loss of informationVSDevice complexity

Solution Approach 1:

The patent introduces an intermediary mapping table that stores the relationship between login credentials (username, email) and account identifiers. This mapping table acts as a bridge between the user pool and identity pool, enabling searchable access to account information without directly coupling the two pools. The intermediary structure preserves the architectural separation while adding search functionality.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Ease of operation

If login credentials are stored in user pool and account identifier in identity pool without mapping, then native system architecture is preserved, but user control and information accessibility are reduced

Engineering Contradiction:
Improveuser control and information accessibilityVSAvoiddata structure complexity
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The patent segments the account information storage into distinct components: login credentials remain in the user pool, account identifiers remain in the identity pool, and the mapping relationship is stored separately in a mapping table. This segmentation allows each component to maintain its original purpose and security characteristics while enabling comprehensive searchability through the mapping structure.

Inventive Principle:
Principle #1Segmentation

3Loss of information

If no mapping exists between user pool and identity pool, then security strategies are maintained, but comprehensive account information retrieval is prevented

Engineering Contradiction:
Improveaccount information retrieval capabilityVSAvoidsecurity strategy integrity
Core Design Contradiction:
Loss of informationVSReliability

Solution Approach 1:

The mapping table serves as a secure intermediary that enables account information retrieval without compromising security strategies. By storing only the necessary mapping relationships (login credentials to account identifier) rather than full account data, the system enables comprehensive information retrieval while maintaining the security boundaries between user pool and identity pool.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS10972444B1Mapping account information
Publication Date: 2021.04.06 AMAZON TECH INC
  • US10972444B1 patent drawing
  • US10972444B1 patent drawing
  • US10972444B1 patent drawing

AI summary

The present disclosure provides a data mapping protocol that securely associates the account user information stored in the user pool with corresponding account identity information stored in the identity pool, such that all the account information is searchable, regardless of which pool the information is in. In an embodiment, a mapping service, which may be provided by the resource provider, obtains a set of login credentials and authenticates the login credentials with the user pool. In response to receiving the login credentials and an authentication request, the user pool returns the account credentials associated with the login credentials. The account credentials are used to access the account identifier, and other associate account identity data in the identity pool. Thus, the login credentials from the user pool and the account identifier from the identity are obtained and associated with each other in a searchable data structure.