Establishing a social application layer

- Kabam, Inc.

A virtual space may be presented within a plurality of virtual environments provided by different platforms without requiring idiosyncratic APIs associated with the virtual space for each different platform. An API adaptor module may be configured to facilitate interfacing between a single virtual space API and platform APIs associated with two or more different platforms. A space module may be configured to execute an instance of a virtual space, and to implement the instance of the virtual space to determine view information defining views of the instance of the virtual space for presentation via two or more virtual environments provided by the two or more platforms. Facilitating user interactivity with the virtual space via a given virtual environment provided by a given platform may include interfacing between the virtual space API and a platform API associated with the given platform.

Skip to: Description  ·  Claims  ·  References Cited  · Patent History  ·  Patent History
Description
FIELD OF THE DISCLOSURE

This disclosure relates to facilitating presentation of a virtual space within a plurality of virtual environments provided by different platforms without requiring idiosyncratic APIs associated with the virtual space for each different platform.

BACKGROUND

Presenting a virtual space within a virtual environment is known. Typically, however, a provider of the virtual space may be required to provide a separate application programming interface (API) for each different virtual environment in which the virtual space is presented. Thus, a change to the virtual space may require corresponding changes to each of the separate APIs.

SUMMARY

One aspect of the disclosure relates to a system configured to facilitate presentation of a virtual space within a plurality of virtual environments provided by different platforms without requiring idiosyncratic APIs associated with the virtual space for each different platform, in accordance with one or more implementations. In exemplary implementations, an API adaptor module may be configured to facilitate interfacing between a single virtual space API and platform APIs associated with two or more different platforms. There may be separate API adaptor modules or sub-modules corresponding to individual ones of the different platforms. The API adaptor module may serve as a converter between the virtual space API and various platform APIs such that a single version of the virtual space may be presented in virtual environments provided by any of the different platforms. Thus, a change to the virtual space may not necessitate corresponding changes to a plurality of virtual space APIs. Some implementations may ensure that the virtual space is displayed correctly within different virtual environments. Some implementations may facilitate accessing social graph information associated with individual virtual environments via the virtual space, interacting with platform mechanics of individual virtual environments via the virtual space, and/or transferring publishing information between the virtual space and individual virtual environments.

In some implementations, system may include one or more of one or more platform servers, one or more space servers, and/or other components. The platform server(s) may be configured to communicate with one or more client computing platforms according to a client/server architecture to provide virtual environments to users via client computing platform(s). The space server(s) may be configured to interface with individual platform server(s) to supplement the functionality provided to the users with respect to the virtual environments. For example, space server(s) may interface with individual platform server(s) via one or more APIs.

The space server(s) may be configured to execute one or more computer program modules. The computer program modules may include one or more of an API adaptor module, a space module, a social graph access module, a platform mechanics module, a platform publishing module, and/or other modules.

The API adaptor module may be configured to facilitate interfacing between a single virtual space API and platform APIs associated with two or more different platforms. Generally speaking, an API may be viewed as a set of routines and/or services used by an application program to direct the performance of procedures by a host environment and/or host computing platform. Interfacing between two APIs (e.g., a virtual space API and a platform API) may include translating commands, calls, functions, and/or other information associated with APIs between the two APIs. The virtual space API may be associated with a virtual space provided by space module, as described further herein. The two or more different platforms may correspond to individual ones of the platform server(s). A given platform server may be associated with a specific platform API. The API adaptor module may be configured to facilitate proper display of the virtual space within virtual environments provided the platform server(s). In some implementations, the API adaptor module may include two or more sub-modules each corresponding to individual platforms.

The space module may be configured to implement at least one instance of the virtual space to determine views of the virtual space. The views may then be communicated (e.g., via streaming, via object/position data, and/or other information) from the platform server(s) to the client computing platform(s) for presentation to users via two or more virtual environments provided by the platform server(s). Facilitating user interactivity with the virtual space via a given virtual environment provided by a given platform may include interfacing between the virtual space API and the platform API associated with the given platform. User interactivity may include accessing social graph information associated with individual virtual environments via the virtual space, interacting with platform mechanics of individual virtual environments via the virtual space, transferring publishing information between the virtual space and individual virtual environments, and/or other interactions by a user with the virtual space.

The social graph access module may be configured to facilitate accessing social graph information associated with individual virtual environments provided by the platform server(s). The social graph information may be accessed via the virtual space provided by the space module. Generally speaking, a social graph may be viewed as a mapping of relationships (e.g., personal, professional, familial, and/or other relationships) between users associated directly and/or indirectly with a given virtual environment. According to some implementations, social graph information associated with a given virtual environment may include one or more of friends, contacts, relationship type, relationship duration, relationships in common, and/or other information included in a social graph of the given virtual environment. Social graph information associated with a given virtual environment may be used within the virtual environment provided by the space module. Accessing social graph information associated with a given virtual environment may include interfacing between the virtual space API and the platform API associated with the platform providing the given virtual environment.

The platform mechanics module may be configured to facilitate interacting with platform mechanics associated with individual virtual environments provided by the platform server(s). The platform mechanics may be interacted with via the virtual space provided by the space module. Platform mechanics may be viewed generally as constructs of rules and/or functions of a virtual environment. In some implementations, platform mechanics associated with a given virtual environment may include one or more of invitations, requests, alerts, gifts, events, and/or other mechanics of the given virtual environment. Platform mechanics associated with a given virtual environment may be used within the virtual environment provided by the space module. Interacting with platform mechanics associated with a given virtual environment may include interfacing between the virtual space API and the platform API associated with the platform providing the given virtual environment.

The platform publishing module may be configured to facilitate transferring publishing information between the virtual space and individual virtual environments provided by the platform server(s). Publishing information may be viewed as information provided by a user that persists within the virtual environment and is viewable and/or otherwise accessible by one or more users. In accordance with some implementations, publishing information associated with a given virtual environment provided by a given platform may include one or more of textual messages, emails, voice-based communications, video-based communications, wall posts, and/or other publishing information. Publishing information associated with a given virtual environment may be used within the virtual environment provided by the space module. Transferring publishing information between the virtual space and a given virtual environment may include interfacing between the virtual space API and the platform API associated with the platform providing the given virtual environment.

These and other features, and characteristics of the present technology, as well as the methods of operation and functions of the related elements of structure and the combination of parts and economies of manufacture, will become more apparent upon consideration of the following description and the appended claims with reference to the accompanying drawings, all of which form a part of this specification, wherein like reference numerals designate corresponding parts in the various figures. It is to be expressly understood, however, that the drawings are for the purpose of illustration and description only and are not intended as a definition of the limits of the invention. As used in the specification and in the claims, the singular form of “a”, “an”, and “the” include plural referents unless the context clearly dictates otherwise.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates a system configured to facilitate presentation of a virtual space within a plurality of virtual environments provided by different platforms without requiring idiosyncratic APIs associated with the virtual space for each different platform, in accordance with one or more implementations.

FIG. 2 illustrates a method of facilitating presentation of a virtual space within a plurality of virtual environments provided by different platforms without requiring idiosyncratic APIs associated with the virtual space for each different platform, in accordance with one or more implementations.

 DETAILED DESCRIPTION

FIG. 1 illustrates a system 100 configured to facilitate presentation of a virtual space within a plurality of virtual environments provided by different platforms without requiring idiosyncratic APIs associated with the virtual space for each different platform, in accordance with one or more implementations. In exemplary implementations, an API adaptor module may be configured to facilitate interfacing between a single virtual space API and platform APIs associated with two or more different platforms. There may be separate API adaptor modules or sub-modules corresponding to individual ones of the different platforms. The API adaptor module may serve as a converter between the virtual space API and various platform APIs such that a single version of the virtual space may be presented in virtual environments provided by any of the different platforms. Thus, a change to the virtual space may not necessitate corresponding changes to a plurality of virtual space APIs. Some implementations may ensure that the virtual space is displayed correctly within different virtual environments. Some implementations may facilitate accessing social graph information associated with individual virtual environments via the virtual space, interacting with platform mechanics of individual virtual environments via the virtual space, and/or transferring publishing information between the virtual space and individual virtual environments.

In some implementations, system 100 may include one or more of one or more platform servers 102 (e.g., platform A server(s) 102a, platform B server(s) 102b, platform C server(s) 102c, and/or other platform servers), one or more space servers 104, and/or other components. The platform server(s) 102 may be configured to communicate with one or more client computing platforms 106 according to a client/server architecture to provide virtual environments to users via client computing platform(s) 106. The space server(s) 104 may be configured to interface with individual platform server(s) 102 to supplement the functionality provided to the users with respect to the virtual environments. For example, space server(s) 104 may interface with individual platform server(s) 102 via one or more APIs.

The space server(s) 104 may be configured to execute one or more computer program modules. The computer program modules may include one or more of an API adaptor module 108, a space module 110, a social graph access module 112, a platform mechanics module 114, a platform publishing module 116, and/or other modules.

The API adaptor module 108 may be configured to facilitate interfacing between a single virtual space API and platform APIs associated with two or more different platforms. Generally speaking, an API may be viewed as a set of routines and/or services used by an application program to direct the performance of procedures by a host environment and/or host computing platform. Interfacing between two APIs (e.g., a virtual space API and a platform API) may include translating commands, calls, functions, and/or other information associated with APIs between the two APIs. The virtual space API may be associated with a virtual space provided by space module 110, as described further herein. The two or more different platforms may correspond to platform server(s) 102. As depicted in FIG. 1, platform A server(s) 102a may be associated with a specific API, for example, platform A API. Similarly, platform B server(s) 102b and platform C server(s) 102c may be respectively associated with platform B API and platform C API. The API adaptor module 108 may be configured to facilitate proper display of the virtual space within virtual environments provided platform server(s) 102.

In some implementations, API adaptor module 108 may includes two or more sub-modules each corresponding to individual platforms. As depicted in FIG. 1, API adaptor module 108 may include platform A API sub-module 108a, platform B API sub-module 108b, platform C API sub-module 108c, and/or other sub-modules. The platform A API sub-module 108a may be configured to facilitate interfacing between a virtual space API and platform A API of platform A server(s) 102a. The platform B API sub-module 108b may be configured to facilitate interfacing between a virtual space API and platform B API of platform B server(s) 102b. The platform C API sub-module 108c may be configured to facilitate interfacing between a virtual space API and platform C API of platform C server(s) 102c.

The space module 110 may be configured to implement at least one instance of the virtual space to determine views of the virtual space. The views may then be communicated (e.g., via streaming, via object/position data, and/or other information) from platform server(s) 102 to client computing platform(s) 106 for presentation to users via two or more virtual environments provided by platform server(s) 102. Facilitating user interactivity with the virtual space via a given virtual environment provided by a given platform may include interfacing between the virtual space API and the platform API associated with the given platform. User interactivity may include accessing social graph information associated with individual virtual environments via the virtual space, interacting with platform mechanics of individual virtual environments via the virtual space, transferring publishing information between the virtual space and individual virtual environments, and/or other interactions by a user with the virtual space.

The view determined and transmitted to a given client computing platform 106 may correspond to a user character being controlled by a user via the given client computing platform 106. The view determined and transmitted to a given client computing platform 106 may correspond to a location in the virtual space (e.g., the location from which the view is taken, the location the view depicts, and/or other locations), a zoom ratio, a dimensionality of objects, a point-of-view, and/or view parameters. One or more of the view parameters may be selectable by the user.

The instance of the virtual space may comprise a simulated space that is accessible by users via clients (e.g., client computing platform(s) 106) that present the views of the virtual space to a user. The simulated space may have a topography, express ongoing real-time interaction by one or more users, and/or include one or more objects positioned within the topography that are capable of locomotion within the topography. In some instances, the topography may be a 2-dimensional topography. In other instances, the topography may be a 3-dimensional topography. The topography may include dimensions of the space, and/or surface features of a surface or objects that are “native” to the space. In some instances, the topography may describe a surface (e.g., a ground surface) that runs through at least a substantial portion of the space. In some instances, the topography may describe a volume with one or more bodies positioned therein (e.g., a simulation of gravity-deprived space with one or more celestial bodies positioned therein). The instance executed by the computer modules may be synchronous, asynchronous, and/or semi-synchronous.

The above description of the manner in which views of the virtual space are determined by space module 110 is not intended to be limiting. The space module 110 may be configured to express the virtual space in a more limited, or more rich, manner. For example, views determined for the virtual space may be selected from a limited set of graphics depicting an event in a given place within the virtual space. The views may include additional content (e.g., text, audio, pre-stored video content, and/or other content) that describes particulars of the current state of the place, beyond the relatively generic graphics. For example, a view may include a generic battle graphic with a textual description of the opponents to be confronted. Other expressions of individual places within the virtual space are contemplated.

Within the instance(s) of the virtual space executed by space module 110, users may control characters, objects, simulated physical phenomena (e.g., wind, rain, earthquakes, and/or other phenomena), and/or other elements within the virtual space to interact with the virtual space and/or each other. The user characters may include avatars. As used herein, the term “user character” may refer to an object (or group of objects) present in the virtual space that represents an individual user. The user character may be controlled by the user with which it is associated. The user controlled element(s) may move through and interact with the virtual space (e.g., non-user characters in the virtual space, other objects in the virtual space). The user controlled elements controlled by and/or associated with a given user may be created and/or customized by the given user. The user may have an “inventory” of virtual goods and/or currency that the user can use (e.g., by manipulation of a user character or other user controlled element, and/or other items) within the virtual space.

The users may participate in the instance of the virtual space by controlling one or more of the available user controlled elements in the virtual space. Control may be exercised through control inputs and/or commands input by the users through client computing platform(s) 106. The users may interact with each other through communications exchanged within the virtual space. Such communications may include one or more of textual chat, instant messages, private messages, voice communications, and/or other communications. Communications may be received and entered by the users via their respective client computing platform(s) 106. Communications may be routed to and from the appropriate users through space server(s) 104 (e.g., through space module 110) and/or individual ones of platform server(s) 102.

The social graph access module 112 may be configured to facilitate accessing social graph information associated with individual virtual environments provided by platform server(s) 102. The social graph information may be accessed via the virtual space provided by space module 110. Generally speaking, a social graph may be viewed as a mapping of relationships (e.g., personal, professional, familial, and/or other relationships) between users associated directly and/or indirectly with a given virtual environment. According to some implementations, social graph information associated with a given virtual environment may include one or more of friends, contacts, relationship type, relationship duration, relationships in common, and/or other information included in a social graph of the given virtual environment. Social graph information associated with a given virtual environment may be used within the virtual environment provided by space module 110. Accessing social graph information associated with a given virtual environment may include interfacing between the virtual space API and the platform API associated with the platform providing the given virtual environment.

The platform mechanics module 114 may be configured to facilitate interacting with platform mechanics associated with individual virtual environments provided by platform server(s) 102. The platform mechanics may be interacted with via the virtual space provided by space module 110. Platform mechanics may be viewed generally as constructs of rules and/or functions of a virtual environment. In some implementations, platform mechanics associated with a given virtual environment may include one or more of invitations, requests, alerts, gifts, events, and/or other mechanics of the given virtual environment. Platform mechanics associated with a given virtual environment may be used within the virtual environment provided by space module 110. Interacting with platform mechanics associated with a given virtual environment may include interfacing between the virtual space API and the platform API associated with the platform providing the given virtual environment.

The platform publishing module 116 may be configured to facilitate transferring publishing information between the virtual space and individual virtual environments provided by platform server(s) 102. Publishing information may be viewed as information provided by a user that persists within the virtual environment and is viewable and/or otherwise accessible by one or more users. In accordance with some implementations, publishing information associated with a given virtual environment provided by a given platform may include one or more of textual messages, emails, voice-based communications, video-based communications, wall posts, and/or other publishing information. Publishing information associated with a given virtual environment may be used within the virtual environment provided by space module 110. Transferring publishing information between the virtual space and a given virtual environment may include interfacing between the virtual space API and the platform API associated with the platform providing the given virtual environment.

In some implementations, individual platform server(s) 102 may comprise electronic storage, one or more processors, and/or other components. For example, platform server(s) 102 may include communication lines, or ports to enable the exchange of information with a network and/or other computing platforms. The processors may be configured to execute computer program modules to provide one or more virtual environments to users via client computing platform(s) 106. The processors may be configured to execute the computer program modules via one or more of hardware, software, and/or firmware. Although system 100 may be described in certain sections herein as including platform server(s) 102, this is not intended to be limiting. The platform server(s) 102 may be separate and distinct from system 100, and may be provided by an entity that is separate from, for example, the entity providing space server(s) 104. In some implementations, some or all of the functionality attributed herein to platform server(s) 102 may be provided by space server(s) 104.

As used herein, a “virtual environment” may include a virtual space, one or more interactive, electronic social media, and/or other virtual environments. Exemplary virtual spaces are described herein. Interactive, electronic social media may include one or more of a social network, a virtual space, a micro-blogging service, a blog service (or host), a browser-based game, a multi-player mobile game, a file (e.g., image file, video file, and/or other files) sharing service, a messaging service, a message board, a forum, and/or other electronically distributed media that are scalable and enable interaction between the users. Some non-limiting specific examples of interactive, electronic social media may include the micro-blogging service provided by Twitter™, the social network provided by Facebook™, the social network provided by Google+™, the social network provided by MySpace™, the social network provided by Foursquare®, the virtual world provided by SecondLife®, the massively multi-player online game provided by World of Warcraft®, the file sharing service provided by Flickr®, Blogger, YouTube, PlayStation® Home, Xbox® Live, and/or other interactive electronic social media.

A given client computing platform 106 may include one or more processors configured to execute computer program modules. The computer program modules may be configured to enable an expert or user associated with the given client computing platform 106 to interface with system 100 and/or external resources 118, and/or provide other functionality attributed herein to client computing platform(s) 106. By way of non-limiting example, the given client computing platform 106 may include one or more of a desktop computer, a laptop computer, a handheld computer, a NetBook, a Smartphone, a gaming console, and/or other computing platforms.

The external resources 118 may include sources of information, hosts and/or providers of virtual environments outside of system 100, external entities participating with system 100, and/or other resources. In some implementations, some or all of the functionality attributed herein to external resources 118 may be provided by resources included in system 100.

The space server(s) 104 may include electronic storage 120, one or more processors 122, and/or other components. The space server(s) 104 may include communication lines, or ports to enable the exchange of information with a network and/or other computing platforms. Illustration of space server(s) 104 in FIG. 1 is not intended to be limiting. The space server(s) 104 may include a plurality of hardware, software, and/or firmware components operating together to provide the functionality attributed herein to space server(s) 104. For example, space server(s) 104 may be implemented by a cloud of computing platforms operating together as space server(s) 104.

Electronic storage 120 may comprise electronic storage media that electronically stores information. The electronic storage media of electronic storage 120 may include one or both of system storage that is provided integrally (i.e., substantially non-removable) with space server(s) 104 and/or removable storage that is removably connectable to space server(s) 104 via, for example, a port (e.g., a USB port, a firewire port, etc.) or a drive (e.g., a disk drive, etc.). Electronic storage 120 may include one or more of optically readable storage media (e.g., optical disks, etc.), magnetically readable storage media (e.g., magnetic tape, magnetic hard drive, floppy drive, etc.), electrical charge-based storage media (e.g., EEPROM, RAM, etc.), solid-state storage media (e.g., flash drive, etc.), and/or other electronically readable storage media. The electronic storage 120 may include one or more virtual storage resources (e.g., cloud storage, a virtual private network, and/or other virtual storage resources). Electronic storage 120 may store software algorithms, information determined by processor(s) 122, information received from platform server(s) 102, information received from client computing platform(s) 106, and/or other information that enables space server(s) 104 to function as described herein.

Processor(s) 122 is configured to provide information processing capabilities in space server(s) 104. As such, processor(s) 122 may include one or more of a digital processor, an analog processor, a digital circuit designed to process information, an analog circuit designed to process information, a state machine, and/or other mechanisms for electronically processing information. Although processor(s) 122 is shown in FIG. 1 as a single entity, this is for illustrative purposes only. In some implementations, processor(s) 122 may include a plurality of processing units. These processing units may be physically located within the same device, or processor(s) 122 may represent processing functionality of a plurality of devices operating in coordination. The processor(s) 122 may be configured to execute modules 108, 110, 112, 114, 116, and/or other modules. The processor(s) 122 may be configured to execute modules 108, 110, 112, 114, and/or 116 by software; hardware; firmware; some combination of software, hardware, and/or firmware; and/or other mechanisms for configuring processing capabilities on processor(s) 122.

It should be appreciated that although modules 108, 110, 112, 114, and 116 are illustrated in FIG. 1 as being co-located within a single processing unit, in implementations in which processor(s) 122 includes multiple processing units, one or more of modules 108, 110, 112, 114, and/or 116 may be located remotely from the other modules. The description of the functionality provided by the different modules 108, 110, 112, 114, and/or 116 described herein is for illustrative purposes, and is not intended to be limiting, as any of modules 108, 110, 112, 114, and/or 116 may provide more or less functionality than is described. For example, one or more of modules 108, 110, 112, 114, and/or 116 may be eliminated, and some or all of its functionality may be provided by other ones of modules 108, 110, 112, 114, and/or 116. As another example, processor(s) 122 may be configured to execute one or more additional modules that may perform some or all of the functionality attributed below to one or more of modules 108, 110, 112, 114, and/or 116.

FIG. 2 illustrates a method 200 of facilitating presentation of a virtual space within a plurality of virtual environments provided by different platforms without requiring idiosyncratic APIs associated with the virtual space for each different platform, in accordance with one or more implementations. The operations of method 200 presented below are intended to be illustrative. In some implementations, method 200 may be accomplished with one or more additional operations not described, and/or without one or more of the operations discussed. Additionally, the order in which the operations of method 200 are illustrated in FIG. 2 and described below is not intended to be limiting.

In some implementations, method 200 may be implemented in one or more processing devices (e.g., a digital processor, an analog processor, a digital circuit designed to process information, an analog circuit designed to process information, a state machine, and/or other mechanisms for electronically processing information). The one or more processing devices may include one or more devices executing some or all of the operations of method 200 in response to instructions stored electronically on an electronic storage medium. The one or more processing devices may include one or more devices configured through hardware, firmware, and/or software to be specifically designed for execution of one or more of the operations of method 200.

At an operation 202, interfacing may be facilitated between a single virtual space API and platform APIs associated with two or more different platforms. Operation 202 may be performed by an API adaptor module that is the same as or similar to API adaptor module 108, in accordance with one or more implementations.

At an operation 204, an instance of a virtual space may be executed. Operation 204 may be performed by a space module that is the same as or similar to space module 110, in accordance with one or more implementations.

At an operation 206, the instance of the virtual space may be implemented to determine view information defining views of the instance of the virtual space for presentation via two or more virtual environments provided by the two or more platforms. Facilitating user interactions with the virtual space via a given virtual environment provided by a given platform may include interfacing between the virtual space API and the platform API associated with the given platform. Operation 206 may be performed by a space module that is the same as or similar to space module 110, in accordance with one or more implementations.

At an operation 208, accessing, via the virtual space, social graph information associated with individual virtual environments provided by the two or more platforms may be facilitated. Accessing social graph information associated with a given virtual environment may include interfacing between the virtual space API and the platform API associated with the platform providing the given virtual environment. Operation 208 may be performed by a social graph access module that is the same as or similar to social graph access module 112, in accordance with one or more implementations.

At an operation 210, interacting, via the virtual space, with platform mechanics associated with individual virtual environments provided by the two or more platforms may be facilitated. Interacting with platform mechanics associated with a given virtual environment may include interfacing between the virtual space API and the platform API associated with the platform providing the given virtual environment. Operation 210 may be performed by a platform mechanics module that is the same as or similar to platform mechanics module 114, in accordance with one or more implementations.

At an operation 212, transferring publishing information may be facilitated between the virtual space and individual virtual environments provided by the two or more platforms. Transferring publishing information between the virtual space and a given virtual environment may include interfacing between the virtual space API and the platform API associated with the platform providing the given virtual environment. Operation 212 may be performed by a platform publishing module that is the same as or similar to platform publishing module 116, in accordance with one or more implementations.

Although the present technology has been described in detail for the purpose of illustration based on what is currently considered to be the most practical and preferred implementations, it is to be understood that such detail is solely for that purpose and that the technology is not limited to the disclosed implementations, but, on the contrary, is intended to cover modifications and equivalent arrangements that are within the spirit and scope of the appended claims. For example, it is to be understood that the present technology contemplates that, to the extent possible, one or more features of any implementation can be combined with one or more features of any other implementation.

Claims

1. A system configured to facilitate presentation of an online game within a plurality of virtual environments provided by different platforms without requiring idiosyncratic APIs associated with the online game for each different platform, the system comprising:

one or more processors configured by machine-readable instructions to facilitate interfacing between a single online game API and platform APIs; and execute an instance of the online game, and to implement the instance of the online game to determine state information of the instance of the online game that describes the state of the online game, such state information being output through the single online game API, wherein facilitating user interactivity with the online game via a virtual environment provided by the platform by translating the state information output from the online game API specific to the platform, facilitating the presentation of views of the online game that reflect the state information within the virtual environment.

2. The system of claim 1, wherein the one or more processors are configured by machine-readable instructions to facilitate proper display of the online game within virtual environments provided by the platform.

3. The system of claim 1, wherein the one or more processors are configured by machine-readable instructions to facilitate interfacing between the online game API and a first platform API, and facilitate interfacing between the online game API and a second platform API.

4. The system of claim 1, wherein the one or more processors are configured by machine-readable instructions to facilitate accessing, via the online game, social graph information associated with individual virtual environments provided by the two or more platforms, wherein accessing social graph information associated with the virtual environment includes interfacing between the online game API and the platform API.

5. The system of claim 4, wherein social graph information associated with a given virtual environment includes one or more of friends, contacts, relationship type, relationship duration, or relationships in common.

6. The system of claim 1, wherein the one or more processors are configured by machine-readable instructions to facilitate interacting, via the online game, with platform mechanics associated with individual virtual environments provided by the platform, wherein interacting with platform mechanics associated with the virtual environment includes interfacing between the online game API and the platform API.

7. The system of claim 6, wherein platform mechanics associated with a given virtual environment provided by a given platform include one or more of invitations, requests, alerts, gifts, or events.

8. The system of claim 1, wherein the one or more processors are configured by machine-readable instructions to facilitate transferring publishing information between the online game and individual virtual environments provided by the platform, wherein transferring publishing information between the online game and the virtual environment includes interfacing between the online game API and the platform API.

9. The system of claim 8, wherein publishing information associated with a given virtual environment provided by a given platform includes one or more of textual messages, emails, voice-based communications, video-based communications, or wall posts.

10. A computer-implemented method of facilitating presentation of an online game within a plurality of virtual environments provided by different platforms without requiring idiosyncratic APIs associated with the online game for each different platform, the method being implemented in a computer system comprising one or more processors configured to execute computer program modules, the method comprising:

facilitating interfacing between a single online game API and platform APIs; and
implementing the instance of the online game to determine state information of the instance of the online game that describes the state of the online game, such state information being output through the single online game API,
wherein facilitating user activity with the online game via a first virtual environment provided by the first platform includes interfacing between the online game API and the first platform API, by translating state information output from the online game API specific to the platform, facilitating presentation of views of the online game that reflect the state information within the virtual environment.

11. The method of claim 10, further comprising facilitating proper display of the online game within virtual environments provided by the platform.

12. The method of claim 10, wherein facilitating interfacing between the online game API and the platform API includes:

facilitating interfacing between the online game API and a first platform API; and
facilitating interfacing between the online game API and a second platform API.

13. The method of claim 10, further comprising facilitating accessing, via the online game, social graph information associated with individual virtual environments provided by the platform, wherein accessing social graph information associated with the first virtual environment includes interfacing between the online game API and the platform API.

14. The method of claim 13, wherein social graph information associated with a given virtual environment includes one or more of friends, contacts, relationship type, relationship duration, or relationships in common.

15. The method of claim 10, further comprising facilitating interacting, via the online game, with platform mechanics associated with individual virtual environments provided by the platform, wherein interacting with platform mechanics associated with the first virtual environment includes interfacing between the online game API and the platform API.

16. The method of claim 15, wherein platform mechanics associated with a given virtual environment provided by a given platform include one or more of invitations, requests, alerts, gifts, or events.

17. The method of claim 10, further comprising facilitating transferring publishing information between the online game and individual virtual environments provided by the platform, wherein transferring publishing information between the online game and the virtual environment includes interfacing between the online game API and the platform API.

18. The method of claim 17, wherein publishing information associated with a given virtual environment provided by a given platform includes one or more of textual messages, emails, voice-based communications, video-based communications, or wall posts.

Referenced Cited
U.S. Patent Documents
6951516 October 4, 2005 Eguchi
7056217 June 6, 2006 Pelkey
7522058 April 21, 2009 Light
7707122 April 27, 2010 Hull
7780530 August 24, 2010 Ushiro
7856471 December 21, 2010 Pounds
7970712 June 28, 2011 Ruvolo
8137193 March 20, 2012 Kelly
8137194 March 20, 2012 Kelly
8214487 July 3, 2012 Savoor
8257174 September 4, 2012 Pincus
8332488 December 11, 2012 Dale
8347225 January 1, 2013 Blinnikka
8347322 January 1, 2013 Brown
8353760 January 15, 2013 Ocko
8622828 January 7, 2014 Harrington
8663004 March 4, 2014 Xu
8734243 May 27, 2014 Harrington
8843557 September 23, 2014 Ranade
8868655 October 21, 2014 Ranade
8881181 November 4, 2014 Harrington
8984541 March 17, 2015 Brown
8986116 March 24, 2015 Harrington
9011242 April 21, 2015 Xu
9116732 August 25, 2015 Harrington
9223599 December 29, 2015 Racanelli
20030078960 April 24, 2003 Murren
20030177187 September 18, 2003 Levine
20040117386 June 17, 2004 Lavender
20050245317 November 3, 2005 Arthur
20050272504 December 8, 2005 Eguchi
20060121986 June 8, 2006 Pelkey
20060287099 December 21, 2006 Shaw
20070150603 June 28, 2007 Crull
20070173324 July 26, 2007 Multerer
20070233736 October 4, 2007 Xiong
20070274460 November 29, 2007 Shaffer
20080119277 May 22, 2008 Thelen
20080134035 June 5, 2008 Pennington
20080187143 August 7, 2008 Mak-Fan
20090034696 February 5, 2009 Ramanathan
20090112989 April 30, 2009 Anderson
20090144075 June 4, 2009 Flinn
20090172795 July 2, 2009 Ritari
20090197681 August 6, 2009 Krishnamoorthy
20090197881 August 6, 2009 Kugimiya
20090199275 August 6, 2009 Brock
20090292814 November 26, 2009 Ting
20090325712 December 31, 2009 Rance
20090327232 December 31, 2009 Carter
20090327427 December 31, 2009 Mathew
20090327882 December 31, 2009 Velusamy
20100024015 January 28, 2010 Hardt
20100063969 March 11, 2010 Kasargod
20100106782 April 29, 2010 Huang
20100146118 June 10, 2010 Wie
20100169798 July 1, 2010 Hyndman
20100197409 August 5, 2010 Van Luchene
20100216553 August 26, 2010 Chudley
20100228617 September 9, 2010 Ransom
20100229106 September 9, 2010 Lee
20100235754 September 16, 2010 Leitheiser
20100274815 October 28, 2010 Vanasco
20100304862 December 2, 2010 Coleman
20100312820 December 9, 2010 Goffinet
20110014972 January 20, 2011 Herrmann
20110016488 January 20, 2011 Athias
20110022450 January 27, 2011 Meredith
20110023101 January 27, 2011 Vernal
20110107239 May 5, 2011 Adoni
20110131508 June 2, 2011 Gershfang
20110151976 June 23, 2011 Holloway
20110179161 July 21, 2011 Guy
20110202605 August 18, 2011 Shochet
20110212783 September 1, 2011 Dale
20110224000 September 15, 2011 Toga
20110237335 September 29, 2011 Holloway
20110238608 September 29, 2011 Sathish
20110250949 October 13, 2011 Van Os
20110251970 October 13, 2011 Oien
20110269548 November 3, 2011 Barclay
20110295626 December 1, 2011 Chen
20120047008 February 23, 2012 Alhadeff
20120054646 March 1, 2012 Hoomani
20120060103 March 8, 2012 Arasaki
20120077523 March 29, 2012 Roumeliotis
20120094766 April 19, 2012 Reynolds
20120124147 May 17, 2012 Hamlin
20120142429 June 7, 2012 Muller
20120202587 August 9, 2012 Allen
20120227086 September 6, 2012 Dale
20120227087 September 6, 2012 Brown
20120244948 September 27, 2012 Dhillon
20120252579 October 4, 2012 Sethi
20120254903 October 4, 2012 Brown
20120290949 November 15, 2012 Elenzil
20120290950 November 15, 2012 Rapaport
20120324001 December 20, 2012 Leacock
20130005476 January 3, 2013 Keswani
20130006736 January 3, 2013 Bethke
20130014033 January 10, 2013 Hamick
20130031171 January 31, 2013 Serena
20130073400 March 21, 2013 Heath
20130090170 April 11, 2013 Reed
20130091204 April 11, 2013 Loh
20130091221 April 11, 2013 Bennett
20130143669 June 6, 2013 Muller
20130151603 June 13, 2013 Lobb
20130151604 June 13, 2013 Ranade
20130159430 June 20, 2013 Ranade
20130165234 June 27, 2013 Hall
20130172085 July 4, 2013 Harrington
20130198275 August 1, 2013 Forsblom
20130212191 August 15, 2013 Suraj
20130282828 October 24, 2013 Lawler
20130326368 December 5, 2013 Voas
20130332825 December 12, 2013 Singh
20140179434 June 26, 2014 Xu
20140187333 July 3, 2014 Craine
Foreign Patent Documents
2383683 November 2011 EP
2008144412 January 2008 WO
2010025343 January 2010 WO
2013086268 June 2013 WO
2013086268 June 2013 WO
2013096261 June 2013 WO
2013096261 June 2013 WO
2013103655 July 2013 WO
2013103655 July 2013 WO
Other references
  • “Buddy Rush:: The World's Best Cross-platform RPG!”, http://buddyrush.sollmo.com/, printed Nov. 28, 2011, copyright 2011 by Team Sollmo with Company 11, Inc., 2 pages.
  • “FriendFeed”, definition from Wikipedia, the free encyclopedia, printed Nov. 28, 2011, 3 pages.
  • Hendrickson, Mark, “Watch Out FriendFeed: Socialthing! Is Even Easier to Use”, http://techcrunch.com/2008/03/10/watch-out-friendfeed-socialthing-is-even-easier-to-use/, posted Mar. 10, 2008, 4 pages.
  • Johnston, Ken. VSCpr for GREE, Inc. “GREE Gaming Platform Provides Global User Base for All Developers. New Platform Offers Unified Social Gaming System” Burlingame, CA, PRWeb, Dec. 5, 2011, 2 pages.
  • Webster, Andrew, “Social games need to become truly cross-platform”, http://www.gamezebo.com/news/2011/06/08/social-games-need-become-truly-cross-platform, posted Jun. 8, 2011, printed Nov. 28, 2011, 2 pages.
Patent History
Patent number: 9596277
Type: Grant
Filed: Jul 30, 2015
Date of Patent: Mar 14, 2017
Assignee: Kabam, Inc. (San Francisco, CA)
Inventor: Clifford J. Harrington (San Francisco, CA)
Primary Examiner: Timothy A Mudrick
Application Number: 14/814,375
Classifications
Current U.S. Class: Application Program Interface (api) (719/328)
International Classification: G06F 3/00 (20060101); G06F 9/44 (20060101); G06F 9/46 (20060101); G06F 13/00 (20060101); H04L 29/06 (20060101); G06F 17/30 (20060101); H04L 12/58 (20060101);