CN116710895A - Body UI for augmented reality components - Google Patents

Abstract

The technical problem of providing a user interface element that can be activated without making physical contact with any particular device is solved by configuring an augmented reality component for displaying a non-touch user selectable element that can be activated in response to detecting a touch of an object from an output of a digital image sensor of an image capturing apparatus with the user selectable element. The augmented reality component detects the touching of a non-touch user selectable element with an object from the image of the person, such as a hand object, and in response triggers a predetermined action, such as starting or stopping the recording of the output of the digital image sensor or capturing a still image of the output of the digital image sensor.

Description

Body UI for augmented reality components

Priority claim

The present application claims priority from U.S. provisional application serial No. 63/131,393, filed on 12/29 in 2020, and U.S. patent application serial No. 17/248,876, filed on 11/2 2021, each of which is incorporated herein by reference in its entirety.

Technical Field

The present disclosure relates generally to facilitating interactions between a messaging client and a third party resource.

Background

The popularity of computer-implemented programs that allow users to access content online and interact with content and other users continues to grow. There are various computer-implemented applications that allow users to share content with other users through messaging clients. Some of such computer-implemented applications (referred to as apps) may be designed to run on mobile devices such as telephones, tablet computers, or wearable devices, while having backend services provided on a server computer system to perform operations (e.g., store large amounts of data or perform computationally expensive processes) that may require more resources than reasonable ones performed at a client device.

A messaging app executing at a client device may provide a User Interface (UI) that allows users to capture their own photos or videos using a front-facing camera of the client device and share the captured content to other devices. The UI provided by the messaging app may include various user-selectable elements that may be activated by touching a screen area displaying the user-selectable elements. For example, the UI may include user selectable elements that cause video recording to start and stop in response to a tap.

Drawings

In the drawings, which are not necessarily drawn to scale, like numerals may describe similar components in different views. To facilitate identification of a discussion of any particular element or act, one or more of the highest digit(s) in a reference number refers to the figure number in which that element was first introduced. Some embodiments are illustrated by way of example, and not by way of limitation, in the figures of the accompanying drawings in which:

FIG. 1 is a diagrammatic representation of a networking environment in which a developer tool system may be deployed, according to some examples.

Fig. 2 is a diagrammatic representation of a messaging system having functionality on both a client side and a server side in accordance with some examples.

FIG. 3 is a diagrammatic representation of a data structure maintained in a database in accordance with some examples.

Fig. 4 is a diagrammatic representation of a message according to some examples.

Fig. 5 is a flow diagram of an access restriction process according to some examples.

Fig. 6 is a flow chart of a method for enhancing a user's experience with Augmented Reality (AR) technology, according to some examples.

Fig. 7 is a diagrammatic representation of a camera view user interface with a loaded body UI AR component in accordance with some examples.

Fig. 8 is a diagrammatic representation of a camera view user interface displaying non-touch user selectable elements configured to cause recording of video in accordance with some examples.

Fig. 9 is a diagrammatic representation of a camera view user interface displaying a hand object in contact (collsion) with a non-touch user selectable element configured to cause recording of video in accordance with some examples.

FIG. 10 is a diagrammatical representation of a camera view user interface displaying a non-touch user selectable element configured to cause recording to cease, in accordance with some examples.

FIG. 11 is a diagrammatical representation of a camera view user interface displaying a touch of a hand object with a non-touch user selectable element configured to cause recording to cease in accordance with some examples.

Fig. 12 is a diagrammatic representation of a camera view user interface displaying a non-touch user-selectable element configured to cause an image to be captured with a camera and another non-touch user-selectable element configured to cause an item selection carousel to be replaced with a color selection carousel, according to some examples.

Fig. 13 is a diagrammatical representation of a camera view user interface displaying a touch of a hand object with a non-touch user selectable element configured to cause replacement of an item selection carousel with a color selection carousel in accordance with some examples.

Fig. 14 is a diagrammatical representation of a visual camera view user interface displaying replacement of an item selection carousel with a color selection carousel in accordance with some examples.

Fig. 15 is a diagrammatic representation of a camera view user interface displaying a color selection carousel in place of an item selection carousel in accordance with some examples.

Fig. 16 is a diagrammatic representation of a body image and anchor points assigned to various segments of the body in accordance with some examples.

FIG. 17 is a diagrammatic representation of machine in the form of a computer system within which a set of instructions, for causing the machine to perform any one or more of the methodologies discussed herein, may be executed according to some examples.

Detailed Description

Embodiments of the present disclosure improve the functionality of electronic messaging software and systems by enhancing the user's experience with Augmented Reality (AR) technology. The user's experience in participating in AR technology is enhanced by allowing the user to interact (engage) with user-selectable elements presented on the camera view screen without physically contacting the screen or with another device. User selectable elements that can interact with the screen in a non-touch manner without physical contact therewith can be advantageously used, particularly in a scenario in which the user is not holding a client device (e.g., a phone) but is a distance from the device. For example, a user may wish to be a distance from a client device to take a full-body photograph of themselves or to "try on" various virtual wearable items.

The technical problem of providing a User Interface (UI) element that can be activated (a function can be performed) in response to detecting a touch of an object from an output of a digital image sensor of an image pickup apparatus with a user selectable element is solved by configuring an AR component for displaying the UI element (also referred to as a user selectable element). For the purposes of this description, an AR component configured to display in an image capture device view screen a user-selectable element that can be activated in response to detecting a touch of an object from the output of the digital image sensor of the image capture device with the user-selectable element is referred to as a body UI AR component. One or more UI elements configured to allow a non-touch operation by means of detecting a touch of an object from an output of a digital image sensor of an image pickup device with a user-selectable element are collectively referred to as a body UI. A UI element configured to allow a non-touch operation by detecting a touch of an object from an output of a digital image sensor of an image pickup device with a user-selectable element is referred to as a non-touch user-selectable element. Fig. 7-11, which will be described further below, illustrate an example process of interacting with user-selectable elements in a non-touch manner in the context of starting and stopping recording of self-timer video. Fig. 12-15, which will be described further below, illustrate an example process of interacting with user-selectable elements in a non-touch manner in the context of a "try-on" virtual wearable item. A body UI comprising non-touch user selectable elements is provided in a messaging system hosting a back-end service for an associated messaging client.

A messaging system hosting a back-end service for an associated messaging client is configured to allow a user to capture images and video with a camera provided to a client device hosting the messaging client and to allow sharing of the captured content with other users via network communications. The messaging system is also configured to provide an AR component accessible via the messaging client. The AR component may be used to modify content displayed on or captured by the camera view screen, for example, by overlaying pictures or animations over captured image frames or video frames, or by adding three-dimensional (3D) effects, objects, characters, and transformations. The camera view screen (also referred to as a camera view UI) is displayed by the messaging client and includes an output of a digital image sensor of the camera, user selectable elements operable to capture images by the camera or operable to start and stop video recording, and may also display one or more user selectable elements representing respective AR components. The AR component may be implemented using a programming language (e.g., javaScript or Java) suitable for app development. The AR components are identified in the messaging server system by respective AR component identifiers. The user may access the functionality provided by the AR component by interacting with user-selectable elements included in the camera view UI presented by the messaging client. When the AR component is loaded, the output of the digital image sensor of the camera displayed in the camera view UI is enhanced with modifications provided by the AR component. For example, the AR component may be configured to detect a head position of a person captured by the digital image sensor and superimpose an image of the party cap over the detected head position such that a viewer will see the person presented on the camera view screen as if wearing the party cap. Loading the body UI AR component includes beginning to monitor the image of the person in the camera view to determine if the image is an image of the entire person, i.e., a whole body image. The determination is made by detecting anchor points assigned to respective segments of the image of the person in the camera view user interface.

The human body may be represented as a set of anchor points assigned to various segments of the body (e.g., skeletal joints), and corresponding distances between the skeletal joints represented by the anchor points. A set of anchors representing a person may include anchors assigned to the head, shoulder, elbow, wrist, hip, knee, and ankle. A set of anchor points representing an image comprising an object depicting a person may indicate whether the image is a whole body of the person. For example, if an object is associated with a set of anchors that includes anchors assigned to the head and shoulders but does not include anchors representing the ankle, knee, and hip, it may be inferred that the object represents a photograph of a person's head. On the other hand, if the subject is associated with a set of anchor points including anchor points assigned to the head, neck and shoulder and including anchor points representing the ankle, knee and hip, it can be inferred that the subject represents a whole-body image of a person. For the purposes of this description, an object depicting a person in an image may be referred to as a person only.

The system detects a person in the image using one or more machine learning models, such as, for example, a neural network, and determines anchor points assigned to the depicted person. The machine learning model is trained using a set of training images depicting a person. In some examples, during training, a machine learning model receives a training image depicting a person, extracts one or more features from the training image, and estimates a set of anchor points assigned to the depicted person based on the extracted features. The estimated anchor point is compared to a ground score (ground score), and based on the compared variance threshold, the machine learning model updates one or more coefficients with another training image from the training image set and repeats the process. After a specified number of epochs (epochs) and/or when the variance threshold reaches a specified value, the machine learning model module completes training and parameters and coefficients of the machine learning model are stored. The trained machine learning model takes as input an image depicting a person and generates a set of anchor points assigned to the depicted person. Fig. 16 is a diagram 1600 of an example anchor 1602 assigned to a depicted person. Anchor points 1602 include anchor points assigned to the head, shoulder, elbow, wrist, hip, knee, and ankle of the depicted person. The example body UI AR component may be configured to determine that the depiction of the person is a whole-body depiction based on the presence of a set of whole-body indication anchors. A set of anchors including anchors assigned to at least the shoulder, hip, and knee may be defined as a whole body indication set. At least a group of anchors that does not include anchors assigned to the shoulder, hip, and knee is not a whole body indication set.

When a whole body image is detected in the camera view screen, the body UI AR component displays a non-touch user selectable element in the camera view UI. The non-touch user selectable element may be placed in a position relative to the image of the person in the camera view screen; for example, the body UI AR may be configured to track movement of the image of the person on the camera view screen and change the position of the non-touch user selectable element in a manner that keeps the non-touch user selectable element within a distance from a shoulder object in the image of the person. The body UI AR component detects the touching of the non-touch user selectable element with the hand object from the image of the person and in response triggers a predetermined action, such as starting or stopping the recording of the output of the digital image sensor or capturing a still image of the output of the digital image sensor. Content captured by the camera using the human UI AR component may be shared to other computing devices.

Networked computing environment

Fig. 1 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 the client device 102, each instance hosting several applications including a messaging client 104. Each messaging client 104 is communicatively coupled to a messaging server system 108 and other instances of the messaging client 104 via a network 106 (e.g., the internet).

The messaging client 104 is capable of communicating and exchanging data with another messaging client 104 and a messaging server system 108 via a network 106. The data exchanged between the messaging clients 104 and the messaging server system 108 includes functions (e.g., commands to invoke the functions) as well as payload data (e.g., text, audio, video, or other multimedia data). For example, the messaging client 104 allows a user to access functionality provided by the body UI AR component, which may reside at least partially at the messaging server system 108.

The messaging server system 108 provides server-side functionality to particular messaging clients 104 via the network 106. Although certain functions of the messaging system 100 are described herein as being performed by the messaging client 104 or by the messaging server system 108, whether certain functions are located within the messaging client 104 or within the messaging server system 108 may be a design choice. For example, it may be technically preferable to: certain techniques and functions are initially deployed within the messaging server system 108, but later migrated to the messaging client 104 where the client device 102 has sufficient processing power.

The messaging server system 108 supports various services and operations provided to the messaging client 104. Such operations include sending data to the messaging client 104, receiving data from the messaging client 104, and processing data generated by the messaging client 104. As examples, the data may include message content, client device information, geographic location information, media enhancements and overlays, message content persistence conditions, social network information, and live event information. The exchange of data within the messaging system 100 is invoked and controlled by functions available via a User Interface (UI) of the messaging client 104. For example, the messaging client 104 may present a camera view user interface that displays output of a digital image sensor of the camera provided to the client device 102 and also displays user selectable elements operable to load the body UI AR component in the messaging client 104.

Turning now specifically to messaging server system 108, application Program Interface (API) server 110 is coupled to application server 112 and provides a programming interface to application server 112. The application server 112 is communicatively coupled to a database server 118, which facilitates access to a database 120, which database 120 stores data associated with messages processed by the application server 112. Similarly, web server 124 is coupled to application server 112 and provides a web-based interface to application server 112. To this end, web server 124 processes incoming network requests via hypertext transfer protocol (HTTP) and several other related protocols.

An Application Program Interface (API) server 110 receives and transmits message data (e.g., command and message payloads) between the client device 102 and an application server 112. In particular, an Application Program Interface (API) server 110 provides a set of interfaces (e.g., routines and protocols) that may be invoked or queried by the messaging client 104 to activate functions of the application server 112. An Application Program Interface (API) server 110 discloses various functions supported by an application server 112, including: registering an account; a login function; sending a message from a particular messaging client 104 to another messaging client 104 via the application server 112; transmitting a media file (e.g., image or video) from the messaging client 104 to the messaging server 114 and for possible access by another messaging client 104; setting a collection of media data (e.g., stories); retrieving a friends list of the user of the client device 102; retrieving such a collection; retrieving the message and the content; adding and deleting entities (e.g., friends) in an entity graph (e.g., social graph); locating friends within the social graph; and open application events (e.g., related to messaging client 104).

The application server 112 hosts several server applications and subsystems, including, for example, a messaging server 114, an image processing server 116, and a social networking server 122. The messaging server 114 implements several message processing techniques and functions, particularly those related to the aggregation and other processing of content (e.g., text and multimedia content) included in messages received from multiple instances of the messaging client 104. As will be described in further detail, text and media content from multiple sources may be aggregated into a collection of content (e.g., referred to as a story or gallery). These sets are then made available to the messaging client 104. Such processing may also be performed by the messaging server 114 on the server side in view of hardware requirements for other processors and memory intensive processing of data.

The application server 112 also includes an image processing server 116, which image processing server 116 is dedicated to performing various image processing operations, typically with respect to images or video within the payload of messages sent from the messaging server 114 or received at the messaging server 114. Some of the various image processing operations may be performed by various AR components, which may be hosted or supported by image processing server 116.

The social networking server 122 supports various social networking functions and services and makes these functions and services available to the messaging server 114. To this end, social network server 122 maintains and accesses entity graph 306 (shown in FIG. 3) within database 120. Examples of functions and services supported by the social network server 122 include identifying other users in the messaging system 100 that have a "friends" relationship with a particular user or that the particular user is "focusing on," as well as identifying interests and other entities of the particular user.

System architecture

Fig. 2 is a block diagram illustrating further details regarding the messaging system 100 according to some examples. In particular, the messaging system 100 is shown to include a messaging client 104 and an application server 112. The messaging system 100 includes several subsystems that are supported on the client side by the messaging client 104 and on the server side by the application server 112. These subsystems include, for example, a transient timer system 202, a collection management system 204, and an enhancement system 206.

The ephemeral timer system 202 is responsible for implementing temporary or time-limited access to content by the messaging client 104 and the messaging server 114. The ephemeral timer system 202 includes a number of timers that selectively enable access (e.g., for presentation and display) of messages and associated content via the messaging client 104 based on a duration and display parameters associated with the message or collection of messages (e.g., a story). Additional details regarding the operation of the transient timer system 202 are provided below.

The collection management system 204 is responsible for managing collections or collections of media (e.g., collections of text, images, video, and audio data). The collection of content (e.g., messages, including images, video, text, and audio) may be organized into an "event gallery" or "event story. Such a collection may be made available for a specified period of time (e.g., the duration of the event to which the content relates). For example, content related to a concert may be made available as a "story" for the duration of the concert. In another example, the collection may include content generated using one or more AR components including a body UI AR component. The collection management system 204 may also be responsible for publishing icons to the user interface of the messaging client 104 that provide notifications regarding the presence of particular collections.

In addition, the collection management system 204 also includes a curation interface 212 that enables a collection manager to manage and curate a particular collection of content. For example, the curation interface 212 enables an event organizer to curate a collection of content related to a particular event (e.g., delete inappropriate content or redundant messages). In addition, the collection management system 204 employs machine vision (or image recognition techniques) and content rules to automatically curate the collection of content. In some examples, the user may be paid the compensation by including the user-generated content into the collection. In such cases, the collection management system 204 operates to automatically pay such users to use their content.

The enhancement system 206 provides various functions that enable a user to enhance (e.g., annotate or otherwise modify or edit) media content that may be associated with a message. For example, the enhancement system 206 provides functionality related to generating and publishing media overlays for messages processed by the messaging system 100. The media overlay may be stored in database 120 and accessed through database server 118.

In some examples, the enhancement system 206 is configured to provide access to AR components, which may be implemented using a programming language suitable for app development (such as, for example, javaScript or Java) and identified in the messaging server system by a corresponding AR component identifier. The AR component may include or reference various image processing operations corresponding to image modification, filtering, media overlay, transformation, and the like. These image processing operations may provide an interactive experience of a real world environment in which perceived information generated by a computer enhances objects, surfaces, backgrounds, lighting, etc., captured by a digital image sensor or camera device. In this context, the AR component includes a collection of data, parameters, and other assets required to apply the selected augmented reality experience to an image or video feed.

In some implementations, the AR component includes a module configured to modify or transform image data presented within a Graphical User Interface (GUI) of a client device in some manner. For example, the AR component data may be used to perform complex additions or transformations to the content image, such as adding rabbit ears to the head of a person in a video clip, adding a floating heart with background color to a video clip, changing the scale of features of a person within a video clip, or many other such transformations. This includes real-time modifications that modify an image as it is captured using a camera associated with the client device and then display the image on the screen of the client device with AR content modifications, which may use, for example, video clips in a library of AR component modifications, as well as modifications to the stored content.

Various augmented reality functions that may be provided by the AR component include: detecting objects (e.g., faces, hands, bodies, cats, dogs, surfaces, objects, etc.), tracking such objects as they leave, enter, and move around the field of view in the video frame, and modifying or transforming such objects as they are tracked. In various embodiments, different methods for achieving such conversions may be used. For example, some implementations may involve generating a 3D mesh model of one or more objects and implementing the transformation using a transformation of the model within the video and an animated texture. In other embodiments, tracking of points on an object may be used to place an image or texture (which may be two-dimensional or three-dimensional) at the tracked location. In yet further embodiments, neural network analysis of video frames may be used to place images, models, or textures into content (e.g., images or video frames). Thus, the AR component data refers to both the images, models, and textures used to create the transformations in the content, as well as the additional modeling and analysis information needed to implement such transformations with object detection, tracking, and placement. The body UI AR component may include other AR functions such as those described above in addition to the functions that allow non-touch operation.

Data architecture

Fig. 3 is a schematic diagram illustrating a data structure 300 that may be stored in the database 120 of the messaging server system 108, according to some examples. While the contents of database 120 are shown as including several tables, it will be appreciated that the data may be stored in other types of data structures (e.g., as an object-oriented database).

Database 120 includes message data stored within message table 302. For any particular message, the message data includes at least message sender data, message recipient (or recipient) data, and a payload. The payload of the message may include content generated using the body UI AR component. Additional details regarding information that may be included in messages and in message data stored in message table 302 are described below with reference to fig. 4.

The entity table 304 stores entity data and is linked (e.g., referenced) to the entity graph 306 and profile data 308. The entities for which records are maintained within entity table 304 may include individuals, corporate entities, organizations, objects, sites, events, and the like. Regardless of the entity type, any entity about which the messaging server system 108 stores data may be an identified entity. Each entity is provided with a unique identifier as well as an entity type identifier (not shown).

The entity map 306 stores information about relationships and associations between entities. By way of example only, such relationships may be interest-based or activity-based social relationships, professional relationships (e.g., working at a common company or organization). Referring to the functionality provided by the AR component, the entity diagram 306 stores information that may be used to determine another profile connected to the profile representing the user controlling the associated client device if the AR component is configured to allow modification of the target media content object using a different portrait image of the user than the portrait image of the user controlling the associated client device. As described above, the portrait image of the user may be stored in a user profile representing the user in the messaging system.

The profile data 308 stores a plurality of types of profile data regarding a particular entity. The profile data 308 may be selectively used and presented to other users of the messaging system 100 based on privacy settings specified by a particular entity. In the case where the entity is a person, the profile data 308 includes, for example, a user name, a telephone number, an address, settings (e.g., notification and privacy settings), and a user-selected avatar representation (or a collection of such avatar representations). A particular user may then selectively include one or more of these avatar representations in the content of messages transmitted via messaging system 100 and on a map interface displayed by messaging client 104 to other users. The set of avatar representations may include a "status avatar" that presents graphical representations of status or activities that the user may select to transmit at a particular time.

Database 120 also stores enhancement data in enhancement table 310. Enhancement data is associated with and applied to video (data of the video is stored in the video table 314) and images (data of the images is stored in the image table 316). In some examples, the enhancement data is used by various AR components including AR components. Examples of enhancement data are target media content objects, which as described above, may be associated with an AR component and used to generate an AR experience for a user.

Another example of augmentation data is an Augmented Reality (AR) tool that may be used by an AR component to implement image transformations. The image transformation includes real-time modifications that modify an image (e.g., a video frame) as it is captured using the digital image sensor of the client device 102. The modified image is displayed on the screen of the client device 102 along with the modification. The AR tool may also be used to apply modifications to stored content, such as video clips or still images stored in a gallery. In a client device 102 having access to multiple AR tools, a user may apply different AR tools to a single video segment (e.g., by participating in different AR components configured to utilize the different AR tools) to see how the different AR tools will modify the same video segment. For example, multiple AR tools applying different pseudo-random motion models may be applied to the same captured content by selecting different AR tools for the same captured content. Similarly, real-time video capture may be used with the illustrated modifications to show how a video image currently captured by a digital image sensor provided with camera means of the client device 102 will modify the captured data. Such data may be displayed on the screen only and not stored in memory, or content captured by the digital image sensor may be recorded and stored in memory with or without modification (or both). The messaging client 104 may be configured to include a preview feature that may display how modifications produced by different AR tools will be viewed simultaneously within different windows in the display. This may, for example, allow a user to view multiple windows with different pseudo-random animations presented simultaneously on a display.

In some examples, when a particular modification is selected along with the content to be transformed, the element to be transformed is identified by the computing device and then detected and tracked if the element to be transformed is present in a frame of the video. Elements of the object are modified according to the modification request, thereby transforming frames of the video stream. For different types of transformations, the transformation of frames of the video stream may be performed by different methods. For example, for transformations of frames that primarily involve changing the form of the elements of the object, feature points of each of the elements of the object are computed (e.g., using an Active Shape Model (ASM) or other known methods). Then, a feature point-based mesh is generated for each of the at least one element of the object. The grid is used at a later stage to track elements of objects in the video stream. During the tracking process, the mentioned grid of each element is aligned with the position of each element. Additional points are then generated on the grid. A first set of first points is generated for each element based on the modification request, and a set of second points is generated for each element based on the set of first points and the modification request. The frames of the video stream may then be converted by modifying the elements of the object based on the set of first points and the set of second points and the grid. In such a method, the background of the modified object may also be changed or distorted by tracking and modifying the background.

In some examples, transforming some regions of the object using elements of the object may be performed by computing feature points for each element of the object and generating a grid based on the computed feature points. Points are generated on the grid, and then various regions are generated based on the points. The elements of the object are then tracked by aligning the region of each element with the position of each of the at least one element, and the attributes of the region may be modified based on the request for modification, thereby transforming the frames of the video stream. The properties of the mentioned areas may be transformed in different ways depending on the specific modification request. Such modifications may involve: changing the color of the region; removing at least some partial regions from frames of the video stream; including one or more new objects in the region (based on the modification request); and modifying or distorting elements of the region or object. In various embodiments, any combination of such modifications or other similar modifications may be used. For some models to be animated, some feature points may be selected as control points for determining the entire state space for the options for model animation.

Story table 312 stores data about a collection of messages and associated image, video, or audio data that is assembled into a collection (e.g., a story or library). Creation of a particular collection may be initiated by a particular user (e.g., each user whose record is maintained in entity table 306). The user may create a "personal story" in the form of a collection of content that has been created and transmitted/broadcast by the user. To this end, the user interface of the messaging client 104 may include user selectable icons to enable the sending user to add particular content to his or her personal story. In some examples, story table 312 stores one or more images or videos created using the AR component.

The collection may also constitute a "live story" that 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" may constitute a curated stream of user-submitted content from different locations and events. A user whose client device enables a positioning service and at a particular time is at a co-location event may be presented with an option to contribute content to a particular live story, for example, via a user interface of messaging client 104. The live story may be identified to the user by the messaging client 104 based on his or her location. The end result is a "live story" told from a community perspective.

Another type of collection of content is referred to as a "location story" that enables users whose client devices 102 are located within a particular geographic location (e.g., at a college or university campus) to contribute to the particular collection. In some examples, the contribution to the positioning story may require a secondary authentication to verify that the end user belongs to a particular organization or other entity (e.g., is a student in a university campus).

As mentioned above, the video table 314 stores video data, which in one example is associated with messages whose records are maintained within the message table 302. Similarly, image table 316 stores image data associated with messages whose message data is stored in entity table 304. Entity table 304 may associate various enhancements from enhancement table 310 with various images and videos stored in image table 316 and video table 314.

Data communication architecture

Fig. 4 is a schematic diagram illustrating the structure of a message 400, the message 400 generated by a messaging client 104 for transmission to another messaging client 104 or messaging server 114, according to some examples. The contents of a particular message 400 are used to populate a message table 302 stored within the database 120, the message table 302 being accessible by the messaging server 114. Similarly, the content of message 400 is stored in memory as "in-flight" or "in-flight" data for client device 102 or application server 112. In some examples, the content of message 400 includes an image or video created using an AR component. Message 400 is shown as including the following example components:

message identifier 402: a unique identifier that identifies the message 400.

Message text payload 404: text to be generated by a user via a user interface of the client device 102 and included in the message 400.

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. Image data for the transmitted or received message 400 may be stored in the image table 316.

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

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

Message enhancement data 412: enhancement data (e.g., filters, stickers, or other annotations or enhancements) representing enhancements to the message image payload 406, the message video payload 408, the message audio payload 410 to be applied to the message 400. Enhancement data for a transmitted or received message 400 may be stored in the enhancement table 310.

Message duration parameter 414: parameter values indicating the amount of time in seconds that the content of the message (e.g., message image payload 406, message video payload 408, message audio payload 410) will be presented to or made accessible to the user via the messaging client 104.

Message geolocation parameters 416: geolocation data (e.g., latitude and longitude coordinates) associated with the content payload of the message. A plurality of 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 particular image within the message image payload 406 or a particular video within the message video payload 408).

Message story identifier 418: an identifier value that identifies one or more content collections (e.g., the "story" identified in story table 312), wherein particular content items in message image payload 406 of message 400 are associated with the one or more content collections. For example, the identifier value may be used to associate a plurality of images within the message image payload 406 with a plurality of content sets each.

Message tag 420: each message 400 may be tagged with a plurality of tags, each of which indicates the subject matter of the content included in the message payload. For example, where a particular image included in the message image payload 406 depicts an animal (e.g., a lion), a tag value indicating the relevant animal may be included in the message tag 420. The tag value may be generated manually based on user input or may be generated automatically using, for example, image recognition.

Message sender identifier 422: an identifier (e.g., a messaging system identifier, an email address, or a device identifier) indicating the user of the client device 102 on which the message 400 was generated and from which the message 400 was sent.

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

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

Time-based access restriction architecture

Fig. 5 is a schematic diagram illustrating an access restriction process 500 according to which access to content (e.g., ephemeral messages 502 and associated multimedia data payloads) or a collection of content (e.g., ephemeral message groups 504) may be time-limited (e.g., such that it is ephemeral). In some examples, the content of ephemeral message 502 includes an image or video created using a body UI AR component.

The ephemeral message 502 is shown as being associated with a message duration parameter 506, the value of the message duration parameter 506 determining the amount of time that the messaging client 104 will display the ephemeral message 502 to the receiving user of the ephemeral message 502. In one example, a receiving user may view the ephemeral message 502 for up to 10 seconds, depending on the amount of time the sending user has specified using the message duration parameter 506.

The message duration parameter 506 and the message recipient identifier 424 are shown as inputs to a message timer 512, which message timer 512 is responsible for determining the amount of time that the ephemeral message 502 is shown to a particular receiving user identified by the message recipient identifier 424. In particular, the transient message 502 is only shown to the relevant receiving user for a period of time determined by the value of the message duration parameter 506. The message timer 512 is shown to provide output to a more generalized ephemeral timer system 202, which ephemeral timer system 202 is responsible for overall timing of the display of content (e.g., ephemeral message 502) to a receiving user.

The ephemeral messages 502 shown in fig. 5 are included within an ephemeral message group 504 (e.g., collection of messages in a personal story or an event story). The ephemeral message group 504 has an associated group duration parameter 508, the value of the group duration parameter 508 determining the duration that the ephemeral message group 504 is presented and accessible by a user of the messaging system 100. For example, the group duration parameter 508 may be a duration of a concert, where the ephemeral message group 504 is a collection of content about the concert. Alternatively, the user (owning user or curator user) may specify the value of the group duration parameter 508 when performing the setting and creation of the ephemeral message group 504.

In addition, each ephemeral message 502 within the ephemeral message group 504 has an associated group participation parameter 510, the value of the group participation parameter 510 determining the duration of time that the ephemeral message 502 is accessible within the context of the ephemeral message group 504. Thus, before the ephemeral message group 504 itself expires according to the group duration parameter 508, a particular ephemeral message group 504 may "expire" and become inaccessible in the context of the ephemeral message group 504. The group duration parameter 508, the group participation parameter 510, and the message recipient identifier 424 each provide input to the group timer 514, and the group timer 514 is operable to first determine whether a particular ephemeral message 502 of the ephemeral message group 504 is to be displayed to a particular receiving user, and if so, how long to display. Note that due to the message recipient identifier 424, the ephemeral message group 504 also knows the identity of the particular recipient user.

Thus, the group timer 514 is operable to control the overall lifetime of the associated ephemeral message group 504 and the individual ephemeral messages 502 included in the ephemeral message group 504. In one example, each ephemeral message 502 within the ephemeral message group 504 remains viewable and accessible for a period of time specified by the group duration parameter 508. In another example, within the context of the ephemeral message group 504, a certain ephemeral message 502 may expire based on the group participation parameter 510. Note that even within the context of the ephemeral message group 504, the message duration parameter 506 may still determine the duration of displaying the particular ephemeral message 502 to the receiving user. Thus, the message duration parameter 506 determines the duration of displaying a particular ephemeral message 502 to a receiving user, regardless of whether the receiving user views the ephemeral message 502 within or outside the context of the ephemeral message group 504.

The ephemeral timer system 202 may also be operable to remove a particular ephemeral message 502 from the ephemeral message group 504 based on determining that the associated group participation parameter 510 has been exceeded. For example, when the sending user has established a group participation parameter 510 of 24 hours from release, the ephemeral timer system 202 will remove the relevant ephemeral message 502 from the ephemeral message group 504 after the specified 24 hours. The ephemeral timer system 202 also operates to remove the ephemeral message group 504 when the group participation parameter 510 of each ephemeral message 502 within the ephemeral message group 504 has expired, or when the ephemeral message group 504 itself has expired according to the group duration parameter 508.

In some use cases, the creator of a particular ephemeral message group 504 may specify an deadline group duration parameter 508. In this case, the expiration of the group participation parameter 510 of the last remaining ephemeral message 502 within the ephemeral message group 504 will determine when the ephemeral message group 504 itself has expired. In this case, the new ephemeral message 502 with the new group participation parameter 510 added to the ephemeral message group 504 actually extends the lifetime of the ephemeral message group 504 to be equal to the value of the group participation parameter 510.

In response to the ephemeral timer system 202 determining that the ephemeral message group 504 has expired (e.g., is no longer accessible), the ephemeral timer system 202 communicates with the messaging system 100 (and, in particular, the messaging client 104, for example) such that the indicia (e.g., icon) associated with the relevant ephemeral message group 504 is no longer displayed within the user interface of the messaging client 104. Similarly, when the ephemeral timer system 202 determines that the message duration parameter 506 for a particular ephemeral message 502 has expired, the ephemeral timer system 202 causes the messaging client 104 to no longer display a marker (e.g., an icon or text identification) associated with the ephemeral message 502.

FIG. 6 is a flow chart of a method 600 for providing an augmented reality experience according to some examples. In an example embodiment, some or all of the processing logic resides at the client device 102 of fig. 1 and/or at the messaging server system 108 of fig. 1. The method 600 begins at operation 610, at which operation 610 the enhancement system 206 of fig. 2 configures a body UI AR component for detecting anchor points assigned to segments of a body image. As described above, the human body may be represented as a set of anchor points assigned to various segments of the body. As shown in fig. 16, a set of anchor points representing a person may include anchor points assigned to the head, shoulder, elbow, wrist, hip, knee, and ankle. At operation 620, the body UI AR component is loaded in a camera view user interface of a messaging client at the client device. The loading operation includes beginning to detect anchor points of respective segments of the image assigned to the person in the camera view user interface. At operation 630, the loaded body UI AR component determines that the detected anchor point includes a whole body indication set of the anchor point. A whole body indication set of anchors may be defined as a set of anchors including anchors assigned to at least the shoulder and hip. As described above, detecting anchor points of individual segments of an image assigned to a person in a camera view user interface may be implemented by executing a machine learning model trained using a training image set. A machine learning model (e.g., neural network) takes an image of a person as input and produces a set of anchor points as output. At operation 640, in response to determining that the detected anchor point includes a whole body indication set of the anchor point, the body UI AR component causes a non-touch user selectable element to be displayed in the camera view user interface, the non-touch user selectable element configured to trigger an action in the messaging system in response to the non-touch user selectable element touching a trigger section of the image from the person. The action may be taking a picture or starting recording a video with the camera of the client device, as well as other actions such as changing or replacing a carousel of selectable user elements. Displaying the non-touch user selectable element in the camera view user interface may include tracking a position of a body segment object (e.g., a shoulder object) in the image of the person and displaying the non-touch user selectable element in the camera view user interface at a position determined based on the tracked position of the body segment object.

Fig. 7-15 illustrate camera view screens presented on a display device when a user is participating in an AR experience provided by a body UI AR component. Fig. 7 is a diagrammatic representation of a camera view user interface 700 with loaded body UI AR components in accordance with some examples. Fig. 8 is a diagrammatic representation of a camera view user interface 800 displaying non-touch user selectable elements configured to cause recording of video in accordance with some examples. Fig. 9 is a diagrammatical representation of a camera view user interface 900 displaying a touch of a hand object with a non-touch user selectable element configured to cause recording of video in accordance with some examples. Fig. 10 is a diagrammatic representation of a camera view user interface 1000 displaying a non-touch user selectable element configured to cause recording to cease, according to some examples. FIG. 11 is a diagrammatical representation of a camera view user interface 1100 displaying a touch of a hand object with a non-touch user selectable element configured to cause recording to cease, in accordance with some examples. Fig. 12 is a diagrammatic representation of a camera view user interface 1200 displaying a non-touch user-selectable element configured to cause an image to be captured with a camera and another non-touch user-selectable element configured to cause an item selection carousel to be replaced with a color selection carousel, according to some examples. Fig. 13 is a diagrammatical representation of a camera view user interface 1300 displaying a touch of a hand object with a non-touch user selectable element configured to cause replacement of an item selection carousel with a color selection carousel in accordance with some examples. Fig. 14 is a diagrammatic representation of a visual camera view user interface 1400 displaying replacement of an item selection carousel with a color selection carousel in accordance with some examples. Fig. 15 is a diagrammatical representation of a camera view user interface 1500 displaying a color selection carousel in place of an item selection carousel in accordance with some examples.

Machine architecture

Fig. 17 is a diagrammatic representation of a machine 1700 within which instructions 1708 (e.g., software, programs, applications, applets, apps, or other executable code) for causing the machine 1700 to perform any one or more of the methods discussed herein may be executed. For example, the instructions 1708 may cause the machine 1700 to perform any one or more of the methods described herein. The instructions 1708 transform a generic, un-programmed machine 1700 into a specific machine 1700 that is programmed to perform the functions described and illustrated in the manner described. The machine 1700 may operate as a standalone device or may be coupled (e.g., networked) to other machines. In a networked deployment, the machine 1700 may operate in the capacity of a server machine or a client machine in a server-client network environment, or as a peer machine in a peer-to-peer (or distributed) network environment. Machine 1700 may include, but is not limited to: a server computer, a client computer, a Personal Computer (PC), a tablet computer, a laptop computer, a netbook, a set-top box (STB), a Personal Digital Assistant (PDA), an entertainment media system, a cellular telephone, a smart phone, a mobile device, a wearable device (e.g., a smart watch), a smart home device (e.g., a smart appliance), other smart device, a web appliance, a network router, a network switch, a network bridge, or any machine capable of executing instructions 1708 that specify actions to be taken by machine 1700, sequentially or otherwise. Furthermore, while only a single machine 1700 is illustrated, the term "machine" shall also be taken to include a collection of machines that individually or jointly execute instructions 1708 to perform any one or more of the methodologies discussed herein. For example, the machine 1700 may include the client device 102 or any one of several server devices that form part of the messaging server system 108. In some examples, machine 1700 may also include both a client and a server system, where certain operations of a particular method or algorithm are performed on the server side and certain operations of a particular method or algorithm are performed on the client side.

The machine 1700 may include a processor 1702, a memory 1704, and input/output (I/O) components 1738 that may be configured to communicate with each other via a bus 1740. In an example, the processor 1702 (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, the processor 1706 and the processor 1710 that execute the instructions 1708. The term "processor" is intended to include a multi-core processor, which may include two or more separate processors (sometimes referred to as "cores") that may execute instructions simultaneously. Although fig. 17 shows multiple processors 1702, machine 1700 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.

The memory 1704 includes a main memory 1712, a static memory 1714, and a storage unit 1716, the main memory 1712, static memory 1714, and storage unit 1716 being accessible by the processor 1702 via the bus 1740. The main memory 1704, static memory 1714, and storage unit 1716 store instructions 1708 that implement any one or more of the methods or functions described herein. The instructions 1708 may also reside, completely or partially, within the main memory 1712, within the static memory 1714, within the machine-readable medium 1718 within the storage unit 1716, within at least one of the processors 1702 (e.g., within the cache memory of the processor), or any suitable combination thereof, during execution thereof by the machine 1700.

I/O component 1738 can include various components for receiving input, providing output, generating output, sending information, exchanging information, capturing measurements, and the like. The particular I/O components 1738 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 would likely not include such a touch input device. It should be appreciated that I/O component 1738 may include many other components not shown in fig. 17. In various examples, I/O components 1738 may include user output components 1724 and user input components 1726. The user output components 1724 may include visual components (e.g., a display such as a Plasma Display Panel (PDP), a Light Emitting Diode (LED) display, a Liquid Crystal Display (LCD), a projector, or a Cathode Ray Tube (CRT)), audible components (e.g., speakers), tactile components (e.g., vibration motor, resistance mechanism), other signal generators, and so forth. The user input component 1726 can include an alphanumeric input component (e.g., a keyboard, a touch screen configured to receive alphanumeric input, an optical keyboard, or other alphanumeric input component), a point-based input component (e.g., a mouse, a touchpad, a trackball, a joystick, a motion sensor, or another pointing instrument), a tactile input component (e.g., a physical button, a touch screen providing the location and/or force of a touch or touch gesture, or other tactile input component), an audio input component (e.g., a microphone), and so forth.

In other examples, I/O components 1738 may include biometric components 1728, motion components 1730, environmental components 1732, or positioning components 1734, among various other components. For example, biometric component 1728 includes components for detecting expressions (e.g., hand expressions, facial expressions, voice expressions, body gestures, or eye tracking), measuring biological signals (e.g., blood pressure, heart rate, body temperature, perspiration, or brain waves), identifying a person (e.g., voice recognition, retinal recognition, facial recognition, fingerprint recognition, or electroencephalogram-based recognition), and the like. The motion component 1730 includes an acceleration sensor component (e.g., accelerometer), a gravity sensor component, a rotation sensor component (e.g., gyroscope).

Environmental components 1732 include, for example, one or more cameras (with still image/photo and video capabilities), illumination sensor components (e.g., photometer), temperature sensor components (e.g., one or more thermometers that detect ambient temperature), humidity sensor components, pressure sensor components (e.g., barometer), acoustic sensor components (e.g., one or more microphones that detect background noise), proximity sensor components (e.g., infrared sensors that detect nearby objects), gas sensors (e.g., gas detection sensors that detect the concentration of hazardous gases or measure contaminants in the atmosphere for safety), or other components that may provide an indication, measurement, or signal corresponding to the surrounding physical environment.

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

Further, the camera system of the client device 102 may include dual rear-facing cameras (e.g., a main camera and a depth sensing camera), or even triple, quadruple, or quintuple rear-facing camera configurations on the front-to-back side of the client device 102. For example, these multiple camera systems may include a wide-angle camera, an ultra-wide-angle camera, a tele camera, a macro camera, and a depth sensor.

Positioning component 1734 includes a positioning sensor component (e.g., a GPS receiver component), an altitude sensor component (e.g., an altimeter or barometer that detects barometric pressure at which altitude may be obtained), an orientation sensor component (e.g., a magnetometer), and so forth.

Communication may be implemented using a variety of techniques. I/O component 1738 also includes a communication component 1736, the communication component 1736 being operable to couple the machine 1700 to the network 1720 or device 1722 via a corresponding coupling or connection. For example, communication component 1736 may include a network interface component or another suitable device to interface with network 1720. In other examples, communication component 1736 may include a wired communication component, a wireless communication component, a cellular communication component, a Near Field Communication (NFC) component,Parts (e.g.)>Low energy),%>Means, and other communication means for providing communication via other modes. Device 1722 may be other machines or any of a variety of peripheral devices (e.g., coupled via USBPeripheral devices).

Further, the communication component 636 may detect an identifier or include components operable to detect an identifier. For example, the communication component 636 can 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 matrices, data symbols (Dataglyph), maximum codes (MaxiCode), PDF417, ultra codes (arc Code), UCC RSS-2D barcodes, and other optical codes) or an acoustic detection component (e.g., a microphone for identifying marked audio signals). In addition, various information may be derived via communication component 1736, e.g., location derived via Internet Protocol (IP) geolocation, via A signal triangulated location, a location derived via detection of NFC beacon signals that may indicate a particular location, etc.

The various memories (e.g., main memory 1712, static memory 1714, and memory of processor 1702) and storage unit 1716 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., instructions 1708), when executed by the processor 1702, cause various operations to implement the disclosed examples.

The instructions 1708 may be transmitted or received over the network 1720 via a network interface device (e.g., a network interface component included in the communications component 1736) using a transmission medium and using any one of several well-known transmission protocols (e.g., hypertext transfer protocol (HTTP)). Similarly, instructions 1708 may be transmitted or received via a coupling (e.g., peer-to-peer coupling) to device 1722 using a transmission medium.

Glossary of terms

"carrier signal" refers to any intangible medium capable of storing, encoding or carrying instructions for execution by a machine, and includes digital or analog communications signals or other intangible medium to facilitate communication of such instructions. The instructions may be transmitted or received over a network via a network interface device using a transmission medium.

"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. The client device may be, but is not limited to, a mobile phone, desktop computer, laptop computer, portable Digital Assistant (PDA), smart phone, tablet computer, super book, netbook, laptop computer, multiprocessor system, microprocessor-based or programmable consumer electronics, game console, set top box, or any other communication device that a user can use to access a network.

"communication network" refers to one or more portions of a network, the network may be an ad hoc network, an intranet, an extranet, a Virtual Private Network (VPN), a Local Area Network (LAN), a Wireless LAN (WLAN), a Wide Area Network (WAN), a Wireless WAN (WWAN), a Virtual Private Network (VPN) Metropolitan Area Networks (MANs), the Internet, portions of the Public Switched Telephone Network (PSTN), plain Old Telephone Service (POTS) networks, cellular telephone networks, wireless networks,A network, other type of network, or a combination of two or more such networks. For example, the network or portion of the network may comprise a wireless network or cellular network, and the coupling may be a Code Division Multiple Access (CDMA) connection, a global system for mobile communications (GSM) connection, or other type of cellular or wireless coupling. In this example, the coupling may implement any of a variety of types of data transmission technologies, such as single carrier radio transmission technology (1 xRTT), evolution data optimized (EVDO) technology, general Packet Radio Service (GPRS) technology, enhanced data rates for GSM evolution (EDGE) technology, third generation partnership project (3 GPP) including 3G, fourth generation wireless (4G) networks, universal Mobile Telecommunications System (UMTS), high Speed Packet Access (HSPA), worldwide Interoperability for Microwave Access (WiMAX), long Term Evolution (LTE) standards, other data transmission defined by various standards setting organizations Technology, other long-range protocols, or other data transmission technologies.

"component" refers to a device, physical entity, or logic having boundaries defined by function or subroutine calls, branch points, APIs, or other techniques that provide partitioning or modularization of particular processing or control functions. The components may be combined with other components via their interfaces to perform machine processes. A component may be a part of a packaged-function hardware unit designed for use with other components, as well as a program that typically performs the specific functions of the relevant function. The components may constitute software components (e.g., code embodied on a machine-readable medium) or hardware components. A "hardware component" is a tangible unit capable of performing certain operations and may be configured or arranged in some physical manner. In various example embodiments, one or more computer systems (e.g., stand-alone computer systems, client computer systems, or server computer systems) or one or more hardware components of a computer system (e.g., processors or groups of processors) may be configured by software (e.g., an application or application part) as hardware components for performing certain operations described herein. The hardware components may also be implemented mechanically, electronically, or in any suitable combination thereof. For example, a hardware component may include specialized circuitry or logic permanently configured to perform certain operations. The hardware component may be a special purpose processor such as a Field Programmable Gate Array (FPGA) or an Application Specific Integrated Circuit (ASIC). The hardware components may also include programmable logic or circuitry that is temporarily configured by software to perform certain operations. For example, the hardware components may include software that is executed by a general purpose processor or other programmable processor. Once configured by such software, the hardware components become specific machines (or specific components of machines) that are uniquely tailored to perform the configured functions, rather than general-purpose processors. It will be appreciated that decisions regarding whether to implement hardware components mechanically, in dedicated and permanently configured circuitry, or in temporarily configured (e.g., via software configuration) circuitry may be driven for cost and time considerations. Accordingly, the phrase "hardware component" (or "hardware-implemented component") should be understood to include a tangible entity, i.e., an entity that is physically constructed, permanently configured (e.g., hardwired), or temporarily configured (e.g., programmed) to operate in a certain manner or to perform certain operations described herein. Considering embodiments in which hardware components are temporarily configured (e.g., programmed), there is no need to configure or instantiate each of the hardware components at any one time. For example, in the case where the hardware components include a general-purpose processor configured by software to become a special-purpose processor, the general-purpose processor may be configured as different special-purpose processors (e.g., including different hardware components) at different times, respectively. The software configures one or more particular processors accordingly to constitute particular hardware components, for example, at one time, and to constitute different hardware components at different times. A hardware component may provide information to and receive information from other hardware components. Accordingly, the hardware components described may be considered to be communicatively coupled. Where multiple hardware components are present at the same time, communication may be achieved by signal transmission between or among two or more hardware components (e.g., via appropriate circuitry and buses). In embodiments in which multiple hardware components are configured or instantiated at different times, communication between such hardware components may be achieved, for example, by storing information in a memory structure accessed by the multiple hardware components and retrieving information in the memory structure. For example, one hardware component may perform an operation and store the output of the operation in a memory device to which it is communicatively coupled. Other hardware components may then access the memory device at a later time to retrieve and process the stored output. The hardware component may also initiate communication with an input device or an output device, and may operate on a resource (e.g., a collection of information). Various operations of the example methods described herein may be performed, at least in part, by one or more processors that are temporarily configured (e.g., via software) or permanently configured to perform the relevant operations. Whether temporarily configured or permanently configured, such a processor may constitute a processor-implemented component that operates to perform one or more operations or functions described herein. As used herein, "processor-implemented components" refers to hardware components implemented using one or more processors. Similarly, the methods described herein may be implemented, at least in part, by processors, with particular one or more processors being examples of hardware. For example, at least some of the operations of the method may be performed by one or more processors 1704 or processor-implemented components. In addition, one or more processors may also operate to support execution of related operations in a "cloud computing" environment or as "software as a service" (SaaS) operations. For example, at least some of the operations may be performed by a computer group (as an example of a machine comprising a processor), where the operations are accessible via a network (e.g., the internet) and via one or more suitable interfaces (e.g., APIs). The performance of certain operations may be distributed among processors, not residing within a single machine, but rather deployed across multiple machines. In some example embodiments, the processor or processor-implemented components may be located in a single geographic location (e.g., within a home environment, an office environment, or a server farm). In other example implementations, the processor or processor-implemented components may be distributed across several geographic locations.

"computer-readable storage medium" refers to both machine storage media and transmission media. Accordingly, these terms include both storage devices/media and carrier wave/modulated data signals. The terms "machine-readable medium," "computer-readable medium," and "device-readable medium" mean the same thing and may be used interchangeably in this disclosure.

"machine storage media" refers to single or multiple storage devices and media (e.g., centralized or distributed databases, and associated caches and servers) that store the executable instructions, routines, and data. Thus, the term should be taken to include, but is not limited to, solid-state memory, as well as 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: nonvolatile memory including, for example, semiconductor memory devices such as erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), FPGA, and flash memory devices; magnetic disks, such as internal hard disks and removable disks; magneto-optical disk; CD-ROM and DVD-ROM discs. The terms "machine storage medium," "device storage medium," "computer storage medium" mean the same thing and may be used interchangeably in this disclosure. The terms "machine storage medium," computer storage medium, "and" device storage medium "expressly exclude carrier waves, modulated data signals, and other such medium, at least some of which are contained within the term" signal medium.

"non-transitory computer-readable storage medium" refers to a tangible medium capable of storing, encoding or carrying instructions for execution by a machine.

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

Claims (20)

1. A method, comprising:

in a messaging system providing a messaging client, an augmented reality component configured to detect an anchor point assigned to a segment of a human body image;

causing the augmented reality component to be loaded in a camera view user interface of the messaging client at a client device, the camera view user interface comprising an output of a digital image sensor of a camera of the client device, the loading comprising starting to detect anchor points in the camera view user interface assigned to respective segments of an image of a person;

Determining that the detected anchor point includes a whole body indication set of the anchor point; and

in response to the determination, causing a non-touch user selectable element to be displayed in the camera view user interface, the non-touch user selectable element configured to trigger an action in the messaging system in response to the non-touch user selectable element touching a trigger section of an image from the person.

2. The method of claim 1, wherein the set of generalized indicators of anchors includes at least a first anchor assigned to a hip object and a second anchor assigned to a shoulder object.

3. The method according to claim 1, comprising:

detecting a touch of the non-touch user selectable element with a trigger section of an image from the person; and

the actions are performed in the messaging system.

4. A method according to claim 3, wherein detecting a touch of the non-touch user selectable element with a trigger section of an image from the person comprises detecting the touch for a predetermined duration.

5. The method of claim 1, wherein the trigger segment of the image from the person is a hand object of the image from the person.

6. The method of claim 1, wherein the action is starting recording video with a camera of the client device.

7. The method according to claim 1, comprising: a set of whole body indications of the anchor point is defined in the messaging system.

8. The method of claim 1, wherein detecting anchor points of respective segments of the image assigned to the person in the camera view user interface comprises: a machine learning model trained using a training image set is performed, the machine learning model having an image of a person as input and producing a set of anchor points as output.

9. The method of claim 1, wherein displaying a non-touch user selectable element in the camera view user interface comprises: the method further includes tracking a position of a body segment object in the image of the person and displaying the non-touch user selectable element at a position in the camera view user interface determined based on the tracked position of the body segment object.

10. The method according to claim 1, comprising:

capturing a content item using the augmented reality component; and

the captured content item is transmitted to another client device.

11. A system, comprising:

one or more processors; and

a non-transitory computer-readable storage medium comprising instructions that, when executed by the one or more processors, cause the one or more processors to perform operations comprising:

in a messaging system providing a messaging client, an augmented reality component configured to detect an anchor point assigned to a segment of a human body image;

causing the augmented reality component to be loaded in a camera view user interface of the messaging client at a client device, the camera view user interface comprising an output of a digital image sensor of a camera of the client device, the loading comprising starting to detect anchor points in the camera view user interface assigned to respective segments of an image of a person;

determining that the detected anchor point includes a whole body indication set of the anchor point; and

in response to the determination, causing a non-touch user selectable element to be displayed in the camera view user interface, the non-touch user selectable element configured to trigger an action in the messaging system in response to the non-touch user selectable element touching a trigger section of an image from the person.

12. The system of claim 11, wherein the set of generalized indicators of anchors includes at least a first anchor assigned to a hip object and a second anchor assigned to a shoulder object.

13. The system of claim 11, wherein the operations caused by the instructions executed by the one or more processors further comprise:

detecting a touch of the non-touch user selectable element with a trigger section of an image from the person; and

the actions are performed in the messaging system.

14. The system of claim 13, wherein detecting the touch of the non-touch user selectable element with the trigger section of the image from the person comprises detecting the touch for a predetermined duration.

15. The system of claim 11, wherein the trigger segment of the image from the person is a hand object of the image from the person.

16. The system of claim 11, wherein the action is to begin recording video with a camera of the client device.

17. The system of claim 11, wherein the operations caused by the instructions executed by the one or more processors further comprise: a set of whole body indications of the anchor point is defined in the messaging system.

18. The system of claim 11, wherein detecting anchor points of respective segments of the image assigned to the person in the camera view user interface comprises: a machine learning model trained using a training image set is performed, the machine learning model having an image of a person as input and producing a set of anchor points as output.

19. The system of claim 11, wherein displaying a non-touch user selectable element in the camera view user interface comprises: tracking a position of a body segment object in the image of the person, and displaying the non-touch user selectable element at a position in the camera view user interface determined based on the tracked position of the body segment object.

20. A machine-readable non-transitory storage medium having instruction data executable by a machine to cause the machine to perform operations comprising:

in a messaging system providing a messaging client, an augmented reality component configured to detect an anchor point assigned to a segment of a human body image;

causing the augmented reality component to be loaded in a camera view user interface of the messaging client at a client device, the camera view user interface comprising an output of a digital image sensor of a camera of the client device, the loading comprising starting to detect anchor points in the camera view user interface assigned to respective segments of an image of a person;

Determining that the detected anchor point includes a whole body indication set of the anchor point; and

in response to the determination, causing a non-touch user selectable element to be displayed in the camera view user interface, the non-touch user selectable element configured to trigger an action in the messaging system in response to the non-touch user selectable element touching a trigger section of an image from the person.