Document Metadata Encoding for External Content Access

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current methods for sharing documents with external content, such as presentations, often fail to ensure seamless access and playback of linked content, due to device constraints and bandwidth limitations, leading to incomplete consumption of shared content.

Innovation Solution

Associating a URL and asset data, including copyright information, with a document, allowing the consuming application to retrieve and display external content items, even if they are stored remotely, and enabling updates and access policies.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Quantity of substance

If a user sends only a document link (URL) to external content, then the document size remains small and easy to share, but end users cannot access or consume the external content due to device constraints and bandwidth limitations

Engineering Contradiction:
Improvedocument sizeVSAvoidcontent accessibility
Core Design Contradiction:
Quantity of substanceVSReliability

Solution Approach 1:

The patent segments the content delivery into two parts: a compact document containing embedded metadata (URLs, asset data, copyright information) and the actual external content items. This allows the document to remain small while providing sufficient information for content retrieval, resolving the contradiction between document size and content accessibility.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces an intermediary mechanism (embedded metadata directory) that bridges the document and external content items. This intermediary contains essential information (URLs, asset data) that enables end users to access external content without receiving the full content data, thus maintaining small document size while ensuring content accessibility.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If a user sends the complete document with all supplemental data and source files, then end users can access all content, but the document size becomes large and difficult to share

Engineering Contradiction:
Improvecontent accessibilityVSAvoiddocument size
Core Design Contradiction:
ReliabilityVSQuantity of substance

Solution Approach 1:

The patent extracts only the essential metadata (URLs, asset data, copyright information) from the complete content set and embeds it in the document. This extraction approach allows the document to remain compact while containing sufficient information for content retrieval, eliminating the need to include large supplemental data and source files.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

Instead of copying the actual content items into the document, the patent copies only the metadata (URLs and asset data) that describes the external content. This creates a lightweight reference system that enables content access without duplicating the actual content data, thus keeping document size small while maintaining content accessibility.

Inventive Principle:
Principle #26Copying

3Quantity of substance

If external content items are stored remotely on websites, then the document remains small and easy to share, but end users face bandwidth limitations and device constraints that prevent complete content consumption

Engineering Contradiction:
Improvedocument sizeVSAvoidcontent consumption efficiency
Core Design Contradiction:
Quantity of substanceVSProductivity

Solution Approach 1:

The patent performs preliminary actions by embedding all necessary metadata (URLs, asset data, copyright information) into the document before sharing. This preparation ensures that when end users receive the document, they have immediate access to all information needed for efficient content retrieval and consumption, eliminating the need for additional searching or configuration steps.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent changes the parameters of content delivery by providing detailed asset data (including URLs, copyright information, and other relevant metadata) that enables optimized content retrieval. This parameter enrichment allows consuming applications to efficiently manage external content items according to device capabilities and network conditions, improving content consumption efficiency despite bandwidth limitations.

Inventive Principle:
Principle #35Parameter changes

4Reliability

If the document includes embedded metadata with URLs and asset data, then end users can access external content items, but the document complexity increases

Engineering Contradiction:
Improvecontent accessibilityVSAvoiddocument structure
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent implements a nested structure where metadata (URLs, asset data, copyright information) is embedded within the document, which itself may be part of a larger content delivery system. This nesting approach organizes information hierarchically, allowing the document to contain structured metadata that enables content access while maintaining a manageable and organized document structure.

Inventive Principle:
Principle #7Nested doll (Nesting)

Data Source

PatentUS11727194B2Encoded associations with external content items
Publication Date: 2023.08.15 MICROSOFT TECHNOLOGY LICENSING LLC
  • US11727194B2 patent drawing
  • US11727194B2 patent drawing
  • US11727194B2 patent drawing

AI summary

An association of one or more renditions of external content items with a document is provided. A user may create a document, and may select to insert a piece of external content into the document. When the user selects to insert the external content into the document, a URL of the location where the content resides may be associated with the document. Other asset data may also be associated with the content item, such as public copyright license information and other relevant information, and may encoded into the document. When the document is shared, the asset data may also be provided. Accordingly, the consuming application software may be enabled to follow the URL and utilize other asset data to retrieve the content item.