Microsoft Technology Licensing, LLC

Marco M DeMello

Jason Matthew Cahill

Vinay Krishnaswamy

John L Beezer

Scott C Cottrille

Peter David Waxman

John L Manferdelli

Lauren Nicole Antonoff

Kevin Lane Brown

David M Silver

Pavel Kouznetsov

Michael Selhorn

Embodiments are described for capturing, displaying, and navigating annotations in an electronic document. In some embodiments, a selection of an object in the electronic document is received, and an annotation associated with the selected object is received. The annotation is maintained in a list of annotations. The annotation can also be displayed. In some embodiments, a selection of the annotation is received and in response to the selection of the annotation being received, a user may be navigated to a location of the selected object in the electronic document.

Annotations for electronic content

A method is disclosed for rendering content encrypted according to a cryptographic key, where the content has corresponding rights data including a decryption key (KD) for decrypting the encrypted content, and where (KD) in the rights data is encrypted according to a public key of a rights management (RM) server (PU-RM) to result in (PU-RM(KD)). The RM server normally delivers (KD) within a license, but upon being decommissioned can no longer issue such license. In the method, a notification is received that the RM server has been decommissioned, and thereafter an attempt is made to render a piece of content. Such content is determined to be protected to the decommissioned RM server, and a request is sent to the decommissioned RM server for the content key (KD) for the content rather than any license. Thereafter (KD) is received from the decommissioned RM server.

Systems, structures, and methods for decrypting encrypted digital content when a rights management server has been decommissioned

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

Growing community of inventors

Redmond, WA, United States of America

Marco M DeMello