TaskLet Widget Platform for Simplifying Web Service Interaction

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing web services are complex and require users to perform multiple actions across multiple sites, which can be cumbersome, especially on mobile devices with limitations and connectivity issues, and creating personalized widgets requires programming knowledge.

Innovation Solution

A system that allows users to create and invoke personalized software packages (widgets) called TaskLets by recording and analyzing browser actions, transforming them into executable scripts that can be executed with a single action from various devices, including non-Internet-enabled mobile phones, using a platform that automatically generates and shares these widgets.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If web services require complex navigation and multiple forms to be invoked, then the web service functionality is comprehensive, but the ease of operation deteriorates

Engineering Contradiction:
Improveease of operationVSAvoiddevice complexity
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The patent segments complex web service interactions into discrete, recordable user actions. By breaking down the invocation process into individual steps (navigation, form filling, submissions) that can be captured and replayed, the system transforms complex multi-step procedures into simplified single-click operations while maintaining the underlying service complexity.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system performs preliminary action by recording user interactions in advance. The recording mechanism captures the sequence of actions required to invoke a web service, storing this information for later replay. This allows the complex service invocation to be prepared beforehand and executed later with minimal user input.

Inventive Principle:
Principle #10Preliminary action

2Ease of operation

If pre-packaged widgets are used to simplify web service invocation, then the ease of operation improves, but the adaptability deteriorates

Engineering Contradiction:
Improveease of operationVSAvoidadaptability
Core Design Contradiction:
Ease of operationVSAdaptability or versatility

Solution Approach 1:

The patent implements dynamics by making widgets adaptive rather than static. The system records actual user interactions with web services, capturing the specific sequence of actions taken by individual users. This creates dynamic widgets that adapt to personal usage patterns rather than enforcing a fixed interaction model, thereby maintaining both ease of operation and adaptability.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The system enables self-service by automatically recording and analyzing user interactions without requiring manual programming. The recording mechanism captures user behavior patterns, and the system automatically generates personalized widgets based on this data, allowing users to benefit from customized interfaces without manual configuration or programming knowledge.

Inventive Principle:
Principle #25Self-service

3Adaptability or versatility

If personalized widgets are created through programming, then the adaptability improves, but the ease of manufacture deteriorates

Engineering Contradiction:
ImproveadaptabilityVSAvoidease of manufacture
Core Design Contradiction:
Adaptability or versatilityVSEase of manufacture

Solution Approach 1:

The system enables self-service by automatically recording and analyzing user interactions without requiring manual programming. The recording mechanism captures user behavior patterns, and the system automatically generates personalized widgets based on this data, allowing users to benefit from customized interfaces without manual configuration or programming knowledge.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The patent replaces the mechanical system of manual programming with an automated recording and analysis system. Instead of requiring users to write code in languages like Java, JSP, or JavaScript, the system captures user interactions and automatically translates them into executable widget code, substituting the programming process with an automated observation and synthesis mechanism.

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

4Adaptability or versatility

If mobile devices are used to access web services, then the accessibility improves, but the reliability deteriorates due to connectivity issues and device limitations

Engineering Contradiction:
ImproveaccessibilityVSAvoidreliability
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The system performs preliminary action by recording user interactions during periods of good connectivity. The recording mechanism captures the complete sequence of actions required to invoke web services, storing this information locally on the mobile device. This allows the widget to be executed later even when connectivity is unavailable, as the essential interaction pattern has been pre-captured.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent uses copying by creating a local representation of the web service interaction pattern. Instead of requiring real-time connection to the original service, the system creates a copied version of the interaction sequence stored in the widget. This copied interaction can be executed locally on the mobile device, reducing dependence on continuous connectivity and improving reliability in mobile environments.

Inventive Principle:
Principle #26Copying

Data Source

PatentUS9183004B2System and method for representing user interaction with a web service
Publication Date: 2015.11.10 MICRO FOCUS LLC
  • US9183004B2 patent drawing
  • US9183004B2 patent drawing
  • US9183004B2 patent drawing

AI summary

Disclosed is a system and method for representing user interaction with a web service. The method comprises the steps of: acquiring a representation of the actions of a user performing a task with the web service; analyzing the acquired actions to determine semantics and at least one variable describing the user actions; and representing the semantics and the at least one variable in at least one script file, the at least one script file supporting performance of user interaction with the web service based on the semantics and a value provided for the variable.