US20140287839A1 - Method and apparatus for interactive gameplay across multiple computing platforms - Google Patents

Method and apparatus for interactive gameplay across multiple computing platforms Download PDF

Info

Publication number
US20140287839A1
US20140287839A1 US14/297,664 US201414297664A US2014287839A1 US 20140287839 A1 US20140287839 A1 US 20140287839A1 US 201414297664 A US201414297664 A US 201414297664A US 2014287839 A1 US2014287839 A1 US 2014287839A1
Authority
US
United States
Prior art keywords
user
game
computing device
data structure
server
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Abandoned
Application number
US14/297,664
Inventor
Jonas Olofsson
Patrik Stymne
Lars Sjodin
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
King com Ltd
Original Assignee
King com Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by King com Ltd filed Critical King com Ltd
Priority to US14/297,664 priority Critical patent/US20140287839A1/en
Publication of US20140287839A1 publication Critical patent/US20140287839A1/en
Assigned to KING.COM LTD. reassignment KING.COM LTD. ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: SJODIN, LARS, KNUTSSON, Sebastian, OLOFSSON, Jonas, STYME, PATRIK
Abandoned legal-status Critical Current

Links

Images

Classifications

    • A63F13/12
    • AHUMAN NECESSITIES
    • A63SPORTS; GAMES; AMUSEMENTS
    • A63FCARD, BOARD, OR ROULETTE GAMES; INDOOR GAMES USING SMALL MOVING PLAYING BODIES; VIDEO GAMES; GAMES NOT OTHERWISE PROVIDED FOR
    • A63F9/00Games not otherwise provided for
    • A63F9/24Electric games; Games using electronic circuits not otherwise provided for
    • GPHYSICS
    • G07CHECKING-DEVICES
    • G07FCOIN-FREED OR LIKE APPARATUS
    • G07F17/00Coin-freed apparatus for hiring articles; Coin-freed facilities or services
    • G07F17/32Coin-freed apparatus for hiring articles; Coin-freed facilities or services for games, toys, sports, or amusements
    • G07F17/3202Hardware aspects of a gaming system, e.g. components, construction, architecture thereof
    • G07F17/3204Player-machine interfaces
    • AHUMAN NECESSITIES
    • A63SPORTS; GAMES; AMUSEMENTS
    • A63FCARD, BOARD, OR ROULETTE GAMES; INDOOR GAMES USING SMALL MOVING PLAYING BODIES; VIDEO GAMES; GAMES NOT OTHERWISE PROVIDED FOR
    • A63F13/00Video games, i.e. games using an electronically generated display having two or more dimensions
    • A63F13/30Interconnection arrangements between game servers and game devices; Interconnection arrangements between game devices; Interconnection arrangements between game servers
    • GPHYSICS
    • G07CHECKING-DEVICES
    • G07FCOIN-FREED OR LIKE APPARATUS
    • G07F17/00Coin-freed apparatus for hiring articles; Coin-freed facilities or services
    • G07F17/32Coin-freed apparatus for hiring articles; Coin-freed facilities or services for games, toys, sports, or amusements
    • G07F17/3202Hardware aspects of a gaming system, e.g. components, construction, architecture thereof
    • G07F17/3223Architectural aspects of a gaming system, e.g. internal configuration, master/slave, wireless communication
    • GPHYSICS
    • G07CHECKING-DEVICES
    • G07FCOIN-FREED OR LIKE APPARATUS
    • G07F17/00Coin-freed apparatus for hiring articles; Coin-freed facilities or services
    • G07F17/32Coin-freed apparatus for hiring articles; Coin-freed facilities or services for games, toys, sports, or amusements
    • G07F17/326Game play aspects of gaming systems
    • G07F17/3272Games involving multiple players
    • G07F17/3276Games involving multiple players wherein the players compete, e.g. tournament

Definitions

  • the embodiments relate generally to an interactive game system that enables players to engage in a common interactive game using different computing platforms.
  • Bubble Witch Saga a popular game that can be played on facebook®.
  • a player can engage in an interactive game with other users within his or her social network such that they can play the same Bubble Witch Saga game.
  • current information about the other players in the game such as the status of each player (score, level, etc.), the names of players who are playing at the current time, and the names of players who have recently joined the game.
  • the platform in this situation would be the facebook environment, where each player accesses the game using a web browser through face book and the game is enabled by a server that communicates with each player's web browser using API's in the facebook environment.
  • One limitation of the prior art systems is that players can only engage in a common interactive video game if they are using the same platform. At present, it is not possible to engage in a common interactive game from different platforms, such as the facebook environment and an ‘iOS’ environment (an operating system created and operated by Apple Inc. and used by mobile devices including iPhone® and iPad®) and Android® based environments used by other mobile devices. It also is not possible to engage in a common interactive game when a user does not have network connectivity. What is needed is a gameplay system that can be accessed by users of different platforms. What is further needed is a gameplay system that allows play to continue even when a user has lost network connectivity and to synchronize once the user has regained network connectivity.
  • a computer implemented method of interactive gameplay comprising: receiving at a server game information from each computing device of a plurality of computing devices; storing said received game information in a respective field of a respective data structure, each data structure being associated with a respective user and stored in a data store of said server; and sending game information of a user to a computing device associated with at least one other user, wherein each data structure comprises: a user ID field; a status of game progress field; and a list of at least one other user.
  • At least one data structure may further comprise a status of in-game virtual currency field.
  • Said storing of said received game information from each computing device may comprise comparing said game progress information of said game information with previously stored game progress information associated with a user of said each computing device and determining based on the outcome of said comparing whether to replace the stored game progress information with said received game progress information.
  • Said game information may comprise one or more of: level; points; and items obtained.
  • Said list of at least one other user may be created from a list of contacts from a social networking site.
  • the method may comprise: receiving at the server an interaction request from a first computing device of said plurality of computing devices; and sending said interaction request to a second computing device of said plurality of computing devices.
  • Said interaction request may be an invitation to play a game.
  • Said interaction request may be a request for an in-game item.
  • Said interaction request may be sent via a social networking site.
  • a computer implemented method of interactive gameplay comprising: sending from a computing device game information to a server; receiving at said computing device game information of at least one other user; storing said game information of at least one other user in a at least one field of a data structure of a data store of said computing device, wherein said data structure comprises: a user ID field; a status of game progress field; and a list of at least one other user.
  • Said data structure further may comprise a status of in-game virtual currency field.
  • Said storing of said received game information may comprise comparing game progress information of said game information with previously stored game progress information associated with a said other user and determining based on the outcome of said comparing whether to replace the stored game progress information with said received game progress information.
  • Said received game information comprises one or more of: level; points; and items obtained.
  • the list of at least one other user may be created from a list of contacts from a social networking site.
  • the method may comprise sending with said computing device an interaction request to the server.
  • the method may comprise receiving at said computing device an interaction request from the server.
  • Said interaction request may be an invitation to play a game.
  • Said interaction request may be request for an in-game item.
  • Said interaction request may be sent via a social networking site.
  • the computing device may be a mobile device.
  • the computing device may be a computer running a web browser.
  • server comprising a data store comprising a plurality of data structures, each data structure being associated with a respective user and wherein each data structure comprises: a user ID field; a status of game progress field; and a list of at least one other user wherein the server is configured to: receive game information from each computing device of a plurality of computing devices; store said received game information in a respective field of a respective one of said plurality of data structures; and send game information of a user to a computing device associated with at least one other user.
  • a computing device comprising a data store comprising a data structure comprising: a user ID field; a status of game progress field; and a list of at least one other user wherein the computing device is configured to: send game information to a server; receive at said computing device game information of at least one other user; store said game information of at least one other user in a at least one field of said data structure.
  • FIG. 1 is a block diagram of a prior art interactive game system.
  • FIG. 2 illustrates an embodiment of a system that enables an interactive game by computing devices of different platforms.
  • FIG. 3 illustrates the embodiment for FIG. 2 with various data structures.
  • FIG. 4 illustrates an embodiment for creating a new interactive game session.
  • FIGS. 5A and 5B illustrate an embodiment for adding a new player to an interactive game.
  • FIG. 1 depicts a prior art system in which exemplary computing devices 30 and 40 are coupled to server 20 across network 10 .
  • Computing devices 30 and 40 each can be a desktop, notebook, server, mobile device, or any other type of device with network connectivity.
  • Network 10 can be a LAN, WAN, the Internet, or any other type of network.
  • Computing devices 30 and 40 and server 20 each are coupled to network 10 using wired connections (such as Ethernet, DSL, cable modems, or other known wired connections) or wireless connections (such as 802.11, CDMA, EDGE, EV-DO, or other known wireless connections).
  • wired connections such as Ethernet, DSL, cable modems, or other known wired connections
  • wireless connections such as 802.11, CDMA, EDGE, EV-DO, or other known wireless connections.
  • all communication between computing device 30 , computing device 40 , and server 20 occur using a common protocol, such as HTTP or an API.
  • FIG. 2 depicts an embodiment of the present invention.
  • Computing device 130 is coupled to server 122 over network 100 .
  • Computing device 140 is coupled to server 124 over network 100 .
  • computing device 130 is a PC running a first platform, such as the facebook environment.
  • Server 122 is configured to communicate with computing devices running the first platform, such as computing device 130 .
  • server 122 can be configured to communicate using facebook APIs with computing devices running the first platform.
  • Computing device 140 is a mobile device running a second platform, such as an iPhone application or Android® application.
  • Server 124 is configured to communicate with computing devices running the second platform, such as computing device 140 .
  • server 124 can be configured to communicate using a proprietary API with computing devices using the second platform.
  • Server 122 and server 124 are coupled to server 120 .
  • Computing device 130 creates and stores data structure 201 for User A
  • computing device 140 creates and stores data structure 301 for User B
  • Server 122 creates and stores data structure 202 for User A
  • server 124 creates and stores data structure 302 for User B
  • Server 120 creates and stores data structure 203 for User A and data structure 303 for User B.
  • Each of these data structures comprise common fields and sub-fields, such as the fields and sub-fields shown in Table 1:
  • FIELDS SUB-FIELDS Data structure ID
  • User ID Name Email address, Photo Game ID Timestamp of last data structure update Status of Game Progress Level, Points, Items Obtained In-Game Purchases Amount of purchase, timestamp of purchase, item purchase, status of use of purchase within game In-Game Virtual Currency Amount, time line of use of currency Other Players For each other player: User ID, Data Structure ID, Status of Game Progress (and sub-fields)
  • data structures 202 , 203 , 302 , and 303 can be tables in a database, such as a MySQL database, wherein the key is the Data Structure ID, Game ID, or User ID.
  • the database storing data structure 202 can run on server 122
  • the database storing data structure 302 can run on server 124
  • the database or databases storing data structures 203 and 303 can run on server 120 .
  • data structures 201 and 301 can be tables in databases running on computing device 130 and computing device 140 , respectively.
  • computing device 130 requests a new game to be created by sending a message to server 122 , and computing device 130 creates data structure 201 (step 400 ).
  • Server 122 then creates a new Game ID and data structure 202 (step 405 ).
  • Server 122 sends a message to server 120 that the new Game ID has been created and that data structure 202 has been created (step 410 ).
  • Server 120 then creates data structure 203 and populates the fields and sub-fields (step 415 ).
  • Server 120 and server 122 then synchronize data structure 203 and data structure 202 using the synchronization process described below (step 420 ).
  • Server 122 and computing device 130 then synchronize data structure 202 and data structure 201 using the synchronization process described below (step 425 ).
  • computing device 130 submits a request to server 122 to invite User B to the interactive game (step 450 ).
  • Server 122 submits the request to server 120 to invite User B (step 455 ).
  • Server 120 then sends a request to User B to join the game (step 460 ).
  • This request can be by email, SMS or MMS text message, an API sent directly to an application running on a computing device associated with User B ⁇ or another communication mechanism.
  • User B then accepts the request using computing device 140 (step 465 ).
  • the acceptance can be made by selecting a web link, responding by email, responding by SMS or MMS text message, selecting a button within an application, or any other communication mechanism.
  • Computing device 140 transmits the acceptance to server 124 (step 470 ).
  • Server 124 transmits the acceptance to server 120 (step 475 ).
  • Server 120 creates data structure 303 and updates data structure 203 (step 480 ).
  • Server 120 and server 122 synchronize data structures 203 and 202 (step 485 ).
  • Server 122 and computing device 130 synchronize data structures 202 and 201 (step 490 ).
  • Server 124 creates data structure 302 based on data structure 303
  • computing device 140 creates data structure 301 based on data structure 302 (step 495 ).
  • server 122 communicates with computing device 130 using a first API (such as the facebook API), and server 124 communicates with computing device 140 using a second API (such as a proprietary API designed for use with an iPhone or Android device as the case may be).
  • server 122 and server 124 can communicate with server 120 using the first and second APIs, respectively, or using a third API or protocol (such as an API for inter-server communications).
  • data structures 201 , 202 , and 203 correspond to user A
  • data structures 301 , 302 , and 303 correspond to User B
  • server 120 can create and store a master game data structure 400 for the game that User A and User B have joined.
  • Master game data structure 400 can contain the same fields and sub-fields describe previously for data structures 201 , 202 , 203 , 301 , 302 , and 303 .
  • Computing device 130 runs local application 135 (not shown), and computing device 140 runs local application 145 (not shown).
  • Local application 135 will update data structure 201 as User A progresses through the game.
  • Local application 145 will update data structure 301 as User B progresses through the game.
  • User A and User B need not necessarily be playing at the same time.
  • computing device 130 will send a synchronization request to server 122 .
  • the request will contain a timestamp. If that timestamp indicates a later time than the timestamp in data structure 202 , then data structure 202 will be written over with the data from data structure 201 as to fields and sub-fields that have changed and the timestamp field of data structure 202 will be updated with the timestamp in the initial request from computing device 130 .
  • server 122 will send a synchronization request to server 120 . If the timestamp of data structure 202 indicates a later time than the timestamp in data structure 203 , then data structure 203 will be written over with the data from data structure 202 as to fields and sub-fields that have changed and the timestamp field of data structure 203 will be updated with the timestamp of data structure 202 .
  • master game data structure 400 will be written over with the data from data structure 203 as to fields and sub-fields that have changed and its timestamp field will be updated with the timestamp of data structure 203 .
  • the “Other Players” field and sub-field of master game data structure 400 and data structure 203 do not match, then the “Other Players” field and sub-fields of data structure 203 will be overwritten with the data from master game data structure 400 , because this mismatch would only occur if the status of other players had changed since the last synchronization event, in which case master game data structure 400 would contain the more recent data for the “Other Players.”
  • server 120 will compare the timestamp fields of master game data structure 400 and data structure 303 . If the timestamp of master game data structure 400 is a later time than that of data structure 303 , then data structure 303 will be written over with the data from master game data structure 400 as to “Other Players” field and sub-fields that have changed and the time stamp of data structure 303 will be updated with the time stamp of data structure 400 .
  • server 120 will send a synchronization request to server 124 .
  • the request will contain the timestamp from data structure 303 . If that timestamp indicates a later time than the timestamp in data structure 302 , then data structure 302 will be written over with the data from data structure 303 as to the “Other Players” field and sub-fields that have changed.
  • server 124 will send a synchronization request to computing device 140 .
  • the request will contain the timestamp from data structure 303 . If that timestamp indicates a later time than the timestamp in data structure 302 , then data structure 302 will be written over with the data from data structure 303 as to “Other Players” field and sub-fields that have changed.
  • the embodiments have been described as to two users, User A and User B, but it will be appreciated by one of ordinary skill in the art that the embodiments can accommodate any number of players.
  • the embodiments have been described as to two computing devices using two different platforms, computing device 130 and 140 , but it will be appreciated by one of ordinary skill in the art that the embodiments can accommodate any number of computing devices utilizing any number of different platforms.

Abstract

A method and apparatus is disclosed for enabling interactive gameplay.

Description

    CROSS-REFERENCE TO RELATED APPLICATIONS
  • This is a continuation of pending U.S. application Ser. No. 13/479,107, filed on May 23, 2012, the entire contents of which is fully incorporated herein by reference.
  • FIELD OF THE INVENTION
  • The embodiments relate generally to an interactive game system that enables players to engage in a common interactive game using different computing platforms.
  • BACKGROUND OF THE INVENTION
  • Interactive video games among multiple players within a social network have become increasingly popular. For example, the assignee of this application is the creator of Bubble Witch Saga™, a popular game that can be played on facebook®. In Bubble Witch Saga, a particular player is faced with challenges of increasing difficulty. A player can engage in an interactive game with other users within his or her social network such that they can play the same Bubble Witch Saga game. When each player logs in to facebook and initiates the Bubble Witch Saga game, he or she will be provided with current information about the other players in the game, such as the status of each player (score, level, etc.), the names of players who are playing at the current time, and the names of players who have recently joined the game. The platform in this situation would be the facebook environment, where each player accesses the game using a web browser through face book and the game is enabled by a server that communicates with each player's web browser using API's in the facebook environment.
  • One limitation of the prior art systems is that players can only engage in a common interactive video game if they are using the same platform. At present, it is not possible to engage in a common interactive game from different platforms, such as the facebook environment and an ‘iOS’ environment (an operating system created and operated by Apple Inc. and used by mobile devices including iPhone® and iPad®) and Android® based environments used by other mobile devices. It also is not possible to engage in a common interactive game when a user does not have network connectivity. What is needed is a gameplay system that can be accessed by users of different platforms. What is further needed is a gameplay system that allows play to continue even when a user has lost network connectivity and to synchronize once the user has regained network connectivity.
  • According to a first embodiment there is provided a computer implemented method of interactive gameplay comprising: receiving at a server game information from each computing device of a plurality of computing devices; storing said received game information in a respective field of a respective data structure, each data structure being associated with a respective user and stored in a data store of said server; and sending game information of a user to a computing device associated with at least one other user, wherein each data structure comprises: a user ID field; a status of game progress field; and a list of at least one other user.
  • At least one data structure may further comprise a status of in-game virtual currency field.
  • Said storing of said received game information from each computing device may comprise comparing said game progress information of said game information with previously stored game progress information associated with a user of said each computing device and determining based on the outcome of said comparing whether to replace the stored game progress information with said received game progress information.
  • Said game information may comprise one or more of: level; points; and items obtained.
  • Said list of at least one other user may be created from a list of contacts from a social networking site.
  • The method may comprise: receiving at the server an interaction request from a first computing device of said plurality of computing devices; and sending said interaction request to a second computing device of said plurality of computing devices.
  • Said interaction request may be an invitation to play a game.
  • Said interaction request may be a request for an in-game item.
  • Said interaction request may be sent via a social networking site.
  • According to a second aspect of the present invention there is provided a computer implemented method of interactive gameplay comprising: sending from a computing device game information to a server; receiving at said computing device game information of at least one other user; storing said game information of at least one other user in a at least one field of a data structure of a data store of said computing device, wherein said data structure comprises: a user ID field; a status of game progress field; and a list of at least one other user.
  • Said data structure further may comprise a status of in-game virtual currency field.
  • Said storing of said received game information may comprise comparing game progress information of said game information with previously stored game progress information associated with a said other user and determining based on the outcome of said comparing whether to replace the stored game progress information with said received game progress information.
  • Said received game information comprises one or more of: level; points; and items obtained.
  • The list of at least one other user may be created from a list of contacts from a social networking site.
  • The method may comprise sending with said computing device an interaction request to the server.
  • The method may comprise receiving at said computing device an interaction request from the server.
  • Said interaction request may be an invitation to play a game.
  • Said interaction request may be request for an in-game item.
  • Said interaction request may be sent via a social networking site.
  • The computing device may be a mobile device.
  • The computing device may be a computer running a web browser.
  • According to a third aspect of the present invention there is provided server comprising a data store comprising a plurality of data structures, each data structure being associated with a respective user and wherein each data structure comprises: a user ID field; a status of game progress field; and a list of at least one other user wherein the server is configured to: receive game information from each computing device of a plurality of computing devices; store said received game information in a respective field of a respective one of said plurality of data structures; and send game information of a user to a computing device associated with at least one other user.
  • According to a fourth aspect of the present invention there is provided a computing device comprising a data store comprising a data structure comprising: a user ID field; a status of game progress field; and a list of at least one other user wherein the computing device is configured to: send game information to a server; receive at said computing device game information of at least one other user; store said game information of at least one other user in a at least one field of said data structure.
  • BRIEF DESCRIPTION OF THE DRAWINGS
  • FIG. 1 is a block diagram of a prior art interactive game system.
  • FIG. 2 illustrates an embodiment of a system that enables an interactive game by computing devices of different platforms.
  • FIG. 3 illustrates the embodiment for FIG. 2 with various data structures.
  • FIG. 4 illustrates an embodiment for creating a new interactive game session.
  • FIGS. 5A and 5B illustrate an embodiment for adding a new player to an interactive game.
  • DETAILED DESCRIPTION OF THE INVENTION
  • FIG. 1 depicts a prior art system in which exemplary computing devices 30 and 40 are coupled to server 20 across network 10. Computing devices 30 and 40 each can be a desktop, notebook, server, mobile device, or any other type of device with network connectivity. Network 10 can be a LAN, WAN, the Internet, or any other type of network. Computing devices 30 and 40 and server 20 each are coupled to network 10 using wired connections (such as Ethernet, DSL, cable modems, or other known wired connections) or wireless connections (such as 802.11, CDMA, EDGE, EV-DO, or other known wireless connections). Notably, in this prior art system, all communication between computing device 30, computing device 40, and server 20 occur using a common protocol, such as HTTP or an API.
  • FIG. 2 depicts an embodiment of the present invention. Computing device 130 is coupled to server 122 over network 100. Computing device 140 is coupled to server 124 over network 100.
  • In this example, computing device 130 is a PC running a first platform, such as the facebook environment. Server 122 is configured to communicate with computing devices running the first platform, such as computing device 130. For example, server 122 can be configured to communicate using facebook APIs with computing devices running the first platform.
  • Computing device 140 is a mobile device running a second platform, such as an iPhone application or Android® application. Server 124 is configured to communicate with computing devices running the second platform, such as computing device 140. For example, server 124 can be configured to communicate using a proprietary API with computing devices using the second platform. Server 122 and server 124 are coupled to server 120.
  • In this embodiment, User A (the user of computing device 130) and User B (the user of computing device 140) are able to play an interactive game together. With reference now to FIG. 3, the same structures from FIG. 2 are shown. Computing device 130 creates and stores data structure 201 for User A, and computing device 140 creates and stores data structure 301 for User B. Server 122 creates and stores data structure 202 for User A, and server 124 creates and stores data structure 302 for User B. Server 120 creates and stores data structure 203 for User A and data structure 303 for User B. Each of these data structures comprise common fields and sub-fields, such as the fields and sub-fields shown in Table 1:
  • TABLE 1
    FIELDS SUB-FIELDS
    Data structure ID
    User ID Name, Email address, Photo
    Game ID
    Timestamp of last data
    structure update
    Status of Game Progress Level, Points, Items Obtained
    In-Game Purchases Amount of purchase, timestamp
    of purchase, item purchase, status of
    use of purchase within game
    In-Game Virtual Currency Amount, time line of use of currency
    Other Players For each other player: User ID, Data
    Structure ID, Status of Game Progress
    (and sub-fields)
  • Optionally, data structures 202, 203, 302, and 303 can be tables in a database, such as a MySQL database, wherein the key is the Data Structure ID, Game ID, or User ID. The database storing data structure 202 can run on server 122, the database storing data structure 302 can run on server 124, and the database or databases storing data structures 203 and 303 can run on server 120. Optionally, data structures 201 and 301 can be tables in databases running on computing device 130 and computing device 140, respectively.
  • Referring now to FIG. 4, the initiation of an interactive game in an embodiment will now be discussed. In this example, computing device 130, at User A's instruction, requests a new game to be created by sending a message to server 122, and computing device 130 creates data structure 201 (step 400). Server 122 then creates a new Game ID and data structure 202 (step 405). Server 122 sends a message to server 120 that the new Game ID has been created and that data structure 202 has been created (step 410). Server 120 then creates data structure 203 and populates the fields and sub-fields (step 415). Server 120 and server 122 then synchronize data structure 203 and data structure 202 using the synchronization process described below (step 420). Server 122 and computing device 130 then synchronize data structure 202 and data structure 201 using the synchronization process described below (step 425).
  • With reference now to FIGS. 5A and 5B, adding an additional player to the interactive game described previously with reference to FIG. 4 will now be discussed. In this example, computing device 130, at User A's instruction, submits a request to server 122 to invite User B to the interactive game (step 450). Server 122 submits the request to server 120 to invite User B (step 455). Server 120 then sends a request to User B to join the game (step 460). This request can be by email, SMS or MMS text message, an API sent directly to an application running on a computing device associated with User B˜ or another communication mechanism. User B then accepts the request using computing device 140 (step 465). The acceptance can be made by selecting a web link, responding by email, responding by SMS or MMS text message, selecting a button within an application, or any other communication mechanism. Computing device 140 transmits the acceptance to server 124 (step 470). Server 124 transmits the acceptance to server 120 (step 475). Server 120 creates data structure 303 and updates data structure 203 (step 480). Server 120 and server 122 synchronize data structures 203 and 202 (step 485). Server 122 and computing device 130 synchronize data structures 202 and 201 (step 490). Server 124 creates data structure 302 based on data structure 303, and computing device 140 creates data structure 301 based on data structure 302 (step 495).
  • In this example, server 122 communicates with computing device 130 using a first API (such as the facebook API), and server 124 communicates with computing device 140 using a second API (such as a proprietary API designed for use with an iPhone or Android device as the case may be). Server 122 and server 124 can communicate with server 120 using the first and second APIs, respectively, or using a third API or protocol (such as an API for inter-server communications).
  • An embodiment of a synchronization process will now be discussed. In the embodiments described thus far, data structures 201, 202, and 203 correspond to user A, and data structures 301, 302, and 303 correspond to User B. Optionally, server 120 can create and store a master game data structure 400 for the game that User A and User B have joined. Master game data structure 400 can contain the same fields and sub-fields describe previously for data structures 201, 202, 203, 301, 302, and 303.
  • During game play, User A will interact with computing device 130 and User B will interact with computing device 140. Computing device 130 runs local application 135 (not shown), and computing device 140 runs local application 145 (not shown). Local application 135 will update data structure 201 as User A progresses through the game. Local application 145 will update data structure 301 as User B progresses through the game. User A and User B need not necessarily be playing at the same time.
  • In the situation where User A is playing the game, periodically (such as every 100 ms) computing device 130 will send a synchronization request to server 122. The request will contain a timestamp. If that timestamp indicates a later time than the timestamp in data structure 202, then data structure 202 will be written over with the data from data structure 201 as to fields and sub-fields that have changed and the timestamp field of data structure 202 will be updated with the timestamp in the initial request from computing device 130. However, if the “Other Players” field and sub-field of data structures 201 and 202 do not match, then the “Other Players” field and sub-fields of data structure 201 will be overwritten with the data from data structure 202, because this mismatch would only occur if the status of other players had changed since the last synchronization event, in which case data structure 202 would contain the more recent data for the “Other Players.”
  • Periodically, server 122 will send a synchronization request to server 120. If the timestamp of data structure 202 indicates a later time than the timestamp in data structure 203, then data structure 203 will be written over with the data from data structure 202 as to fields and sub-fields that have changed and the timestamp field of data structure 203 will be updated with the timestamp of data structure 202. However, if the “Other Players” field and sub-field of data structures 202 and 203 do not match, then the “Other Players” field and sub-fields of data structure 202 will be overwritten with the data from data structure 203, because this mismatch would only occur if the status of other players had changed since the last synchronization event, in which case data structure 203 would contain the more recent data for the “Other Players.”
  • If the timestamp of data structure 203 indicates a later time than the timestamp in master game data structure 400, then master game data structure 400 will be written over with the data from data structure 203 as to fields and sub-fields that have changed and its timestamp field will be updated with the timestamp of data structure 203. However, if the “Other Players” field and sub-field of master game data structure 400 and data structure 203 do not match, then the “Other Players” field and sub-fields of data structure 203 will be overwritten with the data from master game data structure 400, because this mismatch would only occur if the status of other players had changed since the last synchronization event, in which case master game data structure 400 would contain the more recent data for the “Other Players.”
  • This synchronization process between computing device 130, server 122, and server 120 has been described thus far with reference to changes in the status of User A. It will be understood by one of ordinary skill in the art that the same changes could occur in data structures 301, 302, and 303 and master game data structure 400 with reference to changes in the status of User B.
  • The changes in data structures as to User A will now propagate to the data structures associated with User B. Periodically, server 120 will compare the timestamp fields of master game data structure 400 and data structure 303. If the timestamp of master game data structure 400 is a later time than that of data structure 303, then data structure 303 will be written over with the data from master game data structure 400 as to “Other Players” field and sub-fields that have changed and the time stamp of data structure 303 will be updated with the time stamp of data structure 400.
  • Periodically, server 120 will send a synchronization request to server 124. The request will contain the timestamp from data structure 303. If that timestamp indicates a later time than the timestamp in data structure 302, then data structure 302 will be written over with the data from data structure 303 as to the “Other Players” field and sub-fields that have changed.
  • Periodically, server 124 will send a synchronization request to computing device 140. The request will contain the timestamp from data structure 303. If that timestamp indicates a later time than the timestamp in data structure 302, then data structure 302 will be written over with the data from data structure 303 as to “Other Players” field and sub-fields that have changed.
  • Thus, it will be appreciated that User A and User B can engage in an interactive game through this synchronization process.
  • An embodiment enabling “airplane mode” will now be described. If User B loses connectivity to network 100 on computing device 140 (as might occur, for example, if computing device 140 is on an airplane or has lost WiFi or cellphone connectivity), then User B can continue to play the game on computing device 140 using local application 145. Local application 145 will continue to update data structure 301. When computing device 140 regains connectivity to network 100; computing device 140 will initiate the synchronization process described above. In this manner, User A will learn of the changes in User B's status even though the changes had occurred while User B was not connected to network 100.
  • The embodiments have been described as to two users, User A and User B, but it will be appreciated by one of ordinary skill in the art that the embodiments can accommodate any number of players. Similarly, the embodiments have been described as to two computing devices using two different platforms, computing device 130 and 140, but it will be appreciated by one of ordinary skill in the art that the embodiments can accommodate any number of computing devices utilizing any number of different platforms.
  • In addition, while the foregoing has been with reference to particular embodiments of the invention, it will be appreciated by those skilled in the art that changes in these embodiments may be made without departing from the principles and spirit of the invention, the scope of which is defined by the appended claims.

Claims (23)

1. A computer implemented method of interactive gameplay comprising:
receiving at a server game information from each computing device of a plurality of computing devices;
storing said received game information in a respective field of a respective data structure, each data structure being associated with a respective user and stored in a data store of said server; and
sending game information of a user to a computing device associated with at least one other user,
wherein each data structure comprises:
a user ID field;
a status of game progress field; and
a list of at least one other user.
2. The method of claim 1 wherein at least one data structure further comprises a status of in-game virtual currency field.
3. The method of claim 1 wherein said storing of said received game information from each computing device comprises comparing said game progress information of said game information with previously stored game progress information associated with a user of said each computing device and determining based on the outcome of said comparing whether to replace the stored game progress information with said received game progress information.
4. The method of claim 3 wherein said game information comprises one or more of:
level;
points; and
items obtained.
5. The method of claim 1 wherein said list of at least one other user is created from a list of contacts from a social networking site.
6. The method of claim 1 comprising:
receiving at the server an interaction request from a first computing device of said plurality of computing devices; and
sending said interaction request to a second computing device of said plurality of computing devices.
7. The method of claim 6 wherein said interaction request is an invitation to play a game.
8. The method of claim 6 wherein said interaction request is a request for an in-game item.
9. The method of claim 6 wherein said interaction request is sent via a social networking site.
10. A computer implemented method of interactive gameplay comprising:
sending from a computing device game information to a server;
receiving at said computing device game information of at least one other user;
storing said game information of at least one other user in a at least one field of a data structure of a data store of said computing device,
wherein said data structure comprises:
a user ID field;
a status of game progress field; and
a list of at least one other user.
11. The method of claim 10 wherein said data structure further comprises a status of in-game virtual currency field.
12. The method of claim 10 wherein said storing of said received game information comprises comparing game progress information of said game information with previously stored game progress information associated with a said other user and determining based on the outcome of said comparing whether to replace the stored game progress information with said received game progress information.
13. The method of claim 10 wherein said received game information comprises one or more of:
level;
points; and
items obtained.
14. The method of claim 10 wherein the list of at least one other user is created from a list of contacts from a social networking site.
15. The method of claim 10 comprising sending with said computing device an interaction request to the server.
16. The method of claim 10 comprising receiving at said computing device an interaction request from the server.
17. The method of claim 23 wherein said interaction request is an invitation to play a game.
18. The method of claim 23 wherein said interaction request is a request for an in-game item.
19. The method of claim 23 wherein said interaction request is sent via a social networking site.
20. The method of claim 10 wherein the computing device is a mobile device.
21. The method of claim 10 wherein the computing device is a computer running a web browser.
22. A server comprising a data store comprising a plurality of data structures, each data structure being associated with a respective user and wherein each data structure comprises:
a user ID field;
a status of game progress field; and
a list of at least one other user
wherein the server is configured to:
receive game information from each computing device of a plurality of computing devices;
store said received game information in a respective field of a respective one of said plurality of data structures; and
send game information of a user to a computing device associated with at least one other user.
23. A computing device comprising a data store comprising a data structure comprising:
a user ID field;
a status of game progress field; and
a list of at least one other user
wherein the computing device is configured to:
send game information to a server;
receive at said computing device game information of at least one other user;
store said game information of at least one other user in a at least one field of said data structure.
US14/297,664 2012-05-23 2014-06-06 Method and apparatus for interactive gameplay across multiple computing platforms Abandoned US20140287839A1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US14/297,664 US20140287839A1 (en) 2012-05-23 2014-06-06 Method and apparatus for interactive gameplay across multiple computing platforms

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US13/479,107 US9017170B2 (en) 2012-05-23 2012-05-23 Method and apparatus for interactive gameplay across multiple computing platforms
US14/297,664 US20140287839A1 (en) 2012-05-23 2014-06-06 Method and apparatus for interactive gameplay across multiple computing platforms

Related Parent Applications (1)

Application Number Title Priority Date Filing Date
US13/479,107 Continuation US9017170B2 (en) 2012-05-23 2012-05-23 Method and apparatus for interactive gameplay across multiple computing platforms

Publications (1)

Publication Number Publication Date
US20140287839A1 true US20140287839A1 (en) 2014-09-25

Family

ID=48444992

Family Applications (2)

Application Number Title Priority Date Filing Date
US13/479,107 Active US9017170B2 (en) 2012-05-23 2012-05-23 Method and apparatus for interactive gameplay across multiple computing platforms
US14/297,664 Abandoned US20140287839A1 (en) 2012-05-23 2014-06-06 Method and apparatus for interactive gameplay across multiple computing platforms

Family Applications Before (1)

Application Number Title Priority Date Filing Date
US13/479,107 Active US9017170B2 (en) 2012-05-23 2012-05-23 Method and apparatus for interactive gameplay across multiple computing platforms

Country Status (7)

Country Link
US (2) US9017170B2 (en)
EP (1) EP2847743A1 (en)
JP (1) JP2015524677A (en)
KR (1) KR20150024345A (en)
CN (1) CN104508714A (en)
GB (1) GB201305767D0 (en)
WO (1) WO2013174933A1 (en)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20150111643A1 (en) * 2012-05-23 2015-04-23 King.Com Limited Systems and methods for interactive gameplay
US20220270431A1 (en) * 2021-02-24 2022-08-25 DraftKings, Inc. Systems and methods for using a non-regulated device to generate data objects via a regulated device

Families Citing this family (26)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9873045B2 (en) * 2012-05-25 2018-01-23 Electronic Arts, Inc. Systems and methods for a unified game experience
WO2014041199A1 (en) 2012-09-17 2014-03-20 King.Com Limited A method for implementing a computer game
US10828558B2 (en) 2013-02-19 2020-11-10 King.Com Ltd. Video game with spreading tile backgrounds for matched tiles
US9592441B2 (en) 2013-02-19 2017-03-14 King.Com Ltd. Controlling a user interface of a computer device
US9079097B2 (en) 2013-02-19 2015-07-14 King.Com Ltd. Video game with replaceable tiles having selectable physics
US9937418B2 (en) 2013-06-07 2018-04-10 King.Com Ltd. Computing device, game, and methods therefor
US9446313B2 (en) * 2014-03-12 2016-09-20 King.Com Ltd. Device, game and control methods therefor
JP6218178B2 (en) * 2014-03-18 2017-10-25 株式会社コナミデジタルエンタテインメント GAME SYSTEM, STORAGE CONTROL DEVICE, AND PROGRAM
WO2015160746A2 (en) 2014-04-14 2015-10-22 Boulding Blocks LLC Multi-dimensional puzzle
US20150375122A1 (en) * 2014-06-26 2015-12-31 King.Com Limited Systems and methods for controlling multiple accounts
KR102248745B1 (en) * 2014-08-29 2021-05-07 삼성전자주식회사 Display apparatus, server, and method for providing contents
CN105119918B (en) * 2015-08-21 2019-01-08 腾讯科技(深圳)有限公司 Realize the method and terminal device of application cross-platform interaction
CN105597322A (en) * 2015-12-22 2016-05-25 北京奇虎科技有限公司 Data processing method and device
CN105810035A (en) * 2016-03-16 2016-07-27 深圳市育成科技有限公司 Situational interactive cognitive teaching system and teaching method thereof
GB2551323B (en) * 2016-06-08 2021-02-10 Companion Ltd System providing a shared environment
US10974139B2 (en) * 2017-11-09 2021-04-13 Disney Enterprises, Inc. Persistent progress over a connected device network and interactive and continuous storytelling via data input from connected devices
CN109011568B (en) * 2018-08-24 2020-02-14 苏州玩友时代科技股份有限公司 Game map distribution method and system
CN110876852B (en) * 2018-09-06 2023-09-26 深圳市贰陆陆科技有限公司 Network game data processing method and system for micro-service
CN113260434A (en) * 2018-10-22 2021-08-13 索尼互动娱乐有限责任公司 Data model for unified data platform
CN111375200B (en) * 2018-12-28 2021-05-28 广州市百果园网络科技有限公司 Method and system for intelligently configuring game resources, computer storage medium and equipment
US11020660B2 (en) * 2019-02-21 2021-06-01 Sony Interactive Entertainment LLC Transactional memory synchronization between multiple sessions of a video game
CN110856008B (en) * 2019-11-25 2021-12-03 广州虎牙科技有限公司 Live broadcast interaction method, device and system, electronic equipment and storage medium
WO2021146650A1 (en) * 2020-01-17 2021-07-22 Adventure Games, Inc Interactive cloud-based gaming methodology and architecture
CN113368502B (en) * 2021-05-27 2024-01-30 江苏视博云信息技术有限公司 Cloud game management method, device and storage medium
CN113440863A (en) * 2021-07-19 2021-09-28 网易(杭州)网络有限公司 Method and device for processing multiplayer online game, electronic equipment and storage medium
CN113589982A (en) * 2021-07-29 2021-11-02 北京字跳网络技术有限公司 Resource playing method and device, electronic equipment and storage medium

Citations (26)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6050898A (en) * 1996-05-15 2000-04-18 Vr-1, Inc. Initiating and scaling massive concurrent data transaction
US20010041612A1 (en) * 2000-04-05 2001-11-15 Masood Garahi Systems and methods for cross-platform access to a wagering interface
US20010044339A1 (en) * 2000-02-17 2001-11-22 Angel Cordero Multi-player computer game, system and method
US20030177187A1 (en) * 2000-11-27 2003-09-18 Butterfly.Net. Inc. Computing grid for massively multi-player online games and other multi-user immersive persistent-state and session-based applications
US6763371B1 (en) * 1999-05-10 2004-07-13 Telefonaktiebolaget Lm Ericsson (Publ) Method and apparatus for collaborative communication in a communication network
US6947761B2 (en) * 2000-11-22 2005-09-20 Leap Wireless International Inc. Method and system for improving the efficiency of state information transfer over a wireless communications network
US20060287099A1 (en) * 2005-06-20 2006-12-21 Microsoft Corporation On-line gaming session and party management
US20070054716A1 (en) * 2005-09-08 2007-03-08 Kabushiki Kaisha Koei Network game system, client device and server apparatus
US20070088850A1 (en) * 2005-10-19 2007-04-19 Qwest Communications International Inc. Cross-platform support for a variety of media types
US20100093441A1 (en) * 2008-07-11 2010-04-15 Bally Gaming, Inc. Integration gateway
US20100160038A1 (en) * 2008-12-15 2010-06-24 Eui-Joon Youm Interactive asynchronous computer game infrastructure
US20110136577A1 (en) * 2009-12-09 2011-06-09 M5 Systems Llc Game manager with multi-platform api components
US20110281638A1 (en) * 2010-05-12 2011-11-17 Charnjit Singh Bansi System And Method For Enabling Players To Participate In Asynchronous, Competitive Challenges
US20110319169A1 (en) * 2010-06-24 2011-12-29 Zynga Game Network, Inc. Mobile Device Interface for Online Games
US20110320401A1 (en) * 2009-09-30 2011-12-29 Zynga Game Network, Inc. System and method for remote updates
US20120009997A1 (en) * 2008-12-15 2012-01-12 Eui-Joon Youm Interactive asynchronous game offline play architecture
US20120094766A1 (en) * 2010-10-14 2012-04-19 Robert Brian Reynolds Asynchronous interactive game play
US20120165100A1 (en) * 2010-12-23 2012-06-28 Alcatel-Lucent Canada Inc. Crowd mobile synchronization
US20120244950A1 (en) * 2011-03-27 2012-09-27 Edwin Braun System and method for cross-platform and cross-game virtual asset creation and management
US8303416B1 (en) * 2011-05-24 2012-11-06 Zynga Inc. Online asynchronous game with player-matching mechanic based on gameplay characteristics
US20130045803A1 (en) * 2011-08-21 2013-02-21 Digital Harmony Games, Inc. Cross-platform gaming between multiple devices of multiple types
US20130165234A1 (en) * 2011-07-28 2013-06-27 Zynga Inc. Method and system for matchmaking connections within a gaming social network
US8484564B1 (en) * 2006-03-07 2013-07-09 Google Inc. Method, system, and graphical user interface for personalized online sports team charts
US20130190094A1 (en) * 2012-01-19 2013-07-25 Eyal Ronen Asynchronous Team-Based Game
US9141682B1 (en) * 2013-03-25 2015-09-22 Amazon Technologies, Inc. Resolving conflicts within saved state data
US9224259B1 (en) * 2011-09-02 2015-12-29 Zynga Inc. Conflict resolution in asynchronous multiplayer games

Family Cites Families (18)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
AU702015B2 (en) * 1995-09-13 1999-02-11 Micro Forte Pty Limited Communication system and method
KR100741463B1 (en) * 1999-05-10 2007-07-20 텔레폰악티에볼라겟엘엠에릭슨(펍) Method and apparatus in a communication network
US7988559B2 (en) 2001-03-08 2011-08-02 Igt Computerized gaming system, method and apparatus
JP2002149464A (en) * 2000-08-17 2002-05-24 Fusionone Inc Base rolling engine for data transfer and synchronization system
US6581075B1 (en) * 2000-12-28 2003-06-17 Nortel Networks Limited System and method for database synchronization
JP3578344B2 (en) * 2001-03-27 2004-10-20 コナミ株式会社 Game data transmission / reception method, network server system, and program in network server system
WO2003036481A1 (en) * 2001-10-24 2003-05-01 Bea Systems, Inc. System and method for rule-based entitlements
US8597116B2 (en) 2002-03-12 2013-12-03 Igt Virtual player tracking and related services
JP2004046302A (en) * 2002-07-08 2004-02-12 Nec Corp Data synchronization method between two or more pieces of information apparatus, information processor which performs this method and program for performing this method
US7415711B2 (en) 2003-08-01 2008-08-19 Microsoft Corporation System and method for a transport independent gaming API for mobile devices
JP4895812B2 (en) 2003-09-18 2012-03-14 タービン インコーポレイテッド System and method for controlling access to a large multiplayer online role-playing game
JP2005234633A (en) * 2004-02-17 2005-09-02 Sony Corp Service extension method
JP2006326144A (en) * 2005-05-30 2006-12-07 Aruze Corp Game system and game machine
JP2007082626A (en) * 2005-09-20 2007-04-05 Aruze Corp Game system and game management server
CN101063989A (en) * 2006-04-26 2007-10-31 珠海市西山居软件有限公司 large scale PK battle network gaming system capable of instantaneously displaying war communique
JP4408929B2 (en) 2007-11-22 2010-02-03 株式会社スクウェア・エニックス Online game system
US8108468B2 (en) 2009-01-20 2012-01-31 Disney Enterprises, Inc. System and method for customized experiences in a shared online environment
JP2011034175A (en) * 2009-07-30 2011-02-17 Yamatake Corp Transaction control device, transaction processing method, and program

Patent Citations (27)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6050898A (en) * 1996-05-15 2000-04-18 Vr-1, Inc. Initiating and scaling massive concurrent data transaction
US6763371B1 (en) * 1999-05-10 2004-07-13 Telefonaktiebolaget Lm Ericsson (Publ) Method and apparatus for collaborative communication in a communication network
US20010044339A1 (en) * 2000-02-17 2001-11-22 Angel Cordero Multi-player computer game, system and method
US20010041612A1 (en) * 2000-04-05 2001-11-15 Masood Garahi Systems and methods for cross-platform access to a wagering interface
US6947761B2 (en) * 2000-11-22 2005-09-20 Leap Wireless International Inc. Method and system for improving the efficiency of state information transfer over a wireless communications network
US20030177187A1 (en) * 2000-11-27 2003-09-18 Butterfly.Net. Inc. Computing grid for massively multi-player online games and other multi-user immersive persistent-state and session-based applications
US20060287099A1 (en) * 2005-06-20 2006-12-21 Microsoft Corporation On-line gaming session and party management
US20070054716A1 (en) * 2005-09-08 2007-03-08 Kabushiki Kaisha Koei Network game system, client device and server apparatus
US20070088850A1 (en) * 2005-10-19 2007-04-19 Qwest Communications International Inc. Cross-platform support for a variety of media types
US8484564B1 (en) * 2006-03-07 2013-07-09 Google Inc. Method, system, and graphical user interface for personalized online sports team charts
US20100093441A1 (en) * 2008-07-11 2010-04-15 Bally Gaming, Inc. Integration gateway
US20100160038A1 (en) * 2008-12-15 2010-06-24 Eui-Joon Youm Interactive asynchronous computer game infrastructure
US20120009997A1 (en) * 2008-12-15 2012-01-12 Eui-Joon Youm Interactive asynchronous game offline play architecture
US20110320401A1 (en) * 2009-09-30 2011-12-29 Zynga Game Network, Inc. System and method for remote updates
US20110136577A1 (en) * 2009-12-09 2011-06-09 M5 Systems Llc Game manager with multi-platform api components
US20110281638A1 (en) * 2010-05-12 2011-11-17 Charnjit Singh Bansi System And Method For Enabling Players To Participate In Asynchronous, Competitive Challenges
US20110319169A1 (en) * 2010-06-24 2011-12-29 Zynga Game Network, Inc. Mobile Device Interface for Online Games
US20120094766A1 (en) * 2010-10-14 2012-04-19 Robert Brian Reynolds Asynchronous interactive game play
US20120094765A1 (en) * 2010-10-14 2012-04-19 Robert Brian Reynolds Asynchronous interactive game play
US20120165100A1 (en) * 2010-12-23 2012-06-28 Alcatel-Lucent Canada Inc. Crowd mobile synchronization
US20120244950A1 (en) * 2011-03-27 2012-09-27 Edwin Braun System and method for cross-platform and cross-game virtual asset creation and management
US8303416B1 (en) * 2011-05-24 2012-11-06 Zynga Inc. Online asynchronous game with player-matching mechanic based on gameplay characteristics
US20130165234A1 (en) * 2011-07-28 2013-06-27 Zynga Inc. Method and system for matchmaking connections within a gaming social network
US20130045803A1 (en) * 2011-08-21 2013-02-21 Digital Harmony Games, Inc. Cross-platform gaming between multiple devices of multiple types
US9224259B1 (en) * 2011-09-02 2015-12-29 Zynga Inc. Conflict resolution in asynchronous multiplayer games
US20130190094A1 (en) * 2012-01-19 2013-07-25 Eyal Ronen Asynchronous Team-Based Game
US9141682B1 (en) * 2013-03-25 2015-09-22 Amazon Technologies, Inc. Resolving conflicts within saved state data

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20150111643A1 (en) * 2012-05-23 2015-04-23 King.Com Limited Systems and methods for interactive gameplay
US20220270431A1 (en) * 2021-02-24 2022-08-25 DraftKings, Inc. Systems and methods for using a non-regulated device to generate data objects via a regulated device
US11715345B2 (en) * 2021-02-24 2023-08-01 DraftKings, Inc. Systems and methods for using a non-regulated device to generate data objects via a regulated device

Also Published As

Publication number Publication date
WO2013174933A1 (en) 2013-11-28
KR20150024345A (en) 2015-03-06
JP2015524677A (en) 2015-08-27
GB201305767D0 (en) 2013-05-15
US20130316832A1 (en) 2013-11-28
EP2847743A1 (en) 2015-03-18
CN104508714A (en) 2015-04-08
US9017170B2 (en) 2015-04-28

Similar Documents

Publication Publication Date Title
US9017170B2 (en) Method and apparatus for interactive gameplay across multiple computing platforms
US20150111643A1 (en) Systems and methods for interactive gameplay
US9533217B2 (en) Gamelets
US9526989B2 (en) Method and apparatus for receiving game streaming data, and method and server for transmitting game streaming data
US10632388B1 (en) Multilayer framework architecture and user interface for video gaming applications
US20140364210A1 (en) Computing device, game, and methods therefor
CN102016821B (en) Limiting access to shared media content
US11813531B2 (en) Techniques for adapting video game assets based on an aggregated measure of social media interaction and related systems and methods
US20140157246A1 (en) Building cross-platform asynchronous games
JP2018538052A (en) Multiplayer game session management method and management system
JP2021036470A (en) Online game synchronization method, online game synchronization system, server, client terminal, and online game synchronization program
JP2021118895A (en) Program and game system
US20140047431A1 (en) Methods and systems for updating online gaming clients
US10071317B2 (en) Systems and methods of dynamically selecting contacts for a networked gaming environment
US20150375122A1 (en) Systems and methods for controlling multiple accounts
KR20090011679A (en) Community type on-line game service system interworking with multi-game
Perry et al. Extending ARIS for Greater Collaborative Potential
KR20220152820A (en) System and method for providing game service
KR20210015253A (en) Device, system and method for providing an item
US9692803B2 (en) Computer device, system and methods for controlling an exchange of objects between devices
WO2014127651A1 (en) Methods and systems for connecting multiple devices online
JP2015058148A (en) Video game processing program and video game processing system
WO2014025830A1 (en) Methods and systems for updating online gaming clients
KR20130007129A (en) Method for advertising using chatting windows and server apparatus thereof

Legal Events

Date Code Title Description
AS Assignment

Owner name: KING.COM LTD., MALTA

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:OLOFSSON, JONAS;STYME, PATRIK;SJODIN, LARS;AND OTHERS;SIGNING DATES FROM 20141208 TO 20150623;REEL/FRAME:035907/0474

STCB Information on status: application discontinuation

Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION