Remote annotation and navigation in augmented reality

Abstract

Systems, methods, and computer-readable media for sending remote annotation, mapping, and navigation instructions from a computing device to an augmented reality (AR) wearable device are disclosed. The AR wearable device captures an image and sends the image to a remote computing device to provide a real-time view of content seen by a user of the AR wearable device. A user of the remote computing device may add navigation instructions and may select images to annotate or draw. The AR wearable device provides 3D coordinate information within a 3-dimensional (3D) world of the AR wearable device for the selected image. A user of the remote computing device then annotates or draws on the selected image. The remote computing device determines 3D coordinates for annotation and mapping within the 3D world of the AR wearable device. The annotations and drawings are sent to the AR wearable device along with the associated 3D coordinates.

Description

[0001] Priority declaration

[0002] This application claims the benefit of U.S. patent application serial number 18 / 046,367, filed on October 13, 2022, the entire contents of which are hereby incorporated by reference. Technical Field

[0003] Examples of the present disclosure generally relate to remote annotation, drawing, and navigation between augmented reality (AR) wearable devices and computing devices. More particularly, but not by way of limitation, examples of the present disclosure relate to an AR wearable device that captures an image of a scene, determines 3-dimensional (3D) world coordinates of the scene, and enables a user of a computing device to add annotations, drawings, and navigation directions to the 3D world of the AR wearable device. Background Art

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

[0005] In the accompanying drawings (which are not necessarily drawn to scale), similar reference numerals may describe similar components in different views. To easily identify the discussion of any particular element or action, the 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 6A system for remote annotation and navigation using an AR wearable device according to some examples is shown.

[0012] Figure 7 A system for remote annotation and navigation using an AR wearable device according to some examples is shown.

[0013] Figure 8 Operation of a system for remote annotation and navigation using an AR wearable device is illustrated according to some examples.

[0014] Fig. 9 Operation of a system for remote annotation and navigation using an AR wearable device is illustrated according to some examples.

[0015] Fig.10 Operation of a system for remote annotation and navigation using an AR wearable device is illustrated according to some examples.

[0016] Fig.11 A perspective view of a wearable electronic device in the form of glasses 1100 is shown according to some examples.

[0017] Fig.12 Methods for remote annotation and navigation using an AR wearable device according to some examples are shown.

[0018] Fig.13 Methods for remote annotation and navigation using an AR wearable device according to some examples are shown.

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

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

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

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

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

[0024] The AR wearable device 602 (e.g., AR glasses 1100) has limited battery power. In addition, the AR wearable device 602 is tightly coupled to its user when worn. For example, the user A 644 of the AR wearable device 602 may not want to restrict its movement to accommodate the application's need for the AR wearable device 602 to remain in a fixed location. In addition, the user of the AR wearable device 602 will often want to communicate with a remote user of the computing device 702, where the communication is contextualized into what the user of the AR wearable device 602 sees.

[0025] One challenge is how to enable remote user B 744 of computing device 702 to provide augmentations 786 that can be seen by user A 644 of AR wearable device 602. This challenge is addressed by AR wearable device 602 streaming images 616 to computing device 702, where the images 616 enable user B 744 of computing device 702 to see what user A 644 of the AR wearable device sees. This is accomplished by capturing an image of the user's view 672 of the real world scene 670 and by providing display parameters 684 of the display of the AR wearable device 602 to computing device 702.

[0026] While viewing the live feed as image 616, user B 744 of computing device 702 can send navigation directions to AR wearable device 602 in real time, where the navigation directions are based on what user A 644 of AR wearable device 602 actually sees. In some examples, the AR wearable device incorporates the augmentations displayed to user A into the image 616 sent to computing device 702. In this way, user B 744 sees not only the real world scene 670 seen by user A 644, but also any augmentations 686, such as object identification, displayed to user A 644 by AR wearable device 602.

[0027] Additionally, while user B 744 is viewing a live display of what user A 644 sees, user B 744 may select an image 716 to add an augmentation 786. The computing device 702 sends an identification of the selected image 716, and the AR wearable device 602 performs image processing, which may be remote, to determine 3D coordinates 661 within the corresponding image 616, where the 3D coordinates 661 are within the 3D world coordinate 688 system of the AR wearable device 602. The computing device 702 may then determine 3D coordinates 790 within the 3D world coordinate 688 system of the AR wearable device 602 for the augmentation 786 created by user B 744 of the computing device 702. The computing device 602 sends the augmentation 786 created by user B 744 and the associated 3D coordinates 790 to the AR wearable device 602.

[0028] The AR wearable device 602 then adds the augmentation 786 to the 3D world coordinate system 688 of the AR wearable device 602 and displays the augmentation 786 to the user A 644 at the appropriate viewing angle and in its appropriate location when the augmentation 786 is visible to the user A 644. By determining the 3D coordinates 661 within 616 for only one or a limited number of images 616, the AR wearable device 602 is able to reduce the energy required to provide the ability to share annotations and drawings.

[0029] Furthermore, by selecting or freezing the live view with a single image 716 for user B 744 to annotate and draw, user A 644 of the AR wearable device 602 can continue what they are doing without having to remain in a fixed location while user B 744 generates augmentations 786. For example, if user A 644 is in a grocery store and asks their partner for help in selecting breakfast cereal, user B 744 can select the image 716 of breakfast cereal in the live feed and decide which cereal they want and highlight that cereal by generating augmentations 786. Meanwhile, user A 644 can select peanut butter and then return to the breakfast cereal, where augmentations 786 added to the 3D world coordinate system 688 will indicate user B 744's selection of breakfast cereal.

[0030] Networked computing environment

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

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

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

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

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

[0036] The application program interface (API) server 116 receives and sends message data (e.g., commands and message payloads) between the client device 102 and the application server 114. Specifically, the application program interface (API) server 116 provides a set of interfaces (e.g., routines and protocols) that can be called or queried by the messaging client 104 to activate the functions of the application server 114. An application program interface (API) server 116 exposes various functions supported by application server 114, including: account registration; login functionality; sending messages from a particular messaging client 104 to another messaging client 104 via application server 114; sending media files (e.g., images or videos) from a messaging client 104 to messaging server 118, and for possible access by another messaging client 104; setting 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).

[0037] The application server 114 hosts several server applications and subsystems, including, for example, a messaging server 118, an image processing server 122, and an input modality server 124. The messaging server 118 implements several message processing 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.

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

[0039] 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 names of the objects within the sensor data and the locations of the objects 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.

[0040] 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 installed on the client device 102 (e.g., a "local application"), or a small-scale version of the application hosted on the client device 102 or away from the client device 102 (e.g., on a third-party server 110) (e.g., a "applet"). 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).

[0041] 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, all parts of the small-scale application cannot be accessed outside the messaging client 104, or limited parts of the small-scale application can be accessed outside the messaging client 104. The small-scale application can be launched by the messaging client 104 receiving a markup language document associated with the small-scale application, for example from a third-party server 110, and processing such a document.

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

[0043] The messaging client 104 may notify the user of the client device 102 or other users (e.g., "friends") associated with such a user of activities occurring in one or more external resources. For example, the messaging client 104 may provide a notification to a participant in a conversation (e.g., a chat session) in the messaging client 104 about 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.

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

[0045] System Architecture

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

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

[0048] 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 that provides notification of the existence of a particular collection to the user interface of the messaging client 104.

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

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

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

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

[0053] The mapping system 210 provides various geographic 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 map interface of the messaging client 104.

[0054] 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 providing in-game rewards (e.g., game coins and items).

[0055] 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 activated by a WEB-based application. In some examples, the messaging server 118 includes a JavaScript library that provides a given external resource access to certain user data of the messaging client 104. HTML5 is used as an example technology for programming games, but applications and resources programmed based on other technologies can be used.

[0056] In order to integrate the functions of the SDK into the WEB-based resource, the SDK is downloaded by the third-party server 110 from the messaging server 118, or received by the third-party server 110 in other ways. Once downloaded or received, the SDK is included as part of the application code of the WEB-based external resource. Then, the code of the WEB-based resource can call or activate certain functions of the SDK to integrate the features of the messaging client 104 into the WEB-based resource.

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

[0058] 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 indicates that the messaging client 104 accesses the features of the WEB-based external resource through the GUI of the messaging client 104, the messaging client 104 obtains the HTML5 file and instantiates the resources required to access the features of the WEB-based external resource.

[0059] 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 external resource launched has been previously authorized to access the user data of the messaging client 104. In response to determining that the launched external resource has previously been 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 previously been authorized to access the user data of the messaging client 104, after a threshold time period (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.

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

[0061] Image processing system 216 supports AR wearable device 602 ( Figure 6 ) and computing device 702 ( Figure 7 ). The image processing system 216 receives requests from the AR wearable device 602 and the computing device 702 and responds to the requests. Figure 6 As described, the request includes a request to process an image, such as image 616, to generate an object with 3D coordinates 661. Another request is to process image 716 with associated 3D coordinates 771 to determine 3D coordinates 790 of augmentation 786. Image processing system 216 can facilitate communication between computing device 702 and AR wearable device 602 by providing a store and forward service for messages that may include image 616. AR wearable device 602 and computing device 702 can request other services from image processing system 216.

[0062] Data Architecture

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

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

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

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

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

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

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

[0070] 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 the messaging client 104 when the sending user is composing a message. Other types of filters include geo-location filters (also referred to as geo-filters), which can be presented to a sending user based on geo-location. For example, a geo-location filter specific to a nearby or special location can be presented by the messaging client 104 within a user interface based on geo-location information determined by a global positioning system (GPS) unit of the client device 102.

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

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

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

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

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

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

[0077] 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 location for each element of at least one element, and the properties of the area can be modified based on the request for modification, thereby transforming the frame of the video stream. Depending on the specific request for modification, the properties of the mentioned area can be transformed in different ways. Such modifications may involve: changing the color of the area; removing at least some parts of the area from the frame of the video stream; including one or more new objects in the area, which is based on the request for modification; and modifying or distorting the elements of the area or object. In various examples, any combination of such modifications or other similar modifications may be used. For certain models to be animated, some characteristic points may be selected as control points for determining the entire state space of options for model animation.

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

[0079] 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 pupil can be used. If the initial landmarks are not recognizable (for example, if the person has an eye mask), secondary landmarks can be used. Such a landmark recognition process can be used for any such object. In some examples, the set of landmarks forms a shape. The shape can be represented as a vector using the coordinates of the points in the shape. One shape is aligned with another shape using a similarity transformation (allowing translation, scaling, and rotation) that minimizes the average Euclidean distance between the shape points. The average shape is the average of the aligned training shapes.

[0080] In some examples, the landmark search begins with a mean shape aligned with the location and size of the face determined by a global face detector. Such a search then repeats the steps of proposing tentative shapes by adjusting the location 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, individual template matches are unreliable, and the shape model pools the results of weak template matches to form a stronger overall classifier. The entire search is repeated at each level of the image pyramid from coarse resolution to fine resolution.

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

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

[0083] The graphical user interface presenting the modification performed by the transformation system can provide additional interactive options to the user. Such options can be based on an interface for initiating content capture and selecting a specific computer animation model (e.g., initiated from a content creator user interface). In various examples, after the initial selection of the modification icon, the modification can be persistent. 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 being 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.

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

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

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

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

[0088] Data communication architecture

[0089] 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 to include the following example components:

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

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

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

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

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

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

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

[0097] 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 within a message video payload 408).

[0098] Message story identifier 418: An identifier value that identifies one or more content collections (e.g., "Stories" 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.

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

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

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

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

[0103] Time-based access restriction architecture

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

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

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

[0107] exist Figure 51. Ephemeral message 502 is shown as being included in 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.

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

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

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

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

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

[0113] Remote annotation and navigation using AR wearables

[0114] Figure 6 A system 600 for remote annotation and navigation using an AR wearable device is shown according to some examples. The system 600 includes an AR wearable device 602, such as Fig.11 The glasses 1100 may include other devices that can perform one or more of the operations described herein, such as a portion of the messaging server system 108, the client device 102, the image processing system 216, and / or the computing device 702.

[0115] AR wearable device 602 and Figure 7The AR wearable device 602 interacts with the computing device 702. The AR wearable device 602 sends audio 680, an image 616 with 3D coordinates 661, and optional enhancements 686 to the computing device 702. The computing device 702 sends commands 647, audio 662, and enhancements 786 with 3D coordinates 790 to the AR wearable device 602.

[0116] Input / output (IO) devices 604 include devices that enable user A 644 to receive output or provide input to system 600. IO devices 604 include microphone 606, display 610, speaker (not shown), image capture device 608, button 612, touch pad 613, gyroscope (not shown), etc. According to some examples, image capture device 608 captures image 616 of real world scene 670 as a front view of user view 672, which is what user A 644 sees through AR wearable device 602. Location (loc) 673 is a 3D coordinate indicating the location of user view 672 within 3D world coordinate system 688. Image capture device 608 can be a charge coupled device (CCD) or another type of device for capturing images of real world scene 670. Fig.11 The buttons 1178 and touchpad 1176 of are examples of buttons 612 and touchpad 613, respectively. The buttons 612 and touchpad 613 enable user A 644 to provide tactile 646 input. The microphone 606 enables user A 644 to provide voice 650 input. The image capture device 608 enables user A 644 to provide gesture 648 input via the UI module 634, which processes or analyzes the image 616 to determine the user intent 636 based on the gesture 648.

[0117] Some devices, such as a gyroscope, may be both a sensor 614 and an IO device 604. For example, user A 644 may move the AR wearable device 602, which changes the position 652 of user A 644 and transmits input to the AR wearable device 602. According to some embodiments, it is assumed that the position of user A 644 is the same as the AR wearable device 602. The AR wearable device 602 detects the change in position 652 using a sensor 614, such as a gyroscope or another position change sensor, to detect the change in position 652 of user A 644. The movement of user A 644 may have a user intent 636 to transmit input to the AR wearable device 602. However, user A 644 may move with the AR wearable device 602 without a user intent 636 to transmit input to the AR wearable device 602.

[0118] The sensor 614 includes a gyroscope, a light sensor, a positioning sensor, a clock, etc. The clock (not shown) generates a coordinated universal time (UTC) 655. The wireless module 659 communicates 654, 657 with the backend 618 and / or the computing device 702. The wireless module 659 is configured to perform wireless communication protocols with the computing device 702, the backend 618, and / or the intermediate device, wherein the communication protocol includes LE Bluetooth, the Institute of Electrical and Electronics Engineers (IEEE) 802.11 communication protocol, a proprietary communication protocol, a 3GPP communication protocol, etc. The wireless module 659 establishes a wireless communication link between the AR wearable device 602 and the computing device 702, the backend 618, and / or the intermediate device. For example, the wireless module 659 is associated with a corresponding communication module 759 on the computing device 702 and / or the backend 618. The wireless module 659 can communicate with the computing device 702 and / or the backend 618 via another intermediate device such as the user device 102, which can also be the backend 618, an access point, or a node B. In some examples, the wireless module 659 can be used to determine the location and / or orientation of the AR wearable device 602 with the assistance of other wireless devices.

[0119] The assistance state 664 is stored in the memory of the AR wearable device 602 and indicates whether the assistance state 664 is "on" or "off". The assistance state 664 is a state in which the AR wearable device 602 and the computing device 702 communicate with each other for remote annotation and navigation discussed herein. The assistance state 664 is changed based on input from user A 644 and user B 744. User A 644 or user B 744 can request to enter the assistance state 664. The AR wearable device 602 or the computing device 702 will contact the other device and request to enter the assistance state 664. In some examples, the image display module 624 receives a request to enter the assistance state 664 from the computing device 702. The image display module 624 asks user A 644 whether user A 644 wants to enter the assistance state 664. Similarly, the image display module 724 of the computing device 702 can receive a request to enter the assistance state 764 from the AR wearable device 602. In some examples, the auxiliary state 664 has two states: "on" and "off".

[0120] If the auxiliary state 664 is "on", the image display module 624 causes the image capture device 608 to begin capturing an image 616. In some examples, if the image 616 has already been captured, the existing image 616 can be used by the image display module 624. In some examples, as indicated by the user view 672, there are multiple image capture devices 608, and the image display module 624 selects one or more image capture devices 608 that are forward-looking or overlay the real world scene 670 seen by the user A 644 through, for example, the glasses 1100. In some implementations, the image 616 includes more than the user view 672. For example, the image 616 can provide a 360-degree view of the real world scene 670.

[0121] The image display module 624 causes the image 616 to be sent or streamed to the computing device 702. The image display module 624 includes the UTC 655 or associates the UTC 655 with each of the images 616, or another type of identification associated with each of the images 616. In addition, the image display module 624 sends display parameters 684 to the computing device 702. The display parameters 684 enable the computing device 702 to simulate the display 610 of the AR wearable device 602. The display parameters 684 include aspect ratio, screen resolution, etc. The image 616 is stored in the memory of the AR wearable device 602 for a buffer period, such as several seconds, such as 5 to 100 seconds. In some examples, the image display module 624 causes the audio 680 to be captured by the microphone 606 and sent or streamed simultaneously with the image 616.

[0122] In some examples, the image display module 624 sends the enhancement 686 with the 3D coordinates 690 of the enhancement created by the user A 644. In some examples, the enhancement 686 does not include the 3D coordinates 690 and is intended to be displayed on the display 710 of the computing device when the image 616 is displayed as a video. In some examples, the enhancement 686 includes an enhancement generated by the AR wearable device 602, such as a label of the object 656. In some examples, the image display module 624 incorporates the enhancement 686 into the image 616 so that the image 616 represents what is displayed on the display 610 of the AR wearable device 602.

[0123] The image display module 624 responds to the command 647 received from the computing device 702 and causes the audio 662 to be played on the speaker of the AR wearable device 602. The image display module 624 responds to the command 647 from the computing device 702, indicating that the computing device 702 is requesting to send 3D coordinates 661 for the image 616 with UTC 655. The image display module 624 uses the machine learning (ML) module 621 or the ML module 620 that sends the image 616 to the backend 618 to process the image 616 to generate the 3D coordinates 661 and, in some examples, the object 656 of the image 616. According to some examples, the ML module 621 and the ML module 620 are configured to operate according to Visual Inertial Odometry (VIO) to determine the 3D world coordinate 688 system. In some examples, ML module 621 and ML module 620 operate by using other computer vision or machine learning techniques such as deep learning to identify object 656. According to some examples, 3D coordinates 661 are in a 3D world coordinate system 688 of AR wearable device 602. In some examples, 3D coordinates 661 are in a 3D coordinate system relative to the position of AR wearable device 602.

[0124] In some examples, the 3D coordinates 661 are a point cloud where the 3D position is indicated for the x position and the y position within the image 616. Once the 3D coordinates 661 of the image 616 are determined, the image display module 624 sends the 3D coordinates 661 to the computing device 702. For the enhancements 786 to be displayed on the display 610 or to be added to the 3D world coordinates 688 of the AR wearable device 602, the computing device 702 sends the enhancements 786 to the AR wearable device 602 and issues instructions 647.

[0125] The image display module 624 processes the enhancements 786 and displays them on the display 610 for user A644 to view in conjunction with the user view 672 of the real world scene 670. The adjustment module 626 projects or adjusts the enhancements 686 so that it is at the appropriate viewing angle for the location 673 of the user view 672. For example, the size and angle of the line are adjusted according to how far it is from the AR wearable device 602. The placement of the enhancements 686 is based on the 3D coordinates 790 within the 3D world coordinate system 688. Enhancements 786 and enhancements 686 can be AR graphics. The term AR graphics includes anything displayed by the AR wearable device 602 on the display 610 for user A644 to view in conjunction with viewing the real world through the lens. Alternatively, user A644 can view the real world by capturing the image 616 through the AR wearable device 602 and displaying the image 616 and the AR graphics on the opaque display 610.

[0126] The 3D world coordinate system 688 is a coordinate within the real world scene 670 and is determined by the ML module 621 or ML module 620. The 3D world coordinate system 688 may be constructed and updated over time as the ML module 621 or ML module 620 processes the image 616 and / or uses the location (loc) 673 data.

[0127] In some examples, if the 3D coordinates 790 indicate that the augmentation 786 will not be visible to the user A 644 based on the location 673 of the user view 672 of the real-world scene 670, then the augmentation 786 is not displayed. For example, continuing with the above example, the user A 644 may have turned his head to see the peanut butter, making the cereal not visible.

[0128] In some examples, the motion sensor 614 is used to determine the movement 666 of the AR wearable device 602. Then, the change of the location 673 is determined based on the movement 666. According to some examples, the enhancements 786 and 686 can be moved by a number of pixels based on the movement 666 of the AR wearable device 602. The image display module 624 can display the enhancements 786 and 686 based on the 3D coordinates 690, 790 and the location 673 of the user view 672. This is because the 3D coordinates 690, 790 and the location 673 are 3D coordinates within the 3D world coordinate 688 system.

[0129] In some examples, if the enhancement 786 is not visible within the user view 672, the image display module 624 displays an indication on the display 610 that there is an unviewed enhancement 786. In some examples, the image display module 624 determines the direction that the user A 644 will have to travel to be able to see the enhancement 786, and displays an indication of that direction on the display 610.

[0130] In addition, the image display module 624 responds to the command 647 to display the enhancement 644 in real time on the display 610. The enhancement 786 can be a drawing or a direction, such as a left arrow or a right arrow. The enhancement 786 is displayed on the display 610 without regard to the 3D coordinates 790 for a period of time, or in some examples, until the next enhancement 786 is received.

[0131] The UI module 634 processes input from the IO device 604 to determine the user intent 636 from the user A 644. For example, the UI module 634 determines whether the user intent 636 is to turn the auxiliary state 664 to "on" or "off". The UI module 634 provides or displays user interface items, such as a menu for selecting options for enhancements 686. The UI module 634 enables the user A 644 to add enhancements 686, for example, by drawing in the air with his finger. The user A 644 can use gestures 648, such as the movement of his finger, to make a selection. The UI module 634 analyzes the movement of the finger by analyzing the images 616 captured over time. The UI module 634 can determine or estimate the gaze position of the user A 644.

[0132] User 638 is data related to user A 644. Information (info) 642 includes input data from user A 644 and may include additional information about user A 644, such as social media accounts logged into the messaging server system 108, user names, and the like.

[0133] Figure 7 1 shows a system 700 for remote annotation and navigation using an AR wearable device according to some examples. The system 700 includes a computing device 702, such as a user device 102, Fig.14 The system 700 may include other devices that can perform one or more of the operations described herein, such as a portion of the messaging server system 108, the client device 102, the image processing system 216, and / or the AR wearable device 602.

[0134] Computing device 702 interacts with AR wearable device 602. AR wearable device 602 sends audio 680, image 616 with 3D coordinates 661, and optional augmentations 686 to computing device 702. Computing device 702 sends commands 647, audio 662, and augmentations 786 with 3D coordinates 790 to AR wearable device 602.

[0135] Input / output (IO) devices 704 include devices that enable user B 744 to receive output or provide input to system 700. IO devices 704 include microphone 706, display 710, speakers (not shown), image capture device 708, buttons 712, touch pad 713, etc. Image capture device 708 captures images (not shown) to provide tactile 746 input. Microphone 706 enables computing device 702 to capture audio 662 data to send to AR wearable device 602 and provide voice 750 input.

[0136] The communication module 759 communicates 757 between the computing device 702 and the AR wearable device 602. The communication module 759 is configured to perform wireless communication protocols with the AR wearable device 602 and / or an intermediate device, wherein the communication protocol includes, for example, LE Bluetooth, Institute of Electrical and Electronics Engineers (IEEE) 802.11 communication protocol, proprietary communication protocol, 3GPP communication protocol, etc. The communication module 759 establishes a wireless communication link between the AR wearable device 602 and the computing device 702, the backend 618, and / or the intermediate device. For example, the communication module 759 is associated with a corresponding wireless module 659 on the AR wearable device 602. The communication module 759 can communicate with the AR wearable device 602 via an intermediate device such as the user device 102, which can also be the backend 618, an access point, or a node B. For example, the AR wearable device 602 can communicate with the user device 102, the user device 102 can communicate with the messaging server system 108, and the messaging server system 108 can communicate with the computing device 702 via the Internet and a 3GPP connection. In some embodiments, the communication module 759 can be used to determine the location and / or orientation of the computing device 702 with the assistance of other wireless devices.

[0137] The assistance state 764 is stored in the memory of the computing device 702 and indicates that the state of the assistance state 764 is "on" or "off". The assistance state 764 is a state in which the AR wearable device 602 and the computing device 702 communicate with each other for remote annotation and navigation discussed herein. The assistance state 764 is changed based on input from user B 744 and user A 644. User A 644 or user B 744 can request to enter the assistance state 764 or set the assistance state 764 to a value of "on". The AR wearable device 602 or the computing device 702 will contact the other device and request to enter the assistance state 764. In some examples, the image display module 724 receives a request to enter the assistance state 764 from the AR wearable device 602. The image display module 724 asks user B 744 whether he wants to enter the assistance state 764. Similarly, the image display module 624 of the AR wearable device 602 can receive a request to enter the assistance state 764 from the computing device 702. In some examples, the auxiliary state 764 has two states: "on" and "off".

[0138] If the auxiliary state 764 is "on", the image display module 724 accesses the images 716 received from the AR wearable device 602 as images 616 and displays them on the display 710 for consumption by user B 744. The display parameters 684 are received from the AR wearable device 602 or from a configuration operation. The image display module 724 uses the display parameters 684 to simulate the display 610 of the AR wearable device 602 to display the images 616 on the display 710. User B 744 then sees the images 616 on the display 710 in the same way that user A 644 sees the images 616 on the display 610.

[0139] The image display module 724 plays the audio 680 received from the AR wearable device 602 simultaneously with the image 716. In addition, the image display module 724 captures the audio 662 from the microphone 706 and streams the audio to the AR wearable device 602.

[0140] The UI module 734 processes input from the IO device 704 to determine a user intent 737 from the user B 744. For example, the UI module 734 determines whether the user intent 737 is to turn the auxiliary state 764 to "on" or "off". The UI module 734 provides or displays user interface (UI) 723 items, such as a menu for selecting options for commands 782 or enhancements 786. The UI module 734 enables the user B 744 to add an enhancement 786, for example, by the user B 744 drawing the enhancement 786 using his finger in the air, a mouse, a touch screen, selecting or drawing a geometric shape or line, or some other method. In some examples, when the object 656 is identified, the UI module 734 recognizes the user intent 737 to select the object 656, and the enhancement 786 is a highlight of the object 656.

[0141] User 738 is data related to user B 744. Information (info) 742 includes input data 756 from user B 744 and may include additional information about user B 744, such as social media accounts logged into the messaging server system 108, user names, and the like.

[0142] The image display module 724 displays the augmentation 686 from the AR wearable device 602 with the image 716, which is the received image 616. In some examples, the augmentation 686 includes an identifier, such as UTC, to indicate that the augmentation 686 should be displayed with one or more specific images 616.

[0143] There are two types of enhancements 786. A first type of enhancement 786, where user B 744 adds the enhancement 786 to the selected image 716, and determines the 3D coordinates 790 of the enhancement 786. A second type of enhancement 786, where the enhancement 786 is added to the image 716 by user B 744 while the real-time video of the image 716 is playing, and the 3D coordinates 790 are not determined.

[0144] The image display module 724 responds to the command 782 from the user B 744. In response to the user B 744 generating the first type of enhancement 786, the image display module 724 sends the enhancement 786 to the AR wearable device 602 for the AR wearable device 602 to display the enhancement 786 on the display 610. The first type of enhancement 786 can be a direction, a highlight arrow, a free-form drawing, or another enhancement. The first type of enhancement 786 can include UTC 755 to indicate which 716 or images 716 the enhancement 786 is added to.

[0145] While the image 716 is displayed on the display 710, user B 744 may select a command 782 of "Edit". When the "Edit" command 782 is selected by user B 744, the image display module 724 responds to the command "Edit" by displaying the selected image 716 being played on the display 710. The image 716 is displayed in the simulated display of the display 610 of the AR wearable device 602 using the display parameters 684 on the display 710. The image display module 724 may continue to receive the image 716 from the AR wearable device 602 and play the image 716 in a separate window, which may be referred to as a live feed seen by user A 644.

[0146] The image display module 724 then sends the UTC 755 or another identifier to the AR wearable device 602. The AR wearable device 602 responds with the 3D coordinates 661 of the selected image 716. In some examples, the 3D coordinates 661 are sent with the image 616, so the image display module 724 does not have to send the UTC 755 to the AR wearable device 602.

[0147] The enhancement 786 whose 3D coordinates 790 are determined by the ML module 721 is the second type of enhancement 786. The following is an example of determining the 3D coordinates 790 of the enhancement 786. The ML module 721 uses the 3D coordinates 771, which are the received 3D coordinates 661, to determine the 3D coordinates 790 of the enhancement 786 added by the user B 744. In some examples, the 3D coordinates 771 are a point cloud in which the 3D position is indicated for the x position and the y position within the image 716. The ML module 721 associates the enhancement 786 added by the user B 744 with the coordinates on the display 710 simulated for the display 610. Then, the coordinates of the enhancement 786 on the display 710 are matched with the point cloud to determine the 3D coordinates 790 of the enhancement 786.

[0148] In some examples, the AR wearable device 602 sends object 656 information or other information with 3D coordinates 661 of the selected image 716, which can be used by the ML module 721 to determine the 3D coordinates 790 of the augmentation 786. The ML module 721 uses the object 656 information, which can include, for each object 656, an indication of the area of ​​the image 716 occupied by the object 656, and the 3D coordinates 771 of the object 656.

[0149] ML module 721 may determine 3D coordinates 790 for enhancement 786 based on the relationship of object 656 to enhancement 786. For example, if object 656 is surrounded by a free-form drawing around object 656, ML module 721 gives enhancement 786 3D coordinates 790 that place enhancement 786 around object 656. In some examples, object 656 is a surface of image 716, and ML module 721 determines 3D coordinates 790 based on the relationship of enhancement 786 to the surface represented by the 3D coordinates.

[0150] After the ML module 721 determines the 3D coordinates 790 of the augmentation 786, the image display module 724 sends an indication of the augmentation 786 with the 3D coordinates 790 to the AR wearable device 602. The AR wearable device 602 adds the augmentation 786 to its 3D world coordinates 688. The image display module 724 can close the window opened for the selected image 716 based on a timeout or based on a command by the user B 744.

[0151] Figure 8Operation 800 of systems 600 and 700 is shown in accordance with some embodiments. Display 710 of computing device 702 includes two windows. Video inset 812 window is a real-time view of display 610 of AR wearable device 602. In video inset 812, user B 744 sees user view 672 of real world scene 670, which is captured as image 616 by image capture device 608 and sent to computing device 702.

[0152] The image display module 724 displays an image 716 streamed or sent from the AR wearable device 602 to the computing device 702. UI 2 814 is the UI 723 displayed by the UI module 734. Three commands 782 are available from the UI 2 814. The left arrow, the up arrow, and the right arrow are commands 782. If user B 744 selects one of the arrows, the UI module 734 determines the user intent 737 and passes the user intent 737 to the image display module 724. The image display module 724 sends an enhancement 786 to the AR wearable device 602, where the enhancement 786 is an indication of one of the directional arrows. The AR wearable device 602 displays the enhancement 786 in real time on the display 610 of the AR wearable device 602. For example, Fig.10 Aug 1 1002 is a right arrow sent by the computing device 702 to the AR wearable device 602 during real-time viewing of the display 610 of the AR wearable device 602 .

[0153] The second window occupying the rest of the display 710 is the selected image 716, where user B 744 selects the "Edit" command 782 while viewing the image 716 displayed on the display 710. The image display module 724 simulates the display 610 of the AR wearable device 602 using the display parameters 684 for both the second window and the video insert 812.

[0154] UI 1 804 is UI 723 displayed by UI module 734. UI 1 804 has three commands 782. The top instruction 782 is to refresh display 710. The middle command 782 is a downward arrow for pointing to or emphasizing something in image 716 displayed on display 710. The bottom command 782 enables user B 744 to delete enhancements 786, such as Aug 1 806. Aug 1 806, Aug 2 808, and Aug 3 802 are all enhancements 786 added by user B 744, where the ML module 721 determines the 3D coordinates 790 based on the 3D coordinates 771 and / or the object 656 sent by the AR wearable device 602. The ML module 721 can determine the 3D coordinates 771 of Aug 3 802 based on Aug 3 802 surrounding the object 816 that is a charger on the table. 3D coordinates 771 of selected image 716 displayed in display 710 are a point cloud indicated by a box of 3D coordinates 810. ML module 721 may determine 3D coordinates 790 of enhancement 786 based on proximity of enhancement 786 such as Aug 1 806 to 3D coordinates 810. According to some examples, 3D coordinates 810 are not displayed.

[0155] Fig. 9 Operations 900 of systems 600 and 700 are shown according to some implementations. Fig. 9 Aug 1 806, Aug 2 808, and Aug 3 802 are shown displayed on the display 610 of the AR wearable device 602. The image display module 624 displays Aug 1 806, Aug 2 808, and Aug 3 802 based on the 3D coordinates 790 and the location 673 of the user view 672. For example, if the user A 644 were to turn his head to the left, Aug 1 806, Aug 2 808, and Aug 3 802 would not be displayed because they would not be visible based on their 3D coordinates 790, the location 673 of the user view 672, and the 3D world coordinates 688. In some examples, if Aug 1 806, Aug 2 808, and Aug 3 802 are not visible, the image display module 624 displays an indication that they exist in the 3D world coordinate 688 system. For example, arrows indicating which direction user A 644 would have to turn to see Aug 1 806 , Aug 2 808 , and Aug 3 802 .

[0156] Fig.10 Operations 1000 of systems 600 and 700 are shown according to some embodiments. Fig.10The user view 672 and the UI 11006, Aug 1 1002, and Aug 2 1004 displayed by the image display module 624 on the display 610 are shown. The AR wearable device 602 is capturing and sending a series of images 616 to the computing device 702. The computing device 702 sends Aug 1 1002 (type one enhancement 786) to the AR wearable device 602 for display on the display 610 without 3D coordinates 790. Aug 1 1002 indicates a message from user B 744 to user A 644 to go right. UI 1 1006 is displayed by the UI module 634 and provides three commands. The top command is to refresh the display 610. The middle command is a down arrow, which is used to point to or emphasize something in the user view 672, and the image display module 624 converts something into an enhancement 686 that is sent to the computing device 702 as a separate data structure or integrated into the image 616. The bottom command enables user A 644 to delete an enhancement 686 such as Aug 1 1002. If user A 644 selects the middle command, which is a down arrow, or draws with, for example, Aug 2 1004, the image display module 624 sends the enhancement 686 to the computing device 602 along with an indication of where to display the enhancement 686 relative to the image 616 or integrate the enhancement 686 into the image 616.

[0157] In some examples, the augment 686 is created by the augment 2 1004 and the intermediate commands within the 3D world coordinates 688. For example, the image display module 624 determines the 3D coordinates 690 of the augment 2 1004. The augment 2 1004 then has a location within the 3D world coordinates 688 and will remain located at the location where the user A 644 placed the augment 2 1004. For example, if the user A 644 turns left, the augment 2 1004 will not be visible in the user view 672, and therefore the image display module 624 will not display the augment 2 1004 on the display 610. Furthermore, in some examples, if the augment 2 1004 is visible within the user view 672, the image display module 624 integrates the augment 2 1004 with the image 616 of the captured user view 672. In this way, the user B 644 will see the augment 2 1004 at the same location as the user A 644. Additionally, the graphic 1008 is "In the office," which indicates the location of the AR wearable device 602. The graphic 1008 generated by the image display module 624 may be integrated into the image 616 such that the image 616 captures what the user A 644 sees.

[0158] Fig.11A stereogram of a wearable electronic device in the form of glasses 1100 according to some examples is shown. Glasses 1100 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 or a head-mounted display (HMD). Glasses 1100 may include a frame 1132 made of any suitable material, such as plastic or metal, including any suitable shape memory alloy. Frame 1132 may have a front piece 1133, which may include a first lens or left lens, a display or optical element holder 1136 and a second lens or right lens, a display or optical element holder 1137 connected by a bridge 1138. Front piece 1133 additionally includes a left end portion 1141 and a right end portion 1142. A first optical element or left optical element 1144 and a second optical element or right optical element 1143 may be disposed in respective left optical element holders 1136 and right optical element holders 1137. Each of the optical elements 1143, 1144 can be a lens, a display assembly, or a combination thereof. In some examples, for example, the glasses 1100 are provided with an integrated near-eye display mechanism that enables, for example, displaying a preview image of visual media captured by the camera 1169 of the glasses 1100 to the user.

[0159] The frame 1132 further includes a left arm or temple piece 1146 and a right arm or temple piece 1147, which are coupled to the respective left end 1141, right end 1142 of the front piece 1133 by any suitable means such as a hinge (not shown) to couple to the front piece 1133 or rigidly or fixably fix to the front piece 1133, thereby being integral with the front piece 1133. Each of the temple piece 1146 and the temple piece 1147 may include: a first portion 1151 coupled to the respective end 1141 or 1142 of the front piece 1133; and any suitable second portion 1152 for coupling to the ear of the user, such as a curved or arched piece. In one example, the front piece 1133 can be formed of a single piece of material to have a unitary or integrated construction. In one example, the entire frame 1132 can be formed of a single piece of material to have a unitary or integrated construction.

[0160] Eyeglasses 1100 include a computing device such as computer 1161, which can be of any suitable type to be carried by frame 1132, and in one example, can be of a suitable size and shape to be at least partially disposed in one or more of temple pieces 1146, 1147. In one example, computer 1161 has a size and shape similar to the size and shape of one of temple pieces 1146, 1147, and is thus disposed nearly completely, if not completely, within the structure and confines of such temple pieces 1146, 1147.

[0161] In one example, computer 1161 can be arranged in both temple piece 1146 and temple piece 1147. Computer 1161 can include one or more processors with memory, wireless communication circuit system and power supply. Computer 1161 includes low power circuit system, high speed circuit system, location 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 1161 can be realized with reference to the following description.

[0162] The computer 1161 further includes a battery 1162 or other suitable portable power source. In one example, the battery 1162 is disposed in one of the temple pieces 1146 or the temple pieces 1147. Fig.11 In the illustrated eyeglasses 1100, a battery 1162 is shown disposed in the left temple piece 1146 and electrically coupled to the remainder of the computer 1161 disposed in the right temple piece 1147 using a connector 1174. The one or more input and output devices may include a connector or port (not shown) accessible from the exterior of the frame 1132 suitable for charging the battery 1162, a wireless receiver, transmitter or transceiver (not shown), or a combination of such devices.

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

[0164] In various examples, the glasses 1100 may include any number of input sensors or peripherals in addition to the camera 1169. The front piece 1133 is provided with an outward-facing, front-facing, front or outer surface 1166 that faces forward or away from the user when the glasses 1100 are mounted on the user's face; and an opposite inward-facing, rearward-facing, rear or inner surface 1167 that faces the user's face when the glasses 1100 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 1167 of the front piece 1133 or other locations on the frame 1132 to face the user's camera 1169; and an outward-facing video sensor or digital imaging module, such as may be mounted or disposed on or within the outer surface 1166 of the front piece 1133 or other locations on the frame 1132 to face away from the user's camera 1169. Such sensors, peripherals or peripherals may additionally include biometric sensors, location 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 1143, optical element 1144 (or lenses) to provide a mixed reality or augmented reality experience for the user of glasses 1100.

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

[0166] 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 1132 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 1166 of the frame 1132. 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 1169, and other examples may employ different single action tactile control arrangements.

[0167] The computer 1161 is configured to perform the methods described herein. In some examples, the computer 1161 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 1100. In some examples, the computer 1161 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 1100. In some examples, multiple sets of antennas and circuitry are housed in the glasses 1100. In some examples, the antennas and circuitry are configured to receive signals according to, for example, Bluetooth. TM , Bluetooth Low Energy TM , IEEE 802, IEEE 802.11az / be, and other communication protocols. In some examples, the PDR sensor is housed in the glasses 1100 and coupled to the computer 1161. In some examples, the glasses 1100 are VR headsets, wherein the optical elements 1143 and 1144 are opaque screens for displaying images to a user of the VR headset. In some examples, the computer 1161 is coupled to user interface elements such as a slider or touchpad 1176 and a button 1178. Long pressing the button 1178 resets the glasses 1100. The slider or touchpad 1176 and the button 1178 are used by the user to provide input to the computer 1161 and / or other electronic components of the glasses 1100. The glasses 1100 include one or more microphones 1182 coupled to the computer 1161. The glasses 1100 include one or more gyroscopes 1180.

[0168] Fig.12 A method 1200 for remote annotation and navigation using an AR wearable device according to some examples is shown. The method 1200 begins at operation 1202, accessing an image from an AR wearable device, the image including an identification. For example, the image display module 724 accesses an image 716 from an AR wearable device 602 having an identification UTC 655.

[0169] The method 1200 continues at operation 1204 by sending an identification to the AR wearable device. For example, the image display module 724 sends the UTC 755 associated with the user-selected image 716 to the AR wearable device 602.

[0170] The method 1200 continues at operation 1206 by receiving a plurality of 3-dimensional (3D) coordinates corresponding to a plurality of locations within the image. For example, the computing device 702 receives the 3D coordinates 771 from the AR wearable device 602 .

[0171] Method 1200 continues at operation 1208 by displaying the image on a display of the computing device. For example, image display module 724 displays image 716 on display 710. For example, referring to Figure 8 , the portion of the display 710 that is not the video insert 812 is the image 716. The method 1200 continues at operation 1210 by accessing an indication of an enhancement to the image, the enhancement being generated by a user of the computing device. For example, user B 744 created enhancement 3 802.

[0172] The method 1200 continues at operation 1212 by determining an enhanced 3D coordinate based on the plurality of 3D coordinates. For example, the ML module 721 determines such as Figure 8 3D coordinates 790 of enhancement 786 of Aug 3 802.

[0173] The method 1200 continues at operation 1214 by sending the augmented indication and the 3D coordinates to the AR wearable device. For example, the image display module 724 sends the augmented indication 786 and the 3D coordinates 790 to the AR wearable device 602.

[0174] The method 1200 may include one or more additional operations. The operations of the method 1200 may be performed in a different order. One or more of the operations of the method 1200 may be optional. The method 1200 may be performed by the client device 102, the system 700, or another electronic device. A portion of the functions may be performed on a server computer or host. For example, the system 700 may be coupled to the application server 114, and one or more of the operations may be performed in the application server 114.

[0175] Fig.13 A method 1300 for remote annotation and navigation using an AR wearable device according to some examples is shown. The method 1300 begins at operation 1302, where an image capture device of the AR wearable device captures an image corresponding to a first user view of a real-world scene, the image including an identifier. For example, the image capture device 608 captures the image 616.

[0176] The method 1300 continues at operation 1304 by determining a plurality of 3-dimensional (3D) coordinates corresponding to a plurality of locations within the image. For example, the ML module 621 or the ML module 620 determines the 3D coordinates 661 .

[0177] The method 1300 continues at operation 1306 by sending the image and the identification to the computing device. For example, the image display module 624 sends the image 616 with the UTC 655. The method 1300 continues at operation 1308 by receiving the identification from the computing device. For example, the computing device 702 sends the UTC 655 to the AR wearable device 602. The method 1300 continues at operation 1310 by sending a plurality of 3D coordinates corresponding to a plurality of locations within the image to the computing device. For example, the image display module 624 sends the 3D coordinates 661 and / or the object 656 to the computing device 702.

[0178] The method 1300 continues at operation 1312 by receiving an indication of the augmentation and the 3D coordinates associated with the augmentation from the computing device. For example, the computing device 702 sends the augmentation 786 and the 3D coordinates 790 to the AR wearable device 602.

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

[0180] Machine Architecture

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

[0182] The machine 1400 may include a processor 1404, a memory 1406, and an input / output I / O component 1402, which may be configured to communicate with each other via a bus 1440. In an example, the processor 1404 (e.g., a central processing unit (CPU), a reduced instruction set computing (RISC) processor, a complex instruction set computing (CISC) processor, a graphics processing unit (GPU), a digital signal processor (DSP), an application specific integrated circuit (ASIC), a radio frequency integrated circuit (RFIC), another processor, or any suitable combination thereof) may include, for example, a processor 1408 that executes instructions 1410 and a processor 1412. The term "processor" is intended to include a multi-core processor, which may include two or more independent processors (sometimes referred to as "cores") that may execute instructions simultaneously. Although Fig.14 Multiple processors 1404 are shown, but the machine 1400 may include a single processor with a single core, a single processor with multiple cores (e.g., a multi-core processor), multiple processors with a single core, multiple processors with multiple cores, or any combination thereof.

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

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

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

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

[0187] 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 be used, for example, to capture still images and videos of a user of client device 102 (e.g., “selfies”), 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.

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

[0189] The location component 1436 includes a location 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.

[0190] Various technologies may be used to implement communications. I / O components 1402 also include communications components 1438 that are operable to couple machine 1400 to network 1422 or device 1424 via corresponding couplings or connections. For example, communications components 1438 may include a network interface component or other suitable device that interfaces with network 1422. In other examples, communications components 1438 may include wired communications components, wireless communications components, cellular communications components, near field communications (NFC) components, Parts (e.g. Low energy consumption), Components and other communication components for providing communication via other modalities. Device 1424 can be another machine or any peripheral device among various peripheral devices (e.g., a peripheral device coupled via USB).

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

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

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

[0194] Software Architecture

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

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

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

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

[0199] In an example, applications 1506 may include a home application 1536, a contact application 1530, a browser application 1532, a reader application 1534, a location application 1542, a media application 1544, a messaging application 1546, a game application 1548, and a variety of other applications such as third-party applications 1540. Application 1506 is a program that executes the functions defined in the program. Various programming languages ​​can be used to create one or more of the applications 1506 constructed in various ways, such as an object-oriented programming language (e.g., Objective-C, Java, or C++) or a procedural programming language (e.g., C language or assembly language). In a specific example, third-party applications 1540 (e.g., provided 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 phone's mobile operating system or another mobile operating system. In this example, third-party applications 1540 can activate API calls 1550 provided by the operating system 1512 to facilitate the functions described herein.

[0200] Processing components

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

[0202] The processor 1602 is shown coupled to a power source 1604 and includes modules (permanently configured or temporarily instantiated), namely an image processing component 1610, a graphical assistance component 1612, and a user interface component 1614. The image processing component 1610 is activated to process the image 616, 716 to determine the 3D coordinates 661, 790 and other information about the image 616, 716 and the enhancements 686, 786. In the example of the AR wearable device 602, the ML modules 620, 621 process the image 616 to generate the 3D coordinates 661. In the example of the computing device 702, the ML module 721 determines the 3D coordinates 790 of the enhancement 786 of the image 716 based on the 3D coordinates 771 provided for the image 716.

[0203] The graphical assistance component 1612 displays the enhancements 686, 786 and images 616, 716 on the displays 610, 710 of the AR wearable device 602 and the computing device 702, respectively. For example, the image display modules 624, 724 display the enhancements 686, 786 and images 616, 716 on the displays 610, 710, respectively.

[0204] The user interface component 1614 interacts with user A 644 and user B 744 to determine the user intent 636, 737 of user A 644 and user B 744, respectively. For example, in the example of the AR wearable device 602, the UI module 634 processes the tactile 646, gesture 648, voice 650, and position 652 inputs of user A 644 to determine the user intent 636. The UI module 634 presents on the display 610 such as Fig.10 UI 1 1006 UI item.

[0205] In the example of computing device 702, UI module 734 processes tactile 746, gesture 748, and voice 750 inputs of user B 744 to determine user intent 737. UI module 734 presents UI 723 items on display 710. As shown, processor 1602 is communicatively coupled to both processor 1606 and processor 1608.

[0206] Glossary

[0207] Certain examples are described herein as including logic or several components, modules, or mechanisms. A module may constitute a software module (e.g., code contained on a machine-readable medium or in a transmission signal) or a hardware module. A "hardware module" is a tangible unit capable of performing certain operations and may be configured or arranged in some physical manner. In various examples, one or more computer systems (e.g., a stand-alone computer system, a client computer system, or a server computer system) or one or more hardware modules of a computer system (e.g., a processor or a processor group) 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.

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

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

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

[0211] "Component" refers to a device, a physical entity, or logic with boundaries defined by function or subroutine calls, branch points, APIs, or other technical definitions that provide partitioning or modularization for specific processing or control functions. Components can be combined with other components via their interfaces to perform machine processes. Components can be packaged functional hardware units designed for use with other components, and can be part of a program that generally performs specific functions in related functions. Components can constitute software components (e.g., codes embodied on machine-readable media) or hardware components. "Hardware components" are tangible units that can perform certain operations and can be configured or arranged in a certain physical manner. In various examples, one or more computer systems (e.g., independent computer systems, client computer systems, or server computer systems) or one or more hardware components (e.g., processors or processor groups) of a computer system can be configured to operate to perform certain operations as described herein by software (e.g., applications or application parts). Hardware components can also be implemented mechanically, electronically, or in any suitable combination thereof. For example, a hardware component may include a dedicated circuit system or logic that is permanently configured to perform certain operations. The hardware component may be a dedicated processor, such as a field programmable gate array (FPGA) or an application specific integrated circuit (ASIC). The hardware component may also include a programmable logic or circuit system that is temporarily configured to perform certain operations by software. For example, the hardware component may include software executed by a general-purpose processor or other programmable processor. Once configured by such software, the hardware component becomes a specific machine (or a specific component of a machine) that is uniquely customized to perform the configured function, and is no longer a general-purpose processor. It will be understood that the decision to mechanically implement the hardware component in a dedicated and permanently configured circuit or in a circuit system that is temporarily configured (e.g., configured by software) can be driven for cost and time considerations. Therefore, the phrase "hardware component" (or "hardware-implemented component") should be understood to include a tangible entity, that is, an entity that is physically constructed, permanently configured (e.g., hardwired) or temporarily configured (e.g., programmed) to operate in some way or perform certain operations described herein. Considering an example where a hardware component is temporarily configured (e.g., programmed), each of the hardware components does not need to be configured or instantiated at any time. For example, in the case where a hardware component includes a general-purpose processor that is configured by software to become 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. The 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 one or more specific 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 (e.g., the Internet) and via one or more appropriate interfaces (e.g., API). The execution of some operations in the operation can be distributed among the processors, not only resident in a single machine, but also deployed across several machines. In some examples, the processor or the parts implemented by the processor can be located in a single geographic location (e.g., in a home environment, an office environment, or a server cluster). In other examples, the processor or the parts implemented by the processor can be distributed across several geographic locations.

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

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

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

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

[0216] "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 a computing device, the method comprising: accessing an image from an augmented reality (AR) wearable device, the image including a logo; Sending the identifier to the AR wearable device; receiving a plurality of 3-dimensional (3D) coordinates corresponding to a plurality of locations within the image; displaying the image on a display of the computing device; accessing an indication of an enhancement to the image, the enhancement generated by a user of the computing device; determining the enhanced 3D coordinates based on the plurality of 3D coordinates; as well as The enhanced indication and the 3D coordinates are sent to the AR wearable device.

2. The method according to claim 1, further comprising: receiving a video stream from the AR wearable device, the video stream comprising a plurality of images including the image; displaying the video stream and a user interface including an indication of direction on the display; receiving a selection of a direction among the directions; as well as An indication of the direction is sent to the AR wearable device.

3. The method according to claim 2, further comprising: Receiving an audio stream from the AR wearable device; playing the audio stream on the computing device; receiving audio input by the computing device; as well as The audio input is sent to the AR wearable device.

4. The method according to claim 2, wherein: The user interface further includes an indication of an edit command, and wherein the method further includes: When the image is displayed on the display of the AR wearable device, an indication of a selection of the editing command by the user is received.

5. The method according to claim 1, wherein: The identification of the image is an indication of Coordinated Universal Time (UTC) or an indication of an image identification number.

6. The method according to claim 1, wherein: The enhancements to the image include geometric shapes or lines drawn by user input.

7. The method according to claim 1, wherein: The display is a first display, and wherein displaying the image further comprises: Accessing parameters of a second display of the AR wearable device, the parameters comprising an aspect ratio of the second display; and The image is displayed on the first display of the computing device according to parameters of the second display.

8. The method according to claim 1, wherein: The multiple 3D coordinates are 3D world coordinates in a reference system of the AR wearable device.

9. The method according to claim 8, further comprising: Before determining the 3D coordinates: A 3D coordinate among the 3D coordinates is determined based on the enhanced pixel that is closest within the image to a 3D coordinate among the plurality of 3D coordinates.

10. The method according to claim 9, wherein: The plurality of 3D coordinates is a point cloud of 3D coordinates.

11. The method according to claim 1, wherein: The sending also includes: sending an indication of a command for the AR wearable device to return the plurality of 3D coordinates.

12. A computing device comprising: processor; as well as a memory storing instructions that, when executed by the processor, configure the computing device to perform operations comprising: accessing an image from an augmented reality (AR) wearable device, the image including a logo; Sending the identifier to the AR wearable device; receiving a plurality of 3-dimensional (3D) coordinates corresponding to a plurality of locations within the image; displaying the image on a display of the computing device; accessing an indication of an enhancement to the image, the enhancement generated by a user of the computing device; determining the enhanced 3D coordinates based on the plurality of 3D coordinates; and The enhanced indication and the 3D coordinates are sent to the AR wearable device.

13. The computing device of claim 12, wherein: The operations also include: receiving a video stream from the AR wearable device, the video stream comprising a plurality of images including the image; displaying the video stream and a user interface including an indication of direction on the display; receiving a selection of one of the directions by the user; and An indication of the direction is sent to the AR wearable device.

14. The computing device of claim 13, wherein: The operations also include: Receiving an audio stream from the AR wearable device; Playing the audio stream on the AR wearable device; receiving audio input from the user of the computing device; and The audio input is sent to the AR wearable device.

15. An augmented reality (AR) wearable device comprising: processor, and A memory storing instructions that, when executed by the processor, configure the AR wearable device to perform operations, the operations comprising: capturing, by an image capture device of the AR wearable device, an image corresponding to a first user view of a real-world scene, the image including a logo; sending the image and the identifier to a computing device; receiving the identification from the computing device; determining a plurality of 3-dimensional (3D) coordinates corresponding to a plurality of locations within the image; sending the plurality of 3D coordinates corresponding to the plurality of locations within the image to the computing device; and An indication of an enhancement and 3D coordinates associated with the enhancement are received from the computing device.

16. The AR wearable device according to claim 15, wherein: The image is a first image, and wherein the operations further comprise: The augmentation is displayed on a display of the AR wearable device, wherein a location of the augmentation is based on the 3D coordinates associated with the augmentation and the second user view of the real-world scene.

17. The AR wearable device according to claim 15, wherein: The operations also include: The plurality of 3D coordinates are determined based on visual inertial odometry (VIO).

18. The AR wearable device according to claim 15, wherein: The plurality of 3D coordinates is a point cloud of 3D coordinates.

19. The AR wearable device according to claim 15, wherein: The operations also include: capturing, by the image capture device of the AR wearable device, a plurality of images corresponding to a plurality of user views of the real-world scene, the plurality of images including the image; sending the plurality of images to the computing device; receiving an indication of a direction from the computing device; and The direction is displayed on the display.

20. The AR wearable device according to claim 15, wherein: The operations also include: sending the image to a host computing device along with instructions to determine the plurality of 3D coordinates for the image; and An indication of the plurality of 3D coordinates is received from the host computer.

Images