Dynamic augmented reality experience

Abstract

Systems and methods describe an augmented reality (AR) system for generating an AR experience in real time. The AR experience system receives a selection of an AR experience from an application running on a computer device, displays a first set of textual cues associated with the AR experience on the computer device, receives a first set of image data corresponding to the first set of textual cues, generates a first AR object associated with the AR experience, and displays the first set of image data corresponding to the first set of textual cues on the computer device. The first AR object and a second set of textual cues associated with the AR experience are displayed on the computer device, a second set of image data corresponding to the second set of textual cues is received, and a second AR object associated with the AR experience is generated.

Description

[0001] Priority claim

[0002] This application claims the benefit of priority to U.S. patent application Ser. No. 17 / 740,598, filed May 10, 2022, which is incorporated herein by reference in its entirety. Technical Field

[0003] Embodiments herein generally relate to augmented reality. More specifically, but not by way of limitation, systems and methods herein describe real-time dynamic augmented reality gaming through semantic understanding of the real world. Background Art

[0004] Augmented reality allows users to enhance their experience of the physical world with computer-generated input. Augmented reality experiences are interactive experiences that can be enhanced through multiple sensory modalities. BRIEF DESCRIPTION OF THE DRAWINGS

[0005] In the drawings, which are not necessarily drawn to scale, similar reference numerals may describe similar components in different views. To easily identify the discussion of any particular element or action, the highest digit or digits in the reference numeral refer to the figure number in which the element is first introduced. Some non-limiting examples are shown in the accompanying drawings, in which:

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

[0007] Figure 2 is a diagrammatic representation of a messaging system having both client-side and server-side functionality according to some examples.

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

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

[0010] Figure 5 is a flow diagram for an access restriction process according to some examples.

[0011] Figure 6 A head wearable device according to an example embodiment is shown.

[0012] Figure 7 is a block diagram illustrating components of an AR experience system according to an example implementation.

[0013] Figure 8 A method for generating an AR experience according to example implementations is shown.

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

[0015] Fig.10 is a block diagram illustrating a software architecture in which examples may be implemented.

[0016] Fig.11 An aspect of the subject matter according to one implementation is shown. DETAILED DESCRIPTION

[0017] The following paragraphs describe an improved AR experience system that uses computer vision capabilities to understand the semantics and physical shapes of the real world. The AR experience system can be used to construct puzzles, games, or other interactive AR experiences for users in real time. The AR experience system constructs different interactive AR experiences for users based on commonalities in the real world.

[0018] For example, a user can launch the AR experience system from within an application on a phone, wearable AR device, or other computer device. The AR experience system provides a textual affordance asking the user to look around the office. When a table is detected within the field of view of the computer device, the AR experience system places an AR object, such as an AR book, on top of the table.

[0019] After placing the AR book on the table, the AR experience system provides the user with an additional textual affordance instructing the user to open the AR book (via tactile input, gesture, voice command, or any combination). Upon opening the book, the AR experience system provides a affordance (text or other visual affordance) that a key is present next to the window. The user searches for the window in their real-world physical space, and once the window appears in the field of view of the computer device, the user is shown the AR key generated by the AR experience system. The user can continue to walk around in their real-world physical space and find a door, where the AR experience system uses the AR key to "unlock" the door.

[0020] The door may take the user outside, and the AR experience system can use machine learning to determine that the user is now outside rather than indoors. Based on this determination, the AR experience system can apply AR effects such as AR weather patterns (e.g., rain, snow) to the field of view of the computer device.

[0021] Therefore, the AR experience system uses a combination of machine learning and different modalities to build an AR experience using semantic understanding of the real world. The disclosed AR experience system receives a field of view from one or more image sensors of a computer device. The computer device may be a device with AR / VR capabilities. In response to receiving the field of view of the image sensor of the computer device, the AR experience system displays a first set of text prompts on a graphical user interface (GUI) of the computer device. The first set of text prompts is associated with an augmented reality (AR) experience (e.g., as described in the above example). The AR experience system receives a first set of image data corresponding to the first set of text prompts from the computer device, and generates a first AR object associated with the AR experience. The AR experience system displays the first AR object and a second set of text prompts associated with the AR experience on the GUI. The AR experience system receives a second set of image data corresponding to the second set of text prompts, and in response to receiving the second set of image data, generates a second AR object associated with the AR experience. Further details of the AR experience system are described below.

[0022] Networked computing environment

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

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

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

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

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

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

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

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

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

[0032] The AR experience system 130 uses a combination of machine learning and different modalities to build an AR experience using semantic understanding of the real world. For example, the AR experience system 130 is used to generate an AR experience for the user in real time based on commonalities in the real world.

[0033] Returning to the messaging client 104, the features and functions of the external resource (e.g., application 106 or applet) are available to the user via the interface of the messaging client 104. In this context, "external" refers to the fact that the application 106 or applet is outside the messaging client 104. External resources are usually provided by a third party, but can also be provided by the creator or provider of the messaging client 104. The messaging client 104 receives a user selection of an option to launch or access the features of such an external resource. The external resource can be an application 106 (e.g., a "local app") installed on the client device 102, or a small-scale version of the application (e.g., a "applet") hosted on the client device 102 or away from the client device 102 (e.g., on a third-party server 110). The small-scale version of the application includes a subset of the features and functions of the application (e.g., a full-scale, local version of the application) and is implemented using a markup language document. In one example, the small-scale version of the application (e.g., a "applet") is a web-based markup language version of the application and is embedded in the messaging client 104. In addition to using markup language documents (eg, *ml files), applets may include scripting languages ​​(eg, .*js files or .json files) and style sheets (eg, *ss files).

[0034] In response to receiving a user selection of an option to launch or access a feature of an external resource, the messaging client 104 determines whether the selected external resource is a web-based external resource or a locally installed application 106. In some cases, the application 106 locally installed on the client device 102 can be independent of the messaging client 104 and launched separately from the messaging client 104, such as by selecting an icon corresponding to the application 106 on a home screen of the client device 102. A small-scale version of such an application can be launched or accessed via the messaging client 104, and in some examples, none of the portions of the small-scale application can be accessed outside of the messaging client 104 or limited portions of the small-scale application can be accessed outside of the messaging client 104. The small-scale application can be launched by the messaging client 104, for example, receiving a markup language document associated with the small-scale application from a third-party server 110 and processing such a document.

[0035] In response to determining that the external resource is a locally installed application 106, the messaging client 104 instructs the client device 102 to launch the external resource by executing the locally stored code corresponding to the external resource. In response to determining that the external resource is a web-based resource, the messaging client 104 communicates with the third-party server 110 (for example) to obtain a markup language document corresponding to the selected external 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.

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

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

[0038] System Architecture

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

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

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

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

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

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

[0045] In other examples, the enhancement system 208 provides a merchant-based publishing platform that enables merchants to select specific media overlays associated with geographic locations via a bidding process. For example, the enhancement system 208 associates the highest bidding merchant's media overlay with the corresponding geographic location for a predefined amount of time.

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

[0047] The gaming system 212 provides various gaming functions within the context of the messaging client 104. The messaging client 104 provides a gaming interface that provides a list of available games that can be launched by a user within the context of the messaging client 104 and played with other users of the messaging system 100. The messaging system 100 also enables a particular user to invite other users to participate in playing a particular game by sending an invitation to such other users from the messaging client 104. The messaging client 104 also supports both voice messaging and text messaging within the context of game play (e.g., chatting), provides leaderboards for games, and also supports providing in-game rewards (e.g., game coins and items).

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

[0049] To integrate the functionality of the SDK into a web-based resource, the SDK is downloaded by the third-party server 110 from the messaging server 118, or received by the third-party server 110 in other ways. Once downloaded or received, the SDK will be 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.

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

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

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

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

[0054] The AR experience system 130 uses a combination of machine learning and different modalities to build AR experiences using semantic understanding of the real world. For example, the AR experience system 130 is used to generate AR experiences for users in real time based on commonalities in the real world. In some examples, various aspects of the AR experience system 130 are implemented on the messaging server 118. In some examples, various aspects of the AR experience system 130 are implemented on the application server 114.

[0055] Data Architecture

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

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

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

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

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

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

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

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

[0064] 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 input or information collected by the client device 102 during the message creation process. Examples of data filters include the current temperature at a particular location, the current speed at which the sending user is traveling, the battery life of the client device 102, or the current time.

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

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

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

[0068] Real-time video processing can be performed using any kind of video data (e.g., video streams, video files, etc.) stored in the memory of any kind of computerized system. For example, a user can load video files and store them in the memory of the device, or a sensor of the device can be used to generate a video stream. In addition, any object, such as a human face and parts of a human body, an animal, or a non-living thing (e.g., a chair, a car, or other objects) can be processed using computer animation models.

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

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

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

[0072] Other methods and algorithms suitable for face detection can be used. For example, in some examples, landmarks are used to locate features, which represent distinguishable points that exist in most of the images considered. For example, for facial landmarks, the location of the left pupil can be used. If the initial landmarks are not recognizable (for example, if the person wears an eye patch), secondary landmarks can be used. Such landmark identification procedures can be used for any such objects. In some examples, a set of landmarks forms a shape. The coordinates of the points in the shape can be used to represent the shape as a vector. One shape is aligned with another shape using a similarity transformation (allowing translation, scaling, and rotation) that minimizes the average Euclidean distance between the shape points. The mean shape (meanshape) is the average value of the aligned training shapes.

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

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

[0075] In some examples, a computer animation model for transforming image data can be used by a system in which a user can capture an image or video stream of the user (e.g., a selfie) using a client device 102 having a neural network that operates as part of a messaging client 104 operating on the client device 102. A transformation system operating within the messaging client 104 determines the presence of a face within the image or video stream and provides a modification icon associated with the computer animation model to transform the data image, or the computer animation model can be presented as associated with an interface described herein. The modification icon includes the following changes, which can be the basis for modifying the face of the user within the image or video stream as part of the modification operation. Once the modification icon is selected, the transformation system initiates a process of transforming the image of the user 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 can implement a complex convolutional neural network on a portion of the image or video stream to generate and apply the selected modification. That is, a user can capture an image or video stream, and once a modification icon has been selected, the modified result can be presented in real time or near real time. In addition, when the video stream is being captured, the modification can be persistent and the selected modification icon remains toggled. Machine learning neural networks can be used to implement such modifications.

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

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

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

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

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

[0081] Database 126 may also store gesture data in gesture table 322, store revelations in revelation table 318, and store voice command keywords in keyword table 320. Gesture data may include gestures that can be recognized by AR experience system 130 to modify one or more aspects of the AR experience. For example, gestures may be used to select AR objects generated by AR experience system 130 during an interactive AR experience. Revelation table 318 stores textual prompts associated with the AR experience. The textual prompts may be based on commonalities in the real world. Keyword table 320 stores voice command keywords for triggering AR effects in AR experience system 130.

[0082] Data communication architecture

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0097] Time-based access restriction architecture

[0098] Figure 5 is a schematic diagram illustrating an access restriction process 500 according to which access to content (e.g., ephemeral message 502 and associated multimedia data payload) or a collection of content (e.g., ephemeral message group 504) can be time-restricted (e.g., made ephemeral).

[0099] The ephemeral message 502 is shown to be associated with a message duration parameter 506, the value of which determines the amount of time that the messaging client 104 will display the ephemeral message 502 to the receiving user of the ephemeral message 502. In one example, depending on the amount of time specified by the sending user using the message duration parameter 506, the receiving user can view the ephemeral message 502 for up to 10 seconds.

[0100] The message duration parameter 506 and the message recipient identifier 424 are shown as inputs to a message timer 510, which is responsible for determining the amount of time that the transient message 502 is shown to a particular receiving user identified by the message recipient identifier 424. In particular, the transient message 502 is shown to the associated receiving user only for a period of time determined by the value of the message duration parameter 506. The message timer 510 is shown as providing an output to a more generalized transient timer system 202, which is responsible for the overall timing of displaying content (e.g., the transient message 502) to the receiving user.

[0101] Short message 502 Figure 5504 (e.g., a collection of messages in a personal story or an event story). The ephemeral message group 504 has an associated group duration parameter 508, the value of which determines the duration for which the ephemeral message group 504 is presented and accessible to users of the messaging system 100. For example, the group duration parameter 508 may be the duration of a concert, where the ephemeral message group 504 is a collection of content about the concert. Alternatively, a user (an owning user or a curator user) may specify a value for the group duration parameter 508 when performing setup and creation of the ephemeral message group 504.

[0102] In addition, each ephemeral message 502 within the ephemeral message group 504 has an associated group participation parameter 512, the value of which determines the duration for which the ephemeral message 502 is accessible within the context of the ephemeral message group 504. Thus, a particular ephemeral message group 504 may "expire" and become inaccessible within the context of the ephemeral message group 504 before the ephemeral message group 504 itself expires according to the group duration parameter 508. The group duration parameter 508, the group participation parameter 512, and the message recipient identifier 424 each provide inputs to a group timer 514, which is operable to first determine whether a particular ephemeral message 502 in the ephemeral message group 504 is to be displayed to a particular receiving user, and if so, how long to display it. Note that the identity of the particular receiving user is also known to the ephemeral message group 504 due to the message recipient identifier 424.

[0103] Thus, the group timer 514 is operable to control the total lifespan of the associated ephemeral message group 504 and the individual ephemeral messages 502 included in the ephemeral message group 504. In one example, each ephemeral message 502 within the ephemeral message group 504 remains viewable and accessible for a period of time specified by the group duration parameter 508. In another example, within the context of the ephemeral message group 504, a particular ephemeral message 502 may expire based on the group participation parameter 512. Note that even within the context of the ephemeral message group 504, the message duration parameter 506 may still determine the duration for which a particular ephemeral message 502 is displayed to a receiving user. Thus, the message duration parameter 506 determines the duration for which a particular ephemeral message 502 is displayed to a receiving user, regardless of whether the receiving user is viewing the ephemeral message 502 within or outside the context of the ephemeral message group 504.

[0104] The transient timer system 202 may also be operable to remove a particular transient message 502 from the transient message group 504 based on a determination that an associated group participation parameter 512 has been exceeded. For example, where a sending user has established a group participation parameter 512 of 24 hours from posting, the transient timer system 202 will remove the associated transient message 502 from the transient message group 504 after the designated 24 hours. The transient timer system 202 may also be operable to remove a transient message group 504 when the group participation parameter 512 for each transient message 502 within the transient message group 504 has expired, or when the transient message group 504 itself has expired according to the group duration parameter 508.

[0105] In some use cases, the creator of a particular ephemeral message group 504 may specify an indefinite group duration parameter 508. In this case, the expiration of the group participation parameter 512 for the last remaining ephemeral message 502 within the ephemeral message group 504 will determine when the ephemeral message group 504 itself expires. In this case, a new ephemeral message 502 with a new group participation parameter 512 added to the ephemeral message group 504 effectively extends the life of the ephemeral message group 504 to a value equal to the group participation parameter 512.

[0106] In response to the transient timer system 202 determining that the transient message group 504 has expired (e.g., is no longer accessible), the transient timer system 202 communicates with the messaging system 100 (and, for example, in particular, the messaging client 104) to cause the indicia (e.g., icon) associated with the relevant transient message group 504 to no longer be displayed within the user interface of the messaging client 104. Similarly, when the transient timer system 202 determines that the message duration parameter 506 for a particular transient message 502 has expired, the transient timer system 202 causes the messaging client 104 to no longer display the indicia (e.g., icon or text identification) associated with the transient message 502.

[0107] Figure 6 A head wearable device 600 is shown according to an example embodiment. Figure 6 A perspective view of a head wearable device 200 is shown according to an example implementation. In some examples, the client device 102 can include the head wearable device 200. In some examples, the head wearable device can be part of the messaging server system 108.

[0108] exist Figure 6, the head wearable device 200 is a pair of glasses. In some embodiments, the head wearable device 200 may be sunglasses or goggles. Some embodiments may include one or more wearable devices, such as a pendant with an integrated camera that is integrated with, communicates with, or is coupled to the head wearable device 200 or the client device 102. Any desired wearable device may be used in conjunction with embodiments of the present disclosure, such as a watch, headphones, wristband, earbuds, clothing (such as a hat or jacket with integrated electronics), a clip-on electronic device, or any other wearable device. It should be understood that, although not shown, one or more portions of the system included in the head wearable device 200 may be included in a client device 102 that may be used in conjunction with the head wearable device 200.

[0109] exist Figure 6 In the embodiment, the head wearable device 200 is a pair of glasses including a frame 610, which includes a frame (or frame) that is respectively coupled to two handles (or temples) via hinges and / or end pieces. The frame of the frame 610 carries or accommodates a pair of lenses (e.g., lens 612 and lens 614). The frame 610 includes a first (e.g., right) side coupled to the first handle and a second (e.g., left) side coupled to the second handle. The first side is opposite to the second side of the frame 610.

[0110] The head wearable device 200 also includes a camera module (not shown), which includes a camera lens (e.g., camera lens 606, camera lens 608) and at least one image sensor. Camera lens 606 and camera lens 608 can be perspective camera lenses or non-perspective camera lenses. The non-perspective camera lens can be, for example, a fisheye lens, a wide-angle lens, an omnidirectional lens, etc. The image sensor captures digital video through camera lens 606 and camera lens 608. The image can also be a still image frame or a video including multiple still image frames. The camera module can be coupled to frame 610. As shown in FIG. Figure 6 As shown in , frame 610 is coupled to camera lens 606 and camera lens 608 so that the camera lenses (e.g., camera lens 606, camera lens 608) face away from the user (e.g., rear camera). Camera lens 606 and camera lens 608 can be perpendicular to lens 612 and lens 614. The camera module can also include dual front cameras (e.g., cameras facing the user) separated by the width of frame 610 or the width of the head of the user of head wearable device 200.

[0111] exist Figure 6, two handles (or temples) are coupled to microphone housing 602 and microphone housing 604, respectively. The first handle and the second handle are coupled to opposite sides of the frame 610 of the head wearable device 200. The temples are coupled to the frame 610 via temple attachments. The first handle is coupled to the first microphone housing 602, and the second handle is coupled to the second microphone housing 604. The microphone housing 602 and the microphone housing 604 can be coupled to the handles between the position of the frame 610 and the position of the temple tip. When the user wears the head wearable device 200, the microphone housing 602 and the microphone housing 604 can be located on either side of the temple of the user.

[0112] like Figure 6 As shown in , microphone housing 602 and microphone housing 604 enclose multiple microphones (not shown). A microphone is an air interface sound pickup device that converts sound into an electrical signal. More specifically, a microphone is a transducer that converts sound pressure into an electrical signal (e.g., an acoustic signal). The microphone can be a digital or analog micro-electromechanical system (MEMS) microphone. The acoustic signal generated by the microphone can be a pulse density modulation (PDM) signal.

[0113] Figure 7 704 , and a speech system 706 .

[0114] The revelation system 702 provides text prompts to the user who starts the AR experience. The text prompts include revelations related to which gestures, voice commands, tactile inputs, etc. are available within a specific AR experience. In some examples, the text prompts are generated based on commonalities that exist in the real world. The text prompts can be stored in the revelation table 318. For example, the text prompts can ask the user to look around their physical space. In some examples, the text prompts are predetermined prompts stored in the revelation table 318. In some examples, a machine learning model (or any suitable computer vision algorithm) is used to generate and select text prompts. For example, the text prompts are generated and selected based on various aspects of the client device 102 (e.g., the location or positioning of the client device 102) or various aspects associated with the user of the client device 102 (e.g., user profile data 316). The text prompts are displayed on the client device 102. The revelation system 702 can provide text prompts associated with various AR objects within the AR experience. For example, if the AR experience system 130 detects a table and places an AR book on the table, the revelation system 702 can provide a text prompt prompting the user to open the book.

[0115] The gesture system 704 recognizes and determines the user's gestures. For example, the gesture system 704 uses one or more image sensors of the client device 102 to capture an image of the user, and analyzes the image to detect a hand. Once the hand is detected, the gesture system 704 identifies the joint positions in the hand, and determines the pose of the hand based on the joint positions. The gesture system 704 recognizes gestures based on the pose of the hand. The gesture system 704 can use data from the gesture table 322 to determine the pose of the hand and recognize the gesture. In some examples, the gesture system 704 uses a machine learning model that is trained to determine gestures based on analysis of one or more images of the hand. In some examples, based on detecting a specific gesture, the gesture system 704 causes an AR effect or AR object associated with the recognized gesture to be displayed.

[0116] The speech system 706 captures audio commands from the user and determines keywords of the audio commands. Keywords are used to generate or modify AR effects or AR objects in the AR experience. The speech system 706 uses a machine learning model that detects keywords from the audio data stream. The machine learning model can be a natural language processing (NLP) model. Keywords detected by the machine learning model can be stored in association with the keyword table 320.

[0117] Although the flow chart described below can show the operation as a sequential process, many operations in the operation can be performed in parallel or simultaneously. In addition, the order of the operation can be rearranged. When the operation of the process is completed, the process is terminated. The process can correspond to a method, a program, an algorithm, etc. The operation of the method can be performed in whole or in part, can be performed in combination with some or all of the operations in other methods, and can be performed by any number of different systems (e.g., the system described herein) or any part thereof (e.g., a processor included in any one of the systems).

[0118] Figure 8 800 is a method for generating an AR experience according to an example implementation. In one example, a processor in AR experience system 130, a processor in client device 102, a processor in messaging server system 108, or any combination thereof may perform the operations in method 800.

[0119] At operation 802, the AR experience system 130 receives a selection from a computer device. The selection causes an augmented reality (AR) experience to be launched on an application running on the computer device. For example, the application may be a messaging client 104. The application includes an interface that displays a set of selectable user interface elements (e.g., buttons, check boxes, etc.) on the GUI of the client device 102. Each of the selectable user interface elements corresponds to an augmented reality content item (e.g., a combination of Figure 3In some examples, the augmented reality content item includes an AR experience. The AR experience can be a puzzle, a game (e.g., a treasure hunt, a virtual escape room), etc.

[0120] AR experience system 130 receives a selection of a selectable user interface element from a set of selectable user interface elements, and in response to the selection, AR experience system 130 causes a first set of textual prompts to be displayed on the GUI of client device 102 in operation 804. The first set of textual prompts is associated with the AR experience. The textual prompts may be selected and displayed by affordance system 702.

[0121] At operation 806, AR experience system 130 receives a first set of image data corresponding to a first set of text prompts from one or more image sensors of client device 102. In response to receiving the first set of image data, at operation 808, AR experience system 130 generates a first AR object associated with the AR experience. In some examples, during operation 806, AR experience system 130 uses an image machine learning model to analyze the first image data. The image machine learning model can be trained to recognize objects within the first image data. For example, before AR experience system 130 performs operation 810, the objects recognized within the first image data must correspond to the first set of text prompts. Although the image machine learning model is described as an object detection model, it should be understood that any suitable machine learning model for image processing can be used.

[0122] In some examples, AR experience system 130 also receives a first set of audio data corresponding to the first set of text prompts from a microphone of client device 102. AR experience system 130 generates a first AR object based on the first set of image data and the first set of audio data. In some examples, AR experience system 130 generates the first AR object using only the first set of audio data. The first set of audio data can be analyzed using speech system 706.

[0123] At operation 810 , AR experience system 130 causes display of the first AR object and a second set of textual prompts associated with the AR experience on the GUI of client device 102 . The second set of textual prompts is generated and displayed by affordance system 702 .

[0124] At operation 812, AR experience system 130 receives a second set of image data corresponding to a second set of text prompts from one or more image sensors of client device 102. The second set of image data may be analyzed using the image machine learning model described in conjunction with operation 806.

[0125] At operation 814, in response to receiving the second set of image data, AR experience system 130 generates a second AR object associated with the AR experience. In some examples, the second AR object is associated with the first AR object. For example, the second AR object can be based on the first AR object (e.g., the first AR object is an AR book with an indication to search for a key, and the second AR object is an AR key).

[0126] Although the above operations describe generating an AR object associated with an AR experience, the AR experience system 130 may also generate an AR effect associated with the AR experience instead. In some examples, the AR experience system 130 may generate a combination of an AR object and an AR effect. The AR effect may include an audio or visual image AR overlay or filter. In some examples, the AR experience system 130 causes a third set of text prompts associated with the AR experience to be displayed. The third set of text prompts is generated and displayed by the revelation system 702. The AR experience system 130 receives a third set of image data corresponding to the third set of text prompts. The third set of image data is analyzed using the above-mentioned image machine learning model. The AR experience system 130 identifies the location of the client device 102 based on the third set of image data, and generates an AR effect based on the identified location. For example, the AR experience system 130 may determine that the client device 102 is outdoors rather than indoors, and may generate an AR effect based on this determination.

[0127] In some examples, AR experience system 130 receives tactile input from a user of client device 102. In response to receiving the tactile input from the user, AR experience system 130 causes display of a fourth set of textual prompts associated with the AR experience. In some examples, in response to receiving the tactile input, AR experience system 130 displays or modifies an AR effect or an AR object.

[0128] In some examples, AR experience system 130 receives a gesture from a user of client device 102. The gesture may be recognized using gesture system 704. In response to receiving the gesture, AR experience system 130 causes display of a fifth set of textual prompts associated with the AR experience. In some examples, in response to receiving the gesture, AR experience system 130 displays or modifies an AR effect or AR object.

[0129] During the operations described above in method 800 , AR experience system 130 may receive any combination of image data, audio data, tactile input, and gestures to generate or modify AR objects and AR effects, and select and generate text prompts in real time.

[0130] Machine Architecture

[0131] Fig. 9The illustrative embodiment of the present invention is a diagrammatic representation of a machine 900 in which instructions 910 (e.g., software, programs, applications, applet, app, or other executable code) may be executed to cause the machine 900 to perform any one or more of the methods discussed herein. For example, the instructions 910 may cause the machine 900 to perform any one or more of the methods described herein. The instructions 910 convert a general purpose, unprogrammed machine 900 into a specific machine 900 that is programmed to perform the functions described and illustrated in the manner described. The machine 900 may operate as a standalone device or may be coupled (e.g., networked) to other machines. In a network deployment, the machine 900 may operate as a server machine or a client machine in a server-client network environment, or as a peer machine in a peer-to-peer (or distributed) network environment. The machine 900 may include, but is not limited to, a server computer, a client computer, a personal computer (PC), a tablet computer, a laptop computer, a netbook, a set-top box (STB), a personal digital assistant (PDA), an entertainment media system, a cellular phone, a smart phone, a mobile device, a wearable device (e.g., a smart watch), a smart home device (e.g., a smart appliance), other smart devices, a web appliance, a network router, a network switch, a network bridge, or any machine capable of sequentially or otherwise executing instructions 910 specifying actions to be taken by the machine 900. In addition, although only a single machine 900 is shown, the term "machine" should also be taken to include a collection of machines that individually or jointly execute instructions 910 to perform any one or more of the methods discussed herein. For example, the machine 900 may include any of the client device 102 or a number of server devices that form part of the messaging server system 108. In some examples, the machine 900 may also include both a client system and a server system, wherein certain operations of a particular method or algorithm are performed on the server side, and certain operations of the particular method or algorithm are performed on the client side.

[0132] The machine 900 may include a processor 904, a memory 906, and an input / output I / O component 902, which may be configured to communicate with each other via a bus 940. In an example, the processor 904 (e.g., a central processing unit (CPU), a reduced instruction set computing (RISC) processor, a complex instruction set computing (CISC) processor, a graphics processing unit (GPU), a digital signal processor (DSP), an application specific integrated circuit (ASIC), a radio frequency integrated circuit (RFIC), another processor, or any suitable combination thereof) may include, for example, a processor 908 and a processor 912 that execute instructions 910. The term "processor" is intended to include multi-core processors, which may include two or more independent processors (sometimes referred to as "cores") that can execute instructions simultaneously. Although Fig. 9 Multiple processors 904 are shown, but the machine 900 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.

[0133] The memory 906 includes a main memory 914, a static memory 916, and a storage unit 918, which are all accessible by the processor 904 via the bus 940. The main memory 906, the static memory 916, and the storage unit 918 store instructions 910 that implement any one or more of the methods or functions described herein. The instructions 910 may also reside, completely or partially, within the main memory 914, within the static memory 916, within the machine-readable medium 920 within the storage unit 918, within at least one of the processors 904 (e.g., within a cache memory of a processor), or within any suitable combination thereof during execution thereof by the machine 900.

[0134] I / O components 902 may include various components that receive input, provide output, generate output, send information, exchange information, capture measurements, etc. The specific I / O components 902 included in a particular machine will depend on the type of machine. For example, a portable machine such as a mobile phone may include a touch input device or other such input mechanism, while a headless server machine will be less likely to include such a touch input device. It should be understood that I / O components 902 may include Fig. 9928. In various examples, the I / O components 902 may include a user output component 926 and a user input component 928. The user output component 926 may include a visual component (e.g., a display such as a plasma display panel (PDP), a light emitting diode (LED) display, a liquid crystal display (LCD), a projector, or a cathode ray tube (CRT)), an acoustic component (e.g., a speaker), a tactile component (e.g., a vibration motor, a resistance mechanism), other signal generators, etc. The user input component 928 may include an alphanumeric input component (e.g., a keyboard, a touch screen configured to receive alphanumeric input, an optical keyboard, or other alphanumeric input component), a point-based input component (e.g., a mouse, a touch pad, a trackball, a joystick, a motion sensor, or other pointing instrument), a tactile input component (e.g., a physical button, a touch screen or other tactile input component that provides the location and force of a touch or touch gesture), an audio input component (e.g., a microphone), etc.

[0135] In other examples, the I / O component 902 may include a biometric component 930, a motion component 932, an environmental component 934, or a position component 936, as well as a wide range of other components. For example, the biometric component 930 includes components for detecting expressions (e.g., hand expressions, facial expressions, voice expressions, body postures, or eye tracking), measuring biosignals (e.g., blood pressure, heart rate, body temperature, sweat, or brain waves), identifying people (e.g., voice recognition, retinal recognition, facial recognition, fingerprint recognition, or EEG-based recognition), etc. The motion component 932 includes an acceleration sensor component (e.g., an accelerometer), a gravity sensor component, and a rotation sensor component (e.g., a gyroscope).

[0136] Environmental components 934 include, for example, one or more cameras (with still image / photo and video capabilities), lighting sensor components (e.g., a photometer), temperature sensor components (e.g., one or more thermometers that detect ambient temperature), humidity sensor components, pressure sensor components (e.g., a barometer), acoustic sensor components (e.g., one or more microphones that detect background noise), proximity sensor components (e.g., an infrared sensor that detects nearby objects), gas sensors (e.g., a gas detection sensor for detecting concentrations of hazardous gases for safety purposes or for measuring pollutants in the atmosphere), or other components that can provide indications, measurements, or signals corresponding to the surrounding physical environment.

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

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

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

[0140] A variety of technologies may be used to achieve communication. The I / O component 902 also includes a communication component 938 that is operable to couple the machine 900 to the network 922 or device 924 via a corresponding coupling or connection. For example, the communication component 938 may include a network interface component or another suitable device that interfaces with the network 922. In other examples, the communication component 938 may include a wired communication component, a wireless communication component, a cellular communication component, a near field communication (NFC) component, Parts (e.g. Low energy consumption), Components and other communication components that provide communication via other modalities. Device 924 can be another machine or any of a variety of peripheral devices (e.g., a peripheral device coupled via USB).

[0141] In addition, the communication component 938 can detect an identifier or include a component operable to detect an identifier. For example, the communication component 938 can 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 bar codes such as Universal Product Code (UPC) bar codes, multi-dimensional bar codes such as Quick Response (QR) codes, Aztec codes, Data Matrix, Dataglyph, MaxiCode, PDF417, UltraCode, UCC RSS-2D bar codes, and other optical codes) or an acoustic detection component (e.g., a microphone for identifying an audio signal of a tag). In addition, various information can be obtained via the communication component 938, such as a location obtained via Internet Protocol (IP) geolocation, ... Location derived from signal triangulation, location derived via detection of NFC beacon signals that can indicate a specific location, etc.

[0142] Various memories (e.g., main memory 914, static memory 916, and memory of processor 904) and storage unit 918 may store one or more sets of instructions and data structures (e.g., software) used by or implementing any one or more of the methods or functions described herein. When executed by processor 904, these instructions (e.g., instructions 910) cause various operations to implement the disclosed examples.

[0143] The instructions 910 may be sent or received via a network interface device (e.g., a network interface component included in the communication component 938) using a transmission medium and using any of several well-known transmission protocols (e.g., Hypertext Transfer Protocol (HTTP)) over the network 922. Similarly, the instructions 910 may be sent or received via a coupling (e.g., a peer-to-peer coupling) to the device 924 using a transmission medium.

[0144] Software Architecture

[0145] Fig.101000 is a block diagram illustrating a software architecture 1004 that may be installed on any one or more of the devices described herein. The software architecture 1004 is supported by hardware such as a machine 1002 including a processor 1020, a memory 1026, and an I / O component 1038. In this example, the software architecture 1004 may be conceptualized as a stack of layers, where each layer provides specific functionality. The software architecture 1004 includes layers such as an operating system 1012, a library 1010, a framework 1008, and an application 1006. In operation, the application 1006 invokes an API call 1050 through the software stack and receives a message 1052 in response to the API call 1050.

[0146] The operating system 1012 manages hardware resources and provides public services. The operating system 1012 includes, for example, a core 1014, a service 1016, and a driver 1022. The core 1014 serves as an abstraction layer between the hardware and other software layers. For example, the core 1014 provides functions such as memory management, processor management (e.g., scheduling), component management, networking, and security settings. The service 1016 can provide other public services to other software layers. The driver 1022 is responsible for controlling the underlying hardware or interfacing with the underlying hardware. For example, the driver 1022 may include a display driver, a camera driver, or Low-power drivers, Flash drivers, Serial communication drivers (e.g., USB drivers), Drivers, audio drivers, power management drivers, etc.

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

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

[0149] In an example, applications 1006 may include a home application 1036, a contacts application 1030, a browser application 1032, a book reader application 1034, a positioning application 1042, a media application 1044, a messaging application 1046, a game application 1048, and a variety of other applications such as third-party applications 1040. Applications 1006 are programs that execute functions defined in the program. Various programming languages ​​may be used to create one or more of the applications 1006 constructed in various ways, such as an object-oriented programming language (e.g., Objective-C, Java, or C++) or a procedural programming language (e.g., C or assembly language). In a specific example, third-party applications 1040 (e.g., provided by an entity other than the vendor of a particular platform using ANDROID TM or IOS TM Software Development Kit (SDK) can be used for mobile operating systems, such as IOS TM ANDROID TM , Phone, or other mobile operating system running on the mobile software. In this example, the third-party application 1040 can activate the API call 1050 provided by the operating system 1012 to facilitate the functions described in this article.

[0150] System with head wearable device

[0151] Fig.11 A system in which a head wearable device 200 may be implemented is shown according to an example embodiment. Fig.11 is a high-level functional block diagram of an example head wearable device 600 that communicatively couples a mobile client device 102 (or client device 1104 ) and a server system 1132 via various networks 1138 .

[0152] The head wearable device 200 includes a camera device, such as at least one of a visible light camera device 1112, an infrared transmitter 1114, and an infrared camera device 1116. The camera device may include Figure 6 A camera module including a camera lens 606 and a camera lens 608.

[0153] The client device 102 may be able to connect with the head wearable device 200 using both a low power wireless connection 1134 and a high speed wireless connection 1136. The client device 102 connects to the server system 1132 and a network 1138. The network 1138 may include any combination of wired and wireless connections.

[0154] The head wearable device 200 also includes two image displays of the optical assembly's image display 1102. The two image displays of the optical assembly's image display 1102 include one image display associated with the left lateral side of the head wearable device 600 and one image display associated with the right lateral side of the head wearable device 600. The head wearable device 200 also includes an image display driver 1108, an image processor 1110, low power circuitry 1126 for low power consumption, and high speed circuitry 1118. The optical assembly's image display 1102 is used to present images and videos to a user of the head wearable device 200, including images that may include a graphical user interface.

[0155] The image display driver 1108 commands and controls the image display of the image display 1102 of the optical assembly. The image display driver 1108 can deliver the image data directly to the image display in the image display 1102 of the optical assembly for presentation, or can convert the image data into a signal or data format suitable for delivery to the image display device. For example, the image data can be video data formatted according to a compression format (e.g., H.264 (MPEG-4 Part 10), HEVC, Theora, Dirac, RealVideo RV40, VP8, VP9, ​​etc.), and the still image data can be formatted according to a compression format (e.g., Portable Network Graphics Group (PNG), Joint Photographic Experts Group (JPEG), Tagged Image File Format (TIFF) or Exchangeable Image File Format (Exif), etc.).

[0156] As described above, the head wearable device 200 includes a frame 610 and a handle (or temple) extending from a lateral side of the frame 610. The head wearable device 200 also includes a user input device 1106 (e.g., a touch sensor or a push button) that includes an input surface on the head wearable device 600. The user input device 1106 (e.g., a touch sensor or a push button) is used to receive input selections from a user to manipulate a graphical user interface of a presented image.

[0157] Fig.11The components for the head wearable device 200 shown in are located on one or more circuit boards (e.g., PCBs or flexible PCBs) in the frame or temples. Alternatively or additionally, the depicted components may be located in a block, frame, hinge, or beam of the head wearable device 600. The left visible light camera and the right visible light camera 1112 may include digital camera elements, such as complementary metal oxide semiconductor (CMOS) image sensors, charge coupled devices, camera lenses 606 and camera lenses 608, or any other corresponding visible light or light capturing elements that can be used to capture data including images of scenes with unknown objects.

[0158] The head wearable device 200 includes a memory 1122 that stores instructions for performing a subset or all of the functions described herein. The memory 1122 may also include a storage device.

[0159] like Fig.11 As shown, the high-speed circuit system 1118 includes a high-speed processor 1120, a memory 1122, and a high-speed wireless circuit system 1124. In an example, the image display driver 1108 is coupled to the high-speed circuit system 1118 and is operated by the high-speed processor 1120 to drive the left image display and the right image display of the image display 1102 of the optical assembly. The high-speed processor 1120 can be any processor capable of managing high-speed communications and operations of any general computing system required by the head wearable device 200. The high-speed processor 1120 includes the processing resources required to manage high-speed data transmission on the high-speed wireless connection 1136 to the wireless local area network (WLAN) using the high-speed wireless circuit system 1124. In some examples, the high-speed processor 1120 executes an operating system such as a LINUX operating system or other such operating system of the head wearable device 600, and the operating system is stored in the memory 1122 for execution. In addition to any other duties, the high-speed processor 1120 that executes the software architecture of the head wearable device 200 is used to manage data transmission with the high-speed wireless circuit system 1124. In some examples, high-speed wireless circuit system 1124 is configured to implement the Institute of Electrical and Electronics Engineers (IEEE) 902.11 communication standard, also referred to herein as Wi-Fi. In other examples, other high-speed communication standards can be implemented by high-speed wireless circuit system 1124.

[0160] The low-power wireless circuit system 1130 and the high-speed wireless circuit system 1124 of the head wearable device 200 may include a short-range transceiver (Bluetooth TM) and a wireless wide area network transceiver, a local area network transceiver, or a wide area network transceiver (e.g., cellular or WiFi). The client device 102 including a transceiver for communicating via a low power wireless connection 1134 and a high speed wireless connection 1136 can be implemented using details of the architecture of the head wearable device 600, as can other elements of the network 1138.

[0161] The memory 1122 includes any storage device capable of storing various data and applications, including camera data generated by the left and right visible light cameras 1112, the infrared camera 1116, and the image processor 1110, and images generated by the image display driver 1108 for display on the image display 1102 of the optical assembly, etc. Although the memory 1122 is shown as being integrated with the high-speed circuit system 1118, in other examples, the memory 1122 can be a separate independent element of the head wearable device 600. In some such examples, electrical wiring can provide a connection from the image processor 1110 or the low-power processor 1128 to the memory 1122 through a chip including the high-speed processor 1120. In other examples, the high-speed processor 1120 can manage the addressing of the memory 1122 so that the low-power processor 1128 will start the high-speed processor 1120 at any time when a read or write operation involving the memory 1122 is required.

[0162] like Fig.11 As shown, the low-power processor 1128 or the high-speed processor 1120 of the head wearable device 600 can be coupled to a camera device (a visible light camera device 1112; an infrared transmitter 1114, or an infrared camera device 1116), an image display driver 1108, a user input device 1106 (for example, a touch sensor or a push button), and a memory 1122.

[0163] The head wearable device 600 is connected to a host computer. For example, the head wearable device 200 is paired with the client device 102 via a high-speed wireless connection 1136, or is connected to a server system 1132 via a network 1138. The server system 1132 can be one or more computing devices as part of a service or network computing system, for example, the one or more computing devices include a processor, a memory, and a network communication interface that communicates with the client device 102 and the head wearable device 600 through the network 1138.

[0164] The client device 102 includes a processor and a network communication interface coupled to the processor. The network communication interface allows communication via a network 1138, a low-power wireless connection 1134, or a high-speed wireless connection 1136. The client device 102 may also store at least a portion of the instructions for generating two-channel audio content in a memory of the client device 102 to implement the functions described herein.

[0165] The output components of the head wearable device 200 include visual components, such as a display, such as a liquid crystal display (LCD), a plasma display panel (PDP), a light emitting diode (LED) display, a projector, or a waveguide. The image display of the optical assembly is driven by the image display driver 1108. The output components of the head wearable device 200 also include acoustic components (e.g., speakers), tactile components (e.g., vibration motors), other signal generators, etc. The input components of the head wearable device 200, the client device 102, and the server system 1132, such as the user input device 1106, may include alphanumeric input components (e.g., keyboards, touch screens configured to receive alphanumeric input, optical keyboards, or other alphanumeric input components), point-based input components (e.g., mice, touch pads, trackballs, joysticks, motion sensors, or other pointing tools), tactile input components (e.g., physical buttons, touch screens or other tactile input components that provide the location and force of touch or touch gestures), audio input components (e.g., microphones), etc.

[0166] The head wearable device 600 may optionally include additional peripheral elements. Such peripheral elements may include biometric sensors, additional sensors, or display elements integrated with the head wearable device 600. For example, the peripheral elements may include any I / O components including output components, motion components, positioning components, or any other such components described herein.

[0167] For example, the biometric recognition component includes components for the following operations: detecting expressions (e.g., hand expressions, facial expressions, voice expressions, body postures, or eye tracking), measuring biological signals (e.g., blood pressure, heart rate, body temperature, perspiration, or brain waves), identifying people (e.g., voice recognition, retinal recognition, facial recognition, fingerprint recognition, or electroencephalogram-based recognition), etc. The motion component includes an acceleration sensor component (e.g., an accelerometer), a gravity sensor component, a rotation sensor component (e.g., a gyroscope), etc. The positioning component includes a position sensor component for generating position coordinates (e.g., a global positioning system (GPS) receiver component), a Wi-Fi or Bluetooth receiver for generating positioning system coordinates, etc. TMtransceiver, altitude sensor component (e.g., an altimeter or barometer that detects air pressure, from which altitude can be obtained), orientation sensor component (e.g., a magnetometer), etc. Such positioning system coordinates can also be received from the client device 102 via the low-power wireless circuit system 1130 or the high-speed wireless circuit system 1124 through the low-power wireless connection 1134 and the high-speed wireless connection 1136.

[0168] When phrases similar to "at least one of A, B, or C," "at least one of A, B and C," "one or more A, B, or C," or "one or more of A, B, and C" are used, it is intended that the phrase be interpreted to mean that A can exist alone in an embodiment, B can exist alone in an embodiment, C can exist alone in an embodiment, or any combination of elements A, B, and C can exist in a single embodiment; for example, A and B, A and C, B and C, or A and B and C.

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

[0170] Glossary

[0171] "Carrier signal" refers to any intangible medium that can store, encode or carry instructions for execution by a machine and includes digital or analog communications signals or other intangible media that facilitates communication of such instructions. Instructions may be sent or received over a network using a transmission medium via a network interface device.

[0172] "Client Device" refers to any machine that interfaces with a communications network to obtain resources from one or more server systems or other client devices. A client device may be, but is not limited to, a mobile phone, a desktop computer, a laptop computer, a portable digital assistant (PDA), a smart phone, a tablet computer, an ultrabook, a netbook, a laptop computer, a multiprocessor system, a microprocessor-based or programmable consumer electronics product, a game console, a set-top box, or any other communications device that a user may use to access a network.

[0173] "Communications network" means one or more parts of a network, which may be an ad hoc network, an intranet, an extranet, a virtual private network (VPN), a local area network (LAN), a wireless LAN (WLAN), a wide area network (WAN), a wireless WAN (WWAN), a metropolitan area network (MAN), the Internet, a part of the Internet, a part of the public switched telephone network (PSTN), a plain old telephone service (POTS) network, a cellular telephone network, a wireless network, A network, other type of network, or a combination of two or more such networks. For example, the network or a portion of the network may include a wireless network or a cellular network, and the coupling may be a code division multiple access (CDMA) connection, a global system for mobile communications (GSM) connection, or other type of cellular or wireless coupling. In this example, the coupling may implement any of various types of data transmission technologies, such as single carrier radio transmission technology (1xRTT), evolution data optimized (EVDO) technology, general packet radio service (GPRS) technology, enhanced data rate for GSM evolution (EDGE) technology, the third generation partnership project (3GPP) including 3G, fourth generation wireless (4G) network, universal mobile telecommunications system (UMTS), high speed packet access (HSPA), world wide interoperability for microwave access (WiMAX), long term evolution (LTE) standards, other data transmission technologies defined by various standard setting organizations, other long distance protocols, or other data transmission technologies.

[0174] "Component" refers to a device, a physical entity, or logic with boundaries defined by function or subroutine calls, branch points, APIs, or other technologies that provide partitioning or modularization for specific processing or control functions. Components can be combined with other components via their interfaces to perform machine processing. Components can be packaged functional hardware units designed for use with other components and can be part of a program that generally performs specific functions in related functions. Components can constitute software components (e.g., codes implemented on machine-readable media) or hardware components. "Hardware components" are tangible units that can perform certain operations and can be configured or arranged in a certain physical manner. In various examples, one or more computer systems (e.g., independent 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., applications or application parts) to operate to perform certain operations described herein. Hardware components can also be implemented mechanically, electronically, or any suitable combination thereof. For example, a hardware component may include a dedicated circuit or logic that is permanently configured to perform certain operations. The hardware component may be a dedicated processor, such as a field programmable gate array (FPGA) or an application specific integrated circuit (ASIC). The hardware component may also include a programmable logic or circuit system that is temporarily configured to perform certain operations by software. For example, the 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 component of a machine) that is uniquely customized to perform the configured function, and is no longer a general-purpose processor. It should be understood that it can be decided whether to mechanically implement the hardware component in a dedicated and permanently configured circuit system or in a temporarily configured (e.g., configured by software) circuit system for cost and time considerations. Therefore, the phrase "hardware component" (or "hardware-implemented component") should be understood to include a tangible entity, that is, an entity that is physically constructed, permanently configured (e.g., hardwired) or temporarily configured (e.g., programmed) to operate in some way or perform certain operations described herein. Considering an example in which a hardware component is temporarily configured (e.g., programmed), it is not necessary to configure or instantiate each of the hardware components at any one time. For example, in the case where a hardware component includes a general-purpose processor that is configured by software to become a special-purpose processor, the general-purpose processor can be respectively configured as different special-purpose processors (e.g., including different hardware components) at different times. Software accordingly configures one or more specific processors to, for example, constitute a specific hardware component at one time, and to constitute different hardware components at different times. Hardware components can provide information to other hardware components and receive information from other hardware components. Accordingly, the described hardware components can be considered to be coupled in communication.In the case of multiple hardware components being present at the same time, communication can be achieved by signal transmission (e.g., by appropriate circuits and buses) between or among two or more hardware components. In examples where multiple hardware components are configured or instantiated at different times, communication between such hardware components can be achieved, for example, by storing information in a memory structure accessible to multiple hardware components and retrieving information in the memory structure. For example, a hardware component can perform an operation, and the output of the operation is stored in a memory device coupled to it in communication. Then, another hardware component can access the memory device at a subsequent time to retrieve the stored output and process it. The hardware component can also initiate communication with an input device or an output device, and can operate on resources (e.g., a collection of information). The various operations of the example methods described herein can be performed at least in part by one or more processors that are temporarily configured (e.g., by software) or permanently configured to perform related operations. Whether it is temporarily configured or permanently configured, such a processor can constitute a processor-implemented component that operates to perform one or more operations or functions described herein. As used herein, "processor-implemented components" refer to hardware components implemented using one or more processors. Similarly, the method described in this article can be implemented at least in part by a processor, wherein one or more specific processors are examples of hardware. For example, at least some of the operation of the method can be performed by one or more processors or the components implemented by the processor. In addition, one or more processors can also operate to support the execution of related operations in a "cloud computing" environment or as a "software as a service" (SaaS) operation. For example, at least some of the operations in the operation can be performed by a group of computers (as an example of a machine including a processor), wherein these operations can be accessed via a network (e.g., the Internet) and via one or more appropriate interfaces (e.g., API). The execution of some operations in the operation can be distributed between processors, can not only reside in a single machine, but also can be deployed across several machines. In some examples, a processor or a component implemented by a processor can be located in a single geographical location (e.g., in a home environment, an office environment, or a server cluster). In other examples, a processor or a component implemented by a processor can be distributed across several geographical locations.

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

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

[0177] "Machine storage media" refers to a single or multiple storage devices and media (e.g., centralized or distributed databases, and associated caches and servers) that store executable instructions, routines, and data. Thus, the term should be considered to include, but is not limited to, solid-state memory and optical and magnetic media, including memory internal or external to the processor. Specific examples of machine storage media, computer storage media, and device storage media include: non-volatile memory, including, for example, semiconductor memory devices such as erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), FPGA, and flash memory devices; magnetic disks, such as internal hard disks and removable disks; magneto-optical disks; and CD-ROM and DVD-ROM disks. The terms "machine storage media", "device storage media", and "computer storage media" mean the same thing and may be used interchangeably in this disclosure. The terms "machine storage media", "computer storage media", and "device storage media" expressly exclude carrier waves, modulated data signals, and other such media (at least some of which are encompassed by the term "signal media").

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

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

Claims

1. A method comprising: receiving, by a processor, a selection from a computer device, the selection comprising launching an augmented reality (AR) experience on an application running on the computer device; In response to receiving the selection, causing a first set of text prompts to be displayed on a graphical user interface (GUI) of the computer device, the first set of text prompts being associated with the AR experience; receiving a first set of image data corresponding to the first set of textual prompts from one or more image sensors of the computer device; In response to receiving the first set of image data, generating a first AR object associated with the AR experience; causing display of the first AR object and a second set of textual prompts associated with the AR experience on a GUI of the computer device; receiving a second set of image data corresponding to the second set of textual prompts from one or more image sensors of the computer device; as well as In response to receiving the second set of image data, a second AR object associated with the AR experience is generated.

2. The method according to claim 1, wherein: Receiving the selection further comprises: causing a set of selectable user interface elements to be displayed on the GUI; and A selection of a selectable user interface element from the set of selectable user interface elements is received.

3. The method according to claim 1, further comprising: receiving, from a microphone of the computer device, a first set of audio data corresponding to the first set of text prompts; as well as The first AR object is generated based on the first set of image data and the first set of audio data.

4. The method according to claim 3, wherein: Receiving the first set of audio data further includes: The first set of audio data is analyzed using a speech machine learning model, wherein the speech machine learning model is trained to detect keywords from the first set of audio data.

5. The method according to claim 1, further comprising: causing display of a third set of text prompts associated with the AR experience; receiving a third set of image data corresponding to the third set of text prompts; identifying a location of the computer device based on the third set of image data; as well as An AR effect is generated based on the identified location.

6. The method according to claim 1, wherein: The second AR object is associated with the first AR object.

7. The method according to claim 1, wherein: Receiving the first set of image data further includes: The first set of image data is analyzed using an image machine learning model, the image machine learning model being trained to recognize objects within the first set of image data.

8. The method according to claim 1, further comprising: receiving tactile input from a user of the computer device; as well as In response to receiving the tactile input from the user, causing display of a fourth set of textual prompts associated with the AR experience.

9. A computing system comprising: processor, and a memory storing instructions that, when executed by the processor, configure the system to: receiving a selection from a computer device, the selection comprising launching an augmented reality (AR) experience on an application running on the computer device; In response to receiving the selection, causing a first set of text prompts to be displayed on a graphical user interface (GUI) of the computer device, the first set of text prompts being associated with the AR experience; receiving a first set of image data corresponding to the first set of textual prompts from one or more image sensors of the computer device; In response to receiving the first set of image data, generating a first AR object associated with the AR experience; causing display of the first AR object and a second set of textual prompts associated with the AR experience on a GUI of the computer device; receiving a second set of image data corresponding to the second set of textual prompts from one or more image sensors of the computer device; as well as In response to receiving the second set of image data, a second AR object associated with the AR experience is generated.

10. The computing system of claim 9, wherein: Receiving the selection further comprises: causing a set of selectable user interface elements to be displayed on the GUI; and A selection of a selectable user interface element from the set of selectable user interface elements is received.

11. The computing system of claim 9, wherein: The instructions further configure the system to: receiving, from a microphone of the computer device, a first set of audio data corresponding to the first set of text prompts; as well as The first AR object is generated based on the first set of image data and the first set of audio data.

12. The computing system of claim 11, wherein: Receiving the first set of audio data further includes: The first set of audio data is analyzed using a speech machine learning model, wherein the speech machine learning model is trained to detect keywords from the first set of audio data.

13. The computing system of claim 9, wherein: The instructions further configure the system to: causing display of a third set of text prompts associated with the AR experience; receiving a third set of image data corresponding to the third set of text prompts; identifying a location of the computer device based on the third set of image data; as well as An AR effect is generated based on the identified location.

14. The computing system of claim 9, wherein: The second AR object is associated with the first AR object.

15. The computing system of claim 9, wherein: Receiving the first image data further includes: The first set of image data is analyzed using an image machine learning model, the image machine learning model being trained to recognize objects within the first set of image data.

16. The computing system of claim 9, wherein: The instructions further configure the system to: receiving tactile input from a user of the computer device; and In response to receiving the tactile input from the user, causing display of a fourth set of textual prompts associated with the AR experience.

17. A non-transitory computer-readable storage medium comprising instructions that, when executed by a computer, cause the computer to: receiving a selection from a computer device, the selection comprising launching an augmented reality (AR) experience on an application running on the computer device; In response to receiving the selection, causing a first set of text prompts to be displayed on a graphical user interface (GUI) of the computer device, the first set of text prompts being associated with the AR experience; receiving a first set of image data corresponding to the first set of textual prompts from one or more image sensors of the computer device; In response to receiving the first set of image data, generating a first AR object associated with the AR experience; causing display of the first AR object and a second set of textual prompts associated with the AR experience on a GUI of the computer device; receiving a second set of image data corresponding to the second set of textual prompts from one or more image sensors of the computer device; as well as In response to receiving the second set of image data, a second AR object associated with the AR experience is generated.

18. The computer-readable storage medium of claim 17, wherein: Receiving the selection further comprises: causing a set of selectable user interface elements to be displayed on the GUI; and A selection of a selectable user interface element from the set of selectable user interface elements is received.

19. The computer-readable storage medium of claim 17, wherein: The instructions further configure the computer to: receiving, from a microphone of the computer device, a first set of audio data corresponding to the first set of text prompts; as well as The first AR object is generated based on the first set of image data and the first set of audio data.

20. The computer-readable storage medium of claim 19, wherein: Receiving the first set of audio data further includes: The first set of audio data is analyzed using a speech machine learning model, wherein the speech machine learning model is trained to detect keywords from the first set of audio data.

Images