Voice controlled UI for ar wearable devices

Abstract

Systems, methods, and computer readable media for a voice controlled user interface (UI) for augmented reality (AR) wearable devices are disclosed. Embodiments are disclosed that enable a user to interact with an AR wearable device without using a physical user interface device. The application has a non-voice controlled UI mode and a voice controlled UI mode. The user selects a mode of the UI. An application running on the AR wearable device displays UI elements on a display of the AR wearable device. The UI element has a type. A predetermined action is associated with each of the UI element types. The predetermined action is displayed with other information and is used by the user to enable a corresponding UI element.

Description

[0001] Priority declaration

[0002] This application claims the benefit of U.S. patent application serial number 17 / 823,169, filed on August 30, 2022, the entire contents of which are incorporated herein by reference. Technical Field

[0003] Examples of the present disclosure generally relate to voice input for augmented reality (AR) wearable devices. More particularly, but not limitingly, examples of the present disclosure relate to voice input for invoking a user interface (UI) element by using a predetermined action associated with the type of UI element. 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 for interface controls on the wearable device. BRIEF DESCRIPTION OF THE DRAWINGS

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

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

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

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

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

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

[0011] Figure 6 An AR wearable device for providing a voice-controlled UI is shown according to some examples.

[0012] Figure 7An example display is shown in which an application displays a normal display on a display of an AR wearable device in accordance with some embodiments.

[0013] Figure 8 An example display is shown in which an application displays a voice UI mode on a display of an AR wearable device in accordance with some embodiments.

[0014] Fig. 9 Example displays of normal mode and voice UI mode for different UI element types are shown in accordance with some implementations.

[0015] Fig.10 Example displays of normal mode and voice UI mode for an option group UI element type are shown in accordance with some implementations.

[0016] Fig.11 A method for a voice-controlled UI for an AR wearable device is shown in accordance with some embodiments.

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

[0023] AR wearable device 602 is used as an illustrative device; however, those 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 AR applications, VR applications, MR applications, and both applications.

[0024] Typically, an AR wearable device 602 (e.g., AR glasses 1200) has limited physical user interface items such as buttons 1278. Some AR wearable devices 602 have a tactile UI such as one or two buttons 1278 or a touchpad 1276 on the frame 1232 of the AR wearable device 602 with which the user 616 interacts. In addition, an application 648 may have many UI elements 646 such as sliders, buttons, check boxes, etc. The number of UI elements 646 that the user 616 may want to access on the AR wearable device 602 is large. In addition, legacy applications 648 may not have developed voice UIs. In addition, typically, the user 616 may not be able to use the tactile UI because they are involved in activities such as cycling or jogging.

[0025] One challenge is how to make the UI element 646 of the application 648 available to the user 616 without the user 616 having to use the tactile 614 interaction with the UI element 646. The UI element 646 is displayed on the display 606 of the AR wearable device 602. This challenge is solved by an application 648 having a normal display 656 of the UI element 646 and a voice UI display 658 for the UI element 646. In the normal display 656, the UI element 646 is displayed normally. For example, a slider or button is just a slider or button like a slider or button seen in the windows operating system. In the voice UI mode 647, an additional voice UI label 662 is displayed to indicate to the user 616 what to say to invoke the UI element 646. In addition, the voice UI label 662 is generated by associating a predetermined action 636 with each UI element type 644. The action 636 is usually a verb for the user 616 to say to invoke the UI element 646. The action 636 is coupled with a label 650 that is used to mark the UI element 646 in the normal display 656 mode. The user 616 speaks the action 636 coupled with the label 650 to invoke the UI element 646. For example, for a button with the label 650 "Start", the user 616 would say "Press Start" to invoke the button. The predetermined action 636 coupled with the label 650 means that the audio data 618 is easy to process without full grammatical analysis, and the user 616 can more easily remember the action 636. In some embodiments, the neural network is trained to identify the predetermined action 636, and then the label 650 that comes after the predetermined action 636 is matched with the audio data 618. In some embodiments, this enables some or all of the audio data 618 processing to be performed on the AR wearable device 602 without sending the audio data 618 to be processed on the host computer.

[0026] Another challenge is how to enable voice UI display 658 for legacy applications 648. This challenge is solved by a separate UI module 638 that identifies UI element 646 being displayed by application 648 and generates voice UI display 658 for application 648. UI module 638 identifies when user 616 selects UI element 646 via voice UI mode 647, and notifies application 648 that UI element 646 has been selected so that application 648 can invoke event 652 associated with UI element 646. In this way, legacy applications can run on AR wearable device 602 without software updates to accommodate voice UI mode 647.

[0027] Networked computing environment

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

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

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

[0031] 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. Data exchange within the messaging system 100 is enabled and controlled through functionality available via a user interface (UI) of the messaging clients 104.

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

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

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

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

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

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

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

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

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

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

[0042] System Architecture

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

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

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

[0046] In addition, the collection management system 204 includes a curation interface 206 that allows a collection manager to manage and curate a particular content collection. For example, the curation interface 206 enables an event organizer to curate a collection of content related to a particular event (e.g., to delete inappropriate content or redundant messages). 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 may be paid to users to include user-generated content in a collection. In such a case, the collection management system 204 operates to automatically pay such users for use of their content.

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

[0048] 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 in which a particular media overlay should be provided to other users. The enhancement system 208 generates a media overlay that includes the uploaded content and associates the uploaded content with the selected geolocation.

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

[0050] 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 user icons or avatars (e.g., stored in the profile data 316) on a map to indicate the current or past locations of the user's "friends" in the context of the map, as well as media content (e.g., a collection of messages including photos and videos) generated by such friends. For example, on the map interface of the messaging client 104, messages posted by the user to the messaging system 100 from a particular 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 appropriate status avatars) via the messaging client 104, where the location and status information is similarly displayed to selected users within the context of the mapping interface of the messaging client 104.

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

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

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

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

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

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

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

[0058] The voice input system 216 supports the AR wearable device 602. The voice input system 216 receives requests from the AR wearable device 602 and responds to the requests. The request includes a request to process the audio data 618, wherein a transcription 632 is generated from the audio data 618. The transcription 632 is sent back to the AR wearable device 602. In some embodiments, the request to process the audio data 618 returns: an indication of an action in a plurality of predetermined actions 636, or an indication that none of the plurality of predetermined actions 636 is included in the audio data 618. The AR wearable device 602 can request other services from the voice input system 216, such as a request to download weights 626, 630, wherein the weights 626, 630 are used in a trained machine learning model such as a neural network.

[0059] Data Architecture

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0076] Other methods and algorithms suitable for face detection can be used. For example, in some examples, landmarks are used to locate features, which represent distinguishable points that are present in most of the images considered. For example, for facial landmarks, the location of the left eye pupil can be used. If the initial landmarks are not identifiable (for example, when a person is wearing 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 is the average of the aligned training shapes.

[0077] In some examples, a landmark search begins with an average shape that aligns with the location and size of a face determined by a global face detector. Such a search then repeats the steps of suggesting tentative shapes by adjusting the positions of shape points 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, template matching alone is unreliable, and the shape model pools the results of weak template matches to form a stronger overall classifier. The entire search is repeated at each level of the image pyramid from coarse to fine resolution.

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

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

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

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

[0082] A collection may also constitute a "live story" that is a collection of content from multiple users, which is created manually, automatically, or using a combination of manual and automatic techniques. For example, a "live story" may constitute a curated stream of user-submitted content from various locations and events. A user whose client device has location services enabled and who is 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. A live story 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.

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

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

[0085] Data communication architecture

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0100] Time-based access restriction architecture

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

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

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

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

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

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

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

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

[0109] 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 an indicia (e.g., an 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 of a particular transient message 502 has expired, the transient timer system 202 causes the messaging client 104 to no longer display an indicia (e.g., an icon or text identification) associated with the transient message 502.

[0110] Voice-controlled UI for AR wearables

[0111] Figure 6 FIG. 6 shows an AR wearable device 602 for providing a voice-controlled UI according to some examples. In some embodiments, the AR wearable device 602 is Fig.10 The AR wearable device 602 communicates with the messaging server system 108 or the client device 102, both of which can perform one or more of the operations described herein.

[0112] Input / output (IO) devices 604 include devices that enable a user 616 to interact with the AR wearable device 602. For example, the IO devices 604 include a display 606, a speaker, a microphone 610, buttons 1278, a touchpad 1276, and the like.

[0113] Sensors 608 include gyroscopes 1280, light sensors, image sensors or cameras 1269, positioning sensors, clocks, etc. Some devices, such as gyroscopes 1280, enable user 616 to interact with AR wearable device 602 and act as sensors 608. For example, user 616 may move AR wearable device 602 to transmit input to AR wearable device 602. However, user 616 may move AR wearable device 602 without the intention of transmitting input to AR wearable device 602.

[0114] According to some examples, sensor 608 includes wireless communication. Wireless communication includes low energy (LE) Bluetooth, Institute of Electrical and Electronics Engineers (IEEE) 802.11 communication standards, proprietary communication standards, and 3GPP communication standards. Wireless communication can be used to determine the location and / or orientation of system 600, so wireless communication can also be considered as sensor 608. IO device 604 includes an antenna and transceiver circuit for performing wireless communication. Wireless communication can be performed by a dedicated chip that is part of AR wearable device 602. Microphone 610 generates audio data 618 based on the voice 612 of user 616.

[0115] User 617 is a data structure representing user 616 of AR wearable device 602. User 617 indicates data about user 616 stored within AR wearable device 602. Input from user 616 may be indicated based on voice 612 of user 616, position of user 616 changing or remaining the same, tactile 614 input from user 616 such as a button press, and / or gestures from user 616 such as user 616's finger circling UI element 646, which would be detected by analyzing images captured by AR wearable device 602 or by a motion detector attached to an appendage of user 616.

[0116] Application 648 is software, firmware, and / or hardware that resides in whole or in part on AR wearable device 602 and provides functionality. Application 648 provides a user interface displayed on display 606, see Figure 7. The user interface includes a UI element 646, which includes a label 650, a UI element type 654, and an event 652. The label 650 is the text portion of the UI element 646 and may include graphics, icons, text, etc. In some embodiments, the label 650 is not displayed as part of the user interface. The UI element type 654 is the type of UI element such as a button, a slider, a text field, a check box, an option group, etc. An event 652 is an operation to be performed when the user 616 selects the corresponding UI element 646. The normal display 656 is the display of the UI element 646 without the voice UI mode 647 enabled. The voice UI display 658 is the display of the UI element 646 when the voice UI mode 647 is enabled. In some embodiments, the voice UI tag 662 includes a label 650 having an action 636 that matches the UI element type 654 as described in Table 1.

[0117] Scan state 624 indicates whether voice UI mode 647 is enabled or not enabled. In voice UI mode 647, voice UI display 658 is displayed, wherein action 636 is associated with UI element type 644 and displayed on display 606 in association with UI element 646 as voice UI label 662. In addition, voice-controlled UI 620 is active and audio data 618 is processed to determine whether UI element 646 has been selected by user 616. In normal mode 649, normal display 656 is displayed, wherein action 636 is not displayed in conjunction with UI element 646, and audio data 618 is not processed to determine selection of UI element 646.

[0118] The keyword module 622 identifies a keyword within the audio data 618 and determines that a command 660 will follow the keyword. For example, "Hey, glasses" can be a keyword, and then the audio data 618 following "Hey, glasses" is a command 660. The keyword module 622 indicates to the machine learning (ML) module 628 that the keyword has been identified. The ML module 628 and / or the keyword module 622 can be a machine learning model such as a neural network or other type of machine learning model. The ML module 628 then generates a transcription 632 of the remaining audio data 618. The functions of the keyword module 622 and the ML module 628 can be divided differently between the two modules, there can be more than two modules, or there can be only one module. In addition, the ML module 628 and / or the keyword module 622 can send the audio data 618 to a remote server for processing. For example, the AR wearable device 602 is wirelessly connected to a host system such as an application server 114 or a client device 102. The ML module 628 can send a request to the application server 114 and / or the client device 102 using the wireless connection. The ML module 628 then receives a response, which may be a transcription 632 or an indication of a keyword, command 660 , or action 636 .

[0119] In some implementations, the UI module 638 manages input from the user 616 and identifies "voice mode" as a command 660 from the transcription 632 and changes the scan state 624 to voice UI mode 647. In voice UI mode 647, the audio data 618 is processed by the ML module 628, where the transcription 632 is generated without requiring a keyword at the beginning. In some implementations, the keyword must be a prefix before the command 660.

[0120] In response to the UI module 638 determining that the scan state 624 is or has just changed to the voice UI mode 647, the UI module 638 indicates to the application 648 that the scan state 624 is the voice UI mode 647. The application 648 modifies or switches its UI element 646 from the normal display 656 to the voice UI display 658. In some implementations, the UI module 638 modifies the display of the UI element 646 of the application 648 to supplement the normal display 656 with the voice UI display 658. The voice UI display 658 indicates what the user 616 should say in order to select the UI element 646.

[0121] In some implementations, there is a subset of actions 636 associated with UI element types 644, such that the ML module 628 only needs to consider the subset of actions 636. By having the ML module 628 identify a limited number of actions 636, the processing of the audio data 618 can be simplified. For example, the ML module 628 can be trained by, for example, the voice input system 216 to have weights 630 so that the ML module 628 recognizes the actions 636. And then, the UI module 638 matches the rest of the audio data 618 with the label 650 displayed on the display 606 to determine which UI element 646 the user 616 selected.

[0122] After being notified by voice-controlled UI 620 that AR wearable device 602 has entered scanning state 624 of voice UI mode 647, application 648 sends label 650 and UI element type 654 to voice-controlled UI 620 for each UI element 646. According to some embodiments, UI module 638 sends action 636, which may be in text format, to match each of UI element types 654.

[0123] In some implementations, for example, to support legacy applications 648, the UI module 638 determines labels 650 and UI element types 654 for UI elements 646 displayed on the display 606 of the AR wearable device 602. The UI module 638 then determines an action 636 for each of the UI elements 646 and updates the normal display 656 to a voice UI display 658. In this way, legacy applications 648 can be used with the voice UI mode 647.

[0124] UI module 638 takes the transcription 632 and determines which action 636 was spoken or issued by user 616. UI module 638 then matches the next portion or remainder of the transcription 632 to the label 650 of the displayed UI element 646. If UI module 638 finds a match that is a match of user intent 640 with a probability above or exceeding a threshold, UI module 638 indicates to application 648 that UI element 646 was selected. Application 648 will then cause event 652 to be executed, invoked, or implemented.

[0125] In some implementations, if multiple matches are found between the transcription 632 and the action 636 and / or label 650 , the UI module 638 relabels the matching UI elements 646 with new labels such as “1,” “2,” “3,” etc. The user 616 then speaks the new label to select the UI element 646 .

[0126] Table 1 illustrates an implementation of the action mapping 634. UI element types are mapped to actions. For example, a UI element type 654 of a button is mapped to an action 636 of "press". The predetermined actions 636 for different UI element types 644 simplify the training of the ML module 628 and / or the keyword module 622. In some implementations, the ML module 628 resides in the AR wearable device 602 and is trained to identify actions 636 in the audio data 618. The audio data 618 following the action 636 is then compared to the label 650 to generate a likelihood or probability of a match with the user intent 640. In some implementations, the audio data 618 following the action 636 is sent to the voice input system 216 or the client device 102 to generate the transcription 632. In some implementations, the label 650 may not be displayed in the normal display 658, but may be used as an indication of the functionality of the UI element type 644. For example, in Fig. 9 , when the slider 902 is displayed in the normal mode 904, the slider 902 may not display "volume" 908, but the function "volume" may be used when "increase volume" 912 and "decrease volume" 914 are displayed in the voice UI mode 906. In addition, the predetermined actions 636 enable the UI module 638 to generate a voice UI display 658 for the legacy application 648. In addition, the predetermined actions 636 enable the user 616 to remember a limited set of actions 636, and the actions 636 for the UI element type 654 are predictable.

[0127]

[0128] Figure 7 An example display 606 is shown in accordance with some embodiments, where an application 648 displays a normal display 656 on the display 606 of the AR wearable device 602. The application 648 for a timer displays time 702, start 704, and reset 706. The UI elements 646 are start 704 and reset 706. The label 650 for start 704 is "start" and the UI element type 654 is a button. The label 650 for reset 706 is "reset" and the UI element type 654 is a button.

[0129] Figure 8An example display 606 is shown in accordance with some embodiments, wherein an application 648 displays a voice UI display 658 on the display 606 of an AR wearable device 602. The voice UI display 658 includes "Press to Start" 802 and "Press to Reset" 804. "Press to Start" 802 is formed by the action 636 of "Press" associated with the UI element type 644 of button. The label 650 for the button is "Start". Therefore, the voice UI display 658 includes "Press to Start" 802. "Press to Reset" 804 is formed in the same manner as "Press to Start" 802. The UI module 638 or application 648 displays "Press to Start" 802 and "Press to Reset" 804. For example, in the case where the application 648 is a legacy application 648, the UI module 638 displays "Press to Start" 802 and "Press to Reset" 804 because, for legacy applications, as described above, the UI module 638 determines the label 650 and UI element type 654 for the UI element 646 displayed on the display 606 of the AR wearable device 602.

[0130] Fig. 9 An example display of a normal display 656 and a voice UI display 658 for different UI element types 644 according to some embodiments is shown. The slider 902 in normal mode 904 has a label 650 of "volume" that is not displayed in normal mode 904. In voice UI mode 906, the slider 902 has voice UI labels 662 "increase volume" 912 and "decrease volume" 914 added by the application 648 or UI module 638. In some embodiments, "volume" 908 is also added in voice UI mode 906.

[0131] Text field 916 is another UI element type 644. Normal mode 918 shows a text field with a label 650 of "Song" 920. Voice UI mode 922 includes "Enter Song" displayed by application 648 or UI module 638. Action 636 is based on Table 1, where UI element type 644 indicates an action 636 of "Enter."

[0132] Checkbox 928 is another UI element type 644. Normal mode 930 shows a checkbox with labels 650 of "yes" and "no". Voice UI mode 932 includes "enable yes" and "enable no" displayed by application 648 or UI module 638. Action 636 is based on Table 1, where UI element type 644 checkbox 928 indicates an action 636 of "enable".

[0133] Fig.10An example normal display 656 and voice UI display 658 for an option group 1002 UI element type 644 are shown in accordance with some embodiments. Option group 1002 is another UI element type 644. Normal mode 1004 shows an option group label 650 of "Pick a color." Voice UI mode 1006 includes "Pick a color [blue, red, or green]" displayed by application 648 or UI module 638. Action 636 is based on Table 1, where the option group UI element type 644 indicates an action 636 of "Pick." In this example, a label or tag 650 of an option box or selection button is incorporated into the voice UI mode 1006. For example, Figures 7 to 9 As shown, the voice UI indicia 662 of the voice UI display 658 may include a special outline, font, bubble, icon 1010, or another indication that the user 616 will utter or speak the words in the voice UI display 658.

[0134] Fig.11 A method 1100 for a voice-controlled UI for an AR wearable device according to some embodiments is shown. The method 1100 starts at operation 1102, where a user starts an AR application. For example, the user 616 can start the application 648. At operation 1104, the method 1100 continues to determine whether the UI voice mode is enabled. For example, the UI module 638 determines whether the scanning state 624 is in voice UI mode 647 or in normal mode 649. If the voice UI mode 647 is normal mode 649, the method 1100 continues at operation 1106, where the user turns on the voice UI mode. For example, the user 616 generates audio data 618 including a command 660 such as "Hey, glasses, voice mode". The audio data 618 is processed at operation 1112, where the AR wearable device or the backend processes the audio data. For example, the keyword module 622, the ML module 628, and / or the backend host / server processes the audio data 618.

[0135] At operation 1110, method 1100 continues to determine whether UI voice mode is enabled. If audio data 618 does not include a command 660 for enabling voice mode, method 1100 returns to operation 1106. If audio data 618 indicates that voice mode is to be enabled, voice-controlled UI 620 changes scan state 624 to the value of voice UI mode 647. Method 1100 continues to operation 1108, where the application displays a tooltip. For example, the tooltip is Figure 8 , where “Press to start” 802 and “Press to reset” 804 are displayed on the display 606 of the AR wearable device 602. According to some embodiments, the term tooltip may be used instead of the voice UI mark 662 or the voice UI display 658.

[0136] If the user does not speak, the method 1100 will continue at operation 1120, where a timeout is started. For example, there may be a timeout period such as 10 seconds or another time. The method 1100 continues at operation 1128, where a timeout occurs. For example, if the user 616 does not speak for a period of time greater than the timeout period, a timeout occurs, which causes the method 1100 to return to operation 1130.

[0137] If the user 616 does speak, the method 1100 continues at operation 1118, where the user speaks. For example, the user 616 generates audio data 618. The method 1100 continues at operation 1112, where the AR wearable device or backend processes the audio data. For example, the keyword module 622, the ML module 628, and / or the backend host / server processes the audio data 618.

[0138] The method 1100 continues at operation 1122 where the transcription is matched to the voice UI tag. For example, the transcription 632 is compared to the voice UI tag 662 to determine if there is a match.

[0139] The method 1100 continues at operation 1124 where it is determined whether the voice UI tag was found. For example, if the user 616 said "press start" and the transcription 632 was "press start", this would be consistent with Figure 8 The voice UI tag 662 of “Press to start” 804 matches.

[0140] If the voice UI tag is found, the method 1100 continues at operation 1126, where an event associated with the voice UI tag is triggered. Continuing with the above example, the voice UI tag 662 of "press start" 804 will correspond to the event 652, which will be called by the application 648. The method 1100 continues to operation 1130.

[0141] If the voice UI tag is not found, method 1100 continues to operation 1130, where it is determined whether the UI voice mode is disabled. For example, UI module 638 determines whether the scan state 624 is in voice UI mode 647. If the UI voice mode is disabled, method 1100 continues to operation 1132, where the UI voice mode is stopped. For example, UI module 638 can set the scan state 624 to normal mode 649 and notify application 648 that the scan state 624 is no longer in voice UI mode 647. Display 606 is updated to normal display 656. If the voice mode is not disabled, method 1100 returns to operation 1108 or operation 1118 depending on the state of display 606.

[0142] If in operation 1124, there are multiple matches between the transcription and the voice UI tags, or the match with the user intent 640 is uncertain to be greater than a threshold or exceeds a threshold, the method 1100 can perform a disambiguation step. For example, the method 1100 displays a tag next to each of the voice UI tags 662 on the display 606, or replaces each of the voice UI tags 662 with a number such as "1", "2", "3", etc. The user 616 then selects the number of voice UI tags 662 to complete the user intent 640. Other methods can be used to disambiguate between multiple matches. For example, the possible voice UI tags 662 that match can flash, and text can be displayed for the user 616 to repeat their selection.

[0143] 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 another electronic device. 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.

[0144] Fig.12 1 is a stereoscopic view of a wearable electronic device in the form of glasses 1200 according to some examples. Glasses 1200 are eyewear products including electronic products 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 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 further includes a left end portion 1241 and a right end portion 1242. A first optical element or left optical element 1244 and a 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.

[0145] 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 corresponding left end portion 1241 and right end portion 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 can include: a first portion 1251 coupled to the corresponding end portion 1241 or end portion 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 integrated construction. In one example, the entire frame 1232 can be formed of a single piece of material to have a unitary or integrated construction.

[0146] Eyeglasses 1200 include a computing device such as computer 1261, which can be of any suitable type to be carried by frame 1232 and, in some examples, of a suitable size and shape to be at least partially disposed in one or more of temple pieces 1246, 1247. In one example, computer 1261 has 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 piece 1246, 1247.

[0147] In one example, computer 1261 can be arranged in both temple piece 1246 and temple piece 1247. Computer 1261 can include one or more processors with memory, wireless communication circuit system and power supply. Computer 1261 includes low power circuit system, high speed circuit system, positioning circuit system and display processor. Various other examples can include these elements in different configurations or these elements integrated together in different ways. Additional details about various aspects of computer 1261 can be implemented with reference to the following description.

[0148] 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.12In the illustrated eyeglasses 1200, 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.

[0149] 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 related to the camera 1269 will be further described with reference to only a single camera 1269, but it should be understood that these features can be applicable to both cameras 1269 in appropriate examples.

[0150] 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 element 1243, optical element 1244 (or lenses) to provide a mixed reality or augmented reality experience for the user of glasses 1200.

[0151] 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 push 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.

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

[0153] 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, for example, Bluetooth. TM , Bluetooth Low Energy TM, IEEE 802, IEEE 802.11az / be, LTE, proprietary communication standards, 3GPP, etc. to operate. 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 VR headsets, wherein the optical elements 1243 and 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.

[0154] Fig.13 A method 1300 for voice input for an AR wearable device according to some embodiments is shown. The method 1300 is performed on an augmented reality (AR) wearable device. The method 1300 starts at operation 1302, where a notification is sent to an application that a voice UI mode is enabled. For example, the voice-controlled UI 620 sends an indication, such as a process call, that the scan state 624 is in voice UI mode 647 to the application 648. The method 1300 continues at operation 1304, where an indication of a UI element is received from the application, the UI element indicating a label and a UI element type. For example, the application 648 sends an indication of one or more UI elements 646 currently being displayed on the display 606 of the AR wearable device 602 to the UI module 638.

[0155] Method 1300 continues at operation 1306 where the tag is associated with an action corresponding to the UI element type. For example, UI module 638 determines action 636 based on UI element type 654 sent to UI module 638 from application 648.

[0156] The method 1300 continues at operation 1308, where audio data is captured from a microphone of the AR wearable device, the audio data being generated by the user's speech. For example, the microphone 610 generates audio data 618 based on the voice 612 or speech of the user 616. The method 1300 continues at operation 1310, where the audio data is processed to determine that the audio data includes an action and a label. For example, the keyword module 622, the ML module 628, or a remote host computer processes the audio data 618 to generate a transcription 632. The UI module 638 then matches the transcription 632 with the action 636 and the label 650 to determine that the UI element 646 has been selected.

[0157] Method 1300 continues at operation 1312, where an indication that the UI element is activated is sent to the application. For example, UI module 638 sends an indication that UI element 646 has been selected to application 648. Application 648 executes event 652 in response to the notification that UI element 646 has been selected.

[0158] 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 another electronic device. 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, such as processing the audio data 618.

[0159] Machine Architecture

[0160] Fig.141400 within which instructions 1410 (e.g., software, programs, applications, applet, app, or other executable code) may be executed to cause the machine 1400 to perform any one or more of the methods discussed herein. For example, the instructions 1410 may cause the machine 1400 to perform any one or more of the methods described herein. The instructions 1410 transform a general-purpose, non-programmed 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 networked 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 plurality of server devices forming 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.

[0161] 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 a multi-core processor, which may include two or more independent processors (sometimes referred to as "cores") that may 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.

[0162] 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 within any suitable combination thereof during execution thereof by the machine 1400.

[0163] I / O components 1402 may include various components for receiving input, providing output, generating output, transmitting information, exchanging information, capturing 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 is to be understood 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 location and force of a touch or touch gesture), an audio input component (e.g., a microphone), etc.

[0164] In another example, 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 gestures, or eye tracking), measuring biosignals (e.g., blood pressure, heart rate, body temperature, sweating, or brain waves), identifying people (e.g., voice recognition, retinal recognition, facial recognition, fingerprint recognition, or EEG-based recognition), etc. The motion component 1432 includes an acceleration sensor component (e.g., an accelerometer), a gravity sensor component, and a rotation sensor component (e.g., a gyroscope).

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

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

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

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

[0169] Various technologies may be used to implement communications. The I / O components 1402 also include a communications 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 communications component 1438 may include a network interface component or other suitable device that interfaces with the network 1422. In other examples, the communications component 1438 may include a wired communications component, a wireless communications component, a cellular communications component, a near field communications (NFC) component, a wireless communications ... Components (e.g. Low energy consumption), Device 1424 may be another machine or any of a variety of peripherals (eg, a peripheral coupled via USB).

[0170] In addition, the communication component 1438 can detect the identification, or include a component that is operable to detect the identification. For example, the communication component 1438 may include a radio frequency identification (RFID) tag reader component, an NFC smart tag detection component, an optical reader component (e.g., an optical sensor for detecting one-dimensional bar codes such as universal product codes (UPC) bar codes, multi-dimensional bar codes such as quick response (QR) codes, Aztec codes, data matrix, data symbols (Dataglyph), MaxiCode, PDF417, UltraCode, UCC RSS-2D bar codes, and other optical codes) or an acoustic detection component (e.g., a microphone for identifying tagged audio signals). In addition, various information can be obtained via the communication component 1438, such as positioning via Internet Protocol (IP) geolocation, obtaining a location ... and obtaining a location via Internet Protocol (IP) geolocation. Positioning is obtained by signal triangulation, positioning is obtained via detection of NFC beacon signals that can indicate a specific position, etc.

[0171] 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) that embody or are used by any one or more of the methods or functions described herein. These instructions (e.g., instructions 1410) when executed by processor 1404 cause various operations to implement the disclosed examples.

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

[0173] Software Architecture

[0174] Fig.151500 is a block diagram illustrating a software architecture 1504 that can 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, which includes a processor 1520, a memory 1526, and an I / O component 1538. In this example, the software architecture 1504 can 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 enables an API call 1550 through the software stack and receives a message 1552 in response to the API call 1550.

[0175] 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 acts as an abstraction layer between the hardware and other software layers. For example, the kernel 1514 provides memory management, processor management (e.g., scheduling), component management, networking and security settings, and other functions. 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.

[0176] The libraries 1510 provide a common low-level infrastructure used by the applications 1506. The libraries 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 libraries 1510 may include an API library 1524, such as a media library (e.g., a library for supporting presentation and manipulation of various media formats such as Moving Picture Experts Group-4 (MPEG4), Advanced Video Coding (H.264 or AVC), Moving Picture Experts Group Layer-3 (MP3), Advanced Audio Coding (AAC), Adaptive Multi-Rate (AMR) audio codec, Joint Photographic Experts Group (JPEG or JPG), or Portable Network Graphics (PNG)), a graphics library (e.g., an OpenGL framework for rendering in two dimensions (2D) and three dimensions (3D) in graphics content on a display), a database library (e.g., SQLite providing various relational database functions), a web library (e.g., WebKit providing web browsing functions), etc. The library 1510 may also include various other libraries 1528 to provide many other APIs to the application 1506 .

[0177] 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, advanced resource management, and advanced 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 specific operating system or platform.

[0178] In an example, applications 1506 may include a home application 1536, a contacts application 1530, a browser application 1532, a reader application 1534, a positioning application 1542, a media application 1544, a messaging application 1546, a game application 1548, and a variety of other applications such as third-party applications 1540. Application 1506 is a program that executes the functions defined in the program. Various programming languages ​​can be used to create one or more of the applications 1506 constructed in various ways, such as an object-oriented programming language (e.g., Objective-C, Java, or C++) or a procedural programming language (e.g., C language or assembly language). In a specific example, third-party application 1540 (e.g., a third-party application created by an entity other than the vendor of a particular platform using ANDROID TM or IOS TM Software Development Kit (SDK) can be used to develop applications on platforms such as IOS TM ANDROID TM , Mobile software running on the mobile operating system of the phone or another mobile operating system. In this example, third-party applications 1540 can enable APIs 1550 provided by the operating system 1512 to facilitate the functions described herein.

[0179] Processing components

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

[0181] The processor 1602 is shown coupled to a power source 1604 and includes modules (permanently configured or temporarily instantiated), namely, an audio processing component 1610, a rendering component 1612, and a UI element execution component 1614. The audio processing component 1610 is enabled to process audio data 618. For example, an example of the audio processing component 1610 includes a keyword module 622 and an ML module 628. The rendering component 1612 renders a voice UI display 658 on the display 606 of the AR wearable device 602. An example of the rendering component 1612 is Figure 6UI module 638 and application 648.

[0182] When user 616 selects UI element 646, UI element execution component 1614 enables event 652. An example of UI element execution component 1614 is Figure 6 The scanning state 624 and other data may be located 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. In addition, the processor 1602 may be communicatively coupled to a communication component that provides wireless communications to other devices such as the application server 114 and the voice input system 216.

[0183] Glossary

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

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

[0186] "Client Device" refers to any machine that interfaces with a communication network to obtain resources from one or more server systems or other client devices. A client device may be, but is not limited to, a mobile phone, AR glasses, VR glasses, AR wearables, desktop computers, laptop computers, portable digital assistants (PDAs), smart phones, tablet computers, ultrabooks, netbooks, laptop computers, multiprocessor systems, microprocessor-based or programmable consumer electronics, game consoles, set-top boxes, or any other communication device that a user may use to access a network.

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

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

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

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

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

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

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

Claims

1. A method performed on an augmented reality (AR) wearable device, the method comprising: Send a notification to the application that the voice user interface (UI) mode is enabled; receiving an indication of a UI element from the application, the UI element indicating a label and a UI element type; associating the label with an action corresponding to the UI element type; capturing audio data from a microphone of the AR wearable device, the audio data being generated by speech of the user; processing the audio data to determine that the audio data includes the action and the label; as well as An indication is sent to the application that the UI element is activated.

2. The method according to claim 1, wherein: The UI element type is one of a button, a slider, a text field, a check box, or an option group, wherein the label is text.

3. The method according to claim 1, wherein: The tag is a first tag, the UI element type is a first UI element type, the UI element is a first UI element, the audio data is a first audio data, the utterance is a first utterance, and wherein the method further comprises: determining a second label and a second UI element type for a second UI element displayed on the display by the legacy application; associating the second label with a second action corresponding to the second UI element type; capturing second audio data from a microphone of the AR wearable device, the second audio data being generated by a second utterance of the user; processing the second audio data to determine that the second audio data includes the second action and the second label; and A second indication that the second UI element is activated is sent to the legacy application.

4. The method according to claim 1, further comprising: An indication of the UI element with the label is displayed on a display of the AR wearable device.

5. 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, the second audio data generated by the user's speech; processing the second audio data to determine that the second audio data indicates a command for enabling the voice UI mode; and Enables the voice UI mode.

6. The method according to claim 5, wherein: The second audio data is processed using a first machine learning model, and the first audio data is processed by a second machine learning model.

7. The method according to claim 5, further comprising: In response to enabling the voice UI mode, displaying a voice UI mark for the UI element on a display of the AR wearable device, the voice UI mark including the action and the label.

8. The method according to claim 7, wherein: The voice UI mark also includes: a label of a selection button, and the UI element includes the selection button.

9. The method according to claim 7, further comprising: An icon is displayed on a display of the AR wearable device to indicate that the user is to speak the voice UI mark to select the UI element.

10. The method according to claim 7, further comprising: After said sending, disabling said voice UI mode; as well as The voice UI mark for the UI element is removed.

11. The method according to claim 7, wherein: The label is not displayed as part of displaying the UI element.

12. The method according to claim 1, wherein: The processing of the audio data further comprises: sending the audio data to a host computer having instructions for processing the audio data; and A transcription of the audio data is received from the host computer.

13. The method according to claim 1, further comprising: The action is retrieved based on the UI element type from a data structure that associates actions with UI element types.

14. The method according to claim 13, wherein: The processing also includes: processing a first portion of the audio data using a first neural network trained to recognize the action to determine that the audio data includes the action; and A second portion of the audio data is processed using a machine learning model to determine that the audio data includes the label.

15. The method according to claim 1, wherein: The audio data is first audio data, and wherein the method further comprises: receiving an indication of a UI element from the application, the UI element indicating a label and a UI element type; associating the label with an action corresponding to the UI element type; capturing second audio data from a microphone of the AR wearable device, the second audio data being generated by an utterance of the user; processing the second audio data to generate a transcription of the audio data; matching the label and the action with the transcription; and In response to a plurality of labels and actions matching the transcription, for each of the plurality of labels and actions, displaying on the display an indication of what the user should say to select a UI element corresponding to the label and action in the plurality of labels and actions.

16. The method according to claim 1, further comprising: Executes the event associated with the UI element.

17. The method according to claim 1, further comprising: receiving an indication of a UI element from the application; as well as A predetermined action corresponding to the UI element is sent to the application.

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 comprising: Send a notification to the application that the voice user interface (UI) mode is enabled; receiving an indication of a UI element from the application, the UI element indicating a label and a UI element type; associating the label with an action corresponding to the UI element type; capturing audio data from a microphone of the AR wearable device, the audio data being generated by speech of the user; processing the audio data to determine that the audio data includes the action and the label; and An indication is sent to the application that the UI element is activated.

19. The AR wearable device according to claim 18, wherein: The audio data is first audio data, and wherein the operation further comprises: capturing second audio data from the microphone, the second audio data generated by the user's speech; processing the second audio data to determine that the second audio data indicates a command for enabling the voice UI mode; and Enables the voice UI mode.

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: Send a notification to the application that the voice user interface (UI) mode is enabled; receiving an indication of a UI element from the application, the UI element indicating a label and a UI element type; associating the label with an action corresponding to the UI element type; capturing audio data from a microphone of the AR wearable device, the audio data being generated by speech of the user; processing the audio data to determine that the audio data includes the action and the label; as well as An indication is sent to the application that the UI element is activated.

Images