Multi-form game platform for online and social gaming

Patent metadata

Field	Value
Publication number	US-12488653-B2
Application number	US-202318153262-A
Country	US
Kind code	B2
Filing date	Jan 11, 2023
Priority date	Jan 11, 2023
Publication date	Dec 2, 2025
Grant date	Dec 2, 2025

Abstract

The innovations disclosed herein concern improvements for a hosted gaming environment to provide improved flexibility, scalability, and game deployment/maintenance. In particular, the multi-form gaming platforms disclosed herein may host so-called “iGaming” sessions (i.e., online gaming with real money wagering), mobile Class-II gaming sessions (e.g., Bingo games) and/or mobile Class-III gaming sessions (e.g., traditional casino-style games), as well as “Social” or “Demo” gaming sessions (i.e., online gaming with non-real money wagering). The innovations disclosed herein have the following technical benefits: (1) the ability for systems to utilize Class-II and Class-III games in real money gaming (“RMG”) and Social gaming; (2) the creation of “Social” versions of Bingo games; (3) reducing the overall number of game builds needed for each separate platform; (4) reusing games in different markets; (5) reducing branches in platform codebases; (6) reducing deployment effort and optimizing support teams; and (7) easing maintenance and upkeep for games across platforms.

First claim

What is claimed is:

1 . A system, comprising:
one or more processors; memory; and control logic, implemented using the one or more processors and the memory, and configured to perform operations, comprising:
executing a hosted gaming platform, wherein the hosted gaming platform comprises at least a remote gaming server (RGS) instance, a real money gaming (RMG) infrastructure, and at least one interface to a non-RMG infrastructure, wherein the non-RMG infrastructure is hosted by a server external to the RMG infrastructure;
receiving, at the RGS instance, a first request from a current round of a first gameplay session executing at a frontend gaming client, wherein the first request comprises at least session metadata and an identifier for a first user, and wherein the session metadata indicates whether the first gameplay session comprises an RMG session or a non-RMG session;
in response to the session metadata indicating that the first gameplay session comprises an RMG session:
routing the first request for execution using at least the RMG infrastructure, wherein execution of the first request produces one or more results for the current round; and
returning the one or more produced results for the current round to the frontend gaming client; and

in response to the session metadata indicating that the first gameplay session comprises a non-RMG session:
routing the first request, via the at least one interface, to the non-RMG infrastructure hosted by the server external to the RMG infrastructure;
receiving one or more results for the current round produced by the non-RMG infrastructure; and
returning the one or more received results for the current round to the frontend gaming client.

2 . The system of claim 1 , wherein the RGS is configured to manage one or more user wallets.

3 . The system of claim 2 , wherein the one or more wallets comprise: at least one RMG wallet; and at least one non-RMG wallet.

4 . The system of claim 1 , wherein the RGS is configured to receive information from: one or more external Class-II player account management (PAM) systems; and one or more external Class-III PAM systems.

5 . The system of claim 1 , wherein the first gameplay session comprises at least one of: a Class-II gameplay session; or a Class-III gameplay session.

6 . The system of claim 5 , wherein, for Class-II gameplay sessions, producing the one or more results further comprises: utilizing a bingo server.

7 . The system of claim 5 , wherein, for Class-III gameplay sessions, producing the one or more results further comprises: utilizing an outcome resolver and a random number generator (RNG).

8 . The system of claim 1 , wherein the non-RMG infrastructure comprises: an infrastructure configured to produce results for Social gameplay sessions; or an infrastructure configured to produce results for Demo gameplay sessions.

9 . One or more computer-readable media storing computer-executable instructions, which, when executed by a computer, cause the computer to perform the following operations:
execute a hosted gaming platform, wherein the hosted gaming platform comprises at least a remote gaming server (RGS) instance, a real money gaming (RMG) infrastructure, and at least one interface to a non-RMG infrastructure, wherein the non-RMG infrastructure is hosted by a server external to the RMG infrastructure; receive, at the RGS instance, a first request from a current round of a first gameplay session executing at a frontend gaming client, wherein the first request comprises at least session metadata and an identifier for a first user, and wherein the session metadata indicates whether the first gameplay session comprises an RMG session or a non-RMG session; in response to the session metadata indicating that the first gameplay session comprises an RMG session:
route the first request for execution, using at least the RMG infrastructure, wherein execution of the first request produces one or more results for the current round; and
return the one or more produced results for the current round to the frontend gaming client; and
in response to the session metadata indicating that the first gameplay session comprises a non-RMG session: route the first request, via the at least one interface, to the non-RMG infrastructure hosted by the server external to the RMG infrastructure; receive one or more results for the current round produced by the non-RMG infrastructure; and return the one or more received results for the current round to the frontend gaming client.

10 . The one or more computer-readable media of claim 9 , wherein the RGS is configured to manage one or more user wallets.

11 . The one or more computer-readable media of claim 9 , wherein the RGS is configured to receive information from: one or more external Class-II player account management (PAM) systems; and one or more external Class-III PAM systems.

12 . The one or more computer-readable media of claim 9 , wherein the first gameplay session comprises at least one of: a Class-II gameplay session; or a Class-III gameplay session.

13 . The one or more computer-readable media of claim 12 , wherein for Class-II gameplay sessions, producing the one or more results further comprises: utilizing a bingo server.

14 . The one or more computer-readable media of claim 12 , wherein, for Class-III gameplay sessions, producing the one or more results further comprises: utilizing an outcome resolver and a random number generator (RNG).

15 . The one or more computer-readable media of claim 9 , wherein the non-RMG infrastructure comprises: an infrastructure configured to produce results for Social gameplay sessions; or an infrastructure configured to produce results for Demo gameplay sessions.

16 . A computer-implemented method, comprising:
executing a hosted gaming platform, wherein the hosted gaming platform comprises at least a remote gaming server (RGS) instance, a real money gaming (RMG) infrastructure, and at least one interface to a non-RMG infrastructure, wherein the non-RMG infrastructure is hosted by a server external to the RMG infrastructure; receiving, at the RGS instance, a first request from a current round of a first gameplay session executing at a frontend gaming client, wherein the first request comprises at least session metadata and an identifier for a first user, and wherein the session metadata indicates whether the first gameplay session comprises an RMG session or a non-RMG session; in response to the session metadata indicating that the first gameplay session comprises an RMG session:
routing the first request for execution, using at least the RMG infrastructure, wherein the execution of the first request produces one or more results for the current round; and
returning the one or more produced results for the current round to the frontend gaming client; and
in response to the session metadata indicating that the first gameplay session comprises a non-RMG session:
routing the first request, via the at least one interface, to the non-RMG infrastructure hosted by the server external to the RMG infrastructure;
receiving one or more results for the current round produced by the non-RMG infrastructure; and
returning the one or more received results for the current round to the frontend gaming client.

17 . The computer-implemented method of claim 16 , wherein the RGS is configured to receive information from: one or more external Class-II player account management (PAM) systems; and one or more external Class-III PAM systems.

18 . The comput

Assignees

• Aristocrat Technologies Inc

Inventors

• Gupta Ashish
• Agarwal Mayank
• Shrivastava Milind
• Varshney Nitin
• Rathee Pardeep
• Agarwal Sandeep
• Khandelwal Vinay

Classifications

• A63F3/0645

  Electric lottos or bingo games · CPC title

• G07F17/3225

  Data transfer within a gaming system, e.g. data sent between gaming machines and users · CPC title

• G07F17/3244

  Payment aspects of a gaming system, e.g. payment schemes, setting payout ratio, bonus or consolation prizes · CPC title

• G07F17/3223 Primary

  Architectural aspects of a gaming system, e.g. internal configuration, leader-follower, wireless communication · CPC title