CN116724286A

CN116724286A - Gesture control on eyewear devices

Info

Publication number: CN116724286A
Application number: CN202180086042.XA
Authority: CN
Inventors: 凯尔·古德里奇; 安德鲁·詹姆斯·麦克菲; 丹尼尔·莫雷诺
Original assignee: Snap Inc
Current assignee: Snap Inc
Priority date: 2020-12-22
Filing date: 2021-12-15
Publication date: 2023-09-08

Abstract

Systems and methods are provided for performing operations including: displaying one or more virtual objects on the eyewear device; detecting a hand within a field of view of the eyeglass device by an image pickup device of the eyeglass device; determining that a first finger of the hand is oriented in the same direction as the displayed one or more virtual objects; detecting movement of a second finger of the hand relative to the first finger; and in response to detecting movement of the second finger relative to the first finger, controlling display of the one or more virtual objects.

Description

Gesture control on eyewear devices

Priority claim

The present application claims the benefit of priority from U.S. provisional application Ser. No. 63/129,323 filed on 12/22 and U.S. patent application Ser. No. 17/410,787 filed on 8/24 2021, each of which is incorporated herein by reference in its entirety.

Technical Field

The present disclosure relates to eyewear devices.

Background

Some electronic device enabled eyewear devices, such as so-called smart eyewear, allow a user to interact with virtual content while the user is engaged in an activity. The user wears the eyeglass device and can view the real world environment through the eyeglass device while interacting with virtual content displayed by the eyeglass device.

Drawings

Each of the figures merely illustrates an example embodiment of the present disclosure and should not be taken to limit its scope.

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

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

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

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

Fig. 5 is a perspective view of an eyeglass apparatus according to an example embodiment.

FIG. 6 is a flowchart illustrating example operations of a gesture control system according to example embodiments.

Fig. 7-9 are illustrative screens of a gesture control system according to example embodiments.

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

Fig. 11 is a block diagram illustrating a software architecture in which an example may be implemented.

Detailed Description

The following description discusses illustrative embodiments of the present disclosure. In the following description, for purposes of explanation, numerous specific details are set forth in order to provide an understanding of various embodiments of the disclosed subject matter. It will be apparent, however, to one skilled in the art that embodiments of the disclosed subject matter may be practiced without these specific details. In general, well-known instruction instances, protocols, structures, and techniques have not been shown in detail.

Typical smart glasses platforms allow users to read their text messages in the smart glasses and interact with other types of virtual content. Such a platform is configured to display virtual content in the lenses of the smart glasses. While such systems generally work well to allow users to interact with virtual content, such devices do not provide an intuitive interface for browsing virtual content. Some systems allow a user to use a touch interface to control virtual content by touching a touch input interface. However, the size of the touch interface is constrained by the physical layout of the smart glasses, which limits the type and manner in which the user can control the touch input of the content. Because of the limited size of the touch interface, users typically encounter steep learning curves when navigating content using the touch interface. This in turn ultimately frustrates the user, which makes the user reluctant to use smart glasses to consume content.

In addition, the typical manner of presenting and browsing virtual content in the lenses of smart glasses eventually consumes significant processing and battery resources. This is because such devices use standard resource-intensive programming languages and operations to process virtual content and also use additional resources to generate such virtual content for display. Therefore, these typical smart glasses have very limited battery life, requiring the user to constantly charge the smart glasses for use, which reduces the appeal and interest in using the smart glasses.

The disclosed embodiments improve the efficiency of using an electronic device by enabling a user to browse virtual content using intuitive gestures. For example, the disclosed embodiments may detect a user's hand using an imaging device of the eyeglass device, and may detect movement of a finger on the hand. The disclosed embodiments control the display of virtual content based on the placement of the fingers relative to the virtual content and based on how the fingers move relative to each other. In particular, the disclosed embodiments display one or more virtual objects on the eyewear device and detect a hand within the eyewear device's field of view through the eyewear device's camera. The disclosed embodiments determine that a first finger of a hand is oriented in the same direction as one or more virtual objects displayed, and detect movement of a second finger of the hand relative to the first finger. The disclosed embodiments control the display of one or more virtual objects in response to detecting movement of the second finger relative to the first finger.

As an example, the disclosed embodiments detect that the index finger is oriented in the same axial/direction as the scroll bar. When the disclosed embodiments detect a thumb dragging along the length and direction of the index finger, the disclosed embodiments translate the gesture into an instruction to move the scroll bar in the same direction. This results in the virtual content advancing in the direction of the user's thumb, a way of intuitively controlling how the content is displayed and viewed.

Because the processor of the eyeglass device performs low power consumption processing to detect gestures made by the user's hand, the battery life of the electronic eyeglass device is extended. This increases the efficiency, appeal and practicality of the electronic eyewear device.

Networked computing environment

Fig. 1 is a block diagram illustrating an example messaging system 100 for exchanging data (e.g., messages and associated content) over a network. The messaging system 100 includes multiple instances of a client device 102Each instance of which hosts several applications including messaging client 104 and other external applications 109 (e.g., third party applications). Each messaging client 104 is communicatively coupled to other instances of messaging clients 104 (e.g., hosted on respective other client devices 102), messaging server systems 108, and external application servers 110 via a network 112 (e.g., the internet). The messaging client 104 may also communicate with a locally hosted third party application 109 using an Application Programming Interface (API). The messaging system 100 includes a glasses device 119, the glasses device 119 hosting the gesture control system 107, among other applications. The eyewear device 119 is connected via the network 112 (which may include via a dedicated short-range communication path, such as Bluetooth ^TM Or WiFi direct connection) is communicatively coupled to the client device 102.

The gesture control system 107 automatically advances through and browses augmented reality or virtual reality content displayed by the eyewear device 119 based on gestures detected within the field of view of the eyewear device 119. For example, a user or wearer of the eyeglass device 119 may initially be looking at a first portion of the real-world environment (e.g., a first room in a residence). Gesture control system 107 receives user input (e.g., using a voice activated or touch activated interface of client device 102 or eyeglass device 119) to launch or access virtual content comprising one or more virtual objects. In particular, the user input may include a request to access a music or video library. In response, the gesture control system 107 obtains a list of thumbnails or visual indications of media assets associated with the music or video library and presents the list of thumbnails or visual indications within the field of view of the first portion of the real-world environment.

In an example, the gesture control system 107 may communicate with an on-board camera of the eyeglass device 119 to determine or detect that a user's hand is present within a field of view of a lens of the eyeglass device 119. For example, the camera may continuously or periodically scan real world objects included in one or more images or real-time video feeds of the camera. The gesture control system 107 may determine whether the real world object corresponds to a person's hand. In response to determining that the real-world object corresponds to a person's hand, the gesture control system 107 may determine that the user's hand has been detected within the field of view of the lenses of the eyewear device 119.

The gesture control system 107 may then begin analyzing the image of the hand to determine the movement of the fingers of the hand. In particular, the gesture control system 107 may divide the hand into several parts: index finger, palm and thumb. Although the disclosed embodiments are described with respect to an index finger, any other finger (other than a thumb) may be used instead of or in addition to an index finger. The gesture control system 107 may use templates to match different parts of the hand with different parts to mark and track these individual parts within the image. The gesture control system 107 may identify one or more virtual objects currently being displayed within the lenses of the eyewear device 119. Gesture control system 107 determines an orientation of one or more virtual objects. For example, the gesture control system 107 may determine that the scrollbar and the thumbnail representing the different media asset are aligned and oriented along the x-axis (e.g., the scrollbar and the thumbnail are aligned in a horizontal direction). In some implementations, the gesture control system 107 calculates a virtual line connecting two points located on one or more virtual objects.

Then, the gesture control system 107 recognizes the index finger in the image captured by the image pickup device of the eyeglass apparatus. The gesture control system 107 determines two points on the index finger (e.g., the start and end points of the index finger). Gesture control system 107 draws a virtual line along these two points and compares the line to the orientation of one or more virtual objects. For example, gesture control system 107 determines that the orientation of the index finger or the line is within a threshold range of orientations of one or more virtual objects. In particular, the index finger may not be perfectly aligned (e.g., a virtual line connecting two points of the index finger may not be parallel to the orientation of one or more virtual objects). The gesture control system 107 may measure the angle between the line representing the orientation of the index finger and the line representing the orientation of the virtual object. The gesture control system 107 may compare the angle to a threshold (e.g., 15 degrees). Responsive to determining that the angle is less than the threshold, the gesture control system 107 may map the orientation of the index finger to one or more virtual objects. In response to mapping the orientation of the index finger to the virtual object, gesture control system 107 may trigger control of the virtual object (e.g., browse the virtual object and activate functions related to the virtual object) based on the gestures of other fingers (e.g., thumbs) with respect to the index finger.

In some implementations, the gesture control system 107 detects the current position of the thumb in response to mapping the index finger to one or more virtual objects. The gesture control system 107 maps the current position of the scroll bar to the current position of the thumb. The gesture control system 107 detects movement of the thumb along the index finger (e.g., the gesture control system 107 detects that the thumb has been dragged along the index finger). In response, gesture control system 107 moves the scroll bar or advances one or more objects in the same direction as the thumb. For example, if the gesture control system 107 determines that the thumb has moved in a left horizontal direction, the gesture control system 107 moves the scrollbar toward the left an amount corresponding to the movement of the thumb. For example, if the thumb has moved 2 centimeters to the left, the gesture control system 107 moves the scrollbar 20 pixels to the left. As the scrollbar moves 20 pixels to the left, the virtual content item (e.g., thumbnail of the media asset) controlled by the scrollbar navigates to the left. As another example, if the gesture control system 107 determines that the thumb has moved in a right horizontal direction, the gesture control system 107 moves the scroll bar to the right by an amount corresponding to the movement of the thumb. As the scroll bar moves to the right, virtual content items (e.g., thumbnails of media assets) controlled by the scroll bar navigate to the right.

In some implementations, the virtual objects are presented on the eyewear device 119 in a three-dimensional cylindrical carousel arrangement. As the virtual object scrolls based on movement of the user's thumb, the virtual object rotates around the three-dimensional cylindrical carousel to bring other virtual objects into the current field of view and focus.

Conceptually, a user's index finger represents a scroll bar or virtual content item, and a user's thumb represents a cursor associated with the scroll bar. When the thumb is determined to move in a particular direction, the corresponding cursor associated with the scrollbar moves in the same particular direction in a similar manner and magnitude.

In other embodiments, the scroll bar and the thumbnail are aligned along a vertical direction. In this case, the gesture control system 107 may determine that the index finger is oriented upward or in a vertical direction. When the gesture control system 107 determines that the thumb is moving up/down along the index finger, the scroll bar and thumbnail are browsed and advanced up/down.

In some implementations, the first set of virtual content and the second set of virtual content can be displayed together simultaneously in the lenses of the eyewear device 119. The first set of virtual content may be oriented in a horizontal direction and the second set of virtual content may be oriented in a vertical direction. The gesture control system 107 may detect an orientation of the index finger of the user relative to the orientation of the first virtual content and the second virtual content. The gesture control system 107 may measure an angle formed between the index finger and a line representing the orientation of the first virtual content and the second virtual content. The gesture control system 107 compares a first angle formed between the index finger and a first line representing the orientation of the first virtual content to a threshold value. The gesture control system 107 compares a second angle formed between the index finger and a second line representing the orientation of the second virtual content to a threshold value. The gesture control system 107 determines that the first angle is less than the threshold and the second angle is greater than the threshold. In response, gesture control system 107 maps the index finger to the first set of virtual images to control navigation of the first set of content based on movement of the thumb. After browsing the first set of content, the gesture control system 107 may determine that the orientation of the hand has changed, resulting in the first angle being greater than the threshold and the second angle being less than the threshold. In response, gesture control system 107 switches to map the index finger to the second set of virtual images to control navigation of the second set of content but not the first set of content based on movement of the thumb.

In some implementations, the gesture control system 107 identifies a current virtual object of interest on the eyewear device 119. For example, the gesture control system 107 determines or identifies virtual content (e.g., a thumbnail representing a media asset) on which the cursor is currently located. The gesture control system 107 detects contact between the thumb and index finger (e.g., the gesture control system 107 determines that the user is tapping the index finger with the user's thumb). In response, the gesture control system 107 activates a function associated with the identified virtual content. For example, the gesture control system 107 begins playing, pauses playback, or stops playing a media asset associated with and represented by the identified virtual content.

In some implementations, the gesture control system 107 allows the user to switch between sets of media assets based on movement of the thumb relative to the index finger. For example, the gesture control system 107 determines that the thumb has moved behind or in front of the index finger (e.g., the thumb has moved in a direction perpendicular to the orientation of the index finger). Specifically, the gesture control system 107 draws a virtual line representing the thumb movement direction. The gesture control system 107 calculates the angle formed between the virtual line representing thumb movement and the virtual line representing index finger orientation. In response to determining that the difference between the angle and 90 degrees is less than a threshold (e.g., less than 10 degrees), the gesture control system 107 determines that the thumb has moved in a vertical direction relative to the index finger.

The gesture control system 107 may measure a travel distance representing the amount of movement of the thumb in the vertical direction. If the distance exceeds the first value and is less than the second value, the gesture control system 107 replaces the current display of the first plurality of virtual objects associated with the first set (e.g., a first set of thumbnails representing media assets in the first set) with a second plurality of virtual objects (e.g., a second set of thumbnails representing media assets in the second set). If the distance exceeds the second value, the gesture control system 107 replaces the current display of the first plurality of virtual objects associated with the first set (e.g., the first set of thumbnails representing the media assets in the first set) with a third plurality of virtual objects (e.g., a third set of thumbnails representing the media assets in the third set). As the thumb moves a given amount in the vertical direction, the gesture control system 107 may continuously switch the presentation of different sets of virtual objects. The gesture control system 107 may then determine that the thumb at the current location is moving along the orientation and direction of the index finger. In response, the gesture control system 107 advances through the virtual object as part of the collection currently being displayed.

The messaging client 104 is capable of communicating and exchanging data with other messaging clients 104, glasses device 119, and messaging server system 108 via network 112. The data exchanged between the messaging clients 104 and the messaging server system 108 includes functions (e.g., commands to activate the functions) as well as payload data (e.g., text, audio, video, or other multimedia data).

The messaging server system 108 provides server-side functionality to particular 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, the positioning of certain functions within the messaging client 104 or the messaging server system 108 may be a design choice. For example, it may be technically preferable that: certain techniques and functions are initially deployed within messaging server system 108, but later migrated to messaging client 104 if client device 102 has sufficient processing power.

The messaging server system 108 supports various services and operations provided to the messaging client 104. Such operations include sending data to the messaging client 104, receiving data from the messaging client 104, and processing data generated by the messaging client 104. The data may include message content, client device information, geolocation information, media enhancements and overlays, message content persistence conditions, social network information, and live event information as examples. The exchange of data within the messaging system 100 is motivated and controlled by functionality available via a User Interface (UI) of the messaging client 104.

Turning now specifically to messaging server system 108, an Application Program Interface (API) server 116 is coupled to application server 114 and provides a programming interface to application server 114. The application server 114 is communicatively coupled to a database server 120, the database server 120 facilitating access to a database 126, the database 126 storing data associated with messages processed by the application server 114. Similarly, web server 128 is coupled to application server 114 and provides a web-based interface to application server 114. To this end, web server 128 processes incoming network requests via the hypertext transfer protocol (HTTP) and several other related protocols.

An Application Program Interface (API) server 116 receives and transmits message data (e.g., command and message payloads) between the client device 102 and the application server 114. In particular, an Application Program Interface (API) server 116 provides a set of interfaces (e.g., routines and protocols) that the messaging client 104 can call or query to invoke the functionality of the application server 114. An Application Program Interface (API) server 116 exposes various functions supported by the application server 114, including: registering an account; a login function; sending a message from a particular messaging client 104 to another messaging client 104 via the application server 114; sending a media file (e.g., an image or video) from the messaging client 104 to the messaging server 118; and to enable access by another messaging client 104, set up a collection of media data (e.g., stories), retrieve a friends list of the user of the client device 102, retrieve such collection, retrieve messages and content, add and delete entities (e.g., friends) from an entity graph (e.g., social graph), locate friends in the social graph, and open application events (e.g., related to the messaging client 104).

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 networking server 124. The messaging server 118 implements several message processing techniques and functions that are particularly directed to the aggregation and other processing of content (e.g., text and multimedia content) included in messages received from multiple instances of the messaging client 104. As will be described in further detail, text and media content from multiple sources may be aggregated into a collection of content (e.g., referred to as a story or gallery). These sets are then made available to the messaging client 104. Such processing may also be performed by the messaging server 118 on the server side, taking into account the hardware requirements of other processors and memory intensive processing of the data.

The application server 114 also includes an image processing server 122, which image processing server 122 is dedicated to performing various image processing operations, typically with respect to images or video within the payload of a message sent from the messaging server 118 or received at the messaging server 118.

The image processing server 122 is used to implement the scanning functionality of the enhancement system 208. The scanning functionality includes activating and providing one or more augmented reality experiences on the client device 102 when images are captured by the client device 102. In particular, the messaging application 104 on the client device 102 may be used to activate the camera. The camera device displays one or more real-time images or videos and one or more icons or identifiers of one or more augmented reality experiences to the user. The user may select a given one of the identifiers to initiate a corresponding augmented reality experience. Initiating the augmented reality experience includes obtaining one or more augmented reality items associated with the augmented reality experience and overlaying the augmented reality items on top of an image or video being presented.

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

Returning to the messaging client 104, features and functions of external resources (e.g., third party applications 109 or applets)) are available to the user via the interface of the messaging client 104. The messaging client 104 receives a user selection of an option to launch or access a feature of an external resource (e.g., a third party resource) (e.g., the external app 109). The external resource may be a third party application (external app 109) (e.g., a "local app") installed on the client device 102, or a small-scale version (e.g., an "applet") of a third party application hosted on the client device 102 or remote from the client device 102 (e.g., on the third party server 110). The small-scale version of the third-party application includes a subset of the features and functions of the third-party application (e.g., a full-scale local version of the third-party independent application) and is implemented using a markup language document. In one example, the small-scale version of the third-party application (e.g., the "applet") is a web-based markup language version of the third-party application and is embedded in the messaging client 104. In addition to using markup language documents (e.g., a..ml file), applets may also incorporate scripting languages (e.g., a..js file or a. Json file) and style sheets (e.g., a..ss file).

In response to receiving a user selection of an option to launch or access a feature of an external resource (external app 109), messaging client 104 determines whether the selected external resource is a web-based external resource or a locally installed external application. In some cases, the external application 109 locally installed on the client device 102 may be launched independently of the messaging client 104 and separately from the messaging client 104, for example, by selecting an icon corresponding to the external application 109 on a home screen of the client device 102. A small-scale version of such an external application may be launched or accessed via messaging client 104, and in some examples, no portion or a limited portion of the small-scale external application may be accessed from outside of messaging client 104. The small-scale external application may be launched by the messaging client 104 receiving markup language documents associated with the small-scale external application from the external application server 110 and processing such documents.

In response to determining that the external resource is a locally installed external application 109, the messaging client 104 instructs the client device 102 to launch the external application 109 by executing locally stored code corresponding to the external application 109. In response to determining that the external resource is a web-based resource, the messaging client 104 communicates with the external application server 110 to obtain a markup language document corresponding to the selected resource. The messaging client 104 then processes the obtained markup language document to render the web-based external resource within the user interface of the messaging client 104.

The messaging client 104 may notify the user of the client device 102 or other users (e.g., "friends") related to such users of the activity occurring in one or more external resources. For example, the messaging client 104 may provide notifications to participants of a conversation (e.g., chat session) in the messaging client 104 regarding the current or recent use of external resources by one or more members of the user group. One or more users may be invited to join an active external resource or to initiate an external resource that has been recently used but is currently inactive (in the friend group). The external resources may provide the participants in the conversation (each participant using a respective messaging client 104) with the ability to share items, conditions, states, or locations in the external resources with one or more members of the group of users entering into the chat session. The shared item may be an interactive chat card with which members of the chat may interact, for example, to initiate a corresponding external resource, to view specific information within the external resource, or to bring members of the chat to a specific location or state within the external resource. Within a given external resource, a response message may be sent to the 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.

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

System architecture

Fig. 2 is a block diagram illustrating further details regarding the messaging system 100 according to some examples. In particular, the messaging system 100 is shown to include a messaging client 104 and an application server 114. The messaging system 100 includes several subsystems that are supported on the client side by the messaging client 104 and on the server side by the application server 114. These subsystems include, for example, a transient timer system 202, a collection management system 204, an augmentation system 208, a map system 210, a game system 212, and an external resource system 220.

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

The collection management system 204 is responsible for managing groups and collections of media (e.g., collections of text, image video, and audio data). The collection of content (e.g., messages including images, video, text, and audio) may be organized into an "event gallery" or "event story. Such a collection may be made available for a specified period of time, for example, for the duration of a content-related event. For example, content related to a concert may be made available as a "story" for the duration of the concert. The collection management system 204 may also be responsible for publishing icons that provide notifications to the user interface of the messaging client 104 that a particular collection exists.

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

Enhancement system 208 provides various functionality that enables 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 functionality related to generating and publishing media overlays for messages processed by the messaging system 100. The enhancement system 208 is operable to supply media overlays or enhancements (e.g., image filters) to the messaging client 104 based on the geolocation of the client device 102. In another example, the enhancement system 208 is operable to provision the media overlay 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 may 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 may be applied to media content items (e.g., photos) at the client device 102. For example, the media overlay may include text, graphical elements, or images that may be overlaid on top of photographs taken by the client device 102. In another example, the media overlay includes a location identification overlay (e.g., a Venetian beach), a live event name, or a merchant name overlay (e.g., a beach cafe). In another example, the enhancement system 208 uses the geolocation of the client device 102 to identify media overlays that include the name of the merchant at the geolocation of the client device 102. The media overlay may include other indicia associated with the merchant. The media overlay may be stored in database 126 and accessed through database server 120.

In some examples, the enhancement system 208 provides a user-based distribution 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 an environment in which the particular media overlay should be provided to other users. Enhancement system 208 generates a media overlay that includes the uploaded content and associates the uploaded content with the selected geographic location.

In other examples, the enhancement system 208 provides a merchant-based distribution platform that enables merchants to select particular media overlays associated with geographic locations via a bidding process. For example, the enhancement system 208 associates the media coverage of the highest bidding merchant with the corresponding geographic location for a predefined amount of time. The augmentation system 208 communicates with the image processing server 122 to obtain an augmented reality experience and presents an identifier of such experience in one or more user interfaces (e.g., as an icon on a real-time image or video, or as a thumbnail or icon in an interface dedicated to the identifier of the presented augmented reality experience). Once the augmented reality experience is selected, one or more images, videos, or augmented reality graphical elements are retrieved and presented as an overlay over the images or videos captured by the client device 102. In some cases, the camera is switched to a front view (e.g., the front-facing camera of the client device 102 is activated in response to activation of a particular augmented reality experience) and images from the front-facing camera of the client device 102 instead of the rear-facing camera of the client device 102 begin to be displayed on the client device 102. One or more images, videos, or augmented reality graphical elements are retrieved and presented as an overlay over the image captured and displayed by the front-facing camera of the client device 102.

The map system 210 provides various geolocation functions and supports the presentation of map-based media content and messages by the messaging client 104. For example, the map system 210 enables display of user icons or avatars (e.g., stored in the profile data 316) on a map to indicate the current or past positioning of a user's "friends" in the context of the map, as well as media content (e.g., a collection of messages including photographs and videos) generated by such friends. For example, a message posted by a user to the messaging system 100 from a particular geographic location may be displayed on the map interface of the messaging client 104 to a "friend" of the particular user at the particular location in the context of the map. The user may also share his or her location and status information with other users of the messaging system 100 (e.g., using an appropriate status avatar) via the messaging client 104, where the location and status information is similarly displayed to the selected user in the context of the messaging client 104's map interface.

The gaming system 212 provides various gaming functions in the context of the messaging client 104. The messaging client 104 provides a game interface that provides a list of available games (e.g., web-based games or web-based applications) that can be launched by a user in 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 issuing an invitation from the messaging client 104 to such other users. The messaging client 104 also supports both voice messaging and text messaging (e.g., chat) in the context of game play, provides a leaderboard for games, and also supports in-game rewards (e.g., money and items).

The external resource system 220 provides an interface for the messaging client 104 to communicate with the external application server 110 to initiate or access external resources. Each external resource (app) server 110 hosts, for example, a markup language (e.g., HTML 5) based application or a small-scale version of an external application (e.g., a game, utility, payment, or ride share application external to the messaging client 104). The messaging client 104 may launch a web-based resource (e.g., an application) by accessing an HTML5 file from an external resource (app) server 110 associated with the web-based resource. In some examples, the application hosted by the external resource 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) with functionality that can be invoked or activated by web-based applications. In some examples, the messaging server 118 includes a JavaScript library that provides given third party resource access rights to certain user data of the messaging client 104. HTML5 is used as an example technique for programming games, but applications and resources programmed based on other techniques may be used.

To integrate the functionality of the SDK into the web-based resource, the SDK is downloaded from the messaging server 118 by the external resource (app) server 110 or otherwise received by the external resource (app) server 110. Once downloaded or received, the SDK is included as part of the application code of the web-based external resource. The code of the web-based resource may then call or activate certain functions of the SDK to integrate features of the messaging client 104 into the web-based resource.

The SDK stored on the messaging server 118 effectively provides bridging between external resources (e.g., third parties or external applications 109 or applets and the messaging client 104). This provides a seamless experience for a user to communicate with other users on the messaging client 104 while also preserving the look and feel of the messaging client 104. To bridge communications between the external resource and the messaging client 104, in some examples, the SDK facilitates communications between the external resource server 110 and the messaging client 104. In some examples, webviewjavascript bridge running on the client device 102 establishes two unidirectional communication channels between the external resource and the messaging client 104. Messages are sent asynchronously between the external resources and the messaging client 104 via these communication channels. And sending each SDK function call 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.

By using the SDK, not all information from the messaging client 104 is shared with the external resource server 110. The SDK limits which information to share based on the needs of external resources. In some examples, each external resource server 110 provides an HTML5 file corresponding to the web-based external resource to messaging server 118. The messaging server 118 may 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 a visual representation or feature that instructs the messaging client 104 to access the web-based external resource through the GUI of the messaging client 104, the messaging client 104 obtains the HTML5 file and instantiates the resources needed to access the features of the web-based external resource.

The messaging client 104 presents a graphical user interface (e.g., a landing page or a banner screen) for the external resource. During, before, or after presentation of the landing page or the banner screen, the messaging client 104 determines whether the initiated external resource has been previously authorized to access the user data of the messaging client 104. In response to determining that the initiated 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 that includes functionality and features of the external resource. In response to determining that the initiated external resource was not previously authorized to access the user data of messaging client 104, messaging client 104 slides up a menu (e.g., animations the menu as appearing from the bottom of the screen to the middle or other portion of the screen) for authorizing the external resource to access the user data after a threshold period of time (e.g., 3 seconds) of displaying a login page or title screen of the external resource. The menu identifies the type of user data that the external resource is to be authorized to use. In response to receiving a user selection of the accepted option, the messaging client 104 adds the external resource to the list of authorized external resources and allows the external resource to access the user data from the messaging client 104. In some examples, the external resource is authorized by the messaging client 104 to access the user data in accordance with the OAuth 2 framework.

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 comprising a full-scale external application (e.g., third party or external application 109) is provided with access to a first type of user data (e.g., a two-dimensional-only avatar of a user with or without different body characteristics). As another example, an external resource including a small-scale version of an external application (e.g., a web-based version of a third-party application) is provided with access rights to a second type of user data (e.g., payment information, a two-dimensional avatar of the user, a three-dimensional avatar of the user, and avatars having various avatar characteristics). Avatar characteristics include different ways of customizing the look and feel of the avatar, such as different poses, facial features, clothing, etc.

Data architecture

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

Database 126 includes message data stored within message table 302. For any particular one of the messages, the message data includes at least message sender data, message recipient (or recipient) data, and a payload. Additional details regarding information that may be included in a message and in message data stored in message table 302 are described below with reference to fig. 4.

The entity table 306 stores entity data and is linked (e.g., referenced to ground) 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, sites, events, and the like. Whatever 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 and an entity type identifier (not shown).

The entity diagram 308 stores information about relationships and associations between entities. Such relationships may be social, professional (e.g., working at a common company or organization), interest-based, or activity-based, for example only.

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

Where the entity is a community, the profile data 316 of the community may similarly include one or more avatar representations associated with the community in addition to various settings (e.g., notifications) of the community name, members, and related communities.

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

In one example, the filter is an overlay that is displayed as overlaid on the image or video during presentation to the receiving user. The filters may be of various types, including filters that are user-selected from a set of filters presented to the sending user by the messaging client 104 when the sending user is composing a message. Other types of filters include geolocation filters (also referred to as geo-filters), which may be presented to a sending user based on geolocation. For example, a nearby or special location-specific geolocation filter may be presented by the messaging client 104 within the user interface based on geolocation information determined by the Global Positioning System (GPS) unit of the client device 102.

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

Other augmented data that may be stored within the image table 312 includes augmented reality content items (e.g., corresponding to an application augmented reality experience). The augmented reality content item or augmented reality item may be real-time special effects and sounds that may be added to an image or video.

As described above, the augmentation data includes augmented reality content items, overlays, image transforms, AR images, and the like that refer to modifications that may be applied to image data (e.g., video or images). This includes real-time modifications that are made to the image as it is captured using the device sensors (e.g., one or more cameras) of the client device 102 and then displayed on the screen of the client device 102 in the case of modifications. This also includes modifications to the stored content (e.g., video clips in a gallery that may be modified). For example, in a client device 102 having access to multiple augmented reality content items, a user may use a single video clip having multiple augmented reality content items to see how different augmented reality content items will modify stored clips. For example, multiple augmented reality content items that apply different pseudo-random motion models may be applied to the same content by selecting different augmented reality content items for the same content. Similarly, real-time video capture may be used with the illustrated modifications to illustrate 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 sensor may be recorded and stored in memory with or without modification (or both). In some systems, the preview feature may show how different augmented reality content items will appear within different windows in the display at the same time. For example, this may enable multiple windows with different pseudo-random animations to be viewed simultaneously on a display.

Thus, the data of the augmented reality content item and various systems or other such transformation systems that use the data to modify the content may involve the detection of objects (e.g., faces, hands, bodies, cats, dogs, surfaces, objects, etc.), the tracking of such objects as they leave, enter, and move around the field of view in the video frame, and the 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 implementing the transformation within the video using a transformation of the model and an animated texture. 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 still further examples, neural network analysis of video frames may be used to place images, models, or textures in content (e.g., images or frames of video). Thus, augmented reality content items refer to both images, models, and textures used to create transformations in content, as well as additional modeling and analysis information required to implement such transformations using object detection, tracking, and placement.

Real-time video processing may be performed using any kind of video data (e.g., video streams, video files, etc.) stored in the memory of any kind of computerized system. For example, a user may load a video file and save it in the memory of the device, or may generate a video stream using a sensor of the device. In addition, computer animation models may be used to process any object, such as parts of the human face and body, animals, or inanimate (e.g., chairs, automobiles, or other objects).

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

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

In some examples of computer-animated models that use face detection to transform image data, a particular face detection algorithm (e.g., viola-Jones) is used to detect faces on the image. An Active Shape Model (ASM) algorithm is then applied to the facial regions of the image to detect facial feature reference points.

Other methods and algorithms suitable for face detection may be used. For example, in some examples, landmarks are used to locate features, which represent distinguishable points present in most of the images considered. For example, for facial landmarks, the localization of the left eye pupil may be used. If the initial landmarks are not identifiable (e.g., if a person has eye shields), then secondary landmarks may be used. Such a landmark identification procedure may be used for any such object. In some examples, a set of landmarks form a shape. The shape may be represented as a vector using coordinates of points in the shape. One shape is aligned with another shape using a similarity transformation (allowing translation, scaling and rotation) that minimizes the average euclidean distance between shape points. The average shape is the average of the aligned training shapes.

In some examples, searching for landmarks from an average shape aligned with the position and size of the face determined by the global face detector begins. Then, such search repeats the steps of: the tentative shape is suggested by adjusting the positioning of the shape points by template matching of the image texture around each point, and then conforming the tentative shape to the global shape model until convergence occurs. In some systems, individual template matching is unreliable, and shape models pool the results of weak template matching to form a stronger overall classifier. The entire search repeats at each level of the image pyramid from coarse resolution to fine resolution.

The transformation system may capture images or video streams on a client device (e.g., client device 102) and perform complex image manipulation locally on the client device 102 while maintaining an appropriate user experience, computation time, and power consumption. Complex image manipulation may include size and shape changes, mood migration (e.g., changing a face from frowning to smiling), state migration (e.g., aging a subject, reducing apparent age, changing gender), style migration, graphical element application, and any other suitable image or video manipulation implemented by a convolutional neural network that has been configured to be efficiently performed on the client device 102.

In some examples, a computer animation model for transforming image data may be used by a system in which a user may capture an image or video stream (e.g., self-timer) of the user using a client device 102 having a neural network operating 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 faces within an image or video stream and provides a modification icon associated with a computer animation model to transform image data, or the computer animation model may be presented in association with an interface described herein. The modification icon includes a change that may 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 converting the user's image to reflect the selected modification icon (e.g., generating a smiley face on the user). Once the image or video stream is captured and the specified modification is selected, the modified image or video stream may be presented in a graphical user interface displayed on the client device 102. The transformation system may implement a complex convolutional neural network on a portion of the image or video stream to generate and apply the selected modifications. That is, once the modify icon is selected, the user may capture an image or video stream and be presented with the results of the modification in real-time or near real-time. Further, the modification may be persistent while the video stream is being captured, and the selected modification icon remains switched. A neural network of machine teachings may be used to implement such modifications.

Presenting a modified graphical user interface performed by the transformation system may provide the user with additional interaction options. Such options may be based on the interface used to initiate content capture and selection of a particular computer animation model (e.g., initiated from a content creator user interface). In various examples, the modification may be durable after an initial selection of the modification icon. The user may turn the modification on or off by tapping or otherwise selecting the face modified by the transformation system and store it for later viewing or browsing to other areas of the imaging application. In the case of multiple faces modified by the transformation system, the user may globally turn the modification on or off by tapping or selecting a single face modified and displayed within the graphical user interface. In some examples, each face in a set of multiple faces may be modified individually, or such modification may be switched individually by tapping or selecting each face or a series of each faces displayed within the graphical user interface.

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

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

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

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

Data communication architecture

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

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

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

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

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

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

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

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

Message geolocation parameters 416: geolocation data (e.g., latitude and longitude coordinates) associated with the content payload of the message. A plurality of message geolocation parameter 416 values may be included in the payload, each of which is associated with a content item included in the content (e.g., a particular image in the message image payload 406, or a particular video in the message video payload 408).

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

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

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

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

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

Glasses apparatus

Fig. 5 shows a front perspective view of a glasses apparatus 119 in the form of a pair of smart glasses including a gesture control system 107 according to an example embodiment. The eyeglass apparatus 119 comprises a main body 503, the main body 503 comprising a front piece or frame 506 and a pair of temples 509 connected to the frame 506 for supporting the frame 506 in position on the face of a user when the eyeglass apparatus 119 is worn. The frame 506 can be made of any suitable material, such as plastic or metal, including any suitably shaped memory alloy.

The eyeglass apparatus 119 comprises a pair of optical elements in the form of a pair of lenses 512 that are held by a corresponding pair of optical element holders in the form of a pair of frames 515 that form part of the frame 506. The frame 515 is connected by a bridge 518. In other embodiments, one or both of the optical elements may be a display, a display assembly, or a combination of a lens and a display.

The frame 506 includes a pair of end pieces 521 that define the lateral ends of the frame 506. In this example, various electronic components are housed in one or both of the end pieces 521. The temples 509 are coupled to the respective end pieces 521. In this example, the temple 509 is coupled to the frame 506 by a respective hinge so as to be hingedly movable between a wearable mode and a folded mode in which the temple 509 is pivoted toward the frame 506 to lie substantially flat against the frame 506. In other embodiments, the temple 509 can be coupled to the frame 506 by any suitable means, or can be rigidly or fixedly secured to the frame 506 so as to be integral therewith.

Each of the temples 509 includes a front portion that is coupled to the frame 506 and any suitable rear portion for coupling to the user's ear, such as the curvilinear or cutting elements shown in the exemplary embodiment of fig. 5. In some embodiments, the frame 506 is formed from a single piece of material so as to have a unitary or monolithic construction. In some embodiments, the entire body 503 (including both the frame 506 and the temple 509) can be of unitary or monolithic construction.

Eyeglass device 119 has onboard electronics, including a computing device, such as a computer 524 or low power processor, which in different embodiments may be of any suitable type for carrying by body 503. In some embodiments, the computer 524 is at least partially housed in one or both of the temples 509. In this embodiment, various components of the computer 524 are housed in side end pieces 521 of the frame 506. The computer 524 includes one or more processors having memory (e.g., volatile storage, such as random access memory or registers), storage (e.g., non-volatile storage), wireless communication circuitry (e.g., BLE communication devices and/or WiFi direct devices), and a power supply. The computer 524 includes low power circuitry, high speed circuitry, and in some embodiments, a display processor. Various embodiments may include these elements in different configurations or integrated together in different ways.

The computer 524 also includes a battery 527 or other suitable portable power source. In one embodiment, a battery 527 is disposed in one of the temples 509. In the eyeglass apparatus 119 shown in fig. 5, a battery 527 is shown disposed in one of the end pieces 521, electrically coupled with the remainder of the computer 524 housed in the respective end piece 521.

The eyeglass device 119 has a camera function, in this example comprising a camera 530 mounted in one of the end pieces 521 and facing forward, so as to be more or less aligned with the viewing direction of the wearer of the eyeglass device 119. The camera device 530 is configured to capture digital images (also referred to herein as digital photographs or pictures) as well as digital video content. The operation of the camera 530 is controlled by a camera controller provided by the computer 524, and image data representing images or videos captured by the camera 530 is temporarily stored on a memory forming part of the computer 524. In some embodiments, the eyeglass apparatus 119 can have a pair of cameras 530, for example, that are received by respective end pieces 521.

As will be described in greater detail below, the on-board computer 524, the camera 530, and the lens 512 are configured together to provide a gesture control system 107, which gesture control system 107 automatically browses content and activates a function associated with the content based on gestures within the field of view of the lens 512. In particular, the lens 512 may display virtual content or one or more virtual objects. This makes it appear to the user that the virtual content is integrated in the real world environment that the user views through the lens 512. In some implementations, virtual content is received from the client device 102. In some implementations, the virtual content is received directly from the application server 114.

Based on input received by the eyewear device 119 from the camera 530, the eyewear device 119 may control user interactions with the virtual content based on gestures of a hand appearing in one or more images captured by the camera 530. In one example, the user interaction may control playback of content presented on the lens 512. In another example, the user interaction may browse a playlist or a music or video library. In another example, the user interaction may browse conversations in which the user participates, for example, by scrolling through various three-dimensional or two-dimensional conversation elements (e.g., chat conversations) and selecting individual conversation elements to respond to generate a message to communicate to participants of the conversation.

The gesture control system 107 (which may be implemented by the computer 524) determines the current orientation of the index finger relative to the orientation of one or more virtual objects presented in the lens 512. For example, gesture control system 107 determines that the orientation or line of the index finger is within a threshold range of the orientation of one or more virtual objects. Responsive to determining that the orientation or line of the index finger is within a threshold range of the orientation of the one or more virtual objects, gesture control system 107 may map the orientation of the index finger to the one or more virtual objects. In response to mapping the orientation of the index finger to the virtual object, gesture control system 107 may trigger control of the virtual object (e.g., browse the virtual object and activate functions related to the virtual object) based on the gestures of other fingers (e.g., thumbs) with respect to the index finger. For example, the gesture control system 107 detects movement of the thumb along the index finger direction (e.g., the gesture control system 107 detects that the thumb has been dragged along the index finger). In response, gesture control system 107 moves the scroll bar or advances one or more objects in the same direction as the thumb.

The eyeglass device 119 further comprises one or more communication devices, such as a Bluetooth Low Energy (BLE) communication interface. Such BLE communication interface enables the eyeglass device 119 to communicate wirelessly with the client device 102. Instead of or in addition to BLE communication interfaces, other forms of wireless communication may be employed, such as WiFi direct interfaces. The BLE communication interface implements a standard number of BLE communication protocols.

The first communication protocol implemented by the BLE interface of the glasses device 119 enables an unencrypted link to be established between the glasses device 119 and the client device 102. In this first protocol, the link layer communication (physical interface or medium) between the glasses device 119 and the client device 102 includes unencrypted data. In this first protocol, the application layer (the communication layer operating on physically exchanged data) encrypts and decrypts the data physically exchanged in unencrypted form over the link layer of the BLE communication interface. In this way, data exchanged through the physical layer can be freely read by the eavesdropping device, but the eavesdropping device will not be able to crack the exchanged data without performing decryption operations in the application layer.

The second communication protocol implemented by the BLE interface of the glasses device 119 enables an encrypted link to be established between the glasses device 119 and the client device 102. In this second protocol, link layer communications (physical interface) between the glasses device 119 and the client device 102 receive data from the application layer and add a first type of encryption to the data before exchanging the data over the physical medium. In this second protocol, the application layer (the communication layer operating on physically exchanged data) may or may not encrypt and decrypt the data in encrypted form using the first type of encryption over the link layer of the BLE communication interface. That is, the data may be first encrypted by the application layer and then further encrypted by the physical layer before being exchanged over the physical medium. After exchanging over the physical medium, the data is then decrypted by the physical layer and then decrypted again by the application layer (e.g., using a different type of encryption). In this way, data exchanged through the physical layer cannot be read by eavesdropping devices because the data is encrypted in the physical medium.

In some implementations, the client device 102 communicates with the eyeglass device 119 using a first protocol to exchange images or video or virtual content between the messaging client 104 and the eyeglass device 119.

Gesture control system

FIG. 6 is a flowchart illustrating example operations of the gesture control system 107 in performing a process 600 according to an example embodiment. The process 600 may be embodied in computer readable instructions executed by one or more processors such that the operations of the process 600 may be performed in part or in whole by the functional components of the gesture control system 107; thus, process 600 is described below by way of example with reference thereto. However, in other embodiments, at least some of the operations of process 600 may be deployed on a variety of other hardware configurations. Thus, the process 600 is not intended to be limited to the gesture control system 107, but may be implemented in whole or in part by any other component. Some or all of the operations of process 600 may be omitted in parallel, out of order, or entirely.

At operation 601, the gesture control system 107 displays one or more virtual objects on the eyewear device. For example, when the eyeglass device 119 is pointed at a first room in the environment, the gesture control system 107 displays a list of thumbnails representing different media assets in the lens 512 of the eyeglass device 119.

At operation 602, the gesture control system 107 detects a hand within a field of view of the eyeglass device through an image capture device of the eyeglass device. For example, the gesture control system 107 may communicate with an on-board camera of the eyeglass device 119 to determine or detect that a user's hand is present within a field of view of a lens of the eyeglass device 119. For example, the camera may continuously or periodically scan real world objects included in one or more images or real-time video feeds of the camera. The camera device may determine whether the real world object corresponds to a person's hand, for example, using known image recognition techniques. In response, the camera may indicate to the gesture control system 107 that the user's hand has been detected within the field of view of the lenses of the eyewear device 119.

At operation 603, the gesture control system 107 determines that the first finger of the hand is oriented in the same direction as the displayed one or more virtual objects. For example, the gesture control system 107 determines two points on the index finger (e.g., a start point and an end point of the index finger). Gesture control system 107 draws a virtual line along these two points and compares the line to the orientation of one or more virtual objects. The gesture control system 107 determines that the orientation of the index finger or line is within a threshold range of the orientation of one or more virtual objects by, for example, measuring the angle between the line representing the orientation of the index finger and the line representing the orientation of the virtual object and comparing the angle to a threshold (e.g., 15 degrees). Responsive to determining that the angle is less than the threshold, the gesture control system 107 may map the orientation of the index finger to one or more virtual objects.

At operation 604, the gesture control system 107 detects movement of a second finger of the hand relative to the first finger. For example, the gesture control system 107 detects movement of the thumb along the index finger direction (e.g., the gesture control system 107 detects that the thumb has been dragged along the index finger). In response, gesture control system 107 moves the scroll bar or advances one or more objects in the same direction as the thumb. As another example, the gesture control system 107 detects contact between the thumb and the index finger (e.g., the gesture control system 107 determines that the user is tapping the index finger with the user's thumb). In response, the gesture control system 107 activates a function associated with the virtual content item currently focused on (currently highlighted by the cursor).

At operation 605, gesture control system 107 controls the display of one or more virtual objects in response to detecting movement of the second finger relative to the first finger. For example, gesture control system 107 moves a scroll bar or advances one or more objects in the same direction as the thumb. As another example, gesture control system 107 starts playing, pauses playback, or stops playing a media asset associated with and represented by the identified virtual content item in response to detecting contact between the thumb and index finger.

Fig. 7-9 are illustrative screens of a graphical user interface of the gesture control system 107 according to example embodiments. The screens shown in fig. 7-9 may be provided by the messaging client 104 of one or more client devices 102, other applications implemented on one or more client devices 102, or the eyewear device 119.

For example, the screen 700 of fig. 7 shows a view of a first portion of the real world environment 701 through the lens 512 of the eyewear device 112. The eyewear device 112 may receive input from a user requesting to view a list of thumbnails representing a music or video library. In response, the eyewear device 112 obtains one or more virtual objects 702 from the client device 102 and/or from the application server 114. Virtual object 702 includes thumbnails (e.g., cover art) representing different media assets (e.g., different songs or videos). The eyewear device 112 displays the virtual object 702 as a three-dimensional object at the center of the lens 512, and displays the virtual object 702 in a three-dimensional cylindrical carousel arrangement. The eyewear device 112 also displays a scrollbar oriented in the same direction as the virtual object 702. The eyewear device 112 also displays the title of the current virtual object or thumbnail of interest. This makes it appear to the user that the first portion of the real world environment 701 is viewed through the lens 512 as if the virtual object 702 and the scrollbar were within the first portion of the real world environment 701.

The eyewear device 112 processes images captured by the camera of the eyewear device 112. The eyewear device 112 detects that a real world hand 710 is present in an image captured by the camera. The eyewear device 112 recognizes the index finger 712 and thumb 714 of the hand. The eyewear device 112 determines the orientation of the virtual object 702 and the scroll bar 703. For example, the eyewear device 112 determines that the virtual object 702 and the scroll bar 703 are oriented in a horizontal direction. The eyewear device 112 determines that the orientation of the index finger 712 corresponds to the scroll bar 703 (aligned with the scroll bar 703 or within a threshold range of alignment). In response, the eyewear device 112 maps the index finger 712 to the scroll bar 703 to enable the user to browse the virtual object 702 associated with the scroll bar 703.

For example, the eyewear device 112 maps the current position of the thumb 714 to the current position of the cursor of the scroll bar 703. When the eyewear device 112 detects movement of the thumb in the direction and orientation of the scroll bar 703 and index finger 712, the eyewear device 112 advances the carousel of the virtual object 702 in the same direction. For example, as shown in screen 800 (fig. 8), eyeglass device 112 determines that thumb 814 has moved a given amount to the left. In response, the eyewear device 112 navigates the virtual object 702 to the left by rotating the carousel to the right (e.g., rotating the carousel in a direction opposite to the direction of thumb movement). The eyewear device 112 represents this scrolling operation by moving the cursor of the scroll bar 703 from a first position shown in fig. 7 to a second position 803 shown in fig. 8.

In a similar manner, the eyewear device 112 may scroll the virtual object to the right in response to detecting movement of the thumb in the right direction. For example, as shown in screen 900 (fig. 9), eyeglass device 112 determines that thumb 814 has been moved a given amount to the right. In response, the eyewear device 112 navigates the virtual object 702 to the right by rotating the carousel to the left. The eyewear device 112 represents this scrolling operation by moving the cursor of the scroll bar 703 from the first position shown in fig. 7 to the third position shown in fig. 9.

As the thumb moves in a given direction, virtual object 702 is rotated. The rate and speed at which virtual object 702 rotates and scrolls around the carousel corresponds to the rate and speed at which the thumb moves. For example, if the eyewear device 112 determines that the thumb is slid or dragged in the direction of the index finger at a first rate or speed, the eyewear device 112 advances the cursor of the scroll bar and rotates the virtual object 702 at a first rate or speed that matches or corresponds to the rate or speed at which the thumb is moved. If the eyewear device 112 determines that the thumb is slid or dragged in the direction of the index finger at a second rate or speed, the eyewear device 112 advances the cursor of the scrollbar and rotates the virtual object 702 at a second rate or speed that matches or corresponds to the rate or speed at which the thumb is moved.

Once a given virtual object of interest is identified by the cursor, the eyewear device 112 may detect a gesture performed by the user's hand to activate a function associated with the given virtual object. For example, the virtual object may include a thumbnail representing a media asset (e.g., music or video). In response to detecting the thumb 912 tapping or touching the index finger, the eyewear device 112 activates a function to select a media asset represented by the thumbnail currently of interest and identified by the cursor. For example, the eyewear device 112 may retrieve and play back music or video corresponding to the identified thumbnail in response to detecting the thumb 912 tapping or touching the index finger. As another example, in response to detecting a thumb 912 tap or contact with the index finger, music or video corresponding to the identified thumbnail may be stopped or paused.

Machine architecture

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

The machine 1000 may include a processor 1002, a memory 1004, and input/output (I/O) components 1038, which may be configured to communicate with each other via a bus 1040. In an example, the processor 1002 (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 1006 and a processor 1010 that execute instructions 1008. The term "processor" is intended to include multi-core processors, which may include two or more separate processors (sometimes referred to as "cores") that may concurrently execute instructions. Although fig. 10 shows multiple processors 1002, machine 1000 may include a single processor with a single core, a single processor with multiple cores (e.g., a multi-core processor), multiple processors with a single core, multiple processors with multiple cores, or any combination thereof.

The memory 1004 includes a main memory 1012, a static memory 1014, and a storage unit 1016, all of which are accessible by the processor 1002 via the bus 1040. Main memory 1004, static memory 1014, and storage unit 1016 store instructions 1008 that implement any one or more of the methods or functions described herein. The instructions 1008 may also reside, completely or partially, within the main memory 1012, within the static memory 1014, within the machine-readable medium 1018 within the storage unit 1016, within at least one of the processors 1002 (e.g., within a cache memory of a processor), or within any suitable combination thereof, during execution thereof by the machine 1000.

The I/O components 1038 may include various components for receiving input, providing output, producing output, transmitting information, exchanging information, capturing measurement results, and the like. The particular I/O components 1038 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 may not include such a touch input device. It should be appreciated that I/O component 1038 can comprise many other components not shown in FIG. 10. In various examples, I/O components 1038 may include user output components 1024 and user input components 1026. The user output component 1024 can include visual components (e.g., a display such as a Plasma Display Panel (PDP), a Light Emitting Diode (LED) display, a Liquid Crystal Display (LCD), a projector, or a Cathode Ray Tube (CRT)), acoustic components (e.g., speakers), haptic components (e.g., vibration motors, resistance mechanisms), other signal generators, and so forth. User input components 1026 may include alphanumeric input components (e.g., a keyboard, a touch screen configured to receive alphanumeric input, an optical keyboard, or other alphanumeric input components), point-based input components (e.g., a mouse, a touchpad, a trackball, a joystick, a motion sensor, or another pointing instrument), tactile input components (e.g., physical buttons, a touch screen providing positioning and/or force of a touch or touch gesture, or other tactile input components), audio input components (e.g., a microphone), and the like.

In another example, I/O components 1038 may include: biometric component 1028, moving component 1030, environmental component 1032, or location component 1034, among a wide variety of other components. For example, the biometric component 1028 includes components for detecting expressions (e.g., hand expressions, facial expressions, voice expressions, body gestures, or eye tracking), measuring biological signals (e.g., blood pressure, heart rate, body temperature, perspiration, or brain waves), identifying a person (e.g., voice recognition, retinal recognition, facial recognition, fingerprint recognition, or electroencephalogram-based recognition), and the like. The motion component 1030 includes an acceleration sensor component (e.g., accelerometer), a gravity sensor component, a rotation sensor component (e.g., gyroscope).

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

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

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

The location component 1034 includes a position sensor component (e.g., a GPS receiver component), an altitude sensor component (e.g., an altimeter or barometer that detects barometric pressure from which altitude may be derived), an orientation sensor component (e.g., a magnetometer), and so forth.

Communication may be implemented using a variety of techniques. The I/O components 1038 also include a communication component 1036, the communication component 1036 being operable to couple the machine 1000 to the network 1020 or the device 1022 via a corresponding coupling or connection. For example, communication components 1036 may include a network interface component or other suitable device to interface with network 1020. In a further example of this embodiment, the method comprises, the communication means 1036 may include wired communication means, wireless communication means cellular communication component, near Field Communication (NFC) component,Parts (e.g.)>Low power consumption)/(f)>Components, and other communication components that provide communication via other modalities. Device 1022 may be another machine or any of a variety of peripheral devices (e.g., a peripheral device coupled via USB).

Further, communication component 1036 may detect an identifier or include components operable to detect an identifier. For example, the communication component 1036 may include a Radio Frequency Identification (RFID) tag reader component, an NFC smart tag detection component, an optical reader component (e.g., an optical sensor for detecting one-dimensional barcodes such as Universal Product Code (UPC) barcodes, multi-dimensional barcodes such as Quick Response (QR) codes, aztec codes, data Matrix (Data Matrix), data symbol (Dataglyph), maximum Code (MaxiCode), PDF417, ultra Code (Ultra Code), UCC RSS-2D barcodes, and other optical codes), or an acoustic detection component (e.g., a microphone for identifying marked audio signals). In addition, various information may be available via the communication component 1036, e.g., location via Internet Protocol (IP) geolocation, via Signal triangulated positioning, positioning via detection of NFC beacon signals, etc., which may indicate a particular positioning.

The various memories (e.g., main memory 1012, static memory 1014, and memory of processor 1002) and storage unit 1016 may store one or more sets of instructions and data structures (e.g., software) implemented or used by any one or more of the methods or functions described herein. These instructions (e.g., instructions 1008), when executed by the processor 1002, cause various operations to implement the disclosed examples.

The instructions 1008 may be transmitted or received over the network 1020 via a network interface device, such as the network interface component included in the communications component 1036, using a transmission medium and using any of a number of well-known transmission protocols, such as the hypertext transfer protocol (HTTP). Similarly, the instructions 1008 may be transmitted or received via a coupling (e.g., peer-to-peer coupling) with the device 1022 using a transmission medium.

Software architecture

Fig. 11 is a block diagram 1100 illustrating a software architecture 1104 that may be installed on any one or more of the devices described herein. The software architecture 1104 is supported by hardware such as a machine 1102 that includes a processor 1120, memory 1126 and I/O components 1138. In this example, the software architecture 1104 may be conceptualized as a stack of layers, with each layer providing a particular function. The software architecture 1104 includes layers such as an operating system 1112, libraries 1110, frameworks 1108, and applications 1106. In operation, the application 1106 activates an API call 1150 through the software stack and receives a message 1152 in response to the API call 1150.

Operating system 1112 manages hardware resources and provides common services. Operating system 1112 includes, for example, kernel 1114, services 1116 and drivers 1122. The kernel 1114 acts as an abstraction layer between the hardware layer and other software layers. For example, the kernel 1114 provides memory management, processor management (e.g., scheduling), component management, networking, and security settings, among other functions. Service 1116 may provide other common services for other software layers. The driver 1122 is responsible for controlling or interfacing with the underlying hardware. For example, the driver 1122 may include a display driver, an imaging device driver,Or->Low power consumption driver, flash memory driver, serial communication driver (e.g., USB driver)>Drivers, audio drivers, power management drivers, etc.

Library 1110 provides a common low-level infrastructure used by applications 1106. The library 1110 may include a system library 1118 (e.g., a C-standard library), the system library 1118 providing functions such as memory allocation functions, string manipulation functions, mathematical functions, and the like. Further, libraries 1110 may include API libraries 1124, such as media libraries (e.g., libraries for supporting presentation and manipulation of various media formats, such as moving Picture experts group 4 (MPEG 4), advanced video coding (H.264 or AVC), moving Picture experts group layer 3 (MP 3), advanced Audio Coding (AAC), adaptive Multi-Rate (AMR) audio codec, joint Picture experts group (JPEG or JPG) or Portable Network Graphics (PNG)), graphics libraries (e.g., openGL framework for presentation in two-dimensional (2D) and three-dimensional (3D) in graphical content on a display), database libraries (e.g., SQLite providing various relational database functions), web libraries (e.g., webKit providing web browsing functions), and the like. The library 1110 may also include various other libraries 1128 to provide many other APIs to the application 1106.

Framework 1108 provides a common high-level infrastructure used by applications 1106. For example, framework 1108 provides various Graphical User Interface (GUI) functions, advanced resource management, and advanced location services. Framework 1108 can provide a wide variety of other APIs that can be used by applications 1106, some of which can be specific to a particular operating system or platform.

In an example, applications 1106 can include a home application 1136, a contacts application 1130, a browser application 1132, a book reader application 1134, a positioning application 1142, a media application 1144, a messaging application 1146, a gaming application 1148, and a variety of other applications such as an external application 1140. The application 1106 is a program that performs functions defined in the program. One or more of the applications 1106 that are variously structured may be created using a variety of programming languages, such as an object oriented programming language (e.g., objective-C, java or C++) or a procedural programming language (e.g., C-language or assembly language). In a particular example, external application 1140 (e.g., using ANDROID by an entity other than the vendor of the particular platform) ^TM Or IOS ^TM Applications developed in Software Development Kits (SDKs) may be, for example, in IOS ^TM 、ANDROID ^TM 、The Phone's mobile operating system or another mobile software running on the mobile operating system. In this example, external applications 1140 can activate API calls 1150 provided by operating system 1112 to facilitate the functionality described herein.

Glossary of terms:

in this context, a "carrier signal" refers to any intangible medium capable of storing, encoding, or carrying transitory or non-transitory instructions for execution by a machine, and includes digital or analog communication signals or other intangible medium to facilitate communication of such instructions. The instructions may be transmitted or received over a network via a network interface device using a transitory or non-transitory transmission medium and using any of a number of well-known transmission protocols.

In this context, "client device" refers to any machine that interfaces with a communication network to obtain resources from one or more server systems or other client devices. The client device may be, but is not limited to, a mobile phone, desktop computer, laptop computer, PDA, smart phone, tablet computer, super book, netbook, laptop computer, multiprocessor system, microprocessor-based or programmable consumer electronics, game console, set top box, or any other communication device that a user may use to access a network.

In this context, a "communication network" refers to one or more portions of a network, the network may be an ad hoc network, an intranet, an extranet, a Virtual Private Network (VPN), a Local Area Network (LAN), a Wireless LAN (WLAN), a Wide Area Network (WAN), a Wireless WAN (WWAN), a Virtual Private Network (VPN) Metropolitan Area Networks (MANs), the Internet, portions of the Public Switched Telephone Network (PSTN), plain Old Telephone Service (POTS) networks, cellular telephone networks, wireless networks,A network, another type of network, or a combination of two or more such networks. For example, the network or a portion of the network may comprise a wireless network or a cellular networkThe 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 (1 xRTT), evolution data optimized (EVDO) technology, general Packet Radio Service (GPRS) technology, enhanced data rates for GSM evolution (EDGE) technology, third generation partnership project (3 GPP) including 3G, fourth generation wireless (4G) networks, universal Mobile Telecommunications System (UMTS), high Speed Packet Access (HSPA), worldwide Interoperability for Microwave Access (WiMAX), long Term Evolution (LTE) standards, other data transmission technologies defined by various standards setting organizations, other long distance protocols, or other data transmission technologies.

In this context, a "ephemeral message" refers to a message that is accessible for a time-limited duration. The transient message may be text, images, video, etc. The access time for the ephemeral message may be set by the message sender. Alternatively, the access time may be a default setting or a setting specified by the recipient. The message is temporary regardless of the setup technique.

In this context, a "machine-readable medium" refers to a component, apparatus, or other tangible medium capable of temporarily or permanently storing instructions and data, and may include, but is not limited to, random Access Memory (RAM), read Only Memory (ROM), cache memory, flash memory, optical media, magnetic media, cache memory, other types of storage devices (e.g., erasable programmable read only memory (EEPROM)), and/or any suitable combination thereof. The term "machine-readable medium" shall be taken to include a single medium or multiple media (e.g., a centralized or distributed database, or associated caches and servers) that are capable of storing the instructions. The term "machine-readable medium" shall also be taken to include any medium or combination of multiple media that is capable of storing instructions (e.g., code) for execution by a machine such that, when the instructions are executed by one or more processors of the machine, the instructions cause the machine to perform any one or more of the methodologies described herein. Thus, a "machine-readable medium" refers to a single storage device or apparatus, as well as a "cloud-based" storage system or storage network that includes multiple storage devices or apparatus. The term "machine-readable medium" does not include signals themselves.

In this context, "component" refers to a device, physical entity, or logic having the following boundaries: the boundaries are defined by function or subroutine calls, branch points, APIs, or other techniques provided for partitioning or modularizing specific processing or control functions. The components may be combined with other components via their interfaces to perform the machine processes. A component may be a packaged functional hardware unit designed for use with other components and may be part of a program that typically performs certain of the relevant functions. The components may constitute software components (e.g., code embodied on a machine-readable medium) or hardware components. A "hardware component" is a tangible unit capable of performing certain operations and may be configured or arranged in some physical manner. In various example embodiments, one or more computer systems (e.g., stand-alone computer systems, client computer systems, or server computer systems) or one or more hardware components of a computer system (e.g., processors or groups of processors) may be configured by software (e.g., an application or application part) to operate to perform certain operations as described herein.

The hardware components may also be implemented mechanically, electronically, or in any suitable combination thereof. For example, a hardware component may include specialized circuitry or logic permanently configured to perform certain operations. The hardware component may be a special purpose processor such as a Field Programmable Gate Array (FPGA) or ASIC. The hardware components may also include programmable logic or circuitry that is temporarily configured by software to perform certain operations. For example, the hardware components may include software that is executed by a general purpose processor or other programmable processor. Once configured by such software, the hardware components become the specific machine (or specific component of the machine) uniquely tailored to perform the configured functions, and are no longer general purpose processors. It will be appreciated that decisions to implement hardware components mechanically, in dedicated and permanently configured circuitry, or in temporarily configured circuitry (e.g., configured by software) may be driven by cost and time considerations. Accordingly, the phrase "hardware component" (or "hardware-implemented component") should be understood to include a tangible entity, i.e., an entity that is physically constructed, permanently configured (e.g., hardwired), or temporarily configured (e.g., programmed) to operate in a certain manner or to perform certain operations described herein. Considering embodiments in which hardware components are temporarily configured (e.g., programmed), each of the hardware components need not be configured or instantiated at any one time. For example, in the case where the hardware components include general-purpose processors that are dedicated processors by software configuration, the general-purpose processors may be respectively configured as respective different dedicated processors (e.g., including different hardware components) at different times. Thus, software configures one or more particular processors to constitute a particular hardware component at one time and to constitute a different hardware component at a different time, for example.

A hardware component may provide information to and receive information from other hardware components. Thus, the described hardware components may be considered to be communicatively coupled. Where multiple hardware components are present at the same time, communication may be achieved by signaling (e.g., through appropriate circuitry and buses) between or among two or more of the hardware components. In embodiments in which multiple hardware components are configured or instantiated at different times, communication between such hardware components may be achieved, for example, by storing information in a memory structure accessible to the multiple hardware components and retrieving information in the memory structure. For example, one hardware component may perform an operation and store an output of the operation in a memory device communicatively coupled thereto. Other hardware components may then access the memory device at a later time to retrieve the stored output and process it.

The hardware component may also initiate communication with an input device or an output device, and may operate on a resource (e.g., a collection of information). Various operations of the example methods described herein may be performed, at least in part, by one or more processors that are temporarily configured (e.g., via software) or permanently configured to perform the relevant operations. Whether temporarily configured or permanently configured, such a processor may constitute a processor-implemented component that operates to perform one or more operations or functions described herein. As used herein, "processor-implemented components" refers to hardware components implemented using one or more processors. Similarly, the methods described herein may be implemented, at least in part, by processors, where a particular processor or processors are examples of hardware. For example, at least some of the operations of the method may be performed by one or more processors or processor-implemented components. In addition, one or more processors may also operate to support execution of related operations in a "cloud computing" environment or as "software as a service" (SaaS) operations. For example, at least some of the operations may be performed by a set of computers (as examples of machines including processors), where the operations are accessible via a network (e.g., the internet) and via one or more suitable interfaces (e.g., APIs). The performance of certain operations may be distributed among processors, may reside not only within a single machine, but may be deployed across several machines. In some example embodiments, the processor or processor-implemented components may be located in a single geographic location (e.g., within a home environment, an office environment, or a server farm). In other example implementations, the processor or processor-implemented components may be distributed across several geolocations.

In this context, a "processor" refers to any circuit or virtual circuit (a physical circuit emulated by logic executing on an actual processor) that manipulates data values according to control signals (e.g., "commands," "operation codes," "machine codes," etc.) and generates corresponding output signals for operating the machine. For example, the processor may be 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 ASIC, a Radio Frequency Integrated Circuit (RFIC), or any combination thereof. A processor may also be a multi-core processor having two or more separate processors (sometimes referred to as "cores") that may execute instructions simultaneously.

In this context, a "time stamp" refers to a series of characters or coded information that identify when an event occurs, such as a given date and time, sometimes as small as a fraction of a second in accuracy.

Changes and modifications may be made to the disclosed embodiments without departing from the scope of the present disclosure. These and other changes or modifications are intended to be included within the scope of the present disclosure as expressed in the appended claims.

Module, component and logic

Certain embodiments are described herein as comprising logic or multiple components, modules, or mechanisms. A module may constitute a software module (e.g., code embodied on a machine readable medium or in a transmitted signal) or a hardware module. A "hardware module" is a tangible unit capable of performing a particular operation and may be configured or arranged in a particular physical manner. In various example embodiments, one or more computer systems (e.g., a standalone computer system, a client computer system, or a server computer system) or one or more hardware modules (e.g., a processor or a group of processors) of a computer system are configured by software (e.g., an application or application portion) as hardware modules that operate to perform certain operations described herein.

In some implementations, the hardware modules are implemented mechanically, electronically, or in any suitable combination thereof. For example, a hardware module may include specialized circuitry or logic permanently configured to perform certain operations. For example, the hardware module may be a special purpose processor such as a Field Programmable Gate Array (FPGA) or an Application Specific Integrated Circuit (ASIC). A hardware module may also include programmable logic or circuitry that is temporarily configured by software to perform certain operations. For example, the hardware modules may include software contained in a general-purpose processor or other programmable processor. It should be appreciated that decisions to mechanically implement hardware modules in dedicated and permanently configured circuitry or temporarily configured circuitry (e.g., circuitry configured by software) may be driven by cost and time considerations.

Thus, the phrase "hardware module" should be understood to include tangible entities, i.e., entities physically constructed, permanently configured (e.g., hardwired) or temporarily configured (e.g., programmed) to operate in a certain manner or to perform certain operations described herein. As used herein, "hardware-implemented module" refers to a hardware module. In view of the implementation in which hardware modules are temporarily configured (e.g., programmed), each of the hardware modules need not be configured or instantiated at any one time. For example, in the case where the hardware modules include general-purpose processors configured by software as special-purpose processors, the general-purpose processors may be configured at different times as respectively different special-purpose processors (e.g., including different hardware modules). Thus, software may configure one or more particular processors to constitute a particular hardware module at one time and to constitute a different hardware module at a different time, for example.

A hardware module may provide information to and may receive information from other hardware modules. Thus, the described hardware modules may be considered to be communicatively coupled. Where multiple hardware modules exist concurrently, communication may be accomplished through signaling (e.g., through appropriate circuitry and buses) between or among two or more of the hardware modules. In embodiments where multiple hardware modules are configured or instantiated at different times, communication between or among the hardware modules may be implemented, for example, by storing and retrieving information in a memory structure accessible to the multiple hardware modules. For example, one hardware module performs an operation and stores an output of the operation in a memory device to which it is communicatively coupled. Another hardware module may then access the memory device at a later time to retrieve and process the stored output. The hardware module may also initiate communication with an input or output device and may operate on a resource (e.g., a collection of information).

Various operations of the example methods described herein may be performed, at least in part, by one or more processors that are temporarily configured (e.g., by software) or permanently configured to perform related operations. Whether temporarily configured or permanently configured, such processors constitute processor-implemented modules that operate to perform one or more of the operations or functions described herein. As used herein, "processor-implemented module" refers to a hardware module implemented using one or more processors.

Similarly, the methods described herein may be at least partially processor-implemented, where one or more particular processors are examples of hardware. For example, at least some of the operations of the method may be performed by one or more processors or processor-implemented modules. In addition, one or more processors may also be operative to support performance of related operations in a "cloud computing" environment or as "software as a service" (SaaS). For example, at least some of the operations may be performed by a set of computers (as examples of machines including processors), where the operations may be accessed via a network (e.g., the internet) and via one or more suitable interfaces (e.g., APIs).

The performance of certain of the operations may be distributed among processors, not only residing in a single machine, but also deployed across multiple machines. In some example implementations, the processor or processor-implemented module is located in a single geographic location (e.g., within a home environment, an office environment, or a server farm). In other example implementations, the processor or processor-implemented modules are distributed across multiple geographic locations.

Claims

1. A method, comprising:

displaying, by one or more processors of a glasses device, one or more virtual objects on the glasses device;

detecting a hand within a field of view of the eyeglass device by an imaging device of the eyeglass device;

determining that a first finger of the hand is oriented in a same direction as the one or more virtual objects displayed;

detecting movement of a second finger of the hand relative to the first finger; and

in response to detecting movement of the second finger relative to the first finger, controlling display of the one or more virtual objects.

2. The method of claim 1, wherein the one or more virtual objects comprise a scroll bar extending along an x-axis, wherein the first finger comprises an index finger, and wherein the second finger comprises a thumb.

3. The method of any of claims 1-2, further comprising:

determining that the second finger is moving in a first direction along the x-axis; and

in response to determining that the second finger is moving in the first direction along the x-axis, the scrollbar is advanced toward the first direction.

4. The method of claim 3, wherein the one or more virtual objects comprise a plurality of thumbnails, further comprising:

in response to determining that the second finger is moving in the first direction along the x-axis, the plurality of thumbnails are rotated in the first direction.

5. The method of any of claims 3-4, wherein the plurality of thumbnails represent individual media assets.

6. The method of any of claims 3 to 5, further comprising:

determining that the second finger is moving in a second direction along the x-axis; and

in response to determining that the second finger is moving in the second direction along the x-axis, the scrollbar is advanced toward the second direction.

7. The method of any of claims 1-6, wherein the one or more virtual objects represent a first plurality of media assets associated with a first set of media content, further comprising:

Determining that the second finger has moved a first amount in a second direction perpendicular to the first direction; and

replacing a display of the first plurality of media assets associated with the first set of media content with a second plurality of media assets associated with a second set of media content.

8. The method of claim 7, further comprising:

determining that the second finger is moved in the second direction by a second amount greater than the first amount; and

replacing a display of the second plurality of media assets associated with the second set of media content with a third plurality of media assets associated with a third set of media content.

9. The method of any of claims 7 to 8, further comprising:

determining that the second finger is moving along the first direction after the second finger has been moved the first amount in the second direction; and

the second plurality of media assets is rotated in response to determining that the second finger has moved in the first direction after the second finger has moved the first amount in the second direction.

10. The method of any of claims 1-9, wherein the one or more virtual objects comprise a plurality of thumbnails, and wherein the plurality of thumbnails are displayed in a three-dimensional cylindrical carousel.

11. The method of any one of claims 1 to 10, further comprising:

determining that the second finger has been in contact with the first finger; and

determining that a given one of the one or more virtual objects is currently of interest; and

in response to determining that the second finger has been contacted by the first finger, a function associated with the given one of the one or more virtual objects is activated.

12. The method of claim 11, wherein the function comprises playing or pausing a media asset represented by the given one of the one or more virtual objects.

13. A system, comprising:

a storage device for the eyeglass device; and

a processor of an eyeglass device, the processor configured to perform operations comprising:

displaying one or more virtual objects on the eyewear device;

14. The system of claim 13, wherein the one or more virtual objects comprise a scroll bar extending along an x-axis, wherein the first finger comprises an index finger, and wherein the second finger comprises a thumb.

15. The system of any of claims 13 to 14, wherein the operations further comprise:

16. The system of claim 15, wherein the one or more virtual objects comprise a plurality of thumbnails, and wherein the operations further comprise:

17. The system of any of claims 15 to 16, wherein the plurality of thumbnails represent individual media assets.

18. The system of any of claims 13 to 17, wherein the operations further comprise:

19. The system of any of claims 13 to 18, wherein the one or more virtual objects represent a first plurality of media assets associated with a first set of media content, and wherein the operations further comprise:

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

displaying one or more virtual objects on the eyewear device;