Remotely changing settings on ar wearable device

Abstract

Systems, methods, and computer-readable media for remotely changing settings on an augmented reality (AR) wearable device are described. Embodiments are disclosed that enable a user to change settings of an AR wearable device over a user interface (UI) provided by a host client device that may wirelessly communicate with the AR wearable device. The host client device and the AR wearable device provide remote procedure calls (RPCs) and application program interfaces (APIs) to access settings and determine whether the settings have been changed. The API enables the host client device to determine settings on the AR wearable device without requiring any priori knowledge of the settings on the AR wearable device. When a user changes settings on the host client device, the RPC and API enable the host client device to automatically update settings on the AR wearable device.

Description

[0001] Priority declaration

[0002] This application claims the benefit of U.S. patent application serial number 17 / 929,985, filed on September 6, 2022, the entire contents of which are incorporated herein by reference. Technical Field

[0003] Examples of the present disclosure generally relate to remotely changing settings on an augmented reality (AR) wearable device. More specifically, but not by way of limitation, examples of the present disclosure relate to a host device wirelessly coupled to an AR wearable device that remotely changes or updates settings using a remote procedure call (RPC) and an application program interface (API). Background Art

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

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

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

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

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

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

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

[0011] Figure 6 A system for remotely changing settings on an AR wearable device is shown according to some examples.

[0012] Figure 7A user interface for settings is shown according to some embodiments.

[0013] Figure 8 A system for remotely changing settings on an AR wearable device 602 is shown, according to some examples.

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

[0015] Fig.10 Methods for remotely changing settings on an AR wearable device according to some examples are shown.

[0016] Fig.11 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.

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

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

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

[0020] AR wearable device 602 is used as an illustrative device; however, those skilled in the art will recognize that the methods, systems, and computer-readable media disclosed herein are applicable to other wearable devices, including VR wearable devices and MR wearable devices. Application is used to refer to AR applications, VR applications, MR applications, and non-AR applications.

[0021] Typically, AR wearable devices such as Figure 6 AR wearable device 602 or Fig. 9The AR glasses 900 have limited physical user interface items such as buttons 978. Some AR wearable devices 602 have a tactile UI, such as one or two buttons 978 or a touchpad 976 that the user interacts with on the frame 932 of the AR wearable device 602. In addition, there may be many settings 630 for the AR wearable device 602, such as sleep time, display 636 brightness, a default client device 102 to attach to, a UI mode such as voice or tactile, whether to download new applications, security settings, etc. In addition, applications running on the AR wearable device 602 may have many settings 630 associated with running programs, such as a default UI mode, update time, character size on the display 636, full AR mode vs. partial AR mode, etc. The settings 630 may be categorized into categories 628. For example, each application may be its own category 628, or applications may be grouped into categories 628. There may be categories 628 for basic settings of the AR wearable device 602, etc.

[0022] The UI of the AR wearable device 602 may be more limited than the UI of the host client device 102. Therefore, it may be time consuming for the user to find and set the settings 630 using the UI of the AR wearable device 602.

[0023] One challenge is how to make settings 630 of the AR wearable device 602 available for the user to view or change without the user having to use the tactile UI elements of the wearable AR device 602. This challenge is addressed by associating the AR wearable device 602 with the client device 102 and enabling the user to access the settings 630 using the UI of the client device 102. Remote procedure calls (RPCs) and application program interfaces (APIs) are provided to enable the AR wearable device 602 to share the settings 630 of the AR wearable device 602 with the client device 102. The RPCs and APIs enable the client device 102 to determine the category 628, name, and settings 630 using the RPCs and APIs without having to know any of the settings 630 in advance. In addition, the client device 102 or another device provides recommended or default settings 630 to the AR wearable device 602. The AR wearable device 602 can receive settings 630 that have been adjusted based on the use of other AR wearable devices 602.

[0024] Networked computing environment

[0025] Figure 11 is a block diagram illustrating an example of a messaging system 100 for exchanging data (e.g., messages and associated content) over a network. The messaging system 100 includes multiple instances of a client device 102, each of which hosts multiple applications including a messaging client 104 and other applications 106. Each messaging client 104 is communicatively coupled to other instances of the messaging client 104 (e.g., hosted on respective other client devices 102), a messaging server system 108, and a third-party server 110 via a network 112 (e.g., the Internet). The messaging client 104 may also communicate with the locally hosted application 106 using an application program interface (API).

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

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

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

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

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

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

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

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

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

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

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

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

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

[0039] System Architecture

[0040] 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 gaming system 212, an external resource system 214, and a system for remotely changing settings 216.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0055] The system 216 for remotely changing settings supports the AR wearable device 602 and / or the client device 102. The system 216 for remotely changing settings provides settings 630 for the AR wearable device 602 and / or the client device 102. For example, the system 216 for remotely changing settings can provide default or recommended settings 630 for the AR wearable device 602. For example, other AR wearable devices 602 can provide feedback on how the settings 630 have been operated on the AR wearable device 602. A specific example is a timeout period. The timeout period affects battery life and user experience. The system 216 for remotely changing settings can determine that many experienced users of the AR wearable device 602 set their timeout periods to a specific range. Then, the system 216 for remotely changing settings recommends the specific range as a recommended value for the recommended setting 630 for the timeout period. In addition, the system 216 for remotely changing settings can provide one or more functions performed by the client device 102 and / or the AR wearable device 602.

[0056] Data Architecture

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

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

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

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

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

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

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

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

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

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

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

[0068] Thus, data and various systems using augmented reality content items or other such transformation systems using 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.

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

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

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

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

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

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

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

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

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

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

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

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

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

[0082] Data communication architecture

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0097] Time-based access restriction architecture

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

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

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

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

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

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

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

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

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

[0107] Remotely change settings on an AR wearable

[0108] Figure 6 6 is a diagram illustrating a system 600 for remotely changing settings on an AR wearable device according to some examples. According to some implementations, the client device 102 is the same as or similar to the client device 102. The system 600 includes an AR wearable device 602, such as Fig. 9 Glasses 900. In some implementations, the AR wearable device 602 communicates with another device, such as the system 216 for remotely changing settings, which may be running on the messaging server system 108.

[0109] The wireless interface 634 communicates wirelessly with the wireless interface 603 of the AR wearable device 602 according to a wireless communication protocol. The wireless communication protocol can be Bluetooth Low Energy (BLE), the Institute of Electrical and Electronics Engineers (IEEE) 802.11 communication standard, a proprietary communication standard, a 3GPP communication protocol, or another communication protocol. The wireless interfaces 634, 638 include antennas and transceiver circuit systems for performing wireless communication. The AR wearable device 602 and the client device 102 can be associated with each other, where communication parameters are exchanged before transmitting RPCs to each other.

[0110] The client device 102 includes a remote procedure call (RPC) module 604 configured to communicate with an RPC module 626 via a wireless interface 634. The RPC includes send settings for category 618, get settings for category 620, send settings for category 622, and request settings for category 624.

[0111] The setting category modules 606, 627 provide user interfaces 614, 638 that enable a user to change the values ​​of the settings 610, 630. Changed 612, 632 are fields associated with the settings 610, 630, respectively, which are set when the values ​​of the settings 610, 630 are changed. The setting category modules 606, 627 use the user interfaces 614, 638 to display the values ​​of the settings 610, 630, respectively, and enable the user to change the values ​​of the settings 610, 630. In addition, the setting category modules 606, 627 use the user interfaces 614, 638 to enable the user to perform functions such as sending settings for the categories 608, 628 or requesting settings for the categories 624, 628. In some embodiments, the setting category module 606 retrieves all settings 630 and enables the user to change or view all settings 630. The settings category module 606 automatically updates the settings 630 on the AR wearable device 602 so that it appears to the user that the settings 630 are controlled by the settings category module 606 .

[0112] The display 616, 636 is an electronic device for visual presentation of the user interface 614, 638. The user interacts with the user interface 614, 638 to provide input, such as changing the value of the setting 610, 630, respectively. The settings 610, 630 are organized according to categories 608, 628, where the category 608, 628 indicates one or more applications or functional areas. Example categories 608, 628 include a camera service settings category, a lens application settings category, an account service settings category, an out-of-box experience (OOBE) service settings category, and a default AR wearable device settings category. The default AR wearable device settings category may include display brightness settings, input mode selection, and timeout period selection. Each application on the AR wearable device 602 can be a category 608, 628, or the applications can be grouped together into categories 608, 628, such as categories 608, 628 for determining the location of the AR wearable device 602.

[0113] Because AR wearable devices may have limited input options, the user interface 638 of the client device 102 makes it easier for the user to change the value of the setting 610. For example, the client device 102 may have a touch-sensitive screen so that the user can easily display and change the name of the setting 610 and its value. In addition, the AR wearable device 602 has a more limited battery life. In addition, a voice user input mode may be available as a user interface 638 on the AR wearable device 602, but the voice mode may not always be available and may be energy intensive to use.

[0114] The settings 630 of the AR wearable device 602 represent the state of the AR wearable device 602. The settings 630 can be downloaded to the AR wearable device 602 from the client device 102 or another device. For example, the AR wearable device 602 can be reset by downloading the initial settings of the settings 610 from the client device 102. In addition, the settings 630 can be loaded from the AR wearable device 602 to the client device 102, changed 612, and then downloaded back to the AR wearable device 602, which enables the user to change the settings 630 more easily. In addition, a copy of the settings 610 can be kept on the client device 102 so that the user can view the settings 610 and if the settings 610 are changed, the settings 610 are downloaded to the AR wearable device 602.

[0115] The RPC 617 enables the settings 610 of the AR wearable device 602 to be viewed, set, or reset on another device such as the client device 102. The RPC 617 includes sending settings 618 for categories, where the settings category module 627 sends the settings 610 for the category 608 from the client device 102 to the settings category module 606 of the client device 102. The settings category module 606 stores the settings 630 as settings 610 for the user to view or set. The settings category module 62 uses the get settings 620 for categories RPC 617 to retrieve the settings 610 for the category 608 from the client device 102. The settings category module 627 then updates the category 628 based on the settings 610 retrieved from the client device 102.

[0116] A request set for class 624 RPC 617 is sent from set class module 606 to set class module 627 and is a request for set 630 for class 628. Set class module 627 responds by sending a set for class 618 RPC 617.

[0117] The send settings for class 622 RPC 617 is used by the set class module 606 to send settings 610 for class 608 to the set class module 627. The send settings for class 622 may be in response to a get settings for class 620 RPC 617 sent by the set class module 627 to the set class module 606.

[0118] The RPC 617 may indicate one or more categories 628, all categories 628, all settings 610, 630, or all changed settings 610, 630. The RPC 617 may indicate all categories 628 without knowing what the category 628 is. The RPC 617 may not specify what the setting 630 within the category 632 is. The RPC 617 may include fields as indicated in Table 1, which is an example application programming interface (API) between a setup service and a paired device, where the setup service is the setup category module 606 and the paired device is the AR wearable device 602.

[0119]

[0120]

[0121]

[0122] Figure 7A user interface for settings is shown according to some embodiments. The display 616 of the client device 102 is displaying the user interface 614. The user can select a category 710 to cause the settings category module 606 to check whether the category 710 is loaded on the client device 102. If the settings category 710 is not loaded on the client device 102, the settings category module 606 sends a send get settings for category 622 RPC 617 to the AR wearable device 602. In one example, settings 702, 704, 706, 708 are labels sent by the AR wearable device 602 in the send settings for category 618 RPC 617. For example, settings 702, 704, 706, 708 are the "title of this setting in a format that can be presented to the user: required string title=2" at section 3 of the API. According to some embodiments, the values ​​712, 714, 716, 718 are the values ​​described in section 4 of Table 1. The user interface 614 allows a user to view and change the values ​​712 , 714 , 716 , 718 of the settings 702 , 704 , 706 , 708 .

[0123] If the setting 702 value 712 changes, the remote procedure call module 604 sets the corresponding changed 612 field to indicate that the setting 702 value 712 has changed. According to some implementations, the remote procedure call module 604 automatically sends the updated setting 702 to the AR wearable device 602 .

[0124] Figure 8 A system 800 for remotely changing settings on an AR wearable device 602 is shown according to some examples. According to some embodiments, the client device 102 includes a BLE communicator 802 as a wireless interface 603. According to some embodiments, a BLE RPC handler 810 is a wireless interface 634. BLE 804 indicates that BLE is being used for communication and that communication begins with an initial association that shares communication parameter information.

[0125] The BLE RPC handler 810 is executed, implemented or run by processor 1 812. According to some embodiments, processor 1 812 is a dedicated communication processor. The BLE communicator 802 and the BLE RPC handler 810 exchange messages such as requests 806 and responses 808, which include RPC 817 as their payload.

[0126] like Figure 8, there is an example request 806 sent from the client device 102 to the AR wearable device 602, such as a request to send a setup 622 RPC 817 for a category, which is satisfied by the AR wearable device 602 as follows. The BLERPC handler 810 transmits the request 806 as a request 816 (RPC) to the service manager 820 executed by the processor 2 822. According to some embodiments, the processor 1 812 and the processor 2 822 communicate via a serial processor interface (SPI) 814. In the initial setup, the RPC is registered with the service manager 820 in the form of a register RPC handler 826. The registration enables the service manager 820 to identify the RPC and may include information about which RPC handlers the service manager 820 should enable in response to receiving the RPC. The service manager 820 starts the setup service 824 in the form of a start service 828. The setup service 824 indicates the communication channel to be used for the service manager 820 in the service communication channel 830. The service manager 820 requests a service such as sending a settings 622 RPC 817 for a category with a service call 832. The settings service 824 returns the settings 630 for the category 628 with a result 836. The result 836 may be in a format according to Table 1. The service call 832 and result 836 operations are repeated for each category 628 indicated in the RPC 817, or for all categories 628 if the RPC 817 indicates that all categories 628 should be retrieved.

[0127] Then, the service manager 820 encodes and sends a response (RPC) 818 including all settings 630, for example, according to the format of Table 1. The service manager 820 ends the setting service 824 in the form of stopping the service 838. The BLE RPC handler 810 sends a wireless communication to the BLE communicator 802, the wireless communication including the settings 630 in the response 808, the response including the RPC having the format according to Table 1. The client device 102 displays the settings 610 for the user to view or set, such as in conjunction with Figure 7 described.

[0128] Fig. 9900 is a stereoscopic view of a wearable electronic device in the form of glasses 900 according to some examples. Glasses 900 are eyewear products including electronic products that operate within a network system for transmitting image and video content. In some examples, the wearable electronic device is referred to as AR glasses. Glasses 900 may include a frame 932 made of any suitable material, such as plastic or metal, including any suitable shape memory alloy. Frame 932 may have a front piece 933, which may include a first lens or left lens, a display or optical element holder 936 and a second lens or right lens, a display or optical element holder 937 connected by a bridge 938. Front piece 933 further includes a left end portion 941 and a right end portion 942. A first optical element or left optical element 944 and a second optical element or right optical element 943 may be disposed in respective left optical element holders 936 and right optical element holders 937. Each of optical element 943, optical element 944 may be a lens, a display assembly, or a combination of the foregoing. In some examples, for example, the glasses 900 are provided with an integrated near-eye display mechanism that enables, for example, a preview image of visual media captured by the camera 969 of the glasses 900 to be displayed to the user.

[0129] The frame 932 further includes a left arm or temple piece 946 and a right arm or temple piece 947, which are coupled to the corresponding left end 941 and right end 942 of the front piece 933 by any suitable means such as a hinge (not shown) to be coupled to the front piece 933 or rigidly or fixably fixed to the front piece 933, thereby being integral with the front piece 933. Each of the temple piece 946 and the temple piece 947 may include: a first portion 951 coupled to the corresponding end 941 or 942 of the front piece 933; and any suitable second portion 952 for coupling to the user's ear, such as a curved or arched piece. In one example, the front piece 933 can be formed of a single piece of material to have a unitary or integrated construction. In one example, the entire frame 932 can be formed of a single piece of material to have a unitary or integrated construction.

[0130] Eyeglasses 900 include a computing device such as computer 961, which may be of any suitable type to be carried by frame 932 and, in some examples, of a suitable size and shape to be at least partially disposed within one or more of temple pieces 946, 947. In one example, computer 961 is of a size and shape similar to the size and shape of one of temple pieces 946, 947 and is thus disposed nearly completely, if not completely, within the structure and confines of such temple pieces 946, 947.

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

[0132] The computer 961 further includes a battery 962 or other suitable portable power source. In one example, the battery 962 is disposed in one of the temple pieces 946 or the temple pieces 947. Fig. 9 In the illustrated eyeglasses 900, a battery 962 is shown disposed in the left temple piece 946 and electrically coupled to the remainder of the computer 961 disposed in the right temple piece 947 using a connector 974. The one or more input and output devices may include a connector or port (not shown) accessible from the exterior of the frame 932 suitable for charging the battery 962, a wireless receiver, transmitter or transceiver (not shown), or a combination of such devices.

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

[0134] In various examples, the glasses 900 may include any number of input sensors or peripherals in addition to the camera 969. The front piece 933 is provided with an outward-facing, front-facing, front or outer surface 966 that faces forward or away from the user when the glasses 900 are mounted on the user's face; and an opposite inward-facing, rearward-facing, rear or inner surface 967 that faces the user's face when the glasses 900 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 967 of the front piece 933 or elsewhere on the frame 932 to face the camera 969 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 966 of the front piece 933 or elsewhere on the frame 932 to face away from the camera 969 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 943, optical element 944 (or lenses) to provide a mixed reality or augmented reality experience for the user of glasses 900.

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

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

[0137] The computer 961 is configured to perform the methods described herein. In some examples, the computer 961 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 the glasses 900. In some examples, the computer 961 is coupled to one or more wireless antennas and circuitry for sending and receiving wireless signals, wherein the antennas and circuitry are housed in the glasses 900. In some examples, multiple sets of antennas and circuitry are housed in the glasses 900. In some examples, the antennas and circuitry are configured to receive signals based on, for example, Bluetooth. TM , Bluetooth Low Energy TM , IEEE 802.11, IEEE 802.11az / be, LTE, proprietary communication standards, 3GPP, etc. to operate. In some examples, the PDR sensor is housed in the glasses 900 and coupled to the computer 961. In some examples, the glasses 900 are VR headsets, wherein the optical element 943, the optical element 944 is an opaque screen for displaying images to a user of the VR headset. In some examples, the computer 961 is coupled to user interface elements, such as a slider or touchpad 976 and a button 978. Long pressing the button 978 resets the glasses 900. The slider or touchpad 976 and the button 978 are used by the user to provide input to the computer 961 and / or other electronic components of the glasses 900. The glasses 900 include one or more microphones 982 coupled to the computer 961. The glasses 900 include one or more gyroscopes 980.

[0138] Fig.10 A method 1000 for remotely changing settings on an AR wearable device is shown according to some examples. The method 1000 begins at operation 1002, where a first RPC is received from a client device indicating a request to provide setting names and setting values ​​for a plurality of setting categories. For example, the request 806 may be an RPC 617 requesting settings 630 for a plurality of categories 628.

[0139] The method 1000 continues at operation 1004 where setting names and setting values ​​for a plurality of setting categories are retrieved. For example, the service manager 820 retrieves the settings 630 from the settings service 824 according to the API described in Table 1.

[0140] Method 1000 continues at operation 1006 where a second RPC is sent to the client device indicating setting names and setting values ​​for multiple setting categories. For example, according to the API described in Table 1, response 808 may be RPC 617 including all settings 630 for category 628.

[0141] The method 1000 may include one or more additional operations. The operations of the method 1000 may be performed in a different order. One or more of the operations of the method 1000 may be optional. The method 1000 may be performed by a client device 102, a system 600, glasses 900, an AR wearable device 602, or another electronic device. A portion of the functionality may be performed on a server computer or host. For example, the glasses 900 may be coupled to a host client device 102 or application server 114 where one or more of the operations (e.g., providing a default or suggested setting 630 value) are performed.

[0142] Machine Architecture

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

[0144] The machine 1100 may include a processor 1104, a memory 1106, and an input / output I / O component 1102, which may be configured to communicate with each other via a bus 1140. In an example, the processor 1104 (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 1108 that executes instructions 1110 and a processor 1112. 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.11 Multiple processors 1104 are shown, but the machine 1100 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.

[0145] The memory 1106 includes a main memory 1114, a static memory 1116, and a storage unit 1118, which are all accessible by the processor 1104 via a bus 1140. The main memory 1106, the static memory 1116, and the storage unit 1118 store instructions 1110 that implement any one or more of the methods or functions described herein. The instructions 1110 may also reside, completely or partially, within the main memory 1114, within the static memory 1116, within the machine-readable medium 1120 within the storage unit 1118, within at least one of the processors 1104 (e.g., within a cache memory of a processor), or within any suitable combination thereof during execution thereof by the machine 1100.

[0146] I / O components 1102 may include various components for receiving input, providing output, generating output, transmitting information, exchanging information, capturing measurements, etc. The specific I / O components 1102 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 1102 may include Fig.111102. In various examples, the I / O components 1102 may include a user output component 1126 and a user input component 1128. The user output component 1126 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 1128 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.

[0147] In another example, the I / O component 1102 may include: a biometric component 1130, a motion component 1132, an environment component 1134, or a position component 1136, as well as various other components. For example, the biometric component 1130 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 1132 includes an acceleration sensor component (e.g., an accelerometer), a gravity sensor component, and a rotation sensor component (e.g., a gyroscope).

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

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

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

[0151] The location component 1136 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.

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

[0153] In addition, the communication component 1138 can detect the identification, or include a component that is operable to detect the identification. For example, the communication component 1138 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 1138, such as positioning via Internet Protocol (IP) geographic location, obtaining a location via Positioning is obtained by signal triangulation, positioning is obtained via detection of NFC beacon signals that can indicate a specific position, etc.

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

[0155] The instructions 1110 may be sent or received via a network interface device (e.g., a network interface component included in the communication component 1138) using a transmission medium and using any of a number of well-known transmission protocols (e.g., Hypertext Transfer Protocol (HTTP)) over the network 1122. Similarly, the instructions 1110 may be sent or received via a coupling (e.g., a peer-to-peer coupling) to the device 1124 using a transmission medium.

[0156] Software Architecture

[0157] Fig.1212 is a block diagram 1200 illustrating a software architecture 1204 that can be installed on any one or more of the devices described herein. The software architecture 1204 is supported by hardware such as a machine 1202, which includes a processor 1220, a memory 1226, and an I / O component 1238. In this example, the software architecture 1204 can be conceptualized as a stack of layers, where each layer provides specific functionality. The software architecture 1204 includes layers such as an operating system 1212, a library 1210, a framework 1208, and an application 1206. In operation, the application 1206 enables an API call 1250 through the software stack and receives a message 1252 in response to the API call 1250.

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

[0159] The libraries 1210 provide a common low-level infrastructure used by the applications 1206. The libraries 1210 may include a system library 1218 (e.g., a C standard library) that provides functions such as memory allocation functions, string manipulation functions, mathematical functions, etc. In addition, the libraries 1210 may include an API library 1224, 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 1210 may also include various other libraries 1228 to provide many other APIs to the application 1206 .

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

[0161] In an example, applications 1206 may include a home application 1236, a contacts application 1230, a browser application 1232, a reader application 1234, a positioning application 1242, a media application 1244, a messaging application 1246, a game application 1248, and a variety of other applications such as third-party applications 1240. Application 1206 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 1206 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 1240 (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 1240 can enable API calls 1250 provided by the operating system 1212 to facilitate the functions described herein.

[0162] Processing components

[0163] Now go to Fig.13 , which shows a diagrammatic representation of a processing environment 1300 that includes a processor 1302, a processor 1306, and a processor 1308 (eg, a GPU, a CPU, or a combination thereof).

[0164] Processor 1302 is shown coupled to power supply 1304 and includes modules (permanently configured or temporarily instantiated), namely, communication processing component 1310, RPC component 1312, and presentation component 1314. Communication processing component 1310 is enabled to process wireless communications. For example, an example of communication processing component 1310 includes wireless interface 603, wireless interface 634, BLE communicator 802, and BLE RPC handler 810. RPC component 1312 processes RPC requests. Example RPC component 1312 includes remote procedure call module 604, remote procedure call module 626, and service manager 820.

[0165] The presentation component 1314 presents the interface and handles user input and output. The example presentation component 1314 includes the settings category module 606 and the settings category module 627. The settings 610, 630 and other data can be located in a memory associated with the processor 1302. As shown, the processor 1302 is communicatively coupled to both the processor 1306 and the processor 1308.

[0166] Glossary

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

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

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

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

[0171] "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 of specific processing or control functions. Components can be combined with other components via their interfaces to perform machine processes. Components can be packaged functional hardware units designed for use with other components, and can be part of a program that generally performs specific functions in related functions. Components can constitute software components (e.g., codes embodied on machine-readable media) or hardware components. "Hardware components" are tangible units that can perform certain operations and can be configured or arranged in a certain physical manner. In various examples, one or more computer systems (e.g., independent computer systems, client computer systems, or server computer systems) or one or more hardware components (e.g., processors or processor groups) of a computer system can be configured 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 system 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 of the hardware components does not need to be configured or instantiated at any time. For example, in the case where a hardware component includes a general-purpose processor that is configured by software to be a special-purpose processor, the general-purpose processor can be configured as different special-purpose processors (e.g., including different hardware components) at different times. Software accordingly configures one or more specific processors to, for example, constitute a specific hardware component at one time and constitute different hardware components at different times. Hardware components can provide information to other hardware components and receive information from other hardware components. Therefore, the described hardware components can be considered to be communicatively coupled.In the case of multiple hardware components being present at the same time, communication can be achieved by signal transmission (e.g., by appropriate circuits and buses) between or among two or more hardware components. In examples where multiple hardware components are configured or instantiated at different times, communication between such hardware components can be achieved, for example, by storing information in a memory structure accessible to multiple hardware components and retrieving information in the memory structure. For example, a hardware component can perform an operation and store the output of the operation in a memory device to which it is communicatively coupled. Then, other hardware components can access the memory device at a subsequent time to retrieve and process the stored output. The hardware component can also initiate communication with an input device or an output device, and can operate on resources (e.g., a collection of information). The various operations of the example methods described herein can be performed at least in part by one or more processors that are temporarily configured (e.g., by software) or permanently configured to perform related operations. Whether it is temporarily configured or permanently configured, such a processor can constitute a processor-implemented component that operates to perform one or more operations or functions described herein. As used herein, "processor-implemented components" refer to hardware components implemented using one or more processors. Similarly, the method described herein can be implemented at least in part by a processor, wherein specific one or more processors are examples of hardware. For example, at least some of the operation of the method can be performed by one or more processors or the parts implemented by the processor. In addition, one or more processors can also operate to support the execution of related operations in a "cloud computing" environment or as "software as a service" (SaaS). For example, at least some of the operations in the operation can be performed by a group of computers (as an example of a machine including a processor), wherein these operations can be accessed via a network (for example, the Internet) and via one or more appropriate interfaces (for example, API). The execution of some operations in the operation can be distributed among the processors, not only resident in a single machine, but also deployed across multiple machines. In some examples, the processor or the parts implemented by the processor can be located in a single geographical location (for example, in a home environment, an office environment or a server group). In other examples, the processor or the parts implemented by the processor can be distributed across multiple geographical locations.

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

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

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

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

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

Claims

1. A method performed on an augmented reality (AR) wearable device, the method comprising: receiving a first remote procedure call (RPC) from a client device, the RPC indicating a request to provide setting names and setting values ​​for a plurality of setting categories; retrieving the setting names and the setting values ​​for the plurality of setting categories; as well as A second RPC is sent to the client device, the second RPC indicating the setting names and the setting values ​​for the plurality of setting categories.

2. The method according to claim 1, wherein: Receiving also includes: The first RPC is received by a first processor of the AR wearable device from a client device, the first RPC indicating the request for providing setting names and setting values ​​for a plurality of setting categories.

3. The method according to claim 2, further comprising: Prior to the retrieving, sending the RPC to a service manager on a second processor of the AR wearable device, and wherein the retrieving further comprises: The setting names and the setting values ​​for the plurality of setting categories are retrieved from the service manager.

4. The method according to claim 1, further comprising: Bluetooth Low Energy (BLE) is used to associate with the client device, and wherein the receiving and the transmitting are via BLE.

5. The method according to claim 1, wherein: The multiple setting categories include: a camera service setting category, a lens application setting category, an account service setting category, a boot Windows to audit mode (OOBE) service setting category, and a default AR wearable device setting category.

6. The method according to claim 5, wherein: The default AR wearable device setting categories include display brightness setting, input mode selection, and timeout period selection.

7. The method according to claim 1, further comprising: A third RPC is received by the first processor of the AR wearable device from the client device, the third RPC indicating a setting name and a setting value for a setting category among the multiple setting categories, wherein the third RPC also indicates that the AR wearable device is to set a setting indicated by the setting name with a value indicated by the setting value for the setting category.

8. The method according to claim 7, further comprising: Sending the third RPC to a service manager on a second processor of the AR wearable device; as well as The setting indicated by the setting name having the value indicated by the setting value for the setting category is set by the service manager.

9. The method according to claim 1, further comprising: A third RPC is received from the client device, the third RPC indicating a request to provide setting names and setting values ​​for all setting categories.

10. The method according to claim 1, further comprising: A third RPC is received from the client device, the third RPC indicating a request to provide a setting name and a setting value for a setting category in the plurality of setting categories.

11. The method according to claim 1, further comprising: receiving, via a user interface of the AR wearable device, a changed one of the setting values; setting an indication that the setting value has been changed, the indication being associated with the setting value; receiving a third RPC from the client device, the third RPC indicating a request for all setting values ​​that have been changed; as well as A fourth RPC is sent to the client device, the fourth RPC indicating the changed setting value.

12. The method according to claim 1, further comprising: sending a request to the application server for a suggested value for the setting; as well as The suggested value for the setting is received from the application server.

13. A method performed on a client device, the method comprising: sending a first remote procedure call (RPC) to an augmented reality (AR) wearable device, the first RPC indicating a request for providing a setting name and a setting value for a setting category in a plurality of setting categories; receiving, from the AR wearable device, the setting name and the setting value for the setting category among the plurality of setting categories; displaying the setting name and the setting value for the setting category on a display of the client device; as well as In response to receiving a change to one or more of the setting values, sending a second RPC to the AR wearable device, the second RPC indicating the change to the one or more setting values.

14. The method according to claim 13, wherein: The setting category is a first setting category, and wherein the method further comprises: receiving a third RPC from the AR wearable device, the third RPC indicating a request by the AR wearable device for a setting value for a second setting category among the plurality of setting categories; and A fourth RPC is sent to the AR wearable device, where the fourth RPC indicates the setting value for the second setting category.

15. The method according to claim 13, further comprising: Associating with the AR wearable device using Bluetooth Low Energy (BLE), and wherein the receiving is via BLE.

16. A non-transitory computer-readable storage medium comprising instructions that, when executed by an augmented reality (AR) wearable device, cause the AR wearable device to perform operations comprising: receiving a first remote procedure call (RPC) from a client device, the RPC indicating a request to provide setting names and setting values ​​for a plurality of setting categories; retrieving the setting names and the setting values ​​for the plurality of setting categories; as well as A second RPC is sent to the client device, the second RPC indicating the setting names and the setting values ​​for the plurality of setting categories.

17. The non-transitory computer readable storage medium of claim 16, wherein: Receiving also includes: The RPC is received by a first processor of the AR wearable device from a client device, the RPC indicating a request for providing setting names and setting values ​​for a plurality of setting categories.

18. The non-transitory computer readable storage medium of claim 17, wherein: The operations also include: Prior to the retrieving, sending the RPC to a service manager on a second processor of the AR wearable device, and wherein the retrieving further comprises: The setting names and the setting values ​​for the plurality of setting categories are retrieved from the service manager.

19. The non-transitory computer readable storage medium of claim 16, wherein: The operations also include: The method is associated with the client device using BLE, and wherein the receiving and the transmitting are both via BLE.

20. The non-transitory computer readable storage medium of claim 16, wherein: The operations also include: The user of the AR wearable device changes a setting value in the setting values ​​using a user interface of the AR wearable device; setting an indication that the setting value has been changed, the indication being associated with the setting value; receiving a third RPC from the client device, the third RPC indicating a request for all setting values ​​that have been changed; and A fourth RPC is sent to the client device, the fourth RPC indicating the changed setting value.

Images