Patent ID: 12216827

DETAILED DESCRIPTION

When communicating on messaging systems, users are able to call one another and establish a voice call or a video call. Via the messaging systems, the users are also able to share media content items such as audio, video, and pictures. However, it is clear to the users that the communications on messaging systems or using client devices is not akin to a face-to-face communication.

Embodiments of the present disclosure improve the functionality of the messaging system by incorporating tactile or haptic capabilities to the communication interface of the messaging system. By adding the sense of touch to the user's communications on messaging systems, embodiments of the present disclosure takes one step closer to providing a face-to-face communication experience and further allows the user to engage more deeply with his contacts on the messaging system.

Networked Computing Environment

FIG.1is a block diagram showing an example messaging system100for exchanging data (e.g., messages and associated content) over a network. The messaging system100includes multiple instances of a client device102, each of which hosts a number of applications, including a messaging client104and other applications106. In some examples, the client device102comprise a user interface (e.g., display device, touch screen, etc.) that generates haptic feedback responses based on touch inputs received during a communication session, as discussed herein. Each messaging client104is communicatively coupled to other instances of the messaging client104(e.g., hosted on respective other client devices102), a messaging server system108and third-party servers110via a network112(e.g., the Internet). A messaging client104can also communicate with locally-hosted applications106using Applications Program Interfaces (APIs).

A messaging client104is able to communicate and exchange data with other messaging clients104and with the messaging server system108via the network112. The data exchanged between messaging clients104, and between a messaging client104and the messaging server system108, includes functions (e.g., commands to invoke functions) as well as payload data (e.g., text, audio, video or other multimedia data).

The messaging server system108provides server-side functionality via the network112to a particular messaging client104. While certain functions of the messaging system100are described herein as being performed by either a messaging client104or by the messaging server system108, the location of certain functionality either within the messaging client104or the messaging server system108may be a design choice. For example, it may be technically preferable to initially deploy certain technology and functionality within the messaging server system108but to later migrate this technology and functionality to the messaging client104where a client device102has sufficient processing capacity.

The messaging server system108supports various services and operations that are provided to the messaging client104. Such operations include transmitting data to, receiving data from, and processing data generated by the messaging client104. 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 messaging system100are invoked and controlled through functions available via user interfaces (UIs) of the messaging client104.

Turning now specifically to the messaging server system108, an Application Program Interface (API) server116is coupled to, and provides a programmatic interface to, application servers114. The application servers114are communicatively coupled to a database server120, which facilitates access to a database126that stores data associated with messages processed by the application servers114. Similarly, a web server128is coupled to the application servers114, and provides web-based interfaces to the application servers114. To this end, the web server128processes incoming network requests over the Hypertext Transfer Protocol (HTTP) and several other related protocols.

The Application Program Interface (API) server116receives and transmits message data (e.g., commands and message payloads) between the client device102and the application servers114. Specifically, the Application Program Interface (API) server116provides a set of interfaces (e.g., routines and protocols) that can be called or queried by the messaging client104in order to invoke functionality of the application servers114. The Application Program Interface (API) server116exposes various functions supported by the application servers114, including account registration, login functionality, the sending of messages, via the application servers114, from a particular messaging client104to another messaging client104, the sending of media files (e.g., images or video) from a messaging client104to a messaging server118, and for possible access by another messaging client104, the settings of a collection of media data (e.g., story), the retrieval of a list of friends of a user of a client device102, the retrieval of such collections, 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 messaging client104).

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

The application servers114also include an image processing server122that is dedicated to performing various image processing operations, typically with respect to images or video within the payload of a message sent from or received at the messaging server118.

The social network server124supports various social networking functions and services and makes these functions and services available to the messaging server118. To this end, the social network server124maintains and accesses an entity graph308(as shown inFIG.3) within the database126. Examples of functions and services supported by the social network server124include the identification of other users of the messaging system100with which a particular user has relationships or is “following,” and also the identification of other entities and interests of a particular user.

Returning to the messaging client104, features and functions of an external resource (e.g., an application106or applet) are made available to a user via an interface of the messaging client104. In this context, “external” refers to the fact that the application106or applet is external to the messaging client104. The external resource is often provided by a third party but may also be provided by the creator or provider of the messaging client104. The messaging client104receives a user selection of an option to launch or access features of such an external resource. The external resource may be the application106installed on the client device102(e.g., a “native app”), or a small-scale version of the application (e.g., an “applet”) that is hosted on the client device102or remote of the client device102(e.g., on third-party servers110). 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 messaging client104. 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 messaging client104determines whether the selected external resource is a web-based external resource or a locally-installed application106. In some cases, applications106that are locally installed on the client device102can be launched independently of and separately from the messaging client104, such as by selecting an icon, corresponding to the application106, on a home screen of the client device102. Small-scale versions of such applications can be launched or accessed via the messaging client104and, in some examples, no or limited portions of the small-scale application can be accessed outside of the messaging client104. The small-scale application can be launched by the messaging client104receiving, from a third-party server110for 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 application106, the messaging client104instructs the client device102to 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 messaging client104communicates with the third-party servers110(for example) to obtain a markup-language document corresponding to the selected external resource. The messaging client104then processes the obtained markup-language document to present the web-based external resource within a user interface of the messaging client104.

The messaging client104can notify a user of the client device102, or other users related to such a user (e.g., “friends”), of activity taking place in one or more external resources. For example, the messaging client104can provide participants in a conversation (e.g., a chat session) in the messaging client104with 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 messaging clients104, 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 messaging client104. The external resource can selectively include different media items in the responses, based on a current context of the external resource.

The messaging client104can present a list of the available external resources (e.g., applications106or 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 application106(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.2is a block diagram illustrating further details regarding the messaging system100, according to some examples. Specifically, the messaging system100is shown to comprise the messaging client104and the application servers114. The messaging system100embodies a number of subsystems, which are supported on the client-side by the messaging client104and on the server-side by the application servers114. These subsystems include, for example, an ephemeral timer system202, a collection management system204, an augmentation system208, a map system210, a game system212, and an external resource system214.

The ephemeral timer system202is responsible for enforcing the temporary or time-limited access to content by the messaging client104and the messaging server118. The ephemeral timer system202incorporates a number of timers 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 messaging client104. Further details regarding the operation of the ephemeral timer system202are provided below.

The collection management system204is 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 system204may also be responsible for publishing an icon that provides notification of the existence of a particular collection to the user interface of the messaging client104.

The collection management system204furthermore includes a curation interface206that allows a collection manager to manage and curate a particular collection of content. For example, the curation interface206enables 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 system204employs 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 system204operates to automatically make payments to such users for the use of their content.

The augmentation system208provides 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 augmentation system208provides functions related to the generation and publishing of media overlays for messages processed by the messaging system100. The augmentation system208operatively supplies a media overlay or augmentation (e.g., an image filter) to the messaging client104based on a geolocation of the client device102. In another example, the augmentation system208operatively supplies a media overlay to the messaging client104based on other information, such as social network information of the user of the client device102. 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 the client device102. For example, the media overlay may include text or image that can be overlaid on top of a photograph taken by the client device102. In another example, the media overlay includes an identification of a location overlay (e.g., Venice beach), a name of a live event, or a name of a merchant overlay (e.g., Beach Coffee House). In another example, the augmentation system208uses the geolocation of the client device102to identify a media overlay that includes the name of a merchant at the geolocation of the client device102. The media overlay may include other indicia associated with the merchant. The media overlays may be stored in the database126and accessed through the database server120.

In some examples, the augmentation system208provides 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 augmentation system208generates a media overlay that includes the uploaded content and associates the uploaded content with the selected geolocation.

In other examples, the augmentation system208provides 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 augmentation system208associates the media overlay of the highest bidding merchant with a corresponding geolocation for a predefined amount of time.

The map system210provides various geographic location functions, and supports the presentation of map-based media content and messages by the messaging client104. For example, the map system210enables the display of user icons or avatars (e.g., stored in profile data316) 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 messaging system100from 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 messaging client104. A user can furthermore share his or her location and status information (e.g., using an appropriate status avatar) with other users of the messaging system100via the messaging client104, with this location and status information being similarly displayed within the context of a map interface of the messaging client104to selected users.

The game system212provides various gaming functions within the context of the messaging client104. The messaging client104provides a game interface providing a list of available games that can be launched by a user within the context of the messaging client104, and played with other users of the messaging system100. The messaging system100further 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 messaging client104. The messaging client104also supports both the voice 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).

The external resource system214provides an interface for the messaging client104to communicate with remote servers (e.g., third-party servers110) to launch or access external resources, i.e., applications or applets. Each third-party server110hosts, 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 messaging client104may launches a web-based resource (e.g., application) by accessing the HTML5 file from the third-party servers110associated with the web-based resource. In certain examples, applications hosted by third-party servers110are programmed in JavaScript leveraging a Software Development Kit (SDK) provided by the messaging server118. The SDK includes Application Programming Interfaces (APIs) with functions that can be called or invoked by the web-based application. In certain examples, the messaging server118includes a JavaScript library that provides a given external resource access to certain user data of the messaging client104. 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 server110from the messaging server118or is otherwise received by the third-party server110. 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 messaging client104into the web-based resource.

The SDK stored on the messaging server118effectively provides the bridge between an external resource (e.g., applications106or applets and the messaging client104. This provides the user with a seamless experience of communicating with other users on the messaging client104, while also preserving the look and feel of the messaging client104. To bridge communications between an external resource and a messaging client104, in certain examples, the SDK facilitates communication between third-party servers110and the messaging client104. In certain examples, a Web ViewJavaScriptBridge running on a client device102establishes two one-way communication channels between an external resource and the messaging client104. Messages are sent between the external resource and the messaging client104via 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 messaging client104is shared with third-party servers110. The SDK limits which information is shared based on the needs of the external resource. In certain examples, each third-party server110provides an HTML5 file corresponding to the web-based external resource to the messaging server118. The messaging server118can add a visual representation (such as a box art or other graphic) of the web-based external resource in the messaging client104. Once the user selects the visual representation or instructs the messaging client104through a GUI of the messaging client104to access features of the web-based external resource, the messaging client104obtains the HTML5 file and instantiates the resources necessary to access the features of the web-based external resource.

The messaging client104presents 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 messaging client104determines whether the launched external resource has been previously authorized to access user data of the messaging client104. In response to determining that the launched external resource has been previously authorized to access user data of the messaging client104, the messaging client104presents 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 messaging client104, after a threshold period of time (e.g., 3 seconds) of displaying the landing page or title screen of the external resource, the messaging client104slides 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 messaging client104adds the external resource to a list of authorized external resources and allows the external resource to access user data from the messaging client104. In some examples, the external resource is authorized by the messaging client104to access the user data in accordance with an OAuth 2 framework.

The messaging client104controls 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 application106) 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.

Data Architecture

FIG.3is a schematic diagram illustrating data structures300, which may be stored in the database126of the messaging server system108, according to certain examples. While the content of the database126is 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 database126includes message data stored within a message table302. 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 table302is described below with reference toFIG.4.

An entity table306stores entity data, and is linked (e.g., referentially) to an entity graph308and profile data316. Entities for which records are maintained within the entity table306may include individuals, corporate entities, organizations, objects, places, events, and so forth. Regardless of entity type, any entity regarding which the messaging server system108stores 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 graph308stores 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 data316stores multiple types of profile data about a particular entity. The profile data316may be selectively used and presented to other users of the messaging system100, based on privacy settings specified by a particular entity. Where the entity is an individual, the profile data316includes, 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 messaging system100, and on map interfaces displayed by messaging clients104to 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 data316for 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 database126also stores augmentation data, such as overlays or filters, in an augmentation table310. The augmentation data is associated with and applied to videos (for which data is stored in a video table304) and images (for which data is stored in an image table312).

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 messaging client104when 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 messaging client104, based on geolocation information determined by a Global Positioning System (GPS) unit of the client device102.

Another type of filter is a data filter, which may be selectively presented to a sending user by the messaging client104, based on other inputs or information gathered by the client device102during 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 device102, or the current time.

Other augmentation data that may be stored within the image table312includes 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 a client device102and then displayed on a screen of the client device102with 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 device102with 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 device102would 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 device102) and perform complex image manipulations locally on the client device102while 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 device102.

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 a client device102having a neural network operating as part of a messaging client104operating on the client device102. The transformation system operating within the messaging client104determines 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 device102as 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 table314stores 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 table306). 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 messaging client104may 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 messaging client104, to contribute content to a particular live story. The live story may be identified to the user by the messaging client104, 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 device102is 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 table304stores video data that, in one example, is associated with messages for which records are maintained within the message table302. Similarly, the image table312stores image data associated with messages for which message data is stored in the entity table306. The entity table306may associate various augmentations from the augmentation table310with various images and videos stored in the image table312and the video table304.

Data Communications Architecture

FIG.4is a schematic diagram illustrating a structure of a message400, according to some examples, generated by a messaging client104for communication to a further messaging client104or the messaging server118. The content of a particular message400is used to populate the message table302stored within the database126, accessible by the messaging server118. Similarly, the content of a message400is stored in memory as “in-transit” or “in-flight” data of the client device102or the application servers114. A message400is shown to include the following example components:message identifier402: a unique identifier that identifies the message400.message text payload404: text, to be generated by a user via a user interface of the client device102, and that is included in the message400.message image payload406: image data, captured by a camera component of a client device102or retrieved from a memory component of a client device102, and that is included in the message400. Image data for a sent or received message400may be stored in the image table312.message video payload408: video data, captured by a camera component or retrieved from a memory component of the client device102, and that is included in the message400. Video data for a sent or received message400may be stored in the video table304.message audio payload410: audio data, captured by a microphone or retrieved from a memory component of the client device102, and that is included in the message400.message augmentation data412: augmentation data (e.g., filters, stickers, or other annotations or enhancements) that represents augmentations to be applied to message image payload406, message video payload408, or message audio payload410of the message400. Augmentation data for a sent or received message400may be stored in the augmentation table310.message duration parameter414: parameter value indicating, in seconds, the amount of time for which content of the message (e.g., the message image payload406, message video payload408, message audio payload410) is to be presented or made accessible to a user via the messaging client104.message geolocation parameter416: geolocation data (e.g., latitudinal and longitudinal coordinates) associated with the content payload of the message. Multiple message geolocation parameter416values 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 payload406, or a specific video in the message video payload408).message story identifier418: identifier values identifying one or more content collections (e.g., “stories” identified in the story table314) with which a particular content item in the message image payload406of the message400is associated. For example, multiple images within the message image payload406may each be associated with multiple content collections using identifier values.message tag420: each message400may 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 payload406depicts an animal (e.g., a lion), a tag value may be included within the message tag420that 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 identifier422: an identifier (e.g., a messaging system identifier, email address, or device identifier) indicative of a user of the Client device102on which the message400was generated and from which the message400was sent.message receiver identifier424: an identifier (e.g., a messaging system identifier, email address, or device identifier) indicative of a user of the client device102to which the message400is addressed.

The contents (e.g., values) of the various components of message400may be pointers to locations in tables within which content data values are stored. For example, an image value in the message image payload406may be a pointer to (or address of) a location within an image table312. Similarly, values within the message video payload408may point to data stored within a video table304, values stored within the message augmentations412may point to data stored in an augmentation table310, values stored within the message story identifier418may point to data stored in a story table314, and values stored within the message sender identifier422and the message receiver identifier424may point to user records stored within an entity table306.

Real-Time Communication Interface with Haptic Feedback Response

FIG.5illustrates a system500in which a real-time video communication interface with a haptic response can be implemented, in accordance with some examples.

As shown inFIG.5, the system500can comprise a plurality of the client devices102. Each of the client devices102comprises a user interface (e.g., a display device or a touch screen) to receive touch inputs from the users. While not shown, the system500can also comprise a server (e.g., messaging server system108inFIG.1).

FIG.6illustrates the details of one of the client devices102in the system500according to one example embodiment. It is understood that the client devices102in the system500can comprise similar elements that are illustrated inFIG.6. The client devices102can be the machines1100as illustrated inFIG.11.

As shown inFIG.6, the client device102comprises a housing604, a camera602with a camera opening, a microphone606, and display device608. While not shown inFIG.6, the client device102can also comprise a camera lens, a camera image sensor, a processor, a memory, and a communication interface.

In one embodiment, the camera opening is an opening in the housing604that couples to a camera lens of the camera602included in the client device102. In one embodiment, the camera opening can be a window allowing the camera lens to capture image or video content (e.g., media content items). The camera602can include the camera lens and an image sensor. The camera lens may be a perspective camera lens or a non-perspective camera lens. A non-perspective camera lens may be, for example, a fisheye lens, a wide-angle lens, an omnidirectional lens, or the like. The image sensor captures images or digital video through the camera lens. The images may be also be a still image frame or a video including a plurality of still image frames.

In one example, the microphone606(or plurality of microphones) can be air interface sound pickup devices that convert sound into an electrical signal. More specifically, the microphones are transducers that convert acoustic pressure into electrical signals (e.g., acoustic signals). Microphones can be digital or analog microelectro-mechanical systems (MEMS) microphones. The acoustic signals generated by the microphone606can be pulse density modulation (PDM) signals.

The display device608that is included in the client device102can be a touch screen. The display device608can display user interfaces and communication interfaces, as discussed herein.

The user can interact with the display device608by touching a location on the display device608. The user can interact with the display device608by performing an engagement with the display device608. Examples of engagements with the display device608including a single tap, press, or touch on a location on the display device608, double tap or press the location of the display device608, pressing and holding contact with the display device608for a period of time. In one example, the user can also draw a drawing input (e.g., line, a pattern, or a portion of a doodle or drawing) by touching the display device608at a start location on the display device608, maintaining contact with the display device608while drawing the drawing input and releasing the display device608at an end location on the display device608to finish the drawing input.

As shown inFIG.5, the system500can comprise a first client device102and a second client device102. When a communication session between the first client device102and the second client device102is established, the system500causes a communication interface for the communication session to be displayed on the display devices608of the first client device102and the second client device102. The communication session can be a video communication session between the first and second client devices102. In one example, the video communication session is in real-time. In one example, the communication session is an electronic messaging communication session (e.g., electronic chat or instant messaging).

In one example, the system500detects a first touch input on the display device608of the first client device102and a second touch input on the display device608of the second client device102. The system500monitors a location of the first touch input and a location of the second touch input. The system500determines a distance between the location of the first touch input on the display device608of the first client device102and a location on the display device608of the first client device102corresponding to the location of the second touch input on the display device608of the second client device102.

The system500can cause the display devices608of the first and second client devices102to generate a haptic feedback response based on the distance. In one example, the haptic feedback response increases in intensity or speed as the distance decreases and decreases in intensity or speed as the distance increases.

Accordingly, the haptic feedback response is based on the users' touch inputs on their respective client devices102being synchronized in time and location. The changes intensity (or strength) or the speed of the haptic feedback response being generated further guide the users to the locations on the screen the other user is touching.

FIG.7illustrates the details of a client device102that is a head-wearable apparatus700according to one example embodiment.FIG.7illustrates a perspective view of the head-wearable apparatus700according to one example embodiment. InFIG.7, the head-wearable apparatus700is a pair of eyeglasses. In some embodiments, the head-wearable apparatus700can be sunglasses or goggles. Some embodiments can include one or more wearable devices, such as a pendant with an integrated camera that is integrated with, in communication with, or coupled to, the head-wearable apparatus700or a client device102. Any desired wearable device may be used in conjunction with the embodiments of the present disclosure, such as a watch, a headset, a wristband, earbuds, clothing (such as a hat or jacket with integrated electronics), a clip-on electronic device, or any other wearable devices. It is understood that, while not shown, one or more portions of the system included in the head-wearable apparatus700can be included in a client device102(e.g., machine1100inFIG.11) that can be used in conjunction with the head-wearable apparatus700.

InFIG.7, the head-wearable apparatus700is a pair of eyeglasses that includes a frame706that includes eye wires (or rims) that are coupled to two stems (or temples), respectively, via hinges and/or end pieces. The eye wires of the frame706carry or hold a pair of lenses (e.g., lens708aand lens708b). The frame706includes a first (e.g., right) side that is coupled to the first stem and a second (e.g., left) side that is coupled to the second stem. The first side is opposite the second side of the frame706.

The head-wearable apparatus700further includes a camera module (not shown) that includes camera lenses (e.g., camera lens704a, camera lens704b) and at least one image sensor. The camera lens704aand camera lens704bmay be a perspective camera lens or a non-perspective camera lens. A non-perspective camera lens may be, for example, a fisheye lens, a wide-angle lens, an omnidirectional lens, etc. The image sensor captures digital video through the camera lens704aand camera lens704b. The images may be also be still image frame or a video including a plurality of still image frames. The camera module can be coupled to the frame706. As shown inFIG.7, the frame706is coupled to the camera lens704aand camera lens704bsuch that the camera lenses (e.g., camera lens704a, camera lens704b) face forward. The camera lens704aand camera lens704bcan be perpendicular to the lens708aand lens708b. The camera module can include dual-front facing cameras that are separated by the width of the frame706or the width of the head of the user of the head-wearable apparatus700.

InFIG.7, the two stems (or temples) are respectively coupled to microphone housing702aand microphone housing702b. The first and second stems are coupled to opposite sides of a frame706of the head-wearable apparatus700. The first stem is coupled to the first microphone housing702aand the second stem is coupled to the second microphone housing702b. The microphone housing702aand microphone housing702bcan be coupled to the stems between the locations of the frame706and the temple tips. The microphone housing702aand microphone housing702bcan be located on either side of the user's temples when the user is wearing the head-wearable apparatus700.

As shown inFIG.7, the microphone housing702aand microphone housing702bencase a plurality of microphones (not shown) including microphone606. Microphone606can be one or more microphones. The microphones are air interface sound pickup devices that convert sound into an electrical signal. More specifically, the microphones are transducers that convert acoustic pressure into electrical signals (e.g., acoustic signals). Microphones can be digital or analog microelectro-mechanical systems (MEMS) microphones. The acoustic signals generated by the microphones can be pulse density modulation (PDM) signals.

In one embodiment, the pair of lenses (e.g., lens708aand lens708b) in the head-wearable apparatus700can further include a display device that can display the communication interface. In some examples, the head-wearable apparatus700can be virtual reality (VR) googles.

Some embodiments may include one or more wearable devices, such as gloves having the capability to provide haptics feedback, that is integrated with, in communication with, or coupled to, the client device102. Any desired wearable device may be used in conjunction with the embodiments of the present disclosure, such as a watch, eyeglasses, goggles, virtual reality (VR) googles, a headset, a wristband, earbuds, clothing (such as a hat or jacket with integrated electronics), a clip-on electronic device, or any other wearable devices.

FIG.8A,FIG.8B, andFIG.8Cillustrate examples of a communication interface being displayed on a first user interface802of the first client device102according to one example embodiment. It is understood that the communication interface displayed on a second user interface802of the second client device102can include similar elements.

In the examples illustrated inFIG.8A,FIG.8B, andFIG.8C, the communication session is a real-time video communication session between the first user of the first client device102and the second user of the second client device102. On the first user interface802, a real-time image of the second user is displayed. Similarly, the second user interface802can display a real-time image of the first user during the communication session.

The first user of the first client device102and the second user of the second client device102are present in the communication session. In other words, both users have the communication interface displayed on their client devices102such that they are present or active in the communication session.

In one example, a processor in the system500detects a first touch input on the first user interface and a second touch input on the second user interface. The processor can monitor a location of the first touch input on the first user interface802and a location of the second touch input on the second user interface802.

As illustrated inFIG.8A,FIG.8B, andFIG.8C, the communication interface displayed on a first user interface802can comprise a first indicator element804and a second indicator element806. The processor can cause the first user interface802to display the first indicator element804at the location of the first touch input and a second indicator element806at the location on the first user interface802corresponding to the location of the second touch input on the second user interface802. Similarly, the processor can cause the second user interface802to display the first indicator element804at the location of the second touch input and the second indicator element806at the location on the second user interface802corresponding to the location of the first touch input on the first user interface802.

As shown inFIG.8A,FIG.8B, andFIG.8C, the distance between the first indicator element804and the second indicator element806on the first user interface802is larger inFIG.8A, decreases inFIG.8B, and decreases again inFIG.8C.

The processor can determine a distance between the location of the first touch input on the first user interface802(e.g., the location of the first indicator element804) and a location on the first user interface802corresponding to the location of the second touch input on the second user interface802(e.g., the location of the second indicator element806).

The processor can cause the first user interface802and the second user interface802to generate a haptic feedback response based on the distance. In one example, the haptic feedback response increases in intensity or speed as the distance decreases and decreases in intensity or speed as the distance increases.

In one example, the processor can determine whether the distance is below a predetermined threshold. If the distance is below a predetermined threshold, the users' touch inputs on their respective client devices102are determined to be synchronized in time and location. In response to determining that the distance is below a predetermined threshold, the processor can cause the first user interface802and the second user interface802to generate a reward haptic feedback response. In one example, the reward haptic response is different from the haptic feedback response to indicate that that the users are synchronized in their touch inputs. In other words, the users are provided the reward haptic response when the users are simultaneously touching the same corresponding locations on their client devices102.

In one example, the haptic feedback response comprises a first vibration pattern and the reward haptic feedback response comprises a second vibration pattern that is different from the first vibration pattern. The reward haptic feedback response can be a stronger (or more intense) vibration pattern or a faster vibration pattern. In one example, the haptic feedback response can be a vibration pattern that simulates a heartbeat. The heartbeat can be a light heart beat that gets stronger as the distance decreases (e.g., the first and second touch inputs are getting closer) or can be a strong heartbeat that gets lighter as the distance increases (e.g., the first and second touch inputs are getting farther apart).

In response to determining that the distance is below the predetermined threshold, in one example, the processor causes the first user interface802and the second user interface802to generate an augmentation808to the communication interface as shown inFIG.8C. The augmentation808can comprise an overlay, a visual effect, an animation, a sound effect, or any combination thereof. In one example, the augmentation808is generated temporarily for a predetermined period of time.

FIG.9illustrates an example of a communication interface being displayed on a first user interface902of the first client device102according to one example embodiment. InFIG.9, the communication session is an electronic messaging communication session.

As shown in inFIG.9, the user interface902comprises an electronic message display portion904and a tactile portion906. The electronic message display portion904comprises the electronic messages that were inputted by the first user on the first client device102or received by the first client device102from the second client device102. A processor of the system500(e.g., processor in messaging server system108or client devices102) receives content for an electronic message from the first client device102or the second client device102. For example, the electronic message can be inputted by a first user via a user interface902of the first client device. Alternatively, the electronic message can be inputted by a second user via a user interface902of the second client device102. In one embodiment, the first user of the first client device102and the second user of the second client device102are present during the communication session. Users that are present in the communication session have the communication interfaces actively displayed on their respective client devices102. These users that are present are respectively able to view the messages being displayed on the communication interfaces as well as enter content for electronic messages on the communication interfaces. In one embodiment, the content for the electronic message can include a UNICODE character or text. The electronic message can include emoji characters/icons defined by the UNICODE standard. In one embodiment, the content of the electronic message can include images, customized graphics (e.g., avatars) or video. As used herein, an “electronic message” may refer to any message in electronic form, such as an email, a short message service (SMS) message, a multimedia message service (MMS) message, an instant message (IM), Internet Relay Chat (IRC) messages, as well as any other form of real-time, near-real-time, synchronous, or asynchronous electronic messaging format.

In one embodiment, the first user can also transmit via the user interface902a media content item (e.g., picture or video). As shown inFIG.9, a confirmation element914is displayed in the electronic message display portion904corresponding to the media content items that are delivered to the second user. As shown inFIG.9, a selectable element916can be displayed in electronic message display portion904to indicate to the first user that a media content item is received from the second user. Upon activation of the selectable element916via the first user interface902, the processor can cause the media content item that is received to be displayed by the first client device102.

The user interface902further comprises chat presence bar912that includes presence indicators associated with users of the client devices, respectively. In one embodiment, when a user is present in the communication session, an avatar associated with the user may be displayed in the chat presence bar912as a presence indicator for the user. Specifically, when the first user is present in the communication session, the first user's presence indicator in the chat presence bar912included in the user interface902displayed on the second client device102includes the first user's avatar. Similarly, when the second user is present in the communication session, the second user's presence indicator in the chat presence bar912included in the user interface902displayed on the first client device102includes the second user's avatar.

The tactile portion906of the user interface902is an area for the first and second users to touch and receive haptic feedback responses. The haptic feedback response can be based on the users' touch inputs on their respective client devices102being synchronized in time and location. The changes intensity (or strength) or the speed of the haptic feedback response being generated further guide the users to the locations on the screen the other user is touching.

In one example, a processor in the system500detects a first touch input on the first user interface902and a second touch input on the second user interface902. The processor can monitor a location of the first touch input on the first user interface902and a location of the second touch input on the second user interface902.

Similar toFIG.8A,FIG.8B, andFIG.8C, inFIG.9, the communication interface displayed on a first user interface902can comprise a first indicator element908and a second indicator element910. The processor can cause the first user interface902to display the first indicator element908at the location of the first touch input and a second indicator element910at the location on the first user interface902corresponding to the location of the second touch input on the second user interface902. Similarly, the processor can cause the second user interface902to display the first indicator element908at the location of the second touch input and the second indicator element910at the location on the second user interface902corresponding to the location of the first touch input on the first user interface802.

The processor can determine a distance between the location of the first touch input on the first user interface902(e.g., the location of the first indicator element908) and a location on the first user interface902corresponding to the location of the second touch input on the second user interface902(e.g., the location of the second indicator element910).

The processor can cause the first user interface902and the second user interface902to generate a haptic feedback response based on the distance. In one example, the haptic feedback response increases in intensity or speed as the distance decreases and decreases in intensity or speed as the distance increases.

In one example, the processor can determine whether the distance is below a predetermined threshold. If the distance is below a predetermined threshold, the users' touch inputs on their respective client devices102are determined to be synchronized in time and location. In response to determining that the distance is below a predetermined threshold, the processor can cause the first user interface902and the second user interface902to generate a reward haptic feedback response. In one example, the reward haptic response is different from the haptic feedback response to indicate that that the users are synchronized in their touch inputs. In other words, the users are provided the reward haptic response when the users are simultaneously touching the same corresponding locations on their client devices102.

In one example, the haptic feedback response comprises a first vibration pattern and the reward haptic feedback response comprises a second vibration pattern that is different from the first vibration pattern. The reward haptic feedback response can be a stronger (or more intense) vibration pattern or a faster vibration pattern. In one example, the haptic feedback response can be a vibration pattern that simulates a heartbeat. The heart beat can be a light heart beat that gets stronger as the distance decreases (e.g., the first and second touch inputs are getting closer) or can be a strong heart beat that gets lighter as the distance increases (e.g., the first and second touch inputs are getting farther apart).

In response to determining that the distance is below the predetermined threshold, in one example, the processor causes the first user interface902and the second user interface902to generate an augmentation (not shown) to the communication interface. The augmentation can comprise an overlay, a visual effect, an animation, a sound effect, or any combination thereof. In one example, the augmentation is generated temporarily for a predetermined period of time.

Although the described flowcharts can show operations as a sequential process, many of the operations can be performed in parallel or concurrently. In addition, the order of the operations may be re-arranged. A process is terminated when its operations are completed. A process may correspond to a method, a procedure, an algorithm, etc. The operations of methods may be performed in whole or in part, may be performed in conjunction with some or all of the operations in other methods, and may be performed by any number of different systems, such as the systems described herein, or any portion thereof, such as a processor included in any of the systems.

Generating Haptic Feedback Responses on an Electronic Messaging Communication Interface

FIG.10is a flowchart for a process1000to generate haptic feedback responses on an electronic messaging communication interface, in accordance with some examples.

At operation1002, a processor of the system500(e.g., messaging server system108and/or client device102) causes a communication interface for a communication session to be displayed on a first user interface of a first client device and on a second user interface of a second client device. The communication session is between a plurality of client devices including the first client device and the second client device. In one example, a first user of the first client device and a second user of the second client device are present in the communication session. In one example, the communication interface comprises a tactile portion

At operation1004, the processor detects a first touch input on the tactile portion of the first user interface and a second touch input on the tactile portion of the second user interface.

At operation1006, the processor monitors a location of the first touch input on the first user interface and a location of the second touch input on the second user interface.

The processor, at operation1008, determines a distance between the location of the first touch input on the first user interface and a location on the first user interface corresponding to the location of the second touch input on the second user interface.

At operation1010, the processor causing the first user interface and the second user interface to generate a haptic feedback response based on the distance. In one example, the haptic feedback response increases in intensity or speed as the distance decreases and decreases in intensity or speed as the distance increases.

In one example, in response to determining that the distance is below a predetermined threshold, the processor causes the first user interface and the second user interface to generate a reward haptic feedback response. The reward haptic response can be different from the haptic feedback response. The haptic feedback response can comprise a first vibration pattern and the reward haptic feedback response can comprise a second vibration pattern that is different from the first vibration pattern. In response to determining that the distance is below the predetermined threshold, the processor can cause the first user interface and the second user interface to generate an augmentation to the communication interface.

Machine Architecture

FIG.11is a diagrammatic representation of the machine1100within which instructions1110(e.g., software, a program, an application, an applet, an app, or other executable code) for causing the machine1100to perform any one or more of the methodologies discussed herein may be executed. For example, the instructions1110may cause the machine1100to execute any one or more of the methods described herein. The instructions1110transform the general, non-programmed machine1100into a particular machine1100programmed to carry out the described and illustrated functions in the manner described. The machine1100may operate as a standalone device or may be coupled (e.g., networked) to other machines. In a networked deployment, the machine1100may 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 machine1100may 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 instructions1110, sequentially or otherwise, that specify actions to be taken by the machine1100. Further, while only a single machine1100is illustrated, the term “machine” shall also be taken to include a collection of machines that individually or jointly execute the instructions1110to perform any one or more of the methodologies discussed herein. The machine1100, for example, may comprise the client device102or any one of a number of server devices forming part of the messaging server system108. In some examples, the machine1100may 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 machine1100may include processors1104, memory1106, and input/output I/O components1102, which may be configured to communicate with each other via a bus1140. In an example, the processors1104(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 processor1108and a processor1112that execute the instructions1110. 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.11shows multiple processors1104, the machine1100may 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 memory1106includes a main memory1114, a static memory1116, and a storage unit1118, both accessible to the processors1104via the bus1140. The main memory1106, the static memory1116, and storage unit1118store the instructions1110embodying any one or more of the methodologies or functions described herein. The instructions1110may also reside, completely or partially, within the main memory1114, within the static memory1116, within machine-readable medium1120within the storage unit1118, within at least one of the processors1104(e.g., within the Processor's cache memory), or any suitable combination thereof, during execution thereof by the machine1100.

The I/O components1102may 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 components1102that 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 components1102may include many other components that are not shown inFIG.11. In various examples, the I/O components1102may include user output components1126and user input components1128. The user output components1126may 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 components1128may 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 components1102may include biometric components1130, motion components1132, environmental components1134, or position components1136, among a wide array of other components. For example, the biometric components1130include 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 components1132include acceleration sensor components (e.g., accelerometer), gravitation sensor components, rotation sensor components (e.g., gyroscope).

The environmental components1134include, 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 device102may have a camera system comprising, for example, front cameras on a front surface of the client device102and rear cameras on a rear surface of the client device102. The front cameras may, for example, be used to capture still images and video of a user of the client device102(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 device102may also include a 360° camera for capturing 360° photographs and videos.

Further, the camera system of a client device102may 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 device102. 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 components1136include 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 components1102further include communication components1138operable to couple the machine1100to a network1122or devices1124via respective coupling or connections. For example, the communication components1138may include a network interface Component or another suitable device to interface with the network1122. In further examples, the communication components1138may 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 devices1124may be another machine or any of a wide variety of peripheral devices (e.g., a peripheral device coupled via a USB).

Moreover, the communication components1138may detect identifiers or include components operable to detect identifiers. For example, the communication components1138may 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 components1138, 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 memory1114, static memory1116, and memory of the processors1104) and storage unit1118may 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 instructions1110), when executed by processors1104, cause various operations to implement the disclosed examples.

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

Software Architecture

FIG.12is a block diagram1200illustrating a software architecture1204, which can be installed on any one or more of the devices described herein. The software architecture1204is supported by hardware such as a machine1202that includes processors1220, memory1226, and I/O components1238. In this example, the software architecture1204can be conceptualized as a stack of layers, where each layer provides a particular functionality. The software architecture1204includes layers such as an operating system1212, libraries1210, frameworks1208, and applications1206. Operationally, the applications1206invoke API calls1250through the software stack and receive messages1252in response to the API calls1250.

The operating system1212manages hardware resources and provides common services. The operating system1212includes, for example, a kernel1214, services1216, and drivers1222. The kernel1214acts as an abstraction layer between the hardware and the other software layers. For example, the kernel1214provides memory management, processor management (e.g., scheduling), component management, networking, and security settings, among other functionalities. The services1216can provide other common services for the other software layers. The drivers1222are responsible for controlling or interfacing with the underlying hardware. For instance, the drivers1222can 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 libraries1210provide a common low-level infrastructure used by the applications1206. The libraries1210can include system libraries1218(e.g., C standard library) that provide functions such as memory allocation functions, string manipulation functions, mathematic functions, and the like. In addition, the libraries1210can include API libraries1224such 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 libraries1210can also include a wide variety of other libraries1228to provide many other APIs to the applications1206.

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

In an example, the applications1206may include a home application1236, a contacts application1230, a browser application1232, a book reader application1234, a location application1242, a media application1244, a messaging application1246, a game application1248, and a broad assortment of other applications such as a third-party application1240. The applications1206are programs that execute functions defined in the programs. Various programming languages can be employed to create one or more of the applications1206, 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 application1240(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 application1240can invoke the API calls1250provided by the operating system1212to facilitate functionality described herein.

System with Head-Wearable Apparatus

FIG.13illustrates a system1300in which the head-wearable apparatus700can be implemented according to one example embodiment.FIG.13is a high-level functional block diagram of an example head-wearable apparatus700communicatively coupled a mobile client device102and a server system1330via various network1336.

Head-wearable apparatus700includes a camera, such as at least one of visible light camera1310, infrared emitter1312and infrared camera1314. The camera can include the camera module with the camera lens704aand camera lens704binFIG.7.

Client device102can be capable of connecting with head-wearable apparatus700using both a low-power wireless connection1332and a high-speed wireless connection1334. Client device102is connected to server system1330and network1336. The network1336may include any combination of wired and wireless connections.

Head-wearable apparatus700further includes two image displays of the image display of optical assembly1302. The two image displays of optical assembly1302include one associated with the left lateral side and one associated with the right lateral side of the head-wearable apparatus700. Head-wearable apparatus700also includes image display driver1306, image processor1308, low-power low power circuitry1324, and high-speed circuitry1316. Image display of optical assembly1302are for presenting images and videos, including an image that can include a graphical user interface to a user of the head-wearable apparatus700.

Image display driver1306commands and controls the image display of the image display of optical assembly1302. Image display driver1306may deliver image data directly to the image display of the image display of optical assembly1302for presentation or may have to convert the image data into a signal or data format suitable for delivery to the image display device. For example, the image data may be video data formatted according to compression formats, such as H. 264 (MPEG-4 Part 10), HEVC, Theora, Dirac, RealVideo RV40, VP8, VP9, or the like, and still image data may be formatted according to compression formats such as Portable Network Group (PNG), Joint Photographic Experts Group (JPEG), Tagged Image File Format (TIFF) or exchangeable image file format (Exif) or the like.

As noted above, head-wearable apparatus700includes a frame706and stems (or temples) extending from a lateral side of the frame706. Head-wearable apparatus700further includes a user input device1304(e.g., touch sensor or push button) including an input surface on the head-wearable apparatus700. The user input device1304(e.g., touch sensor or push button) is to receive from the user an input selection to manipulate the graphical user interface of the presented image.

The components shown inFIG.13for the head-wearable apparatus700are located on one or more circuit boards, for example a PCB or flexible PCB, in the rims or temples. Alternatively, or additionally, the depicted components can be located in the chunks, frames, hinges, or bridge of the head-wearable apparatus700. Left and right visible light cameras1310can include digital camera elements such as a complementary metal-oxide-semiconductor (CMOS) image sensor, charge coupled device, a camera lens704aand camera lens704b, or any other respective visible or light capturing elements that may be used to capture data, including images of scenes with unknown objects.

Head-wearable apparatus700includes a memory1320which stores instructions to perform a subset or all of the functions described herein. Memory1320can also include storage device.

As shown inFIG.13, high-speed circuitry1316includes high-speed processor1318, memory1320, and high-speed wireless circuitry1322. In the example, the image display driver1306is coupled to the high-speed circuitry1316and operated by the high-speed processor1318in order to drive the left and right image displays of the image display of optical assembly1302. High-speed processor1318may be any processor capable of managing high-speed communications and operation of any general computing system needed for head-wearable apparatus700. High-speed processor1318includes processing resources needed for managing high-speed data transfers on high-speed wireless connection1334to a wireless local area network (WLAN) using high-speed wireless circuitry1322. In certain examples, the high-speed processor1318executes an operating system such as a LINUX operating system or other such operating system of the head-wearable apparatus700and the operating system is stored in memory1320for execution. In addition to any other responsibilities, the high-speed processor1318executing a software architecture for the head-wearable apparatus700is used to manage data transfers with high-speed wireless circuitry1322. In certain examples, high-speed wireless circuitry1322is configured to implement Institute of Electrical and Electronic Engineers (IEEE) 802.11 communication standards, also referred to herein as Wi-Fi. In other examples, other high-speed communications standards may be implemented by high-speed wireless circuitry1322.

Low-power wireless circuitry1328and the high-speed wireless circuitry1322of the head-wearable apparatus700can include short range transceivers (Bluetooth™) and wireless wide, local, or wide area network transceivers (e.g., cellular or WiFi). Client device102, including the transceivers communicating via the low-power wireless connection1332and high-speed wireless connection1334, may be implemented using details of the architecture of the head-wearable apparatus700, as can other elements of network1336.

Memory1320includes any storage device capable of storing various data and applications, including, among other things, camera data generated by the left and right visible light cameras1310, infrared camera1314, and the image processor1308, as well as images generated for display by the image display driver1306on the image displays of the image display of optical assembly1302. While memory1320is shown as integrated with high-speed circuitry1316, in other examples, memory1320may be an independent standalone element of the head-wearable apparatus700. In certain such examples, electrical routing lines may provide a connection through a chip that includes the high-speed processor1318from the image processor1308or low-power processor1326to the memory1320. In other examples, the high-speed processor1318may manage addressing of memory1320such that the low-power processor1326will boot the high-speed processor1318any time that a read or write operation involving memory1320is needed.

As shown inFIG.13, the low-power processor1326or high-speed processor1318of the head-wearable apparatus700can be coupled to the camera (visible light camera1310; infrared emitter1312, or infrared camera1314), the image display driver1306, the user input device1304(e.g., touch sensor or push button), and the memory1320.

Head-wearable apparatus700is connected with a host computer. For example, the head-wearable apparatus700is paired with the client device102via the high-speed wireless connection1334or connected to the server system1330via the network1336. Server system1330may be one or more computing devices as part of a service or network computing system, for example, that include a processor, a memory, and network communication interface to communicate over the network1336with the client device102and head-wearable apparatus700.

The client device102includes a processor and a network communication interface coupled to the processor. The network communication interface allows for communication over the network1336, low-power wireless connection1332or high-speed wireless connection1334. Client device102can further store at least portions of the instructions in the client device102's memory to implement the functionality described herein.

Output components of the head-wearable apparatus700include visual components, such as a display such as a liquid crystal display (LCD), a plasma display panel (PDP), a light emitting diode (LED) display, a projector, or a waveguide. The image displays of the optical assembly are driven by the image display driver1306. The output components of the head-wearable apparatus700further include acoustic components (e.g., speakers), haptic components (e.g., a vibratory motor), other signal generators, and so forth. The input components of the head-wearable apparatus700, the client device102, and server system1330, such as the user input device1304, may include alphanumeric input components (e.g., a keyboard, a touch screen configured to receive alphanumeric input, a photo-optical keyboard, or other alphanumeric input components), point-based input components (e.g., a mouse, a touchpad, a trackball, a joystick, a motion sensor, or other pointing instruments), 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.

Head-wearable apparatus700may optionally include additional peripheral device elements. Such peripheral device elements may include biometric sensors, additional sensors, or display elements integrated with head-wearable apparatus700. For example, peripheral device elements may include any I/O components including output components, motion components, position components, or any other such elements described herein.

For example, the biometric components include components to detect expressions (e.g., hand expressions, facial expressions, vocal expressions, body gestures, or eye tracking), measure biosignals (e.g., blood pressure, heart rate, body temperature, perspiration, or brain waves), identify a person (e.g., voice identification, retinal identification, facial identification, fingerprint identification, or electroencephalogram based identification), and the like. The motion components include acceleration sensor components (e.g., accelerometer), gravitation sensor components, rotation sensor components (e.g., gyroscope), and so forth. The position components include location sensor components to generate location coordinates (e.g., a Global Positioning System (GPS) receiver component), WiFi or Bluetooth™ transceivers to generate positioning system coordinates, 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. Such positioning system coordinates can also be received over low-power wireless connections1332and high-speed wireless connection1334from the client device102via the low-power wireless circuitry1328or high-speed wireless circuitry1322.

Where a phrase similar to “at least one of A, B, or C,” “at least one of A, B, and C,” “one or more A, B, or C,” or “one or more of A, B, and C” is used, it is intended that the phrase be interpreted to mean that A alone may be present in an embodiment, B alone may be present in an embodiment, C alone may be present in an embodiment, or that any combination of the elements A, B and C may be present in a single embodiment; for example, A and B, A and C, B and C, or A and B and C.

Changes and modifications may be made to the disclosed embodiments without departing from the scope of the present disclosure. These and other changes or modifications are intended to be included within the scope of the present disclosure, as expressed in the following 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 processors or 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.