Method and system for identification of music industry releases and licenses

• US 20030200216A1
• Filed: 01/16/2003
• Published: 10/23/2003
• Est. Priority Date: 01/22/2002
• Status: Abandoned Application

• Current Assignee: Recording Industry Association of America
• Original Assignee: Recording Industry Association of America
• Inventors: Hayes, Michael Anthony, Hill, Keith Ryan
• Application Number:
  US10/345,411
• Publication Number:
  US 20030200216A1
• Time in Patent Office: Days
• US Class Current: 707/9
• 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/64 Protecting data integrity, e.g. using checksums, certificates or signatures

Abstract

A memory stores a data structure that comprises release identifier information relating to identification, validation, authorization, and/or use of data associated with releases and intellectual property rights associated with the releases. The data structure further includes a first data element that includes an issuer code, a second data element that includes an intellectual property bundle number, and a third data element that includes a check character. Another memory, or alternatively the same memory, stores a data structure that includes license identifier information relating to identification, validation, authorization, and/or use of data associated with licenses and intellectual property rights associated with the data. The data structure further includes a first data element that includes an issuer code, a second data element that includes a license reference, and a third data element that includes a check character.

Claims

1. A memory storing a data structure that comprises release identifier information relating to at least one of identification, validation, authorization, and use of data comprising at least one of a data arrangement, a data collection, and a data set, and at least one intellectual property right associated with the data, the data structure being retrieved from the memory responsive to instructions being implemented by at least one of a data processor and a computer, the data structure comprising:

a first data element comprising an issuer code;

a second data element comprising an intellectual property bundle number; and

a third data element comprising a check character, wherein the first, second, and third data elements are used in the at least one of the identification, validation, authorization, and use of the data.

2. The memory of claim 1, wherein the issuer code uniquely identifies an entity responsible for issuing a release identifier.

3. The memory of claim 1, wherein the intellectual property bundle number is allocated uniquely by an entity that has been assigned the issuer code to identify a collection of intellectual property assets and accompanying metadata associated with a release.

4. The memory of claim 1, wherein the check character is used to facilitate correct entry of a release identifier into the memory.

5. The memory of claim 1, wherein the data structure further comprises a fourth data element comprising a delivery attribute extension.

6. The memory of claim 5, wherein the delivery attribute extension is allocated uniquely by an entity that has been assigned the issuer code to distinguish between different versions of a release.

7. The memory of claim 1, wherein the data structure further comprises a fifth data element comprising a release identifier scheme.

8. The memory of claim 7, wherein the release identifier scheme uniquely identifies an identification scheme for a release.

9. A memory storing a data structure that comprises license identifier information relating to at least one of identification, validation, authorization, and use of data comprising at least one of a data arrangement, a data collection, and a data set, and at least one intellectual property right associated with the data, the data structure being retrieved from the memory responsive to instructions being implemented by at least one of a data processor and a computer, the data structure comprising:

a first data element comprising an issuer code;

a second data element comprising a license reference; and

a third data element comprising a check character, wherein the first, second, and third data elements are used in the at least one of the identification, validation, authorization, and use of the data.

10. The memory of claim 9, wherein the issuer code uniquely identifies an entity responsible for issuing a license identifier.

11. The memory of claim 9, wherein the license reference is allocated uniquely by an entity that has been assigned the issuer code to identify a license and accompanying metadata associated with the license.

12. The memory of claim 9, wherein the check character is used to facilitate correct entry of a release identifier into the memory.

13. The memory of claim 9, wherein the data structure further comprises a fourth data element comprising a society auxiliary extension.

14. The memory of claim 13, wherein the society auxiliary extension is allocated uniquely by an entity that has been assigned the issuer code to distinguish between difference versions of a license.

15. The memory of claim 9, the data structure further comprising a fifth data element comprising an identifier scheme.

16. The memory of claim 15, wherein the identifier scheme uniquely identifies an identification scheme for a license.

17. A memory storing a data structure that comprises release identifier information relating to at least one of identification, validation, authorization, and use of data comprising at least one of a data arrangement, a data collection, and a data set, and at least one intellectual property right associated with the data, the data structure being retrieved from the memory responsive to instructions being implemented by at least one of a data processor and a computer, the data structure comprising:

a first data element comprising an identifier scheme, the identifier scheme comprising two valid characters;

a second data element comprising an issuer code, the issuer code comprising five valid characters, wherein the first data element precedes the second data element;

a third data element comprising an intellectual property bundle number, the intellectual property bundle comprising ten valid characters, wherein the second data element precedes the third data element, wherein a valid character is one of any upper case letter of the Roman alphabet, excluding “

I” and

“

O”

, and any Arabic digit, and wherein the valid character is defined using ASCII codes; and

a fourth data element comprising a check character, the check character comprising one character comprising one of any upper case letter of the Roman alphabet and any Arabic digit, wherein the character is defined using ASCII codes, and wherein the third data element precedes the fourth data element.

18. The memory of claim 17, wherein the first, second, third, and fourth data elements are separated by a hyphen.

19. A memory storing a data structure that comprises release identifier information relating to at least one of identification, validation, authorization, and use of data comprising at least one of a data arrangement, a data collection, and a data set, and at least one intellectual property right associated with the data, the data structure being retrieved from the memory responsive to instructions being implemented by at least one of a data processor and a computer, the data structure comprising:

a first data element comprising an identifier scheme, the identifier scheme comprising two valid characters;

a second data element comprising an issuer code, the issuer code comprising five valid characters, wherein the first data element precedes the second data element;

a third data element comprising an intellectual property bundle number, the intellectual property bundle comprising seven valid characters, wherein the second data element precedes the third data element;

a fourth data element comprising a delivery attribute extension, the delivery attribute extension comprising three valid characters, wherein the third data element precedes the fourth data element, wherein a valid character is one of any upper case letter of the Roman alphabet, excluding “

I” and

“

O”

, and any Arabic digit, and wherein the valid character is defined using ASCII codes; and

a fifth data element comprising a check character, the check character comprising one character comprising one of any upper case letter of the Roman alphabet and any Arabic digit, wherein the character is defined using ASCII codes, and wherein the fourth data element precedes the fifth data element.

20. The memory of claim 19, wherein the first, second, third, fourth, and fifth data elements are separated by a hyphen.

21. A memory storing a data structure that comprises license identifier information relating to at least one of identification, validation, authorization, and use of data comprising at least one of a data arrangement, a data collection, and a data set, and at least one intellectual property right associated with the data, the data structure being retrieved from the memory responsive to instructions being implemented by at least one of a data processor and a computer, the data structure comprising:

a first data element comprising an identifier scheme, the identifier scheme comprising two valid characters;

a second data element comprising an issuer code, the issuer code comprising five valid characters, wherein the first data element precedes the second data element;

a third data element comprising a license reference, the license reference comprising ten valid characters, wherein the second data element precedes the third data element, wherein the third data element precedes the fourth data element, wherein a valid character is one of any upper case letter of the Roman alphabet, excluding “

I” and

“

O”

, and any Arabic digit, and wherein the valid character is defined using ASCII codes; and

a fourth data element comprising a check character, the check character comprising one character comprising one of any upper case letter of the Roman alphabet and any Arabic digit, wherein the character is defined using ASCII codes, and wherein the third data element precedes the fourth data element.

23. A memory storing a data structure that comprises license identifier information relating to at least one of identification, validation, authorization, and use of data comprising at least one of a data arrangement, a data collection, and a data set, and at least one intellectual property right associated with the data, the data structure being retrieved from the memory responsive to instructions being implemented by at least one of a data processor and a computer, the data structure comprising:

a first data element comprising an identifier scheme, the identifier scheme comprising two valid characters;

a second data element comprising an issuer code, the issuer code comprising five valid characters, wherein the first data element precedes the second data element;

a third data element comprising a license reference, the license reference comprising seven valid characters, wherein the second data element precedes the third data element;

a fourth data element comprising a society auxiliary extension, the society auxiliary extension comprising three valid characters, wherein the third data element precedes the fourth data element, wherein a valid character is one of any upper case letter of the Roman alphabet, excluding “

I” and

“

O”

, and any Arabic digit, and wherein the valid character is defined using ASCII codes; and

a fifth data element comprising a check character, the check character comprising one character comprising one of any upper case letter of the Roman alphabet and any Arabic digit, wherein the character is defined using ASCII codes, and wherein the fourth data element precedes the fifth data element.

24. The memory of claim 23, wherein the first, second, third, fourth, and fifth data elements are separated by a hyphen.

25. A method of managing identification and description of at least one release, comprising:

determining the contents of the at least one release;

obtaining at least one release identifier associated with a unique one of the at least one release;

obtaining musical work details associated with the contents of the at least one release; and

compiling at least one label copy, wherein the at least one label copy comprises the contents of the at least one release, the at least one release identifier, and the musical work details.

22. The memory of claim 25, wherein the first, second, third, and fourth data elements are separated by a hyphen.

26. The method of claim 25, wherein obtaining the at least one release identifier further comprises obtaining at least one issuer code, wherein the issue code is issued by a central registration service and is assigned to a unique one of at least one issuing entity, which issues the at least one release.

27. The method of claim 25, wherein obtaining the at least one release identifier further comprises obtaining at least one intellectual property bundle number, which is allocated uniquely by an entity that has been assigned an issuer code to identify a collection of intellectual property assets and accompanying metadata associated with the at least one release.

28. The method of claim 25, wherein obtaining the at least one release identifier further comprises calculating a check character.

29. The method of claim 25, wherein obtaining the at least one release identifier further comprises obtaining a delivery attribute extension, which is allocated uniquely by an entity that has been assigned an issuer code to distinguish between different versions of the at least one release.

30. The method of claim 25, wherein obtaining the at least one release identifier further comprises obtaining a release identifier scheme, which uniquely identifies an identification scheme for the at least one release.

31. A method of managing identification and description of at least one license associated with at least one release, comprising:

notifying at least one licensing entity of the at least one release;

determining the terms of the at least one license, wherein the terms are negotiated between the at least one licensing entity and at least one issuer entity that issues the at least one release; and

generating at least one license identifier associated with a unique one of the at least one license.

32. The method of claim 31, wherein obtaining the at least one license identifier further comprises generating at least one issuer code, wherein the issuer code is issued by a central registration service and is assigned to a unique one of the at least one licensing entity, which issues the at least one license.

33. The method of claim 31, wherein obtaining the at least one license identifier further comprises obtaining at least one license reference, which is allocated uniquely by a unique one of the at least one licensing entity that has been assigned an issuer code to identify the at least one license and accompanying metadata associated with the at least one license.

34. The method of claim 31, wherein obtaining the at least one license identifier further comprises calculating a check character.

35. The method of claim 31, wherein generating the at least one license identifier further comprises obtaining a society auxiliary extension, which is allocated uniquely by one of the at least one licensing entity that has been assigned an issuer code to distinguish between different versions of the at least one license.

36. The method of claim 31, wherein obtaining the at least one license identifier further comprises obtaining a license identifier scheme, which uniquely identifies an identification scheme for the at least one license.

37. The method of claim 31, wherein there is a one-to-many relationship between the at least one license and the at least one release such that the at least one license identified by the at least one license identifier is associated with a plurality of releases.

38. The method of claim 31, wherein there is a one-to-many relationship between the at least one license and the at least one release such that the at least one release is associated with a plurality of licenses identified by the at least one license identifier.

39. A method of administering a release identifier, comprising:

issuing at least one issuer code, wherein the at least one issuer code is issued by a central registration service and is assigned to a unique one of at least one issuing entity; and

issuing at least one release having a release identifier comprising the at least one issuer code, wherein the at least one release is issued by the unique one of the at least one issuing entity.

40. A method of administering a license identifier, comprising:

issuing at least one issuer code, wherein the at least one issuer code is issued by a central registration service and is assigned to a unique one of at least one licensing entity; and

issuing at least one license having a license identifier comprising the at least one issuer code, wherein the at least one license is issued by the unique one of the at least one licensing entity.

41. A method of exchanging information regarding at least one release, comprising:

converting, by a first entity, a release identifier and metadata associated with the at least one release from a first proprietary format associated with the first entity into a standard format, wherein the standard format comprises a standard metadata schema;

mapping, by the first entity, the release identifier and the metadata associated with the at least one release into appropriate fields within the standard metadata schema;

transmitting the release identifier and metadata from the first entity to a second entity; and

converting, by the second entity, the release identifier and the metadata associated with the at least one release from the standard format into a second proprietary format associated with the second entity, wherein the release identifier and the metadata identify and describe the at least one release.

42. A method of exchanging information regarding at least one license, comprising:

converting, by a first entity, a license identifier and metadata associated with the at least one license from a first proprietary format associated with the first entity into a standard format, wherein the standard format comprises a standard metadata schema;

mapping, by the first entity, the license identifier and the metadata associated with the at least one license into appropriate fields within the standard metadata schema;

transmitting the license identifier and metadata from the first entity to a second entity; and

converting, by the second entity, the license identifier and the metadata associated with the at least one license from the standard format into a second proprietary format associated with the second entity, wherein the license identifier and the metadata identify and describe the at least one license.