Virtual object manipulation using gestures in messaging system

Abstract

The subject technology detects a first gesture and a second gesture, each gesture corresponding to an open trigger finger gesture. The subject technology detects a third gesture and a fourth gesture, each gesture corresponding to a closed trigger finger gesture. The subject technology selects a first virtual object within a first scene. The subject technology detects a first position and a first pose of a first representation of a first finger from a third gesture, and detects a second position and a second pose of a second representation of a second finger from a fourth gesture. The subject technology detects a first change in a first position and a first pose and a second change in a second position and a second pose. The subject technology modifies a set of sizes of a first virtual object to a different set of sizes.

Description

[0001] Priority claim

[0002] This patent application claims the benefit of priority to U.S. application serial number 17 / 941,435, filed on September 9, 2022, which is incorporated herein by reference in its entirety. Background Art

[0003] With the increased use of digital images, the affordability of portable computing devices, the proliferation of digital storage media with increasing capacity, and the improvement in bandwidth and accessibility of network connections, digital images have become a part of daily life for more and more people. BRIEF DESCRIPTION OF THE DRAWINGS

[0004] In the accompanying drawings (not necessarily drawn to scale), similar reference numerals may describe similar components in different views. To easily identify the discussion of any particular element or action, the highest digit or digits in the reference numeral refer to the figure number in which the element is first introduced. Some non-limiting examples are shown in the accompanying drawings, in which:

[0005] Figure 1 is a diagrammatic representation of a networking environment in which the present disclosure may be deployed, according to some examples.

[0006] Figure 2 is a diagrammatic representation of a messaging system having both client-side and server-side functionality according to some examples.

[0007] Figure 3 is a diagrammatic representation of data structures as maintained in a database according to some examples.

[0008] Figure 4 is a graphical representation of messages according to some examples.

[0009] Figure 5 A user interface generation and usage process according to some examples is shown.

[0010] Figure 6 Depicted is a sequence diagram of an example user interface process according to some examples.

[0011] Fig. 7A Example interfaces are shown in accordance with various implementations.

[0012] Figure 7B Example interfaces are shown in accordance with various implementations.

[0013] Figure 8 Example interfaces are shown in accordance with various implementations.

[0014] Fig. 9 Example interfaces are shown in accordance with various implementations.

[0015] Fig.10 Example interfaces are shown in accordance with various implementations.

[0016] Fig.11 Example interfaces are shown in accordance with various implementations.

[0017] Fig.12 Example interfaces are shown in accordance with various implementations.

[0018] Fig.13 Example interfaces are shown in accordance with various implementations.

[0019] Fig.14 Example interfaces are shown in accordance with various implementations.

[0020] Fig.15 Example interfaces are shown in accordance with various implementations.

[0021] Fig.16 Example interfaces are shown in accordance with various implementations.

[0022] Fig.17 Example interfaces are shown in accordance with various implementations.

[0023] Fig.18 Example interfaces are shown in accordance with various implementations.

[0024] Fig.19 Example interfaces are shown in accordance with various implementations.

[0025] Fig. 20 Example interfaces are shown in accordance with various implementations.

[0026] Fig.21 Example interfaces are shown in accordance with various implementations.

[0027] Fig. 22 Example interfaces are shown in accordance with various implementations.

[0028] Fig.23 Example interfaces are shown in accordance with various implementations.

[0029] Fig.24 Example interfaces are shown in accordance with various implementations.

[0030] Fig.25 Example interfaces are shown in accordance with various implementations.

[0031] Fig.26 is a flow chart illustrating a method according to certain example embodiments.

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

[0033] Fig.28 is a block diagram illustrating a software architecture in which examples may be implemented. DETAILED DESCRIPTION

[0034] Users from a variety of locations and with a range of interests can capture digital images of a variety of subjects and make the captured images available to others via a network, such as the Internet. To enhance the user's experience with digital images and provide various features, it can be challenging and computationally intensive to enable a computing device to perform image processing operations on a variety of objects and / or features captured under a wide variety of varying conditions (e.g., variations in image scale, noise, lighting, motion, or geometric distortion).

[0035] Augmented reality technology aims to bridge the gap between virtual and real world environments by providing an augmented real world environment that is enhanced by electronic information. Thus, the electronic information appears to be part of the real world environment perceived by the user. In an example, augmented reality technology also provides a user interface to interact with the electronic information superimposed on the augmented real world environment.

[0036] As mentioned above, with the increased use of digital images, the affordability of portable computing devices, the popularity of digital storage media with increasing capacity, and the improvement of network connection bandwidth and accessibility, digital images have become part of the daily lives of more and more people. Users from various locations and with a range of interests can capture digital images of various subjects and make the captured images available to others via a network (such as the Internet). In order to enhance the user's experience of digital images and provide various features, it may be challenging and computationally intensive to enable computing devices to perform image processing operations on various objects and / or features captured under a wide variety of varying conditions (e.g., changes in image scale, noise, lighting, motion, or geometric distortion).

[0037] Augmented reality technology aims to bridge the gap between virtual and real world environments by providing an augmented real world environment that is enhanced by electronic information. Thus, the electronic information appears to be part of the real world environment perceived by the user. In an example, augmented reality technology also provides a user interface to interact with the electronic information superimposed on the augmented real world environment.

[0038] Augmented reality (AR) systems enable the real environment to be combined with the virtual environment to varying degrees, thereby facilitating interaction from the user in a real-time manner. Therefore, such an AR system as described herein may include various possible combinations of real and virtual environments, including augmented reality, which primarily includes real elements and is closer to the real environment than a virtual environment (e.g., without real elements). In this way, the AR system can connect the real environment with the virtual environment. A user immersed in an AR environment can navigate in such an environment, and the AR system can track the user's viewpoint to provide visualization based on the user's position in the environment. As described in the embodiments of this article, an augmented reality (AR) experience can be provided in a messaging client application (or messaging system).

[0039] Implementations of the subject technology described herein enable various operations involving AR content for capturing and modifying such content using a given electronic device, such as a mobile computing device.

[0040] Users of mobile computing devices increasingly utilize and frequently use messaging systems in a variety of scenarios to provide different types of functionality in a convenient manner. As described herein, the messaging system includes practical applications that provide improvements in capturing images and rendering AR content (e.g., images, videos, etc.) based on captured image data by at least providing technical improvements in capturing image data using power and resource-constrained electronic devices. Such improvements in capturing image data are achieved through techniques provided by the present technology that reduce latency and improve efficiency in processing captured image data, thereby also reducing power consumption of capture devices.

[0041] As further discussed herein, the infrastructure of the present invention supports the creation and sharing of interactive media (referred to herein as messages) including 3D content or AR effects throughout the various components of the messaging system. In the example implementations described herein, messages may enter the system from a live camera device or through a storage device (e.g., where messages including 3D content and / or AR effects are stored in a memory or database). The system supports motion sensor input, as well as the loading of external effects and asset data.

[0042] As referred to herein, the phrases "augmented reality experience," "augmented reality content item," and "augmented reality content generator" include or refer to various image processing operations corresponding to image modification, filtering, AR content generator, media overlay, transformation, etc., and may also include playback of audio or music content during AR content or media content presentation (as further described herein).

[0043] Networked computing environment

[0044] Figure 1 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 client devices 102, each of which hosts several applications, including a messaging client 104 and other applications 106. Each messaging client 104 is communicatively coupled to other instances of the messaging client 104 (e.g., hosted on respective other client devices 102), a messaging server system 108, and a third-party server 110 via a network 112 (e.g., the Internet). The messaging client 104 may also communicate with the locally hosted applications 106 using an application program interface (API).

[0045] The messaging clients 104 are able to communicate and exchange data with other messaging clients 104 and messaging server systems 108 via the network 112. The data exchanged between the messaging clients 104 and between the messaging clients 104 and messaging server systems 108 include functions (e.g., commands for invoking functions) and payload data (e.g., text, audio, video, or other multimedia data).

[0046] The messaging server system 108 provides server-side functionality to certain messaging clients 104 via the network 112. 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, it may be a design choice whether certain functions are located within the messaging client 104 or within the messaging server system 108. For example, it may be technically preferable to initially deploy certain technologies and functions within the messaging server system 108, but later migrate the technologies and functions to the messaging client 104 where the client device 102 has sufficient processing power.

[0047] The messaging server system 108 supports various services and operations provided to the messaging clients 104. Such operations include sending data to the messaging clients 104, receiving data from the messaging clients 104, and processing data generated by the messaging clients 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 data exchange within the messaging system 100 is invoked and controlled by functions available via the user interface (UI) of the messaging client 104.

[0048] Turning now specifically to the messaging server system 108, an application program interface (API) server 116 is coupled to the application server 114 and provides a programming interface to the application server 114. The application server 114 is communicatively coupled to a database server 120, which facilitates access to a database 126 that stores data associated with messages processed by the application server 114. Similarly, a web server 128 is coupled to the application server 114 and provides a web-based interface to the application server 114. To this end, the web server 128 processes incoming network requests via the Hypertext Transfer Protocol (HTTP) and several other related protocols.

[0049] The application program interface (API) server 116 receives and sends message data (e.g., commands and message payloads) between the client device 102 and the application server 114. Specifically, the application program interface (API) server 116 provides a set of interfaces (e.g., routines and protocols) that can be called or queried by the messaging client 104 to invoke the functions of the application server 114. An application program interface (API) server 116 exposes various functions supported by the application server 114, including: account registration; login functionality; sending messages from a particular messaging client 104 to another messaging client 104 via the application server 114; sending media files (e.g., images or videos) from a messaging client 104 to a messaging server 118 and for possible access by another messaging client 104; setting up a collection of media data (e.g., a story); retrieving a friend list of a user of a client device 102; retrieving such a collection; retrieving messages and content; adding and removing entities (e.g., friends) from an entity graph (e.g., a social graph); locating friends in a social graph; and opening application events (e.g., related to a messaging client 104).

[0050] The application server 114 hosts several server applications and subsystems, including, for example, a messaging server 118, an image processing server 122, and a social network server 124. The messaging server 118 implements several message processing technologies 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 more 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 the messaging client 104. In view of the hardware requirements for other processor and memory intensive data processing, other processor and memory intensive data processing can also be performed on the server side by the messaging server 118.

[0051] The application server 114 also includes an image processing server 122 that is dedicated to performing various image processing operations, typically with respect to images or videos within the payload of messages sent from or received at the messaging server 118 .

[0052] The social network server 124 supports various social networking functions and services and makes them available to the messaging server 118. To this end, the social network server 124 maintains and accesses an entity graph 308 (e.g., Figure 3 ). Examples of functions and services supported by the social network server 124 include identifying other users in the messaging system 100 that have a relationship with a particular user or that the particular user is "following," and also identifying interests and other entities of a particular user.

[0053] Returning to the messaging client 104, the features and functions of the external resource (e.g., application 106 or applet) are available to the user via the interface of the messaging client 104. In this context, "external" refers to the fact that the application 106 or applet is outside the messaging client 104. External resources are usually provided by a third party, but can also be provided by the creator or provider of the messaging client 104. The messaging client 104 receives a user selection of an option to launch or access the features of such an external resource. The external resource can be an application 106 (e.g., a "local app") installed on the client device 102, or a small-scale version of the application (e.g., a "applet") hosted on the client device 102 or remotely connected to the client device 102 (e.g., on a third-party server 110). The small-scale version of the application includes a subset of the features and functions of the application (e.g., a full-scale, local version of the application) and is implemented using a markup language document. In one example, the small-scale version of the application (e.g., a "applet") 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 (eg, *ml files), applets may also include scripting languages ​​(eg, .*js files or .json files) and style sheets (eg, .*ss files).

[0054] In response to receiving a user selection of an option to launch or access a feature of an external resource, the messaging client 104 determines whether the selected external resource is a web-based external resource or a locally installed application 106. In some cases, the application 106 locally installed on the client device 102 can be independent of the messaging client 104 and launched separately from the messaging client 104, such as by selecting an icon corresponding to the application 106 on a home screen of the client device 102. A small-scale version of such an application can be launched or accessed via the messaging client 104, and in some examples, all portions of the small-scale application cannot be accessed outside the messaging client 104 or limited portions of the small-scale application can be accessed outside the messaging client 104. The small-scale application can be launched by the messaging client 104, for example, receiving a markup language document associated with the small-scale application from a third-party server 110 and processing such a document.

[0055] 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 the 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 the third-party server 110 (for example) to obtain a markup language document corresponding to the selected external resource. The messaging client 104 then processes the obtained markup language document to present the web-based external resource within the user interface of the messaging client 104.

[0056] The messaging client 104 may notify the user of the client device 102 or other users (e.g., "friends") associated with such a user of one or more external resources of activities that are occurring. For example, the messaging client 104 may provide a participant in a conversation (e.g., a chat session) in the messaging client 104 with a notification related to the current or recent use of an external resource by one or more members of a user group. One or more users may be invited to join a valid external resource or to launch an external resource that was recently used but is currently inactive (in the friend group). The external resource may provide the participants in the conversation (each using a corresponding messaging client 104) with the ability to share items, conditions, states, or locations in the external resource with one or more members of the user group entering the chat session. The shared item may be an interactive chat card that members of the chat may interact with, for example, to launch a corresponding external resource, view specific information within an external resource, or bring members of the chat to a specific location or state within an external resource. Within a given external resource, a response message may be sent to a user on the messaging client 104. The external resource may selectively include different media items in the response based on the current context of the external resource.

[0057] The messaging client 104 may present a list of available external resources (e.g., applications 106 or applets) to the user to launch or access a given external resource. The list may be presented in the form of a context-sensitive menu. For example, icons representing different applications (or applets) of the application 106 (or applets) may vary based on how the user launches the menu (e.g., from a conversational interface or from a non-conversational interface).

[0058] System Architecture

[0059] Figure 2 1 is a block diagram showing additional details about the messaging system 100 according to some examples. Specifically, the messaging system 100 is shown to include a messaging client 104 and an application server 114. The messaging system 100 contains several subsystems that are 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 transient timer system 202, a collection management system 204, an enhancement system 208, a map system 210, a game system 212, and an external resource system 214.

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

[0061] The collection management system 204 is responsible for managing collections or collections of media (e.g., collections of text, images, 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 (e.g., the duration of the event to which the content relates). For example, content related to a concert can be made available as a "story" for the duration of the concert. The collection management system 204 can also be responsible for publishing an icon to the user interface of the messaging client 104 that provides notification of the existence of a particular collection.

[0062] In addition, the collection management system 204 also includes a curation interface 206, which allows collection managers to manage and curate specific content collections. For example, the curation interface 206 enables an event organizer to curate a collection of content related to a specific event (e.g., to delete inappropriate content or redundant messages). In addition, the collection management system 204 uses machine vision (or image recognition technology) and content rules to automatically curate content collections. In some examples, compensation can be paid to users for including user-generated content in a collection. In such a case, the collection management system 204 operates to automatically pay such users for using their content.

[0063] The enhancement system 208 provides various functions that enable a user to enhance (e.g., annotate or otherwise modify or edit) media content associated with a message. For example, the enhancement system 208 provides functions related to generating and publishing media overlays for messages processed by the messaging system 100. The enhancement system 208 is operable to provide media overlays or enhancements (e.g., image filters) to the messaging client 104 based on the geographic location of the client device 102. In another example, the enhancement system 208 is operable to provide media overlays to the messaging client 104 based on other information such as social network information of the user of the client device 102. The media overlay can include audio and visual content and 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 the client device 102. For example, the media overlay can include text or images that can be superimposed on top of a photo taken by the client device 102. In another example, the media overlay includes a location identifier (e.g., Venice Beach) overlay, the name of a live event, or a business name (e.g., Beach Cafe) overlay. In another example, the enhancement system 208 uses the geographic location of the client device 102 to identify a media overlay that includes a business name at the geographic location of the client device 102. The media overlay may include other logos associated with the business. The media overlay may be stored in the database 120 and accessed by the database server 120.

[0064] In some examples, the enhancement system 208 provides a user-based publishing platform that enables a user to select a geographic location on a map and upload content associated with the selected geographic location. The user may also specify under what circumstances a particular media overlay should be provided to other users. The enhancement system 208 generates a media overlay that includes the uploaded content and associates the uploaded content with the selected geographic location.

[0065] In other examples, the enhancement system 208 provides a merchant-based publishing platform that enables merchants to select specific media overlays associated with geographic locations via a bidding process. For example, the enhancement system 208 associates the highest bidding merchant's media overlay with the corresponding geographic location for a predefined amount of time.

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

[0067] The gaming system 212 provides various gaming functions within the context of the messaging client 104. The messaging client 104 provides a gaming interface that provides a list of available games that can be launched by a user within the context of the messaging client 104 and played with other users of the messaging system 100. The messaging system 100 also enables a particular user to invite other users to participate in playing a particular game by sending an invitation to such other users from the messaging client 104. The messaging client 104 also supports both voice messaging and text messaging within the context of game play (e.g., chatting), provides leaderboards for games, and also supports providing in-game rewards (e.g., game coins and items).

[0068] The external resource system 214 provides an interface for the messaging client 104 to communicate with a remote server (e.g., a third-party server 110) to launch or access external resources (i.e., applications or applets). Each third-party server 110 hosts, for example, an application or a small-scale version of an application based on a markup language (e.g., HTML5) (e.g., a game application, a utility application, a payment application, or a ride-sharing application). The messaging client 104 can launch a web-based resource (e.g., an application) by accessing an HTML5 file from a third-party server 110 associated with a web-based resource. In some examples, the application hosted by the third-party server 110 is programmed in JavaScript using a software development kit (SDK) provided by the messaging server 118. The SDK includes an application programming interface (API) having functions that can be called or activated by a web-based application. In some examples, the messaging server 118 includes a JavaScript library that provides a given external resource access to certain user data of the 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.

[0069] To integrate the functionality of the SDK into a web-based resource, the SDK is downloaded by the third-party server 110 from the messaging server 118, or received by the third-party server 110 in other ways. Once downloaded or received, the SDK will be 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 the messaging client 104 into the web-based resource.

[0070] The SDK stored on the messaging server 118 effectively provides a bridge between external resources (e.g., applications 106 or applet) and the messaging client 104. This provides users with a seamless experience of communicating with other users on the messaging client 104 while retaining the look and feel of the messaging client 104. In order to bridge the communication between the external resources and the messaging client 104, in some examples, the SDK facilitates the communication between the third-party server 110 and the messaging client 104. In some examples, the WebViewJavaScriptBridge running on the client device 102 establishes two one-way communication channels between the external resources and the messaging client 104. Messages are sent asynchronously between the external resources and the messaging client 104 via these communication channels. Each SDK function activation is sent as a message and a callback. Each SDK function is implemented by constructing a unique callback identifier and sending a message with the callback identifier.

[0071] 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 an HTML5 file corresponding to a web-based external resource to the messaging server 118. The messaging server 118 can add a visual representation (e.g., box art or other graphics) of the web-based external resource in the messaging client 104. Once the user selects the visual representation or instructs the messaging client 104 to access a feature of a web-based external resource through the GUI of the messaging client 104, the messaging client 104 obtains the HTML5 file and instantiates the resources required to access the features of the web-based external resource.

[0072] The messaging client 104 presents a graphical user interface (e.g., a login page or title screen) for the external resource. During, before, or after presenting the login page or title screen, the messaging client 104 determines whether the launched external resource has been previously authorized to access the user data of the messaging client 104. In response to determining that the launched external resource has been previously authorized to access the user data of the messaging client 104, the messaging client 104 presents another graphical user interface of the external resource including the functions and features of the external resource. In response to determining that the launched external resource has not been previously authorized to access the user data of the messaging client 104, after displaying the login page or title screen of the external resource for a threshold period of time (e.g., 3 seconds), the messaging client 104 slides a menu for authorizing the external resource to access the user data (e.g., animating the menu to emerge from the bottom of the screen to the middle or other portion of the screen). The menu identifies the type of user data that the external resource will be authorized to use. In response to receiving the user selection of the accept option, the messaging client 104 adds the external resource to the list of authorized external resources and enables the external resource to access the user data from the messaging client 104. In some examples, the messaging client 104 authorizes the external resource to access the user data according to the OAuth 2 framework.

[0073] The messaging client 104 controls the type of user data shared with the external resource based on the type of external resource that is authorized. For example, an external resource including a full-scale application (e.g., application 106) is provided with access to a first type of user data (e.g., only a two-dimensional avatar of a user with or without different avatar characteristics). As another example, an external resource including a small-scale version of an application (e.g., a web-based version of the application) is provided access to a second type of user data (e.g., payment information, a two-dimensional avatar of a user, a three-dimensional avatar of a user, and an avatar with various avatar characteristics). Avatar characteristics include different ways to customize the look and feel of an avatar (e.g., different poses, facial features, clothing, etc.).

[0074] Data Architecture

[0075] Figure 3 is a diagram illustrating a data structure 300 that may be stored in a database 126 of a messaging server system 108 according to some examples. Although the contents of the database 126 are illustrated as including several tables, it will be appreciated that data may be stored in other types of data structures (eg, object-oriented databases).

[0076] Database 126 includes message data stored in message table 302. For any particular message, the message data includes at least message sender data, message recipient (or receiver) data, and payload. Figure 4 Additional details regarding information that may be included in a message and included within the message data stored in message table 302 are described.

[0077] The entity table 306 stores entity data and is linked (e.g., referenced) to the entity graph 308 and profile data 316. The entities for which records are maintained within the entity table 306 may include individuals, corporate entities, organizations, objects, places, events, etc. 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).

[0078] The entity graph 308 stores information about relationships and associations between entities. By way of example only, such relationships may be social, professional (e.g., working in a common company or organization), interest-based, or activity-based.

[0079] Profile data 316 stores multiple types of profile data about a particular entity. Based on the privacy settings specified by the particular entity, profile data 316 can be selectively used and presented to other users of the messaging system 100. In the case where the entity is a person, profile data 316 includes, for example, a user name, phone number, address, settings (e.g., notification and privacy settings), and an avatar representation (or a collection of such avatar representations) selected by the user. The particular user can then selectively include one or more of these avatar representations in the content of messages transmitted via the messaging system 100 and in a map interface displayed to other users by the messaging client 104. The collection of avatar representations can include a "status avatar" that presents a graphical representation of a state or activity that a user can select to communicate at a particular time.

[0080] Where the entity is a group, the profile data 316 for the group may similarly include one or more avatar representations associated with the group, in addition to the group name, members, and various settings related to the group (eg, notifications).

[0081] Database 126 also stores enhancement data, such as overlays or filters, in enhancement table 310. Enhancement data is associated with and applied to videos (whose data is stored in video table 304) and images (whose data is stored in image table 312).

[0082] In one example, a filter is an overlay displayed as an overlay on an image or video during presentation to a recipient user. Filters can be of various types, including filters selected by a user from a set of filters presented to a sending user by messaging client 104 when the sending user is composing a message. Other types of filters include geolocation filters (also referred to as geofilters), which can be presented to a sending user based on a geographic location. For example, a geolocation filter specific to a nearby or special location can be presented by messaging client 104 within a user interface based on geographic location information determined by a global positioning system (GPS) unit of client device 102.

[0083] 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 input or information collected by the client device 102 during the message creation process. Examples of data filters include the current temperature at a particular location, the current speed at which the sending user is traveling, the battery life of the client device 102, or the current time.

[0084] Other augmented data that may be stored in the image table 312 include augmented reality content items (eg, corresponding to application lenses or augmented reality experiences). Augmented reality content items may be real-time special effects and / or sounds that may be added to an image or video.

[0085] 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., videos or images). This includes real-time modifications that modify images when they are captured using a device sensor (e.g., one or more cameras) of the client device 102 and then display the modified images on the screen of the client device 102. This also includes modifications to stored content such as video clips that can be modified in a gallery. For example, in a client device 102 that can access multiple augmented reality content items, a user can use a single video clip with multiple augmented reality content items to watch how different augmented reality content items will modify the stored clips. For example, by selecting different augmented reality content items for content, multiple augmented reality content items that apply different pseudo-random movement models can be applied to the same content. Similarly, real-time video capture can be used with the modifications shown to show how the video image currently captured by the sensor of the client device 102 will modify the captured data. Such data may simply be displayed on the screen without being stored in memory, or content captured by the device sensors may be recorded and stored in memory with or without modification (or both). In some systems, a preview function may display different augmented reality content items as they would appear in different windows of a display simultaneously. This may, for example, enable viewing of multiple windows with different pseudo-random animations on a display simultaneously.

[0086] Thus, data and various systems using augmented reality content items or other such transformation systems that modify content using such data may involve detection of objects (e.g., faces, hands, bodies, cats, dogs, surfaces, objects, etc.) in video frames; tracking of such objects as they leave, enter, and move around the field of view; and modification or transformation of such objects as they are tracked. In various examples, different methods for implementing such transformations may be used. Some examples may involve: generating a three-dimensional mesh model of one or more objects; and using transformations of the model and animated textures within a video to implement the transformations. In other examples, tracking of points on an object may be used to place an image or texture (which may be two-dimensional or three-dimensional) at the tracked location. In further examples, neural network analysis of a video frame may be used to place an image, model, or texture in content (e.g., an image or video frame). Thus, augmented reality content items refer both to images, models, and textures used to create transformations in content, and to additional modeling and analysis information required to implement such transformations using object detection, tracking, and placement.

[0087] 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 video files and store them in the memory of the device, or a sensor of the device can be used to generate a video stream. In addition, any object, such as a human face and parts of a human body, an animal, or a non-living thing (e.g., a chair, a car, or other objects) can be processed using computer animation models.

[0088] In some examples, in the case where a specific modification is selected together with the content to be transformed, the element to be transformed is identified by the computing device, and then if the element to be transformed is present in the video frame, the element to be transformed is detected and tracked. The elements of the object are modified according to the request for modification, thereby transforming the frame of the video stream. The transformation of the frame of the video stream can be performed by different methods for different types of transformations. For example, for the transformation of the frame that mainly involves changing the form of the elements of the object, the feature points of each element of the object are calculated (for example, using an active shape model (ASM) or other known methods). Then, for each element of at least one element of the object, a grid based on the feature points is generated. The grid is used for the subsequent stage of tracking the elements of the object in the video stream. During the tracking process, the grid mentioned for each element is aligned with the position of each element. Then, additional points are generated on the grid. A first set of first points is generated for each element based on the request for modification, and a set of second points is generated for each element based on the set of first points and the request for modification. Then, the frame of the video stream can be transformed 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 deformed by tracking and modifying the background of the modified object.

[0089] In some examples, the transformation of some areas of the object using the elements of the object can be performed by calculating the feature points of each element of the object and generating a grid based on the calculated feature points. Points are generated on the grid, and then various areas are generated based on the points. Then, the elements of the object are tracked by aligning the area of ​​each element with the position of each element of at least one element, and the properties of the area can be modified based on the modification request, thereby transforming the frame of the video stream. Depending on the specific modification request, the properties of the mentioned area can be transformed in different ways. Such modifications may involve: changing the color of the area; removing at least some parts of the area from the frame of the video stream; including one or more new objects in the area based on the modification request; and modifying or distorting the elements of the area or object. In various examples, any combination of such modifications or other similar modifications may be used. For certain models to be animated, some feature points may be selected as control points for determining the entire state space of options for model animation.

[0090] In some examples of computer animation models that use face detection to transform image data, faces are detected on an image using a specific face detection algorithm (e.g., Viola-Jones). An active shape model (ASM) algorithm is then applied to the face region of the image to detect facial feature reference points.

[0091] Other methods and algorithms suitable for face detection can be used. For example, in some examples, landmarks are used to locate features, which represent distinguishable points that exist in most of the images considered. For example, for facial landmarks, the location of the left pupil can be used. If the initial landmarks are not recognizable (for example, if the person wears an eye patch), secondary landmarks can be used. Such landmark identification procedures can be used for any such objects. In some examples, a set of landmarks forms a shape. The coordinates of the points in the shape can be used to represent the shape as a vector. One shape is aligned with another shape using a similarity transformation (allowing translation, scaling, and rotation) that minimizes the average Euclidean distance between the shape points. The mean shape (meanshape) is the average value of the aligned training shapes.

[0092] In some examples, a landmark search begins with an average shape that aligns with the position and size of a face determined by a global face detector. Such a search then repeats the steps of suggesting tentative shapes by adjusting the positions of shape points via template matching of the image texture around each point, and then conforming the tentative shapes to a global shape model until convergence occurs. In some systems, individual template matches are unreliable, and the shape model pools the results of weak template matches to form a stronger overall classifier. The entire search is repeated at each level of the image pyramid from coarse to fine resolution.

[0093] The transformation system can capture an image or video stream on a client device (e.g., client device 102) and perform complex image manipulations locally on the client device 102 while maintaining an appropriate user experience, computational time, and power consumption. Complex image manipulations can include size and shape changes, mood transformations (e.g., changing a face from a frown to a smile), state transformations (e.g., aging a subject, reducing apparent age, changing gender), style transformations, application of graphical elements, and any other suitable image or video manipulations that can be implemented by a convolutional neural network that has been configured to execute efficiently on the client device 102.

[0094] 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 of the user (e.g., a selfie) using a client device 102 having a neural network that operates as part of a messaging client 104 operating on the client device 102. A transformation system operating within the 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 an interface described herein. The modification icon includes the following changes, which can be the basis for modifying the face of the user within the image or video stream as part of the modification operation. Once the modification icon is selected, the transformation system initiates a process of transforming the image of the user 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 the 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. That is, a user can capture an image or video stream, and once a modification icon has been selected, the modified result can be presented in real time or near real time. In addition, when the video stream is being captured, the modification can be persistent and the selected modification icon remains toggled. Machine learning neural networks can be used to implement such modifications.

[0095] The graphical user interface presenting the modifications performed by the transformation system can supply additional interactive options for the user. Such options can be based on the interface for initiating content capture and selecting a specific computer animation model (e.g., initiated from a content creator user interface). In various examples, after the modification icon is initially selected, the modification can be persistent. The user can switch to turn the modification on or off by tapping or otherwise selecting the face being modified by the transformation system, and store it for later viewing or browsing other areas of the imaging application. In the case of multiple faces modified by the transformation system, the user can globally turn on or off the modification by tapping or selecting a single face modified and displayed in the graphical user interface. In some examples, each face in a plurality of face groups can be modified individually, or such modifications can be switched individually by tapping or selecting a single face or a series of faces displayed in the graphical user interface.

[0096] The story table 314 stores data about a collection of messages and associated image, video or audio data that are compiled into a collection (e.g., a story or gallery). The creation of a particular collection can be initiated by a particular user (e.g., each user whose record is maintained in the entity table 306). A user can create a "personal story" in the form of a collection of content that has been created and sent / broadcasted by the user. To this end, the user interface of the messaging client 104 may include a user-selectable icon to enable the sending user to add specific content to his or her personal story.

[0097] A 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 content submitted by users from different locations and events. Users whose client devices have location services enabled and who are at a co-located event at a particular time may be presented with an option, for example, via a user interface of the messaging client 104, to contribute content to a particular live story. Live stories may be identified to a user by the messaging client 104 based on his or her location. The end result is a "live story" told from a community perspective.

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

[0099] As mentioned above, the video table 304 stores video data, which in one example is associated with a message whose record is saved within the message table 302. Similarly, the image table 312 stores image data associated with a message whose message data is stored in the entity table 306. The entity table 306 can associate various enhancements from the enhancement table 310 with the various images and videos stored in the image table 312 and the video table 304.

[0100] Data communication architecture

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

[0102] Message identifier 402 : a unique identifier that identifies the message 400 .

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

[0104] • Message Image Payload 406 : Image data captured by a camera component of the client device 102 or retrieved from a memory component of the client device 102 and included in the message 400 . Image data for a message 400 sent or received may be stored in the image table 312 .

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

[0106] 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 .

[0107] Message enhancement data 412 : Enhancement data (eg, filters, stickers, 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 the message 400 . The enhancement data for a sent or received message 400 may be stored in the enhancement table 310 .

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

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

[0110] Message story identifier 418: An identifier value that identifies one or more content collections (e.g., a "story" identified in story table 314) associated with a particular content item in message image payload 406 of message 400. For example, multiple images within message image payload 406 may each be associated with multiple content collections using an identifier value.

[0111] Message tags 420: Each message 400 may be tagged with a plurality of tags, each of which indicates the subject 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 may be included within the message tags 420 indicating the relevant animal. The tag values ​​may be manually generated based on user input, or may be automatically generated using, for example, image recognition.

[0112] • Message sender identifier 422: An identifier (eg, a messaging system identifier, an email address, or a device identifier) ​​that indicates the user of the client device 102 on which the message 400 was generated and from which the message 400 was sent.

[0113] • Message recipient identifier 424: An identifier (eg, a messaging system identifier, an email address, or a device identifier) ​​that indicates the user of the client device 102 to which the message 400 is addressed.

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

[0115] Figure 5A sequence diagram of an example user interface process according to some examples is depicted. During the process, a user interface engine 504 generates 510 a user interface including one or more virtual objects that constitute interactive elements of the user interface. A virtual object can be described as an entity of a 3D geometry having a 3-tuple value of X (horizontal), Y (vertical), and Z (depth). A rendering of the user interface is generated, and rendering data 512 is transmitted to a graphics engine 506 and displayed 516 to a user. The user interface engine 504 generates 514 one or more virtual object colliders for one or more virtual objects. At least one camera device 502 generates 518 real-world video frame data 520 of the real world as viewed by the user. The real-world video frame data 520 includes hand gesture video frame data of one or more hands of a user in the user interface presented by the graphics engine 506. Therefore, the real-world video frame data 520 includes hand gesture (position) video frame data and hand position (location) video frame data of the user's hand when the user performs hand movements.

[0116] As described herein, a collider (e.g., a virtual object collider) refers to a software construct that can be attached to a specific area of ​​a virtual object so that the position of the collider can be tracked and when a collision occurs between the collider and another virtual object (e.g., when the collider intersects with the other virtual object). In an example, when a second virtual object has a collider attached, a collision event can be detected based on determining that a first collider of a first object has intersected with a collider of a second virtual object. As further discussed herein, in response to detecting a collision event, the user interface engine 504 can send user interaction data including such a collision event to a specific application (e.g., application 508) so that the application can respond in a specific manner (e.g., perform a function or operation, etc.).

[0117] The user interface engine 504 utilizes the hand position video frame data and the hand pose video frame data in the real-world video frame data 520 to extract landmarks 522 of the user's hands from the real-world video frame data 520 and generate 524 landmark colliders for one or more landmarks on one or more hands of the user. The landmark colliders are used to determine user interactions between the user and the virtual object by detecting 526 collisions between the landmark colliders and corresponding virtual object colliders of the virtual object. The user interface engine 504 uses the collisions to determine user interactions 528 of the user with the virtual object. The user interface engine 504 transmits user interaction data 530 of the user interaction to the application 508 for utilization by the application 508.

[0118] In some examples, application 508 performs the functionality of user interface engine 504 by utilizing various APIs and system libraries to receive and process real-world video frame data 520 and instruct graphics engine 506 to perform specific operations.

[0119] Although the above description relates to application 508 , it will be appreciated that in some implementations, messaging client 104 , application 106 , or application 608 (discussed below) may perform the same operations as application 508 .

[0120] Figure 6 A sequence diagram of an example user interface process according to some examples is depicted. At least one camera 604 generates 602 real-world video frame data 610 of the real world as seen by a user. In an example, the at least one camera 604 may be provided by a particular client device (e.g., client device 102). The real-world video frame data 610 includes hand gesture video frame data of one or more hands of the user. Thus, the real-world video frame data 610 includes hand gesture video frame data and hand position video frame data of the user's hands when the user performs hand movements. A gesture intent recognition engine 606 utilizes the hand position video frame data and the hand gesture video frame data in the real-world video frame data 610 to generate 612 gesture data 614, the gesture data 614 including gesture classification information indicating one or more gestures made by the user. The gesture intent recognition engine 606 transmits the gesture data 614 to an application 608, which utilizes the gesture data 614 as input from a user interface.

[0121] In some examples, application 608 performs the functionality of gesture intent recognition engine 606 by utilizing various APIs and system libraries to receive and process real-world video frame data 610 from at least one camera 604 to determine gesture data 614 .

[0122] Although the above description refers to application 608 , it should be understood that in some implementations, messaging client 104 , application 106 , or application 508 may perform the same operations as application 608 .

[0123] In addition, it should be understood that the above Figure 5 The user interface engine 504 and the graphics engine 506 discussed above may process the gesture data 614 to perform the Figure 5 For example, user interface engine 504 may generate rendering data for a user interface based at least in part on gesture data 614, and graphics engine 506 may use the generated rendering data to render such a user interface for display.

[0124] Fig. 7AExample interfaces according to various implementations are shown. The example interfaces may be provided for display on a client device (eg, client device 102 ), such as through an interface of a messaging client 104 , application 106 , application 608 .

[0125] As shown, interface 702 includes real-world video frame data of the real world captured by camera 604. The real-world video frame data includes one or more hands of the user within the rendering of interface 702, and also includes hand gesture video frame data and hand position video frame data of the user's hands when the user performs hand movements.

[0126] As discussed above, the gesture intent recognition engine 606 utilizes the hand position video frame data and the hand posture video frame data in the real-world video frame data to generate gesture data, the gesture data including gesture classification information indicating one or more gestures made by the user. In an implementation, the gesture intent recognition engine 606 transmits the gesture data to an application, which utilizes the gesture data as input from a user interface.

[0127] Figure 7B Example interfaces according to various embodiments are shown. The example interfaces may be provided for display on a client device (e.g., client device 102), such as through an interface of a messaging client 104, application 106, application 508, or application 608. Figure 7B The example described above is Fig. 7A Continuation of the discussion.

[0128] exist Figure 7B In the example of , the gesture intent recognition engine 606 analyzes the real-world video frame data displayed in the interface 704 to locate the hand posture video frame data and the hand position video frame data of the user's hand when the user performs hand movements. In this example, the gesture intent recognition engine 606 uses the hand position video frame data and the hand posture video frame data in the real-world video frame data to generate gesture data including gesture classification information, the gesture classification information indicating the gesture made by the user, the gesture indicating the camera device 604 to start or stop recording gestures. Figure 7B As shown, the start or stop recording gesture 706 corresponds to a gesture in which the user has raised his hand and opened his hand to show the palm. Therefore, the start recording gesture corresponds to the first gesture of the aforementioned motion and posture, and the stop recording gesture corresponds to the second gesture of the same motion and posture.

[0129] In some examples, the user may perform a start / stop recording gesture to position the palm of the user's hand over a selectable graphical item shown in interface 704. Such a selectable graphical item may be a graphical representation of a button (e.g., a start recording button or a stop recording button), or may be textual information indicating such a button (e.g., "Start," "Stop," etc.).

[0130] In an embodiment, application 608 (or messaging client 104, application 106, application 508) starts recording when determining to start recording a gesture based on the gesture data, and stops recording when determining to stop recording a gesture based on the gesture data. In this way, a "hands-free" way to start or stop recording can be provided, where the user does not need to return to the client device and perform such actions on the screen of the client device (e.g., by touch or click gestures or inputs).

[0131] Figure 8 Example interfaces are shown according to various implementations. The example interfaces may be provided for display on a client device (eg, client device 102 ), such as through an interface of messaging client 104 , application 106 , application 508 , or application 608 .

[0132] As shown, interface 802 provides a graphical item 806, a graphical area 808, a graphical item 810, and a graphical item 812. In this example, graphical area 808 includes a set of frames corresponding to real-world video frame data, which are displayed in the form of a timeline, and the timeline shows the time sequence of such frames. Graphical item 806 corresponds to a cut point at which the real-world video frame data can be trimmed between a starting point corresponding to graphical item 810 and an end point corresponding to graphical item 812 (e.g., frames after the cut point are truncated, discarded, or deleted).

[0133] As shown, interface 804 shows that graphical item 806 from interface 802 has been moved to a later position in the frame sequence, which corresponds to graphical item 814. Application 608 can perform a trim operation to remove a second set of frames from the cut point corresponding to graphical item 814. In an embodiment, such a cut point is determined in an automatic manner by application 608 based on determining a point within the frame sequence corresponding to a frame indicating the start of a stop recording gesture, and then setting the cut point at a threshold number of frames before the frame indicating the start of the stop recording gesture. In an implementation, the threshold amount of frames can be a predetermined number of frames, such as five (5) frames, but it should be understood that the number of frames can be set to any number of frames. In an embodiment, the user can move the positioning of graphical item 814 by further adjusting or modifying the cut point using touch input or gestures on the screen of the client device displaying interface 804.

[0134] Although the above description relates to application 608 , it should be understood that in some implementations, messaging client 104 , application 106 , or application 508 may perform the same operations as application 608 .

[0135] Fig. 9 Example interfaces are shown according to various implementations. The example interfaces may be provided for display on a client device (eg, client device 102 ), such as through an interface of messaging client 104 , application 106 , application 508 , or application 608 .

[0136] Fig. 9 The example of illustrates an implementation of using a 2-D cursor to interact with other virtual objects.

[0137] As shown, the interface 902 shows real-world video frame data of the real world captured by the camera 502. The real-world video frame data includes one or more hands of the user presented by the graphics engine 506 in the rendering result of the interface 902, and also includes hand gesture video frame data and hand position video frame data when the user's hands are in motion. Based on the position and gesture 910 of the representation of the user's fingers in the real-world video frame data, the user interface engine 504 generates a virtual object 912 corresponding to the cursor for interaction with other virtual objects rendered to be displayed in the interface 902.

[0138] In this example, the user interface engine 504 enables a user to use virtual object 912 to interact with a group of other virtual objects including virtual object 914. The group of other virtual objects in this example is arranged in a grid-like configuration in which each virtual object is positioned with an equal amount of spacing between adjacent one or more virtual objects. In an implementation, the user interface engine 504 generates a virtual object collider for each virtual object. In an implementation, the user interface engine 504 restricts movement of a cursor corresponding to virtual object 912 to one control axis, such as the x-axis (e.g., the horizontal axis). Therefore, virtual object 912 can only select a specific virtual object from the group of other virtual objects in the interface 902, such as from Fig. 9 . As shown, based on detecting a collision event in which a first collider of virtual object 912 intersects a second collider of virtual object 914, virtual object 912 corresponding to the cursor has selected virtual object 914. In response to the collision event, user interface engine 504 can animate virtual object 914 in a particular manner and cause graphics engine 506 to render interface 902 accordingly. In addition, user interface engine 504 sends user interaction data (including data related to the collision event) to a specific application (e.g., application 508), and such application can perform a function or operation in response to the collision event.

[0139] As shown in another example, the rendering result of the interface 904 rendered by the graphics engine 506 shows that the position and posture 930 of the user's finger has changed relative to the interface 902. Based on the changed position and posture 910 of the representation of the user's finger in the real-world video frame data, the user interface engine 504 moves the cursor from the posture and position in the interface 902 to the posture and position corresponding to the virtual object 932 in the interface 904. In the interface 904, the cursor corresponding to the virtual object 932 overlaps with the virtual object 934, which indicates a collision, and the user interface engine 504 can animate the virtual object 934 in response to detecting the collision event. In addition, the user interface engine 504 sends the user interaction data (including data related to the collision event) to a specific application (e.g., application 508), and such an application can perform a function or operation in response to the collision event.

[0140] Although the above description relates to application 508 , it should be understood that in some implementations, messaging client 104 , application 106 , or application 608 may perform the same operations as application 508 .

[0141] Fig.10 Example interfaces according to various embodiments are shown. The example interfaces may be provided for display on a client device (e.g., client device 102), such as through an interface of a messaging client 104, application 106, application 508, or application 608. Fig.10 The example described above is Fig. 9 Continuation of the discussion.

[0142] Fig.10 The example of illustrates an implementation of using a 3-D cursor to interact with other virtual objects.

[0143] As shown, the interface 1002 shows real-world video frame data of the real world captured by the camera 502. The real-world video frame data includes one or more hands of the user within the rendering result of the interface 1002 rendered by the graphics engine 506, and also includes hand gesture video frame data and hand position video frame data when the user performs hand movements. Based on the position and gesture 1010 of the representation of the user's fingers in the real-world video frame data, the user interface engine 504 generates a virtual object 1012 corresponding to the cursor for interaction with other virtual objects rendered to be displayed in the interface 1002.

[0144] In this example, the user interface engine 504 enables a user to use virtual object 1012 to interact with a group of other virtual objects including virtual object 1014. The group of other virtual objects in this example is arranged in a grid-like configuration in which each virtual object is positioned an equal amount apart from adjacent virtual objects. In an implementation, the user interface engine 504 generates a virtual object collider for each virtual object. In an implementation, the user interface engine 504 limits the movement of a cursor corresponding to virtual object 1012 to two control axes (e.g., more than one axis), such as an x-axis (e.g., a horizontal axis) and a y-axis (e.g., a vertical axis). Thus, virtual object 1012 can select a specific virtual object from the group of other virtual objects in interface 1002, such as from Fig.10 . As shown, based on detecting a collision event in which a first collider of virtual object 1012 intersects a second collider of virtual object 1014, virtual object 1012 corresponding to the cursor has selected virtual object 1014. In response to the collision event, user interface engine 504 can animate virtual object 1014 in a specific manner and cause graphics engine 506 to render interface 1002 accordingly. In addition, user interface engine 504 sends user interaction data (including data related to the collision event) to a specific application (e.g., application 508), and such application can perform a function or operation in response to the collision event.

[0145] As another example, the rendering result of the interface 1004 by the graphics engine 506 shows that the position and posture 1030 of the user's finger has changed relative to the interface 902. Based on the changed position and posture 910 of the representation of the user's finger in the real-world video frame data, the user interface engine 504 moves the cursor from the posture and position in the interface 1002 to the posture and position corresponding to the virtual object 1032 in the interface 1004, which is located in the row below the previously selected virtual object 1014. In the interface 1004, the cursor corresponding to the virtual object 1032 overlaps with the virtual object 1034, which indicates a collision, and the user interface engine 504 can animate the virtual object 1034 in response to detecting the collision event. In addition, the user interface engine 504 sends the user interaction data (including data related to the collision event) to a specific application (e.g., application 508), and such an application can perform a function or operation in response to the collision event. For example, the function or operation can be a task related to navigation, gaming, creation, etc.

[0146] Although the above description relates to application 508 , it should be understood that in some implementations, messaging client 104 , application 106 , or application 608 may perform the same operations as application 508 .

[0147] Fig.11 Example interfaces are shown according to various implementations. The example interfaces may be provided for display on a client device (eg, client device 102 ), such as through an interface of messaging client 104 , application 106 , application 508 , or application 608 .

[0148] As shown, the interface 1102 includes real-world video frame data of the real world captured by the camera 502. The real-world video frame data includes one or more hands of the user within the rendering result of the interface 902 by the graphics engine 506, and also includes hand gesture video frame data and hand position video frame data of the user's hands when the user performs hand movements. Based on the position and posture 1110 of the representation of the user's finger (e.g., thumb) and the second position and second posture of the representation of the user's second finger (e.g., index finger) in the real-world video frame data, the user interface engine 504 detects a hand symbol similar to a gun or shooting.

[0149] The rendering result of the interface 1104 by the graphics engine 506 shows that the position and posture 1130 of the user's first finger (such as a thumb) has changed relative to the interface 1102. Based on the changing position and posture of the representation of the user's fingers in the real-world video frame data, the user interface engine 504 determines the direction in which the user's second finger (such as an index finger) is pointing, and performs a ray casting technique to determine a vector or path for animating a virtual object (such as a virtual bullet or laser, etc.) to follow from the user's second finger. As shown in this example, the graphics engine 506 renders virtual objects 1132 and virtual objects 1134 in the interface 1104, and animates these virtual objects to follow the above paths.

[0150] Fig.12 Example interfaces according to various embodiments are shown. Example interfaces may be provided for display on a client device (e.g., client device 102), such as through an interface of a messaging client 104, application 106, application 508, or application 608. Fig.12 The example described in Fig.11 Continuation of the discussion.

[0151] As shown, the interface 1202 includes real-world video frame data of the real world captured by the camera 502. The real-world video frame data includes one or more hands of the user in the rendering result of the interface 1202 by the graphics engine 506, and also includes hand gesture video frame data and hand position video frame data of the user's hands when the user performs hand movements. Based on the position and posture 1210 of the representation of the user's second finger (e.g., index finger) in the real-world video frame data, the user interface engine 504 detects that the position and posture of the user's second finger has changed relative to the interface 1102.

[0152] After this detection, the user interface engine 504 determines the direction in which the user's second finger (e.g., index finger) is pointing, and performs a ray casting technique to determine a vector or path for animating a virtual object (e.g., a virtual bullet or laser, etc.) to follow from the user's first finger. As shown in this example, the graphics engine 506 renders a virtual object 1212 in the interface 1202 and animates the virtual object to follow the above path.

[0153] The rendering result of the interface 1204 by the graphics engine 506 shows that the position and posture 1230 of the user's second finger (e.g., index finger) has changed relative to the interface 1202. Based on the changed position and posture of the representation of the user's second finger in the real-world video frame data, the user interface engine 504 determines the new direction that the user's second finger (e.g., index finger) is pointing, and performs a ray casting technique to determine a vector or path for animating a virtual object to follow from the user's second finger. As shown in this example, the graphics engine 506 renders a virtual object 1232 in the interface 1204 and animates the virtual object to follow the above path.

[0154] Fig.13 Example interfaces are shown in accordance with various implementations. The example interfaces may be provided for display on a client device (eg, client device 102 ), such as through an interface of a messaging client 104 or application 106 .

[0155] As shown, the interface 1302 includes real-world video frame data of the real world captured by the camera 502. The real-world video frame data includes one or more hands of the user in the rendering result of the interface 1302 by the graphics engine 506, and also includes hand gesture video frame data and hand position video frame data of the user's hand when the user performs hand movements. Based on the position and posture 1310 of the representation of the user's finger (such as the thumb) in the real-world video frame data and the second position and second posture of the representation of the user's second finger (such as the index finger), the user interface engine 504 generates a virtual object 1312 corresponding to the cursor for interaction with other virtual objects rendered to be displayed in the interface 1102. As further shown, the user interface engine 504 generates virtual objects 1314 and virtual objects 1316. The close-up view of the user's hand is displayed in the graphics area 1318. In an embodiment, the graphics area 1318 is hidden from the interface 1302 or not displayed in the interface 1302.

[0156] As shown, based on detecting a collision event in which a first collider of virtual object 1312 intersects a second collider of virtual object 1316, virtual object 1312 corresponding to the cursor has selected virtual object 1316. In response to the collision event, user interface engine 504 can attach virtual object 1316 to virtual object 1312 and cause graphics engine 506 to render the two virtual objects accordingly (e.g., so that they appear to be connected to each other). In this example, virtual object 1316 is a slider control that enables a specific color to be selected from a color palette represented by virtual object 1314, including changing the selected color according to the positioning of virtual object 1316 relative to the color palette. Specifically, the selected color is displayed inside virtual object 1316.

[0157] The resulting rendering of interface 1304 by graphics engine 506 shows that virtual object 1332 and the position and posture 1330 of the user's first finger (e.g., thumb) have changed relative to interface 1302. In response to the changed position and posture of the user's first finger (e.g., the thumb is now "closed" or adjacent to the second finger), user interface engine 504 sends user interaction data (including data related to the collision event) to a particular application (e.g., application 508), and such application can perform a function or operation in response to the collision event (e.g., activating a function such as color selection corresponding to the positioning of virtual object 1316 in the color palette provided by virtual object 1314). In this example, virtual object 1336 is the same object as virtual object 1316, and virtual object 1332 is the same object as virtual object 1312, and their respective positioning is different from the previous positioning in interface 1302. A zoomed-in view of the user's hand is displayed in graphics area 1338.

[0158] In response to the changed position and posture 1330 of the user's hand, the graphics engine 506 renders virtual object 1336 and virtual object 1332 in interface 1304 so that their positioning is slightly different from the previous positioning of virtual object 1316 and virtual object 1312 in interface 1302, which causes the color selected from the color palette to be different from the color displayed in virtual object 1316 in interface 1302.

[0159] although Fig.13 The above examples in discuss a user's first finger (e.g., a thumb acting as a trigger when "closed" or against a second finger) causing a selection using virtual object 1336, but in some embodiments, another finger (e.g., an index finger) can act as a "trigger" finger to cause selection or initiate some function or operation.

[0160] Fig.14Example interfaces according to various embodiments are shown. Example interfaces may be provided for display on a client device (e.g., client device 102), such as through an interface of a messaging client 104, application 106, application 508, or application 608. Fig.14 The example described in Fig.13 Continuation of the discussion.

[0161] The resulting rendering of interface 1402 by graphics engine 506 shows that the position and posture 1410 of virtual object 1412 and the user's hand have changed relative to interface 1304. In response to the changed position and posture 1410 of the user's hand and virtual object 1412, graphics engine 506 renders virtual object 1416 and virtual object 1412 in interface 1402 so that their positioning is different from the previous positioning of virtual object 1336 and virtual object 1332 in interface 1304, which causes the color selected from the color palette to be different from the color displayed in virtual object 1336 in interface 1304. A zoomed-in view of the user's hand is displayed in graphics area 1418.

[0162] In response to the changing position and posture of the user's hand, the user interface engine 504 sends user interaction data to perform color selection. In this example, virtual object 1416 is the same object as virtual object 1336, and virtual object 1412 is the same object as virtual object 1332, and their respective positioning is different from the previous positioning in interface 1304.

[0163] The resulting rendering of interface 1404 by graphics engine 506 shows that the position and posture 1430 of the user's hand has changed relative to interface 1402. In response to the changed position and posture 1430 of the user's hand, graphics engine 506 renders virtual object 1436 and virtual object 1432 in interface 1404 so that their positioning is different from the previous positioning of virtual object 1416 and virtual object 1412 in interface 1402, which causes the color selected from the color palette to be different from the color displayed in virtual object 1416 in interface 1402. A zoomed-in view of the user's hand is displayed in graphics area 1438.

[0164] In response to the changing position and posture of the user's hand, the user interface engine 504 sends user interaction data to perform color selection. In this example, virtual object 1436 is the same object as virtual object 1416, and virtual object 1432 is the same object as virtual object 1412, and their respective positioning is different from the previous positioning in interface 1402.

[0165] Fig.15Example interfaces according to various embodiments are shown. Example interfaces may be provided for display on a client device (e.g., client device 102), such as through an interface of a messaging client 104, application 106, application 508, or application 608. Fig.15 The example described in Fig.14 Continuation of the discussion.

[0166] The resulting rendering of interface 1502 by graphics engine 506 shows that the position and posture 1510 of virtual object 1512 and the user's hand have changed relative to interface 1404. In response to the changed position and posture 1510 of virtual object 1512 and the user's hand, graphics engine 506 renders virtual object 1516 and virtual object 1512 in interface 1502 so that their positioning is different from the previous positioning of virtual object 1436 and virtual object 1432 in interface 1404, which results in the color selected from the color palette being different from the color displayed in virtual object 1436 in interface 1404. A zoomed-in view of the user's hand is displayed in graphics area 1518.

[0167] In response to the changing position and posture of the user's hand, the user interface engine 504 sends user interaction data to perform color selection. In this example, virtual object 1516 is the same object as virtual object 1436, and virtual object 1512 is the same object as virtual object 1432, and their respective positioning is different from the previous positioning in interface 1404.

[0168] The graphics engine 506 renders the interface 1504 as shown by a position and posture 1530 of the user's first finger (e.g., thumb) that has changed relative to the interface 1502. In response to the changed position and posture 1430 of the user's first finger, the user interface engine 504 sends user interaction data to perform a final color selection from a color palette that is consistent with the color displayed in the virtual object 1516 in the interface 1502. A zoomed-in view of the user's hand is displayed in the graphics area 1538.

[0169] Fig.16 Example interfaces are shown according to various implementations. The example interfaces may be provided for display on a client device (eg, client device 102 ), such as through an interface of messaging client 104 , application 106 , application 508 , or application 608 .

[0170] As shown, the interface 1602 includes real-world video frame data of the real world captured by the camera 604. The real-world video frame data includes one or more hands of the user within the rendering of the interface 1602, and also includes hand gesture video frame data and hand position video frame data when the user performs hand movements. As further shown, the interface 1602 includes a virtual object 1614, which can be manipulated using various gestures. The rendering of the interface 1602 shows the position and posture 1610 of the user's first hand and the position and posture 1612 of the user's second hand.

[0171] As previously described, the gesture intent recognition engine 606 generates gesture data using the hand position video frame data and the hand posture video frame data in the real-world video frame data, and the gesture data includes gesture classification information indicating one or more gestures made by the user. In an implementation, the gesture intent recognition engine 606 transmits the gesture data to an application, which uses the gesture data as input from a user interface. Fig.16 , Fig.17 and Fig.18 Such gesture data discussed in the example of includes data of the user's two hands, enabling the gesture intent recognition engine 606 to recognize multiple gesture movements involving two hands.

[0172] exist Fig.16 In the example of , the gesture data indicates that the virtual object 1614 is to be selected for responding to and interacting with the user's hand movements. Such a virtual object will be utilized by the application to perform a set of operations based at least in part on the position and posture of the virtual object (including the size of the object).

[0173] As further shown, the interface 1604 includes the position and posture 1630 of the user's first hand and the position and posture 1632 of the user's second hand that have changed (e.g., each thumb on each hand has been closed or closer to the index finger), and the gesture intent recognition engine 606 generates updated gesture data using the hand position video frame data and the hand posture video frame data. Fig.16 In another example, the updated gesture data indicates that virtual object 1614 is expanded to a larger size, which is displayed as virtual object 1634 in the rendering result of interface 1604.

[0174] Fig.17 Example interfaces according to various embodiments are shown. Example interfaces may be provided for display on a client device (e.g., client device 102), such as through an interface of a messaging client 104, application 106, application 508, or application 608. Fig.17 The example described in Fig.16 Continuation of the discussion.

[0175] As shown, the interface 1702 includes the changed position and posture of the user's first hand 1710 and the position and posture of the user's second hand 1712, and the gesture intention recognition engine 606 uses the hand position video frame data and the hand posture video frame data to generate updated gesture data. Fig.17 In this example, the updated gesture data indicates that the Fig.16 The virtual object 1634 in the interface 1702 is rotated in a specific direction, which is displayed as a virtual object 1714 in the rendering result of the interface 1702.

[0176] As further shown, the interface 1704 includes the changed position and posture of the user's first hand 1730 and the position and posture of the user's second hand 1732, and the gesture intent recognition engine 606 uses the hand position video frame data and the hand posture video frame data to generate updated gesture data. Fig.17 In another example, the updated gesture data indicates that the virtual object 1714 is rotated in a different direction than in the interface 1702 , which is displayed as a virtual object 1734 in the rendering result of the interface 1704 .

[0177] Fig.18 Example interfaces according to various embodiments are shown. Example interfaces may be provided for display on a client device (e.g., client device 102), such as through an interface of a messaging client 104, application 106, application 508, or application 608. Fig.18 The example described in Fig.17 Continuation of the discussion.

[0178] As shown, the interface 1802 includes the changed position and posture of the user's first hand 1810 and the position and posture of the user's second hand 1812, and the gesture intention recognition engine 606 uses the hand position video frame data and the hand posture video frame data to generate updated gesture data. Fig.18 In this example, the updated gesture data indicates that the Fig.17 The overall size of virtual object 1734 in the interface 1802 is enlarged, which is displayed as virtual object 1814 in the rendering result of interface 1802.

[0179] As further shown, the interface 1804 includes the changed position and posture of the user's first hand 1830 and the position and posture of the user's second hand 1832, and the gesture intent recognition engine 606 uses the hand position video frame data and the hand posture video frame data to generate updated gesture data. Fig.18In another example, the updated gesture data indicates that the overall size of virtual object 1814 in interface 180202 is to be reduced, which is displayed as virtual object 1834 in the rendering result of interface 1804.

[0180] Fig.19 Example interfaces are shown according to various implementations. The example interfaces may be provided for display on a client device (eg, client device 102 ), such as through an interface of messaging client 104 , application 106 , application 508 , or application 608 .

[0181] As shown, the interface 1902 includes real-world video frame data of the real world captured by the camera 604. The real-world video frame data includes one or more hands of the user within the rendering of the interface 1902, and also includes hand gesture video frame data and hand position video frame data when the user performs hand movements. As further shown, the interface 1902 includes a virtual object 1912, which can be manipulated using various gestures. The rendering of the interface 1902 shows the position and gesture 1910 of the user's first hand.

[0182] As described above, the gesture intent recognition engine 606 utilizes the hand position video frame data and the hand posture video frame data in the real-world video frame data to generate gesture data, the gesture data including gesture classification information indicating one or more gestures made by the user. In an implementation, the gesture intent recognition engine 606 transmits the gesture data to an application, which utilizes the gesture data as input from a user interface.

[0183] exist Fig.19 In the example of , the gesture data indicates that, based at least in part on the user's hand movement, a portion of the virtual object 1912 is to be selected as a starting point for modifying the virtual object 912. Such a virtual object is utilized by an application to perform a set of operations based at least in part on the position and posture of the virtual object (including other features of the object).

[0184] As further shown, the interface 1904 includes the position and posture 1930 of the user's first hand that has changed, and the gesture intent recognition engine 606 utilizes the hand position video frame data and the hand posture video frame data to generate updated gesture data. Fig.19 In this other example, the updated gesture data indicates that virtual object 1912 is to be modified, which is displayed as virtual object 1932 in the virtual screen of interface 1904, where virtual object 1932 includes additional graphics data extending from the starting point of interface 1902.

[0185] Fig. 20Example interfaces according to various embodiments are shown. Example interfaces may be provided for display on a client device (e.g., client device 102), such as through an interface of a messaging client 104, application 106, application 508, or application 608. Fig. 20 The example described in Fig.19 Continuation of the discussion.

[0186] As shown, the interface 2002 includes the position and posture 2010 of the user's first hand that has changed, and the gesture intent recognition engine 606 uses the hand position video frame data and the hand posture video frame data to generate updated gesture data. Fig. 20 In this example, the updated gesture data indicates that, based at least in part on the user's hand movement, a second portion of virtual object 1932 is selected as a starting point for modifying virtual object 1932 , which is displayed as virtual object 2012 in the rendering result of interface 2002 .

[0187] As further shown, the interface 2004 includes the position and posture 2030 of the user's first hand that has changed, and the gesture intent recognition engine 606 utilizes the hand position video frame data and the hand posture video frame data to generate updated gesture data. Fig. 20 In this another example, the updated gesture data indicates that the virtual object 2012 is to be modified, which is displayed as a virtual object 2032 in the rendering result of the interface 2004 , wherein the virtual object 2032 includes second additional graphic data extending from a second starting point of the interface 2002 .

[0188] Fig.21 Example interfaces according to various embodiments are shown. Example interfaces may be provided for display on a client device (e.g., client device 102), such as through an interface of a messaging client 104, application 106, application 508, or application 608. Fig.21 The example described in Fig. 20 Continuation of the discussion.

[0189] As shown in the figure, the interface 2102 includes the position and posture 2110 of the user's second hand that has changed, and the gesture intention recognition engine 606 generates updated gesture data using the hand position video frame data and the hand posture video frame data. Fig.21 In this example, the updated gesture data indicates, based at least in part on the user's hand movement, from Fig. 20 A third part of the virtual object 2032 in is selected as the third starting point for modifying the virtual object 2032 , which is displayed as the virtual object 2112 in the rendering result of the interface 2102 .

[0190] As further shown, the interface 2104 includes the position and posture 2130 of the user's second hand that has changed, and the gesture intent recognition engine 606 uses the hand position video frame data and the hand posture video frame data to generate updated gesture data. Fig.21 In this another example, the updated gesture data indicates that the virtual object 2112 is to be modified, which is displayed as a virtual object 2132 in the rendering result of the interface 2104, wherein the virtual object 2132 includes third additional graphic data extending from a third starting point of the interface 2102.

[0191] Fig. 22 Example interfaces are shown according to various implementations. The example interfaces may be provided for display on a client device (eg, client device 102 ), such as through an interface of messaging client 104 , application 106 , application 508 , or application 608 .

[0192] As shown, the interface 2202 includes real-world video frame data of the real world captured by the camera 604. The real-world video frame data includes one or more hands of the user within the rendering of the interface 2202, and also includes hand gesture video frame data and hand position video frame data when the user performs hand movements. As further shown, the interface 2202 includes virtual objects 2214 and virtual objects 2216, and various gestures can be used to interact with and move the virtual objects 2214 and virtual objects 2216. The rendering of the interface 2202 shows the position and posture 2210 of the user's first hand and the position and posture 2212 of the user's second hand.

[0193] As previously described, the gesture intent recognition engine 606 utilizes the hand position video frame data and the hand posture video frame data in the real-world video frame data to generate gesture data, the gesture data including gesture classification information indicating one or more gestures made by the user. In an implementation, the gesture intent recognition engine 606 transmits the gesture data to an application, which utilizes the gesture data as input from a user interface. Fig. 22 , Fig.23 , Fig.24 and Fig.25 Such gesture data discussed in the example of includes data for both hands of the user, enabling the gesture intent recognition engine 606 to recognize multiple gesture movements involving both hands or gesture movements involving one hand.

[0194] exist Fig. 22 In an example of , the gesture data indicates that additional virtual objects are displayed in response to the user's hand movement. Each virtual object is applied to perform a set of operations after being selected based on the user's hand movement.

[0195] As further shown, the interface 2204 includes a position and posture 2230 of the user's first hand and a position and posture 2232 of the user's second hand that have changed (e.g., each hand has moved outward toward an edge of the interface 2204), and the gesture intent recognition engine 606 utilizes the hand position video frame data and the hand posture video frame data to generate updated gesture data. Fig. 22 In this other example, the updated gesture data causes additional virtual objects to be rendered for display, which are displayed as virtual object 2234, virtual object 2235, virtual object 2236, virtual object 2238, and virtual object 2240 in the rendering result of interface 2204.

[0196] Fig.23 Example interfaces according to various embodiments are shown. Example interfaces may be provided for display on a client device (e.g., client device 102), such as through an interface of a messaging client 104, application 106, application 508, or application 608. Fig.23 The example described in Fig. 22 Continuation of the discussion.

[0197] As shown, the interface 2302 includes a changed position and posture 2310 of the user's first hand and a changed position and posture 2312 of the user's second hand (e.g., an open gesture in which each thumb is separated from the other fingers of the same hand), and the gesture intent recognition engine 606 utilizes the hand position video frame data and the hand posture video frame data to generate updated gesture data. Fig.23 In this example, the updated gesture data indicates that the virtual object has been set to maintain or fix its current position and posture in interface 2302.

[0198] As further shown, the interface 2304 includes the changed position and posture 2330 of the user's first hand, and the gesture intention recognition engine 606 generates updated gesture data using the hand position video frame data and the hand posture video frame data. Fig.23 In this other example, the updated gesture data indicates that the virtual object 2216 is selected, causing the application to perform a corresponding set of operations.

[0199] Fig.24 Example interfaces according to various embodiments are shown. Example interfaces may be provided for display on a client device (e.g., client device 102), such as through an interface of a messaging client 104, application 106, application 508, or application 608. Fig.24 The example described in Fig.23 Continuation of the discussion.

[0200] As shown, the interface 2402 includes a changed position and posture 2410 of the user's first hand and a changed position and posture 2412 of the user's second hand (e.g., both hands from an open hand to a pinch gesture), and the gesture intent recognition engine 606 uses the hand position video frame data and the hand posture video frame data to generate updated gesture data. Fig.24 In this example, the updated gesture data indicates that the virtual object is to move in response to the user's hand movement.

[0201] As further shown, the interface 2404 includes a position and posture 2430 of the user's first hand and a position and posture 2432 of the user's second hand that have changed (e.g., the second hand has moved toward the upper edge of the interface 2404, and the first hand has moved downward toward the lower edge of the interface 2404), and the gesture intent recognition engine 606 utilizes the hand position video frame data and the hand posture video frame data to generate updated gesture data. Fig. 22 In this other example, the updated gesture data causes the virtual objects to be arranged vertically in the rendered screen of interface 2404.

[0202] Fig.25 Example interfaces according to various embodiments are shown. Example interfaces may be provided for display on a client device (e.g., client device 102), such as through an interface of a messaging client 104, application 106, application 508, or application 608. Fig.25 The example described in Fig.24 Continuation of the discussion.

[0203] As shown, the interface 2502 includes the changed position and posture 2510 of the user's first hand and the position and posture 2512 of the user's second hand, and the gesture intention recognition engine 606 uses the hand position video frame data and the hand posture video frame data to generate updated gesture data. Fig.25 In this example, the updated gesture data indicates that the virtual object is to move in response to the user's hand movement. Fig.25 In this example, the updated gesture data causes the virtual object to be arched and arranged horizontally in the rendering of interface 2502.

[0204] As further shown, the interface 2504 includes the position and posture 2530 of the user's first hand and the position and posture 2532 of the user's second hand that have changed (e.g., the second hand has moved toward the center of the interface 2504 and the first hand has moved toward the center of the interface 2504), and the gesture intent recognition engine 606 generates updated gesture data using the hand position video frame data and the hand posture video frame data. Fig.25In this other example, the updated gesture data causes other virtual objects to be removed from the rendered screen of interface 2504 , leaving only virtual object 2214 in interface 2504 .

[0205] Fig.26 2600 according to some example embodiments. The method 2600 may be embodied as computer-readable instructions for execution by one or more computer processors, so that the operations of the method 2600 may be performed in part or in whole by the messaging client 104, particularly with respect to the above-described Figure 5 and Figure 6 , or by an application (e.g., application 106) executed on a given client device (e.g., client device 102) that communicates with the messaging server system 108 and its components; accordingly, method 2600 is described below with reference thereto by way of example. However, it should be understood that at least some of the operations of method 2600 may be deployed on various other hardware configurations, and method 2600b is not intended to be limited to the messaging client 104 or any component or system described above.

[0206] In an embodiment, Fig.26 The operations described in correspond to at least the above Fig.16 , Fig.17 and Fig.18 Description.

[0207] At operation 2602, the messaging client 104 detects a first gesture and a second gesture from a set of frames, each gesture corresponding to an open trigger finger gesture.

[0208] At operation 2604, the messaging client 104 detects a third gesture and a fourth gesture from the second set of frames, each gesture corresponding to a closed trigger finger gesture.

[0209] At operation 2606, the messaging client 104 selects the first virtual object in the first scene in response to the third gesture and the fourth gesture.

[0210] At operation 2608, the messaging client 104 detects a first position and a first posture of a first representation of a first finger from the third gesture, and detects a second position and a second posture of a second representation of a second finger from the fourth gesture.

[0211] At operation 2610, the messaging client 104 detects a first change in the first position and the first posture and a second change in the second position and the second posture.

[0212] At operation 2612, the messaging client 104 modifies a set of dimensions of the first virtual object to a different set of dimensions in response to the first change and the second change.

[0213] At operation 2614, the messaging client 104 renders the first virtual object within the first scene based at least in part on the modification.

[0214] At operation 2616, the messaging client 104 provides the rendered first virtual object for display within the first scene.

[0215] In an embodiment, the messaging client 104 detects a first subsequent change in the first position and the first posture and a second subsequent change in the second position and the second posture, and rotates the first virtual object along a rotation direction about the rotation axis in response to the first subsequent change and the second subsequent change.

[0216] In an embodiment, the messaging client 104 renders the first virtual object within the first scene based at least in part on the rotation, and provides the rendered first virtual object for display within the first scene.

[0217] In an embodiment, the rotation direction determines a first subsequent change of the first position and the first posture based on a second subsequent change relative to the second position and the second posture, based on the first position and the first posture being higher than the second position and the second posture, the rotation direction is a first direction, and based on the first position and the first posture being lower than the second position and the second posture, the rotation direction is a second direction.

[0218] In an embodiment, the first direction is counterclockwise and the second direction is clockwise, or the first direction is clockwise and the second direction is counterclockwise.

[0219] In an embodiment, the open trigger finger gesture includes a specific gesture including a thumb and index finger indicating a gun or shooting gesture, and the closed trigger finger gesture includes the thumb and index finger pointing in the same direction.

[0220] In an embodiment, a first scene includes a first virtual object and a first representation of a real-world scene, wherein the first scene includes real-world video frame data and virtual object data, the virtual object data including information for rendering the first virtual object.

[0221] In an embodiment, the first change and the second change result in an increase in a first distance between a first position and a first posture of a first representation of a first finger and a second position and a second posture of a second representation of a second finger, and modifying a set of dimensions of the first virtual object includes enlarging a set of dimensions in at least one dimension.

[0222] In an embodiment, the first change and the second change result in a reduction in a first distance between a first position and a first posture of a first representation of a first finger and a second position and a second posture of a second representation of a second finger, and modifying a set of dimensions of the first virtual object includes reducing the set of dimensions in at least one dimension.

[0223] In an embodiment, the rendered first virtual object is provided for display within a messaging application executing on the client device.

[0224] Machine Architecture

[0225] Fig. 27 2700 within which instructions 2710 (e.g., software, programs, applications, applet, app, or other executable code) may be executed for causing the machine 2700 to perform any one or more of the methods discussed herein. For example, the instructions 2710 may cause the machine 2700 to perform any one or more of the methods described herein. The instructions 2710 convert a general purpose, unprogrammed machine 2700 into a specific machine 2700 that is programmed to perform the functions described and illustrated in the manner described. The machine 2700 may operate as a standalone device or may be coupled (e.g., networked) to other machines. In a network deployment, the machine 2700 may operate as a server machine or a client machine in a server-client network environment, or as a peer machine in a peer-to-peer (or distributed) network environment. The machine 2700 may include, but is not limited to, a server computer, a client computer, a personal computer (PC), a tablet computer, a laptop computer, a netbook, a set-top box (STB), a personal digital assistant (PDA), an entertainment media system, a cellular phone, a smart phone, a mobile device, a wearable device (e.g., a smart watch), a smart home device (e.g., a smart appliance), other smart devices, a web appliance, a network router, a network switch, a network bridge, or any machine capable of sequentially or otherwise executing instructions 2710 specifying actions to be taken by the machine 2700. In addition, although only a single machine 2700 is shown, the term "machine" should also be taken to include a collection of machines that individually or jointly execute instructions 2710 to perform any one or more of the methods discussed herein. For example, the machine 2700 may include any of the client device 102 or a number of server devices that form part of the messaging server system 108. In some examples, the machine 2700 may also include both a client system and a server system, wherein certain operations of a particular method or algorithm are performed on the server side, and certain operations of the particular method or algorithm are performed on the client side.

[0226] The machine 2700 may include a processor 2704, a memory 2706, and an input / output I / O component 2702, which may be configured to communicate with each other via a bus 2740. In an example, the processor 2704 (e.g., a central processing unit (CPU), a reduced instruction set computing (RISC) processor, a complex instruction set computing (CISC) processor, a graphics processing unit (GPU), a digital signal processor (DSP), an application specific integrated circuit (ASIC), a radio frequency integrated circuit (RFIC), another processor, or any suitable combination thereof) may include, for example, a processor 2708 that executes instructions 2710 and a processor 2712. The term "processor" is intended to include multi-core processors, which may include two or more independent processors (sometimes referred to as "cores") that can execute instructions simultaneously. Although Fig. 27 Multiple processors 2704 are shown, but the machine 2700 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.

[0227] The memory 2706 includes a main memory 2714, a static memory 2716, and a storage unit 2718, which are all accessible by the processor 2704 via the bus 2740. The main memory 2706, the static memory 2716, and the storage unit 2718 store instructions 2710 that implement any one or more of the methods or functions described herein. The instructions 2710 may also reside, completely or partially, within the main memory 2714, within the static memory 2716, within the machine-readable medium 2720 within the storage unit 2718, within at least one of the processors 2704 (e.g., within a cache memory of a processor), or within any suitable combination thereof during execution thereof by the machine 2700.

[0228] I / O components 2702 may include various components that receive input, provide output, generate output, send information, exchange information, capture measurements, etc. The specific I / O components 2702 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 will be less likely to include such a touch input device. It should be understood that I / O components 2702 may include Fig. 272702. In various examples, the I / O component 2702 may include a user output component 2726 and a user input component 2728. The user output component 2726 may include a visual component (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)), an acoustic component (e.g., a speaker), a tactile component (e.g., a vibration motor, a resistance mechanism), other signal generators, etc. The user input component 2728 may 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 touch pad, a trackball, a joystick, a motion sensor, or other pointing instrument), a tactile input component (e.g., a physical button, a touch screen or other tactile input component that provides the location and force of a touch or touch gesture), an audio input component (e.g., a microphone), etc.

[0229] In other examples, the I / O component 2702 may include a biometric component 2730, a motion component 2732, an environmental component 2734, or a positioning component 2736, as well as a wide range of other components. For example, the biometric component 2730 includes components for detecting expressions (e.g., hand expressions, facial expressions, voice expressions, body postures, or eye tracking), measuring biosignals (e.g., blood pressure, heart rate, body temperature, sweat, or brain waves), identifying people (e.g., voice recognition, retinal recognition, facial recognition, fingerprint recognition, or EEG-based recognition), etc. The motion component 2732 includes an acceleration sensor component (e.g., an accelerometer), a gravity sensor component, and a rotation sensor component (e.g., a gyroscope).

[0230] Environmental components 2734 include, for example, one or more cameras (with still image / photo and video capabilities), lighting sensor components (e.g., a photometer), temperature sensor components (e.g., one or more thermometers that detect ambient temperature), humidity sensor components, pressure sensor components (e.g., a barometer), acoustic sensor components (e.g., one or more microphones that detect background noise), proximity sensor components (e.g., an infrared sensor that detects nearby objects), gas sensors (e.g., a gas detection sensor for detecting concentrations 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.

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

[0232] Additionally, 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 triple, quad, or quintuple rear camera configurations on the front and back sides of the client device 102. For example, these multi-camera systems may include a wide-angle camera, an ultra-wide-angle camera, a telephoto camera, a macro camera, and a depth sensor.

[0233] The positioning component 2736 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, from which the altitude can be obtained), an orientation sensor component (e.g., a magnetometer), etc.

[0234] A variety of technologies can be used to achieve communication. The I / O component 2702 also includes a communication component 2738, which is operable to couple the machine 2700 to the network 2722 or the device 2724 via a corresponding coupling or connection. For example, the communication component 2738 may include a network interface component or another suitable device that interfaces with the network 2722. In another example, the communication component 2738 may include a wired communication component, a wireless communication component, a cellular communication component, a near field communication (NFC) component, a Bluetooth component (e.g., Bluetooth low energy), a Wi-Fi component, and other communication components that provide communication via other modalities. The device 2724 can be any peripheral device in another machine or a variety of peripheral devices (e.g., a peripheral device coupled via USB).

[0235] In addition, the communication component 2738 can detect an identifier or include a component operable to detect an identifier. For example, the communication component 2738 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 a one-dimensional barcode such as a universal product code (UPC) barcode, a multi-dimensional barcode such as a Quick Response (QR) code, an Aztec code, a data matrix, a data symbol (Dataglyph), a maximum code (MaxiCode), PDF417, UltraCode, UCC RSS-2D barcode, and other optical codes) or an acoustic detection component (e.g., a microphone for identifying an audio signal of a tag). In addition, various information can be derived via the communication component 2738, such as a location derived via Internet Protocol (IP) geolocation, a location derived via Wi-Fi signal triangulation, a location derived via detection of an NFC beacon signal that can indicate a specific location, and the like.

[0236] Various memories (e.g., main memory 2714, static memory 2716, and memory of processor 2704) and storage unit 2718 may store one or more sets of instructions and data structures (e.g., software) used by or implementing any one or more of the methods or functions described herein. When executed by processor 2704, these instructions (e.g., instructions 2710) cause various operations to implement the disclosed examples.

[0237] The instructions 2710 may be sent or received via a network interface device (e.g., a network interface component included in the communication component 2738) using a transmission medium and using any of several well-known transmission protocols (e.g., Hypertext Transfer Protocol (HTTP)) over the network 2722. Similarly, the instructions 2710 may be sent or received via a coupling (e.g., a peer-to-peer coupling) to the device 2724 using a transmission medium.

[0238] Software Architecture

[0239] Fig.282800 is a block diagram illustrating a software architecture 2804 that may be installed on any one or more of the devices described herein. The software architecture 2804 is supported by hardware such as a machine 2802 including a processor 2820, a memory 2826, and an I / O component 2838. In this example, the software architecture 2804 may be conceptualized as a stack of layers, each of which provides specific functionality. The software architecture 2804 includes layers such as an operating system 2812, a library 2810, a framework 2808, and an application 2806. In operation, the application 2806 invokes an API call 2850 through the software stack and receives a message 2852 in response to the API call 2850.

[0240] The operating system 2812 manages hardware resources and provides public services. The operating system 2812 includes, for example, a core 2814, a service 2816, and a driver 2822. The core 2814 is used as an abstraction layer between the hardware and other software layers. For example, the core 2814 provides functions such as memory management, processor management (e.g., scheduling), component management, networking, and security settings. The service 2816 can provide other public services for other software layers. The driver 2822 is responsible for controlling the underlying hardware or interfacing with the underlying hardware. For example, the driver 2822 may include a display driver, a camera driver, a Bluetooth or Bluetooth low energy driver, a flash drive, a serial communication driver (e.g., a USB driver), a WI-FI driver, an audio driver, a power management driver, etc.

[0241] The library 2810 provides a common low-level infrastructure used by the application 2806. The library 2810 may include a system library 2818 (e.g., a C standard library) that provides functions such as memory allocation functions, string manipulation functions, mathematical functions, etc. In addition, the library 2810 may include an API library 2824, such as a media library (e.g., a library for supporting the presentation and manipulation of various media formats, such as Moving Picture Experts Group-4 (MPEG4), Advanced Video Coding (H.264 or AVC), Moving Picture Experts Group Layer-3 (MP3), Advanced Audio Coding (AAC), Adaptive Multi-Rate (AMR) audio codec, Joint Photographic Experts Group (JPEG or JPG), or Portable Network Graphics (PNG)), a graphics library (e.g., an OpenGL framework for presenting in two dimensions (2D) and three dimensions (3D) in graphics content on a display), a database library (e.g., SQLite providing various relational database functions), a web library (e.g., WebKit providing web browsing functions), etc. The library 2810 may also include various other libraries 2828 to provide many other APIs to the application 2806 .

[0242] The framework 2808 provides a common high-level infrastructure used by the applications 2806. For example, the framework 2808 provides various graphical user interface (GUI) functions, high-level resource management, and high-level positioning services. The framework 2808 can provide a wide range of other APIs that can be used by the applications 2806, some of which can be specific to a particular operating system or platform.

[0243] In the example, application 2806 may include home application 2836, contact application 2830, browser application 2832, book reader application 2834, positioning application 2842, media application 2844, messaging application 2846, game application 2848 and various other applications such as third-party application 2840. Application 2806 is a program that executes the functions defined in the program. Various programming languages ​​can be used to create one or more of the applications 2806 constructed in various ways, such as object-oriented programming languages ​​(e.g., Objective-C, Java or C++) or process programming languages ​​(e.g., C or assembly language). In a specific example, third-party application 2840 (e.g., an application developed by an entity other than a supplier of a specific platform using an ANDROID or IOS software development kit (SDK)) can be a mobile operating system, such as IOS, ANDROID, WINDOWS Phone, or mobile software running on other mobile operating systems. In this example, third-party application 2840 can activate API calls 2850 provided by operating system 2812 to facilitate the functions described herein.

[0244] Glossary

[0245] "Carrier signal" refers to any intangible medium that can store, encode or carry instructions for execution by a machine and includes digital or analog communications signals or other intangible media that facilitates communication of such instructions. Instructions may be sent or received over a network using a transmission medium via a network interface device.

[0246] "Client Device" refers to any machine that interfaces with a communications network to obtain resources from one or more server systems or other client devices. A client device may be, but is not limited to, a mobile phone, a desktop computer, a laptop computer, a portable digital assistant (PDA), a smart phone, a tablet computer, an ultrabook, a netbook, a laptop computer, a multiprocessor system, a microprocessor-based or programmable consumer electronics product, a game console, a set-top box, or any other communications device that a user may use to access a network.

[0247] "Communications network" means one or more parts of a network, which may be an ad hoc network, an intranet, an extranet, a virtual private network (VPN), a local area network (LAN), a wireless LAN (WLAN), a wide area network (WAN), a wireless WAN (WWAN), a metropolitan area network (MAN), the Internet, a part of the Internet, a part of the public switched telephone network (PSTN), a plain old telephone service (POTS) network, a cellular telephone network, a wireless network, A network, other type of network, or a combination of two or more such networks. For example, the network or a portion of the 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 type of cellular or wireless coupling. In this example, the coupling may implement any of various types of data transmission technologies, such as single carrier radio transmission technology (1xRTT), evolution data optimized (EVDO) technology, general packet radio service (GPRS) technology, enhanced data rate for GSM evolution (EDGE) technology, the third generation partnership project (3GPP) including 3G, fourth generation wireless (4G) network, universal mobile telecommunications system (UMTS), high speed packet access (HSPA), world wide interoperability for microwave access (WiMAX), long term evolution (LTE) standards, other data transmission technologies defined by various standard setting organizations, other long distance protocols, or other data transmission technologies.

[0248] "Component" refers to a device, a physical entity, or logic with boundaries defined by function or subroutine calls, branch points, APIs, or other technologies that provide partitioning or modularization for specific processing or control functions. Components can be combined with other components via their interfaces to perform machine processing. Components can be packaged functional hardware units designed for use with other components and can be part of a program that generally performs specific functions in related functions. Components can constitute software components (e.g., codes implemented on machine-readable media) or hardware components. "Hardware components" are tangible units that can perform certain operations and can be configured or arranged in a certain physical manner. In various examples, one or more computer systems (e.g., independent 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., applications or application parts) to operate to perform certain operations described herein. Hardware components can also be implemented mechanically, electronically, or any suitable combination thereof. For example, a hardware component may include a dedicated circuit or logic that is permanently configured to perform certain operations. The hardware component may be a dedicated processor, such as a field programmable gate array (FPGA) or an application specific integrated circuit (ASIC). The hardware component may also include a programmable logic or circuit system that is temporarily configured to perform certain operations by software. For example, the 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 component of a machine) that is uniquely customized to perform the configured function, and is no longer a general-purpose processor. It should be understood that it can be decided whether to mechanically implement the hardware component in a dedicated and permanently configured circuit system or in a temporarily configured (e.g., configured by software) circuit system for cost and time considerations. Therefore, the phrase "hardware component" (or "hardware-implemented component") should be understood to include a tangible entity, that is, an entity that is physically constructed, permanently configured (e.g., hardwired) or temporarily configured (e.g., programmed) to operate in some way or perform certain operations described herein. Considering an example in which a hardware component is temporarily configured (e.g., programmed), it is not necessary to configure or instantiate each of the hardware components at any one time. For example, in the case where a hardware component includes a general-purpose processor that is configured by software to become a special-purpose processor, the general-purpose processor can be respectively configured as different special-purpose processors (e.g., including different hardware components) at different times. Software accordingly configures one or more specific processors to, for example, constitute a specific hardware component at one time, and to constitute different hardware components at different times. Hardware components can provide information to other hardware components and receive information from other hardware components. Accordingly, the described hardware components can be considered to be coupled in communication.In the case of multiple hardware components being present at the same time, communication can be achieved by signal transmission (e.g., by appropriate circuits and buses) between or among two or more hardware components. In examples where multiple hardware components are configured or instantiated at different times, communication between such hardware components can be achieved, for example, by storing information in a memory structure accessible to multiple hardware components and retrieving information in the memory structure. For example, a hardware component can perform an operation, and the output of the operation is stored in a memory device coupled to it in communication. Then, another hardware component can access the memory device at a subsequent time to retrieve the stored output and process it. The hardware component can also initiate communication with an input device or an output device, and can operate on resources (e.g., a collection of information). The various operations of the example methods described herein can be performed at least in part by one or more processors that are temporarily configured (e.g., by software) or permanently configured to perform related operations. Whether it is temporarily configured or permanently configured, such a processor can constitute a processor-implemented component that operates to perform one or more operations or functions described herein. As used herein, "processor-implemented components" refer to hardware components implemented using one or more processors. Similarly, the method described in this article can be implemented at least in part by a processor, wherein one or more specific processors are examples of hardware. For example, at least some of the operation of the method can be performed by one or more processors or the components implemented by the processor. In addition, one or more processors can also operate to support the execution of related operations in a "cloud computing" environment or as a "software as a service" (SaaS) operation. For example, at least some of the operations in the operation can be performed by a group of computers (as an example of a machine including a processor), wherein these operations can be accessed via a network (e.g., the Internet) and via one or more appropriate interfaces (e.g., API). The execution of some operations in the operation can be distributed between processors, can not only reside in a single machine, but also can be deployed across several machines. In some examples, a processor or a component implemented by a processor can be located in a single geographical location (e.g., in a home environment, an office environment, or a server cluster). In other examples, a processor or a component implemented by a processor can be distributed across several geographical locations.

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

[0250] "Transient messages" are messages that are accessible for a limited duration. Transient messages can be text, images, videos, etc. The access time for transient messages can be set by the sender of the message. Alternatively, the access time can be a default setting or a setting specified by the recipient. Regardless of the setting technique, the message is transient.

[0251] "Machine storage media" refers to a single or multiple storage devices and media (e.g., centralized or distributed databases, and associated caches and servers) that store executable instructions, routines, and data. Thus, the 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), FPGA, and flash memory devices; magnetic disks, such as internal hard disks and removable disks; magneto-optical disks; and CD-ROM and DVD-ROM disks. The terms "machine storage media", "device storage media", and "computer storage media" mean the same thing and may be used interchangeably in this disclosure. The terms "machine storage media", "computer storage media", and "device storage media" expressly exclude carrier waves, modulated data signals, and other such media (at least some of which are encompassed by the term "signal media").

[0252] “Non-transitory computer-readable storage medium” refers to tangible media capable of storing, encoding, or carrying instructions to be executed by a machine.

[0253] "Signal medium" refers to any intangible medium that is capable of storing, encoding or carrying instructions executed by a machine and includes digital or analog communication signals or other intangible media that facilitate the communication of software or data. The term "signal medium" should be deemed to include any form of modulated data signals, carrier waves, etc. The term "modulated data signal" refers to a signal that has one or more of its various 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

1. A method comprising: Using one or more hardware processors, detecting a first gesture and a second gesture from a set of frames, each gesture corresponding to an open trigger finger gesture; detecting, using the one or more hardware processors, a third gesture and a fourth gesture from the second set of frames, each gesture corresponding to a closed trigger finger gesture; In response to the third gesture and the fourth gesture, selecting a first virtual object in a first scene; detecting, using the one or more hardware processors, a first position and a first pose of a first representation of a first finger from the third gesture and a second position and a second pose of a second representation of a second finger from the fourth gesture; detecting, using the one or more hardware processors, a first change in the first position and the first posture and a second change in the second position and the second posture; modifying, using the one or more hardware processors, a set of dimensions of the first virtual object to a different set of dimensions in response to the first change and the second change; rendering, using the one or more hardware processors, the first virtual object within a first scene based at least in part on the modification; as well as Using the one or more hardware processors, a rendered first virtual object is provided for display within the first scene.

2. The method according to claim 1, further comprising: detecting a first subsequent change in the first position and the first posture and a second subsequent change in the second position and the second posture; as well as In response to the first subsequent change and the second subsequent change, the first virtual object is rotated around a rotation axis in a rotation direction.

3. The method according to claim 2, further comprising: rendering the first virtual object within the first scene based at least in part on the rotation; as well as The rendered first virtual object is provided for display within the first scene.

4. The method according to claim 2, wherein: The rotation direction determines a first subsequent change in the first position and the first attitude based on a second subsequent change in the second position and the second attitude, wherein, based on the first position and the first posture being higher than the second position and the second posture, the rotation direction is a first direction, and Wherein, based on the fact that the first position and the first posture are lower than the second position and the second posture, the rotation direction is the second direction.

5. The method according to claim 4, wherein: The first direction is a counterclockwise direction and the second direction is a clockwise direction, or the first direction is a clockwise direction and the second direction is a counterclockwise direction.

6. The method according to claim 1, wherein: The open trigger finger gesture includes a specific gesture including a thumb and index finger indicating a gun or shooting gesture, and the closed trigger finger gesture includes the thumb and index finger pointing in the same direction.

7. The method according to claim 1, wherein: The first scene includes the first virtual object and a first representation of a real-world scene, wherein the first scene includes real-world video frame data and virtual object data, the virtual object data including information for rendering the first virtual object.

8. The method according to claim 1, wherein: The first change and the second change result in an increase in the distance between the first position and the first posture of the first representation of the first finger and the second position and the second posture of the second representation of the second finger, and modifying the set of dimensions of the first virtual object includes expanding the set of dimensions in at least one dimension.

9. The method according to claim 1, wherein: The first change and the second change cause a distance between a first position and a first posture of a first representation of the first finger and a second position and a second posture of a second representation of the second finger to decrease, and modifying the set of dimensions of the first virtual object includes reducing the set of dimensions in at least one dimension.

10. The method according to claim 1, wherein: The rendered first virtual object is provided for display within a messaging application executing on the client device.

11. A system comprising processor; as well as a memory, the memory comprising instructions that, when executed by the processor, cause the processor to perform operations comprising: detecting a first gesture and a second gesture from a set of frames, each gesture corresponding to an open trigger finger gesture; detecting a third gesture and a fourth gesture from the second set of frames, each gesture corresponding to a closed trigger finger gesture; In response to the third gesture and the fourth gesture, selecting a first virtual object in a first scene; detecting a first position and a first posture of a first representation of a first finger from the third gesture and detecting a second position and a second posture of a second representation of a second finger from the fourth gesture; detecting a first change in the first position and the first posture and a second change in the second position and the second posture; In response to the first change and the second change, modifying a set of dimensions of the first virtual object to a different set of dimensions; rendering the first virtual object within a first scene based at least in part on the modification; and The rendered first virtual object is provided for display within the first scene.

12. The system according to claim 11, wherein: The operations also include: detecting a first subsequent change in the first position and the first posture and a second subsequent change in the second position and the second posture; and In response to the first subsequent change and the second subsequent change, the first virtual object is rotated around a rotation axis in a rotation direction.

13. The system according to claim 12, wherein: The operations also include: rendering the first virtual object within the first scene based at least in part on the rotation; and The rendered first virtual object is provided for display within the first scene.

14. The system according to claim 12, wherein: The rotation direction determines a first subsequent change in the first position and the first attitude based on a second subsequent change in the second position and the second attitude, wherein, based on the first position and the first posture being higher than the second position and the second posture, the rotation direction is a first direction, and Wherein, based on the fact that the first position and the first posture are lower than the second position and the second posture, the rotation direction is the second direction.

15. The system of claim 14, wherein: The first direction is a counterclockwise direction and the second direction is a clockwise direction, or the first direction is a clockwise direction and the second direction is a counterclockwise direction.

16. The system according to claim 11, wherein: The open trigger finger gesture includes a specific gesture including a thumb and index finger indicating a gun or shooting gesture, and the closed trigger finger gesture includes the thumb and index finger pointing in the same direction.

17. The system of claim 11, wherein: The first scene includes the first virtual object and a first representation of a real-world scene, wherein the first scene includes real-world video frame data and virtual object data, the virtual object data including information for rendering the first virtual object.

18. The system of claim 11, wherein: The first change and the second change cause an increase in the distance between a first position and a first posture of a first representation of the first finger and a second position and a second posture of a second representation of the second finger, and modifying the set of dimensions of the first virtual object includes enlarging the set of dimensions in at least one dimension.

19. The system of claim 11, wherein: The first change and the second change result in a decrease in the distance between a first position and a first posture of a first representation of the first finger and a second position and a second posture of a second representation of the second finger, and modifying the set of dimensions of the first virtual object includes reducing the set of dimensions in at least one dimension.

20. A non-transitory computer-readable medium comprising instructions that, when executed by a computing device, cause the computing device to perform operations comprising: detecting a first gesture and a second gesture from a set of frames, each gesture corresponding to an open trigger finger gesture; detecting a third gesture and a fourth gesture from the second set of frames, each gesture corresponding to a closed trigger finger gesture; In response to the third gesture and the fourth gesture, selecting a first virtual object in a first scene; detecting a first position and a first posture of a first representation of a first finger from the third gesture and detecting a second position and a second posture of a second representation of a second finger from the fourth gesture; detecting a first change in the first position and the first posture and a second change in the second position and the second posture; In response to the first change and the second change, modifying a set of dimensions of the first virtual object to a different set of dimensions; rendering the first virtual object within a first scene based at least in part on the modification; as well as The rendered first virtual object is provided for display within the first scene.

Images