Credential Management with Codebook Formats for Distributed Validation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Decentralized heterogeneous transaction systems face challenges in credential management, particularly in ensuring secure and efficient credential generation and validation across geographically distributed nodes with varying service requirements and constraints on data usage, while maintaining compatibility with existing transaction protocols.

Innovation Solution

A method using a codebook to identify a specific data format for credential generation and validation, allowing a common data envelope to be used across different service contexts, with a service adaptation process to format proofs according to client requirements, and a deterministic process for key management to ensure secure and scalable credential handling.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If a centralized system is used to manage credentials, then credential validation can be performed, but the system cannot scale to exceptionally large numbers of geographically distributed clients

Engineering Contradiction:
Improvesystem scalabilityVSAvoidsystem architecture complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The centralized credential management system is segmented into multiple distributed nodes, each capable of independently generating and validating credentials. This segmentation allows the system to scale to large numbers of clients while maintaining credential management functionality through a network of distributed servers rather than a single central system.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

Each distributed node is designed with universal functionality to both generate and validate credentials, eliminating the need for separate centralized validation infrastructure. This multi-functionality enables any node in the distributed network to serve as both a credential issuer and validator, enhancing system scalability.

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

2Productivity

If different service instances are distributed across multiple nodes, then system scalability improves, but nodes cannot relate to each other to validate past service performance

Engineering Contradiction:
Improvesystem scalabilityVSAvoidservice history information
Core Design Contradiction:
ProductivityVSLoss of information

Solution Approach 1:

The system implements feedback mechanisms where validation nodes can query generation nodes for credential generation information and where service performance data is fed back across the distributed network. This allows nodes to relate to each other and validate past service performance while maintaining distribution and scalability.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

An intermediary communication protocol and data structure are introduced between distributed nodes to enable information exchange about credential generation and service performance. This intermediary layer allows nodes to share necessary information without requiring direct point-to-point connections, maintaining system scalability while enabling validation.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Adaptability or versatility

If long-established transaction protocols are used, then compatibility with installed base is maintained, but severe constraints on data amount limit credential information

Engineering Contradiction:
Improveprotocol compatibilityVSAvoidcredential data amount
Core Design Contradiction:
Adaptability or versatilityVSQuantity of substance

Solution Approach 1:

The credential information is extracted and separated into essential validation data that can be transmitted within existing protocol constraints and supplementary data that can be retrieved through additional distributed queries. This extraction allows compatibility with established protocols while providing access to complete credential information through the distributed network.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The system moves from a single-dimension approach where all credential data must be transmitted in one message to a multi-dimensional approach where credential data is distributed across multiple communication dimensions - initial compact transmission within protocol constraints followed by supplementary retrieval through distributed node queries, effectively bypassing data amount limitations.

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

4Loss of energy

If a common data format is used across all service contexts, then messaging bandwidth is reduced, but diverse client requirements cannot be met

Engineering Contradiction:
Improvemessaging bandwidth usageVSAvoidservice context flexibility
Core Design Contradiction:
Loss of energyVSAdaptability or versatility

Solution Approach 1:

The system uses a common data format structure with local quality variations - a standardized envelope format is used for all credentials to reduce messaging bandwidth, while allowing node-specific customization of credential content and validation parameters to meet diverse client requirements. Each node can tailor the credential data within the standardized format to its specific service context.

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

The credential data format is designed to be dynamic, allowing the same basic structure to adapt to different service contexts through configurable parameters and optional data elements. This dynamic format maintains bandwidth efficiency through a common structure while providing flexibility to meet diverse client requirements through adaptive content configuration.

Inventive Principle:
Principle #15Dynamics

Data Source

PatentEP4432141B1Credential management in a decentralized heterogeneous transaction system
Publication Date: 2025.07.23 MASTERCARD INT INC
  • EP4432141B1 patent drawingFigure 1~2
  • EP4432141B1 patent drawingFigure 3
  • EP4432141B1 patent drawingFigure 4

AI summary

Methods of providing a secure service at a computing node for a requesting party external to the computing node are described. One method comprises receiving a service request comprising a request to generate a credential. Service requirements of the requesting party are determined from the service request. The credential is then generated, and any further data needed to meet service requirements of the requesting party is obtained. A credential data format is determined to meet the service requirements and a code value for the credential data format is established. The code value, the credential and the further data are then stored in the credential data format, and a message comprising the credential in the credential data format is sent to the requesting party. Another method comprises receiving a service request comprising a request to validate a credential, wherein the credential is provided in a credential data format. The credential data format is determined from a code value stored in the credential data format. The credential and further data relating to service requirements are extracted from the credential data format, and the credential is validated. A message comprising a validation result is then sent to the requesting party. Apparatus suitable to perform these methods is also described.