Showing 13–24 of 118 results
-
DASH-IF License Declarations
Guidelines for Implementation: DASH-IF Interoperability Points Version 4.0 Vidscale License Declaration
$0.00Quick View -
DASH-IF License Declarations
Guidelines for Implementation: DASH-IF lnteroperability Points Version 3.0 Qualcomm License Declaration
$0.00Quick View -
$0.00Home-based authentication is a TV Everywhere (TVE) feature aimed at reducing the need for users to manually enter login credentials while they are in their homes. Also referred to as HBA, In-Home Authentication, Network Authentication, Auto Authentication or IP Authentication, it allows users to bypass the step of entering MVPD credentials by performing a subscriber lookup based on methods such as set-top box (STB) identification or client IP address matching. This is simple from a technical perspective when the user is able to login on the same device on which they are consuming content. The same is not true for TV-connected devices, such as game consoles, network media player appliances, smart TVs, etc. The standard HBA workflow happens between the user and the MVPD during authentication, however connected devices usually do not perform authentication. Connected device applications typically depend on Programmer services to manage authentication. These devices typically go through an activation (or pairing) step, wherein the Programmer client or MVPD portal requiring authentication displays a unique code and instructs the user to go to an activation website from a web browser. That website takes the user through the standard authentication process and establishes the user’s identity. After having established the identity of the user, the website then prompts for the code displayed on the screen, which will allow it to link the user to the connected client. This activation step is required because some clients do not support HTML rendering, or do not have browsers that support all the features required by MVPDs, essentially making a direct login solution impractical. This activation approach adds an extra step to the user’s end goal of consuming content. The process is often slow, error-prone and, to the user, commonly perceived as an unnecessary obstacle to content consumption. The OATC has published user experience guidelines for HBA (“Home-Based Authentication User Experience Guidelines for TV Everywhere”), addressing clients that support direct login, e.g. TVE websites and mobile apps. This document expands upon these guidelines to include TV-connected devices in addition to providing technical guidelines to implementation.
(Downloads - 0)
Quick View -
$0.00Home-based authentication (HBA) is a TV Everywhere feature aimed at reducing sign-in friction by removing the need for users to manually enter credentials while they are in their homes. This document from the OATC Usability Working Group, a subcommittee consisting of both content providers and distributors, outlines the guidelines for creating the best HBA user experience on programmers’ and distributors’ Web and mobile TVE properties.
(Downloads - 1)
Quick View -
$0.00Read moreThis document is sent to approved companies who wish to submit public comments to SVTA draft documents.
Quick View -
Quick View -
$0.00
The OATC Metadata Feed Recommended Practice document serves as a recommendation for content providers (“Providers”) and content distributors (“Distributors”) who have a need to exchange data to describe their content and detail how it can be used and further distributed. Adherence to these practices allows implementation of a single data package and could eliminate the need to code provider-specific (or distributor-specific) interfaces. This, in turn, simplifies the content exchange and helps to ensure that metadata is of a consistent quality and delivered in a timely manner. The Metadata Feed Recommended Practice recommends a method for exchange of content metadata between providers and distributors. It is not intended, not is it likely appropriate, to provide a data source for use directly by the end consumer of the content. The delivery of subscription content metadata normally occurs in one of two ways. Method 1 involves the static delivery of a metadata “sidecar” file alongside the audio/video content. Method 2 entails the provision of metadata via an XML document delivered by a web service, generally referred to as a “Metadata Feed”. Under this feed concept a distributor would be expected to call the web service periodically to learn of newly available content or changes to existing content. The refresh rate is subject to agreement between the content provider and the distributor, but it is encouraged that the data be refreshed on a two to four hour basis in order to facilitate quick and effective content takedowns when such a need arises. A Metadata Feed describes all of the distributable content available to a distributor at the time of the request, and for a pre-determined window afterwards. For example, a provider may stipulate that the feed includes all content scheduled to be (or to become) available at any time during the following eight hours. The actual time at which the content becomes visible to consumers is driven by data within the feed itself. The Metadata Feed specifies the provider that is offering the content data along with a collection of “TVE Items”. Each TVE Item contains all relevant data for a particular program or content item. Data for a given TVE Item may change from one update to the next, so distributors are expected to parse the entire feed and apply changes to their own data stores as such changes occur. To assist with this process, each Metadata Feed contains a time stamp that indicates when the data was sent. This time stamp is an ever increasing value useful for comparison.
(Downloads - 2)
Quick View -
$0.00
OATC standards secure back-end data exchanges between content websites/applications and MVPD billing and authentication systems that preserve consumer anonymity and privacy. In addition, the standards define the architecture, protocols and data formats needed to build and deploy interoperable systems that authorize access by consumers. The OATC OMAP specification is a voluntary open standard that provides MVPDs and programmers with consistent technology guidelines for verification service systems that make customers’ subscription content available online across a variety of Internet-based platforms. Multimedia content publishers and distributors are expanding their reach beyond traditional outlets to include a broad range of Internet connected devices, enabling greater consumer access, choice and convenience. Extending subscription and related business models to provide consumer access to media content over the Internet requires new methods of securely authorizing users, their devices and client software. Consumers want these methods to provide a simple and consistent experience, avoiding unfamiliar, intrusive or frequent logins which could discourage usage and broad adoption. They should enable sites and applications to provide customized search results, navigation and personalization while ensuring that the consumer’s identity and privacy are adequately protected. For technology vendors and third-party service providers these methods must provide interoperability, enabling them to develop value-added services and commercial solutions that can be used across the entire TV ecosystem on the Internet. This specification addresses Authorization – the process of granting or denying access to a network resource, e.g. protected media content. It defines the architecture, protocols and data formats needed to build and deploy interoperable systems that authorize access to protected media content on any Internet-connected device. User Authentication, which validates the consumer’s identity, is out of scope. Various authentication methods, such as SAML 2.0, may be used as needed in conjunction with this specification This specification is compliant with the OAuth 2.0 protocol. OAuth 2.0 provides support for both browser and native applications, is natively RESTful with strong developer framework support, and has broad and growing industry adoption. The OAuth 2.0 specification uses JSON data structures. JSON (JavaScript Object Notation) is a lightweight, text-based, data interchange format for the portable representation of structured data. This specification uses additional JSON based specifications for web tokens, encryption and digital signatures.
(Downloads - 0)
Quick View -
$0.00Internet delivery of video services opens up the possibility of users engaging in fraudulent activities (e.g. by sharing of username/password credentials). Content providers and distributors are contractually obligated to prevent such abuse. To be able to detect such activity, a system that can track content usage across service providers is required. Such a system should be capable of collecting real-time data that can then be utilized to detect abuse and any system put in place should be capable of allowing the service provider to stop an on-going delivery of content in real-time. To enable abuse detection, the Online Resource Usage Monitoring Protocol (RUM) specification allows data to be collected and made available to detect abuse such as: active streams per user/account, active devices per user/account, active IP addresses per user/account, active streams per user/account per IP address, and active devices per user/account per IP address. The RUM specification also proposes ways to collect real-time data from the applications used to access the content. Collecting metrics on consumers viewing habits, preferences, types of shows viewed, and other data, together with demographics, geographies and other categories is desirable for a variety of reasons such as providing a more intuitive/personalized experience to the user, understanding the popularity of certain programming and tailoring advertising based upon user preferences, viewing habits, choice of programs and so on.
(Downloads - 1)
Quick View -
$0.00The Streaming Video Technology Alliance’s Principal Member Application. For more information about the rights and benefits of a Principal Member, click here. Note that if you are ready to sign the Principal Member Application, please send an email to hello@streamingvideoalliance.org to initiate a Docusign envelope.
(Downloads - 2)
Quick View -
$0.00
The Streaming Video Technology Alliance’s Public Service Member Application. For more information about the rights and benefits of a Public Service Member, click here. Note that if you are ready to sign the Public Service Member Application, please send an email to hello@streamingvideoalliance.org to initiate an e-sig envelope.
(Downloads - 0)
Quick View -
$0.00Internet delivery of video services opens up the possibility of users engaging in fraudulent activities (e.g. by sharing of username/password credentials). Content providers and distributors are contractually obligated to prevent such abuse. To be able to detect such activity, a system that can track content usage across service providers is required. Such a system should be capable of collecting real-time data and preventing delivery of content that exceeds pre-defined rules in real-time. The OATC RUM Specification prescribes how data should be collected and utilized to mitigate abuse by automatically enforcing stream concurrency limits. This Resource Utilization Monitoring User Experience specification walks the reader through a set of stream concurrency monitoring use cases and offers related user experience flows. The purpose of this specification is to recommend a common set of practices for implementing a concurrency management solution for MVPDs, programmers and/or developers/solution integrators. The intended audience for this specification is business owners as well as technical personnel within MVPDs, programmers and/or developers/solution integrators. Use, transfer, storage of any use data requires to be kept in line with local legislation e.g., GDPR in the EU territories.
(Downloads - 0)
Quick View
