Patent Application
20060248596
The present description will be better understood from the following detailed description read in light of the accompanying drawings, wherein:
Like reference numerals are used to designate like parts in the accompanying drawings.
The detailed description provided below in connection with the appended drawings is intended as a description of the present examples and is not intended to represent the only forms in which the present examples may be constructed or utilized. The description sets forth the functions of the examples and the sequence of steps for constructing and operating the examples in connection with the examples illustrated. However, the same or equivalent functions and sequences may be accomplished by different examples.
The examples described are directed to a Digital Rights Management (DRM) system operating with time based licenses that may support content rental, subscription models and previews. This type of DRM system may utilize a “secure clock” service, and a “grace period” that may allow media to be played in the event the secure clock interruption that may not be reset immediately. This type of DRM system typically includes one or more CE devices.
Although the present examples are described and illustrated as being implemented in a consumer electronics (“CE”) device system, the system described is provided as an example and not a limitation. CE devices may include pocket PCs, set top boxes, portable media centers, cell phones, music players, PCs, software constructed media players, high fidelity components, and the like. In fact PCs are a common device that may be provided with DRM enabling software to function as a CE device. In addition PCs may be equipped with software applications that can also operate in conjunction with grace period. PCs may be used as docking stations for a user to store content on, and then download some or all of it to another CE device, such as an MP3 player. These CE devices are typically configured to operate in a system that includes the internet, PCs and the like to facilitate license and media content transfer.
A typical licensing system is a digital rights management (“DRM”) system. As those skilled in the art will appreciate, the present example is suitable for application in a variety of different types of systems that operate under a license. The use of grace periods may be useful in the management of licensed content for these types of systems, and in particular systems that include a secure clock that tends to prevent tampering with the time based license by setting the clock back.
A license typically accompanies a media file (not shown) that has been downloaded to the CE device 101, or to a PC 113. In the past licenses have been typically downloaded with the content, and not separately, although they may be downloaded together. The number of licenses on the CE device 101 can be extremely large, such that a user typically can not keep track of the individual conditions applied to each media file by its associated license. A PC will typically contain even more licenses. Occasionally, more than one license will be associated with a media file.
Licenses typically regulate the use of content. Most current DRM solutions rely on unique identification of user devices, such as CE devices. In such systems each license is typically bound to a unique consumer electronics device (or playback device), so the license stored in one CE device typically can not be transferred or used by another device. The license may be provided with information to specify a Grace Period for the particular media being controlled by that license. The licenses are typically stored separately from the content, typically in a dedicated storage area such as a secure store.
Licenses may include numerous functions, other than simply giving permission to use an associated file. For example information may be provided in the license to control how the file is played by setting the grace period. Grace periods may be used to allow play of content to continue for limited time periods, on a license by license basis if a system clock in the CE device is interrupted. The grace period may be provided in conjunction with other license features as well.
Specialized licenses may also utilize grace periods. A time based license is a license that allows for content rental, subscription models, premiers and previews. A time-based license typically requires that a clock is present on the CE device before it can be used. Thus using grace periods in association with this type of license will also improve a users experience by allowing content to play for a limited time after a reset event, or clock failure.
A users experience may be improved if licenses specify a grace period so that an interruption to the CE device secure clock does not tend to interfere with use of the CE device. A service provider may or may not wish to provide grace periods for a media file. Also a various content owners, or service providers, may wish to provide grace periods of varying lengths of time. Being able to provide grace periods, if desired, and to vary their lengths by individual file allows content owners more control in licensing their content. Grace period may contribute to a DRM system that is invisible to the user. Licenses and the grace period associated with them may be managed by an application program, or by a system of digital rights management.
In particular content may be anything that a provider desires to protect such as music, video, multimedia, pictures and the like. Content is typically regulated to prevent its unauthorized use by providing licenses. Content may be audio, video, textual, encrypted, unencrypted, compressed, uncompressed or otherwise manipulated. In a DRM system the content, (or equivalently media, media files, files, or the like) to be played, can typically be freely transferred. Transfer of encrypted content is typically over unsecured channels such as the internet. In a DRM system the playback of the content is controlled, or allowed, by a license that may be typically stored on a specific CE device. Those skilled in the art will realize that the term “play” as used herein may also be construed to mean consumed, or other equivalent terms that indicate that there are limits placed upon accessing the media file governed by the license. Digital media file 210 is typically encrypted by service provider 207 prior to transmission, and is typically decrypted into an unencrypted media file 209 at the CE device 201 or 203
A personal computer 203 may be used to couple 204 to the internet 205 as a CE device. The computer may also be used to transfer content and licenses from the service provider 207 to another more portable consumer electronics device 201 via the path 202 shown. The personal computer and the CE devices may operate utilizing any number of suitable operating systems known to those skilled in the art to implement the desired DRM processes being activated. The instructions for implementing the functions described in this application may exist as software, hardware (for example instructions burned into an ASIC), or a combination of both.
The PC may act as a main storage location and have a large number of licenses and media files stored on it. The licenses can have grace period, unlimited rights, rights to play the file a certain number of times, rights to play the file until a certain date, and the like. Protocols for transferring information to the PC 203, and to the CE device 201 over paths 202 and 204 may be achieved by conventional connections such as Ethernet, USB, infrared, Bluetooth, MTP and the like. These pathways may be useful for transmitting licenses and content, including licenses that have incorporated grace period.
A CE device 201 may be as previously noted a variety of devices equipped with a processor. As shown here 201 the CE device may be a portable personal electronics device such as a digital juke box, MP3 player, or the like.
In alternative embodiments a consumer electronics device 201 may be coupled 204 to a service provider 207 without using the personal computer 203 as an intermediary. In this example the CE device 201 operates to download media and licenses directly from the internet.
A DRM capable device, such as a CE device 201, or a PC 203, typically includes a number of DRM components 214 utilized by a DRM system. The components 214 are typical, but not limiting, of DRM components. A similar set of components may be associated with the PC 203, but are omitted to simplify the figure. Typical DRM components may include one or more licenses 202, having grace period 215. Also shown as part of a typical DRM system is a device certificate 211 that may uniquely identify the CE device 201 to the DRM system 200. Device certificates may provide cryptographical hand shake information that may facilitate the transfer of information, such as a master clock signal 210 from a trusted time authority 216.
In a typical application, DRM system 200 protects contents 210 by providing encrypted data files 209. Since files 209 are encrypted, the data itself is protected. Thus, the files 209 may be moved, archived, copied, or distributed without restriction. There is no need to hide files or make them inaccessible, or to put special protection in place when files are transmitted from system to system. However, copying a file and giving it to a friend will not enable that friend to use the file. In order to be able to use an encrypted file, users must obtain a license 208. This license 208, that typically includes a grace period 215, is a way of exercising control over the encrypted file 210 and the unencrypted version 209 of the file. A license 208 is typically granted to a single machine 201, and even if copied, it will not tend to function on other machines.
An example of a Digital Rights Management system that may be capable of utilizing Grace Periods is described in U.S. patent application Ser. No. 09/290,363, filed Apr. 12, 1999, U.S. patent applications Ser. Nos. 10/185,527, 10/185,278, and 10/185,511, each filed on Jun. 28, 2002 which are hereby incorporated by reference in its entirety.
The DRM system described may include a trusted time authority 216. The trusted time authority 216 may be provided by the service provider 207, or by another suitable source. For example the trusted time authority could be supplied by another PC or even by a system clock available from another source such as by a wireless link to a cellular telephone master clock. The trusted time authority 216 typically provides a known time to a CE device 201, 203, so that a clock on the CE device may be set. The trusted time authority 216 may be coupled 220 through the service provider, or alternatively 219 directly to a CE device 201. The exchange to establish the secure clock may be a cryptographically keyed exchange. The CE device typically includes a secure clock 218 that processes the signal from the trusted time authority. Adjustments to the secure clock are typically inaccessible to a user to prevent tampering with time based licenses that may be present. Secure clocks and the trusted time based authority are described in further detail below.
In a conventional DRM capable device, after a clock reset, a CE device should have access to the trusted time authority to set the device clock. Otherwise it will not be able to play the time based contents. Grace period allows playing content until the trusted time authority can be contacted or until Grace period is expired.
A secure clock is typically used to prevent circumvention of time based licenses by turning the clock back. If the CE device supports “Secure Clock”, the clock was previously assumed to be either unset (in unset mode), or set to an accurate time (in normal mode). If device gets reset due to any reason (e.g. batteries exhausted), the clock become unset. The device must set the clock itself by contacting a trusted network source either directly, or by proxying through a PC. To prevent circumvention of the time based license, users are not allowed to manually set the clock. If the network source is not available, time based content will not play on the CE device until the clock is set. Grace periods allow limited play by placing the CE device in a grace period mode.
In the duration called the Grace Period content is allowed to play until the device clock can be securely reset or until the Grace Period duration specified in the license expires. In grace period mode, the device clock is set to “last good known time” after an interruption. Once the device receives an accurate time from the network, it resumes normal operation.
If the clock is set and the device is properly initialized then time based licenses are allowed to flow, or be downloaded, to the CE device 304. Prior to playing content the CE device initiates a check of the clock state 306. At block 308 a determination is made to see if the CE device clock is in the unset mode. If it is, then content may not be played 310. Returning to block 308, if the CE device is in the normal, or grace period modes, then the content is allowed to play 312. While playing any grace period present may be monitored 314 for expiration. If the grace period has expired content is not played 310. If the grace period has not expired then the CE device continues to play the content 316.
In the “grace period mode” 409, 412 of operation in a DRM system the device clock is set to “last good known time” after a power loss and a reset of the CE device playing a media file. The last known good time is the last time reading of a plurality of time readings that were stored to the secure store before a clock failure. A CE device enters in “grace period” mode if device is reset, and if the device clock was set before so it memorizes the “last good known time” and sets clock to that time. The last known good time is not accurate time but it is the best guess of the time when the clock ceased operation.
The grace period may be stored in non volatile memory as are play counts and the like. As the grace period has been used up, this elapsed time may be subtracted from the grace period time stored in the non volatile memory so that a grace period may be consumed over a number of CE device resets before the clock is synchronized with the trusted time authority.
When a CE device is initially connected with PC, it is in an unset mode until the clock is set. First the PC queries the CE device about the state of secure clock. The DRM system secure clock settings on the CE device goes to “Unset”, “Normal” or “Grace period” mode depending upon the state of the CE device.
After initiation of determining the clock state 401, inquiry is next made to determine if the clock is reset at block 403. If the clock of the CE device has not been reset the CE device may get time from the device and store it as a “last known good time” in secure store. A “clock ever set” flag may be set to a true state. Next the device goes to normal mode at block 404.
Returning to block 403, if the clock is determined to have been reset, a further inquiry is made at block 405 to determine if the clock was ever set. If the clock was never set the CE device goes into the unset mode as shown in block 406. If the clock has been set the process proceeds to block 407. At block 407 the clock goes to the last known good time. The device clock is set to this time.
At block 408 an inquiry is made to determine if the CE device is already in the grace period. If it is then the CE device continues in the grace period mode as shown in block 409. If the CE device is not in the grace period mode then the process proceeds to block 410.
Next the current time is stored as the grace period start time at block 410. And finally the CE device goes into the grace period mode at block 412.
If the license specifies a grace period duration, the media file governed by the license can be played for the grace period duration if the device is operating in the grace period mode of operation. The duration of the grace period is typically specified in the license. Whenever the CE device goes in “Grace period” mode for the first time, that time is recorded as “Grace period start time”. This time is used to evaluate the license in grace period. If the difference between current time and “Grace period start time” is less than the duration of the “Grace period”, content will play.
The next time the device gets the time from network, the DRM system clears all Grace Period related flags, and sets the accurate time. Then saves this accurate time as “Last known good time” and puts device in “normal” state.
Secure Clock and Trusted Time Authority
As discussed above, a license associated with a media file may include a temporal requirement or restriction. For example a restriction might be that the media file can not be rendered before and/or after a certain time. In implementing this restriction, reference may be made during license evaluation to a clock on the CE device for a current time. However, a user may circumvent such a temporal restriction merely by falsely setting the clock on the CE device to a time that satisfies the temporal restriction. A secure clock tends to prevent this type of circumvention, and may be called upon in the challenge and response exchange described above for setting the secure clock.
The trusted time authority 216 typically maintains a trusted time in any appropriate convention, and the secure clock 522 on the computing device 201, 203 is adjusted to the trusted time, either by the trusted time authority 216, the computing device 201, 203, the trusted component 518 thereon, or the like.
Trusted time may be kept with respect to a particular time zone or an absolute time—for example, Eastern U.S. time, coordinated universal time (UTC), astronomical time, etc. Such trusted time typically includes date information and time of day information, and is expressed according to a recognizable convention. For example, trusted time at 1:23:46 PM on Apr. 11, 2002, UTC, may be expressed as 20020411132346Z, where 2002 represents the year, 04 represents April, 11 represents the day, 13 represents the hour, 23 represents the minute, 46 represents the second, and Z represents UTC. Of course, any appropriate convention for trusted time may be employed.
A computing device 14 with a secure clock 522 may have an appropriate time display 562 for displaying time to a user of such computing device 201, 203. In some applications a time display may not be provided Such time display 562 may be any appropriate display 562, for example an LED, LCD display, an on-screen display or the like. However, the trusted time as maintained by the secure clock 522 may not necessarily be amenable for displaying on the time display 562. For example, if trusted time is maintained according to the UTC convention and the user is in the United States Eastern time zone (ET), the trusted time may actually be 4 or 5 hours ahead of local time for the user.
In one example of providing a trusted time base, the computing device 201, 203 also has a time offset 564 within which is a time value that may be adjustable by the user. Thus, the computing device 201, 203 can calculate a running real-time display time 566 equal to the trusted time on the secure clock 522 plus the time value in the time offset 564, where the display time 566 is displayed in the time display 562 of the computing device. Notably, while the user can adjust the time value in the time offset 564 to adjust the display time 566 shown in the display 562, such user cannot likewise adjust the trusted time as maintained in the secure clock 522. Thus a trust-based system such as the DRM system can refer to the secure clock 522 for trusted time without fear that such trusted time has somehow been modified by a user who may wish to subvert a temporal requirement in a license.
While the user may adjust the time value in the time offset 564, such a capability is not a requirement in providing a secure clock. In fact, in one alternative example, the time value in the time offset 564 is limited to one or more pre-determined values such as may correspond to time differences that arise from time zones or the like. In addition, the time value in the time offset 564 may be controlled by the trusted time authority 216, the computing device 201, 203, the DRM system, other trust-based system, or the like.
In an alternative example, the trusted component 518 on the computing device 201, 203 is employed to receive trusted time from the trusted time authority 216. Thus, encryption-based signing and verification keys are employed by the trusted component 518 and the trusted time authority 216 to produce signed messages and/or certificates that that may be verified as being valid.
At some point during operation of the trusted component 518 and/or the computing device 201, 203, it may be determined that the secure clock 522 must be set according to trusted time as received from the trusted time authority 216. Regardless of how or when the determination is made, in one example the secure clock 522 is set by having the trusted time authority 216 send a new secure time for the secure clock 522 of the computing device 201, 203. An example of setting the secure clock is provided by a conventional challenge response process with a trusted time authority 302. A challenge is sent to the trusted time authority 216 from the trusted component 518 and/or the computing device 201, 203. After receiving a response from trusted time authority 216, the response is verified by the trusted component 518. If the verification is successful, clock is set to a secure time received in the response.
An example of a secure clock and a trusted time authority that may be capable of utilizing Grace Periods is described in U.S. patent application Ser. No. 10/171,269, filed Jun. 13, 2002, which is hereby incorporated by reference in its entirety.
The computing environment 600 can be implemented with numerous other general purpose or special purpose computing system configurations. Examples of well known computing systems, may include, but are not limited to, personal computers, hand-held or laptop devices, microprocessor-based systems, multiprocessor systems, set top boxes, programmable consumer electronics, gaming consoles, Consumer electronics, cellular telephones, PDAs, and the like.
The computer 600 includes a general-purpose computing system in the form of a computing device 601. The components of computing device 601 can include one or more processors (including CPUs, GPUs, microprocessors and the like) 607, a system memory 609, and a system bus 608 that couples the various system components. Processor 607 processes various computer executable instructions to control the operation of computing device 601 and to communicate with other electronic and computing devices (not shown). The system bus 608 represents any number of several types of bus structures, including a memory bus or memory controller, a peripheral bus, an accelerated graphics port, and a processor or local bus using any of a variety of bus architectures.
The system memory 609 includes computer-readable media in the form of volatile memory, such as random access memory (RAM), and/or non-volatile memory, such as read only memory (ROM). A basic input/output system (BIOS) is stored in ROM. RAM typically contains data and/or program modules that are immediately accessible to and/or presently operated on by one or more of the processors 607.
Mass storage devices 604 may be coupled to the computing device 601 or incorporated into the computing device by coupling to the buss. Such mass storage devices 604 may include a magnetic disk drive which reads from and writes to a removable, non volatile magnetic disk (e.g., a “floppy disk”) 605, or an optical disk drive that reads from and/or writes to a removable, non-volatile optical disk such as a CD ROM or the like 606. Computer readable media 605, 606 typically embody computer readable instructions, data structures, program modules and the like supplied on floppy disks, CDs, portable memory sticks and the like.
Any number of program modules can be stored on the hard disk 610. For example a number of licenses 102, including grace periods 112. Mass storage device 604, ROM and/or RAM 609, including by way of example, an operating system, one or more application programs, other program modules, and program data. Each of such operating system, application programs, other program modules and program data (or some combination thereof) may include an embodiment of the systems and methods described herein.
A display device 602 can be connected to the system bus 608 via an interface, such as a video adapter 611. A user can interface with computing device 602 via any number of different input devices 603 such as a keyboard, pointing device, joystick, game pad, serial port, and/or the like. These and other input devices are connected to the processors 607 via input/output interfaces 612 that are coupled to the system bus 608, but may be connected by other interface and bus structures, such as a parallel port, game port, and/or a universal serial bus (USB).
Computing device 600 can operate in a networked environment using connections to one or more remote computers through one or more local area networks (LANs), wide area networks (WANs) and the like. The computing device 601 is connected to a network 614 via a network adapter 613 or alternatively by a modem, DSL, ISDN interface or the like.
Those skilled in the art will realize that storage devices utilized to store program instructions can be distributed across a network. For example a remote computer may store a tool such as the adaptive instrumentation runtime monitoring and analysis software. A local or terminal computer may access the remote computer and download a part or all of the software to run the program. Alternatively the local computer may download pieces of the software as needed, or distributively process by executing some software instructions at the local terminal and some at the remote computer (or computer network). Those skilled in the art will also realize that by utilizing conventional techniques known to those skilled in the art that all, or a portion of the software instructions may be carried out by a dedicated circuit, such as a DSP, programmable logic array, or the like.
Those skilled in the art will realize that storage devices utilized to store program instructions can be distributed across a network. For example a remote computer may store an example of the process described as software. A local or terminal computer may access the remote computer and download a part or all of the software to run the program. Alternatively the local computer may download pieces of the software as needed, or distributively process by executing some software instructions at the local terminal and some at the remote computer (or computer network). Those skilled in the art will also realize that by utilizing conventional techniques known to those skilled in the art that all, or a portion of the software instructions may be carried out by a dedicated circuit, such as a DSP, programmable logic array, or the like.
