Interactive Document Context Indexing for Size Reduction

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Interactive documents with numerous hypertext links and dynamic content face challenges in efficient storage and retrieval, leading to document bloat and increased complexity, making distribution inefficient.

Innovation Solution

Indexing the context of interactive points within interactive documents and storing this information on a server, allowing for centralized management and retrieval of context data upon user interaction, reducing the need to store context data within the document itself.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Loss of information

If all context information is stored within the interactive document itself, then the document contains all needed information for interactivity, but the document size bloats making distribution undesirable

Engineering Contradiction:
Improvecontext information completenessVSAvoiddocument size
Core Design Contradiction:
Loss of informationVSWeight of stationary object

Solution Approach 1:

The patent extracts context information from the interactive document and stores it externally on a server. The document retains only minimal references (URIs) to the context information, separating the heavy context data from the lightweight document structure. This resolves the contradiction by maintaining information completeness while dramatically reducing document size for efficient distribution.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent introduces a server as an intermediary between the interactive document and the context information. The server stores the context information and provides it to clients upon request using URIs from the document. This mediator approach allows the document to remain small while still providing access to all necessary context information through the server infrastructure.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Weight of stationary object

If context information is stored externally on a server, then document size is reduced for efficient distribution, but the system complexity increases with server management

Engineering Contradiction:
Improvedocument sizeVSAvoidsystem complexity
Core Design Contradiction:
Weight of stationary objectVSDevice complexity

Solution Approach 1:

The patent makes the server perform multiple functions: storing context information, receiving URI requests from clients, retrieving appropriate context data, and sending it back to clients. This multi-functional server approach consolidates complexity into a single infrastructure component that handles all context management tasks, reducing the complexity burden on individual document distribution systems.

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

3Adaptability or versatility

If more context information is included in interactive documents, then interactivity is enhanced, but the document becomes larger and harder to manage

Engineering Contradiction:
Improveinteractivity capabilityVSAvoiddocument management complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent segments the interactive document into two distinct parts: the document itself containing only lightweight URIs, and the context information stored separately on the server. This segmentation allows the document to remain simple and easy to manage while still supporting rich interactivity through the externally stored context information that can be retrieved as needed.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS8055701B2Interactive document information storage and delivery
Publication Date: 2011.11.08 MICROSOFT TECHNOLOGY LICENSING LLC
  • US8055701B2 patent drawing
  • US8055701B2 patent drawing
  • US8055701B2 patent drawing

AI summary

Indexing and storage of context of a plurality of interactive points within an interactive document is provided. The context of the interactive points within the document is stored in a server such that it can be located by the server via the index. Furthermore, information may be received at the server identifying context data for an interactive point stored in the server upon a user activating the interactive point within the document. The server may then transmit to a client the context data stored by the server identified by the information received.