OTT Ad Request Logging for Near Real-Time Stream Debugging

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In the cloud distribution paradigm of OTT video applications, monitoring HTTP request details for content requests and responses is inefficient, leading to resource wastage and revenue loss due to problematic content and requests/responses interfering with content streams, especially when third-party servers are involved.

Innovation Solution

A manifest manipulation system that modifies ad requests and responses, logging data through a logging system to track properties of secondary media content, enabling near real-time quality assurance and debugging without relying on local network proxies, using SSL/TLS certificates, and device-specific limitations.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Measurement precision

If local network proxies are used to monitor HTTP request details, then content monitoring capability is improved, but device complexity and resource consumption increase

Engineering Contradiction:
Improvecontent monitoring capabilityVSAvoidsystem complexity
Core Design Contradiction:
Measurement precisionVSDevice complexity

Solution Approach 1:

The patent introduces a logging system as an intermediary component that sits between the content provider server and third-party servers. This logging system intercepts and logs HTTP requests and responses without requiring complex local network proxies at client devices. The logging system captures request details, forwards requests to appropriate servers, and logs responses, thereby providing monitoring capability while avoiding the complexity of deploying proxies across multiple devices.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Difficulty of detecting and measuring

If comprehensive logging of ad requests and responses is implemented, then debugging capability is improved, but data processing load increases

Engineering Contradiction:
Improvedebugging capabilityVSAvoiddata processing load
Core Design Contradiction:
Difficulty of detecting and measuringVSUse of energy by moving object

Solution Approach 1:

The patent extracts only the essential logging functionality from complex proxy systems and implements it as a dedicated logging system component. This logging system selectively captures HTTP request details and responses without processing or analyzing the entire content stream. By separating the logging function from content processing, the system reduces data processing load while maintaining comprehensive debugging capability for ad requests and responses.

Inventive Principle:
Principle #2Taking out (Extraction)

3Adaptability or versatility

If third-party servers are involved in content distribution, then content variety is improved, but monitoring efficiency deteriorates

Engineering Contradiction:
Improvecontent varietyVSAvoidmonitoring efficiency
Core Design Contradiction:
Adaptability or versatilityVSProductivity

Solution Approach 1:

The patent implements a universal logging system that can handle multiple types of content requests and responses from various third-party servers through a single interface. The logging system is designed to work with different ad servers, content delivery networks, and third-party providers without requiring separate monitoring systems for each. This multi-functional approach maintains content variety from multiple sources while improving monitoring efficiency through centralized logging.

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

Data Source

PatentUS20260059155A1Logging and debugging of streaming applications
Publication Date: 2026.02.26 NBCUNIVERSAL MEDIA LLC
  • US20260059155A1 patent drawing
  • US20260059155A1 patent drawing
  • US20260059155A1 patent drawing

AI summary

Systems and methods for logging OTT device requests and responses are provided. A method may include intercepting, via a logging system, one or more ad requests to be satisfied by an ad server. Data of the ad requests is logged, via the logging system. The request is forwarded to the ad server, which may respond with an ad server response that may also be logged by the logging system.