Content Continuity Across Devices Using Metadata Tagging

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing systems fail to ensure seamless continuity of content across various user devices and media types, limiting the ability to consume related content items in different formats and on multiple platforms.

Innovation Solution

A method and system that tag user history content items with metadata tags describing topical attributes, build playlists based on incomplete consumption, and push suitable content items to user devices, adapting to different formats such as video, audio, and text, and ensuring contextual continuity across devices.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If content items are provided in multiple file formats across various user devices, then adaptability and versatility of content consumption is improved, but device complexity and system complexity increase

Engineering Contradiction:
Improvecontent consumption adaptabilityVSAvoidsystem complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system implements a universal content delivery mechanism that handles multiple file formats (video, audio, text) and device types (e-reader, tablet, smartphone, TV, PC, PVR) through a single unified architecture. The content delivery server and playlist builder are designed to work with any content format and device combination, eliminating the need for separate systems for each format-device pair.

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

Solution Approach 2:

The system changes the parameter of content delivery from format-specific to format-agnostic by using metadata tags and user history tracking. Instead of creating separate delivery systems for video, audio, and text, the system uses parameter-based selection (user consumption history, device capabilities, content metadata) to route content appropriately, reducing system complexity while maintaining versatility.

Inventive Principle:
Principle #35Parameter changes

2Reliability

If user history is tracked across multiple devices with metadata tags, then continuity of content consumption is improved, but data management complexity and storage requirements increase

Engineering Contradiction:
Improvecontent continuityVSAvoiddata management complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system merges user history data from multiple devices into a unified user record stored on the content delivery server. Instead of maintaining separate history databases on each device, the system consolidates consumption history, metadata tags, and user preferences into a single centralized repository, simplifying data management while ensuring continuity across devices.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The content delivery server acts as an intermediary between user devices and the content library. It manages the user history database and metadata tags, mediating between the user's consumption patterns and the available content. This intermediary role centralizes data management complexity in one location rather than distributing it across multiple devices.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Ease of operation

If playlists are built based on user consumption history and metadata tags, then content relevance and user experience are improved, but processing time and computational resources increase

Engineering Contradiction:
Improveuser experienceVSAvoidplaylist generation time
Core Design Contradiction:
Ease of operationVSLoss of time

Solution Approach 1:

The system performs preliminary actions by pre-tagging content items with metadata and pre-building user profiles based on consumption history. When a user accesses the system, the playlist builder can quickly generate relevant playlists by matching pre-existing metadata tags and user preferences, rather than analyzing all content from scratch each time.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system uses feedback from user consumption history to continuously refine and personalize playlists. By tracking what content users consume and how they interact with it, the system learns user preferences and adjusts playlist recommendations accordingly, improving user experience over time while becoming more efficient at generating relevant content.

Inventive Principle:
Principle #23Feedback

4Ease of operation

If content items are pushed to multiple user devices, then accessibility and convenience are improved, but network bandwidth consumption and server load increase

Engineering Contradiction:
Improvecontent accessibilityVSAvoidnetwork bandwidth consumption
Core Design Contradiction:
Ease of operationVSLoss of energy

Solution Approach 1:

The system applies local quality by pushing content to specific devices based on their individual capabilities and the user's consumption history on each device. Instead of uniformly distributing all content to all devices, the system selectively pushes content to the appropriate device type (video content to TV, audio to car radio, text to e-reader), optimizing network bandwidth usage while maintaining accessibility.

Inventive Principle:
Principle #3Local quality

Data Source

PatentUS9762687B2Continuity of content
Publication Date: 2017.09.12 SYNAMEDIA LTD
  • US9762687B2 patent drawing
  • US9762687B2 patent drawing
  • US9762687B2 patent drawing

AI summary

A method and system for media consumption are described. The method including tagging each one of a plurality of content items with at least one metadata tag, the metadata tag including a descriptor of at least one topical attribute describing the content item, the plurality of content items being adapted for consumption on a plurality of user devices, wherein the plurality of content items are provided in multiple file formats; acquiring a history of user consumption of the plurality of content items on a plurality of user devices associated with a single user; storing a user record including the acquired user history, a plurality of metadata tags associated with user consumed content, and including a list of devices comprising the plurality of user devices associated with a single user; building a playlist based, at least in part, on the following criteria, wherein each content item which is listed on the playlist has at least one tag which is also one of a plurality of tags already stored in the user record: a) including a content item which has been started but not completely consumed, b) not including content items marked in the acquired history as being completely consumed, unless the content items have changed with respect to the version consumed, and c) including content items which have not been consumed; selecting at least one content item from the playlist; and pushing the selected at least one content item to at least one of the plurality of user devices associated with a single user, wherein if the selected at least one content item is not suitable for consumption on the at least one of the plurality of user devices, then a next item in the playlist is pushed to the least one of the plurality of user devices.