Token Server Registry for Multi-Entity Transaction Tracking

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In complex transaction ecosystems, it is challenging for token servers to track the distribution and maintain the integrity of tokens as they are passed between multiple entities, leading to difficulties in ensuring the token's validity and security.

Innovation Solution

The implementation of hash functions to trace and record the distribution of token credentials across entities, where each entity generates and transmits a hashed value to the token server, creating a chain of custody and ensuring the token's integrity.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If tokens are passed between multiple entities in complex ecosystems, then the versatility and applicability of tokenized transactions is improved, but the difficulty of tracking and measuring token distribution and integrity increases

Engineering Contradiction:
Improvetoken distribution capabilityVSAvoidtoken tracking difficulty
Core Design Contradiction:
Adaptability or versatilityVSDifficulty of detecting and measuring

Solution Approach 1:

A token server acts as an intermediary between multiple entities in the token distribution chain. The server receives tokens from token requestors, maintains a registry of token distributions, and provides validation services to subsequent entities. This intermediary approach enables complex multi-entity token passing while centralizing the tracking and measurement functions, thereby resolving the contradiction between enhanced versatility and tracking difficulty

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system implements feedback mechanisms where entities receiving tokens must provide verification information back to the token server. The server maintains a registry that records each token distribution event and uses this feedback to validate subsequent token presentations. This feedback loop enables the system to track token flow through multiple entities while maintaining security and integrity, thus solving the tracking difficulty in complex ecosystems

Inventive Principle:
Principle #23Feedback

2Reliability

If the token server tracks all token handoffs through multiple entities, then the reliability and security of token integrity is improved, but the device complexity and operational overhead increases

Engineering Contradiction:
Improvetoken integrity assuranceVSAvoidtracking system complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent extracts the complex tracking and validation logic from individual entity systems and consolidates it into a centralized token server. The server maintains a registry that stores token distribution information and validation rules, thereby simplifying the overall system architecture. Individual entities only need to interact with the server for token issuance and validation, reducing their operational complexity while maintaining high reliability through centralized control

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The token server performs multiple functions: it issues tokens to requestors, tracks token distributions in a registry, validates token presentations, and provides verification services to multiple entities. This multi-functional approach consolidates what would otherwise require separate systems at each entity, reducing overall device complexity while maintaining comprehensive tracking and high reliability through a single coordinated system

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

Data Source

PatentUS12067558B2Method of distributing tokens and managing token relationships
Publication Date: 2024.08.20 VISA INTERNATIONAL SERVICE ASSOCIATION
  • US12067558B2 patent drawing
  • US12067558B2 patent drawing
  • US12067558B2 patent drawing

AI summary

A method for facilitating a transaction may include generating, via a token server computer, a token for use by a first entity computer, wherein the token is generated in response to a request received from the first entity computer. The method may also include transmitting, via the token server computer, the token to the first entity computer, wherein the first entity computer transmits the token to a second entity computer. The method may also include receiving, at the token server computer and from the first entity computer, data indicative of the second entity computer successfully receiving the token. The data may include a hashed value derived from at least the token, data indicative of an identity of the second entity computer, and writing, by the token server computer, the data indicative of the second entity computer successfully receiving the token to a registry.