Access Token Account Linking for Secure Multi-Partition Access

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing systems face challenges in securely managing access to multiple data partitions with different access controls using a single user input, particularly in scenarios involving multiple devices and applications, without compromising user privacy and compliance with regulations like HIPAA and GDPR.

Innovation Solution

A system that generates and associates data partitions using access tokens, allowing a single user input to trigger the creation of a second account and establish a communication session between devices, while ensuring secure access management and compliance with privacy regulations.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If a single user input is used to access multiple data partitions, then ease of operation is improved, but security and access control are worsened

Engineering Contradiction:
Improveease of operationVSAvoidsecurity
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The system segments data access into multiple isolated data partitions (e.g., first data partition with first data, second data partition with second data). Each partition maintains independent access controls, preventing unauthorized cross-access while allowing controlled sharing through explicit token-based permissions.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system introduces an intermediary access token mechanism that mediates between user input and data partitions. The processor generates access tokens that encode specific permissions, acting as a secure intermediary that enables controlled access across partitions without compromising security or requiring direct user credentials in each partition.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If multiple data partitions with different access controls are created, then security is improved, but device complexity is worsened

Engineering Contradiction:
ImprovesecurityVSAvoiddevice complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system implements a universal access token mechanism that works across all data partitions. The token generation and validation system provides multi-functional capability, handling authentication, authorization, and access control uniformly across different partitions, thereby reducing overall system complexity despite the presence of multiple secured data partitions.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Solution Approach 2:

The system changes the parameter of access control from complex per-partition configuration to token-based permission encoding. By embedding access control parameters within portable tokens rather than hardcoding them in each partition, the system simplifies management of multiple data partitions while maintaining strong security controls.

Inventive Principle:
Principle #35Parameter changes

3Reliability

If access tokens are used to manage data partition access, then security is improved, but processing time is worsened

Engineering Contradiction:
ImprovesecurityVSAvoidprocessing time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system performs preliminary action by pre-generating and caching access tokens with encoded permissions before actual data access operations. This advance preparation of access credentials eliminates the need for complex real-time authentication queries, reducing processing time while maintaining security during actual data partition access operations.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS12512092B1Accessing account data based on access tokens
Publication Date: 2025.12.30 AMAZON TECH INC
  • US12512092B1 patent drawing
  • US12512092B1 patent drawing
  • US12512092B1 patent drawing

AI summary

Techniques for generating and associating accounts in support of communication sessions are described. In an example, a system receives, from a first device, input data indicating that an action is requested, the input data associated with a first account. The system determines that a second account is to perform the action and enables generation of the second account using first data that indicates the first account. The system receives a first access token associated with the first account and a second access token associated the second account and stores, in the first account, second data that comprises the second access token. The system receives third data associated with establishing a communication session. The third data indicates a third account associated with the action. The system enables establishment of the communication session with the first device and a second device associated with the third account.