1 / 21

RMP Specification SP005-1

TV Anytime IDE, September 20, 2004, Sony in San Jose CA. RMP Specification SP005-1. TV-Anytime Rights Management and Protection Information for Broadcast Applications. Nicholas R. Givotovsky - MMG - nrg@m-m-g.net. RMP Approach & Scope .

yauvani-sharma
Download Presentation

RMP Specification SP005-1

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. TV Anytime IDE, September 20, 2004, Sony in San Jose CA RMP Specification SP005-1 TV-Anytime Rights Management and Protection Information for Broadcast Applications Nicholas R. Givotovsky - MMG - nrg@m-m-g.net

  2. RMP Approach & Scope • TVAF RMP started with a vision of an end to end security system with the goal of standardizing all of it. • This proved somewhat challenging • Some degree of controversy regarding the overall requirements and specific required technologies for such a system may have played a role in slowing its completion • Via a lengthy debate followed by a scoping process, TVAF RMP has been able to define the set of high priority usage cases or key scenarios RMP was to support • This in turn has allowed us to progress on a modular basis, while still respecting the requirements of the overall architecture.

  3. Rights Management & Protection Information • RMPI= Rights Management & Protection Information or, “the minimum set of usage rules and conditions required to enable protection of broadcast digital television content within a TVA RMP compliant domain.” • RMPI is the essential signaling element of the system which has become the first element of the overall RMP toolbox to be standardized. • We debated (argued) a lot more about what usage models such RMPI should support. On one end of the spectrum, a very rich set of functions could in theory be supported by “RICH” RMPI. • However, it was agreed that RMP’s immediate priority should be on the creation of standardized signaling for the unidirectional broadcast environment.

  4. RMPI-MB & RMPI-M • When associated with a broadcast signal, RMPI for Broadcast Applications is called RMPI-Micro Broadcast (RMPI-MB). • When associated with content present in a TVA RMP compliant domain (post broadcast/ acquisition) it is called RMPI-Micro (RMPI-M).

  5. RMPI in the Broadcast Environment In the diagram above transfer of content from one RMP domain to another is not regulated by the RMPI-M/MB but the use of the content is.

  6. Introducing SP005-1 • SP005-1 Specifies the semantics, syntax and encoding for the usage rights, controls and permissions to be conveyed in RMPI-MB and RMPI-M.

  7. Principle: Positive Assertion of Rights • TV-Anytime RMPI-MB rights are positively asserted and never implied. • These rights are granted to the RMP System component or entity (EG: a domain) and not to a person. • When a right is exercised, asserted conditions are validated. • If those asserted conditions are not met, then the right cannot be exercised • If conditions are not asserted, then they do not constrain the rights.

  8. Operational Approach • RMPI-MB and RMPI-M focus on the usage of content as opposed to the movement of content. • Therefore there is no notion of “copy” within the secure RMP-compliant domain as only those Principals that have been granted rights to use the content are given access to the content under the conditions expressed in RMPI-MB and RMPI-M.

  9. Compliance • TV-Anytime RMP does not itself mandate specific implementations or compliance and robustness rules. • There are certain parameters in the specification that are left for assignment by the compliance bodies; for example geographic control, RMP domain identifier, single point of control identifier and security level. • It is anticipated that compliance bodies that adopt the specification will define implementation requirements and associated compliance regimes to meet the needs of their respective environments.

  10. Principals: RMP Domains • A Domain is a set of TVA RMP-compliant devices that are securely bound to each other for the purpose of exchanging protected content. It is an instance of a Principal. The rules for creating and managing domains are outside the scope of this specification

  11. Rights • PLAY • ANALOG EXPORT • DIGITAL EXPORT HD • DIGITAL EXPORT SD • EXTEND RIGHTS

  12. CONDITIONS • Geographical Control • Single Point of Control • Physical Proximity • Buffer Duration • Time Window Start Date & Time Window End Date • Standard Definition Digital Export Control • High Definition Digital Export Control • Analog Export Signaling • Analog Standard Definition (SD) control • Security Level • Simultaneous Rendering Count • Source of Additional Rights

  13. ANCILLIARY RIGHTS INFORMATION • Scrambling Control • No scrambling/ • Maintain broadcast scrambling • Apply RMP cipher • Cipher Algorithm • Origin of RMPI

  14. Syntax and encoding for RMPI-MB and RMPI-M • The syntax and encoding for the RMPI-MB and RMPI-M payload is composed of at most four grants including:- • A grant for the Receiving Domain that signals the rights and conditions that apply to content once it has entered a given Receiving Domain. This grant excludes the Extend Rights right. • A grant for Any Domain that signals the rights and conditions that apply to content once it has entered Any Domain. This grant excludes the Extend Rights right. • A grant for the Receiving Domain that signals the Extend Rights right and associated conditions. • A grant for Any Domain that signals the Extend Rights right and associated conditions.

  15. RMPI-MB and RMPI-M Lifecycle • RMPI-MB is transmitted in conjunction with the broadcast signal. At the time of reception in the end user’s TVA RMP Domain it is converted to RMPI-M. • Rights that are granted to the Receiving Domain and Single Point of Control (if present) in RMPI-MB are carried over in RMPI-M. • Generic mentioning of the Receiving Domain and Single Point of Control (if present) in RMPI-MB is translated into explicit mentioning through the explicit statement of Identifiers in RMPI-M. • In order to maintain the persistence of the rights assigned by the broadcaster or content provider, a TVA RMP compliant receiver shall not change any other value in RMPI. • Rights granted to Any Domain are always carried over unchanged from RMPI-MB to RMPI-M. The figure below illustrates the transition from RMPI-MB to RMPI-M in a case where Single Point of Control is asserted.

  16. Conclusion • We believe that RMP RMPI provides a useful mechanism for the explicit uniform signaling of content usage conditions. • It does not mandate those conditions, but enables them to be expressed. • It does not exhaustively enable every conceivable consumption model, nor does it impose unrealistic performance requirements on delivery devices or unrealistic restrictions on the use of content. • TVAF RMP - I T L W C D

  17. Thanks! TVAF RMP www.tv-anytime.org nrg@m-m-g.net

More Related