Pluggable file-based digital rights management api layer for applications and engines

Abstract

A pluggable file-based DRM (digital rights management) API (application program interface) layer for applications and engines. The invention defines a pluggable file-based DRM API layer such that mobile operators can choose to use any file-based DRM (FDRM) engine in their final product. An FDRM engine can be content agnostic (e.g., can range from an executable to a media file or ring-tone). In accordance with the invention, an application can become DRM aware by calling the novel file-based DRM APIs. Any FDRM engine can be plugged into the novel API layer such that applications can use the protected content. The API layer of the subject invention can be designed such that applications that are DRM aware by using the file-based DRM API layer can be DRM engine agnostic.

1 . A method of providing DRM-protected content, comprising:
 adding a plug-in DRM API to an application; the plug-in DRM API enables the application to support a plurality of disparate DRM engines;   selecting an object;   verifying a DRM right associated with the object; and   committing the DRM right used by the object.   
   
   
       2 . The method of  claim 1 , further comprising at least one of the acts of enabling a DRM provider notification and disabling the DRM provider notification. 
   
   
       3 . The method of  claim 1 , further comprising launching a UI that updates the DRM right. 
   
   
       4 . The method of  claim 1 , further comprising renewing the DRM right used by the object. 
   
   
       5 . The method of  claim 1 , further comprising an act of converting the application into a DRM aware application using the DRM API. 
   
   
       6 . A system that facilitates employing DRM-protected content, comprising:
 means for receiving a create request from an application that facilitates opening a file;   means for calling a content handler that facilitates storing content of the file in a device file system and storing a content DRM right in a rights store; means for verifying the content DRM right;   means for employing the content if the content DRM right is valid; means for obtaining an updated DRM right if the content DRM right is not valid; and   means for committing at least one of the content DRM right and the updated DRM right.   
   
   
       7 . A pluggable API layer that employs the system of  claim 6  to convert the application into a DRM aware application. 
   
   
       8 . A system for providing DRM-protected content, comprising:
 a computing processor;   computing memory communicatively coupled with the computing processor, the computing memory having stored thereon instructions that cause the computing processor to perform operations comprising:
 adding a plug-in DRM API to an application, the plug-in DRM API enabling the application to support a plurality of disparate DRM engines; 
 selecting an object; 
 verifying a DRM right associated with the object; and 
 committing the DRM right used by the object. 
   
   
   
       9 . The system of  claim 8 , the computing memory having stored thereon instructions that cause the computing processor to perform at least one of:
 enabling a DRM provider notification; and   disabling the DRM provider notification.   
   
   
       10 . The system of  claim 8 , the computing memory having stored thereon instructions that cause the computing processor to perform launching a UI that updates the DRM right. 
   
   
       11 . The system of  claim 8 , the computing memory having stored thereon instructions that cause the computing processor to perform renewing the DRM right used by the object. 
   
   
       12 . The system of  claim 8 , the computing memory having stored thereon instructions that cause the computing processor to perform converting the application into a DRM aware application using the DRM API.