Policy-Based Mobile Forms Engine for Offline Data Capture

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current mobile forms solutions are PC-centric, not optimized for mobile devices, and lack support for intermittently connected networks, multi-tenant hosting, and sophisticated routing and tracking, leading to inefficiencies and high costs in field data capture and processing for businesses.

Innovation Solution

A system comprising a policy-based mobile content engine, mobile-forms application client, and transport engine that uses XML-based forms and policies to define, deploy, and manage mobile forms applications across various devices and networks, enabling offline data capture and routing rules for business processes.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If PC-centric forms solutions are used, then forms can be displayed and processed, but they are not optimized for mobile devices and wireless networks

Engineering Contradiction:
Improvemobile device compatibilityVSAvoidimplementation complexity
Core Design Contradiction:
Adaptability or versatilityVSEase of manufacture

Solution Approach 1:

The patent transforms forms from PC-centric to mobile-optimized by changing key parameters: switching from desktop browsers to mobile browsers and applications, adapting from wired LAN to wireless networks, and optimizing for mobile device constraints. This enables the same forms to function effectively across diverse mobile platforms without requiring separate implementations for each device type.

Inventive Principle:
Principle #35Parameter changes

Solution Approach 2:

The patent creates a universal forms solution that can be deployed across multiple device types (smartphones, tablets, feature phones) and network conditions (wireless, mobile data, offline) through a single mobile-optimized forms architecture. This multi-functional approach eliminates the need for device-specific form implementations while maintaining adaptability to different mobile environments.

Inventive Principle:
Principle #6Universality (Multi-functionality)

2Adaptability or versatility

If on-line browser-centric forms are used, then forms can be accessed via web browser, but they do not support offline use over intermittently connected networks

Engineering Contradiction:
Improveoffline capabilityVSAvoidnetwork connectivity requirement
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent implements preliminary action by pre-loading forms, data, and resources onto mobile devices before they are needed in the field. Forms are cached and prepared in advance so that mobile workers can access and complete them offline without requiring active network connectivity at the time of data capture, ensuring continuous operation across intermittently connected networks.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent provides beforehand cushioning by building offline capability into the forms system through local caching, synchronization queues, and asynchronous data transmission. This cushioning allows the system to function reliably without constant network connectivity, absorbing the impact of intermittent connections and ensuring data can be captured and submitted when connectivity becomes available.

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

3Productivity

If paper-based forms are used, then data can be captured in the field, but the process is slow and inefficient requiring manual data entry and duplicate data entry

Engineering Contradiction:
Improvedata capture efficiencyVSAvoiddata entry time
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

The patent replaces the mechanical paper-based data capture system with electronic mobile forms that can be filled out directly on mobile devices. This substitution eliminates the need for physical paper forms, manual writing, and subsequent manual data entry, allowing workers to capture data electronically in the field and have it automatically transmitted to the back office system.

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

Solution Approach 2:

The patent uses digital copying of forms and data structures to eliminate duplicate data entry. Mobile forms replicate the business process workflows and data collection requirements of paper forms but in an electronic format that can be directly integrated with back office systems, eliminating the need for manual transcription and reducing errors.

Inventive Principle:
Principle #26Copying

4Adaptability or versatility

If complex routing and tracking of forms is implemented, then sophisticated business processes can be supported, but device complexity increases

Engineering Contradiction:
Improvebusiness process routing capabilityVSAvoidsystem architecture complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces a mobile forms server as an intermediary layer between mobile devices and back office systems. This server handles sophisticated routing, tracking, and business process logic centrally, while mobile devices only need to display and interact with simplified forms. The intermediary absorbs the complexity of routing decisions and coordination, keeping client devices simple while enabling advanced business process capabilities.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS7774504B2Policy-driven mobile forms applications
Publication Date: 2010.08.10 TRUECONTEXT INC
  • US7774504B2 patent drawing
  • US7774504B2 patent drawing
  • US7774504B2 patent drawing

AI summary

A system for capturing data via an extensible markup language form is disclosed comprising a policy-based mobile content engine, a mobile-forms application client, and a transport engine. The policy-based mobile content engine is adapted to process a plurality of definitions from one or more mobile-forms application definition files. The policy-based mobile content engine translates the mobile-forms application definitions into policies and actions enforced by the policy-based mobile content engine. The mobile-forms application client has a plurality of rendering engines targeted for a mobile user device to render form controls and to process the forms-based application. The mobile-forms application client is operable on a mobile user device and is adapted to capture the data as an extensible-markup-language document. The transport engine is adapted to transport the mobile-forms application definition files and captured data through a transport layer between the policy-based mobile content engine and the mobile-forms application client.