Source: http://www.google.co.uk/patents/US9707476
Timestamp: 2018-01-20 02:46:01
Document Index: 289712792

Matched Legal Cases: ['Application No. 61', 'Application No. 61', 'Application No. 61', 'Application No. 61', 'Application No. 201380045408', 'Application No. 13841130', 'Application No. 2015']

Patent US9707476 - Method for creating a mini-game - Google Patents
A starting location for the mini-game is chosen in the legacy game state. A snapshot is generated of that location. Once the snapshot is taken, trigger events are identified. Triggers corresponding to the trigger events are identified. A mini-game script is generated using the snapshot and triggers....http://www.google.co.uk/patents/US9707476?utm_source=gb-gplus-sharePatent US9707476 - Method for creating a mini-game
Publication number US9707476 B2
Application number US 13/631,740
Also published as CN104685459A, EP2888651A1, EP2888651A4, US20140094314, US20170312639, US20170312640, WO2014052205A1
Publication number 13631740, 631740, US 9707476 B2, US 9707476B2, US-B2-9707476, US9707476 B2, US9707476B2
Inventors Brian Michael Christopher Watson, Victor Octav Suba Miura, Jacob P. Stine, Nicholas J. Cardell
Patent Citations (72), Non-Patent Citations (68), Classifications (14), Legal Events (2)
US 9707476 B2
A starting location for the mini-game is chosen in the legacy game state. A snapshot is generated of that location. Once the snapshot is taken, trigger events are identified. Triggers corresponding to the trigger events are identified. A mini-game script is generated using the snapshot and triggers. It is emphasized that this abstract is provided to comply with the rules requiring an abstract that will allow a searcher or other reader to quickly ascertain the subject matter of the technical disclosure. It is submitted with the understanding that it will not be used to interpret or limit the scope or meaning of the claims.
1. A non-transitory computer readable medium containing executable instructions and data for a mini-game configured to be implemented on an emulator operating on a network, the instructions and data comprising:
a) a snapshot of a starting location for the mini-game within a legacy game execution state, wherein the snapshot includes saved data corresponding to the legacy game execution state of every device being emulated by the emulator at a designated time during emulation of a legacy game that the emulator can use to start the mini-game;
b) data representing one or more identified triggers that correspond to one or more events within the legacy game; and
c) a script for the mini-game generated from the snapshot and triggers.
2. The non-transitory computer readable medium of claim 1, wherein the snapshot is any location in the legacy game execution state.
3. The non-transitory computer readable medium of claim 1, wherein the event identifies a mini-game-ending trigger.
4. The non-transitory computer readable medium of claim 3, wherein the mini-game-ending trigger is the mini-game timing out.
5. The non-transitory computer readable medium of claim 3, wherein the mini-game-ending trigger is an adversary being neutralized.
6. The non-transitory computer readable medium of claim 3, wherein the mini-game-ending trigger is a protagonist being neutralized.
7. The non-transitory computer readable medium of claim 3, wherein the mini-game-ending trigger is a certain score being achieved.
8. The non-transitory computer readable medium of claim 1, wherein the event identifies a non-mini-game-ending trigger.
9. The non-transitory computer readable medium of claim 8, wherein the non-mini-game-ending trigger is a certain score being achieved.
10. The non-transitory computer readable medium of claim 8, wherein the non-mini-game-ending trigger is a character reaching a certain level within the mini-game.
11. A non-transitory computer readable medium containing program instructions for generating a mini-game, wherein execution of the program instructions by one or more processors of a computer system causes the one or more processors to carry out a method comprising:
a) choosing a snapshot of a starting location for the mini-game within legacy game execution state, wherein the snapshot includes saved data corresponding to the legacy game execution state of every device being emulated by an emulator at a designated time during emulation of a legacy game that the emulator can use to start the mini-game;
b) choosing one or more events within the legacy game execution state;
c) identifying one or more triggers that correspond to the events; and
d) generating a script for the mini-game from the snapshot and triggers.
12. The non-transitory computer readable medium of claim 11, wherein the snapshot is any location in the legacy game execution state.
13. The non-transitory computer readable medium of claim 11, wherein the event is a mini-game-ending trigger.
14. The non-transitory computer readable medium of claim 13, wherein the mini-game-ending trigger is the mini-game timing out.
15. The non-transitory computer readable medium of claim 13, wherein the mini-game-ending trigger is an adversary being neutralized.
16. The non-transitory computer readable medium of claim 13, wherein the mini-game-ending trigger is a protagonist being neutralized.
17. The non-transitory computer readable medium of claim 13, wherein the mini-game-ending trigger is a certain score being achieved.
18. The non-transitory computer readable medium of claim 13, wherein the mini-game-ending trigger is a character reaching a certain level within the mini-game.
19. The non-transitory computer readable medium of claim 11, wherein the event is a non-mini-game-ending trigger.
20. The non-transitory computer readable medium of claim 18, wherein the non-mini-game-ending trigger is a certain score being achieved.
21. The non-transitory computer readable medium of claim 18, wherein the non-mini-game-ending trigger is a character reaching a certain level within the mini-game.
22. A method for generating a mini-game configured to be implemented on an emulator operating on a network, comprising:
a) choosing a snapshot of a starting location for the mini-game within a legacy game execution state, wherein the snapshot includes saved data corresponding to the legacy game execution state of every device being emulated by the emulator at a designated time during emulation of a legacy game that the emulator can use to start the mini-game;
b) choosing one or more events within the legacy game execution state; and
23. The non-transitory computer readable medium of claim 1, wherein every device being emulated by the emulator is in a steady state at the designated time, wherein the steady state is one in which there are no asynchronous activities occurring in the emulator at the designated time.
This application is related to commonly-assigned, co-pending provisional application entitled “DETERMINING TRIGGERS FOR CLOUD-BASED EMULATED GAMES” to Brian Michael Christopher Watson, Victor Octav Suba Miura, Jacob P. Stine and Nicholas J. Cardell, U.S. Application No. 61/666,628, filed Jun. 29, 2012, the entire disclosures of which are incorporated herein by reference.
This application is related to commonly-assigned, co-pending provisional application entitled “HAPTIC ENHANCEMENTS FOR EMULATED VIDEO GAME NOT ORIGINALLY DESIGNED WITH HAPTIC CAPABILITIES” to Victor Octav Suba Miura and Brian Michael Christopher Watson, U.S. Application No. 61/666,645, filed Jun. 29, 2012, the entire disclosures of which are incorporated herein by reference.
This application is related to commonly-assigned, co-pending provisional application entitled “CONVERSION OF HAPTIC EVENTS INTO SCREEN EVENTS” to Brian Michael Christopher Watson and Victor Octav Suba Miura, U.S. Application No. 61/666,665 filed Jun. 29, 2012, the entire disclosures of which are incorporated herein by reference.
This application is related to commonly-assigned, co-pending provisional application entitled “SUSPENDING STATE OF CLOUD-BASED LEGACY APPLICATION” to Jacob P. Stine, Brian Michael Christopher Watson, Victor Octav Suba Miura and Nicholas J. Cardell, U.S. Application No. 61/666,679, filed Jun. 29, 2012, the entire disclosures of which are incorporated herein by reference.
This application is related to commonly-assigned, co-pending application Ser. No. 13/631,725, filed the same day as the present application, and entitled “REPLAY AND RESUMPTION OF SUSPENDED GAME” to Brian Michael Christopher Watson, Victor Octav Suba Miura, Jacob P. Stine and Nicholas J. Cardell, filed the same day as the present application, the entire disclosures of which are incorporated herein by reference.
This application is related to commonly-assigned, co-pending application Ser. No. 13/631,785, filed the same day as the present application, and entitled “PRE-LOADING TRANSLATED CODE IN CLOUD BASED EMULATED APPLICATIONS”, to Jacob P. Stine, Victor Octav Suba Miura, Brian Michael Christopher Watson, and Nicholas J. Cardell the entire disclosures of which are incorporated herein by reference.
This application is related to commonly-assigned, co-pending application Ser. No. 13/631,803 filed the same day as the present application, and entitled “ADAPTIVE LOAD BALANCING IN SOFTWARE EMULATION OF GPU HARDWARE”, to Takayuki Kazama and Victor Octav Suba Miura, the entire disclosures of which are incorporated herein by reference.
This application is related to commonly-assigned, co-pending application Ser. No. 13/631,812, filed the same day as the present application, entitled “METHOD AND APPARATUS FOR IMPROVING EFFICIENCY WITHOUT INCREASING LATENCY IN EMULATION OF A LEGACY APPLICATION TITLE”, to Jacob P. Stine and Victor Octav Suba Miura, the entire disclosures of which are incorporated herein by reference.
The present disclosure is related to a method for creating a video mini-game based on a legacy game title using a snapshot technique. Among other things, this application describes a method for creating a video mini-game from a legacy game by identifying an interesting location in the game where the mini-game can begin. This location is called a snapshot. This method creates a new game based on a snapshot of a legacy game, and provides small cuts of entertainment for players who do not want to play the whole legacy game.
Finding new ways to play legacy video games can increase the longevity of older games. Instead of playing the whole game, which can span many hours, gamers desire an opportunity to play a game with a shorter time frame. Gamers also appreciate being able to play a game with which they are familiar. It is within this context that aspects of the present disclosure arise.
FIG. 2 is a block diagram illustrating a method of generating a mini-game script from a pre-existing game and delivering the script to the emulator.
FIG. 3 is a block diagram illustrating a method of selecting a mini-game at the client device platform and sending the mini-game selection input to the emulator.
FIG. 4 is a block diagram illustrating how the instructions for the mini-game snapshot and emulated game data are sent to the client device platform, mini-game input data is sent back to the emulator.
FIG. 5 is a block diagram illustrating the emulation process and the interaction between the emulator, mini-game script and client device platform.
FIG. 6 is a decision tree illustrating how the mini-game script responds to triggers.
In response to the need for increasing the longevity of legacy games and to play a game with a shorter time frame in which the gamer is familiar, a method to create mini-games has been devised. The method is based on creating a mini-game from a legacy game title using a snapshot technique. The method involves a mini-game generator generating a snapshot of an interesting starting location within the legacy game. There is some defined event that when achieved will cause the mini-game to reach an endpoint or a non-endpoint. These events can include, without limitation, the mini-game timing out, a certain score being achieved, the lead character being neutralized, the adversary being neutralized, or some other objective being reached. One or more triggers that correspond to the events are identified from the legacy game. The triggers are used to define the endpoint of the mini-game. The triggers can also be used to define other corresponding events that occur during mini-game play. The mini-game generator records the snapshot and triggers data. A developer can create a script from the captured data (snapshot and triggers) and bundle the script with the captured data. Within a mini-game, the gamer can be instructed to complete new objectives or challenge their friends for high scores in a format that was not originally designed into the legacy game. Further, since the mini-game is derived from a legacy game, the gamer already knows the characters and basic components of the game, and is therefore more likely to play the mini-game.
In order to create mini-games without reverse engineering and recoding a legacy game, a game designer may rely on the use of triggers and snapshots to provide information needed for the mini-games without having to dig into the code of the legacy game. The mini-games may be created by providing an emulator with game inputs that bring the emulated game to a certain point where the mini-game will begin. A snapshot may be generated at that point in order to be used as the starting point in the future mini-game. A snapshot can be generated at any location in a legacy game. As used herein, a snapshot may be a recorded description of the state of every device being emulated at a designated time during the emulation according to an aspect of the present disclosure.
A snapshot may be generated by a snapshot generator as follows. First the snapshot generator delivers game inputs to an emulator. The emulator receives the game inputs and proceeds to emulate the game according to the game inputs. At some point during the emulation, the snapshot generator delivers a suspension request to the emulator. Once the suspension request is received, the emulator will suspend the emulated title at the next point in time at which all devices being emulated are in a steady state. Steady state means there are no asynchronous activities occurring in the emulator. At this steady state, the snapshot generator generates a snapshot of the emulated game by recording the current state of all devices being emulated. Snapshots are further described in commonly assigned pending application Ser. No. 61/666,679 filed on Jun. 29, 2012, and entitled “SUSPENDING STATE OF CLOUD-BASED LEGACY APPLICATIONS”, which has been incorporated herein by reference.
Once the snapshot is taken to identify the starting point in the mini-game, triggers may be generated according to aspects of the present disclosure in order to provide new experiences for the game. According to an aspect of the present disclosure, a trigger event that requires an emulator to produce a desired output is identified. A trigger that is associated with the trigger event is then identified and stored in a memory of the emulator. Thereafter, when the emulator runs an emulation routine, it will compare the emulated game data to the trigger stored in its memory, and will therefore know to produce the desired output when the emulated game data matches the trigger. Game designers may then develop a script by using the snapshot and triggers to produce the mini-game. Triggers are further described in commonly assigned pending application Ser. No. 61/666,628 filed on Jun. 29, 2012, and entitled “DETERMINING TRIGGERS FOR CLOUD-BASED EMULATED GAMES”, which has been incorporated herein by reference.
FIG. 1 is a schematic diagram illustrating interaction between client device platform 103 and an emulator 107 according to aspects of the present disclosure. The emulator 107 may be accessed by a client device platform 103 over a network 160. Although only a single emulator is shown in FIG. 1, aspects of the present disclosure are not limited to such implementations. The client device platform 103 may access a plurality of alternative emulators 107 over the network 160. The emulators 107 may be identical to each other, or they may each be programmed to emulate unique legacy game titles 106 or unique sets of legacy game titles 106.
The client device platform 103 may include a central processor unit (CPU) 131. By way of example, a CPU 131 may include one or more processors, which may be configured according to, e.g., dual-core, quad-core, multi-core, or Cell processor architecture. The client device platform 103 may also include a memory 132 (e.g., RAM, DRAM, ROM, and the like). The CPU 131 may execute a process-control program 133, portions of which may be stored in the memory 132. The client device platform 103 may also include well-known support circuits 140, such as input/output (I/O) circuits 141, power supplies (P/S) 142, a clock (CLK) 143 and cache 144. The client device platform 103 may optionally include a mass storage device 134 such as a disk drive, CD-ROM drive, tape drive, or the like to store programs and/or data. The client device platform 103 may also optionally include a display unit 137. The display unit 137 may be in the form of a cathode ray tube (CRT) or flat panel screen that displays text, numerals, or graphical symbols. A controller 145 may be connected to the client device platform 103 through the I/O circuit 141 or it may be directly integrated into the client device platform 103. The controller 145 may facilitate interaction between the client device platform 103 and a user. The controller 145 may include a keyboard, mouse, joystick, light pen, hand-held controls or other device. The client device platform 103 may include a network interface 139, configured to enable the use of Wi-Fi, an Ethernet port, or other communication methods.
The emulator 107 may include a central processor unit (CPU) 131′. By way of example, a CPU 131′ may include one or more processors, which may be configured according to, e.g., a dual-core, quad-core, multi-core, or Cell processor architecture. The emulator 107 may also include a memory 132′ (e.g., RAM, DRAM, ROM, and the like). The CPU 131′ may execute a process-control program 133′, portions of which may be stored in the memory 132′. The emulator 107 may also include well-known support circuits 140′, such as input/output (I/O) circuits 141′, power supplies (P/S) 142′, a clock (CLK) 143′ and cache 144′. The emulator 107 may optionally include a mass storage device 134′ such as a disk drive, CD-ROM drive, tape drive, or the like to store programs and/or data. The emulator 107 may also optionally include a display unit 137′ and user interface unit 138′ to facilitate interaction between the emulator 107 and a user who requires direct access to the emulator 107. By way of example and not by way of limitation a client device platform 103 or engineer may need direct access to the emulator 107 in order to program the emulator 107 to properly emulate a desired legacy game 106 or to add additional mini-game capabilities to a legacy game 106. The display unit 137′ may be in the form of a cathode ray tube (CRT) or flat panel screen that displays text, numerals, or graphical symbols. The user interface unit 138′ may include a keyboard, mouse, joystick, light pen, or other device. The emulator 107 may include a network interface 139′, configured to enable the use of Wi-Fi, an Ethernet port, or other communication methods.
Emulator 107 may access a legacy game 106 that has been selected by the client device platform 103 for emulation through the internal system bus 150′. There may be more than one legacy game 106 stored in the emulator 107, e.g., in the memory 132′ or in the mass storage device 134′. Additionally, one or more legacy games 106 may be stored at a remote location accessible to the emulator 107 over the network 160. Each legacy game 106 contains game code 108. When the legacy game 106 is emulated, the game code 108 produces legacy game data 109.
As shown in FIG. 2, the mini-game is generated from a legacy game. By way of example, and not by way of limitation, the mini-game generator 218 chooses a mini-game starting location in the legacy game, as indicated at 251. The starting location may be any location within the legacy game. After a starting location is chosen, the mini-game generator generates a snapshot of that point in the legacy game, as indicated at 252. The next step is to choose one or more events from the legacy game execution state, as indicated at 253. In some implementations, the executions state may be modified slightly after it has been loaded. By way of example, and not by way of limitation, the execution state maybe modified by setting the current score, number of lives remaining, or remaining time in the game.
The mini-game generator identifies one or more triggers that correspond to the events, as indicated at 254. The events may include, by way of example and without limitation, mini-game-ending triggers such as the mini-game timing out, an adversary being neutralized, a protagonist being neutralized or a certain score being achieved. The events may also include, by way of example and without limitation, non-mini-game-ending triggers such as a certain score being achieved or a game character reaching a certain level within the game. The identified triggers may include changes in the game state or game data that correspond to the events. For example, if the event is a certain score being achieved, the corresponding trigger would occur when the game data indicates that the certain score has been achieved. The mini-game generator combines the snapshot and triggers to generate a script 209 for a particular mini-game, as indicated at 255. The mini-game script 209 selection may then be loaded on an emulator 207. The mini-game script 209, a snapshot of the starting location and trigger data may all be stored in a non-transitory computer-readable medium.
In some implementations, game state information may be harvested and utilized within a controlling script to determine subsequent events within the mini-game. By way of example, and not by way of limitation, information regarding virtual items obtained by a player during one the mini-game may be carried over to a subsequent part. Alternatively, the score may determine whether a player advances to another level or determines the level to which the player advances after a section the mini-game has been completed.
FIG. 3 schematically illustrates an example of implementing a mini-game. A client device platform 303 instructs an emulator 307 to send emulated game data of a legacy game by selecting a mini-game option from a plurality of mini-game choices 312 as they may appear on the client device platform display 311. Based on the mini-game 312 selected, the mini-game script 317 provides the emulator 307 with game inputs that bring the emulated game to the starting location of the mini-game within the legacy game execution state 316. The starting location data 314 of the emulated game are then sent to the client device platform 303 and are shown on the client device platform display 311.
FIG. 4 schematically illustrates another example of implementing a mini-game. In this example, as game play begins, a client device platform 403 receives emulated game data 414 of a legacy game from an emulator 407. As the game is played on the client device (e.g., using a game interface 411, which may be implemented in hardware or software or some combination thereof), emulated game data 414 is continually sent to the client device platform 403 from the emulator 407. Simultaneously, mini-game input data 420 is sent from the client device platform 403 to the emulator 407. The mini-game script 417 monitors game play that results from the emulated game data 414 and input data 420 to determine if any triggers occur. The mini-game script 417 provides the emulator 407 with game inputs that bring the emulated game to an end when a game-ending trigger occurs. The mini-game script 417 may also provide the emulator 407 with non-game-ending inputs when a non-game-ending trigger occurs.
FIG. 5 is a flow diagram illustrating the interaction between the client device platform 103 the mini-game script 109 and the emulation process 570. In one embodiment, the mini-game is selected from the client device platform 103, as indicated at 591. The mini-game selection data is sent to the emulator 107 which loads the game instructions and the mini-game script 109, as indicated at 571. The mini-game script 109 loads the snapshot 581 onto the emulator 107 and mini-game play begins, as indicated at 576. The emulator 107 generates emulated game data as indicated at 577. The emulated game data is sent to the client device platform 103. The client device platform 103 receives emulated game data from the emulator 107, as indicated at 592. The client device platform 103 sends game inputs as also indicated at 592 which are received by the emulator 107, as also indicated at 577. The mini-game script 109 monitors data from the emulated game identifying triggers that correspond to events within the game, as indicated at 582.
FIG. 6 is a decision tree illustrating how the mini-game script 209 monitors data from the emulated game at 582. If the mini-game script detects a mini-game-ending trigger, e.g., by comparing the emulated game data to the trigger data, the script sends mini-game-ending instructions to the emulator. If the mini-game script does not detect a mini-game-ending trigger it continues monitoring the game data. If the mini-game script detects a non-mini-game-ending trigger, the script sends non-game-ending instructions to the emulator and continues monitoring the game data.
As may be seen from the foregoing, embodiments of the present invention allow for the increased utility of legacy games through the use of snapshots and triggers without having to expend the resources required for creating an entirely new game. This provides game players with the benefit of shorter gaming experiences for games in which they are already familiar.
US6280323 17 Nov 1997 28 Aug 2001 Konami Co., Ltd. Device, method and storage medium for displaying penalty kick match cursors in a video soccer game
US20020065915 30 Nov 2000 30 May 2002 Anderson Elizabeth A. System and method for server-host connection management to serve anticipated future client connections
US20090082102 19 Sep 2008 26 Mar 2009 Sony Computer Entertainment Inc. Method and apparatus for emulation enhancement
US20140004962 8 Mar 2013 2 Jan 2014 Victor Octav Suba Miura Determining triggers for cloud-based emulated games
CN1192013A 21 Nov 1997 2 Sep 1998 科乐美股份有限公司 Video game system and storage medium for storing program for use in video game system
CN101346162B 2 Nov 2006 21 Mar 2012 科乐美数码娱乐株式会社 Game machine, and game machine control method
CN101889442B 4 Dec 2008 8 Oct 2014 欧乐2号公司 用于结合多个实时流动互动式视频的视图的系统
WO2014052205A1 20 Sep 2013 3 Apr 2014 Sony Computer Entertainment Inc. Method for creating a mini-game
1 Chinese Office Action for CN Application No. 201380045408.4, dated Sep. 20, 2016.
2 Co-Pending U.S. Appl. No. 61/694,718, to Gary M. Zalewski, filed Aug. 29, 2012.
3 Co-Pending U.S. Appl. No. 61/794,811, to Victor Octav Suba Miura, filed Mar. 15, 2013.
4 European Search Report and Written Opinion for EP Application No. 13841130.1, dated Oct. 4, 2016.
5 European Search Report and Written Opinion for European Application No. PCT/US2013/047856, dated Jul. 28, 2016.
6 Final Office Action for U.S. Appl. No. 13/631,725, dated Dec. 19, 2014.
7 Final Office Action for U.S. Appl. No. 13/631,785, dated Dec. 4, 2015.
8 Final Office Action for U.S. Appl. No. 13/631,803, dated Apr. 16, 2015.
9 Final Office Action for U.S. Appl. No. 13/631,803, dated Feb. 1, 2016.
10 Final Office Action for U.S. Appl. No. 13/631,812, dated Aug. 29, 2014.
12 Final Office Action for U.S. Appl. No. 13/790,320, dated Feb. 10, 2016.
13 Final Office Action for U.S. Appl. No. 13/790,320, dated Jan. 15, 2015.
14 Final Office Action for U.S. Appl. No. 13/791,379, dated May 13, 2015.
15 Final Office Action for U.S. Appl. No. 13/791,420, dated Jun. 11, 2014.
16 Final Office Action for U.S. Appl. No. 13/791,420, dated Oct. 9, 2015.
17 Final Office Action for U.S. Appl. No. 13/791,434, dated Feb. 17, 2016.
18 Final Office Action for U.S. Appl. No. 13/791,434, dated Jun. 23, 2015.
19 Final Office Action for U.S. Appl. No. 15/019,891, dated Oct. 19, 2016.
20 * Grand Theft Auto: San Andreas Guide-Territories, https://www.youtube.com/watch?v=5d2GY-grsFA, May 29, 2012.
21 * Grand Theft Auto: San Andreas Guide—Territories, https://www.youtube.com/watch?v=5d2GY-grsFA, May 29, 2012.
22 * GTA San Andreas How to start a gang war, https://www.youtube.com/watch?v=9N49O8kGtL0, Jan. 13, 2013.
23 International Search Report and Written Opinion for International Application No. PCT/US2013/074813, dated May 29, 2014.
24 Japanese Office Action for Japan Application No. 2015-517495, dated Feb. 9, 2016.
25 Non Final Office Action for U.S. Appl. No. 13/790,311 dated Jun. 27, 2013 6 pages.
26 Non-Final Office Action for U.S. Appl. No. 13/631,725, dated Mar. 16, 2015.
27 Non-Final Office Action for U.S. Appl. No. 13/631,725, dated Sep. 12, 2014.
32 Non-Final Office Action for U.S. Appl. No. 13/631,812, dated Mar. 28, 2014.
33 Non-Final Office Action for U.S. Appl. No. 13/790,311, dated Feb. 26, 2014.
34 Non-Final Office Action for U.S. Appl. No. 13/790,311, dated Jun. 27, 2013.
35 Non-Final Office Action for U.S. Appl. No. 13/790,311, dated Nov. 19, 2015.
36 Non-Final Office Action for U.S. Appl. No. 13/790,311,dated Sep. 9, 2014.
37 Non-Final Office Action for U.S. Appl. No. 13/790,320, dated Jul. 28, 2015.
38 Non-Final Office Action for U.S. Appl. No. 13/790,320, dated Jun. 18, 2014.
39 Non-Final Office Action for U.S. Appl. No. 13/791,379 dated Apr. 21, 2017.
40 Non-Final Office Action for U.S. Appl. No. 13/791,379, dated Mar. 27, 2014.
41 Non-Final Office Action for U.S. Appl. No. 13/791,379, dated Oct. 16, 2014.
42 Non-Final Office Action for U.S. Appl. No. 13/791,420, dated Apr. 9, 2015.
43 Non-Final Office Action for U.S. Appl. No. 13/791,420, dated Mar. 27, 2014.
44 Non-Final Office Action for U.S. Appl. No. 13/791,434, dated Nov. 26, 2014.
45 Non-Final Office Action for U.S. Appl. No. 13/792,664, dated Jun. 23, 2014.
46 Non-Final Office Action for U.S. Appl. No. 14/183,351, dated May 11, 2015.
47 Non-Final Office Action for U.S. Appl. No. 15/225,361, dated Oct. 21, 2016.
48 Notice of Allowance for U.S. Appl. No. 13/631,725, dated Oct. 6, 2015.
49 Notice of Allowance for U.S. Appl. No. 13/790,311, dated Mar. 30, 2017.
50 Notice of Allowance for U.S. Appl. No. 13/790,320, dated Dec. 5, 2016.
54 * Playstation2, 2004, Grand Theft Auto-San Andreas.
55 * Playstation2, 2004, Grand Theft Auto—San Andreas.
56 U.S. Appl. No. 13/631,725, entitled "Replay and Resumption of Suspended Game" to Brian Michael Christopher Watson et al., filed Sep. 28, 2012.
57 U.S. Appl. No. 13/631,785, entitled "Pre-loading Translated Code in Cloud Based Emulated Applications" to Jacob P. Stine et al., filed Sep. 28, 2012.
58 U.S. Appl. No. 13/631,803, entitled "Adaptive Load Balancing in Software Emulation of GPU Hardware", to Takayuki Kazama and Victor Octav Suba Miura , filed Sep. 28, 2012.
59 U.S. Appl. No. 13/631,812, entitled "Method and Apparatus for Improving Efficiency Wihout Increasing Latency in Emulation of a Legacy Application Title" to Jacob P. Stine et al., filed Sep. 28, 2012.
60 U.S. Appl. No. 13/790,311, entitled "Adding Triggers to Cloud-Based Emulated Games" to Victor Octav Suba Miura et al., filed Mar. 8, 2013.
61 U.S. Appl. No. 13/790,320, entitled "Determining Triggers for Cloud-Based Emulated Games" to Victor Octav Suba Miura et al., filed Mar. 8, 2013.
62 U.S. Appl. No. 13/791,379, entitled "Suspending State of Cloud-Based Legacy Application" to Jacob P. Stine et al., filed Mar. 8, 2013.
63 U.S. Appl. No. 13/791,420, entitled "Conversion of Haptic Events Into Screen Events" to Brian Michael Christopher Watson and Victor Octav Suba Miura , filed Mar. 8, 2013.
64 U.S. Appl. No. 13/791,434, entitled "Haptic Enhancements for Emulated Video Game Not Originally Designed with Haptic Capabilities" to Victor Octav Suba Miura and Brian Michael Christopher Watson , filed Mar. 8, 2013.
66 U.S. Appl. No. 61/666,645 to Victor Octav Suba Miura et al., filed Jun. 29, 2012.
67 U.S. Appl. No. 61/666,665 to Brian Michael Christopher Watson et al., filed Jun. 19, 2012.
68 U.S. Appl. No. 61/666,679 to Jacob P. Stine et al., filed Jun. 29, 2012.
International Classification A63F13/30, A63F13/60, A63F13/69, A63F13/40, A63F13/70, A63F13/88
Cooperative Classification A63F13/69, A63F2300/6009, A63F13/10, A63F13/12, A63F2300/6036, A63F13/60, A63F13/70, A63F13/88
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:WATSON, BRIAN MICHAEL CHRISTOPHER;SUBA MIURA, VICTOR OCTAV;STINE, JACOB P.;AND OTHERS;SIGNING DATES FROM 20121206 TO 20121210;REEL/FRAME:029474/0886