Content Server Concurrency Enforcement via Permits
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing systems rely on playback devices to enforce concurrency restrictions, which can lead to issues such as proxy attacks and failure to honor concurrency checks, making it desirable for a content server to manage and enforce concurrency policies.
Innovation Solution
A content server receives requests from user devices, sends permits for accessing content assets, and enforces concurrency restrictions by determining if the number of permits exceeds the allowed concurrent playbacks, thereby discontinuing further content asset segments if the limit is exceeded.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If playback devices are responsible for enforcing concurrency restrictions, then device autonomy and simplicity of server management are improved, but system reliability and security deteriorate due to susceptibility to proxy attacks and manipulation
Solution Approach 1:
The patent introduces a token as an intermediary mechanism between the content server and playback device. The token carries concurrency control information and serves as a mediator that enables the server to enforce restrictions remotely while maintaining device autonomy. The token acts as a trusted carrier that translates server policies into device-enforceable rules without requiring direct server involvement in each playback decision.
Solution Approach 2:
The system implements feedback mechanisms where playback devices report their playback status and token information back to the content server. This feedback loop allows the server to monitor concurrency levels, verify compliance, and dynamically adjust token parameters. The feedback ensures that devices remain autonomous while staying aligned with server-enforced concurrency restrictions.
2Reliability
If the content server manages concurrency restrictions centrally, then system security and reliability are improved, but server complexity and processing load increase
Solution Approach 1:
The patent segments concurrency control into discrete tokens, each representing a specific playback permission. Instead of managing all playbacks monolithically, the server issues individual tokens that can be independently tracked and validated. This segmentation reduces server complexity by breaking down the overall concurrency management task into manageable, atomic units that can be processed efficiently.
Solution Approach 2:
The system performs preliminary actions by pre-generating tokens with embedded concurrency control parameters before playback occurs. The server prepares and distributes tokens in advance, containing all necessary authorization information. This preliminary action reduces real-time server processing load during actual playback, as devices can autonomously validate pre-configured tokens without requiring complex server computations.
3Productivity
If tokens are returned by playback devices after playback completion, then resource management is simplified, but security vulnerabilities increase due to potential attacks and manipulation
Solution Approach 1:
The patent implements preliminary action by requiring playback devices to present tokens for validation before playback begins, rather than relying solely on post-playback token returns. The server validates token authenticity and concurrency status in advance, preventing unauthorized playbacks before they occur. This shift from reactive to proactive validation reduces security vulnerabilities while maintaining efficient resource management.
Solution Approach 2:
The system enhances feedback mechanisms by requiring continuous or periodic token validation during playback, not just upon completion. Devices provide feedback about their playback status and token validity, allowing the server to detect and respond to manipulation attempts in real-time. This ongoing feedback loop maintains security while enabling efficient resource allocation and tracking.
Data Source
AI summary
A content server may receive from a user device a request for a content asset and may send to the playback device a permit for accessing the content asset. The permit may be used by the content server in order to enforce a concurrency restriction, or a number of concurrent playbacks of one or more content assets desired or permitted by the playback device. In response to receiving a request for a content asset segment associated with a content asset, the content server may determine whether the number of permits currently granted to the playback device exceeds the number of desired or permitted accesses by the playback device, or a group of playback devices, to the content asset or one or more content assets. If so, then the content server may discontinue sending to the playback device any further content asset segments associated with that content asset.