Electronic transaction activated augmented reality experience

Abstract

Aspects of the disclosure relate to systems and methods for performing operations comprising: receiving, by a client device implementing a messaging application, a request to access a display of a plurality of augmented reality experiences; retrieving a plurality of identifiers for each of the plurality of augmented reality experiences; determining that a given augmented reality experience of the plurality of augmented reality experiences is associated with an access restriction; in response to determining that the given augmented reality experience is associated with the access restriction, modifying a given identifier of the plurality of identifiers that is associated with the given augmented reality experience; and generating a graphical user interface to be displayed on the client device, the graphical user interface comprising the plurality of identifiers including the modified given identifier.

Description

[0001] Priority requirements

[0002] This application claims the benefit of priority to U.S. Provisional Application No. 63 / 124,234, filed December 11, 2020, and U.S. Patent Application No. 17 / 400,394, filed August 12, 2021, the entire contents of each of the aforementioned U.S. Provisional Application and U.S. Patent Application are incorporated herein by reference. Technical Field

[0003] This disclosure generally relates to the use of graphical elements provided by messaging applications. Background Technology

[0004] Modern user equipment offers messaging applications that allow users to exchange messages with each other. These messaging applications have recently begun to incorporate graphics into this communication. Users can choose from a variety of predefined graphics to incorporate into their communications. Attached Figure Description

[0005] In accompanying drawings that are not necessarily drawn to scale, similar reference numerals can describe similar parts in different views. To facilitate identification of any particular element or action being discussed, one or more of the most significant digits in the reference numerals refer to the drawing number in which the element was first introduced. Some non-limiting examples are shown in the figures of the accompanying drawings, in which:

[0006] Figure 1 It is a graphical representation of a networked environment in which the present disclosure can be deployed, based on some examples.

[0007] Figure 2 It is a graphical representation of a messaging system with both client-side and server-side functionalities, based on some examples.

[0008] Figure 3 It is a graphical representation based on examples such as data structures maintained in a database.

[0009] Figure 4 It is a graphical representation based on some example messages.

[0010] Figure 5A , Figure 5B , Figure 6 , Figure 7A , Figure 7B , Figure 8A , Figure 8B , Figure 9A and Figure 9B It is a graphical representation based on some examples of graphical user interfaces.

[0011] Figure 10This is a flowchart illustrating an example operation of a message sending and receiving application server according to an example implementation.

[0012] Figure 11 It is a graphical representation of a machine in the form of a computer system based on some examples, within which a set of instructions can be executed to cause the machine to perform any or more of the methods discussed herein.

[0013] Figure 12 It is a block diagram illustrating an example of a software architecture that can be implemented therein. Detailed Implementation

[0014] The following description includes systems, methods, techniques, instruction sequences, and computer program products for implementing illustrative embodiments of the present disclosure. In the following description, numerous specific details are set forth for purposes of explanation to provide an understanding of various embodiments. However, it will be apparent to those skilled in the art that embodiments can be practiced without these specific details. Generally, well-known examples of instructions, protocols, structures, and techniques do not need to be shown in detail.

[0015] Typically, users exchange messages with each other using messaging applications. Such applications allow users to select from a predefined list of images to send to each other. Users are increasingly using images to communicate with each other and convey their thoughts. However, finding the right image to convey a specific idea can be tedious and time-consuming. Specifically, users must manually search for specific images that convey a given message using keywords. This requires navigating multiple pages of information until the desired image is found. Given the complexity and time commitment involved in finding the right image, users are discouraged from using images for communication, as this leads to a waste of resources or underutilization.

[0016] The disclosed embodiments improve the efficiency of using electronic devices by providing a system that presents users with augmented reality experiences to enhance captured images or videos to be shared with another user in a messaging application. The disclosed embodiments provide a user interface that makes it easy for users to locate, use, and select augmented reality experiences to enhance captured images or videos. Some augmented reality experiences may be advanced experiences that include a set of specialized augmented reality items or features. User attention can be directed to such advanced experiences by displaying identifiers for these experiences in a modified or different manner than those for non-advanced experiences. In some implementations, advanced augmented reality experiences are associated with access restrictions. In such cases, the disclosed embodiments provide an efficient and intuitive user interface for removing such access restrictions and previewing such advanced experiences.

[0017] According to the disclosed implementation, a messaging application implemented by one or more processors of a client device receives a request to access the display of multiple augmented reality experiences. In response, the messaging application retrieves multiple identifiers for each of the multiple augmented reality experiences and determines that a given augmented reality experience is associated with access restrictions. In response, the messaging application modifies a given identifier among the multiple identifiers associated with the given augmented reality experience and generates a graphical user interface for display on the client device, the graphical user interface including multiple identifiers containing the modified given identifier.

[0018] In this way, the disclosed implementation improves the efficiency of using electronic devices by reducing the number of screens and interfaces that users must navigate to find augmented reality items to enhance images captured by the user and then share with other users. This reduces the device resources (e.g., processor cycles, memory, and power usage) required to complete tasks with the device.

[0019] Networked computing environment

[0020] Figure 1 This 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 client devices 102, each hosting several applications including messaging clients 104 and other external applications 109 (e.g., third-party applications). Each messaging client 104 is communicatively coupled via a network 112 (e.g., the Internet) to other instances of the messaging client 104 (e.g., hosted on corresponding other client devices 102), the messaging server system 108, and the external application server 110. The messaging client 104 can also communicate with the locally hosted third-party applications 109 using an application programming interface (API).

[0021] Message transceiver client 104 can communicate and exchange data with other message transceiver clients 104 and message transceiver server system 108 via network 112. The data exchanged between message transceiver clients 104 and between message transceiver client 104 and message transceiver server system 108 includes functions (e.g., commands to activate functions) and payload data (e.g., text, audio, video, or other multimedia data).

[0022] The message transceiver server system 108 can provide server-side functionality to a specific message transceiver client 104 via network 112. While some functions of the message transceiver system 100 are described herein as being performed by the message transceiver client 104 or by the message transceiver server system 108, the location of certain functions within the message transceiver client 104 or the message transceiver server system 108 can be a design choice. For example, it might be technically preferred that certain technologies and functions are initially deployed within the message transceiver server system 108, but later migrated to the message transceiver client 104 of the client device 102 with sufficient processing power.

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

[0024] Specifically, turning to message transceiver server system 108, application programming interface (API) server 116 is coupled to application server 114 and provides a programming interface to application server 114. Application server 114 is communicatively coupled to database server 120, which provides access to database 126, which stores data associated with messages processed by application server 114. Similarly, web server 128 is coupled to application server 114 and provides a web-based interface to application server 114. To this end, web server 128 processes incoming network requests via Hypertext Transfer Protocol (HTTP) and several other related protocols.

[0025] Application Programming Interface (API) server 116 receives and sends message data (e.g., commands and message payloads) between client device 102 and application server 114. Specifically, API server 116 provides a set of interfaces (e.g., routines and protocols) that message sending and receiving client 104 can call or query to activate the functionality of application server 114. Application Programming Interface (API) server 116 exposes various functions supported by application server 114, including: account registration; login functionality; sending messages from one messaging client 104 to another messaging client 104 via application server 114; sending media files (e.g., images or videos) from messaging client 104 to messaging server 118 and for possible access by another messaging client 104; setting up media data collections (e.g., stories); retrieving the friend list of the user of client device 102; retrieving such collections; retrieving messages and content; adding and deleting entities (e.g., friends) in an entity graph (e.g., a social graph); locating friends in a social graph; and opening application events (e.g., related to messaging client 104).

[0026] Application server 114 hosts several server applications and subsystems, including, for example, messaging server 118, image processing server 122, and social networking server 124. Messaging server 118 implements several messaging techniques and functions, which specifically relate to the aggregation and other processing of content (e.g., text and multimedia content) included in messages received from multiple instances of messaging client 104. As will be described in further detail, text and media content from multiple sources can be aggregated into content collections (e.g., referred to as stories or galleries). These collections are then made available to messaging client 104. Given the hardware requirements for such processing, additional processor- and memory-intensive data processing can also be performed by messaging server 118 on the server side.

[0027] Application server 114 also includes image processing server 122, which is dedicated to performing various image processing operations, typically relative to the payload of a message sent from or received at message transceiver server 118.

[0028] Image processing server 122 is used to implement the scanning function of augmented reality system 208. The scanning function includes activating and providing one or more augmented reality experiences on client device 102 when an image is captured by client device 102. Specifically, messaging application 104 on client device 102 can be used to activate a camera device. The camera device displays one or more live images or videos along with one or more icons or identifiers of the augmented reality experiences to the user. The user can select a given identifier from the identifiers to launch the corresponding augmented reality experience. Launching an augmented reality experience involves obtaining one or more augmented reality items associated with the experience and overlaying the augmented reality items onto the image or video being presented.

[0029] In one implementation, the augmented reality item moves around or tracks the depicted real-world object. For example, the augmented reality item could be a cosmetic item placed on a depicted real-world face. As the face moves around, accelerometer and gyroscope sensors of client device 102 provide measurements representing motion. This information is used to adjust the positioning of the augmented reality item relative to the face, such that the augmented reality item tracks the face's position in 3D and maintains its placement on the face as it moves around. In some implementations, initiation of the augmented reality experience includes a preview of the augmented reality experience. For example, the augmented reality experience could be a restricted access experience or a premium experience that can be purchased by a user (e.g., by exchanging a certain amount of virtual currency or tokens). When previewing such an augmented reality experience, only a subset of the augmented reality items (e.g., 2D images of the augmented reality items) is presented over the real-world object (e.g., the face). The 2D image does not track facial movement and does not update the positioning of the augmented reality item based on the accelerometer and gyroscope sensors of client device 102, which provide measurements representing motion. Therefore, while augmented reality items are presented on the cheek of a face depicted in the image within a set of frames, they remain statically positioned as the user moves around and are no longer presented on the cheek in subsequent frames (e.g., they could be presented on another real-world surface or another part of the face). That is, the augmented reality items are statically positioned and overlaid to view any real-world objects appearing at the static location of the augmented reality items in the video. In some cases, once access restrictions are removed from a given augmented reality experience, a preview of that experience is converted into an active augmented reality experience where the augmented reality items track the movement of real-world objects depicted in the video.

[0030] Social network server 124 supports various social networking functions and services and makes these functions and services available to messaging server 118. To this end, social network server 124 maintains and accesses entity graph 308 within database 126 (such as...). Figure 3(As shown). Examples of functions and services supported by the social network server 124 include identifying other users in the messaging system 100 who are related to a particular user or who are being "followed" by that particular user, as well as identifying the interests and other entities of a particular user.

[0031] Returning to messaging client 104, the features and functionalities of the external resource (e.g., third-party application 109 or applet) are made available to the user through the interface of messaging client 104. Messaging client 104 receives user selections regarding options for launching or accessing features of the external resource (e.g., third-party resource) (e.g., external application 109). The external resource may be a third-party application (external application 109) installed on client device 102 (e.g., a "local application"), or a smaller version (e.g., an "applet") of a third-party application hosted on client device 102 or located away from client device 102 (e.g., on a third-party server 110). The smaller version of the third-party application includes a subset of the features and functionalities of the third-party application (e.g., a full, native version of a third-party standalone application) and is implemented using markup language documentation. In one example, the smaller version of the third-party application (e.g., an "applet") is a web-based markup language version of the third-party application and is embedded in messaging client 104. In addition to using markup language documents (e.g., .*ml files), applets can also include scripting languages ​​(e.g., .*js files or .json files) and stylesheets (e.g., .*ss files).

[0032] In response to a user selection of an option to launch or access 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, installed locally on the client device 102, can be launched independently of and separately from the messaging client 104, for example, by selecting an icon corresponding to the external application 109 on the client device 102's home screen. A smaller version of this external application can be launched or accessed via the messaging client 104, and in some examples, no part of the smaller external application can be accessed (or only a limited part can) outside of the messaging client 104. The smaller external application can be launched by receiving and processing a markup language document associated with the smaller external application from the external application server 110 via the messaging client 104.

[0033] 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 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.

[0034] The messaging client 104 can notify users of client device 102 or other users (e.g., "friends") associated with such users of one or more external resources. For example, the messaging client 104 can provide participants in a conversation (e.g., a chat session) within the messaging client 104 with notifications related to the current or recent use of external resources by one or more members of a group of users. One or more users can be invited to join a valid external resource or to activate a recently used but currently invalid external resource (within the group of friends). External resources can provide participants in the conversation (each using the corresponding messaging client 104) with the ability to share items, statuses, states, or locations within the external resource with one or more members of the user group in the chat session. Shared items can be interactive chat cards that chat members can use to interact, for example, to activate the corresponding external resource, view specific information within the external resource, or take chat members to a specific location or state within the external resource. Within a given external resource, response messages can be sent to users on the messaging client 104. External resources can selectively include different media items in the response based on the current context of the external resources.

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

[0036] System Architecture

[0037] Figure 2This is a block diagram illustrating further details of a messaging system 100 according to some examples. Specifically, the messaging system 100 is shown as including a messaging client 104 and an application server 114. The messaging system 100 includes several subsystems 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 short-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.

[0038] The short-lived timer system 202 is responsible for enabling temporary or time-limited access to content by the message sending client 104 and the message sending server 118. The short-lived timer system 202 includes several timers that selectively enable access (e.g., for rendering and displaying) of messages and associated content via the message sending client 104 based on duration and display parameters associated with a message or message set (e.g., a story). Further details regarding the operation of the short-lived timer system 202 are provided below.

[0039] The collection management system 204 is responsible for managing collections or sets of media (e.g., collections of text, images, 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 time period (e.g., the duration of the event the content relates to). 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 icons that provide notifications about the existence of specific collections to the user interface of the messaging client 104.

[0040] Furthermore, the collection management system 204 includes a curation interface 206 that enables collection managers to manage and curate specific collections of content. For example, curation interface 206 allows event organizers to curate collections of content related to a specific event (e.g., removing inappropriate content or redundant messages). Additionally, the collection management system 204 employs machine vision (or image recognition technology) and content rules to automatically curate content collections. In some examples, users may be paid compensation to include user-generated content in the collection. In such cases, the collection management system 204 operates to automatically pay such users for access to their content.

[0041] Enhancement system 208 provides various functionalities that enable users to enhance (e.g., annotate or otherwise modify or edit) media content associated with a message. For example, enhancement system 208 provides functionality related to generating and publishing media overlays for messages processed by messaging system 100. Enhancement system 208 can operablely provide media overlays or enhancements (e.g., image filters) to messaging client 104 based on the geolocation of client device 102. In another example, enhancement system 208 can operablely provide media overlays to messaging client 104 based on other information such as the social network information of the user of client device 102. Media overlays can include audio and visual content as well as visual effects. Examples of audio and visual content include images, 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., photographs) at client device 102. For example, media overlays can include text, graphic elements, or images that can be overlaid on top of photographs taken by client device 102. In another example, media overlays include location identifier overlays (e.g., Venice Beach), names of live events, or merchant names overlays (e.g., Beach Cafe). In yet another example, overlay system 208 uses the geolocation of client device 102 to identify media overlays that include the name of a merchant at the geolocation of client device 102. Media overlays may include additional tags associated with the merchant. Media overlays may be stored in database 126 and accessed via database server 120.

[0042] In some examples, enhancement system 208 provides a user-based publishing platform that allows users to select geolocations on a map and upload content associated with those geolocations. Users can also specify which media overlays should be provided to other users. Enhancement system 208 generates a media overlay that includes the uploaded content and associates it with the selected geolocation.

[0043] In other examples, augmentation system 208 provides a merchant-based publishing platform that enables merchants to select specific media overlays associated with geolocation via a bidding process. For example, augmentation system 208 associates the media overlay of the highest bidder with the corresponding geolocation for a predefined amount of time. Augmentation system 208 communicates with image processing server 122 to obtain augmented reality experiences and presents identifiers of such experiences in one or more user interfaces (e.g., as icons on live images or videos, or as thumbnails or icons in interfaces specifically for presenting augmented reality experiences). Once an augmented reality experience is selected, one or more images, videos, or augmented reality graphic elements are retrieved and presented as overlays on images or videos captured by client device 102. In some cases, the camera is switched to a frontal view (e.g., the front camera of client device 102 is activated in response to the activation of a specific augmented reality experience), and images from the front camera of client device 102, rather than the rear camera of client device 102, begin to appear on client device 102. One or more images, videos, or augmented reality graphics elements are retrieved and rendered as an overlay on an image captured and displayed by the front-facing camera of the client device 102.

[0044] In some cases, a preview of the augmented reality experience is provided instead of the fully activated augmented reality experience. In this case, only a subgroup of augmented reality items associated with the given augmented reality experience is rendered or overlaid onto live images or videos captured by client device 102 or previously received from a third party. For example, only visual elements are rendered, without any audio elements of the augmented reality experience. As another example, only the first set of visual augmented reality items is rendered, while the second set is excluded. As another example, the set of visual augmented reality items rendered in the preview is a static image that does not track the movement of real-world objects depicted in the live images or videos. In some cases, during the preview of the augmented reality experience, only the first set of visual augmented reality items tracks the movement of real-world objects, while the second set does not track the movement of real-world objects and is rendered as a static image. In some cases, the preview of the augmented reality experience includes a video of a third person or third party (e.g., someone who is not a user of client device 102) displaying the complete subgroup of augmented reality items on the video. In this case, the video demonstrates how the augmented reality experience looks and feels by tracking the third person's position and moving with the people depicted in the video.

[0045] Map system 210 provides various geolocation functions and supports the presentation of map-based media content and messages by messaging client 104. For example, map system 210 can display user icons or avatars on the map (e.g., stored in profile data 316) to indicate the current or past locations of the user's "friends," and display media content (e.g., a collection of messages including photos and videos) generated by these friends within the context of the map. For example, a message posted by a user from a specific geolocation to messaging system 100 can be displayed to the specific user's "friends" on the map interface of messaging client 104 within the context of that specific location on the map. The user can also share his or her location and status information with other users of messaging system 100 (e.g., using appropriate status avatars) via messaging client 104, where the location and status information is displayed to selected users within the context of the map interface of messaging client 104.

[0046] Game system 212 provides various game functions within the context of messaging client 104. Messaging client 104 provides a game interface that offers a list of available games (e.g., web-based games or web-based applications), which can be started by a user within the context of messaging client 104 and played with other users of messaging system 100. Messaging system 100 also enables specific users to invite other users to play a specific game by sending invitations from messaging client 104 to such other users. Messaging client 104 also supports both voice and text messaging (e.g., chat) within the game context, provides leaderboards for the game, and also supports providing in-game rewards (e.g., game currency and items).

[0047] External resource system 220 provides an interface for messaging client 104 to communicate with external application server 110 to launch or access external resources. Each external resource (application) server 110 hosts applications, such as those based on markup languages ​​(e.g., HTML5), or smaller versions of external applications (e.g., games, utilities, payment, or ride-sharing applications outside of messaging client 104). Messaging client 104 can launch web-based resources (e.g., applications) by accessing HTML5 files from external resource (application) servers 110 associated with the web-based resource. In some examples, applications hosted by external resource servers 110 utilize a software development kit (SDK) provided by messaging server 118, programmed in JavaScript. The SDK includes an application programming interface (API) with functionality that can be invoked or activated by the web-based application. In some examples, messaging server 118 includes a JavaScript library that provides access to certain user data of messaging client 104 to a given third-party resource. HTML5 is used as an example technology for programming games, but applications and resources programmed based on other technologies can be used.

[0048] 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 otherwise received 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.

[0049] The SDK stored on message transceiver server 118 effectively provides a bridge between external resources (e.g., third-party or external applications 109 or mini-applications) and message transceiver client 104. This provides users with a seamless experience communicating with other users on message transceiver client 104 while preserving the look and feel of message transceiver client 104. To bridge communication between external resources and message transceiver client 104, in some examples, the SDK facilitates communication between external resource server 110 and message transceiver client 104. In some examples, a WebViewJavaScriptBridge running on client device 102 establishes two unidirectional communication channels between external resources and message transceiver client 104. Messages are sent asynchronously between external resources and message transceiver client 104 via these communication channels. 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 that callback identifier.

[0050] 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 the messaging server 118 with an HTML5 file corresponding to the web-based external resource. The messaging server 118 can add a visual representation (such as a box design or other graphics) of the web-based external resource in the messaging client 104. Once the user selects a visual representation or instructs the messaging client 104 via its GUI to access a feature of the web-based external resource, the messaging client 104 obtains the HTML5 file and instantiates the resource required to access the feature of the web-based external resource.

[0051] The messaging client 104 presents a graphical user interface (GUI) for an external resource (e.g., a login page or title screen). During, before, or after presenting the login page or title screen, the messaging client 104 determines whether the initiated external resource has previously been authorized to access the messaging client 104's user data. In response to determining that the initiated external resource has previously been authorized to access the messaging client 104's user data, the messaging client 104 presents another GUI for the external resource, including its functionality and characteristics. In response to determining that the initiated external resource has not previously been authorized to access the messaging client 104's user data, after a threshold time period (e.g., 3 seconds) of displaying the external resource's login page or title screen, the messaging client 104 slides up a menu (e.g., animates the menu to appear from the bottom of the screen to the middle or other part of the screen) to authorize the external resource to access user data. This menu identifies the type of user data that the external resource will be authorized to use. In response to receiving a user's selection of the accept option, messaging client 104 adds the external resource to the list of authorized external resources and allows the external resource to access user data from messaging client 104. In some examples, the external resource is authorized by messaging client 104 to access user data according to the OAuth 2 framework.

[0052] The messaging client 104 controls the type of user data shared with external resources based on the type of authorized external resource. For example, external resources including complete external applications (e.g., third-party or external application 109) are granted access to a first type of user data (e.g., a two-dimensional avatar of a user, with or without different avatar characteristics). As another example, external resources including smaller versions of external applications (e.g., a web-based version of a third-party application) are granted access to a second type of user data (e.g., payment information, a user's two-dimensional avatar, a user's three-dimensional avatar, and avatars with various avatar characteristics). Avatar characteristics include different ways of customizing the appearance and feel of an avatar (e.g., different poses, facial features, clothing, etc.).

[0053] Data Architecture

[0054] Figure 3 This is a schematic diagram illustrating a data structure 300 that can be stored in a database 126 of a message transceiver server system 108, according to certain examples. Although the contents of the database 126 are shown as including several tables, it will be understood that the data can be stored in other types of data structures (e.g., as an object-oriented database).

[0055] Database 126 includes message data stored in message table 302. For any given message, this message data includes at least message sender data, message receiver (or recipient) data, and payload. See below for reference. Figure 4 Further details are provided regarding information that can be included in the message and in the message data stored in message table 302.

[0056] Entity table 306 stores entity data and (for example, reference) links to entity diagram 308 and profile data 316. Entities for which records are maintained within entity table 306 may include individuals, company entities, organizations, objects, locations, events, etc. Regardless of entity type, any entity whose data is stored in message transceiver server system 108 can be an identifiable entity. Each entity is assigned a unique identifier and an entity type identifier (not shown).

[0057] Entity graph 308 stores information about the relationships and associations between entities. As an example only, such relationships can be social, professional (e.g., working in the same company or organization), interest-based, or activity-based.

[0058] Profile data 316 stores various types of profile data about a specific entity. Based on privacy settings specified by the specific entity, profile data 316 can be selectively used and presented to other users of messaging system 100. In the case of an individual, profile data 316 includes, for example, a username, phone number, address, settings (e.g., notification and privacy settings), and an avatar representation (or a set of such avatar representations) selected by the user. A specific user can then selectively include one or more of these avatar representations in the content of messages transmitted via messaging system 100 and in a map interface displayed to other users by messaging client 104. The set of avatar representations may include “status avatars,” which present a graphical representation of a status or activity that the user can choose to transmit at a specific time.

[0059] In the case that the entity is a group, in addition to the group name, members and various settings (e.g., notifications) of the relevant group, the group profile data 316 may similarly include one or more avatars associated with the group.

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

[0061] In one example, a filter is an overlay displayed on an image or video during presentation to the receiving user. Filters can be of various types, including user-selected filters that come from a set of filters presented to the sending user by the messaging client 104 while the sending user is composing a message. Other types of filters include geolocation filters (also known as geographic filters), which can be presented to the sending user based on geographic location. For example, a geolocation filter specific to a nearby or particular location can be presented by the messaging client 104 within the user interface based on geolocation information determined by the Global Positioning System (GPS) unit of the client device 102.

[0062] Another type of filter is a data filter, which can be selectively presented to the sending user by the messaging client 104 based on other inputs or information collected by the client device 102 during the message creation process. Examples of data filters include the current temperature at a specific location, the current speed of the sending user's journey, the battery life of the client device 102, or the current time.

[0063] Other augmented data that can be stored in image table 312 includes augmented reality content items (e.g., corresponding to an applied augmented reality experience). Augmented reality content items or augmented reality items can be real-time special effects and sounds that can be added to images or videos.

[0064] As described above, augmented data includes augmented reality content items, overlays, image transformations, AR images, and similar items referring to modifications that can be applied to image data (e.g., videos or images). This includes real-time modifications, which modify the image while it is being captured by the device sensors (e.g., one or more cameras) of client device 102 and then displayed on the screen of client device 102 in modified form. This also includes modifications to stored content, such as video clips in a gallery that can be modified. For example, in client device 102 that accesses 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 clip. For example, by selecting different augmented reality content items for the same content, multiple augmented reality content items applying different pseudo-random motion models can be applied to that same content. Similarly, real-time video capture can be used with the illustrated modifications to show how the video image currently captured by the sensors of client device 102 will modify the captured data. Such data can be displayed on the screen without being stored in memory, or content captured by the device's sensors can be recorded and stored in memory with or without modification (or both). In some systems, preview functionality can show how different augmented reality content items appear in different windows of the display at the same time. For example, this allows multiple windows with different pseudo-random animations to be viewed on the display simultaneously.

[0065] Therefore, using data from augmented reality content items and various systems, or other such transformation systems that modify content using that data, can involve detecting objects (e.g., faces, hands, bodies, cats, dogs, surfaces, objects, etc.) in video frames, tracking these objects as they leave, enter, and move around within the field of view, and modifying or transforming them while tracking them. Different methods can be used to implement such transformations in various examples. Some examples may involve generating 3D mesh models of one or more objects and using transformations of the models within the video and animated textures to achieve the transformation. In other examples, tracking points on objects can be used to place images or textures (which can be 2D or 3D) at the tracked locations. In yet another example, neural network analysis of video frames can be used to place images, models, or textures within content (e.g., frames of images or videos). Thus, augmented reality content items involve both images, models, and textures used to create transformations within the content, and additional modeling and analysis information required to implement such transformations using object detection, tracking, and placement.

[0066] Live video processing can be performed using any type of video data (e.g., video streams, video files, etc.) stored in the memory of any type of computerized system. For example, a user can load a video file and store it in the device's memory, or a video stream can be generated using the device's sensors. Furthermore, computer-animated models can be used to process any object, such as a human face and parts of the human body, animals, or inanimate objects such as chairs, cars, or other objects.

[0067] In some examples, when a specific modification is selected along with the content to be transformed, the computing device identifies the elements to be transformed and then detects and tracks them if they exist in the video frames. The elements of the object are modified according to the modification request, thereby transforming the frames of the video stream. Different methods can be used to perform the transformation of the video stream frames for different types of transformations. For example, for frame transformations that primarily refer to changes in the forms of the object's elements, feature points of each element of the object are calculated (e.g., using an Active Shape Model (ASM) or other known methods). A feature point-based mesh is then generated for each of at least one element of the object. This mesh is used for subsequent stages of tracking the elements of the object in the video stream. During tracking, the mesh for each mentioned element is aligned with the position of each element. Additional points are then generated on the mesh. A first set of first points is generated for each element based on the modification request, and a second set of points is generated for each element based on the first set of points and the modification request. The frames of the video stream can then be transformed by modifying the elements of the object based on this set of first and second points and the mesh. In this method, the background of the modified object can also be changed or deformed by tracking and modifying the background.

[0068] In some examples, transformations that alter certain regions of an object using its elements can be performed by calculating characteristic points for each element of the object and generating a mesh based on those calculated characteristic points. Points are generated on the mesh, and various regions are then generated based on these points. The elements of the object are then tracked by aligning the regions of each element with the positions of at least one element in the video stream, and the properties of the regions can be modified based on modification requests, thereby transforming frames of the video stream. Depending on the specific modification request, the properties of the mentioned regions can be transformed in different ways. Such modifications can involve: changing the color of the region; removing at least some portions of the region from the frames of the video stream; including one or more new objects in the region based on the modification request; and modifying or distorting the elements of the region or object. In various examples, any combination of such modifications or other similar modifications can be used. For certain models to be animated, some characteristic points can be selected as control points in the entire state space to determine the options for animateting the model.

[0069] In some examples of computer animation models that use face detection to transform image data, a specific face detection algorithm (e.g., Viola-Jones) is used to detect faces in the image. Then, the Active Shape Model (ASM) algorithm is applied to the facial regions of the image to detect facial feature reference points.

[0070] Other methods and algorithms suitable for face detection can be used. For example, in some examples, landmarks are used to locate features; landmarks represent distinguishable points present in most of the images considered. For example, for facial landmarks, the location of the left pupil could be used. Secondary landmarks can be used where the initial landmarks are not identifiable (e.g., if the person is wearing an eye patch). Such a landmark identification process can be used for any such object. In some examples, the set of landmarks forms a shape. The shape can be represented as a vector using the coordinates of the points in the shape. One shape is aligned with another shape using a similarity transformation (allowing translation, scaling, and rotation) that minimizes the average Euclidean distance between the points of the shapes. The average shape is the mean of the aligned training shapes.

[0071] In some examples, the search for landmarks begins with a mean shape aligned with the position and size of the face determined by the global face detector. This search is then repeated until convergence occurs: a provisional shape is suggested by adjusting the localization of the shape points through template matching of the image texture around each point, and then the provisional shape is made to conform to the global shape model. In some systems, individual template matching is unreliable, and the shape model pools the results of weak template matching to form a stronger overall classifier. The entire search is repeated at each level of the image pyramid, from coarse to fine resolution.

[0072] The transformation system can capture image or video streams on a client device (e.g., client device 102) and perform complex image manipulations locally on client device 102 while maintaining an appropriate user experience, computation time, and power consumption. Complex image manipulations can include size and shape changes, emotion transfers (e.g., changing a face from frowning to smiling), state transfers (e.g., aging an object, reducing its apparent age, or changing its gender), style transfers, application of graphical elements, and any other suitable image or video manipulations implemented by a convolutional neural network that has been configured to execute efficiently on client device 102.

[0073] In some examples, a computer animation model for transforming image data can be used by a system in which a user can use a client device 102 with a neural network to capture an image or video stream of the user (e.g., a selfie), the neural network operating 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 to transform the data image, or the computer animation model may exist in association with the interface described herein. The modification icon includes changes, which may be the basis for modifying the user's face within the image or video stream as part of a modification operation. Once a 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 smiley face on 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 may implement a complex convolutional neural network on a portion of the image or video stream to generate and apply the selected modification. In other words, users can capture image or video streams, and once an edit icon is selected, the modified result can be presented in real-time or near real-time. Furthermore, the modifications can be persistent while the video stream is captured and the selected edit icon continues to toggle. Machine learning neural networks can be used to achieve this type of modification.

[0074] A graphical user interface (GUI) presenting modifications performed by the transformation system can provide users with additional interactive options. Such options can be based on an interface used to initiate content capture and select a specific computer animation model (e.g., initiated from a content creator user interface). In various examples, modifications can be persistent after an initial selection of the modification icon. Users can turn modifications on or off by tapping or otherwise selecting the face modified by the transformation system and save them for later viewing or browsing to other areas of the imaging application. In cases where multiple faces are modified by the transformation system, users can globally turn modifications on or off by tapping or selecting a single face modified and displayed within the GUI. In some examples, individual faces within a set of multiple faces can be modified individually, or such modifications can be toggled individually, by tapping or selecting a single face or a series of faces displayed within the GUI.

[0075] Story table 314 stores data related to messages and collections of associated image, video, or audio data, compiled into collections (e.g., stories or galleries). The creation of a specific collection can be initiated by a specific user (e.g., each user whose records are stored in entity table 306). A user can create a "personal story" in the form of a collection of content that has already been created and sent / broadcast by that user. For this purpose, the user interface of messaging client 104 may include user-selectable icons that allow the sending user to add specific content to his or her personal story.

[0076] Collections can also constitute "live stories," which are collections of content from multiple users created manually, automatically, or using a combination of manual and automatic techniques. For example, a "live story" can constitute a curated flow of user-submitted content from various locations and events. Users whose client devices have location services enabled and are at a co-location event at a specific time can be presented with options, for example, via the user interface of messaging client 104, to contribute content to a specific live story. The messaging client 104 can identify live stories to users based on their location. The end result is a "live story" told from a community perspective.

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

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

[0079] Data communication architecture

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

[0081] • Message Identifier 402: A unique identifier that identifies message 400.

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

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

[0084] • Message video payload 408: Video data captured by the camera device component or retrieved from the memory component of the client device 102 and included in message 400. The video data of the sent or received message 400 can be stored in video table 304.

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

[0086] • Message enhancement data 412: Enhancement data (e.g., filters, labels, 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 message 400. Enhancement data for sent or received message 400 can be stored in enhancement table 310.

[0087] • Message duration parameter 414: A parameter value, in seconds, indicating the amount of time that the content of the message (e.g., message image payload 406, message video payload 408, message audio payload 410) will be presented to the user or made accessible to the user via the message sending and receiving client 104.

[0088] • Message geolocation parameter 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 in the message image payload 406, or a specific video in the message video payload 408).

[0089] • Message Story Identifier 418: An identifier value that identifies one or more sets of content (e.g., “Stories” identified in Story Table 314) associated with a specific content item in the message image payload 406 of message 400. For example, the identifier value can be used to associate multiple images within the message image payload 406 with multiple sets of content, respectively.

[0090] • Message Tag 420: Each message 400 can be labeled with multiple tags, each of which indicates the subject of the content included in the message payload. For example, in the case where a specific image in the message image payload 406 depicts an animal (e.g., a lion), a tag value can be included within the message tag 420 indicating the relevant animal. Tag values ​​can be manually generated based on user input or can be automatically generated using, for example, image recognition.

[0091] • Message sender identifier 422: An identifier (e.g., message sending system identifier, email address, or device identifier) ​​indicating the user of the client device 102 on which message 400 is generated and from which message 400 is sent.

[0092] • Message receiver identifier 424: An identifier (e.g., message sending and receiving system identifier, email address, or device identifier) ​​indicating the user of the client device 102 to which message 400 is addressed.

[0093] The content (e.g., values) of each component of message 400 can be pointers to locations in tables where the content data values ​​are stored. For example, the image value in message image payload 406 can be a pointer to a location (or the address of a location within image table 312). Similarly, the value in message video payload 408 can point to data stored in video table 304, the value stored in message annotation 412 can point to data stored in annotation table 310, the value stored in message story identifier 418 can point to data stored in story table 314, and the values ​​stored in message sender identifier 422 and message receiver identifier 424 can point to user records stored in entity table 306.

[0094] Figures 5 through 9 are schematic representations of graphical user interfaces (GUIs) based on some examples. Specifically, Figures 5 through 9 show representations of GUIs including identifiers for augmented reality (AR) experiences, which include at least one restricted AR experience. As referred to herein, a restricted AR experience (an AR experience with limited access or an AR experience associated with access restrictions) is available only to certain users or only when performing electronic transactions. As an example, a restricted AR experience corresponds to a high-level experience available to advanced users. That is, a messaging application may include various AR experiences, but such subgroups of experiences may be available as a whole or independently to users with different access levels. Specifically, a first user may have free access to the messaging application without a paid membership. Free access to a first set of AR experiences may be provided to the first user, and access to restricted AR experiences may be restricted. The first user may upgrade their membership to a higher level, for example, by paying a monthly or one-time fee. In response, the first user is provided with access to the first set of AR experiences as well as some or all of the restricted AR experiences.

[0095] As another example, access-restricted augmented reality experiences can be accessed or activated on a personal basis by purchasing permissions or paying a certain amount of virtual currency. Specifically, an interface presenting one or more access-restricted augmented reality experiences can be provided to any user with any access level to the messaging application. Each access-restricted augmented reality experience is associated with a specified amount of virtual currency that restricts access. If a given user selects an access-restricted augmented reality experience for which they have not previously purchased access or removed restrictions, the given user can execute an electronic transaction to remove the access restrictions. As an example, if an access-restricted augmented reality experience is associated with 30 virtual tokens, the user can request that 30 virtual tokens be deducted from a virtual wallet or token set managed by the messaging application for the user. If the virtual wallet contains a sufficient number of tokens (e.g., more than 30 required to remove the access restrictions from the augmented reality experience), the electronic transaction is completed after deducting the 30 virtual tokens. At this point, the access restrictions are removed from the access-restricted augmented reality experience, and the user can activate the access-restricted augmented reality experience. If the virtual wallet does not contain a sufficient number of tokens (e.g., less than 30), the messaging application presents an interface allowing the user to purchase additional virtual tokens. After purchasing a sufficient number of tokens, the messaging application confirms the purchase of the restricted augmented reality experience and removes the access restrictions from the restricted augmented reality experience.

[0096] The messaging application maintains a profile for each user. This profile uses a unique identifier to indicate which restricted augmented reality experiences the user has previously purchased. That is, the profile identifies each restricted augmented reality experience for which access restrictions have been removed for a given user. Based on whether the augmented reality experience has or does not have access restrictions, the messaging application presents the identifier of each augmented reality experience to the user in different user interfaces.

[0097] As an example, a messaging application might receive a request from a user to access a personalized content page. In response, the messaging application searches for a set of augmented reality experiences (ARAs) with attributes that match the user's profile across all ARAs or subgroups of ARAs. The messaging application then accesses the identifier for each identified ARA and generates a personalized page 500 that includes the identifier. Figure 5A In some implementations, the personalized page 500 includes: a first portion 510 comprising a non-access-restricted augmented reality experience; and a second portion 520 comprising an access-restricted augmented reality experience. Each augmented reality experience in the first portion 510 and the second portion 520 includes attributes that match the profile of the user of the client device 102 displaying them.

[0098] The personalized page 500 includes various options in the top section for accessing different pages. These options include a restricted augmented reality experience option 540 and a popular option 530. Selecting these options allows the messaging application to retrieve a corresponding set of augmented reality experiences and display the identifier of the retrieved augmented reality experience.

[0099] Messaging applications can allow individual creators to submit restricted augmented reality (AR) experiences. That is, an individual creator can generate an AR experience and request that it be restricted. In some implementations, the creator can specify a minimum or threshold number of virtual tokens required to access or activate the AR experience. In some implementations, the creator generates a preview of the AR experience. In this case, the creator specifies which parts or items of the AR experience are disabled during the free preview period. Messaging applications can enable other users to view and purchase access to restricted AR experiences received from creators. In some cases, messaging applications can limit the number of restricted AR experiences a given creator can submit. For example, a messaging application can determine whether the creator has previously submitted AR experiences that are not within the restricted threshold number (e.g., whether the creator has previously offered at least five free AR experiences). In response to determining that a creator has previously submitted a threshold number of non-access-restricted augmented reality experiences (e.g., 5), a messaging application can enable the creator to request access restrictions for a given augmented reality experience. The messaging application can require each creator to submit a threshold number of non-access-restricted augmented reality experiences before allowing the creator to submit an additional access-restricted augmented reality experience.

[0100] In some implementations, messaging applications restrict or limit the accessibility of a given augmented reality experience (ARI) submitted or requested by a creator based on performance metrics associated with previously submitted non-access-restricted ARI experiences. For example, a messaging application might determine whether a creator has previously submitted non-access-restricted ARI experiences that each meet a popularity criterion (e.g., each of the non-access-restricted ARII experiences has been accessed, shared, or used by a threshold number of users). In response to determining that a certain number of non-access-restricted ARII experiences meet the popularity criterion, the messaging application can enable a creator to request access restrictions for a new ARII experience.

[0101] In some implementations, the non-access-restricted augmented reality experiences displayed in the first section 510 are represented by individual icons 512 (e.g., thumbnails). The thumbnails include images or videos representing the behavior of the non-access-restricted augmented reality experiences. In some cases, each icon 512 includes an image, a title, the name of the creator, the name of the set associated with the various non-access-restricted augmented reality experiences, and any other suitable information. The icons 512 are presented in a first size. The messaging application ranks or sorts the icons 512 based on performance attributes (e.g., popularity) of each non-access-restricted augmented reality experience and based on how well each non-access-restricted augmented reality experience matches a user profile. The messaging application ranks the icons 512 based on how each of the non-access-restricted augmented reality experiences performs relative to each other and independently of how other access-restricted augmented reality experiences perform.

[0102] The restricted augmented reality experiences displayed in Part 2, 520, are represented by individual icons, 522 (e.g., thumbnails). Thumbnails include images or videos representing the behavior of the restricted augmented reality experience. In some cases, each icon, 522 includes an image, a title, the name of the creator, the name of the set associated with the individual restricted augmented reality experience, and any other suitable information. The messaging application ranks or sorts the icons, 522, based on performance attributes of each restricted augmented reality experience (e.g., popularity) and on how well each restricted augmented reality experience matches a user profile. The messaging application ranks the icons, 522, based on how each of the restricted augmented reality experiences performs relative to each other and independently of how other non-restricted augmented reality experiences perform.

[0103] The icon 522 for accessing restricted augmented reality experiences includes a restriction status icon 524. The restriction status icon 524 may indicate parameters required to remove the restriction (e.g., the restriction status icon 524 may specify the price or minimum amount of virtual tokens required to purchase the right to remove the restriction from the corresponding restricted augmented reality experience). In some implementations, the icon 522 representing the restricted augmented reality experience in the second portion 520 is displayed at a second size, which is larger than the first size displayed by the icon 512 in the first portion 510. That is, a larger icon than that used for non-restricted augmented reality experiences is used to represent restricted augmented reality experiences on the personalization page 500.

[0104] In some implementations, when displaying the personalized page 500, the messaging application receives a user selection for the popular option 530. In response, the messaging application displays the popular page 501. Specifically, in response to receiving a user selection for the popular option 530, the messaging application searches a database for a list of the most popular restricted and unrestricted augmented reality experiences. As an example, the messaging application obtains the number of times each augmented reality experience has been selected by users of the messaging application and the number of times each augmented reality experience has been shared with other users on the messaging application or mentioned in communications. Based on these parameters, the messaging application ranks the augmented reality experiences (both restricted and unrestricted) and generates a display of the popular page 501, which includes both restricted and unrestricted augmented reality experiences.

[0105] As an example, the featured page 501 includes a first icon 532 (e.g., a thumbnail) representing a non-access-restricted augmented reality experience. The first icon 532 includes an image or video representing the augmented reality experience, along with the title and creator's name. A messaging application can receive a user selection of the first icon 532. In response, the messaging application opens the camera feed of the client device 102 and activates the augmented reality experience associated with the first icon 532. As an example, the messaging application obtains one or more augmented reality items associated with the augmented reality experience and overlays these items onto the live video being captured by the client device 102 and presented in the camera feed. The augmented reality items are repositioned and their movement is tracked as depicted in the live video feed.

[0106] The featured page 501 also includes a second icon 534 (e.g., a thumbnail) representing a restricted augmented reality experience. The second icon 534 includes an image or video representing the augmented reality experience, along with its title and the creator's name. The second icon 534 also includes a restriction status icon 536, which can indicate parameters required to remove restrictions (e.g., the restriction status icon 536 can specify the price or minimum amount of virtual tokens required to purchase permission to remove restrictions from the individual restricted augmented reality experience). The restriction status icon 536 is displayed for restricted augmented reality experiences even if the user has previously purchased permission associated with the restricted augmented reality experience or removed restrictions associated with it. In some implementations, each icon presented on the featured page 501 has the same size, regardless of whether the icon corresponds to a restricted or unrestricted augmented reality experience. This differs from personalized pages 500 where restricted augmented reality experiences are represented by icons larger than those for unrestricted augmented reality experiences.

[0107] In some implementations, only the restriction status icon 536 is included for these restricted augmented reality experiences for which the user has not previously purchased permission to remove access restrictions. In this case, the messaging application accesses a database that specifies these restricted augmented reality experiences for which the user has previously purchased permission to remove restrictions. The messaging application determines whether a given icon displayed on the featured page 501 corresponds to a restricted augmented reality experience for which the user previously removed restrictions (as indicated by the database), and if so, the messaging application prevents the restriction status icon 536 from being displayed.

[0108] In response to receiving a user selection for the second icon 534, the messaging application determines whether the user has previously removed access restrictions from the augmented reality experience associated with the second icon 534 (e.g., payment using virtual tokens). In response to determining that the user has previously removed access restrictions, the messaging application opens the camera feed of the client device 102 and activates the augmented reality experience associated with the second icon 534. As an example, the messaging application obtains one or more augmented reality items associated with the augmented reality experience and overlays these items onto the live video being captured by the client device 102 and presented in the camera feed. The augmented reality items are repositioned and the motion of the live objects depicted in the camera feed is tracked.

[0109] In response to determining that the user has not previously removed access restrictions (e.g., the user has not previously purchased permission to access or activate an augmented reality experience), the messaging application generates a prompt indicating the cost of virtual tokens to purchase permission to access or activate the selected augmented reality experience. This prompt may indicate the current number of virtual tokens available to the user in their virtual token wallet and may include a confirmation option. If the user does not currently have enough tokens in their virtual wallet to purchase the augmented reality experience, the messaging application presents an option to access a virtual token store to purchase additional virtual tokens. The prompt may also include a preview option. In response to receiving a user selection of the preview option, the messaging application opens the camera feed of client device 102 and presents a static 2D image of the augmented reality experience associated with the second icon 534. As an example, the messaging application obtains one or more augmented reality items associated with the augmented reality experience and overlays these items at static locations on the live video being captured by client device 102 and presented in the camera feed. These augmented reality items are not repositioned or tracked for movement of live objects depicted in the camera feed.

[0110] In some implementations, the messaging application receives a user selection for the restricted augmented reality experience option 540. This selection can be received when the personalized page 500 is presented or when the popular page 501 is presented. In response to receiving the user selection for the restricted augmented reality experience option 540, the messaging application navigates the user to the restricted augmented reality experience page 600. Figure 6 The messaging application determines whether the user has previously visited a restricted augmented reality experience page 600. If so, the application determines whether the user has visited the page 600 more than a threshold number of times (e.g., more than three times). In response to determining that the user has not visited the page 600 more than the threshold number of times, the application presents an introductory tile 610. In response to determining that the user has visited the page 600 more than the threshold number of times, or that the user has previously purchased permissions or removed restrictions from at least one restricted augmented reality experience, the application prevents the introductory tile 610 from being displayed on page 600. The introductory tile illustrates various features of the restricted augmented reality experience. These features include instructions on how to remove access restrictions (e.g., how to access a virtual wallet and purchase virtual tokens) and how to access or activate a preview of the restricted augmented reality experience.

[0111] The messaging app searches its database for a list of the most popular restricted augmented reality experiences. For example, the app obtains the number of times each augmented reality experience was selected by users of the messaging app, the number of times each experience was shared with other users on the messaging app or mentioned in communications, and the number of times each restricted augmented reality experience had its restrictions purchased or removed by users. Based on these parameters, the app ranks the restricted augmented reality experiences and generates a display of 600 pages that include these experiences.

[0112] Page 600 also includes icons 620 (e.g., thumbnails) representing restricted augmented reality experiences. Icon 620 includes an image or video representing the augmented reality experience, along with the title and creator's name. Icon 620 also includes a restriction status icon 622, which may indicate the parameters required to remove the restriction (e.g., restriction status icon 622 may specify the price or minimum amount of virtual tokens required to purchase the right to remove the restriction from the individual restricted augmented reality experience). In some implementations, each icon presented on page 600 has the same size.

[0113] In response to receiving a user selection of a given icon 620, the messaging application generates a prompt indicating the cost of virtual tokens for purchasing access to or activating the selected augmented reality experience. This prompt may indicate the current amount of virtual tokens available in the user's virtual token wallet and may include a confirmation option. If the user does not currently have enough tokens in their virtual wallet to purchase the augmented reality experience, the messaging application presents an option to access a virtual token store to purchase additional virtual tokens. The prompt may also include a preview option. In response to receiving a user selection of the preview option, the messaging application opens the camera feed of client device 102 and presents a static 2D image of the augmented reality experience associated with the given icon 620. As an example, the messaging application obtains one or more augmented reality items associated with the augmented reality experience and overlays these items at static locations on the live video being captured by client device 102 and presented in the camera feed. These augmented reality items are not repositioned or tracked for movement of the live objects depicted in the camera feed.

[0114] In some implementations, the messaging application determines that the user has previously purchased permissions or removed access restrictions from one or more restricted augmented reality experiences. In this case, such as... Figure 7A As shown, instead of presenting the introductory tile 610, the messaging application presents a purchased area 710. The purchased area 710 includes one or more indicators 712 that visually represent each access-restricted augmented reality experience for which the user has previously purchased permissions or from which the user has removed restrictions. These access-restricted augmented reality experiences for which the user has not previously purchased permissions are presented in another section 720. Access-restricted augmented reality experiences in section 720 are represented using icons 722 and can be combined with those above. Figure 6 Interact in the same manner as discussed to preview or purchase permissions. The icon 722 used to represent an access-restricted augmented reality experience for which the user has not previously purchased permissions or from which restrictions have not been removed is different from the indicator 712 (e.g., smaller and round) for each access-restricted augmented reality experience for which the user has previously purchased permissions or from which restrictions have been removed (e.g., larger and square).

[0115] Indicators 712 in the purchased areas 710 are ranked and sorted by recentity, usage, or purchase, and / or by popularity. For example, a first access-restricted augmented reality experience recently purchased by a user can be represented by a first indicator that appeared earlier in the list of indicators 712 than a second indicator representing a second access-restricted augmented reality experience. In response to receiving a user selection for a purchased area, the messaging application navigates the user to the purchased page 701. Figure 7B The purchased page 701 includes various icons 730 (e.g., thumbnails) associated with each of one or more indicators 712, the various icons 730 visually representing each access-restricted augmented reality experience for which the user has previously purchased permission or from which the user has removed restrictions. When the user has already purchased permission to access a access-restricted augmented reality experience, icon 730 is presented with an icon without restrictions (e.g., icon 622).

[0116] The messaging application can receive a user selection for a given icon of the first indicator 712 or icon 730. In response, the messaging application opens the camera feed of the client device 102 and activates the access-restricted augmented reality experience associated with the given icon of the first indicator 712 or icon 730. As an example, the messaging application obtains one or more augmented reality items associated with the augmented reality experience and overlays these augmented reality items onto the live video being captured by the client device 102 and presented in the camera feed. The augmented reality items are repositioned and the motion of the live objects depicted in the camera feed is tracked.

[0117] In some implementations, the messaging application receives a user request to access a set of augmented reality experiences. For example, a user might request to view multiple augmented reality experiences, each representing a different makeup look from a makeup palette. The request can be received by presenting a list of sets and receiving a user selection from that list. In this case, the messaging application obtains a list of all augmented reality experiences associated with the selected set.

[0118] In some implementations, in response to determining that the set includes both restricted and unrestricted access augmented reality experiences, the messaging application determines whether the set includes more than a threshold number of unrestricted access augmented reality experiences. If the set includes fewer than the threshold number of unrestricted access augmented reality experiences, the messaging application presents a page (not shown) similar to page 501, where each augmented reality experience in the set is represented by an icon. The messaging application excludes icons or representations of restricted access augmented reality experiences that are part of the set from the list of icons presented on the page. If the set includes more than the threshold number of unrestricted access augmented reality experiences, the messaging application presents a page (not shown) similar to page 501, where each augmented reality experience in the set is represented by an icon, including icons indicating restricted access augmented reality experiences that are part of the set. Restricted access augmented reality experiences can be identified using a suitable indicator such as a restriction status icon 536.

[0119] In some implementations, in response to determining that a set includes both restricted and unrestricted access augmented reality (AR) experiences, the messaging application determines whether the set includes unrestricted access AR experiences that meet minimum performance metrics (e.g., each activated, accessed, or shared by a minimum number of users). If the set includes unrestricted access AR experiences that do not meet the minimum performance metrics, the messaging application presents a page (not shown) similar to page 501, where each AR experience in the set is represented by an icon. The messaging application excludes icons or representations of restricted access AR experiences that are part of the set from the list of icons presented on the page. If the set includes unrestricted access AR experiences that meet the minimum performance metrics, the messaging application presents a page (not shown) similar to page 501, where each AR experience in the set is represented by an icon, including icons indicating restricted access AR experiences that are part of the set. Restricted access AR experiences can be identified using a suitable indicator such as a restriction status icon 536.

[0120] In some implementations, the user can activate the camera feed of the client device 102. For example... Figure 8A As shown, when the camera feed is displayed on screen 800, the user can request to view a list of available augmented reality experiences. Each augmented reality experience is presented with a corresponding icon above the live video feed from the camera. The user can scroll through the list of icons. In some cases, one of the icons is associated with a restricted augmented reality experience. Such icons are modified to depict a restriction status icon 810 that can indicate parameters required to remove the restriction (e.g., icon 810 could resemble a virtual token). In some implementations, after the user has browsed a minimum number of non-restricted augmented reality experiences in the camera feed, the messaging application inserts an icon representing a restricted augmented reality experience. For example, after the user has browsed more than 10 non-restricted augmented reality experiences without activating any of them, the messaging application identifies a restricted augmented reality experience (e.g., from which the user has not previously removed access restrictions) and presents the icon 810 associated with the identified restricted augmented reality experience.

[0121] The messaging application determines whether the user has previously removed access restrictions from the restricted augmented reality experience corresponding to icon 810. In response to receiving a user selection for icon 810 and in response to determining that the user has not previously removed access restrictions from the restricted augmented reality experience corresponding to icon 810, the messaging application displays prompt 814.

[0122] The prompt 814 can provide visual information illustrating the behavior of the restricted augmented reality experience. The messaging application also presents a preview of the restricted augmented reality experience. For example, the messaging application receives one or more augmented reality items associated with the restricted augmented reality experience and presents one or more augmented reality items 812 in a static position such that they do not track the movement of real-world objects (e.g., faces) depicted in a live camera feed. The prompt 814 includes a purchase option indicating the amount of virtual tokens required to activate or purchase permissions for the selected restricted augmented reality experience.

[0123] As an example, if a restricted augmented reality experience is associated with 30 virtual tokens, prompt 814 indicates that if the user confirms the purchase of the restricted augmented reality experience, 30 virtual tokens will be deducted from the user's virtual token wallet. The user can request that 30 virtual tokens be deducted from a virtual wallet or token set managed by the messaging application for the user. If the virtual wallet contains a sufficient number of tokens (e.g., more than the 30 required to remove the access restriction from the augmented reality experience), the electronic transaction is completed after the 30 virtual tokens are deducted. At this point, the access restriction is removed from the restricted augmented reality experience, and the user can activate the restricted augmented reality experience.

[0124] As an example, a graphical user interface 801 is presented. Figure 8B In this graphical user interface, one or more augmented reality items 824 associated with a purchased restricted augmented reality experience are displayed and overlaid on a live video or camera feed, and the motion of real-world objects depicted in the camera feed is tracked (e.g., facial motion is tracked so that they are dynamically repositioned as faces move in the video). The graphical user interface 801 also temporarily presents a message 822 indicating that a restricted augmented reality experience has been successfully purchased. After the user completes the purchase of the restricted augmented reality experience, the messaging application replaces the restriction status icon 810 with an icon 820 that is unique and represents a purchased restricted augmented reality experience. Specifically, the restriction status icon 810 is the same for all restricted augmented reality experiences viewed by the user in the camera view, while icon 820 is unique for a given restricted augmented reality experience purchased by the user.

[0125] In some cases, if the virtual wallet does not contain a sufficient number of tokens (e.g., less than 30), the messaging application presents an interface that allows the user to purchase additional virtual tokens. After purchasing a sufficient number of tokens, the messaging application confirms the purchase of the restricted augmented reality experience and removes the access restrictions from the restricted augmented reality experience.

[0126] In some implementations, a user can receive communications from friends that restrict access to augmented reality experiences. For example, as in user interface 900 (… Figure 9A As shown, a user participates in a conversation with one or more other users or friends. During the conversation, one or more messages are exchanged with the friends in the conversation. One of the messages may include an attachment identifying a restricted augmented reality experience 910. This attachment may specify the minimum number of virtual tokens required to purchase permission to access the restricted augmented reality experience identified in the communication. In response to receiving the user's selection of the attachment, the messaging application may activate a camera feed and present a preview of the restricted augmented reality experience. Users can purchase access to the restricted augmented reality experience to remove the restrictions in the same manner discussed above.

[0127] In some implementations, the messaging application presents a graphical user interface 901. Figure 9B This graphical user interface allows users to enter a search string to identify restricted and non-restricted augmented reality experiences. In response to receiving the search string 920, the messaging application searches for names, sets, or attributes associated with augmented reality experiences stored within the messaging application. Specifically, in response to receiving the search string, the messaging application searches its database for a list of non-restricted augmented reality experiences or the most popular restricted augmented reality experiences that match or correspond to the search string. As an example, the messaging application generates a display of user interface 901 that includes both restricted and non-restricted augmented reality experiences. Users can access this information in conjunction with page 501 above. Figure 5B The same or similar ways of interacting with the user interface 901 are discussed.

[0128] Figure 10 This is a flowchart illustrating example operations of message transceiver client 104 during execution of process 1000 according to an exemplary embodiment. Process 1000 may be embodied in computer-readable instructions for execution by one or more processors, such that the operations of process 1000 may be performed partially or entirely by functional components of message transceiver server system 108; accordingly, process 1000 is described below by way of example. However, in other embodiments, at least some operations of process 1000 may be deployed on various other hardware configurations. Operations in process 1000 may be executed in any order, in parallel, or may be skipped and omitted entirely.

[0129] At operation 1001, image processing server 122 receives a request to access the display of multiple augmented reality experiences. In some cases, instead of image processing server 122, or in addition to image processing server 122, it can be performed locally by client device 102. Figure 10 For example, the image processing server 122 receives requests to access personalized pages 500, popular pages 501, pages 600 with restricted augmented reality experiences, or camera devices with augmented reality experience selection areas.

[0130] At operation 1002, image processing server 122 retrieves multiple identifiers for each of the multiple augmented reality experiences. For example, image processing server 122 retrieves icons 532 and 534 for each of the multiple augmented reality experiences. Figure 5A and Figure 5B ).

[0131] At operation 1003, image processing server 122 determines that a given augmented reality experience among a plurality of augmented reality experiences is associated with access restrictions. For example, image processing server 122 determines that second icon 534 is associated with an augmented reality experience with restricted access.

[0132] At operation 1004, image processing server 122 modifies one of a plurality of identifiers associated with a given augmented reality experience in response to determining that a given augmented reality experience is associated with an access restriction. For example, image processing server 122 adds or includes a restriction status icon 536 that can indicate parameters required to remove the restriction (e.g., restriction status icon 536 can specify the price or minimum amount of virtual tokens required to purchase the right to remove the restriction from the corresponding restricted augmented reality experience).

[0133] At operation 1005, image processing server 122 generates a graphical user interface for display on a client device, the graphical user interface including multiple identifiers containing modified given identifiers. For example, image processing server 122 presents the identifiers in the manner discussed above with respect to Figures 5 through 9.

[0134] Machine architecture

[0135] Figure 11This is a schematic representation of machine 1100, in which instructions 1108 (e.g., software, programs, applications, applets, or other executable code) can be executed to cause machine 1100 to perform any one or more of the methods discussed herein. For example, instructions 1108 can cause machine 1100 to perform any one or more of the methods described herein. Instructions 1108 transform a general, unprogrammed machine 1100 into a specific machine 1100 programmed to perform the described and illustrated functions in the manner described. Machine 1100 can operate as a standalone device or can be coupled (e.g., networked) to other machines. In a networked deployment, machine 1100 can 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. Machine 1100 may include, but is not limited to: server computers, client computers, personal computers (PCs), tablet computers, laptop computers, netbooks, set-top boxes (STBs), personal digital assistants (PDAs), entertainment media systems, cellular phones, smartphones, mobile devices, wearable devices (e.g., smartwatches), smart home devices (e.g., smart appliances), other smart devices, web devices, network routers, network switches, network bridges, or any machine capable of sequentially or otherwise executing instructions 1108 specifying actions to be taken by machine 1100. Furthermore, although only a single machine 1100 is shown, the term "machine" should also be considered to include a collection of machines that individually or jointly execute instructions 1100 to perform any one or more of the methods discussed herein. For example, machine 1100 may include client device 102 or any of several server devices forming part of message transceiver server system 108. In some examples, machine 1100 may also include both client and server systems, wherein certain operations of a particular method or algorithm are performed on the server side and certain operations of a particular method or algorithm are performed on the client side.

[0136] Machine 1100 may include a processor 1102, a memory 1104, and an input / output (I / O) unit 1138 that can be configured to communicate with each other via a bus 1140. In the example, processor 1102 (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, processor 1106 and processor 1110 that execute instruction 1108. The term "processor" is intended to include multi-core processors, which may include two or more independent processors (sometimes referred to as "cores") capable of executing instructions simultaneously. Although Figure 11 Multiprocessor 1102 is shown, but machine 1100 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.

[0137] Memory 1104 includes main memory 1112, static memory 1114, and memory cells 1116, all of which are accessible by processor 1102 via bus 1140. Main memory 1104, static memory 1114, and memory cells 1116 store instructions 1108 embodying any one or more of the methods or functions described herein. Instructions 1108 may also reside wholly or partially in main memory 1112, in static memory 1114, in a machine-readable medium within memory cells 1116, in at least one processor 1102 (e.g., in the processor's cache memory), or in any suitable combination thereof during execution by machine 1100.

[0138] I / O component 1138 may include various components for receiving input, providing output, generating output, sending information, exchanging information, capturing measurement results, etc. The specific I / O component 1138 included in a particular machine will depend on the type of machine. For example, portable machines such as mobile phones may include touch input devices or other such input mechanisms, while headless server machines are unlikely to include such touch input devices. It should be understood that I / O component 1138 may include... Figure 11Many other components are not shown. In various examples, I / O component 1138 may include user output component 1124 and user input component 1126. User output component 1124 may include visual components (e.g., displays such as plasma display panels (PDPs), light-emitting diode (LED) displays, liquid crystal displays (LCDs), projectors, or cathode ray tube (CRT) displays), auditory components (e.g., speakers), haptic components (e.g., vibration motors, resistance mechanisms), other signal generators, etc. User input component 1126 may include alphanumeric input components (e.g., keyboards, touchscreens configured to receive alphanumeric input, photoelectric keyboards, or other alphanumeric input components), point-based input components (e.g., mice, touchpads, trackballs, joysticks, motion sensors, or other pointing instruments), haptic input components (e.g., physical buttons, touchscreens providing positioning and force for touch or touch gestures, or other haptic input components), audio input components (e.g., microphones), etc.

[0139] In another example, I / O component 1138 may include biometric component 1128, motion component 1130, environmental component 1132, or position component 1134, as well as a wide range of other components. For example, biometric component 1128 includes components for detecting expressions (e.g., hand expressions, facial expressions, vocal expressions, body posture, or eye tracking), measuring biosignals (e.g., blood pressure, heart rate, body temperature, sweating, or brain waves), and recognizing people (e.g., voice recognition, retinal recognition, facial recognition, fingerprint recognition, or EEG-based recognition). Motion component 1130 includes: accelerometer components (e.g., accelerometer), gravity sensor components, and rotation sensor components (e.g., gyroscope).

[0140] The environmental component 1132 may include, for example, one or more camera devices (with still image / photograph 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 the concentration of hazardous gases for safety purposes or measure pollutants in the atmosphere), or other components that can provide indications, measurements, or signals corresponding to the surrounding physical environment.

[0141] Regarding the camera device, client device 102 may have a camera device system including, for example, a front-facing camera on the front surface of client device 102 and a rear-facing camera on the rear surface of client device 102. The front-facing camera may be used, for example, to capture still images and videos (e.g., "selfies") of the user of client device 102, and then the still images and videos may be enhanced using 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 device mode, which are similarly enhanced with the enhancement data. In addition to the front and rear-facing cameras, client device 102 may also include a 360° camera for capturing 360° photos and videos.

[0142] Furthermore, the camera system of client device 102 may include dual rear cameras (e.g., a main camera and a depth-sensing camera), or even include triple, quadruple, or quintuple rear camera configurations on the front and rear sides of client device 102. For example, these multi-camera systems may include wide-angle cameras, ultra-wide-angle cameras, telephoto cameras, macro cameras, and depth sensors.

[0143] The position component 1134 may include a positioning sensor component (e.g., a GPS receiver component), an altitude sensor component (e.g., an altimeter or barometer that detects air pressure and from which altitude can be obtained), an orientation sensor component (e.g., a magnetometer), etc.

[0144] Various technologies can be used to achieve communication. I / O component 1138 also includes communication component 1136, which is operable to couple machine 1100 to network 1120 or device 1122 via appropriate coupling or connection. For example, communication component 1136 may include a network interface component or another suitable device to interface with network 1120. In further examples, communication component 1136 may include wired communication components, wireless communication components, cellular communication components, near field communication (NFC) components, etc. Components (e.g.) (low energy consumption) Components and other communication components that provide communication via other modes. Device 1122 can be any peripheral device from another machine or various peripheral devices (e.g., a peripheral device coupled via USB).

[0145] Furthermore, communication component 1136 may detect identifiers or include components operable to detect identifiers. For example, communication component 1136 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 one-dimensional barcodes such as Universal Product Code (UPC) barcodes, multi-dimensional barcodes such as Quick Response (QR) codes, Aztec codes, Data Matrix, Dataglyph, MaxiCode, PDF417, UltraCode, UCC RSS-2D barcodes, and other optical codes), or an acoustic detection component (e.g., a microphone for identifying audio signals of tags). Additionally, various information can be obtained via communication component 1136, such as location via Internet Protocol (IP) geolocation, etc. Positioning methods include signal triangulation and NFC beacon signal detection, where the NFC beacon signal can indicate a specific location.

[0146] Various memories (e.g., main memory 1112, static memory 1114, and the memory of processor 1102) and storage units 1116 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 1102, these instructions (e.g., instruction 1108) enable various operations to implement the disclosed examples.

[0147] Instructions 1108 can be sent or received over network 1120 via a network interface device (e.g., a network interface component included in communication component 1136), using a transmission medium and employing any of a plurality of known transmission protocols (e.g., Hypertext Transfer Protocol (HTTP)). Similarly, instructions 1108 can be sent or received via a transmission medium through a coupling to device 1122 (e.g., peer-to-peer coupling).

[0148] Software Architecture

[0149] Figure 12This is a block diagram 1200 illustrating a software architecture 1204 that can be installed on any or more devices described herein. The software architecture 1204 is supported by hardware, such as a machine 1202 including a processor 1220, memory 1226, and I / O components 1238. In this example, the software architecture 1204 can be conceptualized as a stack of layers, where each layer provides specific functionality. The software architecture 1204 includes layers such as an operating system 1212, libraries 1210, frameworks 1208, and applications 1206. Operationally, application 1206 activates API call 1250 through the software stack and receives messages 1252 in response to API call 1250.

[0150] Operating system 1212 manages hardware resources and provides public services. Operating system 1212 includes, for example, a kernel 1214, services 1216, and drivers 1222. Kernel 1214 serves as an abstraction layer between hardware and other software layers. For example, kernel 1214 provides functions such as memory management, processor management (e.g., scheduling), component management, networking, and security settings. Services 1216 can provide other public services to other software layers. Driver 1222 is responsible for controlling the underlying hardware or interfacing with the underlying hardware. For example, driver 1222 may include a display driver, a camera driver, etc. or Low-power drivers, flash drives, serial communication drivers (e.g., USB drives), Drivers, audio drivers, power management drivers, etc.

[0151] Library 1210 provides a common low-level infrastructure used by application 1206. Library 1210 may include system library 1218 (e.g., the C standard library) that provides functions such as memory allocation, string manipulation, and mathematical functions. Furthermore, library 1210 may include API library 1224, such as media libraries (e.g., libraries for supporting the rendering 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 Picture Experts Group (JPEG or JPG), or Portable Web Graphics (PNG)), graphics libraries (e.g., an OpenGL framework for rendering graphic content on a display in two-dimensional (2D) and three-dimensional (3D) formats), database libraries (e.g., SQLite for providing various relational database functions), web libraries (e.g., WebKit for providing web browsing functionality), etc. Library 1210 may also include various other libraries 1228 to provide many other APIs to application 1206.

[0152] Framework 1208 provides a common high-level infrastructure used by application 1206. For example, framework 1208 provides various graphical user interface (GUI) functions, high-level resource management, and high-level location services. Framework 1208 can provide a wide range of other APIs that can be used by application 1206, some of which may be specific to a particular operating system or platform.

[0153] In the example, application 1206 may include home application 1236, contact application 1230, browser application 1232, book reader application 1234, location application 1242, media application 1244, messaging application 1246, game application 1248, and a wide variety of other applications such as external application 1240. Application 1206 is a program that performs the functions defined in the program. One or more applications of application 1206 can be created using various programming languages, 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 particular example, external application 1240 (e.g., used by an entity other than a vendor of a particular platform using Android) TM or iOS TM Applications developed using a Software Development Kit (SDK) can be used on platforms such as iOS. TM ANDROID TM , Mobile software running on the phone's mobile operating system or another mobile operating system. In this example, external application 1240 can activate API calls 1250 provided by operating system 1212 to facilitate the functions described herein.

[0154] Glossary

[0155] "Carrier signal" refers to any intangible medium capable of storing, encoding, or carrying instructions to be executed by a machine, including digital or analog communication signals or other intangible media to facilitate the communication of such instructions. Instructions can be sent or received over a network using a transmission medium via a network interface device.

[0156] "Client device" refers to any machine that interfaces with a communication network to obtain resources from one or more server systems or other client devices. Client devices can be, but are not limited to, mobile phones, desktop computers, laptop computers, portable digital assistants (PDAs), smartphones, tablet computers, ultrabooks, netbooks, laptops, multiprocessor systems, microprocessor-based or programmable consumer electronics, game consoles, set-top boxes, or any other communication device that a user can use to access the network.

[0157] "Communication network" refers to one or more parts of a network, which can be an ad hoc network, intranet, extranet, virtual private network (VPN), local area network (LAN), wireless LAN (WLAN), wide area network (WAN), wireless WAN (WWAN), metropolitan area network (MAN), the Internet, a part of the Internet, a part of the Public Switched Telephone Network (PSTN), a POTS (Plain Old-Style Telephone Service) network, a cellular telephone network, a wireless network, etc. A network, other types of networks, or a combination of two or more such networks. For example, a network or part 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 types of cellular or wireless coupling. In this example, the coupling can implement any data transmission technology of various types, such as Single Carrier Radio Transmission (1xRTT), Evolved Data Optimization (EVDO), General Packet Radio Service (GPRS), Enhanced Data Rate Evolution of GSM (EDGE), the 3rd Generation Partnership Project (3GPP) including 3G, fourth-generation wireless (4G) networks, Universal Mobile Telecommunications System (UMTS), High-Speed ​​Packet Access (HSPA), Global Microwave Access Interoperability (WiMAX), Long Term Evolution (LTE) standards, other data transmission technologies defined by various standards setting organizations, other long-distance protocols, or other data transmission technologies.

[0158] A "component" refers to a device, physical entity, or logic having boundaries defined by functional or subroutine calls, branch points, APIs, or other technologies that provide partitioning or modularity for specific processing or control functions. Components can interface with other components via their interfaces to perform machine processing. Components can be encapsulated functional hardware units designed for use with other components, as well as part of a program that typically performs related functions.

[0159] Components can constitute software components (e.g., code implemented on a machine-readable medium) or hardware components. A “hardware component” is a tangible unit capable of performing certain operations and can be configured or arranged in some physical manner. In various example implementations, one or more computer systems (e.g., standalone computer systems, client computer systems, or server computer systems) or one or more hardware components (e.g., processors or processor groups) of a computer system can be configured by software (e.g., an application or application portion) to perform certain operations as described herein.

[0160] Hardware components can also be implemented mechanically, electronically, or in any suitable combination thereof. For example, a hardware component may include dedicated circuitry or logic permanently configured to perform certain operations. A hardware component may be a dedicated processor, such as a field-programmable gate array (FPGA) or an application-specific integrated circuit (ASIC). A hardware component may also include programmable logic or circuitry systems that are temporarily configured by software to perform certain operations. For example, a hardware component may include software executed by a general-purpose processor or other programmable processor. Once configured by such software, the hardware component becomes a specific machine (or a specific part of a machine) uniquely tailored to perform the configured function and is no longer a general-purpose processor. It should be understood that the decision to implement a hardware component mechanically in a dedicated and permanently configured circuitry system or in a temporarily configured (e.g., software-configured) circuitry system may be made for cost and time considerations. Therefore, the phrase “hardware component” (or “hardware-implemented component”) should be understood to include tangible entities, i.e., entities physically constructed, permanently configured (e.g., hardwired), or temporarily configured (e.g., programmed) to operate or perform certain operations described herein.

[0161] Consider implementations where hardware components are temporarily configured (e.g., programmed), eliminating the need to configure or instantiate each hardware component at any given time. For example, where the hardware components include a general-purpose processor that is configured by software to become a dedicated processor, this general-purpose processor can be configured at different times as its own distinct dedicated processor (e.g., including different hardware components). The software accordingly configures one or more specific processors to constitute a particular hardware component at one time and different hardware components at different times.

[0162] Hardware components can provide information to and receive information from other hardware components. Therefore, the described hardware components can be considered communicatively coupled. In the presence of multiple hardware components, communication can be achieved through signal transmission between or among two or more hardware components (e.g., via appropriate circuitry and buses). In embodiments where multiple hardware components are configured or instantiated at different times, such communication between hardware components can be achieved, for example, by storing information in a memory structure accessed by the multiple hardware components and retrieving information from that memory structure. For example, a hardware component can perform an operation and store the output of that operation in a communicatively coupled memory device. Other hardware components can then access the memory device at a subsequent time to retrieve and process the stored output. Hardware components can also initiate communication with input or output devices and can operate on resources (e.g., collections of information).

[0163] The various operations of the example methods described herein can be performed, at least in part, by one or more processors configured, either temporarily (e.g., by software) or permanently, to perform the relevant operations. Whether temporarily or permanently configured, such processors can constitute processor-implemented components that operate to perform one or more operations or functions described herein. As used herein, "processor-implemented component" refers to a hardware component implemented using one or more processors. Similarly, the methods described herein can be implemented, at least in part, by processors, where a particular processor or one or more processors are examples of hardware. For example, at least some operations of the methods can be performed by one or more processors 1102 or processor-implemented components. Furthermore, one or more processors can also operate to support the execution of relevant operations in a "cloud computing" environment or as "Software as a Service" (SaaS). For example, at least some operations can be performed by a group of computers (as an example of machines including processors), where these operations are accessible via a network (e.g., the Internet) and via one or more appropriate interfaces (e.g., APIs). The execution of certain operations can be distributed among processors, not residing within a single machine, but can be deployed across several machines. In some example implementations, the processor or processor-implemented components may be located in a single geographic location (e.g., within a home environment, an office environment, or a server cluster). In other example implementations, the processor or processor-implemented components may be distributed across several geographic locations.

[0164] "Computer-readable storage medium" refers to both machine-readable storage media and transmission media. Therefore, these terms include both storage devices / media and carrier / modulated data signals. The terms "machine-readable medium," "computer-readable medium," and "device-readable medium" refer to the same thing and can be used interchangeably in this disclosure.

[0165] "Short-lived messages" are messages that can be accessed for a limited time. Email messages can be text, images, videos, etc. The access time for short messages can be set by the sender. Alternatively, the access time can be a default setting or a setting specified by the recipient. Regardless of the setting technology, the message is temporary.

[0166] "Machine storage medium" refers to one or more storage devices and media (e.g., centralized or distributed databases, and associated caches and servers) that store executable instructions, routines, and data. Therefore, 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), FPGAs, and flash memory devices; disks, such as internal hard disks and removable disks; magneto-optical disks; and CD-ROM and DVD-ROM disks. The terms "machine storage medium," "device storage medium," and "computer storage medium" refer to the same thing and are used interchangeably in this disclosure. The terms "machine storage medium," "computer storage medium," and "device storage medium" expressly exclude carrier waves, modulated data signals, and other such media, at least some of which are covered by the term "signal medium."

[0167] "Non-transitory computer-readable storage medium" refers to a tangible medium capable of storing, encoding, or carrying instructions that can be executed by a machine.

[0168] "Signal medium" means any intangible medium capable of storing, encoding, or carrying machine-executable instructions and including digital or analog communication signals, or other intangible medium that facilitates the communication of software or data. The term "signal medium" should be considered to include any form of modulated data signal, carrier wave, etc. The term "modulated data signal" means a signal whose characteristics are set or altered in a manner that encodes information in the signal. The terms "transmission medium" and "signal medium" mean the same thing and may be used interchangeably in this disclosure.

[0169] Changes and modifications may be made to the disclosed embodiments without departing from the scope of this disclosure. These and other changes or modifications are intended to be included within the scope of this disclosure as set forth in the appended claims.

Claims

1. A method for providing a graphical user interface, comprising: The client device implementing the messaging application receives requests to access the display of multiple augmented reality experiences; Retrieve multiple identifiers for each of the plurality of augmented reality experiences; Identify a given augmented reality experience among the plurality of augmented reality experiences and associate it with access restrictions; In response to determining that the given augmented reality experience is associated with the access restriction, modify the given identifier among the plurality of identifiers associated with the given augmented reality experience; and Generate a graphical user interface for display on the client device, the graphical user interface including the plurality of identifiers containing a modified given identifier.

2. The method according to claim 1, wherein, Each of the plurality of augmented reality experiences overlays one or more augmented reality items onto a video displayed by the client device, and wherein the access restrictions include restrictions based on electronic transactions.

3. The method according to any one of claims 1 to 2, further comprising: Determine that the given augmented reality experience is associated with a set of augmented reality experiences; Determine that a subgroup of the augmented reality experience set is not associated with access restrictions; as well as In response to determining that the subgroup includes more than a threshold number of augmented reality experiences, a given identifier for the given augmented reality experience is allowed to be included among the plurality of identifiers in the graphical user interface.

4. The method according to claim 3, further comprising: In response to determining that the subgroup includes fewer than the threshold number of augmented reality experiences, a given identifier for a given augmented reality experience is prevented from being included among the plurality of identifiers in the graphical user interface.

5. The method according to claim 3, wherein, The plurality of identifiers correspond to the set of augmented reality experiences, and the request includes receiving input to select the set of augmented reality experiences from the plurality of sets of augmented reality experiences.

6. The method according to claim 5, further comprising: Determine whether the given augmented reality experience is associated with a popularity criterion that exceeds a popularity threshold; as well as In response to determining that the given augmented reality experience is associated with a popularity criterion exceeding the popularity threshold, the given identifier is presented independently of the plurality of identifiers in the set of augmented reality experiences.

7. The method according to claim 6, wherein, The popularity metric corresponds to the number of users who purchase or preview the given augmented reality experience.

8. The method according to any one of claims 1 to 2, further comprising: Receive input that selects the given identifier to access the given augmented reality experience; as well as In response to receiving the input and in response to determining that the given augmented reality experience is associated with the access restriction, a preview of the augmented reality experience is generated, wherein generating the preview includes: The video is displayed by the client device; Obtain one or more augmented reality items associated with the given augmented reality experience; and The one or more augmented reality items are overlaid on the video as static images, without dynamically adjusting the position of the one or more augmented reality items based on measurements of motion of the client device using accelerometers and gyroscopes.

9. The method according to claim 8, further comprising: An interface is presented for executing electronic transactions associated with the access restrictions; In response to executing the electronic transaction, the access restrictions associated with the given augmented reality experience are removed; as well as After the access restrictions are removed, one or more augmented reality items are overlaid on the video based on measurements of motion of the client device using accelerometers and gyroscopes.

10. The method of claim 9, further comprising: In response to receiving a request to execute the electronic transaction, access the collection of virtual tokens associated with the user; The electronic transaction is completed in response to determining that the set of virtual tokens includes a number of virtual tokens greater than the access limit; and In response to determining that the set of virtual tokens includes a number of virtual tokens less than the access limit value, an interface is presented that allows the user to purchase additional virtual tokens.

11. The method according to any one of claims 1 to 2, wherein, The plurality of identifiers are presented as icons on a given video captured by the client device, and wherein modifying the given identifier includes presenting a representation of the access restrictions.

12. The method of claim 11, further comprising replacing the representation of the access restriction with a representation of the given augmented reality experience in response to determining that the access restriction has been removed.

13. The method according to any one of claims 1 to 2, further comprising: The graphical user interface is displayed with a personalized graphical user interface that includes content selected based on the user profile; as well as The size of the given identifier is modified relative to the rest of the plurality of identifiers.

14. The method according to claim 13, wherein, The remainder of the plurality of identifiers are presented in a first area of ​​the graphical user interface, wherein the given identifier is presented in a plurality of restricted access identifiers of a plurality of restricted access augmented reality experiences in a second area of ​​the graphical user interface, and wherein the plurality of restricted access augmented reality experiences are ranked relative to each other in the second area.

15. The method according to any one of claims 1 to 2, further comprising: The graphical user interface is displayed in a popular graphical user interface that includes content selected based on popularity. as well as The presentation of the given identifier is nested within the remainder of the plurality of identifiers, wherein the plurality of augmented reality experiences associated with the plurality of identifiers are ranked relative to each other, and wherein the indication of the access restriction is presented independently of whether the access restriction has been removed by the user of the client device.

16. The method according to any one of claims 1 to 2, wherein, The request includes at least one of the following: a search string for searching the server to obtain multiple matching augmented reality experiences or a selection of augmented reality experiences with restricted access received in a message from another user.

17. The method according to any one of claims 1 to 2, wherein, The request includes a request to access a page that includes multiple access-restricted identifiers for multiple restricted access augmented reality experiences, wherein the graphical user interface includes introductory tiles explaining how to use the restricted access augmented reality experiences, and wherein the introductory tiles are removed after the page has been accessed a threshold number of times or after the access restrictions have been removed from the given augmented reality experience.

18. The method of claim 17, further comprising: The given identifier is displayed as an icon of a first type with a first size, the first type of icon representing the given augmented reality experience in a first part of the page dedicated to representing the augmented reality experience in which access restrictions have been removed; as well as The multiple restricted access identifiers are displayed as icons of a second type with a second size, the second type of icons representing the multiple restricted access augmented reality experiences in a second part of the page specifically used to represent the augmented reality experiences with access restrictions enabled.

19. A system for providing a graphical user interface, comprising: A processor configured to perform operations including: The client device implementing the messaging application receives requests to access the display of multiple augmented reality experiences; Retrieve multiple identifiers for each of the plurality of augmented reality experiences; Identify a given augmented reality experience among the plurality of augmented reality experiences and associate it with access restrictions; In response to determining that the given augmented reality experience is associated with the access restriction, modify the given identifier among the plurality of identifiers associated with the given augmented reality experience; and Generate a graphical user interface for display on the client device, the graphical user interface including a plurality of identifiers containing a modified given identifier.

20. A non-transitory machine-readable storage medium comprising instructions that, when executed by one or more processors of the machine, cause the machine to perform operations, the operations including: The client device implementing the messaging application receives requests to access the display of multiple augmented reality experiences; Retrieve multiple identifiers for each of the plurality of augmented reality experiences; Identify a given augmented reality experience among the plurality of augmented reality experiences and associate it with access restrictions; In response to determining that the given augmented reality experience is associated with the access restriction, modify the given identifier associated with the given augmented reality experience among the plurality of identifiers; and Generate a graphical user interface to be displayed on the client device, the graphical user interface including a plurality of identifiers containing a modified given identifier.

Images