Wagering Web Service System & Method

• US 20100151935A1
• Filed: 05/26/2009
• Published: 06/17/2010
• Est. Priority Date: 12/13/2008
• Status: Active Grant

• Current Assignee: Harry Platis
• Original Assignee: Harry Platis
• Inventors: Platis, Harry, Shannon, Kristopher Michael
• Granted Patent: US 8,277,311 B2
• Time in Patent Office: Days
• US Class Current: 463/25
• CPC Class Codes: A63F 9/24 Electric games; Games using electronic circuits not otherwise provided for video games A63F13/00; computerized gaming systems G07F17/32
• CPC Class Codes: G06Q 10/06 Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
• CPC Class Codes: G06Q 20/04 Payment circuits
• CPC Class Codes: G07F 17/32 for games, toys, sports, or amusements
• CPC Class Codes: G07F 17/3225 Data transfer within a gaming system, e.g. data sent between gaming machines and users
• CPC Class Codes: G07F 17/3255 Incentive, loyalty and/or promotion schemes, e.g. comps, gaming associated with a purchase, gaming funded by advertisements
• CPC Class Codes: G07F 17/3258 Cumulative reward schemes, e.g. jackpots

Abstract

A system to coordinate a wagering event using a virtual Web server with an administration application and a server database. The administration application is executable code which can generate a first event page from an event category page. The administration application also has a player management page, a pool page and a ticket management set of pages. The administration application interoperates with a banking application and a casino application. The administration application will send the event information to the casino application, receive wager information from the casino application, coordinate wager amounts with the banking application, close the wagering, monitor the event, update pool, close the pool, and allocate the winnings and losses.

Claims

1. A system for coordinating a wagering event said system comprising:

a. a virtual web server comprising an administration application;

a server 5 database;

b. said administration application configured as executable code to generate a first event page utilizing an event category page;

said first event page comprising a first set of player elements;

c. said administration application further configured as executable code to generate a first pool page for management of a first wager pool;

d. said administration application further configured as executable code to interoperate with a banking application and a casino application, said banking application located at a financial institution, said casino application located at a casino location;

e. said administration application further configured as executable code to send and receive a wager from said casino application, said wager on a player from said first set of player elements;

f. said administration application further configured as said executable code to coordinate a wager amount to said banking application and to credit said first pool with said wager amount in a wager ledger.

2. The system according to claim 1 wherein said server database further comprises:

a. an event object configured to maintain event information from said first event page;

b. an event category object configured to maintain event category information from said event category page.

c. a first set of player objects configured to maintain player information from said first set of player elements.

d. a first pool object configured to maintain pool information from said first pool page.

e. a wager object configured to maintain wager information from said wager, said wager information comprising said wager amount.

f. a wager detail component comprising a wager identification component, a player identification component, and a sequence component;

said wager detail component configured to record wager detail information into said server database.

3. The system according to claim 2 wherein said server database further comprises:

a. a wager detail object comprising a wager identification object configured to maintain information from said wager identification component in said server;

b. a player identification object configured to maintain information from said player identification component in said server database;

c. a sequence object configured to maintain sequence information from said sequence component in said server database;

a. said wager detail object configured to maintain said wager detail information from said wager detail component in said server database.

4. The system according to the claim 3 wherein said administration application further comprises:

a. a pool type component, comprising a win bet or a mandatory pay out.

b. a player odds component configured to calculate, update, and send to said casino application, odds on a player ID component correlated to a particular pool ID component;

c. a player odds object configured to maintain information from said player odds component in said server database.

5. The system according to claim 1 wherein said first event page further comprises:

an event component comprising an event ID component, an event name component, an event description component, an event location component, an event website component, said event category component, an event start date component, an event end date component, a betting start date component, a betting end date component, an event management component.

6. The system according to claim 5 wherein said event object further comprises:

d. an event ID object to maintain event ID information of said event ID component;

a. an event name object configured to maintain event name information from said event name component;

b. an event description object configured to maintain event description information from said event description component;

c. an event location object configured to maintain location information from said event location component.

7. The system according to claim 5 wherein said event object further comprises:

a. an event asset object configured to maintain website information of said event website component;

b. an event time object configured to maintain time information of said event time component, said event time object comprising an event start date object, an event end date object, a bet start date object, a bet end date object;

c. an event management object configured to maintain event information of said event management component.

8. The system according to claim 2 wherein said first pool page further comprises:

a select event component, a get pools component, a pool title component, a bet type component, a pool type component, a commission component, a pick count component, a maximum wager component, a wager minimum component, a wager maximum component, a flat payout component, a pool status component, a gross total component, a paid-out component, a previous pool component, an update component, an edit pool component.

9. The system according to claim 8 wherein said first pool object further comprises:

a. a select event object configured to maintain event information of said select event component;

b. a get-pools object configured to maintain pool information of said get-pool component;

c. a pool title object configured to maintain pool information of said pool title component;

d. a bet type object configured to maintain bet type information of said bet type component.

10. The system according to claim 9 wherein said first pool object further comprises:

a. a pool type object configured to maintain pool type information of said pool type component;

b. a commission object configured to maintain commission information of said commission component;

c. a pick counts object configured to maintain pick information of said pick count component;

d. a maximum wagers object configured to maintain maximum wager information of said maximum wagers component.

11. The system according to claim 10 wherein said first pool object further comprises:

a. a wager minimum object, configured to maintain minimum wager information of said wager minimum component;

b. a wager maximum object, configured to maintain maximum wager information of said wager maximum component;

c. a flat payout object configured to maintain payout information of said flat payout component;

d. a gross total object configured to maintain total wager information of said gross total component.

12. The system according to claim 11 wherein said first pool object further comprises:

a. a paid out object configured to maintain paid information of said paid out component;

b. a previous pool object configured to maintain the prior pool information of said previous pool component;

c. an update object configured to update pool information of said update component;

d. and edit pool object configured to edit prior pool information in said edit pool component.

13. A method for coordinating a wagering event, said method comprising:

a. creating an event in a server database utilizing an administration application hosted on a virtual web server;

b. displaying said event in a casino application located at a casino location;

c. creating a first set of event players in said administration application from a player page;

recording a first set of event players for said event into said server database;

d. creating a first pool in said administration application from a first pool page;

recording said first pool in a first pool object in said server database;

e. wagering on said event by sending an open for wagering signal to said casino application from said server database;

receiving a first set of wagers from said casino application to said administration application;

recording said first set of wagers into said server database;

sending a closed for wagering signal from said administration application to said casino application;

f. hosting a casino event at said casino location and sending from said server database to said casino application an event start signal;

setting a pending status for said first pool and sending from said administration application to said casino application said pending status;

posting results of said casino event from said casino application into said administration application;

recording said results of said casino event into said server database;

sending from said server database to said casino application an event end signal;

setting a closed status for said first pool and sending from said administration application to said casino application said closed status;

g. posting an event results list by sending said event results list from said server database to said casino application;

h. updating said first set of wagers to a win status, a loss status and recording said win status, said loss status, in said server database;

i. sending said win status, said loss status, from said server database to said casino application.

14. The method according to claim 13 wherein said creating an event further comprises:

creating an event category in said administration application by accessing an event category page, entering an event category name, and recording said event category name in an event category object located in said server database.

15. The method according to claim 14 wherein said creating an event further comprises:

initiating an event page in said administration application;

entering an event name in said event page;

recording said event name into an event name object located in said server database.

16. The method according to claim 15 wherein said creating an event further comprises:

entering an event description in said event page;

recording said event description into an event description object located in said server database.

17. The method according to claim 15 wherein said creating an event further comprises:

entering an event location in said event page;

recording said event location into an event location object located in said server database.

18. The method according to claim 15 wherein said creating an event further comprises:

entering an event website into said event page;

recording said event website into an event website object located in said server database.

19. The method according to claim 15 wherein said creating an event further comprises:

choosing an event category from said server database holding said event category object.

20. The method according to claim 15 wherein said creating an event further comprises:

entering an event start/end date and time into said event page;

recording said event start/end date and time into an event start/end date and time objects in said server database.

21. The method according to claim 15 wherein said creating an event further comprises:

entering a bet start/end date and time into said event page;

recording said bet start/end date and time into a bet start/end date and time object located in said server database.

22. The method according to claim 14 wherein said recording a first set of event players further comprises:

receiving a casino list of said first set of event players from said casino application;

entering said first set of event players into an event player page initialized from said administration application;

recording said first set of event players into an event players object in said server database.

23. The method according to claim 14 wherein said creating a first pool further comprises:

loading an event from said server database;

loading an event from said casino application;

recording into said server database a pool title, a bet type, a pool type, a commission, a pick count, a maximum number of wagers, a wagering minimum, a wagering maximum, a flat payout.

24. A system for coordinating a wagering event, said system comprising:

a. means for creating an event in a server database hosted on a virtual web server;

b. means for displaying said event in a casino application located at a casino location;

c. means for recording a first set of event players for said event into said server database;

d. means for recording a first pool in a first pool object in said server database;

e. means for wagering on said event by utilizing means for sending an open for wagering signal to said casino application from said server database;

receiving a first set of wagers from said casino application and utilizing means for recording said first set of wagers into said server database;

means for sending a closed for wagering signal to said casino application;

f. means for hosting a casino event at said casino location and means for sending from said server database to said casino application an event start signal;

means for setting a pending status for said first pool and means for sending to said casino application said pending status;

means for recording results of said casino event into said server database;

means for sending from said server database to said casino application an event end signal;

means for setting a closed status for said first pool and means for sending from said server database to said casino application said closed status;

g. means for posting an event results list by utilizing means for sending said event results list from said server database to said casino application;

h. means for updating said first set of wagers to a win status, a loss status and recording said win status, said loss status, in said server database;

i. means for sending said win status, said loss status, from said server database to said casino application.

25. The system according to claim 24 wherein said means for creating an event further comprises:

means for creating an event category by utilizing means for accessing an event category page, entering an event category name, and recording said event category name in an event category object located in said server database.

26. The system according to claim 25 wherein said means for creating an event further comprises:

means for initiating an event page;

means for entering an event name in said event page;

means for recording said event name into an event name object located in said server database.

27. The system according to claim 26 wherein said means for creating an event further comprises:

means for entering an event description in said event page;

means for recording said event description into an event description object located in said server database.

28. The system according to claim 26 wherein said means for creating an event further comprises:

means for entering an event location in said event page;

means for recording said event location into an event location object located in said server database.

29. The system according to claim 26 wherein said means for creating an event further comprises:

means for entering an event website into said event page;

means for recording said event website into an event website object located in said server database.

30. The system according to claim 26 wherein said means for creating an event further comprises:

means for choosing an event category from said server database holding said event category object.

31. The system according to claim 26 wherein said means for creating an event further comprises:

means for entering an event start/end date and time into said event page;

means for recording said event start/end date and time into an event start/end date and time objects in said server database.

32. The system according to claim 26 wherein said creating an event further comprises:

means for entering a bet start/end date and time into said event page;

means for recording said bet start/end date and time into a bet start/end date and time object located in said server database.

33. The system according to claim 24 wherein said means for recording a first set of event players further comprises:

means for receiving a casino list of said first set of event players from said casino application;

means for entering said first set of event players into an event player page;

means for recording said first set of event players into an event players object in said server database.

34. The system according to claim 24 wherein said means for creating a first pool further comprises:

means for loading an event from said server database;

means for loading an event from said casino application;

means for recording into said server database a pool title, a bet type, a pool type, a commission, a pick count, a maximum number of wagers, a wagering minimum, a wagering maximum, a flat payout.