<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE ep-patent-document PUBLIC "-//EPO//EP PATENT DOCUMENT 1.1//EN" "ep-patent-document-v1-1.dtd">
<ep-patent-document id="EP00920069B1" file="EP00920069NWB1.xml" lang="en" country="EP" doc-number="1197020" kind="B1" date-publ="20071114" status="n" dtd-version="ep-patent-document-v1-1">
<SDOBI lang="en"><B000><eptags><B001EP>......DE....FRGB................................................................</B001EP><B003EP>*</B003EP><B005EP>J</B005EP><B007EP>DIM360 (Ver 1.5  21 Nov 2005) -  2100000/0</B007EP></eptags></B000><B100><B110>1197020</B110><B120><B121>EUROPEAN PATENT SPECIFICATION</B121></B120><B130>B1</B130><B140><date>20071114</date></B140><B190>EP</B190></B100><B200><B210>00920069.2</B210><B220><date>20000329</date></B220><B240><B241><date>20011120</date></B241><B242><date>20040624</date></B242></B240><B250>en</B250><B251EP>en</B251EP><B260>en</B260></B200><B300><B310>126758 P</B310><B320><date>19990329</date></B320><B330><ctry>US</ctry></B330></B300><B400><B405><date>20071114</date><bnum>200746</bnum></B405><B430><date>20020417</date><bnum>200216</bnum></B430><B450><date>20071114</date><bnum>200746</bnum></B450><B452EP><date>20061205</date></B452EP></B400><B500><B510EP><classification-ipcr sequence="1"><text>H04H   1/02        20060101AFI20010321BHEP        </text></classification-ipcr><classification-ipcr sequence="2"><text>H04H   9/00        20060101ALI20010321BHEP        </text></classification-ipcr><classification-ipcr sequence="3"><text>G10H   1/00        20060101ALI20010321BHEP        </text></classification-ipcr></B510EP><B540><B541>de</B541><B542>ELEKTRONISCHE SPEICHERUNG VON MUSIKDATEN UND VON PROGRAMMEN, MIT DER ERKENNUNG VON PROGRAMMSEGMENTEN, WIE ZUM BEISPIEL AUFGEZEICHNETE MUSIKVORTRÄGE, UND SYSTEM FÜR DIE VERWALTUNG UND WIEDERGABE DIESER PROGRAMMSEGMENTE</B542><B541>en</B541><B542>ELECTRONIC MUSIC AND PROGRAMME STORAGE, COMPRISING THE RECOGNITION OF PROGRAMME SEGMENTS, SUCH AS RECORDED MUSICAL PERFORMANCES AND SYSTEM FOR THE MANAGEMENT AND PLAYBACK OF THESE PROGRAMME SEGMENTS</B542><B541>fr</B541><B542>SYSTEME DE MEMORISATION, DE RECONNAISSANCE, DE GESTION ET DE REPRODUCTION DE PROGRAMMES DE MUSIQUE ELECTRONIQUE</B542></B540><B560><B561><text>EP-A- 0 898 278</text></B561><B561><text>WO-A-98/31113</text></B561><B561><text>GB-A- 2 304 489</text></B561><B561><text>US-A- 5 732 216</text></B561></B560></B500><B700><B720><B721><snm>LOGON, James, D.</snm><adr><str>81 Castle Hill Road</str><city>Windham, MA 03087</city><ctry>US</ctry></adr></B721><B721><snm>GOLDHOR, Richard, S.</snm><adr><str>5 Falmouth Street</str><city>Belmont, MA 02178</city><ctry>US</ctry></adr></B721></B720><B730><B731><snm>Gotuit Media, Inc.</snm><iid>03132560</iid><irf>P103658EP CTW</irf><adr><str>300 Brickstone Square, 
Suite 602</str><city>Andover, MA 01810</city><ctry>US</ctry></adr></B731></B730><B740><B741><snm>Wardle, Callum Tarn</snm><iid>00127381</iid><adr><str>Withers &amp; Rogers LLP 
Goldings House 
2 Hays Lane</str><city>London SE1 2HW</city><ctry>GB</ctry></adr></B741></B740></B700><B800><B840><ctry>DE</ctry><ctry>FR</ctry><ctry>GB</ctry></B840><B860><B861><dnum><anum>US2000008823</anum></dnum><date>20000329</date></B861><B862>en</B862></B860><B870><B871><dnum><pnum>WO2000058940</pnum></dnum><date>20001005</date><bnum>200040</bnum></B871></B870></B800></SDOBI><!-- EPO <DP n="1"> -->
<description id="desc" lang="en">
<heading id="h0001"><b>Technical Field</b></heading>
<p id="p0001" num="0001">This invention relates to systems for storing and reproducing recorded music and programming materials and more particularly to program storage and playback systems in which recorded program content and descriptions are transferred between a client location and a remote processing location.</p>
<heading id="h0002"><b>Background Art</b></heading>
<p id="p0002" num="0002">The present invention represents an extension to the systems and methods described in <patcit id="pcit0001" dnum="US5892536A"><text>U.S. Patent 5,892,536 issued to James D. Logan, Richard Goldhor and Daniel Goessling on April 6, 1999</text></patcit> and in <patcit id="pcit0002" dnum="WO9831113A"><text>International Publication WO 98/31113 published on July 16, 1998</text></patcit>.</p>
<p id="p0003" num="0003"><patcit id="pcit0003" dnum="WO9831113A"><text>International Publication WO 98/31113</text></patcit> describes an arrangement of the type illustrated in Fig. 1 of the attached drawings which enables a user at a client location to identify and selectively play back or erase program selections, such as individual songs, using program guide information which is downloaded from a remote processing location.</p>
<p id="p0004" num="0004"><patcit id="pcit0004" dnum="EP0898278A"><text>European patent application EP-A-0 898 278</text></patcit> discloses a transmitting and receiving system wherein a data file produced by a user can be uploaded into a server and the updated data file is downloaded to another user. The transmitting and receiving system provides a place where general users can lay works thereof open.</p>
<heading id="h0003"><b>Summary of the Present Invention</b></heading>
<p id="p0005" num="0005">As the listener accumulates a large number of previously recorded programs or program segments (e.g. songs) which he or she desires to retain, the present invention provides methods for moving those recordings to a central server to free space on the local storage unit, and to allow the user to access the stored material from other players. To this end, the present invention as shown in Fig. 2 of the drawings further includes a mechanism, seen at 123, for identifying programs as shown in Fig. 1, and further for transmitting.<!-- EPO <DP n="2"> --> programs and programs segments to be added to the library file 125 maintained at the remote server.</p>
<p id="p0006" num="0006">As further contemplated by the present invention, to avoid the need to upload programs from local storage, the identification mechanism is employed to verify that the programs are stored locally, and to communicate that fact to the remote processor, which maintains an accounting file which specifies which users have the right to retrieve and play back which programs from the shared library.</p>
<p id="p0007" num="0007">These and other features and advantages of the present invention will be made more apparent by considering the following details description which is presented in connection with the attached drawings.</p>
<heading id="h0004"><b>Brief Description of the Drawings</b></heading>
<p id="p0008" num="0008">
<ul id="ul0001" list-style="none" compact="compact">
<li>Fig. 1 is a block diagram of a prior art client-side program storage and playback device interconnected via a communications pathway to a remote server which recognizes snippets of programs received from the client-side unit and which returns descriptions of matching program segments, such as individual songs, to the play back unit; and</li>
<li>Fig. 2 is a block diagram of program storage and playback system including a mechanism for storing program content on behalf of the user on a central remote shared server.</li>
</ul></p>
<heading id="h0005"><b>Description of the Best Mode</b></heading>
<p id="p0009" num="0009">The prior art arrangement shown in Fig. 1 of the drawings allows a listener or viewer to enjoy selected, previously broadcast radio or television programs or program segments at a later when it is more convenient or desirable. In particular, previously broadcast musical programming segments (here referred to as "songs") can be easily identified and replayed.</p>
<p id="p0010" num="0010">The basic mechanism employed is shown in Fig. 1 of the drawings and consists of a client-side recorder/player, shown at the left of the vertical dashed line 101, and a song identification server shown at the right of the line 101.</p>
<p id="p0011" num="0011">The recorder/player consists of a broadcast receiver 103 coupled to an antenna 105 for receiving, demodulating and digitizing broadcast signals and for recording those signals on a substantially continuous manner in a local storage unit 107. On the client-side, a "snippet extractor" \109 sends brief digitized segments, here called "snippets," to the recognition engine 111 at the server.<!-- EPO <DP n="3"> --></p>
<p id="p0012" num="0012">The recognition engine 111 compares each snippet with a database 113 containing prerecorded programming, such as popular songs. When an incoming snippet from the client recorder/player matches one of the items in the database 113, information describing the matching item is returned to the client side and stored as a record in the stored content guide seem at 115. The transmitted information includes data specifying the time duration between the beginning of the identified snippet and the beginning of the program item (e.g. song) from which the snippet was taken, the time duration between the beginning of the snippet and the end of the program item, as well as descriptive information about the program item (e.g., song title, performer, composer, album name, date performed, etc.). Using the information thus accumulated, the user of the player recorder can review listings of songs that are available in the local song storage unit 107, and play back any song or other program item listed as indicated at 121.</p>
<p id="p0013" num="0013">The broadcast receiver 103 may be set by the user to continuously record the broadcast from a preselected a radio station, or may be programmed to switch to different frequencies at different times to record different selected programs from different stations. The incoming signal may be derived from an AM or FM radio broadcast, or from the audio portion of television programming. The principles employed in the arrangement shown in Fig. 1, and in the present invention, are applicable to television programming as well, and may be used to store, catalog and play back television programs and segments of television programs.</p>
<p id="p0014" num="0014">A variety of different program extraction and recognition mechanisms may be used to implement the arrangement of Fig. 1 and the invention. See, for example, <patcit id="pcit0005" dnum="US5577249A"><text>U.S. Patent 5,577,249</text></patcit> entitled "Method for finding a reference token sequence in an original token string within a database of token strings using appended non-contiguous substrings"; <patcit id="pcit0006" dnum="US4918730A"><text>U.S. Patent 4,918,730</text></patcit> entitled "Process and circuit arrangement for the automatic recognition of signal sequences," <patcit id="pcit0007" dnum="US4739398A"><text>U.S. Patent 4,739,398</text></patcit> entitled "Method, apparatus and system for recognizing broadcast segments," and <patcit id="pcit0008" dnum="US4697209A"><text>U.S. Patent 4,697,209</text></patcit> entitled "Methods and apparatus for automatically identifying programs viewed or recorded."</p>
<p id="p0015" num="0015">The signature database 113 and recognition engine 111 preferably takes the form of a shared system to which multiple client-side recorder players may be connected via a suitable digital communications pathway such as the Internet or a direct modem connection via the dialup telephone system. The broadcast receiver 103 preferably includes analog-to-digital converter and a digital compression mechanism to conserve space on the local storage unit 107 and to reduce the size of each snippet sent to the server.<!-- EPO <DP n="4"> --></p>
<p id="p0016" num="0016">The selection and playback mechanism 121 preferably includes means for displaying a listing of the available programs and program segments stored in local storage unit 107, means for searching the information in the stored content guide 115, and means for selectively playing and erasing selected items in local storage 107 that are identified in the stored content guide information at 115. All of these functions may be performed, if desired, by a suitably programmed personal computer equipped with a TV-Radio tuner card, such as the Hauppauge WinCast/TV-Radio card, and utilizing the PC's local hard disk to provide both the local song storage and storage for the stored program and content guide. An Internet connection from the client PC to a remote server may be used to upload snippets and download program and program segment specification data either continuously or on a batch basis. In the batch mode, the snippet extractor 109 may scan pre-recorded program segments in the store 107 and pass them to the recognition engine 111 for processing at "off hours" when the added computational and communications burden placed on both the client and server side apparatus may be more efficiently handled.</p>
<p id="p0017" num="0017">If desired, snippets which are transmitted to the server but not recognized, and which hence represent programming which cannot be automatically cataloged, may be automatically deleted from the storage unit 107 after a predetermined time, whereas recognized program segments may be retained until there disposition is specified by the user.</p>
<p id="p0018" num="0018">As the listener accumulates a large number of previously recorded programs or program segments (e.g. songs) which he or she desires to retain, it would be desirable to move those recordings to a central server to free space on the local storage unit, and to allow the user to access the stored material from other players. To this end, the present invention as shown in Fig. 2 of the drawings further includes a mechanism, seen at 123, for identifying and transmitting programs and programs segments to be added to the library file 125 maintained at the remote server. As indicated at 127 in Fig. 2, the program material in the remote library file 128 may be retrieved for playback and returned local storage when desired. Those elements seen in Fig. 2 which provide the same functions as like units shown in Fig. 1 are identified by the same reference numbers.</p>
<p id="p0019" num="0019">Multiple users may share the library file 125, with only a single copy of each program segment actually being stored. When a client station signals its intent to store a given program or program segment which has been stored in its local storage unit 115, and that program or program segment is already stored in the shared library file 125 as determined by a server-side account manager routine indicated at 128, rather than actually transferring a copy from the client to the server, the copy at the client side is simply erased and an<!-- EPO <DP n="5"> --> accounting entry is stored in the account file 129 to indicate that a "virtual transfer" of the file has been made. In this way, the copyright on the broadcast program material is protected against making any copy beyond the single copy for listener's personal use. User's who have not actually first created their own copy in local storage on the client recorder/playback unit cannot obtain an accounting "credit" which will entitle them to download the library file copy.</p>
<p id="p0020" num="0020">To insure that only one copy can be used, the system could "lock" the original copy at the time the transfer or virtual transfer was made, making the original copy inoperable even though it is still resident (not yet erased) on the client player. The lock could be opened later after a secure message was received from the server indicating that the accounting credit was being eliminated in the account file 129. In this way, the owner of a recorded program segment can play that segment on different players at different times, while the system insures that only one operative at any one time.</p>
<p id="p0021" num="0021">Each song in the library file 128 would thus be available only to authenticated individuals who had earlier uploaded the song to the server. The master copy on the server would remain operable to be downloaded to other individuals A server that would download (or unlock if it was already there) a copy to a user's second PC after verifying that the copy on the first PC was locked thus ensuring one copy per user.</p>
<p id="p0022" num="0022">Note also that a user may purchase the right to play and locally record a program segment downloaded from the server. The system that would register record/CD purchasers and allow them to download temporary copies of their purchased material to a remote site following appropriate identification.</p>
<p id="p0023" num="0023">Furthermore, users might be able to exchange or sell their personal copies of songs. To this end, the server could manage the sale or auction of previously purchased "virtual copies".</p>
<p id="p0024" num="0024">In order to reduce the cost of the service provided by the server, and to compensate the copyright owners of the program material, advertisements could be added between programs or program segments (songs).</p>
<p id="p0025" num="0025">In addition to, or as an alternative to, the automatic snippet recognition mechanism discussed above, There are several less elegant, but nonetheless practical methods to identify and mark the boundaries of desired program segments stored in the local storage unit 107. The recorder/playback unit could include means for manually marking the beginning and ending of a desired program segment which the user desires to save in his or her "virtual jukebox. Intelligent fast forward and backward buttons, speech speedup software (with pitch<!-- EPO <DP n="6"> --> control so one could listen to the music in fast-time) to get to the end quickly, set-time jumps back and forth, etc. could be used to facilitate the markup process. These techniques might work particularly well in the car given that the listener has the time to do the required "work".</p>
<p id="p0026" num="0026">A music/talk recognition mechanism may be used to delimit the song. This approach rely on an algorithm or circuit that distinguish music from the spoken word (in something akin to "audio scene-change" in video technology). For example, the arrangement described in <patcit id="pcit0009" dnum="US4542525A"><text>U.S. Patent 4,542,525</text></patcit> entitled "Method and apparatus for classifying audio signals" processes an audio signal and derives either a speech recognition signal, a music recognition signal or an indication of an unidentifiable signal.</p>
<p id="p0027" num="0027">Another implementation employs algorithms to separate two songs. That is, the system would be able to distinguish the beginning of one song and the end of another-songA/songB recognition. These transition points would then be used to help delimit songs within a stored audio stream. This technique would work in conjunction with a music/talk recognition system that separates the talk from the music would be more important than separating the occasional pair of songs that have no talk between them.</p>
<p id="p0028" num="0028">These delimitation techniques would then be applied to the audio stored in a time-shifted radio system. The talk or ads between songs could be eliminated either automatically or through user actions. With the bookmarks separating songs, the listener would be able to use an input device (such as a push button or voice-recognized spoken commands) to quickly surf from song to song. The user could then key in, or dictate using voice recognition, descriptive information about any desired song to be saved for future playback, the descriptive information being placed in the stored content guide 115.</p>
<p id="p0029" num="0029">Another form of automatic bookmarking would involve" talk radio." In this environment the system would offer another form of recognition-speaker identification. For talk radio this would allow listeners to jump from segment to segment as new speakers joined in the conversation. Each time a new voice was identified, a bookmark would be planted.</p>
<p id="p0030" num="0030">Specific word or phrase recognition would also be used to identify segments. For instance, the traffic report each day might start with the same phrase which could be recognized with standard speech recognition technology. The system would place intelligent bookmarks (intelligent in that they related to a known topic) at these identified locations.</p>
<p id="p0031" num="0031">Entire talk shows or news broadcasts could be translated to text via speech recognition. Listeners could use the voice input devices in their car PCs to request topics to hear about. These topics would be selected based on word matches.<!-- EPO <DP n="7"> --></p>
<p id="p0032" num="0032">Finally, bookmarks could be created that merely related to time. Thus, a listener might surf through a time-shifted block of audio and one of the bookmarks might be the audio corresponding the top of the hour or the breaks at every quarter hour.</p>
<p id="p0033" num="0033">In another implementation of a delimiting system, computer readable information, possibly in the form of RDS information identifying the song, performers, etc., might accompany the broadcast of a song. In the case of an Internet broadcast, this might include computer readable data such as the name of the song, performer, etc. If these tags were at a known and consistent location vis a vis the start of the song, this would allow for accurate delimiting of the song. If it was inconsistently placed, but generally located near the beginning of a song, then a song could be excised out but it would have some extraneous material associated with it. A system could be devised that excised out a 5 minute block from a buffer surrounding such an identifier. The user could then manually edit the extraneous material.</p>
<p id="p0034" num="0034">Another implementation of time-shifted radio listening would involve a multi-tuner broadcast receiver 103. This system would continuously try to delimit songs on multiple channels at once using our original song recognition algorithms (on the client or server machines), or the ideas of music/talk recognition or songA/songB recognition. Multiple tuners could even be useful in the case of manual markups as this can probably be done faster than real time. One implementation of this would use high end equipment that could digitize all the channels in specific spectrum range with a single circuit.</p>
<p id="p0035" num="0035">In the operation of a time-shifted radio system, with limited tuners and limited disk storage, the user in general has three playing options:
<ol id="ol0001" compact="compact" ol-style="">
<li>1. To play a song out of a stored jukebox (presumably stored long ago)</li>
<li>2. To play a recently stored song (involving a short time-shift)</li>
<li>3. To play a song that was being broadcast live at the moment of play.</li>
</ol></p>
<p id="p0036" num="0036">The Channel Changer implementation is optimized for the latter two options-options which would be most likely in systems with limited memory, or ones with larger memory but little content yet stored. In these cases the listener is more dependent on what is being broadcast at the present than on what is stored on disk from earlier recordings. As a result, a system that finds the greatest number of good songs quickly will have additional utility.<!-- EPO <DP n="8"> --></p>
<p id="p0037" num="0037">There are several aspects of the Channel Changer system which attempt to emulate the methods that people use as they search for good songs by switching from channel to channel in a car.</p>
<p id="p0038" num="0038">In this implementation, song recognition technology (of any of the types described above) is combined with multiple radio tuners, each with its own buffer, and channel-changing algorithms that would be used to intelligently tune the radio tuners to the optimal set of stations. (One of the tuners would be the "playing tuner", while the others would be "searching tuners".) This system will allow a listener to quickly surf multiple radio channels and "pull down" and store the greatest number of desired songs in the shortest time (compared to a single tuner system or a multi-tuner system without channel-changing algorithms).</p>
<p id="p0039" num="0039">The system would consist of a database of song fingerprints and the requisite recognition software. The song fingerprints would be as close to the front of the song as possible (not too close or the DJ might chop it off) so that song identification could happen as soon as possible once the song started playing.</p>
<p id="p0040" num="0040">Each searching tuner would have a buffer available to it (which could be as short as the distance from the beginning of a song to the fingerprint plus processing time) to capture the audio before reaching a given song's fingerprint. Once the fingerprint was found and identified, the song would be rated on a "desirability" scale. The audio before the buffer before the fingerprint would be combined with the rest of the song. The next step would be dependent on which playing option was in effect:
<ol id="ol0002" compact="compact" ol-style="">
<li>1. Under this option, the song would be saved in the jukebox.. If there is not enough unused memory to save the song, the system would compare the new song's rating to that of the song in the jukebox that had the lowest rating. If the new song has a higher rating, it would replace the existing song having the lowest rating. The process would continue over time over multiple tuners, gradually lifting the average rating of songs in memory.</li>
<li>2. Under this option, the song would be saved in a short term buffer and queued up for playback. Again, if the queue was filed, the new song would have to be better than the worst song in the queue to find a space.</li>
<li>3. Under this option (which uses minimum memory), the playing tuner would switch over to the new song as soon as it was being broadcast. There would not necessarily be storage of the whole song. The switch to the new song would be made with some consideration being given to how much better the new song is, and how close the old song is to being over.</li>
</ol><!-- EPO <DP n="9"> --></p>
<p id="p0041" num="0041">This search algorithm to find better stations to tune to using multiple tuners would have several steps. The first would be to rank stations by the probability of finding a desired song. This list could be fluid and change depending on the number of successful searches completed on each station over a recent period of time.</p>
<p id="p0042" num="0042">Then, using a predictive algorithm which would keep track of which channels had just played a song and which were in the middle of a song or an ad, the system would predict the probability of finding a desired song in the immediate future on any one given station.</p>
<p id="p0043" num="0043">The station ranking and the "song-immediacy probability" would both be assessed to decide which station to send the next available tuner to. There the tuner would wait for the next song to come on and be identified. If would then assess the desirability of the new song and under playing options
<ol id="ol0003" compact="compact" ol-style="">
<li>1. see if the song warranted space in the jukebox,</li>
<li>2. buffer the song and put it in the playing queue</li>
<li>3. switch the playing tuner over to the newly found song.</li>
</ol></p>
<p id="p0044" num="0044">(Under scenario 3, the user might want the flexibility to use fingerprints that are deeper into the song. Deeper fingerprints would allow the search tuner to identify a song even if it was "found" while in the middle of its playback. This would allow especially desirable songs to be listened to in part. Ideally however, the system would have a separate tuner for each worthwhile station. This would eliminate having to jump from station to station and deal with partial songs.)</p>
<p id="p0045" num="0045">The recorder/playback unit can be programmed to develop song desirability ratings automatically. The rating system could learn from the listener:
<ol id="ol0004" compact="compact" ol-style="">
<li>1. It could watch to see if, and when, a listener skipped out of a song as it was being played under any of the three listening options.</li>
<li>2. It could monitor if, under option #3, the user un-did a swap presented by the system.</li>
<li>3. The system could also keep track of over how long a time, and how many times, each title had been listened to and deduce a decay rate in the desirability in that song due to the multiple exposures. The system could learn what the listeners typical desired decay rate was.</li>
<li>4. Also, the user could have a simple rating interface whereby he or she could consciously rate songs so the system would know how to rate them later. The rating system could be an ongoing process so that a user could help the system understand over time at what rate the listener might be growing tired of a new system. This could be a simple<!-- EPO <DP n="10"> --> "thumbs down" button that might depress the songs rating in the personal jukebox so that the song would not be played as often.</li>
</ol></p>
<p id="p0046" num="0046">In addition, a self-reflective mechanism could be employed. That is, if the user expressed a preference for the Beatles tune #1, the system then knows which songs are most like that and puts the others in the desirability scale accordingly.</p>
<p id="p0047" num="0047">For a car-PC system, the buttons on the standard radio could be used for any of the skipping and approval rating functions mentioned above.</p>
<p id="p0048" num="0048">An interesting and potentially valuable use for this information would be to provide the song ratings back to the broadcasters or record companies. This information could be uploaded when the system "docks" to receive more song fingerprints if that system is employed, or a separate communications step may be used to transmit this information.</p>
<p id="p0049" num="0049">With the vast amount of music in existence and being played over the airwaves, a major problem is figuring out what an individual listener may like-and then using this information to listen to the songs have a higher probability of being desirable. Solving this problem is a three step process. First the listener must get exposed to wide range of new material. Radio broadcast (over the airwaves or Internet) is perfect for this. It pushes at listeners randomized playlists of songs grouped around certain musical interest groups.</p>
<p id="p0050" num="0050">The second step is "documenting" the listener's tastes while listening. And the third step is making the song available for replay. This can be done by merely waiting to hear it again on the radio, buying the record, or using the present system to snip it out for future listening. The listener can document his or her preferences and save the song all at the same time.</p>
<p id="p0051" num="0051">The car is the ideal environment to use this system as the listener is easily able to hit a button or use a verbal command to rate or store a desirable song when it is being played.</p>
<p id="p0052" num="0052">Once a personal jukebox has been developed, playlist software may be utilized. This enables automatic play of either randomized or listener-selected songs in much the same way a CD player does. When in user-controlled mode, the user would be able to work from an audio menu which would announce the group and/or song before playing. The listener could then surf through the jukebox while driving.</p>
<p id="p0053" num="0053">In random or playlist mode, the system would adapt and use some of the playlist software used by radio stations to construct the random playlists. This software would continuously scan new songs that had been delimited by the system and offer them as new material to the listener. An audible signal would announce that this was a new song. The user could command the system to discard the song and not play it again or rate the song during<!-- EPO <DP n="11"> --> the first or a subsequent play which would then allow it a place in the jukebox. The playlist generator would attempt to optimize the presentation of new material to a listener based on past listening habits, surfing actions, and explicit expressions of interest in certain types of music.</p>
<p id="p0054" num="0054">Another use for song identification with a stored audio system would be to purchase the song being played much in the same way that the listener can now while listening to an Internet broadcast. Other interactive features would be to allow the listener to request information about the band, etc.</p>
<p id="p0055" num="0055">Another use for song recognition technology (whether on the client or server side) would be to help listeners identify a specific song that they can't remember-a computerized version of "name that tune". For instance, a user might be able to sing, or perform with an instrument, a few notes of a song. The system would come back with a match or a list of songs that may match the user's attempt to sing the song. The user could then play some of the songs on the "possible matches" list or may recognize the song by the name. In any case, the user might go on from there to buy the song that matched his or her "performed" rendition or cite it as a song for which it would desirable to capture with the song recognition system when played over the radio again.</p>
<p id="p0056" num="0056">It is to be understood that the specific arrangements which have been described are merely illustrative applications of the principles of the invention.</p>
</description><!-- EPO <DP n="12"> -->
<claims id="claims01" lang="en">
<claim id="c-en-01-0001" num="0001">
<claim-text>A method for selectively reproducing locally stored programming signals comprising, in combination, the steps of:
<claim-text>storing a first set of separate programming segments at a client location,</claim-text>
<claim-text>storing, at a remote processing location, a second set of separate programming segments and content descriptions for each of said programming segments in said second set,</claim-text>
<claim-text>at said client location, employing processing means to derive identification data from each of said first set of separate programming segments,</claim-text>
<claim-text>transmitting said identification data from said client location to a remote processing location,</claim-text>
<claim-text>at said remote processing location, comparing said identification data with said second set of programming segments to identify common program segments found in both said first and said second set of programming segments,</claim-text>
<claim-text>transmitting from said remote processing location to said client location selected ones of content descriptions which describe said common program segments,</claim-text>
<claim-text>at said client location, presenting said selected content descriptions to a user to facilitate the selection of particular ones of said common program segments,</claim-text>
<claim-text>at said remote processing location, accepting a retrieval request from said client location specifying one or more of said particular ones of said common program segments, and</claim-text>
<claim-text>responding to said request by transmitting to said client location the content of said one or more particular ones of said common program segments.</claim-text></claim-text></claim>
<claim id="c-en-01-0002" num="0002">
<claim-text>The method set forth in claim 1 wherein at least some of said programming signals are recorded musical performances.</claim-text></claim>
<claim id="c-en-01-0003" num="0003">
<claim-text>The method set forth in claim 2 wherein at least some of said content descriptions specify one or more attributes of the corresponding recorded musical performance from the group of attributes consisting of the title, performer, composer, and date of the corresponding recorded musical performance.<!-- EPO <DP n="13"> --></claim-text></claim>
<claim id="c-en-01-0004" num="0004">
<claim-text>The method set forth in claim 1 wherein said step of storing said first set of programming signals comprises receiving and recording broadcasted programming signals.</claim-text></claim>
<claim id="c-en-01-0005" num="0005">
<claim-text>The method set forth in claim 4 wherein said second set of programming segments is derived from said broadcasted programming signals received at said remote processing location concurrently with the reception and recording of said broadcast programming signals at said client location, and said content descriptions transmitted to said client location from said remote processing location are used at said client location to facilitate the selective time-shifted reproduction of said broadcast programming signals.</claim-text></claim>
<claim id="c-en-01-0006" num="0006">
<claim-text>The method as set forth in 1 wherein said content descriptions transmitted from said remote processing location to said client location include information specifying the beginning and ending time of each of said common program segments.</claim-text></claim>
<claim id="c-en-01-0007" num="0007">
<claim-text>The method as set forth in claim 1 further including the steps of transmitting one or more previously received program segments from said client location to said remote processing location, and storing said previously received program segments at said remote processing location for subsequent retrieval.</claim-text></claim>
<claim id="c-en-01-0008" num="0008">
<claim-text>The method set forth in claim 1 further comprising the steps of uploading a copy of a program segment stored locally at said client location to said remote processing location and storing the uploaded copy in said stored library for later retrieval from said remote processing location.</claim-text></claim>
<claim id="c-en-01-0009" num="0009">
<claim-text>The method set forth in claim 1 further including the steps of posting an entry in an accounting file upon the transmittal of said identification data to said remote processing location, subsequently transmitting a playback request identifying said client location and identifying a requested program segment, and authorizing the transmittal of said requested program segment if said accounting file contains data indicating that identification data for said requested program segment was previously transmitted from said client location.<!-- EPO <DP n="14"> --></claim-text></claim>
<claim id="c-en-01-0010" num="0010">
<claim-text>The method set forth in claim 9 further including the step of disabling the playback of a local copy of an program segment when the remote playback of said program segment is authorized at said remote processing location.</claim-text></claim>
<claim id="c-en-01-0011" num="0011">
<claim-text>The method set forth in claim 9 further including the step of disabling the transmittal of said requested program segment from said remote processing location when the playback of the copy of said requested program segment locally stored at said client location is enabled.</claim-text></claim>
</claims><!-- EPO <DP n="15"> -->
<claims id="claims02" lang="de">
<claim id="c-de-01-0001" num="0001">
<claim-text>Verfahren zum wahlweisen Wiedergeben von lokal gespeicherten Programmsignalen, mit den kombinierten Schritten:
<claim-text>Speichern eines ersten Satzes von separaten Programmsegmenten an einem Kundenort,</claim-text>
<claim-text>Speichern eines zweiten Satzes von separaten Programmsegmenten und Inhaltsbeschreibungen für jedes der Programmsegmente im zweiten Satz an einem entfernten Verarbeitungsort,</claim-text>
<claim-text>Einsetzen einer Verarbeitungseinrichtung am Kundenort, um Identifizierungsdaten aus allen separaten Programmsegmenten des ersten Satzes abzuleiten, Übertragen der Identifizierungsdaten vom Kundenort zu einem entfernten Verarbeitungsort,</claim-text>
<claim-text>Vergleichen der Identifizierungsdaten mit dem zweiten Satz von Programmsegmenten am entfernten Verarbeitungsort, um gemeinsame Programmsegmente zu identifizieren, die in sowohl dem ersten als auch dem zweiten Satz von Programmsegmenten gefunden werden,</claim-text>
<claim-text>Übertragen ausgewählter Inhaltsbeschreibungen, die die gemeinsamen Programmsegmente beschreiben, vom entfernten Verarbeitungsort zum Kundenort,</claim-text>
<claim-text>Präsentieren der ausgewählten Inhaltsbeschreibungen am Kundenort für einen Benutzer, um die Auswahl spezieller gemeinsamer Programmsegmente zu erleichtern,</claim-text>
<claim-text>Annehmen einer Bereitstellungsanfrage vom Kundenort, die eines oder mehrere der speziellen gemeinsamen Programmsegmente bestimmt, am entfernten Verarbeitungsort, und</claim-text>
<claim-text>Antworten auf die Anfrage durch Senden des Inhalts des einen oder mehreren speziellen gemeinsamen Programmsegmente an den Kundenort.</claim-text></claim-text></claim>
<claim id="c-de-01-0002" num="0002">
<claim-text>Verfahren nach Anspruch 1, bei welchem wenigstens einige der Programmsignale aufgezeichnete musikalische Aufführungen sind.<!-- EPO <DP n="16"> --></claim-text></claim>
<claim id="c-de-01-0003" num="0003">
<claim-text>Verfahren nach Anspruch 2, bei welchem wenigstens einige der Inhaltsbeschreibungen eines oder mehrere Attribute der entsprechenden aufgezeichneten musikalischen Aufführung aus der Gruppe von Attributen bestimmen, die aus dem Titel, dem Künstler, dem Komponisten und dem Datum der entsprechenden aufgezeichneten musikalischen Aufführung besteht.</claim-text></claim>
<claim id="c-de-01-0004" num="0004">
<claim-text>Verfahren nach Anspruch 1, bei welchem der Schritt des Speicherns des ersten Satzes von Programmsignalen das Empfangen und Aufzeichnen von ausgestrahlten Programmsignalen aufweist.</claim-text></claim>
<claim id="c-de-01-0005" num="0005">
<claim-text>Verfahren nach Anspruch 4, bei welchem der zweite Satz von Programmsegmenten aus den ausgestrahlten Programmsignalen, die am entfernten Verarbeitungsort empfangen werden, gleichzeitig mit dem Empfang und dem Aufzeichnen der ausgestrahlten Programmsignale am Kundenort abgeleitet wird und die vom entfernten Verarbeitungsort zum Kundenort übertragenen Inhaltsbeschreibungen am Kundenort verwendet werden, um die selektive zeitverschobene Wiedergabe der ausgestrahlten Programmsignale zu erleichtern.</claim-text></claim>
<claim id="c-de-01-0006" num="0006">
<claim-text>Verfahren nach Anspruch 1, bei welchem die vom entfernten Verarbeitungsort zum Kundenort übertragenen Inhaltsbeschreibungen Informationen enthalten, die die Anfangs- und die Endzeit jedes der gemeinsamen Programmsegmente bestimmen.</claim-text></claim>
<claim id="c-de-01-0007" num="0007">
<claim-text>Verfahren nach Anspruch 1, ferner mit den Schritten des Übertragens eines oder mehrerer früher empfangener Programmsegmente vom Kundenort zum entfernten Verarbeitungsort und des Speicherns der früher empfangenen Programmsegmente am entfernten Verarbeitungsort für eine anschließende Bereitstellung.</claim-text></claim>
<claim id="c-de-01-0008" num="0008">
<claim-text>Verfahren nach Anspruch 1, ferner mit den Schritten des Hochladens einer Kopie eines Programmsegments, das lokal am Kundenort gespeichert ist, zum entfernten Verarbeitungsort und des Speicherns der hochgeladenen Kopie in dem gespeicherten Archiv für eine spätere Bereitstellung vom entfernten Verarbeitungsort.</claim-text></claim>
<claim id="c-de-01-0009" num="0009">
<claim-text>Verfahren nach Anspruch 1, ferner mit den Schritten des Verbuchens eines Eintrags in einer Abrechnungsdatei bei der Übertragung der Identifikationsdaten<!-- EPO <DP n="17"> --> zum entfernten Verarbeitungsort, des anschließenden Übertragens einer Wiedergabeanfrage, die den Kundenort identifiziert und ein angefordertes Programmsegment identifiziert, und des Autorisierens der Übertragung des angeforderten Programmsegments, falls die Abrechnungsdatei Daten enthält, die anzeigen, dass Identifizierungsdaten für das angeforderte Programmsegment zuvor vom Kundenort übertragen wurden.</claim-text></claim>
<claim id="c-de-01-0010" num="0010">
<claim-text>Verfahren nach Anspruch 9, ferner mit dem Schritt des Sperrens der Wiedergabe einer lokalen Kopie eines Programmsegments, wenn die entfernte Wiedergabe des Programmsegments am entfernten Verarbeitungsort autorisiert wird.</claim-text></claim>
<claim id="c-de-01-0011" num="0011">
<claim-text>Verfahren nach Anspruch 9, ferner mit dem Schritt des Sperrens der Übertragung des angeforderten Programmsegments vom entfernten Verarbeitungsort, wenn die Wiedergabe der Kopie des angeforderten Programmsegments, das lokal am Kundenort gespeichert ist, ermöglicht wird.</claim-text></claim>
</claims><!-- EPO <DP n="18"> -->
<claims id="claims03" lang="fr">
<claim id="c-fr-01-0001" num="0001">
<claim-text>Procédé de reproduction sélective de signaux de programmation mémorisés localement, comprenant, en combinaison, les étapes suivantes :
<claim-text>la mémorisation d'un premier ensemble de segments séparés de programmation à un emplacement client,</claim-text>
<claim-text>la mémorisation, à un emplacement distant de traitement, d'un second ensemble de segments séparés de programmation et de descriptions de contenu pour chacun des segments de programmation du second ensemble,</claim-text>
<claim-text>à l'emplacement client, l'utilisation d'un dispositif de traitement pour la dérivation de données d'identification de chaque segment du premier ensemble de segments séparés de programmation,</claim-text>
<claim-text>la transmission des données d'identification de l'emplacement client à un emplacement distant de traitement,</claim-text>
<claim-text>à l'emplacement distant de traitement, la comparaison des données d'identification avec le second ensemble de segments de programmation pour l'identification de segments communs de programme trouvés à la fois dans le premier et le second ensemble de segments de programmation,</claim-text>
<claim-text>la transmission, depuis l'emplacement distant de traitement vers l'emplacement client, de descriptions sélectionnées parmi les descriptions de contenu qui décrivent les segments communs de programme,</claim-text>
<claim-text>à l'emplacement client, la présentation des descriptions sélectionnées de contenu à un utilisateur afin que la sélection de segments particuliers parmi les segments communs de programme soit facilitée,</claim-text>
<claim-text>à l'emplacement distant de traitement, l'acceptation d'une requête de récupération provenant de l'emplacement client et spécifiant un ou plusieurs des segments particuliers parmi les segments communs de programme, et</claim-text>
<claim-text>la réponse à la requête par transmission à l'emplacement client du contenu d'un ou plusieurs des segments particuliers parmi les segments communs de programme.</claim-text><!-- EPO <DP n="19"> --></claim-text></claim>
<claim id="c-fr-01-0002" num="0002">
<claim-text>Procédé selon la revendication 1, dans lequel certains au moins des signaux de programmation sont des exécutions musicales enregistrées.</claim-text></claim>
<claim id="c-fr-01-0003" num="0003">
<claim-text>Procédé selon la revendication 2, dans lequel certaines au moins des descriptions de contenu spécifient un ou plusieurs attributs de l'exécution musicale enregistrée correspondante tirés du groupe d'attributs constitué du titre, de l'interprète, du compositeur et de la date de l'exécution musicale enregistrée correspondante.</claim-text></claim>
<claim id="c-fr-01-0004" num="0004">
<claim-text>Procédé selon la revendication 1, dans lequel l'étape de mémorisation du premier ensemble de signaux de programmation comprend la réception et l'enregistrement de signaux diffusés de programmation.</claim-text></claim>
<claim id="c-fr-01-0005" num="0005">
<claim-text>Procédé selon la revendication 4, dans lequel le second ensemble de segments de programmation est dérivé des signaux diffusés de programmation reçus à l'emplacement distant de traitement simultanément avec la réception et l'enregistrement des signaux diffusés de programmation à l'emplacement client, et les descriptions de contenu transmises à l'emplacement client depuis l'emplacement distant de traitement sont utilisées à l'emplacement client pour faciliter la reproduction sélective des signaux diffusés de programmation avec décalage dans le temps.</claim-text></claim>
<claim id="c-fr-01-0006" num="0006">
<claim-text>Procédé selon la revendication 1, dans lequel les descriptions de contenu transmises depuis l'emplacement distant de programmation vers l'emplacement client comprennent des informations spécifiant les moments de début et de fin de chacun des segments communs de programme.</claim-text></claim>
<claim id="c-fr-01-0007" num="0007">
<claim-text>Procédé selon la revendication 1, comprenant en outre des étapes suivantes : la transmission d'un ou plusieurs segments de programme antérieurement reçus, de l'emplacement client vers l'emplacement distant de traitement, et la mémorisation des segments de programme antérieurement reçus à l'emplacement distant de traitement en vue d'une récupération ultérieure.</claim-text></claim>
<claim id="c-fr-01-0008" num="0008">
<claim-text>Procédé selon la revendication 1, comprenant en outre les étapes suivantes : le téléchargement d'une copie d'un segment de programme mémorisé localement à<!-- EPO <DP n="20"> --> l'emplacement client vers l'emplacement distant de traitement, et la mémorisation de la copie téléchargée dans la bibliothèque mémorisée en vue d'une récupération ultérieure à l'emplacement distant de traitement.</claim-text></claim>
<claim id="c-fr-01-0009" num="0009">
<claim-text>Procédé selon la revendication 1, comprenant en outre les étapes suivantes : l'écriture d'une entrée dans un fichier de comptabilité après la transmission des données d'identification à l'emplacement distant de traitement, puis la transmission d'une requête de lecture identifiant l'emplacement client et identifiant un segment demandé de programme, et l'autorisation de la transmission du segment demandé de programme lorsque le fichier de comptabilité contient des données indiquant que les données d'identification du segment demandé de programme ont été transmises antérieurement depuis l'emplacement client.</claim-text></claim>
<claim id="c-fr-01-0010" num="0010">
<claim-text>Procédé selon la revendication 9, comprenant en outre l'étape d'inhibition de la lecture d'une copie locale d'un segment de programme lorsque la lecture distante du segment de programme est autorisée à l'emplacement distant de traitement.</claim-text></claim>
<claim id="c-fr-01-0011" num="0011">
<claim-text>Procédé selon la revendication 9, comprenant en outre l'étape d'inhibition de la transmission du segment demandé de programme de l'emplacement distant de traitement lorsque la lecture de la copie du segment demandé de programme mémorisé localement à l'emplacement client est autorisée.</claim-text></claim>
</claims><!-- EPO <DP n="21"> -->
<drawings id="draw" lang="en">
<figure id="f0001" num=""><img id="if0001" file="imgf0001.tif" wi="159" he="160" img-content="drawing" img-format="tif"/></figure><!-- EPO <DP n="22"> -->
<figure id="f0002" num=""><img id="if0002" file="imgf0002.tif" wi="161" he="211" img-content="drawing" img-format="tif"/></figure>
</drawings>
<ep-reference-list id="ref-list">
<heading id="ref-h0001"><b>REFERENCES CITED IN THE DESCRIPTION</b></heading>
<p id="ref-p0001" num=""><i>This list of references cited by the applicant is for the reader's convenience only. It does not form part of the European patent document. Even though great care has been taken in compiling the references, errors or omissions cannot be excluded and the EPO disclaims all liability in this regard.</i></p>
<heading id="ref-h0002"><b>Patent documents cited in the description</b></heading>
<p id="ref-p0002" num="">
<ul id="ref-ul0001" list-style="bullet">
<li><patcit id="ref-pcit0001" dnum="US5892536A"><document-id><country>US</country><doc-number>5892536</doc-number><kind>A</kind><name>James D. Logan, Richard Goldhor and Daniel Goessling </name><date>19990406</date></document-id></patcit><crossref idref="pcit0001">[0002]</crossref></li>
<li><patcit id="ref-pcit0002" dnum="WO9831113A"><document-id><country>WO</country><doc-number>9831113</doc-number><kind>A</kind><date>19980716</date></document-id></patcit><crossref idref="pcit0002">[0002]</crossref><crossref idref="pcit0003">[0003]</crossref></li>
<li><patcit id="ref-pcit0003" dnum="EP0898278A"><document-id><country>EP</country><doc-number>0898278</doc-number><kind>A</kind></document-id></patcit><crossref idref="pcit0004">[0004]</crossref></li>
<li><patcit id="ref-pcit0004" dnum="US5577249A"><document-id><country>US</country><doc-number>5577249</doc-number><kind>A</kind></document-id></patcit><crossref idref="pcit0005">[0014]</crossref></li>
<li><patcit id="ref-pcit0005" dnum="US4918730A"><document-id><country>US</country><doc-number>4918730</doc-number><kind>A</kind></document-id></patcit><crossref idref="pcit0006">[0014]</crossref></li>
<li><patcit id="ref-pcit0006" dnum="US4739398A"><document-id><country>US</country><doc-number>4739398</doc-number><kind>A</kind></document-id></patcit><crossref idref="pcit0007">[0014]</crossref></li>
<li><patcit id="ref-pcit0007" dnum="US4697209A"><document-id><country>US</country><doc-number>4697209</doc-number><kind>A</kind></document-id></patcit><crossref idref="pcit0008">[0014]</crossref></li>
<li><patcit id="ref-pcit0008" dnum="US4542525A"><document-id><country>US</country><doc-number>4542525</doc-number><kind>A</kind></document-id></patcit><crossref idref="pcit0009">[0026]</crossref></li>
</ul></p>
</ep-reference-list>
</ep-patent-document>
