Patent ID: 12212885

DETAILED DESCRIPTION

An example interaction system is described that enables the initiation and sharing of augmented reality (AR) experiences, based on stored digital images (e.g., still images or video) between users of the interaction system. The described example augmented reality (AR) technology enables users to share digital content reflecting memories, moments, and other shared experiences using a convenient mechanism that provides an improved person-machine interface. Further, the described example technology deploys automation to automatically detect and present digital content for sharing between users, based on several criteria.

FIG.1is a user interface diagram showing screenshot116and screenshot118of an example camera interface102that may be presented on a client device302(e.g., a mobile phone or other client device) by an interaction client304(e.g., a communications or social networking app) executing on the client device302. The camera interface102operationally displays digital content (e.g., still image or video data) in the example form of a primary image114, as captured by a camera that forms part of or that is coupled to the client device302. For example, where the client device302is a mobile phone, the image data displayed within the camera interface102may be real-time video images captured by a front-facing camera of the mobile phone and streamed to a display of the mobile phone display by the interaction client304within the context of the camera interface102.

The camera interface102also displays a rotatable filter carousel104of filter icons106, the filter icons106being examples of augmentation icons that are presented within the camera interface102for user selection. Each of the filter icons106is associated with a respective image augmentation mechanism (e.g., an image filter) that is invoked by a user selection (e.g., by tapping on the screen of the client device302) of the associated filter icon106. In one example, only the filter icon106displayed the horizontally center position of the carousel is selectable to invoke the associated image augmentation mechanism. A user rotates the filter carousel104by performing a swipe operation, applied to the screen of the client device302in either the left or the right direction, so as to rotate the filter carousel104accordingly. A user is also able to rotate the filter carousel104by selecting an off-center filter icon106, which will rotate the filter carousel104so as to place the selected folder icon in the horizontally centered position, at which the user can type on the centered filter icon106to activate the relevant image augmentation mechanism.

A filter icon106displayed at a position at or adjacent to the horizontal center of the camera interface102is furthermore enlarged relative to other filter icons106to indicate that it is selectable to activate the associated image augmentation mechanism. Further, a title or other descriptive information120associated with the centered filter icon106may be displayed above the filter icon106. In the displayed example screenshot116, the title “friend memories” is displayed above the centered filter icon106as an example of such descriptive information120.

Considering the example of a “friend memories” filter icon106, user selection of this filter icon106within the camera interface102causes activation of an associated “friend memories” filter, as an example of an associated auxiliary image augmentation mechanism. Each auxiliary image augmentation mechanism has an associated auxiliary image selection criterion that is activated responsive to the user selection of the associated filter icon106. For example, the “friend memories” filter, once activated, causes modification of the camera interface102to show a further friend carousel108, an example of which is shown in the screenshot118. The friend carousel108is navigable in the same way as the filter carousel104.

The friend carousel108is populated with user graphical elements in the form of friend icons110. Each friend icon110represents a respective user of an interaction system that is connected or linked to a viewing user (e.g., is a “friend” of the viewing user) and includes a digital, two-dimensional avatar of the relevant user. Responsive to user selection of friend icon110within the friend carousel108, a user identifier for the selected user associated with the selected friend icon110is retrieved. This user identifier is then used to identify digital content, such as an auxiliary image112, related to the selected user. This auxiliary image112is selected from a collection of digital content (e.g., photographs) that are associated with the viewing user of an application (e.g., interaction client304). The collection of digital content is managed by a collection management system416.

The selected auxiliary image112is displayed within the camera interface102, as shown in screenshot118. The selected auxiliary image112is, in some examples, overlaid on a primary image114in order to create a composite data (e.g., comprising the primary image114and the auxiliary image112) that is presented in displayed within the camera interface102. The selected auxiliary image112may also be displayed with relevant metadata122, such as date information reflecting a date on which the auxiliary image112was captured.

In this way, an image augmentation mechanism is presented to a user that automatically identifies other users of an interaction system300to which a viewing user is connected (e.g., friends of the viewing user) and automatically surfaces augmentation data (e.g., one or more auxiliary images112) that can be conveniently shared and used to create a new composite image or collage. The new composite image may, for example, be captured by and stored on a client device302, and furthermore included in a message that is shared with other users.

In a further example, video content is displayed within the camera interface102during a synchronous video chat, and an example image augmentation mechanism may be used to surface and share augmentation data (e.g., an auxiliary still or video images) with other participants of a video chat. In this example, as opposed to displaying a still auxiliary image112, video auxiliary images112may be selected, and presented as an overlay on video primary images114within the camera interface102.

FIG.2is a user interface diagram showing screenshots of further examples of image augmentation mechanisms, in the form of filters, that can be invoked to cause selection and presentation of an auxiliary image with a primary image within a camera interface102.

In screenshot202, a filter icon210is user selectable to invoke a “my best selfie” filter, which operatively determines an auxiliary image selection criterion related to high-quality or favorite “selfie” images of a viewing user (e.g., depicted in the primary image114). High-quality images meeting this criterion may be automatically selected, from a collection of digital images associated with the viewing user, in an automated manner based on predetermined image characteristics. Alternatively, certain images may have been flagged or tagged by the viewing user as favorite images. Further, the content of digital images within the collection may be automatically analyzed to identify, and flag images are “selfie” images. Once the “my best selfie” filter mechanism has identified one or more digital images that satisfy the relevant criterion, these images are presented as auxiliary images112within the camera interface102. Where multiple digital images are identified as satisfying the selection criterion, multiple such images may be simultaneously presented within the camera interface102as a collage. Alternatively, the camera interface102may enable the viewing user to “scroll” through these multiple images by tapping on a displayed auxiliary image112to advanced display to a next image in the selected group of auxiliary images.

Screenshot204shows an example “saved with friends” filter, having an associated filter icon212that is user-selectable to invoke a filter mechanism that automatically identifies one or more digital images that include both the viewing user and one or more “friends” of the viewing user. Friends of the viewing user are determined by the user management system412, with reference to the entity table506, entity graph508, and profile data516stored within the database518.

Screenshot206illustrates an example “time of day” filter having an associated icon that is user-selectable to invoke a friend carousel108, including avatar icons for friends of the viewing user. User selection of one of the avatar icons results in the creation of composite selection criteria, including a time of day criterion (e.g., early mornings) and a friend criterion (e.g., based on a user identifier of the friend associated with the selected avatar icon). The composite selection criteria is used to identify an auxiliary image112that includes a depiction of the selected friend, and for which the metadata indicates that the auxiliary image onto was taken before 8 AM. The auxiliary image112is then shown overlaid on a primary image114to create a composite image.

Screenshot208illustrates an example “pet” filter having an associated pet filter icon214that is user-selectable to invoke a filter mechanism that automatically identifies one or more digital images showing an animal or pet of the viewing user. Image recognition technology may be used, in some examples, to detect digital photographs shared by the viewing user that include an animal. In other examples, metadata associated with digital photographs (e.g., the content of text messages within which a digital photograph was included) may be used to identify digital photographs shared by the viewing user, and that depict a pet.

It will be appreciated that a wide variety of selection criteria may be used to identify digital photographs, associated with the viewing user, there may be a selected as an auxiliary image112, and used to create a collage or composite image that includes the auxiliary image112(or multiple auxiliary images112) and a primary image114.

An example interaction system300, within which example image augmentation mechanisms may be deployed, will now be described, whereafter further details will be provided regarding various orientation mechanisms will be provided.

Networked Computing Environment

FIG.3is a block diagram showing an example interaction system300for facilitating interactions (e.g., exchanging text messages, conducting text audio and video calls, or playing games) over a network. The interaction system300includes multiple instances of a client device302, each of which hosts a number of applications, including an interaction client304and other applications306. Each interaction client304is communicatively coupled, via a network312(e.g., the Internet), to other instances of the interaction client304(e.g., hosted on respective other client devices302), an interaction server system308and third-party servers310). An interaction client304can also communicate with locally-hosted applications306using Applications Program Interfaces (APIs).

An interaction client304is able to interact with other interaction clients304and with the interaction server system308via the network312. The data exchanged between interaction clients304, and between an interaction client304and the interaction server system308, includes functions (e.g., commands to invoke functions) as well as payload data (e.g., text, audio, video or other multimedia data).

The interaction server system308provides server-side functionality via the network312to the interaction clients304. While certain functions of the interaction system300are described herein as being performed by either an interaction client304or by the interaction server system308, the location of certain functionality either within the interaction client304or the interaction server system308may be a design choice. For example, it may be technically preferable to initially deploy certain technology and functionality within the interaction server system308but to later migrate this technology and functionality to the interaction client304where a client device302has sufficient processing capacity.

The interaction server system308supports various services and operations that are provided to the interaction clients304. Such operations include transmitting data to, receiving data from, and processing data generated by the interaction clients304. This data may include message content, client device information, geolocation information, media augmentation and overlays, message content persistence conditions, social network information, and live event information, as examples. Data exchanges within the interaction system300are invoked and controlled through functions available via user interfaces (UIs) of the interaction clients304.

Turning now specifically to the interaction server system308, an Application Program Interface (API) server316is coupled to, and provides a programmatic interface to, interaction servers314. The interaction servers314are communicatively coupled to a database server318, which facilitates access to a database320that stores data associated with interactions processed by the interaction servers314. Similarly, a web server322is coupled to the interaction servers314, and provides web-based interfaces to the interaction servers314. To this end, the web server322processes incoming network requests over the Hypertext Transfer Protocol (HTTP) and several other related protocols.

The Application Program Interface (API) server316receives and transmits interaction data (e.g., commands and message payloads) between the client device302and the interaction servers314. Specifically, the Application Program Interface (API) server316provides a set of interfaces (e.g., routines and protocols) that can be called or queried by the interaction client304in order to invoke functionality of the interaction servers314. The Application Program Interface (API) server316exposes various functions supported by the interaction servers314, including account registration, login functionality, the sending of interaction data via the interaction servers314, from a particular interaction client304to another interaction client304, the communication of media files (e.g., images or video) from an interaction client304to the interaction servers314, the settings of a collection of media data (e.g., a story), the retrieval of a list of friends of a user of a client device302, the retrieval of messages and content, the addition and deletion of entities (e.g., friends) to an entity graph (e.g., a social graph), the location of friends within a social graph, and opening an application event (e.g., relating to the interaction client304).

The interaction servers314host a number of systems and subsystems, describe below with reference toFIG.4.

Returning to the interaction client304, features and functions of an external resource (e.g., an application306or applet) are made available to a user via an interface of the interaction client304. In this context, “external” refers to the fact that the application306or applet is external to the interaction client304. The external resource is often provided by a third party but may also be provided by the creator or provider of the interaction client304. The interaction client304receives a user selection of an option to launch or access features of such an external resource. The external resource may be the application306installed on the client device302(e.g., a “native app”), or a small-scale version of the application (e.g., an “applet”) that is hosted on the client device302or remote of the client device302(e.g., on third-party servers310). The small-scale version of the application includes a subset of features and functions of the application (e.g., the full-scale, native version of the application) and is implemented using a markup-language document. In one example, the small-scale version of the application (e.g., an “applet”) is a web-based, markup-language version of the application and is embedded in the interaction client304. In addition to using markup-language documents (e.g., a .*ml file), an applet may incorporate a scripting language (e.g., a .*js file or a .json file) and a style sheet (e.g., a .*ss file).

In response to receiving a user selection of the option to launch or access features of the external resource, the interaction client304determines whether the selected external resource is a web-based external resource or a locally-installed application306. In some cases, applications306that are locally installed on the client device302can be launched independently of and separately from the interaction client304, such as by selecting an icon, corresponding to the application306, on a home screen of the client device302. Small-scale versions of such applications can be launched or accessed via the interaction client304and, in some examples, no or limited portions of the small-scale application can be accessed outside of the interaction client304. The small-scale application can be launched by the interaction client304receiving, from a third-party server310for example, a markup-language document associated with the small-scale application and processing such a document.

In response to determining that the external resource is a locally-installed application306, the interaction client304instructs the client device302to launch the external resource by executing locally-stored code corresponding to the external resource. In response to determining that the external resource is a web-based resource, the interaction client304communicates with the third-party servers310(for example) to obtain a markup-language document corresponding to the selected external resource. The interaction client304then processes the obtained markup-language document to present the web-based external resource within a user interface of the interaction client304.

The interaction client304can notify a user of the client device302, or other users related to such a user (e.g., “friends”), of activity taking place in one or more external resources. For example, the interaction client304can provide participants in a conversation (e.g., a chat session) in the interaction client304with notifications relating to the current or recent use of an external resource by one or more members of a group of users. One or more users can be invited to join in an active external resource or to launch a recently-used but currently inactive (in the group of friends) external resource. The external resource can provide participants in a conversation, each using respective interaction clients304, with the ability to share an item, status, state, or location in an external resource with one or more members of a group of users into a chat session. The shared item may be an interactive chat card with which members of the chat can interact, for example, to launch the corresponding external resource, view specific information within the external resource, or take the member of the chat to a specific location or state within the external resource. Within a given external resource, response messages can be sent to users on the interaction client304. The external resource can selectively include different media items in the responses, based on a current context of the external resource.

The interaction client304can present a list of the available external resources (e.g., applications306or applets) to a user to launch or access a given external resource. This list can be presented in a context-sensitive menu. For example, the icons representing different ones of the application306(or applets) can vary based on how the menu is launched by the user (e.g., from a conversation interface or from a non-conversation interface).

System Architecture

FIG.4is a block diagram illustrating further details regarding the interaction system300, according to some examples. Specifically, the interaction system300is shown to comprise the interaction client406and the interaction servers418. The interaction system300embodies a number of subsystems, which are supported on the client-side by the interaction client406and on the sever-side by the interaction servers418. Example subsystems are discussed below.

A302is responsible for enabling and processing multiple forms of communication and interaction within the interaction system300, and includes a messaging system404, an audio communication system408, and a video communication system410. The messaging system404is responsible for enforcing the temporary or time-limited access to content by the interaction clients406. The messaging system404incorporates a number of timers (e.g., within an ephemeral timer system430) that, based on duration and display parameters associated with a message, or collection of messages (e.g., a story), selectively enable access (e.g., for presentation and display) to messages and associated content via the interaction client406. Further details regarding the operation of the ephemeral timer system430are provided below. The audio communication system408enables and supports audio communications (e.g., real-time audio chat) between multiple interaction clients406. Similar, the video communication system410enables and supports video communications (e.g., real-time video chat) between multiple interaction clients406.

A user management system412is operationally responsible for the management of user data and profiles, and includes a social network system414that maintains information regarding relationships between users of the interaction system300.

A collection management system416which is operationally responsible for managing sets or collections of media (e.g., collections of text, image video, and audio data). A collection of content (e.g., messages, including images, video, text, and audio) may be organized into an “event gallery” or an “event story.” Such a collection may be made available for a specified time period, such as the duration of an event to which the content relates. For example, content relating to a music concert may be made available as a “story” for the duration of that music concert. The collection management system416may also be responsible for publishing an icon that provides notification of the existence of a particular collection to the user interface of the interaction client406. The collection management system416furthermore includes a curation function that allows a collection manager to manage and curate a particular collection of content. For example, the curation interface enables an event organizer to curate a collection of content relating to a specific event (e.g., delete inappropriate content or redundant messages). Additionally, the collection management system416employs machine vision (or image recognition technology) and content rules to automatically curate a content collection. In certain examples, compensation may be paid to a user for the inclusion of user-generated content into a collection. In such cases, the collection management system416operates to automatically make payments to such users for the use of their content.

An image processing and augmentation system420provides various functions that enable a user to augment (e.g., annotate or otherwise modify or edit) media content associated with a message. For example, the image processing and augmentation system420provides functions related to the generation and publishing of media overlays for messages processed by the interaction system300. The image processing and augmentation system420operatively supplies a media overlay or augmentation (e.g., an image filter) to the interaction client406based on a geolocation of the client device302. In another example, the image processing and augmentation system420operatively supplies a media overlay to the interaction client406based on other information, such as social network information of the user of the client device302. A media overlay may include audio and visual content and visual effects. Examples of audio and visual content include pictures, texts, logos, animations, and sound effects. An example of a visual effect includes color overlaying. The audio and visual content or the visual effects can be applied to a media content item (e.g., a photo) at client device302for communication in a message, or applied to video content, such as a video content stream or feed transmitted from an interaction client406. As such, the image processing and augmentation system420may interact with, and support, the various subsystems of the communication system402, such as the messaging system404and the video communication system410. A media overlay may include text or image that can be overlaid on top of a photograph taken by the client device302, or a video stream produced by the client device302. In another examples, the media overlay may be a location overlay (e.g., Venice beach), a name of a live event, or a name of a merchant overlay (e.g., Beach Coffee House). In further examples, the image processing and augmentation system420uses the geolocation of the client device302to identify a media overlay that includes the name of a merchant at the geolocation of the client device302. The media overlay may include other indicia associated with the merchant. The media overlays may be stored in the databases320and accessed through the database server318.

In some examples, the image processing and augmentation system420provides a user-based publication platform that enables users to select a geolocation on a map and upload content associated with the selected geolocation. The user may also specify circumstances under which a particular media overlay should be offered to other users. The image processing and augmentation system420generates a media overlay that includes the uploaded content and associates the uploaded content with the selected geolocation.

In other examples, the image processing and augmentation system420provides a merchant-based publication platform that enables merchants to select a particular media overlay associated with a geolocation via a bidding process. For example, the image processing and augmentation system420associates the media overlay of the highest bidding merchant with a corresponding geolocation for a predefined amount of time.

A map system422provides various geographic location functions, and supports the presentation of map-based media content and messages by the interaction client406. For example, the map system422enables the display of user icons or avatars (e.g., stored in profile data516) on a map to indicate a current or past location of “friends” of a user, as well as media content (e.g., collections of messages including photographs and videos) generated by such friends, within the context of a map. For example, a message posted by a user to the interaction system300from a specific geographic location may be displayed within the context of a map at that particular location to “friends” of a specific user on a map interface of the interaction client406. A user can furthermore share his or her location and status information (e.g., using an appropriate status avatar) with other users of the interaction system300via the interaction client406, with this location and status information being similarly displayed within the context of a map interface of the interaction client406to selected users.

A game system424provides various gaming functions within the context of the interaction client406. The interaction client406provides a game interface providing a list of available games that can be launched by a user within the context of the interaction client406, and played with other users of the interaction system300. The interaction system300further enables a particular user to invite other users to participate in the play of a specific game, by issuing invitations to such other users from the interaction client406. The interaction client406also supports audio, video and text messaging (e.g., chats) within the context of gameplay, provides a leaderboard for the games, and also supports the provision of in-game rewards (e.g., coins and items).

An external resource system426provides an interface for the interaction client406to communicate with remote servers (e.g., third-party servers310) to launch or access external resources, i.e. applications or applets. Each third-party server310hosts, for example, a markup language (e.g., HTML5) based application or small-scale version of an application (e.g., game, utility, payment, or ride-sharing application). The interaction client406may launches a web-based resource (e.g., application) by accessing the HTML5 file from the third-party servers310associated with the web-based resource. In certain examples, applications hosted by third-party servers310are programmed in JavaScript leveraging a Software Development Kit (SDK) provided by the interaction servers418. The SDK includes Application Programming Interfaces (APIs) with functions that can be called or invoked by the web-based application. In certain examples, the interaction servers418includes a JavaScript library that provides a given external resource access to certain user data of the interaction client406. HTML5 is used as an example technology for programming games, but applications and resources programmed based on other technologies can be used.

In order to integrate the functions of the SDK into the web-based resource, the SDK is downloaded by a third-party server310from the interaction servers418or is otherwise received by the third-party server310. Once downloaded or received, the SDK is included as part of the application code of a web-based external resource. The code of the web-based resource can then call or invoke certain functions of the SDK to integrate features of the interaction client406into the web-based resource.

The SDK stored on the interaction server system308effectively provides the bridge between an external resource (e.g., applications306or applets and the interaction client406. This provides the user with a seamless experience of communicating with other users on the interaction client406, while also preserving the look and feel of the interaction client406. To bridge communications between an external resource and an interaction client406, in certain examples, the SDK facilitates communication between third-party servers310and the interaction client406. In certain examples, a WebViewJavaScriptBridge running on a client device302establishes two one-way communication channels between an external resource and the interaction client406. Messages are sent between the external resource and the interaction client406via these communication channels asynchronously. Each SDK function invocation is sent as a message and callback. Each SDK function is implemented by constructing a unique callback identifier and sending a message with that callback identifier.

By using the SDK, not all information from the interaction client406is shared with third-party servers310. The SDK limits which information is shared based on the needs of the external resource. In certain examples, each third-party server310provides an HTML5 file corresponding to the web-based external resource to interaction servers418. The interaction servers418can add a visual representation (such as a box art or other graphic) of the web-based external resource in the interaction client406. Once the user selects the visual representation or instructs the interaction client406through a GUI of the interaction client406to access features of the web-based external resource, the interaction client406obtains the HTML5 file and instantiates the resources necessary to access the features of the web-based external resource.

The interaction client406presents a graphical user interface (e.g., a landing page or title screen) for an external resource. During, before, or after presenting the landing page or title screen, the interaction client406determines whether the launched external resource has been previously authorized to access user data of the interaction client406. In response to determining that the launched external resource has been previously authorized to access user data of the interaction client406, the interaction client406presents another graphical user interface of the external resource that includes functions and features of the external resource. In response to determining that the launched external resource has not been previously authorized to access user data of the interaction client406, after a threshold period of time (e.g., 3 seconds) of displaying the landing page or title screen of the external resource, the interaction client406slides up (e.g., animates a menu as surfacing from a bottom of the screen to a middle of or other portion of the screen) a menu for authorizing the external resource to access the user data. The menu identifies the type of user data that the external resource will be authorized to use. In response to receiving a user selection of an accept option, the interaction client406adds the external resource to a list of authorized external resources and allows the external resource to access user data from the interaction client406. In some examples, the external resource is authorized by the interaction client406to access the user data in accordance with an OAuth 2 framework.

The interaction client406controls the type of user data that is shared with external resources based on the type of external resource being authorized. For example, external resources that include full-scale applications (e.g., an application306) are provided with access to a first type of user data (e.g., only two-dimensional avatars of users with or without different avatar characteristics). As another example, external resources that include small-scale versions of applications (e.g., web-based versions of applications) are provided with access to a second type of user data (e.g., payment information, two-dimensional avatars of users, three-dimensional avatars of users, and avatars with various avatar characteristics). Avatar characteristics include different ways to customize a look and feel of an avatar, such as different poses, facial features, clothing, and so forth.

An advertisement system428operationally enables the purchasing of advertisements by third parties for presentation to end-users via the interaction clients204, and also handles the delivery and presentation of these advertisements.

Data Architecture

FIG.5is a schematic diagram illustrating data structures500, which may be stored in the database518of the interaction server system308, according to certain examples. While the content of the database518is shown to comprise a number of tables, it will be appreciated that the data could be stored in other types of data structures (e.g., as an object-oriented database).

The database518includes message data stored within a message table502. This message data includes, for any particular one message, at least message sender data, message recipient (or receiver) data, and a payload. Further details regarding information that may be included in a message, and included within the message data stored in the message table502is described below with reference toFIG.5.

An entity table506stores entity data, and is linked (e.g., referentially) to an entity graph508and profile data516. Entities for which records are maintained within the entity table506may include individuals, corporate entities, organizations, objects, places, events, and so forth. Regardless of entity type, any entity regarding which the interaction server system308stores data may be a recognized entity. Each entity is provided with a unique identifier, as well as an entity type identifier (not shown).

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

The profile data516stores multiple types of profile data about a particular entity. The profile data516may be selectively used and presented to other users of the interaction system300, based on privacy settings specified by a particular entity. Where the entity is an individual, the profile data516includes, for example, a user name, telephone number, address, settings (e.g., notification and privacy settings), as well as a user-selected avatar representation (or collection of such avatar representations). A particular user may then selectively include one or more of these avatar representations within the content of messages communicated via the interaction system300, and on map interfaces displayed by interaction clients304to other users. The collection of avatar representations may include “status avatars,” which present a graphical representation of a status or activity that the user may select to communicate at a particular time.

Where the entity is a group, the profile data516for 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 relevant group.

The database518also stores augmentation data, such as overlays or filters, in an augmentation table510. The augmentation data is associated with and applied to videos (for which data is stored in a video table504) and images (for which data is stored in an image table512).

Filters, in one example, are overlays that are displayed as overlaid on an image or video during presentation to a recipient user. Filters may be of various types, including user-selected filters from a set of filters presented to a sending user by the interaction client304, when the sending user is composing a message. Other types of filters include geolocation filters (also known as geo-filters), which may be presented to a sending user based on geographic location. For example, geolocation filters specific to a neighborhood or special location may be presented within a user interface by the interaction client304, based on geolocation information determined by a Global Positioning System (GPS) unit of the client device302.

Another type of filter is a data filter, which may be selectively presented to a sending user by the interaction client304, based on other inputs or information gathered by the client device302during the message creation process. Examples of data filters include current temperature at a specific location, a current speed at which a sending user is traveling, battery life for a client device302, or the current time.

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

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

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

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

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

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

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

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

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

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

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

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

A story table514stores data regarding collections of messages and associated image, video, or audio data, which are compiled into a collection (e.g., a story or a gallery). The creation of a particular collection may be initiated by a particular user (e.g., each user for which a record is maintained in the entity table506). A user may create a “personal story” in the form of a collection of content that has been created and sent/broadcast by that user. To this end, the user interface of the interaction client304may include an icon that is user-selectable to enable a sending user to add specific content to his or her personal story.

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

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

As mentioned above, the video table504stores video data that, in one example, is associated with messages for which records are maintained within the message table502. Similarly, the image table512stores image data associated with messages for which message data is stored in the entity table506. The entity table506may associate various augmentations from the augmentation table510with various images and videos stored in the image table512and the video table504.

Methodology/Routines

FIG.6is a flowchart illustrating a method600, according to some examples, of selecting and presenting auxiliary data within a camera interface102presented by an interaction client304executing on a client device302. The method600may be implemented on the client device302by the interaction client304and may be implemented on the interaction server system308by the interaction servers314. The image processing and augmentation system420is invoked by various image augmentation mechanisms (e.g., filters), while other subsystems of the interaction system300(e.g., the user management system412and the collection management system416) provide additional functionality and services to image augmentation mechanisms.

The method600commences at start block602and progresses to operation604, where an interaction client304causes the presentation of a camera interface102, the camera interface102depicting a primary image114captured by a camera (e.g., a front-facing or a rear-facing camera) of the client device302of a first user.

In operation606, the interaction client304causes the presentation of multiple image augmentation graphical elements, in the example form of filter icons106, within the camera interface102. Each of the filter icons106is associated with a respective image augmentation mechanism in the form of a filter mechanism.

In operation608, the interaction client304detects user selection of an auxiliary augmentation icon (e.g., the “friend memories” filter icon106) of the image augmentation icons, the auxiliary image icon being associated with an auxiliary image augmentation mechanism (e.g., a “friend memories” filter).

In operation610, the interaction system300determines an auxiliary image selection criterion (or criteria) for an auxiliary image augmentation mechanism. In one example, such as that described with reference toFIG.1, the determination of the auxiliary image selection criterion may be a multistage process that solicits further input and selections from a viewing user. One such multistage process is described below with reference toFIG.7. In other examples, the selection criterion may be directly associated with the selected image augmentation mechanism, such as, for example, the augmentation mechanisms described above with reference to screenshot202and screenshot208ofFIG.2. The selection criterion may be temporal (e.g., criterion related to a specific time of day or to a specific date) or content related (e.g., related to the content of a digital image, such as a specific person, object or location identified in metadata or that image tag of the auxiliary image).

In operation612, the interaction system300selects an auxiliary image112based on the auxiliary image selection criterion, the auxiliary image112being selected from a collection of digital media (e.g., digital photographs) associated with the viewing user. For example, the viewing user may have taken a number of photographs using the client device302and shared these photographs with other users of the interaction system300in messages communicated using the communication system402. The auxiliary image112may be selected from this collection of shared digital photographs. In another example, the viewing user may have been tagged in a digital photograph, or have received a digital photograph from another user, and as such digital photographs may also be regarded as included in the collection from which the auxiliary image112is selected. Additionally, the collection of media may include videos, digital stickers, digital avatars, and other captured or created visual or audio digital information.

In operation614, the interaction system300overlays the auxiliary image112on the primary image114to generate a composite image that is presented within the camera interface102of the interaction client304. At operation616, the composite image may be captured (e.g., by a user selection of the friend icon110), and communicated as part of a message sent from the interaction client304of the viewing user to an interaction client326of a receiving user. The method600then ends at done block618.

While the selection and presentation of only a single auxiliary image112onto is shown and described above, the method600may be deployed to select multiple auxiliary images112for presentation with a primary image114to create a multi-image collage that is presented within the camera interface102, and that can be captured and shared by the viewing user with other users. In this case, multiple selection criteria may be used to identify multiple auxiliary images.

FIG.7is a flowchart illustrating a method700, according to some examples, that may be implemented at operation610in order to determine an auxiliary image selection criterion to be used by an auxiliary image augmentation mechanism (e.g., a filter) to identify and select one or more auxiliary images112. The method700may be used to generate, for example, the friend carousel108shown inFIG.1andFIG.2.

The method700commences at start block702and then progresses to operation704with the presentation, within the camera interface102, of multiple user graphical elements in the form of friend icons110that are presented within the context of a friend carousel108. Each of these friend icons is associated with a respective user of the interaction system300, and each of these uses may be identified as being associated with the viewing user (e.g., a friend of the viewing user or someone included in a common group with the viewing user).

At operation706, user-selection of a friend icon110is detected within the context of the camera interface102. User selection may include tapping on the friend icon on a haptic or touch sensitive screen of the client device302.

At operation708, the auxiliary image augmentation mechanism determines the auxiliary image selection criterion (e.g., a filter criterion) based on the selection of a specific friend icon110. The filter criterion, in this example, may be a user identifier that is used to identify digital content (e.g., digital photographs captured or shared by or with the viewing user) associated with the user identifier. A user identifier may be associated with a particular digital photograph by the interaction system300on account of the digital photograph being shared by or with the relevant user (e.g., the relevant user was a sender or recipient of a digital communication that included the particular digital photograph).

The method700hen terminates at done block710

Data Communications Architecture

FIG.8is a schematic diagram illustrating a structure of a message800, according to some examples, generated by an interaction client304for communication to a further interaction client304via the interaction servers314. The content of a particular message800is used to populate the message table502stored within the database320, accessible by the interaction servers314. Similarly, the content of a message800is stored in memory as “in-transit” or “in-flight” data of the client device302or the interaction servers314. A message800is shown to include the following example components:message identifier802: a unique identifier that identifies the message800.message text payload804: text, to be generated by a user via a user interface of the client device302, and that is included in the message800.message image payload808: image data, captured by a camera component of a client device302or retrieved from a memory component of a client device302, and that is included in the message800. Image data for a sent or received message800may be stored in the image table820.message video payload812: video data, captured by a camera component or retrieved from a memory component of the client device302, and that is included in the message800. Video data for a sent or received message800may be stored in the video table806.message audio payload814: audio data, captured by a microphone or retrieved from a memory component of the client device302, and that is included in the message800.message augmentation data818: augmentation data (e.g., filters, stickers, or other annotations or enhancements) that represents augmentations to be applied to message image payload808, message video payload812, or message audio payload814of the message800. Augmentation data for a sent or received message800may be stored in the augmentation table816.message duration parameter822: parameter value indicating, in seconds, the amount of time for which content of the message (e.g., the message image payload808, message video payload812, message audio payload814) is to be presented or made accessible to a user via the interaction client304.message geolocation parameter828: geolocation data (e.g., latitudinal and longitudinal coordinates) associated with the content payload of the message. Multiple message geolocation parameter828values may be included in the payload, each of these parameter values being associated with respect to content items included in the content (e.g., a specific image into within the message image payload808, or a specific video in the message video payload812).message story identifier830: identifier values identifying one or more content collections (e.g., “stories” identified in the story table824) with which a particular content item in the message image payload808of the message800is associated. For example, multiple images within the message image payload808may each be associated with multiple content collections using identifier values.message tag832: each message800may be tagged with multiple tags, each of which is indicative of the subject matter of content included in the message payload. For example, where a particular image included in the message image payload808depicts an animal (e.g., a lion), a tag value may be included within the message tag832that is indicative of the relevant animal. Tag values may be generated manually, based on user input, or may be automatically generated using, for example, image recognition.message sender identifier834: an identifier (e.g., a messaging system identifier, email address, or device identifier) indicative of a user of the Client device302on which the message800was generated and from which the message800was sent.message receiver identifier826: an identifier (e.g., a messaging system identifier, email address, or device identifier) indicative of a user of the client device302to which the message800is addressed.

The contents (e.g., values) of the various components of message800may be pointers to locations in tables within which content data values are stored. For example, an image value in the message image payload808may be a pointer to (or address of) a location within an image table820. Similarly, values within the message video payload812may point to data stored within a video table806, values stored within the message augmentations412may point to data stored in an augmentation table816, values stored within the message story identifier830may point to data stored in a story table824, and values stored within the message sender identifier834and the message receiver identifier826may point to user records stored within an entity table810.

Time-Based Access Limitation Architecture

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

An ephemeral message902is shown to be associated with a message duration parameter908, the value of which determines an amount of time that the ephemeral message902will be displayed to a receiving user of the ephemeral message902by the interaction client304. In one example, an ephemeral message902is viewable by a receiving user for up to a maximum of 10 seconds, depending on the amount of time that the sending user specifies using the message duration parameter908.

The message duration parameter908and the message receiver identifier918are shown to be inputs to a message timer912, which is responsible for determining the amount of time that the ephemeral message902is shown to a particular receiving user identified by the message receiver identifier918. In particular, the ephemeral message902will only be shown to the relevant receiving user for a time period determined by the value of the message duration parameter908. The message timer912is shown to provide output to a more generalized messaging system904, which is responsible for the overall timing of display of content (e.g., an ephemeral message902) to a receiving user.

The ephemeral message902is shown inFIG.9to be included within an ephemeral message group906(e.g., a collection of messages in a personal story, or an event story). The ephemeral message group906has an associated group duration parameter910, a value of which determines a time duration for which the ephemeral message group906is presented and accessible to users of the interaction system300. The group duration parameter910, for example, may be the duration of a music concert, where the ephemeral message group906is a collection of content pertaining to that concert. Alternatively, a user (either the owning user or a curator user) may specify the value for the group duration parameter910when performing the setup and creation of the ephemeral message group906.

Additionally, each ephemeral message902within the ephemeral message group906has an associated group participation parameter914, a value of which determines the duration of time for which the ephemeral message902will be accessible within the context of the ephemeral message group906. Accordingly, a particular ephemeral message group906may “expire” and become inaccessible within the context of the ephemeral message group906, prior to the ephemeral message group906itself expiring in terms of the group duration parameter910. The group duration parameter910, group participation parameter914, and message receiver identifier918each provide input to a group timer916, which operationally determines, firstly, whether a particular ephemeral message902of the ephemeral message group906will be displayed to a particular receiving user and, if so, for how long. Note that the ephemeral message group906is also aware of the identity of the particular receiving user as a result of the message receiver identifier918.

Accordingly, the group timer916operationally controls the overall lifespan of an associated ephemeral message group906, as well as an individual ephemeral message902included in the ephemeral message group906. In one example, each and every ephemeral message902within the ephemeral message group906remains viewable and accessible for a time period specified by the group duration parameter910. In a further example, a certain ephemeral message902may expire, within the context of ephemeral message group906, based on a group participation parameter914. Note that a message duration parameter908may still determine the duration of time for which a particular ephemeral message902is displayed to a receiving user, even within the context of the ephemeral message group906. Accordingly, the message duration parameter908determines the duration of time that a particular ephemeral message902is displayed to a receiving user, regardless of whether the receiving user is viewing that ephemeral message902inside or outside the context of an ephemeral message group906.

The messaging system904may furthermore operationally remove a particular ephemeral message902from the ephemeral message group906based on a determination that it has exceeded an associated group participation parameter914. For example, when a sending user has established a group participation parameter914of 24 hours from posting, the messaging system904will remove the relevant ephemeral message902from the ephemeral message group906after the specified 24 hours. The messaging system904also operates to remove an ephemeral message group906when either the group participation parameter914for each and every ephemeral message902within the ephemeral message group906has expired, or when the ephemeral message group906itself has expired in terms of the group duration parameter910.

In certain use cases, a creator of a particular ephemeral message group906may specify an indefinite group duration parameter910. In this case, the expiration of the group participation parameter914for the last remaining ephemeral message902within the ephemeral message group906will determine when the ephemeral message group906itself expires. In this case, a new ephemeral message902, added to the ephemeral message group906, with a new group participation parameter914, effectively extends the life of an ephemeral message group906to equal the value of the group participation parameter914.

Responsive to the messaging system904determining that an ephemeral message group906has expired (e.g., is no longer accessible), the messaging system904communicates with the interaction system300(and, for example, specifically the interaction client304) to cause an indicium (e.g., an icon) associated with the relevant ephemeral message group906to no longer be displayed within a user interface of the interaction client304. Similarly, when the messaging system904determines that the message duration parameter908for a particular ephemeral message902has expired, the messaging system904causes the interaction client304to no longer display an indicium (e.g., an icon or textual identification) associated with the ephemeral message902.

Machine Architecture

FIG.10is a diagrammatic representation of the machine1000within which instructions1010(e.g., software, a program, an application, an applet, an app, or other executable code) for causing the machine1000to perform any one or more of the methodologies discussed herein may be executed. For example, the instructions1010may cause the machine1000to execute any one or more of the methods described herein. The instructions1010transform the general, non-programmed machine1000into a particular machine1000programmed to carry out the described and illustrated functions in the manner described. The machine1000may operate as a standalone device or may be coupled (e.g., networked) to other machines. In a networked deployment, the machine1000may operate in the capacity of a server machine or a client machine in a server-client network environment, or as a peer machine in a peer-to-peer (or distributed) network environment. The machine1000may comprise, but not be limited to, a server computer, a client computer, a personal computer (PC), a tablet computer, a laptop computer, a netbook, a set-top box (STB), a personal digital assistant (PDA), an entertainment media system, a cellular telephone, a smartphone, a mobile device, a wearable device (e.g., a smartwatch), a smart home device (e.g., a smart appliance), other smart devices, a web appliance, a network router, a network switch, a network bridge, or any machine capable of executing the instructions1010, sequentially or otherwise, that specify actions to be taken by the machine1000. Further, while only a single machine1000is illustrated, the term “machine” shall also be taken to include a collection of machines that individually or jointly execute the instructions1010to perform any one or more of the methodologies discussed herein. The machine1000, for example, may comprise the client device202(deleted) or any one of a number of server devices forming part of the interaction server system208(deleted). In some examples, the machine1000may also comprise both client and server systems, with certain operations of a particular method or algorithm being performed on the server-side and with certain operations of the particular method or algorithm being performed on the client-side.

The machine1000may include processors1004, memory1006, and input/output I/O components1002, which may be configured to communicate with each other via a bus1040. In an example, the processors1004(e.g., a Central Processing Unit (CPU), a Reduced Instruction Set Computing (RISC) Processor, a Complex Instruction Set Computing (CISC) Processor, a Graphics Processing Unit (GPU), a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Radio-Frequency Integrated Circuit (RFIC), another processor, or any suitable combination thereof) may include, for example, a processor1008and a processor1012that execute the instructions1010. The term “processor” is intended to include multi-core processors that may comprise two or more independent processors (sometimes referred to as “cores”) that may execute instructions contemporaneously. AlthoughFIG.10shows multiple processors1004, the machine1000may include a single processor with a single-core, a single processor with multiple cores (e.g., a multi-core processor), multiple processors with a single core, multiple processors with multiples cores, or any combination thereof.

The memory1006includes a main memory1014, a static memory1016, and a storage unit1018, both accessible to the processors1004via the bus1040. The main memory1006, the static memory1016, and storage unit1018store the instructions1010embodying any one or more of the methodologies or functions described herein. The instructions1010may also reside, completely or partially, within the main memory1014, within the static memory1016, within machine-readable medium1020within the storage unit1018, within at least one of the processors1004(e.g., within the Processor's cache memory), or any suitable combination thereof, during execution thereof by the machine1000.

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

In further examples, the I/O components1002may include biometric components1030, motion components1032, environmental components1034, or position components1036, among a wide array of other components. For example, the biometric components1030include components to detect expressions (e.g., hand expressions, facial expressions, vocal expressions, body gestures, or eye-tracking), measure biosignals (e.g., blood pressure, heart rate, body temperature, perspiration, or brain waves), identify a person (e.g., voice identification, retinal identification, facial identification, fingerprint identification, or electroencephalogram-based identification), and the like. The motion components1032include acceleration sensor components (e.g., accelerometer), gravitation sensor components, rotation sensor components (e.g., gyroscope).

The environmental components1034include, for example, one or cameras (with still image/photograph and video capabilities), illumination sensor components (e.g., photometer), temperature sensor components (e.g., one or more thermometers that detect ambient temperature), humidity sensor components, pressure sensor components (e.g., barometer), acoustic sensor components (e.g., one or more microphones that detect background noise), proximity sensor components (e.g., infrared sensors that detect nearby objects), gas sensors (e.g., gas detection sensors to detection concentrations of hazardous gases for safety or to measure pollutants in the atmosphere), or other components that may provide indications, measurements, or signals corresponding to a surrounding physical environment.

With respect to cameras, the client device302may have a camera system comprising, for example, front cameras on a front surface of the client device302and rear cameras on a rear surface of the client device302. The front cameras may, for example, be used to capture still images and video of a user of the client device302(e.g., “selfies”), which may then be augmented with augmentation data (e.g., filters) described above. The rear cameras may, for example, be used to capture still images and videos in a more traditional camera mode, with these images similarly being augmented with augmentation data. In addition to front and rear cameras, the client device302may also include a 360° camera for capturing 360° photographs and videos.

Further, the camera system of the client device302may include dual rear cameras (e.g., a primary camera as well as a depth-sensing camera), or even triple, quad or penta rear camera configurations on the front and rear sides of the client device302. These multiple cameras systems may include a wide camera, an ultra-wide camera, a telephoto camera, a macro camera and a depth sensor, for example.

The position components1036include location sensor components (e.g., a GPS receiver component), altitude sensor components (e.g., altimeters or barometers that detect air pressure from which altitude may be derived), orientation sensor components (e.g., magnetometers), and the like.

Communication may be implemented using a wide variety of technologies. The I/O components1002further include communication components1038operable to couple the machine1000to a network1022or devices1024via respective coupling or connections. For example, the communication components1038may include a network interface Component or another suitable device to interface with the network1022. In further examples, the communication components1038may include wired communication components, wireless communication components, cellular communication components, Near Field Communication (NFC) components, Bluetooth® components (e.g., Bluetooth® Low Energy), Wi-Fi® components, and other communication components to provide communication via other modalities. The devices1024may be another machine or any of a wide variety of peripheral devices (e.g., a peripheral device coupled via a USB).

Moreover, the communication components1038may detect identifiers or include components operable to detect identifiers. For example, the communication components1038may include Radio Frequency Identification (RFID) tag reader components, NFC smart tag detection components, optical reader components (e.g., an optical sensor to detect one-dimensional bar codes such as Universal Product Code (UPC) bar code, multi-dimensional bar codes such as Quick Response (QR) code, Aztec code, Data Matrix, Dataglyph, MaxiCode, PDF417, Ultra Code, UCC RSS-2D bar code, and other optical codes), or acoustic detection components (e.g., microphones to identify tagged audio signals). In addition, a variety of information may be derived via the communication components1038, such as location via Internet Protocol (IP) geolocation, location via Wi-Fi® signal triangulation, location via detecting an NFC beacon signal that may indicate a particular location, and so forth.

The various memories (e.g., main memory1014, static memory1016, and memory of the processors1004) and storage unit1018may store one or more sets of instructions and data structures (e.g., software) embodying or used by any one or more of the methodologies or functions described herein. These instructions (e.g., the instructions1010), when executed by processors1004, cause various operations to implement the disclosed examples.

The instructions1010may be transmitted or received over the network1022, using a transmission medium, via a network interface device (e.g., a network interface component included in the communication components1038) and using any one of several well-known transfer protocols (e.g., hypertext transfer protocol (HTTP)). Similarly, the instructions1010may be transmitted or received using a transmission medium via a coupling (e.g., a peer-to-peer coupling) to the devices1024.

Software Architecture

FIG.11is a block diagram1100illustrating a software architecture1104, which can be installed on any one or more of the devices described herein. The software architecture1104is supported by hardware such as a machine1102that includes processors1120, memory1126, and I/O components1138. In this example, the software architecture1104can be conceptualized as a stack of layers, where each layer provides a particular functionality. The software architecture1104includes layers such as an operating system1112, libraries1110, frameworks1108, and applications1106. Operationally, the applications1106invoke API calls1150through the software stack and receive messages1152in response to the API calls1150.

The operating system1112manages hardware resources and provides common services. The operating system1112includes, for example, a kernel1114, services1116, and drivers1122. The kernel1114acts as an abstraction layer between the hardware and the other software layers. For example, the kernel1114provides memory management, processor management (e.g., scheduling), component management, networking, and security settings, among other functionality. The services1116can provide other common services for the other software layers. The drivers1122are responsible for controlling or interfacing with the underlying hardware. For instance, the drivers1122can 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, and so forth.

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

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

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

CONCLUSION

In one example, the method includes causing presentation of a camera interface, the camera interface to display a primary image captured by a camera of a computing device of a first user, causing presentation of a plurality of augmentation icons within the camera interface, each of the image augmentation icons being associated with a respective image augmentation mechanism, detecting user selection of an auxiliary augmentation icon of the plurality of image augmentation icons, the auxiliary image icon being associated with an auxiliary image augmentation mechanism, determining an auxiliary image selection criterion for an auxiliary image augmentation mechanism, selecting an auxiliary image based on the auxiliary image selection criterion, the auxiliary image being selected from a plurality of photographs associated with the first user, and overlaying the auxiliary image on the primary image to generate a composite image that is presented within the camera interface.

The method may also include where the determining of the auxiliary image selection criterion for the auxiliary image augmentation mechanism includes presenting a plurality of user graphical elements, associated with respective users of an interaction system within the camera interface, detecting user selection of a user graphical element within the camera interface, and determining the auxiliary image selection criterion based on the user graphical element.

The method may also include where the auxiliary image selection criterion includes a temporal criterion, and the auxiliary image is identified based on the temporal criterion.

The method may also include where the auxiliary image selection criterion includes an image content criterion, and the selecting of the auxiliary image is based on detecting content corresponding to the image content criterion within the auxiliary image.

The method may also include where the auxiliary image selection criterion includes an image tag criterion, and the selecting of the auxiliary image is based on detecting an image tag for the user image corresponding to the image tag criterion.

The method may also include including capturing the composite image is presented within the camera interface, and communicating the composite image as part of a message from the computing device, responsive to user messaging input.

The method may also include where the plurality of photographs from which the auxiliary images selected includes a collection of images generated by the first user. Other technical features may be readily apparent to one skilled in the art from the following figures, descriptions, and claims.

The method may also include where the user graphical element is a user avatar associated with the first user, the auxiliary image selection criterion is an identifier for the first user, and the selecting of the auxiliary image includes selecting the auxiliary image using the identifier of the first user.

The method may also include where the auxiliary image depicts the first user.

The method may also include where the temporal criterion includes a time of day.

The method may also include where the temporal criterion includes a specific date.

Other technical features may be readily apparent to one skilled in the art from the following figures, descriptions, and claims

Glossary

“Carrier signal” refers to any intangible medium that is capable of storing, encoding, or carrying instructions for execution by the machine, and includes digital or analog communications signals or other intangible media to facilitate communication of such instructions. Instructions may be transmitted or received over a network using a transmission medium via a network interface device.

“Client device” refers to any machine that interfaces to a communications network to obtain resources from one or more server systems or other client devices. A client device may be, but is not limited to, a mobile phone, desktop computer, laptop, portable digital assistants (PDAs), 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 may use to access a network.

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

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

“Computer-readable storage medium” refers to both machine-storage media and transmission media. Thus, the terms include both storage devices/media and carrier waves/modulated data signals. The terms “machine-readable medium,” “computer-readable medium” and “device-readable medium” mean the same thing and may be used interchangeably in this disclosure.

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

“Machine storage medium” refers to a single or multiple storage devices and media (e.g., a centralized or distributed database, and associated caches and servers) that store executable instructions, routines and data. The term shall accordingly be taken to include, but not be limited to, solid-state memories, and optical and magnetic media, including memory internal or external to processors. Specific examples of machine-storage media, computer-storage media and device-storage media include non-volatile memory, including by way of example semiconductor memory devices, e.g., erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), FPGA, and flash memory devices; magnetic disks such as internal hard disks and removable disks; magneto-optical disks; and CD-ROM and DVD-ROM disks The terms “machine-storage medium,” “device-storage medium,” “computer-storage medium” mean the same thing and may be used interchangeably in this disclosure. The terms “machine-storage media,” “computer-storage media,” and “device-storage media” specifically exclude carrier waves, modulated data signals, and other such media, at least some of which are covered under the term “signal medium.”

“Non-transitory computer-readable storage medium” refers to a tangible medium that is capable of storing, encoding, or carrying the instructions for execution by a machine.

“Signal medium” refers to any intangible medium that is capable of storing, encoding, or carrying the instructions for execution by a machine and includes digital or analog communications signals or other intangible media to facilitate communication of software or data. The term “signal medium” shall be taken to include any form of a modulated data signal, carrier wave, and so forth. The term “modulated data signal” means a signal that has one or more of its characteristics set or changed in such a matter as to encode information in the signal. The terms “transmission medium” and “signal medium” mean the same thing and may be used interchangeably in this disclosure.