Multi-Part Persistent Content State Management via Server Intermediary

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing content items, such as interactive content or application previews, are limited to single, self-contained items, leading to user frustration and disengagement as they lack persistence across multiple presentations, which is challenging for publishers to maintain user interest in an online context.

Innovation Solution

Implementing multi-part persistent content that maintains a state across multiple presentations by storing user interactions with a content server, allowing subsequent portions of the content to be provided based on the stored association, thereby reducing repetitive content transmission and enhancing user engagement.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If single, self-contained content items are provided to client devices, then the content delivery system is simple and self-contained, but user engagement decreases due to lack of persistence across multiple presentations

Engineering Contradiction:
Improveuser engagementVSAvoidcontent delivery system complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The content item is divided into multiple portions (first portion, second portion, etc.) that can be delivered separately to client devices. Each portion represents a segment of the overall content experience, allowing the system to manage complexity by breaking down the content delivery into manageable units while maintaining user engagement across multiple interactions.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

A content server acts as an intermediary between the content source and client devices. The server receives content items, divides them into portions, tracks user interactions and states, and delivers appropriate portions to clients. This intermediary manages the complexity of state tracking and portion management, shielding client devices from the underlying system complexity while enabling persistent, engaging content experiences.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Productivity

If content items are presented multiple times to users, then user engagement opportunities increase, but computational and bandwidth resources are wasted due to retransmission of the same content

Engineering Contradiction:
Improveuser engagement opportunitiesVSAvoidcomputational and bandwidth resources
Core Design Contradiction:
ProductivityVSLoss of energy

Solution Approach 1:

The content server performs preliminary actions by dividing the content item into portions in advance and storing these portions ready for delivery. When a client device requests content, the server can immediately deliver the appropriate pre-divided portion without needing to retransmit the entire content item, thus reducing computational and bandwidth resources while enabling multiple engagement opportunities.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system discards portions of content that have already been delivered and tracked, and recovers only the next appropriate portion to deliver based on the user's interaction state. This prevents redundant transmission of already-viewed content while maintaining the ability to present content multiple times as users progress through different portions, optimizing resource usage while preserving engagement opportunities.

Inventive Principle:
Principle #34Discarding and recovering

3Adaptability or versatility

If multi-part persistent content with state tracking is implemented, then user engagement and content personalization improve, but system complexity increases due to state management requirements

Engineering Contradiction:
Improvecontent personalizationVSAvoidstate management system
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The content server serves as an intermediary that centralizes state management functionality. It tracks user interactions with each content portion, maintains the execution state, and uses this information to determine which next portion to deliver. This centralizes the complexity of state management in the server rather than requiring complex state management on client devices, enabling personalized content delivery while managing system complexity through a dedicated intermediary component.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system implements feedback mechanisms where client devices report user interactions and execution state back to the content server. The server uses this feedback to track progress through the multi-part content item and determine the appropriate next portion to deliver. This feedback loop enables content personalization and adaptability while keeping the state management logic centralized in the server, which is better suited to handle the complexity of tracking and responding to user interactions across multiple content portions.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS20250018303A1Systems and methods for providing multi-part persistent content
Publication Date: 2025.01.16 GOOGLE LLC
  • US20250018303A1 patent drawing
  • US20250018303A1 patent drawing
  • US20250018303A1 patent drawing

AI summary

A method for providing multi-part persistent content includes requesting a content item from a content server, and receiving a first portion of a multi-part content item. The method also includes providing a state of execution of the multi-part content item to the content server, and after providing the state of execution, requesting a second content item. The method also includes receiving a second portion of the multi-part content item. The second portion is selected by the content server based on the state of execution of the multi-part content item.