IP Library › Granted Patent US 12,367,736
Granted Patent B2
US 12,367,736 · App. 18/680,926 · Granted Jul 22, 2025

Rendering pipeline for electronic games

Inventors: Jody Brown (Austin, TX); Joseph Bibbo (Austin, TX)
Assignee: Aristocrat Technologies, Inc.
G07F17/3211
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,367,736
App. No.
18/680,926
Granted
Jul 22, 2025
Kind
B2
Abstract

An electronic gaming device provides a rendering pipeline for an electronic game. The rendering pipeline includes a client component and a native component of the rendering pipeline, where the client component is configured to: initiate a rendering operations pipe between the client component and the native component; convert display commands from a source language of the electronic game into rendering operations of an intermediate rendering language; and transmit the rendering operations through the rendering operations pipe to the native component. The native component is configured to: receive the rendering operations via the rendering operations pipe; translate the rendering operations from the intermediate rendering language into rendering operations of the native component; and perform the rendering operations of the native component on the display device.

Claims (31)

1. An electronic gaming system configured to provide a rendering pipeline for an electronic game, the electronic gaming system comprising:

at least one memory for storing the electronic game and a client component of the rendering pipeline; and

at least one processor configured to execute the client component, wherein the client component, when executed on the at least one processor, is configured to:

initiate a rendering operations pipeline between the client component and a native component;

convert display commands from a source language of the electronic game into rendering operations of an intermediate rendering language; and

transmit the rendering operations through the rendering operations pipeline to the native component, wherein the native component is configured to translate the rendering operations from the intermediate rendering language into rendering operations of the native component that, when performed by the native component, control video output on a display device.

2. The electronic gaming system of claim 1 , wherein the at least one processor is further configured to execute the native component that translate the rendering operations from the intermediate rendering language into the rendering operations of the native component.

3. The electronic gaming system of claim 1 , wherein the client component includes a virtual machine that is configured to perform just-in-time compilation and execution of the electronic game.

4. The electronic gaming system of claim 1 , wherein the source language of the electronic game is one of JavaScript and Typescript, wherein the client component includes a java virtual machine that executes the electronic game.

5. The electronic gaming system of claim 4 , wherein the client component is configured to create a WebView object and execute source code of the electronic game via offscreen WebKit rendering in the WebView object.

6. The electronic gaming system of claim 1 , wherein the client component is configured to transmit asset loading operations to the native component, wherein the native component is configured to load assets identified by the asset loading operations.

7. The electronic gaming system of claim 1 , wherein at least some of the rendering operations of the intermediate rendering language include an operation type, a node identifier, and model data.

8. The electronic gaming system of claim 1 , wherein a heartbeat is established between the native component and the client component, wherein the client component uses the heartbeat as timing for when to generate and transmit rendering operations through the rendering operations pipe.

9. A method for providing a rendering pipeline for an electronic game using an electronic gaming system, the electronic gaming system including at least one memory for storing the electronic game and a client component of the rendering pipeline, the electronic gaming device also including at least one processor configured to execute the client component, the method comprising:

initiating a rendering operations pipeline between the client component and a native component;

converting display commands from a source language of the electronic game into rendering operations of an intermediate rendering language; and

transmitting the rendering operations through the rendering operations pipeline to the native component, wherein the native component is configured to translate the rendering operations from the intermediate rendering language into rendering operations of the native component that, when performed by the native component, control video output on a display device.

10. The method of claim 9 , wherein the client component includes a virtual machine that is configured to perform just-in-time compilation and execution of the electronic game.

11. The method of claim 9 , wherein the source language of the electronic game is one of JavaScript and Typescript, wherein the client component includes a java virtual machine that executes the electronic game.

12. The method of claim 11 , further comprising creating a Web View object and execute source code of the electronic game via offscreen WebKit rendering in the WebView object.

13. The method of claim 9 , further comprising transmitting asset loading operations to the native component, wherein the native component is configured to load assets identified by the asset loading operations.

14. The method of claim 9 , wherein at least some of the rendering operations of the intermediate rendering language include an operation type, a node identifier, and model data.

15. The method of claim 9 , wherein a heartbeat is established between the native component and the client component, wherein the client component uses the heartbeat as timing for when to generate and transmit rendering operations through the rendering operations pipe.

16. A non-transitory computer-readable medium storing instructions that, when executed by at least one processor of an electronic gaming system, cause the at least one processor to:

initiate, at a client component, a rendering operations pipeline between the client component and a native component;

convert display commands from a source language of the electronic game into rendering operations of an intermediate rendering language; and

transmit the rendering operations through the rendering operations pipeline to the native component, wherein the native component is configured to translate the rendering operations from the intermediate rendering language into rendering operations of the native component that, when performed by the native component, control video output on a display device.

17. The non-transitory computer-readable medium of claim 16 , wherein the client component includes a virtual machine that is configured to perform just-in-time compilation and execution of an electronic game.

18. The non-transitory computer-readable medium of claim 16 , wherein the client component is configured to transmit asset loading operations to the native component, wherein the native component is configured to load assets identified by the asset loading operations.

19. The non-transitory computer-readable medium of claim 16 , wherein at least some of the rendering operations of the intermediate language include an operation type, a node identifier, and model data.

20. The non-transitory computer-readable medium of claim 16 , wherein a heartbeat is established between the native component and the client component, wherein the client component uses the heartbeat as timing for when to transmit the rendering operations to the native component through the rendering pipeline.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jun 24, 2024
From: BROWN, JODY; BIBBO, JOSEPH
To: ARISTOCRAT TECHNOLOGIES, INC.
Reel/Frame 067817/0558 →
Continuity (5)
Continuation 18316171 · May 11, 2023
Continuation 17125483 · Dec 17, 2020
Provisional Application 63090661 · Oct 12, 2020
Provisional Application 62959407 · Jan 10, 2020
Related Publication 20240321037A1 · Sep 26, 2024
References Cited (65)
US 7070501B2 · Cormack · 2006 [cited by applicant]
US D624927S · Allen · 2010 [cited by applicant]
US D648347S · Chaudhri · 2011 [cited by applicant]
US 8360851B2 · Aoki · 2013 [cited by applicant]
US 8911294B2 · Antkowiak · 2014 [cited by applicant]
US 9424720B2 · Suda · 2016 [cited by applicant]
US 9928691B2 · Olive · 2018 [cited by applicant]
US D824932S · Joensson · 2018 [cited by applicant]
US 10074206B1 · Ingegneri · 2018 [cited by applicant]
US D834596S · Bae · 2018 [cited by applicant]
US 20030216165A1 · Singer · 2003 [cited by applicant]
US 20040137982A1 · Cuddy · 2004 [cited by applicant]
US 20060189369A1 · Taylor · 2006 [cited by applicant]
US 20070060248A1 · Rodgers · 2007 [cited by applicant]
US 20070129135A1 · Marks · 2007 [cited by applicant]
US 20090054129A1 · Yoshimura · 2009 [cited by applicant]
US 20090239634A1 · Nguyen · 2009 [cited by applicant]
US 20100075737A1 · Bluemel · 2010 [cited by applicant]
US 20100210343A1 · Englman · 2010 [cited by applicant]
US 20100234092A1 · Gomez · 2010 [cited by applicant]
US 20100281107A1 · Fallows · 2010 [cited by applicant]
US 20110157196A1 · Nave · 2011 [cited by examiner]
US 20120178517A1 · Montenegro · 2012 [cited by applicant]
US 20120258786A1 · Sylla · 2012 [cited by examiner]
US 20130331168A1 · Street · 2013 [cited by applicant]
US 20140080564A1 · Acres · 2014 [cited by applicant]
US 20140274292A1 · Suda · 2014 [cited by applicant]
US 20140323198A1 · Tuck · 2014 [cited by applicant]
US 20150310699A1 · Meyer · 2015 [cited by applicant]
US 20160042597A1 · Olive · 2016 [cited by applicant]
US 20160253873A1 · Olive · 2016 [cited by applicant]
US 20170032609A1 · Inamura · 2017 [cited by applicant]
US 20170111477A1 · Davis · 2017 [cited by examiner]
US 20170148274A1 · Olive · 2017 [cited by applicant]
US 20170154498A1 · Olive · 2017 [cited by applicant]
US 20180001216A1 · Bruzzo · 2018 [cited by applicant]
US 20180075708A1 · San · 2018 [cited by applicant]
US 20180268655A1 · Olive · 2018 [cited by applicant]
US 20200111312A1 · Olive · 2020 [cited by applicant]
US 20200312081A1 · Perrow · 2020 [cited by examiner]
US 20200368616A1 · Delamont · 2020 [cited by examiner]
US 20210362050A1 · Gault · 2021 [cited by examiner]
AU 2013202658A1 · 2014 [cited by applicant]
AU 2013251288A1 · 2014 [cited by applicant]
AU 2014202042A1 · 2014 [cited by applicant]
EP 0984408A2 · 2000 [cited by applicant]
Office Action dated Sep. 2, 2020 for U.S. Appl. No. 16/383,435 (pp. 1-7). [cited by applicant]
Australian Examination Report for Application No. 2018278882, dated Dec. 9, 2019, 2 pages. [cited by applicant]
Australian Examination Report for AU2016100230, dated May 11, 2016, 5 pages. [cited by applicant]
Australian Examination Report for AU2015210489, dated Jun. 14, 2016, 5 pages. [cited by applicant]
Australian Examination Report for AU2016202727, dated Jul. 4, 2016, 5 pages. [cited by applicant]
Australian Examination Report for AU2017101629, dated Jan. 16, 2018, 3 pages. [cited by applicant]
Australian Examination Report for AU2017204560, dated Feb. 1, 2018, 3 pages. [cited by applicant]
Australian Examination Report for Application No. 2018241080, dated Sep. 24, 2019. [cited by applicant]
U.S. Appl. No. 16/455,166, filed Jun. 27, 2019, System and Method for Providing a Feature Game. [cited by applicant]
Australian Examination Report for Application No. 2019200719, dated Apr. 8, 2020, 3 pages. [cited by applicant]
Australian Examination Report for AU2017101097, dated Dec. 7, 2017. (3 pages). [cited by applicant]
Office Action dated Jun. 4, 2020 for U.S. Appl. No. 29/622,662 (pp. 1-8). [cited by applicant]
Office Action dated Jun. 25, 2020 for U.S. Appl. No. 16/537,223 (pp. 1-11). [cited by applicant]
Notice of Allowance dated Aug. 31, 2020 for U.S. Appl. No. 29/622,662 (pp. 1-7). [cited by applicant]
Notice of Allowance dated Dec. 1, 2020 for U.S. Appl. No. 16/383,435 (pp. 1-7). [cited by applicant]
Corrected Notice of Allowabality dated Jan. 26, 2021 for U.S. Appl. No. 16/383,435 (pp. 1-2). [cited by applicant]
Office Action (Notice of Allowance and Fees Due (PTOL-85)) dated Feb. 23, 2023 for U.S. Appl. No. 17/125,483 (pp. 1-8). [cited by applicant]
Office Action (Non-Final Rejection) dated Nov. 21, 2023 for U.S. Appl. No. 18/316,171 (pp. 1-6). [cited by applicant]
Office Action (Notice of Allowance and Fees Due (PTOL-85)) dated Mar. 11, 2024 for U.S. Appl. No. 18/316,171 (pp. 1-7). [cited by applicant]