1. Field of the Invention
The present invention is related to playback of media such as music, and more particularly to techniques for allowing user control of media playback while conforming to applicable sound recording performance complement restrictions.
2. Description of the Background Art
For purposes of clarity, in the following description the terms “sound recording,” “song,” and “track” are used interchangeably. “Song-skipping” or “track-skipping” refers to skipping a song in its entirety. “Fast-forwarding” or “scanning” refers to skipping a portion of a song or playing a song more rapidly than the normal speed. The general term “skipping” refers to either song-skipping or fast-forwarding.
Internet radio, or webcasting, is becoming an increasingly popular delivery mechanism for music. A user installs player software on a conventional personal computer, and can usually specify preferences as to the types of music he or she is interested in. A music server selects sound recordings in accordance with the specified preferences, and transmits the sound recordings to the player over the Internet, using standard file transmission techniques. The player software outputs the music for the user.
Internet radio providers typically license the rights to sound recordings to be provided via webcasting. Under certain conditions, such a license can be obtained under the statutory license provisions of the Digital Millennium Copyright Act (DMCA). A statutory license is a form of blanket license that allows the provider to acquire rights to broadcast a large number of sound recordings without having to obtain separate licenses from each copyright holder.
In the United States, pursuant to 17 U.S.C. §114, statutory licenses are available only if certain conditions are met. One such condition is that the provider's transmission must not exceed a “sound recording performance complement,” which is defined as the transmission during any three-hour time period, on a particular channel, of not more than (A) three sound recordings from a particular album, including no more than two consecutive sound recordings from a particular album, or (B) four sound recordings by a particular artist or from a set or compilation of albums, including no more than three consecutive sound recordings by a particular artist or from a set or compilation of albums.
Many Internet radio providers use server-based software to select sound recordings to be transmitted; such software is usually specifically designed to generate a playlist in such a manner as to ensure that the sound recording performance complement is not exceeded. Thus, the algorithm for selecting sound recordings keeps track of which sound recordings have been selected, and makes sure that in any three-hour time period no more than the designated number of sound recordings from a particular album, by a particular artist, or from a set or compilation of albums, is transmitted.
Some player software programs allow users to skip unwanted songs and/or to fast-forward through a portion of a song. In response to a user clicking on an on-screen button or icon to song-skip or fast-forward, the player proceeds to the next song, skips a portion of the current song, or plays the current song more rapidly until the user releases the button.
When the user wishes to skip a song, the player may transmit a request that the music server begin transmitting the next song on the playlist. A player that periodically downloads transitory copies of songs may simply discard the copy of the currently playing song and start to play the next song.
When the user wishes to fast-forward, the player may transmit a request that the music server begin transmitting a subsequent portion of the current song; if appropriate, the player may discard the portion of the song that was skipped.
Such song-skipping and fast-forwarding functionality allows the user some flexibility in listening to webcast music. However, skipping in response to the user's requests may result in violation of the sound recording performance complement provisions of the DMCA. For example, song selection software may construct a playlist in which four Beatles songs appear during a three-hour time period, and a fifth Beatles song appears during the fourth hour; such a playlist would not normally exceed the sound recording performance complement provisions of the DMCA. However, if the user were to skip some of the intervening songs or fast-forward through them, the overall length of the playlist may be shortened so that the fifth Beatles song now falls within the three-hour time period. The playlist would then violate the sound recording performance complement requirements by including five Beatles songs within a three-hour time period.
What is needed is a system and method for enabling song-skipping and fast-forwarding (collectively referred to herein as “skipping”) by users, while ensuring that the sound recording performance complement provisions of the DMCA are not violated.
The present invention provides a mechanism that allows users to skip songs and/or to fast-forward through songs, while limiting the extent to which skipping is allowed in order to maintain conformance with sound performance complement restrictions such as those specified by the DMCA. If the user requests a skip that may result in a DMCA violation, the skip is disallowed and the request is denied.
The invention determines the limit to which skipping is permitted as follows. Playlists are constructed so that the sound recording performance complement limitations are applied to a longer time period than the period specified in the DMCA (the “DMCA period”, which is generally three hours). The amount by which the longer time period exceeds the DMCA period, referred to herein as “excess time,” can be preset to any desired amount.
The invention keeps track of a quantity, referred to herein as “slippage,” representing the amount of time that has been skipped by the user over the past X hours, where X is the length of the DMCA period. For example, X may equal three. Whenever the user skips a song or fast-forwards through a song, the invention increases slippage by the length of the skipped song or song portion. Updates to total slippage may be made incrementally, or upon the conclusion of each song, or upon conclusion of a block of songs. Once X hours have passed after the skip, slippage is reduced by the length of the skipped song or song portion; this process is referred to as “slippage expiry.”
The invention is implemented by maintaining a history of the user's skipping behavior over the last X hours, and updating the slippage quantity according to the maintained history.
If the user attempts to skip a song or song portion that would cause slippage to exceed the predetermined amount of excess time, the skip is disallowed. Thus, skips that would result in potential violations of the sound recording performance complement limitations of the DMCA are avoided.
If the user attempts to fast-forward through a song, the invention may permit fast-forwarding up to a point limited by the current slippage value, or alternatively the invention may disallow fast-forwarding entirely for a particular song whenever skipping the entire song would cause the maximum slippage to be exceeded.
In an alternative embodiment, songs are collected into blocks, and slippage is computed and updated on a block-by-block basis. The invention determines the total allowable amount of skipping at the beginning of the block, and skipping is enabled only for the songs in the block whose cumulative duration is less than the allowable amount of skipping. The amount of skipping done during the playing of the block can be computed by comparing the elapsed time it takes to play the block to the total length of all of the songs in the block. The degree to which the elapsed time is less than the total length of the songs in the block is the total amount of skipping that took place during the block.
For a block-oriented approach, if the skipping action is recorded as occurring at the time that the end of listening to the block is noted, then the limitations on user action are, in general, more conservative than would be incurred if the skipping is recorded at the time that it was actually done. This conservatism arises because some skipping is recorded at a later time than when it was actually done; thus, that skipping is generally kept in the history longer than is necessary, increasing the estimate of the skipping that the user has done and thus restricting skipping more than is strictly necessary. Similarly, if available skip time is computed at the beginning of a block, conservatism may also result, since a worst-case analysis requires that skipping is assumed to take place as early as possible within the block. However, despite these limitations, a block-oriented approach may be desirable in order to avoid excess complexity and processing time in determining total slippage.
In an alternative embodiment, actual and theoretical start times for songs can be retained. The difference between actual and theoretical start time for a song represents the total amount of slippage accumulated up to the beginning of that song. The difference between the accumulated slippage at a current point in time and the accumulated slippage at some previous point in time indicates the amount of slippage that has occurred in the intervening time period. According to this embodiment, theoretical start times can be computed by successively adding the lengths of each song to be played. Then, a history of actual start times, extending back as far as desired, can be maintained for each listener. Slippage over a given time period is determined based on how much the difference between theoretical and actual times has changed over the time period. Thus, no explicit expiration of slippage values need be done. Rather, the invention can simply discard start times that are older than the expiration period. This expiration period can correspond to the length of the DMCA period, as described above.
Limits on skipping may be implemented at the server or at the client. In one embodiment, the server can provide the client with an estimate of how much skipping is permitted for a block or a song, and the client can be responsible for disallowing skipping when the limit has been reached.
The FIGURES depict a preferred embodiment of the present invention for purposes of illustration only. One skilled in the art will readily recognize from the following discussion that alternative embodiments of the structures and methods illustrated herein may be employed without departing from the principles of the invention described herein.
The following description of system components and operation is merely exemplary of one embodiment of the present invention.
For illustrative purposes, the following description and examples describe the operation of the invention with respect to the particular sound recording performance complement provisions of the DMCA that specify that no more than four sound recordings by a particular artist be transmitted during a three-hour time period. However, one skilled in the art will recognize that the same principles and methods can be applied to other sound recording performance complement provisions of the DMCA or other restrictions imposed for legal or other reasons. For example, the technique of the present invention can be applied to limit the number of recordings from a particular album or set or compilation of albums, the number of consecutive recordings from a particular album, the number of consecutive recordings by a particular artist, and the like. Furthermore, the three-hour time period specified by the DMCA is merely an example, and any time period can be used. Finally, the techniques of the present invention can be applied to songs, song segments, video programs, radio programs, or any other type of transmissions.
System
Referring now to
Player 305 may be implemented as a software program that runs on client machine 301. Player 305 may be a stand-alone software application, or a plug-in for a larger application such as a browser. User 306 interacts with player 305 via a graphical user interface that provides buttons, menus, icons, and the like for controlling the operation of player 305. In particular, user 306 can activate and deactivate player 305, control the volume of output, pause, skip tracks or songs, and/or fast-forward. Some of these functions may be selectively limited or disabled according to the techniques of the present invention, as will be described in more detail below. Player 305 may also provide various configuration options to allow user 306 to select the appearance of the graphical user interface, the type of music played, and the like.
In one embodiment, music data is temporarily stored in buffer 309 when it is received from application 321. Player 305 reads music data from buffer 309 as it is needed. Buffer 309 may be implemented in random access memory of client machine 301, or in secondary storage such as a hard drive. The use, management, and operation of buffer 309 for purposes of implementing streaming audio are well known in the art.
In one embodiment, music server application 321 runs on a remote server 320 and responds to requests for music received from player 305 (as well as from other players on other machines). Application 321 obtains digital music data from database 322 and transmits the music data across the Internet 330 to player 305. In one embodiment, for each song it plays, player 305 obtains metadata including, for example, song title, artist, song length, album, and the like. Such information may be provided by application 321 from information in database 322, or it may be entered by user 306, or it may be obtained by other means. Metadata may be used for implementing sound performance complement limitations according to the techniques of the present invention; for example, player 305 may allow or deny a requested song skip based on the length of the song, as determined from the metadata for the song.
In one embodiment, player 305 includes controls that allow user 306 to skip unwanted songs or to fast-forward through a portion of a song. For example, user 306 can click on an on-screen button or icon to song-skip or fast-forward, causing player 305 to proceed to the next song in a playlist, or to skip a portion of the current song, or to play the current song more rapidly until user 306 releases the button. When user 306 indicates that he or she wishes to skip a song or fast-forward, player 305 may transmit a request that server 320 begin transmitting subsequently needed song data, or, if data is already available in buffer 309, player 305 interacts with buffer 309 and instructs buffer 309 to discard skipped songs or portions as appropriate.
In one embodiment, the present invention is implemented as a mechanism for disallowing skipping under certain circumstances as will be described in more detail below. The invention can therefore be implemented at either client machine 301 or server 320. If the present invention is implemented at client machine 301, certain buttons or icons on player 305 may disappear, or their appearance may change, to indicate that skipping is limited or disallowed at a given time. Attempts to activate skipping at such times will be ignored by player 305. If the invention is implemented at server 320, requests for skips are still transmitted from player 305 to server 320, but application 321 ignores the received requests when it is appropriate to do so.
Sound Recording Performance Complement Limitations
Under certain circumstances, skipping songs or fast-forwarding through portions of songs may result in violation of the sound recording performance complement provisions of the DMCA. For example, if four Beatles songs appear in a playlist that is normally played during a three-hour time period, and a fifth Beatles song appears during the fourth hour, the sound recording performance complement would not be exceeded. However, if the user skips some of the intervening songs or fast-forwards through them, the overall length of the playlist may be shortened so that the fifth Beatles song now falls within the three-hour time period. The playlist would then violate the sound recording performance complement requirements by including five Beatles songs within a three-hour time period.
For illustrative purposes, the following discussion and accompanying FIGURES refer to the sound recording performance complement limitations of the DMCA that prohibit transmission of more than four sound recordings by a particular artist during a three-hour time period. Similar principles and techniques can be applied to the DMCA limitations of the number of recordings from a particular album, or for any other similar types of limitations.
Referring now to
Referring now to
Referring now to
The present invention provides a mechanism that allows user 306 to skip songs or to fast-forward through songs, but only to a limited extent. If the user requests a skip that may result in a DMCA violation, the skip is disallowed and the request is ignored.
The invention determines the limit to which skipping is permitted by constructing playlists 701 in such a manner that the sound recording performance complement limitations are applied to a longer time period than the DMCA period. The amount by which the longer time period exceeds the DMCA period, referred to herein as “excess time,” can be preset to any desired amount. In the examples shown herein, the DMCA period is three hours, and the excess time period is two hours, although one skilled in the art will recognize that any time period may be used.
In one embodiment, client machine 301 keeps track of “slippage,” representing the amount of time that has been skipped by user 306 over the past X hours, where X is the length of the DMCA period. Whenever user 306 skips a song or fast-forwards through a song, client 301 increases slippage by the length of the skipped song or song portion. In one embodiment, the increase in slippage is determined by subtracting the amount of time taken to perform the skip from the amount of time skipped. Thus, if two minutes (2:00) of music were skipped in five seconds (0:05), slippage would be increased by one minute and fifty-five seconds (1:55). Updates to total slippage may be made incrementally or upon the conclusion of each song. Once X hours have passed after the skip, slippage is reduced by the length of the skipped song or song portion (slippage expiry).
If user 306 attempts to skip a song or song portion that would cause slippage to exceed the predetermined amount of excess time, the skip is disallowed. Thus, skips that would result in potential violations of the sound recording performance complement limitations of the DMCA are avoided.
The invention is implemented by maintaining, at client machine 301, a history of the user's skipping behavior over the last X hours, and updating the slippage quantity according to the maintained history. In an alternative embodiment, server 320, rather than client machine 301, keeps track of slippage and disallows skips when appropriate to do so.
Referring now to
Referring now to
Referring now to
Method
Referring now to
A slippage amount is initialized 402. Typically, at the beginning of a music program, slippage is initialized to zero. Slippage may be stored in any convenient memory location for easy access and updating when appropriate.
Player 305 begins 403 playing music. This step may include making requests to application 321 on server 320 as needed to obtain music data, and receiving music data across the Internet 330. Music may be temporarily stored in buffer 309, according to well-known techniques.
As music is playing, player 305 periodically checks 409 whether sufficient time has elapsed for previously added slippage to expire. In one embodiment, this determination 409 is only made if the current slippage amount is non-zero. Determination 409 is made, for example, by referring to a stored log of previous skips, to determine whether any of the previous skips occurred at a time sufficiently far in the past. If sufficient time has elapsed for slippage to expire, player 305 reduces 410 the slippage amount by the expired amount.
Whether or not any slippage has expired, player 305 continues 411 to play music. If user 306 requests 412 a skip, player 305 determines 405 whether the skip would exceed the slippage limit. Determination 405 is made by ascertaining whether the sum of the amount of music to be skipped and the current slippage amount exceed the slippage limit. If the limit would be exceeded, player 305 ignores 406 the skip request. In one embodiment, when a skip is disallowed, an on-screen message is displayed to inform user 306 that the skip is not permitted.
If the limit would not be exceeded, player 305 proceeds 407 with the skip, advancing music play as requested and communicating with application 321 as needed to obtain additional music data. Player 305 stores 413 information describing the amount of the skip and the time the skip occurred, so that it can later determine when the slippage associated with the skip should expire. Player 305 increases 408 the slippage amount by the skipped amount.
Implementation
In one embodiment, the skip limitations of the present invention are enforced as follows. Player 305 stores, in RAM or in secondary storage, a history of skips that have been requested and executed. The history is kept for at least a period of time equal to the DMCA period. For each skip, player 305 stores the time that the skip took place and the amount of music that was skipped. As described above, the latter quantity may be reduced by the amount of actual time taken to perform the skip. Alternatively, start times and lengths, or actual and theoretical start times, may be stored. One skilled in the art will recognize that such alternatives are mathematically equivalent, and that other equivalent alternatives could also be used.
Player 305 can also keep track of a current slippage value, or it can compute this number at any time by adding the amounts for all skips that took place within a window of time defined by the DMCA period. This sum can be determined, for example, at the beginning of each song to determine whether or not to allow skipping during that song. In one embodiment, player 305 disables skipping for any part of a song whenever skipping the entire song would cause a violation of the sound recording complement. Such a restriction may be stricter than necessary under DMCA provisions, but in some embodiments may be easier to implement than performing real-time assessment of whether and how much skipping is permitted.
In an alternative embodiment, songs are grouped into blocks, each containing one or more songs. Referring now to
Slippage value is initialized 602, typically to a value of 0:00:00, before any songs 101 are played. Player 305 begins 603 block 501. Player 305 determines 604 the allowable amount of skipping for current block 501 based on the current slippage value at the beginning of the block. For example, as shown in
As player 305 plays music 605 from block 501, it detects user requests 606 for skips. Player 305 determines 607 whether the requested skip would exceed the remaining allowable slippage. If the allowable slippage would be exceeded, player 305 denies 609 the skip (or in an alternative embodiment, allows a portion of the skip corresponding to the remaining allowable slippage, but denies the remainder of the skip). If the allowable slippage would not be exceeded, player 305 allows 608 the skip.
In the example of
In one embodiment, the current slippage amount is increased whenever a skip is allowed. In another embodiment, when the end of block 501 is reached 610, if new blocks are to be played 611, player 305 determines 612 a new slippage value as follows. The total elapsed time to play block 501 (determined by a real-time counter, or by comparing the start time with the end time for block playback) is subtracted from the total track time for the songs in block 501 (determined by summing song lengths for songs 101 in block 501); the result is the amount skipped during block 501. This amount is added to the current slippage value. Any expired slippage (slippage that took place sufficiently long ago to be outside the DMCA window, such as three hours) is subtracted from the current slippage value. Player 305 then proceeds 613 with the next block 501.
In the example of
Block 501B has a total track time of 0:37:25, whereas the elapsed time to play block 501B was 0:23:17. Thus, player 305 determines that a total of 0:14:08 was skipped during block 501B. This amount of time is added to the slippage value of 1:50:39. Player 305 also determines that 0:08:03 of slippage has expired, and subtracts this amount from the slippage value. The net result is a current slippage value of 1:56:44 at the end of block 501B.
In Block 501C, the user attempts two skips. The skip of song 101EN is allowed, because it does not cause the slippage value to exceed the limit of 2:00:00. However the skip of song 101EQ is disallowed, because it would result in excess slippage. Once block 501C has ended, player 305 determines, a new slippage value, as follows. Block 501C has a total track time of 0:24:03, whereas the elapsed time to play block 501C was 0:20:43. Thus, player 305 determines that a total of 0:03:20 was skipped during block 501C (the disallowed skip is not included in this total). This amount of time is added to the slippage value of 1:56:44. Player 305 also determines that 0:04:30 of slippage has expired, and subtracts this amount from the slippage value. The net result is a current slippage value of 1:55:34 at the end of block 501C.
In one embodiment, skipping is permitted only for the songs in a block whose cumulative duration is less than the allowable amount of skipping. The amount of skipping that was done during the playing of the block is determined by comparing the elapsed time required to play the block to the total length of all of the songs in the block. The degree to which the elapsed time is less than the total length of the songs in the block is the total amount of skipping done during the block. Player 305 adjusts the slippage value (increasing it when songs are skipped and decreasing it once the DMCA period passes since the increase), at the end of each block.
In one embodiment, player 305 records any skipping during the block as having occurred at the time that the block ends. When such a technique is used, the limitations on user action are in general more conservative than they would be if skipping were recorded in real-time. This conservatism arises because some skipping is recorded at a later time than the time at which it actually takes place; expiry of the skipping history may therefore take place later than it otherwise would be. Accordingly such a technique increases the estimate of the skipping that the user has done and thus restricts the availability of the skip feature more than is strictly necessary. However, in some applications, such a methodology may be advantageous because of the reduced overhead associated with updating slippage values at the end of blocks rather than in real-time.
In another embodiment, a modified block-oriented approach is used. As described above, songs are grouped into blocks, each containing one or more songs. As user 306 skips songs or song portions during a block, player 305 accumulates an amount corresponding to the skipped amount. If skipping exceeds or equals the permissible amount for that block, then skipping is disallowed for the remainder of the block. Such a technique allows user 306 to skip more songs than would be allowed in the previously described block implementation, without violating the sound performance complement provisions of the DMCA.
In another embodiment, the above-described block-oriented approach is modified so that player 305 estimates, based on past behavior, how many of the songs in a block that user 306 is likely to skip. If it is unlikely that the user would skip more songs than are allowable, then player 305 can allow skipping for all of the songs in the block on the theory that the user is unlikely to skip so many songs in the block as to actually reach the limit. Using such a technique, although sound performance complement limitations are not strictly enforced, violations can be made very rare.
In another embodiment, the above-described block-oriented approach is modified as follows. Player 305 reports times of the skipping events that occur within the block when the next block is requested. Thus, individual skipping events are recorded in the history at very nearly the time that they actually occurred. Such a technique allows the discarding of events from the history (due to expiry of the slippage value) to be performed on a more accurate, less conservative basis, without increasing the likelihood of a violation of the sound performance complement provisions of the DMCA.
In yet, another embodiment, player 305 is given an estimate of how much skipping is to be allowed within the block and can disable the skip button when this limit is reached. This system has the virtue that the degree of conservatism is limited so that the user is allowed to skip as much as possible (although still subject to the limitations resulting from determining allowable skipping at the beginning of each block), while still strictly conforming to the sound performance complement limitations of the DMCA. Such an alternative can be combined with the reporting of the timing of each skip event to the server so that the skipping allowable at the beginning of each block can be computed accurately.
The present invention can limit the potential for fraud by enforcing skip limitations at server 320 rather than at player 305. Server 320 can note when excess skipping is occurring by noting when new songs or blocks are requested. Once a listener is noted to have consistently requested songs or blocks at a higher than possible rate, server 320 can refuse to honor requests from that user.
In another embodiment, if a playlist includes tracks that may be skipped (skippable tracks) as well as tracks that, if skipped, would result in violations of sound recording performance complement violations (non-skippable tracks), server 320 does not transmit the entire playlist to player 305. Rather, server 320 transmits only a subset of the playlist, so that all tracks in the playlist are skippable or non-skippable. In this manner, the system of the invention avoids the need to make assumptions as to which tracks in a playlist the user may or may not skip in the playlist.
Referring now to
In 701A, indicator 702A is at the beginning of the playlist. Slippage is initialized at 0:00.
In 701B, 2:31 into the playlist, during playback of song 101GB, the user requests a song skip. This song skip may be activated, for example, by the user clicking on an on-screen button or icon representing a song skip. Player 305 advances to the beginning of next song 101GC, which corresponds to a point 9:38 into the playlist. Since 7:07 of the playlist have been skipped, slippage is incremented to 7:07.
In 701C, 15:13 into the playlist, during playback of song 101GD, the user requests another song skip. Player 305 advances to the beginning of next song 101GE, which corresponds to a point 15:59 into the playlist. Since 0:46 of the playlist have been skipped, 0:46 is added to the slippage quantity, for a running total of 7:53.
In 701D, the user requests that song 101GE be skipped in its entirety. Player 305 advances to the beginning of next song 101GF, which corresponds to a point 19:40 into the playlist. Since 3:41 of the playlist have been skipped (corresponding to the length of song 101GE), 3:41 is added to the slippage quantity, for a running total of 11:34.
In 701E, 2:51:10 into the playlist, during playback of song 101GH, the user requests another song skip. Player 305 advances to the beginning of next song 101GI, which corresponds to a point 2:58:10 into the playlist. Since 7:00 of the playlist have been skipped, 7:00 is added to the slippage quantity, for a running total of 18:34.
In 701F, 3:11:00 into the playlist, over three hours have elapsed since 701B, so the time skipped in 701B is now outside the three-hour window specified by the DMCA. Accordingly, slippage is reduced by 7:07, which corresponds to the time skipped in 701B. In one embodiment, the amount by which to reduce slippage and the time at which to do so is determined by keeping track of previous skips. Reducing the slippage total by 7:07 yields 11:27 as the current slippage value. In one embodiment, the invention checks for slippage “expiry” at the end of each song; in another embodiment, the invention periodically makes such checks; in a third embodiment, the invention checks for slippage expiry when the slippage amount is about to be increased due to another skip request by the user; in a fourth embodiment, the difference in accumulated slippage between the current time and a point in time three hours ago is used to compute slippage during the intervening time period.
In 701G, 3:20:11 into the playlist, over three hours have elapsed since 701D, so the time skipped in 701C and 701D is now outside the three-hour window specified by the DMCA. Accordingly, slippage is reduced by 0:46, which corresponds to the time skipped in 701C, and by an additional 3:41, which corresponds to the time skipped in 701D. In addition, in 701G, during playback of song 101GJ, the user requests another song skip. Player 305 advances to the beginning of next song 101GK, which corresponds to a point 3:23:01 into the playlist. Since 2:50 of the playlist have been skipped, 2:50 is added to the slippage quantity. The subtraction of 0:46 and 3:41, plus the addition of 2:50, results in a running total of 9:50.
Referring now to
For illustrative purposes, in
In 701B, 2:31 into the playlist, during playback of song 101GB, the user requests a song skip. Player 305 advances to the beginning of next song 101GC, which corresponds to a point 9:38 into the playlist. Since 7:07 of the playlist have been skipped, slippage is incremented to 7:07, for a running total of 1:57:13.
In 701C, 15:13 into the playlist, during playback of song 101GD, the user requests another song skip. Player 305 advances to the beginning of next song 101GE, which corresponds to a point 15:59 into the playlist. Since 0:46 of the playlist have been skipped, 0:46 is added to the slippage quantity, for a running total of 1:57:59.
In 701D, the user requests that song 101GE be skipped in its entirety. Song 101GE is 3:41 long. Skipping song 101GE would cause slippage to increase to 2:01:40. Since this would exceed the permissible limit of 2:00:00, and would therefore potentially result in a DMCA violation, the user's requested skip is disallowed. In one embodiment, the icon or button for skipping songs is “grayed out” or otherwise indicated as disabled, whenever a song skip would result in excess slippage. At any rate, the invention continues playing song 101GE and ignores the user's request. The slippage value remains unchanged at 1:57:59.
Similarly, in 701E, when the user requests that part of song 101GH be skipped, which would result in an increase of the slippage value to 2:04:59, the user's requested skip is disallowed. In one embodiment, the request is disallowed whenever skipping the entire song would result in excess slippage, even if the user's request is to skip only a portion of the song that would not in itself result in excess slippage. In another embodiment, a skip request is allowed as long as the skipped portion itself does not result in excess slippage. In yet another embodiment, a portion of the skip request may be allowed, so that player 305 carries out the skip as far as possible without exceeding total slippage limits.
Referring now to
In 701A, indicator 702A is at the beginning of the playlist. Slippage is initialized at 0:00.
In 701B, 2:31 into the playlist, during playback of song 101GB, the user fast-forwards to a point in song 101GC that is 9:50 into the playlist. This fast-forward operation may be activated, for example, by the user clicking or holding down an on- screen button or icon representing fast-forward, and clicking again or releasing the button or icon when he or she wishes to resume normal playback. Player 305 advances to the specified point 9:50 into the playlist. Since 7:19 of the playlist have been skipped, slippage is incremented to 7:19. As mentioned above, in an alternative embodiment, the amount of time taken to fast-forward would be subtracted from the 7:19.
In 701C, 15:13 into the playlist, during playback of song 101GD, the user requests a song skip. Player 305 advances to the beginning of next song 101GE, which corresponds to a point 15:59 into the playlist. Since 0:46 of the playlist have been skipped, 0:46 is added to the slippage quantity, for a running total of 8:05.
In 701D, 15:59 into the playlist at the beginning of playback of song 101GE, the user fast-forwards to a point in song 101GE that is 19:10 into the playlist. Player 305 advances to the specified point 19:10 into the playlist. Since 3:11 of the playlist have been skipped, slippage is incremented to 11:16.
In 701E, 2:51:10 into the playlist, during playback of song 101GH, the user fast-forwards to a point in song 101GI that is 3:03:17 into the playlist. Player 305 advances to the specified point 3:03:17 into the playlist. Since 12:07 of the playlist have been skipped, slippage is incremented to 23:23.
In 701F, 3:11:00 into the playlist, over three hours have elapsed since 701B, so the time skipped in 701B is now outside the three-hour window specified by the DMCA. Accordingly, slippage is reduced by 7:19, which corresponds to the time skipped in 701B. Reducing the slippage total by 7:19 yields 16:04 as the current slippage value.
In 701G, 3:20:11 into the playlist, over three hours have elapsed since 701D, so the time skipped in 701C and 701D is now outside the three-hour window specified by the DMCA. Accordingly, slippage is reduced by 0:46, which corresponds to the time skipped in 701C, and by an additional 3:11, which corresponds to the time skipped in 701D. In addition, in 701G, during playback of song 101GJ, the user fast-forwards to a point in song 101GJ that is 3:21:45 into the playlist. Player 305 advances to the specified point 3:21:45 into the playlist. Since 1:34 of the playlist have been skipped, slippage is incremented to 13:41.
Referring now to
For illustrative purposes, in
In 701B, 2:31 into the playlist, during playback of song 101GB, the user fast-forwards to a point in song 101GC that is 9:50 into the playlist. Player 305 advances to the specified point 9:50 into the playlist. Since 7:19 of the playlist have been skipped, slippage is incremented to 1:55:25.
In 701C, 15:13 into the playlist, during playback of song 101GD, the user requests a song skip. Player 305 advances to the beginning of next song 101GE, which corresponds to a point 15:59 into the playlist. Since 0:46 of the playlist have been skipped, 0:46 is added to the slippage quantity, for a running total of 1:56:11.
In 701D, 15:59 into the playlist at the beginning of playback of song 101GE, the user fast-forwards to a point in song 101GE that is 19:10 into the playlist. Player 305 advances to the specified point 19:10 into the playlist. Since 3:11 of the playlist have been skipped, slippage is incremented to 1:59:22.
In 701E, 2:51:10 into the playlist, during playback of song 101GH, the user attempts to fast-forward to a point in song 101GI that is 3:03:17 into the playlist. Such an operation would result in excess slippage, since the skip of 12:07 added to the current slippage value of 1:59:22 results in a total of 2:11:29. In one embodiment, the requested skip is carried out only to the extent that it complies with the limit on slippage. Thus, player 305 fast-forwards by 0:48 and total slippage is incremented to 2:00:00. Further fast-forwarding is disabled, at least until slippage falls below 2:00:00. In another embodiment, when the user requests a fast-forward operation that would exceed allowable slippage, no fast-forwarding is performed, and the user's request is ignored. Player 305 advances to the specified point 3:03:17 into the playlist. Since 12:07 of the playlist have been skipped, slippage is incremented to 23:23.
The above-described examples illustrate the operation of the invention in several embodiments, in response to both song-skipping and fast-forwarding operations. They further illustrate the technique by which the present invention disallows or shortens skips when total slippage limits have been reached.
In the above description, for purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of the invention. It will be apparent, however, to one skilled in the art that the invention can be practiced without these specific details. In other instances, structures and devices are shown in block diagram form in order to avoid obscuring the invention.
Reference in the specification to “one embodiment” or “an embodiment” means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment of the invention. The appearances of the phrase “in one embodiment” in various places in the specification are not necessarily all referring to the same embodiment.
Some portions of the detailed description are presented in terms of algorithms and symbolic representations of operations on data bits within a computer memory. These algorithmic descriptions and representations are the means used by those skilled in the data processing arts to most effectively convey the substance of their work to others skilled in the art. An algorithm is here, and generally, conceived to be a self-consistent sequence of steps leading to a desired result. The steps are those requiring physical manipulations of physical quantities. Usually, though not necessarily, these quantities take the form of electrical or magnetic signals capable of being stored, transferred, combined, compared, and otherwise manipulated. It has proven convenient at times, principally for reasons of common usage, to refer to these signals as bits, values, elements, symbols, characters, terms, numbers, or the like.
It should be borne in mind, however, that all of these and similar terms are to be associated with the appropriate physical quantities and are merely convenient labels applied to these quantities. Unless specifically stated otherwise as apparent from the discussion, it is appreciated that throughout the description, discussions utilizing terms such as “processing” or “computing” or “calculating” or “determining” or “displaying” or the like, refer to the action and processes of a computer system, or similar electronic computing device, that manipulates and transforms data represented as physical (electronic) quantities within the computer system's registers and memories into other data similarly represented as physical quantities within the computer system memories or registers or other such information storage, transmission or display devices.
The present invention also relates to an apparatus for performing the operations herein. This apparatus may be specially constructed for the required purposes, or it may comprise a general-purpose computer selectively activated or reconfigured by a computer program stored in the computer. Such a computer program may be stored in a computer readable storage medium, such as, but is not limited to, any type of disk including floppy disks, optical disks, CD-ROMs, and magnetic-optical disks, read-only memories (ROMs), random access memories (RAMs), EPROMs, EEPROMs, magnetic or optical cards, or any type of media suitable for storing electronic instructions, and each coupled to a computer system bus.
The algorithms and displays presented herein are not inherently related to any particular computer, network of computers, or other apparatus. Various general-purpose systems may be used with programs in accordance with the teachings herein, or it may prove convenient to construct more specialized apparatus to perform the required method steps. The required structure for a variety of these systems appears from the description. In addition, the present invention is not described with reference to any particular programming language. It will be appreciated that a variety of programming languages may be used to implement the teachings of the invention as described herein.
As will be understood by those familiar with the art, the invention may be embodied in other specific forms without departing from the spirit or essential characteristics thereof. For example, the particular architectures depicted above are merely exemplary of one implementation of the present invention. The functional elements and method steps described above are provided as illustrative examples of one technique for implementing the invention; one skilled in the art will recognize that many other implementations are possible without departing from the present invention as recited in the claims. Likewise, the particular capitalization or naming of the modules, protocols, features, attributes, or any other aspect is not mandatory or significant, and the mechanisms that implement the invention or its features may have different names or formats. In addition, the present invention may be implemented as a method, process, user interface, computer program product, system, apparatus, or any combination thereof. Accordingly, the disclosure of the present invention is intended to be illustrative, but not limiting, of the scope of the invention, which is set forth in the following claims.
The present application is a continuation-in-part of U.S. patent application Ser. No. 09/846,823 for “Relationship Discovery Engine,” filed Apr. 30, 2001, the disclosure of which is incorporated herein by reference.
Number | Name | Date | Kind |
---|---|---|---|
3568156 | Thompson | Mar 1971 | A |
4384329 | Rosenbaum et al. | May 1983 | A |
4833610 | Zamora | May 1989 | A |
5062143 | Schmitt | Oct 1991 | A |
5182708 | Ejiri | Jan 1993 | A |
5241674 | Kuorsawa | Aug 1993 | A |
5303150 | Komeda | Apr 1994 | A |
5303302 | Burrows | Apr 1994 | A |
5371807 | Register | Dec 1994 | A |
5392212 | Geist | Feb 1995 | A |
5404505 | Levinson | Apr 1995 | A |
5418951 | Damashek | May 1995 | A |
5497488 | Akizawa | Mar 1996 | A |
5499046 | Schiller et al. | Mar 1996 | A |
5539635 | Larson, Jr. | Jul 1996 | A |
5548507 | Martino | Aug 1996 | A |
5583763 | Atcheson | Dec 1996 | A |
5592511 | Schoen | Jan 1997 | A |
5608622 | Church | Mar 1997 | A |
5616876 | Cluts | Apr 1997 | A |
5661787 | Pocock | Aug 1997 | A |
5675786 | McKed | Oct 1997 | A |
5678054 | Shibata | Oct 1997 | A |
5706365 | Rangarajan | Jan 1998 | A |
5708709 | Rose | Jan 1998 | A |
5713016 | Hill | Jan 1998 | A |
5721827 | Logan | Feb 1998 | A |
5726909 | Krikorian | Mar 1998 | A |
5740134 | Peterson | Apr 1998 | A |
5751672 | Yankowsky | May 1998 | A |
5754938 | Herz | May 1998 | A |
5758257 | Herz | May 1998 | A |
5764235 | Hunt | Jun 1998 | A |
5774357 | Hoffberg | Jun 1998 | A |
5790423 | Lan et al. | Aug 1998 | A |
5790935 | Payton | Aug 1998 | A |
5809246 | Goldman | Sep 1998 | A |
5819160 | Foladare | Oct 1998 | A |
5842010 | Jain | Nov 1998 | A |
5862220 | Perlman | Jan 1999 | A |
5862339 | Bonnaure | Jan 1999 | A |
5864868 | Contois | Jan 1999 | A |
5872921 | Zahariev | Feb 1999 | A |
5881234 | Schwab | Mar 1999 | A |
5883986 | Kopec | Mar 1999 | A |
5884312 | Dustan | Mar 1999 | A |
5898833 | Kidder | Apr 1999 | A |
5913040 | Rakavy | Jun 1999 | A |
5913041 | Ramanathan | Jun 1999 | A |
5926207 | Vaughan | Jul 1999 | A |
5930526 | Iverson | Jul 1999 | A |
5930768 | Hooban | Jul 1999 | A |
5931907 | Davies | Aug 1999 | A |
5941951 | Day | Aug 1999 | A |
5945988 | Williams | Aug 1999 | A |
5950189 | Cohen | Sep 1999 | A |
5956482 | Agraharam | Sep 1999 | A |
5960430 | Haimowitz | Sep 1999 | A |
5969283 | Looney | Oct 1999 | A |
5977964 | Williams | Nov 1999 | A |
5983176 | Hoffert | Nov 1999 | A |
5987525 | Roberts | Nov 1999 | A |
5996015 | Day | Nov 1999 | A |
6000008 | Simcoe | Dec 1999 | A |
6009382 | Martino et al. | Dec 1999 | A |
6012098 | Bayeh | Jan 2000 | A |
6020883 | Herz | Feb 2000 | A |
6021203 | Douceur | Feb 2000 | A |
6026398 | Brown | Feb 2000 | A |
6026439 | Chowdhury | Feb 2000 | A |
6029195 | Herz | Feb 2000 | A |
6031795 | Wehmeyer | Feb 2000 | A |
6031797 | Van Ryzin | Feb 2000 | A |
6035268 | Carus | Mar 2000 | A |
6038527 | Renz | Mar 2000 | A |
6038591 | Wolfe | Mar 2000 | A |
6047251 | Pon | Apr 2000 | A |
6047268 | Bartoli | Apr 2000 | A |
6047320 | Tezuka | Apr 2000 | A |
6047327 | Tso | Apr 2000 | A |
6052717 | Reynolds | Apr 2000 | A |
6061680 | Scherf | May 2000 | A |
6064980 | Jacobi | May 2000 | A |
6065051 | Steele | May 2000 | A |
6065058 | Hailpern | May 2000 | A |
6070185 | Anupam | May 2000 | A |
6085242 | Chandra | Jul 2000 | A |
6097719 | Benash | Aug 2000 | A |
6102406 | Miles | Aug 2000 | A |
6105022 | Takahashi | Aug 2000 | A |
6131082 | Hargrave, III et al. | Oct 2000 | A |
6134532 | Lazarus | Oct 2000 | A |
6138142 | Linsk | Oct 2000 | A |
6154773 | Roberts et al. | Nov 2000 | A |
6161132 | Roberts et al. | Dec 2000 | A |
6161139 | Win et al. | Dec 2000 | A |
6167369 | Schulze | Dec 2000 | A |
6182142 | Win | Jan 2001 | B1 |
6185560 | Young | Feb 2001 | B1 |
6192340 | Abecassis | Feb 2001 | B1 |
6205126 | Moon | Mar 2001 | B1 |
6222980 | Asai et al. | Apr 2001 | B1 |
6225546 | Kraft | May 2001 | B1 |
6230192 | Roberts | May 2001 | B1 |
6230207 | Roberts | May 2001 | B1 |
6240459 | Roberts | May 2001 | B1 |
6246672 | Lumelsky | Jun 2001 | B1 |
6249810 | Kiraly | Jun 2001 | B1 |
6252988 | Ho | Jun 2001 | B1 |
6263313 | Milsted | Jul 2001 | B1 |
6272456 | de Campos | Aug 2001 | B1 |
6272495 | Hetherington | Aug 2001 | B1 |
6282548 | Burner | Aug 2001 | B1 |
6292795 | Peters et al. | Sep 2001 | B1 |
6298446 | Schreiber | Oct 2001 | B1 |
6314421 | Sharnoff | Nov 2001 | B1 |
6317761 | Landsman | Nov 2001 | B1 |
6321205 | Eder | Nov 2001 | B1 |
6321221 | Bieganski | Nov 2001 | B1 |
6330593 | Roberts | Dec 2001 | B1 |
6343317 | Glorikian | Jan 2002 | B1 |
6353849 | Linsk | Mar 2002 | B1 |
6370315 | Mizuno | Apr 2002 | B1 |
6370513 | Kolawa | Apr 2002 | B1 |
6389467 | Eyal | May 2002 | B1 |
6405203 | Collart | Jun 2002 | B1 |
6430539 | Lazarus | Aug 2002 | B1 |
6434535 | Kupka | Aug 2002 | B1 |
6434621 | Pezzillo et al. | Aug 2002 | B1 |
6438579 | Hosken | Aug 2002 | B1 |
6487598 | Valencia | Nov 2002 | B1 |
6490553 | Van Thong et al. | Dec 2002 | B2 |
6505203 | Levy | Jan 2003 | B1 |
6512763 | DeGolia, Jr. | Jan 2003 | B1 |
6513061 | Ebata | Jan 2003 | B1 |
6522769 | Rhoads | Feb 2003 | B1 |
6526411 | Ward | Feb 2003 | B1 |
6532477 | Tang | Mar 2003 | B1 |
6535854 | Buchner | Mar 2003 | B2 |
6538996 | West | Mar 2003 | B1 |
6557026 | Stephens, Jr. | Apr 2003 | B1 |
6560403 | Tanaka | May 2003 | B1 |
6560704 | Dieterman | May 2003 | B2 |
6587127 | Leeke | Jul 2003 | B1 |
6611812 | Hurtado | Aug 2003 | B2 |
6611813 | Bratton | Aug 2003 | B1 |
6614914 | Rhoads | Sep 2003 | B1 |
6615208 | Behrens | Sep 2003 | B1 |
6655963 | Horvitz | Dec 2003 | B1 |
6657117 | Weare | Dec 2003 | B2 |
6658151 | Lee | Dec 2003 | B2 |
6661787 | O'Connell | Dec 2003 | B1 |
6677894 | Sheynblat | Jan 2004 | B2 |
6725446 | Hahn | Apr 2004 | B1 |
6741980 | Langseth | May 2004 | B1 |
6757740 | Parekh | Jun 2004 | B1 |
6807632 | Carpentier | Oct 2004 | B1 |
6889383 | Jarman | May 2005 | B1 |
6925441 | Jones, III | Aug 2005 | B1 |
6952523 | Tanaka | Oct 2005 | B2 |
7028082 | Rosenberg et al. | Apr 2006 | B1 |
20010005823 | Fischer | Jun 2001 | A1 |
20010042107 | Palm | Nov 2001 | A1 |
20010042109 | Bolas et al. | Nov 2001 | A1 |
20010044855 | Vermeire | Nov 2001 | A1 |
20010052028 | Roberts | Dec 2001 | A1 |
20010055276 | Rogers | Dec 2001 | A1 |
20020002039 | Qureshey et al. | Jan 2002 | A1 |
20020004839 | Wine et al. | Jan 2002 | A1 |
20020007418 | Hegde et al. | Jan 2002 | A1 |
20020010621 | Bell | Jan 2002 | A1 |
20020010714 | Hetherington | Jan 2002 | A1 |
20020010789 | Lord | Jan 2002 | A1 |
20020013852 | Janik | Jan 2002 | A1 |
20020016839 | Smith | Feb 2002 | A1 |
20020035561 | Archer | Mar 2002 | A1 |
20020045717 | Grenda | Apr 2002 | A1 |
20020056004 | Smith | May 2002 | A1 |
20020065857 | Michalewicz | May 2002 | A1 |
20020082901 | Dunning | Jun 2002 | A1 |
20020095387 | Sosa | Jul 2002 | A1 |
20020099696 | Prince | Jul 2002 | A1 |
20020099737 | Porter | Jul 2002 | A1 |
20020111912 | Hunter | Aug 2002 | A1 |
20020129123 | Johnson | Sep 2002 | A1 |
20020152204 | Ortega et al. | Oct 2002 | A1 |
20020175941 | Hand | Nov 2002 | A1 |
20030002608 | Glenn | Jan 2003 | A1 |
20030007507 | Rajwan et al. | Jan 2003 | A1 |
20030018797 | Dunning et al. | Jan 2003 | A1 |
20030028796 | Roberts | Feb 2003 | A1 |
20030046283 | Roberts | Mar 2003 | A1 |
20030083871 | Foote | May 2003 | A1 |
20030093476 | Syed | May 2003 | A1 |
20030133453 | Makishima | Jul 2003 | A1 |
20030135513 | Quinn | Jul 2003 | A1 |
20030139989 | Churquina | Jul 2003 | A1 |
20030165200 | Pugel | Sep 2003 | A1 |
20030182139 | Harris | Sep 2003 | A1 |
20030190077 | Ross | Oct 2003 | A1 |
20030206558 | Parkkinen | Nov 2003 | A1 |
20050149759 | Vishwanath | Jul 2005 | A1 |
Number | Date | Country |
---|---|---|
A5303198 | Feb 1997 | AU |
0173639 | May 1986 | EP |
0 847 156 | Sep 1997 | EP |
1010098 | Apr 1998 | EP |
1324567 | Apr 1998 | EP |
0955592 | Apr 1999 | EP |
1 050 833 | Aug 2000 | EP |
1236354 | Sep 2002 | EP |
2306869 | Nov 1995 | GB |
2001202368 | Jul 2001 | JP |
2001521642 | Nov 2001 | JP |
WO 9707467 | Feb 1997 | WO |
WO 9825269 | Jun 1998 | WO |
WO 9847080 | Oct 1998 | WO |
WO 9927681 | Jun 1999 | WO |
WO 9943111 | Aug 1999 | WO |
WO 0046681 | Feb 2000 | WO |
WO 0031964 | Jun 2000 | WO |
WO 0154323 | Jan 2001 | WO |
WO 0133379 | May 2001 | WO |
WO 0135667 | May 2001 | WO |
WO 0173639 | Oct 2001 | WO |
WO 0242862 | May 2002 | WO |
WO 02065341 | Aug 2002 | WO |
WO 02065341 | Aug 2002 | WO |
WO 03012695 | Feb 2003 | WO |
Number | Date | Country | |
---|---|---|---|
20030018797 A1 | Jan 2003 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 09846823 | Apr 2001 | US |
Child | 10177643 | US |