Input modality for AR wearable devices

Abstract

Systems, methods, and computer readable media for augmented reality (AR) wearable device input modalities are disclosed. The AR wearable device captures an image using an image capture device and processes the image to identify an object. The object can be a person, a place, an object and the like. The AR wearable device associates the object with a tag (e.g., a name of the object or a function that may be provided by selecting the object). The AR wearable device then matches the tag of the object with a tag associated with the AR application. The AR wearable device presents an indication of an AR application with a matching tag on a display of the AR wearable device, which provides a user with an opportunity to enable one of the AR applications. The AR wearable device identifies a selection of an AR application in a variety of different ways including gesture recognition and voice commands.

Description

[0001] Priority declaration

[0002] This application claims the benefit of U.S. patent application serial number 17 / 830,708, filed on June 2, 2022, the entire contents of which are incorporated herein by reference. Technical Field

[0003] Examples of the present disclosure generally relate to input modalities for augmented reality (AR) wearable devices. More specifically, but not by way of limitation, examples of the present disclosure relate to input modalities for enabling AR applications based on objects recognized in images. Background Art

[0004] Users increasingly want augmented reality (AR) wearable devices to operate in a more user-friendly manner. However, typically, AR wearable devices have very little space for interface controls, which may make interacting with the AR wearable devices difficult or inconvenient. BRIEF DESCRIPTION OF THE DRAWINGS

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

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

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

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

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

[0010] Figure 5 is a flow chart for access restriction processing according to some examples.

[0011] Figure 6 A system for providing input modalities for an AR wearable device according to some examples is shown.

[0012] Figure 7 According to some examples Figure 6 Display of the system shown in .

[0013] Figure 8 Methods for input modalities for AR wearable devices according to some examples are shown.

[0014] Fig. 9 A continuation of a method for input modalities for an AR wearable device according to some examples is shown.

[0015] Fig.10 An example of a wearable electronic device in the form of glasses according to some examples is shown.

[0016] Fig.11 Methods for providing multiple input modalities for an AR wearable device according to some examples are shown.

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

[0018] Fig.13 is a block diagram illustrating a software architecture within which examples may be implemented.

[0019] Fig.14 is a diagrammatic representation of a processing environment according to some examples. DETAILED DESCRIPTION

[0020] The following description includes systems, methods, techniques, instruction sequences and computer program products that embody the illustrative examples of the present disclosure. In the following description, for the purpose of illustration, many specific details are set forth to provide an understanding of the various examples of the subject matter of the present invention. However, it will be apparent to those skilled in the art that the examples of the subject matter of the present invention can be put into practice without these specific details. Typically, known instruction instances, protocols, structures and techniques are not necessarily shown in detail.

[0021] The term “AR wearable device” is used as an illustrative device; however, one skilled in the art will recognize that the methods, systems, and computer-readable media disclosed herein are applicable to other wearable devices, such as mixed reality (MR) wearable devices and virtual reality (VR) wearable devices.

[0022] Typically, AR wearable devices, such as AR glasses, have limited physical space for user interface items such as buttons, mice, and touch screens. Some AR wearable devices have one or two buttons or touchpads on the side or frame of the AR wearable device with which the user can interact. However, the number of available AR applications continues to increase, making it difficult for users to select AR applications.

[0023] One challenge is how to provide a selection of AR applications for user selection, and how to enable the user to select an AR application, for example, in a limited physical space of a user interface. The application addresses this challenge by processing images captured by an AR wearable device and identifying objects within the images. The application assigns or associates metadata in the form of tags (e.g., object names or functions that can be provided by selecting the object) to the objects. The AR application is also associated with metadata (e.g., tags selected by an AR application developer or other entity). The application matches the tags of the AR application with the tags of the object. The application presents an indication of the AR application with a matching tag on the display of the AR wearable device.

[0024] Example indications include the name of the object, an icon, modifications to the object by the system, etc. The user of the AR wearable device can select one of the indications of the AR application to enable the corresponding AR application. The user can select the indication in a variety of ways. For example, the object in the image can be a quick response (QR) code. The system identifies the QR code given a QR code label. The system finds the AR application with the QR code label and presents the indication of the AR application on the display of the wearable AR device close to the QR code. For example, the indication can be "QR code". The user can select "QR code" by moving his head so that the "QR code" is located in the selection rectangle 730 in the center of the display. The system enables an AR application that provides functions related to the QR code.

[0025] Networked computing environment

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

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

[0028] The messaging server system 108 provides server-side functionality to specific messaging clients 104 via the network 112. Although specific functionality of the messaging system 100 is described herein as being performed by the messaging client 104 or by the messaging server system 108, the location of specific functionality within the messaging client 104 or within the messaging server system 108 may be a design choice. For example, it may be technically preferred to initially deploy certain technologies and functionality within the messaging server system 108, but later migrate the technologies and functionality to the messaging client 104 where the client device 102 has sufficient processing power.

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

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

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

[0032] The application server 114 hosts multiple server applications and subsystems, including, for example, a messaging server 118, an image processing server 122, and an input modality server 124. The messaging server 118 implements multiple message processing techniques and functions, particularly those related to the aggregation and other processing of content (e.g., text and multimedia content) included in messages received from multiple instances of the messaging client 104. As will be described in more detail, text and media content from multiple sources can be aggregated into collections of content (e.g., referred to as stories or galleries). These collections are then made available to the messaging client 104. In view of the hardware requirements for other processor- and memory-intensive data processing, such processing can also be performed on the server side by the messaging server 118.

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

[0034] The input modality server 124 supports input modalities for AR wearable devices. The input modality server 124 receives requests from the AR wearable device and responds to the requests. The request includes sensor data, such as an image sent to the input modality server 124 for processing. The input modality server 124 processes the sensor data and identifies objects within the sensor data, and returns the name of the object within the sensor data and the location of the object to the AR wearable device. Another request from the AR wearable device is a request for an AR application associated with a tag such as a "QR code" that can be run on the AR wearable device. The input modality server 124 can load an AR application to the AR wearable device, which may be used by the user of the AR wearable device, or can respond to the AR application based on criteria given from the AR wearable device to the input modality server 124. The criteria can be a limit on the number of AR applications, a user's preference such as an AR application linked back to the messaging system 100, and the like.

[0035] Returning to the messaging client 104, the features and functions of the external resource (e.g., application 106 or applet) are available to the user via the interface of the messaging client 104. In this context, "external" refers to the fact that the application 106 or applet is outside the messaging client 104. External resources are usually provided by a third party, but can also be provided by the creator or provider of the messaging client 104. The messaging client 104 receives a user selection of an option for launching or accessing the features of such an external resource. The external resource can be an application 106 (e.g., a "local application") installed on the client device 102, or a small-scale version of the application (e.g., a "applet") hosted on the client device 102 or away from the client device 102 (e.g., on a third-party server 110). The small-scale version of the application includes a subset of the features and functions of the application (e.g., the full-scale, local version of the application) and is implemented using a markup language document. In one example, the small-scale version of the application (e.g., a "applet") is a web-based markup language version of the application and is embedded in the messaging client 104. In addition to using markup language documents (eg, .*ml files), applets may include scripting languages ​​(eg, .*js files or .json files) and style sheets (eg, .*ss files).

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

[0037] In response to determining that the external resource is a locally installed application 106, the messaging client 104 instructs the client device 102 to launch the external resource by executing the locally stored code corresponding to the external resource. In response to determining that the external resource is a web-based resource, the messaging client 104 communicates with (for example) a third-party server 110 to obtain a markup language document corresponding to the selected external resource. The messaging client 104 then processes the obtained markup language document to present the web-based external resource within the user interface of the messaging client 104.

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

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

[0040] System Architecture

[0041] Figure 2 1 is a block diagram showing additional details about the messaging system 100 according to some examples. Specifically, the messaging system 100 is shown as including a messaging client 104 and an application server 114. The messaging system 100 contains a number of subsystems that are supported on the client side by the messaging client 104 and on the server side by the application server 114. These subsystems include, for example, a transient timer system 202, a collection management system 204, an enhancement system 208, a map system 210, a game system 212, an external resource system 214, and an input modality system 216.

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

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

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

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

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

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

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

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

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

[0051] To integrate the functionality of the SDK into a web-based resource, the SDK is downloaded by the third-party server 110 from the messaging server 118, or received by the third-party server 110 in other ways. Once the SDK is downloaded or received, the SDK is included as part of the application code of the web-based external resource. The code of the web-based resource can then call or enable certain functions of the SDK to integrate the features of the messaging client 104 into the web-based resource.

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

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

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

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

[0056] The input modality system 216 supports input modalities for the AR wearable device. The input modality system 216 receives requests from the AR wearable device and responds to the requests. The request includes sensor data, such as an image sent to the input modality system 216 for processing. The input modality system 216 processes the sensor data and identifies objects within the sensor data, and returns the name of the object and the location of the object within the sensor data to the AR wearable device. Another request from the AR wearable device is a request for an AR application associated with a tag that can be run on the AR wearable device. The input modality system 216 can load an AR application to the AR wearable device, which may be used by a user of the AR wearable device, or can respond to the AR application based on criteria given from the AR wearable device to the input modality system 216.

[0057] Data Architecture

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

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

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

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

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

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

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

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

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

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

[0068] As described above, augmented data includes augmented reality content items, overlays, image transformations, AR images, and similar items involving modifications that can be applied to image data (e.g., videos or images). This includes real-time modifications that modify images when they are captured using a device sensor (e.g., one or more cameras) of the client device 102 and then display the modified images on the screen of the client device 102. This also includes modifications to stored content (e.g., video clips in a library that can be modified). For example, in a client device 102 that accesses multiple augmented reality content items, a user can use a single video clip with multiple augmented reality content items to see how different augmented reality content items will modify the stored clips. For example, by selecting different augmented reality content items for the content, multiple augmented reality content items that apply different pseudo-random movement models can be applied to the same content. Similarly, real-time video capture can be used with the modifications shown to show how the video image currently being captured by the sensor of the client device 102 will modify the captured data. Such data can be displayed only on the screen without being stored in the memory, or the content captured by the device sensor can be recorded and stored in the memory with or without modification (or both). In some systems, the preview function can show how different augmented reality content items will be displayed in different windows of the display at the same time. For example, this can enable viewing multiple windows with different pseudo-random animations on the display at the same time.

[0069] Thus, data and various systems using augmented reality content items or other such transformation systems that use the data to modify content may involve detection of objects (e.g., faces, hands, bodies, cats, dogs, surfaces, objects, etc.) in video frames; tracking of such objects as they leave, enter, and move around the field of view; and modification or transformation of such objects as they are tracked. In various examples, different methods for implementing such transformations may be used. Some examples may involve generating a three-dimensional mesh model of one or more objects, and implementing the transformation using transformations and animated textures of the models within the video. 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 yet another example, neural network analysis of a video frame may be used to place an image, model, or texture in content (e.g., an image or video frame). Thus, an augmented reality content item refers to both images, models, and textures used to create transformations in the content, and additional modeling and analysis information required to implement such transformations using object detection, tracking, and placement.

[0070] Real-time video processing can be performed with 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 can load video files and store them in the memory of the device, or a sensor of the device can be used to generate a video stream. In addition, any object, such as human faces and parts of the human body, animals, or non-living things (e.g., chairs, cars, or other objects) can be processed using computer animation models.

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

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

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

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

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

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

[0077] In some examples, a computer animation model for transforming image data can be used by a system in which a user can capture an image or video stream of the user (e.g., a selfie) using a client device 102 having a neural network that operates as part of a messaging client 104 operating on the client device 102. A transformation system operating within the messaging client 104 determines the presence of a face within the image or video stream and provides a modification icon associated with the computer animation model to transform the data image, or the computer animation model can be presented as associated with an interface described herein. The modification icon includes the following changes, which can be the basis for modifying the user's face in the image or video stream as part of the modification operation. Once the modification icon is selected, the transformation system initiates the process of transforming the user's image to reflect the selected modification icon (e.g., generating a smiley face on the user). Once the image or video stream is captured and the specified modification is selected, the modified image or video stream can be presented in a graphical user interface displayed on the client device 102. The transformation system can implement a complex convolutional neural network on a portion of the image or video stream to generate and apply the selected modification. That is, a user can capture an image or video stream, and once a modification icon is selected, the modified result can be presented in real time or near real time. In addition, while the video stream is being captured, the modification can be persistent and the selected modification icon remains toggled. A machine learning neural network can be used to implement such modification.

[0078] The graphical user interface presenting the modifications performed by the transformation system can provide additional interactive options to the user. Such options can be based on the interface for initiating content capture and selecting a specific computer animation model (e.g., initiated from a content creator user interface). In various examples, the modification can be persistent after the initial selection of the modification icon. The user can switch to turn on or off the modification by tapping or otherwise selecting the face being 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 can globally switch on or off the modification by tapping or selecting a single face modified and displayed in the graphical user interface. In some examples, each face in a group of multiple faces can be modified individually, or such modifications can be switched individually by tapping or selecting an individual face or a series of individual faces displayed in the graphical user interface.

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

[0080] A collection may also constitute a "live story" that is a collection of content from multiple users, which is created manually, automatically, or using a combination of manual and automatic techniques. For example, a "live story" may constitute a curated stream of user-submitted content from various locations and events. Users whose client devices have location services enabled and who are at a co-located event at a particular time may be presented with an option, for example via a user interface of the messaging client 104, to contribute content to a particular live story. Live stories may be identified to a user by the messaging client 104 based on his or her location. The end result is a "live story" told from a community perspective.

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

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

[0083] Data communication architecture

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0098] Time-based access restriction architecture

[0099] Figure 5 is a schematic diagram illustrating an access restriction process 500, according to which access to content (e.g., ephemeral message 502 and associated multimedia data payload) or a collection of content (e.g., ephemeral message group 504) can be time-restricted (e.g., made ephemeral).

[0100] The ephemeral message 502 is shown to be associated with a message duration parameter 506, the value of which determines the amount of time that the messaging client 104 will display the ephemeral message 502 to the receiving user of the ephemeral message 502. In one example, the receiving user can view the ephemeral message 502 for up to 10 seconds, depending on the amount of time specified by the sending user using the message duration parameter 506.

[0101] The message duration parameter 506 and the message recipient identifier 424 are shown as inputs to a message timer 510, which is responsible for determining the amount of time that the transient message 502 is shown to a particular receiving user identified by the message recipient identifier 424. In particular, the transient message 502 is shown to the associated receiving user only for a period of time determined by the value of the message duration parameter 506. The message timer 510 is shown as providing an output to a more general transient timer system 202, which is responsible for the overall timing of displaying content (e.g., the transient message 502) to the receiving user.

[0102] exist Figure 51. Ephemeral message 502 is shown as being included within an ephemeral message group 504 (e.g., a collection of messages in a personal story or event story). Ephemeral message group 504 has an associated group duration parameter 508, the value of which determines the duration for which ephemeral message group 504 is presented and accessible to users of messaging system 100. For example, group duration parameter 508 may be the duration of a concert, wherein ephemeral message group 504 is a collection of content about the concert. Alternatively, a user (an owning user or a curator user) may specify the value of group duration parameter 508 when performing setup and creation of ephemeral message group 504.

[0103] In addition, each ephemeral message 502 within the ephemeral message group 504 has an associated group participation parameter 512, the value of which determines the duration for which the ephemeral message 502 is accessible within the context of the ephemeral message group 504. Thus, a particular ephemeral message group 504 may "expire" and become inaccessible within the context of the ephemeral message group 504 before the ephemeral message group 504 itself expires according to the group duration parameter 508. The group duration parameter 508, the group participation parameter 512, and the message recipient identifier 424 each provide inputs to a group timer 514, which is operable to first determine whether a particular ephemeral message 502 of the ephemeral message group 504 is to be displayed to a particular receiving user, and if so, how long to display it. Note that the identity of the particular receiving user is also known to the ephemeral message group 504 due to the message recipient identifier 424.

[0104] Thus, the group timer 514 operatively controls the total lifespan of the associated ephemeral message group 504 and the individual ephemeral messages 502 included in the ephemeral message group 504. In one example, each ephemeral message 502 within the ephemeral message group 504 remains viewable and accessible for a period of time specified by the group duration parameter 508. In another example, within the context of the ephemeral message group 504, a particular ephemeral message 502 may expire based on the group participation parameter 512. Note that even within the context of the ephemeral message group 504, the message duration parameter 506 may still determine the duration for which a particular ephemeral message 502 is displayed to a receiving user. Thus, the message duration parameter 506 determines the duration for which a particular ephemeral message 502 is displayed to a receiving user, regardless of whether the receiving user is viewing the ephemeral message 502 within or outside the context of the ephemeral message group 504.

[0105] The transient timer system 202 may also be operable to remove a particular transient message 502 from a transient message group 504 based on a determination that an associated group participation parameter 512 has been exceeded. For example, where a sending user has established a group participation parameter 512 of 24 hours from posting, the transient timer system 202 will remove the associated transient message 502 from the transient message group 504 after the designated 24 hours. The transient timer system 202 is also operable to remove a transient message group 504 when the group participation parameter 512 for each transient message 502 within the transient message group 504 has expired, or when the transient message group 504 itself has expired according to the group duration parameter 508.

[0106] In some use cases, the creator of a particular ephemeral message group 504 may specify an indefinite group duration parameter 508. In this case, the expiration of the group participation parameter 512 for the last remaining ephemeral message 502 within the ephemeral message group 504 will determine when the ephemeral message group 504 itself expires. In this case, a new ephemeral message 502 with a new group participation parameter 512 added to the ephemeral message group 504 effectively extends the life of the ephemeral message group 504 to a value equal to the group participation parameter 512.

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

[0108] Input modalities for AR wearables

[0109] Figure 6 A system 600 for providing input modalities for an AR wearable device according to some examples is shown. The system 600 includes an AR wearable device such as glasses 1000 in Figure 1000, and may include other devices, such as a portion of a messaging server system 108 that may perform one or more of the operations described herein.

[0110] Input / output (IO) devices 604 include devices that enable user 646 to receive output or send input to system 600. IO devices 604 include display 606, speakers, microphones, buttons, touchpads, gyroscopes, etc. Some devices, such as gyroscopes, can be both sensors 608 and IO devices 604 because by moving system 600, user 646 can pass input to system 600. However, user 646 can move system 600 without intending to pass input to system 600. Sensors 608 include gyroscopes, light sensors, image sensors or cameras, positioning sensors, clocks, etc. According to some examples, sensors 608 include wireless communications. Wireless communications such as LE Bluetooth can be used to determine the location and / or orientation of system 600, so wireless communications can also be considered sensors 608. Scan state 623 is stored in the memory of system 600 and indicates whether system 600 is in a visual scan mode, in which system 600 scans sensor data 611, such as image 610, to detect object 618 and provides user 646 with an opportunity to enable application (APP) 642 associated with object 618. Visual scan mode is energy intensive and can drain a battery (not shown) of system 600. Therefore, it is desirable to reduce the amount of time that system 600 is in visual scan mode.

[0111] Context data 612 includes data associated with system 600 and user 646, such as a profile of a user of messaging system 100 or other users. In some examples, context data 612 includes information available on the Internet. Context data 612 includes information available from body wearable electronic device 602. Sensor data 611 includes location 615 data, time 617 data, voice 613 data, and image 610 data. Sensor data 611 is generated from sensor 608 and IO device 604. Display 606 is an electronic device for visually presenting data (e.g., visually presenting application 642 activity to user 646). According to some examples, display 606 is Fig. 9 Optical element 943 and optical element 944.

[0112] In some examples, user 646 is a user of messaging system 100. User 646 data structure has information associated with user 646, such as location 650. The user can input data using voice 648, tactile 652 means, gesture 654 (i.e., user 646 performs some movement or sound that can be interpreted as gesture 654), or other means.

[0113] Machine learning (ML) module 614 receives sensor data 611 and processes sensor data 611 to generate objects 618 with locations 620, persistence 622, and labels 624. For example, in combination Figure 6 Let's discuss Figure 7 . Figure 7 Display 606 of system 600 is shown. For example, a user may walk into a newly located pet store 709 and encounter his friend John 702. ML module 614 identifies object 618, friend John 702, QR code 710, and bird 712. ML module 614 uses sensor data 611 to determine that this is a newly located pet store 709 and generates object 618 representing the newly located pet store 709. According to some examples, tag 632, tag 624, and tag 645 are metadata associated with scan manager 626, object 624, and application 642, respectively.

[0114] ML module 614 uses ML object identifier 616 to identify objects within sensor data 6122. ML object identifier 616 includes information necessary to identify objects within sensor data 611 and indicates a tag 624 associated with object 618. In some examples, ML object identifier 616 is a trained neural network that recognizes one or more objects within an image. In some examples, system 600 sends sensor data 611 to a host computer to find object 618 within the sensor data.

[0115] ML module 614 determines location 620 of object 618 within image 610, tag 624 associated with object 618, and persistence 622 associated with object 618. Tag 624 indicates a name, description, or action associated with object 618. Tag 624 is used to associate application 642 with object 618 so that user 646 can select object 618 or tag 624 and activate application 642. Tag 624 can also be used to display an indication of application 642 on display 606, such as "Friend John". The friend portion indicates that John is a friend within messaging system 100. In some embodiments, system 600 does not perform identification of people other than friends of the user. In some embodiments, system 600 does not perform identification of anyone. Persistence 622 data indicates persistence of object 618 within sensor data 611. For example, persistence 622 can indicate that object 618 has been present for a certain number of seconds or a certain number of captured images. In some implementations, scan manager 626 will ignore object 618 unless it has a persistence 622 indicating that object 618 did not appear in image 610 during a rapid turn of the user's head. For example, a persistence 622 value of 0.2 seconds may indicate that the user is likely stable in their head orientation.

[0116] The scan manager 626 module scans applications 642 and objects 618 to find matches of tags 624 of objects 618 with tags 645 of applications 642. The application filter 630 module selects which applications 642 are to be presented to the user. The application filter 630 module uses historical usage data (e.g., frequency of use) of the user (or other users) available from the contextual data 612 to select which applications 642 are to be presented to the user. The application filter 630 module limits the number of applications 642 presented to the user 646 to a manageable number, e.g., from 1 to 20. The privacy 628 module filters any application 642 that is determined to be unsafe for the user 646 to run, or for which running the application 642 for the user would require passing information about the user 646 or the system 600, which would violate the security settings of the user 646 or the system 600. For example, user 646 data may indicate a setting to not pass location information to application 642, so if application 642 requires location information, the privacy 628 module filters application 642 and prevents it from being presented to user 646 as an option.

[0117] Application 642 may include ML object identifier 644, which is information that identifies the object by ML module 614 and is associated with a tag 645, which will be associated with the object if object 618 is identified in sensor data 611. A third party, such as a pet store owner, can register application 642 with system 600. Application filter 630 determines whether to consider registered application 642. When system 600 is started or turned on, scan manager 626 optionally communicates with a host device, such as client device 102, to download or select application 642 to be included in the memory of system 600. The downloaded application 642 is then considered to be passed to UI module 634. Application 642 includes action 651, which is associated with a process performed by application 642 if action 651 is selected. According to some examples, action 651 is displayed as a superior option to user 646 before enabling application 642. For example, referring to Figure 7 , if "Friend John" 702 is selected by the user, a menu will appear with actions 651 available for "Friend John" 702, such as "Message", "Remind me of his name", etc. In some embodiments, one or more of the actions 651 are displayed before any selection by the user. For example, for "Friend John" 702, the action 651 "Date" 704 is displayed, which indicates that there is an appointment with John, and the selection of "Date" 704 will tell the user when the appointment is. In some embodiments, if there is only one appointment, the date and time will be displayed near "Friend John" 702.

[0118] Scan manager 626 sends an indication of application 642 selected by scan manager 626 for UI module 634 to present to user 646. UI module 634 presents application 642 to user 646. For example, referring to Figure 7 , "Friend John" 702, "Date" 704, graphic bullet 706, "QR code" 720, "Bird" 712, graphic bullet 708, "Newly located pet store" 709, and "1" 728 are presented on display 604 to provide an AR experience for user 646. Each of "Friend John" 702, "Date" 704, "Bird" 712, "QR code" 710, and "Newly located pet store" 709 is associated with application 642. Application 642 includes display logo 647, for convenience, in addition to combining Figure 8 and Fig. 9 The logo 647 is the same as the label 645 in this example, except for the label 645 "bird" in question. The application 642 includes a gesture 649, which, when present, is used by the gesture detector 641 to detect when the application 642 is selected. In some examples, the gesture detector 641 uses the gesture 649 information associated with the application 642. The gesture 649 can be used to limit which gestures 649 the user 646 can use to select the application 642.

[0119] In some examples, in order to protect privacy, the privacy 628 module does not allow applications 642 that recognize people. The application 642 associated with "Friend John" 702 is an application 642 for a camera to take pictures of people associated with "Friend John" 702. The application 642 associated with "Appointment" 704 is an application 642 for viewing appointments scheduled with "Friend John" 702. The application 642 associated with "Bird" 712 is an application 642 that provides information about the bird, such as the name of the bird. The application 642 associated with "QR code" 710 is an application 642 that reads a QR code. The application 642 associated with "Newly located pet store" 709 is an application 642 provided by a pet store, which provides information about the pet store.

[0120] The application carousel 722 is an alternative way to select and display which applications 642 are available. By selecting the icons displayed in the application carousel 722, the applications 642 associated with the QR code 714, "Friend John" 716, the pet store 720, the bird 724, and the appointment 726 are available. The application carousel 722 is presented by the UI module 634. As shown, the user's finger 718 is hovering over the bird 724 icon. The application carousel 722 is part of the AR, and the finger 718 is the user's actual finger 718, where the user sees light reflected from his finger 718.

[0121] The user input module 638 determines the input of the user 646 from the sensor data 611. For example, the user can provide input using his voice 648, moving his position 650 such as moving his head, using tactile 652 means such as touching a button or a touchpad with his finger, using gestures 654 such as waving a finger, etc. The finger 718 can be another appendage or object controlled by the user such as a pencil. The user input module 638 determines which sensor data 611 are inputs from the user 646 from all the sensor data 611. In some examples, the user input module 638 monitors the sensor data 611 for new sensor data 611 and evaluates or determines whether the new sensor data 611 should be considered as input from the user 646. The user intent module 636 determines the user's intent. For example, the user 646 input can have multiple interpretations, and the user intent 636 determines the user's 646 intent.

[0122] In one example, referring to Figure 7 , the user 646 moves his head so that the bird 712 becomes located in the center of the display. The user input module 638 determines that the movement of the head to place one of the labels 645 of the application 642 in the center of the display 606 is an input. The UI module 634 receives multiple sensor data 611, such as an image 610, which is used by the user intent module 636 to determine the user intent 636. The user intent module 636 determines that the user 646's intention is to enable the application 642 for the bird 712 by moving the label 645 to the center of the display 606. The application selector 640 indicates the user intent 636 of the user 646 to the scan manager 626. The scan manager 626 enables the application 642 for the bird 712, which can provide actions 651 available to the user 646. The scan manager 626 determines which data, such as the image 610, the context data 612, etc., to be passed to the application 642. The application 642 for the bird 712 describes the types of birds in the pet store and the prices of the birds. UI module 634 considers not only a single instance of new sensor data 611, but also a series of sensor data 611 over time. In the above example, UI module 634 receives multiple versions of object 618 with location 620 as bird 712 becomes closer and closer to the center of display 606. Bird 712 then remains in the center for a threshold period of time, which is interpreted by user intent 636 module as meaning selection of bird 712.

[0123] In some examples, the text "bird" 712 changes as it becomes closer to the user intent 636 selected as user 646. For example, as "bird" 712 gets closer to the center of display 606, "bird" is bolded. In some examples, selection rectangle 730 is presented as part of AR, and then user 646 moves label 645 into selection rectangle 730 for a threshold period of time to select label 645, such as bird 712. In some examples, selection rectangle 730 appears when user intent 636 module determines that user 646 is in the process of selecting label 645 or attempting to select label 645. In some examples, selection rectangle 730 may indicate secondary gesture 654 of selecting label 645 performed by user 646. For example, if label 645 is in selection rectangle 730, "select" is displayed on display 606, where the user is instructed to move his head up and down to select label 645. Selection rectangle 730 may be another shape, such as a polygon, a circle, a triangle, an irregular shape, etc. In some examples, selection rectangle 730 is referred to as a selection shape.

[0124] In some examples, user 646 indicates selection of label 645 by reading label 645 using his voice 648. For example, "1" can be selected by saying "1". In some examples, user 646 indicates selection of label 645 by placing his finger 718 near label 645. In some examples, UI module 634 presents bullet 706 or another icon to indicate that object 618 or action 651 does not have a tangible example. In some implementations, UI module 634 presents an indication of AR application 642 adjacent to or near object 618. For example, the indication of AR application 642 for appointment 704 is bullet 706, not "Friend John" 702. "Newly located pet store" 709 is an object 618 identified by ML module 614 based on location 615, which can be from a GPS system, information from a host device, a QR code, an object identification in image 610, or other sources. "Newly located pet store" 709 is seen as an object 618 with a label 624 of "Newly located pet store". An object 618, such as a pet store, may be identified based on the location of the body wearable electronic device 602. The system 600 may query a host device, such as the client device 102, for an application 642 associated with the object 618 "Newly located pet store." The bullet point 708 serves as the location of the object 618 "Newly located pet store" for purposes of selecting the object 618 by the user 646. "Scan off" 728 enables the user 646 to turn off or on the scanning state 623. In some examples, an indication of the application 642 is presented by changing the object 618 rather than presenting the label 645. For example, instead of presenting "bird" 712, the bird itself is changed to indicate that the bird can be selected. For example, the bird may be highlighted, flashed, or otherwise changed. As Fig.10 As shown in , the scanning state 623 can be turned on and off in various ways, such as using a button or a touch pad. In some embodiments, when the scanning manager 626 enables the application 642, the scanning state 623 is turned off. The term "rendering" is used to display data on the display 606; however, those skilled in the art will recognize that other terms such as "rendering", "outputting", etc. can also be used or applicable.

[0125] Figure 8 and Fig. 9 are described in conjunction with each other. Figure 8 A method 800 of input modality for an AR wearable device is shown according to some examples. Fig. 9 800 is a continuation of method 800 for input modalities for an AR wearable device according to some examples. Method 800 is performed by an AR wearable device such as Fig.10 The method 800 begins at operation 802, where the correct button is pressed. For example, the user 646 can use the IO device 604, such as Fig.10 The method 800 continues at operation 804, where a scan intent is sent. For example, the IO device 604 sends a scan intent to the running or executing Figure 6 The method 800 continues at operation 806 where the interpreter receives the intent. The interpreter module receives a signal to start scanning. The interpreter module sets the scanning state 623 to indicate that the scanning state has been entered.

[0126] The method 800 continues at operation 808, where the scanner is started. For example, the interpreter module causes the body wearable electronic device 602 to collect data, such as an image 610, or in some examples, to collect a single image 610, which can be part of a power saving state. The method 800 continues at operation 810, where a timeout is started 810. For example, the interpreter module waits for the body wearable electronic device 602 to provide sensor data 611. The method 800 continues at operation 816, where a timeout occurs. For example, if there is difficulty collecting data using the body wearable electronic device 602, a timeout may occur. The interpreter module or system 600 can return to a state associated with operation 802, or can attempt to collect sensor data 611 again.

[0127] The method 800 continues at operation 808, where a scanner is started. For example, the scanner is an image capture device that captures the image 610. The method 800 continues at operation 812, where context information is collected. For example, context data 612 and other sensor data 611 are collected. The method 800 continues at operation 814, where a request is submitted to a back end 834. For example, the IO device 604 includes a wireless connection to a host, such as the client device 102. The sensor data 611 and the context data 612 are submitted to the back end 834.

[0128] The method 800 continues at operation 818 to determine if there are parameters for analysis? These parameters indicate different ways to analyze the sensor data 611 and the context data 612. For example, as shown, "yes" indicates that the sensor data 611 and the context data 612 should be analyzed using the perception 832 server, while "no" indicates that the sensor data 611 and the context data 612 should be analyzed using the local ML module 614. According to some examples, the perception 832 server is the input modality server 124 of the input modality system 216.

[0129] The method 800 continues at operation 820, where the request is received, indicating that the backend has received the request. The method 800 continues at operation 822, where it is forwarded to the service provider. For example, the service provider can be a sense 832 server, which is indicated at operation sense 832. The method 800 continues at operation 824, where a list of sorted tags 837 is constructed. For example, the backend 834 constructs a set of objects 618 including the sorted tags 624.

[0130] Forwarding to the service provider 822 may include operations 828 and 830, where a timeout may occur while sending the sensor data 611 and context data 612 to the service provider. The default is to build an ordered list of tags using the available information.

[0131] The method 800 continues at operation 826, where the result 826 is returned. For example, the backend 834 sends the result to the system 600 via a wireless connection. The method 800 continues at operation 836, where a response is received. For example, the system 600 receives the sorted tags 837. The method 800 continues at operation 838, where the scan manager performs operations. For example, the operations of the scan manager 838 are performed at Fig. 9 As shown in Figure 6 and Figure 7 8, wherein scan manager 838 is an example of scan manager 626. In some examples, method 800 continues with carousel appearing 840. For example, application carousel 722 may appear instead of tab 645, or the application carousel may appear with the tab, such as Figure 7 . The method 800 continues with the scanner stopping 842. For example, the scanner may time out, stop after an application is run, or stop when a user 646 determines to stop the scanner. The scanning state 623 is changed to indicate that scanning is no longer being performed.

[0132] The method 800 continues at operation 838, where the operation of the scan manager 924 is performed. The method 800 at operation 902 Figure 8 Continue to Fig. 9 The sorted tags 837 are passed to the scan manager 924. In some examples, the scan manager 924 is the same as or similar to the scan manager 626.

[0133] The method 800 continues at operation 904, where the sorted tags 837 are received. For example, the scan manager 924 receives the object 618, which may be from both the backend 834 and from the ML module 614. According to some examples, the sorted tags 837 are examples of the object 618. The method 800 continues at operation 906, where tags having confidence values ​​less than a minimum threshold are filtered. The tags 624 are associated with confidence values ​​(not shown). The confidence values ​​indicate the confidence that the tag 624 is related to the object 618 or that the tag 624 will be of interest to the user 646. The scan manager 924 removes tags 624 having associated confidence values ​​below the confidence threshold. The method 800 continues at operation 908, where it is determined which registered AR applications match at least one tag 624. For example, the scan manager 626 looks for an application 642 that includes a tag 645 that matches the tag 624.

[0134] Method 800 continues at operation 910 where it is determined whether one or more AR applications match the tag. For example, if there is no application 642 with a tag 645 that matches tag 624, method 800 returns to Figure 8 , the scanner stops 842 at operation 842. If there is an AR application with a tag 645 that matches the tag 624, the method 800 continues at operation 912, where it is determined whether a single AR application matches the tag. If only a single AR application's tag 645 matches the tag 624, the method 800 continues at operation 912, where the AR application is launched. For example, the scan manager 626 launches the application 642 and passes the context data 612 and the sensor data 611 to the application 642 based on the privacy 628 setting.

[0135] If there is more than one application with a tag 645 that matches the tag 624, the method 800 continues at operation 916 where all AR applications are presented. For example, the scan manager 626 causes the UI module 634 to display three different applications 642 for Figure 7 642 is displayed with a label "bird" for the object 618 being a bird. For example, the following are three different applications 642 and how they would be displayed by the UI module 634. A first application 642 associated with the label 645 "bird" and having a display badge 647 for "bird" is displayed at the top. A second application 642 associated with the label "bird" and having a display badge 647 for the application 642 for "exotic bird information" 713 is displayed. A third application 642 associated with the label "bird" and having a display badge 647 for the application 642 for "pet store birds" 715 is displayed. All three applications 642 enable different functions or programs.

[0136] Method 800 continues at operation 918, where the user selects an AR application. For example, UI module 634 may determine that user 646 selected application 642. Method 800 then continues at operation 914, where the AR application is launched. For example, scan manager 626 launches application 642 and determines what to pass to application 642 based on privacy 628 module. For example, privacy 628 module may determine not to pass location 615 or position of user 646 based on privacy settings. Method 800 continues at operation 920, where the user discards one or more AR applications presented. For example, user 646 determines not to select application 642. Method 800 continues at operation 922, where it returns to Figure 8 To operation 842, where the scanner is stopped, where the system 600 closes the scanning state 623.

[0137] Fig.10 An example of a wearable electronic device in the form of glasses 1000 according to some examples is shown. The wearable electronic device is in the form of glasses 1000. Glasses 1000 are eyewear articles composed of electronic products that operate within a network system for transmitting image and video content. Fig.10A front perspective view of glasses 1000 is shown. In some examples, the wearable electronic device is referred to as AR glasses. Glasses 1000 may include a frame 1032 made of any suitable material, such as plastic or metal, including any suitable shape memory alloy. Frame 1032 may have a front piece 1033, which may include a first lens or left lens, a display or optical element holder 1036 and a second lens or right lens, a display or optical element holder 1037 connected by a bridge 1038. Front piece 1033 further includes a left end portion 1041 and a right end portion 1042. A first optical element or left optical element 1044 and a second optical element or right optical element 1043 may be disposed in respective left optical element holders 1036 and right optical element holders 1037. Each of optical elements 1043, 1044 may be a lens, a display assembly, or a combination of the foregoing. Optical element 1043, 1044 may be one optical element. In some examples, for example, glasses 1000 are provided with an integrated near-eye display mechanism that enables, for example, preview images of visual media captured by camera 1069 of glasses 1000 to be displayed to the user.

[0138] The frame 1032 further includes a left arm or temple piece 1046 and a right arm or temple piece 1047, which are coupled to the respective left end 1041 and right end 1042 of the front piece 1033 by any suitable means such as a hinge (not shown) to be coupled to the front piece 1033 or rigidly or fixably fixed to the front piece 1033, thereby being integral with the front piece 1033. Each of the temple piece 1046 and the temple piece 1047 may include: a first portion 1051 coupled to the respective end 1041 or 1042 of the front piece 1033; and any suitable second portion 1052 for coupling to the ear of the user, such as a curved or arched piece. In one example, the front piece 1033 can be formed of a single piece of material to have a unitary or integrated construction. In one example, the entire frame 1032 can be formed of a single piece of material to have a unitary or integrated construction.

[0139] Eyeglasses 1000 include a computing device such as computer 1061, which may be of any suitable type to be carried by frame 1032 and, in one example, of a suitable size and shape to be at least partially disposed within one or more of temple pieces 1046, 1047. In one example, computer 1061 has a size and shape similar to the size and shape of one of temple pieces 1046, 1047 and is thus disposed nearly completely, if not completely, within the structure and confines of such temple pieces 1046, 1047.

[0140] In one example, the computer 1061 can be arranged in both the temple piece 1046 and the temple piece 1047. The computer 1061 may include one or more processors with memory, wireless communication circuitry, and a power supply. The computer 1061 includes a low power circuitry, a high speed circuitry, a position circuitry, and a display processor. Various other examples may include these elements in different configurations or these elements integrated together in different ways. Additional details about aspects of the computer 1061 may be implemented with reference to the following description.

[0141] The computer 1061 further includes a battery 1062 or other suitable portable power source. In one example, the battery 1062 is disposed in one of the temple pieces 1046 or the temple pieces 1047. Fig.10 In the illustrated eyewear 1000, the battery 1062 is shown as being disposed in the left temple piece 1046 and electrically coupled to the remainder of the computer 1061 disposed in the right temple piece 1047 using a connector 1074. The one or more input and output devices may include a connector or port (not shown) accessible from the exterior of the frame 1032 suitable for charging the battery 1062, a wireless receiver, transmitter or transceiver (not shown), or a combination of such devices.

[0142] Computer 1061 further includes a gyroscope 1080 or other suitable motion detector. In one example, gyroscope 1080 is disposed in one of temple piece 1046 or temple piece 1047. Fig.10 In the glasses 1000 shown in FIG. 1 , the gyroscope 1080 is shown as being disposed in the right temple piece 1047 and electrically coupled to the rest of the computer 1061 using a connector.

[0143] The glasses 1000 include a digital camera 1069. Although two cameras 1069 are depicted, other examples contemplate the use of a single or additional (i.e., more than two) cameras 1069. For ease of description, various features related to the camera 1069 will be further described with reference to only a single camera 1069, but it should be understood that these features may apply to multiple cameras 1069 in appropriate examples.

[0144] In various examples, the glasses 1000 may include any number of input sensors or peripherals in addition to the camera 1069. The front piece 1033 is provided with an outward-facing, front-facing, front or outer surface 1066 that faces forward or away from the user when the glasses 1000 are mounted on the user's face, and an opposite inward-facing, rearward-facing, rear or inner surface 1067 that faces the user's face when the glasses 1000 are mounted on the user's face. Such sensors may include an inward-facing video sensor or digital imaging module, such as may be mounted or disposed on or within an inner surface 1067 of the front piece 1033 or elsewhere on the frame 1032 to face the camera 1069 of the user, and an outward-facing video sensor or digital imaging module, such as may be mounted or disposed on or within an outer surface 1066 of the front piece 1033 or elsewhere on the frame 1032 to face away from the camera 1069 of the user. Such sensors, peripherals or peripherals may additionally include biometric sensors, position sensors, accelerometers, or any other such sensors. In some examples, a projector (not shown) is used to project images onto the inner surfaces of optical elements 1043, 1044 (or lenses) to provide a mixed reality or augmented reality experience for a user of glasses 1000.

[0145] Eyewear 1000 also includes an example of a camera control mechanism or user input mechanism, which includes a camera control button mounted on frame 1032 for tactile or manual engagement by the user. The camera control button provides a dual-mode or single-action mechanism because it can be set by the user between only two states, an engaged state and an idle state. In this example, the camera control button is a button that is in a disengaged state by default, which can be pressed by the user to set it to an engaged state. When the camera control button is released from being pressed, it automatically returns to the disengaged state.

[0146] In other examples, the single action input mechanism may instead be provided by, for example, a touch sensitive button including a capacitive sensor mounted on the frame 1032 adjacent to a surface thereof for detecting the presence of a user's finger to set the touch sensitive button to an engaged state when the user touches the finger to a corresponding point on the outer surface 1066 of the frame 1032. It should be understood that the camera control button and the capacitive touch button described above are merely two examples of tactile input mechanisms for single action control of the camera 1069, and other examples may employ different single action tactile control arrangements.

[0147] The glasses also include an input button 1078, wherein the computer 1061 is configured to recognize a press of the button 1078 and can distinguish between a short press and a long press. The glasses also include a touch pad 1076, wherein the computer 1061 is configured to recognize a touch of the touch pad 1076 and can be configured to recognize different types of touches, such as a long stroke, a short stroke, a touch, etc.

[0148] The computer 1061 is configured to perform the methods described herein. In some examples, the computer 1061 is coupled to one or more antennas for receiving signals from a GNSS, a local area network, a 3GPP network, or other type of network, and circuitry for processing the signals, wherein the antennas and circuitry are housed in the glasses 1000. In some examples, the computer 1061 is coupled to one or more wireless antennas and circuitry for sending and receiving wireless signals, wherein the antennas and circuitry are housed in the glasses 1000. In some examples, multiple sets of antennas and circuitry are housed in the glasses 1000. In some examples, the antennas and circuitry are configured to receive signals based on, for example, Bluetooth. TM , Bluetooth Low Energy TM , IEEE 802, IEEE 802.11, and other communication protocols. In some examples, the PDR sensor is housed in the glasses 1000 and coupled to the computer 1061. In some examples, the glasses 1000 are VR headsets, wherein the optical elements 1043 and 1044 are opaque screens for displaying images to a user of the VR headset. According to some examples, the glasses 1000 include one or more microphones 1082.

[0149] Fig.11 A method 1100 for an input modality for an AR wearable device according to some examples is shown. The method 1100 begins at operation 1102, where image data of an image captured from an image capture device is received. For example, the sensor 608 includes an image capture device, such as a camera-type device. The scan manager 626 module or another module receives image data of an image 610 captured from the image capture device.

[0150] Method 1100 continues at operation 1104, where an object in the image is identified by processing the image data, the object being associated with a first label. For example, ML module 614 identifies one or more objects in image 610 by processing image 610. ML module 614 identifies object 618 using ML object identifier 616 and ML object identifier 644. ML object identifier 616 is a neural network trained to identify one or more objects 618 within image 610. Alternatively, as in combination with Figure 8 and Fig. 9As discussed, the image 610 may be sent to the backend 834 for processing.

[0151] The method 1100 continues at operation 1106, where an AR application from among the plurality of AR applications with a second tag matching the first tag is selected. For example, the scan manager 626 module can match the tag 632 associated with the object 618 with the tag 645 associated with the application 642. In addition, the scan manager 626 module filters or selects the applications 642 to a number that can be presented, such as 1 to 15, so that the number of options for the user 646 is manageable, thereby enabling easier selection of the application 642.

[0152] The method 1100 continues at operation 1108, where an indication of the AR application is presented on an AR display of an AR wearable device of the AR system. Figure 7 606. The indication may be a word such as "bird" 712, an icon, a label 645, a display logo 647, or other indication that the AR application 642 is available, which is associated with an object 618 visible to the user 646. In some examples, the object 618 may not be a physical object, but an event, such as GPS data indicating that the user 646 is in a new physical location, such as "new location pet store" 709. However, the pet store itself can be considered as an object 618.

[0153] The method 1100 continues at operation 1110, where a user input is identified as a selection of an AR application. For example, the UI module 634 identifies a user intent 636 that the user wants to enable an application 642 indicated on the display 606. An example of an indication is that the user 646 says a label such as "1" 728, or the user 646 can move his head so that an indication such as "bird" 712 is located within the selection rectangle 730. The method 1100 continues at operation 1112, where in response to the selection of the AR application, the AR application is enabled. For example, in response to the user 646 selecting the application 643, the scan manager 626 enables the application 642 according to the privacy 628 module. When the scan manager 626 enables the application 642, the scan manager 626 may include parameters or data, such as an indication of an object and an indication of the location of the object within the image. The scan manager 626 may include other data, such as one or more of the object 618, the sensor data 611, the context data 612, the scanned image, etc. In some embodiments, the object 642 accesses the data via a shared memory. For example, the object 618 associated with the indication of the selected AR application and the location of the object 618 may be located in a shared memory accessible to both the scan manager 626 and the application 642 .

[0154] The method 1100 may include one or more additional operations. The operations of the method 1100 may be performed in a different order. One or more of the operations of the method 1100 may be optional. The method 1100 may be performed by the client device 102, the system 600, the glasses 900, or another electronic device. A portion of the functionality may be performed on a server computer or host. For example, the glasses 900 may be coupled to a host client device 102 or an application server 114, where one or more of the operations are performed.

[0155] Machine Architecture

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

[0157] The machine 1200 may include a processor 1204, a memory 1206, and an input / output I / O component 1202, which may be configured to communicate with each other via a bus 1240. In an example, the processor 1204 (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 1208 that executes instructions 1210 and a processor 1212. The term "processor" is intended to include a multi-core processor, which may include two or more independent processors (sometimes referred to as "cores") that may execute instructions simultaneously. Although Fig.12 Multiple processors 1204 are shown, but the machine 1200 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.

[0158] The memory 1206 includes a main memory 1214, a static memory 1216, and a storage unit 1218, which are all accessible by the processor 1204 via a bus 1240. The main memory 1206, the static memory 1216, and the storage unit 1218 store instructions 1210 that implement any one or more of the methods or functions described herein. The instructions 1210 may also reside, completely or partially, within the main memory 1214, within the static memory 1216, within the machine-readable medium 1220 within the storage unit 1218, within at least one of the processors 1204 (e.g., within a cache memory of a processor), or within any suitable combination thereof during execution thereof by the machine 1200.

[0159] I / O components 1202 may include various components for receiving input, providing output, generating output, transmitting information, exchanging information, capturing measurements, etc. The specific I / O components 1202 included in a particular machine will depend on the type of machine. For example, a portable machine such as a mobile phone may include a touch input device or other such input mechanism, while a headless server machine will be less likely to include such a touch input device. It is to be understood that I / O components 1202 may include Fig.121202. In various examples, the I / O components 1202 may include a user output component 1226 and a user input component 1228. The user output component 1226 may include a visual component (e.g., a display such as a plasma display panel (PDP), a light emitting diode (LED) display, a liquid crystal display (LCD), a projector, or a cathode ray tube (CRT)), an acoustic component (e.g., a speaker), a tactile component (e.g., a vibration motor, a resistance mechanism), other signal generators, etc. The user input component 1228 may include an alphanumeric input component (e.g., a keyboard, a touch screen configured to receive alphanumeric input, an optical keyboard, or other alphanumeric input component), a pointing-based input component (e.g., a mouse, a touch pad, a trackball, a joystick, a motion sensor, or other pointing instrument), a tactile input component (e.g., a physical button, a touch screen or other tactile input component that provides location and force of a touch or touch gesture), an audio input component (e.g., a microphone), etc.

[0160] In another example, the I / O component 1202 may include: a biometric component 1230, a motion component 1232, an environment component 1234, or a position component 1236, as well as various other components. For example, the biometric component 1230 includes components for detecting expressions (e.g., hand expressions, facial expressions, voice expressions, body gestures, or eye tracking), measuring biosignals (e.g., blood pressure, heart rate, body temperature, sweating, or brain waves), identifying people (e.g., voice recognition, retinal recognition, facial recognition, fingerprint recognition, or EEG-based recognition), etc. The motion component 1232 includes an acceleration sensor component (e.g., an accelerometer), a gravity sensor component, and a rotation sensor component (e.g., a gyroscope).

[0161] Environmental components 1234 include, for example, one or more cameras (with still image / photo and video capabilities), lighting sensor components (e.g., a photometer), temperature sensor components (e.g., one or more thermometers that detect ambient temperature), humidity sensor components, pressure sensor components (e.g., a barometer), acoustic sensor components (e.g., one or more microphones that detect background noise), proximity sensor components (e.g., an infrared sensor that detects nearby objects), gas sensors (e.g., a gas detection sensor that detects concentrations of hazardous gases for safety or measures pollutants in the atmosphere), or other components that can provide indications, measurements, or signals corresponding to the surrounding physical environment.

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

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

[0164] The location component 1236 includes a positioning sensor component (e.g., a GPS receiver component), an altitude sensor component (e.g., an altimeter or a barometer that detects air pressure that can obtain altitude), an orientation sensor component (e.g., a magnetometer), and the like.

[0165] Various technologies may be used to implement communications. The I / O components 1202 also include a communications component 1238 that is operable to couple the machine 1200 to the network 1222 or device 1224 via a corresponding coupling or connection. For example, the communications component 1238 may include a network interface component or other suitable device that interfaces with the network 1222. In other examples, the communications component 1238 may include a wired communications component, a wireless communications component, a cellular communications component, a near field communications (NFC) component, a wireless communications ... Components (e.g. Low energy consumption), Components and other communication components for providing communication via other modalities. Device 1224 can be another machine or any peripheral device among various peripheral devices (e.g., a peripheral device coupled via USB).

[0166] In addition, the communication component 1238 can detect the identification, or include a component that is operable to detect the identification. For example, the communication component 1238 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 bar codes such as universal product codes (UPC) bar codes, multi-dimensional bar codes such as quick response (QR) codes, Aztec codes, data matrix, data symbols (Dataglyph), MaxiCode, PDF417, UltraCode, UCC RSS-2D bar codes, and other optical codes) or an acoustic detection component (e.g., a microphone for identifying an audio signal of a tag). In addition, various information can be obtained via the communication component 1238, such as positioning via Internet Protocol (IP) geographic location, obtaining a location via Positioning is obtained through signal triangulation, positioning is obtained via detection of NFC beacon signals that can indicate a specific position, etc.

[0167] Various memories (e.g., main memory 1214, static memory 1216, and memory of processor 1204) and storage unit 1218 may store one or more sets of instructions and data structures (e.g., software) that embody or are used by any one or more of the methods or functions described herein. These instructions (e.g., instructions 1210) when executed by processor 1204 cause various operations to implement the disclosed examples.

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

[0169] Software Architecture

[0170] Fig.131300 is a block diagram illustrating a software architecture 1304 that can be installed on any one or more of the devices described herein. The software architecture 1304 is supported by hardware such as a machine 1302, which includes a processor 1320, a memory 1326, and an I / O component 1338. In this example, the software architecture 1304 can be conceptualized as a stack of layers, where each layer provides specific functionality. The software architecture 1304 includes layers such as an operating system 1312, a library 1310, a framework 1308, and an application 1306. In operation, the application 1306 enables an API call 1350 through the software stack and receives a message 1352 in response to the API call 1350.

[0171] The operating system 1312 manages hardware resources and provides public services. The operating system 1312 includes, for example, a kernel 1314, services 1316, and drivers 1322. The kernel 1314 acts as an abstraction layer between the hardware and other software layers. For example, the kernel 1314 provides memory management, processor management (e.g., scheduling), component management, networking and security settings, and other functions. Services 1316 can provide other public services to other software layers. Drivers 1322 are responsible for controlling or interfacing with the underlying hardware. For example, drivers 1322 may include display drivers, camera drivers, or Low-power drivers, Flash drivers, Serial communication drivers (e.g., USB drivers), Drivers, audio drivers, power management drivers, etc.

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

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

[0174] In an example, applications 1306 may include a home application 1336, a contacts application 1330, a browser application 1332, a reader application 1334, a positioning application 1342, a media application 1344, a messaging application 1346, a game application 1348, and a variety of other applications such as third-party applications 1340. Application 1306 is a program that executes the functions defined in the program. Various programming languages ​​may be used to create one or more of the applications 1306 constructed in various ways, 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 specific example, third-party application 1340 (e.g., a third-party application created by an entity other than the vendor of a particular platform using ANDROID TM or IOS TM Software Development Kit (SDK) can be used to develop applications on platforms such as IOS TM ANDROID TM , Mobile software running on the mobile operating system of the phone or another mobile operating system. In this example, third-party applications 1340 can enable APIs 1350 provided by the operating system 1312 to facilitate the functions described herein.

[0175] Processing components

[0176] Now go to Fig.14 , which shows a diagrammatic representation of a processing environment 1400 that includes a processor 1402, a processor 1406, and a processor 1408 (eg, a GPU, a CPU, or a combination thereof).

[0177] Processor 1402 is shown coupled to power source 1404 and includes modules (permanently configured or temporarily instantiated), namely image processing component 1410, rendering component 1412, and application execution component 1414. Image processing component 1410 is enabled to process sensor data 611. An example of image processing component 1410 is Figure 6 The ML module 614 of the AR wearable device. The presentation component 1412 presents an indication of the AR application on the display of the AR wearable device. An example of the presentation component 1412 is Figure 6 UI module 634.

[0178] When the user 646 selects the AR application 642, the application execution component 1414 activates the AR application 642. An example of the application execution component 1414 is Figure 6 1408. The scan state 623 and other data may be located in a memory associated with the processor 1402. As shown, the processor 1402 is communicatively coupled to both the processor 1406 and the processor 1408.

[0179] Glossary

[0180] Certain embodiments are described herein as including logic or multiple components, modules, or mechanisms. A module may constitute a software module (e.g., a code contained on a machine-readable medium or in a transmission signal) or a hardware module. A "hardware module" is a tangible unit that is capable of performing certain operations and may be configured or arranged in a physical manner. In various example embodiments, one or more computer systems (e.g., a stand-alone computer system, a client computer system, or a server computer system) or one or more hardware modules (e.g., a processor or a processor group) of a computer system may be configured by software (e.g., an application or an application portion) as a hardware module that operates to perform certain operations as described herein.

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

[0182] "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. A client device may be, but is not limited to, a mobile phone, AR glasses, VR glasses, AR wearables, desktop computers, laptop computers, portable digital assistants (PDAs), smart phones, tablet computers, ultrabooks, netbooks, laptop computers, multiprocessor systems, microprocessor-based or programmable consumer electronics, game consoles, set-top boxes, or any other communication device that a user may use to access a network.

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

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

[0185] "Computer-readable storage media" refers to both machine storage media and transmission media. Thus, the term includes both storage devices / media as well as carrier / modulated data signals. The terms "machine-readable medium," "computer-readable medium," and "device-readable medium" mean the same thing and may be used interchangeably in this disclosure.

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

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

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

[0189] "Signal medium" refers to any intangible medium that can store, encode or carry instructions executed by a machine and includes digital or analog communication signals or other intangible media that facilitate the communication of software or data. The term "signal medium" should be deemed to include any form of modulated data signals, carrier waves, etc. The term "modulated data signal" means a signal in which one or more of its characteristics is set or changed in such a manner as to encode information in the signal. The terms "transmission medium" and "signal medium" mean the same thing and may be used interchangeably in this disclosure.

Claims

1. A method performed on an augmented reality (AR) system, the method comprising: receiving image data of an image captured from an image capture device; identifying an object in the image by processing the image data, the object being associated with a first tag; selecting an AR application from among a plurality of AR applications having a second tag matching the first tag; presenting an indication of the AR application on an AR display of an AR wearable device of the AR system; recognizing user input as a selection of the AR application; as well as In response to the selection of the AR application, the AR application is enabled.

2. The method according to claim 1, further comprising: The object is identified using a neural network trained to identify the object.

3. The method according to claim 1, further comprising: selecting the plurality of AR applications; as well as The images are processed using a plurality of neural networks associated with the plurality of AR applications, the plurality of neural networks being trained to recognize objects associated with tags that match tags of the plurality of AR applications.

4. The method according to claim 1, further comprising: transmitting the image and instructions for processing the image to a host computer via a wireless connection; as well as An indication of the object is received from the host computer.

5. The method according to claim 1, wherein: The indication of the AR application includes an icon and text, the text indicating a function or a name of the AR application, and wherein the method further comprises: identifying the object by positioning the AR wearable device; and A location for the icon is selected within the image.

6. The method according to any one of claims 1 to 5, further comprising: Presenting a selection shape on an AR display of the AR wearable device; as well as Based on the indication of the AR application being within the selection shape, the user input is recognized as the selection of the AR application.

7. The method according to any one of claims 1 to 5, further comprising: The first tag is selected based on the identification of the object.

8. The method according to any one of claims 1 to 5, further comprising: processing the user input to recognize a gesture, wherein the user input is movement of a user's appendage or utterance by the user's voice; The user input is recognized as the selection of the AR application based on the gesture matching gesture information, the gesture information being associated with the AR application.

9. The method according to any one of claims 1 to 5, wherein: The instruction to present the AR application on the AR display of the AR wearable device further includes: presenting an indication of the AR application at a first location on an AR display of the AR wearable device, and wherein recognizing the user input as the selection of the AR application further comprises: capturing a second image using the image capture device; processing the second image to identify a second location of the indication of the AR application within the second image; and Determining that movement of the indication of the AR application from the first location to the second location indicates the selection of the AR application.

10. The method according to any one of claims 1 to 5, further comprising: receiving an indication that the scanning state is on; as well as After recognizing the user input as the selection of the AR application, the scanning state is set to off.

11. The method according to any one of claims 1 to 5, wherein: The plurality of AR applications are a first plurality of AR applications, and wherein the method further comprises: receiving second image data of a second image captured from the image capture device; identifying a plurality of objects within the second image, the plurality of objects being associated with the first plurality of tags; selecting a second plurality of AR applications from among the first plurality of AR applications with tags associated with a second plurality of AR applications, the second plurality of AR applications matching one or more of the first plurality of tags; presenting indications of the second plurality of AR applications on an AR display of the AR wearable device; recognizing a second user input as a selection of a second AR application among the second plurality of AR applications; and In response to the selection of the second AR application, the second AR application is activated.

12. The method according to claim 11, wherein: The selection of the second plurality of AR applications is based on usage frequencies of the second plurality of AR applications.

13. The method according to any one of claims 1 to 5, wherein: The user input includes a selection of a button or a touchpad of the AR wearable device.

14. The method according to any one of claims 1 to 5, wherein: The instruction to present the AR application on the AR display of the AR wearable device further includes: An indication of the AR application and actions associated with the AR application on the AR display are presented on an AR display of the AR wearable device.

15. The method according to any one of claims 1 to 5, wherein: The AR wearable device is AR glasses.

16. The method according to any one of claims 1 to 5, wherein: An indication of the AR application is presented adjacent to the object.

17. The method according to any one of claims 1 to 5, wherein: Enabling the AR application also includes: The AR application is enabled using the image data, the indication of the object, and the indication of the location of the object within the image.

18. An augmented reality (AR) system, comprising: one or more processors; as well as one or more memories storing instructions that, when executed by the processors, configure the one or more processors to perform operations comprising: receiving image data of an image captured from an image capture device; identifying an object in the image by processing the image data, the object being associated with a first tag; selecting an AR application from among a plurality of AR applications having a second tag matching the first tag; presenting an indication of the AR application on an AR display of an AR wearable device of the AR system; recognizing user input as a selection of the AR application; and In response to the selection of the AR application, the AR application is enabled.

19. The AR wearable device according to claim 18, wherein: The operations also include: selecting the plurality of AR applications; and The images are processed using a plurality of neural networks associated with the plurality of AR applications, the plurality of neural networks being trained to recognize objects associated with tags that match tags of the plurality of AR applications.

20. A non-transitory computer-readable storage medium comprising instructions that, when executed by one or more processors of a virtual reality (AR) system, cause the one or more processors to perform operations comprising: receiving image data of an image captured from an image capture device; identifying an object in the image by processing the image data, the object being associated with a first tag; selecting an AR application from among a plurality of AR applications having a second tag matching the first tag; presenting an indication of the AR application on an AR display of an AR wearable device of the AR system; recognizing user input as a selection of the AR application; as well as In response to the selection of the AR application, the AR application is enabled.

Images