Lightweight Form Pattern Validation on Mobile Devices

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing form-based input systems, particularly on mobile devices, face challenges in performing client-side pattern validation due to resource limitations, which necessitates server-side validation and the use of heavyweight libraries, compromising efficiency and resource usage.

Innovation Solution

A lightweight pattern validation system that includes a validation processor and script library, allowing for client-side validation of form inputs within a content browser, using a validation shell function to process input fields against predefined patterns without requiring a heavyweight library.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If heavyweight Javascript validation libraries are deployed for client-side pattern validation, then validation capability is improved, but resource consumption on mobile devices increases

Engineering Contradiction:
Improvepattern validation capabilityVSAvoidresource consumption on mobile device
Core Design Contradiction:
ReliabilityVSUse of energy by moving object

Solution Approach 1:

The validation system is segmented into a lightweight core validation processor and separate pattern definition components. Instead of deploying a comprehensive heavyweight library, the patent implements a minimal validation engine that can be extended with specific patterns as needed, allowing mobile devices to load only the essential validation functionality rather than a complete validation suite.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent changes the parameter of library size by implementing a lightweight validation processor that uses simplified validation logic and data structures. The validation patterns are defined externally and loaded dynamically, allowing the core validation engine to remain small while still providing pattern validation capabilities through parameter-efficient algorithms and data representations.

Inventive Principle:
Principle #35Parameter changes

2Use of energy by moving object

If server-side validation is used instead of client-side validation, then resource constraints are satisfied, but transaction efficiency decreases

Engineering Contradiction:
Improveresource usage on mobile deviceVSAvoidform submission efficiency
Core Design Contradiction:
Use of energy by moving objectVSProductivity

Solution Approach 1:

The patent implements preliminary validation actions on the client side by providing a lightweight validation processor that can execute pattern validation locally before form submission. This preliminary client-side filtering prevents obviously invalid data from being transmitted to the server, reducing unnecessary transactions while maintaining resource efficiency on mobile devices.

Inventive Principle:
Principle #10Preliminary action

3Reliability

If HTML forms with embedded scripts are used, then pattern validation is achieved, but separation of data, logic and presentation is compromised

Engineering Contradiction:
Improvepattern validationVSAvoidmixing of data, logic and presentation
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent extracts the validation logic from embedded HTML scripts and implements it as a separate lightweight validation processor. The validation patterns are defined externally in a structured format, and the validation logic is implemented as a independent component that can be applied to forms without mixing validation logic with presentation markup, thereby maintaining the MVC paradigm while enabling pattern validation.

Inventive Principle:
Principle #2Taking out (Extraction)

Data Source

PatentUS8055996B2Lightweight form pattern validation
Publication Date: 2011.11.08 TAASERA LICENSING LLC
  • US8055996B2 patent drawing
  • US8055996B2 patent drawing
  • US8055996B2 patent drawing

AI summary

A pattern validation method can include retrieving a value for a form based input field from a form defined in markup rendered in a content browser. The retrieved value along with a validation pattern for the form based input field can be passed to a validation process disposed within a lightweight validation library coupled to the rendered markup. Subsequently, the retrieved value can be validated in the content browser according to the validation pattern. Notably, each step of retrieving, passing and validating can be repeated for at least one additional value for at least one additional form based input field disposed in the markup rendered in the content browser. In this regard, the retrieving, passing, and validating steps can be performed in a validation shell function disposed in the markup rendered in the content browser.