Persistent augmented reality experience

Abstract

Methods and systems are disclosed for performing generating an AR experience on a messaging platform. The method and system perform operations including: receiving, from a client device, a request to access an augmented reality (AR) experience; adding one or more AR elements to a first image captured by the client device, the first image depicting the real-world object; storing data representing a position of the one or more AR elements relative to the real-world object, the data being maintained after termination of the AR experience; after the AR experience has terminated, receiving a request to restore the AR experience; and in response to receiving a request to restore the AR experience, accessing data stored prior to termination of the AR experience to generate a display of the AR experience that depicts one or more AR elements at a particular location within the second image.

Description

[0001] Priority claim

[0002] This application claims the benefit of priority to U.S. Application No. 17 / 728,473, filed on April 25, 2022, the entire contents of which are incorporated herein by reference. Technical Field

[0003] The present disclosure generally relates to generating augmented reality (AR) experiences on messaging applications. Background Art

[0004] Augmented reality (AR) is a modification of a virtual environment. For example, in virtual reality (VR), the user is completely immersed in a virtual world, while in AR, the user is immersed in a world that combines virtual objects with the real world or superimposes virtual objects on the real world. AR systems are designed to generate and present virtual objects that interact realistically with the real world environment and with each other. Examples of AR applications can include single or multiplayer video games, instant messaging systems, etc. BRIEF DESCRIPTION OF THE DRAWINGS

[0005] In the accompanying drawings (which are not necessarily drawn to scale), like numbers may describe similar components in different views. To easily identify the discussion of any particular element or action, one or more of the most significant digits in a reference numeral refers to the figure number in which the element is first introduced. Some non-limiting examples are shown in the accompanying drawings, in which:

[0006] Figure 1 is a diagrammatic representation of a networking environment in which the present disclosure may be deployed, according to some examples.

[0007] Figure 2 is a diagrammatic representation of a messaging client application according to some examples.

[0008] Figure 3 is a diagrammatic representation of data structures maintained in a database according to some examples.

[0009] Figure 4 is a graphical representation of messages according to some examples.

[0010] Figure 5 is a block diagram illustrating an example AR element positioning system according to some examples.

[0011] Figure 6-Figure 8 is a graphical representation of the output of an AR element positioning system according to some examples.

[0012] Fig. 9 is a flow diagram illustrating example operations of an AR element positioning system according to some examples.

[0013] Fig.10 is a diagrammatic representation of a machine in the form of a computer system according to some examples within which a set of instructions may be executed for causing the machine to perform any one or more of the methodologies discussed herein.

[0014] Fig.11 is a block diagram illustrating a software architecture in which examples may be implemented. DETAILED DESCRIPTION

[0015] The following description includes systems, methods, techniques, instruction sequences and computing machine program products that implement the illustrative examples of the present disclosure. In the following description, for the purpose of illustration, many specific details are set forth to provide an understanding of various examples. However, it will be apparent to those skilled in the art that examples may be practiced without these specific details. Typically, it is not necessary to show in detail known instruction instances, protocols, structures and techniques.

[0016] Messaging applications typically enable end users to access various AR experiences by launching an AR experience bundle or package that includes AR content associated with the AR experience. AR experiences typically present AR elements that are animated or anchored to a specific location. This allows the user to move around in the real world and keep the AR elements in place or move around in a similar manner. Sometimes, users are interested in closing the AR experience and restarting the AR experience again in the future or on another device. However, when the AR experience is closed, the contextual information associated with the AR elements presented or created as part of the AR experience is typically deleted. As a result, when the user revisits the same AR experience at a future time, the AR elements are unavailable or presented in their original default positions and do not reflect any changes performed by the user relative to those AR elements. This forces users to recreate their previous AR experience, which can be time-consuming and wasteful of resources. This reduces the user's interest level in revisiting the AR experience, resulting in missed opportunities.

[0017] The disclosed technology solves these technical problems by maintaining contextual information and positioning information of AR elements across devices and across different times or instances of launching an AR experience. To this end, the disclosed technology receives a request to access an AR experience from a client device and adds one or more AR elements to a first image captured by the client device, the first image depicting a real-world object. The disclosed technology stores data representing the position of one or more AR elements relative to the real-world object, wherein the data is maintained after the AR experience is terminated. The disclosed technology receives a request to resume the AR experience after the AR experience has been terminated, and in response to receiving the request to resume the AR experience, accesses the data stored before the AR experience is terminated to generate a display of the AR experience, which depicts one or more AR elements at a specific location within a second image.

[0018] In some examples, an AR development platform may be provided to an AR experience developer. The AR development platform may present a user interface to the AR experience developer that enables the AR developer to select which AR elements will save their positions after the AR experience is terminated or closed. The graphical user interface presents a list of AR elements associated with the AR experience and includes a first option associated with a first AR element in the AR element list to cause the location data of the first AR element to be stored after the AR experience is terminated in response to a selection of the first option. The graphical user interface also includes a second option associated with a second AR element in the AR element list to prevent the location data of the second AR element from being stored after the AR experience is terminated in response to a selection of the second option. This provides developers with greater flexibility to create useful, interesting, and engaging AR experiences without being limited by resource constraints of the messaging application and / or client device running the AR experience.

[0019] This improves the efficiency of using the electronic device and the overall experience of the user using the electronic device. In addition, by automating the presentation of AR elements across devices and / or subsequent presentation times of associated AR experiences, the total amount of system resources required to complete the task is reduced.

[0020] Networked computing environment

[0021] Figure 11 is a block diagram illustrating an example messaging system 100 for exchanging data (e.g., messages and associated content) over a network. The messaging system 100 includes multiple instances of a client device 102, each of the multiple instances hosting several applications including a messaging client 104 and other external applications 109 (e.g., third-party applications). Each messaging client 104 is communicatively coupled to other instances of the messaging client 104 (e.g., hosted on corresponding other client devices 102), a messaging server system 108, and an external application server 110 via a network 112 (e.g., the Internet). The messaging client 104 may also communicate with locally hosted third-party applications (e.g., external applications 109) using an application programming interface (API).

[0022] The client device 102 can operate as a standalone device, or can be coupled (e.g., networked) to other machines. In a networked deployment, the client device 102 can operate with the capabilities of a server machine or a client machine in a server-client network environment, or operate as a peer machine in a peer-to-peer (or distributed) network environment. The client device 102 may include, but is not limited to, a server computer, a client computer, a personal computer (PC), a tablet computer, a notebook computer, a netbook, a set-top box (STB), a personal digital assistant (PDA), an entertainment media system, a cellular phone, a smart phone, a mobile device, a wearable device (e.g., a smart watch), a smart home device (e.g., a smart appliance), other smart devices, a web device, a network router, a network switch, a network bridge, or any machine capable of performing the disclosed operations. In addition, although only a single client device 102 is shown, the term "client device" should also be considered to include a collection of machines that perform the disclosed operations individually or jointly.

[0023] In some examples, client device 102 may include AR glasses or an AR head-mounted device, in which virtual content is displayed within the lenses of the glasses while the user views the real world environment through the lenses. For example, an image may be presented on a transparent display that allows the user to simultaneously view the content presented on the display and real-world objects.

[0024] In some examples, client device 102 may be operated by an AR experience developer. In this case, the AR experience developer (or AR developer) accesses an AR experience development platform. The AR experience development platform allows the AR developer to generate an AR experience bundle that includes a set of AR elements. The AR developer may specify conditions for persisting the set of AR elements or a portion of the set of AR elements (or select an option to enable / disable persisting the set of AR elements or a portion of the set of AR elements). In this case, persisting the AR elements causes context data and / or position data (spatial position and / or display position) of the AR elements to be stored and available for the AR experience when the AR experience is subsequently launched or resumed on the same or different device after termination or closure. The context data and / or position data may be used by the resumed AR experience to display the AR elements in the same location and in the same context as the AR experience previously displayed the AR elements on another device or at an earlier point in time before the AR experience was closed or terminated.

[0025] In some examples, the condition may include a geographic location, a level in a game application or AR experience, a view or depiction of a portion of a real-world environment, a time, a location tag, an image tag, or any other suitable condition. In some examples, the context data and / or location data may include at least one of the following: the latitude and longitude of a real-world object, the global positioning system coordinates of the real-world object, a bounding box associated with the real-world object, an object type of the real-world object, or a three-dimensional match of the real-world object. In some examples, the context data and / or location data may include at least one of the following: the latitude and longitude of a persisted AR element, the global positioning system coordinates of a persisted AR element, a bounding box associated with a persisted AR element, an object type of a persisted AR element, or a three-dimensional match of a persisted AR element.

[0026] The messaging clients 104 are able to communicate and exchange data with other messaging clients 104 and messaging server systems 108 via the network 112. The data exchanged between the messaging clients 104 and between the messaging clients 104 and messaging server systems 108 include functions (e.g., commands for activating functions) and payload data (e.g., text, audio, video, or other multimedia data).

[0027] The messaging server system 108 provides server-side functionality to specific messaging clients 104 via the network 112. Although certain functions of the messaging system 100 are described herein as being performed by the messaging client 104 or by the messaging server system 108, the location of certain functions within the messaging client 104 or within the messaging server system 108 may be a design choice. For example, it may be technically preferable to initially deploy certain technologies and functions within the messaging server system 108, but later migrate the technologies and functions to the messaging client 104 where the client device 102 has sufficient processing power.

[0028] The messaging server system 108 supports various services and operations provided to the messaging clients 104. Such operations include sending data to the messaging clients 104, receiving data from the messaging clients 104, and processing data generated by the messaging clients 104. As examples, the data may include message content, client device information, geographic location information, media enhancements and overlays, message content persistence conditions, social network information, and live event information. The exchange of data within the messaging system 100 is activated and controlled by functions available via the user interface (UI) of the messaging client 104.

[0029] Turning now specifically to the messaging server system 108, an application programming interface (API) server 116 is coupled to and provides a programming interface to the application server 114. The application server 114 is communicatively coupled to a database server 120, which facilitates access to a database 126 that stores data associated with messages processed by the application server 114. Similarly, a web server 128 is coupled to and provides a web-based interface to the application server 114. To this end, the web server 128 processes incoming network requests via the Hypertext Transfer Protocol (HTTP) and several other related protocols.

[0030] The API server 116 receives and sends message data (e.g., commands and message payloads) between the client device 102 and the application server 114. Specifically, the API server 116 provides a set of interfaces (e.g., routines and protocols) that can be called or queried by the messaging client 104 to activate the functionality of the application server 114. The API server 116 exposes various functions supported by the application server 114, including: account registration; login functionality; sending messages from a particular messaging client 104 to another messaging client 104 via the application server 114; sending media files (e.g., images or videos) from the messaging client 104 to the messaging server 118 and for possible access by another messaging client 104; setting up a collection of media data (e.g., a story); retrieving a friend list of the user of the client device 102; retrieving such a collection; retrieving messages and content; adding and removing entities (e.g., friends) from an entity graph (e.g., a social graph); locating friends within a social graph; and opening application events (e.g., related to the messaging client 104).

[0031] The application server 114 hosts several server applications and subsystems, including, for example, a messaging server 118, an image processing server 122, and a social network server 124. The messaging server 118 implements several message processing techniques and functions, particularly those related to aggregation and other processing of content (e.g., text and multimedia content) included in messages received from multiple instances of the messaging client 104. As will be described in further detail, text and media content from multiple sources can be aggregated into collections of content (e.g., called stories or galleries). These collections are then made available to the messaging client 104. Given the hardware requirements for other processor- and memory-intensive data processing, such processing can also be performed on the server side by the messaging server 118.

[0032] The application server 114 also includes an image processing server 122 that is dedicated to performing various image processing operations, typically on images or videos within the payload of messages sent from or received at the messaging server 118 .

[0033] The image processing server 122 is used to implement the enhancement system 208 ( Figure 2). The scanning function includes activating and providing one or more augmented reality experiences on the client device 102 when an image is captured by the client device 102. Specifically, the messaging client 104 on the client device 102 can be used to activate the camera. The camera displays one or more real-time images or videos and one or more icons or identifiers of one or more augmented reality experiences to the user. The user can select a given identifier in the identifier to start the corresponding augmented reality experience or perform the desired image modification (for example, replace the clothing worn by the user in the video or recolor the clothing worn by the user in the video or modify the clothing based on the gesture performed by the user).

[0034] The social network server 124 supports various social networking functions and services and makes them available to the messaging server 118. To this end, the social network server 124 maintains and accesses an entity graph 308 (e.g., Figure 3 ). Examples of functions and services supported by the social networking server 124 include identifying other users of the messaging system 100 that have a relationship with a particular user or that the particular user is "following," and also include identifying interests and other entities of a particular user.

[0035] Returning to the messaging client 104, the features and functions of the external resource (e.g., a third-party application 109 or a mini-program) are available to the user via the interface of the messaging client 104. The messaging client 104 receives a user selection of an option for launching or accessing features of an external resource (e.g., a third-party resource) such as an external application 109. The external resource can be a third-party application (external application 109) installed on the client device 102 (e.g., a "native application"), or a small-scale version of a third-party application (e.g., a "mini-program") hosted on the client device 102 or away from the client device 102 (e.g., on a third-party server 110). The small-scale version of the third-party application includes a subset of the features and functions of the third-party application (e.g., a full-scale, native version of a third-party standalone application) and is implemented using a markup language document. In one example, the small-scale version of the third-party application (e.g., a "mini-program") is a web-based markup language version of the third-party application and is embedded in the messaging client 104. In addition to using markup language documents (eg, *ml files), applets may include scripting languages ​​(eg, .*js files or .json files) and style sheets (eg, *ss files).

[0036] In response to receiving a user selection of an option for launching or accessing a feature of an external resource (external application 109), the messaging client 104 determines whether the selected external resource is a web-based external resource or a locally installed external application. In some cases, the external application 109 locally installed on the client device 102 can be launched independently of the messaging client 104 and separately from the messaging client 104, for example, by selecting an icon corresponding to the external application 109 on the home screen of the client device 102. A small-scale version of such an external application can be launched or accessed via the messaging client 104, and in some examples, no part of the small-scale external application can be (or a limited part can be) accessed outside the messaging client 104. The small-scale external application can be launched by the messaging client 104 receiving a markup language document associated with the small-scale external application from the external application server 110 and processing such a document.

[0037] In response to determining that the external resource is a locally installed external application 109, the messaging client 104 instructs the client device 102 to launch the external application 109 by executing the locally stored code corresponding to the external application 109. In response to determining that the external resource is a web-based resource, the messaging client 104 communicates with the external application server 110 to obtain a markup language document corresponding to the selected resource. The messaging client 104 then processes the obtained markup language document to present the web-based external resource within the user interface of the messaging client 104.

[0038] The messaging client 104 may notify the user of the client device 102 or other users (e.g., "friends") associated with such a user of activities occurring in one or more external resources. For example, the messaging client 104 may provide a participant in a conversation (e.g., a chat session) in the messaging client 104 with a notification related to the current or recent use of an external resource by one or more members of a user group. One or more users may be invited to join an active external resource or to start an external resource that has been recently used but is currently inactive (in the friend group). The external resource may provide the participants in the conversation who each use the corresponding messaging client 104 with the ability to share items, conditions, states, or locations in the external resource with one or more members of the user group entering the chat session. The shared item may be an interactive chat card that members of the chat may interact with, such as starting a corresponding external resource, viewing specific information within an external resource, or bringing members of the chat to a specific location or state within an external resource. Within a given external resource, a response message may be sent to the user on the messaging client 104. The external resource may selectively include different media items in the response based on the current context of the external resource.

[0039] The messaging client 104 may present a list of available external resources (e.g., third-party or external applications 109 or applets) to the user to launch or access a given external resource. The list may be presented in a context-sensitive menu. For example, icons representing different external applications in the external applications 109 (or applets) may vary based on how the user launches the menu (e.g., from a conversation interface or from a non-conversation interface).

[0040] The messaging client 104 may allow a user to launch an AR experience having AR elements that may be persistent. Specifically, the messaging client 104 may receive a request to access an AR experience associated with multiple AR elements. The messaging client 104 may add one or more AR elements to a first image captured by the client device 102, the first image depicting a real-world object. The messaging client 104 may store data representing the position of one or more AR elements relative to the real-world object. The data may be retained after the AR experience is terminated by the messaging client 104 and / or a server associated with the messaging client 104. The messaging client 104 may receive a request to restore the AR experience after the AR experience has been terminated. In response to receiving a request to restore the AR experience, the messaging client 104 may access the data stored before the AR experience is terminated to generate a display of the AR experience that depicts one or more AR elements at a specific location within the second image. This may result in consistent presentation of the AR experience and the associated AR elements of the AR experience across devices and across the time or instance accessed after the AR experience is terminated or closed.

[0041] In some examples, the messaging client 104 may present an AR developer interface. In this case, as discussed below, the messaging client 104 may be operated by an AR developer to develop and create one or more AR experiences.

[0042] System Architecture

[0043] Figure 2 1 is a block diagram showing additional details about the messaging system 100 according to some examples. Specifically, the messaging system 100 is shown to include a messaging client 104 and an application server 114. The messaging system 100 contains several subsystems that are supported on the client side by the messaging client 104 and on the server side by the application server 114. These subsystems include, for example, a transient timer system 202, a collection management system 204, an enhancement system 208, a map system 210, a game system 212, and an external resource system 220.

[0044] The transient timer system 202 is responsible for implementing temporary or time-limited access to content by the messaging client 104 and the messaging server 118. The transient timer system 202 includes several timers that selectively enable access to messages and associated content (e.g., for presentation and display) via the messaging client 104 based on duration and display parameters associated with a message or a collection of messages (e.g., a story). Additional details regarding the operation of the transient timer system 202 are provided below.

[0045] The collection management system 204 is responsible for managing collections or collections of media (e.g., collections of text, image video, and audio data). Collections of content (e.g., messages, including images, videos, text, and audio) can be organized into "event galleries" or "event stories." Such collections can be made available for a specified period of time (e.g., the duration of an event related to the content). For example, content related to a concert can be made available as a "story" for the duration of the concert. The collection management system 204 can also be responsible for publishing an icon that provides notification of the existence of a particular collection to the user interface of the messaging client 104.

[0046] The collection management system 204 also includes a curation interface 206 that allows a collection manager to manage and curate a particular collection of content. For example, the curation interface 206 enables an event organizer to curate a collection of content related to a particular event (e.g., to remove inappropriate content or redundant messages). In addition, the collection management system 204 uses machine vision (or image recognition technology) and content rules to automatically curate content collections. In some examples, compensation may be paid to users for including user-generated content in a collection. In such a case, the collection management system 204 operates to automatically pay such users for use of their content.

[0047] The enhancement system 208 provides various functions that enable users to enhance (e.g., annotate or otherwise modify or edit) media content associated with a message. For example, the enhancement system 208 provides functions related to generating and publishing media overlays for messages processed by the messaging system 100. The enhancement system 208 is operable to provide media overlays or enhancements (e.g., image filters) to the messaging client 104 based on the geographic location of the client device 102. In another example, the enhancement system 208 is operable to provide media overlays to the messaging client 104 based on other information such as social network information of the user of the client device 102. The media overlay can include audio and visual content and visual effects. Examples of audio and visual content include pictures, text, logos, animations, and sound effects. Examples of visual effects include color overlays. Audio and visual content or visual effects can be applied to media content items (e.g., photos) at the client device 102. For example, the media overlay can include text, graphic elements, or images that can be superimposed on photos taken by the client device 102. In another example, the media overlay includes a location identification overlay (e.g., Venice Beach), the name of a live event, or a business name overlay (e.g., Beach Cafe). In another example, the augmentation system 208 uses the geographic location of the client device 102 to identify a media overlay that includes the name of a business at the geographic location of the client device 102. The media overlay may include other tags associated with the business. The media overlay may be stored in the database 126 and accessed through the database server 120.

[0048] In some examples, the enhancement system 208 provides a user-based publishing platform that enables a user to select a geographic location on a map and upload content associated with the selected geographic location. The user can also specify situations in which a particular media overlay should be provided to other users. The enhancement system 208 generates a media overlay that includes the uploaded content and associates the uploaded content with the selected geographic location.

[0049] In other examples, the augmentation system 208 provides a merchant-based publishing platform that enables merchants to select specific media overlays associated with a geographic location via a bidding process. For example, the augmentation system 208 associates the media overlay of the highest bidding merchant with the corresponding geographic location for a predefined amount of time. The augmentation system 208 communicates with the image processing server 122 to obtain an augmented reality experience, and presents an identifier of such an experience in one or more user interfaces (e.g., as an icon on a real-time image or video, or as a thumbnail or icon in an interface dedicated to an identifier of the presented augmented reality experience). Once an augmented reality experience is selected, one or more images, videos, or augmented reality graphical elements are retrieved and presented as an overlay on top of an image or video captured by the client device 102. In some cases, the camera is switched to a front view (e.g., the front camera of the client device 102 is activated in response to activation of a particular augmented reality experience), and an image from the front camera of the client device 102, rather than the rear camera of the client device 102, begins to be displayed on the client device 102. One or more images, videos, or augmented reality graphical elements are retrieved and presented as an overlay on top of the image captured and displayed by the front-facing camera of the client device 102 .

[0050] In other examples, the augmentation system 208 can communicate and exchange data with another augmentation system 208 on another client device 102 and with a server via the network 112. The data exchanged (e.g., during a video call between multiple users or participants) may include: a session identifier identifying a shared AR session; a transformation between a first client device 102 and a second client device 102 (e.g., multiple client devices 102, including the first device and the second device) for aligning the shared AR session to a common origin; a common coordinate system; functionality (e.g., commands for activating functions), and other payload data (e.g., text, audio, video, or other multimedia data).

[0051] The augmentation system 208 sends the transformation to the second client device 102 so that the second client device 102 can adjust the AR coordinate system based on the transformation. In this way, the first client device 102 and the second client device 102 synchronize their coordinate systems and frames to display the content in the AR session. Specifically, the augmentation system 208 calculates the origin of the second client device 102 in the coordinate system of the first client device 102. The augmentation system 208 can then determine an offset in the coordinate system of the second client device 102 based on the position of the origin in the coordinate system of the second client device 102 from the perspective of the second client device 102. The transformation is generated using the offset so that the second client device 102 generates AR content according to a common coordinate system with the first client device 102.

[0052] The augmentation system 208 can communicate with the client device 102 to establish an individual or shared AR session. The augmentation system 208 can also be coupled to the messaging server 118 to establish an electronic group communication session (e.g., group chat, instant messaging, video call, group video call, etc.) for the client device 102 in the shared AR session. The electronic group communication session can be associated with a session identifier provided by the client device 102 to obtain access to the electronic group communication session and the shared AR session. In one example, the client device 102 first obtains access to the electronic group communication session, and then obtains a session identifier in the electronic group communication session that allows the client device 102 to access the shared AR session. In some examples, the client device 102 is able to access the shared AR session without the assistance of the augmentation system 208 in the application server 114 or communication with the augmentation system 208 in the application server 114.

[0053] The mapping system 210 provides various geo-location functions and supports presentation of map-based media content and messages by the messaging client 104. For example, the mapping system 210 enables display of (e.g., stored in a database such as ... Figure 3The user icons or avatars (in the profile data 316 shown) are displayed to indicate the current or past locations of the user's "friends", as well as media content (e.g., a collection of messages including photos and videos) generated by such friends within the context of the map. For example, messages posted by the user to the messaging system 100 from a particular geographic location can be displayed to the "friends" of the particular user on the map interface of the messaging client 104 within the context of that particular location on the map. The user can also share his or her location and status information with other users of the messaging system 100 via the messaging client 104 (e.g., using appropriate status avatars), where the location and status information is similarly displayed to the selected user within the context of the map interface of the messaging client 104.

[0054] The gaming system 212 provides various gaming functions within the context of the messaging client 104. The messaging client 104 provides a gaming interface that provides a list of available games (e.g., web-based games or web-based applications) 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. The messaging system 100 also enables a particular user to invite other users to participate in playing a particular game by sending an invitation to such other users from the messaging client 104. The messaging client 104 also supports both voice messaging and text messaging within the context of playing games (e.g., chatting), provides leaderboards for games, and also supports providing in-game rewards (e.g., game coins and items).

[0055] The external resource system 220 provides an interface for communicating with an external application server 110 to launch or access external resources to the messaging client 104. Each external resource (application) server 110 hosts, for example, an application based on a markup language (e.g., HTML5) or a small-scale version of an external application (e.g., a game, utility, payment, or ride-sharing application external to the messaging client 104). The messaging client 104 can launch the web-based resource by accessing an HTML5 file from an external resource (application) server 110 associated with a web-based resource (e.g., application). In some examples, the application hosted by the external resource server 110 is programmed in JavaScript using a software development kit (SDK) provided by the messaging server 118. The SDK includes an application programming interface (API) with functions that can be called or activated by a web-based application. In some examples, the messaging server 118 includes a JavaScript library that provides access to certain user data of the messaging client 104 to a given third-party resource. HTML5 is used as an example technology for programming the game, but applications and resources programmed based on other technologies may be used.

[0056] In order to integrate the functionality of the SDK into a web-based resource, the SDK is downloaded from the messaging server 118 by the external resource (application) server 110 or received in other ways by the external resource (application) server 110. Once downloaded or received, the SDK is included as part of the application code of the web-based external resource. The code of the web-based resource can then call or activate certain functions of the SDK to integrate the features of the messaging client 104 into the web-based resource.

[0057] The SDK stored on the messaging server 118 effectively provides a bridge between external resources (e.g., a third party or external application 109 or applet and a messaging client 104). This provides users with a seamless experience of communicating with other users on the messaging client 104 while retaining the look and feel of the messaging client 104. In order to bridge the communication between the external resources and the messaging client 104, in some examples, the SDK facilitates the communication between the external resource server 110 and the messaging client 104. In some examples, the WebViewJavaScriptBridge running on the client device 102 establishes two one-way communication channels between the external resources and the messaging client 104. Messages are sent asynchronously via these communication channels between the external resources and the messaging client 104. Each SDK function call is sent as a message and a callback. Each SDK function is implemented by constructing a unique callback identifier and sending a message with the callback identifier.

[0058] By using the SDK, not all information from the messaging client 104 is shared with the external resource server 110. The SDK limits which information is shared based on the needs of the external resource. In some examples, each external resource server 110 provides an HTML5 file corresponding to a web-based external resource to the messaging server 118. The messaging server 118 can add a visual representation (e.g., a box design or other graphics) of the web-based external resource in the messaging client 104. Once the user selects the visual representation or instructs the messaging client 104 to access the features of the web-based external resource through the GUI of the messaging client 104, the messaging client 104 obtains the HTML5 file and instantiates the resources required to access the features of the web-based external resource.

[0059] The messaging client 104 presents a graphical user interface (e.g., a login page or title screen) for the external resource. During, before, or after presenting the login page or title screen, the messaging client 104 determines whether the launched external resource has been previously authorized to access the user data of the messaging client 104. In response to determining that the launched external resource has been previously authorized to access the user data of the messaging client 104, the messaging client 104 presents another graphical user interface of the external resource, which includes the functions and features of the external resource. In response to determining that the launched external resource has not been previously authorized to access the user data of the messaging client 104, after a threshold time period (e.g., 3 seconds) of displaying the login page or title screen of the external resource, the messaging client 104 slides up a menu for authorizing the external resource to access the user data (e.g., animating the menu to emerge from the bottom of the screen to the middle or other portion of the screen). The menu identifies the type of user data that the external resource will be authorized to use. In response to receiving the user selection of the accept option, the messaging client 104 adds the external resource to the list of authorized external resources and enables the external resource to access the user data from the messaging client 104. In some examples, the external resource is authorized to access the user data by the messaging client 104 according to the OAuth 2 framework.

[0060] The messaging client 104 controls the type of user data shared with the external resource based on the type of external resource that is authorized. For example, access to a first type of user data (e.g., only a two-dimensional avatar of a user with or without different avatar characteristics) is provided to an external resource including a full-scale external application (e.g., a third party or external application 109). As another example, access to a second type of user data (e.g., payment information, a two-dimensional avatar of a user, a three-dimensional avatar of a user, and an avatar with various avatar characteristics) is provided to an external resource including a small-scale version of an external application (e.g., a web-based version of a third-party application). Avatar characteristics include different ways to customize the look and feel of an avatar (e.g., different poses, facial features, clothing, etc.).

[0061] The AR element positioning system 224 may receive a request to access an AR experience associated with multiple AR elements. The AR element positioning system 224 may add one or more AR elements to a first image captured by the client device 102, the first image depicting a real-world object. The AR element positioning system 224 may store data representing the position of one or more AR elements relative to the real-world object. The data may be retained after the AR experience is terminated. The AR element positioning system 224 may receive a request to resume the AR experience after the AR experience has been terminated. In response to receiving the request to resume the AR experience, the AR element positioning system 224 may access the data stored before the AR experience was terminated to generate a display of the AR experience that depicts one or more AR elements at a specific location within the second image. This may result in consistent presentation of the AR experience and the associated AR elements of the AR experience across devices and across times or instances accessed after the AR experience is terminated or closed.

[0062] The AR element positioning system 224 can allow AR developers to create AR experiences with persistent AR elements or assets. AR elements can include any combination of three-dimensional mesh objects, two-dimensional meshes, machine learning models, sounds, or videos. The AR element positioning system 224 can present a user interface for the AR developer platform. The user interface can be used to select which AR elements will save their positions after the AR experience is terminated or closed. The graphical user interface presents a list of AR elements associated with the AR experience, and includes a first option associated with a first AR element in the AR element list, so that the position data of the first AR element is stored after the AR experience is terminated in response to the selection of the first option. The graphical user interface also includes a second option associated with a second AR element in the AR element list, so that the position data of the second AR element is prevented from being stored after the AR experience is terminated in response to the selection of the second option. This provides developers with greater flexibility to create useful, interesting, and engaging AR experiences without being limited by the resource constraints of the messaging application and / or client device running the AR experience.

[0063] Data Architecture

[0064] Figure 3 is a schematic diagram illustrating a data structure 300 that may be stored in a database 126 of a messaging server system 108 according to some examples. Although the contents of the database 126 are illustrated as including several tables, it will be appreciated that data may be stored in other types of data structures (e.g., in an object-oriented database).

[0065] Database 126 includes message data stored in message table 302. For any particular message, the message data includes at least message sender data, message recipient (or receiver) data, and payload. Figure 4 Additional details regarding information that may be included in a message and included within the message data stored in message table 302 are described.

[0066] The entity table 306 stores entity data and is linked (e.g., by reference) to the entity graph 308 and profile data 316. The entities whose records are maintained within the entity table 306 may include individuals, corporate entities, organizations, objects, places, events, etc. Regardless of the entity type, any entity about which the messaging server system 108 stores data may be an identified entity. Each entity is provided with a unique identifier as well as an entity type identifier (not shown).

[0067] The entity graph 308 stores information about relationships and associations between entities. Such relationships may be social, professional (e.g., working in a common company or organization), interest-based, or activity-based, by way of example only.

[0068] Profile data 316 stores multiple types of profile data about a particular entity. Based on the privacy settings specified by the particular entity, profile data 316 can be selectively used and presented to other users of the messaging system 100. In the case where the entity is a person, profile data 316 includes, for example, a user name, phone number, address, settings (e.g., notification and privacy settings), and an avatar representation (or a collection of such avatar representations) selected by the user. A particular user can then selectively include one or more of these avatar representations within the content of messages transmitted via the messaging system 100 and on a map interface displayed to other users by the messaging client 104. The collection of avatar representations can include a "status avatar" that presents a graphical representation of a status or activity that a user may choose to convey at a particular time.

[0069] Where the entity is a group, profile data 316 for the group may similarly include one or more avatar representations associated with the group, in addition to the group name, members, and various settings for the relevant group (eg, notifications).

[0070] Database 126 also stores enhancement data, such as overlays or filters, in enhancement table 310. Enhancement data is associated with and applied to videos (data for videos is stored in video table 304) and images (data for images is stored in image table 312).

[0071] The database 126 may also store data related to individual and shared AR sessions. The data may include data transmitted between an AR session client controller of a first client device 102 and another AR session client controller of a second client device 102, and data transmitted between an AR session client controller and an augmented system 208. The data may include data for establishing a common coordinate system for a shared AR scene, transformations between devices, session identifiers, images depicting the body, skeletal joint positions, wrist joint positions, feet, and the like.

[0072] In one example, a filter is an overlay displayed as an overlay on an image or video during presentation to a recipient user. The filter can be of various types, including a user-selected filter from a set of filters presented to a sending user by the messaging client 104 when the sending user is composing a message. Other types of filters include geolocation filters (also referred to as geofilters), which can be presented to a sending user based on a geographic location. For example, a geolocation filter specific to a nearby or specific location can be presented by the messaging client 104 within a user interface based on geographic location information determined by a global positioning system (GPS) unit of the client device 102.

[0073] Another type of filter is a data filter that can be selectively presented to the sending user by the messaging client 104 based on other input or information collected during the message creation process by the client device 102. Examples of data filters include the current temperature at a particular location, the current speed the sending user is traveling, the battery life of the client device 102, or the current time.

[0074] Other augmented data that may be stored in the image table 312 include augmented reality content items (eg, corresponding to an applied augmented reality experience). Augmented reality content items or augmented reality items may be real-time special effects and sounds that may be added to an image or video.

[0075] As described above, augmented data includes augmented reality content items, overlays, image transformations, AR images, AR logos or badges, and similar items involving modifications that can be applied to image data (e.g., videos or images). This includes real-time modifications that modify the image when it is captured using a device sensor (e.g., one or more cameras) of the client device 102 and then display the image with the modification on the screen of the client device 102. This also includes modifications to stored content (e.g., video clips in a gallery that can be modified). For example, in a client device 102 that can access multiple augmented reality content items, a user can use a single video clip with multiple augmented reality content items to see how different augmented reality content items will modify the stored clips. For example, by selecting different augmented reality content items for the content, multiple augmented reality content items that apply different pseudo-random movement models can be applied to the same content. Similarly, real-time video capture can be used with the modifications shown to show how the video image currently captured by the sensor of the client device 102 will modify the captured data. Such data may be displayed only on the screen and not stored in memory, or the content captured by the device sensors may be recorded and stored in memory with or without modification (or both). In some systems, a preview feature may simultaneously show how different augmented reality content items will look in different windows in the display. This may, for example, enable viewing of multiple windows with different pseudo-random animations on the display at the same time.

[0076] Thus, data and various systems using augmented reality content items or other such transformation systems using the data to modify content may involve: detection of objects (e.g., faces, hands, bodies, cats, dogs, surfaces, objects, etc.) in video frames; tracking of such objects as they leave, enter, and move around the field of view; and modifying or transforming such objects as they are tracked. In various examples, different methods for implementing such transformations may be used. Some examples may involve: generating a three-dimensional mesh model of one or more objects, and using transformations and animated textures of the models within a video to implement the transformations. In other examples, tracking of points on an object may be utilized to place an image or texture (which may be two-dimensional or three-dimensional) at the tracked location. In yet another example, neural network analysis of video frames may be used to place an image, model, or texture in content (e.g., an image or frame of a video). Thus, augmented reality content items refer both to images, models, and textures used to create transformations in content, and to additional modeling and analysis information required to implement such transformations using object detection, tracking, and placement.

[0077] Real-time video processing can be performed using any kind of video data (e.g., video streams, video files, etc.) stored in the memory of any kind of computerized system. For example, a user can load a video file and save it in the memory of the device, or a sensor of the device can be used to generate a video stream. In addition, any object, such as human faces and body parts, animals, or non-living things (e.g., chairs, cars, or other objects) can be processed using computer animation models.

[0078] In some examples, when a specific modification is selected together with the content to be transformed, the elements to be transformed are identified by a computing device, and then if the elements are present in the frame of the video, they are detected and tracked. The elements of the object are modified according to the modification request, thereby transforming the frame of the video stream. For different types of transformations, the transformation of the frame of the video stream can be performed by different methods. For example, for a frame transformation that mainly involves changing the form of the elements of the object, the feature points of each element of the object are calculated (for example, using an active shape model (Active Shape Model, ASM) or other known methods). Then, a grid based on the feature points is generated for each element of at least one element of the object. The grid is used for the subsequent stage of tracking the elements of the object in the video stream. During the tracking process, the grid mentioned for each element is aligned with the position of each element. Then, additional points are generated on the grid. A first group of first points is generated for each element based on the modification request, and a group of second points is generated for each element based on the group of first points and the modification request. Then, the frame of the video stream can be transformed by modifying the elements of the object based on the group of first points, the group of second points and the grid. In such a method, the background of the modified object may also be changed or distorted by tracking and modifying the background of the modified object.

[0079] In some examples, a transformation that changes some areas of an object using elements of an object can be performed by calculating feature points for each element of the object and generating a grid based on the calculated feature points. Points are generated on the grid, and then various areas based on the points are generated. The elements of the object are then tracked by aligning the area for each element with the position for each element of at least one element, and the properties of the area can be modified based on the modification request, thereby transforming the frame of the video stream. Depending on the specific modification request, the properties of the mentioned area can be transformed in different ways. Such modifications may involve changing the color of the area; removing at least some parts of the area from the frame of the video stream; including one or more new objects into the area based on the modification request; and modifying or distorting the elements of the area or object. In various examples, any combination of such modifications or other similar modifications may be used. For certain models to be animated, some feature points may be selected as control points for determining the entire state space of options for model animation.

[0080] In some examples of computer animation models that use face detection to transform image data, faces are detected on an image using a specific face detection algorithm (e.g., Viola-Jones). An active shape model (ASM) algorithm is then applied to the face region of the image to detect facial feature reference points.

[0081] Other methods and algorithms suitable for face detection can be used. For example, in some examples, landmarks are used to locate features, and the landmarks represent distinguishable points that are present in most of the images considered. For example, for facial landmarks, the location of the left pupil can be used. If the initial landmarks are not identifiable (for example, when a person is wearing an eye patch), secondary landmarks can be used. Such a landmark identification process can be used for any such object. In some examples, a set of landmarks forms a shape. The coordinates of the points in the shape can be used to represent the shape as a vector. A similarity transformation (which allows translation, scaling, and rotation) that minimizes the average Euclidean distance between the shape points is used to align one shape with another shape. The average shape is the average of the aligned training shapes.

[0082] In some examples, a landmark search begins with an average shape that aligns with the location and size of a face determined by a global face detector. Such a search then repeats the steps of proposing tentative shapes by template matching the image texture around each point to adjust the location of the shape points, and then conforming the tentative shapes to a global shape model until convergence occurs. In some systems, template matching alone is unreliable, and the shape model pools the results of weak template matches to form a stronger overall classifier. The entire search is repeated at each level in the image pyramid from coarse to fine resolution.

[0083] The transformation system can capture an image or video stream on a client device (e.g., client device 102) and perform complex image manipulations locally on the client device 102 while maintaining an appropriate user experience, computational time, and power consumption. Complex image manipulations can include size and shape changes, emotional transitions (e.g., changing a face from a frown to a smile), state transitions (e.g., aging a subject, reducing apparent age, changing gender), style transitions, application of graphical elements, and any other suitable image or video manipulations enabled by a convolutional neural network that has been configured to execute efficiently on the client device 102.

[0084] In some examples, a computer animation model for transforming image data can be used by a system in which a user can capture an image or video stream of the user (e.g., a selfie) using a client device 102 having a neural network, where the neural network operates as part of a messaging client 104 operating on the client device 102. A transformation system operating within the messaging client 104 determines the presence of a face within the image or video stream and provides a modification icon associated with the computer animation model for transforming the image data, or the computer animation model can exist in association with an interface described herein. The modification icon includes the following changes that can be used as a basis for modifying the user's face within the image or video stream as part of the modification operation. Once the modification icon is selected, the transformation system initiates a process of transforming the user's image to reflect the selected modification icon (e.g., generating a smiling face for the user). Once the image or video stream is captured and the specified modification is selected, the modified image or video stream can be presented in a graphical user interface displayed on the client device 102. The transformation system can implement a complex convolutional neural network on a portion of the image or video stream to generate and apply the selected modification. That is, a user can capture an image or video stream, and once a modification icon is selected, the modified result can be presented to the user in real time or near real time. In addition, the modification can be persistent while the video stream is being captured and the selected modification icon remains toggled. A machine learning neural network can be used to implement such modification.

[0085] The graphical user interface presenting the modifications performed by the transformation system can provide additional interactive options to the user. Such options can be based on the interface used to initiate content capture and selection of a specific computer animation model (e.g., initiated from a content creator user interface). In various examples, the modifications can be persistent after the modification icon is initially selected. The user can switch the modification on or off by tapping or otherwise selecting the face being modified by the transformation system, and store it for later viewing or browsing other areas of the imaging application. In the case where multiple faces are modified by the transformation system, the user can globally switch the modification on or off by tapping or selecting a single face modified and displayed within the graphical user interface. In some examples, individual faces in a group of multiple faces can be modified individually, or such modifications can be switched individually by tapping or selecting an individual face or a series of faces displayed within the graphical user interface.

[0086] The story table 314 stores data about a collection of messages and associated image, video or audio data that are compiled into a collection (e.g., a story or gallery). The creation of a particular collection can be initiated by a particular user (e.g., each user whose record is maintained in the entity table 306). A user can create a "personal story" in the form of a collection of content that has been created and sent / broadcasted by the user. To this end, the user interface of the messaging client 104 may include a user-selectable icon to enable the sending user to add specific content to his or her personal story.

[0087] A collection may also constitute a "live story," which is a collection of content from multiple users that is created manually, automatically, or using a combination of manual and automatic techniques. For example, a "live story" may constitute a curated stream of user-submitted content from various locations and events. Users whose client devices have location services enabled and who are at a common location event at a particular time may be presented with the option to contribute content to a particular live story, for example, via the user interface of the messaging client 104. Live stories may be identified to the user by the messaging client 104 based on his or her location. The end result is a "live story" told from a community perspective.

[0088] Another type of content collection is called a "location story," which enables users whose client devices 102 are located in a particular geographic location (e.g., on a college or university campus) to contribute to a particular collection. In some examples, contributions to location stories may require secondary authentication to verify that the end user belongs to a particular organization or other entity (e.g., is a student on a university campus).

[0089] As mentioned above, the video table 304 stores video data, which in one example is associated with a message whose record is maintained within the message table 302. Similarly, the image table 312 stores image data, which is associated with a message whose message data is stored in the entity table 306. The entity table 306 can associate various enhancements from the enhancement table 310 with the various images and videos stored in the image table 312 and the video table 304.

[0090] Data communication architecture

[0091] Figure 4 is a schematic diagram illustrating the structure of a message 400 according to some examples, the message 400 being generated by a messaging client 104 for transmission to another messaging client 104 or a messaging server 118. The content of a particular message 400 is used to populate a message table 302, which is stored in a database 126 and accessible by a messaging server 118. Similarly, the content of the message 400 is stored in memory as "in transit" or "in flight" data of a client device 102 or an application server 114. The message 400 is shown to include the following example components:

[0092] Message identifier 402 : a unique identifier that identifies the message 400 .

[0093] Message text payload 404 : Text to be generated by a user via the user interface of the client device 102 and included in the message 400 .

[0094] Message image payload 406 : Image data captured by a camera component of the client device 102 or retrieved from a memory component of the client device 102 and included in the message 400 . Image data for a sent or received message 400 may be stored in the image table 312 .

[0095] Message video payload 408 : Video data captured by the camera component or retrieved from the memory component of the client device 102 and included in the message 400 . The video data for a message 400 that has been sent or received may be stored in the video table 304 .

[0096] Message audio payload 410 : audio data captured by a microphone or retrieved from a memory component of the client device 102 and included in the message 400 .

[0097] Message enhancement data 412 : Enhancement data (eg, filters, stickers, or other annotations or enhancements) representing enhancements to be applied to the message image payload 406 , message video payload 408 , or message audio payload 410 of the message 400 . The enhancement data for a sent or received message 400 may be stored in the enhancement table 310 .

[0098] Message duration parameter 414: A parameter value indicating the amount of time in seconds that the content of a message (eg, message image payload 406, message video payload 408, message audio payload 410) will be presented to or made accessible to a user via messaging client 104.

[0099] Message geolocation parameters 416: Geolocation data (e.g., latitude and longitude coordinates) associated with the content payload of the message. Multiple message geolocation parameter 416 values ​​may be included in the payload, each of which is associated with a content item included in the content (e.g., a specific image within a message image payload 406, or a specific video within a message video payload 408).

[0100] Message story identifier 418: An identifier value that identifies one or more content collections (e.g., a "story" identified in story table 314) associated with a particular content item in message image payload 406 of message 400. For example, an identifier value may be used to associate multiple images within message image payload 406 with each of multiple content collections.

[0101] Message tags 420: Each message 400 may be tagged with a plurality of tags, each of which indicates the subject of the content included in the message payload. For example, where a particular image included in the message image payload 406 depicts an animal (e.g., a lion), a tag value indicating the relevant animal may be included within the message tags 420. The tag values ​​may be manually generated based on user input, or may be automatically generated using, for example, image recognition.

[0102] • Message sender identifier 422: An identifier (eg, a messaging system identifier, an email address, or a device identifier) ​​that indicates the user of the client device 102 on which the message 400 was generated and from which the message 400 was sent.

[0103] • Message recipient identifier 424: An identifier (eg, a messaging system identifier, an email address, or a device identifier) ​​that indicates the user of the client device 102 to which the message 400 is addressed.

[0104] The content (e.g., value) of each component of message 400 may be a pointer to a location in a table in which the content data value is stored. For example, the image value in message image payload 406 may be a pointer to a location in image table 312 (or the address of a location in image table 312). Similarly, the value in message video payload 408 may point to data stored in video table 304, the value stored in message enhancement data 412 may point to data stored in enhancement table 310, the value stored in message story identifier 418 may point to data stored in story table 314, and the values ​​stored in message sender identifier 422 and message recipient identifier 424 may point to user records stored in entity table 306.

[0105] AR element positioning system

[0106] Figure 5 is a block diagram illustrating an example AR element positioning system 224 according to some examples. The AR element positioning system 224 includes an AR experience development module 500 , an AR asset location storage module 510 , and an AR asset generation module 520 .

[0107] The AR experience development module 500 may generate a user interface for presentation to an AR developer on an AR developer client device 102. The user interface may enable an AR developer to select an AR element to persist across instances of launching an AR experience. The AR asset location storage module 510 may generate a user interface for presentation to an end user on a client device 102. The user interface may enable the end user's client device 102 to access and load the AR elements of the selected AR experience, and to interact with such AR elements by modifying the display properties of the AR elements (e.g., changing their context) and / or modifying or anchoring the AR elements to a specific display location. The user interface may enable the client device 102 to close the AR experience and terminate the execution of the AR experience after the AR elements have been modified or anchored to the display location. Thereafter, the user interface may receive a user request to restart the AR experience (on the same client device 102 or on another client device 102), and may resume the display of the AR experience so that the AR elements are re-presented in the same context and / or at the same specific display location as previously displayed in the AR experience.

[0108] As referred to herein, an “AR experience package” or “AR package” refers to a set of AR elements (including standard AR elements and linked AR elements) and corresponding code that dictates the visual appearance, interactions, and behavior of each AR element. An AR package includes code required for a client device 102 to launch and execute an AR experience associated with the AR package.

[0109] In some examples, AR experience development module 500 receives a request to access a developer user interface from developer client device 102. AR experience development module 500 may receive login credentials from developer client device 102. AR experience development module 500 may search for an account associated with the login credentials, and may generate a graphical user interface associated with the account for presentation to developer client device 102. AR experience development module 500 may present multiple AR experience packages associated with the account in the graphical user interface. In some cases, an account is accessible to an organization, in which case multiple users within the organization may share access to the account and may view the same set of AR experience packages.

[0110] AR experience development module 500 may receive input from developer client device 102 selecting a given AR experience package. In response to receiving the input, AR experience development module 500 may present graphical user interface 600 ( Figure 6 ). The AR experience development module 500 may include an identifier of the AR experience package and a list of AR objects or AR elements 620 included in the AR experience package in the graphical user interface 600. The elements may include a 2D mesh, a 3D mesh, a video, an audio file, an image file, and / or a machine learning model. The AR experience development module 500 may receive an input that selects an option for persisting a given one of the AR objects or AR elements 620.

[0111] In response, the AR experience development module 500 presents a prompt that lists options for persistently storing a given one of the AR objects or AR elements 620. The prompt may include one or more fields for entering one or more conditions for persisting the AR object or AR element 620. For example, the conditions may specify a subscription level of the end user, a geographic region associated with the end user, a time of day, a type of AR experience, a geographic location, a level in a game application or AR experience, a view or depiction of a portion of a real-world environment, a request from the end user to enable persistence of the AR object or AR element, a time, a location tag, an image tag, or any other suitable condition. The prompt may also include a persist AR asset location option 630 and an avoid persist AR asset location option 632.

[0112] In some examples, one or more conditions may include a linked AR experience group. The linked AR experience group may use corresponding identifiers to identify different AR experiences. The linked AR experience group may be configured to share persistently stored data. That is, a first AR experience may generate a first set of persistently stored data associated with a given AR object or AR element. Thereafter, a second AR experience may be launched (after closing the first AR experience or together with the first AR experience). The second AR experience may be determined to be on the same linked AR experience group as the first AR experience. This may mean that the two AR experiences share at least one AR element or AR object. In this case, the second AR experience may obtain the first set of persistently stored data generated using the first AR experience. The second AR experience may then use the first set of persistently stored data to control and display the positioning and contextual information of the AR element or AR object displayed by the second AR experience.

[0113] In some examples, in response to receiving input from a developer selecting the persist AR asset position option 630, the AR experience development module 500 enables the AR experience to store data representing the position of an AR object or AR element or the context of the AR object or AR element after the AR experience is closed or terminated. Specifically, if a given AR object or AR element is associated with the enabled persist AR asset position option 630, the position data or context data associated with the AR object or AR element is stored by the client device 102 (on which the AR experience is launched) or a remote server. The position data or context data is later used by the same client device 102 or a different client device to re-render the given AR object or AR element at the same position within the display of the AR experience and / or with the same context information (e.g., the same modifications applied to the AR object or AR element).

[0114] In some examples, location data is generated by specifying or selecting a landmark depicted in an image to be included in a persistently stored object. Specifically, when the persistently stored data is available or the AR experience enabled for it is terminated, an image in which the AR element was last displayed is captured. The image is processed to identify landmarks corresponding to one or more real-world objects depicted in the image. Landmarks or identifiers of landmarks may be stored as part of the persistently stored data. In this way, when the same AR experience or a related AR experience is launched at a later time, the AR experience may process the real-time image to search for real-world objects depicted and corresponding to landmarks stored in the persistently stored data. When such a real-world object is detected in the image, the AR experience may place and position the AR element at the same placement or position relative to the real-world object as the AR element had at a previous time or instance when the AR experience was executed before the AR experience was terminated.

[0115] In some examples, position data is generated for inclusion in a persistently stored object by specifying or generating an object classifier for one or more real-world objects depicted in an image. Specifically, when the persistently stored data is available or the AR experience for which it is enabled is terminated, an image in which the AR element is last displayed is captured. The image is processed to generate one or more object classifiers for one or more real-world objects depicted in the image. The one or more object classifiers may be stored as part of the persistently stored data. In this way, when the same AR experience or a related AR experience is launched at a later time, the AR experience may process the real-time image to search for an object classifier of a real-world object depicted and corresponding to one or more object classifiers stored in the persistently stored data. When such a real-world object is detected in the image, the AR experience may place and position the AR element at the same placement or position that the AR element had relative to the real-world object at a previous time or instance when the AR experience was executed before the AR experience was terminated.

[0116] In some examples, in response to receiving input from the developer selecting option 632, AR experience development module 500 prohibits the AR experience from storing data representing the position of the AR object or AR element or the context of the AR object or AR element after the AR experience is closed or terminated. In this case, when the AR experience is launched by a given client device 102 and is closed or terminated, the AR objects or AR elements are re-rendered at the default position when the AR experience is subsequently used by the same client device 102 or a different client device.

[0117] In some examples, the AR object may correspond to a specific AR graphic that is displayed on the client device 102 and can be moved around on the client device 102. In this case, the client device 102 may receive a request from the end user to start an AR experience. In response, the client device 102 may present the specific AR graphic at a specific default display position. The client device 102 may detect input to move the specific AR graphic to a specific display position. The client device 102 may also receive input to modify the visual attributes of the specific AR graphic (e.g., the input may draw a graphic or text on the specific AR graphic, may adjust the color or style of the specific AR graphic, may adjust the orientation of the specific AR graphic, or any other suitable modification). Such modifications may be stored as context information for the specific AR graphic.

[0118] The client device 102 may detect or receive input requesting to close or terminate the AR experience. In response to the input, the client device 102 returns the user to the graphical user interface (e.g., a chat window) of the messaging client 104 and removes all content associated with the AR experience from the presentation. The client device 102 may access one or more conditions associated with a particular AR graphic based on input from the developer, which are stored as part of the AR package. The client device 102 may determine that at least one of the one or more conditions is met or satisfied. For example, the client device 102 may determine that the AR experience is in a list of related AR experiences. In this case, the client device 102 may access the persistently stored data when launching any of the listed AR experiences. This allows different types of AR experiences to share the same persistent data, so that a user can use one AR experience to place an AR object at a specific location or in a specific context, and launch a different AR experience to view the same or different AR object at a previously placed specific location or context.

[0119] In some cases, when one or more conditions are met, the client device 102 may access the AR package to determine whether the persist AR asset position option 630 has been set or selected for the particular AR graphic. In response to determining that the persist AR asset position option 630 has been set or selected for the particular AR graphic and / or one or more conditions are met or satisfied, the client device 102 communicates with the AR asset position storage module 510 to persistently store data associated with the particular AR graphic. The data may include any set of information that specifies the location of the particular AR graphic, such as relative to the location of one or more real-world objects depicted in an image captured by the client device 102 (before the AR experience was terminated). The data may also or alternatively include any set of information that represents contextual information about the particular AR graphic or modifications performed on the particular AR graphic.

[0120] The data may be maintained and stored locally by the client device 102. In some examples, the data is transmitted back to a server associated with the client device 102 and stored in an account of the client device 102. In some examples, the data is not shared or provided to the developer of the AR experience. In some examples, the data transmitted back to the server may be encrypted or otherwise protected.

[0121] At a later time (after the AR experience is closed or terminated), the client device 102 may receive input from the user to resume the AR experience. In some cases, the client device 102 may list multiple AR experiences available for launch. The client device 102 may determine whether any AR experience in the listed multiple AR experiences has been previously launched and terminated, and is associated with data that persistently stores position information or context information for one or more associated AR objects or AR elements. In response to identifying that the first AR experience is associated with data that persistently stores position information or context information for one or more associated AR objects or AR elements, the client device 102 may modify the visual attributes of the display of the icon or representation of the first AR experience relative to other AR experiences in the list that are not associated with persistently stored data (e.g., highlight or change font, or bold or visually distinguish).

[0122] In some examples, client device 102 may receive input from an end user selecting an icon or representation of a first AR experience. In response, client device 102 communicates with AR asset generation module 520 to restore the presentation of the first AR experience based on persistently stored data. Specifically, client device 102 provides an identifier of the user and the first AR experience. AR asset generation module 520 searches a database of persistently stored data based on the user identifier and the identifier of the first AR experience. In response to identifying persistently stored data associated with the user identifier and the identifier of the first AR experience, AR asset generation module 520 retrieves the persistently stored data.

[0123] The AR asset generation module 520 may receive a new image captured by the client device 102. The AR asset generation module 520 may process the new image based on the persistently stored data to determine whether any of the real-world objects or landmarks are depicted in the new image, or whether a landmark is depicted, and match it with the positioning information stored in the persistently stored data. In response to detecting a match between the real-world objects or landmarks depicted in the new image and the positioning information stored in the persistently stored data, the AR asset generation module 520 retrieves the corresponding AR object or AR element referenced in the persistently stored data. The AR asset generation module 520 automatically positions the retrieved AR object or AR element at a specific location within the new image relative to the real-world object or landmark depicted in the new image. In some examples, the AR object or AR element was previously positioned and anchored at a specific orientation and distance relative to a given building in the first image. The AR experience may have been turned off, and the positioning of the AR object or AR element relative to the given building is stored as part of the persistently stored data. When the same given building is later detected in a relaunched AR experience (after the AR experience was closed), the AR asset generation module 520 positions the same AR object or AR element at the same orientation and location as it was placed in the first image. This process can be performed automatically and seamlessly, and thereby provide the end user with a consistent view of the real world modified by the AR experience, even after the end user closes the AR experience and relaunches the AR experience on the same or a different device.

[0124] Figures 7 and 8 is a graphical representation of the output of the AR element positioning system 224 according to some examples. Figure 7 As shown, the client device 102 may present a user interface 700 corresponding to or generated by a first AR experience. The user interface 700 includes a first image captured or received by a camera of the client device 102. The first image depicts a first real-world object 710 and a second real-world object 712. The first AR experience may cause a first AR element 720 to be presented within the first image, for example, at a default position and with default visual attributes.

[0125] The client device 102 may receive input from a user to modify the position or visual attributes of an AR element. This causes the first AR experience to position the AR element 720 at a specific orientation and distance 730 relative to the first real-world object 710 and / or the second real-world object 712 (e.g., placement). The client device 102 may access configuration data (e.g., an AR package of the first AR experience) to determine whether persistent AR elements 720 have been enabled. If persistent AR elements 720 are enabled or in the case where persistent AR elements 720 are enabled, the client device 102 may store placement, position, and / or context information associated with the AR element 720 continuously or under certain conditions (e.g., closing or termination of the first AR experience). In some examples, the client device 102 also determines whether conditions for storing such placement, position, and / or context information are met. The client device 102 may store the placement, position, and / or context information as persistently stored data only when the conditions are met and / or the developer has enabled the option to persist the AR element 720.

[0126] In some examples, the client device 102 may receive input to close or terminate the first AR experience. In response, the client device 102 stores the placement, position, and / or context information in association with the user and the AR element 720 as persistently stored data. The placement, position, and / or context information may include an object classifier of the first real-world object 710, features of the first real-world object 710, 2D coordinates or 3D coordinates of the first real-world object 710 and / or the AR element 720, latitude and longitude coordinates or GPS coordinates of the first real-world object 710, and the like.

[0127] At a later time (on another day) after closing or terminating the first AR experience, client device 102 may receive input from the user to launch a second AR experience or the same first AR experience. Client device 102 may determine that the second AR experience is on a list associating the second AR experience with the first AR experience. In response, client device 102 may obtain any persistently stored data generated by the first AR experience.

[0128] like Figure 8 As shown, the client device 102 may present a user interface 800 corresponding to or generated by the first AR experience or the second AR experience. The user interface 800 includes a second image captured or received by a camera of the client device 102. The second image depicts a first real-world object 810 (which may be Figure 7 The first real-world object 710 previously depicted in the first image shown is the same as or related to the first real-world object 710) and the third real-world object 812 (which is different from Figure 7The first (or second) AR experience may enable an AR element 820 (which may be associated with a second real-world object 712 depicted in the first image). Figure 7 The first AR element 720 (the same as or related to the first AR element 720 depicted in the first image) is presented within the second image.

[0129] The first (or second) AR experience can access the persistently stored data and determine that the persistently stored data is associated with the AR element 820 and identifies the AR element 820. In this case, rather than placing the AR element 820 at a default location and having default visual attributes, the client device 102 positions or places the AR element 820 at a location defined or derived by the persistently stored data, and can also modify the visual attributes according to the attributes defined or derived by the persistently stored data. In some examples, the client device 102 automatically determines that the first real-world object 810 matches the real-world object specified in the persistently stored data. In response, the client device 102 obtains positioning information that specifies an orientation and distance relative to the first real-world object 810 at which the associated AR element 820 is displayed. The client device 102 then displays the AR element 820 at a distance and orientation 830 relative to the first real-world object 810 based on the positioning information. In this case, the distance and orientation 830 at which the AR element 820 is placed matches the distance and orientation 830 previously generated by the first AR experience. Figure 7 The specific orientation and distance 730 of the AR element 720 in FIG. 7A matches the AR element 720 in FIG.

[0130] Fig. 9 is a flowchart of a process 900 performed by the AR element positioning system 224 according to some examples. Although the flowchart may describe the operations as a sequential process, many of these operations may be performed in parallel or simultaneously. In addition, the order of the operations may be rearranged. When the operations of the process are completed, the process is terminated. A process may correspond to a method, a procedure, etc. The steps of a method may be performed in whole or in part, may be performed in combination with some or all of the steps in other methods, and may be performed by any number of different systems or any part thereof (e.g., a processor included in any system).

[0131] At operation 901 , as discussed above, the AR element positioning system 224 (eg, the client device 102 or a server) receives a request from a client device to access an AR experience.

[0132] At operation 902 , the AR element positioning system 224 adds one or more AR elements to a first image captured by a client device, the first image depicting a real-world object, as discussed above.

[0133] At operation 903 , as discussed above, the AR element positioning system 224 stores data representing the position of one or more AR elements relative to real-world objects, which is maintained after the AR experience is terminated.

[0134] At operation 904 , as discussed above, the AR element positioning system 224 receives a request to resume the AR experience after the AR experience has terminated.

[0135] At operation 905 , as discussed above, the AR element positioning system 224 , in response to receiving the request to resume the AR experience, accesses data stored before the AR experience was terminated to generate a display of the AR experience that depicts one or more AR elements at a specific location within the second image.

[0136] Machine structure

[0137] Fig.101000 within which instructions 1008 (e.g., software, programs, applications, applet, app, or other executable code) may be executed for causing the machine 1000 to perform any one or more of the methods discussed herein. For example, the instructions 1008 may cause the machine 1000 to perform any one or more of the methods described herein. The instructions 1008 transform a general-purpose, unprogrammed machine 1000 into a specific machine 1000 that is programmed to perform the functions described and illustrated in the manner described. The machine 1000 may operate as a standalone device or may be coupled (e.g., networked) to other machines. In a networked deployment, the machine 1000 may operate as 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 1000 may include, but is not 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 phone, a smart phone, a mobile device, a wearable device (e.g., a smart watch), 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 sequentially or otherwise executing instructions 1008 specifying actions to be taken by the machine 1000. In addition, although only a single machine 1000 is shown, the term "machine" should also be considered to include a collection of machines that individually or jointly execute instructions 1008 to perform any one or more of the methods discussed herein. For example, the machine 1000 may include any of the client devices 102 or a number of server devices that form part of the messaging server system 108. In some examples, the machine 1000 may also include both a client system and a server system, wherein certain operations of a particular method or algorithm are performed on the server side and certain operations of the particular method or algorithm are performed on the client side.

[0138] The machine 1000 may include a processor 1002, a memory 1004, and an input / output (I / O) component 1038 that may be configured to communicate with each other via a bus 1040. In an example, the processor 1002 (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 1006 that executes instructions 1008 and a processor 1010. The term "processor" is intended to include multi-core processors, which may include two or more independent processors (sometimes referred to as "cores") that may execute instructions simultaneously. Although Fig.10 Multiple processors 1002 are shown, but the machine 1000 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 multiple cores, or any combination thereof.

[0139] The memory 1004 includes a main memory 1012, a static memory 1014, and a storage unit 1016, which are all accessible by the processor 1002 via the bus 1040. The main memory 1012, the static memory 1014, and the storage unit 1016 store instructions 1008 that embody any one or more of the methodologies or functions described herein. The instructions 1008 may also reside, completely or partially, within the main memory 1012, within the static memory 1014, within a machine-readable medium within the storage unit 1016, within at least one of the processors 1002 (e.g., within a cache memory of a processor), or within any suitable combination thereof during execution thereof by the machine 1000.

[0140] The I / O components 1038 may include various components for receiving input, providing output, generating output, sending information, exchanging information, capturing measurements, etc. The specific I / O components 1038 included in a particular machine will depend on the type of machine. For example, a portable machine (e.g., a mobile phone) may include a touch input device or other such input mechanism, while a headless server machine will likely not include such a touch input device. It should be appreciated that the I / O components 1038 may include Fig.101024 and 1026. In various examples, the I / O components 1038 may include a user output component 1024 and a user input component 1026. The user output component 1024 may include a visual component (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)), an acoustic component (e.g., a speaker), a tactile component (e.g., a vibration motor, a resistance mechanism), other signal generators, etc. The user input component 1026 may include an alphanumeric input component (e.g., a keyboard, a touch screen configured to receive alphanumeric input, an optical keyboard, or other alphanumeric input component), a point-based input component (e.g., a mouse, a touch pad, a trackball, a joystick, a motion sensor, or other pointing instrument), a tactile input component (e.g., a physical button, a touch screen or other tactile input component that provides the location and force of a touch or touch gesture), an audio input component (e.g., a microphone), etc.

[0141] In other examples, I / O component 1038 may include biometric component 1028, motion component 1030, environment component 1032, or position component 1034, as well as various other components. For example, biometric component 1028 includes components for detecting expressions (e.g., hand expressions, facial expressions, voice expressions, body postures, or eye tracking), measuring biosignals (e.g., blood pressure, heart rate, body temperature, sweat, or brain waves), identifying people (e.g., voice recognition, retinal recognition, facial recognition, fingerprint recognition, or EEG-based recognition), etc. Motion component 1030 includes acceleration sensor components (e.g., accelerometers), gravity sensor components, and rotation sensor components (e.g., gyroscopes).

[0142] Environmental components 1032 include, for example, one or more cameras (with still image / photo and video capabilities), lighting sensor components (e.g., photometers), temperature sensor components (e.g., one or more thermometers that detect ambient temperature), humidity sensor components, pressure sensor components (e.g., barometers), 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 that detect concentrations of hazardous gases for safety or measure pollutants in the atmosphere), or other components that can provide indications, measurements, or signals corresponding to the surrounding physical environment.

[0143] With respect to cameras, client device 102 may have a camera system including, for example, a front-facing camera on a front surface of client device 102 and a rear-facing camera on a rear surface of client device 102. The front-facing camera may, for example, be used to capture still images and videos (e.g., “selfies”) of a user of client device 102, which may then be enhanced with the enhancement data (e.g., filters) described above. For example, the rear-facing camera may be used to capture still images and videos in a more conventional camera mode, where the images are similarly enhanced with the enhancement data. In addition to the front-facing camera and the rear-facing camera, client device 102 may also include a 360° camera for capturing 360° photos and videos.

[0144] Additionally, the camera system of the client device 102 may include dual rear cameras (e.g., a main camera and a depth sensing camera), or even triple, quad, or quintuple rear camera configurations on the front and back sides of the client device 102. For example, these multiple camera systems may include a wide-angle camera, an ultra-wide-angle camera, a telephoto camera, a macro camera, and a depth sensor.

[0145] The position component 1034 includes a position sensor component (e.g., a GPS receiver component), an altitude sensor component (e.g., an altimeter or barometer that detects air pressure, from which the altitude can be obtained), an orientation sensor component (e.g., a magnetometer), and the like.

[0146] A variety of technologies may be used to achieve communication. The I / O components 1038 also include a communication component 1036 that is operable to couple the machine 1000 to the network 1020 or the device 1022 via a corresponding coupling or connection. For example, the communication component 1036 may include a network interface component or other suitable device that interfaces with the network 1020. In other examples, the communication component 1036 may include a wired communication component, a wireless communication component, a cellular communication component, a near field communication (NFC) component, a Bluetooth component (e.g., Bluetooth low energy), a Wi-Fi component, and other communication components that provide communication via other modalities. The device 1022 may be any peripheral device of another machine or a variety of peripheral devices (e.g., a peripheral device coupled via USB).

[0147] In addition, the communication component 1036 can detect the identifier or include a component that can be operated to detect the identifier. For example, the communication component 1036 may include a radio frequency identification (RFID) tag reader component, an NFC smart tag detection component, an optical reader component (e.g., an optical sensor for detecting a one-dimensional barcode such as a universal product code (UPC) barcode, a multi-dimensional barcode such as a quick response (QR) code, an Aztec code, a data matrix, a data symbol (Dataglyph), a maximum code, PDF417, a super code, a UCCRSS-2D barcode, and other optical codes) or an acoustic detection component (e.g., a microphone for identifying a marked audio signal). In addition, various information can be derived via the communication component 1036, such as deriving a location via Internet Protocol (IP) geolocation, deriving a location via Wi-Fi signal triangulation, deriving a location via detecting an NFC beacon signal that can indicate a specific location, etc.

[0148] Various memories (e.g., main memory 1012, static memory 1014, and memory of processor 1002) and storage unit 1016 may store one or more sets of instructions and data structures (e.g., software) implemented or used by any one or more of the methods or functions described herein. When executed by processor 1002, these instructions (e.g., instructions 1008) cause various operations to implement the disclosed examples.

[0149] The instructions 1008 may be transmitted or received over the network 1020 using a transmission medium via a network interface device (e.g., a network interface component included in the communication component 1036) and using any of several well-known transfer protocols (e.g., Hypertext Transfer Protocol (HTTP)). Similarly, the instructions 1008 may be sent or received via a coupling (e.g., a peer-to-peer coupling) with the device 1022 using a transmission medium.

[0150] Software Architecture

[0151] Fig.11 1100 is a block diagram illustrating a software architecture 1104 that may be installed on any one or more of the devices described herein. The software architecture 1104 is supported by hardware, such as a machine 1102 including a processor 1120, a memory 1126, and an I / O component 1138. In this example, the software architecture 1104 may be conceptualized as a stack of layers, each of which provides specific functionality. The software architecture 1104 includes layers such as an operating system 1112, a library 1110, a framework 1108, and an application 1106. In operation, the application 1106 invokes an API call 1150 through the software stack and receives a message 1152 in response to the API call 1150.

[0152] The operating system 1112 manages hardware resources and provides public services. The operating system 1112 includes, for example, a core 1114, a service 1116, and a driver 1122. The core 1114 is used as an abstraction layer between the hardware and other software layers. For example, the core 1114 provides functions such as memory management, processor management (e.g., scheduling), component management, networking, and security settings. The service 1116 can provide other public services for other software layers. The driver 1122 is responsible for controlling the underlying hardware or connecting to the underlying hardware. For example, the driver 1122 may include a display driver, a camera driver, a Bluetooth or Bluetooth low energy driver, a flash drive, a serial communication driver (e.g., a USB driver), a WI-FI driver, an audio driver, a power management driver, etc.

[0153] The libraries 1110 provide a common low-level infrastructure used by the applications 1106. The libraries 1110 may include a system library 1118 (e.g., a C standard library) that provides functions such as memory allocation functions, string manipulation functions, mathematical functions, etc. In addition, the libraries 1110 may include an API library 1124, such as a media library (e.g., a library for supporting the presentation and manipulation of various media formats, such as Moving Picture Experts Group-4 (MPEG4), Advanced Video Coding (H.264 or AVC), Moving Picture Experts Group Layer-3 (MP3), Advanced Audio Coding (AAC), Adaptive Multi-Rate (AMR) audio codec, Joint Photographic Experts Group (JPEG or JPG), or Portable Network Graphics (PNG)), a graphics library (e.g., an OpenGL framework for presenting in two dimensions (2D) and three dimensions (3D) in graphical content on a display), a database library (e.g., SQLite providing various relational database functions), a web library (e.g., WebKit providing web browsing functions), etc. The library 1110 may also include various other libraries 1128 to provide many other APIs to the application 1106 .

[0154] The framework 1108 provides a common high-level infrastructure used by the applications 1106. For example, the framework 1108 provides various graphical user interface (GUI) functions, advanced resource management, and advanced location services. The framework 1108 can provide a wide range of other APIs that can be used by the applications 1106, some of which can be specific to a particular operating system or platform.

[0155] In an example, applications 1106 may include home applications 1136, contact applications 1130, browser applications 1132, book reader applications 1134, positioning applications 1142, media applications 1144, messaging applications 1146, game applications 1148, and various other applications such as external applications 1140. Applications 1106 are programs that execute functions defined in programs. Various programming languages ​​can be used to create one or more of the applications 1106 constructed in various ways, such as object-oriented programming languages ​​(e.g., Objective-C, Java, or C++) or procedural programming languages ​​(e.g., C or assembly language). In a specific example, external applications 1140 (e.g., applications developed using ANDROID or IOS software development kits (SDKs) by entities other than the supplier of a specific platform) can be mobile software running on a mobile operating system such as IOS, ANDROID, WINDOWSPhone, or another mobile operating system. In this example, external application 1140 may invoke API calls 1150 provided by operating system 1112 to facilitate the functionality described herein.

[0156] Glossary

[0157] "Carrier signal" refers to any intangible medium capable of storing, encoding or carrying instructions for execution by a machine and includes digital or analog communications signals or other intangible media to facilitate the transmission of such instructions. Instructions may be sent or received over a network using a transmission medium via a network interface device.

[0158] "Client Device" refers to any machine that connects 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, a desktop computer, a laptop computer, a portable digital assistant (PDA), a smart phone, a tablet computer, an ultrabook, a netbook, a laptop computer, a multiprocessor system, a microprocessor-based or programmable consumer electronics product, a game console, a set-top box, or any other communications device that a user may use to access a network.

[0159] A "communication network" refers to one or more portions of a network, which 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 a public switched telephone network (PSTN), a plain old telephone service (POTS) network, a cellular telephone network, a wireless network, a Wi-Fi network, other types of networks, or a combination of two or more such networks. For example, a network or a portion of a network may include a wireless network or a cellular network, and the coupling may be a code division multiple access (CDMA) connection, a global system for mobile communications (GSM) connection, or other type of cellular or wireless coupling. In this example, the coupling can implement any of various types of data transmission technologies, such as single carrier radio transmission technology (1xRTT), evolution data optimized (EVDO) technology, general packet radio service (GPRS) technology, enhanced data rates for GSM evolution (EDGE) technology, the third generation partnership project (3GPP) including 3G, fourth generation wireless (4G) networks, universal mobile telecommunications system (UMTS), high speed packet access (HSPA), world wide interoperability for microwave access (WiMAX), long term evolution (LTE) standards, other data transmission technologies defined by various standard setting organizations, other long distance protocols, or other data transmission technologies.

[0160] "Component" means a device, physical entity, or logic having boundaries defined by function or subroutine calls, branch points, APIs, or other techniques that provide partitioning or modularization of specific processing or control functions. Components may be combined with other components via their interfaces to perform a machine process. A component may be a packaged functional hardware unit designed for use with other components and is part of a program that typically performs a specific one of the related functions.

[0161] Components may constitute software components (e.g., code implemented on a machine-readable medium) or hardware components. A "hardware component" is a tangible unit that is capable of performing certain operations and that can be configured or arranged in some physical manner. In various examples, one or more computer systems (e.g., stand-alone computer systems, client computer systems, or server computer systems) or one or more hardware components of a computer system (e.g., a processor or group of processors) may be configured by software (e.g., an application or application portion) as hardware components that operate to perform certain operations described herein.

[0162] Hardware components can also be implemented mechanically, electronically or in any suitable combination thereof. For example, hardware components can include dedicated circuits or logic that are permanently configured to perform certain operations. Hardware components can be dedicated processors, such as field programmable gate arrays (FPGAs) or application specific integrated circuits (ASICs). Hardware components can also include programmable logic or circuits that are temporarily configured to perform certain operations by software. For example, hardware components can include software executed by general-purpose processors or other programmable processors. Once configured by such software, hardware components become a specific machine (or a specific component of a machine) that is uniquely customized to perform the configured function, and are no longer general-purpose processors. It will be recognized that it can be decided whether to implement hardware components mechanically in a dedicated and permanently configured circuit or in a temporarily configured circuit (e.g., configured by software) for cost and time considerations. Therefore, the phrase "hardware components" (or "hardware-implemented components") should be understood to include tangible entities, i.e., entities that are physically constructed, permanently configured (e.g., hardwired) or temporarily configured (e.g., programmed) to operate in some way or perform certain operations described herein.

[0163] Consider an example where hardware components are temporarily configured (e.g., programmed), without configuring or instantiating each of the hardware components at any one time. For example, where the hardware components include a general-purpose processor that is configured by software to become a special-purpose processor, the general-purpose processor can be configured into different special-purpose processors (e.g., including different hardware components) at different times. The software accordingly configures one or more specific processors to, for example, constitute a specific hardware component at one time and constitute different hardware components at different times.

[0164] Hardware components can provide information to other hardware components and receive information from other hardware components. Therefore, the described hardware components can be considered to be coupled in communication. In the case of multiple hardware components simultaneously, communication can be realized by signal transmission (for example, by appropriate circuits and buses) between or among two or more hardware components in the hardware components. In the example that multiple hardware components are configured or instantiated at different times, the communication between such hardware components can be realized, for example, by storing information in a memory structure that multiple hardware components can access and retrieving information in the memory structure. For example, a hardware component can perform an operation and store the output of the operation in a memory device coupled in communication with it. Then, other hardware components can access the memory device at a subsequent time to retrieve the stored output and process it. The hardware component can also initiate communication with an input device or an output device, and can operate on resources (for example, a collection of information).

[0165] The various operations of the example methods described herein may be performed at least in part by one or more processors that are temporarily configured (e.g., by software) or permanently configured to perform related operations. Whether temporarily configured or permanently configured, such a processor may constitute a processor-implemented component that operates to perform one or more operations or functions described herein. As used herein, a "processor-implemented component" refers to a hardware component implemented using one or more processors. Similarly, the method described herein may be implemented at least in part by a processor, wherein a specific one or more processors are examples of hardware. For example, at least some operations of the method may be performed by one or more processors 1002 or a processor-implemented component. In addition, one or more processors may also operate to support the execution of related operations in a "cloud computing" environment or as a "software as a service" (SaaS) operation. For example, at least some of the operations may be performed by a group of computers (as an example of a machine including a processor), wherein these operations may be accessed via a network (e.g., the Internet) and via one or more appropriate interfaces (e.g., API). The execution of certain operations may be distributed between processors, not just residing in a single machine, but deployed across several machines. In some examples, the processor or processor-implemented components may be located in a single geographic location (e.g., in a home environment, an office environment, or a server farm). In other examples, the processor or processor-implemented components may be distributed across several geographic locations.

[0166] "Computer-readable storage media" refers to both machine storage media and transmission media. Thus, the term includes both storage devices / media and carrier / 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.

[0167] "Transient messages" are messages that are accessible for a limited duration. Transient messages can be text, images, videos, etc. The access time for a transient message can be set by the sender of the message. Alternatively, the access time can be a default setting or a setting specified by the recipient. Regardless of the setting technique, the message is transient.

[0168] "Machine storage media" refers to a single or multiple storage devices and media (e.g., centralized or distributed databases, and associated caches and servers) that store executable instructions, routines, and data. Thus, the term should be considered to include, but is not limited to, solid-state memory and optical and magnetic media, including memory internal or external to the processor. Specific examples of machine storage media, computer storage media, and device storage media include: non-volatile memory, including, for example, semiconductor memory devices such as 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 media," "device storage media," and "computer storage media" mean the same thing and may be used interchangeably in this disclosure. The terms "machine storage media," "computer storage media," and "device storage media" expressly exclude carrier waves, modulated data signals, and other such media, at least some of which are encompassed by the term "signal media."

[0169] “Non-transitory computer-readable storage medium” refers to tangible media capable of storing, encoding, or carrying instructions to be executed by a machine.

[0170] "Signal medium" refers to any intangible medium that is capable of storing, encoding or carrying instructions to be executed by a machine, and includes digital or analog communication signals or other intangible media that facilitate the communication of software or data. The term "signal medium" should be deemed to include any form of modulated data signals, carrier waves, etc. The term "modulated data signal" refers to a signal that has one or more of its characteristics set or changed in order to encode information therein. The terms "transmission medium" and "signal medium" refer to the same thing and may be used interchangeably in this disclosure.

[0171] Changes and modifications may be made to the disclosed examples without departing from the scope of the present disclosure. These and other changes or modifications are intended to be included within the scope of the present disclosure as expressed in the appended claims.

Claims

1. A method, include: receiving a request from a client device to access an augmented reality (AR) experience; adding one or more AR elements to a first image captured by the client device, the first image depicting a real-world object; storing data representing a position of the one or more AR elements relative to the real-world object, the data being retained after the AR experience is terminated; After the AR experience has terminated, receiving a request to resume the AR experience; as well as In response to receiving the request to resume the AR experience, accessing data stored prior to termination of the AR experience to generate a display of the AR experience that depicts the one or more AR elements at the specific location within the second image.

2. The method according to claim 1, in, The data is stored on a remote server associated with the client device.

3. The method according to any one of claims 1 to 2, in, The AR experience is initiated by a messaging application implemented on the client device.

4. The method according to any one of claims 1 to 3, further comprising: include: A request to terminate the AR experience is received, wherein the data is stored in a local storage of the client device in response to receiving the request to terminate the AR experience.

5. The method according to any one of claims 1 to 4, in, The client device is a first client device, and wherein the AR experience is resumed on a second client device, wherein the second image was captured by the second client device.

6. The method according to any one of claims 1 to 5, further comprising: include: A request to terminate the AR experience is received, wherein, in response to receiving the request to terminate the AR experience, the data is sent to a remote server.

7. The method according to any one of claims 1 to 6, further comprising: include: obtaining an identifier of the real-world object from the stored data; detecting the real-world object in the second image based on the identifier obtained from the stored data; as well as The one or more AR elements are positioned in the second image based on placement of the real-world object in the second image.

8. The method according to any one of claims 1 to 7, in, The specific position corresponds to a position of the one or more AR elements relative to the real-world object depicted in the first image.

9. The method according to any one of claims 1 to 8, in, The AR experience is a first AR experience, and further includes: After terminating the first AR experience, receiving a request to start a second AR experience on the client device; Determining that the second AR experience is related to the first AR experience; and In response to determining that the second AR experience is related to the first AR experience, the one or more AR elements are automatically positioned within the second AR experience using the stored data.

10. The method according to any one of claims 1 to 9, further comprising: include: determining that the real-world object corresponds to a landmark; storing the landmark as part of the data; as well as The one or more AR elements are caused to be displayed in a subsequent presentation of the AR experience in which the landmark appears.

11. The method according to any one of claims 1 to 10, further comprising: include: generating an object classifier based on the real-world object depicted in the first image; storing the object classifier as part of the data; obtaining an object classifier for one or more objects depicted in the second image; determining that the object classifier in the data matches a given one of the object classifiers; as well as In response to determining that the object classifier in the data matches a given one of the object classifiers, causing the one or more AR elements to be displayed in the second image.

12. The method according to claim 11, in, The one or more AR elements are displayed at the same position in the second image relative to a given one of the object classifiers as in the first image.

13. The method according to any one of claims 1 to 12, in, The data includes location information of the real-world object, the location information including at least one of: a latitude and longitude of the real-world object, global positioning system coordinates of the real-world object, a bounding box associated with the real-world object, an object type of the real-world object, or a three-dimensional match of the real-world object.

14. The method according to any one of claims 1 to 13, in, The AR experience is developed using an AR developer platform that includes a graphical user interface that enables storage of position data of AR elements after termination of the AR experience.

15. The method according to claim 14, in, The graphical user interface comprises: a list of AR elements associated with the AR experience, the graphical user interface comprising a first option associated with a first AR element in the list of AR elements, the first option causing, in response to selection of the first option, storage of position data for the first AR element after termination of the AR experience, the graphical user interface comprising a second option associated with a second AR element in the list of AR elements, the second option preventing, in response to selection of the second option, storage of position data for the second AR element after termination of the AR experience.

16. A system, include: processor; as well as A memory component, wherein the memory component stores instructions, and when the instructions are executed by the processor, the processor performs operations, the operations comprising: receiving a request from a client device to access an augmented reality (AR) experience; adding one or more AR elements to a first image captured by the client device, the first image depicting a real-world object; storing data representing a position of the one or more AR elements relative to the real-world object, the data being retained after the AR experience is terminated; After the AR experience has terminated, receiving a request to resume the AR experience; and In response to receiving the request to resume the AR experience, accessing the data stored before the AR experience was terminated to generate a display of the AR experience that depicts the one or more AR elements at the specific location within the second image.

17. The system according to claim 16, in, The data is stored on a remote server associated with the client device.

18. A system according to any one of claims 16 to 17, in, The AR experience is initiated by a messaging application implemented on the client device.

19. The system according to any one of claims 16 to 18, wherein the operation further include: A request to terminate the AR experience is received, wherein the data is stored in a local storage of the client device in response to receiving the request to terminate the AR experience.

20. A non-transitory computer-readable storage medium having instructions stored thereon, wherein when the instructions are executed by a processor, the processor is caused to perform an operation, wherein the operation include: receiving a request from a client device to access an augmented reality (AR) experience; adding one or more AR elements to a first image captured by the client device, the first image depicting a real-world object; storing data representing a position of the one or more AR elements relative to the real-world object, the data being retained after the AR experience is terminated; After the AR experience has terminated, receiving a request to resume the AR experience; as well as In response to receiving the request to resume the AR experience, accessing the data stored prior to terminating the AR experience to generate a display of the AR experience that depicts the one or more AR elements at the specific location within the second image.

Images