Conversational Data Input With Partial Account Freeze Authentication

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current data ingestion methods provide a tedious and error-prone user experience, and conventional software solutions fail to ensure secure data access and authentication without usernames or passwords.

Innovation Solution

Implementing dynamic graphical user interfaces that emulate a conversation with the user through chat-like messages, allowing efficient data input, secure data retention, and authentication without traditional credentials.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If static input fields are used for data intake, then the form structure is simple and easy to implement, but the user experience becomes tedious and time-consuming

Engineering Contradiction:
Improveuser experienceVSAvoiddata entry time
Core Design Contradiction:
Ease of operationVSLoss of time

Solution Approach 1:

The patent applies dynamics by transitioning from static input fields to dynamic conversation bubbles that adapt their content and appearance based on user interactions. The system dynamically generates prompts, adjusts form fields, and modifies the conversation flow in real-time, transforming the rigid static form into a flexible interactive dialogue that reduces data entry time and improves user experience.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The patent substitutes the mechanical structure of traditional forms with a conversational interface. Instead of users manually navigating through fixed fields, the system uses natural language prompts and automated dialogue to guide data input, replacing the mechanical form-filling process with an automated conversational mechanism that accelerates data collection.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

2Reliability

If static input fields are used for data intake, then the implementation is straightforward, but data entry becomes error-prone

Engineering Contradiction:
Improvedata entry accuracyVSAvoidform structure
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent implements feedback mechanisms where the system provides real-time validation, confirms data entry, and guides users through the conversation flow based on their responses. This feedback loop ensures data accuracy by immediately correcting errors and confirming inputs, while the conversational structure simplifies the overall form complexity compared to complex validation systems.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The patent introduces an intermediary conversational layer between the user and the data collection system. This mediator (the conversation bubble interface) simplifies the interaction by translating complex form requirements into simple conversational prompts, reducing user errors while maintaining data integrity without requiring complex form structures.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Ease of operation

If conventional authentication methods are used, then the security is straightforward, but the user experience is negative due to requiring usernames or passwords

Engineering Contradiction:
Improveauthentication processVSAvoiduser authentication
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The patent applies self-service authentication by enabling users to access their accounts and data without manual username or password entry. The system automatically identifies users through contextual information, device recognition, or biometric data, allowing the authentication process to serve itself rather than requiring active user participation, thus improving ease of operation while maintaining security.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The patent changes the authentication parameters from traditional credentials (username/password) to alternative identification methods such as device fingerprints, biometric data, or contextual parameters. This parameter transformation maintains authentication reliability while significantly improving user experience by eliminating the need for memorized credentials and manual login procedures.

Inventive Principle:
Principle #35Parameter changes

4Loss of information

If conventional data retention methods are used, then the data storage is simple, but sensitive information is lost when users abandon the application

Engineering Contradiction:
Improvesensitive data retentionVSAvoiddata management system
Core Design Contradiction:
Loss of informationVSDevice complexity

Solution Approach 1:

The patent applies preliminary action by saving user progress and sensitive information at each stage of the conversation before the user potentially abandons the application. The system continuously stores data in secure temporary storage during the conversation flow, ensuring that even if the user closes the application, the saved information remains accessible and secure, preventing data loss without requiring complex backup systems.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent implements beforehand cushioning by creating secure data retention mechanisms that protect sensitive information in case of user abandonment. The system prepares and safeguards data in advance using secure storage protocols and recovery mechanisms, cushioning against the potential loss of information while maintaining a relatively simple data management architecture through proactive rather than reactive protection.

Inventive Principle:
Principle #11Beforehand cushioning (Prior cushioning)

Data Source

PatentUS12481822B1Methods and systems for interactive data input
Publication Date: 2025.11.25 CITIBANK N A
  • US12481822B1 patent drawing
  • US12481822B1 patent drawing
  • US12481822B1 patent drawing

AI summary

Described herein are methods and systems to partially freeze an electronic account associated with a user. The server receives, via a graphical user interface a request to execute a network operation to connect to a webserver. When the server executes the network operation, the server transmits a request for access to the electronic account associated with an electronic application of the user. Once the webserver authenticates the request, the server can receive an indication that the request to access the electronic account has been blocked by the webserver. The server can revise the graphical user interface and authorize the user. Once the user is authorized, the server can cause the webserver to remove the blocked access and provide access to the electronic account. Furthermore, the server can cause the webserver to block future access to the electronic application.