Electronic Signature Verification via Server Intermediary
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing systems lack an efficient method for third-party verification of electronically signed electronic resources, making it difficult to confirm the identity of users who have electronically signed documents or files, especially in scenarios where verification is required by recipients or other parties.
Innovation Solution
A method and system that involves associating electronically signed resources with unique identifiers, allowing clients to request and verify the identity of the signer through various representations (alphanumeric, ultrasonic audio signals, or optical machine-readable formats) using a server-based verification process, enabling third-party confirmation of electronic signatures.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If electronic resources are signed electronically without a verification system, then the signing process is simple and fast, but third parties cannot confirm the identity of the signer
Solution Approach 1:
The patent introduces a server as an intermediary between the client device and the electronic resource storage system. The server receives verification requests, queries the electronic signature information, and returns verification results. This intermediary approach enables third-party verification without requiring direct access to the signature storage system, thus improving reliability while managing complexity through a dedicated verification component.
Solution Approach 2:
The verification system is segmented into distinct functional components: (1) the electronic signature application for creating and storing signatures, (2) the server for processing verification requests, and (3) the client device for initiating verification. This segmentation allows each component to specialize in its function, improving overall system reliability while enabling modular implementation that manages complexity.
2Adaptability or versatility
If a verification system is implemented to confirm signer identity, then third-party verification capability is improved, but the system complexity increases
Solution Approach 1:
The server implements a universal verification interface that can handle verification requests for any electronically signed resource regardless of the specific application or document type. The system uses standardized data structures (JSON format for requests and responses) that enable versatile verification across different platforms and applications, improving adaptability while reducing complexity through standardization.
Solution Approach 2:
The system creates a verification copy of the signature information by querying the original electronic signature data and returning a representation of the verification status without transferring the actual signed resource. This copying approach enables verification capability while maintaining security and managing system complexity by working with data representations rather than the complete signed resources.
3Measurement precision
If detailed signer information is stored and verified, then verification accuracy is improved, but data storage and processing requirements increase
Solution Approach 1:
The system extracts only the essential verification information (signer identity, signature timestamp, and verification status) from the complete electronic signature data set. By taking out only the critical elements needed for verification rather than storing and processing all signature metadata, the system achieves high measurement precision for identity verification while minimizing the quantity of stored and processed data.
Data Source
AI summary
A method comprising: storing, at a server, an electronic resource that has been electronically signed by a user; associating the electronic resource with an identifier; receiving, at the server and from a client device, a request to identify the user who electronically signed the electronic resource, the request including a reference to the identifier; responsive to receiving the request to identify the user who electronically signed the electronic resource, identifying, based on the reference to the identifier, the electronic resource stored at the server; responsive to identifying the electronic resource stored at the server, identifying the user who electronically signed the identified electronic resource; and transmitting, from the server to the client device, an indication of an identity of the user who electronically signed the electronic resource.