Method and apparatus for optimally formatting media key blocks stored on media with high transfer latencies

Abstract

A method and apparatus to format and process a Media Key Block so as to reduce latencies when processing the Media Key Block. A new record is generated containing header information for the records comprising the Media Key Block. This new record is read just once and allows a device to skip seeking and reading each record header individually. In addition, the records are adjusted so that individual records or individual fields within a record always fit within a single transfer unit.

Description

FIELD

[0001] The present invention relates to a system to minimize user-perceptible latencies when processing encrypted information. More particularly, the invention relates to a method and apparatus to format a Media Key Block so as to reduce latencies when processing the Media Key Block.

BACKGROUND OF THE INVENTION

[0002] Increasingly, copyrightable content is being distributed in digital form on various physical media types, including Digital Versatile Disk (DVD). While digital content, such as video and music, has provided greater fidelity to the consumer, it has the significant drawback of being relatively easy to reproduce perfect copies of the content without the authorization of the copyright owner. Because digital content may be copied at any point along the path through which it is transmitted, a number of security measures are usually utilized in combination.

[0003] One such security measure revolves around the use of data or content encryption. Generally, digital content is encrypted and then recorded onto a chosen media. A pre-selected key(s) is then employed by playback devices to decrypt the digital content in order to play it. One drawback with this technology is that once the key(s) has been compromised, unauthorized parties may build devices to copy the decrypted digital content. Said compromised key(s) cannot be revoked without unduly burdening consumers and/or authorized electronic device manufacturers.

[0004] An alternative method of digital content protection has been proposed and implemented by an industry organization named the 4C Entity, LLC, which is comprised of International Business Machines Corp., Intel Corp., Matsushita Electric Industries Corp., and Toshiba Corp. The 4C Entity describes their method of content protection in a publication entitled “Content Protection For Recordable Media Specifications” (CPRM), Rev. 0.94, Oct. 18, 2000. CPRM, and its equivalent for pre-recorded media, Content Protection For Pre-Recorded Media (CPPM), define a renewable method for protecting content recorded on a number of physical media types which allows for the revocation or invalidation of any key(s) which may have been compromised. For purposes of this document, all disclosures with respect to CPRM are also understood to apply to CPPM.

[0005] Digital content protection under CPRM generally works as follows, although the details may vary among different implementations. The 4C Entity provides one or more secret Device Key(s) to each device manufacturer for inclusion into each CPRM-compliant device produced.

[0006] As illustrated in FIG. 1, manufacturers of physical media for digital content place a Media Identifier (MID) 102 and the Media Key Block (MKB) 104, generated by the 4C Entity, on each piece of compliant media 100. In one implementation, the physical media 100 may be a rotational disk, such as a DVD. When compliant media 100 is placed within a compliant drive or player/recorder, a secret Media Key is generated by the device using its Device Key(s) and the MKB 104 stored on the media itself. The same secret Media Key is generated regardless of which compliant device is used to access the media. Content 106 stored on the media 100 is encrypted/decrypted by a Content Key from a one-way function of a secret Title Key and the copy control information (CCI) associated with the content. The Title Key is encrypted and stored on the media using a key derived from a one-way function of the Media Key and MID.

[0007] In one implementation, each Device Key has an associated column and row value which relate to the columns and rows of the MKB. For example a Device Key X may be associated with column 4, row 7. For a given device, no two Device Keys have the same associated column value. The number of Device Keys given to each device varies depending on the implementation.

[0008] As illustrated in FIG. 2A, the MKB 200 may be formatted as a sequence of contiguous records 204, hereinafter referred to as Media Key Record(s) (MKR). In order to decrypt the digital content, a compliant device uses its Device Key(s) to calculate a Media Key by processing records of the MKB 200 one-by-one, from first to last.

[0009] Thus, if a particular Device Key becomes compromised in a way that threatens the integrity of the system, the 4C Entity may “revoke” that Device Key by providing media manufacturers with a new MKB to be stored on new media. The new MKB causes devices with the compromised Device Key to calculate a Media Key which is different than that which is computed by compliant devices, thereby preventing the decryption of the digital content stored on that media. The device may still utilize one of its other Device Keys, if available, to calculate the Media Key that decrypts the digital content.

[0010] However, one disadvantage of this security method is the latency caused by reading of the MKB 200. Before playing or accessing the digital content, each compliant device must read the MKB 200 to decrypt the digital content. A MKB 200 can be quite large, typically 3 megabytes (Mbytes) or larger. However, there is no size limit for a MKB per se; the size being merely dictated by the number of Device Keys which have been revoked. In time, the size of a MKB may increase as a result of such revocations. Consequently, the time to process a large MKB 200 can be significant, causing a perceptible nuisance to the user trying to enjoy the content.

[0011] In order to appreciate this problem, some additional background information on the MKB 200 is necessary. As illustrated in FIG. 2A, a MKB 200 is comprised of a contiguous sequence of Media Key Records (MKR) 204.

[0012] The first record, or MKR, in a MKB 200 is called the Verify Media Key Record 202 and is illustrated in FIG. 2B. This record serves an optimizing function, allowing a device to more quickly terminate the decryption process if the correct Media Key has been calculated. That is, if a particular Device Key and MKR yields a Media Key which satisfies the verifying algorithm, found within the Verification Data field 214, then processing of the MKB 200 may stop and the encrypted data may be decrypted.

[0013] Every MKB 200 also has one Calculate Media Key Record (CMKR) 230, illustrated in FIG. 2C. The CMKR 230 is used by the device to calculate a Media Key. The device uses the column and row numbers associated with a particular Device Key to match to the Column field 234 and index to the corresponding Encrypted Key Data field 236, 238, 240, 242, or 244 associated with the row. The Encrypted Key Data field 236, 238, 240, 242, or 244 is employed by the device, in conjunction with its Device Key(s) to calculate a Media Key.

[0014] Additionally, the MKB 200 may contain one or more Conditionally Calculate Media Key Records (CCMKR) 250, which is another type of MKR. As illustrated in FIG. 2D, each CCMKR 250 may have a header comprising encrypted information 270, which must be decrypted before processing, and a plurality of doubly Encrypted Key Data fields 272. Like with CMKRs, the device uses an Encrypted Key Data field 260, 262, 264, 266, or 268 in conjunction with Device Key(s) to calculate and update the Media Key.

[0015] FIG. 3A illustrates the protocol for accessing a conventional Media Key Record 300. For each MKR 300, a device must first seek and transfer a block containing the record header 302. If the Column field 234 (in FIG. 2C) or 274 (FIG. 2D) of the MKR 300 matches the column value associated with Device Key, then the device must index into the Encrypted Key Data field 304 corresponding to the row associated with the Device Key. Obtaining the Encrypted Key Data 304 may require at least one additional seek and read operation. Thus for each record, at least two read and two seek operations may be required; the first seek and read operations for accessing the MKR header 302 and the second seek and read operations for accessing the Encrypted Key Data 304.

[0016] Note that the number of read operations will vary depending on the block size. That is, physical media types may be formatted into different block sizes; the block size being the transfer unit or number of bytes that may be transferred in a single read operation. For DVD-compliant media, the transfer unit is know as known as the Error Control Code (ECC) block; each ECC block comprising 32,768 bytes.

[0017] FIG. 3B illustrates another scenario when accessing a Media Key Record 350. In this example, the Encrypted Key Data field 354 spans two blocks 362 and 364. Hence, an additional read operation is required under this circumstance.

[0018] Accordingly, there is a need for a system to optimize the processing and/or formatting of a Media Key Block so as to minimize user-perceptible delays.

BRIEF DESCRIPTION OF THE DRAWINGS

[0019] FIG. 1 illustrates a Media Key Block as recorded on a physical media.

[0020] FIG. 2A illustrates one implementation of a Media Key Block.

[0021] FIG. 2B illustrates one implementation of a Verify Media Key Record within a MKB.

[0022] FIG. 2C illustrates one implementation of a Calculate Media Key Record within a MKB.

[0023] FIG. 2D illustrates one implementation of a Conditionally Calculate Media Key Record within a MKB.

[0024] FIG. 3A illustrates accessing a first conventional Media Key Record.

[0025] FIG. 3B illustrates accessing a second conventional Media Key Record.

[0026] FIG. 4A illustrates a n exemplary embodiment of a Media Key Block as formatted by the present invention.

[0027] FIG. 4B illustrates an exemplary embodiment of a Column Index Record of the present invention.

[0028] FIG. 5 illustrates accessing the Media Key Record as formatted according to the present invention.

[0029] FIG. 6 illustrates a method to process a Media Key Block according to the present invention.

[0030] FIG. 7 illustrates one way to format a Media Key Block according to the present invention.

DETAILED DESCRIPTION OF THE INVENTION

[0031] According to one embodiment of the present invention, illustrated in FIG. 4A, the MKB 400 is formatted so that the header information for all or some of the Media Key Records is placed together in a single new record 402. This new record is hereinafter referred to as the Column Index Record 402.

[0032] As illustrated in FIG. 4B, the Column Index Record 402 may comprise one or more sets of Media Key Record headers 450 and 452. The information contained within each Media Key Record header 450 and 452 may include a Column field 460 and 462 for each record. Although the Record Type 464, Record Length 466, Revision 468, Column 460, and Generation 470 fields are shown in this embodiment, this is not a limitation upon the present invention. In some embodiments of the invention, some of these fields may not be present in the Column Index Record 402. Additionally, the Column Index Record 402 may comprise fields not shown in FIG. 4B.

[0033] The Column Index Record 402 may be stored anywhere within or outside the MKB 400. According to one embodiment, the Column Index Record 402 is placed just before the Media Key Records 404 in the MKB 400. In one embodiment, the Column Index Record 402 is placed just before the Verify Media Key Record 406.

[0034] According to one embodiment of the invention, illustrated in FIG. 5, a device processing the newly formatted Media Key Block 400 (FIG. 4A) begins by accessing the Column Index Record 502 using a read operation. Depending on the size of the Column Index Record 502 and transfer unit or block size of the media type, the read operation may be accomplished in a single read operation. In one embodiment, this read operation is not a new requirement since it is already required to read the Verify Media Key Record 406 (FIG. 4A) located at the beginning of the Media Key Block 400. That is, the device may read the Column Index Record 502 and Verify Media Key Record 406, both located within a single transfer unit or block 506 of the physical media type, in a single read operation.

[0035] Having read the Column Index Record 502, the device may examine all of the record headers contained therein. According to one embodiment, with each header in the Column Index Record 502, the device may be able to determine, up front, whether it needs to access the Decrypt Key Data fields 504 from the corresponding Media Key Record. Such determination may be made by comparing the associated column value of the Device Key for the device with the Column field 460 (FIG. 4B) of each header. If a match is found, an offset to read the Encrypted Key Data field 504 may be determined by using the associated row value of the Device Key.

[0036] Through the use of the Column Index Record 502, which in one embodiment may be read just once, the device may avoid having to seek for and read the header of each Media Key Record. Thus, where two seek and read operations have usually been required to read each Media Key Record, the Column Index Record 502 may enable accessing this same data in fewer operations. In one embodiment, the Column Index Record 502 may permit accessing a Media Key Record in just half as many seek and read operations; that is, one seek and one read operation.

[0037] According to one embodiment of this invention, the Media Key Records 404 (FIG. 4A) may have their headers removed. That is, once the Column Index Record 402 (FIG. 4B) contains the Media Key Record headers, the Media Key Records 404 may be reduced in size by removing their headers. In another embodiment, the Media Key Records 404 may contain part or all of their header information.

[0038] Additionally, the Media Key Block 400 (FIG. 4A) may be formatted to guarantee that one or more Media Key Records and/or one or more fields of a Media Key Record(s) aligns or fits completely within a single transfer unit or block on a physical media type. For example, as illustrated in FIG. 5, the Encrypted Key Data field 504 may be aligned to fit within a single transfer unit or block 508. Such alignment may be accomplished in a number of ways. In one embodiment, this result may be achieved by modifying the Record Length field as necessary. This may also entail appending bytes to one or more Media Key Records.

[0039] By formatting the Media Key Block in this manner a single seek and read operation may be employed where before one seek and two read operations may have been necessary. This alignment technique may be further combined with the new Column Index Record 402 (FIG. 4A) formatting technique described above to achieve faster processing of the Media Key Block 400 (FIG. 4A).

[0040] In one implementation, the newly formatted Media Key Block is stored on DVD-compliant media type and comprises 16 columns, with the size of each Encrypted Key Data field being 8 bytes. Accordingly, in one embodiment of the present invention, all of the Media Key Records are adjusted, using the Record Length field, to be multiples of 8 bytes long. This ensures that all of the 8-byte Encrypted Key Data fields fall completely within one media block; each DVD ECC block being 32,768-bytes long.

[0041] As an example of the savings in processing time of a Media Key Block that may be achieved by the present invention, consider a simplified example of a DVD player with a 1×-speed reading mechanism, and an estimated worst-case time to read an ECC block of 75 milliseconds (ms), ignoring seek times. This includes approximately 50 ms for rotation of the physical media and an approximate 25 ms transfer time. Using the new format described above, the worst-case total time for all reads needed to process the Media Key Block is 75 ms+16×75 ms=1.3 seconds. That's 75 ms for reading the Column Index Record and Verify Media Key Record (1 rotation & 1 read operation) and 16 columns times 75 ms per Media Key Record Key Data field with no overlapping since the fields are aligned (1 rotation & 1 read operation).

[0042] Without the present invention, the worst-case processing time would be 75 ms+16×75 ms+16×100 ms=2.9 seconds. That's 75 ms for reading the Verify Media Key Record (1 rotation & 1 read operation), 16 columns times 75 ms per Media Key Record header (1 rotation & 1 read operation), and 16 columns times 100 ms per Media Key Record Key Data field overlapping two blocks (1 rotation & 2 read operations).

[0043] Alignment of the Media Key Records with the block size will vary depending on the media type. While a block size of 32,768 bytes has been used to illustrate the invention on a DVD media, this is not a limitation upon the invention. The concept of aligning the Media Key Record fields within a single block is independent of the block size.

[0044] The Column Index Record and/or the Media Key Record alignment techniques, alone or in combination, also enable the use of larger Media Key Blocks than would otherwise be possible. That is, without this invention, as the Media Key Block comprises more Media Key Records, the user-perceptible delays may grow to unacceptable levels. However, as a result of the faster processing that may be achieved by the present invention, larger Media Key Blocks may be employed while minimizing the user-perceptible delay.

[0045] One consideration in minimizing the user-perceptible delay is the size and layout of the specific blocks comprising the Media Key Block. For instance, for a typical DVD reader, jumps of over 100 tracks may require a longer linear head seek, whereas jumping less than 100 tracks requires an optical head seek which takes a significantly shorter time. Near the inside of a disk, 100 tracks comprises about 100 tracks×2 blocks/track×32,768 bytes/block=6 Megabytes. Thus, the overall Media Key Block size can be chosen to avoid the longer linear seeks.

[0046] FIG. 6 illustrates one method of processing a Media Key Block according to the present invention. According to one embodiment, a device processing the newly formatted Media Key Block would seek for the Column Index Record on any given media, and read it 600. The terms “seek” and “read” are used herein to describe seek and read operations on a particular media type which may hold part or all of the Media Key Records. According to one embodiment, the device may store the Column Index Record in memory for later access. Using the Column Index Record, the device may search for a Media Key Record header which matches one of its Device Keys 602. In one embodiment of the invention, this step may entail matching the Column field of a Media Key Record header to the column number associated with one or more of its Device Keys. Note that in one embodiment, a device may always have at least one Device Key that matches the Calculate Media Key Record.

[0047] Once a particular Media Key Record has been identified, the device may then seek and read the Media Key Record 604. In one embodiment, the device may access only the Encrypted Key Data field corresponding to the row number associated with the Device Key. The device may index into this field by using the row number and known size of the fields to calculate an indexing point.

[0048] Once the device has obtained the Encrypted Key Data field, it may then calculate a Media Key 606 using the Encrypted Key Data and its Device Key. It may then check whether the Media Key is valid 608 by using the verifying algorithm in the Verify Media Key Record which it may have been read at the same time as the Column Index Record. If a valid Media Key is found, then the device may stop processing the Media Key Block 616, and use the Media Key to decrypt encrypted content 618.

[0049] If the Media Key is not valid 608, then the device may search the Column Index Record for the next Media Key Record header which corresponds to one or more of its Device Keys 610. If such record is found 612, the device may then seek and read the Media Key Record 614. According to one embodiment, the device may only seek and read the Encrypted Key Data field for the Media Key Record of interest. The device may then proceed to calculate a Media Key 614 as before. This process may be repeated until a valid Media Key is found or no more Media Key Records are available.

[0050] If no corresponding Media Key Record is found or no more Media Key Records are available, then the device may terminate processing of the MKB 620. In one embodiment, failure to obtain a valid Media Key may prevent a device from being able to decrypt the encrypted data.

[0051] The present invention may also be embodied in a signal carrying instructions to process the Media Key Block as described above. Additionally, the present invention may be embodied in a machine-readable medium, in the form of instructions to carry out the steps described above.

[0052] FIG. 7 illustrates one process of formatting a Media Key Block according the present invention. Generally, a conventional Media Key Block may be parsed to collect header information for its Media Key Records. The header information for the Media Key Records is arranged in a new record 700. The new record may be stored or recorded onto the same media as the Media Key Block 702. Additionally, one or more Media Key Records and/or one or more fields of a Media Key Record in the Media Key Block may be adjusted to fit within a single transfer unit or block 704. According to one embodiment, the Record Length field may be adjusted to guarantee that the record fits within a single block. In another embodiment, this adjustment may comprise appending additional bits to the record or to a field within the record.

[0053] The present invention may be embodied in a device, system, computer, media, and/or software program. Additionally, the invention may also be practiced by transmitting to a device one or more Device Keys, the newly formatted Media Key Block, including the Column Index Record, and the encrypted content. This transmission may take place over the airwaves.

[0054] Additionally, while the invention has been described with reference to a Media Key Block and its associated components, it should be clearly understood that the present invention may be practiced on other types of applications.

[0055] While the invention has been described and illustrated in detail, it is to be clearly understood that this is intended by way of illustration and example only and is not to be taken by way of limitation, the spirit and scope of this invention being limited only by the terms of the following claims.

Claims

1. A method comprising: formatting a media key block to include a first record containing header information for media key records; and adjusting the length of the media key records to guarantee that individual key data in each media key record is contained in a single data transfer unit of the given media.

2. The method of claim 1, wherein media key record headers contain a length field.

3. The method of claim 1, wherein media key record headers include a column field.

4. The method of claim 1, further comprising: storing the media key block in a physical media.

5. The method of claim 4, wherein the physical media is a Digital Versatile Disk (DVD)—compliant media.

6. The method of claim 4, wherein the physical media is logically divided into at least one block.

7. The method of claim 1, wherein the first record containing header information for media key records is the first record of the media key block.

8. The method of claim 1, wherein adjusting the length comprises changing the value in the length field of at least one media key record.

9. The method of claim 1, wherein adjusting the length of the media key records to guarantee that individual key data in each media key record is contained in a single data transfer unit comprises aligning one or more fields to guarantee that they are contained within a single data transfer unit.

10. The method of claim 1, wherein adjusting the length of the media key records to guarantee that individual key data in each media key record is contained in a single data transfer unit further comprises guaranteeing that each media key record is contained within a single data transfer unit.

11. A method comprising: reading a first record containing header information for one or more media key records; and accessing at least one of the one or more media key records.

12. The method of claim 11, further comprising: determining which of the one or more media key records should be accessed based on the header information found in the first record.

13. The method of claim 11, wherein the accessing at least one of the one or more media key records comprises: seeking the physical location of the at least one media key record on a physical media.

14. The method of claim 11, wherein the accessing at least one of the one or more media key record comprises: reading the at least one media key record from a physical media.

15. The method of claim 11, further comprising: calculating a media key from the information in the at least one media key record.

16. The method of claim 15, wherein only the necessary records to calculate the media key are accessed.

17. A machine-readable medium comprising at least one instruction to access and process a media key block which when executed by a processor, causes the processor to perform operations comprising: reading a first record of the media key block containing header information for one or more media key records; and accessing at least one of the one ore more media key records.

18. The machine-readable medium of claim 17, further comprising: determining which of the one or more media key records should be accessed based on the header information found in the first record.

19. The machine-readable medium of claim 17, wherein accessing at least one of the one or more media key records comprises: seeking the physical location of the at least one media key record.

20. The machine-readable medium of claim 19, further comprising: calculating a media key from the information in the at least one media key record.

21. The machine-readable medium of claim 20, further comprising: verifying the calculated media key to determine if a match has been found.

22. The machine-readable medium of claim 20, wherein calculating the media key, only the necessary media key records are accessed.

23. A device comprising; a machine-readable physical media; a media key block, including one or more media key records, contained within the physical media; and a first record, within the physical media, including header information for at least one of the one or more media key records.

24. The device of claim 23, wherein the machine-readable media is a Digital Versatile Disk (DVD)—compliant media.

25. The device of claim 23, wherein the machine-readable physical media is a rotational media.

26. The device of claim 23, further comprising: digital data contained within the physical media.

27. The device of claim 26, wherein the digital data contained within the physical media is encrypted.

28. The device of claim 26, wherein the digital data contained within the physical media can only be decrypted by calculating a media key from data within the at least one of the one or more media key records.

29. The device of claim 23, wherein the physical media is logically divided into at least one block.

30. The device of claim 29, wherein each of the at least one of the one or more media key records includes data fields, each data field contained within a single data transfer unit for the given media.