Selecting a tilt angle for an ar display

Abstract

Systems, methods, and computer readable media for selecting an angle of tilt of an augmented reality (AR) display of an AR wearable device. Some examples of the present disclosure capture simulation data of a gaze point when a user performs a task using an application residing on an AR wearable device. A tilt angle of the AR display is selected based on including more gaze points within a field of view (FOV) of the AR display than gaze points outside the FOV. In some examples, an AR wearable device having a fixed vertical tilt angle for an AR display is manufactured. In some examples, the AR wearable device may dynamically adjust the vertical tilt angle of the AR display according to an application that a user of the AR wearable device may use or is using.

Description

[0001] Priority declaration

[0002] This application claims the benefit of U.S. Patent Application No. 17 / 930,263, filed on September 7, 2022, the entire contents of which are incorporated herein by reference. Technical Field

[0003] Examples of the present disclosure generally relate to selecting a tilt angle of an augmented reality (AR) display of an AR wearable device. More specifically, but not by way of limitation, examples of the present disclosure relate to capturing simulation data of gaze fixations and selecting a tilt angle that accommodates the gaze fixations for applications and tasks performed by a user of the AR wearable device. Background Art

[0004] Users increasingly expect virtual reality (VR), mixed reality (MR), and augmented reality (AR) wearable devices to operate in a more user-friendly manner and have more functionality. However, typically, wearable device displays are limited, and AR wearable devices are limited in their ability to provide additional functionality. 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 most significant digit or digits in a reference numeral refer to the figure number in which the element is first introduced. Some non-limiting examples are shown in the accompanying drawings, in which:

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

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

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

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

[0010] Figure 5 is a flow chart of an access restriction process according to some examples.

[0011] Figure 6 A system for selecting a tilt angle of an AR display according to some examples is shown.

[0012] Figure 7 A system for selecting a tilt angle of an AR display according to some examples is shown.

[0013] Figure 8 Vertical tilt angles are shown according to some examples.

[0014] Fig. 9 Vertical tilt angles are shown according to some examples.

[0015] Fig.10 Graphs according to some examples are shown.

[0016] Fig.11 Graphs according to some examples are shown.

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

[0018] Fig.13 Methods for selecting a tilt angle of an AR display according to some examples are 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. Usually, it is not necessary to show in detail known instruction examples, protocols, structures and techniques.

[0023] The term AR wearable device is used as an illustrative device; however, one skilled in the art will recognize that the methods, systems, and computer-readable media disclosed herein are applicable to other wearable devices including VR wearable devices and MR wearable devices.

[0024] The AR wearable device 602, such as the AR glasses 1200, has a limited field of view (FOV) for displaying graphics or AR graphics on the AR display 616. The limited FOV is smaller than the full FOV of the user 608. For example, the user 608 can get a 35-degree gaze fixation by gazing upward without moving the AR wearable device 602 they are wearing. The gaze fixation can be located on an object onto which the AR display 616 cannot project graphics.

[0025] One challenge is to select the vertical tilt 618 angle of the AR display 616 relative to the horizontal line 804 to reduce the number of gaze fixations of the user 608 that fall outside the FOV of the AR display 616 and increase the number of gaze fixations of the user 608 that fall within the FOV of the AR display 616. For example, referring to Fig. 9 , the AR display 616 can display graphics 910 to enhance object 2 906, but cannot generate graphics to enhance object 1 904 or object 3 908 because object 1 904 and object 3 908 are outside the FOV of the AR display 616, but object 2 906 is within the FOV of the AR display 616.

[0026] In some examples, the challenge is addressed by collecting gaze fixation data from a user 608 while performing a task 606 using an application 604, such as selecting breakfast cereal from a food market. The gaze fixation data is collected and then processed to generate a probability distribution of vertical viewing angles or different processed data that can be used to determine a vertical tilt 618 angle for an AR display 616 that increases or maximizes a gaze fixation of the user 608 within the FOV of the AR display 616 while performing the task 606 using the application 604. The task 606 using the application 604 is selected based on the likelihood that the user 608 will perform the task 606, which is based on the previous behavior of the user 608 or the previous behavior of many users 608 using the AR wearable device 602. In some examples, the AR wearable device 602 is manufactured with a fixed vertical tilt 618 angle, while in some examples, the AR wearable device 602 can adjust the vertical tilt 618 angle based on a set of tasks 606 that the user 608 is likely to perform or is performing.

[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 certain messaging clients 104 via the network 112. Although certain functionality of the messaging system 100 is described herein as being performed by the messaging client 104 or by the messaging server system 108, it may be a design choice whether certain functionality is located within the messaging client 104 or within the messaging server system 108. For example, it may be technically preferred to initially deploy certain technologies and functionality within the messaging server system 108, but to 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, geographic location information, media enhancements and overlays, message content persistence conditions, social network information, and live event information. The exchange of data within the messaging system 100 is enabled and controlled by 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 (network) 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 libraries). 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 on 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 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, features and functionality of an external resource (e.g., an application 106 or applet) are made available to the user via an interface of the messaging client 104. In this context, "external" refers to the fact that the application 106 or applet is external to the messaging client 104. External resources are typically provided by a third party, but may also be provided by a creator or provider of the messaging client 104. The messaging client 104 receives a user selection of an option for launching or accessing features of such an external resource. The external resource may be an application 106 installed on the client device 102 (e.g., a "local application"), or a small-scale version of an application (e.g., a "applet") hosted on the client device 102 or remote from the client device 102 (e.g., on a third-party server 110). The small-scale version of an application includes a subset of the features and functionality of an application (e.g., a full-scale, local version of an application) and is implemented using a markup language document. In one example, a small-scale version of an 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 (e.g., .*ml files), an applet may include scripting languages ​​(e.g., .*js files or .json files) and style sheets (e.g., .*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 activities occurring in one or more external resources. For example, the messaging client 104 may provide a notification related to the current or recent use of an external resource by one or more members of a group of users to a participant in a conversation (e.g., a chat session) in the messaging client 104. 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) in the applications 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 tilt angle selection 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, such as 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 that provides notification of the existence of a particular collection to the user interface of the messaging client 104.

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

[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 the generation and publication of 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 an overlay of an identification of a location (e.g., Venice Beach), a name of a live event, or a name of a business (e.g., Beach Cafe). In another example, the augmentation system 208 uses the geographic location of the client device 102 to identify a media overlay that includes the name of a business at the geographic location of the client device 102. The media overlay may include other tags associated with the business. The media overlay may be stored in the database 126 and accessed by 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 geographic location on a map and upload content associated with the selected geographic location. The user can also specify situations in which a particular media overlay should be provided to other users. The enhancement system 208 generates a media overlay that includes the uploaded content and associates the uploaded content with the selected geographic location.

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

[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 geographic location can be displayed to the "friends" of a 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 the selected user 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 also supports providing 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 the web-based external resource to the messaging server 118. The messaging server 118 can add a visual representation (e.g., a box design 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 the features of the web-based external resource through the GUI of the messaging client 104, the messaging client 104 obtains the HTML5 file and instantiates the resources 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 the login portion of the 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 tilt angle selection system 216 supports the system 600 for the AR wearable device. The tilt angle selection system 216 can perform one or more functions described herein in conjunction with the AR wearable device 602. In addition, the tilt angle selection system 216 can store simulation data 622 and process the simulation data 622. In addition, the tilt angle selection system 216 can provide suggestions for vertical tilt 618 angles for the AR display 616 based on the applications 604 and / or tasks 606 that the user 608 is likely to use or has used.

[0059] The tilt angle selection system 216 receives the request from the AR wearable device 602 and responds to the request. The request includes processing the simulation data 622 and making a request for a recommendation regarding the vertical tilt 618 angle, which may include combining Figure 6 The AR wearable device 602 may request other services from the tilt angle selection system 216 .

[0060] Data Architecture

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

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

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

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

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

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

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

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

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

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

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

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

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

[0074] 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, thereby transforming the frame of the video stream. For different types of transformations, the frame of the video stream can be transformed by different methods. For example, for the transformation of the frame that mainly refers to the form of the elements of the object to be changed, the characteristic points of each element of the object are calculated (for example, using an active shape model (ASM) or other known methods). Then, for each element of at least one element of the object, a grid based on the characteristic points is generated. The grid is used in a subsequent stage, in which the elements of the object in the video stream are tracked. During the tracking process, the grid mentioned for each element is aligned with the positioning of each element. Then, additional points are generated on the grid. A first group of first points is generated for each element based on the modification request, and a group of second points is generated for each element based on the group of first points and the request for modification. Then, the frame of the video stream can be transformed by modifying the elements of the object based on the group of first points and the group of second points and the grid. In such methods, the background of the modified object may also be changed or distorted by tracking and modifying the background of the modified object.

[0075] 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 may involve: changing the color of the area; removing at least some parts of the area from the frame of the video stream; including one or more new objects in the area based on the modification request; and modifying or distorting the elements of the area or object. In various examples, any combination of such modifications or other similar modifications may be used. For certain models to be animated, some characteristic points may be selected as control points for determining the entire state space of options for model animation.

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

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

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

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

[0080] In some examples, a computer-animated 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, where the neural network 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-animated model to transform the image data, or the computer-animated model can be presented in association with an interface described herein. The modification icon includes the following changes, which can be the basis for modifying the 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 a process of transforming the user's image to reflect the selected modification icon (e.g., generating a smiling face about 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.

[0081] 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 modifications can be persistent after the initial selection of the modification icon. The user can switch to turn the modification on or off by tapping or otherwise selecting the face being modified by the transformation system, and store it for later viewing or browsing to other areas of the imaging application. In the case of multiple faces being modified by the transformation system, the user can globally switch the modification on or off by tapping or selecting a single face modified and displayed within the graphical user interface. In some examples, each face in a 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 within the graphical user interface.

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

[0083] A collection may also constitute a "live story" as 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.

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

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

[0086] Data communication architecture

[0087] 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:

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

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

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

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

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

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

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

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

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

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

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

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

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

[0101] Time-based access restriction architecture

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

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

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

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

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

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

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

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

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

[0111] Select the tilt angle of the AR display

[0112] Figure 6 A system 600 for selecting a tilt angle of an AR display according to some examples is shown. The system 600 includes an AR wearable device 602 such as Fig.12The glasses 1200 of the present invention may include other devices such as a message server system 108 or a part of a client device 102 that can perform one or more of the operations described herein. The term AR graphics includes any content displayed by the AR display 616 for the user 608 to view through the lens together with viewing the real world. The AR display 616 cannot display graphics 646 over the full gaze range 645 of the user 608's upward and downward range. The system 600 determines a vertical tilt 618 or tilt angle to be used for the AR display 616, which determines the location where the AR graphics view 644 falls within the gaze range 645 of the user 608. The vertical tilt 618 can be between +90 degrees and -90 degrees. In some examples, the vertical tilt 618 ranges from +30 degrees to -40 degrees. As an example, the gaze range 645 can be 70 degrees, which indicates the range of the user 608 moving their eyes up and down to view things without moving their head and therefore without moving the AR wearable device 602. The AR graphics view 644 may be only 27.4 degrees or less than half of the full gaze range 645 of the user 608. Therefore, the AR wearable device 602 cannot display the graphics 646 on the AR display 616 over the full gaze range 645 of the user 608, and the AR graphics view 644 is determined by the selected vertical tilt 618 selected for the AR display 616. The AR wearable device 602 is worn by the user 608.

[0113] The display 610 includes an optical element 612 and an AR display 616. According to some examples, the user 608 sees a user view 642 of a real world scene 634 through the optical element 612, and sees an AR graphics view 644 from graphics 646 displayed by the AR display 616. According to some examples, the AR display 616 includes a projector that projects graphics 646 of the AR graphics view 644 onto the optical element 612. Those skilled in the art will recognize that other AR display 616 designs can be used, and other designs that do not include the optical element 612 can be used. The AR display 616 includes a field of view 636 and a vertical tilt 618. The field of view 636 can be characterized by a degree, such as 27.4 degrees, which indicates the range in which the AR display 616 can display the graphics 646 on the display 610. The field of view 636 is symmetric about the vertical tilt 618. The field of view 636 is narrower than the fixed field of view 640 of the optical element 612. The user view 642 corresponds to what the user 608 can see of the real world scene 634 through the optical element 612. The AR graphics view 644 corresponds to the graphics 646 seen by the user 608 , where the graphics 646 is displayed by the AR display 616 .

[0114] Optical element 612 has vertical tilt 614, which can be zero degrees, but can be set to a downward angle of 1 to 20 degrees, or another degree. AR display 616 has vertical tilt 618, which can be zero degrees, but can be set to a downward angle of 1 to 40 degrees, or another degree. System 600 determines vertical tilt 618 for AR display 616.

[0115] Application 604 runs on AR wearable device 602. Example applications 604 include applications 604 that use AR graphics to help users perform tasks, applications 604 that recognize real-world objects, and applications 604 that provide directions, among others. User 608 uses application 604 to perform task 606. For example, user 608 can use application 604 that helps user 608 select breakfast cereals in a grocery store. Task 606 is to select breakfast cereals. Graphics 646 can indicate ratings of breakfast cereals in terms of nutrition and sugar content, past purchase records of user 608, and any ratings of breakfast cereals by user 608 or family members of user 608. Viewing gaze range 638 indicates viewing gaze range 638 of user 608 when performing task 606. For example, when user 608 looks up and down at different shelves in an aisle of a grocery store, for task 606 of selecting breakfast cereals, viewing gaze range 638 can be 60 degrees. Viewing gaze range 638 can be larger than field of view 636. For example, user 608 may look up at the top shelf and down at the bottom shelf without moving their head, so that viewing gaze range 638 may be as large as 60 degrees. But field of view 636 may be only 27.4 degrees, so that AR display 616 cannot display graphics 646 in all places where user 608 can see or gaze. Viewing gaze range 638 may be determined by actually measuring viewing gaze ranges 638 of multiple users 608 while performing task 606.

[0116] The simulator module 620 first accesses the simulation data 622. The simulation data 622 is collected by performing a study or experiment in which the user 608 performs the task 606 of the application 604 and measures the viewing gaze range 638 used when performing the task 606. The simulation data 622 can be collected in a usability lab where the viewing gaze range 638 is monitored or tracked using equipment separate from the AR wearable device 602. Alternatively or additionally, the simulation data 622 can be collected by an instrument attached to or as part of the AR wearable device 602 that monitors or tracks the viewing gaze of the user 608. In some examples, the simulator module 620 is configured to monitor the viewing gaze of the user 608 and collect the simulation data 622. In the event that the AR wearable device 602 is capable of tracking the viewing gaze angle 626 , the simulation data 622 may be collected from the user 608 who is using the AR wearable device 602 and stored in a central server such as the messaging server system 108 .

[0117] Simulation data 622 indicates application 624, task 606, vertical gaze angle 626 for gaze fixation of user 628, and user 628. For example, application 624 is application 604 and task 606 is a task of selecting breakfast cereal. Vertical gaze angle 626 is the angle (upward or downward) of gaze fixation of user 628 when performing task 606 of selecting breakfast cereal. Vertical gaze angle 626 indicates that gaze fixation is detected at vertical gaze angle 626, e.g., -10 degrees or 20 degrees. Gaze fixation is when eyes 802 of user 608 gaze at a location for at least a threshold hold time period, e.g., .01 seconds or another number.

[0118] The simulator module 620 processes the simulation data 622 to generate processed simulation data 630. For example, the processed simulation data 630 includes a probability distribution of vertical viewing angles for the selected application 624 and task 606. Graph 1000 provides an example probability distribution of vertical viewing angles. The simulator module 620 can process the simulation data 622 to generate other statistical information or probability information. For example, there may be a task 606 of an application 604 that is considered important to support. The simulator module 620 can weight the viewing gaze range 638 of the task 606, which is important to provide greater support when creating the processed simulation data 630. The viewing gaze range 638 can be indicated by the distribution of the number of gaze fixed points for each vertical gaze angle.

[0119] The AR display tilt selection module 632 selects a vertical tilt 618 to use. In some examples, the AR display tilt selection module 632 sweeps through all possible vertical tilt 618 angles and determines, for each vertical tilt 618 angle, which portion of the total distribution of the probability distribution of vertical viewing angles will fall into the field of view 636. The AR display tilt selection module 632 then selects a vertical tilt 618 angle that maximizes the portion of the gaze fix point included in the field of view 636. The AR display tilt selection module 632 can select the vertical tilt 618 to ensure that a specific vertical gaze angle 626, such as -10 degrees, is included in the field of view 636 to support the task 606 of the important application 604. In some examples, the vertical tilt 618 angle is selected and then the AR wearable device 602 is manufactured with a permanent vertical tilt 618 relative to the vertical tilt 614 of the optical element 612. In some examples, the source of the noise distribution is taken into account. An example of noise is that the user 608 wears the AR wearable device 602 differently or wears the AR wearable device 602 differently at different times, which may change the vertical tilt 614 of the optical element 612. The simulator module 620 can convolve the distribution of the source of noise with the simulation data 622 when generating the processed simulation data 630. The processed simulation data 630 thus includes the source of noise and will affect the selection of the vertical tilt 618 of the AR display 616. For example, if the user 608 wears the AR wearable device 602 correctly or as intended 80% of the time, but wears the AR wearable device 602 with an additional vertical tilt 614 of 10 degrees 20% of the time, the simulator module 620 thus shifts the original data, where 20% of the original data is shifted by 10 degrees for the vertical gaze angle 626.

[0120] Figure 7 1 shows a system 700 for selecting a tilt angle of an AR display according to some examples. The system 700 includes an AR wearable device 602 such as Fig.12 The glasses 1200 may include other devices, such as other devices including a portion of the messaging server system 108 or the client device 102 that may perform one or more of the operations described herein.

[0121] In some examples, the vertical tilt 618 angle is adjustable. The AR display tilt selection module 632 resides on the AR wearable device 602, the messaging server system 108, the client device 102, or another device. The AR display tilt selection module 632 selects the vertical tilt 618 angle based on the application 604 and task 606 that the user 608 is using or is likely to use, and causes an actuator (not shown) to adjust the vertical tilt 618 angle.

[0122] Figure 8 618 according to some examples. Eye 802 is the eye of a user 608 wearing the AR wearable device 602. Optical element 612 is tilted at a vertical tilt 614 angle relative to a horizontal line 804 or a normal line out of the eye 802. The vertical tilt 618 angle indicates the vertical tilt of the horizontal line 804 from the AR display 616 ( Figure 8 618). The AR display 616 can be mounted on the AR wearable device 602 or on the optical element 612 or on a structure associated with the optical element 612. Those skilled in the art will recognize that the AR display 616 can be mounted in different ways. In addition, in some examples, the AR display 616 can be implemented in different ways, such as via an element within the optical element 612 or directly projected onto the eye 802. For different AR displays 616, the selection of the field of view 636 is the same or similar to the selection of the vertical tilt 618 angle.

[0123] Fig. 9 618 angles according to some examples are shown. Person 902 is wearing AR wearable device 602. Field of view 636 is determined by the vertical tilt 618 angle relative to horizontal line 804. AR wearable device 602 cannot project graphics 646 onto object 1 904 because object 1 904 is outside of field of view 636. Therefore, if the eyes 802 of person 902 look up or down without moving the head of person 902, object 1 904 or object 3 908, respectively, will appear as they are in the real world scene 634 without any graphics 646. However, since object 2 906 is within the field of view 636 of AR display 616, AR wearable device 602 can generate graphics 910 associated with object 2 906. For example, graphics 910 can be projected onto object 2 906, which can be a cereal box. Graphic 910 may be adjusted at a size and perspective that appears to complement the surface of the cereal box to add information such as the likelihood that person 902 will like the cereal and a healthfulness score for the cereal.

[0124] Fig.10 1000 is shown according to some examples. Graph 1000 graphically represents the number of gaze fixations 1008 for vertical gaze angles 1010. In some examples, the vertical gaze angles range from +30 degrees to -40 degrees. Graph 1000 is combined with the raw number of gaze fixations 1008 instead of the probability of gaze fixations. Figure 6 The graph of the probability distribution of vertical viewing angle discussed above is similar. Gaze fixation 1008 is the number of gaze fixations counted when user 608 performs task 606 of application 604 covered by graph 1000 multiplied by 10. 4. The vertical tilt 618 shown in the graph 1000 is -4.6 degrees relative to the horizontal line 804. The gaze 1004 in the field of view (FOV) is the AR graphics view 644. The gaze 1002 outside the FOV is the user view 642 that is not part of the gaze 1004 in the FOV. For example, object 1 904 will be in the upper 1014 portion of the graph 1000, and object 3 908 will be in the lower portion 1012 of the graph. Object 2 906 will be within the field of view 636 of the AR display 616. The select AR display tilt module 632 can select the bore sight or vertical tilt 618 to maximize the area under the curve. The select AR display tilt module 632 can select the bore sight or vertical tilt 618 with the largest number of gaze fixed points 1008 within the gaze 1004 in the FOV. In some examples, the vertical tilt 618 is adjusted to accommodate important or necessary gaze fixed points 1008. For example, a gaze fix of -22 degrees may be a gaze used to check the battery level of the AR wearable device 602, so selecting the AR display tilt module 632 ensures that -22 degrees is within the gaze 1004 in the FOV.

[0125] Fig.11 Graph 1100 is shown according to some examples. Graph 1100 graphically represents a percentage 1102 in FOV, wherein the percentage 1102 in FOV refers to Fig.10 The percentage of gaze fixation 1008 relative to the visual axis angle 1104 or vertical tilt 618. The curve 1100 is actually Fig.10 The FOV of the gaze is 1004 divided by Fig.10 The total number of gaze fixations based on vertical tilt 618. The maximum inclusion 1108 is the viewing axis angle 1104 where the percentage 1102 in the FOV is the highest, which is about 9 degrees here.

[0126] Fig.121 is a perspective view of a wearable electronic device in the form of glasses 1200 according to some examples. Glasses 1200 are eyewear products that include electronic devices that operate within a network system to transmit 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 additionally 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, 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.

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

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

[0129] 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, position 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 of various aspects of computer 1261 can be implemented as described with reference to the following description.

[0130] 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 piece 1246 or the temple piece 1247. Fig.12 In the glasses 1200 shown in FIG. 1 , the battery 1262 is shown as being 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.

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

[0132] 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 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 camera 1269 of the user; and an outward-facing video sensor or digital imaging module, such as 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 camera 1269 of the user. Such sensors, peripherals or peripherals may additionally include biometric sensors, position sensors, accelerometers, or any other such sensors. In some examples, a projector (not shown) is used to project images onto the inner surfaces of optical element 1243, optical element 1244 (or lenses) to provide a mixed reality or augmented reality experience for the user of glasses 1200.

[0133] 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 a disengaged state. In this example, the camera control button is a button that is in the disengaged state by default and can be pressed by the user to set it to the engaged state. Once the camera control button is released from being pressed, it automatically returns to the disengaged state.

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

[0135] 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 communicate with each other based on, for example, Bluetooth. TM , Bluetooth Low Energy TM , IEEE 802, IEEE 802.11az / be, etc. The PDR sensor is operated in glasses 1200 and coupled to computer 1261. In some examples, glasses 1200 are VR headsets, wherein optical element 1243, optical element 1244 are opaque screens for displaying images to a user of the VR headset. In some examples, computer 1261 is coupled to user interface elements such as a slider or touchpad 1276 and a button 1278. A long press of button 1278 resets glasses 1200. Slider or touchpad 1276 and button 1278 are used by the user to provide input to computer 1261 and / or other electronic components of glasses 1200. Glasses 1200 include one or more microphones 1282 coupled to computer 1261. Glasses 1200 include one or more gyroscopes 1280. Glasses 1200 include an AR display 616 as described herein.

[0136] Fig.13 A method 1300 for selecting a tilt angle of an AR display according to some examples is shown. The method 1300 may be performed by an AR wearable device 602, for example Fig.12 The method 1300 may be performed in other ways to generate a tilt angle for making an AR display 616 and / or an AR wearable device 602. One or more of the operations may be performed in whole or in part by other devices, such as by a messaging server system 108, a portion of a client device 102, or in another way.

[0137] The method 1300 for setting a tilt angle for an AR display of an AR wearable device begins at operation 1302 , where data indicating the number of gaze fixations for each vertical gaze angle is accessed. For example, the simulator module 620 accesses the simulation data 622 .

[0138] The method 1300 continues to operation 1304, where a tilt angle for the AR display is selected based on the number of gaze fixations within the field of view of the AR display, wherein the tilt angle indicates the field of view of the AR display. For example, the select AR display tilt module 632 selects a vertical tilt 618 of the AR display 616 based on the application 604 and / or task 606 that the user 608 is about to use or is using.

[0139] The method 1300 continues to operation 1306 where a tilt angle for the AR display is set. For example, selecting the AR display tilt module 632 may cause the vertical tilt 618 to change, or the AR wearable device 602 may be manufactured such that the vertical tilt 618 of the AR display 616 is set to the selected vertical tilt angle 618.

[0140] 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, another electronic device, or in another manner. Portions of the functionality may be performed on a server computer or a host computer. For example, the glasses 1200 may be coupled to a host client device 102 or an application server 114 where one or more operations are performed.

[0141] Machine Architecture

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

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

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

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

[0146] In another example, the I / O component 1402 may include: a biometric component 1430, a motion component 1432, an environmental component 1434, or a positioning 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).

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

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

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

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

[0151] 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 ... Parts (e.g. Low energy consumption), Components and other communication components for providing communication via other modalities. Device 1424 can be another machine or any peripheral device among various peripheral devices (e.g., a peripheral device coupled via USB).

[0152] 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 an audio signal of a tag). In addition, various information can be obtained via the communication component 1438, such as positioning via Internet Protocol (IP) geographic location, obtaining a location via Positioning is obtained through signal triangulation, positioning is obtained via detection of NFC beacon signals that can indicate a specific position, etc.

[0153] 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 implement 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.

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

[0155] Software Architecture

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

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

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

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

[0160] 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 API calls 1550 provided by the operating system 1512 to facilitate the functions described herein.

[0161] Processing components

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

[0163] Processor 1602 is shown coupled to power source 1604 and includes modules (permanently configured or temporarily instantiated), namely, graphics display component 1610, simulation component 1612, and AR display tilt selection component 1614. Graphics display component 1610 controls an AR display such as AR display 616. Simulation component 1612 processes simulation data 622 to generate processed simulation data 630. According to some embodiments, simulation component 1612 is combined with Figure 6 The simulator module 620 described is the same or similar.

[0164] The select AR display tilt component 1614 selects a vertical tilt 618 of the AR display 616. For example, the select AR display tilt module 632 selects a vertical tilt 618 angle of the AR display 616 of the AR wearable device 602. As shown, the processor 1602 is communicatively coupled to both the processor 1606 and the processor 1608.

[0165] Glossary

[0166] Certain examples 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 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., 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.

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

[0168] "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.

[0169] "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, The coupling may be a network, another type of network, or a combination of two or more such networks. For example, the network or a portion of the network may 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.

[0170] "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 a specific function in a related function. Components can constitute software components (e.g., codes implemented on machine-readable media) or hardware components. "Hardware components" are tangible units that can perform certain operations and can be configured or arranged in a certain physical manner. In various examples, one or more computer systems (e.g., independent computer systems, client computer systems, or server computer systems) or one or more hardware components (e.g., processors or processor groups) of a computer system can be configured by software (e.g., applications or application parts) to operate to perform certain operations as described herein. 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 temporarily configured (e.g., configured by software) circuit system 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 hardware component in the hardware component 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 operations in 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 operations in the operation can be performed by a group of computers (as an example of a machine including a processor), wherein these operations can be accessed via a network (for example, the Internet) and via one or more appropriate interfaces (for example, API). The execution of some operations in the operation can be distributed among the processors, not only resident in a single machine, but also deployed across multiple machines. In some examples, the processor or the parts implemented by the processor can be located in a single geographical location (for example, in a home environment, an office environment or a server group). In other examples, the processor or the parts implemented by the processor can be distributed across multiple geographical locations.

[0171] "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.

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

[0173] "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".

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

[0175] "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 for setting a tilt angle for an augmented reality (AR) display of an augmented reality (AR) wearable device, the method comprising: accessing data indicating a number of gaze fixations for each vertical gaze angle; selecting a tilt angle for the AR display based on a number of the gaze fixations within a field of view of the AR display, wherein the tilt angle is indicative of a field of view of the AR display; as well as Sets a tilt angle for the AR display.

2. The method according to claim 1, wherein: The vertical gaze angle is from +30 degrees to -40 degrees.

3. The method according to claim 1, further comprising: The data is collected for the plurality of applications by monitoring gaze fixations of users of the plurality of applications as the users perform tasks using the plurality of applications.

4. The method according to claim 3, wherein: The plurality of applications is a first plurality of applications, and wherein the method further comprises: The first plurality of applications are selected from a second plurality of applications based on a probability that a user of the AR wearable device will use the first plurality of applications.

5. The method according to claim 1, wherein: The tilt angle is selected based on the number of gaze fixations being a maximum number within a field of view of the AR display for the tilt angle.

6. The method according to claim 1, wherein: The AR wearable device has a fixed field of view that is larger than a field of view of the AR display.

7. The method according to claim 6, wherein: The fixed field of view is of a real-world scene, wherein a user of the AR wearable device sees the fixed field of view through an optical element of the AR wearable device.

8. The method according to claim 7, wherein: The tilt angle is a first tilt angle, and the optical element has a second tilt angle, and wherein the first tilt angle is measured based on the second tilt angle.

9. The method according to claim 1, further comprising: The AR wearable device is manufactured with the tilt angle for the AR display.

10. The method according to claim 1, wherein: Setting a tilt angle for the AR display further includes: An actuator is caused to change a current tilt angle for the AR display to the tilt angle for the AR display.

11. The method according to claim 1, further comprising: The number of gaze fixed points at each vertical gaze angle is adjusted based on a noise distribution, wherein the noise distribution is an angle at which a user of the AR wearable device wears the AR wearable device.

12. The method according to claim 1, wherein: Selecting the tilt angle is also based on including a gaze range of one or more applications within a field of view of the AR display.

13. An augmented reality (AR) wearable device comprising: processor; as well as A memory storing instructions, which, when executed by the processor, configure the AR wearable device to perform the following operations, including: accessing data indicating a number of gaze fixations for each vertical gaze angle; selecting a tilt angle for the AR display based on a number of the gaze fixations within a field of view of the AR display, wherein the tilt angle is indicative of a field of view of the AR display; and Sets a tilt angle for the AR display.

14. The AR wearable device according to claim 13, wherein: The vertical gaze angle is from +30 degrees to -40 degrees.

15. The AR wearable device according to claim 13, wherein: The operations also include: The data is collected for the plurality of applications by monitoring gaze fixations of users of the plurality of applications as the users perform tasks using the plurality of applications.

16. The AR wearable device according to claim 13, wherein: Setting a tilt angle for the AR display further includes: An actuator is caused to change a current tilt angle for the AR display to the tilt angle for the AR display.

17. 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 the following operations, including: accessing data indicating a number of gaze fixations for each vertical gaze angle; selecting a tilt angle for the AR display based on a number of the gaze fixations within a field of view of the AR display, wherein the tilt angle is indicative of a field of view of the AR display; as well as Sets a tilt angle for the AR display.

18. The non-transitory computer readable storage medium of claim 17, wherein: The vertical gaze angle is from +30 degrees to -40 degrees.

19. The non-transitory computer-readable storage medium of claim 17, wherein: The operations also include: The data is collected for the plurality of applications by monitoring gaze fixations of users of the plurality of applications as the users perform tasks using the plurality of applications.

20. The non-transitory computer readable storage medium of claim 17, wherein: Setting a tilt angle for the AR display further includes: An actuator is caused to change a current tilt angle for the AR display to the tilt angle for the AR display.

Images