Patent Description:
The present disclosure relates generally to messaging applications, including providing display of augmented reality content within a messaging application.

Messaging systems provide for the exchange of message content between users. For example, a messaging system allows a user to exchange message content (e.g., text, images) with one or more other users.

<CIT> describes a system, methods, platform, database, search engine & device that enable a user to auto open or unlock a user device, auto open a camera display screen, auto capture photos or auto start recording of video, auto open media viewer when user wants to view, apply ephemeral or non-ephemeral and real-time content access rules and settings for one or more destinations and/or sources.

A messaging system typically allow users to exchange content items (e.g., messages, images and/or video) with one another in a message thread. A messaging system may implement or otherwise work in conjunction with an augmented reality system to display augmented reality content with respect to messaging. For example, the augmented reality content is combined with image data captured by a device camera in creating message content. However, a user may wish for facilitated creation and/or selection of augmented reality content with respect to messaging.

The disclosed embodiments provide for a messaging application running on a device to select between augmented reality content items (e.g., corresponding to applying augmented reality experiences or Lenses) based on received speech input. The speech input corresponds to a voice command to perform an action on an object depicted in a captured image. The messaging application determines keywords from the speech input, for example, by requesting the keywords from a speech recognition service.

The messaging application determines that the keywords indicate an object depicted in the image, and further indicate an action to perform on the object. The messaging application sends attributes of the object and attributes of the action to a server, which is configured to select an augmented reality content item (e.g., corresponding to an augmented reality experience) based on the attributes. The messaging application displays augmented reality content, corresponding to the selected augmented reality content item, together with the captured image data.

<FIG> is a block diagram showing an example messaging system <NUM> for exchanging data (e.g., messages and associated content) over a network <NUM>. The messaging system <NUM> includes instances of a client device <NUM>, each of which hosts a number of applications, including a messaging client application <NUM> and a speech recognition client application <NUM>. Each messaging client application <NUM> is communicatively coupled to other instances of the messaging client application <NUM> and a messaging server system <NUM> via a network <NUM> (e.g., the Internet).

A messaging client application <NUM> is able to communicate and exchange data with another messaging client application <NUM> and with the messaging server system <NUM> via the network <NUM>. The data exchanged between the messaging client application <NUM>, and between the other messaging client application <NUM> and the messaging server system <NUM>, includes functions (e.g., commands to invoke functions) as well as payload data (e.g., text, audio, video or other multimedia data).

Disclosed communications between the messaging client application <NUM> and the speech recognition client application <NUM> can be transmitted directly. Alternatively, or in addition, disclosed communications between the messaging client application <NUM> and the speech recognition client application <NUM> can be transmitted indirectly (e.g., via one or more servers).

In one or more embodiments, the speech recognition client application <NUM> is an application that is separate and distinct from the messaging client application <NUM>. For example, the speech recognition client application <NUM> is downloaded and installed by the client device <NUM> separately (e.g., before or after) from the messaging client application <NUM>. Moreover, the speech recognition client application <NUM> is an application that is provided by an entity or organization that is different from the entity or organization that provides the messaging client application <NUM>. In one or more embodiments, the speech recognition client application <NUM> is an application that can be accessed by a client device <NUM> using separate login credentials than the messaging client application <NUM>. For example, the speech recognition client application <NUM> can maintain a first user account and the messaging client application <NUM> can maintain a second user account.

In one or more alternative embodiments, the speech recognition client application <NUM> is a component that is included as part of the messaging client application <NUM>. For example, the speech recognition client application <NUM> includes one or more hardware and/or software component(s) that are integrated within the messaging client application <NUM>. In this manner, the messaging client application <NUM> in conjunction with the speech recognition server system <NUM> and/or the messaging server system <NUM> is configured to perform the functions of speech recognition client application <NUM>.

In one or more embodiments, the speech recognition client application <NUM> is configured to perform speech recognition of sound input (e.g., corresponding to a user's voice) received at the client device <NUM>. For example, the sound input is received by the messaging client application <NUM>, and corresponds to a voice command to perform a particular function (e.g., to display augmented reality content).

In one or more embodiments, the speech recognition client application <NUM> corresponds to a client-side component which communicates (e.g., via the network <NUM>) with a speech recognition server system <NUM>, corresponding to a server-side component for performing speech recognition. For example, the speech recognition client application <NUM> is configured to receive sound input provided by the messaging client application <NUM>, to determine that the sound input includes a trigger word for activating speech recognition, and to request the speech recognition server system <NUM> to perform speech recognition with respect to additional sound input (e.g., a voice command corresponding to a remaining part of the sound input after the trigger word, or to subsequent sound input received by the messaging client application <NUM>).

In some embodiments, the messaging client application <NUM> activates a camera of the client device <NUM> (e.g., upon startup of the messaging client application <NUM>). The messaging client application <NUM> allows a user to request to scan one or more items in a camera feed captured by the camera. For example, the messaging client application <NUM> may receive a user selection of a dedicated scan option (e.g., a button) presented together with the camera feed. In an alternative embodiment, the messaging client application <NUM> may detect physical contact between a finger of the user's hand and a region of the touch screen for a threshold period of time. For example, the messaging client application <NUM> determines that the user touched and held their finger on the screen for more than three seconds. In response, the messaging client application <NUM> captures an image being displayed on the screen and processes the image to identify one or more objects in the image. Alternatively, or in addition, a scanning operation for detecting objects is performed in response to speech input (e.g., a voice command) to perform an action with respect to an object, as described herein. In some embodiments, the messaging client application <NUM> uses one or more trained classifiers and/or environmental factors to identify the objects in the image.

The messaging server system <NUM> provides server-side functionality via the network <NUM> to a particular messaging client application <NUM>. While certain functions of the messaging system <NUM> are described herein as being performed by either the messaging client application <NUM> or by the messaging server system <NUM>, it will be appreciated that the location of certain functionality either within the messaging client application <NUM> or the messaging server system <NUM> is a design choice. For example, it may be technically preferable to initially deploy certain technology and functionality within the messaging server system <NUM>, but to later migrate this technology and functionality to the messaging client application <NUM> where a client device <NUM> has a sufficient processing capacity.

The messaging server system <NUM> supports various services and operations that are provided to the messaging client application <NUM>. Such operations include transmitting data to, receiving data from, and processing data generated by the messaging client application <NUM>. This data may include message content, client device information, graphical elements, geolocation information, media annotation and overlays, virtual objects, message content persistence conditions, social network information, and live event information, as examples. Data exchanges within the messaging system <NUM> are invoked and controlled through functions available via user interfaces (UIs) (e.g., graphical user interfaces) of the messaging client application <NUM>.

Turning now specifically to the messaging server system <NUM>, an API server <NUM> (application programming interface server) is coupled to, and provides a programmatic interface to, an application server <NUM>. The application server <NUM> is communicatively coupled to a database server <NUM>, which facilitates access to a database <NUM> in which is stored data associated with messages processed by the application server <NUM>.

Dealing specifically with the API server <NUM>, this server receives and transmits message data (e.g., commands and message payloads) between the client device <NUM> and the application server <NUM>. Specifically, the API server <NUM> provides a set of interfaces (e.g., routines and protocols) that can be called or queried by the messaging client application <NUM> in order to invoke functionality of the application server <NUM>. The API server <NUM> exposes various functions supported by the application server <NUM>, including account registration; login functionality; the sending of messages, via the application server <NUM>, from a particular messaging client application <NUM> to another messaging client application <NUM>; the sending of media files (e.g., graphical elements, images or video) from the messaging client application <NUM> to the messaging server application <NUM>, and for possible access by another messaging client application <NUM>; a graphical element list; the setting of a collection of media data (e.g., a Story); the retrieval of such collections; the retrieval of a list of friends of a user of a client device <NUM>; maintaining augmented reality content items; the retrieval of messages and content; the adding and deleting of friends to a social graph; the location of friends within a social graph; access to user conversation data; access to avatar information stored on messaging server system <NUM>; and opening an application event (e.g., relating to the messaging client application <NUM>).

The application server <NUM> hosts a number of applications and subsystems, including a messaging server application <NUM>, an image processing system <NUM>, a social network system <NUM>, and augmented reality system <NUM>. The messaging server application <NUM> implements a number of message processing technologies and functions, particularly related to the aggregation and other processing of content (e.g., textual and multimedia content) included in messages received from multiple instances of the messaging client application <NUM>. As will be described in further detail, the text and media content from multiple sources may be aggregated into collections of content (e.g., called Stories or galleries). These collections are then made available, by the messaging server application <NUM>, to the <NUM>. Other processor- and memory-intensive processing of data may also be performed server-side by the messaging server application <NUM>, in view of the hardware requirements for such processing.

The application server <NUM> also includes an image processing system <NUM> that is dedicated to performing various image processing operations, typically with respect to images or video received within the payload of a message at the messaging server application <NUM>. In one or more implementations, a portion of the image processing system <NUM> may also be implemented by the augmented reality system <NUM>.

The social network system <NUM> supports various social networking functions and services and makes these functions and services available to the messaging server application <NUM>. To this end, the social network system <NUM> maintains and accesses an entity graph within the database <NUM>. Examples of functions and services supported by the social network system <NUM> include the identification of other users of the messaging system <NUM> with which a particular user has relationships or is "following" and also the identification of other entities and interests of a particular user. Such other users may be referred to as the user's friends. The social network system <NUM> may access location information associated with each of the user's friends to determine where they live or are currently located geographically. The social network system <NUM> may maintain a location profile for each of the user's friends indicating the geographical location where the user's friends live.

The messaging client application <NUM> includes a set of functions that allows the client device <NUM> to access the augmented reality system <NUM>. The augmented reality system <NUM> generates and maintains a list of augmented reality content items. The augmented reality content items may correspond to an augmented reality experience for supplementing captured image data with augmented reality content.

In one or more embodiments, the augmented reality system <NUM> provides for determining (e.g., receives) one or more attributes (e.g., a name) of an object and/or one or more attributes of an action (e.g., provide identifying information, provide a visual effect, provide a solution) to perform on the object. The augmented reality system <NUM> provides for searching for one or more augmented reality content items (e.g., virtual objects) that are associated with the one or more attributes of the object and/or action, and for ranking the virtual objects (e.g., based on the associations and weights assigned to each of the attributes). The augmented reality system <NUM> causes one or more virtual objects or graphical elements of the highest ranked augmented reality content item to be presented on top of the captured image.

The application server <NUM> is communicatively coupled to a database server <NUM>, which facilitates access to a database <NUM>, in which is stored data associated with messages processed by the messaging server application <NUM>. The database <NUM> may be a third-party database. For example, the application server <NUM> may be associated with a first entity, and the database <NUM> or a portion of the database <NUM> may be associated and hosted by a second different entity. In some embodiments, the database <NUM> stores user data that the first entity collects about various each of the users of a service provided by the first entity. For example, the user data includes user names, phone numbers, passwords, addresses, friends, activity information, preferences, videos or content consumed by the user, and so forth.

<FIG> is block diagram illustrating further details regarding the messaging system <NUM>, according to example embodiments. Specifically, the messaging system <NUM> is shown to comprise the messaging client application <NUM> and the application server <NUM>, which in turn embody a number of some subsystems, namely an ephemeral timer system <NUM>, a collection management system <NUM> and an annotation system <NUM>.

The ephemeral timer system <NUM> is responsible for enforcing the temporary access to content permitted by the messaging client application <NUM> and the messaging server application <NUM>. To this end, the ephemeral timer system <NUM> incorporates a number of timers that, based on duration and display parameters associated with a message, or collection of messages (e.g., a Story), selectively display and enable access to messages and associated content via the messaging client application <NUM>. Further details regarding the operation of the ephemeral timer system <NUM> are provided below.

The collection management system <NUM> is responsible for managing collections of media (e.g., collections of text, image video and audio data). In some examples, a collection of content (e.g., messages, including images, video, text and audio) may be organized into an "event gallery" or an "event Story. " Such a collection may be made available for a specified time period, such as the duration of an event to which the content relates. For example, content relating to a music concert may be made available as a "Story" for the duration of that music concert. The collection management system <NUM> may also be responsible for publishing an icon that provides notification of the existence of a particular collection to the user interface of the messaging client application <NUM>.

In certain embodiments, compensation may be paid to a user for inclusion of user-generated content into a collection. In such cases, the curation interface <NUM> operates to automatically make payments to such users for the use of their content.

The annotation system <NUM> provides various functions that enable a user to annotate or otherwise modify or edit media content associated with a message. For example, the annotation system <NUM> provides functions related to the generation and publishing of media overlays for messages processed by the messaging system <NUM>. The annotation system <NUM> operatively supplies a media overlay or supplementation (e.g., an image filter) to the messaging client application <NUM> based on a geolocation of the client device <NUM>. In another example, the annotation system <NUM> operatively supplies a media overlay to the messaging client application <NUM> based on other information, such as social network information of the user of the client device <NUM>. A media overlay may include audio and visual content and visual effects. Examples of audio and visual content include pictures, texts, logos, animations, and sound effects. An example of a visual effect includes color overlaying. The audio and visual content or the visual effects can be applied to a content item (e.g., a photo) at the client device <NUM>. For example, the media overlay may include text that can be overlaid on top of a photograph taken by the client device <NUM>. In another example, the media overlay includes an identification of a location overlay (e.g., Venice beach), a name of a live event, or a name of a merchant overlay (e.g., Beach Coffee House). In another example, the annotation system <NUM> uses the geolocation of the client device <NUM> to identify a media overlay that includes the name of a merchant at the geolocation of the client device <NUM>. The media overlay may include other indicia associated with the merchant. The media overlays may be stored in the database <NUM> and accessed through the database server <NUM>.

In one example embodiment, the annotation system <NUM> provides a user-based publication platform that enables users to select a geolocation on a map, and upload content associated with the selected geolocation. The user may also specify circumstances under which a particular media overlay should be offered to other users. The annotation system <NUM> generates a media overlay that includes the uploaded content and associates the uploaded content with the selected geolocation.

In another example embodiment, the annotation system <NUM> provides a merchant-based publication platform that enables merchants to select a particular media overlay associated with a geolocation via a bidding process. For example, the annotation system <NUM> associates the media overlay of a highest bidding merchant with a corresponding geolocation for a predefined amount of time.

<FIG> is a schematic diagram illustrating data structures <NUM> which may be stored in the database <NUM> of the messaging server system <NUM>, according to certain example embodiments. While the content of the database <NUM> is shown to comprise a number of tables, it will be appreciated that the data could be stored in other types of data structures (e.g., as an object-oriented database).

The database <NUM> includes message data stored within a message table <NUM>. An entity table <NUM> stores entity data, including an entity graph <NUM>. Entities for which records are maintained within the entity table <NUM> may include individuals, corporate entities, organizations, objects, places, events, and so forth. Regardless of type, any entity regarding which the messaging server system <NUM> stores data may be a recognized entity. Each entity is provided with a unique identifier, as well as an entity type identifier (not shown).

The entity graph <NUM> stores information regarding relationships and associations between entities. Such relationships may be social, professional (e.g., work at a common corporation or organization), interest-based, or activity-based, merely for example.

The message table <NUM> may store a collection of conversations between a user and one or more friends or entities. The message table <NUM> may include various attributes of each conversation, such as the list of participants, the size of the conversation (e.g., number of users and/or number of messages), the chat color of the conversation, a unique identifier for the conversation, and any other conversation related feature(s).

The database <NUM> also stores annotation data, in the example form of filters, in an annotation table <NUM>. The database <NUM> also stores annotated content received in the annotation table <NUM>. Filters for which data is stored within the annotation table <NUM> are associated with and applied to videos (for which data is stored in a video table <NUM>) and/or images (for which data is stored in an image table <NUM>). Filters, in one example, are overlays that are displayed as overlaid on an image or video during presentation to a recipient user. Filters may be of various types, including user-selected filters from a gallery of filters presented to a sending user by the messaging client application <NUM> when the sending user is composing a message. Other types of filters include geolocation filters (also known as geo-filters), which may be presented to a sending user based on geographic location. For example, geolocation filters specific to a neighborhood or special location may be presented within a UI by the messaging client application <NUM>, based on geolocation information determined by a Global Positioning System (GPS) unit of the client device <NUM>. Another type of filter is a data filter, which may be selectively presented to a sending user by the messaging client application <NUM>, based on other inputs or information gathered by the client device <NUM> during the message creation process. Examples of data filters include current temperature at a specific location, a current speed at which a sending user is traveling, battery life for a client device <NUM>, or the current time.

Other annotation data that may be stored within the image table <NUM> are augmented reality content items (e.g., corresponding to augmented reality experiences or Lenses). An augmented reality content item may be a real-time special effect and sound that may be added to an image or a video.

As described above, augmented reality content items, overlays, image transformations, AR images and similar terms refer to modifications that may be made to videos or images. This includes real-time modification which modifies an image as it is captured using a device sensor and then displayed on a screen of the device with the modifications. This also includes modifications to stored content, such as video clips in a gallery that may be modified. For example, in a device with access to multiple augmented reality content items, a user can use a single video clip with multiple augmented reality content items to see how the different augmented reality content items will modify the stored clip. For example, multiple augmented reality content items that apply different pseudorandom movement models can be applied to the same content by selecting different augmented reality content items for the content. Similarly, real-time video capture may be used with an illustrated modification to show how video images currently being captured by sensors of a device would modify the captured data. Such data may simply be displayed on the screen and not stored in memory, or the content captured by the device sensors may be recorded and stored in memory with or without the modifications (or both). In some systems, a preview feature can show how different augmented reality content items will look within different windows in a display at the same time. This can, for example, enable multiple windows with different pseudorandom animations to be viewed on a display at the same time.

Data and various systems using augmented reality content items or other such transform systems to modify content using this data can thus involve detection of objects (e.g., faces, hands, bodies, cats, dogs, surfaces, objects, etc.), tracking of such objects as they leave, enter, and move around the field of view in video frames, and the modification or transformation of such objects as they are tracked. In various embodiments, different methods for achieving such transformations may be used. For example, some embodiments may involve generating a three-dimensional mesh model of the object or objects, and using transformations and animated textures of the model within the video to achieve the transformation. In other embodiments, tracking of points on an object may be used to place an image or texture (which may be two dimensional or three dimensional) at the tracked position. In still further embodiments, neural network analysis of video frames may be used to place images, models, or textures in content (e.g., images or frames of video). Augmented reality content items thus refer both to the images, models, and textures used to create transformations in content, as well as to additional modeling and analysis information needed to achieve such transformations with object detection, tracking, and placement.

Real-time video processing can be performed with any kind of video data (e.g., video streams, video files, etc.) saved in a memory of a computerized system of any kind. For example, a user can load video files and save them in a memory of a device, or can generate a video stream using sensors of the device. Additionally, any objects can be processed using a computer animation model, such as a human's face and parts of a human body, animals, or non-living things such as chairs, cars, or other objects.

In some embodiments, when a particular modification is selected along with content to be transformed, elements to be transformed are identified by the computing device, and then detected and tracked if they are present in the frames of the video. The elements of the object are modified according to the request for modification, thus transforming the frames of the video stream. Transformation of frames of a video stream can be performed by different methods for different kinds of transformation. For example, for transformations of frames mostly referring to changing forms of object's elements characteristic points for each of element of an object are calculated (e.g., using an Active Shape Model (ASM) or other known methods). Then, a mesh based on the characteristic points is generated for each of the at least one element of the object. This mesh used in the following stage of tracking the elements of the object in the video stream. In the process of tracking, the mentioned mesh for each element is aligned with a position of each element. Then, additional points are generated on the mesh. A first set of first points is generated for each element based on a request for modification, and a set of second points is generated for each element based on the set of first points and the request for modification. Then, the frames of the video stream can be transformed by modifying the elements of the object on the basis of the sets of first and second points and the mesh. In such method, a background of the modified object can be changed or distorted as well by tracking and modifying the background.

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

In some embodiments of a computer animation model to transform image data using face detection, the face is detected on an image with use of a specific face detection (e.g., Viola-Jones). Then, an Active Shape Model (ASM) algorithm is applied to the face region of an image to detect facial feature reference points.

In other embodiments, other methods and algorithms suitable for face and/or object detection can be used. For example, in some embodiments, features are located using a landmark which represents a distinguishable point present in most of the images under consideration. For facial landmarks, for example, the location of the left eye pupil may be used. In an initial landmark is not identifiable (e.g., if a person has an eyepatch), secondary landmarks may be used. Such landmark identification procedures may be used for any such objects. In some embodiments, a set of landmarks forms a shape. Shapes can be represented as vectors using the coordinates of the points in the shape. One shape is aligned to another with a similarity transform (allowing translation, scaling, and rotation) that minimizes the average Euclidean distance between shape points. The mean shape is the mean of the aligned training shapes.

In some embodiments, a search for landmarks from the mean shape aligned to the position and size of the face determined by a global face detector is started. Such a search then repeats the steps of suggesting a tentative shape by adjusting the locations of shape points by template matching of the image texture around each point and then conforming the tentative shape to a global shape model until convergence occurs. In some systems, individual template matches are unreliable and the shape model pools the results of the weak template matchers to form a stronger overall classifier. The entire search is repeated at each level in an image pyramid, from coarse to fine resolution.

Embodiments of a transformation system can capture an image or video stream on a client device (e.g., the client device <NUM>) and perform complex image manipulations locally on the client device <NUM> while maintaining a suitable user experience, computation time, and power consumption. The complex image manipulations may include size and shape changes, emotion transfers (e.g., changing a face from a frown to a smile), state transfers (e.g., aging a subject, reducing apparent age, changing gender), style transfers, graphical element application, and any other suitable image or video manipulation implemented by a convolutional neural network that has been configured to execute efficiently on the client device <NUM>.

In some example embodiments, a computer animation model to transform image data can be used by a system where a user may capture an image or video stream of the user (e.g., a selfie) using a client device <NUM> having a neural network operating as part of a messaging client application <NUM> operating on the client device <NUM>. The transform system operating within the messaging client application <NUM> determines the presence of an object (e.g., a face) within the image or video stream and provides modification icons associated with a computer animation model to transform image data, or the computer animation model can be present as associated with an interface described herein. The modification icons include changes which may be the basis for modifying the user's face within the image or video stream as part of the modification operation. Once a modification icon is selected, the transform system initiates a process to convert the image of the user to reflect the selected modification icon (e.g., generate a smiling face on the user). In some embodiments, a modified image or video stream may be presented in a graphical user interface displayed on the mobile client device as soon as the image or video stream is captured and a specified modification is selected. The transform system may implement a complex convolutional neural network on a portion of the image or video stream to generate and apply the selected modification. That is, the user may capture the image or video stream and be presented with a modified result in real time or near real time once a modification icon has been selected. Further, the modification may be persistent while the video stream is being captured and the selected modification icon remains toggled. Machine taught neural networks may be used to enable such modifications.

In some embodiments, the graphical user interface, presenting the modification performed by the transform system, may supply the user with additional interaction options. Such options may be based on the interface used to initiate the content capture and selection of a particular computer animation model (e.g., initiation from a content creator user interface). In various embodiments, a modification may be persistent after an initial selection of a modification icon. The user may toggle 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 browse to other areas of the imaging application. Where multiple faces are modified by the transformation system, the user may toggle the modification on or off globally by tapping or selecting a single face modified and displayed within a graphical user interface. In some embodiments, individual faces, among a group of multiple faces, may be individually modified or such modifications may be individually toggled by tapping or selecting the individual face or a series of individual faces displayed within the graphical user interface.

As mentioned above, the video table <NUM> stores video data which, in one embodiment, is associated with messages for which records are maintained within the message table <NUM>. Similarly, the image table <NUM> stores image data associated with messages for which message data is stored in the entity table <NUM>. The entity table <NUM> may associate various annotations from the annotation table <NUM> with various images and videos stored in the image table <NUM> and the video table <NUM>.

The augmented reality content items table <NUM> stores an indication (e.g., a list) of augmented reality content items available for selection and activation by the messaging client application <NUM>. In one or more embodiments, each augmented reality content item in the augmented reality content items table <NUM> is associated with one or more object attributes. Each augmented reality content item in the augmented reality content items table <NUM> may also be associated with one or more predefined words (e.g., using metadata labels, designations, and the like). In one or more embodiments, the messaging client application <NUM> searches the object attributes and/or predefined words stored in the augmented reality content items table <NUM> to identify one or more augmented reality content items associated with a scanned object or an object identified in a captured image. Each augmented reality content item stored in the augmented reality content items table <NUM> includes one or more graphical elements or virtual objects which may or may not be animated. Each augmented reality content item also includes instructions on where to position the graphical elements or virtual objects relative to other objects depicted in the captured image.

A story table <NUM> stores data regarding collections of messages and associated image, video, or audio data, which are compiled into a collection (e.g., a Story or a gallery). The creation of a particular collection may be initiated by a particular user (e.g., each user for which a record is maintained in the entity table <NUM>). A user may create a "personal Story" in the form of a collection of content that has been created and sent/broadcast by that user. To this end, the UI of the messaging client application <NUM> may include an icon that is user-selectable to enable a sending user to add specific content to his or her personal Story.

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

A further type of content collection is known as a "location Story," which enables a user whose client device <NUM> is located within a specific geographic location (e.g., on a college or university campus) to contribute to a particular collection. In some embodiments, a contribution to a location Story may require a second degree of authentication to verify that the end user belongs to a specific organization or other entity (e.g., is a student on the university campus).

<FIG> is a schematic diagram illustrating a structure of a message <NUM>, according to some embodiments, generated by a messaging client application <NUM> for communication to a further messaging client application <NUM> or the messaging server application <NUM>. The content of a particular message <NUM> is used to populate the message table <NUM> stored within the database <NUM>, accessible by the messaging server application <NUM>. Similarly, the content of a message <NUM> is stored in memory as "in-transit" or "in-flight" data of the client device <NUM> or the application server <NUM>. The message <NUM> is shown to include the following components:.

The contents (e.g., values) of the various components of message <NUM> may be pointers to locations in tables within which content data values are stored. For example, an image value in the message image payload <NUM> may be a pointer to (or address of) a location within an image table <NUM>. Similarly, values within the message video payload <NUM> may point to data stored within a video table <NUM>, values stored within the message annotations <NUM> may point to data stored in an annotation table <NUM>, values stored within the message story identifier <NUM> may point to data stored in a story table <NUM>, and values stored within the message sender identifier <NUM> and the message receiver identifier <NUM> may point to user records stored within an entity table <NUM>.

<FIG> is a schematic diagram illustrating an access-limiting process <NUM>, in terms of which access to content (e.g., an ephemeral message <NUM>, and associated multimedia payload of data) or a content collection (e.g., an ephemeral message group <NUM>) may be time-limited (e.g., made ephemeral).

An ephemeral message <NUM> is shown to be associated with a message duration parameter <NUM>, the value of which determines an amount of time that the ephemeral message <NUM> will be displayed to a receiving user of the ephemeral message <NUM> by the messaging client application <NUM>. In one embodiment, an ephemeral message <NUM> is viewable by a receiving user for up to a maximum of <NUM> seconds, depending on the amount of time that the sending user specifies using the message duration parameter <NUM>.

The message duration parameter <NUM> and the message receiver identifier <NUM> are shown to be inputs to a message timer <NUM>, which is responsible for determining the amount of time that the ephemeral message <NUM> is shown to a particular receiving user identified by the message receiver identifier <NUM>. In particular, the ephemeral message <NUM> will only be shown to the relevant receiving user for a time period determined by the value of the message duration parameter <NUM>. The message timer <NUM> is shown to provide output to a more generalized ephemeral timer system <NUM>, which is responsible for the overall timing of display of content (e.g., an ephemeral message <NUM>) to a receiving user.

The ephemeral message <NUM> is shown in <FIG> to be included within an ephemeral message group <NUM> (e.g., a collection of messages in a personal Story, or an event Story). The ephemeral message group <NUM> has an associated group duration parameter <NUM>, a value of which determines a time-duration for which the ephemeral message group <NUM> is presented and accessible to users of the messaging system <NUM>. The group duration parameter <NUM>, for example, may be the duration of a music concert, where the ephemeral message group <NUM> is a collection of content pertaining to that concert. Alternatively, a user (either the owning user or a curator user) may specify the value for the group duration parameter <NUM> when performing the setup and creation of the ephemeral message group <NUM>.

Additionally, each ephemeral message <NUM> within the ephemeral message group <NUM> has an associated group participation parameter <NUM>, a value of which determines the duration of time for which the ephemeral message <NUM> will be accessible within the context of the ephemeral message group <NUM>. Accordingly, a particular ephemeral message group <NUM> may "expire" and become inaccessible within the context of the ephemeral message group <NUM>, prior to the ephemeral message group <NUM> itself expiring in terms of the group duration parameter <NUM>. The group duration parameter <NUM>, group participation parameter <NUM>, and message receiver identifier <NUM> each provide input to a group timer <NUM> which operationally determines, firstly, whether a particular ephemeral message <NUM> of the ephemeral message group <NUM> will be displayed to a particular receiving user and, if so, for how long. Note that the ephemeral message group <NUM> is also aware of the identity of the particular receiving user as a result of the message receiver identifier <NUM>.

Accordingly, the group timer <NUM> operationally controls the overall lifespan of an associated ephemeral message group <NUM>, as well as an individual ephemeral message <NUM> included in the ephemeral message group <NUM>. In one embodiment, each and every ephemeral message <NUM> within the ephemeral message group <NUM> remains viewable and accessible for a time-period specified by the group duration parameter <NUM>. In a further embodiment, a certain ephemeral message <NUM> may expire, within the context of ephemeral message group <NUM>, based on a group participation parameter <NUM>. Note that a message duration parameter <NUM> may still determine the duration of time for which a particular ephemeral message <NUM> is displayed to a receiving user, even within the context of the ephemeral message group <NUM>. Accordingly, the message duration parameter <NUM> determines the duration of time that a particular ephemeral message <NUM> is displayed to a receiving user, regardless of whether the receiving user is viewing that ephemeral message <NUM> inside or outside the context of an ephemeral message group <NUM>.

The ephemeral timer system <NUM> may furthermore operationally remove a particular ephemeral message <NUM> from the ephemeral message group <NUM> based on a determination that it has exceeded an associated group participation parameter <NUM>. For example, when a sending user has established a group participation parameter <NUM> of <NUM> hours from posting, the ephemeral timer system <NUM> will remove the relevant ephemeral message <NUM> from the ephemeral message group <NUM> after the specified <NUM> hours. The ephemeral timer system <NUM> also operates to remove an ephemeral message group <NUM> either when the group participation parameter <NUM> for each and every ephemeral message <NUM> within the ephemeral message group <NUM> has expired, or when the ephemeral message group <NUM> itself has expired in terms of the group duration parameter <NUM>.

In certain use cases, a creator of a particular ephemeral message group <NUM> may specify an indefinite group duration parameter <NUM>. In this case, the expiration of the group participation parameter <NUM> for the last remaining ephemeral message <NUM> within the ephemeral message group <NUM> will determine when the ephemeral message group <NUM> itself expires. In this case, a new ephemeral message <NUM>, added to the ephemeral message group <NUM>, with a new group participation parameter <NUM>, effectively extends the life of an ephemeral message group <NUM> to equal the value of the group participation parameter <NUM>.

Responsive to the ephemeral timer system <NUM> determining that an ephemeral message group <NUM> has expired (e.g., is no longer accessible), the ephemeral timer system <NUM> communicates with the messaging system <NUM> (and, for example, specifically the messaging client application <NUM>) to cause an indicium (e.g., an icon) associated with the relevant ephemeral message group <NUM> to no longer be displayed within a user interface of the messaging client application <NUM>. Similarly, when the ephemeral timer system <NUM> determines that the message duration parameter <NUM> for a particular ephemeral message <NUM> has expired, the ephemeral timer system <NUM> causes the messaging client application <NUM> to no longer display an indicium (e.g., an icon or textual identification) associated with the ephemeral message <NUM>.

<FIG> is an interaction diagram illustrating a process <NUM> for selecting augmented reality content based on speech input to perform an action on an object, in accordance with some example embodiments. For explanatory purposes, the process <NUM> is primarily described herein with reference to the messaging client application <NUM>, the speech recognition client application <NUM>, the speech recognition server system <NUM>, and the messaging server system <NUM> of <FIG>. However, the process <NUM> may be performed by one or more other components, and/or by other suitable devices. Further for explanatory purposes, the blocks of the process <NUM> are described herein as occurring in serial, or linearly. However, multiple blocks of the process <NUM> may occur in parallel. In addition, the blocks of the process <NUM> need not be performed in the order shown and/or one or more blocks of the process <NUM> need not be performed and/or can be replaced by other operations.

As described herein, the client device <NUM> is configured to provide for selecting augmented reality content items (e.g., corresponding to augmented reality experiences), based on speech input (e.g., a user's voice) received at the messaging client application <NUM>, and further based on objects detected in image data captured by a device camera. For example, the messaging client application <NUM> requests the speech recognition client application <NUM> to perform speech recognition on the speech input, in order to determine keyword(s) for searching plural augmented reality content items (e.g., available augmented reality content items). The messaging client application <NUM> determines that the keyword(s) indicate an action to perform on an object depicted in the captured image data. The messaging client application <NUM> sends attributes of the object and attributes of the action to the messaging server system <NUM>, which is configured to select an augmented reality content item (e.g., augmented reality experience) based on the attributes. The messaging client application <NUM> displays the selected augmented reality content item (e.g., augmented reality experience) together with the captured image data.

At block <NUM>, the messaging client application <NUM> causes a camera of the client device <NUM> to capture an image. For example, the messaging client application <NUM> is configured to default to activating the camera when the messaging client application <NUM> is initialized. Alternatively, or in addition, the messaging client application <NUM> automatically activates the camera for particular interfaces of the messaging client application <NUM>, such as an interface for generating multimedia content (e.g., for including in a message).

At block <NUM>, the messaging client application <NUM> receives speech input (e.g., a voice command to select an augmented reality content item for display). The speech input is received when the camera of the client device <NUM> is activated and capturing image data.

In one or more embodiments, the speech input received by the messaging client application <NUM> includes a trigger word (e.g., "Hey," "Hey Messaging App," "Messaging App") indicating to initialize speech recognition, and further includes a voice command to select an augmented reality content item for display (e.g., "what book is that," "solve this math problem" and the like, as discussed below with respect to <FIG> and <FIG>). The messaging client application <NUM> is configured to provide the speech input to the speech recognition client application <NUM>, for speech recognition (operation <NUM>).

In one or more embodiments, the speech recognition client application <NUM> is configured to process the speech input in multiple stages. For example, in a first stage, the speech recognition client application <NUM> detects whether at least a portion of the speech input corresponds to a human voice, using voice activity detection (VAD) or other known techniques. In some embodiments, the speech recognition client application <NUM> implements the VAD locally, such that the client device <NUM> itself performs the detection of a human voice.

In a second stage, if human voice is detected in the speech input, the speech recognition client application <NUM> locally determines (e.g., on the client device <NUM>) if the speech input includes a predefined trigger word (e.g., "Hey," "Hey Messaging App," "Messaging App"). Alternatively, detection of the trigger word may be performed by the speech recognition server system <NUM>, based on a request sent thereto.

In a third phase, if the speech input is determined to include the trigger word, the speech recognition client application <NUM> provides the speech input to the speech recognition server system <NUM>, to determine keyword(s) based on the speech input. As noted above, in addition to including the trigger word, the speech input may include a voice command (e.g., from which the keyword(s) are determined) to select a particular augmented reality content item for display.

It is noted that the above-described three stages correspond to an example of speech recognition, and that other techniques may be used instead of, or in addition to, these stages. For example, as an alternative to requiring a trigger word, the speech recognition client application <NUM> may be configured to initiate the speech recognition service of the speech recognition server system <NUM> in response to a predefined gesture (e.g., user input associated with a hardware button of the client device <NUM> and/or a software button displayed within the messaging client application <NUM>). The user gesture may be accompanied by speech input provided by the user, where the speech input includes the voice command (and does not include the trigger word).

In another example, it is possible that the speech input includes the trigger word, but does not initially include a voice command (e.g., "Hey," "Hey Messaging App," and/or "Messaging App," followed by a pause signifying the end of the speech input). In such a case, the speech recognition client application <NUM> in conjunction with the messaging client application <NUM> may prompt the user for the voice command (e.g., by a display message and/or audio message such as "How can I help you?"). The user may respond, via the messaging client application <NUM>, with additional speech input corresponding to the voice command, with the speech recognition client application <NUM> being configured to send the additional speech input to the speech recognition server system <NUM> for speech recognition and keyword determination.

Thus, at block <NUM>, the speech recognition client application <NUM> determines one or more keywords based on the speech input, where such determination is based on the speech recognition client application <NUM> sending the speech input to the speech recognition server system <NUM>. In some embodiments, the speech recognition server system <NUM> is configured to implement one or more automatic speech recognition (ASR) algorithms, or other known techniques, to translate the speech input into the one or more text-based keywords. The speech recognition client application <NUM> then sends the one or more keywords (e.g., received from the speech recognition server system <NUM>) to the messaging client application <NUM> (operation <NUM>).

In one or more embodiments, the messaging client application <NUM> is configured to display a text-based version of the voice command portion of the speech input. In this regard, the speech recognition server system <NUM> may perform ASR to translate the entirety of the voice command portion of the speech input into text, and may provide that text (along with the keyword(s)) to the messaging client application (e.g., at operation <NUM>). Alternatively, or in addition, the messaging client application <NUM> in some embodiments is configured to display a graphical element (e.g., an animation) while the speech input is being received from the user.

At block <NUM>, the messaging client application <NUM> determines that the keyword(s) indicate an object depicted in the image captured by the device camera, and further indicate an action to perform with respect to the object. For example, the messaging client application <NUM> determines that a first of the keyword(s) indicates the object depicted in the captured image, and that a second of the keyword(s) indicates the action to perform with respect to the object.

As noted above, the messaging client application <NUM> is configured to implement or otherwise access object recognition algorithms (e.g., including machine learning algorithms) configured to scan a captured image, and to detect/track the movement of objects within the image. By way of non-limiting example, detectable objects within an image include: a human face, parts of a human body, animals and parts thereof, landscapes, objects in nature, non-living objects (e.g., chairs, books, cars, buildings, other structures), illustrations of objects (e.g., on posters and/or flyers), text-based objects, equation-based objects and the like. Moreover, the messaging client application <NUM> is configured to determine or otherwise access attributes of objects, such as a name, type, genre, color, size, shape, texture, geolocation and/or other supplemental information (e.g., a song title/artist for an object corresponding to media).

In one or more implementations, the messaging client application <NUM> is further configured to determine actions associated with objects. For example, the messaging client application <NUM> may access (e.g., from local and/or remote storage) one or more respective actions associated with a particular type of object. By way of non-limiting example, actions that may be performed with respect to an object include: providing identifying and/or supplemental information for an object (e.g., name, genre, song title, author, geolocation, etc.), providing a solution to an object corresponding to a problem (e.g., a solution to a math problem, an answer to a question), applying a visual effect to the object (e.g., texture, three-dimensional mesh), and the like. Further, the messaging client application <NUM> is configured to determine or otherwise access attributes for actions, such as a type of action (e.g., actions to identify, solve, modify, provide visual effects, and the like), a duration to perform the action, and/or other characteristics related to performing the action.

Thus, based on the keyword(s) provided at operation <NUM>, the detection of object(s) within captured image data, and the actions associated with different types of objects, the messaging client application <NUM> is configured to determine that the keyword(s) indicate an object depicted in the image, and further indicate an action to perform with respect to the obj ect.

At operation <NUM>, the messaging client application <NUM> sends attribute(s) of the object (e.g., a name of the object) and/or attribute(s) of the action (e.g., a type of the action) to messaging server system <NUM> (operation <NUM>). In one or more embodiments, the messaging client application <NUM> sends the keyword(s), as provided by the speech recognition client application <NUM>, as the attributes of the object and of the action.

In response, the messaging server system <NUM> searches for and selects an augmented reality content item (e.g., augmented reality experience) based on the attributes of the object and the attributes of the action (block <NUM>). In one or more embodiments, the messaging server system <NUM> is configured to search a set of available augmented reality content items, by comparing the attributes of the object and of the action with respective attributes and/or predefined words associated each of the available augmented reality content items.

As noted above, the augmented reality content items table <NUM> included in the database <NUM> is configured to designate or label each augmented reality content item (e.g., via metadata) with respective attributes and/or predefined word(s) to search the augmented reality content item. Thus, in one or more embodiments, the messaging server system <NUM> queries the database <NUM> with the attributes of the object and of the action (e.g., the name of the object and the type of the action to perform), and the database <NUM> may provide one or more selected augmented reality content item(s) as a result to the query.

In a case where the object/action attributes correspond with the respective attributes and/or predefined word(s) for more than one augmented reality content item, the database <NUM> may be configured to provide an indication of multiple augmented reality content items as a result to the query. Moreover, the database <NUM> may rank the multiple augmented reality content items (e.g., based on a number of matches, and/or weights assigned to one of more of the object/action attributes, augmented reality content items attributes, and/or the predefined words). The database <NUM> may provide an indication of the ranking to the messaging server system <NUM> as part of the result to the query.

Based on the received results, the messaging server system <NUM> sends the indication of the selected augmented reality content item(s) to the messaging client application <NUM>, together with the ranking information, if applicable (operation <NUM>).

The messaging client application <NUM> displays the selected augmented reality content item together with image data captured by a camera of the client device <NUM> (block <NUM>). In a case where multiple augmented reality content item(s) are provided by the messaging server system <NUM>, the messaging client application <NUM> may display the highest-ranked augmented reality content item with the image data, and provide the remaining augmented reality content item(s) within a carousel interface, for example, in ranked order. As discussed below with respect to <FIG> and <FIG>, the messaging client application <NUM> displays the carousel interface, which provides for the user to switch between the multiple available augmented reality content items. The available augmented reality content items may include the ranked set of augmented reality content item(s) provided to the messaging client application <NUM> at operation <NUM> and/or additional available augmented reality content item(s) (e.g., as stored in the augmented reality content items table <NUM>).

Thus, by virtue of the process <NUM>, it is possible to provide for selecting augmented reality content (e.g., an augmented reality content item) based on voice commands (e.g., speech input) and on objects depicted in image data captured be a device camera, with respect to the messaging client application <NUM>. The selected augmented reality content item may be displayed together with the captured image data.

<FIG> illustrate a user interface <NUM> and a user interface <NUM> for selecting augmented reality content (e.g., an augmented reality experience) based on speech input to provide identifying information for an object, in accordance with some example embodiments. For example, the user interface <NUM> and the user interface <NUM> are displayed within the messaging client application <NUM>. The user interface <NUM> of <FIG> corresponds to an interface in which a voice command is received, and the user interface <NUM> of <FIG> corresponds to an interface in which a selected augmented reality content item is applied to captured image data.

In the example of <FIG>, the user interface <NUM> includes captured image data <NUM> corresponding to image data captured by a front-facing camera of the client device <NUM>. Alternatively, the image data may be captured by a rear-facing camera of the client device <NUM>. In one or more embodiments, user selection of the button <NUM> provides for generating a message which includes an image (e.g., in response to a press/tap gesture of the button <NUM>) and/or a video (e.g., in response to a press-and-hold gesture of the button <NUM>) of the screen content, for example, to send to friends, include in a Story, and the like.

As discussed above, the user of the client device <NUM> may provide speech input to the messaging client application <NUM>. The speech input includes a voice command (e.g., which may be preceded by a trigger word) for selecting a particular augmented reality content item. In the example of <FIG>, the speech input may have included a trigger word (e.g., not shown), followed by the voice command/inquiry of "what book is that.

In one or more implementations, while receiving the speech input, the messaging client application <NUM> is configured to display converted text <NUM>, corresponding to a text-based version of the speech input as determined by the speech recognition server system <NUM>. Alternatively, or in addition, the messaging client application <NUM> is configured to display voice command graphics (not shown), for example, corresponding to an animation indicating receipt (e.g., in real-time) of speech input.

Turning to <FIG>, the user interface <NUM> is displayed (e.g., by the messaging client application <NUM>) in response to receiving the speech input. As discussed above, the messaging server system <NUM> selects an augmented reality content item from plural available augmented reality content items based at least part on keyword(s) (e.g., "what," "book,") from speech input. For example, the keyword of "book" corresponds to an object depicted in the captured image data <NUM>, as detected by the messaging client application <NUM> as discussed above.

The messaging client application <NUM> may detect different objects in the captured image data <NUM> (e.g., as part of a scanning operation as discussed above). For example, the messaging client application <NUM> may identify the book object <NUM>, as well as multiple other objects (not shown, such as a table, a magazine, a light, and the like) in the captured image data <NUM>. In identifying the objects, the messaging client application <NUM> determines that the keyword of "book" is depicted in the captured image data <NUM> (e.g., as the book object <NUM>).

In addition, the messaging client application <NUM> determines that the keyword of "what" indicates an action to perform on the book object <NUM>. For example, the keyword of "what" may be predetermined to be associated with the action of providing identifying information for an object. Other examples of predetermined keyword(s) associated with the action of providing identifying information include, but are not limited to "identify," "inform me about," "provide information on," and the like.

As discussed above, the messaging server system <NUM> searches for and select(s) one or more augmented reality content item(s) based on attributes of the book object <NUM> and the action (e.g., providing identifying information), and provides an indication of the Len(es) and/or ranking information to the messaging client application <NUM>. The messaging client application <NUM> then launches the selected augmented reality content item for displaying augmented reality content item <NUM> (e.g., the title for the book object <NUM>) together with the captured image data <NUM>. For example, the selected augmented reality content item may correspond to an application configured to provide identifying information for books. In one or more implementations, a supplemental information element <NUM> may be displayed to indicate other identifying information (e.g., author, availability) for the book object <NUM>. The other identifying information may also be provided by the selected augmented reality content item. Moreover, the supplemental information element <NUM> may correspond to a user-selectable link for redirecting to a third-party application for additional information regarding and/or the ability to purchase, the book.

Moreover, the user interface <NUM> includes a carousel interface <NUM> which allows the user to cycle through and/or select a different augmented reality content item to apply with respect to the captured image data <NUM>. Each of the available augmented reality content items is represented by an icon which is user-selectable for switching to the respective augmented reality content item. In one or more embodiments, the icon corresponding to the active augmented reality content item (e.g., selected augmented reality content item icon <NUM>) is displayed in a different manner relative to (e.g., larger than) the remaining icons. In one or more embodiments, user selection of the selected augmented reality content item icon <NUM> provides for generating a message which includes an image (e.g., in response to a press/tap gesture of the selected augmented reality content item icon <NUM>) and/or a video (e.g., in response to a press-and-hold gesture of the selected augmented reality content item icon <NUM>) of the screen content, for example, to send to friends, include in a Story, and the like.

<FIG> illustrate a user interface <NUM> and a user interface <NUM> for selecting augmented reality content (e.g., an augmented reality experience) based on speech input to solve a problem corresponding to an object, in accordance with some example embodiments. For example, the user interface <NUM> and the user interface <NUM> are displayed within the messaging client application <NUM>. The user interface <NUM> of <FIG> corresponds to an interface in which a voice command is received, and the user interface <NUM> of <FIG> corresponds to an interface in which a selected augmented reality content item is applied to captured image data.

As discussed above, the user of the client device <NUM> may provide speech input to the messaging client application <NUM>. The speech input includes a voice command (e.g., which may be preceded by a trigger word) for selecting a particular augmented reality content item. In the example of <FIG>, the speech input may have included a trigger word (e.g., not shown), followed by the voice command/inquiry of "solve this math problem.

Turning to <FIG>, the user interface <NUM> is displayed (e.g., by the messaging client application <NUM>) in response to receiving the speech input. As discussed above, the messaging server system <NUM> selects an augmented reality content item from plural available augmented reality content items based at least part on keyword(s) (e.g., "solve," "math problem") from speech input. For example, the keywords of "math problem" corresponds to an object depicted in the captured image data <NUM>, as detected by the messaging client application <NUM> as discussed above.

The messaging client application <NUM> may detect different objects in the captured image data <NUM> (e.g., as part of a scanning operation). For example, the messaging client application <NUM> may identify the math problem object <NUM>, as well as multiple other objects (paper, a pen, and the like) in the captured image data <NUM>. In identifying the objects, the messaging client application <NUM> determines that the keyword of "math problem" is depicted in the captured image data <NUM> (e.g., as the math problem object <NUM>).

In addition, the messaging client application <NUM> determines that the keyword of "solve" indicates an action to perform with respect to the math problem object <NUM>. For example, the keyword of "solve" may be predetermined to be associated with the action of solving a problem. Other examples of predetermined keyword(s) associated with the action of solving a problem include, but are not limited to "calculate," "figure out," "provide an answer for," and the like.

As discussed above, the messaging server system <NUM> searches for and select(s) one or more augmented reality content item(s) based on attributes of the math problem object <NUM> and the action (e.g., solving a problem), and provides an indication of the Len(es) and/or ranking information to the messaging client application <NUM>. The messaging client application <NUM> then launches the selected augmented reality content item for displaying the augmented reality content item <NUM> (e.g., that solves the math problem object <NUM>) together with the captured image data <NUM>. For example, the selected augmented reality content item may correspond to an application configured to solve math problems (e.g., a math solver application). In one or more implementations, the messaging client application <NUM> may provide a user-selectable link (e.g., the button <NUM>) for redirecting to a third-party application that provides additional information with respect to solving the math problem object <NUM>.

It is noted that <FIG> and <FIG> correspond to examples of augmented reality content items that may be selected based on speech input (e.g., a voice command) provided by the user. Other examples of augmented reality content item selection are discussed as follows.

In one example, the messaging client application <NUM> receives speech input to provide visual effects for a food item depicted in a captured image. For example, the user may have provided the voice command to "animate my hamburger" (e.g., or other similar command). In response, the messaging client application <NUM> (e.g., in conjunction with speech recognition client application <NUM>, the speech recognition server system <NUM> and/or the messaging server system <NUM>) retrieves an augmented reality content item (e.g., an augmented reality content item) that includes one or more graphical elements that look like the food item (e.g., animated images of hamburgers and/or objects associated with hamburgers). The messaging client application <NUM> presents the one or more graphical elements around the food item or on top of the food item. The one or more graphical elements may be animated to appear to be circling around the food item.

In another example, the messaging client application <NUM> receives speech input to provide identifying information and/or visual effects for a movie or media item depicted in a captured image. For example, the user may have provided the voice command "what movie is this" (e.g., or other similar command). In response, the messaging client application <NUM> (e.g., in conjunction with speech recognition client application <NUM>, the speech recognition server system <NUM> and/or the messaging server system <NUM>) retrieves an augmented reality content item that includes information and/or graphical elements that are associated with the movie or media item. The messaging client application <NUM> presents the information and/or graphical elements around the movie or media item or on top of the movie or media item. For example, if cover art includes a picture of a lion, the augmented reality content item includes a graphical element that animates a lion and replaces the picture of the lion in the cover art with the animated lion of the graphical element.

In another example, the messaging client application <NUM> receives speech input to provide weather information for a landscape (e.g., including the sky) depicted in a captured image. For example, the user may have provided the voice command "what's the weather like here" (e.g., or other similar command). In response, the messaging client application <NUM> (e.g., in conjunction with speech recognition client application <NUM>, the speech recognition server system <NUM> and/or the messaging server system <NUM>) employs an augmented reality content item (e.g., corresponding to a weather application) to provide current weather information for the depicted landscape. The current weather information may be based at least partially on a geographical location of the client device <NUM>. The selected augmented reality content item provides one or more graphical elements that depict the weather, and the messaging client application <NUM> presents the one or more graphical elements on top of the landscape (e.g., including the sky).

<FIG> is a flowchart illustrating a process <NUM> for selecting augmented reality content based on speech input to perform an action on an object, in accordance with some example embodiments. For explanatory purposes, the process <NUM> is primarily described herein with reference to the messaging client application <NUM>, the speech recognition client application <NUM>, the speech recognition server system <NUM>, and the messaging server system <NUM> of <FIG>. However, one or more blocks (or operations) of the process <NUM> may be performed by one or more other components, and/or by other suitable devices. Further for explanatory purposes, the blocks of the process <NUM> are described herein as occurring in serial, or linearly. However, multiple blocks of the process <NUM> may occur in parallel. In addition, the blocks of the process <NUM> need not be performed in the order shown and/or one or more blocks of the process <NUM> need not be performed and/or can be replaced by other operations.

The messaging client application <NUM> running on the client device <NUM> causes a camera of the client device <NUM> to capture an image (block <NUM>). The messaging client application <NUM> receives speech input to select augmented reality content (e.g., an augmented reality content item) for display with the image (block <NUM>).

The messaging client application <NUM> determines at least one keyword included in the speech input (block <NUM>). Determining the at least one keyword may include sending, to the speech recognition server system <NUM>, a request to perform speech recognition based on the speech input, and receiving, from the speech recognition server system <NUM> and based on sending the request, the at least one keyword. A first part of the speech input may include a trigger word, and the at least one keyword may be based on a second part of the speech input that does not include the trigger word.

The messaging client application <NUM> determines that the at least one keyword indicates an object depicted in the image and an action to perform with respect to the object (block <NUM>). The at least one keyword may include a first keyword indicating the object and a second keyword indicating the action to perform with respect to the object. The messaging client application <NUM> may perform a scan of the image to identify multiple objects in the image, and detect, based on performing the scan, the object from among the multiple objects.

The action may correspond to providing identifying information for the object, such that the augmented reality content provides the identifying information for the object. In another example, the object may correspond to a problem for solving, such that the action corresponds to solving the problem, and the augmented reality content displays a solution to the problem. In another example, the action may correspond to applying a visual effect to the object depicted in the image, such that the augmented reality content provides for applying the visual effect to the object depicted in the image.

The messaging client application <NUM> identifies, from plural augmented reality content items, an augmented reality content item that corresponds to performing the action with respect to the object (block <NUM>).

Identifying the augmented reality content item may include sending, to a messaging server system <NUM>, a request to search the plural augmented reality content items based on an attribute of the object and an attribute of the action, and receiving, from the messaging server system <NUM> and based on sending the request, an indication of the augmented reality content item. The messaging server system <NUM> may be configured to search the plural augmented reality content items by comparing the attribute of the object and the attribute of the action with predefined attributes associated with each of the plural augmented reality content items.

The messaging client application <NUM> displays the augmented reality content item (e.g., augmented reality content item) with the image (block <NUM>). The messaging client application <NUM> may provide a carousel interface for display, the carousel interface including a respective icon for each of the plural augmented reality content items, and provide for differentiated display of the icon for the augmented reality content item, relative to the remaining icons, within the carousel interface.

The operating system <NUM> manages hardware resources and provides common services. The operating system <NUM> includes, for example, a kernel <NUM>, services <NUM>, and drivers <NUM>. The kernel <NUM> acts as an abstraction layer between the hardware and the other software layers. For example, the kernel <NUM> provides memory management, processor management (e.g., scheduling), component management, networking, and security settings, among other functionality. The services <NUM> can provide other common services for the other software layers. The drivers <NUM> are responsible for controlling or interfacing with the underlying hardware. For instance, the drivers <NUM> can include display drivers, camera drivers, BLUETOOTH® or BLUETOOTH® Low Energy drivers, flash memory drivers, serial communication drivers (e.g., Universal Serial Bus (USB) drivers), WI-FI® drivers, audio drivers, power management drivers, and so forth.

The libraries <NUM> provide a low-level common infrastructure used by the applications <NUM>. The libraries <NUM> can include system libraries <NUM> (e.g., C standard library) that provide functions such as memory allocation functions, string manipulation functions, mathematic functions, and the like. In addition, the libraries <NUM> can include API libraries <NUM> such as media libraries (e.g., libraries to support presentation and manipulation of various media formats such as Moving Picture Experts Group-<NUM> (MPEG4), Advanced Video Coding (H. <NUM> or AVC), Moving Picture Experts Group Layer-<NUM> (MP3), Advanced Audio Coding (AAC), Adaptive Multi-Rate (AMR) audio codec, Joint Photographic Experts Group (JPEG or JPG), or Portable Network Graphics (PNG)), graphics libraries (e.g., an OpenGL framework used to render in two dimensions (2D) and three dimensions (3D) in a graphic content on a display), database libraries (e.g., SQLite to provide various relational database functions), web libraries (e.g., WebKit to provide web browsing functionality), and the like. The libraries <NUM> can also include a wide variety of other libraries <NUM> to provide many other APIs to the applications <NUM>.

The frameworks <NUM> provide a high-level common infrastructure that is used by the applications <NUM>. For example, the frameworks <NUM> provide various graphical user interface (GUI) functions, high-level resource management, and high-level location services. The frameworks <NUM> can provide a broad spectrum of other APIs that can be used by the applications <NUM>, some of which may be specific to a particular operating system or platform.

In an example embodiment, the applications <NUM> may include a home application <NUM>, a contacts application <NUM>, a browser application <NUM>, a book reader application <NUM>, a location application <NUM>, a media application <NUM>, a messaging application <NUM> (e.g., corresponding to the messaging client application <NUM>), a game application <NUM>, and a broad assortment of other applications such as third-party applications <NUM>. The applications <NUM> are programs that execute functions defined in the programs. Various programming languages can be employed to create one or more of the applications <NUM>, structured in a variety of manners, such as object-oriented programming languages (e.g., Objective-C, Java, or C++) or procedural programming languages (e.g., C or assembly language). In a specific example, the third-party applications <NUM> (e.g., applications developed using the ANDROID™ or IOS™ software development kit (SDK) by an entity other than the vendor of the particular platform) may be mobile software running on a mobile operating system such as IOS™, ANDROID™, WINDOWS® Phone, or another mobile operating system. In this example, the third-party applications <NUM> can invoke the API calls <NUM> provided by the operating system <NUM> to facilitate functionality described herein.

<FIG> is a diagrammatic representation of a machine <NUM> within which instructions <NUM> (e.g., software, a program, an application, an applet, an app, or other executable code) for causing the machine <NUM> to perform any one or more of the methodologies discussed herein may be executed. For example, the instructions <NUM> may cause the machine <NUM> to execute any one or more of the methods described herein. The instructions <NUM> transform the general, non-programmed machine <NUM> into a particular machine <NUM> programmed to carry out the described and illustrated functions in the manner described. The machine <NUM> may operate as a standalone device or may be coupled (e.g., networked) to other machines. In a networked deployment, the machine <NUM> may operate in the capacity of a server machine or a client machine in a server-client network environment, or as a peer machine in a peer-to-peer (or distributed) network environment. The machine <NUM> may comprise, but not be limited to, a server computer, a client computer, a personal computer (PC), a tablet computer, a laptop computer, a netbook, a set-top box (STB), a PDA, an entertainment media system, a cellular telephone, 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 executing the instructions <NUM>, sequentially or otherwise, that specify actions to be taken by the machine <NUM>. Further, while only a single machine <NUM> is illustrated, the term "machine" shall also be taken to include a collection of machines that individually or jointly execute the instructions <NUM> to perform any one or more of the methodologies discussed herein.

The machine <NUM> may include processors <NUM>, memory <NUM>, and I/O components <NUM>, which may be configured to communicate with each other via a bus <NUM>. In an example embodiment, the processors <NUM> (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 ASIC, a Radio-Frequency Integrated Circuit (RFIC), another processor, or any suitable combination thereof) may include, for example, a processor <NUM> and a processor <NUM> that execute the instructions <NUM>. The term "processor" is intended to include multi-core processors that may comprise two or more independent processors (sometimes referred to as "cores") that may execute instructions contemporaneously. Although <FIG> shows multiple processors <NUM>, the machine <NUM> may include a single processor with a single core, a single processor with multiple cores (e.g., a multi-core processor), multiple processors with a single core, multiple processors with multiples cores, or any combination thereof.

The memory <NUM> includes a main memory <NUM>, a static memory <NUM>, and a storage unit <NUM><NUM>, both accessible to the processors <NUM> via the bus <NUM>. The instructions <NUM> may also reside, completely or partially, within the main memory <NUM>, within the static memory <NUM>, within machine-readable medium <NUM> within the storage unit <NUM>, within at least one of the processors <NUM> (e.g., within the processor's cache memory), or any suitable combination thereof, during execution thereof by the machine <NUM>.

The I/O components <NUM> may include a wide variety of components to receive input, provide output, produce output, transmit information, exchange information, capture measurements, and so on. The specific I/O components <NUM> that are included in a particular machine will depend on the type of machine. For example, portable machines such as mobile phones may include a touch input device or other such input mechanisms, while a headless server machine will likely not include such a touch input device. It will be appreciated that the I/O components <NUM> may include many other components that are not shown in <FIG>. In various example embodiments, the I/O components <NUM> may include output components <NUM> and input components <NUM>. The output components <NUM> may include visual components (e.g., a display such as a plasma display panel (PDP), a light emitting diode (LED) display, a liquid crystal display (LCD), a projector, or a cathode ray tube (CRT)), acoustic components (e.g., speakers), haptic components (e.g., a vibratory motor, resistance mechanisms), other signal generators, and so forth. The input components <NUM> may include alphanumeric input components (e.g., a keyboard, a touch screen configured to receive alphanumeric input, a photo-optical keyboard, or other alphanumeric input components), point-based input components (e.g., a mouse, a touchpad, a trackball, a joystick, a motion sensor, or another pointing instrument), tactile input components (e.g., a physical button, a touch screen that provides location and/or force of touches or touch gestures, or other tactile input components), audio input components (e.g., a microphone), optical sensor components (e.g., a camera) and the like.

In further example embodiments, the I/O components <NUM> may include biometric components <NUM>, motion components <NUM>, environmental components <NUM>, or position components <NUM>, among a wide array of other components. For example, the biometric components <NUM> include components to detect expressions (e.g., hand expressions, facial expressions, vocal expressions, body gestures, or eye tracking), measure biosignals (e.g., blood pressure, heart rate, body temperature, perspiration, or brain waves), identify a person (e.g., voice identification, retinal identification, facial identification, fingerprint identification, or electroencephalogram-based identification), and the like. The motion components <NUM> include acceleration sensor components (e.g., accelerometer), gravitation sensor components, rotation sensor components (e.g., gyroscope), and so forth. The environmental components <NUM> include, for example, illumination sensor components (e.g., photometer), temperature sensor components (e.g., one or more thermometers that detect ambient temperature), humidity sensor components, pressure sensor components (e.g., barometer), acoustic sensor components (e.g., one or more microphones that detect background noise), proximity sensor components (e.g., infrared sensors that detect nearby objects), gas sensors (e.g., gas detection sensors to detection concentrations of hazardous gases for safety or to measure pollutants in the atmosphere), or other components that may provide indications, measurements, or signals corresponding to a surrounding physical environment. The position components <NUM> include location sensor components (e.g., a GPS receiver component), altitude sensor components (e.g., altimeters or barometers that detect air pressure from which altitude may be derived), orientation sensor components (e.g., magnetometers), and the like.

Communication may be implemented using a wide variety of technologies. The I/O components <NUM> further include communication components <NUM> operable to couple the machine <NUM> to a network <NUM> or devices <NUM> via a coupling <NUM> and a coupling <NUM>, respectively. For example, the communication components <NUM> may include a network interface component or another suitable device to interface with the network <NUM>. In further examples, the communication components <NUM> may include wired communication components, wireless communication components, cellular communication components, Near Field Communication (NFC) components, Bluetooth® components (e.g., Bluetooth® Low Energy), Wi-Fi® components, and other communication components to provide communication via other modalities. The devices <NUM> may be another machine or any of a wide variety of peripheral devices (e.g., a peripheral device coupled via a USB).

For example, the communication components <NUM> may include Radio Frequency Identification (RFID) tag reader components, NFC smart tag detection components, optical reader components (e.g., an optical sensor to detect one-dimensional bar codes such as Universal Product Code (UPC) bar code, multidimensional bar codes such as Quick Response (QR) code, Aztec code, Data Matrix, Dataglyph, MaxiCode, PDF417, Ultra Code, UCC RSS-2D bar code, and other optical codes), or acoustic detection components (e.g., microphones to identify tagged audio signals).

The various memories (e.g., memory <NUM>, main memory <NUM>, static memory <NUM>, and/or memory of the processors <NUM>) and/or storage unit <NUM> may store one or more sets of instructions and data structures (e.g., software) embodying or used by any one or more of the methodologies or functions described herein. These instructions (e.g., the instructions <NUM>), when executed by processors <NUM>, cause various operations to implement the disclosed embodiments.

The instructions <NUM> may be transmitted or received over the network <NUM>, using a transmission medium, via a network interface device (e.g., a network interface component included in the communication components <NUM>) and using any one of a number of well-known transfer protocols (e.g., hypertext transfer protocol (HTTP)). Similarly, the instructions <NUM> may be transmitted or received using a transmission medium via the coupling <NUM> (e.g., a peer-to-peer coupling) to the devices <NUM>.

A "client device" refers to any machine that interfaces to a communications network to obtain resources from one or more server systems or other client devices.

A "communication network" refers to one or more portions of a network that may be an ad hoc network, an intranet, an extranet, a virtual private network (VPN), a local area network (LAN), a wireless LAN (WLAN), a wide area network (WAN), a wireless WAN (WWAN), a metropolitan area network (MAN), the Internet, a portion of the Internet, a portion of the Public Switched Telephone Network (PSTN), a plain old telephone service (POTS) network, a cellular telephone network, a wireless network, a Wi-Fi® network, another type of network, or a combination of two or more such networks.

A "component" refers to a device, physical entity, or logic having boundaries defined by function or subroutine calls, branch points, APIs, or other technologies that provide for the partitioning or modularization of particular processing or control functions. Components may be combined via their interfaces with other components to carry out a machine process. A component may be a packaged functional hardware unit designed for use with other components and a part of a program that usually performs a particular function of related functions. Components may constitute either software components (e.g., code embodied on a machine-readable medium) or hardware components. A "hardware component" is a tangible unit capable of performing certain operations and may be configured or arranged in a certain physical manner. In various example embodiments, one or more computer systems (e.g., a standalone computer system, a client computer system, or a server computer system) or one or more hardware components of a computer system (e.g., a processor or a group of processors) may be configured by software (e.g., an application or application portion) as a hardware component that operates to perform certain operations as described herein. A hardware component may also be implemented mechanically, electronically, or any suitable combination thereof. For example, a hardware component may include dedicated circuitry or logic that is permanently configured to perform certain operations. A hardware component may be a special-purpose processor, such as a field-programmable gate array (FPGA) or an application specific integrated circuit (ASIC). A hardware component may also include programmable logic or circuitry that is temporarily configured by software to perform certain operations. For example, a hardware component may include software executed by a general-purpose processor or other programmable processor. Once configured by such software, hardware components become specific machines (or specific components of a machine) uniquely tailored to perform the configured functions and are no longer general-purpose processors. It will be appreciated that the decision to implement a hardware component mechanically, in dedicated and permanently configured circuitry, or in temporarily configured circuitry (e.g., configured by software), may be driven by cost and time considerations. Accordingly, the phrase "hardware component"(or "hardware-implemented component") should be understood to encompass a tangible entity, be that an entity that is physically constructed, permanently configured (e.g., hardwired), or temporarily configured (e.g., programmed) to operate in a certain manner or to perform certain operations described herein. Considering embodiments in which hardware components are temporarily configured (e.g., programmed), each of the hardware components need not be configured or instantiated at any one instance in time. For example, where a hardware component comprises a general-purpose processor configured by software to become a special-purpose processor, the general-purpose processor may be configured as respectively different special-purpose processors (e.g., comprising different hardware components) at different times. Software accordingly configures a particular processor or processors, for example, to constitute a particular hardware component at one instance of time and to constitute a different hardware component at a different instance of time. Hardware components can provide information to, and receive information from, other hardware components. Accordingly, the described hardware components may be regarded as being communicatively coupled. Where multiple hardware components exist contemporaneously, communications may be achieved through signal transmission (e.g., over appropriate circuits and buses) between or among two or more of the hardware components. In embodiments in which multiple hardware components are configured or instantiated at different times, communications between such hardware components may be achieved, for example, through the storage and retrieval of information in memory structures to which the multiple hardware components have access. For example, one hardware component may perform an operation and store the output of that operation in a memory device to which it is communicatively coupled. A further hardware component may then, at a later time, access the memory device to retrieve and process the stored output. Hardware components may also initiate communications with input or output devices, and can operate on a resource (e.g., a collection of information). Whether temporarily or permanently configured, such processors may constitute processor-implemented components that operate to perform one or more operations or functions described herein. As used herein, "processor-implemented component" refers to a hardware component implemented using one or more processors. Similarly, the methods described herein may be at least partially processor-implemented, with a particular processor or processors being an example of hardware. For example, at least some of the operations of a method may be performed by one or more processors or processor-implemented components. For example, at least some of the operations may be performed by a group of computers (as examples of machines including processors), with these operations being accessible via a network (e.g., the Internet) and via one or more appropriate interfaces (e.g., an API). The performance of certain of the operations may be distributed among the processors, not only residing within a single machine, but deployed across a number of machines. In some example embodiments, the processors or processor-implemented components may be located in a single geographic location (e.g., within a home environment, an office environment, or a server farm). In other example embodiments, the processors or processor-implemented components may be distributed across a number of geographic locations.

A "computer-readable medium" refers to both machine-storage media and transmission media.

An "ephemeral message" refers to a message that is accessible for a time-limited duration. An ephemeral message may be a text, an image, a video and the like. The access time for the ephemeral message may be set by the message sender. Alternatively, the access time may be a default setting or a setting specified by the recipient. Regardless of the setting technique, the message is transitory.

A "machine-storage medium" refers to a single or multiple storage devices and/or media (e.g., a centralized or distributed database, and/or associated caches and servers) that store executable instructions, routines and/or data. Specific examples of machine-storage media, computer-storage media and/or device-storage media include non-volatile memory, including by way of example semiconductor memory devices, e.g., erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), FPGA, and flash memory devices; magnetic disks such as internal hard disks and removable disks; magneto-optical disks; and CD-ROM and DVD-ROM disks The terms "machine-storage medium," "device-storage medium," "computer-storage medium" mean the same thing and may be used interchangeably in this disclosure.

A "processor" refers to any circuit or virtual circuit (a physical circuit emulated by logic executing on an actual processor) that manipulates data values according to control signals (e.g., "commands", "op codes", "machine code", etc.) and which produces corresponding output signals that are applied to operate a machine. A processor may, for example, be 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) or any combination thereof. A processor may further be a multi-core processor having two or more independent processors (sometimes referred to as "cores") that may execute instructions contemporaneously.

Claim 1:
A method of selecting and displaying an augmented reality content item, the method comprising:
causing (<NUM>), by a messaging application running on a device, a camera of the device to capture an image;
receiving (<NUM>) by the messaging application, speech input to select augmented reality content for display with the image;
determining (<NUM>) at least one keyword included in the speech input;
determining (<NUM>) that the at least one keyword indicates an object depicted in the image and an action to perform with respect to the object, characterized in that the object is a math problem and the action corresponds to solving the math problem;
selecting (<NUM>), from plural augmented reality content items, an augmented reality content item that corresponds to displaying a solution to the math problem; and
displaying (<NUM>) the augmented reality content item, which includes the solution to the math problem, with the image.