Media Content Detection and Management

Abstract

The method and system include the steps of receiving an indication of a user interaction within a predetermined period; determining that the user interaction is a context-triggering event based on a plurality of triggering conditions; identifying a media content item associated with the context-triggering event; generating a first user interface including a user-selectable element representing a content transmission proposal; and generating a second user interface including a media content item and a plurality of user-selectable entity icons in response to detecting a user selection of the user-selectable element.

Description

Technology Field

[0001] Claim of priority

[0002] This application claims the benefit of priority to U.S. Provisional Application No. 63 / 085,877 filed September 30, 2020 and U.S. Patent Application No. 17 / 087,145 filed November 2, 2020, the full text of each of which is incorporated herein by reference. Background Technology

[0003] Electronic messaging, particularly instant messaging, continues to gain popularity worldwide. Users can instantly and rapidly share electronic media content items, including text, electronic images, audio, and video, with one another. As the number of users on social networking systems increases, the personal networks that each user follows are also growing. Brief explanation of the drawing

[0004] In drawings that are not necessarily drawn in a fixed proportion, the same reference numbers may describe similar components in different drawings. To facilitate the identification of a discussion of any specific element or action, the top digit or numbers of a reference number indicate the drawing number where the element is first introduced. Some embodiments are illustrated in the accompanying drawings as examples rather than limitations. FIG. 1 is a schematic representation of a networked environment in which the present disclosure may be arranged, according to some examples. Figure 2 is a schematic representation of a messaging system according to some examples that has functionality on both the client side and the server side. Figure 3 is a schematic representation of a data structure as maintained in a database, according to some examples. Figure 4 is a schematic representation of a message according to some examples. Figure 5 is a flowchart of an access-limiting process according to some examples. FIG. 6 illustrates a process for detecting context-related media content items and generating corresponding content transmission proposals according to one embodiment. FIG. 7 illustrates a user interface displayed on a client device according to one embodiment. FIG. 8 illustrates a user interface displayed on a client device according to one embodiment. FIG. 9 illustrates a user interface displayed on a client device according to one embodiment. FIG. 10 illustrates a content display area displayed on a client device according to one embodiment. FIG. 11 illustrates a user interface displayed on a client device according to one embodiment. FIG. 12 is a schematic representation of a machine in the form of a computer system in which a set of instructions can be executed to enable the machine to perform one or more of the methodologies discussed in this specification, according to some examples. FIG. 13 is a block diagram illustrating a software architecture in which examples can be implemented. Figure 14 is a schematic representation of a processing environment according to some examples. Specific details for implementing the invention

[0005] In messaging systems, users are connected to various other users with different types of relationships. For example, a user may be socially connected to groups of users who are not known to the user, as well as close friends, colleagues, and acquaintances. To maintain user engagement with a social networking system, it is crucial that the system possesses the ability to detect context-related content associated with user activity on a client device and to propose sending content for the detected context-related content. In this way, users can share media content items with others in the most time-efficient manner. Existing social networking systems face the challenge of detecting context-related content associated with user activity on a client device and proposing sending media content for the detected content.

[0006] Embodiments of the present disclosure improve the functionality of electronic messaging software and systems by identifying context-triggering events based on user activity or interaction on a client device within a predetermined time period and generating content transmission proposals by triggering the display of user-selectable elements representing media content items associated with the triggering events. When a user selection of proposed media content is detected, the messaging system generates a content transmission user interface comprising media content items and a plurality of user-selectable entity icons, each of which represents a recipient user. In one embodiment, when a user selection of proposed media content is detected, the messaging system generates a collection sharing user interface to invite users to share media content items from a collection of content collectively generated by a plurality of users. The collection of content is managed and curated by a collection management system.

[0007] In one embodiment, the messaging system receives indications of user interaction or activity on an associated client device. The messaging system determines whether the user interaction is a context-triggering event and whether its occurrence occurs within a predetermined time period. The predetermined period ensures that the user activity occurs within a time frame short enough to reflect the current user activity so that a content transmission proposal is made. The messaging system identifies a media content item associated with the context-triggering event. The context-triggering event may be the playback of video or audio, or the capture of an image, video, or audio, or the capture of a hyperlink from the clipboard. For example, the user may perform activities on a mobile phone such as taking a photo, streaming a video or song from a third-party application, or copying and pasting a hyperlink from a browser. The messaging system may detect these activities and determine whether any of the activities are context-triggering events based on a plurality of triggering conditions.

[0008] In one embodiment, the determination of a context-triggering event is based on a plurality of triggering conditions determined based on content transmission history data or user preference data. Specifically, regarding the determination of triggering conditions based on content transmission history data, the messaging system may track user interactions with past content transmission proposals within a time period and determine the type of media content item associated with proposals that are frequently selected and transmitted by a specific user. Thus, the determination of triggering conditions is primarily based on user behavior. Regarding the determination of triggering conditions based on user preference data, a specific user may configure triggering conditions by selecting the type of media content item to be contextually detected for the purpose of generating content transmission proposals based on their interactions with the client device, through a user preference user interface generated by the messaging system. For example, the user may select an image captured through the front or rear camera, or both cameras, as the sole type of media content item to be included in the content transmission proposal. In one embodiment, the triggering condition represents the current contextual state of the device or user profile inferred through usage history.

[0009] In one embodiment, the messaging system generates a first user interface comprising a user-selectable element that represents a content transmission proposal on a client device. The content transmission proposal includes a media content item. Depending on the type of the detected media content item, the representation of the content transmission proposal may be displayed as an icon of a silhouette of a captured image, a hyperlink, or a logo of a music service provider of a captured playback of a song. In response to detecting a user selection of the user-selectable element, the messaging system generates a second user interface comprising a media content item and a plurality of user-selectable entity icons within a content display area, each of which represents a receiving user.

[0010] Networked computing environment

[0011] FIG. 1 is a block diagram illustrating an exemplary messaging system (100) for exchanging data (e.g., messages and associated content) over a network. The messaging system (100) includes multiple instances of client devices (102), each of which hosts multiple applications including messaging clients (104). Each messaging client (104) is coupled to communicate with other instances of messaging clients (104) and messaging server systems (108) over a network (106) (e.g., the Internet).

[0012] A messaging client (104) can communicate and exchange data with another messaging client (104) and a messaging server system (108) through a network (106). The data exchanged between messaging clients (104) and between a messaging client (104) and a messaging server system (108) includes functions (e.g., commands to invoke functions) as well as payload data (e.g., text, audio, video, or other multimedia data).

[0013] The messaging server system (108) provides server-side functionality to a specific messaging client (104) via the network (106). Although specific functions of the messaging system (100) are described herein as being performed by the messaging client (104) or by the messaging server system (108), the location of specific functions within the messaging client (104) or the messaging server system (108) may be a design choice. For example, it may be technically desirable to initially place specific technologies and functions within the messaging server system (108), but later migrate these technologies and functions to the messaging client (104) when the client device (102) has sufficient processing capacity.

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

[0015] Now, referring specifically to the messaging server system (108), an application program interface (API) server (110) is coupled to an application server (112) to provide a programmatic interface. The application server (112) is communicably coupled to a database server (118), which facilitates access to a database (120) that stores data associated with messages processed by the application server (112). Similarly, a web server (124) is coupled to the application servers (112) and provides web-based interfaces to the application servers (112). To this end, the web server (124) processes incoming network requests via HTTP (Hypertext Transfer Protocol) and some other related protocols.

[0016] An API (Application Program Interface) server (110) receives and transmits message data (e.g., commands and message payloads) between a client device (102) and application servers (112). Specifically, the application program interface (API) server (110) provides a set of interfaces (e.g., routines and protocols) that can be called or queried by a messaging client (104) to activate the functionality of the application servers (112). The application program interface (API) server (110) exposes various functions supported by the application servers (112), including account registration, login functionality, transmission of messages through the application servers (112) from a specific messaging client (104) to another messaging client (104), transmission of media files (e.g., images or videos) from the messaging client (104) to the messaging server (114), and settings of a collection of media data (e.g., stories) for possible access by another messaging client (104), searching of a list of friends of the user of the client device (102), searching of such collections, searching of messages and content, adding and deleting entities (e.g., friends) to an entity graph (e.g., social graph), locating friends within the social graph, and opening application events (e.g., related to the messaging client (104)).

[0017] Application servers (112) host a number of server applications and subsystems, including, for example, a messaging server (114), an image processing server (116), and a social network server (122). The messaging server (114) implements a number of message processing techniques and functions, particularly those related to the aggregation and other processing of content (e.g., text and multimedia content) contained in messages received from multiple instances of the messaging client (104). As described in more detail, 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 to the messaging client (104). Other processor and memory-intensive data processing may also be performed on the server side by the messaging server (114), taking into account the hardware requirements for such processing.

[0018] The application servers (112) also include an image processing server (116) dedicated to performing various image processing operations with respect to images or videos in the payload of a message typically transmitted from or received from the messaging server (114).

[0019] The social network server (122) supports various social networking functions and services and makes these functions and services available to the messaging server (114). To this end, the social network server (122) maintains and accesses an entity graph (306) (shown in FIG. 3) within the database (120). Examples of functions and services supported by the social network server (122) include the identification of other users of the messaging system (100) with whom a specific user has relationships or is "following," and also the identification of other entities and the interests of the specific user.

[0020] System Architecture

[0021] FIG. 2 is a block diagram illustrating additional details regarding a messaging system (100) according to some examples. Specifically, the messaging system (100) is illustrated as including a messaging client (104) and application servers (112). The messaging system (100) implements a number of subsystems supported by the messaging client (104) on the client side and by the application servers (112) on the server side. These subsystems include, for example, a short-term timer system (202), a collection management system (204), an augmentation system (206), a map system (208), and a game system (210).

[0022] The short-term timer system (202) is responsible for enforcing temporary or time-limited access to content by the messaging client (104) and the messaging server (114). The short-term timer system (202) includes a plurality of timers that selectively allow access (e.g., for presentation and display) to the message and associated content through the messaging client (104) based on duration and display parameters associated with the message, or a collection of messages (e.g., stories), or a media content item (e.g., text messages, hyperlinks, images, videos, and audio) corresponding to a content transmission proposal. In one embodiment, the receiving user may have time-limited access to the media content item received in a private or group messaging user interface. Further details regarding the operation of the short-term timer system (202) are provided below.

[0023] The collection management system (204) is responsible for managing sets or collections of media (e.g., collections of text, image, video, and audio data). Collections of content (e.g., messages including images, video, text, and audio) can be organized to become "event galleries" or "event stories." These collections may be available for a specified period, such as the duration of the event to which the content is related. For example, content about a music concert may be available as a 'story' for the duration of that music concert. The collection management system (204) may also be responsible for publishing an icon that provides notification of the existence of a specific collection in the user interface of the messaging client (104). Furthermore, the collection management system (204) includes a curation interface (212) that allows a collection manager to manage and curate a collection of specific content. For example, the curation interface (212) enables an event organizer to curate a collection of content related to a specific event (e.g., removing inappropriate content or duplicate messages). Additionally, the collection management system (204) automatically curates a collection of content using machine vision (or image recognition technology) and content rules. In certain examples, a reward may be paid to the user for including user-generated content in the collection. In these cases, the collection management system (204) operates to automatically pay these users for using their content.

[0024] The augmentation system (206) provides various functions that enable a user to augment media content associated with a message (e.g., annotate or modify or edit in other ways). For example, the augmentation system (206) provides functions related to the creation and publication of media overlays for messages processed by the messaging system (100). The augmentation system (206) operatively supplies media overlays or augmentations (e.g., image filters) to the messaging client (104) based on the geolocation of the client device (102). In another example, the augmentation system (206) operatively supplies media overlays to the messaging client (104) based on other information, such as the social network information of the user of the client device (102). Media overlays may include audio and visual content and visual effects. Examples of audio and visual content include photos, text, logos, animations, and sound effects. Examples of visual effects include color overlaying. Audio and visual content or visual effects may be applied to a media content item (e.g., a photo) on the client device (102). For example, the media overlay may include text or an image that can be overlaid on a photo taken by the client device (102). In another example, the media overlay may include a location identification overlay (e.g., Venice Beach), the name of a live event, or a merchant name overlay (e.g., Beach Coffee House). In another example, the augmentation system (206) uses the geolocation of the client device (102) to identify a media overlay containing the merchant name at the geolocation of the client device (102). The media overlay may include other indicia associated with the merchant.Media overlays are stored in a database (120) and can be accessed through a database server (118).

[0025] In some examples, the augmentation system (206) provides a user-based publication platform that enables users to select a geolocation on a map and upload content associated with the selected geolocation. Users can also specify situations in which a particular media overlay should be provided to other users. The augmentation system (206) creates a media overlay that includes the uploaded content and associates the uploaded content with the selected geolocation.

[0026] In other examples, the augmentation system (206) provides a merchant-based publication platform that enables merchants to select a specific media overlay associated with a geolocation through a bidding process. For example, the augmentation system (206) associates the media overlay of the highest bidder with a corresponding geolocation for a predefined amount of time.

[0027] The map system (208) provides various geographic location functions and supports the presentation of map-based media content and messages by the messaging client (104). For example, the map system (208) triggers the display of user icons or avatars (e.g., stored in profile data (308)) on the map to display the current or past locations of the user's "friends" as well as media content created by these friends (e.g., collections of messages including photos and videos) within the context of the map. For example, a message posted by a user to the messaging system (100) from a specific geographic location can be displayed to the specific user's "friends" on the map interface of the messaging client (104) within the context of the map at that specific location. Furthermore, the user can share their location and status information with other users of the messaging system (100) through the messaging client (104) (e.g., using an appropriate status avatar), and this location and status information is similarly displayed to selected users within the context of the map interface of the messaging client (104).

[0028] The game system (210) provides various gaming functions within the context of the messaging client (104). The messaging client (104) provides a game interface that provides a list of available games that can be launched by a user within the context of the messaging client (104) and played with other users of the messaging system (100). The messaging system (100) also enables a specific user to invite other users to participate in the play of a specific game by issuing invitations to other users from the messaging client (104). The messaging client (104) also supports both voice and text messaging (e.g., chats) within the context of gameplay, provides a leaderboard for games, and supports the provision of in-game rewards (e.g., coins and items).

[0029] The content detection and transmission system (214) is responsible for identifying a context-triggering event based on user activity or interaction on a client device within a predetermined period and generating a content transmission proposal by triggering the display of a user-selectable element corresponding to a media content item associated with the triggering event. When activation of a user-selectable element (e.g., icon (702) in FIG. 7 or icon (802 or 804) in FIG. 8) is detected, the system (214) generates a content transmission user interface (e.g., user interface (900) in FIG. 9) including a media content item and a plurality of user-selectable entity icons, each of which represents a receiving user. Specifically, when an indication of user activity on an associated client device is received, the content detection and transmission system (214) determines whether the user interaction is a context-triggering event and whether the occurrence of the event is within a predetermined time period. The system (214) identifies a media content item associated with the context-triggering event.

[0030] In one embodiment, the determination of a context-triggering event is based on a plurality of triggering conditions determined based on content transmission history data or user preference data. Specifically, regarding the determination of triggering conditions based on content transmission history data, the system (214) tracks user interactions with past content transmission proposals within a certain period and determines the type of media content item associated with proposals that are frequently selected and transmitted by a specific user. Thus, the determination of triggering conditions is primarily based on user behavior. Regarding the determination of triggering conditions based on user preference data, a specific user may configure triggering conditions by selecting the type of media content item to be contextually detected for the purpose of generating content transmission proposals based on their interactions with the client device (102) through a user preference user interface generated by the content detection and transmission system (214). For example, the user may select a captured image as the only type of media content item to be detected and included in the content transmission proposal.

[0031] In one embodiment, the content detection and transmission system (214) generates a first user interface including a user-selectable element representing a content transmission proposal on a client device. The representation of the content transmission proposal refers to a corresponding media content item. For example, depending on the type of the detected media content item, the representation of the content transmission proposal may be displayed as an icon of a silhouette of a captured image, a hyperlink, or a logo of a music service provider of a song. In response to detecting the activation of the user-selectable element, the system (214) generates a second user interface (e.g., user interface (900)) including a corresponding media content item within a content display area and a plurality of user-selectable entity icons, each representing a receiving user.

[0032] Data Architecture

[0033] FIG. 3 is a schematic diagram illustrating data structures (300) that may be stored in a database (120) of a messaging server system (108) according to specific examples. Although the contents of the database (120) are depicted as including multiple tables, it will be recognized that data may be stored in data structures of other types (e.g., as an object-oriented database).

[0034] The database (120) contains message data stored in the message table (302). For any specific message, this message data includes at least message sender data, message recipient (or receiver) data, and payload. Additional details regarding information that may be included in the message and may be included in the message data stored in the message table (302) are described below with reference to FIG. 4.

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

[0036] The entity graph (306) stores information regarding relationships and associations between entities. Such relationships may be based on interests or activities, for example, social, professional (for example, work in a general corporation or organization).

[0037] Profile data (308) stores multiple types of profile data for a specific entity. Profile data (308) may be optionally used and presented to other users of the messaging system (100) based on privacy settings specified by the specific entity. If the entity is a person, profile data (308) includes, for example, a username, phone number, address, settings (e.g., notification and privacy settings), as well as a user-selected avatar representation (or a collection of such avatar representations). A specific user may then optionally include one or more of these avatar representations within the content of messages communicated through the messaging system (100) and on map interfaces displayed to other users by messaging clients (104). A collection of avatar representations may include "state avatars" that present a graphic representation of a state or activity that the user may select to communicate at a specific time.

[0038] If the entity is a group, the profile data (308) for the group may similarly include one or more avatar representations associated with the group, in addition to the group name, members, and various settings (e.g., notifications) for the related group.

[0039] The database (120) also stores augmentation data, such as overlays or filters, in the augmentation table (310). The augmentation data is associated with and applied to videos (data about which is stored in the video table (314)) and images (data about which is stored in the image table (316)).

[0040] In one example, the filters are overlays that are displayed overlaid on an image or video during presentation to the receiving user. The filters may be various types of filters, including user-selected filters from a set of filters presented to the sending user by the messaging client (104) when the sending user is composing a message. Other types of filters include geolocation filters (also known as geo-filters) that may be presented to the sending user based on geolocation. For example, geolocation filters specific to a neighborhood or a specific location may be presented within the user interface by the messaging client (104) based on geolocation information determined by the Global Positioning System (GPS) unit of the client device (102).

[0041] Another type of filter is a data filter that may be optionally presented to the sending user by the messaging client (104) based on other inputs or information collected by the client device (102) during the message generation process. Examples of data filters include the current temperature at a specific location, the current speed at which the sending user is moving, the battery life of the client device (102), or the current time.

[0042] Other augmented data that may be stored in the image table (316) includes augmented reality content items (e.g., corresponding to applying lenses or augmented reality experiences). Augmented reality content items may be real-time special effects and sounds that can be added to an image or video.

[0043] As described above, augmented data includes similar terms referring to augmented reality content items, overlays, image transformations, AR images, and modifications that can be applied to image data (e.g., videos or images). This includes real-time modifications that modify an image, such as when the image is captured using device sensors (e.g., one or more cameras) of the client device (102) and then displayed on the screen of the client device (102) along with modifications. This also includes modifications to stored content, such as video clips within a gallery, that can be modified. For example, on a client device (102) accessing multiple augmented reality content items, the user may use a single video clip along with multiple augmented reality content items to determine how different augmented reality content items modify the stored clip. For example, multiple augmented reality content items applying different pseudorandom movement models may be applied to the same content by selecting different augmented reality content items for the content. Similarly, real-time video capture can be used with the illustrated modifications to show how video images currently being captured by the sensors of the client device (102) will modify the captured data. This data may simply be displayed on the screen and not stored in memory, or the content captured by the device sensors may be written to and stored in memory with or without modification (or both). In some systems, a preview feature may show how different augmented reality content items will appear simultaneously in different windows within the display. This may, for example, allow multiple windows with different pseudo-random animations to be displayed simultaneously on the display.

[0044] Accordingly, data and various systems using augmented reality content items or other such transformation systems to modify content using this data may involve the detection of objects (e.g., faces, hands, bodies, cats, dogs, surfaces, objects, etc.), the tracking of these objects as they move out of, enter, and around video frames, and the modification or transformation of these objects when they are tracked. In various embodiments, different methods may be used to achieve these transformations. Some examples may involve generating a 3D mesh model of an object or objects, and using transformations of the model and animated textures within the video to achieve the transformation. In other examples, tracking points on an object may be used to place an image or texture (which may be 2D or 3D) at the tracked location. In yet other examples, neural network analysis of video frames may be used to place images, models, or textures on the content (e.g., an image or video frame). Therefore, augmented reality content items refer to images, models, and textures used to generate transformations in the content, as well as all additional modeling and analysis information required to achieve these transformations through object detection, tracking, and placement.

[0045] Real-time video processing can be performed with any type of video data (e.g., video streams, video files, etc.) stored in the memory of any type of computerized system. For example, a user can load video files and store them in the device's memory, or generate video streams using the device's sensors. Additionally, any objects, such as human faces and parts of the human body, animals, or inanimate objects like chairs, cars, or other objects, can be processed using computer animation models.

[0046] In some examples, when a specific modification is selected along with the content to be transformed, the elements to be transformed are identified by the computing device and subsequently detected and tracked if they exist in the video frames. The elements of the object are modified according to the request for modification, thereby transforming the frames of the video stream. The transformation of the frames of the video stream can be performed by different methods for different types of transformations. For example, for frame transformations that primarily refer to changing the shapes of the elements of an object, characteristic points for each element of the object are calculated (e.g., using the Active Shape Model (ASM) or other known methods). Then, a mesh based on the characteristic points is generated for each of at least one element of the object. This mesh is used in the next stage of tracking the elements of the object within the video stream. In the tracking process, the mesh mentioned for each element is aligned with the location of each element. Subsequently, 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 second set of points is generated for each element based on the first set of points and the request for modification. Then, frames of a video stream can be transformed by modifying the elements of an object based on the mesh and the first and second sets of points. In this method, the background of the modified object can also be changed or distorted by tracking and modifying the background.

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

[0048] In some examples of computer animation models for transforming image data using face detection, faces are detected on the image using a specific face detection algorithm (e.g., Viola-Jones). Then, the Active Shape Model (ASM) algorithm is applied to the face region of the image to detect face feature reference points.

[0049] In other cases, other methods and algorithms suitable for face detection may be used. For example, in some embodiments, features are located using landmarks representing distinguishable points present in most of the images under consideration. For face landmarks, for example, the location of the left pupil may be used. If the initial landmark is not identifiable (e.g., a person wearing an eye patch), auxiliary landmarks may be used. These landmark identification procedures may be used for any such objects. In some examples, a set of landmarks forms a feature. Features may be represented as vectors using the coordinates of points within the feature. One feature is aligned with another using a similarity transformation (allowing for translation, scaling, and rotation) that minimizes the average Euclidean distance between feature points. The average feature is the average of the aligned training features.

[0050] In some examples, a search for landmarks from the average shape aligned with the position and size of the face determined by the whole face detector is initiated. Subsequently, this search proposes a tentative shape by adjusting the positions of the shape points through template matching of the image texture around each point, and then repeats the steps of matching the tentative shape to the global shape model until convergence occurs. In some systems, individual template matches are unreliable, and the shape model pools the results of weak template matches to form a stronger whole classifier. The whole search is repeated at each level of the image pyramid from coarse resolution to fine resolution.

[0051] The transformation system can capture an image or video stream on a client device (e.g., client device (102)) and perform complex image manipulations locally on the client device (102) while maintaining an appropriate user experience, computation time, and power consumption. 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, application of graphic elements, and any other appropriate image or video manipulations implemented by a convolutional neural network programmed to be executed efficiently on the client device (102).

[0052] In some examples, a computer animation model for transforming image data may be used by a system capable of capturing a user's image or video stream (e.g., a selfie) using a client device (102) having a neural network that operates as part of a messaging client application (104) operating on the client device (102). A transformation system operating within the messaging client (104) determines the presence of a face in the image or video stream and provides modification icons associated with the computer animation model for transforming image data, or the computer animation model may exist as being associated with the interface described herein. The modification icons include changes that may be the basis for modifying the user's face in the image or video stream as part of a modification operation. When a modification icon is selected, the transformation system initiates a process of transforming the user's image to reflect the selected modification icon (e.g., generating a smiling face for the user). The modified image or video stream may be presented in a graphical user interface displayed on the client device (102) as soon as the image or video stream is captured and a specific modification is selected. The transformation system can generate and apply selected modifications by implementing complex convolutional neural networks on a portion of an image or video stream. That is, a user can capture an image or video stream and, if a modification icon is selected, be presented with the modified result in real-time or near real-time. Furthermore, modifications can be sustained as long as the video stream is being captured and the selected modification icon remains toggled. Machine-taught neural networks can be used to enable these modifications.

[0053] A graphical user interface presenting modifications performed by a transformation system may provide the user with additional interaction options. These options may be based on an interface used to initiate the capture and selection of content from a specific computer animation model (e.g., initiation from a content creator user interface). In various embodiments, modifications may be persistent after the 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 may save it for later viewing or browsing to other areas of the imaging application. If 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 that is modified and displayed within the graphical user interface. In some embodiments, among a group of multiple faces, individual faces may be modified individually, or these modifications may be toggled individually by tapping or selecting an individual face or a series of individual faces displayed within the graphical user interface.

[0054] The story table (312) stores data regarding collections of messages and associated image, video, or audio data that are compiled into collections (e.g., stories or galleries). The creation of a specific collection may be initiated by a specific user (e.g., each user for whom a record is maintained in the entity table (304)). The user may create a 'personal story' in the form of a collection of content created and transmitted / broadcasted by that user. To this end, the user interface of the messaging client (104) may include a user-selectable icon to enable the transmitting user to add specific content to their personal story.

[0055] The collection may also constitute a ‘Live Story,’ which is a collection of content from multiple users generated 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 who have client devices running location services and are at a common location event at a specific time may be presented with an option to contribute content to a specific Live Story, for example, through the user interface of a messaging client (104). A Live Story may be identified to the user by the messaging client (104) based on their location. The final result is a ‘Live Story’ as described in community terms.

[0056] An additional type of content collection that enables a user whose client device (102) is located within a specific geographical location (e.g., a college or university campus) to contribute to a specific collection is known as a “location story.” In some examples, contribution to a location story may require a second degree of authentication to verify whether the end user belongs to a specific organization or other entity (e.g., a student on a university campus).

[0057] As mentioned above, the video table (314) stores video data associated with messages for which records are maintained in the message table (302), in one example. Similarly, the image table (316) stores image data associated with messages for which message data is stored in the entity table (304). The entity table (304) can associate various augmentations from the augmentation table (310) with various images and videos stored in the image table (316) and the video table (314).

[0058] Data communication architecture

[0059] FIG. 4 is a schematic diagram illustrating the structure of a message (400), according to some examples, generated by a messaging client (104) for communication with an additional messaging client (104) or a messaging server (114). The content of a specific message (400), such as the content of a media content item (e.g., a media content item (902, 1002, or 1004)), is used to populate a message table (302) stored in a database (120) accessible by the messaging server (114). Similarly, the content of the message (400) is stored in memory as "in-transit" or "in-flight" data of the client device (102) or application servers (112). The message (400) is illustrated as comprising the following exemplary components:

[0060] · Message identifier (402): A unique identifier that identifies the message (400).

[0061] · Message text payload (404): Text generated by the user through the user interface of the client device (102) and included in the message (400).

[0062] · Message image payload (406): Image data included in the message (400) that is captured by the camera component of the client device (102) or retrieved from the memory component of the client device (102). Image data for the transmitted or received message (400) may be stored in an image table (316).

[0063] · Message video payload (408): Video data captured by the camera component or retrieved from the memory component of the client device (102) and included in the message (400). Video data for the transmitted or received message (400) may be stored in the video table (314).

[0064] · Message audio payload (410): Audio data captured by a microphone or retrieved from a memory component of a client device (102) and included in a message (400).

[0065] · Message augmentation data (412): Augmentation data (e.g., filters, stickers, or other annotations or enhancements) representing augmentations to be applied to the message image payload (406), message video payload (408), or message audio payload (410) of the message (400). Augmentation data for a transmitted or received message (400) may be stored in an augmentation table (310).

[0066] · Message duration parameter (414): A parameter value indicating the amount of time in seconds during which the content of a message (e.g., message image payload (406), message video payload (408), message audio payload (410)) is presented to or made accessible to the user through the messaging client (104).

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

[0068] · Message Story Identifier (418): Identifier values ​​that identify one or more content collections (e.g., "stories" identified in the story table (312)) to which a specific content item within the message image payload (406) of the message (400) is associated. For example, multiple images within the message image payload (406) may each be associated with multiple content collections using identifier values.

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

[0070] · Message sender identifier (422): An identifier representing the user of the client device (102) to which the message (400) was created and the message (400) was sent (e.g., a messaging system identifier, an email address, or a device identifier).

[0071] · Message recipient identifier (424): An identifier representing the user of the client device (102) to which the message (400) is addressed (e.g., a messaging system identifier, an email address, or a device identifier).

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

[0073] Time-based access restriction architecture

[0074] FIG. 5 is a schematic diagram illustrating an access-restriction process (500) in which access to content (e.g., short-term message (502), and associated multimedia payload of data) or a collection of content (e.g., group of short-term messages (504)) may be time-restricted (e.g., short-term).

[0075] A short message (502) is illustrated as being associated with a message duration parameter (506), the value of which determines the amount of time the short message (502) is displayed to the recipient of the short message (502) by the messaging client (104). In one example, depending on the amount of time specified by the sending user using the message duration parameter (506), the recipient may view the short message (502) for up to 10 seconds. In one embodiment, the short message (502) may be a media content item such as the media content item (902, 1002, or 1004) as illustrated in FIGS. 9 and FIGS. 10. The media content item may be a text message, a hyperlink, an image, a video, or audio.

[0076] The message duration parameter (506) and the message recipient identifier (424) are illustrated as inputs to the message timer (512), and the message timer (512) is responsible for determining the amount of time that a short message (502) is shown to a specific recipient identified by the message recipient identifier (424). In particular, the short message (502) will be shown only to the relevant recipient for a period determined by the value of the message duration parameter (506). The message timer (512) is illustrated as providing an output to a more generalized short timer system (202) responsible for the overall timing of the display of content (e.g., the short message (502)) to the recipient.

[0077] A short message (502) is illustrated in FIG. 5 as being included within a short message group (504) (e.g., a collection of messages in a personal story or event story). The short message group (504) has an associated group duration parameter (508), the value of which determines the time duration for which the short message group (504) is presented and accessible to users of the messaging system (100). For example, the group duration parameter (508) may be the duration of a music concert, where the short message group (504) is a collection of content related to that concert. Alternatively, a user (owner user or curator user) may specify a value for the group duration parameter (508) when setting up and creating the short message group (504).

[0078] Additionally, each short message (502) within a short message group (504) has an associated group participation parameter (510), the value of which determines the duration of time the short message (502) is accessible within the context of the short message group (504). Thus, a specific short message group (504) may 'expire' and become inaccessible within the context of the short message group (504) before the short message group (504) itself expires in terms of the group duration parameter (508). The group duration parameter (508), the group participation parameter (510), and the message recipient identifier (424) each provide input to a group timer (514), which first determines whether a specific short message (502) of the short message group (504) will be displayed to a specific recipient user, and if so, for how long. Note that the short-term message group (504) also recognizes the identity of a specific recipient user as a result of the message recipient identifier (424).

[0079] Accordingly, the group timer (514) operatively controls the entire lifespan of the associated short-term message group (504) as well as the individual short-term messages (502) included in the short-term message group (504). In one example, each and all short-term messages (502) within the short-term message group (504) remain visible and accessible for a period specified by the group duration parameter (508). In an additional example, a specific short-term message (502) may expire within the context of the short-term message group (504) based on the group participation parameter (510). Note that the message duration parameter (506) can still determine the duration of time that a specific short-term message (502) is displayed to the receiving user, even within the context of the short-term message group (504). Accordingly, the message duration parameter (506) determines the duration of time that a specific short message (502) is displayed to a receiving user, regardless of whether the receiving user is viewing the short message (502) inside or outside the context of the short message group (504).

[0080] The short-term timer system (202) may also operatively remove a specific short-term message (502) from a short-term message group (504) based on the determination that it has exceeded the associated group participation parameter (510). For example, when a sending user establishes a group participation parameter (510) of 24 hours from a posting, the short-term timer system (202) will remove the associated short-term message (502) from the short-term message group (504) after a specified 24 hours. The short-term timer system (202) also operates to remove the short-term message group (504) when the group participation parameter (510) for each and all short-term messages (502) within the short-term message group (504) has expired, or when the short-term message group (504) itself has expired with respect to the group duration parameter (508).

[0081] In certain use cases, the creator of a specific short-term message group (504) may specify an infinite group duration parameter (508). In this case, the expiration of the group participation parameter (510) for the last remaining short-term message (502) within the short-term message group (504) will determine when the short-term message group (504) itself expires. In this case, a new short-term message (502) added to the short-term message group (504) with a new group participation parameter (510) effectively extends the life of the short-term message group (504) to be equal to the value of the group participation parameter (510).

[0082] In response to the short-term timer system (202) determining that a short-term message group (504) has expired (e.g., is no longer accessible), the short-term timer system (202) communicates with the messaging system (100) (and, for example, specifically the messaging client (104)) to prevent the indication (e.g., an icon) associated with the relevant short-term message group (504) from being displayed within the user interface of the messaging client (104). Similarly, when the short-term timer system (202) determines that the message duration parameter (506) for a specific short-term message (502) has expired, the short-term timer system (202) prevents the messaging client (104) from displaying the indication (e.g., an icon or text identification) associated with the short-term message (502) from being displayed.

[0083] Media Content Detection and Management

[0084] In one embodiment, the content detection and transmission system (214) identifies a context-triggering event based on user activity or interaction on a client device within a predetermined time period and generates a content transmission proposal by triggering the display of a user-selectable element representing a media content item associated with the triggering event. When a user selection of the proposed media content is detected, the content detection and transmission system (214) generates a content transmission user interface including a media content item and a plurality of user-selectable entity icons, each of which represents a receiving user.

[0085] FIG. 6 illustrates a process (600) that detects context-related media content items and generates corresponding content transmission proposals according to one embodiment. The operation of the process (600) may be performed by any number of different systems, such as a messaging server (114) or a messaging client (104) described herein, or by any part thereof, such as a processor included in any of the systems including a content detection and transmission system (214).

[0086] In operation 602, the processor receives indication of user interaction or activity with the associated client device within a predetermined period. User activity may be the capture of an image, the playback of video or audio, or a copied link within the clipboard. The predetermined period may be any time duration, such as seconds or minutes. The predetermined period may be adjusted to ensure that the processor captures current user activity that is relevantly maintained in a timely manner for the generated content transmission proposal. In one embodiment, the capture of a media content item may be a user activity captured by an embedded or external sensor, such as a camera or microphone. Specifically, the capture of a media content item may be a user activity of taking an image or video by the front or rear embedded camera of the client device (102), or by an external camera coupled to the client device (102). The capture of a media content item may also be a user activity of recording audio by the embedded microphone of the client device (102), or by an external microphone coupled to the client device (102).

[0087] In one embodiment, the hyperlink corresponds to media content of a webpage, which is a media content item. The media content item associated with the hyperlink may be displayed as a media content item (1002) in a content display area (904), as illustrated in FIG. 10. The media content item (1002) includes a text indicator comprising a hyperlink (e.g., XYZtimes.com), an avatar representing the media content of the webpage (e.g., a person wearing a mask), and a caption (e.g., a title) of the media content of the webpage.

[0088] In one embodiment, a media content item associated with the playback of video or audio may be displayed as a media content item (1004) in a content display area (904), as illustrated in FIG. 10. The media content item (1004) includes a hyperlink (e.g., Listen at XYZ Media) that can guide the user to a third-party video or audio streaming platform. The media content item (1004) also includes a caption for the video or audio. The caption may include the name of the song (e.g., Bingo Bingo) and the artist (e.g., Dr. K). The media content item (1004) further includes an avatar of the video or audio, such as a silhouette of the song's album cover.

[0089] In one embodiment, a media content item associated with a captured image may be displayed as a media content item (902), such as the silhouette of the captured image, in a content display area (904), as shown in FIG. 9.

[0090] In operation 604, the processor determines that a user interaction is a context-triggering event based on a plurality of triggering conditions. The triggering conditions represent the current context state of a device or user profile inferred from usage history. The context state of a specific user may be modified over time based on user behavior data accumulated for that specific user. In one embodiment, the triggering conditions may be determined based on content transmission history data. Specifically, the processor may track user interactions with previously generated content transmission proposals within a time period and determine the type of media content item associated with proposals that are frequently selected and transmitted by a specific user. For example, if a specific user transmits captured images more frequently than capture hyperlinks in content transmission proposals, the processor may generate a content transmission proposal whenever the user captures an image, provided that the capture occurs within a predetermined time period. As another example, if a specific user mostly ignores content transmission proposals associated with video playback, the processor may decrease the frequency of such content sharing proposals every two times upon detection of such triggering events. Thus, the determination of the triggering conditions is primarily based on user behavior.

[0091] In one embodiment, the triggering condition may also be determined based on user preference data. Specifically, a specific user may configure the triggering condition by selecting the type of media content item to be contextually detected for the purpose of generating a content transmission proposal based on their interaction with the client device, through a user preference user interface generated by the processor. For example, the user may select only captured images as the type of media content item to be detected and included in the content transmission proposal. In one embodiment, the captured images may include images captured through the front camera of the client device and images captured through the rear camera of the client device. The user may select only images captured by the front camera (e.g., selfies) that can be contextually detected for generating a content transmission proposal.

[0092] In operation 606, the processor identifies a media content item associated with a context-triggering event. In one embodiment, the context-triggering event may be the playback of video or audio, the capture of an image, video or audio, or the capture of a hyperlink within the clipboard. The clipboard may include a data structure stored in storage within the messaging system (100) along with metadata identifying the associated media content item and the user profile. The processor determines the context-triggering event based on the context-triggering condition.

[0093] In operation 608, the processor generates a first user interface that includes a user-selectable element representing a content transmission proposal. For example, as illustrated in FIGS. 7 and 8, the first user interface may be a user interface (700, 810, or 820). The user-selectable element may be an icon (702, 802, or 804). The icon (702) represents a content transmission proposal associated with a captured image, and the icon (702) includes a silhouette of the captured image. The icon (702) may also include a text indicator such as "Send Screenshot" (not shown).

[0094] The icon (802) represents a content transmission suggestion associated with the playback of video or audio, and the icon (802) may include a logo of a service provider of video or audio, such as a music streaming service provider or a video streaming service provider. The icon (802) may also include a text indicator such as "Send Bingo Bingo" (not shown), because "Bingo Bingo" represents the name of the song being played. The icon (804) represents a content transmission suggestion associated with a hyperlink captured from a webpage. The icon (804) may include a hyperlink icon as shown, a logo of the web service provider of the captured hyperlink, and a text indicator such as "Send link to clipboard" (not shown).

[0095] In operation 610, when a user selection of a user-selectable element (e.g., an icon (702, 802, or 804)) is detected, the processor generates a second user interface, such as a user interface (900), as illustrated in FIG. 9. The second user interface includes a media content item in a content display area, such as a content display area (904), and also includes a plurality of user-selectable entity icons, such as entity icons (906 and 908). Each entity icon corresponds to a connected user in the entity graph (306). An entity icon, such as entity icon (908), includes the connected user's username (e.g., Grace), avatar, and current state (e.g., a smiling face icon indicating a happy state). The user can input a media content item, such as a text message, into the content display area (904).

[0096] In one embodiment, when the activation of the content transmission button (910) is detected, the processor can transmit a media content item, such as that shown in the content display area (904), to the client device (102) of the receiving user.

[0097] In one embodiment, the processor may generate a user-selectable element corresponding to a content transmission proposal, such as an element (1102) as shown in FIG. 11. The element (1102) includes a text indicator such as "Add to my collection" to inform the user that, upon activation of the element (1102), the processor may generate a user interface (1120) for including a media content item in a collection of content collectively generated by multiple users. The collection of content may be managed and curated by a collection management system (204). Thus, activating a user-selectable element corresponding to a content transmission proposal may generate a content transmission user interface such as the user interface (900) of FIG. 9, or a collection sharing user interface such as the user interface (1120) of FIG. 11.

[0098] FIG. 7 illustrates a user interface displayed on a client device according to one embodiment. The user interface (700) includes a user interface element (704) and a user interface icon (702). The icon (702) represents a content transmission proposal associated with a captured image, and the icon (702) includes a silhouette of the captured image. In one embodiment, activation of the user interface element (704) may cause the processor to generate and display the user interface (900), except that the content display area (902) is left without inserting a media content item. In one embodiment, activation of the user interface icon (702) may cause the processor to generate and display the user interface (900) and automatically fill the content display area (904) with a media content item associated with a corresponding content transmission proposal.

[0099] FIG. 8 illustrates a user interface displayed on a client device according to one embodiment. The user interface (810) includes a user interface element (704) and a user interface icon (802). The icon (802) represents a content transmission offer associated with the playback of video or audio, and the icon (802) may include a logo of a video or audio service provider, such as a music streaming service provider or a video streaming service provider. The user interface (820) includes a user interface element (704) and a user interface icon (804). The icon (804) represents a content transmission offer associated with a hyperlink captured from a webpage.

[0100] FIG. 9 illustrates a user interface (900) displayed on a client device according to one embodiment. The user interface (900) (e.g., a second user interface) includes a content display area (904), a plurality of user-selectable entity icons such as entity icons (906 and 908), and a content transmission button (910). The content display area (904) includes media content items such as a media content item (902) associated with a corresponding content transmission proposal. When activation of a user-selectable element (702, 802, or 804) is received, the processor generates and displays the user interface (900) and automatically fills the content display area with the media content item associated with the content transmission proposal.

[0101] FIG. 10 illustrates a content display area (904) displayed on a client device according to one embodiment. When a context-triggering event is the capture of a hyperlink from the clipboard, and when a user-selectable element (804) is activated, the processor may automatically populate the content display area (904) with a media content item (1002). The media content item (1002) includes a text indicator comprising a hyperlink (e.g., XYZtimes.com), an avatar (1008) representing the media content of the webpage (e.g., a person wearing a mask), and a caption (e.g., a title) of the media content of the webpage.

[0102] In one embodiment, when a context-triggering event is the playback of video or audio, upon activation of a user-selectable element (802), the processor may automatically populate a content display area (904) with a media content item (1004). The media content item (1004) includes a hyperlink (e.g., Listen at XYZ Media) that can guide the user to a third-party video or audio streaming platform. The media content item (1004) also includes a caption for the video or audio. The caption may be the name of a song (e.g., Bingo Bingo) and an artist (e.g., Dr. K). The media content item (1004) further includes an avatar (1006) of the video or audio, such as a silhouette of the song's album cover.

[0103] FIG. 11 illustrates a user interface displayed on a client device according to one embodiment. A processor may generate a user interface (1100) that includes a user-selectable element such as an element (1102). The element (1102) includes a text indicator such as "Add to my collection" to inform the user that, upon activation of the element (1102), the processor may generate a user interface (1120) for including a media content item in a collection of content collectively generated by a plurality of users. The collection of content is managed and curated by a collection management system (204).

[0104] Machine Architecture

[0105] FIG. 12 is a schematic representation of a machine (1200) on which instructions (1208) (e.g., software, program, application, applet, app, or other executable code) can be executed to cause the machine (1200) to perform one or more of the methodologies discussed herein. For example, instructions (1208) can cause the machine (1200) to perform one or more of the methods described herein. Instructions (1208) convert a general unprogrammed machine (1200) into a specific machine (1200) programmed to perform the described and illustrated functions in the described manner. The machine (1200) may operate as a standalone device or may be coupled to other machines (e.g., networked). In a networked deployment, the machine (1200) may operate as a server machine or a client machine in a server-client network environment, or as a peer machine in a peer-to-peer (or distributed) network environment. The machine (1200) may include, but is not limited to, a server computer, a client computer, a personal computer (PC), a tablet computer, a laptop computer, a netbook, a set-top box (STB), a personal digital assistant (PDA), an entertainment media system, a cellular phone, a smartphone, a mobile device, a wearable device (e.g., a smartwatch), a smart home device (e.g., a smart device), other smart devices, a web appliance, a network router, a network switch, a network bridge, or any machine capable of executing commands (1208) that specify actions to be taken by the machine (1200) sequentially or otherwise.Additionally, although only a single machine (1200) is exemplified, the term “machine” may also be taken to include a collection of machines that execute instructions (1208) individually or jointly to perform one or more of the methodologies discussed herein. For example, the machine (1200) may include a client device (102) or one of a plurality of server devices forming part of a messaging server system (108). In some examples, the machine (1200) may also include both client and server systems, where specific operations of a specific method or algorithm are performed on the server side and specific operations of a specific method or algorithm are performed on the client side.

[0106] The machine (1200) may include processors (1202), memory (1204), and input / output I / O components (1238) that can be programmed to communicate with each other via a bus (1240). In one example, the processors (1202) (e.g., a CPU (Central Processing Unit), a RISC (Reduced Instruction Set Computing) processor, a CISC (Complex Instruction Set Computing) processor, a GPU (Graphics Processing Unit), a DSP (Digital Signal Processor), an ASIC (Application Specific Integrated Circuit), an RFIC (Radio-Frequency Integrated Circuit), other processors, or any suitable combination thereof) may include, for example, a processor (1206) and a processor (1210) that execute instructions (1208). The term “processor” is intended to include multi-core processors that may include two or more independent processors (sometimes referred to as “cores”) capable of executing instructions simultaneously. FIG. 12 illustrates multiple processors (1202), but the machine (1200) may include a single processor having a single core, a single processor having multiple cores (e.g., a multi-core processor), multiple processors having a single core, multiple processors having multiple cores, or any combination thereof.

[0107] The memory (1204) includes a main memory (1212), a static memory (1214), and a storage unit (1216), both of which are accessible to the processors (1202) via a bus (1240). The main memory (1204), the static memory (1214), and the storage unit (1216) store instructions (1208) that implement one or more of the methodologies or functions described herein. The instructions (1208) may also reside, wholly or partially, during the execution by the machine (1200), in the main memory (1212), in the static memory (1214), in the machine-readable medium (1218) within the storage unit (1216), in at least one of the processors (1202) (e.g., in the processor's cache memory), or any suitable combination thereof.

[0108] The I / O components (1238) may include a wide variety of components for receiving inputs, providing outputs, generating outputs, transmitting information, exchanging information, capturing measurements, etc. The specific I / O components (1238) included in a particular machine will depend on the type of machine. For example, portable machines such as mobile phones may include touch input devices or other such input mechanisms, while headless server machines are unlikely to include such touch input devices. It will be acknowledged that the I / O components (1238) may include many other components not shown in FIG. 12. In various examples, the I / O components (1238) may include user output components (1224) and user input components (1226). User output components (1224) may include visual components (e.g., displays such as a plasma display panel (PDP), light-emitting diode (LED) display, liquid crystal display (LCD), projector, or cathode ray tube (CRT)), acoustic components (e.g., speakers), haptic components (e.g., vibration motors, resistance mechanisms), other signal generators, etc. User input components (1226) may include alphanumeric input components (e.g., keyboard, touch screen programmed to receive alphanumeric input, photo-optical keyboard, or other alphanumeric input components), point-based input components (e.g., mouse, touchpad, trackball, joystick, motion sensor, or other pointing device), haptic input components (e.g., physical buttons, touch screens providing the location and force of touches or touch gestures, or other haptic input components), audio input components (e.g., microphones), and similar ones.

[0109] In additional examples, I / O components (1238) may include, among various other components, biometric components (1228), motion components (1230), environment components (1232), or position components (1234). For example, biometric components (1228) include components for detecting expressions (e.g., hand expressions, facial expressions, voice expressions, body gestures, or eye tracking), measuring biosignals (e.g., blood pressure, heart rate, body temperature, sweat, or brain waves), identifying a person (e.g., voice identification, retinal identification, face identification, fingerprint identification, or EEG-based identification), and performing similar tasks. Motion components (1230) include acceleration sensor components (e.g., accelerometers), gravity sensor components, and rotation sensor components (e.g., gyroscopes).

[0110] Environmental components (1232) may include, for example, one or more cameras (having still image / photo and video capabilities), light sensor components (e.g., photometers), temperature sensor components (e.g., one or more thermometers for detecting ambient temperature), humidity sensor components, pressure sensor components (e.g., barometers), acoustic sensor components (e.g., one or more microphones for detecting background noise), proximity sensor components (e.g., infrared sensors for detecting nearby objects), gas sensors (e.g., gas detection sensors for detecting concentrations of hazardous gases for safety or measuring contaminants in the atmosphere), or other components capable of providing indications, measurements, or signals corresponding to the surrounding physical environment.

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

[0112] Additionally, the camera system of the client device (102) may include dual rear cameras (e.g., a depth-sensing camera as well as a main camera) or even triple, quadruple, or quintuple rear camera configurations on the front and rear sides of the client device (102). These multiple camera systems may include, for example, a wide camera, an ultra-wide camera, a telephoto camera, a macro camera, and a depth sensor.

[0113] The position components (1234) include position sensor components (e.g., GPS receiver components), altitude sensor components (e.g., altimeters or barometers that detect atmospheric pressure from which altitude can be derived), orientation sensor components (e.g., magnetometers), and similar ones.

[0114] Communication can be implemented using a wide variety of technologies. The I / O components (1238) further include communication components (1236) operable to connect the machine (1200) to a network (1220) or devices (1222) through respective combinations or connections. For example, the communication components (1236) may include a network interface component, or other suitable devices for interfacing with the network (1220). In additional examples, the communication components (1236) 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 that provide communication through other aspects. The devices (1222) may be other machines or any various peripheral devices (e.g., peripheral devices connected via USB).

[0115] Furthermore, the communication components (1236) may include components capable of detecting identifiers or operable to detect identifiers. For example, the communication components (1236) may include Radio Frequency Identification (RFID) tag reader components, NFC smart tag detection components, optical reader components (e.g., optical sensors for detecting one-dimensional barcodes such as Universal Product Code (UPC) barcodes, multi-dimensional barcodes such as Quick Response (QR) codes, Aztec codes, Data Matrix, Dataglyph, MaxiCode, PDF417, Ultra Code, UCC RSS-2D barcodes, and other optical codes), or acoustic detection components (e.g., microphones for identifying tagged audio signals). In addition, various information, such as location via Internet Protocol (IP) geolocation, location via Wi-Fi® signal triangulation, and location via detection of NFC beacon signals that can indicate a specific location, can be derived through the communication components (1236).

[0116] Various memories (e.g., main memory (1212), static memory (1214), and memory of the processors (1202)) and storage unit (1216) may store one or more sets of instructions and data structures (e.g., software) that implement or are used by any one or more of the methodologies or functions described herein. These instructions (e.g., instructions (1208)) enable various operations to implement the disclosed examples when executed by the processors (1202).

[0117] Commands (1208) may be transmitted or received over a network (1220) using a transmission medium through a network interface device (e.g., a network interface component included in the communication components (1236)) and using any one of several well-known transmission protocols (e.g., HTTP (hypertext transfer protocol)). Similarly, commands (1208) may be transmitted or received using a transmission medium through a connection to the devices (1222) (e.g., peer-to-peer connection).

[0118] Software Architecture

[0119] FIG. 13 is a block diagram (1300) illustrating a software architecture (1304) that may be installed in one or more of the devices described herein. The software architecture (1304) is supported by hardware such as a machine (1302) that includes processors (1320), memory (1326), and I / O components (1338). In this example, the software architecture (1304) may be conceptualized as a stack of layers, each layer providing a specific function. The software architecture (1304) includes layers such as an operating system (1312), libraries (1310), frameworks (1308), and applications (1306). Operationally, applications (1306) initiate API calls (1350) through the software stack and receive messages (1352) in response to the API calls (1350).

[0120] The operating system (1312) manages hardware resources and provides common services. The operating system (1312) includes, for example, a kernel (1314), services (1316), and drivers (1322). The kernel (1314) acts as an abstraction layer between the hardware and other software layers. For example, the kernel (1314) provides memory management, processor management (e.g., scheduling), component management, networking, and security settings, among other functions. Services (1316) may provide other common services for other software layers. Drivers (1322) are responsible for controlling or interfacing with the underlying hardware. For example, drivers (1322) may include display drivers, camera drivers, BLUETOOTH® or BLUETOOTH® Low Energy drivers, flash memory drivers, serial communication drivers (e.g., USB drivers), WI-FI® drivers, audio drivers, power management drivers, etc.

[0121] Libraries (1310) provide a common low-level infrastructure used by applications (1306). Libraries (1310) may include system libraries (1318) (e.g., the C standard library) that provide functions such as memory allocation functions, string manipulation functions, mathematical functions, etc. Additionally, the libraries (1310) may include API libraries (1324) such as media libraries (e.g., libraries that support the presentation and manipulation of various media formats such as MPEG4 (Moving Picture Experts Group-4), Advanced Video Coding (H.264 or AVC), MP3 (Moving Picture Experts Group Layer-3), AAC (Advanced Audio Coding), AMR (Adaptive Multi-Rate) audio codecs, Joint Photographic Experts Group (JPEG or JPG), or PNG (Portable Network Graphics), graphics libraries (e.g., OpenGL frameworks used to render graphic content on a display in two dimensions (2D) and three dimensions (3D)), database libraries (e.g., SQLite providing various relational database functions), web libraries (e.g., WebKit providing web browsing functionality). The libraries (1310) may also include a wide variety of other libraries (1328) that provide many different APIs to applications (1306).

[0122] Frameworks (1308) provide common high-level infrastructure used by applications (1306). For example, frameworks (1308) provide various graphical user interface (GUI) functions, high-level resource management, and high-level location services. Frameworks (1308) may provide a wide range of other APIs that can be used by applications (1306), some of which may be specific to a particular operating system or platform.

[0123] In one example, applications (1306) may include a wide range of other applications such as a home application (1336), a contacts application (1330), a browser application (1332), a book reader application (1334), a location application (1342), a media application (1344), a messaging application (1346), a game application (1348), and a third-party application (1340). Applications (1306) are programs that execute functions defined in programs. Various programming languages ​​may be used to create one or more of the applications (1306), which are structured in various ways, such as object-oriented programming languages ​​(e.g., Objective-C, Java, or C++) or procedural programming languages ​​(e.g., C or assembly language). In a specific example, a third-party application (1340) (e.g., ANDROID by an entity other than the vendor of a specific platform) TM or iOS TM Applications developed using a Software Development Kit (SDK) are iOS TM , ANDROID TMIt may be mobile software running on a mobile operating system such as WINDOWS® Phone or other mobile operating systems. In this example, a third-party application (1340) may initiate API calls (1350) provided by the operating system (1312) to facilitate the functions described herein.

[0124] Processing components

[0125] Now, referring to FIG. 14, a schematic representation of a processing environment (1400) including a processor (1402), a processor (1406), and a processor (1408) (e.g., a GPU, a CPU, or any combination thereof) is shown.

[0126] The processor (1402) is coupled to the power supply (1404) and is illustrated as comprising modules (permanently programmed or temporarily instantiated), namely a content transmission component (1410) and an R / W component (1412). The content detection and transmission component (1410) operatively identifies a context-triggering event based on user activity or interaction on a client device within a predetermined time period and generates a content transmission proposal by triggering the display of a user-selectable element representing a media content item associated with the triggering event. The R / W component (1412) operatively manages data reading and writing during a normal computer processing cycle to support the various functions described above. As illustrated, the processor (1402) is communicably coupled to both the processor (1406) and the processor (1408).

[0127] Glossary

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

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

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

[0131] "Component" refers to a device, physical entity, or logic having boundaries defined by function or subroutine calls, branch points, APIs, or other techniques that provide the division or modularization of specific processing or control functions. Components may be combined with other components through their interfaces to execute machine processes. A component may be a packaged functional hardware unit designed to be used with other components and part of a program that performs a specific function among the related functions. Components may constitute either software components (e.g., code implemented on a machine-readable medium) or hardware components. "Hardware component" is a type unit capable of performing specific operations and may be programmed or arranged in a specific physical manner. In various exemplary embodiments, one or more computer systems (e.g., standalone computer systems, client computer systems, or server computer systems) or one or more hardware components of a computer system (e.g., processors or groups of processors) may be programmed by software (e.g., an application or part of an application) as hardware components that operate to perform specific operations as described herein. Hardware components may also be implemented mechanically, electronically, or any suitable combination thereof. For example, a hardware component may include dedicated circuits or logic permanently programmed to perform specific 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 circuits that are temporarily programmed by software to perform specific operations.For example, a hardware component may include software executed by a general-purpose processor or another programmable processor. Once programmed by such software, the hardware components become specific machines (or specific components of a machine) uniquely customized to perform the programmed functions and are no longer general-purpose processors. It will be recognized that the decision to implement a hardware component mechanically, in a dedicated, permanently programmed circuit, or in a temporarily programmed circuit (e.g., programmed by software) may be driven by cost and time considerations. Accordingly, the phrase "hardware component" (or "hardware-implemented component") should be understood to encompass type entities, that is, entities that are physically configured, permanently configured (e.g., hardwired), or temporarily configured (e.g., programmed) to operate in a particular manner or perform the specific operations described herein. When considering embodiments where hardware components are temporarily programmed (e.g., programmed), it is not necessary for each hardware component to be configured or instantiated at any single time instance. For example, in the case where a general-purpose processor is programmed by software to have a hardware component become a special-purpose processor, the general-purpose processor may be programmed as different special-purpose processors at different times (e.g., including different hardware components). Thus, the software configures a specific processor or processors to configure a specific hardware component at one time instance and a different hardware component at a different time instance. Hardware components can provide information to other hardware components and receive information from them.Accordingly, the described hardware components may be considered to be coupled communicably. In cases where multiple hardware components exist simultaneously, communication may be achieved through the transmission of signals between or between two or more of the hardware components (e.g., via appropriate circuits and buses). In embodiments where multiple hardware components are programmed or instantiated at different times, communication between such hardware components may be achieved, for example, through the storage and retrieval of information within memory structures accessible to multiple hardware components. For example, one hardware component may perform an operation and store the output of that operation in a memory device coupled communicably to it. Subsequently, additional hardware components may access the memory device to retrieve and process the stored output. Hardware components may also initiate communication with input or output devices and manipulate resources (e.g., collections of information). Various operations of the exemplary methods described herein may be performed at least partially by one or more processors that are temporarily programmed (e.g., by software) or permanently programmed to perform the relevant operations. Whether configured temporarily or permanently programmed, 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 implemented at least partially by a processor, and specific processors or processors are examples of hardware.For example, at least some of the operations of the method may be performed by one or more processors (1406) or components implemented by processors. Furthermore, one or more processors may also operate to support the performance of the relevant operations in a “cloud computing” environment or as “software as a service” (SaaS). For example, at least some of the operations may be performed by a group of computers (as examples of machines including processors), and these operations may be accessible via a network (e.g., the Internet) and through one or more appropriate interfaces (e.g., APIs). The performance of certain operations may not only exist within a single machine but may also be distributed among processors deployed across multiple machines. In some exemplary embodiments, the processors or components implemented by processors may be located in a single geographic location (e.g., a home environment, an office environment, or within a server farm). In other exemplary embodiments, the processors or components implemented by processors may be distributed across multiple geographic locations.

[0132] "Computer-readable storage medium" refers to a machine storage medium. Accordingly, the terms include storage devices / mediums. The terms "machine-readable medium," "computer-readable medium," and "device-readable medium" mean the same thing and may be used interchangeably in this disclosure.

[0133] An "ephemeral message" refers to a message accessible for a time-limited duration. Ephemeral messages can be text, images, videos, etc. The access time for an ephemeral message can be set by the message sender. Alternatively, the access time can be a default setting or a setting specified by the recipient. Regardless of the setting technique, the message is transitory.

[0134] "Machine storage medium" refers to a single or multiple storage devices and media (e.g., centralized or distributed databases, and associated caches and servers) that store executable instructions, routines, and data. Accordingly, the term should be considered to include, but not be limited to, solid-state memories including memory inside or outside processors, and optical and magnetic media. Specific examples of machine storage medium, computer storage medium, and device storage medium include, by example, non-volatile memory including semiconductor memory devices, e.g., EPROM (erasable programmable read-only memory), EEPROM (electrically erasable programmable read-only memory), FPGAs, 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," and "computer storage medium" mean the same thing and may be used interchangeably in this disclosure. The terms "machine storage medium," "computer storage medium," and "device storage medium" specifically exclude carrier waves, modulated data signals, and other such media, at least some of which are included under the term "signal medium."

[0135] "Non-transient computer-readable storage medium" refers to a type of medium capable of storing, encoding, or carrying instructions for execution by a machine.

[0136] "Signal medium" refers to any intangible medium capable of storing, encoding, or carrying instructions for execution by a machine, and includes digital or analog communication signals or other intangible media for facilitating the communication of software or data. The term "signal medium" should be considered to include any form of modulated data signal, carrier wave, etc. The term "modulated data signal" means a signal in which one or more of its characteristics are set or altered in matters such as encoding information within the signal. The terms "transmission medium" and "signal medium" mean the same thing and may be used interchangeably in this disclosure.

Claims

Claim 1 A method comprising: receiving an indication of a user interaction within a predetermined period; determining that the user interaction is a context-triggering event based on a plurality of triggering conditions, wherein the triggering event corresponds to the capture of a hyperlink associated with a media content item; identifying a media content item associated with the context-triggering event; generating a first user interface including a user-selectable element indicating a content transmission proposal; and generating a second user interface in response to detecting a user selection of the user-selectable element, wherein the second user interface includes the media content item and a plurality of user-selectable entity icons. Claim 2 In claim 1, the method wherein the content transmission proposal includes the media content item. Claim 3 A method according to claim 1, further comprising: a step of determining a plurality of triggering conditions based on content transmission history data or user preference data; and a step of determining a context triggering event based on the plurality of triggering conditions. Claim 4 In claim 1, the context triggering event is the playback of a media content item, a method. Claim 5 A method according to claim 1, wherein the context triggering event is the capture of a media content item by a sensor. Claim 6 A method according to claim 1, wherein the context triggering event is the capture of a hyperlink from the clipboard. Claim 7 In claim 6, the method comprises a clipboard having a data structure having metadata that identifies the media content item and the associated user profile. Claim 8 In paragraph 6, the method wherein the hyperlink corresponds to the media content item. Claim 9 In claim 6, the method wherein the second user interface comprises the hyperlink and the avatar of the media content item. Claim 10 A method according to claim 1, further comprising the step of generating a third user interface including a user interface icon corresponding to a proposal to add the media content item to a collection of media content in response to detecting the user selection of the user selectable element. Claim 11 A method according to claim 1, wherein each of the plurality of user-selectable entity icons is associated with a user profile connected in an entity graph. Claim 12 In claim 1, the method wherein the user-selectable element is associated with a text indicator. Claim 13 A system comprising: one or more processors; and a non-transient computer-readable storage medium comprising instructions that cause the one or more processors to perform an operation when executed by the one or more processors, wherein the operation comprises: receiving an indication of a user interaction within a predetermined period; determining that the user interaction is a context-triggering event based on a plurality of triggering conditions—the triggering event corresponds to the capture of a hyperlink associated with a media content item—; identifying a media content item associated with the context-triggering event; generating a first user interface comprising a user-selectable element representing a content transmission proposal; and generating a second user interface in response to detecting a user selection of the user-selectable element—the second user interface comprising the media content item and a plurality of user-selectable entity icons. Claim 14 In Clause 13, the above content transmission proposal is a system including the above media content item. Claim 15 In paragraph 13, the system further performs the operation of one or more processors determining a plurality of triggering conditions based on content transmission history data or user preference data; and the operation of determining a context triggering event based on the plurality of triggering conditions. Claim 16 In Clause 13, the above context-triggering event is the playback of a media content item, a system. Claim 17 In paragraph 13, the above context triggering event is a system in which the capture of a media content item by a sensor. Claim 18 In paragraph 13, the above context-triggering event is a capture of a hyperlink within the clipboard, the system. Claim 19 A system according to claim 13, wherein the one or more processors further perform the operation of generating a third user interface including a user interface icon corresponding to a proposal to add the media content item to a collection of media content in response to detecting the user selection of the user selectable element. Claim 20 A machine-readable non-transient storage medium having instruction data executable by said machine to cause a machine to perform an operation, wherein the operation comprises: receiving an indication of a user interaction within a predetermined period; determining that said user interaction is a context-triggering event based on a plurality of triggering conditions, said triggering event corresponds to the capture of a hyperlink associated with a media content item; identifying a media content item associated with said context-triggering event; generating a first user interface including a user-selectable element indicating a content transmission proposal; and generating a second user interface in response to detecting a user selection of said user-selectable element, said second user interface including said media content item and a plurality of user-selectable entity icons.

Images