Decentralized Digital Identity Verification via DID Wallet and Hub

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current digital identity verification systems lack a complete decentralized solution, with no well-defined system for users to conveniently manage and verify digital identities, and existing technologies are in the initial phase of exploration for decentralized identity management.

Innovation Solution

A method and apparatus for verifying digital identity using a decentralized identity (DID) wallet and identity hub, which includes acquiring target login information, sending a login request with the user's DID to authorize the verifier to acquire a claim from the user's identity hub, and logging in using the verified DID and claim, with encryption and decryption mechanisms to ensure data security and ownership.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If a decentralized identity verification system is implemented, then user ownership and control of digital identities is improved, but system complexity and definition completeness worsens

Engineering Contradiction:
Improveuser ownership and controlVSAvoidsystem definition completeness
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system is divided into three independent modules: DID wallet (user端) for identity management, identity hub (middleware) for data storage and coordination, and verifier (service端) for verification operations. This segmentation allows each component to be developed and deployed independently, reducing overall system complexity while maintaining decentralized control.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The identity hub serves as an intermediary layer between the DID wallet and verifier, handling data storage, retrieval, and coordination. This mediator absorbs system complexity, providing a well-defined interface that simplifies interactions while enabling complete decentralized identity verification.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If proxy re-encryption mechanisms are used for secure data sharing, then data security is improved, but computational overhead and processing time worsen

Engineering Contradiction:
Improvedata securityVSAvoidprocessing time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

Public key pairs are generated in advance and registered with the identity hub before actual verification operations. The DID wallet and verifier both cache relevant public keys and encryption parameters, so that when verification is needed, the proxy re-encryption can proceed efficiently without key generation delays.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system implements automatic key management and certificate validation without manual intervention. The identity hub automatically handles key pairing, certificate issuance, and revocation checking, reducing processing time while maintaining security through automated cryptographic operations.

Inventive Principle:
Principle #25Self-service

Data Source

PatentEP3852338B1Method and apparatus for verifying digital identity, device and storage medium
Publication Date: 2023.09.06 BEIJING BAIDU NETCOM SCI & TECH CO LTD
  • EP3852338B1 patent drawingFigure 1~2
  • EP3852338B1 patent drawingFigure 3
  • EP3852338B1 patent drawingFigure 4

AI summary

Embodiments of the present disclosure disclose a method and apparatus for verifying digital identity, a device and a storage medium, and relate to the technical field of blockchain. An implementation of the method includes: acquiring target login information of a target verifier, in response to a login operation of a target user on the target verifier; sending, based on the target login information, a login request including a target user DID of a target user to the target verifier, to authorize the target verifier to acquire a target claim of the target user from an identity hub of the target user and verify the target user DID and the target claim; and logging in to the target verifier using the target user DID, in response to the target user DID and the target claim passing the verification.