Microsoft Technology Licensing, LLC

Microsoft Corporation

Vinay Krishnaswamy

Marco A Demello

John L Manferdelli

Attila Narin

Frank Byrum

Pavel Zeman

Chandramouli Venkatesh

Michael David Marr

Mariusz Hieronim Jakubowski

Scott C Cottrille

Peter David Waxman

Gregory Kostal

Steven Bourne

Prashant Malik

Steve Bourne

Vladimir Yarmolenko

Ravipal S Soin

Yoram Yaacovi

Rushmi U Malaviarachchi

Venkateshaiah Setty

Stephane Joseph Comeau

Patrick Edgar Schreiber

Ramraj Rajkumar

Leroy B Keely

Leroy Bertrand Keely, Jr

Joseph M Joy

David B Wecker

Ravindra Pandya

Eric Joel Stollnitz

Muthukrishnan Paramasivam

Michael P Calligaro

Randal James Ramig

Aditya Sankar

Jeffrey H Alger

Tanuja Abhay Joshi

Kathryn E Hughes

Thomas K Lindeman

Bradley S Serbus

Yevgeniy (Eugene) Rozenfeld

Marco M DeMello

Attilla Narin

James E Oker

Jeffrey A Alger

Narendranath Datha

Bartosz Gulik

James B Shobe, Jr

Sujith Radhakrishnan Warrier

Kanchen Rajanna

Jason Ralls

Frank D Byrum

Ravindra N Pandya

Marko A Demello

Bradley Serbus

David Brian Wecker

Randal Ramig

'Experience Streams' (ESs) are used by a 'rich interactive narrative' (RIN) data model as basic building blocks that are combined in a variety of ways to enable or construct a large number of RIN scenarios for presenting interactive narratives to the user. In general various ES types contain all the information required to define and populate a particular RIN, as well as the information (in the form of a series of navigable states) that charts an animated and interactive course through each RIN. In other words, combinations of various ES provide a scripted path through a RIN environment, as well as various UI controls and/or toolbars that enable user interaction with the interactive narrative provided by each RIN. Example ESs include, but are not limited, content browser experience streams, zoomable media experience streams, relationship graph experience streams, player-controls/toolbar experience streams, etc.

Experience streams for rich interactive narratives

Systems and methods for visually representing scripted behaviors are provided. A system is disclosed that includes an authoring program executable on a computing device and configured to display a visual scripting interface. The visual scripting interface may be configured to display a plurality of user-selectable graphical building blocks. Each graphical building block may represent a respective component of a script, and may be spatially arrangable within the visual scripting interface to visually represent a script for a target scripted object. Input selectors may be provided on the graphical building blocks to enable users to input script information, and status indicators and messages may also be displayed on the graphical building blocks to inform users whether script information has been properly inputted. Propagation tools may be provided to enable users to successively add new graphical building blocks to build a tree that represents a script sentence.

Visual interface to represent scripted behaviors

A secure repository individualized for a hardware environment and a method and system for providing the same. The secure repository includes a hidden cryptographic key and code that applies the key without requiring access to a copy of the key. The code that implements the secure repository is generated in a manner that is at least partly based on a hardware ID associated with the hardware environment in which the secure repository is to be installed, and may also be based on a random number. Cryptographic functions implemented by the secure repository include decryption of encrypted information and validation of cryptographically signed information. The secure repository may be coupled to an application program, which uses cryptographic services provided by the secure repository, by way of a decoupling interface that provides a common communication and authentication interface for diverse types of secure repositories. The decoupling interface may take the form of a single application programmer interface (API) usable with multiple dynamically linkable libraries.

Secure repository with layers of tamper resistance and system and method for providing same

A presentation application provides for authoring and playback of a presentation. A presentation is an interactive collection of activities. An activity may include one or more frames, wherein each frame includes one or more modules. A module may consist of media content such as video, text, images or other content. A user may provide input during playback of the presentation. In response to the input, the module or frame receiving the input may call an action on a presentation activity, frame or module, thereby allowing the user to navigate through the presentation and accomplish objectives. When authoring a presentation, a user may associate a user initiated event or internally generated event with a module action. Authoring may be performed through an authoring interface provided by an authoring tool. The authoring tool may save a presentation as a package which can be distributed.

Generating media presentations

A digital rights management system for the distribution, protection and use of electronic content. The system includes a client architecture which receives content, where the content is preferably protected by encryption and may include a license and individualization features. Content is protected at several levels, including: no protection; source-sealed; individually-sealed (or 'inscribed'); source-signed; and fully-individualized (or 'owner exclusive'). The client also includes and/or receives components which permit the access and protection of the encrypted content, as well as components that allow content to be provided to the client in a form that is individualized for the client. In some cases, access to the content will be governed by a rights construct defined in the license bound to the content. The client components include an object which accesses encrypted content, an object that parses the license and enforces the rights in the license, an object which obtains protection software and data that is individualized for the client and/or the persona operating the client, and a script of instructions that provides individualization information to a distributor of content so that the content may be individualized for the client and/or its operating persona. Content is generally protected by encrypting it with a key and then sealing the key into the content in a way that binds it to the meta-data associated with the content. In some instances, the key may also be encrypted in such a way as to be accessible only by the use of individualized protection software installed on the client, thereby binding use of the content to a particular client or set of clients.

Accessing protected content in a rights-management architecture

A presentation application provides for authoring and playback of multi-media presentations. Each page of the presentation may contain one or more types of media, including video, text, images and other media. A user may interact with the presentation during playback by selecting different instances of the media. Media elements of the presentation may be tagged with meta-data. Tagged media elements may generate a tag event associated with meta-data in response to being selected, perform an action when a tag event with a particular meta-data occurs, or both. When a user selects a tagged media instance during presentation playback, the tagged media generates a tag event with a particular meta-data. The application detects the tag event, determines one or more other media instances (if any) configured to perform an action upon detection of the tag event with the particular meta-data, and carries out the corresponding action.

Media presentation driven by meta-data events

A method for managing rights in digital content includes generating rights data for a piece of digital content and forming a piece of rights managed digital content by associating the rights data with the piece of digital content. The rights data includes parameters that govern the terms on which the content may be licensed, and may include a list of entities to which the content may be licensed, a respective set of one or more rights that each such entity has in the digital content, and any conditions that may be placed on those rights. A method for licensing rights managed digital content includes receiving a license request for a license to use the piece of rights managed digital content, where the license request includes such a signed rights label. The digital signature on the signed rights label is validated to determine whether a trusted entity issued the signed rights label. If a trusted entity issued the signed rights label, a license to use the piece of rights managed digital content in accordance with the rights data may be issued.

Systems and methods for issuing usage licenses for digital content and services

A license is issued to a user as decryption and authorization portions. The decryption portion is accessible only by such user and has a decryption key (KD) for decrypting corresponding encrypted digital content and validating information including an identification of a root trust authority. The authorization portion sets forth rights granted in connection with the digital content and conditions that must be satisfied to exercise the rights granted, and has a digital signature that is validated according to the identified root trust authority in the decryption portion. The user issued accesses the decryption portion and employs the validation information therein to validate the digital signature of the authorization portion. If the conditions in the authorization portion so allow, the rights in the authorization portion are exercised by decrypting the encrypted content with the decryption key (KD) from the decryption portion and rendering the decrypted content.

Flexible licensing architecture in content rights management systems

A digital rights management system for the distribution, protection and use of electronic content. The system includes a client architecture which receives content, where the content is preferably protected by encryption and may include a license and individualization features. Content is protected at several levels, including: no protection; source-sealed; individually-sealed (or 'inscribed'); source-signed; and fully-individualized (or 'owner exclusive'). The client also includes and/or receives components which permit the access and protection of the encrypted content, as well as components that allow content to be provided to the client in a form that is individualized for the client. In some cases, access to the content will be governed by a rights construct defined in the license bound to the content. The client components include an object which accesses encrypted content, an object that parses the license and enforces the rights in the license, an object which obtains protection software and data that is individualized for the client and/or the persona operating the client, and a script of instructions that provides individualization information to a distributor of content so that the content may be individualized for the client and/or its operating persona. Content is generally protected by encrypting it with a key and then sealing the key into the content in a way that binds it to the meta-data associated with the content. In some instances, the key may also be encrypted in such a way as to be accessible only by the use of individualized protection software installed on the client; thereby binding use of the content to a particular client or set of clients.

System and method for accessing protected content in a rights-management architecture

Systems and methods for providing digital rights management services are disclosed. Such a system includes a service program that provides a processing framework for performing a digital rights management service, such as publishing or licensing rights managed digital content. A plurality of plug-in components are provided, each of which performs a respective task associated with the digital rights management service. The plug-in components are integrated into the processing framework according to predefined sets of interface rules.

Secure server plug-in architecture for digital rights management systems

A licensor receives a request from a requestor including an identifier identifying the requestor and rights data associated with digital content, where the rights data lists at least one identifier and rights associated therewith. The licensor thereafter locates the identifier of the requestor in a directory, and locates in the directory based thereon an identifier of each group which the requestor is a member of. Each of the located requestor identifier and each located group identifier is compared to each identifier listed in the rights data to find a match, and a digital license to render the content is issued to the requestor with the rights associated with the matching identifier.

Publishing digital content within a defined universe such as an organization in accordance with a digital rights management (DRM) system

Content is encrypted according to a content key (CK) ((CK(content))), (CK) is protected according to a license server public key (PU-DRM), and rights data associated with the content is retrieved from a rights template and protected according to (PU-DRM). The protected items and a digital signature from the rights template are submitted as a rights label to the license server for signing. The license server verifies the rights template signature, and if such signature verifies signs the rights label to result in a signed rights label (SRL), and returns same. The SRL is concatenated with (CK(content)) and both are distributed to a user. To render the content, the user submits the SRL to the license server to request a license.

Using a rights template to obtain a signed rights label (SRL) for digital content in a digital rights management system

Growing community of inventors

Woodinville, WA, United States of America

Vinay Krishnaswamy