Appeal 2007-1319
Application 09/797,017
INTRODUCTION
The claims relate to a digital license for specifying rights with respect
to corresponding digital content. When a user attempts to render digital
content on a computing device, the rendering application invokes a Digital
Rights Management (DRM) system on the user’s computing device. If the
user is attempting to render the digital content for the first time, the DRM
system either directs the user to a license server to obtain a license to render
the digital content, or may obtain the license from the server without user
action. The license includes: a decryption key for decrypting the digital
content; a description of the rights (e.g., play, copy) conferred by the license
and related conditions (e.g., begin date, expiration date, number of plays);
and a digital signature that ensures the integrity of the licenses.
(Specification 4: 19-30.)
A generated license 16 (Fig. 8) includes a Digital Rights License
(DRL) 48. (Specification 36: 11-18.) DRLs are written according to a
“flex” language that can specify rights according to events. The flex
language can specify conditions precedent 62 (Fig. 13) to allowing the event
60 to proceed and actions 64 to be taken once the event 62 has been allowed
to proceed. In one embodiment, the flex language allows the license 16 to
store and modify license-related information. (Specification 59: 1-14.)
The Specification provides two examples of a Digital Rights License
(DRL) 48 (Fig. 8). The first, or “simple,” DRL is written in a DRL language
that specifies license attributes. (Specification 48: 20 - 51: 13.) The second
“script” DRL 48 is written in a DRL language that can perform functions
according to the script specified in the DRL 48. (Specification 48: 20-27;
51: 14 - 53: 5.)
2
Page: Previous 1 2 3 4 5 6 7 8 9 10 Next
Last modified: September 9, 2013