Voice input for ar wearable devices

Through the combination of voice input system and machine learning module, the problem of limited space in AR wearable devices is solved, and multiple applications are quickly switched and new application downloads are realized, improving the convenience of user interaction and the power efficiency of the device.

CN119654616APending Publication Date: 2025-03-18SNAP INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202380057444.6
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2022-08-02
Filing Date
2023-07-31
Publication Date
2025-03-18

AI Technical Summary

Technical Problem

Existing augmented reality (AR) wearable devices have limited space on the user interface, making it difficult to achieve rapid switching of multiple applications and download new applications.

Method used

By recognizing voice commands, users can interact without physical user interface items, use keyword modules and machine learning modules to reduce the power consumption of audio data processing, and realize efficient monitoring of voice input systems.

Benefits of technology

It realizes rapid multi-application switching and new application downloads for AR wearable devices, reducing the power consumption of devices and improving the convenience of user interaction.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119654616A_ABST
    Figure CN119654616A_ABST
Patent Text Reader

Abstract

Systems, methods, and computer readable media for augmented reality (AR) wearable device voice input are disclosed. Embodiments are disclosed that enable a user to interact with an AR wearable device without using a physical user interface device. Keywords are used to indicate that a user is about to speak an action or command. The AR wearable device divides the processing of the audio data into a keyword module trained to identify keywords and a module that processes the audio data after the keywords. In some embodiments, the AR wearable device transmits audio data following the keyword to a host device for processing. The AR wearable device maintains an application registry that associates an action with an application. An application may be downloaded and an application registry updated, where the application indicates an action to be associated with the application.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] Priority declaration

[0002] This application claims the benefit of U.S. patent application serial number 17 / 816,914, filed on August 2, 2022, which is incorporated herein by reference in its entirety. 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 voice input to identify applications to be enabled by an AR wearable device. Background Art

[0004] Users increasingly expect virtual reality (VR), mixed reality (MR), and augmented reality (AR) wearable devices to operate in a more user-friendly manner. However, typically, wearable devices have very little space on the wearable device for interface controls. BRIEF DESCRIPTION OF THE DRAWINGS

[0005] In the 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 of an access restriction process according to some examples.

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

[0012] Figure 7 A display of a system with an indication of an application is shown according to some embodiments.

[0013] Figure 8 A display of a system with an indication of an application is shown according to some embodiments.

[0014] Fig. 9 An application according to some embodiments is shown.

[0015] Fig.10 A method for voice input for an AR wearable device according to some embodiments is shown.

[0016] Fig.11 A method for operating a scan manager according to some embodiments is shown.

[0017] Fig.12 is a perspective view of a wearable electronic device in the form of glasses 1200 according to some examples.

[0018] Fig.13 A method for voice input for an AR wearable device according to some embodiments is shown.

[0019] Fig.14 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.

[0020] Fig.15 is a block diagram illustrating a software architecture in which examples may be implemented.

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

[0022] The following description includes the system, method, technology, instruction sequence and computer program product of the illustrative example of implementation of the present disclosure. In the following description, for the purpose of illustration, many specific details are set forth, so as to provide an understanding of the various examples of the subject of the present invention. However, it will be apparent to those skilled in the art that the example of the subject of the present invention can be put into practice without these specific details. Usually, it is not necessary to show in detail known instruction examples, protocols, structures and technologies.

[0023] 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, including VR wearable devices and MR wearable devices. Application is used to refer to both AR applications and non-AR applications.

[0024] Typically, an AR wearable device 602, such as AR glasses 900, has limited physical user interface items, such as buttons 1278. Some AR wearable devices 602 have one or two buttons 1278 or a touchpad 1276 that a user 646 interacts with on the frame 1232 of the AR wearable device 602. However, the number of applications 642 that a user 646 may want to access on the AR wearable device 602 is numerous. In addition, new applications 642 may be downloaded to the AR wearable device 602.

[0025] One challenge is how to make applications 642 available to users without the user 646 having to use physical user interface items. The challenge is addressed by recognizing voice commands from the user 646. In addition, the user 646 can respond to the system 600 using voice commands to resolve ambiguity about which application 642 the user 646 wants to run or to provide input to the application 642. The AR wearable device 602 communicates with the user 646 visually by displaying information on the display 606 or verbally by using a speaker. The user 646 can respond to the AR wearable device 602 using their voice 648, position 650, or gesture 659 without having to resort to using physical user interface items. In this way, the user 646 can interact with the AR wearable device 602 without using physical user interface items.

[0026] Another challenge is how to allow new applications 642 to be downloaded to the AR wearable device 602. This challenge is solved by the application 642 indicating the command or action 643 that the application 642 wants to be associated with. The AR wearable device 602 maintains an application registry 645 that associates the application 642 with the action 643. The system 600 uses the application registry 645 to select an application 642 to satisfy the user intent 636.

[0027] Another challenge is how to monitor the voice of user 646. AR wearable device 602 relies on battery power, and processing all audio data 613 received from user 646 will require power at a rate that requires frequent recharging. This challenge is solved in two ways. First, keywords are used to indicate to AR wearable device 602 that user 646 is about to issue a command. Keyword module 652 resides on AR wearable device 602 and is trained to recognize keywords, and in some embodiments, only recognize keywords. This reduces the power required to process audio data 613. The second way to solve this challenge is that when a keyword is recognized, the AR wearable device 602 uses ML module 614 to process audio data 613 after the keyword, or sends audio data 613 to an external host to process audio data 613. Sending audio data 613 to an external host reduces the power required to process audio data 613.

[0028] The host returns a transcription 656, which is used to determine the appropriate application 642 to run to satisfy the user intent 636. A third way to address this challenge is for the AR wearable device 602 to monitor for speech based only on tactile user interface items, such as a pressed button. Unless the user explicitly selects the AR wearable device 602 to monitor for speech, the AR wearable device 602 does not waste energy monitoring for speech.

[0029] Networked computing environment

[0030] Figure 1 1 is a block diagram illustrating an example messaging system 100 for exchanging data (e.g., messages and associated content) over a network. The messaging system 100 includes multiple instances of a client device 102, each instance hosting a number of 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).

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

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

[0033] 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, geolocation information, media enhancements and overlays, message content persistence conditions, social network information, and live event information. The data exchange within the messaging system 100 is stimulated and controlled by functions available via the user interface (UI) of the messaging client 104.

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

[0035] 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 activate the functions 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 of media data collections (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 in a social graph; and opening application events (e.g., related to messaging client 104).

[0036] The application server 114 hosts several 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 several message processing technologies and functions, particularly those related to the aggregation and other processing of content (e.g., text and multimedia content) included in messages received from multiple instances of the messaging client 104. As will be described in more detail, text and media content from multiple sources can be aggregated into collections of content (e.g., referred to as stories or galleries). These collections are then made available to the messaging client 104. In view of the hardware requirements for other processor- and memory-intensive data processing, such processing can also be performed on the server side by the messaging server 118.

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

[0038] 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 an AR application associated with a label 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.

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

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

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

[0042] 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 activities occurring in one or more external resources. For example, the messaging client 104 may provide a participant in a conversation (e.g., a chat session) in the messaging client 104 with a notification related to the current or recent use of an external resource by one or more members of a user group. One or more users may be invited to join 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 a user group entering a 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.

[0043] 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 applications 106 (or applets) may vary based on how the user launches the menu (e.g., from a conversational interface or from a non-conversational interface).

[0044] System Architecture

[0045] Figure 21 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 several subsystems that are supported on the client side by the messaging client 104 and on the server side by the application server 114. These subsystems include, for example, a transient timer system 202, a collection management system 204, an enhancement system 208, a map system 210, a game system 212, an external resource system 214, and a voice input system 216.

[0046] The transient timer system 202 is responsible for implementing temporary or time-limited access to content by the messaging client 104 and the messaging server 118. The transient timer system 202 includes several timers that selectively enable access (e.g., for presentation and display) of 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.

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

[0048] In addition, the collection management system 204 includes a curation interface 206 that enables 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). In addition, the collection management system 204 uses machine vision (or image recognition technology) and content rules to automatically curate content collections. In some examples, compensation can be paid to users 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.

[0049] 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 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 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 augmentation system 208 uses the geolocation of the client device 102 to identify a media overlay that includes the business name at the geolocation of the client device 102. The media overlay may include other logos associated with the business. The media overlay may be stored in the database 120 and accessed by the database server 120.

[0050] In some examples, the enhancement system 208 provides a user-based publishing platform that enables a user to select a geolocation on a map and upload content associated with the selected geolocation. The user can also specify situations where 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 geolocation.

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

[0052] The mapping system 210 provides various geolocation functions and supports the presentation of map-based media content and messages by the messaging client 104. For example, the mapping system 210 enables the display of a user icon or avatar (e.g., stored in the profile data 316) on a map to indicate the current or past locations of the user's "friends" and media content (e.g., a collection of messages including photos and videos) generated by such friends in the context of the map. For example, on the map interface of the messaging client 104, messages posted by the user to the messaging system 100 from a particular geolocation 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 an appropriate status avatar) 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.

[0053] 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 gaming, provides leaderboards for gaming, and also supports providing in-game rewards (e.g., gaming coins and items).

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

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

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

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

[0058] 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 displaying the login page or title screen of the external resource for a threshold period of time (e.g., 3 seconds), the messaging client 104 slides up a menu for authorizing the external resource to access the user data (e.g., animating the menu to emerge from the bottom of the screen to the middle or other portion of the screen). The menu identifies the type of user data that the external resource will be authorized to use. In response to receiving the user selection of the accept option, the messaging client 104 adds the external resource to the list of authorized external resources and enables the external resource to access the user data from the messaging client 104. In some examples, the messaging client 104 authorizes the external resource to access the user data according to the OAuth 2 framework.

[0059] 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 the 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 the user, a three-dimensional avatar of the 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.).

[0060] The voice input system 216 supports the system 600 for AR wearable devices. The voice input system 216 receives requests from the AR wearable device and responds to the requests. The request includes sensor data, such as audio data 613 that is sent to the voice input system 216 for processing. The input modality system 216 processes the audio data and recognizes actions 643 within the audio data 613, and returns a transcription 656 of the audio data 613, which may include an indication of the action 643. The AR wearable device can request other services from the voice input system 216.

[0061] Data Architecture

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

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

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

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

[0066] 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 status or activity that a user can select to transmit at a particular time.

[0067] 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).

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

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

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

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

[0072] As described above, augmented data includes augmented reality content items, overlays, image transformations, AR images, and similar items that refer to modifications that can be applied to image data (e.g., videos or images). This includes real-time modifications that modify images when they are captured using a device sensor (e.g., one or more cameras) of the client device 102 and then display the modified images on the screen of the client device 102. This also includes modifications to stored content such as video clips that can be modified in a gallery. For example, in a client device 102 that can access multiple augmented reality content items, a user can use a single video clip with multiple augmented reality content items to watch how different augmented reality content items will modify the stored clips. For example, by selecting different augmented reality content items for content, multiple augmented reality content items that apply different pseudo-random movement models can be applied to the same content. Similarly, real-time video capture can be used with the modifications shown to show how the video image currently captured by the sensor of the client device 102 will modify the captured data. Such data 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 different augmented reality content items will be displayed in different windows of the display at the same time. This can, for example, enable multiple windows with different pseudo-random animations to be viewed on the display at the same time.

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

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

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

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

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

[0078] Other methods and algorithms suitable for face detection can be used. For example, in some examples, landmarks are used to locate features, which represent distinguishable points that exist in most of the images considered. For example, for facial landmarks, the location of the left pupil can be used. If the initial landmarks are not recognizable (for example, if the person wears an eye patch), secondary landmarks can be used. Such 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 (meanshape) is the average value of the aligned training shapes.

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

[0080] 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, mood transformations (e.g., changing a face from a frown to a smile), state transformations (e.g., aging a subject, reducing apparent age, changing gender), style transformations, application of graphical elements, and any other suitable image or video manipulations enabled by a convolutional neural network that has been configured to execute efficiently on the client device 102.

[0081] 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 in association with an interface described herein. The modification icon includes the following changes, which can be the basis for modifying the face of the user within the image or video stream as part of the modification operation. Once the modification icon is selected, the transformation system initiates a process of transforming the image of the user to reflect the selected modification icon (e.g., generating a smiley face on the user). Once the image or video stream is captured and the specified modification is selected, the modified image or video stream can be presented in a graphical user interface displayed on the client device 102. The transformation system can implement a complex convolutional neural network on a portion of the image or video stream to generate and apply the selected modification. That is, a user can capture an image or video stream, and once a modification icon has been selected, the modified result can be presented in real time or near real time. In addition, when the video stream is being captured, the modification can be persistent and the selected modification icon remains toggled. Machine learning neural networks can be used to implement such modifications.

[0082] The graphical user interface presenting the modifications performed by the transformation system can supply the user with additional interactive options. 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 modifications can be persistent after the modification icon is initially selected. The user can switch to turn the modification on or off by tapping or otherwise selecting the face being modified by the transformation system, and store it for later viewing or browsing to other areas of the imaging application. In the case of multiple faces being modified by the transformation system, the user can globally switch the modification on or off by tapping or selecting a single face modified and displayed within the graphical user interface. In some examples, each face in a plurality of face groups can be modified individually, or such modifications can be individually switched by tapping or selecting a single face or a series of single faces displayed within the graphical user interface.

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

[0084] A collection may also constitute a "live story" that is a collection of content from multiple users, created manually, automatically, or using a combination of manual and automatic techniques. For example, a "live story" may constitute a curated stream of user-submitted content from different locations and events. Users whose client devices have location services enabled and who are at a co-located event at a 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.

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

[0086] 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 whose message data is stored in the entity table 306. The entity table 306 can associate various enhancements from the enhancement table 310 with the various images and videos stored in the image table 312 and the video table 304.

[0087] Data communication architecture

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

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

[0090] • 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 .

[0091] • 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 .

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

[0093] • 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 .

[0094] Message enhancement data 412 : Enhancement data (eg, filters, stickers, or other annotations or enhancements) representing enhancements to be applied to the message image payload 406 , message video payload 408 , or message audio payload 410 of the message 400 .

[0095] • 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.

[0096] 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).

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

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

[0099] • 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.

[0100] • 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.

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

[0102] Time-based access restriction architecture

[0103] Figure 5is 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).

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

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

[0106] exist Figure 5 1. 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.

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

[0108] Thus, the group timer 514 operatively controls the overall 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.

[0109] 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 also operates 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.

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

[0111] In response to the transient timer system 202 determining that the transient 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 transient 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 for a particular transient 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 transient message 502.

[0112] Voice input for AR wearables

[0113] Figure 6 A system 600 for providing voice input to an AR wearable device according to some examples is shown. The system 600 includes a Fig.10 The glasses 1200 may include an AR wearable device and may include other devices such as a portion of the messaging server system 108 or the client device 102 that may perform one or more of the operations described herein.

[0114] Input / output (IO) devices 604 include devices that enable user 646 to receive output or provide input to system 600. IO devices 604 include display 606, speakers, microphone 603, buttons 1078, touch pad 1076, gyroscopes, etc. Some devices such as gyroscopes can be both sensors 608 and IO devices 604. For example, user 646 of mobile system 600 transmits input to system 600. However, user 646 can move system 600 without intending to transmit input to system 600. Sensor 608 includes gyroscope, light sensor, image sensor or camera, positioning sensor, clock, etc. According to some examples, sensor 608 includes wireless communication. Wireless communication such as LE Bluetooth, Institute of Electrical and Electronics Engineers (IEEE) 802.11 communication standard, proprietary communication standard or 3GPP communication standard can be used to determine the position and / or orientation of system 600, so wireless communication can also be considered as sensor 608. Scan state 623 is stored in a memory of system 600 and indicates a state of system 600 for processing audio data 613 .

[0115] Context data 612 includes data associated with system 600 and user 646. Data associated with user 646 includes other users of messaging system 100 and profiles of the user. In some examples, context data 612 includes information available on the Internet. Additionally, context data 612 includes information available from or generated by AR wearable device 602. For example, sensor 608 generates location 615 data, time 617 data, and image 610 data. IO device 604 generates information based on information such as Fig.13 The display 606 is an electronic device for visually presenting data (e.g., visually presenting application 642 activity to user 646). According to some examples, the display 606 is Fig.13 Optical elements 1343, 1344. Display 606 can be referred to as AR display 606.

[0116] In some implementations, there are three scanning states 623. An off state, in which the system 600 does not scan the audio data 613 for actions 643 or user intent 636. A continuous state, in which the system 600 continuously scans the audio data 613 for actions 643 or user intent 636 without regard to keywords. And a keyword-activated state, in which the system 600 scans the audio data 613 for keywords or user intent 636, and if a keyword is found, processes the audio data 613 after the keyword for actions 643 or user intent 636. The action 643 can be a command, an action 643 phrase, an action 643 word, etc.

[0117] In the keyword-activated state, the audio data 613 is passed or fed into the keyword module 652, which processes the audio data 613 to identify whether the audio data 613 includes a keyword. Example keywords include "Hey, glasses", "execute command", "computer:", etc. Keywords can be phrases, words, or sounds. In some embodiments, keywords can be selected by a user 646. The keyword module 652 can be a neural network trained to recognize keywords. According to some embodiments, the keyword module 652 has weights 654. When the keyword module 652 recognizes a keyword, it passes the audio data 613 to the machine learning (ML) module 614.

[0118] According to some embodiments, in a continuous state of the scanning state 623, the audio data 613 is passed directly to the ML module 614 without first identifying keywords. The ML module 614 is a neural network or other type of machine learning module with weights 616. The ML module 614 takes the audio data 613, the context data 612, and / or the application registry 645 as input and generates a transcription 656 of the audio data 613 as output. In some embodiments, the ML module 614 looks for actions 643 within the audio data 613. Some or all of the functionality of the ML module 614 may be part of the voice input system 216.

[0119] In some embodiments, the keyword module 652 resides within the AR wearable device 602, and the functionality of the ML module 614 is performed on a host system such as the voice input system 216 or the user device 102. The continuous state of the scanning state 623 is energy intensive and drains the battery (not shown) of the system 600. Therefore, it is desirable to reduce the amount of time that the system 600 is in the scanning state 623 where the audio data 613 is continuously scanned. The keyword-enabled state of the scanning state 623 requires less energy because all of the audio data 613 does not need to be analyzed. The keyword module 652 can efficiently scan the audio data 613 for keywords based on training. The training of the keyword module 652 and / or the ML module 614 is performed by the system 600 or a host computer such as the voice input system 216. For example, the system 600 or the voice input system 216 trains the keyword module 652 to determine the voice 648 of the user 646 and / or the weight 654 of a given keyword. According to some implementations, the system 600 or the voice input system 216 trains the ML module 614 to determine the weight 616 of the user 646 's voice 648 .

[0120] The application registry 645 is an association between applications 642 and actions 643. Applications 642 register to be associated with actions 643. In some implementations, applications 642 implicitly register actions 643 by defining actions 643 exposed by application 642 via a settings file bundled with application 642. Then, when system 600 boots up, system 600 builds application registry 645. Additionally, applications 642 may be downloaded after booting up and their actions 643 added to application registry 645.

[0121] When the scan manager 626 determines that the action 643 is part of the transcription 656, the scan manager 626 considers all applications 642 associated with the action 643. The UI module 634 provides a user interface for the user 646 to associate the action 643 with the application 642, such as in conjunction with Fig.10 In some implementations, the action 643 is associated with metadata 657. For example, an action such as "play" can be associated with metadata 657 indicating that a band name or song name may follow "play". For example, the action 643 is "play <band name|song name>".

[0122] An application 642 may be associated with more than one action 643, and an action 643 may be associated with more than one application 642. For example, a music player application 642 is associated with actions 643 such as "play", "next song", "stop", etc. The complete command to the system 600 is "Hey, glasses, next song". Wherein the keyword module 652 recognizes the keyword "Hey, glasses", and activates the ML module 614 by passing the audio data 613 following "Hey, glasses" to the ML module 614. The ML module 614 generates a transcription of "next song", which is passed to the scan manager 626. The ML module 614 may use the action 643 currently associated with the application 642 to help determine the transcription 656.

[0123] In addition, the ML module 614 provides information or metadata 657 about the words or phrases in the transcription 656. For example, for the utterance "Hey, Glasses, play 'pop star name'", the ML module 614 generates a transcription 656 with metadata 657 indicating that "play" is the action 643 and that "pop star name" is a proper noun or pop star name. The ML module 614 uses the metadata 647 associated with the action 643 to determine the metadata 657. The scan manager 626 uses the metadata 657 to determine the application 642 intended by the user 646.

[0124] In another example, for the utterance "Hey, glasses, convert 5 meters to feet", the ML module 614 generates a transcription 656, where "convert" is identified as an action 643, and "convert 5 meters to feet" is identified as a number, a first measurement unit, and a second measurement unit. The metadata 647 associated with the action 643 includes information indicating that after the action 643 "convert", there will be a number, a first measurement system, and a second measurement system. The scan manager 626 uses the transcription 656 and the metadata 657 to determine one or more applications 642 to run or present to the user 646.

[0125] In another example, for the utterance “Hey, glasses, select sweet white wine,” the ML module 614 generates a transcription 656, in which “select” is identified as an action 643, and “sweet white wine” is identified as a noun phrase indicating a type of “wine.” The metadata 647 associated with the action 643 includes information that after the action 643 “select,” there will be a noun, which may include enumerated objects that the application 642 is able to “select,” such as “wine,” “beer,” “peanut butter,” and the like.

[0126] In another example, for the utterance "Hey, glasses, select sweet white wine", the keyword module 652 identifies the keyword "Hey, glasses", and then passes the audio data 613 to the ML module 614. The ML module 614 processes the audio data 613 to determine an action 643 such as "select". The scan manager 626 determines the application 642 based at least on the action 643. The scan manager 626 then enables the application 642 with the audio data 613, which may have been truncated to remove the keyword and action 643. For example, continuing the example above, the audio data 613 will include "sweet white wine" or "select sweet white wine", depending on whether the audio data 613 is truncated. The application 642 then determines how to process the audio data 613 or controls the processing of the audio data 613.

[0127] The application 642 for “selecting” “wine” captures the image 610 or uses a previously captured image 610 and segments the image 610 into different wine bottle labels in the image 610. The application 642 then displays a label on the suggested wine bottle or plays the name of the wine on the speaker of the AR wearable device 602.

[0128] Scan manager 626 accesses transcription 656 and application registry 645 to determine whether to run application 642, present application 642 for confirmation by user 646, or present a list of applications 642 for selection by user 646. Scan manager 626 determines which actions 643 are present in transcription 656. Scan manager 626 evaluates which applications 642 are most likely to satisfy user intent 636. Scan manager 626 performs one or more of the following actions to determine probability 633 that application 642 and action 643 match user intent 636. User intent 636 represents what user 646 expects or wants based on audio data 613.

[0129] If there are multiple actions 643 and / or multiple applications 642 associated with action 643, scan manager 626 compares metadata 647 to metadata 657. Metadata 647 is specific to a particular application 642, so if metadata 647 matches metadata 657, scan manager 626 increases the probability 633 that user intent 636 executes application 642 associated with matching metadata 647. For example, there may be two applications associated with action 643 "select". The metadata 647 for one may be "Select <"wine"|"beer">", while the metadata for the other may be "Select <street name 1> & <street name 2>". Metadata 657 may indicate a match with "select wine", such that application 642 for selecting wine is given a higher probability of satisfying user intent 636.

[0130] In addition, the scan manager 626 can execute the application 642 using the transcription 656, and the application 642 can return a value indicating whether the transcription 656 includes valid parameters or invalid parameters for the application 642. The scan manager 626 can use this information to determine the probability that the application 642 will satisfy the user intent 636. In addition, the scan manager 626 can use additional information available in the system 600. For example, in some embodiments, the system 600 identifies an object within the image 610. The scan manager 626 can adjust the probability 633 based on the relationship between the identified object and the application 642 and / or the action 643. For example, if an object including a wine bottle is identified in the image 610, and the metadata 647 indicates that the name of the wine can be included after the action 643, then the probability 633 of the action 643 associated with the metadata 647 is increased. The scan manager 626 evaluates the probability 633 of each eligible application 642 and action 643.

[0131] If the probability 633 is greater than or exceeds the threshold for the action 643 and the application 642, the scan manager 626 executes the application 642 without additional user 646 input. If there are multiple applications 642 and / or actions 643, and none of the associated probabilities 633 is greater than or exceeds the threshold, the scan manager 626 passes the list of actions 643 and associated applications 642 to the user interface (UI) module 634 to determine the user intent 636.

[0132] When scan manager 626 executes application 642, application 642 may access one or more of: audio data 613, transcription 656, contextual data 612, and input from user 646. In some implementations, scan manager 626 maintains privacy 618 for user 646. Scan manager 626 may ask user 646 whether application 642 may be executed and whether application 642 may access data associated with user 646.

[0133] In some implementations, access to data associated with a user 646 has multiple privacy levels 618. For example, at one privacy level 618, the actual audio data 613 may be accessed, and at a lower privacy level 618, only the transcription 656 may be accessed. Access to the transcription 656 is less intrusive than access to the audio data 613. An application 642 may be granted a privacy level 618, which is typically the minimum level required for the application 642 to perform its function. In some implementations, the application 642 is required or encouraged to request the minimum privacy level 618 required to perform its actions. According to some implementations, each of the contextual data 612 is assigned a privacy level 618.

[0134] The UI module 634 presents actions 643 and / or applications 642 to confirm a default selection or for the user 646 to select an action 643 and / or application 642. The UI module 634 determines user intent 636 based on input from the user 646. The user input module 638 manages input from the user 646. The input from the user 646 can be indicated based on the user's 646 voice 648, the user's 646 position 650 that changes or remains unchanged, tactile 653 input from the user 646 (such as a button press), and / or gestures 659 from the user 646 (such as a circle indicated by the user's 646 finger to the application 642). The action 643 word or phrase can be spoken by the user 646 in their voice 648.

[0135] Figure 7Display 606 of system 600 with indications of applications is shown in accordance with some embodiments. For example, a user can see person 702 standing nearby. User 646 (not visible) says "Hey, Glasses, play 'Song Name'". Keyword module 652 recognizes "Hey, Glasses" within audio data 613 and sends audio data 613, which may be edited to remove "Hey, Glasses", to ML module 614. System 600 may wirelessly send audio data 613 to ML module 614 residing on a host device such as voice input system 216 or client device 102. ML module 614 generates transcription 656, which may be wirelessly transmitted to system 600 by voice input system 216 or client device 102.

[0136] Scan manager 626 determines that transcription 656 includes action 643 “play”. Scan manager 626 determines that there are two applications 642 associated with action 643 “play”. Scan manager 626 determines that the probability that application 642 “plays” the song is not greater than or does not exceed a threshold, so scan manager 626 sends the two applications 642 to UI module 634.

[0137] The UI module 634 displays "Play Song Title" 706, "Play Game Title" 710, "Cancel" 712, "Voice Scan On" 714, and "Other" 714 on the display 606. The UI module 634 displays the options on the display 606 as shown and / or displays 606 application carousel 720, where icon 729 corresponds to "Other" 714, icon 726 corresponds to "Cancel" 712, icon 716 corresponds to "Play Song Title", icon 718 corresponds to "Play Game Title" 710, and icon 722 corresponds to "Cancel" 710. The user input module 638 determines the user's intent 636 or selection of possible options. The user 646 can indicate the selection by using their voice 648, by moving or tilting their head to move the selection rectangle 704 over the options, using a tactile 653 control, or by a gesture 659, for example, by virtually pressing or selecting one of the icons with an appendage such as their finger 724. For example, UI module 634 recognizes user 646's input as a selection of application 642 "Play Song Title" 706 based on the indication of application "Play Song Title" 706 being within the selection shape, selection rectangle 704. In some implementations, the position of selection rectangle 704 remains stable as AR wearable device 602 moves and the position of the indication of one or more applications moves according to the movement of AR wearable device 602. In this way, user 646 can move their head up or down to select application 642.

[0138] UI module 634 sends the user intent 636 or selection to scan manager 626. Scan manager 626 may determine whether the privacy 618 of user 646 is satisfied before executing or running application 642 using transcription 656 and context data 612. For example, user 646 may grant permission for application 642 to access transcription 656 and / or context data 612. The "game title" may be an AR game that interacts with the environment as seen in display 606. For example, graphics may be added to augment trees to indicate a list of possible tree species. User 646 will guess the appropriate species of tree.

[0139] Figure 8 A display 606 of the system 600 is shown with an indication of an application in accordance with some implementations. Figure 8 Similar to Figure 7 , but only one application 642 is shown to match the action 643 "play". Scan manager 626 determines that the probability is not greater than or does not exceed the threshold for executing or running application 642 without first confirming that user intent 636 is to execute or run application 642 to "play song title" 706. User 646 confirms or selects one of the options displayed on display 606, such as Figure 7 As described in.

[0140] Fig. 9 An application 642 is shown according to some embodiments. When a user 646 is in a wine store where wines 904 and wine clerk 902 are visible, a wine selection application 642 is executed or run. The user 646 says "Hey, glasses, select a wine". The scan manager 626 determines an application based on the action 643 "select", metadata 647, and a location 615 indicating that the user 646 is within the wine store. The scan manager 626 executes or runs the application 642 without confirmation from the user 646 because the probability of the user's intent 636 to execute or run the selection application 642 associated with the action 643 "select" is greater than or exceeds a threshold. The application 642 provides recommendations 908 for wines and provides options including "next" 911, which, when selected, provides the next best recommendation 908 for another wine. The application 642 accesses the image 610 and segments the image to determine the wines available in the store. The application 642 may additionally access the Internet and use information available on the store's website to help make the recommendation 908. Additionally, user 646 may select "Cancel" 906 application 642. An application carousel 918 may also be provided. Icon 916 corresponds to "Cancel" 906, icon 920 "Next" corresponds to "Next" 911, icon 922 "More" provides additional options, and icon 912 turns off voice scanning. User 646 indicates user intent 636 as disclosed herein.

[0141] Fig.10 A method 1000 for voice input for an AR wearable device is shown according to some embodiments. The method 1000 begins at operation 1002 where activation is detected. For example, the keyword module 652 is monitoring the audio data 613 and detects "Hey, glasses".

[0142] The method 1000 continues at operation 1004, where a scan intent is sent. For example, the keyword module 652 sends an indication to the ML module 614 that a keyword has been detected in the audio data 613. In some implementations, when the keyword module 652 has detected a keyword, an indication that the keyword has been detected is communicated to the user 646. For example, by uttering or displaying "Please comment".

[0143] The method 1000 continues at operation 1006, where the interpreter receives an intent. For example, the ML module 614 receives an indication that a keyword has been detected in the audio data 613. The method 1000 continues at operation 1008 to initiate a scanner. For example, the ML module 614 collects audio data 613 following the keyword. The method 1000 continues at operation 1012 to collect contextual information. For example, the ML module 614 collects contextual data 612, which may include sending a command to an image capture device to capture an image 610.

[0144] The method 1000 continues at operation 1014, where the request is submitted to the backend 1018. For example, the ML module 614 can send the request to the application server 114 and / or the client device 102 using wireless communication. The AR wearable device 602 is wirelessly connected to a host system such as the application server 114 or the client device 102. The method 1000 continues at operation 1019, where the audio data is processed using a machine learning model. For example, the ML module 614 processes the audio data 613, such as in combination with the Figure 6 The ML module 614 may reside remotely or locally on the AR wearable device 602 .

[0145] The method 1000 continues at operation 1015 where a response is received. For example, the ML module 614 has completed processing the audio data 613. When the ML module 614 is located at a remote location, it sends a signal to the AR wearable device 602 indicating that it has completed processing. The ML module 614 sends the transcript and data 1021 to the scan manager.

[0146] Method 1000 continues at operation 1016 where the scan manager is executed. For example, scan manager 626 receives transcript 656 and determines whether to execute or run application 642, such as in conjunction with Figure 6 and as described herein.

[0147] The method 1000 continues at operation 1020, where the user discards the application 642. For example, the user 646 can determine "cancel" 710 instead of running the application 642. In some implementations, the method 1000 continues, where the carousel appears 1024. For example, the application carousel 720 can be displayed on the display 606, providing the user 646 with various options, such as displaying a menu to select an application 642.

[0148] If the user does not discard the option to execute or run the application 642, the method 1000 continues with launching the application at operation 1022. For example, the scan manager 626 may execute the selected application 642 while first ensuring that the privacy 618 criteria are met.

[0149] From operations 1022, 1024, and 1026, method 1000 continues to operation 1028 where scanning stops. For example, ML module 614 may no longer examine audio data 613. Keyword module 652 continues to scan audio data 613 for another instance of the keyword.

[0150] In some embodiments, the method 1000 continues from operation 1008 to operation 1010, where a timeout is initiated. For example, the ML module 614 may initiate a timeout threshold when processing the audio data 613. The method 1000 continues at operation 1026, where a timeout occurs. For example, if no new audio data 613 is received after the keyword, the ML module 614 determines that a timeout has occurred. The method 1000 may return to operation 1002.

[0151] The method 1000 may include one or more additional operations. The operations of the method 1000 may be performed in a different order. One or more of the operations of the method 1000 may be optional. The method 1000 may be performed by the client device 102, the system 600, the glasses 1200, or other electronic devices. A portion of the functions may be performed on a server computer or a host computer. 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.

[0152] Fig.11 A method 1100 for operating a scan manager according to some embodiments is shown. The method 1100 is an extension of operating a scan manager and is based on Fig.10 1102 and returns to Fig.10 1122 ends. Method 1100 continues with receiving transcripts and data at operation 1104. For example, scan manager 626 receives transcript 656 and may access context data 612.

[0153] The method 1100 continues at operation 1106 where a list of supported actions is generated based on the transcript and the data. For example, the scan manager 626 generates a list of actions based on the transcript 656 and the application registry 645, using other data such as the context data 612 in some embodiments.

[0154] The method 1100 continues at operation 1108 where a registered application matching at least one action is found. For example, the scan manager 626 can search the application registry 645 to determine which applications 642 are associated with one of the actions 643.

[0155] Method 1100 continues at operation 1110 where it is determined whether one or more applications match the action. If there is no application matching the action 643 in transcript 656, method 1100 returns to Fig.10 If there are one or more applications 642 that match the action 643 in the transcription 656, the method 1100 continues to operation 1112 to determine whether a single application matches the action with a probability greater than a threshold.

[0156] If the determination is successful, method 1100 continues at operation 1114 where the application is started. Fig. 9 The wine selection application 642 is shown executed based on the probability of the user intent 636 to execute the application 642 being greater than or exceeding a threshold.

[0157] If the determination at operation 1112 is unsuccessful, method 1100 continues at operation 1116 where all AR applications are presented. Figure 7 The situation where two applications 642 are presented to the user 646 is shown. When the user selects an AR application, the method 1100 continues at operation 1118, where the user selects an AR application. For example, Figure 7 The user 646 is shown selecting or selecting "Play Song Title" 706, where the action 643 is "Play". If the user 646 does not select an AR application, the method 1100 continues at operation 1120, where the user discards the AR application. For example, Figure 7 The user 646 in can select "Cancel" 710, which will discard the application 642. The method 1100 returns to Fig.10 1122.

[0158] 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 1200, or other electronic devices. A portion of the functions may be performed on a server computer or a host computer. 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.

[0159] Fig.12 1 is a perspective view of a wearable electronic device in the form of glasses 1200 according to some examples. Glasses 1200 are eyewear products including electronic devices that operate within a network system for transmitting image and video content. In some examples, the wearable electronic device is referred to as AR glasses. Glasses 1200 may include a frame 1232, which is made of any suitable material such as plastic or metal, including any suitable shape memory alloy. Frame 1232 may have a front piece 1233, which may include a first lens or left lens, a display or optical element holder 1236 and a second lens or right lens, a display or optical element holder 1237 connected by a bridge 1238. Front piece 1233 also includes a left end 1241 and a right end 1242. The first optical element or left optical element 1244 and the second optical element or right optical element 1243 may be disposed in respective left optical element holders 1236 and right optical element holders 1237. Each of the optical elements 1243 and 1244 can be a lens, a display assembly, or a combination thereof. In some examples, for example, the glasses 1200 are provided with an integrated near-eye display mechanism that enables, for example, displaying a preview image of visual media captured by the camera 1269 of the glasses 1200 to the user.

[0160] The frame 1232 further includes a left arm or temple piece 1246 and a right arm or temple piece 1247, which are coupled to the respective left end 1241 and right end 1242 of the front piece 1233 by any suitable means such as a hinge (not shown) to be coupled to the front piece 1233 or rigidly or fixably fixed to the front piece 1233, thereby being integral with the front piece 1233. Each of the temple piece 1246 and the temple piece 1247 may include: a first portion 1251 coupled to the respective end 1241 or 1242 of the front piece 1233; and any suitable second portion 1252 for coupling to the ear of the user, such as a curved or arched piece. In one example, the front piece 1233 can be formed of a single piece of material to have a unitary or one-piece construction. In one example, the entire frame 1232 can be formed of a single piece of material to have a unitary or one-piece construction.

[0161] Eyeglasses 1200 include a computing device such as computer 1261, which may be of any suitable type to be carried by frame 1232 and, in one example, of a suitable size and shape to be at least partially disposed within one or more of temple pieces 1246 and 1247. In one embodiment, computer 1261 is of a size and shape similar to the size and shape of one of temple pieces 1246, 1247, and is thus disposed nearly completely, if not completely, within the structure and confines of such temple pieces 1246, 1247.

[0162] In one embodiment, the computer 1261 can be disposed in both temple pieces 1246, 1247. The computer 1261 can include one or more processors with memory, wireless communication circuitry, and a power supply. The computer 1261 includes low power circuitry, high speed circuitry, position circuitry, and a display processor. Various other examples can include these elements in different configurations or integrated together in different ways. Additional details about aspects of the computer 1261 can be implemented with reference to the following description.

[0163] The computer 1261 further includes a battery 1262 or other suitable portable power source. In one example, the battery 1262 is disposed in one of the temple pieces 1246 or the temple pieces 1247. Fig.12 In the glasses 1200 shown in FIG. 1 , a battery 1262 is shown disposed in the left temple piece 1246 and electrically coupled to the remainder of the computer 1261 disposed in the right temple piece 1247 using a connector 1274. The one or more input and output devices may include a connector or port (not shown) accessible from the exterior of the frame 1232 suitable for charging the battery 1262, a wireless receiver, transmitter or transceiver (not shown), or a combination of such devices.

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

[0165] In various examples, the glasses 1200 may include any number of input sensors or peripherals in addition to the camera 1269. The front piece 1233 is provided with an outward-facing, front-facing, front or outer surface 1266 that faces forward or away from the user when the glasses 1200 are mounted on the user's face; and an opposite inward-facing, rearward-facing, rear or inner surface 1267 that faces the user's face when the glasses 1200 are mounted on the user's face. Such sensors may include an inward-facing video sensor or digital imaging module, such as the camera 1269 that may be mounted or disposed on or within the inner surface 1267 of the front piece 1233 or elsewhere on the frame 1232 to face the user; and an outward-facing video sensor or digital imaging module, such as the camera 1269 that may be mounted or disposed on or within the outer surface 1266 of the front piece 1233 or elsewhere on the frame 1232 to face away from 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 1243 , 1244 (or lenses) to provide a mixed reality or augmented reality experience for a user of glasses 1200 .

[0166] The glasses 1200 also include an example of a camera control mechanism or user input mechanism, which includes a camera control button mounted on the frame 1232 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.

[0167] 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 frame 1232 adjacent to a surface of frame 1232 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 outer surface 1266 of frame 1232. It should be understood that the camera control button and capacitive touch button described above are merely two examples of tactile input mechanisms for single action control of camera 1269, and other examples may employ different single action tactile control arrangements.

[0168] Computer 1261 is configured to perform the methods described herein. In some examples, computer 1261 is coupled to one or more antennas for receiving signals from a GNSS and circuitry for processing the signals, wherein the antennas and circuitry are housed in glasses 1200. In some examples, computer 1261 is coupled to one or more wireless antennas and circuitry for sending and receiving wireless signals, wherein the antennas and circuitry are housed in glasses 1200. In some examples, multiple sets of antennas and circuitry are housed in glasses 1200. In some examples, the antennas and circuitry are configured to receive signals based on a device such as Bluetooth. TM , Bluetooth Low Energy TM , IEEE 802, IEEE 802.11az / be, and other communication protocols. In some examples, the PDR sensor is housed in the glasses 1200 and coupled to the computer 1261. In some examples, the glasses 1200 are a VR headset, in which the optical elements 1243, 1244 are opaque screens for displaying images to a user of the VR headset. In some examples, the computer 1261 is coupled to user interface elements such as a slider or touchpad 1276 and a button 1278. Long pressing the button 1278 resets the glasses 1200. The slider or touchpad 1276 and the button 1278 are used by the user to provide input to the computer 1261 and / or other electronic components of the glasses 1200. The glasses 1200 include one or more microphones 1282 coupled to the computer 1261. The glasses 1200 include one or more gyroscopes 1280.

[0169] Fig.13 A method 1300 for voice input for an AR wearable device is shown in accordance with some embodiments. The method 1300 is performed on an augmented reality (AR) wearable device. The method 1300 begins at operation 1302, where audio data is captured from a microphone of the AR wearable device, the audio data including speech of a user of the AR wearable device and / or generated by speech of a user of the AR wearable device. For example, the AR wearable device 602 captures audio data 613 using a microphone 603. The method 1300 continues at operation 1304, where an action is determined from a plurality of actions by processing the audio data. For example, the keyword module 652 and / or the ML module 614 generates a transcription 656, and the scan manager 626 identifies an action 643 within the transcription 656.

[0170] Method 1300 continues at operation 1306, where one or more applications associated with the action are selected. For example, scan manager 626 selects one or more applications 642 based on action 643 in transcription 656. Method 1300 continues at operation 1308, where an indication of the one or more applications is presented. For example, Figure 7As shown in , UI module 634 presents application 642 "Play Song Title" 706 and "Play Game Title" 708. Method 1300 continues at operation 1310, where the user's input is recognized as a selection of an application in one or more applications. For example, UI module 634 determines user intent 636 for user 646 to select application 642.

[0171] The method 1300 continues at operation 1312, where, in response to the selection of an application from the one or more applications, an application is enabled to access the audio data and, in some embodiments, the context data. For example, the scan manager 626 enables, runs, or executes the selected application 642, where the content data 612 and the transcription 656 are available to the application 642. In addition, the scan manager 626 ensures that the privacy 618 conditions are met before enabling the application 642 to access the transcription 656 or the context data 612.

[0172] The method 1300 may include one or more additional operations. The operations of the method 1300 may be performed in a different order. One or more of the operations of the method 1300 may be optional. The method 1300 may be performed by the client device 102, the system 600, the glasses 1200, or other electronic devices. A portion of the functions may be performed on a server computer or a host computer. 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.

[0173] Machine Architecture

[0174] Fig.141400 within which instructions 1410 (e.g., software, programs, applications, applet, app, or other executable code) may be executed for causing the machine 1400 to perform any one or more of the methodologies discussed herein. For example, the instructions 1410 may cause the machine 1400 to perform any one or more of the methodologies described herein. The instructions 1410 convert a general purpose, unprogrammed machine 1400 into a specific machine 1400 that is programmed to perform the functions described and illustrated in the manner described. The machine 1400 may operate as a standalone device or may be coupled (e.g., networked) to other machines. In a network deployment, the machine 1400 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 1400 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 1410 specifying actions to be taken by the machine 1400. In addition, although only a single machine 1400 is shown, the term "machine" should also be taken to include a collection of machines that individually or jointly execute instructions 1410 to perform any one or more of the methods discussed herein. For example, the machine 1400 may include any of the client device 102 or a number of server devices that form part of the messaging server system 108. In some examples, the machine 1400 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.

[0175] The machine 1400 may include a processor 1404, a memory 1406, and an input / output I / O component 1402, which may be configured to communicate with each other via a bus 1440. In an example, the processor 1404 (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 1408 that executes instructions 1410 and a processor 1412. The term "processor" is intended to include multi-core processors, which may include two or more independent processors (sometimes referred to as "cores") that can execute instructions simultaneously. Although Fig.14 Multiple processors 1404 are shown, but the machine 1400 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.

[0176] The memory 1406 includes a main memory 1414, a static memory 1416, and a storage unit 1418, which are all accessible by the processor 1404 via a bus 1440. The main memory 1406, the static memory 1416, and the storage unit 1418 store instructions 1410 that implement any one or more of the methods or functions described herein. The instructions 1410 may also reside, completely or partially, within the main memory 1414, within the static memory 1416, within the machine-readable medium 1420 within the storage unit 1418, within at least one of the processors 1404 (e.g., within a cache memory of a processor), or any suitable combination thereof during execution thereof by the machine 1400.

[0177] I / O components 1402 may include various components that receive input, provide output, generate output, send information, exchange information, capture measurements, etc. The specific I / O components 1402 included in a particular machine will depend on the type of machine. For example, a portable machine such as a mobile phone may include a touch input device or other such input mechanism, while a headless server machine will be less likely to include such a touch input device. It should be appreciated that I / O components 1402 may include Fig.141402. In various examples, the I / O components 1402 may include a user output component 1426 and a user input component 1428. The user output component 1426 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 1428 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 the location and force of a touch or touch gesture), an audio input component (e.g., a microphone), etc.

[0178] In other examples, the I / O component 1402 may include a biometric component 1430, a motion component 1432, an environment component 1434, or a position component 1436, as well as various other components. For example, the biometric component 1430 includes components for detecting expressions (e.g., hand expressions, facial expressions, voice expressions, body postures, or eye tracking), measuring biosignals (e.g., blood pressure, heart rate, body temperature, sweat, or brain waves), identifying people (e.g., voice recognition, retinal recognition, facial recognition, fingerprint recognition, or EEG-based recognition), etc. The motion component 1432 includes an acceleration sensor component (e.g., an accelerometer), a gravity sensor component, and a rotation sensor component (e.g., a gyroscope).

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

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

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

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

[0183] A variety of technologies may be used to achieve communication. The I / O components 1402 also include a communication component 1438 that is operable to couple the machine 1400 to the network 1422 or device 1424 via a corresponding coupling or connection. For example, the communication component 1438 may include a network interface component or another suitable device that interfaces with the network 1422. In other examples, the communication component 1438 may include a wired communication component, a wireless communication component, a cellular communication component, a near field communication (NFC) component, Parts (e.g. Low energy consumption), Components, and other communication components for providing communication via other modalities. Device 1424 can be another machine or any peripheral device of a variety of peripheral devices (e.g., a peripheral device coupled via USB).

[0184] In addition, the communication component 1438 can detect the identifier or include components operable to detect the identifier. For example, the communication component 1438 can include a radio frequency identification (RFID) tag reader component, an NFC smart tag detection component, an optical reader component (e.g., an optical sensor for detecting one-dimensional bar codes such as Universal Product Code (UPC) bar codes, multi-dimensional bar codes such as Quick Response (QR) codes, Aztec codes, Data Matrix, 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 derived via the communication component 1438, such as a location via Internet Protocol (IP) geolocation, a location via Internet Protocol (IP), ... The location of signal triangulation, the location of an NFC beacon signal via detection that can indicate a specific location, etc.

[0185] Various memories (e.g., main memory 1414, static memory 1416, and memory of processor 1404) and storage unit 1418 may store one or more sets of instructions and data structures (e.g., software) used by or implementing any one or more of the methods or functions described herein. When executed by processor 1404, these instructions (e.g., instructions 1410) cause various operations to implement the disclosed examples.

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

[0187] Software Architecture

[0188] Fig.151500 is a block diagram illustrating a software architecture 1504 that may be installed on any one or more of the devices described herein. The software architecture 1504 is supported by hardware such as a machine 1502 including a processor 1520, a memory 1526, and an I / O component 1538. In this example, the software architecture 1504 may be conceptualized as a stack of layers, where each layer provides specific functionality. The software architecture 1504 includes layers such as an operating system 1512, a library 1510, a framework 1508, and an application 1506. In operation, the application 1506 invokes an API call 1550 through the software stack and receives a message 1552 in response to the API call 1550.

[0189] The operating system 1512 manages hardware resources and provides public services. The operating system 1512 includes, for example, a kernel 1514, services 1516, and drivers 1522. The kernel 1514 serves as an abstraction layer between the hardware and other software layers. For example, the kernel 1514 provides functions such as memory management, processor management (e.g., scheduling), component management, networking, and security settings. Services 1516 can provide other public services to other software layers. Drivers 1522 are responsible for controlling or interfacing with the underlying hardware. For example, drivers 1522 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.

[0190] The library 1510 provides a common low-level infrastructure used by the application 1506. The library 1510 may include a system library 1518 (e.g., a C standard library) that provides functions such as memory allocation functions, string manipulation functions, mathematical functions, etc. In addition, the library 1510 may include an API library 1524, such as a media library (e.g., a library for supporting the presentation and manipulation of various media formats, such as Moving Picture Experts Group-4 (MPEG4), Advanced Video Coding (H.264 or AVC), Moving Picture Experts Group Layer-3 (MP3), Advanced Audio Coding (AAC), Adaptive Multi-Rate (AMR) audio codec, Joint Photographic Experts Group (JPEG or JPG), or Portable Network Graphics (PNG)), a graphics library (e.g., an OpenGL framework for 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 1510 may also include various other libraries 1528 to provide many other APIs to the application 1506 .

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

[0192] In an example, applications 1506 may include home applications 1536, contact applications 1530, browser applications 1532, reader applications 1534, positioning applications 1542, media applications 1544, messaging applications 1546, game applications 1548, and a broad category of other applications such as third-party applications 1540. Applications 1506 are programs that perform functions defined in the program. Various programming languages ​​may be used to create one or more of the applications 1506 structured in various ways, such as object-oriented programming languages ​​(e.g., Objective-C, Java, or C++) or procedural programming languages ​​(e.g., C or assembly language). In a specific example, third-party applications 1540 (e.g., applications created by entities other than the vendor of a particular platform using ANDROID TM or IOS TM Software Development Kit (SDK) can be used for mobile operating systems, such as IOS TM ANDROID TM , Phone, or other mobile operating system running on the mobile software. In this example, the third-party application 1540 can activate the API call 1550 provided by the operating system 1512 to facilitate the functions described in this article.

[0193] Processing components

[0194] Now go to Fig.16 , which shows a diagrammatic representation of a processing environment 1600 that includes a processor 1602, a processor 1606, and a processor 1608 (eg, a GPU, a CPU, or a combination thereof).

[0195] Processor 1602 is shown coupled to power source 1604 and is shown to include modules (permanently configured or temporarily instantiated), namely, audio processing component 1610, presentation component 1612, and application execution component 1614. Audio processing component 1610 is enabled to process audio data 613. For example, an example of audio processing component 1610 includes keyword module 652 and ML module 614 that process audio data 613. Presentation component 1612 presents an indication of application 642 on display 606 of AR wearable device 602. An example of presentation component 1612 is Figure 6UI module 634.

[0196] When the user 646 selects the application 642, the application execution component 1614 starts the application 642. An example of the application execution component 1614 is Figure 6 The scan manager 626 of FIG. 624 may include a processor 1602. The scan status 623 and other data may be in a memory associated with the processor 1602. As shown, the processor 1602 is communicatively coupled to both the processor 1606 and the processor 1608.

[0197] Glossary

[0198] 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 specific 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.

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

[0200] "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, a desktop computer, a laptop computer, a portable digital assistant (PDA), a smartphone, a tablet computer, an ultrabook, a netbook, a laptop computer, a multiprocessor system, a microprocessor-based or programmable consumer electronics product, a game console, a set-top box, or any other communication device that a user may use to access a network.

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

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

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

[0204] "Ephemeral messages" are messages that are accessible for a time-limited duration. 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.

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

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

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

Claims

1. A method performed on an augmented reality (AR) wearable device, the method comprising: capturing audio data from a microphone of an AR wearable device, the audio data comprising speech of a user of the AR wearable device; determining an action from a plurality of actions by processing the audio data; selecting one or more applications associated with the action; presenting an indication of the one or more applications; recognizing a user input as a selection of an application from among the one or more applications; as well as In response to selection of an application from among the one or more applications, an application capable of accessing the audio data is enabled.

2. The method according to claim 1, wherein: Processing the audio data to determine the action further comprises: sending the audio data and contextual data and instructions for the audio data to be processed to a host system via a wireless connection; receiving a transcription of the audio data from the host system; and The action is determined from the plurality of actions based on the transcription.

3. The method according to claim 1, wherein: The processing is based on the audio data, contextual data, and the plurality of actions.

4. The method according to claim 1, wherein: The audio data is first audio data, and wherein capturing the first audio data from a microphone of the AR wearable device comprises: capturing second audio data from the microphone; processing the second audio data based on the keyword to determine that the second audio data includes the keyword; and In response to the second audio data indicating a keyword, the first audio data is captured from a microphone of the AR wearable device.

5. The method according to claim 4, wherein: Processing the second audio data comprises: The second audio data is processed using a machine learning model to determine that the second audio data includes a keyword, wherein the machine learning model is trained to recognize a keyword through an utterance of a user.

6. The method according to claim 4, wherein: The first audio data is processed by sending the first audio data to a host device, and the second audio data is processed by the AR wearable device.

7. The method according to claim 1, further comprising: capturing an image using an image capture device of the AR wearable device; Determining a location of the AR wearable device; as well as A current time is accessed, wherein the context data includes one or more of: the image, the location, and the current time.

8. The method according to claim 1, wherein: The action is expressed by an action word or an action phrase spoken by the user of the AR wearable device.

9. The method according to claim 1, wherein: The audio data is first audio data, and wherein the method further comprises: capturing second audio data from the microphone; and The second audio data is processed to determine a selection of the application.

10. The method according to claim 1, wherein: Enabling applications to access the audio data and contextual data also includes: It is determined that a user has granted the application permission to access the audio data and the context data.

11. The method according to claim 1, further comprising: The application is associated with the action.

12. The method according to claim 1, wherein: The user's input includes a selection of a button of the AR wearable device or a touch of a touch panel of the AR wearable device.

13. The method according to claim 1, wherein: Presenting an indication of the one or more applications includes: Instructions for the one or more applications are played using a speaker of the AR wearable device.

14. The method according to claim 1, wherein: Presenting an indication of the one or more applications includes: Presenting indications of the one or more applications on an AR display of the AR wearable device.

15. The method according to claim 14, further comprising: presenting a selection shape on the AR display; as well as Based on the indication of the application being within the selection shape, the user's input is recognized as a selection of the application, wherein the position of the selection shape remains stable when the AR wearable device moves, and the position of the indication of the one or more applications moves according to the movement of the AR wearable device.

16. The method according to claim 14, further comprising: processing the user's input to recognize a gesture, wherein the input is movement of a user's appendage or utterance of the user's voice; and Based on the gesture indicating a selection of the application, the user's input is recognized as a selection of the application.

17. The method according to claim 1, wherein: The AR wearable device is AR glasses.

18. An augmented reality (AR) wearable device comprising: processor; as well as A memory storing instructions that, when executed by the processor, configure the AR wearable device to perform operations, the operations comprising: capturing audio data from a microphone of the AR wearable device, the audio data generated by speech of a user of the AR wearable device; processing the audio data to determine an action from a plurality of actions; selecting one or more applications associated with the action; presenting an indication of the one or more applications; recognizing a user input as a selection of an application from among the one or more applications; and In response to selection of an application from the one or more applications, an application capable of accessing the audio data and context data is enabled.

19. The AR wearable device according to claim 18, wherein: Processing the audio data to determine the action further comprises: sending the audio data and contextual data and instructions for the audio data to be processed to a host system via a wireless connection; receiving a transcription of the audio data from the host system; and The action is determined from the plurality of actions based on the transcription.

20. A non-transitory computer-readable storage medium comprising instructions that, when executed by an augmented reality (AR) wearable device, cause the AR wearable device to perform operations comprising: capturing audio data from a microphone of the AR wearable device, the audio data generated by speech of a user of the AR wearable device; processing the audio data to determine an action from a plurality of actions; selecting one or more applications associated with the action; presenting an indication of the one or more applications; recognizing a user input as a selection of an application from among the one or more applications; as well as In response to selection of an application from the one or more applications, an application capable of accessing the audio data and context data is enabled.