Mobile Document Signing via Credential Mediator

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Mobile devices lack support for electronic signature options available on personal computers, particularly for two-factor or multi-factor authentication, limiting their use for electronically signing documents.

Innovation Solution

A system that allows users to sign electronic documents using trusted digital certificates derived from user credentials, such as cryptographic tokens from smart cards, with revocation or expiration mechanisms to enforce signing privileges, and supports authentication through various methods like passwords, biometrics, or hardware security tokens.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If electronic signature options are implemented on mobile devices, then document signing capability is improved, but device complexity increases

Engineering Contradiction:
Improvedocument signing capabilityVSAvoiddevice complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces a credential application as an intermediary component that manages digital certificates and authentication credentials on the mobile device. This mediator handles the complex cryptographic operations and certificate management, allowing the document signing capability to be added without directly complicating the core mobile device architecture. The credential application acts as a bridge between the mobile device's limited capabilities and the requirements for electronic signature functionality.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If two-factor or multi-factor authentication is supported on mobile devices, then security is improved, but ease of operation deteriorates

Engineering Contradiction:
ImprovesecurityVSAvoidease of operation
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The patent implements a universal credential application that can handle multiple authentication methods (passwords, biometrics, hardware security tokens) through a single interface. This multi-functional approach allows the system to support two-factor or multi-factor authentication while presenting a unified, simple user experience. The credential application can adaptively select and manage different authentication factors based on the specific signing scenario, maintaining ease of operation while enhancing security.

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

3Reliability

If trusted digital certificates are used for signing, then authentication reliability is improved, but device complexity increases

Engineering Contradiction:
Improveauthentication reliabilityVSAvoiddevice complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent extracts the complex certificate management and cryptographic validation functions into a separate credential application component. By isolating these complex authentication mechanisms into a dedicated module, the core mobile device architecture remains relatively simple while still supporting reliable authenticated signing. The credential application handles all certificate lifecycle management, key storage, and cryptographic operations, preventing these complexities from propagating throughout the entire device system.

Inventive Principle:
Principle #2Taking out (Extraction)

Data Source

PatentUS11275858B2Document signing system for mobile devices
Publication Date: 2022.03.15 OMNISSA LLC
  • US11275858B2 patent drawing
  • US11275858B2 patent drawing
  • US11275858B2 patent drawing

AI summary

Disclosed are various approaches for encrypting documents using mobile devices. A first application receives, from a second application a file and an identifier of a user account. The first application then sends a request for a certificate to a certificate authority and receives a certificate in response. The file is then encrypted using the certificate, and the encrypted file is returned to the second application. The second application can identify the user account as the recipient of a file. Then, the second application can send an encryption request that includes the identifier of the user account and the file to the first application. In response to the request, the second application receives the encrypted file and then provides the encrypted file to the recipient.