Horse race betting graphical user interface
Abstract
A method of generating a graphical user interface for horse race betting includes displaying a first list of horses scheduled to run a first race from among a plurality of horses, displaying, in association with each horse of the first list of horses, a win selection element by which a user of the graphical user interface may mark the horse as selected to win the first race, displaying an automatic ticket generation button by which a user may request an automatic selection of horses, and, in response to a user interaction with the automatic ticket generation button, marking one or more horses of the first list of horses as selected to win the first race based on predicted win percentages of the horses of the first list. The method may include displaying, in association with each horse of the first list of horses, the predicted win percentage of the horse.
Claims
exact text as granted — not AI-modified1 - 26 . (canceled)
27 . A method of generating a graphical user interface for horse race betting, the method comprising:
displaying a first list of horses scheduled to run a first race from among one or more races; displaying, in association with each horse of the first list of horses, one or more manual selection elements by which a user of the graphical user interface may mark or unmark the horse as selected to win the first race; displaying an automatic ticket generation button by which the user may request an automatic selection of horses; in response to a first user interaction with the automatic ticket generation button, marking one or more horses of the first list of horses as selected to win the first race based on predicted win percentages of the horses of the first list, wherein the one or more horses marked in response to the first user interaction with the automatic ticket generation button maximizes a function of a predicted ticket win percentage, the predicted ticket win percentage being calculated from the predicted win percentages of the horses and representing a likelihood that, in each respective race from among the one or more races, a horse will win from among the horses marked to win that respective race; and, in response to a user interaction with the one or more manual selection elements of at least one horse of the first list of horses, imposing one or more constraints on the function.
28 . The method of claim 27 , wherein the marking in response to the first user interaction with the automatic ticket generation button occurs before the user interaction with the one or more manual selection elements.
29 . The method of claim 28 , further comprising, in response to a second user interaction with the automatic ticket generation button that occurs after the user interaction with the one or more manual selection elements, marking one or more horses of the first list of horses as selected to win the first race based on the predicted win percentages of the horses of the first list, wherein the one or more horses marked in response to the second user interaction with the automatic ticket generation button maximizes the function of the predicted ticket win percentage with the one or more constraints imposed.
30 . The method of claim 27 , wherein the one or more manual selection elements displayed in association with each horse of the first list of horses further allows the user to mark or unmark the horse as selected not to win the first race.
31 . The method of claim 27 , wherein the one or more manual selection elements displayed in association with each horse of the first list of horses further allows the user to mark or unmark the horse as selected to finish in second place in the first race.
32 . The method of claim 31 , wherein the one or more manual selection elements displayed in association with each horse of the first list of horses further allows the user to mark or unmark the horse as selected not to finish in second place in the first race.
33 . The method of claim 27 , further comprising:
displaying a second list of horses scheduled to run a second race from among the one or more races; displaying, in association with each horse of the second list of horses, one or more manual selection elements by which the user may mark or unmark the horse as selected to win the second race; in response to the first user interaction with the automatic ticket generation button, further marking one or more horses of the second list of horses as selected to win the second race based on predicted win percentages of the horses of the second list; and, in response to a user interaction with the one or more manual selection elements of at least one horse of the second list of horses, imposing one or more constraints on the function.
34 . The method of claim 33 , further comprising:
displaying a third list of horses scheduled to run a third race from among the one or more races; displaying, in association with each horse of the third list of horses, one or more manual selection elements by which the user may mark or unmark the horse as selected to win the third race; in response to the first user interaction with the automatic ticket generation button, further marking one or more horses of the third list of horses as selected to win the third race based on predicted win percentages of the horses of the third list; and, in response to a user interaction with the one or more manual selection elements of at least one horse of the third list of horses, imposing one or more constraints on the function.
35 . The method of claim 27 , further comprising:
displaying a maximum ticket price selector by which the user may select a maximum ticket price; and, in response to a user interaction with the maximum ticket price selector, imposing one or more additional constraints on the function based on a bet amount and the selected maximum ticket price.
36 . The method of claim 35 , further comprising displaying a bet amount selector by which the user may select the bet amount.
37 . The method of claim 27 , further comprising submitting a finalized selection of marked horses to a third-party provider of direct bet placement functionality.
38 . The method of claim 37 , wherein said submitting is via a link to a third-party website.
39 . The method of claim 37 , wherein said submitting is via a third-party API.
40 . A non-transitory program storage medium on which are stored instructions executable by a processor or programmable circuit to perform operations for generating a graphical user interface for horse race betting, the operations comprising:
displaying a first list of horses scheduled to run a first race from among one or more races; displaying, in association with each horse of the first list of horses, one or more manual selection elements by which a user of the graphical user interface may mark or unmark the horse as selected to win the first race; displaying an automatic ticket generation button by which the user may request an automatic selection of horses; in response to a first user interaction with the automatic ticket generation button, marking one or more horses of the first list of horses as selected to win the first race based on predicted win percentages of the horses of the first list, wherein the one or more horses marked in response to the first user interaction with the automatic ticket generation button maximizes a function of a predicted ticket win percentage, the predicted ticket win percentage being calculated from the predicted win percentages of the horses and representing a likelihood that, in each respective race from among the one or more races, a horse will win from among the horses marked to win that respective race; and, in response to a user interaction with the one or more manual selection elements of at least one horse of the first list of horses, imposing one or more constraints on the function.
41 . The non-transitory program storage medium of claim 40 , wherein the marking in response to the first user interaction with the automatic ticket generation button occurs before the user interaction with the one or more manual selection elements.
42 . The non-transitory program storage medium of claim 41 , wherein the operations further comprise, in response to a second user interaction with the automatic ticket generation button that occurs after the user interaction with the one or more manual selection elements, marking one or more horses of the first list of horses as selected to win the first race based on the predicted win percentages of the horses of the first list, wherein the one or more horses marked in response to the second user interaction with the automatic ticket generation button maximizes the function of the predicted ticket win percentage with the one or more constraints imposed.
43 . A system for generating a graphical user interface for horse race betting, the system comprising:
a user device configured to display a first list of horses scheduled to run a first race from among one or more races, to display, in association with each horse of the first list of horses, one or more manual selection elements by which a user of the user device may mark or unmark the horse as selected to win the first race, and to display an automatic ticket generation button by which the user may request an automatic selection of horses; and a server in communication with the user device, the server being configured, in response to a first user interaction with the automatic ticket generation button, to mark one or more horses of the first list of horses as selected to win the first race based on predicted win percentages of the horses of the first list, wherein the one or more horses marked in response to the first user interaction with the automatic ticket generation button maximizes a function of a predicted ticket win percentage, the predicted ticket win percentage being calculated from the predicted win percentages of the horses and representing a likelihood that, in each respective race from among the one or more races, a horse will win from among the horses marked to win that respective race; wherein the server is configured to impose one or more constraints on the function in response to a user interaction with the one or more manual selection elements of at least one horse of the first list of horses.
44 . The system of claim 43 , wherein the server is configured to mark the one or more horses in response to the first user interaction with the automatic ticket generation button before the user interaction with the one or more manual selection elements occurs.
45 . The system of claim 44 , wherein the server is configured, in response to a second user interaction with the automatic ticket generation button that occurs after the user interaction with the one or more manual selection elements, to mark one or more horses of the first list of horses as selected to win the first race based on the predicted win percentages of the horses of the first list, wherein the one or more horses marked in response to the second user interaction with the automatic ticket generation button maximizes the function of the predicted ticket win percentage with the one or more constraints imposed.
46 . The system of claim 43 , wherein the user device is configured to display the first list of horses, the one or more manual selection elements, and the automatic ticket generation button using a web browser or mobile application.Join the waitlist — get patent alerts
Track US2021233365A1 — get alerts on status changes and closely related new filings.
We store only your email — no account needed. See our privacy policy.