Patent Grant
7818350
The present disclosure relates generally to a method, server, and user interface associated with creating a collaborative playlist between one or more users based on user interaction with a media program. In one embodiment, the media program forms a part of instant messaging (IM) application.
Current technology allows for individuals to create their own playlist of media files and/or media file identifiers. For example, media management and playing applications allow a user to compile a particular set of media files into a playlist or playlist usable to play media files The individual can further manipulate the playlist by re-arranging, deleting, and editing this playlist as desired. However, there lacks a system and method for allowing an individual to collaboratively create a playlist with other users in real-time. Moreover, there lacks a system and method for allowing an individual with at least one other user to essentially simultaneously view the collaborative playlist as it being built. Further, there lacks a capability to allow the participants to discuss and communicate about the playlist they are creating in real-time.
Thus, the present disclosure addresses these failings. Specifically, in one embodiment, the present disclosure relates to a system, method, and user interface for creating a collaborative playlist, in real-time, of media content, media files, and/or media file identifiers between two or more users. The embodiments herein can be implemented in a variety of ways, by way of non-limiting example, as a plug-in or extension to existing media player applications, as part of existing messaging platforms, or as an individual application.
The present disclosure relates to a system, method, and user interface for creating a collaborative playlist usable to play media files between two or more users. As used herein, the terms “content”, “media”, or “media files” are used broadly to encompass any type or category of experienceable, retrievable, filed and/or stored media, either singly or collectively, and individual items of media or content are generally referred to as entries, songs, tracks, items or files, however, the use of any one term is not to be considered limiting as the concepts features and functions described herein are generally intended to apply to any storable and/or retrievable item that may be experienced by a user, whether aurally, visually or otherwise, in any manner now known or to become known. Further, the term media includes all types of media such as audio and video.
In one embodiment, a method for creating a collaborative playlist comprises establishing, a communication between a first user at a first computing device and a second user at a second computing device, then providing, for display on each of the first computing device and the second computing device a playlist application accessible by both the first user and the second user for essentially simultaneous interaction by the users with a playlist creation tool for collaboratively creating a playlist usable to play media files and then accepting a media file identifier selected by either one or both of the users for inclusion on the playlist.
In one embodiment, the playlist usable to play media files is a playlist comprising media files and/or media file identifiers wherein the user can access the contents of the media files associated with the media file identifiers.
In one embodiment, the media file identifier is associated with a media file that is identified by the media file identifier. In another embodiment, the media file identifier is acquired from a server. In another embodiment, the media file identifier is acquired from the first user's local media library. In another embodiment, the media file identifier is acquired from the second user's local media library. In another embodiment, the media file identifier is acquired from a third user's local media library. In another embodiment, the media file identifier is acquired from the internet. In another embodiment, the media file identifier is acquired from a network.
In a further embodiment, the method further comprises displaying the playlist at each user's computing device. Thus, in one embodiment, each user can save the playlist to each user's respective computing device. In another embodiment, each user can independently edit the playlist from each user's respective computing device. In a further embodiment, wherein upon editing, each user's edits are only displayed on each user's respective computing device.
In one embodiment, the ability of each user to access a media file associated with the media file identifier is governed by a permission level. In one exemplary embodiment, the permission level is associated with the media file. In another exemplary embodiment, the permission level is controlled by a subscription from a service provider.
In one embodiment, the media identifier is a pointer. In another embodiment, the media file identifier is a uniform resource locator. In another embodiment, the media file identifier is user-defined. In another embodiment, the media file identifier is server-defined. In another embodiment, the media file identifier is a genre. In another embodiment, the media file identifier indicates the identity of the contributor of the media file. In another embodiment, the media file identifier identifies a site on a network from which an associated media file may be streamed.
In one embodiment, the media file identifier is associated with a media file and the media file is acquired by downloading the media file to the user's computing device from a remote database of media files. In another embodiment, the media file identifier is associated with a media file and the media file is acquired by locating the media file on either the first user's computing device or the second user's computing device.
In another embodiment, the media file identifier is associated with a media file and the media file is acquired from any of the following, by either streaming the media file to the user, downloading the media file to the user's computing device from a remote database of media files, or locating the media file on either the first user's computing device or the second user's computing device.
In one embodiment, either one or both of the first computing device and the second computing device is a portable media player. In another embodiment, either one or both of the first computing device and the second computing device is a personal digital assistant. In another embodiment, either one or both of the first computing device and the second computing device is a cellular telephone. In another embodiment, either one or both of the first computing device and the second computing device is a personal computer. In further embodiments, the first and/or second computing device can be any combination of the computing devices discussed above. For example, in one embodiment, the first computing device may be a personal computer and the second computing device may be a cellular phone.
In one embodiment, the media file is an audio file. In another embodiment, the media file is a video file. In an alternative embodiment, the media file can be a combination file compatible with a MPEG-21 standard or the like.
In one embodiment, the playlist creation tool comprises a user interface for building the collaborative playlist. In one exemplary embodiment of the playlist creation tool's user interface, the user interface comprises an area for displaying the collaborative playlist. In another exemplary embodiment, the playlist creation tool's user interface comprises an area for displaying the results of a search performed by either one or both of first user and second user. In an alternative embodiment, the playlist creation tool's user interface comprises both an area for displaying the collaborative playlist and area for displaying the results of a search performed by either one or both of first user and second user.
In another embodiment, the playlist creation tool comprises a searching software module that allows either one or both of the users to search for the media file identifier from a media file source. In one embodiment the media file source is an on-demand streaming media file service. In another embodiment, the media file source is either one or both of the user's local media library. In another embodiment, the media file source is a third user's media file library.
In another embodiment, the playlist creation tool comprises a searching software module that allows a user to search by input criteria for at least one media file identifier from a media file source. In one embodiment, the input criteria can be an artist name, an album name, a media file title, a list of recommended media files, and/or a set of highly rated media files.
In one embodiment, the selection of the media file identifier to be included in the collaborative playlist is done via a one-button feature which allows each user to add the media file identifier to be included in the collaborative playlist. In a further embodiment, wherein upon adding the media file identifier to the playlist, the media file identifier is displayed essentially simultaneously on the playlist of each user's computing device.
In one embodiment, the playlist creation tool comprises a browser to permit browsing for media file identifiers from multiple media file sources.
In a further embodiment, the playlist creation tool can comprise any combination of the following: a browser to permit browsing for media file identifiers from multiple media file sources, a one-button feature, a searching software module, an area for displaying the collaborative playlist, and an area for displaying the results of a search performed by either one or both of first user and second user.
In one embodiment, the first user and the second user communicate via a server. In another embodiment, first user and the second user communicate via a network. In another embodiment, the first user and the second user communicate via the internet.
One embodiment discloses a server that distributes data for collaborative playlist creation, the server comprising a communications software module that establishes communication with a first user at a first computing device and a second user at a second computing device and a data distribution software module that receives a first data set associated with a first media file from the first computing device and transmits the first data set to the second computing device, the data distribution software module receiving a second data set associated with a second media file from a second computing device and transmitting the second data set to the first computing device so that the first computing device can identify the second media file to form a playlist that is essentially simultaneously viewed on the first computing device and the second computing device.
In one embodiment, the first media file is found as a result of a search performed by either one or both users. In another embodiment, the second media file is found as a result of a search performed by either one or both users. In a further embodiment, the search at the second computing device is performed by inputting search criteria received at the instant messaging software application on the server from the first computing device.
In one embodiment, the communication is established via an instant messaging application. In an exemplary embodiment, the second computing device receives information about the playlist via the instant messaging software application from the first computing device. Further, in another exemplary embodiment, the first computing device receives information about the playlist via the instant messaging software application from the second computing device.
In one embodiment, the instant messaging application comprises a playlist creation tool. In one exemplary embodiment, the playlist creation tool comprises a user interface on the first computing device and on the second computing device for displaying the playlist.
In one embodiment, either one or both of the first data set or the second data set comprises an identifier. In another embodiment, either one or both of the first data set or the second data set comprises at least a name. In another embodiment, either one or both of the first data set or the second data set comprises a uniform resource locator. In another embodiment, either one or both of the first data set or the second data set comprises a pointer. In one embodiment, the playlist comprises at least the first data set and the second data set.
In one embodiment, the second media file is identified by downloading the media file from the server. In another embodiment, the second media file is identified by streaming the second media file from the server. In another embodiment, the second media file is identified by obtaining the media file from local memory in the remote computing device.
In one embodiment, the computing device is a cellular phone. In another embodiment, the computing device is a portable media player. In another embodiment, the computing device is a personal digital assistant.
In one embodiment, either one or both of the first or second media file is an audio file. In another embodiment, either one or both of the first or second media file is a video file.
In one embodiment, the second user receives an input from the first user indicating criteria to search for the second media file. In one embodiment, the criteria input is a rating. In another embodiment, the criteria input is an artist name. In another embodiment, the criteria input is a media file name.
One embodiment discloses a user interface for an instant messaging application comprising: a first area comprising an area for inputting messages and a conversation area for viewing the exchange of messages; a second area for searching for media file identifiers from a media file source; and a third area for displaying a collaborative playlist. In one embodiment, this collaborative playlist comprises a media file identifier.
In a further embodiment, the instant messaging environment application specifically designed for building a collaborative playlist between two or more users includes a user interface for creating the collaborative playlist. Further, the user interface can include areas or panes which allow for the users to communicate in real-time via instant messaging, and areas for building a collaborative playlist among the users.
In one embodiment, the media file identifier is a pointer. In another embodiment, the media file identifier is a uniform resource locator. In another embodiment, the media file identifier is user-defined. In another embodiment, the media file identifier is server-defined. In another embodiment, the media file identifier is a genre. In another embodiment, the media file identifier indicates the identity of the contributor of the media file. In another embodiment, the media file identifier is associated with a media file, the media file being acquired from either streaming the media file to the user, downloading the media file to the user's computing device from a remote database of media files, or locating the media file on either the first user's computing device or the second user's computing device.
In one embodiment, the collaborative playlist comprises a media file identifier.
In another embodiment, the user interface further comprising a button for initiating the search. In one embodiment, the search is based upon input criteria. In one embodiment, the input criteria is selected via a drop down menu and a corresponding text field box. In one embodiment, the input criteria is an artist name. In another embodiment, the input criteria a media file name. In another embodiment, the input criteria is a list of recommended media files.
In one embodiment, the user interface further comprising a button for adding the media file identifier from the second area to the third area to be included in the collaborative playlist. In one embodiment, the media file identifier can be dragged and dropped into the third area to be included in the collaborative playlist.
In one embodiment, the user interface is displayed at a first user's first computing device and at a second user's second computing device. In a further embodiment, the second area at the first user's computing device is displayed differently than the second user's computing device. In another embodiment, the third area is displayed essentially simultaneously at the first user's computing device and a second user's computing device.
One embodiment discloses a program storage device tangibly embodying a program of instructions executable by a computing device to perform method steps comprising establishing, via an instant messaging application, a communication between a first user at the computing device and a second user at a second computing device; displaying on each of the first computing device and the second computing device a playlist application accessible by both the first user and the second user for essentially simultaneous interaction by the users with a playlist creation tool for collaboratively creating a playlist usable to play media files; and accepting, via the playlist creation tool, a media file identifier selected by either one or both of the users for inclusion on the playlist so as to a collaboratively create the playlist.
One embodiment discloses a computer data signal embodied in a carrier wave comprising instruction for receiving signals transmitted by network entities, wherein at least a subset of the signals comprise code for performing the steps of establishing, via an instant messaging application, a communication between a first user at the computing device and a second user at a second computing device; displaying on each of the first computing device and the second computing device a playlist application accessible by both the first user and the second user for essentially simultaneous interaction by the users with a playlist creation tool for collaboratively creating a playlist usable to play media files; and accepting, via the playlist creation tool, a media file identifier selected by either one or both of the users for inclusion on the playlist so as to a collaboratively create the playlist.
In an alternate embodiment, a method and system allows two or more users of a particular group to receive a collaborative playlist and/or at least one media file.
In further embodiments, once the collaborative playlist is created, the user interface, in conjunction with a media management program, assists each user in managing their playlists.
In one embodiment, the user can manage the playlist by loading and playing the playlist in a media player. In another embodiment, the user can manage the playlist by saving the playlist to their computing device.
In another embodiment, the user can manage the playlist by sending the playlist to another person. In another embodiment, the user can manage the playlist by burning the playlist to a CD. In another embodiment, the user can manage the playlist by transferring the playlist to a portable device. In another embodiment, the user can manage the playlist by rearranging and/or deleting the tracks within the playlist.
In a further embodiment, the user can perform any of the above managing functions in any combination as the user desires. For example, once the playlist is generated, the user can delete tracks from the playlist, play the playlist, and then send the playlist to another user.
The following drawing figures, which form a part of this application, are illustrative of embodiments of the present invention and are not meant to limit the scope of the invention in any manner, which scope shall be based on the claims appended hereto.
In general, the present disclosure includes a method, system, and user interface for creating a collaborative playlist among two or more users. Certain embodiments of the present disclosure will now be discussed with reference to the aforementioned figures, wherein like reference numerals refer to like components.
In one embodiment, a method and system for allowing two or more users to build a collaborative playlist in real-time is disclosed.
In one embodiment, a method for creating a collaborative playlist comprises establishing, via an instant messaging application, a communication between a first user at a first computing device and a second user at a second computing device, then displaying on each of the first computing device and the second computing device a playlist application accessible by both the first user and the second user for essentially simultaneous interaction by the users with a playlist creation tool for collaboratively creating a playlist usable to play media files and then accepting, via the playlist creation tool, a media file identifier selected by either one or both of the users for inclusion on the playlist so as to a collaboratively create the playlist.
In one embodiment, the playlist application is displayed as part of an instant messaging environment application. In one embodiment, the playlist application can include a playlist creation tool. In a further embodiment, the playlist application facilitate text messaging. For example, with reference to
In one embodiment, the playlist creation tool can include a user interface. In one embodiment, the playlist creation tool can include an area for searching for media file identifiers and for displaying the search results. In a further embodiment, the playlist creation tools' user interface comprises an area for displaying the collaborative playlist as it is being built. In another embodiment, the playlist execution tool can comprise a button for serving the collaborative playlist to a user's computing device. In another embodiment, the playlist creation tool can comprise a button for adding the selected media files found in the search into the area for displaying the collaborative playlist. In another embodiment, the playlist creation tool's user interface can include any combination of the areas and features discussed above. For example, in
In another embodiment, two or more users can build a collaborative playlist through a instant messaging environment application. Typically, Instant Messaging (IM) refers to any real-time or any near real-time messaging or information exchange system. Further, an instant messaging environment application allows users to share a particular environment or application among themselves while still allowing for instant messaging capabilities. Instant messaging environment applications and their supporting backend systems and system configurations are disclosed, for example, in U.S. application Ser. No. 09/930,978, published Oct. 28, 2004 as U.S. Publication No. 20040215731, entitled “Instant Messaging Environments” the content of which is hereby incorporated herein by reference in its entirety.
In an alternate embodiment, a method and system allows two or more users belonging to a particular group to receive the same collaborative playlist usable to play at least one media file from a sending user or entity. For example, the sending user or entity could be any type of user or entity including a disc jockey, a celebrity, a recording label, a company, a radio station, a musician, and/or a producer. The user group could be constructed from a sign-up forum or from the sending user's messenger distribution list.
In one exemplary embodiment, the two or more users participating in the collaborative playlist could be a part of a particular group as a result of being a part of a user's instant messaging contacts. In an alternate embodiment, the two or more users could be a part of a particular messenger group as a result of the users' signing up to a particular group or list. For example, fans of a particular genre could sign up to receive and participate in building playlists along with other users who also enjoy that particular genre. Thus, through the present system and method, the sending user or entity can send a collaborative playlist to each user in the particular group.
In a further embodiment, the playlist application for building a collaborative playlist between two or more users includes a user interface. In one embodiment, the playlist application includes a user interface which allows one or more users to build a collaborative playlist together while in an instant messaging environment. One exemplary embodiment of a user interface for building a collaborative playlist in an Instant Messaging environment is described in detail further below.
A user can access the application for building the collaborative playlist in various ways. For example, the user can access a drop down menu, button, or tab located on the user interface of his or her local instant messaging program. In one exemplary embodiment, as stated above, a user can access the collaborative playlist application 850 by selecting a particular button or drop down menu on a user interface. Referring additionally to
With reference once again to
In a further embodiment, the collaborative playlist application could be stored in a user's computing device (not shown) to avoid the necessity for downloading.
Next, via an instant messaging server 815, or directly via peer-to-peer communication, the user sends a message to another user's instant messaging program user interface 820 which includes a command to invoke the collaborative playlist application. Then, the environment server 810 will download the requested application 830 to another user's local instant messaging program user interface 820. At this point, both users will have the collaborative playlist application loaded on their respective computing devices. In one embodiment, the collaborative playlist application will be loaded in its initial state onto each user's instant messaging user interface. Thus, once the collaborative playlist application is loaded onto each user's computing device, the users can begin to collaboratively build a playlist using the collaborative playlist application's user interface. (See
In one embodiment, the user interface for the collaborative playlist application in an instant messaging embodiment is displayed in a window having one or more panes, areas, or hierarchy of menus, depending on the user's needs or designer's choices. For example, in an alternate embodiment, where the computing device may have a limited display area, such as in a cellular phone, the areas, panes, or hierarchy of menus will preferably be arranged so as to properly fit within the display or could be arranged in a particular order so that the user could easily navigate through the user interface to build the collaborative playlist. Thus, the layout and number of panes or areas can vary depending on the user's needs. One exemplary embodiment of a user interface for the collaborative playlist environment application in an instant messaging environment is depicted in
In a manner known in the art the conversation area pane 105 displays all the typed text messages in real-time as they are exchanged between the users. In one aspect, this area pane 105 is a history window, viewable by both users, which contains the messages that have been exchanged in the past between the users. Thus, through the conversation area pane 105, both users can engage in conversation, view the typed conversation in real- or near real-time, and view the past exchanged messages.
Also in a manner know in the art the text in the area pane 120 is a space where the user can type in and input text to send to the other user. Typically, the user types in text and in the field box 185 and then presses a button 190 or key which will send the entered text to the other user while essentially simultaneously displaying to both users the entered text in the conversation area 105. Thus, through the input area 120 and conversation area 105, both users can exchange messages back and forth having a typed conversation in essentially real-time. In one aspect, this allows the users to discuss the potential features, attributes, or any issues surrounding the collaborative playlist (see e.g.
In further embodiments, as known in the art, the text input area pane 120 may also include various buttons and menus 195 that activate common messaging functions such as altering the input font, ringing another user, adding sounds or tones, inserting symbols, sending animated flash media, and activating an instant messaging environment application.
In one embodiment, the user interface comprises an area for searching and/or browsing for media file identifiers. For example,
In one embodiment, the drop down box 125 as depicted in
One exemplary embodiment illustrating a media file identifier search using a drop down menu box and a text field box is depicted in
The playlist collaboration application can initiate a search of media file sources such as the user's personal library of media files, an on-demand streaming media file service, another user's media library, a network and/or, the internet. It is contemplated that the user can initiate search for media files from a mixture of media sources. For example, at times, the user may want search for media files and/or media file identifiers solely from his or her own local media library files. At other times, the user may want to search solely from an on-demand streaming media service that can provide the user access to tens of thousands of media files and/or media file identifiers. Furthermore, the user may want to search from a mixture of two or more sources such as local media library and on-demand streaming service. Moreover, a user may want to only create a collaborative playlist with the other participating user's media library.
In one embodiment, with reference once again to
Another exemplary embodiment illustrating a media file and/or media file identifier search using a drop down menu box and a text field box is depicted in
In one embodiment, referring to
Another exemplary embodiment illustrating a media file search using a drop down menu box and a text field box is depicted in
In addition, referring to
Another exemplary embodiment illustrating a media file search of recommended media files using a drop down menu box and a text field box is depicted in
In addition, referring to
In one embodiment, the tool is dedicated to randomly select media files and/or media file identifiers from the user's local media library. In another embodiment, the tool selects content from the user's local media library based upon the popularity of the media files, based on the media files' ranking, based upon the degree of frequency the media files and/or media file identifiers are played, or any other basis for selecting media files and/or media file identifiers from a local user library. Thus, the tool assists the user in choosing content and can further streamline the playlist generation process. For example, if the user cannot remember the media file in their local media file library or simply does not have the time, the user can select the tool which will quickly provide the user with media file and/or media file identifier. The user can use this tool as many times as necessary to retrieve the desired content. Accordingly, each time the user selects the tool, different media file identifiers will be displayed for the user in the text field box.
In another embodiment, instead of entering media file identifiers into the text field box, the user can select media files and/or media file identifiers by clicking a tool which will select and automatically populate the text field box for the user. For example, the user could enter the first three characters of an artist name or media file title, then the system could complete the search term and populate the field box.
It should be noted that in one embodiment, with reference to
Regardless of what search input criteria is selected, once the user selects the button which will cause the environment application to initiate or perform a search of all media file identifiers, the results are displayed in the playlist creation or workspace pane. In one embodiment, with reference to
In one embodiment, as depicted in
Referring to
In a further embodiment, each user can alter and manage this collaborative playlist on their local collaborative playlist application user interface as they wish without affecting the other user's display of the collaborative playlist. For example, in an embodiment having two users, User 1 and User 2, once User 1 and User 2 have added their respective media file identifiers to the collaborative playlist, those media file identifiers are displayed in each of their resulting playlist panes. User 1 can delete as many media file identifiers from the resulting playlist pane as he or she wishes. However, User 2's collaborative playlist status and display in his resulting collaborative playlist pane remains unaffected by User 1's deletions. Thus, User 1 and User 2 can build the playlist together in a collaborative application, wherein when each user adds a media file identifier, it is reflected in both user's local user interfaces. But, any deletions will only be displayed on the deleting user's local user interface. Of course, alternate embodiments may include many variations of what media file identifier capabilities are displayed among all the users and which ones are not displayed.
In one embodiment (see e.g.
This drop down menu 1005 can include features and functions such as playing 1110 the particular media file 1140. Further, the drop down menu 1005 can include links to other features and functions relating to a particular media file identifier 1140. For example, the menu 1005 includes a link 1115 which will direct the user to the particular media files' 1140 associated artists' webpage and a link 1120 which will direct the user to the particular media files' 1140 associated song title web page. For example, in
Another feature or link 1130 allows the user to search for further media files and/or media file identifiers 1130 for the particular artist associated with the media file. In one embodiment, if the user selects this link 1130, using a music search service or database, the system will initiate a search for all songs and/or media file identifiers related to that artist. In one embodiment, a returned list of related media files and/or media file identifiers will be displayed for the user in a separate page or a new window pane of the user's interface.
Finally, as depicted in
In one embodiment, with reference to
In a one embodiment, as depicted in
Moreover, once the collaborative playlist is created to the user's satisfaction, through a media management program (such as media player like Yahoo! Music Engine or MusicMatch), the user can further manage the collaborative playlist. In one embodiment, the following variations and features regarding managing and the collaborative playlist is controlled by the media management program. For example, a media management program's user interface may allow the user to stop, rewind, fast-forward, pause, and or/stop the playing of the playlist. In another embodiment, the user can manage the playlist by rearranging and/or deleting the media files within the collaborative playlist. Further, the user may be able to send and share the collaborative playlist with others.
In one embodiment, the ability to send and share playlists with another user will be dependent on certain Digital Rights Management (DRM). In one embodiment, the playlists created and sent to another user will contain sufficient DRM information to ensure that the user to which the playlist is sent has sufficient rights or a specific permission level to permit that other user to experience the media contained in the playlist. In one embodiment, this function is controlled by the media management program, in one embodiment, the collaborative playlist building environment application does not have to distinguish between subscribing and non-subscribing users.
In one embodiment, the ability of each user to access a media file and/or media file identifier is governed by a permission level. Meaning, in one embodiment, the ability to send, play, view, add a media file and/or media file identifier may be governed by a permission level. In one exemplary embodiment, the permission level is associated with the media file. In another exemplary embodiment, the permission level is controlled by a subscription from a service provider. Rights and permissions can be managed by the application 850 or an associated media management application or media player or combination thereof.
In an exemplary embodiment, the permission level depends on user's status as a subscriber or a non-subscriber to a on-demand-streaming media service (ODSMS). For example, if the user who is adding the media file and/or media file identifier to the collaborative playlist is a subscriber and the user receiving the newly added media file or media file identifier is also a subscriber, then the receiving user can have full access to each ODSMS media file identifier on the playlist.
In another exemplary embodiment of adding a media file identifier, if the user adding the media file identifier to the collaborative playlist is a subscriber to a ODSMS and the receiving user is a non-subscriber, then the receiving user may have limited access to the ODSMS media files. For example, the receiving user may be limited to a pre-determined length clip of each ODSMS media file, such as a 30-second clip when the receiving user plays the media file.
In another example of subscribing-adding-user and a non-subscribing—receiving-user, the receiving user may be given a pre-determined number of times the user can play each ODSMS media file. After this pre-determined number of times has been reached, the user is then limited to a default, pre-determined length of time for each media file (such as a 30-second clip). For example, the non-subscribing, receiving user may be limited to playing a ODSMS media file at its full-length to three times. Thus, once the user had played the media file and/or media file identifier three times, the user can now only listen to 30 second clips of the media file. This allows a non-subscribing receiving user to listen to ODSMS music otherwise not available to the user, while enticing the user to subscribe to the service. Accordingly, in one embodiment, once the user's pre-determined number of full-length plays are used, the user is prompted and has the option to subscribe to the ODSMS.
Of course, these embodiments are not limited to ODSMS media files, but can apply to any media files which require a specified level of sharing and playing access. For example, it could be negotiated that certain media files generally not available for full-length sharing could be shared and played between any status (subscribing or non-subscribing) of users for a pre-determined number of times. For example, if there is a particular artist who wants to promote and/or entice users to listen to their media files, the artist or their representatives can allow a particular media file to be able to be played in a collaborative playlist among any type of users. However, the users are limited to playing the media file to a certain number of times.
In another embodiment, the user can further utilize the collaborative playlist by burning the playlist to a CD or transferring the media files to a portable device. For example, the user can burn the media filed listed in playlist in the media player window to a CD and/or transfer the media files to a portable device by clicking a button and selecting the option from a drop-down menu. In some embodiments, the ability to transfer media files to a portable device or burn media files to a CD may depend on whether the user has specified access to those media files. Particularly, the user may be required to pay for files not located on the user's local media library. For example, the user may be required to pay for files located on an on-demand, streaming media service. Thus, the user may be required to pay a price for each media file before downloading or burning the media files. In another example, the user may be required to be subscriber to a service that allows the user to download and burn media files.
In a further embodiment, the user can perform any of the above managing functions in any combination as the user desires using the media management program. For example, once the playlist is generated, the user can delete media files and/or media file identifiers from the playlist, play the playlist, and then send the playlist to another user.
Those skilled in the art will recognize that the method and system of the present invention within the application, may be implemented in many manners and as such is not to be limited by the foregoing exemplary embodiments and examples. In other words, functional elements being performed by a single or multiple components, in various combinations of hardware and software, and individual functions can be distributed among software applications at either the client or server level. In this regard, any number of the features of the different embodiments described herein may be combined into one single embodiment and alternate embodiments having fewer than or more than all of the features herein described are possible. Functionality may also be, in whole or in part, distributed among multiple components, in manners now known or to become known. Thus, myriad software/hardware/firmware combinations are possible in achieving the functions, features, interfaces and preferences described herein. Moreover, the scope of the present invention covers conventionally known and features of those variations and modifications through the system component described herein as would be understood by those skilled in the art.
This application claims the benefit of U.S. Provisional Application Ser. No. 60/657,222, filed Feb. 28, 2005, entitled A SYSTEM AND METHOD FOR DELIVERING MEDIA OVER A NETWORK, and U.S. Provisional Application Ser. No. 60/678,718, filed May 5, 2005, entitled A SYSTEM AND METHOD FOR DELIVERING MEDIA OVER A NETWORK, both of which are hereby incorporated herein by reference.
| Number | Name | Date | Kind |
|---|---|---|---|
| 5566353 | Cho et al. | Oct 1996 | A |
| 5616876 | Cluts | Apr 1997 | A |
| 5729741 | Liaguno et al. | Mar 1998 | A |
| 5748956 | Lafer et al. | May 1998 | A |
| 5864870 | Guck | Jan 1999 | A |
| 5886698 | Sciammarella et al. | Mar 1999 | A |
| 5890152 | Rapaport et al. | Mar 1999 | A |
| 5903892 | Hoffert et al. | May 1999 | A |
| 5928330 | Goetz et al. | Jul 1999 | A |
| 5950173 | Perkowski | Sep 1999 | A |
| 5982369 | Sciammarella et al. | Nov 1999 | A |
| 5996015 | Day et al. | Nov 1999 | A |
| 6006241 | Purnaveja et al. | Dec 1999 | A |
| 6064380 | Swenson et al. | May 2000 | A |
| 6118450 | Proehl et al. | Sep 2000 | A |
| 6157377 | Shah-Nazaroff et al. | Dec 2000 | A |
| 6192340 | Abecassis | Feb 2001 | B1 |
| 6226672 | DeMartin et al. | May 2001 | B1 |
| 6232539 | Looney et al. | May 2001 | B1 |
| 6248946 | Dwek | Jun 2001 | B1 |
| 6356971 | Katz et al. | Mar 2002 | B1 |
| 6389467 | Eyal | May 2002 | B1 |
| 6393430 | Van Ryzin | May 2002 | B1 |
| 6466918 | Spiegel et al. | Oct 2002 | B1 |
| 6477704 | Cremia | Nov 2002 | B1 |
| 6484199 | Eyal | Nov 2002 | B2 |
| 6526411 | Ward | Feb 2003 | B1 |
| 6538665 | Crow et al. | Mar 2003 | B2 |
| 6605770 | Yamane et al. | Aug 2003 | B2 |
| 6609096 | De Bonet et al. | Aug 2003 | B1 |
| 6662231 | Drosset et al. | Dec 2003 | B1 |
| 6691162 | Wick | Feb 2004 | B1 |
| 6721489 | Benyamin et al. | Apr 2004 | B1 |
| 6728729 | Jawa et al. | Apr 2004 | B1 |
| 6731312 | Robbin | May 2004 | B2 |
| 6735628 | Eyal | May 2004 | B2 |
| 6738766 | Peng | May 2004 | B2 |
| 6816944 | Peng | Nov 2004 | B2 |
| 6820238 | Auflick et al. | Nov 2004 | B1 |
| 6829033 | Hose et al. | Dec 2004 | B2 |
| 6850256 | Crow et al. | Feb 2005 | B2 |
| 6928433 | Goodman et al. | Aug 2005 | B2 |
| 6941324 | Plastina et al. | Sep 2005 | B2 |
| 6968179 | De Vries | Nov 2005 | B1 |
| 6987221 | Platt | Jan 2006 | B2 |
| 7013290 | Ananian | Mar 2006 | B2 |
| 7020704 | Lipscomb et al. | Mar 2006 | B1 |
| 7024424 | Platt et al. | Apr 2006 | B1 |
| 7043477 | Mercer et al. | May 2006 | B2 |
| 7096234 | Plastina et al. | Aug 2006 | B2 |
| 7111009 | Gupta et al. | Sep 2006 | B1 |
| 7113767 | Vaananen | Sep 2006 | B2 |
| 7127454 | Deguchi | Oct 2006 | B2 |
| 7136874 | Mercer et al. | Nov 2006 | B2 |
| 7146404 | Kay et al. | Dec 2006 | B2 |
| 7159000 | Plastina et al. | Jan 2007 | B2 |
| 7219308 | Novak et al. | May 2007 | B2 |
| 7275063 | Horn | Sep 2007 | B2 |
| 7277852 | Iyoku et al. | Oct 2007 | B2 |
| 7281034 | Eyal | Oct 2007 | B1 |
| 7310350 | Shao et al. | Dec 2007 | B1 |
| 7409639 | Dempski et al. | Aug 2008 | B2 |
| 7426537 | Lee et al. | Sep 2008 | B2 |
| 7617278 | Edelman et al. | Nov 2009 | B1 |
| 20010018858 | Dwek | Sep 2001 | A1 |
| 20010033296 | Fullerton et al. | Oct 2001 | A1 |
| 20010042107 | Palm | Nov 2001 | A1 |
| 20020002498 | Hatakeyama | Jan 2002 | A1 |
| 20020010652 | Deguchi | Jan 2002 | A1 |
| 20020040326 | Spratt | Apr 2002 | A1 |
| 20020042834 | Kremens et al. | Apr 2002 | A1 |
| 20020045960 | Phillips et al. | Apr 2002 | A1 |
| 20020049037 | Christensen et al. | Apr 2002 | A1 |
| 20020052933 | Leonhard et al. | May 2002 | A1 |
| 20020054134 | Kelts | May 2002 | A1 |
| 20020087887 | Busam et al. | Jul 2002 | A1 |
| 20020089529 | Robbin | Jul 2002 | A1 |
| 20020099731 | Abajian | Jul 2002 | A1 |
| 20020126135 | Ball et al. | Sep 2002 | A1 |
| 20020138619 | Ramaley et al. | Sep 2002 | A1 |
| 20020151327 | Levitt | Oct 2002 | A1 |
| 20020152267 | Lennon | Oct 2002 | A1 |
| 20020156546 | Ramaswamy | Oct 2002 | A1 |
| 20020188363 | Ashy | Dec 2002 | A1 |
| 20030023427 | Cassin et al. | Jan 2003 | A1 |
| 20030028539 | Nunome et al. | Feb 2003 | A1 |
| 20030031176 | Sim | Feb 2003 | A1 |
| 20030037035 | Deguchi | Feb 2003 | A1 |
| 20030041108 | Henrick et al. | Feb 2003 | A1 |
| 20030046273 | Deshpande | Mar 2003 | A1 |
| 20030046399 | Boulter et al. | Mar 2003 | A1 |
| 20030065639 | Fiennes et al. | Apr 2003 | A1 |
| 20030071851 | Unger et al. | Apr 2003 | A1 |
| 20030088571 | Ekkel | May 2003 | A1 |
| 20030110502 | Creed | Jun 2003 | A1 |
| 20030151618 | Johnson et al. | Aug 2003 | A1 |
| 20030172090 | Asunmaa et al. | Sep 2003 | A1 |
| 20030182254 | Plastina et al. | Sep 2003 | A1 |
| 20030182315 | Plastina et al. | Sep 2003 | A1 |
| 20030191753 | Hoch | Oct 2003 | A1 |
| 20030200452 | Tagawa et al. | Oct 2003 | A1 |
| 20030212710 | Guy | Nov 2003 | A1 |
| 20030222907 | Heikes et al. | Dec 2003 | A1 |
| 20030223411 | de la Fuente | Dec 2003 | A1 |
| 20030225834 | Lee et al. | Dec 2003 | A1 |
| 20030225848 | Heikes et al. | Dec 2003 | A1 |
| 20030228134 | Kim et al. | Dec 2003 | A1 |
| 20030236582 | Zamir et al. | Dec 2003 | A1 |
| 20030236711 | Deguchi | Dec 2003 | A1 |
| 20030236832 | McIntyre et al. | Dec 2003 | A1 |
| 20030237043 | Novak et al. | Dec 2003 | A1 |
| 20040002938 | Deguchi | Jan 2004 | A1 |
| 20040003090 | Deeds | Jan 2004 | A1 |
| 20040003706 | Tagawa et al. | Jan 2004 | A1 |
| 20040019497 | Volk et al. | Jan 2004 | A1 |
| 20040055445 | Iyoku et al. | Mar 2004 | A1 |
| 20040056901 | March et al. | Mar 2004 | A1 |
| 20040057348 | Shteyn et al. | Mar 2004 | A1 |
| 20040057449 | Black | Mar 2004 | A1 |
| 20040064476 | Rounds | Apr 2004 | A1 |
| 20040068606 | Kim et al. | Apr 2004 | A1 |
| 20040078383 | Mercer et al. | Apr 2004 | A1 |
| 20040083273 | Madison et al. | Apr 2004 | A1 |
| 20040088348 | Yeager et al. | May 2004 | A1 |
| 20040103153 | Chang et al. | May 2004 | A1 |
| 20040117442 | Thielen | Jun 2004 | A1 |
| 20040117843 | Karaoguz et al. | Jun 2004 | A1 |
| 20040128308 | Obrador | Jul 2004 | A1 |
| 20040137882 | Forsyth | Jul 2004 | A1 |
| 20040148353 | Karaoguz et al. | Jul 2004 | A1 |
| 20040162871 | Pabla et al. | Aug 2004 | A1 |
| 20040162878 | Lewis et al. | Aug 2004 | A1 |
| 20040165006 | Kirby et al. | Aug 2004 | A1 |
| 20040174905 | Caspi et al. | Sep 2004 | A1 |
| 20040177116 | McConn | Sep 2004 | A1 |
| 20040184778 | Jung et al. | Sep 2004 | A1 |
| 20040196315 | Swearingen et al. | Oct 2004 | A1 |
| 20040199667 | Dobbins | Oct 2004 | A1 |
| 20040201609 | Obrador | Oct 2004 | A1 |
| 20040205028 | Verosub et al. | Oct 2004 | A1 |
| 20040215731 | Tzann-en Szeto | Oct 2004 | A1 |
| 20040220791 | Lamkin et al. | Nov 2004 | A1 |
| 20040220926 | Lamkin et al. | Nov 2004 | A1 |
| 20040221299 | Gibbs et al. | Nov 2004 | A1 |
| 20040226039 | Jung et al. | Nov 2004 | A1 |
| 20040236568 | Guillen et al. | Nov 2004 | A1 |
| 20040252604 | Johnson et al. | Dec 2004 | A1 |
| 20040260753 | Regan | Dec 2004 | A1 |
| 20040267812 | Harris et al. | Dec 2004 | A1 |
| 20050004985 | Stochosky | Jan 2005 | A1 |
| 20050004995 | Stochosky | Jan 2005 | A1 |
| 20050021398 | McCleskey et al. | Jan 2005 | A1 |
| 20050021470 | Martin et al. | Jan 2005 | A1 |
| 20050021750 | Abrams et al. | Jan 2005 | A1 |
| 20050027539 | Weber et al. | Feb 2005 | A1 |
| 20050038707 | Roever et al. | Feb 2005 | A1 |
| 20050038724 | Roever et al. | Feb 2005 | A1 |
| 20050038814 | Iyengar et al. | Feb 2005 | A1 |
| 20050038819 | Hicken et al. | Feb 2005 | A1 |
| 20050038877 | Gupta et al. | Feb 2005 | A1 |
| 20050044229 | Brown | Feb 2005 | A1 |
| 20050055472 | Krzyzanowski et al. | Mar 2005 | A1 |
| 20050060264 | Schrock et al. | Mar 2005 | A1 |
| 20050065935 | Chebolu et al. | Mar 2005 | A1 |
| 20050071780 | Muller et al. | Mar 2005 | A1 |
| 20050080807 | Beilinson et al. | Apr 2005 | A1 |
| 20050086309 | Galli et al. | Apr 2005 | A1 |
| 20050086606 | Blennerhassett et al. | Apr 2005 | A1 |
| 20050091069 | Chuang | Apr 2005 | A1 |
| 20050102191 | Heller | May 2005 | A1 |
| 20050108176 | Jarol et al. | May 2005 | A1 |
| 20050108320 | Lord et al. | May 2005 | A1 |
| 20050114324 | Mayer | May 2005 | A1 |
| 20050138543 | Liu | Jun 2005 | A1 |
| 20050146996 | Roman | Jul 2005 | A1 |
| 20050160111 | Plastina et al. | Jul 2005 | A1 |
| 20050172001 | Zaner et al. | Aug 2005 | A1 |
| 20050197906 | Kindig et al. | Sep 2005 | A1 |
| 20050198317 | Byers | Sep 2005 | A1 |
| 20050210396 | Galli | Sep 2005 | A1 |
| 20050210507 | Hawkins et al. | Sep 2005 | A1 |
| 20050216443 | Morton et al. | Sep 2005 | A1 |
| 20050216855 | Kopra et al. | Sep 2005 | A1 |
| 20050227676 | De Vries | Oct 2005 | A1 |
| 20050234875 | Auerbach et al. | Oct 2005 | A1 |
| 20050234995 | Plastina et al. | Oct 2005 | A1 |
| 20050240494 | Cue et al. | Oct 2005 | A1 |
| 20050246651 | Krzanowski | Nov 2005 | A1 |
| 20050251565 | Weel | Nov 2005 | A1 |
| 20050251566 | Weel | Nov 2005 | A1 |
| 20050251576 | Weel | Nov 2005 | A1 |
| 20050251807 | Weel | Nov 2005 | A1 |
| 20050262186 | Szeto et al. | Nov 2005 | A1 |
| 20060008256 | Khedouri et al. | Jan 2006 | A1 |
| 20060010240 | Chuah | Jan 2006 | A1 |
| 20060031770 | McMenamin | Feb 2006 | A1 |
| 20060041627 | Tu | Feb 2006 | A1 |
| 20060056324 | Hyyppa et al. | Mar 2006 | A1 |
| 20060080103 | Van Breemen | Apr 2006 | A1 |
| 20060095502 | Lewis et al. | May 2006 | A1 |
| 20060107297 | Toyama et al. | May 2006 | A1 |
| 20060123058 | Mercer et al. | Jun 2006 | A1 |
| 20060123113 | Friedman | Jun 2006 | A1 |
| 20060133768 | Ellis | Jun 2006 | A1 |
| 20060143236 | Wu | Jun 2006 | A1 |
| 20060167985 | Albanese et al. | Jul 2006 | A1 |
| 20060173838 | Garg et al. | Aug 2006 | A1 |
| 20060190410 | Harper | Aug 2006 | A1 |
| 20060195462 | Rogers | Aug 2006 | A1 |
| 20060218195 | LaChapelle et al. | Sep 2006 | A1 |
| 20070011206 | Gupta et al. | Jan 2007 | A1 |
| 20070016865 | Johnson et al. | Jan 2007 | A1 |
| 20070050413 | Kominek et al. | Mar 2007 | A1 |
| 20070143740 | Hoerentrup et al. | Jun 2007 | A1 |
| 20070159934 | Weon | Jul 2007 | A1 |
| 20070191108 | Brunet De Courssou et al. | Aug 2007 | A1 |
| 20080215882 | Coldicott et al. | Sep 2008 | A1 |
| Number | Date | Country |
|---|---|---|
| 1 176 840 | Jan 2002 | EP |
| 1 489 800 | Dec 2004 | EP |
| 1-489-800 | Dec 2004 | EP |
| WO 0233579 | Apr 2002 | WO |
| WO 2004046874 | Jun 2004 | WO |
| Number | Date | Country | |
|---|---|---|---|
| 20060195521 A1 | Aug 2006 | US |
| Number | Date | Country | |
|---|---|---|---|
| 60657222 | Feb 2005 | US | |
| 60678718 | May 2005 | US |
