Web Application Document Storage Context Management

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current web technologies lack a consistent set of services that allow arbitrary web applications to store and access content and context across different devices, limiting users' ability to seamlessly store and retrieve varied forms of content using multiple devices.

Innovation Solution

A system and method providing web system services that enable clients to create, store, and restore web application documents on web servers, incorporating view, content, and context information, using a graphical user interface and web system services interface to support operations like New, Open, Save, and Restore across various devices.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If web users store content locally on client devices, then content is readily accessible on that specific device, but the content cannot be accessed from other devices or applications

Engineering Contradiction:
Improvecross-device accessibilityVSAvoidstorage system complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent implements a universal web-based storage system where content is stored on remote servers and accessible through multiple devices and applications. The system provides multi-functionality by enabling the same content to be accessed from desktops, mobile devices, and various applications (text editors, media players, etc.) through a standardized interface, eliminating device-specific storage limitations.

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

Solution Approach 2:

The patent introduces a web server as an intermediary between client devices and stored content. Instead of direct local storage, content is uploaded to and retrieved from remote servers through web protocols. This intermediary enables cross-device access while maintaining a consistent storage model, as the server mediates all access requests from different devices and applications.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If a standardized web storage model is implemented, then content can be accessed across multiple devices and applications, but supporting diverse document types and contexts becomes more complex

Engineering Contradiction:
Improveapplication compatibilityVSAvoiddata model complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent segments the storage model into distinct components: content data, context information, and metadata. Each component is handled separately with specific data structures and protocols. This segmentation allows the system to support diverse document types by treating each component independently, reducing the complexity of managing heterogeneous data formats within a unified web storage framework.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent employs parameter changes to accommodate different document types and applications. The storage model uses configurable parameters such as content type identifiers, context flags, and format specifications that can be adjusted based on the specific document being stored. This flexibility allows the standardized model to adapt to diverse requirements without requiring a completely different storage approach for each document type.

Inventive Principle:
Principle #35Parameter changes

3Loss of information

If context information is collected and stored with content, then related information is preserved for later retrieval, but the amount of data to be stored and managed increases

Engineering Contradiction:
Improvecontext information preservationVSAvoiddata storage volume
Core Design Contradiction:
Loss of informationVSQuantity of substance

Solution Approach 1:

The patent extracts context information as a separate, optional component from the main content data. Context such as creation date, author information, and associated metadata are stored in distinct fields rather than being embedded within the content itself. This extraction allows users to store only the necessary context information relevant to their specific needs, reducing overall data volume while preserving essential contextual details.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent implements partial action by allowing users to selectively store context information based on their requirements. Not all context data is collected or stored for every content item - users can choose which context parameters to preserve. This partial approach prevents unnecessary data accumulation while ensuring that relevant context information is maintained for effective later retrieval and application.

Inventive Principle:
Principle #16Partial or excessive action

Data Source

PatentUS8046436B2System and method of providing context information for client application data stored on the web
Publication Date: 2011.10.25 PINTEREST INC
  • US8046436B2 patent drawing
  • US8046436B2 patent drawing
  • US8046436B2 patent drawing

AI summary

An improved system and method for supporting web system services is provided for storing data and context of client applications on the web. A client application may include a web system services interface for invoking web system services to support web applications to operate over the web using different devices that may store data and context of web applications as a web application document onto a web server. A web application document may be represented by components that may include view information, content, and context information. The application may also include a web system services user interface for providing a graphical user interface for a user to invoke web system services that may include a new document system service, a store document system service, and a restore document system service. A schema for context scope may be implemented for collecting context information relevant to the web application document.