Method and system for operating and participating in fantasy leagues

Abstract

A system and computer-implemented method for operating a fantasy league including: fantasy player information including performance history of one or more real-world athletes selected as fantasy players is stored. Sponsorship information associated with the fantasy player is stored on at least one of an individual or team basis. An operational request from a fantasy client device is received. An association between the operational request and the fantasy player is determined. An operational result is determined. At least one item of sponsorship information is associated with the operational result. The operational result and the sponsorship information are transmitted. An alert window is displayed at the fantasy client device including the sponsorship information.

Claims

1. A fantasy league system comprising: at least one server operable to communicate over a network with a user device, the user device being remote from the at least one server; wherein the at least one server is configured to: store fantasy player information regarding one or more real-world athletes as fantasy players; store sponsorship information associated with a fantasy player on at least one of an individual basis and a team basis; provide a graphical user interface for display by the user device, wherein the graphical user interface is configured to visually represent the sponsorship information and the fantasy player, and wherein the graphical user interface comprises at least one selectable element to enable selection of the fantasy player; receive a fantasy player transaction request for the fantasy player, determine when the fantasy player transaction request is valid; and transmit a fantasy player transaction confirmation when the fantasy player transaction request is valid.

2. The fantasy league system of claim 1, wherein the at least one server is further configured to: determine when the fantasy player transaction request is invalid; and transmit a fantasy player transaction rejection when the fantasy player transaction request is invalid.

3. The fantasy league system of claim 1, wherein determining when the fantasy player transaction request is valid comprises determining when the fantasy player transaction request is in compliance with a fantasy league transaction policy.

4. The fantasy league system of claim 3, wherein the fantasy league transaction policy identifies legal transaction time periods for particular transaction types.

5. The fantasy league system of claim 3, wherein, when the fantasy player transaction request is in compliance with the fantasy league transaction policy, the at least one server is further configured to associate one or more portions of the sponsorship information associated with the fantasy player to the fantasy player information of the fantasy player.

6. The fantasy league system of claim 1, wherein the at least one server is further configured to generate a fantasy roster webpage.

7. The fantasy league system of claim 1, wherein the fantasy player transaction request is selected from the group consisting of a draft, waiver addition, waiver release, free agent addition, free agent release, and trade.

8. A computer-implemented method for operating a fantasy league using one or more servers operable to communicate over a network with a user device, the method comprising: storing, at the one or more servers, fantasy player information regarding one or more real-world athletes as fantasy players; storing, at the one or more servers, sponsorship information associated with a fantasy player on at least one of an individual basis and a team basis; providing a graphical user interface for display by the user device, wherein the graphical user interface is configured to visually represent the sponsorship information and the fantasy player, wherein the graphical user interface comprises at least one selectable element to enable selection of the fantasy player; receiving, at the one or more servers, a fantasy player transaction request for the fantasy player; determining when the fantasy player transaction request is valid; and transmitting a fantasy player transaction confirmation when the fantasy player transaction request is valid.

9. The method of claim 8, further comprising: determining when the fantasy player transaction request is invalid, and transmitting a fantasy player transaction rejection when the fantasy player transaction request is invalid.

10. The method of claim 8, wherein determining when the fantasy player transaction request is valid comprises determining when the fantasy player transaction request is in compliance with a fantasy league transaction policy.

11. The method of claim 10, wherein the fantasy league transaction policy identifies legal transaction time periods for particular transaction types.

12. The method of claim 8, further comprising, when the fantasy player transaction request is in compliance with the fantasy league transaction policy, associating one or more portions of the sponsorship information associated with the fantasy player to the fantasy player information of the fantasy player.

13. The method of claim 8, further comprising generating a fantasy roster webpage.

14. The method of claim 8, wherein the fantasy player transaction request is selected from the group consisting of a draft, waiver addition, waiver release, free agent addition, free agent release, and trade.

Description

BRIEF DESCRIPTION OF THE DRAWINGS

(1) FIG. 1 illustrates an exemplary environment for practicing the present invention;

(2) FIG. 2 illustrates one embodiment of fantasy player information in accordance with the present invention;

(3) FIG. 3 illustrates one embodiment of sponsorship information in accordance with the present invention;

(4) FIG. 4 illustrates a first embodiment of a flowchart representative of a fantasy client request method in accordance with the present invention;

(5) FIG. 5 illustrates a first embodiment of a web page in accordance with the present invention;

(6) FIG. 6 illustrates a second embodiment of a flowchart representative of a fantasy client request method in accordance with the present invention;

(7) FIG. 7 illustrates a third embodiment of a flowchart representative of a fantasy client request method in accordance with the present invention;

(8) FIG. 8 illustrates one embodiment of a flowchart representative of a transaction validation method in accordance with the present invention;

(9) FIG. 9 illustrates a second embodiment of a web page in accordance with the present invention;

(10) FIG. 10 illustrates a fourth embodiment of a flowchart representative of a fantasy client request method in accordance with the present invention;

(11) FIG. 11 illustrates one embodiment of a flowchart representative of a fantasy scoring method in accordance with the present invention;

(12) FIG. 12 illustrates a third embodiment of a flowchart representative of a fantasy substitution method in accordance with the present invention;

(13) FIG. 13 illustrates a third embodiment of a web page in accordance with the present invention;

(14) FIG. 14 illustrates exemplary embodiments of fantasy client devices and a fantasy server system in accordance with the present invention;

(15) FIG. 15 illustrates one embodiment of feed formatted content, as known in the art;

(16) FIG. 16 illustrates a flowchart representative of one embodiment of a method for providing feed formatted content;

(17) FIG. 17 illustrates a flowchart representative of one embodiment of a method for operating a real time fantasy sports league; and

(18) FIG. 18 illustrates a flowchart representative of one embodiment of a method for operating a real time fantasy sports league.

DETAILED DESCRIPTION OF THE PRESENT INVENTION

(19) FIG. 1 illustrates a network based environment employing an X number of fantasy client device 20, where X;;:::1, a network system 30 and a fantasy server system 40. For purposes of the present invention, the term fantasy client device is broadly defined herein as a device of any type structurally configured to facilitate member participation in a fantasy league of any type that is operated by a fantasy server system of the present invention, the term network system is broadly defined herein as one network of any type or an interconnect array of networks of any type, and the term fantasy server system is broadly defined herein as one or more servers of any type structurally configured to operate the fantasy league.

(20) In operation, network system 30 facilitates bi-directional communication between fantasy client devices 20 and fantasy server system 40 involving access by fantasy client devices 20 to the fantasy league operated by fantasy server system 40. One operational aspect of the fantasy league as provided by fantasy server system 40 is directed to facilitating access to fantasy content by fantasy client devices 20 and facilitating fantasy game play by fantasy client devices 20 as would be appreciated by those having ordinary skill in the art Examples of this operational aspect include, but are not limited to, (1) off-season actions by fantasy client devices 20 (e.g., configuring the fantasy league, accessing pre-season rankings of fantasy players and conducting a draft of the fantasy players), (2) in-season, off-time actions by fantasy client devices 20 (e.g., managing a lineup prior to or subsequent to real-time performances by the fantasy players, and accessing reports of past performances by the fantasy players and commentaries on predicted future performances of the fantasy players), and (3) in-season, gameplay actions by fantasy client devices 20 (e.g., managing a lineup during real-time performances by the fantasy players, and accessing reports of real-time performances and real-time playing status of the fantasy players).

(21) A new and unique operational aspect of the fantasy league in accordance with the present invention as provided by fantasy server system 40 is directed to a realization of a comprehensive sponsorship of fantasy players on an individual basis and/or a team basis with an improved exchange of fantasy content between fantasy client devices 20 and fantasy server system 40. To this end, as shown in FIG. 1, fantasy server system 40 manages one or more records of fantasy player information 50 and one or more records of sponsorship information 60, and employs a fantasy content manager 70 and fantasy gameplay manager 80.

(22) For purposes of the present invention, the term fantasy player information is broadly defined herein as any information of any type that is relevant, directly or indirectly, to a gameplay and performance history of a fantasy player as reviewed by a member of the fantasy league (e.g., physical dimensions, statistics, injury history/status, ranking, recommendations, etc.). In one embodiment, as shown in FIG. 2, fantasy player information 50 is managed by fantasy server system 40 in the form of fantasy player text data 51, fantasy player image data 52, fantasy player video data 53, fantasy player audio data 54, fantasy player multimedia data 55 and fantasy player hyperlink data 56.

(23) For purposes of the present invention, the term sponsorship information is broadly defined herein as any information of any type that is relevant to an advertisement/promotion of good(s) and/or service(s) as designated to a fantasy player on an individual basis and/or a team basis, the term individual basis is broadly defined herein as a designation by a sponsor of an advertisement/promotion of good(s) and/or service(s) to a specific player (e.g., Indianapolis Star designates the promotion of its paper to Peyton Manning, quarterback of the Indianapolis Colts), and the term team basis is broadly defined herein as a designation by a sponsor of an advertisement/promotion of good(s) and/or service(s) to a specific team (e.g., Indianapolis Star designates the promotion of its paper to all of tile team members of the Indianapolis Colts). Similarly, in one embodiment, as shown in FIG. 2, sponsorship information 60 is managed by fantasy server system 40 in the form of sponsorship text data 61, sponsorship image data 62, sponsorship video data 63, sponsorship audio data 64, sponsorship multimedia data 65 and sponsorship hyperlink data 66.

(24) In operation, fantasy content manager 70 associates relevant portions of sponsorship information of a fantasy player to relevant portions of fantasy player information of the fantasy player as needed. In particular, fantasy content manager 70 associates relevant portions of sponsorship information of a fantasy player to relevant portions of fantasy player information of the fantasy player in response to fantasy client requests directed to primarily acquiring fantasy player information for purposes of (1) learning/reviewing fantasy player information to thereby make informed gameplay decisions concerning the fantasy player and (2) make recommendations of the fantasy player to another member of the fantasy league. Similarly, fantasy gameplay manager 80 associates relevant portions of sponsorship information of a fantasy player to relevant portions of fantasy player information of the fantasy player in response to fantasy client requests directed to primarily acquiring fantasy player information for purposes of (1) conducting transactions involving a fantasy player prior to and/or during a fantasy performance period of the fantasy player (e.g., drafting, acquiring, releasing, trading, and lineup substitutions) and (2) monitoring a scoring of the fantasy player during a fantasy performance period of the fantasy player.

(25) The following description of FIGS. 4-14 are directed to describing exemplary fantasy client requests scenarios to facilitate an understanding of the present invention by those having ordinary skill in the art.

(26) FIG. 4 depicts a fantasy client request in the form of a request for fantasy player information. Specifically, a stage S92 of a flowchart 90 and a stage S102 of a flowchart 100 encompasses one of the fantasy client devices 20 and fantasy content manager 70 exchanging a request for fantasy player information FPIRQ of one or more fantasy players (e.g., a request for player news for Peyton Manning). A stage S104 of flowchart 100 encompasses fantasy content manager 70 determining fantasy player information of fantasy player(s) responsive to the information request (e.g., statistics and news feed items regarding Peyton Manning). A stage S106 of flowchart 100 encompasses fantasy content manager 70 associating sponsorship information of the fantasy players(s) corresponding to the fantasy player information (e.g., associating an advertisement/promotion of Indianapolis star in text, image, audio, video, multimedia, or hyperlink form to Peyton Manning's statistics and news feed items). Finally, a stage S94 of flowchart 90 and a stage S108 of flowchart 100 encompasses the fantasy client device 20 and fantasy content manager 70 exchanging the sponsored fantasy football player information SFPL.

(27) The present invention does not impose any limitations or any restrictions to the format of the sponsored fantasy player information. FIG. 5 illustrates an exemplary fantasy player news web page 110 as the form of the sponsored fantasy football player information SFP1 provided to the fantasy client device 20. As shown, fantasy player statistics 111 and three (3) player news feed items 112-114 are provided on webpage 110. A sponsor logo feed item 115 is displayed adjacent a player news feed item 112 in text form. A playable sponsor video clip feed item 116 is displayed adjacent player news feed item 113 in video clip form. And a sponsor hyperlink feed item 117 is displayed adjacent players news feed item 114 in hyperlink form.

(28) In view of the applications referenced above, those having ordinary skill in tile art will appreciate feed formatted content is structured data, such as, for example Electronic Data Interchange (EDI), Extensible Markup Language (XML), or a subset of a general format such as RSS (Rich Site Summary or. Really Simple Syndication), a hybrid or extension of some such standard, or the like. Feed formatted content may be accessed through a feed, stored in a local file, or the like of fantasy client device 20. Tile aforementioned feed items are the data corresponding to the feed formatted content of webpage 110. Concurrently or alternatively, subfeed formatted content in the form of a browser window or frame spawned by feed items can also be provided for webpage 110.

(29) In practice, the three sponsor items 115-117 can correspond to the same or difference sponsors. Furthermore, for a subsequent request for the same fantasy player information, new sponsorship information can be associated with the fantasy player information. In one embodiment, this is accomplished by implementing a technique for associating the sponsorship information of fantasy players to the fantasy player information of the fantasy players based on sponsorship selection criteria including, but not limited to, ad-targeting based criteria, profile based criteria, event based criteria and time based criteria as would be appreciated by those having ordinary skill in the art in view of the applications referenced above.

(30) FIG. 6 depicts a fantasy client request in the form of a recommendation of fantasy player information. Specifically, a stage S122 of a flowchart 120 and a stage S132 of a flowchart 130 encompasses one of the fantasy client devices 20 and fantasy content manager 70 exchanging a recommendation for fantasy player information FPIRC of one or more fantasy players (e.g., a recommendation for player news for Peyton Manning) to be transmitted to another one of the fantasy client devices 20). A stage S134 of flowchart 130 encompasses fantasy content manager 70 determining fantasy player information of fantasy player(s) responsive to the information recommendation (e.g., statistics and news feed items regarding Peyton Manning). A stage S136 of flowchart 130 encompasses fantasy content manager 70 associating sponsorship information of the fantasy players(s) corresponding to the fantasy player information (e.g., associating an advertisement/promotion of Indianapolis star in text, image, audio, video, multimedia, or hyperlink form to Peyton Manning's statistics and news feed items). Finally, a stage S124 of flowchart 120 and a stage S138 of flowchart 130 encompasses the intended fantasy client device 20 and fantasy content manager 70 exchanging the sponsored recommended fantasy football player information SRFPI.

(31) A fantasy player recommendation webpage can be similarly structured to fantasy player news web page 110 as shown in FIG. 5.

(32) FIG. 7 depicts a fantasy client request in the form of a fantasy player transaction request. Specifically, a stage S142 of a flowchart 140 and a stage S152 of a flowchart 140 encompasses a fantasy client device 20 and fantasy gameplay manager 80 exchanging a fantasy player transaction request TRRQ involving one or more fantasy players (e.g., a drafting, a waiver addition, a waiver release, a free agent addition, a free agent release and a trade involving one or more fantasy players). A stage S154 of flowchart 150 encompasses fantasy gameplay manager 80 determining whether the fantasy player transaction request is valid or invalid.

(33) In one embodiment, a stage S162 of a flowchart 60 encompasses fantasy gameplay manager 80 determining whether the fantasy player transaction request is in compliance with the fantasy league transaction policy. For example, such a policy may specify one or more transaction time periods and which types of transactions are legal and which types are illegal during each transaction time period (e.g., trading can only occur from Monday to Friday during each week of the fantasy season and a waiver addition can only occur after three days from a fantasy player's waiver release). The fantasy player transaction request is denied during a stage S164 of flowchart 160 if it is determined by fantasy gameplay manager 80 not to be in compliance with the fantasy league transaction policy. Otherwise, fantasy gameplay manager 80 associates relevant portions of sponsorship information of the subject fantasy player(s) to the relevant portions fantasy player information of the subject fantasy player(s) during a stage S166 of flowchart 160, and executes the sponsored transaction during a stage S168 of flowchart 160.

(34) In one embodiment, an execution of the sponsored transaction invokes a generation by fantasy gameplay manager 80 of one or more webpages related to the sponsored transaction. FIG. 9 illustrates an exemplary fantasy roster web page 170 generated in response to a sponsored transaction. As shown, a fantasy team roster 171 is provided on webpage 170. Provided below roster 171, are leased fantasy player hyperlink 172 and an associated sponsor audio clip feed item 175 are displayed. Next, an acquired fantasy player hyperlink 173 and an associated sponsor multimedia clip feed item 176 are displayed. Finally, a recommended fantasy player hyperlink 174 and an associated sponsor text feed item 177 are displayed.

(35) Referring again to FIG. 7, a stage S144 of flowchart 140 and a stage S168 of flowchart 160 encompasses the intended fantasy client device 20 and fantasy content manager 70 exchanging a fantasy player transaction confirmation TRCM for an executed sponsored transaction, or alternatively, stage S144 of flowchart 140 and a stage S168 of a flowchart 160 encompasses the intended fantasy client device 20 and fantasy content manager 70 exchanging a fantasy player transaction rejection TRRF for an a denied transaction request.

(36) FIG. 10 depicts a fantasy client request in the form of a fantasy player/team scoring request. Specifically, a stage S182 of a flowchart 180 and a.Math.stage S192 of a flowchart 190 encompasses a fantasy client device 20 and fantasy gameplay manager 80 exchanging a fantasy scoring request SCRO involving an individual fantasy player or a team of fantasy players. A stage S194 of flowchart 190 encompasses fantasy gameplay manager 80 determining a fantasy scoring of each fantasy player responsive to the request.

(37) In one embodiment, a stage S202 of a flowchart 200 encompasses fantasy gameplay manager 80 calculating fantasy player points in accordance with a league scoring policy based on fantasy player performance in real-time in relation to a schedule fantasy performance period. A stage S204 of flowchart 200 encompasses fantasy gameplay manager 80 determining fantasy team scoring based on a fantasy team starting lineup and any substitution indicators. Stages S202 and S204 are continually updated until such time the scheduled fantasy performance period has ended.

(38) For purposes of the present invention, the term substitution indicator is broadly defined herein as an indication of one fantasy player being substituted in fantasy team lineup by another fantasy player. In one embodiment, as shown in FIG. 12, the substitution indicator is generated by fantasy gameplay manager 80 as a substitution time stamp during a stage S212 of a flowchart 210 in response to a valid gameplay lineup substitution having one fantasy player designated as a substituted fantasy player and another fantasy player designated as the replacement fantasy player. The substitution time stamp can be on based on Greenwich Mean Time (GMT) or a time related to one or more player performance periods.

(39) A stage S214 of flowchart 210 encompasses fantasy gameplay manager 80 determining a substitute fantasy player's fantasy scoring and a replacement fantasy player's fantasy scoring based on the substitution time stamp and the player's performance periods. For example, if a fantasy client device 20 transacts a replacement of Peyton Manning for Tom Brady at the end of the first quarter of Manning's game as indicated by the substitution time stamp and Brady completed his game, then Manning's scoring will be based on his only quarter of game and Tom Brady's scoring will be based on the 2.sup.nd, 3rd and 4th quarters of Brady's game. Also by example, if a fantasy client transacts a replacement of Roger Clemens for Randy Johnson at the end of the 1st and 2nd innings pitched by Clemens as indicated by the substitution time stamp and Johnson completed his game, then Clemens' scoring will be based on his pitched 1st and 2nd innings and Randy Johnson's scoring will be based on his pitched 3.sup.rd-9th innings. From these two examples, those having ordinary skill in the art will appreciate the many benefits and various simple to complex implementations of the substitution time stamp in accordance with the present invention.

(40) Referring again to FIG. 10, a stage S196 of flowchart 190 encompasses fantasy gameplay manager 80 associates relevant portions of sponsorship information of the subject fantasy players(s) to the relevant portions fantasy player information of the subject fantasy player(s) as previously described herein, particularly in view of sponsorship selection criteria. A stage S184 of flowchart 180 and a stage S198 of flowchart 190 encompasses the intended fantasy client device 20 and fantasy gameplay manager 80 exchanging a fantasy player/team scoring report SCRP.

(41) FIG. 13 illustrates an exemplary fantasy player/team scoring report SCRP in the form of a webpage 220. As shown, five (5) fantasy players 230-234 with the respective fantasy scoring 240-244 and sponsor logo feed item 250-254 are displayed.

(42) Referring to FIG. 1, the present Invention does not impose any limitations or restrictions to the structural configurations of fantasy client devices 20, network system 30 and fantasy server system 40. FIG. 14 illustrates an example implementation of the network based environment illustrated in FIG. 1. Specifically, five (5) fantasy client devices in the form of a personal computer 21, a laptop 22, a personal data assistant 23, a mobile phone 24 and a smart phone 25 are structurally configured as known in the art to access via an Internet 31 an exemplary array of servers in the form a web server 41, a me server 42, an e-commerce server 43, a content management server 44, a real-time communication server 45, a streaming media server 46, a database server 47, a mobile information server 48 and a directory server 49, which are optionally linked via an Intranet 32. In practice, fantasy player information and sponsorship information are managed by this array of servers 41-49, and fantasy content manager 70 and fantasy gameplay manager 80 are embodied as software and/or firmware installed/distributed within one or more of the servers 41-49 whereby the processors of servers 41-49 can execute instructions of the software and/or firmware to implement the various inventive principles of the present invention.

(43) Those having ordinary skill in the art will appreciate that the array of servers 41-49 can physically exist as separate hardware platforms or logically exist on a minimum number of hardware platforms. Those having ordinary skill in the art will appreciate that some of the servers 41-49 can be eliminated and/or other types of servers can be added to this array. In one embodiment, web server 41 can individually execute the instructions of fantasy content manager 70 and fantasy gameplay manager 80 while fantasy player information and/or sponsorship information can be managed by file server 42, content management server 44, stream media server 46, and/or database server 47.

(44) Referring to FIGS. 1-14, the present invention does not impose any limitations or any restrictions to the form of fantasy client requests whereby any fantasy client request can invoke action by fantasy content manager 70 and/or fantasy gameplay manager 80. In practice, a fantasy client request can take the form of one of the fantasy client requests described herein, a combination of two or more of the fantasy client requests described herein, or any other form not described herein as would be appreciated by those having ordinary skill in the art.

(45) Furthermore, in some cases, sponsorship information may be not designated to one or more of the fantasy players. During these cases, all requests are executed as taught herein and under the inventive principles of the present invention exclusive of any association of sponsorship information to fantasy player information.

(46) An alert window can be displayed with fantasy point updates on players. The feed item associated with the alert can be accessed to see a streamed video clip of the play. Alerts can also be given to other player performance that are not being played or those on waivers or not drafted. In a real time substitution version of fantasy sports, for example football, the user can determine if it would be beneficial to replace a player that is injured or not performing well. In another window game information, including game score, time remaining, line up, having involved fantasy players can be displayed for both the users fantasy team and the users opponents fantasy team. The user can then have a continuous update of each game.

(47) A user can view all carries by your running backall routes by your receiverencourage more involvement and more sponsorship. Real time point counts on all players and ability to sub in and out during a gametime periods tracked by system. Ability to see what substitutions your opponent has made and you can counter with a moveyou are ahead and your opponent subs in a quarterbackif you have the receiver that quarterback throws toyou can sub in to lessen the potential impact.

(48) One type of information that may be displayed in the single item window is information related to fantasy sports. For example, a user may receive updates on the statistics of players they have specified, player injuries, players not currently held in their league that are having impressive statistics, scouting reports for weekly matcllups, or the like.

(49) A user may select that all Fantasy Football players on his team and/or opponents team with yardage, touchdowns and Fantasy points be displayed every 5 minutes or scrolled through while the user is watching TV or as a message to the users portable communication device on Sundays. Friends' messages related to the football or other game can be prioritized for display when the user is watching TV on game day.

(50) FIG. 15 shows representative feed formatted content 1500. Feed formatted content is structured data, such as for example Electronic Data Interchange (EDI), Extensible Markup Language (XML), or a subset of a general format such as RSS (Rich Site Summary or Really Simple Syndication), a hybrid or extension of some such standard, or the like. Feed formatted content 1500 may be accessed through a feed, stored in a local file, or the like. A feed is the data returned when a request for feed formatted content is made. Feed formatted content may include a feed header 1501. In one embodiment, feed header 1501 includes a header labeling feed formatted content 1500 as XML data, and further provides two element wrappers: rss and channel. Feed formatted content 1500 often represents multiple items, as is that displayed in FIG. 1. Each feed item 1506 may represent one or more news headlines, events, search results, items for sale or any other data. Feed item 1506 may contain any number of elements. For example, it may include a title element 1507, link element 1508, and a description element 1509. The term feed formatted content may describe an entire feed, a portion of a feed, a feed item, or a portion of a feed item.

(51) One type of information that may be displayed in the single item window is information related to fantasy sports. FIG. 16 illustrates a flowchart representative of one embodiment of a method for providing feed formatted content at 4000. Fantasy league and team data is stored at 4002. New fantasy information is received at 4004. For example, a server may receive feed formatted content representing fantasy information. A determination is then made whether the received fantasy information is related to the league and team date. If the information is related, feed formatted content is provided at 4406. For example, a user may receive updates on the statistics of players they have specified, player injuries, players not currently held in their league that are having impressive statistics, scouting reports for weekly matchups, or the like. In one embodiment, a fantasy sports information feed may be provided for each-player in a sport. Alternatively, the feed may include information in feed items indicating what play the information may be associated with.

(52) In one embodiment, feed formatted content may facilitate fantasy league play. FIG. 17 illustrates a flowchart representative of one embodiment of a method for operating a real time fantasy sports league at 4100. A user provides a fantasy team player list at 4102. A server creates feed formatted content based on real time statistics and on the fantasy team player list and provides the feed formatted content to the user at 4104. The user provides a substitution request at 4106. The server receives the substitution request, determines a time associated with the substitution, and modifies the feed formatted content based on the substitution request and the determined time at 4108. For example, statistics and feed formatted content may be provided and tallied to a user based on their specified team. A user may note that a player has been injured, or that it is halftime in a game, and may substitute in an alternate player at that time. The provided and tallied statistics may represent the team with the substitute starting at the time the substitution is submitted.

(53) In one embodiment, feed items may include one or more video, audio, or audio/video clips or links to one or more video, audio, or audio/video clips. Such a feed may be read to a computer, a cellphone, an internet connected digital video recorder (DVR), or the like. In one embodiment, a DVR or other device may aggregate clips into a highlight reel of important fantasy sports plays, for example for a user's active players in a league. FIG. 18 illustrates a flowchart representative of one embodiment of a method for operating a real time fantasy sports league at 4200. A user provides a fantasy team player list at 4202. A server receives a plurality of fantasy team players, receives a list of video clips, creates feed formatted content based on the video clips and the players, and provides tile feed formatted content at 4204. The user provides a request for a video clip based on the provided feed formatted content at 4206. The server may receive the request for a video clip and provide access to tile video clip at 4208. In this way a user may request either an individual highlight video clip of a fantasy player, or, in one embodiment, the user may request all video clips associated with one or more of their players. When more than one video clip is selected, a playlist may be provided. In one embodiment, the playlist may include one or more accompanying audio clips, for example selected by the user, to play in conjunction with the playlist. Commentary, audio, video or written may also be included in the feed formatted content. For example, an opponent may make supply a heckling comment to accompany a play in which one a user's key player is injured.

(54) In one embodiment, a fantasy sports feed can be continuously adjusted based on user selected or IAP suggested or provided factors, for example, for fantasy football some factors may include: player versus defense strength, player versus opponent time of possession, player's historical performance against opponent team, players performance at stadium, weather conditions, opponents players, player's recent performance, injury reports, etc. The user may select factors for the player selection feed, which then based on the factors selects the best team from the users fantasy team and all other available players. For example, during a football season Sunday, a fantasy player may be injured; the feed will provide a replacement player based on the selected or provided factors. The feed may make the selection for the user or alert the user with a feed item alert.

(55) Those having ordinary skill in the art will further appreciate various objects and advantages of the present invention, such as, for example, a realization of a comprehensive sponsorship of fantasy players on an individual basis and/or a team basis with an improved exchange of fantasy content between fantasy client devices 20 and fantasy server system 40.

(56) While the embodiments of the invention disclosed herein are presently considered to be preferred, various changes and modifications can be made without departing from the spirit and scope of the present invention. Tile scope of the invention is indicated in the appended claims, and all changes that come within the meaning and range of equivalents are intended to be embraced therein.