Non-intrusive Background Sync Authentication Notification

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing data synchronization models are either intrusive, pose security risks by saving authentication credentials, or fail to synchronize data when authentication is required.

Innovation Solution

A notification user interface element is displayed persistently but unobtrusively to inform users of required authentication credentials, allowing them to input credentials without interrupting their workflow and enabling continuous background synchronization.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If the first model (prompting user for credentials) is used, then authentication can be obtained, but user workflow is interrupted and becomes annoying

Engineering Contradiction:
Improveauthentication capabilityVSAvoiduser workflow continuity
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The system performs preliminary authentication by detecting when credentials are required before the user needs to take action. It proactively prepares authentication prompts and manages credential input in the background, allowing synchronization to proceed without interrupting the user's workflow.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system enables self-service authentication by automatically detecting authentication requirements, managing credential prompts, and handling the authentication process without requiring user intervention. The user simply continues their workflow while the system handles authentication autonomously.

Inventive Principle:
Principle #25Self-service

2Ease of operation

If the second model (saving credentials with client) is used, then authentication tasks can be handled automatically, but security concerns arise from saving passwords

Engineering Contradiction:
Improveauthentication automationVSAvoidsecurity risk
Core Design Contradiction:
Ease of operationVSObject-affected harmful factors

Solution Approach 1:

The system extracts the credential storage function from the client application and relocates it to a secure credential store managed by the parent application or operating system. This separation allows the client to automate authentication without compromising security, as credentials are never stored in plain text within the client application.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The system introduces a secure credential store as an intermediary between the client application and the authentication server. Credentials are stored securely in this intermediary location and accessed through secure authentication protocols, eliminating the security risks of storing credentials directly in the client while maintaining automation capability.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Object-affected harmful factors

If the third model (failing to synchronize) is used, then security is maintained by not saving credentials, but data synchronization fails when authentication is required

Engineering Contradiction:
Improvesecurity maintenanceVSAvoiddata synchronization
Core Design Contradiction:
Object-affected harmful factorsVSReliability

Solution Approach 1:

The system uses a secure credential store as an intermediary to enable authentication without compromising security. This intermediary allows the system to maintain security standards while successfully performing data synchronization, resolving the contradiction between security and synchronization reliability.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system performs self-service authentication by automatically retrieving credentials from the secure store and using them for synchronization without user intervention. This maintains security by not exposing credentials while ensuring synchronization succeeds when authentication is required.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS9779223B2Non-intrusive background synchronization when authentication is required
Publication Date: 2017.10.03 MICROSOFT TECHNOLOGY LICENSING LLC
  • US9779223B2 patent drawing
  • US9779223B2 patent drawing
  • US9779223B2 patent drawing

AI summary

A non-modal notification user interface element is displayed persistently but unobtrusively such that a user may easily determine that authentication credentials are required by a background synchronization process. The non-modal notification is configured such that it may be ignored by the user such that their workflow is not interrupted. The background synchronization continues to synchronize the data it can even though the background synchronization may require authentication credentials for a subset of the data to be synchronized. The user may select the non-modal notification user interface element at any point in time in order to supply the required authentication credentials. The non-modal notification is removed from the display when there are no further authentication credentials required.