Web Action Guidance System for Dynamic Interface Segmentation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Web-based systems often require significant user knowledge and industry-specific terminology, leading to navigation challenges and increased bandwidth and system usage due to inadequate user interface designs that fail to guide users efficiently.

Innovation Solution

A web server device configured to match user commands with workflows and select appropriate database devices for executing actions, while preventing unnecessary information entry and retaining requests on the user interface, ensuring a responsive and intuitive design adaptable to various devices.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If web-based systems use comprehensive user interface designs to support multiple action types, then system functionality is improved, but user navigation complexity and time required to complete tasks increase

Engineering Contradiction:
Improvesystem functionalityVSAvoiduser navigation time
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The system performs preliminary actions by automatically determining the user's intent from the identified action type and pre-configuring the user interface with only the necessary information fields and options relevant to that specific action. This prevents users from navigating through unrelated interface elements and reduces the time required to complete tasks while maintaining support for multiple action types.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The comprehensive user interface is segmented into multiple specialized interfaces, each tailored to a specific action type (e.g., payment, transfer, deposit). The system dynamically selects and presents only the relevant segmented interface based on the identified action type, reducing navigation complexity while preserving full system functionality across different action categories.

Inventive Principle:
Principle #1Segmentation

2Reliability

If web-based systems require users to enter all possible information fields, then data completeness is improved, but system bandwidth usage and processing load increase

Engineering Contradiction:
Improvedata completenessVSAvoidsystem bandwidth usage
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

The system applies local quality by configuring each user interface with information fields specifically relevant to the identified action type. For example, a payment action displays payment-specific fields while a transfer action displays transfer-specific fields. This ensures data completeness for each action type while minimizing unnecessary data transmission and reducing system bandwidth usage by only collecting and processing relevant information.

Inventive Principle:
Principle #3Local quality

3Manufacturing precision

If web-based systems use industry-specific terminology and processes, then professional accuracy is improved, but ease of use for general users deteriorates

Engineering Contradiction:
Improveprofessional accuracyVSAvoiduser accessibility
Core Design Contradiction:
Manufacturing precisionVSEase of operation

Solution Approach 1:

The system dynamically adapts the user interface content, labels, and options based on the identified action type. The interface structure and presented information change dynamically to match the specific action being performed, ensuring professional accuracy for each action type while maintaining ease of use through context-appropriate presentations that avoid unnecessary industry jargon for general users.

Inventive Principle:
Principle #15Dynamics

4Adaptability or versatility

If web-based systems provide comprehensive user interface options for all device types, then device compatibility is improved, but interface complexity and load times increase

Engineering Contradiction:
Improvedevice compatibilityVSAvoidinterface complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system performs preliminary device detection and configuration, identifying the user's device type and capabilities before rendering the user interface. Based on this preliminary action, the system pre-configures the interface with appropriate complexity levels, optimizing for each device type while maintaining device compatibility. This reduces interface complexity and load times by avoiding the presentation of unnecessary options on simpler devices.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS11887096B2Web page action guidance system
Publication Date: 2024.01.30 TRUIST BANK
  • US11887096B2 patent drawing
  • US11887096B2 patent drawing
  • US11887096B2 patent drawing

AI summary

A web server device can match a series of commands from a user device to a workflow associated with a particular type of action. The web server device can, based on the particular type of action, select a particular database device from which to obtain data for executing the particular type of action. The web server device can prevent, via a user interface displayable by the user device, the user from entering information on the user interface that is unnecessary for executing the particular type of action. The web server device can retain, on the user interface, requests for information for executing the particular type of action.