Secure Document Workflow Automation for Identity Verification

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional secure document workflows experience bloat due to unnecessary activities, leading to storage and bandwidth constraints, as users are often required to repeat identity verification processes that have already been completed in previous workflows or under different circumstances.

Innovation Solution

A secure document service system that determines and modifies workflows based on user profile data and location, using machine learning to identify and omit redundant activities, and adapt to changes in user location by replacing identity verification protocols as needed.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If identity verification activities are included in secure document workflows, then security and compliance are ensured, but workflow bloat occurs leading to increased storage and bandwidth usage

Engineering Contradiction:
Improveidentity verification complianceVSAvoidbandwidth and storage efficiency
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

The system performs identity verification in advance and stores the verification results in user profiles. When a secure document workflow is initiated, the system checks whether the identity verification has already been completed by retrieving profile data, thereby avoiding redundant verification activities and reducing bandwidth and storage usage.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system dynamically modifies workflow parameters based on user profile data. When identity verification is found to be already completed in the user's profile, the system removes or modifies the corresponding verification activities from the workflow, adapting the workflow structure to avoid redundancy while maintaining compliance requirements.

Inventive Principle:
Principle #35Parameter changes

2Reliability

If comprehensive identity verification protocols are required for all users, then security standards are met, but workflow complexity and user burden increase

Engineering Contradiction:
Improvesecurity standard complianceVSAvoidworkflow structure
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

Identity verification is performed in advance and the results are cached in user profiles. The system retrieves this pre-computed verification data during document workflows, eliminating the need to repeat complex verification protocols and simplifying the workflow structure while maintaining security compliance.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system applies identity verification selectively based on user profiles and specific workflow contexts. Rather than uniformly applying comprehensive verification to all users and all documents, the system tailors the verification requirements to individual user histories and specific document types, reducing overall workflow complexity.

Inventive Principle:
Principle #3Local quality

3Reliability

If identity verification is repeated in each workflow, then current security requirements are satisfied, but time and user effort are wasted

Engineering Contradiction:
Improvecurrent security requirement satisfactionVSAvoidworkflow completion time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system performs identity verification once and stores the results in user profiles for future use. When subsequent workflows are initiated, the system retrieves the stored verification data from profiles, eliminating the need to repeat the verification process and significantly reducing workflow completion time while maintaining security requirements.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system implements a feedback mechanism where identity verification results are stored and reused across multiple workflows. The profile data serves as feedback that informs future workflow configurations, allowing the system to automatically determine when verification can be omitted based on previous successful verifications.

Inventive Principle:
Principle #23Feedback

4Measurement precision

If high resolution identity document images are required, then verification accuracy is improved, but storage and network bandwidth requirements increase

Engineering Contradiction:
Improveidentity verification accuracyVSAvoidnetwork bandwidth and storage
Core Design Contradiction:
Measurement precisionVSLoss of energy

Solution Approach 1:

High resolution identity document images are uploaded and verified in advance. The verified images are stored in user profiles, and subsequent workflows reference these pre-stored images rather than requiring re-uploads. This approach maintains verification accuracy while reducing network bandwidth usage in ongoing workflows.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system creates and stores copies of identity documents during initial verification. These copies are then reused across multiple workflows, eliminating the need to transmit the same high-resolution images repeatedly over the network, thereby reducing bandwidth consumption while maintaining verification accuracy through reference to the stored copies.

Inventive Principle:
Principle #26Copying

Data Source

PatentUS11989317B2Modifying elements of a secure document workflow based on change in profile of recipient
Publication Date: 2024.05.21 DOCUSIGN INC
  • US11989317B2 patent drawing
  • US11989317B2 patent drawing
  • US11989317B2 patent drawing

AI summary

A system and a method are disclosed for receiving a request for a user to perform a plurality of activities with respect to a secure document, a given activity of the plurality activities being assigned based on a known parameter of the user. The system transmits the request to the user, and responsive to detecting an interaction with the request, determines that the known parameter has changed. The system responsively determines requirements for performing the plurality of activities based on a replacement parameter of the user, determines a replacement activity based on the requirements, and transmits a new request to the user, the new request replacing the given activity with the replacement activity.