Callback Pattern for Decentralized Identifier Attestation Verification

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional decentralized systems lack mechanisms for entities to verify the validity of attestations presented by others without knowing their identity, leading to potential interactions with invalid attestations.

Innovation Solution

Implementing a callback pattern for Decentralized Identifier (DID) attestations that includes contact metadata, allowing entities to contact the attestation provider directly for validation and verification, enabling negotiation of discounts or values without revealing the attestation owner's identity.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Loss of information

If entities use decentralized identifiers without a callback mechanism, then identity privacy is improved, but verification reliability deteriorates because entities cannot confirm attestation validity without knowing the owner's identity

Engineering Contradiction:
Improveidentity informationVSAvoidattestation verification
Core Design Contradiction:
Loss of informationVSReliability

Solution Approach 1:

The patent implements a feedback mechanism where the verifying entity sends a callback request to the attestation provider after receiving an attestation. The provider responds with verification information indicating whether the attestation is valid, creating a closed-loop feedback system that enables verification without revealing the owner's identity to the verifying entity.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The patent introduces an intermediary communication channel between the verifying entity and the attestation provider. The callback mechanism acts as this intermediary, allowing the verifying entity to query the provider about attestation validity through a controlled communication path that does not expose the owner's identity information.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If entities implement direct contact with attestation providers for verification, then verification capability is improved, but system complexity increases due to additional communication protocols and metadata handling

Engineering Contradiction:
Improveattestation verificationVSAvoidverification system
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent segments the verification process into distinct components: the attestation itself, the contact metadata embedded in the attestation, and the separate callback verification step. This segmentation allows each component to have a specific function and keeps the overall system architecture modular and manageable.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The callback mechanism serves multiple functions: it verifies attestation validity, provides verification information to the requesting entity, and maintains the privacy of the attestation owner. This multi-functionality reduces the need for separate verification systems and simplifies the overall architecture.

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

Data Source

PatentEP3942449B1Callback pattern for did attestations
Publication Date: 2024.05.29 MICROSOFT TECHNOLOGY LICENSING LLC
  • EP3942449B1 patent drawingFigure 1
  • EP3942449B1 patent drawingFigure 2
  • EP3942449B1 patent drawingFigure 3

AI summary

Embodiments disclosed herein are related to computing systems, computer program products, and methods for providing a callback pattern for DID attestations or claims. An attestation is provided from a first entity of a decentralized network to a second entity of the decentralized network. The attestation defines information about an owner of the attestation that has been generated by the first entity and that is to be used by the second entity. The attestation includes contact metadata that defines how to contact the first entity. In response to the attestation being provided to the second entity, the first entity is contacted using the contact metadata.