Cross-Platform Video End Caps for Device-Compatible Call to Action

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing systems fail to provide cross-platform end caps that are compatible with diverse user devices, leading to potential malfunctions and broken video instances due to incompatible data, especially when devices lack the capability to execute certain actions.

Innovation Solution

A video distribution system determines user device capabilities and selectively appends end caps with compatible call-to-action elements, extending the presentation time of third-party content to ensure seamless integration and prevent device malfunctions.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If end caps with call-to-action elements are provided for all user devices, then the opportunity to request subsequent resources is maximized, but device malfunctions and broken video instances occur due to incompatible data

Engineering Contradiction:
Improveopportunity to request subsequent resourcesVSAvoiddevice malfunction prevention
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The system provides different end cap implementations tailored to specific device capabilities. Mobile devices receive end caps with phone call initiation functionality, while non-mobile devices receive end caps with web redirect functionality. This local customization ensures each device receives compatible data that maximizes resource request opportunities without causing malfunctions.

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

The end cap data is dynamically modified based on device capability parameters. The system changes the call-to-action implementation parameter (phone call vs. web redirect) according to the detected device type, ensuring compatibility while maintaining the core function of requesting subsequent resources.

Inventive Principle:
Principle #35Parameter changes

2Adaptability or versatility

If third-party content includes bum-ins for specific devices, then device-specific functionality is improved, but compatibility across all devices and operating systems deteriorates

Engineering Contradiction:
Improvedevice-specific functionalityVSAvoidcross-platform compatibility
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The system creates a universal end cap framework that can adapt to multiple device types. Instead of using device-specific bum-ins that work only on certain platforms, the end cap is designed as a universal component that detects device capabilities and adjusts its behavior accordingly, maintaining cross-platform compatibility while providing device-specific functionality.

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

Solution Approach 2:

The end cap implementation is dynamic rather than static. It automatically adjusts its call-to-action mechanism based on the user's device capabilities detected at runtime, allowing the same third-party content to function correctly across mobile devices, desktop browsers, and other platforms without requiring separate bum-in versions.

Inventive Principle:
Principle #15Dynamics

3Duration of action of moving object

If end caps are appended to third-party content, then the presentation time duration is extended and interactive opportunities are provided, but seamless integration and prevention of broken video instances require complex capability detection

Engineering Contradiction:
Improvepresentation time durationVSAvoidcapability detection complexity
Core Design Contradiction:
Duration of action of moving objectVSDevice complexity

Solution Approach 1:

The system performs capability detection in advance, before the end cap is appended to the third-party content. By detecting user device capabilities upfront and selecting the appropriate end cap implementation beforehand, the system avoids complex real-time detection during video playback and ensures seamless integration without breaking the video instance.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentEP3395076B1Cross-platform end caps
Publication Date: 2026.04.08 GOOGLE LLC
  • EP3395076B1 patent drawingFigure 1
  • EP3395076B1 patent drawingFigure 2
  • EP3395076B1 patent drawingFigure 3

AI summary

Methods, systems, and apparatus, including computer programs encoded on a computer storage medium, for providing a call to action at the end of a resource. In one aspect, a method includes receiving a request for media content to present on a user device, the request including a second request for third-party content to present with the media content, identifying, user device capabilities that describes information about system compatibility for the user device, determining third-party content to present with the media, the third-party content including a first presentation time duration indicative of a length of time the third-party content is presented, determining that an end cap is compatible with the user device and related to the third-party content, the end cap providing an interactive opportunity to request subsequent resources for the user device, and transmitting data to present the third-party content, the end cap, and the media.