Please find the list of use cases currently identified by the team to be addressed by our Content Replacement application. This list is of course non-exhaustive and you could find your own use of our application.
All these use cases are based upon a linear workflow. The original content is always a live source.
The replacement content is also live but it can actually be generated from a live, slate or an asset source type.
|Use Case||Replacement content||Contextualization added value|
|Blackout||Alternate content (e.g. content with no restrictions, slate message, promotional message)||Comply with content provider distribution policies (typically for live sports events)|
|Regionalization||Regional or local variant (e.g. local news)||Stream channel variants with more relevant content|
|SimSub (Simultaneous Substitution)||Regional or local variant||Protect rights of local broadcasters and secure advertising revenue, mostly enforced in Canada|
|EAS (Emergency Alert System)||Regional or local alerting message||Override current content regardless of what channel is being watched|
|Geo-blocking||Alternate content (e.g. content with no restrictions, slate message, promotional message)||Enforcing of market strategies (focus on special regions) and limitation of frauds|
For all those use cases, the core engine used to automatically and dynamically enforce content replacement gives you the capability to define how the contextualization is being done.
Origination of contextualized content
Initially, only the manifests are being processed to do contextualization, which means that contextualized content is being streamed from your origin server and CDN. Soon, the broadpeak.io platform will also do streaming (check out the feature announcements).
Updated 5 months ago