Streaming rights have become harder to manage. A single service may need to account for live and on-demand content, subscription tiers, rentals, purchases, household limits, device policies, regional restrictions, and offline viewing.
Traditional stream caps were not built for that level of complexity. Rules that are too loose can increase licensing risk, credential sharing, and revenue leakage. Rules that are too strict can block legitimate viewers, increase support requests, and contribute to churn.
This whitepaper looks at a more flexible approach. It explains how Comcast Technology Solutions' Business Logic Constructor, delivered through the Cloud Video Platform, uses programmable policies to manage streaming sessions and enforce content, entitlement, account, and contextual rules before playback begins.
Frequently asked questions
Stream concurrency management controls how many streams can play at the same time under an account, household, subscription, or content policy. More advanced systems can apply different limits based on content rights, service tiers, devices, locations, and commercial entitlements.
Fixed stream limits do not always reflect the rules attached to live programming, on-demand content, rentals, purchases, premium events, or different subscription tiers. They can leave content underprotected or block legitimate viewers when more specific rules are needed.
Business Logic Constructor is a programmable policy enforcement layer within the Comcast Technology Solutions Cloud Video Platform. It manages streaming sessions and applies concurrency, content, entitlement, and account rules before playback begins.
BLC can evaluate several policies for one playback request. These policies may relate to a title or live event, an SVOD, TVOD, or EST entitlement, an account or household limit, or the viewer's device, location, service tier, and access scenario. Playback proceeds when the applicable policy conditions are satisfied.
Media companies can use account, household, device, content, and entitlement policies to place more precise limits on streaming access. BLC also uses ClientID-based session identification rather than relying only on IP addresses, which can reduce tampering risk and false-positive lockouts.
Yes. Operators can use different concurrency limits for subscription tiers, content packages, and premium access offers. This can support product differentiation and give frequent users a reason to move to a higher tier.
