Blockchain Identity Proofing via Contextual Relation Graphs
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current identity verification systems lack efficiency in data integration and provide inadequate security features, making it difficult to authenticate users and prevent fraudulent access while maintaining cost-effectiveness.
Innovation Solution
The system employs contextual information from access requests to build a relation graph, correlating data elements such as electronic signatures, device attributes, and user attributes to enhance user authentication and access control, allowing for improved recognition of user identities and prevention of fraudulent activities.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If traditional authentication credentials (username/password) are used, then user authentication is simple and widely compatible, but security against fraudulent access is insufficient
Solution Approach 1:
The patent segments authentication into multiple independent credential types (knowledge-based, possession-based, inherent-based) that can be combined. Each credential type is verified separately through different mechanisms (password checking, device ownership verification, biometric analysis), allowing systematic security enhancement without monolithic complexity
Solution Approach 2:
The patent employs composite authentication by combining multiple credential types and verification methods into a unified authentication framework. Different credential types (password, device token, biometric data) are integrated and weighted together to form a composite authentication score, enhancing security while maintaining manageable system architecture
2Ease of operation
If anonymous or pseudonymous access is allowed, then user privacy is protected and access is easier, but ability to deny access based on real identity is lost
Solution Approach 1:
The patent implements dynamic authentication where the required credential types and verification strictness adjust based on context. For low-risk operations, anonymous access with basic credentials suffices; for high-risk operations or identity-sensitive resources, the system dynamically requires additional verification layers including real identity confirmation
Solution Approach 2:
The system changes authentication parameters (required credential types, verification thresholds, trust weights) based on user identity status and access context. Anonymous users receive baseline authentication treatment, while verified users gain enhanced access with adjusted parameters, allowing flexible adaptation without sacrificing privacy for low-stakes operations
3Measurement precision
If multiple data sources are integrated for identity verification, then authentication accuracy improves, but data integration efficiency decreases
Solution Approach 1:
The patent performs preliminary actions by pre-registering and verifying user credentials across multiple data sources during onboarding. Biometric templates, device profiles, and identity attributes are预先 captured and stored with established trust relationships, eliminating the need for real-time multi-source querying during authentication and significantly improving verification speed
Solution Approach 2:
The patent introduces an intermediary authentication service that centralizes credential verification across multiple data sources. Instead of directly integrating numerous data sources, the intermediary service acts as a mediator that receives authentication requests, coordinates verification across trusted data sources, and returns consolidated results, simplifying the integration architecture while maintaining high verification accuracy
Data Source
AI summary
Systems and methods for managing a reputation score of a user based on successful and failed logins, successful and failed multifactor authentications, and profile changes is described. The method includes receiving, by a server, status information of a user event from one or more computing devices. The status information includes one or more of an indicator of a successful login, an indicator of a failed login, an indicator of a successful multifactor authentication, an indicator of a failed multifactor authentication, an indicator of a profile update, and metadata associated with the user event from the one or more computing devices. The server updates events based on a type of the status information received and storing the events in a data store and determines whether a problematic situation has occurred. A reputation score of the user is updated when the problematic situation is determined.