SECURE IDENTIFICATION OF MUSIC FILES

• US 20100312810A1
• Filed: 06/09/2009
• Published: 12/09/2010
• Est. Priority Date: 06/09/2009
• Status: Abandoned Application

• Current Assignee: Universal Music Group Incorporated (Universal Music Group NV)
• Original Assignee: Universal Music Group Incorporated (Universal Music Group NV)
• Inventors: Watt, Simon, Radbel, Dmitry, Horton, Christopher
• Application Number:
  US12/481,355
• Publication Number:
  US 20100312810A1
• Time in Patent Office: Days
• US Class Current: 707/912
• CPC Class Codes: G06F 16/68 Retrieval characterised by using metadata, e.g. metadata not derived from the content or metadata generated manually
• CPC Class Codes: G06F 16/907 Retrieval characterised by using metadata, e.g. metadata not derived from the content or metadata generated manually
• CPC Class Codes: G06F 21/10 Protecting distributed programs or content, e.g. vending or licensing of copyrighted material protection in video systems or pay television H04N7/16 ; Digital rights management [DRM]
• CPC Class Codes: G06F 21/16 Program or content traceability, e.g. by watermarking

Abstract

Digital content files may include media content, metadata uniquely identifying a transaction in which the content file was obtained, and a digital signature of at least a portion of the metadata. The metadata may include a distributor ID, a date and time of the transaction, an asset ID, a secure hash of the media content, a nonce, and one of a user ID, uniquely identifying a user who obtained the content file in the transaction, and a transaction ID uniquely identifying the transaction.

Claims

1-22. -22. (canceled)

23. A method of auditing a distributor of digital content, comprising:

receiving, with a digital content audit server, a content file obtained from a content distributor through a transaction, the content file containing metadata uniquely identifying the transaction and a digital signature of at least a portion of the metadata;

receiving, with the digital content audit server, from the content distributor a list of transactions for content files entered into by the content distributor;

searching, with the digital content audit server, the list of transactions for the transaction identified by the metadata; and

responsive to an indication that the transaction was not found, recording, with the digital content audit server, an indication that the transaction was not reported.

24. The method of claim 23, further comprising:

receiving, with the digital content audit server, a second content file obtained from the content distributor through a second transaction, the second content file containing second metadata uniquely identifying the second transaction and a second digital signature of at least a portion of the second metadata;

comparing, with the digital content audit server, the metadata to the second metadata; and

responsive to a determination that a portion of the metadata uniquely identifying the transaction is identical to a portion of the second metadata uniquely identifying the second transaction, recording, with the digital content audit server, an indication that the content distributor is not property identifying transactions.

25. The method of claim 23, wherein the metadata includes:

a distributor identifier;

a date and time of the transaction;

an asset identifier;

a secure hash generated from a non-metadata portion of the content file;

a nonce, randomly generated at the time of the transaction; and

one of a user identifier, uniquely identifying the user, and a transaction identifier, uniquely identifying the transaction.

26. The method of claim 23, wherein:

the content file is an MP3 file; and

the metadata and the digital signature are embedded in a PRIV ID3 tag.

27. The method of claim 23, wherein the metadata and the digital signature are in XML form.

28. A digital content audit server, comprising:

a file load component configured to receive a content file obtained from a content distributor through a transaction, the content file containing metadata uniquely identifying the transaction and a digital signature of at least a portion of the metadata;

a transaction report component configured to receive from the content distributor a list of transactions for content files entered into by the content distributor; and

a analysis component configured to search the list of transactions for the transaction identified by the metadata, and, responsive to an indication that the transaction was not found, record an indication that the audit failed.

29. The server of claim 28, wherein:

the file load component is further configured to receive a second content file obtained from the content distributor through a second transaction, the second content file containing second metadata uniquely identifying the second transaction and a second digital signature of at least a portion of the second metadata; and

the analysis component is further configured to compare the metadata to the second metadata, and, responsive to a determination that a portion of the metadata uniquely identifying the transaction is identical to a portion of the second metadata uniquely identifying the second transaction, record an indication that the content distributor is not property identifying transactions.

30. The server of claim 28, wherein the metadata includes:

a distributor identifier;

a date and time of the transaction;

an asset identifier;

a secure hash generated from a non-metadata portion of the content file;

a nonce, randomly generated at the time of the transaction; and

one of a user identifier, uniquely identifying the user, and a transaction identifier, uniquely identifying the transaction.

31. The server of claim 28, wherein:

the content file is an MP3 file; and

the metadata and the digital signature are embedded in a PRIV ID3 tag.

32. The server of claim 28, wherein the metadata and the digital signature are in XML form.

33. A method of providing access to bonus content, comprising:

receiving, with an access control server, metadata and a digital signature which are associated with a content file obtained from a content distributor through a transaction, wherein the metadata uniquely identifies the transaction, and wherein the digital signature is made from at least a portion of the metadata;

validating, with the access control server, the metadata and the digital signature;

determining, with the access control server, whether access to bonus content has been requested more than a predetermined number of times using the content file, where the content file is identified using the metadata; and

responsive to an indication that the digital signature and the metadata are valid and an indication that access to the bonus content has been requested less than the predetermined number of times using the content file, allowing access to the bonus content, with the access control server.

34. The method of claim 33, wherein the metadata includes:

a distributor identifier;

a date and time of the transaction;

a track identifier;

a secure hash generated from a non-metadata portion of the content file;

a nonce, randomly generated at the time of the transaction; and

one of a user identifier, uniquely identifying the user, and a transaction identifier, uniquely identifying the transaction.

35. The method of claim 33, wherein:

the content file is an MP3 file; and

the metadata and the digital signature are embedded in a PRIV ID3 tag.

36. The method of claim 33, wherein the metadata and the digital signature are in XML form.

37. The method of claim 33, wherein the predetermined number is 1.

38. The method of claim 33, wherein determining whether access to the bonus content has been requested more than a predetermined number of times using the content file, comprises searching for the metadata in a list of metadata used to request access to the bonus content.

39. The method of claim 33, wherein the metadata and the digital signature are embedded in the content file.

40. The method of claim 33, wherein allowing access to the bonus content further comprises issuing an access token configured to allow access to the bonus content.

41. An access control server for providing access to bonus content, comprising:

a request component configured to receive metadata and a digital signature which are associated with a content file obtained from a content distributor through a transaction, wherein the metadata uniquely identifies the transaction, and wherein the digital signature is made from at least a portion of the metadata;

a validation component configured to validate the metadata and the digital signature, and configured to determine whether access to bonus content has been requested more than a predetermined number of times using the content file, where the content file is identified using the metadata; and

an access component configured to, responsive to an indication that digital signature and the metadata are valid and an indication that access to the bonus content has been requested less than the predetermined number of times using the content file, allow access to the bonus content.

42. The server of claim 41, wherein the metadata includes:

a distributor identifier;

a date and time of the transaction;

an asset identifier;

a secure hash generated from a non-metadata portion of the content file;

a nonce, randomly generated at the time of the transaction; and

one of a user identifier, uniquely identifying the user, and a transaction identifier, uniquely identifying the transaction.

43. The server of claim 41, wherein:

the content file is an MP3 file; and

the metadata and the digital signature are embedded in a PRIV ID3 tag.

44. The server of claim 41, wherein the metadata and the digital signature are in XML form.

45. The system of claim 41, wherein the predetermined number is 1.

46. The server of claim 41, wherein the validation component is further configured to determine whether access to the bonus content has been requested more than a predetermined number of times using the content file by searching for the metadata in a list of metadata used to request access to the bonus content.

47. The server of claim 41, wherein the metadata and the digital signature are embedded in the content file.

48. The server of claim 41, wherein the access component is further configured allow access to the bonus content by issuing an access token configured to allow access to the bonus content.

49. A method of rendering media content based on authenticated metadata, comprising:

receiving, with a rendering device, a content file containing metadata and a digital signature of at least a portion of the metadata, wherein the metadata includes a secure hash of media content stored in the content file;

identifying, with the rendering device, information in the metadata usable to control rendering of the media content;

determining, with the rendering device, whether the metadata is the same as original metadata used to create the digital signature;

determining, with the rendering device, whether the media content is the same as original media content used to create the secure hash; and

responsive to an indication that the metadata is the same as the original metadata and the media content is the same as the original media content, rendering, with the rendering device, the media content according to the information.

50. The method of claim 49, wherein the metadata includes:

a distributor identifier;

a date and time of the transaction;

an asset identifier;

a nonce, randomly generated at the time of the transaction; and

one of a user identifier, uniquely identifying the user, and a transaction identifier, uniquely identifying the transaction.

51. The method of claim 49, wherein:

the content file is an MP3 file; and

the metadata and the digital signature are embedded in a PRIV ID3 tag.

52. The method of claim 49, wherein the metadata and the digital signature are in XML form.

53. A media rendering system, comprising:

a file load component configured to receive a content file containing metadata and a digital signature of at least a portion of the metadata, wherein the metadata includes a secure hash of media content stored in the content file;

a metadata extraction component configured to identify information in the metadata usable to control rendering of the media content;

an authentication component configured to determine whether the metadata is the same as original metadata used to create the digital signature, and configured to determine whether the media content is the same as original media content used to create the secure hash; and

a rendering component configured to, responsive to an indication that the metadata is the same as the original metadata and the media content is the same as the original media content, render with the rendering device, the media content according to the information.

54. The system of claim 53, wherein the metadata includes:

a distributor identifier;

a date and time of the transaction;

an asset identifier;

a nonce, randomly generated at the time of the transaction; and

one of a user identifier, uniquely identifying the user, and a transaction identifier, uniquely identifying the transaction.

55. The server of claim 53, wherein:

the content file is an MP3 file; and

the metadata and the digital signature are embedded in a PRIV ID3 tag.

56. The server of claim 53, wherein the metadata and the digital signature are in XML form.

57-58. -58. (canceled)