Patent Description:
The present invention relates to a method, system, and machine-readable medium for presenting a menu element within a presentation of media.

Further aspects of the invention are the subject of the dependent claims.

According to an aspect of the present invention, there is described: a method comprising: causing display of a presentation of media at a client device, the presentation of the media including a display of an icon within the presentation of the media, wherein the icon comprises an identifier that identifies a location of interest; receiving an input that selects the icon from the client device, the input comprising an input attribute; accessing location data from the client device in response to the input that selects the icon, the location data identifying a location within a threshold distance of the location of interest; selecting one or more menu options from among a collection of menu options based on the input duration of the input and the location data from the client device; generating a menu element based on the icon and the input attribute in response to the input that selects the icon, the menu element including the one or more menu options and a display of a map image that includes the location of interest and an indication of the location of the client device; and presenting the menu element at a position within the presentation of the media at the client device.

Social messaging applications are platforms that enable the sharing and distribution of various forms of media content. Users of social messaging applications may send and receive messages that include multimedia to one another, wherein the multimedia may include images, videos, or other content.

One aspect of social messaging applications which have grown in popularity are "stickers. " A sticker is an illustration, or graphical icon, which may be placed or added at a user-defined position within a message. In its simplest form, it may be described as an emoticon, developed to add more depth and breadth of expression than what is possible with traditional punctuation or message content.

<CIT> describes systems, methods, and non-transitory computer readable media to provide one or more candidate stickers through a display screen of a computing device.

As discussed above, in the context of social messaging applications, a sticker is an illustration, or graphical icon, which may be placed or added at a user-defined position within contents of a message. Users of such social messaging applications may add more depth and breadth of expression to their message through the selection and placement of stickers, than what was previously possible through traditional messaging applications. Accordingly, the disclosed system further enhances a user's ability to convey expression through messages, by generating and presenting interactive stickers, wherein the interactive stickers may receive inputs to present content based on contextual factors.

In certain example embodiments, a sticker comprises a graphical icon, and corresponding data objects. For example, a sticker may reference a user account, a location, a group, an event, as well as a topic (i.e., a hashtag), and may also include interactive elements, such as a poll (i.e., a radio selection), a multiple choice question or request, or a true or false question or request. A user may apply a sticker to a message or contents of a message (i.e., media), which may then be received and displayed at a client device. A user of the client device may thereby provide inputs (i.e., tactile inputs) that select the sticker. Responsive to such inputs, further content associated with the sticker may be presented at the client device.

Accordingly, an interactive sticker system is disclosed which performs operations that include: causing display of a presentation of media at a client device, the presentation of the media including a display of an icon within the presentation of the media; receiving an input that selects the icon from the client device, the input comprising an input attribute; generating a menu element based on the icon and the input attribute in response to the input that selects the icon; and presenting the menu element at a position within the presentation of the media at the client device.

In certain example embodiments, the client device may be associated with a user profile that comprises user profile data. For example, user profile data may include a list of user connections (i.e., buddy list), user preferences, user demographics information, a log of user activities performed by the user, user interaction data that indicates bi-directional communications which the user may engage in, location data, as well as explicit and implicit user affinities.

In such embodiments, the interactive sticker system may generate the menu element based on the user profile data associated with the user account, and attributes of the sticker. For example, the sticker may reference a user account (i.e., a username). Responsive to receiving an input from a first user that selects the sticker, the interactive icon system may determine a relationship between the first user and a second user account identified by the sticker. The relationship may include a bidirectional relationship (i.e., the first user and the second user are linked in a social network), a one-way connection (i.e., the first user is linked with the second user in the social network), or an indication that a bidirectional connection of the first user is bidirectionally linked with the second user. The interactive sticker system may thereby present a menu element that comprises one or more menu options based on the relationship.

The interactive sticker corresponds with a location or location of interest. For example, the sticker may comprise a reference to a location of interest. Responsive to receiving an input that selects the sticker, the interactive sticker system may present a menu element that includes content related to the location. For example, in some embodiments, the interactive sticker system may identify one or more client devices within a threshold distance of the location of interest, and may present identifies associated with the one or more client devices within the menu element.

Responsive to receiving a selection of the sticker, the interactive sticker system accesses location data at the client device in order to determine a location of the client device. Responsive to determining that the client device is within a threshold distance of the location that corresponds with the sticker, the interactive sticker system may present content related to the location within a menu element.

In some embodiments, the interactive sticker may include an identification of an event, wherein the event comprises a location and a time. Responsive to receiving a selection of the sticker, the interactive sticker system may present a menu element that comprises a display of the location and time of the event, along with one or more selectable options. A user of the client device may thereby provide an input selecting an option from among the one or more selectable options in order to add the event to a calendar associated with a user profile of the user.

<FIG> is a block diagram showing an example messaging system <NUM> for exchanging data (e.g., messages and associated content) over a network. The messaging system <NUM> includes one or more client device <NUM> which host a number of applications including a messaging 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).

Accordingly, each 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 messaging client applications <NUM>, and between a 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).

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 a 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>. In some embodiments, this data includes, message content, client device information, geolocation information, media annotation and overlays, message content persistence conditions, social network information, and live event information, as examples. In other embodiments, other data is used. Data exchanges within the messaging system <NUM> are invoked and controlled through functions available via GUIs of the messaging client application <NUM>.

Turning now specifically to the messaging server system <NUM>, an Application Program Interface (API) server <NUM> 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 Application Program Interface (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 Application Program Interface (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 Application Program Interface (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., images or video) from a messaging client application <NUM> to the messaging server application <NUM>, and for possible access by another messaging client application <NUM>. the setting of a collection of media data (e.g., story), the retrieval of a list of friends of a user of a client device <NUM>, the retrieval of such collections, the retrieval of messages and content, the adding and deletion of friends to a social graph, the location of friends within a social graph, opening and 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 an interactive sticker system <NUM>. The interactive sticker system <NUM> is configured to generate and cause display of interactive stickers within media content displayed at a client device <NUM>, according to certain example embodiments. Further details of the Interactive sticker system <NUM> can be found in <FIG> below.

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 messaging client application <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>.

The social network system <NUM> supports various social networking functions 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 <NUM> 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.

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>.

<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, collection of messages (e.g., a collection of media), or graphical element, 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 (e.g., a filter, lens) 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, as well as animated facial models. An example of a visual effect includes color overlaying. The audio and visual content or the visual effects can be applied to a media content item (e.g., a photo or video) at the client device <NUM>. For example, the media overlay including text that can be overlaid on top of a photograph generated 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 block diagram illustrating components of the interactive sticker system <NUM> that configure the interactive sticker system <NUM> to perform operations to generate and cause display of an interactive sticker at a client device <NUM>, according to certain example embodiments.

The interactive sticker system <NUM> is shown as including a display module <NUM>, an input module <NUM>, and a menu module <NUM>, all configured to communicate with each other (e.g., via a bus, shared memory, or a switch). Any one or more of these modules may be implemented using one or more processors <NUM> (e.g., by configuring such one or more processors to perform functions described for that module) and hence may include one or more of the processors <NUM>. In certain embodiments, the interactive sticker system <NUM> may include or have access to the database <NUM>, wherein the database <NUM> may comprise a collection of media content indexed based on user attributes and astrological signs.

Any one or more of the modules described may be implemented using hardware alone (e.g., one or more of the processors <NUM> of a machine) or a combination of hardware and software. For example, any module described of the interactive sticker system <NUM> may physically include an arrangement of one or more of the processors <NUM> (e.g., a subset of or among the one or more processors of the machine) configured to perform the operations described herein for that module. As another example, any module of the interactive sticker system <NUM> may include software, hardware, or both, that configure an arrangement of one or more processors <NUM> (e.g., among the one or more processors of the machine) to perform the operations described herein for that module. Accordingly, different modules of the interactive sticker system <NUM> may include and configure different arrangements of such processors <NUM> or a single arrangement of such processors <NUM> at different points in time. Moreover, any two or more modules of die interactive sticker system <NUM> may be combined into a single module, and the functions described herein for a single module may be subdivided among multiple modules. Furthermore, according to various example embodiments, modules described herein as being implemented within a single machine, database, or device may be distributed across multiple machines, databases, or devices.

<FIG> is a flowchart depicting a method <NUM> presenting a menu element based on an input that selects an interactive sticker, according to certain example embodiments. Operations of the method <NUM> may be performed by the modules described above with respect to <FIG>. As shown in <FIG>, the method <NUM> includes one or more operations <NUM>, <NUM>, <NUM>, and <NUM>.

At operation <NUM>, the display module <NUM> generates and causes display of media at a client device <NUM>. For example, the media may include contents of a message received at the client device <NUM>, wherein the media from the message includes a display of an icon at a position upon the media. According to certain example embodiments, the icon may include an interactive sticker, as discussed above, wherein a position and attributes of the interactive sticker within the media may be defined based on a user input. Attributes of the interactive sticker may include graphical properties of the interactive sticker, as well as interactive features of the interactive sticker.

At operation <NUM>, the input module <NUM> receives an input at the client device <NUM>, wherein the input selects the icon. The input comprises input attributes, wherein the input attributes include an input duration and, in some embodiments, an input pressure. For example, a user of the client device <NUM> may provide a tactile input at a position upon a display of the client device <NUM> which corresponds with the position of the icon within the media.

At operation <NUM>, the menu module <NUM> generates a menu element that comprises a set of menu options responsive to the input, and based on attributes of the icon, input attributes of the input, and in some embodiments user attributes of a user associated with the client device <NUM>. At operation <NUM>, the menu module <NUM> causes display of a presentation of the menu element at a position within the presentation of the media at the client device <NUM>. Illustrative examples of menu elements are depicted in <FIG> and <FIG>, such as the menu element <NUM> depicted in <FIG>, and the menu element <NUM> depicted in <FIG>.

<FIG> is a flowchart depicting a method <NUM> of presenting a menu element based on an input that selects an interactive sticker, according to certain example embodiments. Operations of the method <NUM> may be performed by the modules described above with respect to <FIG>. As shown in <FIG>, the method <NUM> includes one or more operations <NUM>, and <NUM>, that may be performed as a part (i.e., a subroutine) of operations <NUM> and <NUM> of the method <NUM>.

At operation <NUM>, responsive to the input module <NUM> receiving the input that selects the icon (i.e., the interactive sticker), the menu module <NUM> generates a set of menu options based on user data associated with the user profile of the client device <NUM>. For example, the user data may include a set of user connections of the user, user preferences (i.e., language preferences), user affinities (likes and follows), as well as user demographics data.

According to certain example embodiments, the menu module <NUM> may access a database <NUM>, wherein the database <NUM> comprises a collection of menu options, wherein each menu option among the set of menu options may correspond with user data. For example, a first set of menu options may correspond with a first user attribute, while a second set of menu options may correspond with a second user attribute.

In some embodiments, the set of menu options may be presented based on user data indicating a relationship between a first user (i.e., a user of the client device <NUM>), and an account, such as an account of a second user, or location identified by the icon. For example, the icon may include a display of an identifier of an account, such as a user account or an account that corresponds with a location of interest (i.e., a business account). Responsive to receiving the input that selects the icon, the menu module <NUM> accesses user data associated with the client device <NUM> in order to determine a relationship between the user and the account identified by the icon. The relationship may include a bidirectional relationship (i.e., a first user and a second user are network connections), the first user follows or has expressed an affinity toward the account, or that the first user has visited the location, or is currently at the location identified by the account.

At operation <NUM>, the display module <NUM> causes display of a presentation of the menu element within the presentation of the media at the client device <NUM>, wherein the menu element includes the set of menu options generated by the menu module <NUM> based on the user data associated with the client device <NUM>. Illustrative examples of menu elements are depicted in <FIG> and <FIG>, such as the menu element <NUM> depicted in <FIG>, and the menu element <NUM> depicted in <FIG>.

For example, as seen in the menu element <NUM> depicted in the interface diagram <NUM> of <FIG>, the menu element <NUM> may comprise a display of a user action which may be performed by a user of the client device <NUM>, wherein the user action may have been selected based on a relationship between the user of the client device <NUM> and the user account identified by the interactive sticker <NUM>.

<FIG> is a flowchart depicting a method <NUM> of presenting a menu element based on an input, according to certain example embodiments. Operations of the method <NUM> may be performed by the modules described above with respect to <FIG>. As shown in <FIG>, the method <NUM> includes one or more operations <NUM>, <NUM>, <NUM> and <NUM>, and may be performed as a part of operations <NUM> and <NUM> of the method <NUM>.

At operation <NUM>, the menu module <NUM> accesses location data at the client device <NUM>, wherein the location data identifies a current location of the client device <NUM>. In some embodiments, the menu module <NUM> may access the location data responsive to detecting the display of the media that includes the presentation of the icon (i.e., the interactive sticker) at the client device <NUM>. The menu module <NUM> accesses the location data responsive to the input module <NUM> receiving the input that selects the icon at the client device <NUM>.

At operation <NUM>, the menu module <NUM> determines that the location data from the client device <NUM> identifies a location associated with the icon. The icon comprises an identifier that identifies a location of interest.

At operation <NUM>, the menu module <NUM> selects a set of menu options from a collection of menu options based on the location data from the client device identifying the location associated with the icon. For example, in such embodiments, the set of menu options may only be presented to users that are at a particular location that corresponds with the icon. At operation <NUM>, the menu module <NUM> generates the menu element based on the selected set of menu options.

<FIG> is a flowchart depicting a method <NUM> of presenting a menu element based on an input, according to certain example embodiments. Operations of the method <NUM> may be performed by the modules described above with respect to <FIG>. As shown in <FIG>, the method <NUM> includes one or more operations <NUM>, <NUM>, and <NUM>, and may be performed as a part of operations <NUM> and <NUM> of the method <NUM>.

At operation <NUM>, as in operation <NUM> of the method <NUM>, the input module <NUM> receives an input that selects an icon (i.e., an interactive sticker) from a presentation of media at a client device <NUM> (i.e., a first client device).

At operation <NUM>, responsive to receiving the input that selects the icon, the input module <NUM> identifies a second client device within a threshold distance of a location associated with the icon. For example, in certain embodiments, the second client device <NUM> may correspond with a second user account which may be linked to a first user account associated with the first client device <NUM> (i.e., as a social network connection). For example, the input module <NUM> may identify client devices associated with network connections of the first user account.

At operation <NUM>, the menu module <NUM> generates a menu element that includes an identifier associated with the second client device <NUM>. For example, the menu element may include a display of a map image, wherein an identifier associated with the second client device <NUM> is presented at a position within the map image based on a location of the second client device <NUM>, as seen in the menu element <NUM> depicted in the interface diagram <NUM> of <FIG>.

<FIG> is an interface diagram <NUM> depicting a GUI that includes a presentation of one or more interactive stickers (<NUM>, <NUM>, <NUM>, <NUM>, and <NUM>), according to certain example embodiments.

As seen in the interface diagram <NUM>, the interactive stickers may include a display of an identifier that identifies an account, a media category, or a location. For example, the interactive stickers <NUM> and <NUM> comprises a display of an identifier (i.e., #quarantine, #sendmeurcatz) which identifies a media category. Similarly, the interactive sticker <NUM> comprises a display of a user identifier that identifies a user account (i.e., @yamill).

The interactive stickers <NUM> and <NUM> comprise a display of identifiers that identify a location or event. For example, the interactive sticker <NUM> comprises a display of an event identifier (i.e., "Billic Eilish @ the shrine), wherein the event identifier includes a location identifier and a time and date. The interactive sticker <NUM> comprises a display of an identifier that identifies a location of interest (i.e., Birmingham international airport).

<FIG> is an interface flow diagram <NUM> depicting interfaces presented by the interactive sticker system <NUM> at a client device <NUM>, according to certain example embodiments. As seen in the diagram <NUM>, an interface <NUM> may include a display of media (i.e., an image) that includes a presentation of an interactive sticker <NUM>. According to certain example embodiments, the interactive sticker <NUM> may include a display of an identifier, such as a user identifier that references a user account.

According to certain embodiments, a user of a client device <NUM> may provide the input <NUM> that selects the interactive sticker <NUM>. As discussed in the method <NUM>, responsive to receiving the input that selects the interactive sticker <NUM>, the interactive sticker system <NUM> may present the interface <NUM>, wherein the interface <NUM> includes a display of a menu element <NUM>, wherein one or more menu options of the menu element <NUM> are selected based on one or more of attributes of the input <NUM>. user data associated with a user of the client device <NUM>, as well as contextual factors that include a current location of the client device <NUM>, and a time of day.

<FIG> is an interface flow diagram <NUM> depicting interfaces presented by the interactive sticker system <NUM> at a client device <NUM>, according to certain example embodiments. As seen in the diagram <NUM>. an interface <NUM> may include a display of media (i.e., an image) that includes a presentation of an interactive sticker <NUM>. According to certain example embodiments, the interactive sticker <NUM> may include a display of an identifier, such as an identifier that identifies a location of interest or an account associated with a business.

According to certain embodiments, a user of a client device <NUM> may provide the input <NUM> that selects the interactive sticker <NUM>. As discussed in the method <NUM>, responsive to receiving the input that selects the interactive sticker <NUM>, the interactive sticker system <NUM> may present the interface <NUM>, wherein the interface <NUM> includes a display of a menu element <NUM>, wherein one or more menu options of the menu element <NUM> are selected based on one or more of attributes of the input <NUM>, user data associated with a user of the client device <NUM>, as well as contextual factors that include a current location of the client device <NUM>. a time of day. and client devices that may be within a threshold distance of the location identified by the identifier from the interactive sticker <NUM>.

For example, as discussed in the method <NUM> described in <FIG>, one or more user identifiers, such as the user identifier <NUM>. associated with client devices <NUM> which are within a threshold distance of the location associated with the interactive sticker <NUM>, or in some embodiments, within a threshold distance of the client device <NUM>, may be presented within the menu element <NUM>.

<FIG> is a block diagram illustrating an example software architecture <NUM>, which may be used in conjunction with various hardware architectures herein described. <FIG> is a non-limiting example of a software architecture and it will be appreciated that many other architectures may be implemented to facilitate the functionality described herein. The software architecture <NUM> may execute on hardware such as machine <NUM> of <FIG> that includes, among other things, processors <NUM>, memory <NUM>, and I/O components <NUM>. A representative hardware layer <NUM> is illustrated and can represent, for example, the machine <NUM> of <FIG>. The representative hardware layer <NUM> includes a processing unit <NUM> having associated executable instructions <NUM>. Executable instructions <NUM> represent the executable instructions of the software architecture <NUM>, including implementation of the methods, components and so forth described herein. The hardware layer <NUM> also includes memory and/or storage modules memory/storage <NUM>, which also have executable instructions <NUM>. The hardware layer <NUM> may also comprise other hardware <NUM>.

In the example architecture of <FIG>, the software architecture <NUM> may be conceptualized as a stack of layers where each layer provides particular functionality. For example, the software architecture <NUM> may include layers such as an operating system <NUM>, libraries <NUM>, applications <NUM> and a presentation layer <NUM>. Operationally, the applications <NUM> and/or other components within the layers may invoke application programming interface (API) API calls <NUM> through the software stack and receive a response as in response to the API calls <NUM>. The layers illustrated are representative in nature and not all software architectures have all layers. For example, some mobile or special purpose operating systems may not provide a frameworks/middleware <NUM>, while others may provide such a layer. Other software architectures may include additional or different layers.

The operating system <NUM> may manage hardware resources and provide common services. The operating system <NUM> may include, for example, a kernel <NUM>, services <NUM> and drivers <NUM>. The kernel <NUM> may act as an abstraction layer between the hardware and the other software layers. For example, the kernel <NUM> may be responsible for memory management, processor management (e.g., scheduling), component management, networking, security settings, and so on. The drivers <NUM> are responsible for controlling or interfacing with the underlying hardware. For instance, the drivers <NUM> include display drivers, camera drivers, Bluetooth® 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 depending on the hardware configuration.

The libraries <NUM> provide a common infrastructure that is used by the applications <NUM> and/or other components and/or layers. The libraries <NUM> provide functionality that allows other software components to perform tasks in an easier fashion than to interface directly with the underlying operating system <NUM> functionality (e.g., kernel <NUM>, services <NUM> and/or drivers <NUM>). The libraries <NUM> may include system libraries <NUM> (e.g., C standard library) that may provide functions such as memory allocation functions, string manipulation functions, mathematical functions, and the like. In addition, the libraries <NUM> may include API libraries <NUM> such as media libraries (e.g., libraries to support presentation and manipulation of various media format such as MPREG4. <NUM>, MP3, AAC, AMR, JPG, PNG), graphics libraries (e.g., an OpenGL framework that may be used to render 2D and 3D in a graphic content on a display), database libraries (e.g., SQLite that may provide various relational database functions), web libraries (e.g., WebKit that may provide web browsing functionality), and the like. The libraries <NUM> may also include a wide variety of other libraries <NUM> to provide many other APIs to the applications <NUM> and other software components/modules.

The frameworks/middleware <NUM> (also sometimes referred to as middleware) provide a higher-level common infrastructure that may be used by the applications <NUM> and/or other software components/modules. For example, the frameworks/middleware <NUM> may provide various graphic user interface (GUI) functions, high-level resource management, high-level location services, and so forth. The frameworks/middleware <NUM> may provide a broad spectrum of other APIs that may be utilized by the applications <NUM> and/or other software components/modules, some of which may be specific to a particular operating system <NUM> or platform.

The applications <NUM> include built-in applications <NUM> and/or third-party applications <NUM>. Examples of representative built-in applications <NUM> may include, but are not limited to, a contacts application, a browser application, a book reader application, a location application, a media application, a messaging application, and/or a game application. Third-party applications <NUM> may include an application developed using the ANDROID™ or IOS™ software development kit (SDK) by an entity other than the vendor of the particular platform, and may be mobile software running on a mobile operating system such as IOST™, ANDROID™. WINDOWS® Phone, or other mobile operating systems. The third-party applications <NUM> may invoke the API calls <NUM> provided by the mobile operating system (such as operating system <NUM>) to facilitate functionality described herein.

The applications <NUM> may use built in operating system functions (e.g., kernel <NUM>, services <NUM> and/or drivers <NUM>), libraries <NUM>, and frameworks/middleware <NUM> to create user interfaces to interact with users of the system. Alternatively, or additionally, in some systems interactions with a user may occur through a presentation layer, such as presentation layer <NUM>. In these systems, the application/component "logic" can be separated from the aspects of the application/component that interact with a user.

<FIG> is a block diagram illustrating components of a machine <NUM>, according to some example embodiments, able to read instructions from a machine-readable medium (e.g., a machine-readable storage medium) and perform any one or more of the methodologies discussed herein. Specifically, <FIG> shows a diagrammatic representation of the machine <NUM> in the example form of a computer system, 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. the instructions <NUM> may be used to implement modules or components 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. In alternative embodiments, the machine <NUM> operates 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 personal digital assistant (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 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 memory/storage <NUM>, and I/O components <NUM>, which may be configured to communicate with each other such as via a bus <NUM>. The memory/storage <NUM> may include a memory <NUM>, such as a main memory, or other memory storage, and a storage unit <NUM>, both accessible to the processors <NUM> such as via the bus <NUM>. The storage unit <NUM> and memory <NUM> store the instructions <NUM> embodying any one or more of the methodologies or functions described herein. The instructions <NUM> may also reside, completely or partially, within the memory <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>. Accordingly, the memory <NUM>, the storage unit <NUM>, and the memory of processors <NUM> are examples of machine-readable media.

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 <NUM> will depend on the type of machine. For example, portable machines such as mobile phones will likely 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>. The I/O components <NUM> are grouped according to functionality merely for simplifying the following discussion and the grouping is in no way limiting. 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 other 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), and the like.

In further example embodiments, the I/O components <NUM> may include biometric components <NUM>, motion components <NUM>. environmental environment components <NUM>, or position components <NUM> among a wide array of other components. For example, the biometric components <NUM> may 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> may include acceleration sensor components (e.g., accelerometer), gravitation sensor components, rotation sensor components (e.g., gyroscope), and so forth. The environment components <NUM> may include, for example, illumination sensor components (e.g.. photometer), temperature sensor components (e.g.. one or more thermometer 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> may include location sensor components (e.g., a Global Position system (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> may include communication components <NUM> operable to couple the machine <NUM> to a network <NUM> or devices <NUM> via coupling <NUM> and coupling <NUM> respectively. For example, the communication components <NUM> may include a network interface component or other suitable device to interface with the network <NUM>. In further examples, 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 Universal Serial Bus (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, multi-dimensional bar codes such as Quick Response (QR) code. Aztec code. Data Matrix, Dataglyph, MaxiCode, PDF417, Ultra Code. UCC RSS-2D bar code, and other optical codes), or acoustic detection components (e.g., microphones to identify tagged audio signals). In addition, a variety of information may be derived via the communication components <NUM>, such as, location via Internet Protocol (IP) geo-location, location via Wi-Fi® signal triangulation, location via detecting a NFC beacon signal that may indicate a particular location, and so forth.

"CARRIER SIGNAL" in this context refers to any intangible medium that is capable of storing, encoding, or carrying instructions for execution by the machine, and includes digital or analog communications signals or other intangible medium to facilitate communication of such instructions. Instructions may be transmitted or received over the network using a transmission medium via a network interface device and using any one of a number of well-known transfer protocols.

"CLIENT DEVICE" in this context refers to any machine that interfaces to a communications network to obtain resources from one or more server systems or other client devices. A client device may be, but is not limited to, a mobile phone, desktop computer, laptop, portable digital assistants (PDAs), smart phones, tablets, ultra books, netbooks, laptops, multi-processor systems, microprocessor-based or programmable consumer electronics, game consoles, set-top boxes, or any other communication device that a user may use to access a network.

"COMMUNICATIONS NETWORK" in this context refers to one or more portions of a network that may be an ad hoc network, an intranet, an extranet, a virtual private network (VPN), a local area network (LAN), a wireless LAN (WLAN), a wide area network (WAN), a wireless WAN (WWAN), a metropolitan area network (MAN), the Internet, a portion of the Internet, a portion of the Public Switched Telephone Network (PSTN), a plain old telephone service (POTS) network, a cellular telephone network, a wireless network, a Wi-Fi® network. another type of network, or a combination of two or more such networks. For example, a network or a portion of a network may include a wireless or cellular network and the coupling may be a Code Division Multiple Access (CDMA) connection, a Global System for Mobile communications (GSM) connection, or other type of cellular or wireless coupling. In this example, the coupling may implement any of a variety of types of data transfer technology, such as Single Carrier Radio Transmission Technology (1xRTT), Evolution-Data Optimized (EVDO) technology, General Packet Radio Service (GPRS) technology, Enhanced Data rates for GSM Evolution (EDGE) technology, third Generation Partnership Project (3GPP) including <NUM>. fourth generation wireless (<NUM>) networks. Universal Mobile Telecommunications System (UMTS), High Speed Packet Access (HSPA), Worldwide Interoperability for Microwave Access (WiMAX), Long Term Evolution (LTE) standard, others defined by various standard setting organizations. other long range protocols, or other data transfer technology.

"EMPHEMERAL MESSAGE" in this context 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.

"MACHINE-READABLE MEDIUM" in this context refers to a component, device or other tangible media able to store instructions and data temporarily or permanently and may include, but is not be limited to, random-access memory (RAM), read-only memory (ROM), buffer memory, flash memory, optical media, magnetic media, cache memory, other types of storage (e.g., Erasable Programmable Read-Only Memory (EEPROM)) and/or any suitable combination thereof. The term "machine-readable medium" should be taken to include a single medium or multiple media (e.g., a centralized or distributed database, or associated caches and servers) able to store instructions. The term "machine-readable medium" shall also be taken to include any medium, or combination of multiple media, that is capable of storing instructions (e.g.. code) for execution by a machine, such that the instructions, when executed by one or more processors of the machine, cause the machine to perform any one or more of the methodologies described herein. Accordingly, a "machine-readable medium" refers to a single storage apparatus or device, as well as "cloud-based" storage systems or storage networks that include multiple storage apparatus or devices. The term "machine-readable medium" excludes signals per se.

"COMPONENT" in this context refers to a device, physical entity or logic having boundaries defined by function or subroutine calls, branch points, application program interfaces (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 Application Program Interface (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.

"PROCESSOR" in this context 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.

"TIMESTAMP" in this context refers to a sequence of characters or encoded information identifying when a certain event occurred, for example giving date and time of day. sometimes accurate to a small fraction of a second.

"LIFT" in this context is a measure of the performance of a targeted model at predicting or classifying cases as having an enhanced response (with respect to a population as a whole), measured against a random choice targeting model.

"PHONEME ALIGNMENT" in this context, a phoneme is a unit of speech that differentiates one word from another. One phoneme may consist of a sequence of closure, burst, and aspiration events; or, a dipthong may transition from a back vowel to a front vowel. A speech signal may therefore be described not only by what phonemes it contains, but also the locations of the phonemes. Phoneme alignment may therefore be described as a "time-alignment" of phonemes in a waveform, in order to determine an appropriate sequence and location of each phoneme in a speech signal.

"AUDIO-TO-VISUAL CONVERSION" in this context refers to the conversion of audible speech signals into visible speech, wherein the visible speech may include a mouth shape representative of the audible speech signal.

"TIME DELAYED NEURAL NETWORK (TDNN)" in this context, a TDNN is an artificial neural network architecture whose primary purpose is to work on sequential data. An example would be converting continuous audio into a stream of classified phoneme labels for speech recognition.

Claim 1:
A method comprising:
causing (<NUM>) display of a presentation of media at a client device, the presentation of the media including a display of an icon within the presentation of the media, wherein the icon comprises an identifier that identifies a location of interest;
receiving (<NUM>) an input that selects the icon from the client device, the input comprising an input attribute;
accessing (<NUM>) location data from the client device in response to the input that selects the icon, the location data identifying a location within a threshold distance of the location of interest;
selecting (<NUM>) one or more menu options from among a collection of menu options based on the input duration of the input and the location data from the client device;
generating (<NUM>, <NUM>) a menu element based on the icon and the input attribute in response to the input that selects the icon, the menu element including the one or more menu options and a display of a map image that includes the location of interest and an indication of the location of the client device; and
presenting (<NUM>) the menu element at a position within the presentation of the media at the client device.