Application monetization platform

• US 9,076,290 B2
• Filed: 08/09/2012
• Issued: 07/07/2015
• Est. Priority Date: 08/09/2011
• Status: Active Grant

• Current Assignee: Collisse Group Limited (Rubicon Media, Inc.)
• Original Assignee: Collisse Group Limited (Rubicon Media, Inc.)
• Inventors: Griffin, Christopher E.
• Primary Examiner(s): MYHR, JUSTIN L
• Application Number:
  US13/571,281
• Publication Number:
  US 20130040729A1
• Time in Patent Office: 1,062 Days
• Field of Search: 463 9- 13, 463 16- 22, 463/25, 463/29, 463 40- 42
• US Class Current: 1/1
• CPC Class Codes: A63F 13/50 Controlling the output signals based on the game progress
• CPC Class Codes: A63F 2300/535 for monitoring, e.g. of user parameters, terminal parameters, application parameters, network parameters
• CPC Class Codes: G06Q 30/00 Commerce
• CPC Class Codes: G06Q 30/0241 Advertisements
• CPC Class Codes: G07F 17/3204 Player-machine interfaces
• CPC Class Codes: G07F 17/3209 Input means, e.g. buttons, touch screen
• CPC Class Codes: G07F 17/3213 Details of moving display elements, e.g. spinning reels, tumbling members
• CPC Class Codes: G07F 17/3223 Architectural aspects of a gaming system, e.g. internal configuration, master/slave, wireless communication
• 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/3227 Configuring a gaming machine, e.g. downloading personal settings, selecting working parameters
• CPC Class Codes: G07F 17/3237 about the players, e.g. profiling, responsible gaming, strategy/behavior of players, location of players
• CPC Class Codes: G07F 17/3239 Tracking of individual players
• CPC Class Codes: G07F 17/3241 Security aspects of a gaming system, e.g. detecting cheating, device integrity, surveillance computer security G06F21/00
• CPC Class Codes: G07F 17/3244 Payment aspects of a gaming system, e.g. payment schemes, setting payout ratio, bonus or consolation prizes
• CPC Class Codes: G07F 17/329 Regular and instant lottery, e.g. electronic scratch cards
• CPC Class Codes: G07F 17/34 depending on the stopping of moving members in a mechanical slot machine, e.g. "fruit" machines
• CPC Class Codes: H04L 2463/102 applying security measure for e-commerce
• CPC Class Codes: H04L 9/321 involving a third party or a trusted authority

Abstract

Various example embodiments are directed to a computer-implemented gaming management system for facilitating applications that support user wagering. The gaming management system may comprise a computer system in communication with a developer computer device. The computer system may be programmed to receive from the developer computer device configuration data for a contingent event to be associated with a user application; determine whether the configuration data meets at least one predetermined standard; and provided that the configuration data meets the at least one predetermined standard, provide the developer computer device with an application program interface (API) credential to be utilized by the user application, wherein the API credential is to give the user application access to an API for resolving the contingent event.

Claims

1. A computer-implemented gaming management system for facilitating applications that support user wagering, the system comprising:

a computer system in communication with a developer computer device, the computer system comprising at least one processor and operatively associated memory, wherein the computer system is programmed to;

receive, from the developer computer device, configuration data for a contingent event type to be associated with a user application, wherein the contingent event type indicates a plurality of potential outcomes and wherein each of the plurality of potential outcomes is associated with a probability;

determine whether the configuration data meets at least one predetermined standard;

provided that the configuration data meets the at least one predetermined standard, provide the developer computer device with an application program interface (API) credential to be utilized by the user application, wherein the API credential is to give the user application access to an API for resolving at least one contingent event;

receive the API credential from the user application executing on a user device;

receive from the user application a contingent event request, wherein the contingent event request comprises an indication of a contingent event of the contingent event type and a wager on the contingent event;

select an outcome for the contingent event from the plurality of potential outcomes considering at least one of the probabilities associated with the plurality of potential outcomes;

calculate a result amount for the wager considering the selected outcome; and

initiate a financial transfer for an account associated with a user of the user application to resolve the wager.

2. The system of claim 1, wherein determining whether the configuration data meets at least one predetermined standard comprises comparing the configuration data to a set of allowable contingent event configurations.

3. The system of claim 2, wherein the set of allowable contingent event configurations is based on at least one regulatory requirement associated with a gambling license held by an entity implementing the gaming management system and not held by an entity implementing the developer computer device.

4. The system of claim 2, wherein determining whether the configuration data meets at least one predetermined standard comprises:

calculating at least one configuration event parameter based on the configuration data; and

comparing the at least one configuration parameter to at least one of a regulatory requirement and a configuration parameter of a contingent event form previously cleared under at least one regulatory requirement.

5. The system of claim 1, wherein the computer system is further programmed to:

calculate an allowable event configuration;

provide the allowable event configuration to the developer computer device; and

receive from the developer computer device an update to the configuration data.

6. The system of claim 1, wherein the computer system is further programmed to:

prompt the developer computer device for an indication of whether house funds will be provided by an entity implementing the developer computer device; and

set a compensation level for the developer based on whether the house funds will be provided by the developer.

7. The system of claim 1, wherein the computer system is further programmed to receive from the developer computer device a request to transfer money from a payment mechanism of the developer computer device to an account associated with the computer system.

8. The system of claim 1, wherein the computer system is further programmed to receive the user application comprising the API credential.

9. The system of claim 8, wherein the computer system is further programmed to perform a plurality of test wagers utilizing the application.

10. The system of claim 1, wherein the computer system is further programmed to publish an indication of an application comprising the API credential.

11. The system of claim 1, wherein the configuration data for the contingent event further comprises an indication that the contingent event supports real money wagers.

12. The system of claim 1, wherein the configuration data for the contingent event comprises a maximum allowable wager, and wherein the computer system is further programmed to:

determine an estimated profit per unit of wagers; and

provide the estimated profit to the developer computer device.

13. The system of claim 1, wherein the indication of the contingent event associated with the application comprises a contingent event type of the contingent event, and wherein the computer system is further programmed to provide the developer computer device with a template for receiving at least a portion of the configuration data for the contingent event.

14. The system of claim 13, wherein the contingent event type is a slot machine event type and the template for receiving at least a portion of the configuration data comprises:

a field for receiving a number of reels;

a field for receiving at least one symbol to appear on the reels; and

a field for receiving at least one pay line of the reels.

15. The system of claim 13, wherein the contingent event type is a keno event type and the template for receiving at least a portion of the configuration data comprises a field for receiving data describing each potential outcome for at least a first ticket type.

16. The system of claim 13, wherein the contingent event type is a roulette event type and the template for receiving at least a portion of the configuration data comprises a field for receiving a number of slots.

17. The system of claim 13, wherein the template for receiving at least a portion of the configuration data comprises:

a field for receiving an outcome probability for a first outcome;

a field for receiving a payout factor for the first outcome;

a field for receiving an outcome probability for a second outcome; and

a field for receiving a payout factor for the second outcome.

18. The system of claim 13, wherein the configuration data from the contingent event comprises an indication of a house edge for the contingent event.

19. The system of claim 1, wherein the computer system is in communication with the user application executed at least in part by a user device, and wherein the computer system is further programmed to:

receive from the user application an application authentication indicating that at least one contingent event associated with the user application has been approved by the gaming management system;

provide the user device with an authentication interface for receiving information describing the user of the user device;

receive, through the authentication interface and from the user, information describing the user; and

determine whether the user is eligible to place a wager based on the information describing the user, and wherein initiating the financial transfer for the account associated with the user comprises applying the result amount to the account.

20. The system of claim 19, wherein determining whether the user is eligible to place a wager comprises comparing the information describing the user to at least one regulatory requirement associated with a gambling license held by an entity implementing the gaming management system.

21. The system of claim 19, wherein the computer system is further programmed to send to the user device an indication of the outcome and the result amount.

22. The system of claim 19, wherein the information describing the user comprises a date of birth for the user and a geographic location of the user.

23. The system of claim 19, wherein applying the result amount to the account associated with the user comprises sending at least one instruction to a financial institution holding a financial account associated with the user.

24. The system of claim 19, wherein the contingent event request further comprises at least one parameter for determining the probability associated with at least one of the plurality of potential outcomes.

25. The system of claim 19, wherein the computer system is further programmed to prompt the user device for an indication of whether the wager is a money wager.

26. The system of claim 19, wherein result amount is in a virtual currency, and wherein the computer system is further programmed to:

determine that the user has won the wager; and

prompt the user device to provide the contingent event with the wager in a real currency.

27. The system of claim 19, wherein the information describing the user comprises log-in information associated with the account, and wherein determining whether the user is eligible to place the wager based on the information describing the user comprises accessing additional information associated with the account.

28. The system of claim 19, wherein the computer system is further programmed to provide the user device with a balance of the user associated with the account.

29. The system of claim 19, wherein the computer system is further programmed to extrapolate a geographic location of the user from the information describing the user.

30. The system of claim 19, wherein the computer system is further programmed to:

upon determining that the user is eligible to place a wager, provide the user application with an access token.

31. The system of claim 30, wherein the contingent event request comprises the access token.

32. A computer-implemented method for facilitating applications that support user wagering, the method comprising:

receiving, by a computer system and from a developer computer device, configuration data for a contingent event type to be associated with a user application, wherein the computer system comprises at least one processor and operatively associated memory, wherein the contingent event type indicates a plurality of potential outcomes, and wherein each of the plurality of potential outcomes is associated with a probability;

determining, by the computer system, whether the configuration data meets at least one predetermined standard;

provided that the configuration data meets the at least one predetermined standard, providing the developer computer device with an application program interface (API) credential to be utilized by the user application, wherein the API credential is to give the user application access to an API for resolving at least one contingent event;

receiving the API credential from the user application executing on a user device;

receiving from the user application a contingent event request, wherein the contingent event request comprises an indication of the contingent event and a wager on the contingent event;

selecting an outcome for the contingent event from the plurality of potential outcomes considering at least one of the probabilities associated with the plurality of potential outcomes;

selecting a result amount for the wager considering the selected outcome; and

initiating a financial transfer for an account associated with a user of the user application to resolve the wager.

33. The method of claim 32, wherein determining whether the configuration data meets at least one predetermined standard comprises comparing the configuration data to set of allowable contingent event configurations, and wherein the set of allowable contingent event configurations is based on at least one regulatory requirement associated with a gambling license held by an entity implementing the computer system and not held by an entity implementing the developer computer device.

34. The method of claim 32, wherein the computer system is in communication with a user application executed at least in part by a user device, the method comprising:

receiving, by the computer system and from the user application, an application authentication indicating that at least one contingent event associated with the user application has been approved by the computer system;

providing, by the computer system and to the user device, an authentication interface for receiving information describing the user of the user device;

receiving, by the computer system, through the authentication interface and from the user, information describing the user; and

determining, by the computer system, whether the user is eligible to place a wager based on the information describing the user, and wherein initiating the financial transfer for the account associated with the user comprises applying the result amount to the account.