Direct Resource Allocation Identifier for Streaming Media
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In real-time programmatic bidding ecosystems, the lack of standardization in interfaces and involvement of multiple vendors and service providers makes it difficult to introduce and manage new information and changes, and publishers have limited control over data sharing, especially in the connected TV ecosystem where they need to share information with various ecosystem entities.
Innovation Solution
The implementation of direct path resource allocation techniques that create a synchronized parallel data path from the player to the DSP, allowing publishers to securely and efficiently share approved information in real-time without intermediate entities, providing more control over data sharing and reducing dependency on other ecosystem components.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If publishers use existing real-time bidding paths with multiple intermediaries (ad stitchers, ad servers, SSPs), then resource allocation can be achieved through established ecosystem components, but the system complexity increases and data control is reduced
Solution Approach 1:
The patent extracts the essential resource allocation function from the complex intermediary chain and implements it directly through a synchronized parallel data path. The bid request and bid response are transmitted separately without requiring passage through ad stitchers, ad servers, or SSPs, thereby reducing system complexity while maintaining adaptability.
Solution Approach 2:
The patent segments the resource allocation process into two independent synchronized paths: one for bid requests and one for bid responses. This segmentation allows each path to be optimized independently and reduces the complexity of managing a single monolithic bidding system with multiple intermediaries.
2Productivity
If publishers share information with multiple ecosystem entities through standard bidding paths, then resource allocation can proceed with broad ecosystem participation, but data exposure increases and privacy protection becomes difficult
Solution Approach 1:
The patent introduces a direct synchronized data path as an intermediary mechanism that enables efficient resource allocation while controlling data exposure. This direct path acts as a mediator that allows bid requests and responses to be transmitted without requiring publishers to share information with multiple ecosystem entities, thereby maintaining productivity while reducing data exposure risks.
3Adaptability or versatility
If heterogeneous interfaces are used between different bidding components, then compatibility with various vendors and service providers is achieved, but introducing and managing new information becomes difficult
Solution Approach 1:
The patent creates a universal synchronized parallel data path that can handle bid requests and responses from multiple vendors and service providers without requiring customization for each interface. This universal approach maintains vendor compatibility while simplifying the management of new information, as the same direct path mechanism works across all participants.
4Productivity
If bid requests are distributed across multiple demand side partners by SSPs, then open bidding can occur, but publishers lose control over data sharing timing and selectivity
Solution Approach 1:
The patent enables publishers to take preliminary action by sending bid requests directly to demand side partners through the synchronized parallel data path before SSPs distribute them. This preliminary direct transmission allows publishers to control which partners receive information and when, while still enabling open bidding across multiple partners.
Data Source
AI summary
Resource allocation includes generating a resource allocation identifier corresponding to a resource allocation request. The resource allocation request pertains to allocation of a resource associated with streaming of an audiovisual content item. The resource allocation identifier comprises a first portion and a second portion, the first portion comprising a key, and the second portion comprising information associated with contextual metadata pertaining to the corresponding resource allocation request. It further includes performing a first transmission of a first message including the resource allocation identifier. The first message including the resource allocation identifier is directed to a first address associated with a first entity. It further includes performing a second transmission of a second message. Transmission of the second message causes transmission of the resource allocation request. The second message is directed to a second address associated with a second entity. The first address and the second address are different.Resource allocation includes receiving a first message comprising a resource allocation identifier. It further includes, at a time subsequent to receiving the first message, receiving a second message comprising a resource allocation request pertaining to allocation of a resource associated with streaming of an audiovisual content item. It further includes matching the resource allocation request with the resource allocation identifier. It further includes, based at least in part on the match, receiving contextual metadata associated with the resource allocation request. It further includes facilitating resource allocation at least in part by using the contextual metadata.