Snap Patent | Location-based shared augmented reality experience system
Patent: Location-based shared augmented reality experience system
Patent PDF: 20240281192
Publication Number: 20240281192
Publication Date: 2024-08-22
Assignee: Snap Inc
Abstract
A location-based shared augmented reality (AR) experience system is configured to permit users that find themselves in the same geographic area to easily join in a shared AR experience by creating respective instances of the shared AR experience for different previously defined geographic areas. When a user indicates a request to launch a shared AR experience accessible via a messaging client, the location-based shared AR experience system obtains or receives from the user device executing the messaging client location information of the user device, determines a previously-defined AR experience area that encompasses the location of the user device, and communicates to the user device an address of an associated instance of the shared AR experience.
Claims
What is claimed is:
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.
15.
16.
17.
18.
19.
20.
Description
CLAIM OF PRIORITY
This application is a continuation of U.S. patent application Ser. No. 17/725,319, filed Apr. 20, 2022, which is incorporated herein by reference in its entirety.
TECHNICAL FIELD
The present disclosure relates generally to facilitating interactions between client devices over a network.
BACKGROUND
As the popularity of computer-implemented tools that permit users to access and interact with content and other users online continues to grow, various computer-implemented tools are being developed to permit users to interact and share content with other users through messaging applications. For example, a messaging system may host a backend service for an associated messaging client that is configured to permit users to interact asynchronously via messages and, also, synchronously via audio and video interactions. A messaging system may permit users to engage in video games that provide users an opportunity to interact without having to meet in the same place at the same time. Some existing video games use a real world map as a gaming platform and may include a virtual object that appears as overlaid over a representation of the real world. Some existing applications require explicit pairing of the devices in order for these devices to be used in a shared experience.
BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS
In the drawings, which are not necessarily drawn to scale, like numerals may describe similar components in different views. To easily identify the discussion of any particular element or act, the most significant digit or digits in a reference number refer to the figure number in which that element is first introduced. Some examples are illustrated by way of example, and not limitation, in the figures of the accompanying drawings in which:
FIG. 1 is a diagrammatic representation of a networked environment in which a location-based shared augmented reality (AR) experience system may be deployed, in accordance with some examples.
FIG. 2 is a diagrammatic representation of a messaging system, in accordance with some examples, that has both client-side and server-side functionality, and that includes a location-based shared AR experience system.
FIG. 3 is a diagrammatic representation of a data structure as maintained in a database, in accordance with some examples.
FIG. 4 is a flowchart of a method for enhancing experience of users engaging with a shared AR experience, in accordance with some examples.
FIG. 5 is a diagram of an activity user interface, in accordance with some examples.
FIG. 6 is a diagram of a general scheme of communication between various components of a location-based shared AR experience system, in accordance with some examples.
FIG. 7 is a diagram 500 illustrating the concept of geographical sharding, in accordance with some examples.
FIG. 8 is a diagrammatic representation of a machine in the form of a computer system within which a set of instructions may be executed for causing the machine to perform any one or more of the methodologies discussed herein, in accordance with some examples.
DETAILED DESCRIPTION
Embodiments of the present disclosure improve the functionality of electronic messaging software and systems by enhancing the experience of users interacting with each other through their respective user devices.
Augmented reality (AR) is an environment in which the real world, as viewed through a camera lens, for example, is augmented by overlaying virtual content over the view of the real world presented on the display of a user device. AR may be used in video games, in which the real world is used as an activity user interface (UI) on which the game is taking place, referred to a game level. In a game that uses the real world as an activity UI, the activity UI includes the output of the digital image sensor of the camera of the device used for playing the game, such as AR glasses or a smartphone.
A computing application configured to permit two or more users to interact by manipulating and/or viewing a virtual object in the real world is referred to as a shared AR experience, for the purposes of this description. A shared AR experience is associated with at least one virtual object. The users participating in a shared AR experience session are interacting in the real world, in that they are located in substantially the same geographic area such that they can see the same real-world objects around them, even if from different angles. The users participating in a shared AR experience session are also able to manipulate the virtual object provided by the shared AR experience by interacting with the activity UI. The activity UI presents the virtual object as overlayed over the output of the digital image sensor of the camera of their respective user devices. For example, participants of a shared AR experience can see a virtual object provided by the shared AR experience displayed as located in front of a real-world object on the camera screens of the participants' respective user devices. For example, the participants can see a virtual object, such as an animal, a robot, a dragon or other magical creature, displayed in front of a real-world object, such as a structure or tree. User devices operated by users to engage in a session of the same shared AR experience are referred to as participating devices, for the purposes of this description. The technical problem of permitting users to join in a session of a shared AR experience without requiring the users explicitly connect with each other for the purpose of participating in the shared AR experience and without pairing of the user devices, is addressed by configuring a messaging system to include a location-based shared AR experience system described herein. The location-based shared AR experience system is configured to permit users that find themselves in the same geographic area to easily join in a shared AR experience, by creating respective sessions, also referred as instances, of the shared AR experience for different previously defined geographic areas. These previously defined geographic areas are referred to as AR experience areas for the purposes of this description. In one example, an AR experience area is defined by at least three latitude/longitude pairs in the global coordinate system.
An AR experience area defines a geographic location within which one or more virtual objects provided by a given AR experience can be viewed and/or manipulated by more than one participating user in a consistent manner with respect to one or more anchor objects that correspond to real-world objects that exists in that geographic location. An anchor object for a shared AR instance is determined based information derived from the output of a digital image sensor of a camera of a participating device. Because an anchor object corresponds to a real-world object that exists in the geographic location corresponding to the AR experience area of the instance of the given shared AR experience and that can be seen on a device that displays the output of the digital image sensor of the camera of the associated participating device, the virtual object is displayed on the activity UI of every participant consistently relative to the anchor object. In some examples, the location-based shared AR experience system is configured to scan a selected region in the output of the digital image sensor of the camera, which may alleviate the need for storing high-volume of the anchor objects data. In a newly created shared AR instance, the current location of the user device determines the scanned region. For a new user who is within the range of the shared ARF instance, but outside of the visually scanned region, the location-based shared AR experience system is configured to guide the user on how to get into the previously scanned region.
In one example, a user indicates a request to launch a shared AR experience, such as a location-based multi-participant game, for example, that is accessible via a messaging client. Upon receiving the indication of the request, the location-based shared AR experience system obtains or receives from the user device executing the messaging client the global positioning service (GPS) information of the user device, determines an AR experience area that encompasses the location indicated by the GPS information, and communicates to the user device an address identifying the user device as a participant with respect to an instance of the shared AR experience. The address can be derived from the GPS information of the user device. If there is no existing instance of the shared AR experience associated with the AR experience area that encompasses the geographic location of the user device, the messaging system creates a new instance of the shared AR experience. In this case the user is the first participant of the newly-created instance of the shared AR experience in the geographic location represented by the AR experience area. In some examples, the methodology described herein can be used beneficially to implement a shared AR experience at a planet scale by combining geographical sharding based on GPS positioning and shared AR techniques.
Details of the messaging system configured to include a location-based shared AR experience system are described below.
Networked Computing Environment
FIG. 1 is a block diagram 100 showing an example messaging system for exchanging data (e.g., messages and associated content) over a network. The messaging system includes multiple instances of a messaging client 104 executing at respective client devices such as a client device 102 and a messaging server system 108. Each messaging client 104 is communicatively coupled to other instances of the messaging client 104 and a messaging server system 108 via a network 106 (e.g., the Internet). The client device 102 is a computing device that is able to display AR content, has access to a global position provider (e.g., GPS or other network location provider) and has a network connection, such as cellular or Internet connection. Some examples of a client device 102 include a smartphone, AR glasses or another type of wearable device, and the like.
A messaging client 104 is able to communicate and exchange data with another messaging client 104 and with the messaging server system 108 via the network 106. The data exchanged between messaging client 104, and between a messaging client 104 and the messaging server system 108, includes functions (e.g., commands to invoke functions) as well as payload data (e.g., text, audio, video or other multimedia data).
The messaging server system 108 provides server-side functionality via the network 106 to a particular messaging client 104. While certain functions of the messaging system are described herein as being performed by either a messaging client 104 or by the messaging server system 108, the location of certain functionality either within the messaging client 104 or the messaging server system 108 may be a design choice. For example, it may be technically preferable to initially deploy certain technology and functionality within the messaging server system 108 but to later migrate this technology and functionality to the messaging client 104 where a client device 102 has sufficient processing capacity.
The messaging server system 108 supports various services and operations that are provided to the messaging client 104. Such operations include transmitting data to, receiving data from, and processing data generated by the messaging client 104. This data may include, as examples, message content, client device information, geolocation information, media augmentation and overlays, message content persistence conditions, social network information, live event information, as well as images and video captured with a front facing camera of an associated client device using customized image reprocessing. Data exchanges within the messaging system are invoked and controlled through functions available via user interfaces (UIs) of the messaging client 104.
Turning now specifically to the messaging server system 108, an Application Program Interface (API) server 110 is coupled to, and provides a programmatic interface to, application servers 112. The application servers 112 are communicatively coupled to a database server 118, which facilitates access to a database 120 that stores data associated with messages processed by the application servers 112. Similarly, a web server 124 is coupled to the application servers 112, and provides web-based interfaces to the application servers 112. To this end, the web server 124 processes incoming network requests over the Hypertext Transfer Protocol (HTTP) and several other related protocols. The web server 124, in some examples, hosts a clustering service that, in the context of facilitating access to shared AR experiences to users, provides to user devices addresses identifying the user devices as participants with respect to an instance of the shared AR experience.
The Application Program Interface (API) server 110 receives and transmits message data (e.g., commands and message payloads) between the client device 102 and the application servers 112. Specifically, the Application Program Interface (API) server 110 provides a set of interfaces (e.g., routines and protocols) that can be called or queried by the messaging client 104 in order to invoke functionality of the application servers 112. The Application Program Interface (API) server 110 exposes various functions supported by the application servers 112, including account registration, login functionality, the sending of messages, via the application servers 112, from a particular messaging client 104 to another messaging client 104, the sending of media files (e.g., images or video) from a messaging client 104 to a messaging server 114, and for possible access by another messaging client 104, the settings of a collection of media data (e.g., story), the retrieval of a list of friends of a user of a client device 102, the retrieval of such collections, the retrieval of messages and content, the addition and deletion of entities (e.g., friends) to an entity graph (e.g., a social graph), the location of friends within a social graph, and opening an application event (e.g., relating to the messaging client 104).
The application servers 112 host a number of server applications and subsystems, including for example a messaging server 114, an image processing server 116, and a social network server 122. The messaging server 114 implements a number of message processing technologies and functions, particularly related to the aggregation and other processing of content (e.g., textual and multimedia content) included in messages received from multiple instances of the messaging client 104. As will be described in further detail, the text and media content from multiple sources may be aggregated into collections of content (e.g., called stories or galleries). These collections are then made available to the messaging client 104. Other processor and memory intensive processing of data may also be performed server-side by the messaging server 114, in view of the hardware requirements for such processing.
The application servers 112 also include an image processing server 116 that is dedicated to performing various image processing operations, typically with respect to images or video within the payload of a message sent from or received at the messaging server 114. Some of the various image processing operations may be performed by various AR components, collectively referred to as an AR engine, which can be hosted or supported by the image processing server 116. An AR engine, in some examples, is used to facilitate the functionality provided by the location-based shared AR experience system, which is described herein.
The social network server 122 supports various social networking functions and services and makes these functions and services available to the messaging server 114. To this end, the social network server 122 maintains and accesses an entity graph 306 (as shown in FIG. 3) within the database 120. Examples of functions and services supported by the social network server 122 include the identification of other users of the messaging system with which a particular user has a “friend” relationship or is “following,” and also the identification of other entities and interests of a particular user.
The game server 126, in some examples, is configured as the authoritative source of user actions and the effects of user actions in a multiplayer game. The user action and effects of user actions are also referred to herein as events. The game server 126 being the authoritative source of events in a multiplayer game means that each user device engaged in the same multiplayer game maintains a version of the state of the game. The version of the state of the game for maintained by each user device is consistent with the respective versions of the state of the game available to other users via their respective user devices. In some examples, a multi-player game is a shared AR experience. As mentioned above, users participating in a shared AR experience session are interacting in the real world, in that they are located in substantially the same geographic area such that they can see the same real-world objects around them, even if from different angle, while also being able to manipulate the virtual object provided by the shared AR experience by interacting with the activity UI of the shared UI experience.
System Architecture
FIG. 2 is a block diagram illustrating further details regarding the messaging system, according to some examples. Specifically, the messaging system is shown to comprise the messaging client 104 and the application servers 112. The messaging system embodies a number of subsystems, which are supported on the client-side by the messaging client 104, and on the sever-side by the application servers 112. These subsystems include, for example a location-based shared AR experience system 202, an augmentation system 206, a map system 210, and a game system 212.
The location-based shared AR experience system 202 is configured to detect a request to launch a location-based shared AR experience at a client device and, in response, generate a location-based shared AR experience user interface. As mentioned above, the location-based shared AR experience UI includes a video feed area to display an output of a digital image sensor of a camera of the client device 102. The location-based shared AR experience system 202 causes display of the location-based shared AR experience UI at the client device 102.
The augmentation system 206 provides various functions that enable a user to augment (e.g., annotate or otherwise modify or edit) media content, which may be associated with a message. For example, the augmentation system 206 provides functions related to the generation and publishing of media overlays for messages processed by the messaging system. The media overlays may be stored in the database 120 and accessed through the database server 118.
In some examples, the augmentation system 206 is configured to provide access to AR components that can be implemented using a programming language suitable for application development, such as, e.g., JavaScript or Java and that are identified in the messaging server system by respective AR component identifiers. An AR component may include or reference various image processing operations corresponding to an image modification, filter, media overlay, transformation, and the like. These image processing operations can provide an interactive experience of a real-world environment, where objects, surfaces, backgrounds, lighting etc., captured by a digital image sensor or a camera, are enhanced by computer-generated perceptual information. In this context an AR component comprises the collection of data, parameters, and other assets needed to apply a selected augmented reality experience to an image or a video feed.
In some embodiments, an AR component includes modules configured to modify or transform image data presented within a graphical user interface (GUI) of a client device in some way. For example, complex additions or transformations to the content images may be performed using AR component data, such as adding rabbit ears to the head of a person in a video clip, adding floating hearts with background coloring to a video clip, altering the proportions of a person's features within a video clip, or many numerous other such transformations. This includes both real-time modifications that modify an image as it is captured using a camera associated with a client device and then displayed on a screen of the client device with the AR component modifications, as well as modifications to stored content, such as video clips in a gallery that may be modified using AR components.
Various augmented reality functionality that may be provided by an AR component include detection of objects (e.g. faces, hands, bodies, cats, dogs, surfaces, objects, etc.), tracking of such objects as they leave, enter, and move around the field of view in video frames, and the modification or transformation of such objects as they are tracked. In various embodiments, different methods for achieving such transformations may be used. For example, some embodiments may involve generating a 3D mesh model of the object or objects, and using transformations and animated textures of the model within the video to achieve the transformation. In other embodiments, tracking of points on an object may be used to place an image or texture, which may be two dimensional or three dimensional, at the tracked position. In still further embodiments, neural network analysis of video frames may be used to place images, models, or textures in content (e.g. images or frames of video). AR component data thus refers to both to the images, models, and textures used to create transformations in content, as well as to additional modeling and analysis information needed to achieve such transformations with object detection, tracking, and placement. In some embodiments, the augmentation system 206 is used by the location-based shared AR experience system 202 as an AR engine to generate and track one or more virtual objects provided by a shared AR experience.
The map system 210 provides various geographic location functions, and supports the presentation of map-based media content and messages by the messaging client 104. For example, the map system 210 enables the display of user icons or avatars (e.g., stored in profile data 308) on a map to indicate a current or past location of “friends” of a user, as well as media content (e.g., collections of messages including photographs and videos) generated by such friends, within the context of a map. For example, a message posted by a user to the messaging system 100 from a specific geographic location may be displayed within the context of a map at that particular location to “friends” of a specific user on a map interface of the messaging client 104. A user can furthermore share his or her location and status information (e.g., using an appropriate status avatar) with other users of the messaging system 100 via the messaging client 104, with this location and status information being similarly displayed within the context of a map interface of the messaging client 104 to selected users. In some embodiments, the map system 210 is used by the location-based shared AR experience system 202 to determine or to obtain geographic location information of a user device.
The game system 212 provides various gaming functions within the context of the messaging client 104. The messaging client 104 provides a game interface providing a list of available games that can be launched by a user within the context of the messaging client 104, and played with other users of the messaging system 100, including shared AR experiences that are facilitated by the location-based shared AR experience system 202.
Data Architecture
FIG. 3 is a schematic diagram illustrating data structures 300, which may be stored in the database 120 of the messaging server system 108, according to certain examples. While the content of the database 120 is shown to comprise a number of tables, it will be appreciated that the data could be stored in other types of data structures (e.g., as an object-oriented database).
The database 120 includes message data stored within a message table 302. This message data includes, for any particular one message, at least message sender data, message recipient (or receiver) data, and a payload. Further details regarding information that may be included in a message, and included within the message data stored in the message table 302 is described below with reference to FIG. 4.
An entity table 304 stores entity data, and is linked (e.g., referentially) to an entity graph 306 and profile data 308. Entities for which records are maintained within the entity table 304 may include individuals, corporate entities, organizations, objects, places, events, and so forth. Regardless of entity type, any entity regarding which the messaging server system 108 stores data may be a recognized entity. Each entity is provided with a unique identifier, as well as an entity type identifier (not shown).
The entity graph 306 stores information regarding relationships and associations between entities. Such relationships may be social, professional (e.g., work at a common corporation or organization) interested-based or activity-based, merely for example.
The profile data 308 stores multiple types of profile data about a particular entity. As explained above, users in the messaging system are represented by respective profiles storing information pertaining to the associated users. The profile data 308 may be selectively used and presented to other users of the messaging system, based on privacy settings specified by a particular entity. Where the entity is an individual, the profile data 308 includes, for example, a user name, telephone number, address, settings (e.g., notification and privacy settings), as well as a user-selected avatar representation (or collection of such avatar representations). The profile data 308 may include information about a user that can be accessed by the location-based shared AR experience system 202. Information about a user that can be accessed by the location-based shared AR experience system 202 includes, for example, statistics of the user with respect to a given shared AR experience.
The database 120 also stores augmentation data in an augmentation table 310. The augmentation data is associated with and applied to videos (for which data is stored in a video table 314) and images (for which data is stored in an image table 316). In some examples, the augmentation data is used by various AR components, including the AR component. An example of augmentation data is a target media content object, which may be associated with an AR component and used to generate an AR experience for a user, as described above.
Another example of augmentation data is augmented reality (AR) tools that can be used in AR components to effectuate image transformations. Image transformations include real-time modifications, which modify an image (e.g., a video frame) as it is captured using a digital image sensor of a client device 102. The modified image is displayed on a screen of the client device 102 with the modifications. AR tools may also be used to apply modifications to stored content, such as video clips or still images stored in a gallery. In a client device 102 with access to multiple AR tools, a user can apply different AR tools (e.g., by engaging different AR components configured to utilize different AR tools) to a single video clip to see how the different AR tools would modify the same video clip. For example, multiple AR tools that apply different pseudorandom movement models can be applied to the same captured content by selecting different AR tools for the same captured content. Similarly, real-time video capture may be used with an illustrated modification to show how video images currently being captured by a digital image sensor of a camera provided with a client device 102 would modify the captured data. Such data may simply be displayed on the screen and not stored in memory, or the content captured by digital image sensor may be recorded and stored in memory with or without the modifications (or both). A messaging client 104 can be configured to include a preview feature that can show how modifications produced by different AR tools will look, within different windows in a display at the same time. This can, for example, permit a user to view multiple windows with different pseudorandom animations presented on a display at the same time.
In some examples, when a particular modification is selected along with content to be transformed, elements to be transformed are identified by the computing device, and then detected and tracked if they are present in the frames of the video. The elements of the object are modified according to the request for modification, thus transforming the frames of the video stream. Transformation of frames of a video stream can be performed by different methods for different kinds of transformation. For example, for transformations of frames mostly referring to changing forms of object's elements characteristic points for each element of an object are calculated (e.g., using an Active Shape Model (ASM) or other known methods). Then, a mesh based on the characteristic points is generated for each of the at least one element of the object. This mesh used in the following stage of tracking the elements of the object in the video stream. In the process of tracking, the mentioned mesh for each element is aligned with a position of each element. Then, additional points are generated on the mesh. A first set of first points is generated for each element based on a request for modification, and a set of second points is generated for each element based on the set of first points and the request for modification. Then, the frames of the video stream can be transformed by modifying the elements of the object on the basis of the sets of first and second points and the mesh. In such method, a background of the modified object can be changed or distorted as well by tracking and modifying the background.
As mentioned above, the video table 314 stores video data that, in some examples, is associated with messages for which records are maintained within the message table 302. Similarly, the image table 316 stores image data associated with messages for which message data is stored in the entity table 304. The entity table 304 may associate various augmentations from the augmentation table 310 with various images and videos stored in the image table 316 and the video table 314.
Process Flow
FIG. 4 is a flowchart of a method 400 for enhancing experience of users engaging with a shared AR experience, in accordance with some examples.
Although the described flowchart can show operations as a sequential process, many of the operations can be performed in parallel or concurrently. In addition, the order of the operations may be re-arranged. A process is terminated when its operations are completed. A process may correspond to a method, a procedure, an algorithm, etc. The operations of methods may be performed in whole or in part, may be performed in conjunction with some or all of the operations in other methods, and may be performed by any number of different systems, such as the systems described herein, or any portion thereof, such as a processor included in any of the systems. In one example, some or all processing logic resides at the client device 102 of FIG. 1 and/or at the messaging server system 108 of FIG. 1.
The method 400 commences at operation 410, a computing system receives a request to launch the shared AR experience at a user device. In one example, the computing system is a messaging system that hosts a backend service for a messaging client and that provides a shared AR experience. For example, a user of the user device selects an option in a UI of the user device to request to launch a shared AR experience. The user device transmits the request to the computing system. In one example the request includes information corresponding to the geographic location of the user device.
The shared AR experience is associated with at least one virtual object and an activity UI. The activity UI is generated for respective participating devices using respective camera views of the respective participating devices. A camera view of a device with respect to an instance of the shared AR experience comprises an output of a digital image sensor of a camera of the device. The user device is located at a geographic location that can be determined using a global positioning service.
At operation 420, the computing system (e.g., via location-based shared AR experience system 202 of FIG. 2) determines an AR experience area corresponding to the geographic location of the user device. In some examples, the location-based shared AR experience system 202 of FIG. 2 receives a GPS location from the user device and selects a previously-defined AR experience area encompassing the GPS location. In one example, the previously-defined AR experience area corresponds to a geographic area defined by at least three latitude/longitude pairs. In another example, an AR experience area can be defined using a GPS location and a predetermined radius. Using this definition an AR experience area it's easy to determine if a new instance should be created, or the user should be guided to the center of the radius to get to the scanned area and increase probability of meeting other players.
At operation 430, the computing system, (e.g., via the location-based shared AR experience system 202) communicates, to the user device, an address identifying the user device as a participating device with respect to the instance of the shared AR experience.
At operation 440, the location-based shared AR experience system 202 causes display of the activity UI on a display of the user device. An example activity UI is shown in FIG. 5 and described below.
The computing system, such as the location-based shared AR experience system 202, would perform the same operations for other user devices requesting to join the shared AR experience. For instance, the computing system receives a request to launch the shared AR experience at another user device located at another geographic location corresponding to the same AR experience area. The computing system communicates, to the other user device, an address identifying the other user device as a participating device with respect to the same instance of the shared AR experience and causes display of the activity UI on a display of the other user device.
The location-based shared AR experience system 202 determines an anchor object corresponding to a real-world object represented in the activity UI displayed on the display of the participating user devices and generates a mapping of the virtual object to the anchor object. In some examples, the anchor object is a mesh of visual features of the associated real-world object that allows an AR-enabled device (the user device) to orient itself.
The location-based shared AR experience system 202 positions the virtual object on the activity UI based on the mapping, such that the activity UI displayed on respective displays of the participating devices reflects the location of the virtual object overlaying the representation of the real world in a consistent manner. The location-based shared AR experience system 202 receives events from the participating devices and updates the state of the instance of the shared AR experience based on the events.
User Interface
FIG. 5 is a diagram 500 of an activity UI including the output of a digital image sensor of a camera of a user device and a virtual object 510 overlaid over the output of the digital image sensor of the camera of a user device. The activity UI shown in FIG. 5 also illustrates a representation of three real-world objects—BUILDING 1, BUILDING 2 and STRUCTURE 1. The location-based shared AR experience system 202 of FIG. 2 determines at least one anchor object corresponding to a real-world object represented in the activity UI displayed on the display of the first user device, such as BUILDING 1 identified in FIG. 5 by reference numeral 520. The location-based shared AR experience system 202 generates a mapping of the virtual object to the anchor object and positions the virtual object on the activity UI displayed on every participating user device, based on the mapping.
Communications Scheme
FIG. 6 is a diagram 600 of a general scheme of communication between various components of the location-based shared AR experience system 202 of FIG. 2. A user device 610 has access to the GPS and provides its own location information to a clustering service 620, in response to or contemporaneous with a request to launch a shared AR experience associated with one or more virtual objects. The clustering service 620 is a backend service, which provides to user devices addresses identifying the user devices as participants with respect to an instance of the shared AR experience. A given instance of the shared AR experience corresponds to an AR experience area that encompasses the geographical location of the user device 610. The activity UI of a given instance of the shared AR experience is generated for respective participating devices using respective camera views of the respective participating devices. A camera view of a participating device comprises an output of a digital image sensor of a camera of the device.
The address identifying the user device 610 as a participant with respect to an instance of the shared AR experience, which is identified in FIG. 6 with a reference numeral 630, is used to permit the instance of the shared AR experience to provide an activity UI to the user device 610, receive from the user device 610 events indicative of interactions of the user with the activity UI, and to send, to the user device 610, updates to the activity UI and to the state of one or more virtual objects associated with the instance of the shared AR experience 630. The state of the instance of the shared AR experience 630 is updated based on the events indicative of interactions of the user of the user device 610 with the activity UI. The instance of the shared AR experience 630 tracks the state of the one or more virtual objects bound with some area in the real world and also tracks respective positions of the participating devices, such as the user device 610, with respect to the shared AR experience area.
The instance of the shared AR experience 630 is configured to provide to a game server 640 data associated with the events indicative of interactions of the user with the activity UI. The game server 640 may be configured to generate a profile of the user and the statistics representing the user's activity and status with respect to the shared AR experience 630 and provide this information to the user device 610. The game server 640 is also configured to update the profile of the user based on information received from the user device 610.
Geographical Sharding
FIG. 7 is a diagram 700 illustrating geographical sharding, which can be used in embodiments describes herein. A world map 710 is partitioned (or sharded) into geographical regions, such as regions 720 and 760, that are small enough to be suitable for engaging users in a shared AR experience. The location-based shared AR experience system 202 of FIG. 1 creates respective AR experience areas corresponding to regions of the world map 710, including respective AR experience areas corresponding the regions 720 and 760. When a user of a user device 722 located in the region 720 requests launching of the shared AR experience at their user device 722, the location-based shared AR experience system 202 determines whether an instance of the shared AR experience already exists for the AR experience area that encompasses the geographic location of the user device 722. If an instance of a shared AR experience does not already exist for the experience area that encompasses the geographic location of the user device 722, the location-based shared AR experience system 202 creates an instance of the shared AR experience (an instance 730).
A clustering service 780 provides the users engaged with the instance 730 addresses identifying the respective mobile devices, such as devices identified with reference numerals 722 and 724, as participating devices with respect to the instance 730. Also shown in FIG. 7 is another instance of the shared AR experience (an instance 740) associated with an AR experience area representing a region 760 of the world map 710. The clustering service 780 provides the users engaged with the instance 740 addresses identifying the respective mobile devices, such as devices identified with reference numerals 762, 764 and 766, as participating devices with respect to the instance 740.
Machine Architecture
FIG. 8 is a diagrammatic representation of the machine 800 within which instructions 808 (e.g., software, a program, an application, an applet, an app, or other executable code) for causing the machine 800 to perform any one or more of the methodologies discussed herein may be executed. For example, the instructions 808 may cause the machine 800 to execute any one or more of the methods described herein. The instructions 808 transform the general, non-programmed machine 800 into a particular machine 800 programmed to carry out the described and illustrated functions in the manner described. The machine 800 may operate as a standalone device or may be coupled (e.g., networked) to other machines. In a networked deployment, the machine 800 may operate in the capacity of a server machine or a client machine in a server-client network environment, or as a peer machine in a peer-to-peer (or distributed) network environment. The machine 800 may comprise, but not be limited to, a server computer, a client computer, a personal computer (PC), a tablet computer, a laptop computer, a netbook, a set-top box (STB), a personal digital assistant (PDA), an entertainment media system, a cellular telephone, a smartphone, a mobile device, a wearable device (e.g., a smartwatch), a smart home device (e.g., a smart appliance), other smart devices, a web appliance, a network router, a network switch, a network bridge, or any machine capable of executing the instructions 808, sequentially or otherwise, that specify actions to be taken by the machine 800. Further, while only a single machine 800 is illustrated, the term “machine” shall also be taken to include a collection of machines that individually or jointly execute the instructions 808 to perform any one or more of the methodologies discussed herein. The machine 800, for example, may comprise the client device 102 or any one of a number of server devices forming part of the messaging server system 108. In some examples, the machine 800 may also comprise both client and server systems, with certain operations of a particular method or algorithm being performed on the server-side and with certain operations of the particular method or algorithm being performed on the client-side.
The machine 800 may include processors 802, memory 804, and input/output I/O components 838, which may be configured to communicate with each other via a bus 840. In an example, the processors 802 (e.g., a Central Processing Unit (CPU), a Reduced Instruction Set Computing (RISC) Processor, a Complex Instruction Set Computing (CISC) Processor, a Graphics Processing Unit (GPU), a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Radio-Frequency Integrated Circuit (RFIC), another processor, or any suitable combination thereof) may include, for example, a processor 806 and a processor 810 that execute the instructions 808. The term “processor” is intended to include multi-core processors that may comprise two or more independent processors (sometimes referred to as “cores”) that may execute instructions contemporaneously. Although FIG. 8 shows multiple processors 802, the machine 800 may include a single processor with a single-core, a single processor with multiple cores (e.g., a multi-core processor), multiple processors with a single core, multiple processors with multiples cores, or any combination thereof.
The memory 804 includes a main memory 812, a static memory 814, and a storage unit 816, both accessible to the processors 802 via the bus 840. The main memory 804, the static memory 814, and storage unit 816 store the instructions 808 embodying any one or more of the methodologies or functions described herein. The instructions 808 may also reside, completely or partially, within the main memory 812, within the static memory 814, within machine-readable medium 818 within the storage unit 816, within at least one of the processors 802 (e.g., within the Processor's cache memory), or any suitable combination thereof, during execution thereof by the machine 800.
The I/O components 838 may include a wide variety of components to receive input, provide output, produce output, transmit information, exchange information, capture measurements, and so on. The specific I/O components 838 that are included in a particular machine will depend on the type of machine. For example, portable machines such as mobile phones may include a touch input device or other such input mechanisms, while a headless server machine will likely not include such a touch input device. It will be appreciated that the I/O components 838 may include many other components that are not shown in FIG. 8. In various examples, the I/O components 838 may include user output components 824 and user input components 826. The user output components 824 may include visual components (e.g., a display such as a plasma display panel (PDP), a light-emitting diode (LED) display, a liquid crystal display (LCD), a projector, or a cathode ray tube (CRT)), acoustic components (e.g., speakers), haptic components (e.g., a vibratory motor, resistance mechanisms), other signal generators, and so forth. The user input components 826 may include alphanumeric input components (e.g., a keyboard, a touch screen configured to receive alphanumeric input, a photo-optical keyboard, or other alphanumeric input components), point-based input components (e.g., a mouse, a touchpad, a trackball, a joystick, a motion sensor, or another pointing instrument), tactile input components (e.g., a physical button, a touch screen that provides location and force of touches or touch gestures, or other tactile input components), audio input components (e.g., a microphone), and the like.
In further examples, the I/O components 838 may include biometric components 828, motion components 830, environmental components 832, or position components 834, among a wide array of other components. For example, the biometric components 828 include components to detect expressions (e.g., hand expressions, facial expressions, vocal expressions, body gestures, or eye-tracking), measure biosignals (e.g., blood pressure, heart rate, body temperature, perspiration, or brain waves), identify a person (e.g., voice identification, retinal identification, facial identification, fingerprint identification, or electroencephalogram-based identification), and the like. The motion components 830 include acceleration sensor components (e.g., accelerometer), gravitation sensor components, rotation sensor components (e.g., gyroscope).
The environmental components 832 include, for example, one or cameras (with still image/photograph and video capabilities), illumination sensor components (e.g., photometer), temperature sensor components (e.g., one or more thermometers that detect ambient temperature), humidity sensor components, pressure sensor components (e.g., barometer), acoustic sensor components (e.g., one or more microphones that detect background noise), proximity sensor components (e.g., infrared sensors that detect nearby objects), gas sensors (e.g., gas detection sensors to detection concentrations of hazardous gases for safety or to measure pollutants in the atmosphere), or other components that may provide indications, measurements, or signals corresponding to a surrounding physical environment.
With respect to cameras, the client device 102 may have a camera system comprising, for example, front cameras on a front surface of the client device 102 and rear cameras on a rear surface of the client device 102. The front cameras may, for example, be used to capture still images and video of a user of the client device 102 (e.g., “selfies”), which may then be augmented with augmentation data (e.g., filters) described above. The rear cameras may, for example, be used to capture still images and videos in a more traditional camera mode, with these images similarly being augmented with augmentation data. In addition to front and rear cameras, the client device 102 may also include a 360° camera for capturing 360° photographs and videos.
Further, the camera system of a client device 102 may include dual rear cameras (e.g., a primary camera as well as a depth-sensing camera), or even triple, quad or penta rear camera configurations on the front and rear sides of the client device 102. These multiple cameras systems may include a wide camera, an ultra-wide camera, a telephoto camera, a macro camera and a depth sensor, for example.
The position components 834 include location sensor components (e.g., a GPS receiver component), altitude sensor components (e.g., altimeters or barometers that detect air pressure from which altitude may be derived), orientation sensor components (e.g., magnetometers), and the like.
Communication may be implemented using a wide variety of technologies. The I/O components 838 further include communication components 836 operable to couple the machine 800 to a network 820 or devices 822 via respective coupling or connections. For example, the communication components 836 may include a network interface Component or another suitable device to interface with the network 820. In further examples, the communication components 836 may include wired communication components, wireless communication components, cellular communication components, Near Field Communication (NFC) components, Bluetooth® components (e.g., Bluetooth® Low Energy), Wi-Fi® components, and other communication components to provide communication via other modalities. The devices 822 may be another machine or any of a wide variety of peripheral devices (e.g., a peripheral device coupled via a USB).
Moreover, the communication components 636 may detect identifiers or include components operable to detect identifiers. For example, the communication components 636 may include Radio Frequency Identification (RFID) tag reader components, NFC smart tag detection components, optical reader components (e.g., an optical sensor to detect one-dimensional bar codes such as Universal Product Code (UPC) bar code, multi-dimensional bar codes such as Quick Response (QR) code, Aztec code, Data Matrix, Dataglyph, MaxiCode, PDF417, Ultra Code, UCC RSS-2D bar code, and other optical codes), or acoustic detection components (e.g., microphones to identify tagged audio signals). In addition, a variety of information may be derived via the communication components 836, such as location via Internet Protocol (IP) geolocation, location via Wi-Fi® signal triangulation, location via detecting an NFC beacon signal that may indicate a particular location, and so forth.
The various memories (e.g., main memory 812, static memory 814, and memory of the processors 802) and storage unit 816 may store one or more sets of instructions and data structures (e.g., software) embodying or used by any one or more of the methodologies or functions described herein. These instructions (e.g., the instructions 808), when executed by processors 802, cause various operations to implement the disclosed examples.
The instructions 808 may be transmitted or received over the network 820, using a transmission medium, via a network interface device (e.g., a network interface component included in the communication components 836) and using any one of several well-known transfer protocols (e.g., hypertext transfer protocol (HTTP)). Similarly, the instructions 808 may be transmitted or received using a transmission medium via a coupling (e.g., a peer-to-peer coupling) to the devices 822.
Glossary
“Carrier signal” refers to any intangible medium that is capable of storing, encoding, or carrying instructions for execution by the machine, and includes digital or analog communications signals or other intangible media to facilitate communication of such instructions. Instructions may be transmitted or received over a network using a transmission medium via a network interface device.
“Client device” refers to any machine that interfaces to a communications network to obtain resources from one or more server systems or other client devices. A client device may be, but is not limited to, a mobile phone, desktop computer, laptop, portable digital assistants (PDAs), smartphones, tablets, ultrabooks, netbooks, laptops, multi-processor systems, microprocessor-based or programmable consumer electronics, game consoles, set-top boxes, or any other communication device that a user may use to access a network.
“Communication network” refers to one or more portions of a network that may be an ad hoc network, an intranet, an extranet, a virtual private network (VPN), a local area network (LAN), a wireless LAN (WLAN), a wide area network (WAN), a wireless WAN (WWAN), a metropolitan area network (MAN), the Internet, a portion of the Internet, a portion of the Public Switched Telephone Network (PSTN), a plain old telephone service (POTS) network, a cellular telephone network, a wireless network, a Wi-Fi® network, another type of network, or a combination of two or more such networks. For example, a network or a portion of a network may include a wireless or cellular network and the coupling may be a Code Division Multiple Access (CDMA) connection, a Global System for Mobile communications (GSM) connection, or other types of cellular or wireless coupling. In this example, the coupling may implement any of a variety of types of data transfer technology, such as Single Carrier Radio Transmission Technology (1×RTT), Evolution-Data Optimized (EVDO) technology, General Packet Radio Service (GPRS) technology, Enhanced Data rates for GSM Evolution (EDGE) technology, third Generation Partnership Project (3GPP) including 3G, fourth generation wireless (4G) networks, Universal Mobile Telecommunications System (UMTS), High Speed Packet Access (HSPA), Worldwide Interoperability for Microwave Access (WiMAX), Long Term Evolution (LTE) standard, others defined by various standard-setting organizations, other long-range protocols, or other data transfer technology.
“Component” refers to a device, physical entity, or logic having boundaries defined by function or subroutine calls, branch points, APIs, or other technologies that provide for the partitioning or modularization of particular processing or control functions. Components may be combined via their interfaces with other components to carry out a machine process. A component may be a packaged functional hardware unit designed for use with other components and a part of a program that usually performs a particular function of related functions. Components may constitute either software components (e.g., code embodied on a machine-readable medium) or hardware components. A “hardware component” is a tangible unit capable of performing certain operations and may be configured or arranged in a certain physical manner. In various example embodiments, one or more computer systems (e.g., a standalone computer system, a client computer system, or a server computer system) or one or more hardware components of a computer system (e.g., a processor or a group of processors) may be configured by software (e.g., an application or application portion) as a hardware component that operates to perform certain operations as described herein. A hardware component may also be implemented mechanically, electronically, or any suitable combination thereof. For example, a hardware component may include dedicated circuitry or logic that is permanently configured to perform certain operations. A hardware component may be a special-purpose processor, such as a field-programmable gate array (FPGA) or an application specific integrated circuit (ASIC). A hardware component may also include programmable logic or circuitry that is temporarily configured by software to perform certain operations. For example, a hardware component may include software executed by a general-purpose processor or other programmable processor. Once configured by such software, hardware components become specific machines (or specific components of a machine) uniquely tailored to perform the configured functions and are no longer general-purpose processors. It will be appreciated that the decision to implement a hardware component mechanically, in dedicated and permanently configured circuitry, or in temporarily configured circuitry (e.g., configured by software), may be driven by cost and time considerations. Accordingly, the phrase “hardware component” (or “hardware-implemented component”) should be understood to encompass a tangible entity, be that an entity that is physically constructed, permanently configured (e.g., hardwired), or temporarily configured (e.g., programmed) to operate in a certain manner or to perform certain operations described herein. Considering embodiments in which hardware components are temporarily configured (e.g., programmed), each of the hardware components need not be configured or instantiated at any one instance in time. For example, where a hardware component comprises a general-purpose processor configured by software to become a special-purpose processor, the general-purpose processor may be configured as respectively different special-purpose processors (e.g., comprising different hardware components) at different times. Software accordingly configures a particular processor or processors, for example, to constitute a particular hardware component at one instance of time and to constitute a different hardware component at a different instance of time. Hardware components can provide information to, and receive information from, other hardware components. Accordingly, the described hardware components may be regarded as being communicatively coupled. Where multiple hardware components exist contemporaneously, communications may be achieved through signal transmission (e.g., over appropriate circuits and buses) between or among two or more of the hardware components. In embodiments in which multiple hardware components are configured or instantiated at different times, communications between such hardware components may be achieved, for example, through the storage and retrieval of information in memory structures to which the multiple hardware components have access. For example, one hardware component may perform an operation and store the output of that operation in a memory device to which it is communicatively coupled. A further hardware component may then, at a later time, access the memory device to retrieve and process the stored output. Hardware components may also initiate communications with input or output devices, and can operate on a resource (e.g., a collection of information). The various operations of example methods described herein may be performed, at least partially, by one or more processors that are temporarily configured (e.g., by software) or permanently configured to perform the relevant operations. Whether temporarily or permanently configured, such processors may constitute processor-implemented components that operate to perform one or more operations or functions described herein. As used herein, “processor-implemented component” refers to a hardware component implemented using one or more processors. Similarly, the methods described herein may be at least partially processor-implemented, with a particular processor or processors being an example of hardware. For example, at least some of the operations of a method may be performed by one or more processors or processor-implemented components. Moreover, the one or more processors may also operate to support performance of the relevant operations in a “cloud computing” environment or as a “software as a service” (SaaS). For example, at least some of the operations may be performed by a group of computers (as examples of machines including processors), with these operations being accessible via a network (e.g., the Internet) and via one or more appropriate interfaces (e.g., an API). The performance of certain of the operations may be distributed among the processors, not only residing within a single machine, but deployed across a number of machines. In some example embodiments, the processors or processor-implemented components may be located in a single geographic location (e.g., within a home environment, an office environment, or a server farm). In other example embodiments, the processors or processor-implemented components may be distributed across a number of geographic locations.
“Computer-readable storage medium” refers to both machine-storage media and transmission media. Thus, the terms include both storage devices/media and carrier waves/modulated data signals. The terms “machine-readable medium,” “computer-readable medium” and “device-readable medium” mean the same thing and may be used interchangeably in this disclosure.
“Machine storage medium” refers to a single or multiple storage devices and media (e.g., a centralized or distributed database, and associated caches and servers) that store executable instructions, routines and data. The term shall accordingly be taken to include, but not be limited to, solid-state memories, and optical and magnetic media, including memory internal or external to processors. Specific examples of machine-storage media, computer-storage media and device-storage media include non-volatile memory, including by way of example semiconductor memory devices, e.g., erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), FPGA, and flash memory devices; magnetic disks such as internal hard disks and removable disks; magneto-optical disks; and CD-ROM and DVD-ROM disks The terms “machine-storage medium,” “device-storage medium,” “computer-storage medium” mean the same thing and may be used interchangeably in this disclosure. The terms “machine-storage media,” “computer-storage media,” and “device-storage media” specifically exclude carrier waves, modulated data signals, and other such media, at least some of which are covered under the term “signal medium.”
“Non-transitory computer-readable storage medium” refers to a tangible medium that is capable of storing, encoding, or carrying the instructions for execution by a machine.
“Signal medium” refers to any intangible medium that is capable of storing, encoding, or carrying the instructions for execution by a machine and includes digital or analog communications signals or other intangible media to facilitate communication of software or data. The term “signal medium” shall be taken to include any form of a modulated data signal, carrier wave, and so forth. The term “modulated data signal” means a signal that has one or more of its characteristics set or changed in such a matter as to encode information in the signal. The terms “transmission medium” and “signal medium” mean the same thing and may be used interchangeably in this disclosure.
