Content Request Flag for Payable Transaction Tracking
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The existing method for tracking payable content transactions in wireless media delivery systems is burdensome, requiring access providers to maintain extensive lists of URIs and update them frequently as content items change, leading to difficulties in accounting for payments between providers.
Innovation Solution
Incorporating a flag in the content request that indicates whether the requested content item is payable or non-payable, allowing the access system to increment a payable content count and determine payment amounts based on these flags, simplifying the tracking and accounting process.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Measurement precision
If access providers maintain extensive lists of URIs to track payable content, then payment tracking accuracy is improved, but system complexity and maintenance burden increase
Solution Approach 1:
The patent extracts the payment status information from the content listing and embeds it directly into the content request message as a flag. This removes the need for access providers to maintain separate extensive URI lists, as the payment status is now self-contained within the request itself, reducing system complexity while maintaining tracking accuracy.
Solution Approach 2:
The content provider pre-markets each content item with a payment status flag before the content is even requested. This preliminary action of tagging content items with payment information eliminates the need for subsequent complex tracking and accounting processes, as the payment status is already determined and attached to the content request.
2Measurement precision
If access providers maintain extensive lists of URIs and update them frequently, then payment tracking accuracy is improved, but time and resources for updates increase
Solution Approach 1:
By extracting payment status from separate URI lists and embedding it in content requests, the system eliminates the time-consuming process of maintaining and updating extensive URI databases. The payment information travels with the content request, requiring no separate update cycles.
Solution Approach 2:
The content provider automatically attaches payment status flags to content items without requiring access providers to manually update their lists. This self-service approach eliminates the manual maintenance burden and time loss associated with keeping URI lists current.
3Productivity
If content requests include payment flags, then tracking efficiency is improved, but message size and processing complexity increase
Solution Approach 1:
The patent applies local quality by adding only a small flag or indicator to the content request message rather than embedding entire payment terms or large data structures. This localized addition provides the necessary payment information while minimizing impact on message size and processing complexity.
4Measurement precision
If access providers manually track payable content, then payment accuracy is improved, but operational burden increases
Solution Approach 1:
The system implements self-service by automatically attaching payment status flags to content requests and enabling access providers to track payable content through simple automated processes. This eliminates manual tracking operations while maintaining payment accuracy, significantly reducing operational burden.
Solution Approach 2:
The payment flag in the content request provides immediate feedback to the access provider about whether the content is payable. This automated feedback mechanism replaces manual tracking processes, maintaining accuracy while reducing operational burden through systematic automated identification.
Data Source
AI summary
A method to facilitate determination of an extent to which payment should be exchanged between the access provider and the content provider for delivery of content items to the client stations. Each client station will be provisioned with a list of available content items, including for each a flag and/or other data specifying whether the content item is payable or non-payable. When the client station sends a content request seeking a particular one of the content items, the client station includes the flag or other data. As the content request passes through the access provider's system on the way to the content provider, the access provider then reads the flag or other data to determine whether the content item is payable and perhaps an applicable payment amount. The access provider may thereby maintain a count of payable content transactions and/or other data to facilitate proper payment.