Join Us
Get involved in the OATC community and help us shape the future development of the subscription TV on the Internet technical ecosystem.
Become a Member...
Specifications and Recommended Practices

Published Specifications

  1. OMAP 1.0 Online Multimedia Authorization Protocol based on Oauth 2.0 using JSON web tokens

    The OMAP Specification follows the Oauth 2.0 model but instead of the "End User" authorizing a third party on their own behalf, the MVPD provides the authorization token after the End-user has been authenticated by the MVPD. The authorization is used by the content distributor to provide access to authorized content or to help the content provider mark the content for which the end user is authorized.

    OMAP supports authorization on three types of devices:
    1. Devices with a web browser where a consumer attempts to access content via the web browser from a content provider's web site.
    2. Devices with a native application like a mobile app where the content provider's mobile app is enabled to view/stream content.
    3. Devices with limited display capabilities like a game console that may require the end user to authenticate on another device.

  2. RUM 1.1 Online Resource Usage Monitoring Protocol

    The RUM Specification is designed to enable concurrency monitoring of end users who are attempting to access content at multiple destinations that may include websites, mobile apps from both content providers and distributors, and to enforce concurrency limits based on the business agreements between the content distributors and content developers.

    The specification assumes that a consumer has been authenticated and authorized for a piece of content using the OLCA and OMAP protocol and then defines how the content provider communicates to the device the need to establish a heartbeat communication with the RUM provider.

    Once the content provider has communicated to the client that it is authorized to access a piece of content the client then communicates with a CDN to access the content. This means that the DRM client on the client's device will need to establish and maintain a heartbeat communication with the RUM service provider in order for the system to function.

    The data obtained through this heartbeat is used for multiple purposes including monitoring the number of sessions, streams, locations, fraud detection etc.

  3. Resource Utilization Monitoring User Experience

    Internet 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.

  4. Home-Based Authentication for TV-Connected Devices

    Home-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.

Released Recommended Practices Documents

  1. Live TV Metadata Recommended Practice
    This document recommends a method for exchange of content metadata between providers and distributors. It is not intended, nor is it likely appropriate, to provide a data source for use directly by the consumer of the content. Its purpose is to enable content providers and content distributors to exchange data to describe their content and detail how it can be used and further distributed.

  2. Social Login for MVPDs

    The purpose of this document is to make baseline recommendations on how distributors can use social networks login credentials to improve the TV Everywhere user experience.

  3. Authentication Conversion Funnel for Content Programmer's Apps and Sites
    The purpose of this document is to define a set of metrics/funnel steps for the authentication process as it pertains to a content provider's TVEverywhere site/app.

  4. Error Messaging for TV Everywhere Authentication and Authorization

    The purpose of this document is to define error messaging for TV Everywhere authentication and authorization with the end goal of presenting clear and consistent error messaging to consumers with the larger objective being to improving overall TV Everywhere user experience.

  5. Home-based Authentication Use cases

    In-home automatic authentication is the process by which a distributor uses characteristics of the home network (or identifiers automatically accessible between devices on the home network) to authenticate which subscriber account is associated with that home network so that users do not need to manually enter credentials when establishing a TV Everywhere session for accessing TVE content.

  6. Usability Recommendations For TV Everywhere
    The purpose of this document is to outline the OATC-endorsed Usability Recommendations for the TV Everywhere authentication experience. This document represents an initial set of recommendations based on usability testing that was conducted by the OATC in April 2014. This set of OATC TVE Usability Guidelines are aligned with CTAM's TVE Usability Recommendations and extend them in some areas.
About Us  |  OATC History  |  Markets  |  Board and Officers  |  Our Members  |  Partners and Liaisons  |  Specifications  |  Terms Of Use | Privacy Statement | Login
Alliance Management by Inventures. Copyright 2021 OATC