Selecting color values for ar-based makeup

Abstract

Aspects of the disclosure relate to systems including computer-readable storage media storing programs and methods for providing makeup-based augmented reality content. The programs and methods cause receiving a request to present augmented reality content in association with a captured image depicting a user's face; accessing an augmented reality content item associated with applying makeup to the face and configured to generate a mesh for tracking a plurality of regions of the face; receiving user input selecting a region; determining at least one of a range of color values or a range of contrast values related to available makeup products for the selected region; and presenting, in association with the face, an interface element for user selection of at least one of a color value within the range of color values or a contrast value within the range of contrast values.

Description

[0001] Cross-references to related applications

[0002] This patent application claims the benefit of U.S. Application Serial No. 17 / 394,095, filed August 4, 2021, and U.S. Provisional Patent Application No. 63 / 198,078, filed September 28, 2020, entitled “SELECTING COLOR VALUES FOR AUGMENTED REALITY-BASED MAKEUP,” which is incorporated herein by reference in its entirety. Technical Field

[0003] This disclosure generally relates to messaging systems that include providing augmented reality content along with captured images. Background Technology

[0004] A messaging system enables the exchange of message content between users. For example, a messaging system allows a user to exchange message content (e.g., text, images) with one or more other users. Attached Figure Description

[0005] In accompanying drawings that are not necessarily drawn to scale, the same reference numerals may describe similar parts in different views. For ease of identification of any particular element or action being discussed, one or more of the highest digits in the reference numerals indicate the drawing number in which the element was first introduced. Some non-limiting examples are shown in the figures of the accompanying drawings, in which:

[0006] Figure 1 It is a graphical representation of a networked environment in which the present disclosure can be deployed, based on some examples.

[0007] Figure 2 It is a graphical representation of a messaging system with both client-side and server-side functionalities, based on some examples.

[0008] Figure 3 It is a graphical representation based on examples such as data structures maintained in a database.

[0009] Figure 4 It is a graphical representation based on some example messages.

[0010] Figure 5 This is an interactive diagram illustrating a process for providing augmented reality-based makeup in a messaging system, according to some example implementations.

[0011] Figure 6A An example user interface with interface elements for selecting makeup color and contrast is shown according to some example implementations.

[0012] Figure 6B Another example user interface with interface elements for selecting makeup color and contrast, according to some example implementations, is shown.

[0013] Figure 6C Another example user interface with interface elements for selecting makeup color and contrast, according to some example implementations, is shown.

[0014] Figure 7A An example user interface is shown, according to some example implementations, in which a user provides touch input for changing the color of makeup.

[0015] Figure 7B An example user interface for changing makeup colors is shown, according to some example implementations.

[0016] Figure 8 This is a flowchart illustrating a process for providing augmented reality-based makeup in a messaging system, according to some example implementations.

[0017] Figure 9 This is a flowchart of an access restriction process based on some examples.

[0018] Figure 10 It is a graphical representation of a machine in the form of a computer system, based on some examples, within which a set of instructions can be executed to cause the machine to perform any or more of the methods discussed herein.

[0019] Figure 11 It is a block diagram showing a software architecture in which examples can be implemented. Detailed Implementation

[0020] Message sending and receiving systems typically allow users to exchange content items (e.g., messages, images, and / or videos) with each other in message threads. Message sending and receiving systems can be used to implement shopping systems for online purchase of goods and / or services, or otherwise integrate with shopping systems.

[0021] The disclosed embodiments provide a messaging client for presenting augmented reality content for trying out cosmetic products. The messaging client activates or otherwise accesses an augmented reality content item (e.g., corresponding to a camera lens or augmented reality experience) that generates a grid for tracking regions of a face depicted in a captured image. The augmented reality content item allows a user to select regions of the face and depicts a range of colors and contrasts corresponding to makeup that can be applied to the selected regions. The user can select specific colors and / or contrasts within the depicted range, and the messaging client renders the simulated makeup as an overlay on the facial regions. Additionally, cosmetic products matching the selected colors and / or contrasts can be presented along with shopping cart interface elements for addition to the user's shopping cart for final purchase.

[0022] Figure 1 This is a block diagram illustrating an example messaging system 100 for exchanging data (e.g., messages and associated content) over a network. The messaging system 100 includes multiple instances of client devices 102, each hosting several applications including a messaging client 104 and other applications 106. Each messaging client 104 is communicatively coupled via a network 112 (e.g., the Internet) to other instances of the messaging client 104 (e.g., hosted on corresponding other client devices 102), a messaging server system 108, and a third-party server 110. The messaging client 104 can also communicate with the local host applications 106 using an application programming interface (API).

[0023] The messaging client 104 can communicate and exchange data with other messaging clients 104 and messaging server system 108 via network 112. The data exchanged between messaging clients 104 and between messaging clients 104 and messaging server system 108 includes functions (e.g., commands for activating functions) and payload data (e.g., text, audio, video, or other multimedia data).

[0024] The message transceiver server system 108 provides server-side functionality to specific message transceiver clients 104 via network 112. While some functions of the message transceiver system 100 are described herein as being performed by either the message transceiver client 104 or the message transceiver server system 108, the location of certain functions within the message transceiver client 104 or the message transceiver server system 108 may be a design choice. For example, it may be technically preferred that certain technologies and functions are initially deployed within the message transceiver server system 108, but that technology and functions are later migrated to the message transceiver client 104 of the client device 102 with sufficient processing capabilities.

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

[0026] Specifically, turning to message transceiver server system 108, application programming interface (API) server 116 is coupled to application server 114 and provides a programming interface to application server 112. Application server 114 is communicatively coupled to database server 120, which facilitates access to database 126, which stores data associated with messages processed by application server 114. Similarly, web server 128 is coupled to application server 114 and provides a web-based interface to application server 114. For this purpose, web server 128 handles incoming network requests via Hypertext Transfer Protocol (HTTP) and several other related protocols.

[0027] Application Programming Interface (API) server 116 receives and sends message data (e.g., commands and message payloads) between client device 102 and application server 114. Specifically, API server 116 provides a set of interfaces (e.g., routines and protocols) that can be invoked or queried by message transceiver client 104 to activate the functionality of application server 114. Application Programming Interface (API) server 116 exposes various functions supported by application server 114, including: account registration; login functionality; sending messages from a specific messaging client 104 to another messaging client 104 via application server 114, sending media files (e.g., images or videos) from messaging client 104 to messaging server 118, and providing possible access for another messaging client 104; setting up collections of media data (e.g., stories); retrieving the friend list of the user of client device 102; retrieving such collections; retrieving messages and content; adding and deleting entities (e.g., friends) to an entity graph (e.g., a social graph); locating friends within the social graph; and opening application events (e.g., related to messaging client 104).

[0028] Application server 114 hosts several server applications and subsystems, including, for example, messaging server 118, image processing server 122, and social networking server 124. Messaging server 118 implements several messaging techniques and functions, particularly relating to the aggregation and other processing of content (e.g., text and multimedia content) included in messages received from multiple instances of messaging client 104. As will be described in further detail, text and media content from multiple sources can be aggregated into collections of content (e.g., referred to as stories or galleries). These collections are then made available to messaging client 104. Given the hardware requirements for additional processor- and memory-intensive processing of data, such processing can also be performed on the server side by messaging server 118.

[0029] Application server 114 also includes image processing server 122, which is dedicated to performing various image processing operations on images or videos typically within the payload of messages sent from or received at message server 114.

[0030] Social networking server 124 supports various social networking functions and services, and makes these functions and services available to messaging server 118. To this end, social networking server 124 maintains and accesses entity graph 304 (such as...) within database 126. Figure 3 (As shown). Examples of the functions and services supported by the social networking server 124 include identifying other users in the messaging system 100 who are related to a particular user or who are being "followed" by that particular user, and also identifying the interests and other entities of that particular user.

[0031] Returning to messaging client 104, the features and functionality of external resources (e.g., application 106 or applet) are available to the user via the interface of messaging client 104. In this context, "external" refers to the fact that application 106 or applet is outside of messaging client 104. External resources are typically provided by third parties, but may also be provided by the creator or provider of messaging client 104. Message client 104 receives user selections regarding options to launch or access the features of such external resources. External resources may be application 106 installed on client device 102 (e.g., a "native app"), or a smaller version (e.g., an "app") of an application hosted on client device 102 or located remotely on client device 102 (e.g., on a third-party server 110). A smaller version of an application includes a subset of the application's features and functionality (e.g., a full-scale, native version of the application) and is implemented using markup language documentation. In one example, a smaller version of the application (e.g., a “mini-application”) is a web-based markup language version of the application and is embedded in the messaging client 104. In addition to using markup language documents (e.g., .*ml files), mini-applications may also include scripting languages ​​(e.g., .*js files or .json files) and stylesheets (e.g., .*ss files).

[0032] In response to a user selection of an option to launch or access an external resource, messaging client 104 determines whether the selected external resource is a web-based external resource or a locally installed application 106. In some cases, application 106, locally installed on client device 102, can be launched independently of messaging client 104 and separately from it, for example, by selecting the icon corresponding to application 106 on the home screen of client device 102. A smaller version of such an application can be launched or accessed via messaging client 104, and in some examples, no part of the smaller application can be accessed (or only a limited part can) outside of messaging client 104. A smaller application can be launched by messaging client 104, for example, by receiving and processing markup language documents associated with the smaller application from a third-party server 110.

[0033] In response to determining that the external resource is a locally installed application 106, the messaging client 104 instructs the client device 102 to 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 client 104 communicates with a third-party server 110 (e.g.) to obtain a markup language document corresponding to the selected external resource. The messaging client 104 then processes the obtained markup language document to render the web-based external resource within the user interface of the messaging client 104.

[0034] The messaging client 104 can notify users of client device 102 or other users (e.g., "friends") associated with such users of one or more external resources. For example, the messaging client 104 can provide participants in a conversation (e.g., a chat session) within the messaging client 104 with notifications related to the current or recent use of external resources by one or more members of a group of users. One or more users can be invited to join a valid external resource or to activate a recently used but currently invalid external resource (within the group of friends). External resources can provide participants in the conversation, each using the corresponding messaging client 104, with the ability to share items, statuses, conditions, or locations within the external resource to the chat session with one or more members of a group of users. Shared items can be interactive chat cards that chat members can use to interact, for example, to activate the corresponding external resource, view specific information within the external resource, or take chat members to a specific location or status within the external resource. Within a given external resource, response messages can be sent to users on the messaging client 104. External resources can selectively include different media items in the response based on the current context of the external resources.

[0035] The messaging client 104 can present a list of available external resources (e.g., application 106 or applet) to the 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 applications 106 (or applets) can vary based on how the user launches the menu (e.g., from a conversational interface or a non-conversational interface).

[0036] Figure 2This is a block diagram illustrating further details of a messaging system 100 according to some examples. Specifically, the messaging system 100 is shown as including a messaging client 104 and an application server 114. The messaging system 100 includes several subsystems supported on the client side by the messaging client 104 and on the server side by the application server 114. These subsystems include, for example, a short-lived timer system 202, a collection management system 204, an enhancement system 208, a map system 210, an external resource system 212, and a shopping system 214.

[0037] The short-lived timer system 202 is responsible for enabling temporary or time-limited access to content by the message sending client 104 and the message sending server 118. The short-lived timer system 202 incorporates several timers that selectively enable access (e.g., for rendering and displaying) of messages and associated content via the message sending client 104 based on duration and display parameters associated with a message or set of messages (e.g., a story). Further details regarding the operation of the short-lived timer system 202 are provided below.

[0038] The collection management system 204 is responsible for managing media collections and sets (e.g., collections of text, image, video, and audio data). Collections of content (e.g., messages, including images, videos, text, and audio) can be organized into "event galleries" or "event stories." Such collections can be made available for a specified time period, such as the duration of an event related to the content. For example, content related to a concert can be made available as a "story" during the duration of the concert. The collection management system 204 can also be responsible for publishing icons that provide notifications of the existence of specific collections to the user interface of the messaging client 104.

[0039] Furthermore, the collection management system 204 includes a curation interface 206 that enables the collection manager to manage and curate collections of specific content. For example, the curation interface 206 allows an event organizer to curate collections of content related to a specific event (e.g., removing inappropriate content or redundant messages). Additionally, the collection management system 204 employs machine vision (or image recognition technology) and content rules to automatically curate content collections. In some examples, users may be compensated for including user-generated content in the collection. In such cases, the collection management system 204 operates to automatically pay such users for using their content.

[0040] Enhancement system 208 provides various functionalities that enable users to enhance (e.g., annotate or otherwise modify or edit) media content associated with messages. For example, enhancement system 208 provides functionality related to generating and publishing media overlays for messages processed by messaging system 100. Enhancement system 208 can operable to provide media overlays or enhancements (e.g., image filters) to messaging client 104 based on the geolocation of client device 102. In another example, enhancement system 208 can operable to provide media overlays to messaging client 104 based on other information such as the social network information of the user of client device 102. Media overlays can include audio and visual content as well as visual effects. Examples of audio and visual content include pictures, text, logos, animations, and sound effects. Examples of visual effects include color overlays. Audio and visual content or visual effects can be applied to media content items (e.g., photos) at client device 102. For example, media overlays can include text or images that can be overlaid on a photograph taken by client device 102. In another example, media overlays include location identifier overlays (e.g., Venice Beach), live event names, or business name overlays (e.g., Beach Cafe). In yet another example, enhancement system 208 uses the geolocation of client device 102 to identify media overlays that include the business name at the geolocation of client device 102. Media overlays may include additional tags associated with the business. Media overlays may be stored in database 126 and accessed through database server 120.

[0041] In some examples, enhancement system 208 provides a user-based publishing platform that allows users to select a geolocation on a map and upload content associated with that geolocation. Users can also specify the environment in which a particular media overlay should be provided to other users. Enhancement system 208 generates a media overlay that includes the uploaded content and associates the uploaded content with the selected geolocation.

[0042] In other examples, enhancement system 208 provides a merchant-based publishing platform that enables merchants to select specific media overlays associated with geolocation through bidding processes. For example, enhancement system 208 associates the media overlay of the highest bidder with a corresponding geolocation for a predefined amount of time.

[0043] In other examples, such as the following about Figure 3As discussed, augmentation system 208 enables the presentation of augmented reality content in association with images or videos captured by the camera device of client device 102. Augmentation system 208 may implement or otherwise access augmented reality content items (e.g., corresponding to application lenses or augmented reality experiences) to provide real-time effects and / or sound that can be added to the images or videos. To facilitate the presentation of augmented reality content, augmentation system 208 may implement or otherwise access object recognition algorithms (e.g., including machine learning algorithms) configured to scan images or videos and detect / track movement of objects within the images or videos.

[0044] Map system 210 provides various geolocation functions and supports the presentation of map-based media content and messages by messaging client 104. For example, map system 210 enables the display (e.g., stored in profile data 302) of user icons or avatars on a map to indicate the current or past locations of the user's "friends" and media content generated by these friends (e.g., a collection of messages including photos and videos) within the map context. For example, a message posted by a user from a specific geolocation to messaging system 100 can be displayed to a specific user's "friends" on the map interface of messaging client 104 within the context of that specific location on the map. The user can also share his or her location and status information with other users of messaging system 100 (e.g., using appropriate status avatars) via messaging client 104, where the location and status information is similarly displayed to selected users within the context of the map interface of messaging client 104.

[0045] External resource system 212 provides an interface for messaging client 104 to communicate with remote servers (e.g., third-party server 110) to launch or access external resources (i.e., applications or applets). Each third-party server 110, for example, hosts applications or applets based on markup languages ​​(e.g., HTML5) or smaller versions of applications (e.g., game applications, utility applications, payment applications, or ride-sharing applications). Messaging client 104 can launch web-based resources (e.g., applications) by accessing HTML5 files from the third-party server 110 associated with the web-based resource. In some examples, the application hosted by third-party server 110 is programmed in JavaScript using a software development kit (SDK) provided by messaging server 118. The SDK includes an application programming interface (API) with functionality that can be called or activated by the web-based application. In some examples, messaging server 118 includes a JavaScript library that provides access to a given external resource for some user data of messaging client 104. HTML5 is used as an example technology for programming games, but applications and resources programmed based on other technologies can be used.

[0046] To integrate the SDK's functionality into the web-based resource, the SDK is downloaded by third-party server 110 from message server 118, or otherwise received by third-party server 110. Once downloaded or received, the SDK is included as part of the application code of the web-based external resource. The code of the web-based resource can then call or activate certain functions of the SDK to integrate the features of message client 104 into the web-based resource.

[0047] The SDK stored on message transceiver server 118 effectively provides a bridge between external resources (e.g., application 106 or a mini-application) and message transceiver client 104. This provides users with a seamless experience communicating with other users on message transceiver client 104 while preserving the look and feel of message transceiver client 104. To bridge communication between external resources and message transceiver client 104, in some examples, the SDK facilitates communication between third-party server 110 and message transceiver client 104. In some examples, a WebViewJavaScriptBridge running on client device 102 establishes two unidirectional communication channels between external resources and message transceiver client 104. Messages are sent asynchronously between external resources and message transceiver client 104 via these communication channels. Each SDK function call is sent as a message and a callback. Each SDK function is implemented by constructing a unique callback identifier and sending a message with that callback identifier.

[0048] By using the SDK, not all information from the messaging client 104 is shared with the third-party server 110. The SDK limits which information is shared based on the needs of the external resource. In some examples, each third-party server 110 provides the messaging server 118 with an HTML5 file corresponding to the web-based external resource. The messaging server 118 can add a visual representation (such as a box design or other graphics) of the web-based external resource in the messaging client 104. Once the user selects a visual representation or instructs the messaging client 104 via its GUI to access a feature of the web-based external resource, the messaging client 104 obtains the HTML5 file and instantiates the resources required to access the feature of the web-based external resource.

[0049] The messaging client 104 presents a graphical user interface (GUI) for an external resource (e.g., a login page or title screen). During, before, or after presenting the login page or title screen, the messaging client 104 determines whether the initiated external resource has previously been authorized to access the messaging client 104's user data. In response to determining that the initiated external resource has previously been authorized to access the messaging client 104's user data, the messaging client 104 presents another GUI for the external resource, including its functionality and characteristics. In response to determining that the initiated external resource has not previously been authorized to access the messaging client 104's user data, after a threshold time period (e.g., 3 seconds) of displaying the external resource's login page or title screen, the messaging client 104 slides up a menu (e.g., animates the menu to appear from the bottom of the screen to the middle or other part of the screen) to authorize the external resource to access user data. This menu identifies the type of user data that the external resource will be authorized to use. In response to receiving a user's selection of the accept option, messaging client 104 adds the external resource to the list of authorized external resources and allows the external resource to access user data from messaging client 104. In some examples, the external resource is authorized by messaging client 104 to access user data according to the OAuth 2 framework.

[0050] The messaging client 104 controls the type of user data shared with external resources based on the type of authorized external resource. For example, it provides access to a first type of user data (e.g., a two-dimensional avatar of a user, with or without different avatar characteristics) to external resources including full-scale applications (e.g., application 106). As another example, it provides access to a second type of user data (e.g., payment information, a user's two-dimensional avatar, a user's three-dimensional avatar, and avatars with various avatar characteristics) to external resources including smaller versions of the application (e.g., a web-based version of the application). Avatar characteristics include different ways of customizing the appearance and feel of the avatar (e.g., different poses, facial features, clothing, etc.).

[0051] Shopping system 214 provides various shopping-related functions within the context of messaging system 100. Examples of shopping-related functions include, but are not limited to, allowing users to: browse a range of items (e.g., products and / or services), view images and / or videos of items, view information about item specifications, features, and prices, maintain a shopping cart for selecting items for final purchase, and / or purchase the selected items. In one or more embodiments, shopping system 214 works in conjunction with third-party services (e.g., external resource system 212) to perform one or more of the shopping-related functions of messaging system 100. Furthermore, augmentation system 208 may work in conjunction with shopping system 214 to modify captured images or videos to include shopping information (e.g., via overlay, augmented reality content, etc.).

[0052] Figure 3 This is a schematic diagram illustrating a data structure 300 that can be stored in a database 126 of a message transceiver server system 108, according to certain examples. Although the contents of the database 126 are shown as including several tables, it will be understood that the data can be stored in other types of data structures (e.g., stored as an object-oriented database).

[0053] Database 126 includes message data stored in message table 306. For any given message, this message data includes at least message sender data, message receiver (or recipient) data, and payload. See below for reference. Figure 4 Further details are provided regarding information that can be included in the message and in the message data stored in message table 306.

[0054] Entity table 308 stores entity data and (for example, links to entity diagram 304 and profile data 302). Entities for which records are stored in entity table 308 can include individuals, company entities, organizations, objects, locations, events, etc. Regardless of the entity type, any entity for which the message transceiver server system 108 stores data can be an identifiable entity. Each entity is assigned a unique identifier and an entity type identifier (not shown).

[0055] Entity Graph 304 stores information about the relationships and associations between entities. As an example only, such relationships could be professional relationships based on interests or activities (e.g., working in the same company or organization), or social relationships.

[0056] Profile data 302 stores various types of profile data about a specific entity. Based on privacy settings specified by the specific entity, profile data 302 can be selectively used and presented to other users of messaging system 100. In the case of an individual, profile data 302 includes, for example, a username, phone number, address, settings (e.g., notification and privacy settings), and an avatar representation (or a set of such avatar representations) selected by the user. A specific user can then selectively include one or more of these avatar representations in the content of messages transmitted via messaging system 100 and in a map interface displayed to other users by messaging client 104. The set of avatar representations may include “status avatars,” which present a graphical representation of a status or activity that the user can choose to transmit at a specific time.

[0057] In the case that the entity is a group, in addition to the group name, members and various settings for the relevant group (e.g., notifications), the profile data 302 for the group may similarly include one or more avatars associated with the group.

[0058] Database 126 also stores enhancement data, such as overlays or filters, in enhancement table 310. The enhancement data is associated with and applied to videos (video data is stored in video table 314) and images (image data is stored in image table 316).

[0059] In one example, a filter is an overlay displayed on an image or video during presentation to the receiving user. Filters can be of various types, including user-selected filters that come from a set of filters presented to the sending user by the messaging client 104 while the sending user is composing a message. Other types of filters include geolocation filters (also known as geographic filters), which can be presented to the sending user based on geographic location. For example, a geolocation filter specific to a nearby or particular location can be presented by the messaging client 104 within the user interface based on geolocation information determined by the Global Positioning System (GPS) unit of the client device 102.

[0060] Another type of filter is a data filter, which can be selectively presented to the sending user by the messaging client 104 based on other inputs or information collected by the client device 102 during the message creation process. Examples of data filters include the current temperature at a specific location, the current speed of the sending user, the battery life of the client device 102, or the current time.

[0061] Other augmented data that can be stored in image table 316 includes augmented reality content items (e.g., corresponding to an application lens or augmented reality experience). Augmented reality content items can provide real-time effects and / or sound that can be added to images or videos.

[0062] As described above, augmented data includes augmented reality content items, overlays, image transformations, AR images, and similar terms referring to modifications that can be applied to image data (e.g., video or images). This includes real-time modifications, which modify the image using the modifications as the device sensors (e.g., one or more cameras) of client device 102 capture the image and then display the image on the screen of client device 102. This also includes modifications to stored content (e.g., video clips in a gallery that can be modified). For example, in client device 102 where multiple augmented reality content items can be accessed, a user can use a single video clip with multiple augmented reality content items to see how different augmented reality content items will modify the stored clip. For example, by selecting different augmented reality content items for the same content, multiple augmented reality content items with different pseudo-random motion models can be applied to the same content. Similarly, real-time video capture can be used with the illustrated modifications to show how the video image currently being captured by the sensors of client device 102 will modify the captured data. Such data can be displayed on the screen without being stored in memory, or the content captured by the device's sensors can be recorded and stored in memory with or without modification (or both). In some systems, preview features can simultaneously show how different augmented reality content items will look in different windows on the display. For example, this can make it possible to view multiple windows with different pseudo-random animations on the display at the same time.

[0063] Therefore, using augmented reality content items and various systems, or other such transformation systems that use this data to modify content, can involve: the detection of objects (e.g., faces, hands, bodies, cats, dogs, surfaces, objects, etc.) in video frames; tracking these objects as they leave, enter, and move around within the field of view; and modifying or transforming them while tracking these objects. In various examples, different methods can be used to implement such transformations. Some examples may involve generating 3D mesh models of one or more objects, and using transformations and animated textures of the models within the video to implement the transformations. In other examples, tracking points on objects can be used to place images or textures (which can be two-dimensional or three-dimensional) at the tracked locations. In still other examples, neural network analysis of video frames can be used to place images, models, or textures within content (e.g., images or video frames). Therefore, augmented reality content items refer both to the images, models, and textures used to create transformations within content, and to the additional modeling and analysis information required to implement such transformations using object detection, tracking, and placement.

[0064] Real-time video processing can be performed using any type of video data (e.g., video streams, video files, etc.) stored in the memory of any type of computerized system. For example, a user can load a video file and store it in the device's memory, or the device's sensors can be used to generate a video stream. Additionally, computer-animated models can be used to process any object, such as human faces and parts of the human body, animals, or inanimate objects (e.g., chairs, cars, or other objects).

[0065] In some examples, when a specific modification is selected along with the content to be transformed, the computing device identifies the element to be transformed, and then, if the element to be transformed exists in a frame of the video, detects and tracks the element to be transformed. The elements of the object are modified according to the modification request, thereby transforming the frames of the video stream. For different kinds of transformations, the transformation of the video stream frames can be performed using different methods. For example, for frame transformations that primarily involve changing the form of elements of an object, feature points of each element of the object are calculated (e.g., using an Active Shape Model (ASM) or other known methods). Then, a feature point-based mesh is generated for each element of at least one element of the object. This mesh is used in subsequent stages of tracking the elements of the object in the video stream. During tracking, the aforementioned mesh for each element is aligned with the 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 the modification request, and a second set of points is generated for each element based on the first set of points and the modification request. The frames of the video stream can then be transformed by modifying the elements of the object based on the first set of points, the second set of points, and the mesh. In this method, the background of the object being modified can also be changed or distorted by tracking and modifying the background.

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

[0067] In some examples of computer animation models that use face detection to transform image data, a specific face detection algorithm (e.g., Viola-Jones) is used to detect faces in the image. Then, the Active Shape Model (ASM) algorithm is applied to the facial regions of the image to detect facial feature reference points.

[0068] Other methods and algorithms suitable for face detection can be used. For example, in some examples, landmarks are used to locate features; landmarks represent distinguishable points present in most of the images considered. For example, for facial landmarks, the location of the left pupil could be used. If the initial landmark is unrecognizable (e.g., if the person is wearing an eye patch), secondary landmarks can be used. Such a landmark recognition process can be used for any such object. In some examples, the set of landmarks forms a shape. The shape can be represented as a vector using the coordinates of the points in the shape. One shape is aligned with another shape using a similarity transformation (allowing translation, scaling, and rotation) that minimizes the average Euclidean distance between the points of the shape. The mean shape is the mean of the aligned training shapes.

[0069] In some examples, a search for landmarks begins with a mean shape aligned with the position and size of a face determined by a global face detector. This search then repeats the following steps: proposing provisional shapes by adjusting the localization of shape points through template matching of the image texture around each point, and then conforming the provisional shapes to a global shape model until convergence occurs. In some systems, individual template matching is unreliable, and the shape model pools the results of weak template matching to form a stronger overall classifier. The entire search is repeated at each level of the image pyramid, from coarse to fine resolution.

[0070] The transformation system can capture image or video streams on a client device (e.g., client device 102) and perform complex image manipulations locally on client device 102 while maintaining an appropriate user experience, computation time, and power consumption. Complex image manipulations can include size and shape changes, emotion shifts (e.g., changing a face from frowning to smiling), state shifts (e.g., aging an object, reducing its apparent age, or changing its gender), style shifts, application of graphical elements, and any other suitable image or video manipulations implemented by a convolutional neural network that has been configured to execute efficiently on client device 102.

[0071] In some examples, a computer animation model for transforming image data can be used by a system in which a user can capture an image or video stream (e.g., a selfie) using a client device 102 that has a neural network operating as part of a messaging client 104 operating on client device 102. A transformation system operating within messaging client 104 determines the presence of a face within the image or video stream and provides a modification icon associated with the computer animation model to transform the data image, or the computer animation model can be presented as associated with the interface described herein. The modification icon includes changes that can be the basis for modifying the user's face within the image or video stream as part of a modification operation. Once a modification icon is selected, the transformation system initiates a process to transform the user's image to reflect the selected modification icon (e.g., generating a smiley face on the user). Once the image or video stream is captured and the specified modification is selected, the modified image or video stream can be presented in a graphical user interface displayed on client device 102. The transformation system can implement a complex convolutional neural network on a portion of the image or video stream to generate and apply the selected modification. In other words, users can capture image or video streams, and once an edit icon is selected, the changes are presented to the user in real-time or near real-time. Furthermore, while a video stream is being captured, the changes can be persistent, and the selected edit icon continues to be toggled. Machine-trained neural networks can be used to achieve such modifications.

[0072] The graphical user interface (GUI) presenting the modifications performed by the transformation system can provide users with additional interactive options. Such options can be based on the interface used to initiate the selection and content capture of a specific computer animation model (e.g., initiated from a content creator user interface). In various examples, the modifications can be persistent after an initial selection of the modification icon. Users can turn the modification on or off by tapping or otherwise selecting the face being modified by the transformation system and save it for later viewing or browsing to other areas of the imaging application. In cases where multiple faces are modified by the transformation system, users can globally turn the modification on or off by tapping or selecting a single face being modified and displayed within the GUI. In some examples, individual faces within a set of multiple faces can be modified separately, or such modifications can be toggled individually by tapping or selecting individual faces or a series of individual faces displayed within the GUI.

[0073] Story table 312 stores data about collections of messages and associated image, video, or audio data, compiled into collections (e.g., stories or galleries). The creation of a specific collection can be initiated by a specific user (e.g., each user whose records are stored in entity table 308). A user can create a "personal story" in the form of a collection of content that has been created and sent / broadcast by that user. For this purpose, the user interface of messaging client 104 may include user-selectable icons that allow the sending user to add specific content to his or her personal story.

[0074] The collection can also constitute a "live story," which is a collection of content from multiple users created manually, automatically, or using a combination of manual and automatic techniques. For example, a "live story" can constitute a curated stream of user-submitted content from different locations and events. Users whose client devices have location services enabled and who are at a co-located event at a specific time can be presented with the option to contribute content to a specific live story, for example, via the user interface of messaging client 104. The messaging client 104 can identify a live story to a user based on their location. The end result is a "live story" told from a collective perspective.

[0075] Another type of content collection is called a "location story," which allows users whose client devices 102 are located in a specific geographic location (e.g., on a college or university campus) to contribute to a specific collection. In some examples, contributing to a location story may require secondary authentication to verify that the end user belongs to a specific organization or other entity (e.g., a student on a university campus).

[0076] As mentioned above, video table 314 stores video data, which in one example is associated with a message whose record is stored in message table 306. Similarly, image table 316 stores image data associated with a message whose message data is stored in entity table 308. Entity table 308 can associate various enhancements from enhancement table 310 with various images and videos stored in image table 316 and video table 314.

[0077] Figure 4This is a schematic diagram illustrating the structure of a message 400 according to some examples, generated by a messaging client 104 for transmission to another messaging client 104 or a messaging server 118. The content of a particular message 400 is used to populate a message table 306 stored in a database 126 accessible by the messaging server 118. Similarly, the content of message 400 is stored in memory as "in-transit" or "in-flight" data for the client device 102 or application server 114. Message 400 is shown as including the following example components:

[0078] • Message Identifier 402: A unique identifier that identifies message 400.

[0079] • Message text payload 404: The text to be generated by the user via the user interface of the client device 102 and included in message 400.

[0080] • Message image payload 406: Image data captured by the camera component of the client device 102 or retrieved from the memory component of the client device 102 and included in the message 400. The image data for the sent or received message 400 can be stored in the image table 316.

[0081] • Message video payload 408: Video data captured by the camera device component or retrieved from the memory component of the client device 102 and included in the message 400. The video data for the sent or received message 400 can be stored in the video table 314.

[0082] • Message audio payload 410: Audio data captured by the microphone or retrieved from the memory component of the client device 102 and included in message 400.

[0083] • Message enhancement data 412: Enhancement data (e.g., filters, labels, or other annotations or enhancements) representing enhancements to be applied to the message image payload 406, message video payload 408, or message audio payload 410 of message 400. Enhancement data for the sent or received message 400 can be stored in enhancement table 310.

[0084] • Message duration parameter 414: A parameter value, in seconds, indicating the amount of time that the content of the message (e.g., message image payload 406, message video payload 408, message audio payload 410) will be presented to the user or made accessible to the user via the message sending and receiving client 104.

[0085] • Message geolocation parameter 416: Geolocation data (e.g., latitude and longitude coordinates) associated with the message's content payload. Multiple message geolocation parameter 416 values ​​may be included in the payload, each of which is associated with a content item included in the content (e.g., a specific image within the message image payload 406 or a specific video within the message video payload 408).

[0086] • Message Story Identifier 418: An identifier value that identifies one or more sets of content (e.g., “Stories” identified in Story Table 312) associated with a specific content item in the message image payload 406 of message 400. For example, the identifier value can be used to associate multiple images within the message image payload 406 with multiple sets of content, respectively.

[0087] • Message Tag 420: Each message 400 can be labeled with multiple tags, each of which indicates the subject of the content included in the message payload. For example, in the case where a specific image included in the message image payload 406 depicts an animal (e.g., a lion), the tag value can be included within the message tag 420 indicating the relevant animal. The tag value can be manually generated based on user input, or it can be automatically generated using, for example, image recognition.

[0088] • Message sender identifier 422: An identifier (e.g., message sending system identifier, email address, or device identifier) ​​indicating the user of the client device 102 on which message 400 is generated and from which message 400 is sent.

[0089] • Message receiver identifier 424: An identifier (e.g., message sending and receiving system identifier, email address, or device identifier) ​​indicating the user of the client device 102 to which message 400 is addressed.

[0090] The content (e.g., values) of each component of message 400 can be pointers to locations in tables where content data values ​​are stored. For example, image values ​​in message image payload 406 can be pointers (or addresses) to locations within image table 316. Similarly, values ​​in message video payload 408 can point to data stored in video table 314, values ​​in message enhancement 412 can point to data stored in enhancement table 310, values ​​in message story identifier 418 can point to data stored in story table 312, and values ​​in message sender identifier 422 and message receiver identifier 424 can point to user records stored in entity table 308.

[0091] Figure 5This is an interactive diagram illustrating a process 500 for providing augmented reality-based makeup in a messaging system, according to some example implementations. For illustrative purposes, reference is made primarily herein. Figure 1 Message sending and receiving client 104 Figure 2 The process 500 is described using the enhancement system 208 and the shopping system 214. However, one or more blocks (or operations) of the process 500 may be executed by one or more other components and / or other suitable devices. Further, for illustrative purposes, the blocks (or operations) of the process 500 are described herein as occurring serially or linearly. However, multiple blocks (or operations) of the process 500 may occur in parallel or simultaneously. Additionally, the blocks (or operations) of the process 500 do not need to be executed in the order shown, and / or one or more blocks (or operations) of the process 500 do not need to be executed and / or may be replaced by other operations. The process 500 may terminate when its operations are complete. Furthermore, the process 500 may correspond to a method, program, algorithm, etc.

[0092] The messaging client 104 can be associated with a corresponding user of the messaging server system 108, and this user can be associated with a user account of the messaging server system 108. As described above, a user can be identified by the messaging server system 108 based on a unique identifier associated with that user's user account (e.g., a messaging system identifier, email address, and / or device identifier). Additionally, the messaging server system 108 can implement and work in conjunction with a social networking server 124 configured to identify other users (e.g., friends) with whom a particular user has a relationship.

[0093] As described herein, messaging client 104 (e.g., in conjunction with messaging server system 108) presents augmented reality content for trying out cosmetic products. Messaging client 104 activates or otherwise accesses an augmented reality content item that generates a grid for tracking areas of the face depicted in a captured image (e.g., a live video feed). The augmented reality content item allows the user to select areas of the face, and depicts a range of colors / contrasts of makeup that can be applied to the selected areas. The user selects a specific color and / or contrast, and the corresponding makeup is presented as an overlay on the facial area. Additionally, cosmetic products matching the selected color and / or contrast can be presented along with shopping cart interface elements for addition to the user's shopping cart for final purchase.

[0094] In one or more embodiments, messaging client 104, for example, activates the camera device of client device 102 upon startup to capture an image depicting a face. For example, the camera device may correspond to a front-facing camera for capturing an image depicting a user's face, or a rear-facing camera for capturing an image of another person's face. Alternatively or additionally, the image may correspond to an image (e.g., a photograph) stored in association with a user of client device 102 (e.g., a photo library).

[0095] At block 502, messaging client 104 receives user input to present augmented reality content in association with the face depicted in the captured image. As described above, augmented system 208 may implement or otherwise access augmented reality content items. Augmented system 208 may correspond to a subsystem of messaging system 100 and may be supported on the client side by messaging client 104 and / or on the server side by application server 114. Therefore, the provision of augmented reality content items may be implemented on the client side, the server side, and / or a combination of client-side and server-side.

[0096] In conjunction with augmented reality system 208, messaging client 104 can provide a carousel interface that allows users to cycle through and / or select between different augmented reality content items to apply / display information about the image captured by the camera device. Each available augmented reality content item is represented by an icon that is selectable by the user to switch to the corresponding augmented reality content item.

[0097] Therefore, the user input corresponding to block 502 can correspond to the user selecting an augmented reality content item from multiple augmented reality content items presented in the carousel interface. For example, the selected augmented reality content item provides augmented reality content for a makeup simulation application. The messaging client 104 sends a request for the selected augmented reality content item to the augmented system 208 (operation 504).

[0098] In response, augmentation system 208 accesses the selected augmented reality content item (block 506) and provides access to the augmented reality content item to messaging client 104 (operation 508). For example, augmentation system 208 provides appropriate code and / or application interface to messaging client 104 for rendering the augmented reality content item within messaging client 104.

[0099] As described above, the Augmented Reality Content Item provides augmented reality content for applications depicting simulated makeup on a face in captured images (e.g., from a live video feed or images / videos stored in a photo library). The Augmented Reality Content Item is configured to detect when different facial regions are present in the captured image and generate a mesh based on feature points of these facial regions. In the example of makeup, facial regions include, but are not limited to, the user's eyebrows, eyes, cheekbone high points, lower cheekbone areas, and / or lips. The generated mesh can be used to track these regions of the face in the video stream (e.g., by aligning the mesh regions with the corresponding regions of the face) to enhance / transform the display of facial regions captured by the device's camera. The generation of the mesh and the detection and / or tracking of facial regions used can be based on machine learning algorithms.

[0100] The messaging client 104 is configured to present an augmented reality content item, including a grid, in association with a captured image. In one or more embodiments, the presented augmented reality content item corresponds to a region of the depicted face that is traced using a grid, but does not display an overlay of each region (e.g., contour regions). Alternatively, the augmented reality content item may provide an overlay of one or more regions (e.g., contours corresponding to the outer edges of the regions) to facilitate user selection of the region.

[0101] Therefore, at block 510, message transceiver client 104 receives user input indicating a region of the captured image. For example, the user can select a region corresponding to the user's eyes, eyebrows, cheekbone high points, lower cheekbone, and / or lips. The user's selection of a region may correspond to a user request for available color / contrast options (e.g., range) for the selected region to be rendered.

[0102] The messaging client 104 sends a request to the shopping system 214 for a range of color / contrast values ​​for a cosmetic product corresponding to the selected area (operation 512). For example, the request may be for a range of color and contrast values ​​related to available cosmetic products for the selected area. In one or more embodiments, the request indicates a selected area of ​​the face (e.g., in the form of keywords such as "eyes," "eyebrows," "high cheekbone," "lower cheekbone," "lips," or via other known techniques for identifying regions of an image / face).

[0103] Shopping system 214 determines the color / contrast range based on the selected area of ​​the face (block 514). As described above, shopping system 214 may correspond to a subsystem of messaging system 100 and may be supported on the client side by messaging client 104 and / or on the server side by application server 114. In one or more embodiments, the functions performed by shopping system 214 may be implemented on the client side, server side, and / or a combination of client side and server side. Regarding the available color / contrast range, shopping system 214 may (e.g., from data storage) access a predetermined range of color values ​​and / or contrast values ​​for each facial region. The range of color / contrast values ​​may be based on available cosmetic products accessible by shopping system 214. The determination of color contrast values ​​may be based on other signals and / or parameters discussed below with respect to block 526.

[0104] At operation 516, the shopping system 214 sends an indication of a color / contrast range to the messaging client 104. For example, the shopping system 214 may define the color / contrast range based on one or more of the RGB (red, green, blue) color model, the HSL (hue, saturation, lightness) color model, and / or the HSV (hue, saturation, lightness) color model. The messaging client 104 is configured to receive values ​​for defining the color / contrast range and for displaying corresponding interface elements that depict the color / contrast range.

[0105] Therefore, the messaging client 104 displays interface elements (block 518) depicting a range of colors / contrast ratios. In one or more embodiments, the messaging client 104 displays a first arc bar depicting a range of color values ​​for a user to select a specific color. The messaging client 104 also displays a second arc bar depicting a range of contrast values ​​for a user to select a specific contrast ratio (e.g., based on the selected color). For example, after the user selects a color value, the range of contrast values ​​can be determined and displayed with respect to the selected color value.

[0106] As shown below Figure 6A As discussed in the example, the messaging client 104 displays a first arc bar and a second arc bar on the left and right sides of the screen, while continuing to display a captured image depicting the user's face. In the corresponding... Figure 6B In another example, the messaging client 104 displays a first arc bar and a second arc bar at the top and bottom of the screen, while continuing to display a captured image depicting the user's face.

[0107] In another example, as follows about Figure 6CThe interface element discussed, used for color / contrast selection, is presented as a circle. The outer edge of the circle outlines the range of color values ​​for the user to select a specific color. The user's selection of the contrast value can be based on the distance of the touch input relative to the center of the circle (e.g., lower contrast for touch input at the outer edge and increased contrast as the touch input approaches the center of the circle).

[0108] At block 520, message transceiver client 104 receives user input selecting color values ​​within a range of color values ​​and contrast values ​​within a range of contrast values. Message transceiver client 104 then displays an overlay corresponding to the makeup based on the user-selected color and contrast values ​​(block 522). For example, the augmented reality content item is configured to render simulated makeup corresponding to the selected color / contrast values ​​on a selected facial area. In this way, the augmented reality content item appears to apply makeup to the user's face depicted in the image in real time.

[0109] In addition to applications simulating makeup colors and contrasts, messaging client 104 can also enable the display of available makeup products corresponding to the selected color / contrast. Therefore, at operation 524, messaging client 104 sends a request for available makeup products based on the user-selected color and contrast values. In one or more embodiments, the request indicates the color / contrast value and indicates a selected area of ​​the face (e.g., via keywords as described above). Furthermore, the request may include other information such as user identifiers (e.g., messaging system identifier, email address, and / or device identifier) ​​and / or facial feature data. For example, messaging client 104, in conjunction with enhancement system 208, can determine facial feature data (e.g., the size, shape, and / or position of individual areas of the face or the overall size, shape, and / or position of the face) based on dimensions and / or measurements from a grid.

[0110] As described above, shopping system 214 (e.g., in conjunction with third-party services such as external resource system 212) allows users to browse a range of products, view product images and / or videos, view information about product specifications, features, and prices, maintain a shopping cart for selecting products for final purchase, and / or purchase the selected products. At block 526, shopping system 214 determines the available cosmetic products based on the request provided at operation 524. Shopping system 214 may make such a determination based on one or more of the following: selected color / contrast values, selected areas of the face (e.g., via keywords), user identifiers, and / or facial data provided with the request.

[0111] For example, shopping system 214 may determine the available makeup product set based on ranking one or more of the following signals and / or parameters: a predefined makeup set associated with a selected area of ​​the face; user history indicating preferences (e.g., previous purchases associated with a user identifier and involving makeup color, contrast, brand name, etc.); user activity (e.g., activities associated with a user identifier and involving practice and non-practice makeup); time of year (e.g., different seasons are associated with different makeup sets); user-submitted responses to questionnaires; makeup trend data; sponsored keywords; and / or makeup product sets associated with predefined entities.

[0112] Regarding the user's response to the questionnaire, messaging client 104 can present the questionnaire to the user in conjunction with augmented reality content items. For example, the questionnaire could be a user-selectable option with predefined questions (e.g., presented when the augmented reality content item is activated). These questions could relate to one or more of the following: makeup goals, desired appearance, areas of interest, makeup sensitivities (e.g., allergies), and / or preferred colors / intensities. If the user selects a questionnaire, messaging client 104 can send an indication of the user's submitted response to shopping system 214 as a parameter for determining (e.g., ranking) available cosmetic products.

[0113] Regarding sponsorship, shopping system 214 may allow third parties (e.g., cosmetic manufacturers corresponding to brand names) to sponsor keywords. For example, a third party may sponsor one or more keywords related to facial areas (e.g., "eyes," "eyebrows," "high point of the cheekbone," "lower cheekbone," "lips") and / or corresponding makeup (e.g., "eye makeup," "mascara," "eyeshadow," "lipstick," etc.). In response to determining that the selected facial area corresponds to the sponsored keyword, shopping system 214 can provide higher rankings for cosmetic products from third parties relative to other cosmetic products.

[0114] Regarding the set of cosmetic products associated with a predefined entity, the predefined entity could correspond to a company entity, a social media influencer, a celebrity, etc. For example, a company entity via external resource system 212 could associate a selected set of cosmetic products with corresponding facial features (e.g., the size, shape, and / or location of individual areas of the face or the overall size, shape, and / or location of the face). In another example, a social media influencer could recommend a selected set of cosmetic products or otherwise associate it with a selected set of cosmetic products.

[0115] Shopping system 214 can be configured to access a database (e.g., database 126) that stores information about a predefined set of entities (e.g., companies, social media influencers). For example, each entity authorizes the storage of information in database 126, which includes the entity's cosmetic products / sets and facial feature data. Based on the user's facial feature data provided in the request of operation 512, shopping system 214 can (e.g., based on meeting thresholds regarding matching face size, shape, dimensions, etc.) select entities with facial feature data corresponding to the user's face.

[0116] Therefore, after ranking the cosmetic products based on the aforementioned signals and / or parameters, the shopping system 214 selects available cosmetic products corresponding to the user's selected color / contrast and facial region. The shopping system 214 sends an indication of the available cosmetic products to the messaging client 104 (operation 528). In one or more embodiments, the aforementioned signals and / or parameters may be used (e.g., based on ranking) to determine the color / contrast range described above with respect to block 514.

[0117] The messaging client 104 displays cosmetic products for potential purchase by the user (block 530). For example, the messaging client 104 may provide interface elements allowing the user to select one or more available cosmetic products to add to a shopping cart associated with their user account. In response, the messaging client 104 sends an instruction to the shopping system 214 regarding the selected cosmetic products, which in turn adds one or more of the selected cosmetic products to the shopping cart. As described above, the shopping cart can be implemented by the shopping system 214 to allow users to select items associated with their user accounts for final purchase.

[0118] Figures 6A to 6C and Figures 7A to 7B A user interface for displaying augmented reality content corresponding to makeup is shown. For example, the user interface can be presented in response to a user's selection of an augmented reality content item to apply the makeup as described above. As described above, augmented reality system 208 can provide message transceiver client 104 with access to such augmented reality content items.

[0119] Figure 6A An example user interface 602 with interface elements for selecting makeup color and contrast, according to some example embodiments, is shown. User interface 602 displays a captured image 604 corresponding to the user's face. User interface 622 also includes a camera selection button 606, a flash button 608, a color selector 610, a contrast selector 614, and a carousel interface 618 with selected AR icons 620.

[0120] The captured image 604 may correspond to a live video feed captured by the camera device of the client device 102. Alternatively or additionally, the image may correspond to an image (e.g., a photograph) stored in association with a user of the client device 102 (e.g., a photo library).

[0121] Although Figure 6A The example shows a captured image 604 captured by the front-facing camera of client device 102, but messaging client 104 may alternatively capture images from a rear-facing camera (e.g., a live video feed). In this regard, the camera selection button 606 corresponds to a user-selectable button for switching between the rear and front-facing cameras of client device 102. User interface 602 also includes a flash button 608 for activating or deactivating the flash for the captured image 604.

[0122] As described above, the augmented reality content item provides a mesh configured to track facial regions. The augmented reality content item may or may not display a representation of the mesh (e.g., via an overlay outlining the facial regions). Figures 6A to 6C In the example, the grid is not displayed.

[0123] The user can select a specific area of ​​the face (e.g., lips), and the shopping system 214 can determine the range of available color and contrast values ​​corresponding to the selected lip area. Furthermore, the augmented reality content item enables a color selector 610 to display the range of color values, and also enables a contrast selector 614 to display the range of contrast values. The color selector 610 is displayed as a first vertical curved bar on the left side of the device screen, and the contrast selector 614 is displayed as a second vertical curved bar on the right side of the device screen.

[0124] In one or more embodiments, a user can select a color via touch input 612 using color selector 6102. The range of available contrast values ​​depicted in contrast selector 614 can be adjusted based on the selected color. Additionally, a user can select a contrast ratio via contrast selector 614 using touch input 616. Based on the selected color and contrast, augmented reality content items can display simulated makeup at selected facial areas (e.g., lips) corresponding to the selected color / contrast values ​​(e.g., associated with touch inputs 612 and 616).

[0125] The carousel interface 618 allows the user to cycle through and / or select different augmented reality content items to be applied / displayed with respect to the captured image 604. Each available augmented reality content item is represented by an icon that the user can select to switch to the corresponding augmented reality content item. In one or more embodiments, the icon corresponding to the active augmented reality content item (e.g., the selected AR icon 620) is displayed differently (e.g., larger than the other icons) relative to the remaining icons. The user's selection of the selected AR icon 620 causes the generation of media content items for example, to be sent to friends, included in stories, etc., wherein the media content items include images of screen content (e.g., in response to a press / tap gesture on the selected AR icon 620) and / or videos (e.g., in response to a press and hold gesture on the selected AR icon 620).

[0126] Figure 6B Another example user interface 622 with interface elements for selecting makeup color and contrast, according to some example embodiments, is shown. For example, user interface 622 corresponds to an alternative embodiment of augmented reality content items corresponding to the selected AR icon 620. Similar to... Figure 6A The user interface 622 depicts the captured image 604 and includes a camera device selection button 606, a flash button 608, and a carousel interface 618.

[0127] User interface 622 also includes a color picker 624, which is configured to receive touch input 626 and perform operations related to touch input. Figure 6A The color selector 610 has a similar function. Furthermore, the user interface 622 includes a contrast selector 628, which is configured to receive touch input 630 and perform similar functions. Figure 6A The contrast selector 614 has similar functionality. However, the color selector 624 and the contrast selector 628 are in a horizontal (relative to) manner. Figure 6A The image is displayed vertically (in the image's orientation) and at the top and bottom of the device screen (relative to the screen's orientation). Figure 6A (Left and right in the middle).

[0128] Figure 6C Another example user interface 632 with interface elements for selecting makeup color and contrast, according to some example embodiments, is shown. For example, user interface 622 corresponds to an alternative embodiment of augmented reality content items corresponding to the selected AR icon 620. Similar to... Figure 6A The user interface 622 depicts the captured image 604 and includes a camera device selection button 606, a flash button 608, and a carousel interface 618.

[0129] The user can select a specific area of ​​the face (e.g., the lips), and the shopping system 214 can determine the range of available color and contrast values ​​corresponding to the selected lip area. Furthermore, the augmented reality content item enables the display of a color picker 634 depicting the range of color values, and also provides a contrast picker 636 for selecting the contrast ratio.

[0130] Color selector 634 is presented as the outer perimeter of a circle and includes a range of color values ​​for the user to select a specific color. Furthermore, contrast selector 636 is depicted as an element (e.g., a smaller circle) located at the center of the circle corresponding to color selector 634. The user can select a contrast value based on the distance of the touch input relative to contrast selector 636 (e.g., lower contrast for touch input at the perimeter and increased contrast as the touch input approaches contrast selector 636). The range of available contrast values ​​can be adjusted based on the selected color. In one or more embodiments, the user can select both color and contrast via tap and drag gestures (e.g., using a tap portion for color selection and a drag portion for contrast selection). Based on the selected color and contrast, augmented reality content items can present simulated makeup at selected facial areas (e.g., lips) corresponding to the selected color / contrast values ​​(e.g., associated with touch inputs 612 and 616).

[0131] Figure 7A An example user interface 702, according to some example implementations, provides user-provided touch input for changing makeup colors. Similar to... Figure 6A The user interface 702 depicts the captured image 604 and includes a camera device selection button 606, a flash button 608, a carousel interface 618, and a selected AR icon 620.

[0132] The user interface 702 can be displayed in response to user input, which instructs the display of selected color / contrast values ​​for multiple areas of the depicted face to achieve the final appearance. The user input may correspond to predefined gestures and / or the user's selection of a dedicated button (not shown) to display the final appearance. If the user has selected multiple makeup products, the final appearance corresponds to applying all selected color / contrast values ​​to the face depicted in the captured image 604. In response to touch input 704 (e.g., corresponding to a press and hold gesture), the messaging client 104 displays a color picker 706, as described below. Figure 7B The subject of discussion.

[0133] Figure 7B A user interface 702 is shown for changing makeup color in response to touch input 704. Figure 7BIn the example, touch input 704 corresponds to the lip region of the face depicted in captured image 604. In response to touch input 704, messaging client 104 (e.g., in conjunction with augmented reality content items) displays a color picker 706, which outlines a range of colors that can be used to select the region (e.g., the lips). Color picker 706 is configured to receive additional touch input 708 for the user to select a specific color within the color range presented by color picker 706.

[0134] Figure 8 This is a flowchart illustrating a process 800 for providing augmented reality-based makeup in a messaging system, according to some example implementations. For illustrative purposes, reference is made primarily herein. Figure 1 Message sending and receiving client 104 Figure 2 The process 800 is described using the enhancement system 208 and the shopping system 214. However, one or more blocks (or operations) of process 800 may be executed by one or more other components and / or other suitable devices. Further, for illustrative purposes, the blocks (or operations) of process 800 are described herein as occurring serially or linearly. However, multiple blocks (or operations) of process 800 may occur in parallel or simultaneously. Additionally, the blocks (or operations) of process 800 do not need to be executed in the order shown, and / or one or more blocks (or operations) of process 800 need not be executed and / or may be replaced by other operations. Process 800 may terminate when its operations are complete. Furthermore, process 800 may correspond to a method, program, algorithm, etc.

[0135] The messaging client 104 receives a request to present augmented reality content associated with an image captured by the device's camera, the image depicting the user's face (block 802). The messaging client 104 may display a carousel interface for selecting an augmented reality content item from a plurality of augmented reality content items, and receive the user's selection of an augmented reality content item from the plurality of items via the carousel interface. This request may correspond to the user's selection.

[0136] In response to receiving the request, messaging client 104 (e.g., in conjunction with augmentation system 208) accesses an augmented reality content item associated with applying makeup to the face, which is configured to generate a mesh for tracking multiple regions of the face (block 804). Messaging client 104 receives user input to select regions from the multiple regions of the face (block 806).

[0137] The messaging client 104 (e.g., in conjunction with shopping system 214) determines at least one of a range of color values ​​or a range of contrast values ​​related to the available cosmetic products for the selected area (block 808). The messaging client 104 presents interface elements in association with a face depicted in an image via augmented reality content items, which are used by the user to select at least one of a color value within the range of color values ​​or a contrast value within the range of contrast values ​​(block 810).

[0138] The interface element may include a first selection bar depicting a range of color values, configured for the user to select a color value from the range. The interface element may also include a second selection bar depicting a range of contrast values, configured for the user to select a contrast value from the range. Each of the first and second selection bars may be curved.

[0139] Alternatively, interface elements may include a circle with an outer perimeter depicting a range of color values, configured for the user to select a color value from the range. The user's selection of a contrast value may be based on the distance of the touch input relative to the center of the circle.

[0140] The messaging client 104 can receive a second user input selecting at least one of a color value or a contrast value, and display a makeup overlay corresponding to at least one color value or contrast value for the selected area of ​​the face via an augmented reality content item. The messaging client 104 (e.g., in conjunction with the shopping system 214) can determine at least one makeup product corresponding to the makeup overlay and provide a second interface element for adding at least one makeup product to a shopping cart associated with the user's user account.

[0141] Figure 9 This is a schematic diagram illustrating an access restriction process 900, according to which access to content (e.g., a short message 902 and a multimedia payload of associated data) or a collection of content (e.g., a short message group 904) can be time-restricted (e.g., made short-lived).

[0142] A brief message 902 is shown as associated with a message duration parameter 906, the value of which determines the amount of time the message sending and receiving client 104 will display the brief message 902 to the receiving user. In one example, depending on the amount of time specified by the sending user using the message duration parameter 906, the receiving user can view the brief message 902 for up to 10 seconds.

[0143] Message duration parameter 906 and message receiver identifier 424 are shown as inputs to message timer 910, which is responsible for determining the amount of time for which brief message 902 is shown to a specific receiving user identified by message receiver identifier 424. Specifically, brief message 902 is shown to the relevant receiving user only within the time period determined by the value of message duration parameter 906. Message timer 910 is shown as providing an output to a more generalized brief timer system 202, which is responsible for the overall timing of displaying content (e.g., brief message 902) to the receiving user.

[0144] Brief message 902 Figure 9 The message group 904 is shown as a collection of messages included within a short message group 904 (e.g., a collection of messages in a personal story or event story). The short message group 904 has an associated group duration parameter 908, the value of which determines the duration for which the short message group 904 is presented and accessible to a user of the messaging system 100. For example, the group duration parameter 908 could be the duration of a concert, where the short message group 904 is a collection of content about that concert. Alternatively, when setting up and creating the short message group 904, the user (owner user or curator user) can specify the value of the group duration parameter 908.

[0145] Additionally, each short message 902 within a short message group 904 has an associated group participation parameter 912, the value of which determines the duration for which the short message 902 is accessible within the context of the short message group 904. Therefore, a particular short message group 904 can "expire" and become inaccessible within its context before the short message group 904 itself expires according to the group duration parameter 908. The group duration parameter 908, the group participation parameter 912, and the message receiver identifier 424 each provide input to a group timer 914, which is operable to first determine whether a particular short message 902 in the short message group 904 will be displayed to a specific receiving user, and if so, determine for how long. Note that the short message group 904 also knows the identity of the specific receiving user due to the message receiver identifier 424.

[0146] Therefore, the group timer 914 operatively controls the total usage period of the associated ephemeral message group 904 and the individual ephemeral messages 902 included within the ephemeral message group 904. In one example, each ephemeral message 902 within the ephemeral message group 904 remains viewable and accessible for a period of time specified by the group duration parameter 908. In another example, within the context of the ephemeral message group 904, a particular ephemeral message 902 may expire based on the group participation parameter 912. Note that even within the context of the ephemeral message group 904, the message duration parameter 906 can still determine the duration for which a particular ephemeral message 902 is displayed to the receiving user. Therefore, the message duration parameter 906 determines the duration for which a particular ephemeral message 902 is displayed to the receiving user, regardless of whether the receiving user views the ephemeral message 902 within or outside the context of the ephemeral message group 904.

[0147] The short-lived timer system 202 can also operatively remove a specific short-lived message 902 from the short-lived message group 904 based on determining that the specific short-lived message 902 has exceeded its associated group participation parameter 912. For example, if the sending user has established a group participation parameter 912 for 24 hours from the date of publication, the short-lived timer system 202 will remove the relevant short-lived message 902 from the short-lived message group 904 after the specified 24 hours. The short-lived timer system 202 also operates to remove the short-lived message group 904 when the group participation parameter 912 for each short-lived message 902 within the short-lived message group 904 has expired, or when the short-lived message group 904 itself has expired according to the group duration parameter 908.

[0148] In certain use cases, the creator of a specific ephemeral message group 904 can specify an indefinite group duration parameter 908. In this case, the expiration of the group participation parameter 912 for the last remaining ephemeral message 902 within the ephemeral message group 904 will determine when the ephemeral message group 904 itself expires. In this case, adding a new ephemeral message 902 with a new group participation parameter 912 to the ephemeral message group 904 effectively extends the lifetime of the ephemeral message group 904 to a value equal to the group participation parameter 912.

[0149] In response to the short-lived timer system 202 determining that a short-lived message group 904 has expired (e.g., is no longer accessible), the short-lived timer system 202 communicates with the messaging system 100 (and, in particular, the messaging client 104) to cause the markers (e.g., icons) associated with the relevant short-lived message group 904 to no longer be displayed in the user interface of the messaging client 104. Similarly, when the short-lived timer system 202 determines that the message duration parameter 906 for a particular short-lived message 902 has expired, the short-lived timer system 202 causes the messaging client 104 to no longer display the markers (e.g., icons or text labels) associated with the short-lived message 902.

[0150] Figure 10 This is a schematic representation of machine 1000, within which instructions 1010 (e.g., software, program, application, app, or other executable code) can be executed to cause machine 1000 to perform any or more of the methods discussed herein. For example, instructions 1010 can cause machine 1000 to perform any or more of the methods described herein. Instructions 1010 transform a general, unprogrammed machine 1000 into a specific machine 1000 programmed to perform the described and illustrated functions in the described manner. Machine 1000 can operate as a standalone device or can be coupled (e.g., networked) to other machines. In a networked deployment, machine 1000 can operate as a server machine or a client machine in a server-client network environment, or as a peer machine in a peer-to-peer (or distributed) network environment. Machine 1000 may include, but is not limited to, server computers, client computers, personal computers (PCs), tablet computers, laptop computers, netbooks, set-top boxes (STBs), personal digital assistants (PDAs), entertainment media systems, cellular phones, smartphones, mobile devices, wearable devices (e.g., smartwatches), smart home devices (e.g., smart appliances), other smart devices, web devices, network routers, network switches, network bridges, or any machine capable of sequentially or otherwise executing instructions 1010 specifying actions to be taken by machine 1000. Furthermore, although only a single machine 1000 is shown, the term "machine" should also be considered as a collection of machines that individually or jointly execute instructions 1010 to perform any or more of the methods discussed herein. For example, machine 1000 may include client device 102 or any of several server devices forming part of message transceiver server system 108. In some examples, machine 1000 may also include both client and server systems, wherein certain operations of a particular method or algorithm are performed on the server side and certain operations of said particular method or algorithm are performed on the client side.

[0151] Machine 1000 may include a processor 1004, a memory 1006, and an input / output (I / O) unit 1002 that can be configured to communicate with each other via a bus 1040. In the example, processor 1004 (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, processors 1008 and 1012 that execute instruction 1010. The term "processor" is intended to include multi-core processors, which may include two or more independent processors (sometimes referred to as "cores") capable of executing instructions simultaneously. Although Figure 10 Multiple processors 1004 are shown, but machine 1000 may include a single processor with a single core, a single processor with multiple cores (e.g., a multi-core processor), multiple processors with a single core, multiple processors with multiple cores, or any combination thereof.

[0152] Memory 1006 includes main memory 1014, static memory 1016, and storage cells 1018, all of which are accessible by processor 1004 via bus 1040. Main memory 1006, static memory 1016, and storage cells 1018 store instructions 1010 that implement any one or more of the methods or functions described herein. Instructions 1010 may also reside wholly or partially in main memory 1014, in static memory 1016, in machine-readable medium 1020 within storage cell 1018, in at least one of the processor 1004 (e.g., in the processor's cache memory), or in any suitable combination thereof during execution by machine 1000.

[0153] I / O component 1002 may include various components for receiving input, providing output, generating output, sending information, exchanging information, capturing measurement results, etc. The specific I / O component 1002 included in a particular machine will depend on the type of machine. For example, a portable machine such as a mobile phone may include a touch input device or other such input mechanism, while a headless server machine is unlikely to include such a touch input device. It should be understood that I / O component 1002 may include... Figure 10Many other components are not shown. In various examples, I / O component 1002 may include user output component 1026 and user input component 1028. User output component 1026 may include visual components (e.g., displays such as plasma display panels (PDPs), light-emitting diode (LED) displays, liquid crystal displays (LCDs), projectors, or cathode ray tube (CRT) displays), acoustic components (e.g., speakers), haptic components (e.g., vibration motors, resistance mechanisms), other signal generators, etc. User input component 1028 may include alphanumeric input components (e.g., keyboards, touchscreens configured to receive alphanumeric input, optical keyboards, or other alphanumeric input components), point-based input components (e.g., mice, touchpads, trackballs, joysticks, motion sensors, or other pointing instruments), haptic input components (e.g., physical buttons, touchscreens or other haptic input components that provide the position and force of a touch or touch gesture), audio input components (e.g., microphones), etc.

[0154] In other examples, I / O component 1002 may include biometric component 1030, motion component 1032, environmental component 1034, or position component 1036, as well as a wide range of other components. For example, biometric component 1030 includes components for detecting expressions (e.g., hand expressions, facial expressions, vocal expressions, body posture, or eye tracking), measuring biosignals (e.g., blood pressure, heart rate, body temperature, sweating, or brain waves), and identifying people (e.g., voice recognition, retinal recognition, facial recognition, fingerprint recognition, or EEG-based recognition). Motion component 1032 includes accelerometer components (e.g., accelerometers), gravity sensor components, and rotation sensor components (e.g., gyroscopes).

[0155] The environmental component 1034 includes, for example, one or more camera devices (with still image / photograph and video capabilities), lighting sensor components (e.g., photometers), temperature sensor components (e.g., one or more thermometers for detecting ambient temperature), humidity sensor components, pressure sensor components (e.g., barometers), acoustic sensor components (e.g., one or more microphones for detecting background noise), proximity sensor components (e.g., infrared sensors for detecting nearby objects), gas sensors (e.g., gas detection sensors for detecting the concentration of hazardous gases for safety purposes or for measuring pollutants in the atmosphere), or other components that can provide indications, measurements, or signals corresponding to the surrounding physical environment.

[0156] Regarding the camera device, client device 102 may have a camera device system including, for example, a front-facing camera on the front surface of client device 102 and a rear-facing camera on the rear surface of client device 102. The front-facing camera may be used, for example, to capture still images and videos (e.g., "selfies") of the user of client device 102, which can then be enhanced with the aforementioned enhancement data (e.g., filters). For example, the rear-facing camera may be used to capture still images and videos in a more conventional camera device mode, which are similarly enhanced with the enhancement data. In addition to the front and rear-facing cameras, client device 102 may also include a 360° camera for capturing 360° photos and videos.

[0157] Furthermore, the camera system of the client device 102 may include dual rear cameras (e.g., a main camera and a depth-sensing camera), or even include triple, quadruple, or quintuple rear camera configurations on the front and rear sides of the client device 102. For example, these multi-camera systems may include wide-angle cameras, ultra-wide-angle cameras, telephoto cameras, macro cameras, and depth sensors.

[0158] The position component 1036 includes a positioning sensor component (e.g., a GPS receiver component), an altitude sensor component (e.g., an altimeter or barometer that detects air pressure and from which altitude can be obtained), an orientation sensor component (e.g., a magnetometer), etc.

[0159] Various technologies can be used to achieve communication. I / O component 1002 also includes communication component 1038, which is operable to couple machine 1000 to network 1022 or device 1024 via a corresponding coupling or connection. For example, communication component 1038 may include a network interface component or another suitable device that interfaces with network 1022. In other examples, communication component 1038 may include wired communication component, wireless communication component, cellular communication component, near field communication (NFC) component, etc. Components (e.g.) (Low energy consumption) Components and other communication components for providing communication via other modes. Device 1024 can be any peripheral device from another machine or various peripheral devices (e.g., a peripheral device coupled via USB).

[0160] Furthermore, the communication component 1038 can detect identifiers, or includes components operable to detect identifiers. For example, the communication component 1038 may include a radio frequency identification (RFID) tag reader component, an NFC smart tag detection component, an optical reader component (e.g., an optical sensor for detecting one-dimensional barcodes such as Universal Product Code (UPC) barcodes, multi-dimensional barcodes such as Quick Response (QR) codes, Aztec codes, Data Matrix, Dataglyph, MaxiCode, PDF417, Ultra Code, UCC RSS-2D barcodes, and other optical codes), or an acoustic detection component (e.g., a microphone for identifying audio signals from the tag). Additionally, various information can be obtained via the communication component 1038, such as location via Internet Protocol (IP) geolocation, etc. Location can be determined by signal triangulation or by detecting NFC beacon signals that indicate a specific location.

[0161] Various memories (e.g., main memory 1014, static memory 1016, and the memory of processor 1004) and storage units 1018 may store one or more sets of instructions and data structures (e.g., software) implemented or used by any one or more of the methods or functions described herein. These instructions (e.g., instruction 1010) cause various operations to implement the disclosed examples when executed by processor 1004.

[0162] Instructions 1010 can be sent or received over network 1022 via a transmission medium using a network interface device (e.g., a network interface component included in communication component 1038) and using any of several known transmission protocols (e.g., Hypertext Transfer Protocol (HTTP)). Similarly, instructions 1010 can be sent or received via a transmission medium coupled to device 1024 (e.g., peer-to-peer coupling).

[0163] Figure 11 This is a block diagram 1100 illustrating a software architecture 1104 that can be installed on any or more devices described herein. The software architecture 1104 is supported by hardware such as a machine 1102 including a processor 1120, memory 1126, and I / O components 1138. In this example, the software architecture 1104 can be conceptualized as a stack of layers, where each layer provides specific functionality. The software architecture 1104 includes layers such as an operating system 1112, libraries 1110, frameworks 1108, and applications 1106. Operationally, application 1106 activates API call 1150 via the software stack and receives message 1152 in response to API call 1150.

[0164] Operating system 1112 manages hardware resources and provides public services. Operating system 1112 includes, for example, a kernel 1114, services 1116, and drivers 1122. Kernel 1114 acts as an abstraction layer between the hardware layer and other software layers. For example, kernel 1114 provides memory management, processor management (e.g., scheduling), component management, networking and security settings, and other functions. Service 1116 can provide other public services to other software layers. Driver 1122 is responsible for controlling or interfacing with the underlying hardware. For example, driver 1122 may include a display driver, a camera driver, etc. or Low-power drivers, flash drives, serial communication drivers (e.g., USB drives), Drivers, audio drivers, power management drivers, etc.

[0165] Library 1110 provides common low-level infrastructure used by application 1106. Library 1110 may include system library 1118 (e.g., the C standard library), which provides functions such as memory allocation, string manipulation, and mathematical functions. Additionally, library 1110 may include API library 1124, such as media libraries (e.g., libraries for supporting the rendering 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 Audio Layer 3 (MP3), Advanced Audio Coding (AAC), Adaptive Multi-Rate (AMR) audio codecs, Joint Picture Experts Group (JPEG or JPG) or Portable Web Graphics (PNG)), graphics libraries (e.g., the OpenGL framework for rendering graphic content on a display in two-dimensional (2D) and three-dimensional (3D) formats), database libraries (e.g., SQLite, which provides various relational database functions), web libraries (e.g., WebKit, which provides web browsing capabilities), and so on. Library 1110 may also include various other libraries 1128 to provide many other APIs to application 1106.

[0166] Framework 1108 provides common high-level infrastructure for use by application 1106. For example, framework 1108 provides various graphical user interface (GUI) functions, advanced resource management, and advanced location services. Framework 1108 can provide a wide range of other APIs that can be used by application 1106, some of which may be specific to a particular operating system or platform.

[0167] In the example, application 1106 may include home application 1136, contact application 1130, browser application 1132, book reader application 1134, location application 1142, media application 1144, messaging application 1146, game application 1148, and a wide variety of other applications such as third-party application 1140. Application 1106 is a program that performs the functions defined in the program. One or more applications 1106 can be created using various programming languages, 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 particular example, third-party application 1140 (e.g., using Android by an entity other than the vendor of a particular platform). TM or iOS TM Applications developed using a Software Development Kit (SDK) can be used on platforms such as iOS. TM ANDROID TM , Mobile software running on the phone's mobile operating system or another mobile operating system. In this example, a third-party application 1140 may invoke API calls 1150 provided by the operating system 1112 to facilitate the functions described herein.

[0168] "Carrier signal" refers to any intangible medium capable of storing, encoding, or carrying instructions to be executed by a machine, and includes digital or analog communication signals or other intangible media to facilitate the communication of such instructions. Instructions can be sent or received over a network using a transmission medium via a network interface device.

[0169] "Client device" refers to any machine that interfaces with a communication network to obtain resources from one or more server systems or other client devices. Client devices can be, but are not limited to, mobile phones, desktop computers, laptop computers, portable digital assistants (PDAs), smartphones, tablet computers, ultrabooks, netbooks, laptop computers, multiprocessor systems, microprocessor-based or programmable consumer electronics, game consoles, set-top boxes, or any other communication device that a user can use to access the network.

[0170] "Communication network" refers to one or more parts of a network, which can be an ad hoc network, intranet, extranet, virtual private network (VPN), local area network (LAN), wireless LAN (WLAN), wide area network (WAN), wireless WAN (WWAN), metropolitan area network (MAN), the Internet, a part of the Internet, a part of the Public Switched Telephone Network (PSTN), a POTS (Plain Old-Style Telephone Service) network, a cellular telephone network, a wireless network, etc. A network, another type of network, or a combination of two or more such networks. For example, a network or part of a network may include a wireless network or a 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 can implement any data transmission technology of various types, such as Single Carrier Radio Transmission (1xRTT), Evolved Data Optimization (EVDO), General Packet Radio Service (GPRS), Enhanced Data Rate Evolution of GSM (EDGE), the 3rd Generation Partnership Project (3GPP) including 3G, fourth-generation wireless (4G) networks, Universal Mobile Telecommunications System (UMTS), High-Speed ​​Packet Access (HSPA), Global Microwave Access Interoperability (WiMAX), Long Term Evolution (LTE) standards, other data transmission technologies defined by various standards setting organizations, other long-distance protocols, or other data transmission technologies.

[0171] A “component” refers to a device, physical entity, or logic having boundaries defined by functional or subroutine calls, branch points, APIs, or other technologies that provide partitioning or modularity for specific processing or control functions. A component can be combined with other components via its interface to perform machine processing. A component can be an encapsulated functional hardware unit designed for use with other components and can be part of a program that typically performs a specific function within a related function. A component can constitute a software component (e.g., code embodied on a machine-readable medium) or a hardware component. A “hardware component” is a tangible unit capable of performing certain operations and can be configured or arranged in some physical manner. In various examples, one or more hardware components (e.g., standalone computer systems, client computer systems, or server computer systems) or one or more hardware components (e.g., processors or processor groups) of a computer system can be configured by software (e.g., an application or application portion) to operate to perform certain operations as described herein. Hardware components can also be implemented mechanically, electronically, or in any suitable combination thereof. For example, a hardware component can include a dedicated circuit system or logic permanently configured to perform certain operations. Hardware components can be dedicated processors, such as field-programmable gate arrays (FPGAs) or application-specific integrated circuits (ASICs). Hardware components can also include programmable logic or circuit systems 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, the hardware component becomes a specific machine (or a specific part of a machine) uniquely tailored to perform the configured function and is no longer a general-purpose processor. It should be understood that the decision to implement a hardware component mechanically in a dedicated and permanently configured circuit system or in a temporarily configured (e.g., software-configured) circuit system can be made for cost and time considerations. Therefore, the phrase "hardware component" (or "hardware-implemented component") should be understood to include tangible entities, i.e., entities physically constructed, permanently configured (e.g., hardwired), or temporarily configured (e.g., programmed) to operate in a certain way or perform certain operations described herein. Consider the example of a hardware component being temporarily configured (e.g., programmed), without needing to configure or instantiate each hardware component at any given time. For example, in cases where the hardware components include a general-purpose processor that is configured as a dedicated processor via software, this general-purpose processor can be configured at different times as its respective dedicated processor (e.g., including different hardware components). The software accordingly configures one or more specific processors to constitute a specific hardware component at one time and different hardware components at different times. Hardware components can provide information to and receive information from other hardware components. Therefore, the described hardware components can be considered communicatively coupled.In the presence of multiple hardware components, communication can be achieved through signal transmission between or among these hardware components (e.g., via appropriate circuitry and buses). In examples where multiple hardware components are configured or instantiated at different times, such communication between hardware components can be achieved, for example, by storing information in a memory structure accessible to the multiple hardware components and retrieving information from the memory structure. For example, a hardware component can perform an operation and store the output of that operation in a memory device communicatively coupled to it. Another hardware component can then access the memory device at a subsequent time to retrieve and process the stored output. Hardware components can also initiate communication with input or output devices and can operate on resources (e.g., collections of information). The various operations of the example methods described herein can be performed at least in part by one or more processors configured, either temporarily (e.g., by software) or permanently, to perform the relevant operations. Whether temporarily or permanently configured, such processors can 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 can be implemented at least in part by processors, wherein a particular processor or one or more processors are examples of hardware. For example, at least some operations of the methods can be performed by one or more processors 1004 or processor-implemented components. Furthermore, one or more processors can also be configured to support the execution of related operations in a “cloud computing” environment or to operate as “Software as a Service” (SaaS). For example, at least some operations can be performed by a group of computers (as an example of machines including processors), wherein these operations are accessible via a network (e.g., the Internet) and via one or more appropriate interfaces (e.g., APIs). The execution of certain operations can be distributed among processors, residing not only within a single machine but also deployed across several machines. In some examples, the processor or processor-implemented component may be located in a single geographic location (e.g., within a home environment, office environment, or server cluster). In other examples, the processor or processor-implemented component may be distributed across several geographic locations.

[0172] "Computer-readable storage medium" refers to both machine-readable storage media and transmission media. Therefore, these terms encompass both storage devices / media and carrier / modulated data signals. The terms "machine-readable medium," "computer-readable medium," and "device-readable medium" refer to the same thing and can be used interchangeably in this disclosure.

[0173] A "brief message" is a message that can be accessed for a limited time. Brief messages can be text, images, videos, etc. The access time for a brief message can be set by the message sender. Alternatively, the access time can be a default setting or a setting specified by the recipient. Regardless of the setting method, the message is temporary.

[0174] "Machine storage medium" refers to one or more storage devices and media (e.g., centralized or distributed databases, and associated caches and servers) that store executable instructions, routines, and data. Therefore, this term should be considered to include, but is not limited to, solid-state memory and optical and magnetic media, including memory internal or external to the processor. Specific examples of machine storage media, computer storage media, and device storage media include: non-volatile memory, including, for example, semiconductor memory devices such as erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), FPGAs, and flash memory devices; disks, such as internal hard disks and removable disks; magneto-optical disks; and CD-ROM and DVD-ROM disks. The terms "machine storage medium," "device storage medium," and "computer storage medium" mean the same thing and may be used interchangeably in this disclosure. The terms "machine storage medium," "computer storage medium," and "device storage medium" expressly exclude carrier waves, modulated data signals, and other such media, at least some of which are covered by the term "signal medium."

[0175] "Non-transitory computer-readable storage medium" refers to a tangible medium capable of storing, encoding, or carrying instructions that can be executed by a machine.

[0176] "Signal medium" means any intangible medium capable of storing, encoding, or carrying machine-executable instructions and including digital or analog communication signals, or other intangible medium that facilitates the communication of software or data. The term "signal medium" should be considered to include any form of modulated data signal, carrier wave, etc. The term "modulated data signal" means a signal whose characteristics are set or altered in a manner that encodes information in the signal. The terms "transmission medium" and "signal medium" mean the same thing and may be used interchangeably in this disclosure.

Claims

1. A message sending and receiving method, comprising: A request is received by a messaging application running on the user's device to present augmented reality content associated with an image captured by the device's camera, the image depicting the user's face; In response to receiving the request, access is made to an augmented reality content item associated with applying makeup to the face, the augmented reality content being configured to generate a mesh for tracking multiple regions of the face; Receive user input selecting regions from the plurality of regions of the face; Determine at least one of a range of color values ​​or a range of contrast values ​​related to the available cosmetic products for the selected area; and Interface elements are presented in association with the face depicted in the image via the augmented reality content item. These interface elements are used by the user to select at least one of a color value within the color value range or a contrast value within the contrast value range. The interface element includes a first circle having an outer perimeter that depicts the range of color values, the outer perimeter allowing the user to select the color value via a tap gesture. The interface element also includes a second circle smaller than the first circle and located within the first circle, the second circle allowing the user to select the contrast value via a drag gesture.

2. The message sending and receiving method according to claim 1 further includes: Receive second user input selecting at least one of the color value or the contrast value; and The augmented reality content item displays a makeup overlay corresponding to the at least one color value or contrast value for a selected area of ​​the face.

3. The message sending and receiving method according to claim 2 further includes: Identify at least one cosmetic product corresponding to the cosmetic layering; and A second interface element is provided for adding the at least one cosmetic product to a shopping cart associated with the user's user account.

4. The message sending and receiving method according to claim 1 further includes: The messaging application displays a carousel interface for selecting augmented reality content items from multiple augmented reality content items; and The system receives the user's selection of augmented reality content items from the plurality of augmented reality content items via the carousel interface. The request corresponds to the user's selection.

5. A message transceiver device, comprising: processor; as well as A memory that stores instructions, which, when executed by the processor, configure the processor to perform operations including: A message-reading application running on a user's messaging device receives a request to present augmented reality content associated with an image captured by the device's camera, the image depicting the user's face; In response to receiving the request, access is made to an augmented reality content item associated with applying makeup to the face, the augmented reality content being configured to generate a mesh for tracking multiple regions of the face; Receive user input selecting regions from the plurality of regions of the face; Determine at least one of a range of color values ​​or a range of contrast values ​​related to the available cosmetic products for the selected area; and Interface elements are presented in association with the face depicted in the image via the augmented reality content item. These interface elements are used by the user to select at least one of a color value within the color value range or a contrast value within the contrast value range. The interface element includes a first circle having an outer perimeter that depicts the range of color values, the outer perimeter allowing the user to select the color value via a tap gesture. The interface element also includes a second circle smaller than the first circle and located within the first circle, the second circle allowing the user to select the contrast value via a drag gesture.

6. The message transceiver device according to claim 5, further comprising: Receive second user input selecting at least one of the color value or the contrast value; and The augmented reality content item displays a makeup overlay corresponding to the at least one color value or contrast value for a selected area of ​​the face.

7. The message transceiver device according to claim 6, further comprising: Identify at least one cosmetic product corresponding to the cosmetic layering; as well as A second interface element is provided for adding the at least one cosmetic product to a shopping cart associated with the user's user account.

8. The message transceiver device according to claim 5, further comprising: The messaging application displays a carousel interface for selecting augmented reality content items from multiple augmented reality content items; and The system receives the user's selection of augmented reality content items from the plurality of augmented reality content items via the carousel interface. The request corresponds to the user's selection.

9. A non-transitory computer-readable storage medium, the computer-readable storage medium comprising instructions that, when executed by a computer, cause the computer to perform the following operations: A request is received by a messaging application running on the user's device to present augmented reality content associated with an image captured by the device's camera, the image depicting the user's face; In response to receiving the request, access is made to an augmented reality content item associated with applying makeup to the face, the augmented reality content being configured to generate a mesh for tracking multiple regions of the face; Receive user input selecting regions from the plurality of regions of the face; Determine at least one of a range of color values ​​or a range of contrast values ​​related to the available cosmetic products for the selected area; and Interface elements are presented in association with the face depicted in the image via the augmented reality content item. These interface elements are used by the user to select at least one of a color value within the color value range or a contrast value within the contrast value range. The interface element includes a first circle having an outer perimeter that depicts the range of color values, the outer perimeter allowing the user to select the color value via a tap gesture. The interface element also includes a second circle smaller than the first circle and located within the first circle, the second circle allowing the user to select the contrast value via a drag gesture.

Images