Abstract: A system for processing a media content comprising an application space, a media control mechanism operating in the application space, the media control mechanism controlling the operation of the system, a user interface adapted to provide input to the media control mechanism, a protected space distinct from the application space, and a protected media pipeline operating in the protected space, the protected media pipeline coupled to the media control mechanism, the protected media pipeline adapted to access the media content, process the media content, and output the media content.

Abstract: A system for processing a media content comprising an application space, a media control mechanism operating in the application space, the media control mechanism controlling the operation of the system, a user interface adapted to provide input to the media control mechanism, a protected space distinct from the application space, and a protected media pipeline operating in the protected space, the protected media pipeline coupled to the media control mechanism, the protected media pipeline adapted to access the media content, process the media content, and output the media content.

Abstract: A method of establishing a protected environment within a computing device including validating a kernel component loaded into a kernel of the computing device, establishing a security state for the kernel based on the validation, creating a secure process and loading a software component into the secure process, periodically checking the security state of the kernel, and notifying the secure process when the security state of the kernel has changed.

Abstract: Various embodiments utilize hardware-enforced boundaries to provide various aspects of digital rights management or DRM in an open computing environment. Against the backdrop of these hardware-enforced boundaries, DRM provisioning techniques are employed to provision such things as keys and DRM software code in a secure and robust way. Further, at least some embodiments utilize secure time provisioning techniques to provision time to the computing environment, as well as techniques that provide for tamper-resistant storage.

Abstract: A protocol is provided that permits a third-party key issuing entity to have its issued keys protected by an unrelated key protecting entity. In at least some embodiments, a trusted key protecting entity is injected, in a sense, in a conversation between the third-party key issuing entity and a client to which one or more keys are distributed. The trusted key protecting entity is able to apply various protections which, in at least some embodiments are unknown to the key issuing entity, to a distributed key which can then be used by the client to access protected content.

Abstract: Various embodiments utilize hardware-enforced boundaries to provide various aspects of digital rights management or DRM in an open computing environment. Against the backdrop of these hardware-enforced boundaries, DRM provisioning techniques are employed to provision such things as keys and DRM software code in a secure and robust way. Further, at least some embodiments utilize secure time provisioning techniques to provision time to the computing environment, as well as techniques that provide for tamper-resistant storage.

Abstract: Various embodiments utilize hardware-enforced boundaries to provide various aspects of digital rights management or DRM in an open computing environment. Against the backdrop of these hardware-enforced boundaries, DRM provisioning techniques are employed to provision such things as keys and DRM software code in a secure and robust way. Further, at least some embodiments utilize secure time provisioning techniques to provision time to the computing environment, as well as techniques that provide for tamper-resistant storage.

Abstract: Methods, systems and architectures for enhancing a user's DVD experience are described. In one embodiment, the physical structure (e.g. titles and chapters) of a DVD is ascertained and a playlist structure shell that represents the DVD's physical structure is built. Metadata associated with the DVD is acquired and used to populate the playlist structure shell. In some embodiments, the metadata can be acquired from a metadata source external to the DVD and/or remote from a computing device on which the DVD is being played. Remote locations can include, without limitation, those that are network- or Internet-accessible. Once the playlist structure shell is populated, it can be used to render a playlist associated with the DVD's video in an area of a user interface display.

Abstract: Various embodiments provide a mapping layer to translate DRM system requirements from one DRM system, such as a source system, to another DRM system, such as a target system. In at least some embodiments, DRM system requirement translation is performed using a signed data structure that maps DRM system requirements from one DRM system to one or more other DRM systems. By mapping DRM system requirements from one system to another, licenses associated with DRM-protected content and associated content can be safely transferred between systems.

Abstract: Systems and methods for providing a protected computing environment comprising separating out a protected environment management component from a kernel of a computing device, providing identification information as a part of the protected environment management component, and providing individualization information as part of the protected environment management component.

Abstract: A media timeline is described. In an implementation, a method includes receiving a request from an application at an application programming interface (API) to interact with a plurality of media. Based on the request, a media timeline is generated. The media timeline is for exposure via the API to the application and includes a plurality of nodes. The media timeline defines a presentation of a first media referenced by a first node with respect to a second media referenced by a second node.

Abstract: Media processing methods, systems and application program interfaces (APIs) are described. In but one embodiment, a media engine component, also referred to as a media engine, provides a simple and unified way of rendering media from an origin to a destination of choice without requiring intimate knowledge about the underlying components, their connectivity and management. Clients of the media engine need not worry about how to render the particular media, but rather can simply focus on what media to render and where to render the media. In at least one embodiment, a media session is provided and is used by the media engine and provides a mechanism by which additional components are made transparent to the application and, in at least some embodiment, the media engine. In some embodiments, the media engine and media session provide a simple API for building, configuring, and manipulating a pipeline of components (e.g.

Abstract: Media processing methods, systems and application program interfaces (APIs) are described. In but one embodiment, a media engine component, also referred to as a media engine, provides a simple and unified way of rendering media from an origin to a destination of choice without requiring intimate knowledge about the underlying components, their connectivity and management. Clients of the media engine need not worry about how to render the particular media, but rather can simply focus on what media to render and where to render the media. In at least one embodiment, a media session is provided and is encapsulated by the media engine and provides a mechanism by which additional components are made transparent to the application and, in at least some embodiment, the media engine. In some embodiments, the media engine and media session provide a simple API for building, configuring, and manipulating a pipeline of components (e.g.

Abstract: Techniques for playing a media file in a multimedia application include launching a multimedia application as one process and automatically launching a pipeline of one or more media processing components as one or more isolated processes. In this manner, any untrustworthy components can be executed in an isolated process that is separate from the execution process of the multimedia application, thereby improving fault tolerance and hang resistance.

Abstract: Systems and methods described herein provide access to multimedia content of varying types from a variety of sources using a uniform resource locator (URL).

Abstract: The present automatic update mechanism provides a method for determining whether computer-readable components loaded within a memory device are at a level of protection specified for protected content that a media application is attempting to process. If a current level of protection provides lower protection that the level specified, a file is updated to achieve at least the level of protection specified by the protected content. Updating the file to achieve the level of protection is performed in a manner that minimizes rebooting of a computing device.

Abstract: Various embodiments provide a mapping layer to translate DRM system requirements from one DRM system, such as a source system, to another DRM system, such as a target system. In at least some embodiments, DRM system requirement translation is performed using a signed data structure that maps DRM system requirements from one DRM system to one or more other DRM systems. By mapping DRM system requirements from one system to another, licenses associated with DRM-protected content and associated content can be safely transferred between systems.

Abstract: In accordance with one or more aspects, a license for content is retrieved, the license having been previously embedded in the content. A requested action is allowed to be performed with the content only if a standalone license, or both a leaf license and a root license, indicate that the action with the content is permissible. Leaf licenses and/or standalone licenses can be embedded by a source of the content and/or by a target device that receives the content. Additionally, licenses can include one or more rules indicating where a target device that receives the content is to store the licenses.

Abstract: A protocol is provided that permits a third-party key issuing entity to have its issued keys protected by an unrelated key protecting entity. In at least some embodiments, a trusted key protecting entity is injected, in a sense, in a conversation between the third-party key issuing entity and a client to which one or more keys are distributed. The trusted key protecting entity is able to apply various protections which, in at least some embodiments are unknown to the key issuing entity, to a distributed key which can then be used by the client to access protected content.

Abstract: Techniques relating to managing multimedia transmissions in terminal services scenarios are described. In one instance, a method sends a user-interface component from a server to a remote client. The method further streams a media component for presentation on the remote client in combination with the user-interface component and wherein the media presentation is tracked but not displayed by the server.