Microsoft Technology Licensing, LLC

Panasonic Corporation

Michael Jay Parks

Charlton E Lui

Clifford Paul Strom

Kevin Phillip Paulson

Jeff Blum

Brian Patrick Evans

Toshihisa Nakano

Kaoru Murase

Shunji Harada

James Morris Alkove

Ian Cameron Mercer

Jeffrey Richard McKune

Kevin Leigh LaChapelle

Benjamin Brooks Cutter, Jr

Benjamin Brooks Cutter

A source generates a medium key (KM) and a media secret table including a plurality of entries, each entry including (KM) encrypted by a public key (PU-PD) of a plurality of devices, obtains the medium ID of a medium therefrom, generates a content key (KD) for a piece of content, encrypts the content with (KD) to result in (KD(content)), encrypts (KD) with (KM) to result in (KM(KD)), generates a package for the content including (KD(content)), (KM(KD)), the medium ID, and a signature based on at least the medium ID and verifiable with (KM), and copies the generated package and the media secret table to the medium. Thus, a device with the medium and a private key (PR-PD) corresponding to an entry of the media secret table can access and render the content.

Encryption and data-protection for content on portable medium

A request to render encrypted content is received and a chain of licenses corresponding to the content is located. The chain includes a leaf license linked to the content at one end of the chain, a root license at the other end of the chain, and any intermediate licenses therebetween. The leaf license and any intermediate licenses in the chain are each bound to the adjoining license in the chain toward the root license, and the root license is bound to an owner of a private key (PR-U). For each license in the chain, the license is verified and it is confirmed that the license allows the content to be rendered. A decryption key is obtained from the leaf license based on application of (PR-U) to the root license, the obtained key is applied to decrypt the encrypted content, and the decrypted content is rendered.

Rendering digital content in a content protection system according to a plurality of chained digital licenses

A method of embedding voice data in a computing system includes detecting a record event and detecting if a software application currently running on the computing system is voice-aware. The method also includes embedding the voice data within associated data in the software application, if the software application is voice-aware. If the software application is not voice-aware, the method also includes triggering a voice note application to record and store the voice data. A method in a computing system for modifying a user interface displayed on a display device includes receiving an indication from the computing device to modify the user interface. The method further includes displaying an identification block, a record toolbar, a note pad, and a note tab.

Method and system for embedding voice notes

Metered data is accumulated and is indexed within a metering database of a client according to a metering ID (MID) and a content-associated ID (KID). The client selects a particular MID and metered data in the metering database having the selected MID, and constructs a challenge based on the selected metered data and sends same to a metering service. The metering service obtains the metered data from the challenge, stores same, and constructs a response. The client receives the response including a list of KIDs of the selected metered data in the challenge, and processes the list of KIDs by, for each KID in the list, deleting the metered data from the metering database having the selected MID and the KID.

Metering accessing of content and the like in a content protection system or the like

A universal file format for providing digital rich ink data documents. Digital rich ink data is hidden among the ink image data otherwise stored in a widely-accepted image file format. For example, depending on the type of file, data can be concealed in the least significant bit or bits of pixel information, or stored in-different color indexes of a palette that result in the same color output. In other file types, digital rich ink data may be appended after the end of file marker, or placed in a comment area. When such a file is accessed, computing devices capable of handling rich ink data recognize and extract the rich ink data from the file, while devices incapable of recognizing the format are still able to display the ordinary ink data. Two file formats for describing the arrangement of rich ink data are also provided.

Universal file format for digital rich ink data

Growing community of inventors

Kirkland, WA, United States of America

Michael Jay Parks