Abstract:
A method for digital rights management for a copyright work that is copied from device to device from among a plurality of devices, some of which are parent devices and some of which are child devices, and wherein a child device may be registered with a parent device, including copying a digital work from a parent device, P 1 , to a child device, C 1 , registered with device P 1 , the digital work encapsulating digital rights management (DRM) data that serves to permit full access to the digital work by parent device P 1 , and to deny access to the digital work by devices other than device P 1 , modifying the DRM data in the copy of the digital work within device C 1 , so as to permit full access to the digital work, for a prescribed time period, by device C 1  and by child devices other than device C 1 , inserting auxiliary DRM data in the copy of the digital work within device C 1 , so as to permit full access to the digital work by device C 1 , and so as to permit limited access to the digital work by child devices other than device C 1 , if the digital work is copied from device C 1  to a parent device P 2  other than device P 1 , then modifying the DRM data in the copy of the digital work within device P 2 , so as to permit limited access to the digital work by device P 2 , and removing the auxiliary DRM data in the copy of the digital work within device P 2 , and if the digital work is copied from device C 1  to a child device C 2  other than device C 1 , then modifying the auxiliary DRM data in the copy of the digital work within device C 2 , so as to permit limited access to the digital work by child device C 2  and so as to permit limited access to the digital work by child devices other than device C 2 . A system and a computer-readable storage medium are also described and claimed.

Description:
CROSS REFERENCES TO RELATED APPLICATIONS 
       [0001]    The present application claims priority from and is a divisional application of U.S. patent application Ser. No. 11/261,687, filed Oct. 28, 2005, published as U.S. Patent Publication No. 2006/0107330 A1, entitled “Method and System for Tracking and Managing Rights for Digital Music,” which is a continuation-in-part of assignee&#39;s pending application U.S. Ser. No. 10/893,473, filed on Jul. 16, 2004, published as U.S. Patent Publication No. 2005/0065624 A1, entitled “Method and System for Managing Rights for Digital Music,” which is a continuation-in-part of assignee&#39;s pending application U.S. Ser. No. 10/829,581, filed on Apr. 21, 2004, published as U.S. Patent Publication No. 2004/0267390 A1, entitled “Portable Music Player and Transmitter,” which is a continuation-in-part of assignee&#39;s issued application U.S. patent application Ser. No. 10/336,443, filed on Jan. 2, 2003, now U.S. Pat. No. 7,191,193, entitled “Automatic Digital Music Library Builder.” 
     
    
     FIELD 
       [0002]    Embodiments of the present invention relate to rights management for use and transfer of digital music recordings. 
       BACKGROUND 
       [0003]    Consumers are generally aware to some extent of copyright laws concerning digital recordings, but there are no automatic features in place to assist consumers in abiding with them. For example, a consumer who purchases a song on a CD, or through a subscription with an Internet music sharing service such as Napster, generally does not know if he is permitted to make personal copies of the song for himself, on one or more of his computers, or on one or more CDs, or on one or more MP3 players. 
         [0004]    Digital rights management (DRM) technology addresses this concern by encapsulating a DRM wrapper within digital songs. The DRM wrapper, which is generally encrypted, specifies whether or not a specific device has the necessary rights to play a specific song. Hardware or software within the player then enables or disables playing of the song accordingly. Generally, DRM systems only enable playing of a song on a device if the owner of the device has purchased a license for the song. If the owner of the device has not purchased a license for the song and wishes to do so, and if the device is connected via a computer network to a licensing authority, referred to as a “clearing house,” then the owner may purchase a license from the clearing house, in which case the DRM wrapper is updated so as to reflect current ownership. 
         [0005]    A disconnected device, however, generally cannot purchase such a license unless the disconnected device connects with a connected device that can access a clearing house. As such, the disconnected device cannot play a song that is not licensed by the owner of the device, when the owner is not located at a point of connection. 
         [0006]    For marketing purposes, it would be beneficial if disconnected devices could play trial versions of songs that are not licensed by the device owners, and if such trial versions could be copied as trial versions from one disconnected device to another. The owners of the disconnected devices could then listen to the trial versions of the songs and afterwards, if they wish to purchase licenses to the songs, could do so by connecting their disconnected devices to a connected device, at their convenience, and purchasing licenses from a clearing house. 
         [0007]    It would thus be beneficial if a merchandising system was in place to manage digital rights for songs that are obtained as trial versions, copied from device to device, and subsequently converted to fully licensed versions. 
         [0008]    It would also be beneficial to track the history of license purchases within such a merchandising system, as trial versions of songs are copied from device to device through a sharing chain of friends, some of whom eventually purchase licenses to the trial versions. In particular, tracking of licensing history would enable a profit-sharing arrangement whereby a portion of the payment paid by a person along the sharing chain is allotted to the original clearing house or vendor from which a song was licensed. 
       SUMMARY 
       [0009]    One embodiment of the present invention concerns a configurable method and system for managing copyright privileges when a digital work is copied from one device to another. Embodiments of the present invention apply to many forms of digital copyright works, including inter alia songs, movies and pictures. The ensuing description refers primarily to digital songs, for the sake of clarity. 
         [0010]    In a general setting, digital songs are (i) acquired from external sources, including inter alia Internet music services such as iTunes® and Napster®, CDs and other recording media, music kiosks and broadcast music stations such as cable and satellite stations; and thereafter (ii) copied between digital audio recorders and digital audio players. Transfer of songs may be likened in some respects to a virtual water distribution system with nodes and conduits, wherein the nodes store water and the conduits transmit water from one node to another. External nodes represent music sources such as record stores, kiosks and Internet music services; and internal nodes represent audio recorders and players. 
         [0011]    Within this paradigm of water distribution, digital rights management concerns controlling valves that restrict the flow of water within the pipes, and controlling access to the water in the nodes. 
         [0012]    For one embodiment of the present invention,
       digital audio devices may be registered with one another; and   songs stored within recorders and players are labeled as being “Purchased,” “Recorded” or “Try &amp; Buy.”       
 
         [0015]    Preferably, digital audio players are registered with either zero or one digital audio recorder. In other words, a digital player cannot be registered with more than one recorder, but one digital recorder can have multiple digital players registered therewith. 
         [0016]    For one embodiment, the label of a song is used to identify copyrights associated therewith. The Try &amp; Buy label is used for promotional or trial versions of songs, and generally include an expiration event, upon occurrence of which the song “evaporates”; i.e., can no longer be played in its entirety. 
         [0017]    For one embodiment of the present invention, copyright management is achieved by (i) restricting a song from being copied from a source device to a target device; and (ii) specifying the way a song is labeled within a target device when the song is copied from a source device to the target device—based on the source device, the target device, the label of the song in the source device, and based on whether or not the source and target device are commonly registered. 
         [0018]    Further, for an alternate embodiment of the present invention, copyright management may restrict the number of copies permitted to be made for a song resident on a source device. For example, when a recorder is used to copy songs to a plurality of players, up to three copies of a song may be permitted. 
         [0019]    Embodiments of the present invention enable audio device manufacturers to configure a flexible logic for digital rights management in accordance with legal requirements in their respective locales. Various such configurations are described in the detailed description hereinbelow. 
         [0020]    Embodiments of the present invention may be implemented in conjunction with third-party digital rights management systems in order to comply with third-party DRM rules and in order to ensure backward compatibility with third-party players. As such, one embodiment of the present invention provides an enhancement to conventional DRM systems, within conventional architectures. 
         [0021]    Embodiments of the present invention may also be used advantageously for tracking usage and merchandising. Specifically, a first user purchases a license to a digital work. Subsequently the digital work is copied from device to device along a sharing chain of friends, one friend sharing with the next friend. The shared copies are Try &amp; Buy copies, which can only be accessed in limited ways. Some or all of the friends along the chain may eventually purchase their copy of the digital work, converting it from a Try &amp; Buy copy to an owned copy. Using an embodiment of the present invention, when such a friend purchases a license to convert a shared Try &amp; Buy copy of the digital work into an owned copy, information as to the original source of purchase as well as the friend&#39;s usage is tracked. This information can be used, inter alia, to allot a portion of the payment received by the friend to the original source of purchase, and to aggregate usage and purchase statistics. 
         [0022]    In distinction from the present invention, prior art digital rights managers do not include the fundamental feature of adapting labels from source label to target label when a song is copied from a source device to a target device. One such prior art digital rights manager is Microsoft Corporation&#39;s Windows Media Rights Manager, which implements digital rights by encrypting audio files using keys, and packaging the files with key IDs. In order to play the audio files, a user obtains a license, which contains a key to decrypt the file. 
         [0023]    Another such prior art digital rights manager is Apple Corporation&#39;s iTunes rights manager, which registers iPod music players with computers, so that an iPod cannot download an MP3 song from a computer that it is not registered with. 
         [0024]    There is thus provided in accordance with an embodiment of the present invention a method for digital rights management for a copyright work that is copied from device to device from among a plurality of devices, some of which are parent devices and some of which are child devices, and wherein a child device may be registered with a parent device. A digital work is copied from a parent device, P 1 , to a child device, C 1 , registered with device P 1 , the digital work encapsulating digital rights management (DRM) data that serves to permit full access to the digital work by parent device P 1 , and to deny access to the digital work by devices other than device P 1 . The DRM data in the copy of the digital work within device C 1  is modified, so as to permit full access to the digital work, for a prescribed time period, by device C 1  and by child devices other than device C 1 . Auxiliary DRM data is inserted in the copy of the digital work within device C 1 , so as to permit full access to the digital work by device C 1 , and so as to permit limited access to the digital work by child devices other than device C 1 . If the digital work is copied from device C 1  to a parent device P 2  other than device P 1 , then the DRM data in the copy of the digital work within device P 2  is modified, so as to permit limited access to the digital work by device P 2 . The auxiliary DRM data in the copy of the digital work within device P 2  is removed, and if the digital work is copied from device C 1  to a child device C 2  other than device C 1 , then the auxiliary DRM data in the copy of the digital work within device C 2  is modified, so as to permit limited access to the digital work by child device C 2  and so as to permit limited access to the digital work by child devices other than device C 2 . 
         [0025]    There is further provided in accordance with an embodiment of the present invention a method for digital rights management for a copyright digital work that is copied from device to device from among a plurality of devices, some of which are parent devices and some of which are child devices, and wherein a child device may be registered with a parent device, and wherein a copy of the digital work may encapsulate digital rights management (DRM) data that serves to determine one of at least two levels of access, namely, (i) permit full access to the digital work, or (ii) permit limited access to the digital work. Rules are enforced for setting the DRM data within copies of the digital work that encapsulate DRM data, according to the following principles: (1) if the digital work is copied from a child device, C 1 , to a parent device, P 1 , with which C 1  is registered, then the DRM data in the copy of the digital work within device P 1  is kept at the same access level as the copy of the digital work within device C 1 ; (2) if the digital work is copied from a child device, C 1 , which is registered with a parent device, P 1 , to another child device, C 2 , which is also registered with a parent device, P 1 , then the DRM data in the copy of the digital work within device C 2  is kept at the same access level as the copy of the digital work within device C 1 ; (3) if the digital work is copied from a child device, C 1 , which is registered with a parent device, P 1 , to a parent device, P 2 , other than P 1 , then the DRM data in the copy of the digital work within device P 2  is set to access level (ii); (4) if the digital work is copied from a child device, C 1 , which is registered with a parent device, P 1 , to a child device, C 2 , that is not registered with device P 1 , then the DRM data in the copy of the digital work within device C 2  is set to access level (ii); (5) if the digital work is copied from a parent device, P 1 , to another parent device, P 2 , then the DRM data in the copy of the digital work within device P 2  is set to access level (ii); (6) if the digital work is copied from a parent device, P 1 , to a child device, C 1 , that is not registered with device P 1 , then the DRM data in the copy of the digital work within device C 1  is set to access level (ii). 
         [0026]    There is yet further provided in accordance with an embodiment of the present invention a method for tracking usage and fulfillment of a copyright digital work that is copied from device to device from among a plurality of devices, some of which are parent devices and some of which are child devices, and wherein a child device may be registered with a parent device, and wherein a copy of the digital work may encapsulate digital rights management (DRM) data that serves to determine one of at least two levels of access, namely, (i) permit full access to the digital work, or (ii) permit limited access to the digital work, and wherein a copy of the digital work may be licensed from a fulfiller in at least two ways, namely, (A) receiving a copy of the digital work with DRM data set to access level (i), or (B) adjusting the DRM data within an already existing copy of the digital work from access level (ii) to access level (i). A cumulative record of licenses is generated within copies of the digital work, including (1) maintaining a record of source information within a copy of the digital work, when the digital work is copied from a source to a device; (2) maintaining a record of purchase information within a copy of the digital work, when the digital work is licensed from a fulfiller; (3) maintaining a record of usage information within a copy of the digital work, for the current device in which the copy of the digital work is stored; and (4) further maintaining a record of usage information within a copy of the digital work, for a previous device from which the copy of the digital work on the current device was copied, if the current device is a parent device and the previous device is a child device that is registered with the current device, or if the previous device is a parent device and the current device is a child device that is registered with the previous device. 
         [0027]    There is additionally provided in accordance with an embodiment of the present invention a system for digital rights management for a copyright work that is copied from device to device from among a plurality of devices, some of which are parent devices and some of which are child devices, and wherein a child device may be registered with a parent device. A digital rights manager within a parent device P 1  is provided for: (1) copying a digital work from device P 1  to a child device, C 1 , registered with device P 1 , the digital work encapsulating digital rights management (DRM) data that serves to permit full access to the digital work by parent device P 1 , and to deny access to the digital work by devices other than device P 1 ; (2) modifying the DRM data in the copy of the digital work intended for device C 1 , so as to permit full access to the digital work, for a prescribed time period, by device C 1  and by child devices other than device C 1 ; and (3) inserting auxiliary DRM data in the copy of the digital work intended for device C 1 , so as to permit full access to the digital work by device C 1 , and so as to permit limited access to the digital work by child devices other than device C 1 . A digital rights manager within child device C 1  is provided for: (1) for copying the digital work from device C 1  to a parent device P 2  other than device P 1 ; (2) modifying the DRM data in the copy of the digital work intended for device P 2 , so as to permit limited access to the digital work by device P 2 ; (3) removing the auxiliary DRM data in the copy of the digital work intended for device P 2 ; (4) copying the digital work from device C 1  to a child device C 2  other than device C 1 ; (5) and modifying the auxiliary DRM data in the copy of the digital work intended for device C 2 , so as to permit limited access to the digital work by child device C 2  and so as to permit limited access to the digital work by child devices other than device C 2 . 
         [0028]    There is moreover provided in accordance with an embodiment of the present invention a system for digital rights management for a copyright digital work that is copied from device to device from among a plurality of devices, some of which are parent devices and some of which are child devices, and wherein a child device may be registered with a parent device, and wherein a copy of the digital work may encapsulate digital rights management (DRM) data that serves to determine one of at least two levels of access, namely, (i) permit full access to the digital work, or (ii) permit limited access to the digital work. A digital rights manager within a child device C 1  is provided for enforcing rules for setting the DRM data within copies of the digital work that encapsulate DRM data, according to the following principles: (1) if the digital work is copied from the child device, C 1 , to a parent device, P 1 , with which C 1  is registered, then the DRM data in the copy of the digital work within device P 1  is kept at the same access level as the copy of the digital work within device C 1 ; (2) if the digital work is copied from the child device, C 1 , which is registered with a parent device, P 1 , to another child device, C 2 , which is also registered with a parent device, P 1 , then the DRM data in the copy of the digital work within device C 2  is kept at the same access level as the copy of the digital work within device C 1 ; (3) if the digital work is copied from the child device, C 1 , which is registered with a parent device, P 1 , to a parent device, P 2 , other than P 1 , then the DRM data in the copy of the digital work within device P 2  is set to access level (ii); and (4) if the digital work is copied from the child device, C 1 , which is registered with a parent device, P 1 , to a child device, C 2 , that is not registered with device P 1 , then the DRM data in the copy of the digital work within device C 2  is set to access level (ii). A digital rights manager within a parent device P 1  is provided for enforcing rules for setting the DRM data within copies of the digital work that encapsulate DRM data, according to the following principles: (1) if the digital work is copied from the parent device, P 1 , to another parent device, P 2 , then the DRM data in the copy of the digital work within device P 2  is set to access level (ii); and (2) if the digital work is copied from the parent device, P 1 , to a child device, C 1 , that is not registered with device P 1 , then the DRM data in the copy of the digital work within device C 1  is set to access level (ii). 
         [0029]    There is further provided in accordance with an embodiment of the present invention a system for tracking usage and fulfillment of a copyright digital work that is copied from device to device from among a plurality of devices, some of which are parent devices and some of which are child devices, and wherein a child device may be registered with a parent device, and wherein a copy of the digital work may encapsulate digital rights management (DRM) data that serves to determine one of at least two levels of access, namely, (i) permit full access to the digital work, or (ii) permit limited access to the digital work, and wherein a copy of the digital work may be licensed from a fulfiller in at least two ways, namely, (A) receiving a copy of the digital work with DRM data set to access level (i), or (B) adjusting the DRM data within an already existing copy of the digital work from access level (ii) to access level (i). Cumulative record managers within parent devices and child devices are provided for generating cumulative records of licenses within copies of the digital work, the cumulative record including: (1) a record of source information within a copy of the digital work, when the digital work is copied from a source to a device; (2) a record of purchase information within a copy of the digital work, when the digital work is licensed from a fulfiller; (3) a record of usage information within a copy of the digital work, for the current device in which the copy of the digital work is stored; and (4) a record of usage information within a copy of the digital work, for a previous device from which the copy of the digital work on the current device was copied, if the current device is a parent device and the previous device is a child device that is registered with the current device, or if the previous device is a parent device and the current device is a child device that is registered with the previous device. 
     
    
     
       BRIEF DESCRIPTION OF THE DRAWINGS 
         [0030]    Embodiments of the present invention will be more fully understood and appreciated from the following detailed description, taken in conjunction with the drawings in which: 
           [0031]      FIG. 1  is a front view of a digital archive, referred to as a “Nest,” in accordance with an embodiment of the present invention; 
           [0032]      FIG. 2  is a side view of a music player, referred to as an “Egg,” in accordance with an embodiment of the present invention; 
           [0033]      FIG. 3  is a bottom view of the music player of  FIG. 2 , in accordance with an embodiment of the present invention; 
           [0034]      FIG. 4  is an illustration of a user interface for copying songs from the digital archive of  FIG. 1  into the music player of  FIG. 2 , in accordance with an embodiment of the present invention; 
           [0035]      FIG. 5  is a simplified flowchart of a method for “checking-out” songs from the digital archive of  FIG. 1  to the music player of  FIG. 2 , in accordance with an embodiment of the present invention; 
           [0036]      FIG. 6  is a simplified flowchart of a method for “checking-in” songs from the music player of  FIG. 2  to the digital archive of  FIG. 1 , in accordance with an embodiment of the present invention; 
           [0037]      FIG. 7  is a simplified flowchart of a method for tracking the number of times the same song is broadcast while the digital archive of  FIG. 1  is recording music, in accordance with an embodiment of the present invention; 
           [0038]      FIG. 8  is a simplified block diagram of a digital rights management system, in accordance with an embodiment of the present invention; 
           [0039]      FIG. 9  is a simplified flow chart for a digital rights management method, in accordance with an embodiment of the present invention; 
           [0040]      FIGS. 10A and 10B  are simplified illustrations of a first consumer use case of acquiring a song in accordance with an embodiment of the present invention; 
           [0041]      FIGS. 11A and 11B  are simplified illustrations of a second consumer use case of acquiring a song in accordance with an embodiment of the present invention; 
           [0042]      FIGS. 12A ,  12 B and  12 C are simplified illustrations of a third consumer use case of acquiring a song in accordance with an embodiment of the present invention; 
           [0043]      FIG. 13  is a simplified illustration of a workflow for implementing digital rights management in conjunction with a third-party DRM system, in accordance with an embodiment of the present invention; and 
           [0044]      FIG. 14  is a simplified workflow for usage and merchandising tracking in accordance with an embodiment of the present invention. 
       
    
    
     LIST OF APPENDICES 
       [0045]    Appendix A is a source listing of an XML file for usage and merchandising tracking, in accordance with an embodiment of the present invention. 
       DETAILED DESCRIPTION 
       [0046]    Digital music players are proliferating as standalone consumer electronic devices, such as MP3 players, as bundled components within portable devices such as personal data assistants (PDAs) and cell-phones, and as home network appliances. Listeners typically build up their own personal libraries of digital songs, which are stored on memory units such as hard disk drives and removable memory cards. Digital songs are typically acquired through the Internet via subscription services and peer-to-peer exchanges, or by converting songs from a compact disc (CD) and importing them into an MP3 library. Acquiring digital music files may infringe copyrights, unless the files are validly obtained through a service that pays royalties to the recording industry. 
         [0047]    Digital songs typically include audio data and auxiliary data, referred to as meta-data, used to index the songs within the listener&#39;s library. For example, within MP3 files, meta-data is accessed through an ID3Tag; WMA files embed meta-data within the files, and also within the filenames themselves. By indexing the songs, a listener can inspect his library, search his library to access individual songs therein, remove songs, and create playlists. Typically audio players provide a user interface through which users view meta-data. 
         [0048]    Barring copyright issues, building up a digital music library requires a lot of time and work. Typically, a listener first searches the Internet for one or more songs of interest, then identifies locations of the songs, and then downloads them into a database associated with a media player. Songs are typically stored as digital files, formatted in compliance with a standard format, such as MP3 or WMA. Once the songs are downloaded, the listener typically uses software such as Windows Media Player or Winamp to play the songs on a computer, or alternatively he copies the songs onto a hardware device, such as an iPod™ or MP3 player, that plays the songs. 
         [0049]    A shortcoming in the world of digital music is the great effort required to build custom music libraries at home. Often individuals spend nights on end downloading their favorite songs and building their own personal music libraries. An alternative is to either purchase libraries that have been prepared by others, but often someone else&#39;s library does not match another listener&#39;s taste and the listener prefers to collect his own favorite songs. 
         [0050]    A popular source for a listener to hear his favorite songs is on music stations. Cable, satellite broadcast and the Internet provide music channels for almost every genre of music—classical music, rock and roll, jazz, music of the 80&#39;s, etc. A listener can enjoy music according to his taste by subscribing to such broadcast services. 
         [0051]    Embodiments of the present invention enable a listener to automatically copy and import songs that are broadcast from a music station into his digital music library, along with the songs&#39; meta-data required for indexing his library. Using embodiments of the present invention, a listener, with practically no effort, can automatically build up a large digital music library with tens of thousands of his choice of songs, all properly indexed for search and retrieval. Moreover, an additional feature of an embodiment of the present invention enables the listener to select which songs from among those broadcast on the music stations are to be imported into his library, based on one or more of criteria including, inter alia, genre, song title, artist, album, and length of song. 
         [0052]    Copying songs that are broadcast from a music station is akin to copying television programs onto a VCR. Copyright law permits a consumer to copy television programs broadcast to his home onto his VCR. The technology for automatically copying songs, however, is more complex since raw audio recording from a music station does not provide the meta-data necessary to identify such songs and incorporate them into a digital music library. Moreover, each song has to be separated out from other songs, because songs are played sequentially with overlapping on the music station, generally without breaks in between. 
         [0053]    Embodiments of the present invention concern a method and system for automatically building digital music libraries, from music channels broadcast through cable and satellite stations. For one embodiment of the present invention, broadcast songs are recorded into a digital music library, along with meta-data necessary for indexing and accessing each individual song, and for display while the songs are being played. Using an embodiment of the present invention, the digital music library generated from the broadcast music serves as a large library of individual songs, with full search and access capability. 
         [0054]    An embodiment of the present invention provides a system that enables the listener to automatically digitally record broadcast songs into a digital music library, and automatically index each recorded song according to genre, song title, artist, and album title, as described hereinbelow. Additionally, an embodiment of the present invention enables the listener to filter songs to be automatically recorded, by specifying, inter alia, a genre, song tile or artist, instead of recording all of the broadcast songs. The listener need not be present while the system of an embodiment of the present invention is in operation. It may thus be appreciated that an embodiment of the present invention enables automatic generation of large libraries of songs. 
         [0055]    An embodiment of the present invention is embodied in a programmable device, referred to herein as a “Nest,” that can interface with computers, with MP3 players and other digital music players, and with other electronic devices that include MP3 players or other digital music players therewithin, including, inter alia, cell phones, PDAs, home network appliances, and Internet appliances. For a first embodiment, the Nest is coupled to a satellite/cable receiver; for a second embodiment, the Nest is coupled to a television; for a third embodiment, the Nest is coupled to various external components via a USB and a Firewire connection. 
         [0056]    For all embodiments, the memory storing the digital music library can be either a large hard disk situated within the Nest itself, or one or more smaller removable memory units such as compact disks and memory cards, or a combination of hard disk and removable memory. The advantage of a large hard disk is that the listener&#39;s music library is consolidated into a single library that can be searched and accessed in its entirety. The advantage of removable memory units, such as compact disks, is that the listener can insert the disks into portable players such as MP3 players. Assuming that 40 songs on average require 128 MB of data and include one and a half hour&#39;s worth of listening, a large 80 GB hard disk can hold a library of approximately 25,600 songs; and a 640 MB compact disk can hold approximately 200 songs, or about 7½ hours worth of listening. 
         [0057]      FIG. 1  is a front view of a Nest  100 , in accordance with an embodiment of the present invention. Nest  100  is shown with its front panel open. On the left side of the front panel are female left and right analog audio-in connectors  110  and  120 , and female analog video-in connector  130  used for connecting auxiliary audio and video devices, such as a CD player, in order to add content into the Nest. On the right side of the front panel are female USB sockets  140  and  150  used for connecting foreign MP3 players to the Nest; a female Ethernet connector  160  for connecting the Nest to a computer network; and a mini-jack socket  170  used to provide analog stereo audio-out for headphones. 
         [0058]    For an embodiment of the present invention, a Nest includes one or more exchange ports  180 , also referred to herein as “cradles,” through which one or more hand-held digital music players, referred to herein as “Eggs,” can be connected to the Nest, for loading songs from a digital music library stored on the Nest thereto. Such exchange ports may be circular or oval ports into which Eggs in the shape of film canisters are inserted. Thus it may be appreciated that Eggs may be “charged up” with songs while they are plugged into the cradles of the Nest. 
         [0059]      FIG. 2  is a side view of an Egg  200 , in accordance with an embodiment of the present invention. Egg  200  is shown with a panel  210  that displays meta-data for a song currently being played. As can be seen in  FIG. 2 , the meta-data includes a title (“Blowing in the Wind”), an author (“Bob Dylan”) and an album (“Bob Dylan&#39;s Greatest Hits”). 
         [0060]      FIG. 3  is a bottom view of the Egg  200  of  FIG. 2 , in accordance with an embodiment of the present invention. The bottom of the Egg includes a female audio/video connector  210  for transferring analog audio and analog video between the Egg and a Nest; and a female USB connector  220  for transferring digital data between the Egg and a Nest, between the Egg and a “filling station” kiosk, and between the Egg and another Egg. Corresponding to connectors  210  and  220 , the cradles of the Nest contain male analog audio/video connector and male USB connectors (not shown in  FIG. 1 ). 
         [0061]    A typical usage scenario for a Nest and Egg is as follows. A listener sets his cable or satellite receiver box to a specific music channel, such as from a commercial-free radio station, such as The Music Choice®, and activates the Nest to capture songs from the music channel. The Nest automatically creates a digital music library and imports the broadcast songs therein. Thereafter, the listener plugs an Egg into a cradle of the Nest, and downloads selected songs from the music library onto the Egg. If the Nest is connected to the listener&#39;s speaker system, then the listener may also pipe music from the Nest into speakers in various rooms. If the Nest is connected to a home network, the listener may stream audio to a computer that is authorized to work with the Nest. 
         [0062]    In addition to a Nest being able to download songs to the Egg when the Egg is connected to the Nest, the Nest is also able to remove songs stored in the Egg. Thus, if the Egg storage is full, the Nest can remove songs from the Egg, in order for the Egg to download a new set of songs. 
         [0063]    Eggs of embodiments of the present invention may receive digital music from other sources, in addition to the Nest. Thus the Eggs may be compatible with kiosks, such as music kiosks located in music distribution stores, used for listening to songs prior to purchase and for subsequent purchase. When an Egg is connected to a Nest, the digital music received from other devices and stored within the Egg can be archived on the Nest. 
         [0064]    An Egg may receive control commands through its USB connector. Specifically,
       when connected to a Nest, the Nest may issue control commands to the Egg, such as a command to advance to the next song; and   when connected to a docking station, such as a docking station for the Egg in a room of a house, the docking station may receive infra red commands issued by a user, and translate them into control commands to the Egg over the USB connector.       
 
         [0067]      FIG. 4  is an illustration of a graphical user interface (GUI) for copying songs from the Nest of  FIG. 1  into the Egg of  FIG. 2 , in accordance with an embodiment of the present invention. The GUI shown in  FIG. 4  is displayed on a television or other display device connected to the Nest, and interacted with through use of a remote control device, such as an infra-red control unit. As such, the GUI of  FIG. 4  is intended for navigation with simple directional buttons and a select button. 
         [0068]    The GUI shown in  FIG. 4  is used to organize a digital music library and create playlists; i.e., sequences of songs for playing from the Nest, or for copying to an Egg for playback from the Egg. 
       Copyright Management 
       [0069]    An enhanced embodiment of the present invention incorporates digital rights management. In accordance with an embodiment of the present invention, an Egg is registered with at most one Nest, and only Eggs registered with a Nest have the right to check-out non-promotional songs therefrom, as described hereinbelow. Typically, a Nest will have multiple Eggs registered with the Nest. 
         [0070]    In accordance with an embodiment of the present invention, a song within a Nest or an Egg is labeled as “Purchased,” “Recorded,” or “Try &amp; Buy.” A “Purchased” song is one that is paid for by a consumer. Purchased songs include inter alia songs purchased through an Internet service such as iTunes® or Napster®, songs purchased through a kiosk, and songs copied and converted (“ripped”) to a format such as MP3 from a CD that is purchased. “Recorded” songs include songs recorded for a consumer from a cable or satellite music station. “Try &amp; Buy” songs are promotional or trial versions of songs that are provided to a consumer for free, and eventually expire. If the consumer wishes to continue to listen to such songs, he must obtain a Purchased or Recorded version of the song. 
         [0071]    Expiration of a Try &amp; Buy song may occur inter alia after a fixed time period, such as thirty days, or after a fixed number of playbacks of the song. Upon expiration, a Try &amp; Buy song may cease to play altogether, or may play only a down-sampled version of the song or a header of the song, or may instead play a message explaining how to purchase the song, or otherwise enable purchase of the song. 
         [0072]    The label of a Try &amp; Buy song may include a URL or other such identifier for one or more web sites that serve as a clearinghouse through which the song can be purchased. 
         [0073]    In accordance with an embodiment of the present invention, the Nest includes a list of songs that are already contained within the Nest and a list of songs that are not already contained within the Nest. For example, whenever a song from a specific album by a specific artist is contained within the Nest, the list includes other songs from the same album or other songs by the same artist. Songs that have been recorded within the Nest are labeled as Recorded. Other songs, not contained within the Nest, can be downloaded to the Nest as trial Try &amp; Buy versions, upon request by a consumer. After listening to a Try &amp; Buy version of a song, the consumer may purchase the song using the Nest, and the purchased song is then labeled as Purchased. Such labeling of a song as Recorded, Purchased or Try &amp; Buy serves to identify the copyrights associated with the song. 
         [0074]    When a song is copied from one device to another device where the two devices are registered with one another, such as from a Nest to an Egg that is registered with the Nest, or from an Egg to a Nest that the Egg is registered with, the label of the song is maintained; i.e., the label of the song on the target device is set to the label of the song on the source device. For example, if a Try &amp; Buy song is copied from a Nest to an Egg that is registered with the Nest, and then to another Egg that is also registered with the same Nest, then the song is labeled as Try &amp; Buy on the two Eggs. Similarly, if an Egg is used to purchase a song from a kiosk and the song is subsequently copied to a Nest that the Egg is registered with, then the song is labeled as Purchased on the Egg and on the Nest. 
         [0075]    When a song is copied from one device to another device where the two devices are not registered with one another, such as from a Nest to an Egg or from an Egg to a Nest, where the Egg is not registered with the Nest, then regardless of the label of the song on the source device, the song is labeled as Try &amp; Buy on the target device. 
         [0076]    Table I summarizes the copyright labeling of a song on a target device. 
         [0000]    
       
         
               
             
               
               
             
           
               
                 TABLE I 
               
             
             
               
                   
               
               
                 Copyright Label of Song on Target Device with First Embodiment 
               
             
          
           
               
                 Source Device --&gt; Target Device 
                 Source Label --&gt; Target Label 
               
               
                   
               
               
                 Nest --&gt; Egg registered with 
                 Purchased --&gt; Purchased 
               
               
                 the Nest OR 
               
               
                 Egg registered with Nest --&gt; 
                 Recorded --&gt; Recorded 
               
               
                 Nest OR 
               
               
                 Egg --&gt; Egg, both Eggs 
                 Try &amp; Buy --&gt; Try &amp; Buy 
               
               
                 registered with the same Nest 
               
               
                 Nest --&gt; Egg not registered 
                 Purchased --&gt; Try &amp; Buy 
               
               
                 with the Nest OR 
               
               
                 Egg not registered with Nest --&gt; 
                 Recorded --&gt; Try &amp; Buy 
               
               
                 Nest OR 
               
               
                 Egg --&gt; Egg, Eggs registered with 
                 Try &amp; Buy --&gt; Try &amp; Buy 
               
               
                 the different Nests 
               
               
                 Cable/satellite broadcast --&gt; Nest 
                 --&gt; Recorded 
               
               
                 CD or other recording media 
                 --&gt; Purchased 
               
               
                 (optical, magnetic, etc.) --&gt; Nest 
               
               
                 CD or other recording media 
               
               
                 (optical, magnetic, etc.) --&gt; Egg 
               
               
                 Internet music service (iTunes ®, 
               
               
                 Napster ®) --&gt; Nest 
               
               
                 Music kiosk --&gt; Egg 
               
               
                   
               
             
          
         
       
     
         [0077]    The logic of Table I assumes that any two devices can determine whether or not they are commonly registered. This capability can be achieved, for example, if the registration information is built into a Nest and an Egg at the time of manufacture. 
         [0078]    In addition to the logic of Table I, the label of a song within a Nest or an Egg is changed from Try &amp; Buy to Purchased if a user purchases the song from a clearinghouse, using the Nest or the Egg, respectively. 
         [0079]    For a second embodiment of the present invention, the Nest can directly determine whether an Egg is registered with it, but an Egg cannot directly determine whether it is registered with a Nest, or whether it and another Egg are registered to the same Nest. This occurs, for example, if an Egg has the capability of registering itself with any one of a plurality of Nests after it is manufactured. In this latter case, the logic of Table I is modified so that whenever a song is copied from a source Egg to a target Egg, the song is labeled as Try &amp; Buy in the target Egg. Accordingly, the copyright labeling of a song on a target device follows Table II. 
         [0000]    
       
         
               
             
               
               
             
           
               
                 TABLE II 
               
             
             
               
                   
               
               
                 Copyright Label of Song on Target 
               
               
                 Device with Second Embodiment 
               
             
          
           
               
                 Source Device --&gt; Target Device 
                 Source Label --&gt; Target Label 
               
               
                   
               
               
                 Nest --&gt; Egg registered with 
                 Purchased --&gt; Purchased 
               
               
                 the Nest OR 
               
               
                 Egg registered with Nest --&gt; 
                 Recorded --&gt; Recorded 
               
               
                 Nest 
               
               
                   
                 Try &amp; Buy --&gt; Try &amp; Buy 
               
               
                 Nest --&gt; Egg not registered 
                 Purchased --&gt; Try &amp; Buy 
               
               
                 with the Nest OR 
               
               
                 Egg not registered with Nest --&gt; 
                 Recorded --&gt; Try &amp; Buy 
               
               
                 Nest OR 
               
               
                 Egg --&gt; Egg 
                 Try &amp; Buy --&gt; Try &amp; Buy 
               
               
                 Cable/satellite broadcast --&gt; 
                 --&gt; Recorded 
               
               
                 Nest 
               
               
                 CD or other recording media 
                 --&gt; Purchased 
               
               
                 (optical, magnetic, etc.) --&gt; Nest 
               
               
                 CD or other recording media 
               
               
                 (optical, magnetic, etc.) --&gt; Egg 
               
               
                 Internet music service (iTunes ®, 
               
               
                 Napster ®) --&gt; Nest 
               
               
                 Music kiosk --&gt; Egg 
               
               
                   
               
             
          
         
       
     
         [0080]    For this second embodiment, an egg that is registered with a first Nest may be re-registered with a second Nest. In such case, the Egg is no longer registered with the first Nest. There is a limit to the number of times an Egg can be re-registered, and after an Egg re-registers itself a maximum number of times, it is blocked from further re-registration. 
         [0081]    For a third embodiment of the present invention, the distinction between Purchased and Recorded songs is ignored, and both are identified as “Owned” songs. For this third embodiment, the copyright labeling of a song on a target device follows Table III. 
         [0000]    
       
         
               
             
               
               
             
           
               
                 TABLE III 
               
             
             
               
                   
               
               
                 Copyright Label of Song on Target 
               
               
                 Device with Third Embodiment 
               
             
          
           
               
                 Source Device --&gt; Target Device 
                 Source Label --&gt; Target Label 
               
               
                   
               
               
                 Nest --&gt; Egg registered with 
                 Owned --&gt; Owned 
               
               
                 the Nest OR Egg registered 
               
               
                 with Nest --&gt; Nest OR 
               
               
                 Egg --&gt; Egg, both Eggs 
                 Try &amp; Buy --&gt; Try &amp; Buy 
               
               
                 registered with the same Nest 
               
               
                 Nest --&gt; Egg not registered 
                 Owned --&gt; Try &amp; Buy 
               
               
                 with the Nest OR Egg not 
               
               
                 registered with Nest --&gt; Nest OR 
               
               
                 Egg --&gt; Egg, Eggs registered 
                 Try &amp; Buy --&gt; Try &amp; Buy 
               
               
                 with the different Nests 
               
               
                 Cable/satellite broadcast --&gt; 
                 --&gt; Owned 
               
               
                 Nest 
               
               
                 CD or other recording media 
                 --&gt; Owned 
               
               
                 (optical, magnetic, etc.) --&gt; Nest 
               
               
                 CD or other recording media 
               
               
                 (optical, magnetic, etc.) --&gt; Egg 
               
               
                 Internet music service (iTunes ®, 
               
               
                 Napster ®) --&gt; Nest 
               
               
                 Music kiosk --&gt; Egg 
               
               
                   
               
             
          
         
       
     
         [0082]    For yet a fourth embodiment of the present invention, copying of songs from a Nest to multiple Eggs, each of which is registered with the Nest, is restricted. This fourth embodiment has a more elaborate logic than the first, second, and third embodiments. In order to best describe this logic, the terms “checking-out” and “checking-in” of songs are used as follows. When an Egg is connected to a Nest in order to download songs from the Nest to the Egg, this is referred to herein as “checking-out” of songs. When an Egg is connected to a Nest in order to remove songs stored in the Egg, this is referred to herein as “checking-in” of songs. 
         [0083]    Often the same song can be broadcast multiple times from a cable or satellite music station, while the Nest is operational to record the broadcast songs. For an embodiment of the present invention, the Nest stores a count for each Recorded song, which is incremented when the Nest encounters a broadcast song that has already been recorded onto the Nest archive. Such count thus corresponds to the total number of times the Recorded song has been broadcast while the Nest was recording, and is denoted henceforth as max_permitted_copies. For example, if a Recorded song is re-played five times on the Music Channel while the Nest is recording from the Music Channel, then max_permitted_copies=5 for such song. The max_permitted_copies count for a Recorded song is used to restrict the number of different Eggs that the Nest allows to check-out the song. For example, if max_permitted_copies=5 for a Recorded song, then at most five different Eggs can check-out the song from the Nest. That is, for each Recorded song in its archive, the Nest stores a count for each song, which is incremented when an Egg checks-out the song. Such count corresponds to the number of Eggs that have checked-out the song, and is denoted henceforth as number_copies_checked_out. For example, if three Eggs have checked-out the same Recorded song from the Nest, then number_copies_checked_out=3 for such song. 
         [0084]    In accordance with an embodiment of the present invention, when an Egg checks-in a Recorded song with the Nest, thereby removing the song from the Egg, the number_copies_checked_out count is decremented. For example, if number_copies_checked_out=3 for a Recorded song and an Egg that checked-out the song subsequently checks-in the song, then number_copies_checked_out is decremented to 2 for such song. 
         [0085]      FIG. 5  is a simplified flowchart of a method for tracking the number of times the same song is broadcast while the Nest  100  of  FIG. 1  is recording music, in accordance with an embodiment of the present invention. At step  510  the Nest identifies a song being broadcast from a cable or satellite station that is currently being recorded by the Nest. At step  520  the Nest determines whether or not the song is already stored within the Nest&#39;s digital archive. If so, then at step  530  the Nest increments max_permitted_copies by one. Otherwise, at step  540  the Nest initializes max_permitted_copies=1 for the song, and number_copies_checked_out=0 for the song. At step  550  the Nest stores the Recorded song and its meta-data within the Nest&#39;s digital archive. 
         [0086]      FIG. 6  is a simplified flowchart of a method for “checking-out” Recorded songs from the Nest of  FIG. 1  to the Egg of  FIG. 2  in accordance with an embodiment of the present invention. At step  610  an Egg that is connected to a cradle in a Nest requests to copy a Recorded song from the Nest to the Egg. At step  620  the Nest determines whether or not the Egg is registered with the Nest. If so, then at step  630  the Nest determines whether number_copies_checked_out is less than max_permitted_copies for the requested song. If so, then at step  640  the Nest increments number_copies_checked_out for the song by one, and at step  650  the Nest permits the Egg to copy the song from the Nest to the Egg. 
         [0087]    If at step  620  the Nest determines that the Egg is not registered with the Nest, or if at step  630  the Nest determines that number_copies_checked_out is equal to max_permitted_copies, then the Egg&#39;s request for the Recorded song is denied at step  660 . Alternatively, the Recorded song may be copied onto the Egg as a trial version, and labeled Try &amp; Buy. 
         [0088]      FIG. 7  is a simplified flowchart of a method for “checking-in” songs from the Egg of  FIG. 2  to the Nest of  FIG. 1 , in accordance with an embodiment of the present invention. If a song labeled Try &amp; Buy is checked in from an Egg to a Nest, then the song is also labeled Try &amp; Buy on the Nest. 
         [0089]    If a song labeled Recorded is checked in from an Egg to a Nest, then at step  710  an Egg connected to a cradle in the Nest requests to check-in the Recorded song. At step  720  the Nest determines whether or not the Egg is registered with the Nest. If so, then at step  730  the Nest determines whether or not the song already resides within the Nest&#39;s digital archive. If so, then at step  740  the Nest decrements number_copies_checked_out for the song by one, and at step  750  the Nest instructs the Egg to erase the song from the Egg. 
         [0090]    If at step  720  the Nest determines that the Egg is not registered with the Nest, than the Egg&#39;s request to check-in the song is denied at step  760 . Alternatively, the song may be copied onto the Nest as a trial version, and labeled Try &amp; Buy. If at step  730  the Nest determines that the song does not currently reside within its digital archive, then this indicates that the Egg obtained the song from another source, such as from a kiosk. As such, at step  770  the Nest initializes max_permitted_copies=1 for the song, and number_copies_checked_out=0 for the song. At step  780  the Nest copies the song and its meta-data from the Egg into the Nest&#39;s digital archive. 
         [0091]    When a Recorded song is copied from a first Egg to a second Egg in this embodiment, the song is labeled as Try &amp; Buy on the second Egg, even if the first and second Egg are both registered to the same Nest. 
         [0092]    Purchased songs may also be restricted for copying to multiple Eggs with similar logic, by setting max_permitted_copies=1. 
         [0093]    In general, embodiments of the present invention support a general digital rights configuration, by means of rules that specify whether or not a song residing on a source device has requisite permission for copying to a target device and, if so, how the song should be labeled when copied to the target device. Such rules may be embodied within functions 
         [0094]    mayBeCopied(srcDeviceType, trgtDeviceType, isRegistered, srcDeviceLabel), 
         [0095]    trgtLabel(srcDeviceType, trgtDeviceType, isRegistered, srcLabel), 
         [0000]    where srcDeviceType and trgtDeviceType are device specific parameters: 
         [0096]    srcDeviceType indicates the type of the source device in which the digital song resides, including inter alia Nest and Egg; and 
         [0097]    trgtDeviceType indicates the type of the target device onto which the digital song is to be copied, including inter alia Nest and Egg; where isRegistered is specific to a pair of devices: 
         [0098]    isRegistered indicates whether or not the source device and target device are commonly registered; 
         [0000]    where srcLabel and trgtLabel are both song and device specific parameters: 
         [0099]    srcLabel indicates the label of the song on the source device, including inter alia Recorded, Purchased and Try &amp; Buy or, alternatively, Owned and Try &amp; Buy; and 
         [0100]    trgtLabel indicates the label of the song on the target device, including inter alia Recorded, Purchased and Try &amp; Buy or, alternatively, Owned and Try &amp; Buy; and where: 
         [0101]    mayBeCopied indicates whether or not the song may be copied from the source device to the target device. 
         [0102]    More generally, as described hereinabove, the functions mayBeCopied( ) and trgtLabel( ) may have additional parameters max_permitted_copies and number_copies_checked_out, 
         [0000]    where max_permitted_copies and number_copies_checked_out are both song and device specific parameters: 
         [0103]    max_permitted_copies indicates the maximum number of copies of the song that are permitted from the device; and 
         [0104]    number_copies_checked_out indicates the current number of copies of the song that have been made from the device. 
         [0105]    Alternatively the functions mayBeCopied( ) and trgtLabel( ) may be embodied as tables or other data structures. 
         [0106]      FIG. 8  is a simplified block diagram of a digital rights management system, in accordance with an embodiment of the present invention. Shown in  FIG. 8  is a source device  805  including a database manager  810  and a rights manager  815 . Database manager  810  preferably controls a database  820  that stores digital songs and meta-data associated therewith. The meta-data includes a label for each song, indicating whether the song is Purchased, Recorded or Try &amp; Buy, as described hereinabove. Optionally, the meta-data may also include max_permitted_copies and number_copies_checked_out for one or more songs. The songs, their labels, and their max_permitted_copies and number_copies_checked_out parameters are accessible through database manager  810 . 
         [0107]    Digital songs and their meta-data may be stored in one or more database tables, within database  820 , that can be joined. Alternatively, the binary song data may be stored in memory locations outside of database  820 , and pointed to by address entries in database  820 . Database  820  may instead be structured as a plurality of databases. 
         [0108]    Also shown in  FIG. 8  is a target device  825 , including its own database manager  830 , rights manager  835 , and database  840 . 
         [0109]    Rights manager  815  determines whether or not a song resident on source device  810  may be copied to a specified target device, such as target device  825 . If copying of the song is permitted, then rights manager  815  further determines a label to be used for the song on the target device, referred to as the target label. In accordance with an embodiment of the present invention, rights manager  815  bases its determination on (i) the type of source device  805 , (ii) the type of target device  825 , (iii) the label of the song on source device  805 , and (iv) the max_permitted_copies and number_copies_checked_out parameters for the song on source device  805 . Rights manager  815  implements functions such as mayBeCopied( ) and trgtLabel( ) described hereinabove. 
         [0110]    After rights manager  815  determines the target label, it transmits the song and the target label to target device  825 . Target device  825  adds the song to its database  840  and labels the song in database  840  according to the target label. 
         [0111]    Also shown in  FIG. 8  is a clearing house  845  for purchasing songs. Source device  805  and target device  825  may purchase songs directly from clearing house  845 . For songs not currently resident on source device  805  or target device  825 , clearing house  845  sends the songs to the device that purchases them. For songs currently resident on source device  805  or target device  825  labeled Try &amp; Buy, clearing house  845  sends an authorization to source database manager  810  or target database manager  830  to change the label of the songs from Try &amp; Buy to Purchased. Clearing house  845  includes a transaction processor  850 , which enables a user to purchase rights to songs and verifies the user&#39;s payment. Upon completion of a user&#39;s purchase of a song by transaction processor  850 , clearing house  845  sends the songs to the user&#39;s device, or sends an authorization to the user&#39;s device to change the label of the song, as appropriate. 
         [0112]    In accordance with an embodiment of the present invention, clearing house  845  also freely distributes Try &amp; Buy versions of songs, which can be converted to Purchased versions at a later date, if a user so desires. 
         [0113]    Clearing house  845  is administered by an entity that has distribution privileges for the songs it sells, such as a cable or satellite company. 
         [0114]      FIG. 9  is a simplified flow chart for a digital rights management method, in accordance with an embodiment of the present invention. As can be seen,  FIG. 9  is divided into two columns, the leftmost column indicating steps performed by a source audio device, such as source device  805  ( FIG. 8 ) and the rightmost column indicating steps performed by a target audio device, such as target device  825 . 
         [0115]    At step  910  the target device requests a song to be copied from the source device. At step  920  the source device receives the request and identifies the target device. In particular, the source device determines the type of the target device, and whether or not the source and target device are registered with one another. 
         [0116]    At step  930  the source device determines the label for the requested song, and the max_permitted_copies and number_copies_checked_out parameters for the requested song. This information is contained within a source device database, such as database  820  ( FIG. 8 ). At step  940  the source device determines whether or not the target device has permission to copy the song. Such determination is made by a rights manager within the source device, such as rights manager  815 . If it is determined at step  940  that the target device does not have permission to copy the song from the source device, then at step  950  the source device denies the copy request. Otherwise, if it is determined at step  940  that the target device does have permission to copy the song from the source device, then at step  960  the source device determines how to label the song within the target device. Such determination is also made by a rights manager, such as rights manager  815 . 
         [0117]    At step  970  the source device transmits the requested song and its label to the target device, and at step  980  the target device copies the requested song to its database, and labels it accordingly. 
         [0118]    In reading the above description, persons skilled in the art will realize that there are many apparent variations that can be applied to the methods and systems described. Thus, the configurable logic described hereinabove for songs and audio devices is applicable as well to movies and video devices, and to other types of media and media devices. 
         [0119]    Transfer of songs from sources devices to target devices, and from clearing houses to devices, may be performed in batches of songs, such as entire albums, as well as for single songs. In addition, devices may be “hot-synched” to one another. For example, an Egg may be hot-synched to a Nest, using wired or wireless communication, so that the Nest is updated periodically with the songs in the Egg. 
         [0120]      FIGS. 10A and 10B  are simplified illustrations of a first consumer use case of acquiring a song in accordance with an embodiment of the present invention. As shown in  FIG. 10A , a consumer  1010  downloads a trial version of a song onto his Egg  1020  from a McMusic kiosk  1030  located within a McDonald&#39;s store  1040 . The song is labeled Try &amp; Buy, and consumer  1010  has limited rights to play the song for a one-week trial period. Subsequently, as shown in  FIG. 10B , consumer  1010  decides to purchase the song for $1.00 from a clearinghouse via a wireless communication. As a result of the purchase, the song is re-labeled as Purchased in Egg  1020 , and consumer  1010  is granted full rights to the song. 
         [0121]    Also shown in  FIG. 10B  is a pie chart  1050  illustrating how the $1.00 of revenue for the song is allocated between the content owner, the wireless provider, McDonald&#39;s and the owner of the present invention, as described hereinbelow. 
         [0122]      FIGS. 11A and 11B  are simplified illustrations of a second consumer use case of acquiring a song in accordance with an embodiment of the present invention. As shown in  FIG. 11A , a consumer downloads a trial version of a song onto his Egg  1120  from a Starbuck&#39;s Sounds music kiosk  1130  located within a Starbuck&#39;s store  1140 . The song is labeled Try &amp; Buy, and consumer  1110  has limited rights to play the song for a one-week trial period. Subsequently, as shown in  FIG. 11B , consumer  1110  decides to purchase the song for $1.00 from a McMusic kiosk  1150  located within a McDonald&#39;s store  1160 . As a result of the purchase, the song is re-labeled as Purchased in Egg  1020 , and consumer  1010  is granted full rights to the song. 
         [0123]    Also shown in  FIG. 11B  is a pie chart  1170  illustrating how the $1.00 of revenue for the song is allocated between the content owner, Starbuck&#39;s, McDonald&#39;s and the owner of an embodiment of the present invention, as described hereinbelow. 
         [0124]      FIGS. 11A ,  11 B and  11 C are simplified illustrations of a third consumer use case of acquiring a song in accordance with an embodiment of the present invention. As shown in  FIG. 12A , a consumer  1210  records a song from a DirectTV broadcast music stations onto her Nest  1220 , while enjoying home entertainment on her television  1230 . The recorded song is labeled as Recorded, and consumer  1210  has corresponding rights to the song. Consumer  1210  copies the song from her Nest  1220  onto her Egg  1240 . 
         [0125]    Subsequently, as shown in  FIG. 12B , consumer  1210  meets a friend, namely consumer  1250 , who expresses interest in the song. Consumer  1210  then copies the song from her Egg  1240  onto his Egg  1260 . Although the song is labeled as Recorded on Egg  1240 , the song is labeled as Try &amp; Buy on Egg  1260 . As such consumer  1250  only has limited rights to play the song for a one week trial period. 
         [0126]    Subsequently, as shown in  FIG. 12C , consumer  1250  decides to purchase the song, which he does for $1.00 via a music kiosk  1270  located in a Best Buy store  1280 . After purchasing the song, the song is re-labeled from Try &amp; Buy to Purchased within Egg  1260 , as a result of which consumer  1250  then has full rights to the song. 
         [0127]    Also shown in  FIG. 12C  is a pie chart  1290 , indicating allocating of the $1.00 purchase price for the song between the content owner, DirectTV, Best Buy and the owner of the present invention, as described hereinbelow. 
         [0000]    Implementation of the Present Invention in Conjunction with Conventional Digital Rights Management Systems 
         [0128]    The digital rights management of embodiments of the invention can be implemented in conjunction with a third-party DRM method or system. Conventional DRM systems typically allow usage of music on a disconnected mobile device, but do not allow sharing from one disconnected device to another. With conventional DRM systems, if a disconnected mobile device receives music for which it does not have a valid license, it is not able to play the music, and will not be granted a license until it connects to a license server, usually by docking to a personal computer. 
         [0129]    In distinction, using an embodiment of the present invention, music may be shared from a first consumer&#39;s Egg to a second consumer&#39;s Egg, and the second consumer is granted limited Try &amp; Buy access to the music, within an option to purchase the music. 
         [0130]    Yet despite the drawbacks with conventional DRM systems, it is necessary to preserve the DRM wrappers for the sake of backward compatibility. If a conventional DRM wrapper is removed from digital music, even if it is replaced with a non-conventional DRM wrapper, then typically conventional players will not be able to play the music at all. 
         [0131]      FIG. 13  is a simplified illustration of a workflow for implementing digital rights management in conjunction with a third-party DRM system, in accordance with an embodiment of the present invention. Shown in  FIG. 13  is a first copy  1305  of a digital work stored in a user&#39;s Nest. The copy includes a digital audio portion  1310 , which has been licensed by the user, and a third-party DRM wrapper  1315  specifying unlimited play for the user&#39;s nest only. 
         [0132]    When the user copies the digital work from his Nest (copy  1305 ) to his Egg, a second copy,  1320 , of the digital work is created. The second copy  1320  includes a digital audio portion,  1325 , substantially similar to portion  1310 , and a third-party DRM wrapper  1330 . However, the third-party DRM wrapper has been modified so as to specify unlimited play on all eggs, with a prescribed timeout, such as a two-week timeout. In addition, an auxiliary DRM wrapper  1335  is added to the second copy,  1320 , specifying unlimited play on the user&#39;s Egg, and the ability to generate limited play licenses for other devices. 
         [0133]    When the user shares the digital work with his friend, a third copy,  1340 , of the digital work is created as the digital work is copied from the user&#39;s Egg (copy  1320 ) to his friend&#39;s Egg ( 1340 ). The third copy  1340  includes a digital audio portion,  1345 , substantially similar to portion  1310 , and a third-party DRM wrapper  1350  that is substantially identical to the third-party digital wrapper  1330  from the second copy  1320 . The third copy  1340  also includes an auxiliary DRM wrapper  1355 , but in distinction to DRM wrapper  1335 , DRM wrapper  1355  specifies limited play on the friend&#39;s Egg, and the ability to generate limited play licenses for other devices. 
         [0134]    When the friend copies the digital work from the friend&#39;s Egg (copy  1340 ) to the friend&#39;s Nest, a fourth copy,  1360 , of the digital work is created. The fourth copy  1360  includes a digital audio portion, substantially similar to portion  1310 , and a third-party DRM wrapper  1370  specifying limited play on the friend&#39;s Nest only. It will be noted that the auxiliary DRM layer is removed in copy  1360 . As such, the music on the friend&#39;s Nest can be played by a conventional player. 
         [0135]    It may be appreciated in  FIG. 13  that the auxiliary DRM wrappers  1335  and  1355 , instead of being stored within various copies of the digital work, may instead be stored in separate files associated within the copies of the digital work, or may alternatively be stored in a database table having a primary key that serves as an identifier for a copy of the digital work. Similarly, the conventional third-party DRM wrappers  1315 ,  1330 ,  1350  and  1370  may also be stored in separate files or within a database table. 
       Use an Embodiment of the Invention for Usage and Merchandising Tracking 
       [0136]    As illustrated in  FIGS. 10B ,  11 B, and  12 C, an embodiment of the present invention has application to usage tracking for purposes of revenue sharing or aggregation of statistics. Licenses for digital music may be purchased through several channels, including inter alia: 
         [0137]    (i) music recorded onto a Nest from broadcast, off-the-air; 
         [0138]    (ii) music purchased through a Nest from a licensing authority; and 
         [0139]    (iii) music purchased through an Egg from a music kiosk. 
         [0000]    Music for preview, with a Try &amp; Buy wrapper, may be licensed from these same channels. 
         [0140]    An embodiment of the present invention is advantageous for tracking the following information for songs: 
         [0141]    (a) if recorded, when it was recorded and from which provider; 
         [0142]    (b) if purchased directly, the fulfiller of the purchase; 
         [0143]    (c) if upgraded from a Try &amp; Buy version, the fulfiller of the original purchase by the original owner and the fulfiller of the purchase from the Try &amp; Buy version; 
         [0144]    (d) if shared, the customer who originally owned the copy, the original fulfiller, and the sharing chain of users; and 
         [0145]    (e) play information for the current owner, whether played on the owner&#39;s Nest or the owner&#39;s Egg. 
         [0146]    Reference is now made to  FIG. 14 , which is a simplified workflow for usage and merchandising tracking in accordance with an embodiment of the present invention. Shown in  FIG. 14  is a first copy,  1405 , of a digital work that is purchased by user A, on user A&#39;s Nest. User A may have purchased the digital work, for example, over the Internet through a licensing authority, or on a CD at a retail store. Copy  1405  includes a digital audio portion,  1410 , and a record,  1415 , including user A&#39;s purchase information and user A&#39;s usage data on user A&#39;s Nest. 
         [0147]    When user A copies the digital work from his Nest to his Egg, a second copy of the digital work,  1420 , is created. Copy  1420  includes a digital audio portion, substantially similar to digital audio portion  1410 , and a record,  1430 , including user A&#39;s purchase information and user A&#39;s usage data on user A&#39;s Nest and user A&#39;s Egg. 
         [0148]    When user A shares the digital work with user B, a third copy of the digital work,  1435 , is created. Copy  1435  is a Try &amp; Buy copy, since user B has not yet purchased a license for the digital work. Copy  1435  includes a digital audio portion,  1440 , substantially similar to digital audio portion  1410 , and a record,  1445 , including user A&#39;s purchase information and user B&#39;s usage data on user B&#39;s Egg. 
         [0149]    When user B copies the digital work from user B&#39;s Egg to user B&#39;s Nest, a fourth copy of the digital work,  1450 , is created. Copy  1450  includes a digital audio portion,  1455 , substantially similar to digital audio portion  1410 , and a record,  1460 . When user B subsequently purchases a license for the digital work, record  1460  is updated to reflect user A&#39;s purchase data, user B&#39;s purchase data and user B&#39;s usage data on user B&#39;s Egg and user B&#39;s Nest. 
         [0150]    For the purpose of merchandising, a portion of user B&#39;s purchase price may be paid to the fulfiller from which user A purchased the digital work. More generally, the present invention can be used to track a purchase of a digital work along a sharing chain, back to an original fulfiller from which the digital work was purchased; and a portion of the purchase prices along the sharing chain can be allotted to the original fulfiller. 
         [0151]    It may be appreciated in  FIG. 14  that the records  1415 ,  1430 ,  1445  and  1460 , instead of being stored within various copies of the digital work, may instead be stored in separate files associated within the copies of the digital work, or may alternatively be stored in a database table having a primary key that serves as an identifier for a copy of the digital work. 
         [0152]    Reference is now made to Appendix A, which includes a source listing of an XML file for usage and merchandising tracking, in accordance with an embodiment of the present invention. The XML file of Appendix A can be used for storing tracking records  1415 ,  1430 ,  1445  and  1460  ( FIG. 14 ). As shown in Appendix A, the XML file includes a section (“UsageRules”) with data for usage rules, including sub-sections for play restrictions, preview restrictions and copy restrictions. The XML file also includes a section (“SongData”) with data for ownership and usage, including sub-sections for play data, ownership data and copy data. In addition, the XML file also includes a section (“AdvertisingInfo”) for playing advertisements in conjunction with Try &amp; Buy music. 
         [0153]    In the foregoing specification, the invention has been described with reference to specific exemplary embodiments thereof. It will, however, be evident that various modifications and changes may be made to the specific exemplary embodiments without departing from the broader spirit and scope of the invention. Accordingly, the specification and drawings are to be regarded in an illustrative rather than a restrictive sense. 
         [0000]    
       
         
               
             
               
             
               
               
             
               
               
             
               
               
             
               
               
             
               
               
             
               
               
             
               
               
             
               
               
             
               
               
             
               
               
             
               
               
             
               
               
             
               
               
             
               
               
             
               
               
             
               
               
             
               
               
             
               
               
             
               
               
             
               
               
             
               
               
             
               
               
             
               
               
             
               
               
             
               
               
             
               
               
             
               
               
             
               
               
             
               
               
             
               
               
             
               
               
             
               
               
             
               
               
             
               
               
             
               
               
             
               
               
             
               
               
             
               
               
             
               
               
             
               
             
               
               
             
               
             
               
               
             
               
             
               
               
             
               
               
             
               
               
             
               
               
             
               
               
             
               
               
             
               
               
             
               
               
             
               
               
             
               
               
             
               
               
             
               
               
             
               
               
             
               
               
             
               
               
             
               
             
           
               
                   
               
               
                 APPENDIX A 
               
               
                   
               
             
             
               
                   
               
             
          
           
               
                 &lt;?xml version=“1.0” encoding=“utf-8”?&gt; 
               
               
                 &lt;EggName&gt;&lt;/EggName&gt; 
               
               
                 &lt;!-- Unique identifier of Egg&#39;s parent Nest.--&gt; 
               
               
                 &lt;MotherNestID&gt;00:07:E9:7E:2E:F1&lt;/MotherNestID&gt; 
               
               
                 &lt;!-- Unique identifiers of all other Eggs belonging to this Nest --&gt; 
               
               
                 &lt;SisterEggs&gt; 
               
               
                 &lt;/SisterEggs&gt; 
               
               
                 &lt;Folder name=“Main”&gt; 
               
             
          
           
               
                   
                 &lt;Song name=“Allentown” 
               
               
                   
                 artist=“Billy Joel” 
               
               
                   
                 album=“The Nylon Curtain” 
               
               
                   
                 id=“356334”&gt; 
               
             
          
           
               
                   
                 &lt;!-- How may we use this item? --&gt; 
               
               
                   
                 &lt;UsageRules&gt; 
               
             
          
           
               
                   
                 &lt;PlayRestrictions&gt; 
               
             
          
           
               
                   
                 &lt;!-- Date range in which the song may be played --&gt; 
               
               
                   
                 &lt;StartDate&gt;&lt;/StartDate&gt; 
               
               
                   
                 &lt;EndDate&gt;&lt;/EndDate&gt; 
               
               
                   
                 &lt;!-- Time from first play during which the 
               
             
          
           
               
                   
                 song may be played --&gt; 
               
             
          
           
               
                   
                 &lt;TimeSpan&gt;&lt;/TimeSpan&gt; 
               
               
                   
                 &lt;!-- Number of times the song may be played --&gt; 
               
               
                   
                 &lt;NumPlays&gt;&lt;/NumPlays&gt; 
               
             
          
           
               
                   
                 &lt;/PlayRestrictions&gt; 
               
               
                   
                 &lt;PreviewRestrictions&gt; 
               
             
          
           
               
                   
                 &lt;!-- If the song may not be fully played, 
               
             
          
           
               
                   
                 how many seconds may we play? --&gt; 
               
             
          
           
               
                   
                 &lt;NumSeconds&gt;&lt;/NumSeconds&gt; 
               
             
          
           
               
                   
                 &lt;/PreviewRestrictions&gt; 
               
               
                   
                 &lt;CopyRestrictions&gt; 
               
             
          
           
               
                   
                 &lt;!-- May we copy the song to other Eggs/Nests, 
               
             
          
           
               
                   
                 if so how many times --&gt; 
               
             
          
           
               
                   
                 &lt;CopiesAllowed&gt; 
               
               
                   
                 &lt;/Copies Allowed&gt; 
               
               
                   
                 &lt;!-- May we save the song to external media, 
               
             
          
           
               
                   
                 such as burning a CD --&gt; 
               
             
          
           
               
                   
                 &lt;WriteToMedia&gt; 
               
               
                   
                 &lt;/WriteToMedia&gt; 
               
             
          
           
               
                   
                 &lt;/CopyRestrictions&gt; 
               
             
          
           
               
                   
                 &lt;/UsageRules&gt; 
               
               
                   
                 &lt;!-- How did we come to own the song, and what have we 
               
             
          
           
               
                   
                 done with it? --&gt; 
               
             
          
           
               
                   
                 &lt;SongData&gt; 
               
             
          
           
               
                   
                 &lt;!-- Play history for the song, both on Nest and Eggs --&gt; 
               
               
                   
                 &lt;PlayData&gt; 
               
             
          
           
               
                   
                 &lt;FirstPlay&gt; 
               
               
                   
                 &lt;/FirstPlay&gt; 
               
               
                   
                 &lt;NumPlays&gt; 
               
               
                   
                 &lt;/NumPlays&gt; 
               
             
          
           
               
                   
                 &lt;/PlayData&gt; 
               
               
                   
                 &lt;!-- Where was song originally purchased? Who else 
               
             
          
           
               
                   
                 is in the ownership chain? --&gt; 
               
             
          
           
               
                   
                 &lt;OwnershipData&gt; 
               
             
          
           
               
                   
                 &lt;!-- Was song purchased? Recorded? Ripped? 
               
             
          
           
               
                   
                 If purchased, has it been synchronized w 
               
               
                   
                 with the Nest yet? --&gt; 
               
             
          
           
               
                   
                 &lt;OwnershipType&gt; 
               
               
                   
                 &lt;/OwnershipType&gt; 
               
               
                   
                 &lt;!-- Complete ownership chain --&gt; 
               
               
                   
                 &lt;OwnershipAuditTrail&gt; 
               
             
          
           
               
                   
                 &lt;!-- Who was it originally purchased from? --&gt; 
               
               
                   
                 &lt;OwnershipOriginator&gt; 
               
               
                   
                 &lt;/OwnershipOriginator&gt; 
               
               
                   
                 &lt;!-- Complete ownership chain --&gt; 
               
               
                   
                 &lt;OwnershipHistory&gt; 
               
               
                   
                 &lt;/OwnershipHistory&gt; 
               
             
          
           
               
                   
                 &lt;/OwnershipAuditTrail&gt; 
               
               
                   
                 &lt;!-- Date/time acquired for this user --&gt; 
               
               
                   
                 &lt;DateAcquired&gt; 
               
               
                   
                 &lt;/DateAcquired&gt; 
               
               
                   
                 &lt;!-- How many times, if any, have we recorded 
               
             
          
           
               
                   
                 this song on our Nest? --&gt; 
               
             
          
           
               
                   
                 &lt;NumTimesRecorded&gt; 
               
               
                   
                 &lt;/NumTimesRecorded&gt; 
               
             
          
           
               
                   
                 &lt;/OwnershipData&gt; 
               
               
                   
                 &lt;CopyData&gt; 
               
             
          
           
               
                   
                 &lt;!-- How many times have we copied the song to 
               
             
          
           
               
                   
                 another Egg/Nest? --&gt; 
               
             
          
           
               
                   
                 &lt;CopiesMade&gt; 
               
               
                   
                 &lt;/CopiesMade&gt; 
               
             
          
           
               
                   
                 &lt;/CopyData&gt; 
               
             
          
           
               
                   
                 &lt;/SongData&gt; 
               
             
          
           
               
                   
                 &lt;/Song&gt; 
               
               
                   
                 &lt;!-- Repeats for all songs on the Egg --&gt; 
               
               
                   
                 &lt;Song&gt; 
               
               
                   
                 &lt;/Song&gt; 
               
             
          
           
               
                 &lt;/Folder&gt; 
               
               
                 &lt;!-- All user-defined folders and their contents are listed. --&gt; 
               
               
                 &lt;Folder name=“Joe&#39;s Jazz”&gt; 
               
             
          
           
               
                   
                 &lt;SongID&gt;&lt;/SongID&gt; 
               
             
          
           
               
                 &lt;/Folder&gt; 
               
               
                 &lt;!-- Egg lists all songs owned on our Nest --&gt; 
               
               
                 &lt;NestSongList&gt; 
               
             
          
           
               
                   
                 &lt;SongID&gt;&lt;/SongID&gt; 
               
               
                   
                 &lt;SongID&gt;&lt;/SongID&gt; 
               
             
          
           
               
                 &lt;/NestSongList&gt; 
               
               
                 &lt;AdvertisingInfo&gt; 
               
             
          
           
               
                   
                 &lt;Advertisement&gt; 
               
             
          
           
               
                   
                 &lt;MediaFile&gt; 
               
               
                   
                 &lt;/MediaFile&gt; 
               
               
                   
                 &lt;!-- How many times should we play this ad? --&gt; 
               
               
                   
                 &lt;MaxPlays&gt; 
               
               
                   
                 &lt;/MaxPlays&gt; 
               
               
                   
                 &lt;!-- Should the add expire after a certain date? --&gt; 
               
               
                   
                 &lt;ExpirationDate&gt; 
               
               
                   
                 &lt;/ExpirationDate&gt; 
               
               
                   
                 &lt;!-- How frequently should this ad be played relative 
               
             
          
           
               
                   
                 to the other ads on the Egg? --&gt; 
               
             
          
           
               
                   
                 &lt;AdvertisementWeight&gt; 
               
               
                   
                 &lt;/AdvertisementWeight&gt; 
               
             
          
           
               
                   
                 &lt;/Advertisement&gt; 
               
               
                   
                 &lt;!-- Can have any number of advertisements --&gt; 
               
               
                   
                 &lt;Advertisement&gt; 
               
               
                   
                 &lt;/Advertisement&gt; 
               
               
                   
                 &lt;!-- Sequence could be “RoundRobin” or “Randomized” --&gt; 
               
               
                   
                 &lt;PlaySequence&gt; 
               
               
                   
                 &lt;/PlaySequence&gt; 
               
               
                   
                 &lt;!-- What event/s trigger an advertisement? What do we do? --&gt; 
               
               
                   
                 &lt;AdvertisingTriggers&gt; 
               
             
          
           
               
                   
                 &lt;Trigger&gt; 
               
             
          
           
               
                   
                 &lt;!-- What event triggers an advertisement? 
               
             
          
           
               
                   
                 When Egg is plugged into Mother Nest? 
               
               
                   
                 When plugged into kiosk? When song ends? 
               
               
                   
                 When song begins? --&gt; 
               
             
          
           
               
                   
                 &lt;TriggerEvent&gt; 
               
               
                   
                 &lt;/TriggerEvent&gt; 
               
               
                   
                 &lt;!-- What do we do when an ad is triggered? 
               
             
          
           
               
                   
                 Play ad on the Egg? On the Nest/kiosk? --&gt; 
               
             
          
           
               
                   
                 &lt;TriggerAction&gt; 
               
               
                   
                 &lt;/TriggerAction&gt; 
               
               
                   
                 &lt;!-- For what percentage of occurrences of this 
               
             
          
           
               
                   
                 trigger event should we take the action? 
               
               
                   
                 e.g. play an ad on song end, but only every 
               
               
                   
                 other time --&gt; 
               
             
          
           
               
                   
                 &lt;TriggerFrequency&gt; 
               
               
                   
                 &lt;/TriggerFrequency&gt; 
               
             
          
           
               
                   
                 &lt;/Trigger&gt; 
               
               
                   
                 &lt;!-- Can have more than one trigger --&gt; 
               
               
                   
                 &lt;Trigger&gt; 
               
               
                   
                 &lt;/Trigger&gt; 
               
             
          
           
               
                   
                 &lt;/AdvertisingTriggers&gt; 
               
             
          
           
               
                 &lt;/AdvertisingInfo&gt;