Abstract: A digital rights management (DRM) system distributes the storage of rights and/or the rights management decision making process between a DRM client and a DRM server, in order to overcome the shortcomings inherent in exclusively client-side or exclusively server-side DRM systems.

Abstract: DRM-encrypted content is opened up to “trusted search”, without compromising copyright control, thus allowing end users to locate DRM-encrypted content alongside upon unencrypted content. The indexer (or crawler) (216) of a search engine (214) is provided with a DRM module (302) for communication with a DRM server (306) so that the indexer (216) can access even the encrypted content nominally as if it were a human end user of the content. The indexer (216) may be issued with a DRM-recognized “identity” so as to distinguish itself from other end users and DRM-enabled search engines. Thus, the search engine (214) can programmatically access the content, subject to being able to obtain permission from the DRM solution.

Abstract: A digital rights management (DRM) “bureau” server can be used in many different ways. In one example, a system distributes the storage of rights and/or the rights management decision making process between a DRM client and a DRM server, in order to overcome the shortcomings inherent in exclusively client-side or exclusively server-side DRM systems. In another example, a system manages rights to content on behalf of plural publishers.

Abstract: A method is disclosed for controlling access by use of an operating system service to content that is to be protected from unauthorised access. The method includes the steps of, for an operating system service which can enable unauthorised access to protected content, modifying the operation of said operating system service to restrict or deny access to the protected content.

Abstract: A method of protecting Java bytecode is provided that includes the steps of encrypting at least one Java class file to produce at least one encrypted Java class file (414a) which is archived in an archive (414). A Java application that depends on the encrypted Java archive (414) is configured to run by first loading an application stub class (414b) and calling an entry point within the application stub class (414b). A method is provided of running a Java application that uses such a previously encrypted Java archive (414). The method includes the steps of loading an application stub class (414b). An entry point within the application stub class (414b) is called thereby to call a secure class loader to enable the at least one encrypted Java class file (414a) to be loaded from the archive (414) and decrypted.

Abstract: A digital rights management (DRM) system distributes the storage of rights and/or the rights management decision making process between a DRM client and a DRM server, in order to overcome the shortcomings inherent in exclusively client-side or exclusively server-side DRM systems.

Abstract: A digital rights management (DRM) system distributes the storage of rights and/or the rights management decision making process between a DRM client and DRM server, in order to overcome the shortcomings inherent in exclusively client-side or exclusively server-side DRM systems.

Abstract: Digital rights are associated with a semi-unique node identifier obtained or calculated from characteristics of a mobile device attached to a consumer device, rather than with the node identifier of the consumer device itself. The user of the consumer device may access the digital rights management encrypted content (which may come from local persistent storage or a network) by attaching the mobile device to the consumer device. In this way, the rights can be associated with the node identifier of the mobile device, and the rights are thus usable for the consumer device to access the encrypted content.

Abstract: A digital rights management (DRM) “bureau” server can be used in many different ways. In one example, a system distributes the storage of rights and/or the rights management decision making process between a DRM client and a DRM server, in order to overcome the shortcomings inherent in exclusively client-side or exclusively server-side DRM systems. In another example, a system manages rights to content on behalf of plural publishers.