Federated PII Mapping for Permissioned Trading History Access

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing trading systems lack efficient methods to map personally identifiable information (PII) from broker-dealer databases onto anonymized data from public distributed ledgers, compromising privacy and security while hindering access to comprehensive trading histories.

Innovation Solution

A federated PII service system that integrates broker-dealer databases with distributed ledgers, allowing permission-based mapping of PII onto public transaction data, using a PII mapping module to connect users with relevant databases and ledgers.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Loss of information

If PII is stored in broker-dealer databases for trading history, then comprehensive trading information is available, but privacy and security are compromised

Engineering Contradiction:
Improvetrading history informationVSAvoidprivacy and security risks
Core Design Contradiction:
Loss of informationVSObject-affected harmful factors

Solution Approach 1:

The patent introduces a federated PII service as an intermediary layer between users and broker-dealer databases. This service includes a PII mapping module that mediates access to PII by mapping anonymized distributed ledger data to relevant PII in broker databases, allowing users to obtain trading history without direct access to raw PII, thus resolving the contradiction between information availability and privacy protection

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system segments the trading information system into separate components: distributed ledgers storing anonymized transaction data, broker-dealer databases storing PII, and a federated PII service that coordinates between them. This segmentation allows each component to serve its specific function while maintaining security boundaries, enabling comprehensive trading history access without compromising overall system security

Inventive Principle:
Principle #1Segmentation

2Object-affected harmful factors

If distributed ledgers store anonymized trading data, then privacy is protected, but access to comprehensive trading histories is hindered

Engineering Contradiction:
Improveprivacy protectionVSAvoidtrading history accessibility
Core Design Contradiction:
Object-affected harmful factorsVSLoss of information

Solution Approach 1:

The federated PII service performs multiple functions: it receives requests from users, determines which broker-dealer databases contain relevant PII, receives permission information, and maps anonymized distributed ledger data to PII. This multi-functional service enables the system to maintain privacy while simultaneously providing comprehensive trading history access through intelligent data correlation

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

3Reliability

If permission-based access control is implemented, then security is improved, but system complexity increases

Engineering Contradiction:
ImprovesecurityVSAvoidpermission verification system
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system implements self-service permission verification where the federated PII service automatically determines which broker-dealer databases contain relevant PII and retrieves permission information without requiring manual intervention. The service autonomously coordinates between multiple databases and distributed ledgers, reducing operational complexity while maintaining security through automated permission checks

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS20250278518A1Federated personally identifiable information (PII) service
Publication Date: 2025.09.04 TZERO IP LLC
  • US20250278518A1 patent drawing
  • US20250278518A1 patent drawing
  • US20250278518A1 patent drawing

AI summary

A system comprises: first, second, third computing device(s) and distributed ledger(s). Third computing device(s) store PII for accounts. First computing device(s) receive request to obtain PII regarding public information for first account from first user of second computing device(s). First computing device(s) determine that the third computing device(s) includes PII regarding public information for first account. First computing device(s) determine whether first user has permission to obtain PII regarding public information for first account from third computing device(s) that includes PII regarding public information for first account. First computing device(s) receive public information for first account from distributed ledger(s) when first user has permission to obtain PII regarding public information for first account from third computing device(s) that includes PII regarding public information for first account. First computing device(s) provide PII regarding public information for first account to first user of second computing device(s).