The present application relates generally to live events and, more particularly, methods and systems for enabling fans or audience members to participate in calling plays at football games and other events.
While traditional applications of technology for user participation in live events exist, they are generally passive forms of user participation. For example, some traditional entertainment shows allow fans to vote for a winner, but results are not shown until the end of a show, or days or weeks later. Fans can help decide which entertainer ‘wins’, but fans do not decide what activity occurs from minute-to-minute. Fans have minimal real-time impact on the real-time action.
In the context of sporting events, traditional applications allow users to participate in a fantasy game, where they can choose players and teams, and compete based on statistics corresponding to real time events in the sporting events. While real time events can affect a user's score or standing in traditional applications, the user has no ability to participate or influence real time events.
Systems and methods are disclosed for facilitating state-based participation in calling plays in a football game thereby allowing fans to proactively participate in real-time in the game with players, referees and coaches. In some aspects, the systems and methods comprise receiving, by a computing device, a user profile, the user profile corresponding to a user registered to vote in a real-time football game, the user profile comprising a coach score. In some aspects, the systems and methods comprise initiating, by the computing device, a sequence of states in response to a start of a play during the real-time football game. In some aspects, the sequence of states comprise a poll creation state for a first time period, the poll creation state comprising receiving, by the computing device, a submission of a set of plays from a computing device associated with a coach at a time corresponding to a time prior to an execution of a play in the real-time football game; a notification state for a second time period, the notification state comprising sending, by the computing device, the set of plays to a computing device associated with a registered user in a format such that the sets of plays automatically display upon the registered user device; a fan voting state for a third time period, the fan voting state comprising receiving, by the computing device, a vote from the registered user device, the vote corresponding to one play from the set of plays; a notification state for a fourth time period, the notification state comprising sending, by the computing device, a winning play to the registered user device and the coach device, the winning play based on results of the vote, such that a sum of the first time period, second time period, third time period, and fourth time period is equal to or less than 100 seconds; and a play in action state for a fifth time period, the play in action state comprising receiving, by the computing device, a result of a real-time play based on the winning play from a computing device associated with at least one of a referee and an administrator. In some aspects, the systems and methods comprise updating, by the computing device, the user score by comparing the vote with the winning play and with the result of the real-time play; and outputting, by the computing device, content to the registered user device related to the coach score.
In some aspects, the sequence of states terminates upon the start of a subsequent state. In some aspects, the submission of the set of plays further comprises a coach override, the coach override comprising a winning play selected by the coach. In some aspects, the poll creation state further comprises creating at least one of: a random set of plays, a set of plays based on prior game statistics, and a set of plays based on current game statistics, when the submitted set of plays comprises no plays. In some aspects, the content comprises a winning play score, the winning play score corresponding to a number of times a play selected by the user, from the set of plays associated with the poll creation state, is the winning play. In some aspects, the content further comprises at least one of a participation score and a scoring play score, the participation score corresponding to a number of plays where the user submits a vote, the scoring play score corresponding to a number of times a play selected by the user results in a team associated with the voting scoring a goal or preventing the scoring of a goal. In some aspects, the content comprises at least one of voting information, challenges, and education information, the voting information comprising a record corresponding to how a user earned the coach score, the challenges comprising comparing the coach score with coach scores corresponding to other user profiles, the education information comprising at least one of information and an activity to improve the coach score. In some aspects, the systems and methods comprise sending, by the computing device, state information to the referee device. In some aspects, the systems and methods comprise receiving, by the computing device, a duration of at least one of the first time period, second time period, third time period and fourth time period from the referee device. In some aspects, the systems and methods comprise outputting, by the computing device, live game information to at least one of the user device, the coach device, and the referee device. In some aspects, the sum of the time periods ranges from 30 seconds to 60 seconds.
Systems and methods are disclosed for determining a score for a user of a gaming platform such that the score reflects the user's success rate in calling plays in a sporting event. In some aspects, the systems and methods include receiving, by a computing device, a user profile, the user profile corresponding to a user registered to vote in a real-time football game, the user profile comprising a coach score. In some aspects, the systems and methods include initiating, by the computing device, a sequence of states in response to a start of a play during the real-time football game. In some aspects, the sequence of states includes a poll creation state, the poll creation state comprising receiving, by the computing device, a submission of a set of plays from at least one of a referee computing device, an administrator computing device, and a coach computing device at a time corresponding to a time prior to an execution of a play in the real-time football game. In some aspects, the sequence of states includes a first notification state, the first notification state comprising sending, by the computing device, the set of plays to a registered user computing device and the coach computing device in a format such that the sets of plays automatically displays on the registered user computing device and the coach computing device. In some aspects, the sequence of states includes a coach pick state, the coach pick state comprising receiving, by the computing device, a coach pick from the coach computing device, the coach pick corresponding to one play from the set of plays. In some aspects, the sequence of states includes a fan voting state, the fan voting state comprising receiving, by the computing device, a fan vote from the registered user computing device, the fan vote corresponding to one play from the set of plays. In some aspects, the sequence of states includes a second notification state, the second notification state comprising sending, by the computing device, a winning play to the registered user computing device and the coach computing device, the winning play based on results of the vote. In some aspects, the sequence of states includes a play in action state, the play in action state comprising receiving, by the computing device, an on-field result associated with a real-time play based on the winning play from at least one of a referee computing device and an administrator computing device. In some aspects, the systems and methods include calculating, by the computing device, a field score associated with the real-time play, the field score comprising points allocated based on at least one event associated with the on-field result during the real-time play, the field score comprising a positive value when the on-field result comprises a good result and a negative value when the on-field result comprises a bad result. In some aspects, the systems and methods include determining, by the computing device, the coach score, the coach score associated with points awarded based on the fan vote and at least one of the coach pick, the winning play, and the field score. In some aspects, the systems and methods include outputting, by the computing device, content to the registered user computing device related to the coach score.
In some aspects, the at least one event comprises at least one of rushing yardage, passing yardage, penalty yardage, first down, touchdown, interception, fumble, punt, sack, safety, touchback and field goal. In some aspects, the winning play comprises a play associated with a coach selected play when the results of the vote comprise a tie vote. In some aspects, the points awarded comprise no points awarded when the fan vote does not equal the winning play, the fan vote does not equal the coach pick, and the field score comprises a positive value. In some aspects, the points awarded comprise an against the grain point award when the fan vote does not equal the winning play, the fan vote does not equal the coach pick, and the field score comprises a negative value. In some aspects, the points awarded comprise a coach pick award when the fan vote does not equal the winning play, the fan vote equals the coach pick, and the field score comprises a positive value. In some aspects, the points awarded comprise a coach pick award and an against the grain award when the fan vote does not equal the winning play, the fan vote equals the coach pick, and the field score comprises a negative value. In some aspects, the points awarded comprise a field score award when the fan vote equals winning play and the fan vote does not equal the coach pick. In some aspects, the points awarded comprise a field score award and a coach pick award when the fan vote equals winning play and the fan vote equals the coach pick. In some aspects, the field score further includes points allocated based on a yardage score, the yardage score associated with a number of yards gained or lost during the real-time play. In some aspects, the methods and systems described herein are not limited to football, and may also be applied to other live events such as, e.g., soccer, baseball, golf, hockey, or basketball.
When football fans watch a football game, either live or on television, they have no involvement in how the game is played. They know little about the plays the coach of their team is picking to execute on the field, and have no ability to influence the coach's play choices. Various embodiments disclosed herein are directed to computer-implemented methods and systems for increasing fan involvement in games by enabling fans to actively participate in calling plays at football games.
As will be discussed in greater detail below, in accordance with various embodiments, a computer-implemented live-game system or engine is provided that enables fans of a team to collectively decide in real-time which plays should be executed by their team during a game. For each play, the coaches of the teams pick a set of possible plays, which the fans vote on. The system tabulates the fan votes, and the winning play can be executed on the field in real-time. The system provides users with access to a wide variety of information needed to participate in the system including information on plays, player rosters, teams, stats etc. The system also tracks each fan's coaching performance (e.g., the % of times the fan's play choice was the winning play, the % of times the fan's play succeeded (scored, achieved first down, gained certain yardage), or the % of times the fan's play selection likely would have been a better choice given the poor performance of the actual play run on the field, etc.). The system also enables fans to compete against one another, individually or in leagues, in their coaching skills.
While the exemplary embodiments illustrated herein relate to the game of American football, this is by way of example only. It should be understood that the methods and systems for increasing fan participation are not limited to football, and may also be applied to other live events such as, e.g., soccer, baseball, golf, hockey, basketball, movie screenings, game shows, award shows, sales meetings, political events, and business conferences. It should also be understood live-action events can be designed or simulated specifically for the systems and methods described herein. For example, instead of employing the systems and methods described herein for a live football game (e.g., a National Football League (NFL) game), live football games and football leagues can be created specifically for the systems and methods described herein. That is, a real, live game can include an athletic event run by a preexisting organization (e.g., NFL, National Basketball Association (NBA)), while a simulated game can be one that is designed by a developer of the systems and methods described herein. In some embodiments, a simulated game includes a league and teams of players playing specifically for the gaming systems and methods described herein. As described in more detail below, both simulated and real live games can include a coach, a coach-selected play, fans, fan voting and real time plays. In some embodiments, based on the outcome of a play, a coach-selected play, and fan voting, each fan can be awarded a field score and coach score.
The client devices communicate with the system 100 over a communications network 116. The communications network 116 can include any network or combination of networks including, without limitation, the Internet, a local area network, a wide area network, a wireless network, and a cellular network.
The client devices operated by users to access the live-game system 100 can include any computing device that can communicate with the computer server system including, without limitation, personal computers (including desktop, notebook, and tablet computers), smart phones (e.g., Apple-based smart phones and Android-based smart phones), wearable computer devices (e.g., smart watches and smart glasses), cell phones, personal digital assistants, and other mobile devices. The client devices include operating systems (e.g., Android, Apple iOS, and Windows Phone OS, among others) on which applications run. The operating systems allow programmers to create applications (often called “Apps”) to provide particular functionality to the devices.
A representative client device can include at least one computer processor and a storage medium readable by the processor for storing applications and data. The client device also can include input/output devices, one or more speakers for acoustic output, a microphone for acoustic input, and a display for visual output, e.g., an LCD or LED display, which may have touch screen input capabilities.
Message listener 202 is active software built into the system. It provides asynchronous event handling that defines the initial action to be taken as each message arrives. Different actions may be defined for different message types.
Record manager 204 includes a database for storing user voting records (e.g., votes during a game). The database can include any physical database or cloud-based data storage (e.g., Mongo database instance).
Score manager 206 includes a database for storing game statistics (e.g., wins, losses, play executed during a game). The database can include any physical database or cloud-based data storage (e.g., Mongo database instance). As described in more detail below, information from the database can be utilized by a scoring engine (also referred to herein as a coach score engine or a field event manager (FEM)) for determining a score for a user (also referred to herein as a coachscore or a coach score). In some embodiments, a scoring engine is positioned with the score manager 206. In some embodiments, a scoring engine is a separate logical entity.
Poll manager 208 controls state logic for polling. As described in more detail, polling can include a series of discrete states.
AMQP 210 comprises an Advanced Message Queuing Protocol (e.g., RabbitMQ). AMQP can support a variety of protocols and includes message orientation, queuing, and routing.
Game manager 212 includes a database for storing real-time events and statistics during a game. The database can include any physical database or cloud-based data storage (e.g., Mongo database instance). Game manger 212 can communicate with Ref App 222. As described in more detail below, game manager 212 can send Ref App 222 real-time data corresponding to a game. Ref App 222 can send instructions to Game Manager 212, based on the real-time data, to update state information (e.g., state information for polling) and information for display on one or more coach device 226 or fan device 228.
Engagement service 214 represents multiple discreet services that coordinate elements of the game experience. These services include a user interface, logic, and storage. One of the services, FanScore Moderator 224, stores the data behind multiple question-and-answer games (e.g., the name of each game, one to one-thousand questions, timing logic associated with answers for each of the questions, and tips for each of the questions). A person operating the FanScore Moderator can define a game, initiate a game, and trigger the delivery of each question (e.g., the first question is sent 10 minutes before kickoff, the second question during the first timeout), and identify the recipients of each question (e.g., all registered fans or fans voting with only one of the two teams). Another service, CoachScore Moderator 224, allows an operator to evaluate the results of plays run on the field in real time (e.g., declaring an error on a play and assessing the success of the play run on the field). These evaluations are then used to create each Fan's CoachScore.
Coach manager 216 includes a database for storing coaching records (e.g., information about plays, players, scheduling) and other data that is used in multiple devices across the system. The database can include any physical database or cloud-based data storage (e.g., Mongo database instance). Coach manager 216 is in communication with a coach application 226. Coach manager 216 can display information in the database to the coach device and receive edits and changes from the coach device to information in the database.
Vote manager 218 coordinates voter polling. Vote manager 218 maintains the logic for communication and controls that communication with fan devices 228 via fan connections 240. Fan Connections 240 declares and manages the communication channel used with fan devices. Vote manager 218, through a fan connection module, can push a poll to fan device 228 and receive results from the poll.
Fan device 228 represents the mobile devices used by fans to participate in calling plays. The Info Service 220 includes web services that execute key processes (e.g., retrieving fan profile information, updating playbook information in fan apps, etc.). The information service refers to a fast, in-memory data store 230 (e.g., Redis).
The system provides users with access to a wide variety of information needed to participate in the system including information on plays, player rosters, teams, stats etc.
In one or more embodiments, fans can download a Fan App on their client devices to access the system.
Fans who are registered and logged in can enter a Fan App Dashboard as illustrated in the exemplary screenshot of
Fans can access team information 700, including coach and player videos and talk sessions as illustrated in the exemplary screenshot of
Along with this content, the system also offers fans functionalities to track their performance —My Stats 1501 shown in the exemplary screenshot of
In some embodiments, Coach Score can be displayed on a user device, as shown in the exemplary screenshot of
A FanScore page can also include an Events section, as shown in the exemplary screenshot of
In some embodiments, fan coins can also be awarded for social sharing, watching a video advertisement, completing a profile, participating in predictive questioning, participating in head to head challenges, and participating in surveys. Each of these activities can result in a different number of fan coins awarded. For example, fan coins can be awarded according to the following scheme:
In some embodiments, fan coins can be redeemed for prizes or opportunities to earn larger prizes. For example, fan coins can be redeemed for sweepstakes entries, charitable donations, and cash cards.
In some embodiments, fan coins can also be wagered in head to head challenges. Fans can challenge other fans to a head to head competition and wager fan coins. In some embodiments, the winner of the challenge receives their fan coins back and collects the loser's fan coins. Users can issue multiple challenges per game and can wager an amount of fan coins. In some embodiments, 1 to 500 fan coins can be wagered.
Fans may participate in Challenges, as shown in the exemplary screenshot of
Fans can also access real-time results on the system, as shown in the exemplary screenshot of
The coach score moderator application can rank (e.g., good, neutral, bad or 1st, 2nd, 3rd) the play result seen on the field relative to the historical expectations of the two plays not selected, and submit any additional factors, especially errors (dropped pass, fumble, etc.), that impact the assessment of the play 3002. The application can display which plays are suggested by a coach and which play was run on a field 30003001. The ranking can come from a human operator or can be determined by a computing device.
The Playbook section of the Fan App is indicated by way of example in the screenshot of
The content items discussed above are live and active content during an actual game. When a game starts, the Fan App automatically changes to a gamecasting/push app determined by a League Official as shown in the exemplary screenshots of
Once a game is in progress and a fan is logged in correctly, the system automatically pushes a vote to the app as shown in the exemplary screenshots of
Once fans receive a poll from the system as illustrated in the exemplary screenshots of
In addition to the live football game, fans can compete against other fans and other groups of fans on their coaching expertise. Fans can choose and structure the ways in which they want to compete 4300 as shown in the exemplary screenshot of
The system allows coaches/coordinators to enter plays or formations to facilitate player coaching, game planning, and play selection. As shown in the exemplary screenshot of
As shown in the exemplary screenshot of
Coaches/coordinators can build scripts of plays that can be used for game planning, coaching, and easy selection as shown in the exemplary screenshot of
As shown in the exemplary screenshot of
As shown in the exemplary screenshot of
Coaches/coordinators can pick plays to be voted on by fans as shown in the exemplary screenshot of
As shown in
According to some embodiments, a Coach Management System allows coaches to select their plays during games and coordinate other aspects of planning and executing plays during a game. An interface allows coaches to pick a set of plays offered to fans during each play, to see the winning play selected by fans, and to call “overrides” when they have to get their play run.
In some embodiments, the Coach Management System allows football coaches to manage everything about a football team, as described in more detail below. Briefly, a roster module can store the names, profiles, and video of all players. Scouting can keep the profiles and assessments of all potential draftees and opposing players. Medical Manager can track all injuries, readying them for the injury report. Playbook can give coaches a place to create any play they want, to organize each play by any attribute, and to create installs, scripts, and game plans for any situation. Calendar can allow assistant coaches to structure daily coaching plans that roll up into weekly and seasonal plans managed by head coaches. Analytics can allow coaches to understand the performance of all plays by situation, package and player.
As shown in the exemplary screenshot of
Production personnel can access the system as shown in the exemplary screenshot of
As shown in the exemplary screenshot of
The system is modeled as a finite state machine. This means the system is in exactly one state at any given time. As different actions occur (referee pushing a button, timer completed, etc.) the system moves onto other states. These states define what is possible and occurring at any given moment. The finite machine can be executed by a computing device.
When a new game is created and scheduled, its first state is the “pregame” state. The system has been configured with two teams, but the game hasn't actually started yet. In this state users will be able to interact with the game in different ways from when the game is running. This might include interactions/planning with their team coach.
The only action from here that will change the state of the game is having the appropriate official input the command to start the game (via the Admin Application). This will transition the game to the state “coach creating polls”.
All states except “pregame” and “game over” are considered to mean the game is currently “active”.
This state means the coaches are currently selecting plays for inclusion in polls that will be sent out to and voted on by fans. Coaches may also submit a “coach override” during this time. In this state, the system accepts play choice options for a poll from the Coach Application. A timer is started which can automatically transition to the “notifying fans of polls” state. The timer can range between 1 second and 60 seconds. In some embodiments, the timer is set for seven seconds.
This state means the system is currently working to send both polls (one for each team) to their fans. In this state, coaches are no longer able to submit play choice options for a poll. A timer is started that will automatically transition to the “fan voting” state. The timer can range between 1 second and 60 seconds. In some embodiments, the timer is set for two seconds. The system verifies that each coach was able to create a poll. If a coach did not create their poll, the system can create a poll for them and populate it with three random play options. Once both polls are ready they are transmitted to all fans.
This state means the system is accepting votes from all fans. In this state, the poll sent to the fan in the previous state is made visible now. Vote submissions are now accepted by the system. A timer is started which automatically transitions the game to the “notify everyone of results” state. The timer can range between 1 second and 60 seconds. In some embodiments, the timer is set for ten seconds.
This state means the system is sending out vote results to all fans and coaches. In this state, votes are no longer accepted by the system. Poll voting results are tabulated and a winning play or a tie is determined for each poll. A summary of each poll results are broadcast to all fans and coaches. A record of the vote summaries is stored for future use. A timer is started which automatically transitions the game to the “play in action” state. The timer can range between 1 second and 60 seconds. In some embodiments, the timer is set for two seconds.
This state means that the winning plays are now being executed on the field by the actual football players. The system is waiting for input via the Admin Application about the final result of the play. Depending on the results, the game can transition into two different states:
In this state the game is now over and is no longer capable of going back to any of the other states.
In some embodiments, the total execution time for the first four states is under 100 seconds. In some embodiments, the total execution time is in between 30 and 60 seconds.
As described above, a live game, as described herein, can include both real, live games or simulated live games. For example, a real, live game can include an athletic event run by a preexisting organization (e.g., NFL, National Basketball Association (NBA)), while a simulated game can be one that is designed by a developer of the systems and methods described herein. In some embodiments, a simulated game includes a league and teams of players playing specifically for the gaming systems and methods described herein. As described above, both simulated and real live games can include a coach, a coach-selected play, fans, fan voting and real time plays. In some embodiments, based on the outcome of a play, a coach-selected play, and fan voting, each fan can be awarded a field score and coach score. Also as described above, calculation of a coach score and a field score can occur in a scoring engine or a field event manger (FEM) in the live-game system 100 of
In some embodiments, the systems and methods described herein incentivize fans to achieve the highest possible coach score within a given game, weekend or season. In some embodiments, the systems and methods described herein also incentivize fans to accumulate as many fan coins as possible, which can be used to redeem prizes or gaming advantages offered by the gaming platform.
As described above, in some embodiments, a coach score is a metric that measures a fan's ability to call a successful and effective play. As described above, a fan can choose to play with a particular team for any duration of time. As such, a fan can call either offensive or defensive plays, as applicable for an event. A fan can earn points towards a coach score over the course of a season. In some embodiments, the best cumulative score over a set period (e.g., one game, five games, all games) is the winner. A winner can be determined based on a total population of fans or users affiliated with the gaming platform (e.g., holder of an account on the gaming platform) or a subset of the fans or users affiliated with the gaming platform.
First, a gaming engine receives data associated with a coach override instruction 7602. A coach override refers to an override of fan voting for a play. When the gaming engine receives data associated with instructions to play with a coach override 7604, no points are awarded to fans for a play 7620. A coach override instruction can be received when an anomaly is detected for a particular play (e.g., lag in system processing, fan voting below a threshold amount). The coach override instruction can also be associated with a human intervention based on the live action/situation on the field and whether that situation warrants a change in play that only the coach or another on field human can determine. A coach override instruction can be received as an input from any of a referee application 222, moderator devices 224, or coach devices 226. As described above, a coach override can be limited in number (e.g., 4-5 per half of a game).
When a the gaming engine receives data associated with instruction to play with no coach override 7604, the gaming engine begins with a voting and scoring process. The first step of the voting process is to receive a coach pick for a play 7606. As described above, a play can be chosen from any set or subset of plays. For example, a coach can select a single play from any number of plays available within the gaming engine. In some embodiments, a coach can create a play to add to the collection of plays within the gaming engine. In some embodiments, a coach can choose a particular play and also choose a set of plays from which fans can select from.
After a coach makes a play(s) selection, fan votes are received 7608. As described above, fans can choose from any number of plays designated by the gaming engine. For example, a fan can choose from any of the plays available within the gaming system or from a subset of plays that are limited to the fan for a particular play. The subset of plays can be designated by a default setting within the gaming system or as a result of plays chosen by a coach or other game administrator during a play.
After all fans participating in a play have cast their votes, the play with the most number of fan votes is designated as a fan pick 7610. If there is a tie between two or more plays after the fan votes are tabulated, a coach can decide on which play to run on the field. In the event of a tie, the gaming system can also randomly select a play to run on the field.
Next, a play is sent to the team on the field such that the team can run the play 7612. In some embodiments, the team runs a play associated with the fan pick. In some embodiments, the team runs a play associated with a field override play. A field override play can be a play designated by a coach or system administrator, or chosen by the gaming system as a default or randomly selected play.
After the play is run on the field 7612, a field score is calculated 7614. A field score is associated with an outcome of a play. More specifically, a field score is an evaluation of how a fan's play performs from an on-field , statistical standpoint. Users can be rewarded or penalized based on the statistical success of a play. For example, a play that is unsuccessful (e.g., an offensive play that results in an interception rather than a first down or a touchdown) can result in a low or negative field score. A play that is successful (e.g., an offensive play that results in a first down or a touchdown) can result in a positive or high score. As described in more detail in
After calculating a field score 7614, coach score points are awarded based on at least one of coach pick, fan vote, and a result of the play 7616. As described above and in more detail below in
As described above in
When a fan's vote does not equal a play run on the field, the next step is to determine whether the fan's vote equals the coach pick 7704. When the fan's vote equals the coach pick, the next step is to determine whether the on-field result is good or bad 7708. As described above, a good on-field result can be associated with a positive or high field score while a bad on-field result can result in a negative or low field score. When the on-field result is good 7708, the fan is awarded coach score points 7728 associated with coach pick points 7808. Coach pick points 780878127814 can be taken from a coach pick score table 7810. In some embodiments, the coach pick score table 7810 can include coach scores that vary based on whether a coach score aligns with a good or bad play result. When the on-field result is bad 7708, the fan is awarded both coach pick points 7814 and against the grain points 7818. Against the grain points 7818 can refer to points awarded to a fan when a fan does not vote with a coach or the majority and the play on the field results in a negative outcome.
When a fan's vote does not equal the coach pick 7704, the next step is to determine whether the on-field result is good or bad 7706. If the result is good, the fan is awarded coach score points 7722 associated with no points awarded 7802. If the result is bad, the fan is awarded coach points 7724 associated with against the grain points 7804. Against the grain points 78047818 can refer to points awarded for not choosing the bad play run on the field, as well as not choosing the bad play run on the field and choosing a play that the coach did not choose. Against the grain points can be derived from an against the grain score table 7806. The table 7806 contains varying points amounts for different types of against the grain points.
First, event data is received for the play 7902. Events, as described in more detail in the text accompanying
Referring to step 7904, an event score is calculated. In some embodiments, an event score is calculated by matching a portion of the event data with a table of information associated with the gaming engine. As described in more detail below in
Referring to step 7906, a yardage score is calculated. In some embodiments, an yardage score is calculated by using a yardage multiplier table. The fieldscore point system allocates points to various onfield situations—yards gained/loss, fumble etc. From a yardage perspective if the point for yardage is 1 and the yards gained on a play is 10 then the fan receives 10 Fieldscore points.
Referring to step 7908, the event and yardage scores are added together and stored. Next, the gaming engine determines if all events are entered for a play 7910. If not all events are entered, the gaming engine receives more event data for the play 7902. If all events are entered 7910, then the gaming engine adds up all of the points associated with each of the sets of event data 7912.
Event category 8002 refers to a type of event. As described above, multiple events can be present in a single play. For example, if a play involved running the ball and resulted in a first down, that play would be associated with event categories 8002 of run and first down.
Beginning possession 8004 refers to, e.g., in football, whether a team has possession of the ball at the beginning of a play. If a team has possession of the ball, beginning possession 8004 is associated with offense. Conversely, if a team does not have possession of the ball, beginning possession 8004 is associated with defense.
Event details 8006 refers to additional details associated with an event category 8002. For example, when the event category 8002 is associated with points after touchdown (PAT), event details 8006 can include whether an extra point is awarded with a successful field goal attempt or whether two points are awarded for a successful conversion (e.g., running or passing the ball into the in zone after the initial touchdown). In some embodiments, an event comprises at least one of rushing yardage, passing yardage, penalty yardage, first down, touchdown, interception, fumble, punt, sack, safety, touchback and field goal.
Ending possession 8008 refers to, e.g., in football, whether a team has possession of the ball at the end of a play. Ending possession 8008 can be the same as beginning possession 8002 when a team retains control of the ball from the beginning of the play to the end of the play. Conversely, ending possession 8008 can be different from beginning possession 8002 when a team loses possession of the ball or gains possession of the ball.
Points 8010 are points associated each combination of event category 8002, beginning possession 8004, event details 8006, and ending possession 8008. Points can be awarded or subtracted for good and bad results, respectively. For example, a team with beginning possession 8004 of offense that has a ball intercepted during a play can be awarded points of −3. As another example, a team with beginning possession 8004 of defense that recovers a fumbled ball can be award point of +3. As explained above, all events that are relevant to a play can have their associated scores summed to form a total point value for a fan for a particular play.
The processes of the live-game system described above may be implemented in software, hardware, firmware, or any combination thereof. The processes are preferably implemented in one or more computer programs executing on a programmable computer (which can be part of the computer server system) including a processor, a storage medium readable by the processor (including, e.g., volatile and non-volatile memory and/or storage elements), and input and output devices. Each computer program can be a set of instructions (program code) in a code module resident in the random access memory of the computer. Until required by the computer, the set of instructions may be stored in another computer memory (e.g., in a hard disk drive, or in a removable memory such as an optical disk, external hard drive, memory card, or flash drive) or stored on another computer system and downloaded via the Internet or other network.
Having thus described several illustrative embodiments, it is to be appreciated that various alterations, modifications, and improvements will readily occur to those skilled in the art. Such alterations, modifications, and improvements are intended to form a part of this disclosure, and are intended to be within the spirit and scope of this disclosure. While some examples presented herein involve specific combinations of functions or structural elements, it should be understood that those functions and elements may be combined in other ways according to the present disclosure to accomplish the same or different objectives. In particular, acts, elements, and features discussed in connection with one embodiment are not intended to be excluded from similar or other roles in other embodiments.
Additionally, elements and components described herein may be further divided into additional components or joined together to form fewer components for performing the same functions. For example, the computer server system may comprise one or more physical machines, or virtual machines running on one or more physical machines. In addition, the computer server system may comprise a cluster of computers or numerous distributed computers that are connected by the Internet or another network.
Accordingly, the foregoing description and attached drawings are by way of example only, and are not intended to be limiting.
Those of skill in the art would appreciate that the various illustrations in the specification and drawings described herein can be implemented as electronic hardware, computer software, or combinations of both. To illustrate this interchangeability of hardware and software, various illustrative blocks, modules, elements, components, methods, and algorithms have been described above generally in terms of their functionality. Whether such functionality is implemented as hardware, software, or a combination depends upon the particular application and design constraints imposed on the overall system. Skilled artisans can implement the described functionality in varying ways for each particular application. Various components and blocks can be arranged differently (for example, arranged in a different order, or partitioned in a different way) all without departing from the scope of the subject technology.
Furthermore, an implementation of the communication protocol can be realized in a centralized fashion in one computer system, or in a distributed fashion where different elements are spread across several interconnected computer systems. Any kind of computer system, or other apparatus adapted for carrying out the methods described herein, is suited to perform the functions described herein.
A typical combination of hardware and software could be a general purpose computer system with a computer program that, when being loaded and executed, controls the computer system such that it carries out the methods described herein. The methods for the communications protocol can also be embedded in a computer program product, which comprises all the features enabling the implementation of the methods described herein, and which, when loaded in a computer system is able to carry out these methods.
Computer program or application in the present context means any expression, in any language, code or notation, of a set of instructions intended to cause a system having an information processing capability to perform a particular function either directly or after either or both of the following: a) conversion to another language, code or notation; b) reproduction in a different material form. Significantly, this communication protocol can be embodied in other specific forms without departing from the spirit or essential attributes thereof, and accordingly, reference should be had to the following claims, rather than to the foregoing specification, as indicating the scope of the invention.
The communications protocol has been described in detail with specific reference to these illustrated embodiments. It will be apparent, however, that various modifications and changes can be made within the spirit and scope of the disclosure as described in the foregoing specification, and such modifications and changes are to be considered equivalents and part of this disclosure.
This application is a continuation of U.S. application Ser. No. 15/069,273, filed Mar. 14, 2016, entitled “COMPUTER-IMPLEMENTED METHODS AND SYSTEMS ENABLING FAN PARTICIPATION IN CALLING PLAYS AT SPORTING AND OTHER EVENTS,” which is a continuation in part of U.S. application Ser. No. 14/575,698, filed Dec. 18, 2014, entitled “Computer-Implemented Methods and Systems Enabling Fan Participation in Calling Plays at Sporting and Other Events,” now patented as U.S. Pat. No. 9,751,018, which claims priority under 35 U.S.C. 119(e) to U.S. Provisional Application No. 61/918,350, filed Dec. 19, 2013, entitled “Computer-Implemented Methods and Systems Enabling Fan Participation in Calling Plays at Sporting and Other Events,” the contents of each of which are hereby incorporated by reference in their entirety.
Number | Date | Country | |
---|---|---|---|
61918350 | Dec 2013 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 15069273 | Mar 2016 | US |
Child | 15723727 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 14575698 | Dec 2014 | US |
Child | 15069273 | US |