Microsoft Mediaroom 2.0 IPTV Platform: CodeName 'Taos, Monaco and Rome Clients'

Microsoft is believed to be merging its Mediaroom IPTV platform with Xbox Live via a project codenamed "Orapa". In a September 4 blog post on Mediaroom 2.0's single-sign-on functionality, Microsoft's William Zhang acknowledged the "In addition to Mediaroom 2.0 set-top-box (STB) client also supports:Taos: PC browser client;Monaco: Windows Media Center client;Rome: Windows Mobile client"However, he […]

Microsoft is believed to be merging its Mediaroom IPTV platform with Xbox Live via a project codenamed "Orapa". In a September 4 blog post on Mediaroom 2.0's single-sign-on functionality, Microsoft's William Zhang acknowledged the "In addition to Mediaroom 2.0 set-top-box (STB) client also supports:

  1. Taos: PC browser client;
  2. Monaco: Windows Media Center client;
  3. Rome: Windows Mobile client"

However, he didn't reference Ventura at all in his post.

MJF said of about the following components figured into this new platform:

Rome = Mediaroom for Windows Phone
Taos = Silverlight for Mediaroom
Monaco = Mediaroom for Media Center
Santa Fe = Settop box using Silverlight/running Mediaroom
Ventura = Music and video discovery/consumption services (related to Zune)

Zhang further said the "critical enabler for supporting these clients is MDS (Mediaroom Data Store), introduced in Mediaroom 2.0. Devices/users registered and authenticated are identified by SSO token which is further associated with its MDS token. MDS token is required to access data in MDS."

He said that "to access each video asset, PlayReady license is then required to decrypt PlayReady protection. Therefore to implement and test such a SSO system, you need to secure PlayReady certificates from Microsoft by going through the PlayReady license process as specified here, or speak to your Microsoft contact person, PlayReady license server is already included in Mediaroom 2.0."

The following table summarizes the authentication mechanisms required for various Mediaroom client applications:

Client Type

Version

Scenario

Approach

STB PF App

ADK 3.0

Call App Service API to get MDS data, no PlayReady license
challenge

Handled by PF:

  • With PF page reload: HTTP header value of
    "x-mstv-mds-token";
  • Without PF page reload: Use ApplicationUrlList
    for cases without PF page load such as refreshing TVXmlDataSource only

Simulator

PC Client

Taos

1.2 & 1.1

Storefront for DRM protected VOD assets, requires
PlayReady

Custom SSO:

  • Authentication against custom Identity
    Provider (SAML) to get SSO token;
  • Validation of SSO token against customer
    billing;
  • MDS STS generates MDS token;
  • PlayReady License challenge.

Monaco

1.0.1172.0

Rome

The following diagram illustrates the various components in a custom SSO implementation and the flow of SSO token and MDS token: