overview of bda and pbdadownload.microsoft.com/.../pbda_bda_migration.docx · web viewman-machine...

Migrating a BDA Solution to PBDA

Guidelines for Computer OEMs and Digital Tuner Vendors

April21, 2009

Abstract

This white paper provides information about the Protected Broadcast Driver Architecture (PBDA) for the Windows® family of operating systems.

PBDA is the Microsoft worldwide platform to integrate broadcast TV services into Windows Media Center on a computer that is running the Windows® family of operating systems. Although Windows Media Center still supports existing Broadcast Driver Architecture (BDA) solutions, computer original equipment manufacturers (OEMs) and tuner vendors can use the guidelines in this white paper to migrate an existing BDA solution to PBDA.

This information applies for the following operating systems:Windows 7Windows Vista® SP1 with Windows Media Center TV Pack 2008

References and resources discussed here are listed at the end of this paper.

For the latest information, see: http://www.microsoft.com/whdc/device/broadcast/pbda/BDA_migration.mspx

http://www.microsoft.com/whdc/device/broadcast/pbda/BDA_migration.mspx

Migrating a BDA Solution to PBDA - 2

Disclaimer: This is a preliminary document and may be changed substantially prior to final commercial release of the software described herein.

The information contained in this document represents the current view of Microsoft Corporation on the issues discussed as of the date of publication. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information presented after the date of publication.

This White Paper is for informational purposes only. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS DOCUMENT.

Complying with all applicable copyright laws is the responsibility of the user. Without limiting the rights under copyright, no part of this document may be reproduced, stored in or introduced into a retrieval system, or transmitted in any form or by any means (electronic, mechanical, photocopying, recording, or otherwise), or for any purpose, without the express written permission of Microsoft Corporation.

Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document. Except as expressly provided in any written license agreement from Microsoft, the furnishing of this document does not give you any license to these patents, trademarks, copyrights, or other intellectual property.

Unless otherwise noted, the example companies, organizations, products, domain names, e-mail addresses, logos, people, places and events depicted herein are fictitious, and no association with any real company, organization, product, domain name, email address, logo, person, place or event is intended or should be inferred.

© 2009 Microsoft Corporation. All rights reserved.

Microsoft, Windows, and Windows Vista are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries.

The names of actual companies and products mentioned herein may be the trademarks of their respective owners.

Document HistoryDate ChangeApril 21, 2009 First publication

ContentsOverview of BDA and PBDA...........................................................................................3PBDA Services................................................................................................................3

Tuner Requirements for Windows Media Center......................................................4Supported Combinations of Requirements...............................................................5

Converting an Existing BDA Solution to PBDA................................................................5Primary Features in PBDA..............................................................................................6

Man-Machine Interface (MMI)..................................................................................6Descramble Failure Notifications (DFNs)...................................................................7Extensible Setup for Tuners.......................................................................................8PBDA Guide Data.......................................................................................................9Protected Content in PBDA.....................................................................................10

Resources....................................................................................................................12Appendix: Acronyms....................................................................................................12

April21, 2009© 2009 Microsoft Corporation. All rights reserved.


Overview of BDA and PBDAThe Protected Broadcast Driver Architecture (PBDA) is the new Microsoft worldwide platform for watching broadcast TV on the computer. The recent release of the Windows® Media Center TV Pack makes this possible. For the first time, the PBDA platform enables the computer-TV hardware ecosystem to integrate virtually any free or premium TV service into Windows Media Center, while it satisfies the TV industry's requirements for strong content protection for pay TV.

The PBDA platform enhances and supersedes the existing Broadcast Driver Architecture (BDA), which was the Microsoft standard for digital video capture on Windows-based operating systems for many years. The PBDA platform enables original equipment manufacturers (OEMs) and tuner vendors to integrate virtually any free or premium TV service into Windows Media Center, while satisfying the TV industry's requirements for strong content protection.

PBDA extends BDA because it: Adds the ability to send protected content through BDA.

Is independent of network protocol binding, such as IP or kernel streaming (KS) bindings, and allows PBDA to transmit content in several ways.

For more information about PBDA, refer to the PBDA specification, which is listed in “Resources” at the end of this paper.

This white paper provides information on how to migrate a BDA solution to PBDA. It also describes the required services and primary features of a PBDA implementation.

PBDA Services

PBDA services can be divided into the following two types: Required PBDA services, which a tuner must implement to be considered a PBDA

solution. The PBDA specification defines five required services that are described in Table 1.

Optional PBDA services, one or all of which a tuner may implement. The PBDA specification defines ten optional services that are described in Table 2.

Table 1. Required PBDA ServicesService DescriptionEventing Support for sending events from all PBDA services.Tuner Generic tuning service that provides access to live content. It is typically

used to configure and monitor a physical tuner and its associated demodulator.

Conditional Access Service (CAS)

Generic service that reflects the activity of the conditional access (CA) application. It is used to report any CA diagnostics and messaging, and to request control of the tuner.

General Purpose Name Value Service (GPNVS)

Support for getting and setting tuner information.

Digital Rights Unique portal to enumerate and select all proprietary DRM systems.



Service DescriptionManagement (DRM) Note that the actual implementation of a DRM system is not required,

only this service, which allows the tuner to signal which DRM, if any, it implements.

Table 2. Optional PBDA ServicesService DescriptionMux Support for selecting and monitoring each component of the released

content.Scanning Support for physically locating signals through hardware scanning.Guide Data Delivery Service (GDDS)

Support for the tuner to deliver out-of-band guide data. This service sends events when guide data is ready for delivery.

Debug Support for the tuner to generate debugging and logging information.Internet Gateway Internet connectivity to the tuner.Aux Support for obtaining the tuner’s auxiliary input capabilities and receive

events that are related to signal lock on an auxiliary input.Encoder Support for discovering encoder capabilities and sets encoder

parameters on the tuner.User Activity Information about the activity of users on the computer.WMDRMSession Support for the tuner to validate the credentials of Windows Media

Center. The communication between the tuner and Windows Media Center is through authenticated commands.

WMDRMTuner Support for the tuner to provide secure transactions to Windows Media Center. The transactions between the tuner and Windows Media Center is through authenticated commands.

For more information about the PBDA services that are described in this section, refer to the following specifications: Sections 6 and 7 of the PBDA Core Services specification.

Sections 3.16 and 3.17 of the PBDA Windows Media Digital Rights Management (WMDRM) specification.

These specifications are part of the overall PBDA specification, which is listed in “Resources” at the end of this paper.

Tuner Requirements for Windows Media CenterFor each PBDA feature in Windows Media Center, a tuner must support one or more PBDA service. Table 3 shows the PBDA services that are required for each PBDA feature.

Table 3. PBDA Features and Required PBDA ServicesFeature Description Required PBDA servicesMan-Machine Interface (MMI)

The MMI defines a set of dialog boxes that PBDA uses to inform and notify the user.

GPNVSCASEventingDFN

Descramble Failure Notifications (DFNs)

DFNs are used to track media streaming errors in PBDA. Failure notifications rely on the MMI to display errors to the user.

GPNVSCAS Note This requirement is necessary for MMI support.

Eventing



Feature Description Required PBDA servicesDFN

Extensible Setup for Tuners

This feature extends Windows Media Center setup capabilities and provides additional first run (FRUN) setup for tuners.

GPNVSCASNote This requirement is necessary for MMI support.

EventingExtensible Tuning PBDA supports an XML-based

tuning mechanism for diverse tuner devices.

TunerGPNVSPotentially GDDS as a source of a

XML tune request (TuneXml) data.PBDA Guide Data This feature extends the guide

data that Windows Media Center provides and defines methods for delivering the data to the user.

GPNVSGDD

Protected Content PBDA provides robust transmission of premium content to Windows Media Center.

DRM WMDRMSession WMDRMTuner

For more information on these features, see “Primary Features in PBDA” later in this paper.

Supported Combinations of RequirementsTo comply with PBDA, a tuner must support the required PBDA services. As long as the tuner supports all required PBDA services, it can support any number of optional PBDA services.

For a complete list of the required and optional PBDA services, see “PBDA Services“ earlier in this paper.

Converting an Existing BDA Solution to PBDAConverting an existing BDA KS tuner to a PBDA tuner is simple. Depending on the configuration of the BDA tuner, you usually do this by updating the tuner’s hardware or firmware.

To convert an existing BDA solution to PBDA and satisfy the mandatory requirements, the BDA events must be updated to meet the PBDA implementation. For more information about converting BDA events to PBDA, refer to the PBDA specification, which is listed in “Resources” at the end of this paper.

Primary Features in PBDAThe primary features that are available when you implement a PBDA solution include the following: The use of MMIs to send messages from the tuner to the user.

Extensible setup (or FRUN customization) that allows tuner OEMs to design the FRUN page for Windows Media Center.



Support for PBDA guide data, if the guide data that Windows Media Center provides is not sufficient for a particular scenario.

Support for protected content.

Man-Machine Interface (MMI)In PBDA, a session is established between the tuner and the user through an MMI.

A tuner can easily generate a MMI because the MMI consists of simple Hypertext Markup Language (HTML) script that creates buttons and links. You can author the MMI in Media Center Markup language (MCML) or simple HTML.

MMI messages can appear to the user through the following formats: Dialog box

A dialog box does not appear in a full-screen format and can have up to three buttons. The size of the box changes dynamically depending on the amount of text in the MMI message.Figure 1 shows an example of an MMI message that appears in a dialog box.

Figure 1. MMI that uses a dialog box

Full-screen dialog boxThis type of dialog box always appears full-screen regardless of the amount of text in the MMI message. It can also have up to three buttons.Figure 2 shows an example of an MMI message that appears in a full-screen dialog box.



Figure 2. MMI that uses a full-screen dialog box

Descramble Failure Notifications (DFNs)DFNs are used to track media streaming errors in PBDA. The DFNs are listed in a PBDA TAG table and use the table to associate a failure to the media stream.

Windows Media Center provides a localized user experience (UX) that is based on the error code. However, the tuner can optionally provide a custom UX through an entitlement token in the DFN.

In Windows Media Center, you can use two types of DFNs with PBDA: Simple DFN

This type of notification appears to the user in a full-screen dialog box, as shown in Figure 3.

Figure 3. A simple DFN full-screen dialog box

DFN with MMI



This type of notification provides additional information to the user on top of the simple DFN, as shown in Figure 4.For more information on MMI, see “Man-Machine Interface (MMI)“ earlier in this paper.

Figure 4. DFN with MMI dialog box

Extensible Setup for TunersSome tuners might require additional setup beyond what Windows Media Center provides. For example, a tuner might require proprietary satellite configuration or subscription verification.

Figure 5 shows an example of a FRUN or extensible setup page that a tuner created for satellite activation. In this example, the user is asked to choose to activate the service now, to activate it later, or to specify that it is already activated. The PBDA solution provides this FRUN page, not Windows Media Center.

Figure 5. Example of an extensible setup page



PBDA Guide DataFor a PBDA solution, the guide data that Windows Media Center provides might not be enough for a particular scenario. In this case, PBDA provides the option of delivering proprietary guide data in one of the following ways:

In-band guide data deliveryPBDA supports both Digital Video Broadcast (DVB) and Integrated Services Digital Broadcasting (ISDB) in-band formats for this type of guide data delivery.

Guide Date Delivery Service (GDDS)In this case, the guide data is sent through the command and control channel, not the transport stream.

You can use GDDS in the following ways: As a PBDA service list in XML format that can provide an XML tune request

(TuneXml) for each required service. As a PBDA event information table (EIT) format that supports PBDA or DVB legacy

descriptors.

The XML tuning option provides an extensible tuning mechanism that has diverse devices. Figure 6 shows a simplified tuning flow between the Windows 7 computer and the tuner.

Figure 6. Simplified XML tuning flow

For more information on how to implement XML tuning, refer to the PBDA Tuning Schemas specification. This specification is part of the overall PBDA specification, which is listed in “Resources” at the end of this paper.

Protected Content in PBDAPBDA provides robust transmission of premium content to Windows Media Center. It uses PBDA in-band tag tables and WMDRM. PBDA also maps of both proprietary and standards-based CA policies to WMDRM policies.

The WMDRM uses a session to send all protected content from the tuner to the computer. This session provides a means for the tuner to validate the credentials of



Windows Media Center and allows communication between the tuner and Windows Media Center through authenticated commands.

Figure 7 shows the data flow when you use a protected tuner.

Figure 7. Protected tuner data flow

The WMDRM licenses contain the policy and content keys. The policy consists of rights and restrictions, including the following:

Copyrights, such as copying data to another computer. Export rights based on Content Protection for Recordable Media (CPRM).

Playback restrictions based on: High-Bandwidth Digital Content Protection (HDCP)

Copy Generation Management System (CGMS) Macrovision (MV)

Also, content providers can send different types of content to the tuner. The tuner must be able to identify which protection (if any) is required for each type of content that it supports. A PBDA-compliant tuner must support the following content protection algorithms:

Unencrypted contentThis type of content is free to the user and requires no subscription.

Nonexpiring contentThis content, such as sporting events, is regulated by the provider.

Subscription-based renewable contentThis content is distributed by pay TV providers, such as HBO, based on a renewable subscription to the provider’s service.



Nonrenewable, expiring contentThis content, such as a pay-per-view (PPV) content, is purchased by the user and distributed by the provider on a one-time-only basis.

ResourcesFor the latest information about the Microsoft Windows family, see the Windows Web site at http://www.microsoft.com/windows.

WHDC Web site:Home page

http://www.microsoft.com/whdc/default.mspxProtected Broadcast Driver Architecture (PBDA) Specification (Version 1.3)

http://www.microsoft.com/whdc/device/broadcast/PBDA/pbda_spec.mspx

Appendix: AcronymsAcronym MeaningBDA Broadcast Driver ArchitectureCA conditional accessCAS Conditional Access ServiceCGMS Copy Generation Management SystemCPRM Content Protection for Recordable MediaDFN Descramble Failure NotificationDRM Digital Rights ManagementDVB Digital Video BroadcastingEIT event information tableFRUN First RunGDDS Guide Data Delivery ServiceGPNVS General Purpose Name Value ServiceHDCP High-Bandwidth Digital Content ProtectionHTML Hyper Text Markup LanguageISDB Integrated Services Digital BroadcastingKS kernel streamingMCML Media Center Markup LanguageMMI Man-Machine InterfaceMV MacrovisionOEM original equipment manufacturerPBDA Protected Broadcast Driver ArchitecturePPV pay-per-viewUX user experienceWMDRM Windows Media Digital Rights ManagementXML Extensible Markup Language


http://www.microsoft.com/whdc/device/broadcast/PBDA/pbda_spec.mspx

http://www.microsoft.com/whdc/default.mspx

http://www.microsoft.com/windows

overview of bda and pbdadownload.microsoft.com/.../pbda_bda_migration.docx · web viewman-machine...

Documents