IP Library Granted Patent US 12,285,693
Granted Patent B2
US 12,285,693 · App. 18/543,293 · Granted Apr 29, 2025

Method of synchronizing online game, and server device

Inventor: Robert Jay Gould (Minato-ku, JP)
Assignee: GREE, INC.
A63F13/77A63F13/35H04L67/02H04L67/1095H04L67/55A63F13/493A63F2300/402A63F2300/407A63F2300/408A63F2300/534A63F2300/5533
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,285,693
App. No.
18/543,293
Granted
Apr 29, 2025
Kind
B2
Abstract

The present disclosure provides a method of synchronizing an online game, and a server device, that do not require centralized information management, reduce the processing burden on each device during online communication, and allow for continuation of processing in an offline environment. A method, according to the present disclosure, of synchronizing an online game that allows for transmission and reception of information related to game processing between a first client terminal and a second client terminal via a server includes: receiving, from the first client terminal connected online, first information related to game processing on the first client terminal; determining whether the first information is information that determines a game status; and storing the first information on the server and transmitting the first information to the second client terminal when the first information is determined to be information that determines the game status.

Claims (56)

1. A method of synchronizing an online game between a first mobile device and a second mobile device via a server, the method comprising:

initiating execution of the online game with each of the first mobile device and second mobile device in an online state;

determining that the first mobile device has entered an offline state;

after determining that the first mobile device has entered the offline state, causing the second mobile device to be set to a rollback state;

subsequently determining that the first mobile device has entered the online state, and receiving, on the server, first information from the first mobile device connected online;

determining whether the first information is valid, wherein determining whether the first information is valid comprises determining whether a loss of synchronization of the online game between the first mobile device and the second mobile device would result from a transmission of the first information to the second mobile device;

transmitting the first information to the second mobile device when it is determined that the first information is valid; and

invalidating the first information and not transmitting the first information to the second mobile device when it is determined that the first information is not valid.

2. The method of claim 1 , wherein determining that the first mobile device has entered the offline state comprises:

transmitting information from the server to the first mobile device; and

determining that there is no response from the first mobile device after transmitting the information to the first mobile device.

3. The method of claim 1 , wherein the method further comprises:

in an online state, and prior to determining that the first mobile device has entered the offline state, completing at least one event with the first mobile device and second mobile device.

4. The method of claim 3 , wherein determining that the first mobile device has entered the offline state comprises:

after completing the at least one event, transmitting information from the server to the first mobile device; and

determining that there is no response from the first mobile device after transmitting the information to the first mobile device.

5. The method of claim 1 , wherein causing the second mobile device to be set to the rollback state comprises:

restricting synchronization, with the server, of a first type of gameplay advancement from the second mobile device; and

permitting synchronization, with the server, of a second type of gameplay advancement from the second mobile device.

6. The method of claim 5 , wherein the second type of gameplay advancement is at least one of: a result of a battle by a game character and progress by the game character in a game space.

7. The method of claim 5 , wherein the first type of gameplay advancement is event advancement.

8. The method of claim 7 , wherein restricting synchronization, with the server, of the first type of gameplay advancement comprises comparing event information to a specific threshold for an event, and rolling back a game state of the second mobile device based on comparison of the event information to the specific threshold.

9. The method of claim 7 , wherein restricting synchronization, with the server, of the first type of gameplay advancement comprises restricting event advancement until after a step of determining whether event advancement would disrupt mutual synchronization between the first mobile device and the second mobile device; and

performing event advancement only when it is determined that event advancement would not disrupt mutual synchronization.

10. The method of claim 1 , wherein initiating execution of the online game with the first mobile device comprises causing the first mobile device to provide at least one gameplay element, comprising providing, to the first mobile device, when the first mobile device is in an online state, information for causing the first mobile device to provide the at least one gameplay element during a condition in which the first mobile device is subsequently operated in an offline state.

11. The method of claim 10 , wherein the first information from the first mobile device connected online comprises information related to at least one interaction received by the first mobile device during a preceding period in which the first mobile device was in the offline state.

12. The method of claim 10 , wherein the at least one gameplay element includes a preset path, wherein a degree of progress of a user character along the preset path is tracked separately from a score of the user character, and wherein a user interaction with the at least one gameplay element comprises advancing the degree of progress of the user character along the preset path.

13. The method of claim 10 , wherein a user interaction with the at least one gameplay element comprises initiating a battle between a user character and at least one opponent character.

14. The method of claim 13 , further comprising providing a change in score based on an outcome of the battle.

15. The method of claim 1 , further comprising:

causing a user interface of the first mobile device to display an interface element corresponding to a degree of progress, said interface element comprising at least one of a progress bar or a percentage.

16. The method of claim 1 , wherein determining whether the first information is valid comprises:

determining whether the first information includes a change in score; and

when the first information includes the change in score, determining that a loss of synchronization would result based on the change in score.

17. A system for synchronizing an online game, comprising a server, a first mobile device, and a second mobile device, the server configured to perform steps of:

initiating execution of the online game with each of the first mobile device and second mobile device in an online state;

determining that the first mobile device has entered an offline state;

after determining that the first mobile device has entered the offline state, causing the second mobile device to be set to a rollback state;

subsequently determining that the first mobile device has entered the online state, and receiving, on the server, first information from the first mobile device connected online;

determining whether the first information is valid, wherein determining whether the first information is valid comprises determining whether a loss of synchronization of the online game between the first mobile device and the second mobile device would result from a transmission of the first information to the second mobile device;

transmitting the first information to the second mobile device when it is determined that the first information is valid; and

invalidating the first information and not transmitting the first information to the second mobile device when it is determined that the first information is not valid.

18. The server of claim 17 , wherein causing the second mobile device to be set to the rollback state comprises:

restricting synchronization, with the server, of a first type of gameplay advancement from the second mobile device; and

permitting synchronization, with the server, of a second type of gameplay advancement from the second mobile device.

19. A non-transitory computer-readable medium comprising computer program code that, when executed by a server communicatively coupled to a first mobile device and a second mobile device, is configured to configure the server to perform steps of:

initiating execution of the online game with each of the first mobile device and second mobile device in an online state;

determining that the first mobile device has entered an offline state;

after determining that the first mobile device has entered the offline state, causing the second mobile device to be set to a rollback state;

subsequently determining that the first mobile device has entered the online state, and receiving, on the server, first information from the first mobile device connected online;

determining whether the first information is valid, wherein determining whether the first information is valid comprises determining whether a loss of synchronization of the online game between the first mobile device and the second mobile device would result from a transmission of the first information to the second mobile device;

transmitting the first information to the second mobile device when it is determined that the first information is valid; and

invalidating the first information and not transmitting the first information to the second mobile device when it is determined that the first information is not valid.

20. The non-transitory computer-readable medium according to claim 19 , wherein causing the second mobile device to be set to the rollback state comprises:

restricting synchronization, with the server, of a first type of gameplay advancement from the second mobile device; and

permitting synchronization, with the server, of a second type of gameplay advancement from the second mobile device.

Assignments (3)
CORRECTIVE ASSIGNMENT TO CORRECT THE RECEIVING PARTY STREET ADDRESS AND ATTORNEY DOCKET NUMBER PREVIOUSLY RECORDED AT REEL: 71308 FRAME: 765. ASSIGNOR(S) HEREBY CONFIRMS THE CHANGE OF NAME. Recorded Jun 10, 2025
From: GREE, INC.
To: GREE HOLDINGS, INC.
Reel/Frame 071611/0252 →
CHANGE OF NAME Recorded May 16, 2025
From: GREE, INC.
To: GREE HOLDINGS, INC.
Reel/Frame 071308/0765 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Dec 18, 2023
From: GOULD, ROBERT JAY
To: GREE, INC.
Reel/Frame 065898/0664 →
Priority Claims (1)
JP 2012-221566 · Oct 3, 2012 · national
Continuity (6)
Continuation 17217169 · Mar 30, 2021
Continuation 16601457 · Oct 14, 2019
Continuation 16116542 · Aug 29, 2018
Continuation 15812000 · Nov 14, 2017
Continuation 14432060
Related Publication 20240115958A1 · Apr 11, 2024
References Cited (90)
US 5166502A · Rendleman et al. · 1992 [cited by applicant]
US 7552148B2 · Liu et al. · 2009 [cited by applicant]
US 7803054B1 · Ogus et al. · 2010 [cited by applicant]
US 8812856B2 · Tamma · 2014 [cited by applicant]
US 9224259B1 · Miller et al. · 2015 [cited by applicant]
US 10080968B2 · Gould · 2018 [cited by applicant]
US 20020129096A1 · Mansour et al. · 2002 [cited by applicant]
US 20020130040A1 · Baldwin et al. · 2002 [cited by applicant]
US 20020194269A1 · Owada et al. · 2002 [cited by applicant]
US 20030007464A1 · Balani · 2003 [cited by applicant]
US 20030171986A1 · Itkis et al. · 2003 [cited by applicant]
US 20030220136A1 · Soltys et al. · 2003 [cited by applicant]
US 20040029638A1 · Hytcheson et al. · 2004 [cited by applicant]
US 20050054445A1 · Gatto et al. · 2005 [cited by applicant]
US 20060004874A1 · Hutcheson et al. · 2006 [cited by applicant]
US 20060035707A1 · Nguyen et al. · 2006 [cited by applicant]
US 20060121989A1 · O'Kelley, II et al. · 2006 [cited by applicant]
US 20060121992A1 · Bortnik · 2006 [cited by examiner]
US 20060247051A1 · Liu · 2006 [cited by applicant]
US 20070021216A1 · Guruparan et al. · 2007 [cited by applicant]
US 20070047586A1 · Tieman · 2007 [cited by examiner]
US 20070054716A1 · Hiruta et al. · 2007 [cited by applicant]
US 20070087791A1 · Feeney et al. · 2007 [cited by applicant]
US 20070173327A1 · Kilgore et al. · 2007 [cited by applicant]
US 20070218980A1 · Pachnis et al. · 2007 [cited by applicant]
US 20080020814A1 · Kernene · 2008 [cited by applicant]
US 20080070703A1 · Campo et al. · 2008 [cited by applicant]
US 20080076573A1 · Loehrer · 2008 [cited by applicant]
US 20080109727A1 · Colle · 2008 [cited by examiner]
US 20080147781A1 · Hopmann et al. · 2008 [cited by applicant]
US 20080205330A1 · Stadler et al. · 2008 [cited by applicant]
US 20080220878A1 · Michaelis · 2008 [cited by applicant]
US 20080270513A1 · Fujiwara et al. · 2008 [cited by applicant]
US 20080320025A1 · Ozzie et al. · 2008 [cited by applicant]
US 20090013027A1 · Tanaka · 2009 [cited by applicant]
US 20090075725A1 · Koyama · 2009 [cited by applicant]
US 20090215538A1 · Jew · 2009 [cited by applicant]
US 20090299960A1 · Lineberger · 2009 [cited by applicant]
US 20090307284A1 · Welingkar et al. · 2009 [cited by applicant]
US 20100069149A1 · Kisenwether et al. · 2010 [cited by applicant]
US 20100113159A1 · Chapman et al. · 2010 [cited by applicant]
US 20100190549A1 · Park et al. · 2010 [cited by applicant]
US 20100275229A1 · Civanlar et al. · 2010 [cited by applicant]
US 20100302961A1 · Timmers · 2010 [cited by applicant]
US 20110014984A1 · Penman et al. · 2011 [cited by applicant]
US 20110028203A1 · Agarwal et al. · 2011 [cited by applicant]
US 20110028219A1 · Heatherly · 2011 [cited by examiner]
US 20110223996A1 · Yerli et al. · 2011 [cited by applicant]
US 20110265119A1 · Jeong et al. · 2011 [cited by applicant]
US 20110275432A1 · Lutnick et al. · 2011 [cited by applicant]
US 20110280214A1 · Lee et al. · 2011 [cited by applicant]
US 20120040692A1 · Baba · 2012 [cited by applicant]
US 20120122552A1 · Youm · 2012 [cited by applicant]
US 20120165100A1 · Lalancette · 2012 [cited by applicant]
US 20120172132A1 · Molyneaux et al. · 2012 [cited by applicant]
US 20120190453A1 · Skaff et al. · 2012 [cited by applicant]
US 20120295686A1 · Lockton · 2012 [cited by applicant]
US 20130053150A1 · Miller et al. · 2013 [cited by applicant]
US 20130178281A1 · Ayyar · 2013 [cited by examiner]
US 20130183021A1 · Osman · 2013 [cited by applicant]
US 20130217501A1 · Bruno, Jr. et al. · 2013 [cited by applicant]
US 20130244784A1 · Assa et al. · 2013 [cited by applicant]
US 20130260885A1 · Beyr et al. · 2013 [cited by applicant]
US 20130260887A1 · Cahill et al. · 2013 [cited by applicant]
US 20130260888A1 · Thornton et al. · 2013 [cited by applicant]
US 20130316797A1 · Gelinotte et al. · 2013 [cited by applicant]
US 20140038721A1 · Archer et al. · 2014 [cited by applicant]
US 20140243086A1 · Yang et al. · 2014 [cited by applicant]
US 20150111643A1 · Olofsson et al. · 2015 [cited by applicant]
US 20150209670A1 · Furumoto et al. · 2015 [cited by applicant]
US 20150238867A1 · Gould · 2015 [cited by applicant]
US 20180350191A1 · Shigeta · 2018 [cited by applicant]
JP 2001265704A · 2001 [cited by applicant]
JP 200266139A · 2002 [cited by applicant]
JP 20036127A · 2003 [cited by applicant]
JP 2003258813A · 2003 [cited by applicant]
JP 2003260272A · 2003 [cited by applicant]
JP 2006288769A · 2006 [cited by applicant]
JP 200798063A · 2007 [cited by applicant]
JP 2007160001A · 2007 [cited by applicant]
JP 200024315A · 2020 [cited by applicant]
WO 0157678A1 · 2001 [cited by applicant]
WO 2010119866A1 · 2010 [cited by applicant]
Japanese Office Action issued on Aug. 25, 2020 in Patent Application No. 2018-242439 (with English translation), 8 pages. [cited by applicant]
Japanese Office Action issued on Jan. 28, 2020, in Patent Application No. 2018-242439; 6 pages (with unedited computer generated English translation). [cited by applicant]
Office Action issued Jan. 23, 2018 in Japanese Patent Application No. 2017-022349 (with English language translation). [cited by applicant]
International Search Report issued Nov. 5, 2013, in PCT/JP2013/077005, filed Oct. 3, 2013. [cited by applicant]
Office Action issued Jan. 6, 2015, in Japanese Patent Application No. 2014-531028 (with English language translation). [cited by applicant]
Office Action issued Apr. 7, 2015 in Japanese Patent Application No. 2014-531028 (with English language translation). [cited by applicant]
Office Action issued on Oct. 5, 2021, in connection with corresponding Japanese Application No. 2020-193252 (4 pp., including machine-generated English translation). [cited by applicant]