US 12,488,653 B2
Multi-form game platform for online and social gaming
Ashish Gupta, Uttar Pradesh (IN); Mayank Agarwal, Uttar Pradesh (IN); Milind Shrivastava, Uttar Pradesh (IN); Nitin Varshney, Uttar Pradesh (IN); Pardeep Rathee, Haryana (IN); Sandeep Agarwal, Haryana (IN); and Vinay Khandelwal, Uttar Pradesh (IN)
Assigned to Aristocrat Technologies, Inc., Las Vegas, NV (US)
Filed by Aristocrat Technologies, Inc., Las Vegas, NV (US)
Filed on Jan. 11, 2023, as Appl. No. 18/153,262.
Prior Publication US 2024/0233479 A1, Jul. 11, 2024
Int. Cl. G07F 17/32 (2006.01); A63F 3/06 (2006.01)
CPC G07F 17/3223 (2013.01) [A63F 3/0645 (2013.01)] 20 Claims
OG exemplary drawing
 
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.