Object counting on AR wearable device

Abstract

Systems, methods, and computer readable media for object counting on augmented reality (AR) wearable devices are disclosed. Embodiments are disclosed that can display a count of objects as part of a user view. Upon receiving a request to count objects, the AR wearable device captures an image of a user view. The AR wearable device transmits the image to a back end for processing to determine an object in the image. The AR wearable device selects a set of objects of the determined objects to count and overlays a bounding box over the counted objects within the user view. The position of the bounding box is adjusted to handle movement of the AR wearable device. The hierarchy of objects is used to merge together a set of objects that are related but have different tags or names.

Description

[0001] Priority claim

[0002] This application claims the benefit of U.S. patent application serial number 17 / 893,738, filed on August 23, 2022, which is incorporated herein by reference in its entirety. Technical Field

[0003] Examples of the present disclosure generally relate to counting objects with respect to augmented reality (AR) wearable devices. More specifically, but not limited to, examples of the present disclosure relate to capturing an image of a scene, processing the image to identify objects within the scene, and counting a set of objects among the identified objects, wherein the results are superimposed on the scene. 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 the wearable device, and typically AR wearable devices have limited power to provide additional functionality. BRIEF DESCRIPTION OF THE DRAWINGS

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

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

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

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

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

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

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

[0012] Figure 7 Schematic diagram illustrating object counting on an AR wearable device according to some embodiments.

[0013] Figure 8 Schematic diagram illustrating object counting on an AR wearable device according to some embodiments.

[0014] Fig. 9 Schematic diagram illustrating object counting on an AR wearable device according to some embodiments.

[0015] Fig.10 Schematic diagram illustrating object counting on an AR wearable device according to some embodiments.

[0016] Fig.11 Schematic diagram illustrating object counting on an AR wearable device according to some embodiments.

[0017] Fig.12 A method of object counting on an AR wearable device according to some embodiments is shown.

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

[0019] Fig.14 A method of object counting on an AR wearable device according to some embodiments is shown.

[0020] Fig.15 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.

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

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

[0023] The following description includes systems, methods, techniques, instruction sequences and computing machine 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.

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

[0025] AR wearable devices 602, such as AR glasses 1300, have limited physical user interface items such as buttons 1378. Some AR wearable devices 602 have one or two buttons 1378 or a touchpad 1376 that the user 644 interacts with on the frame 1332 of the AR wearable device 602. In addition, the AR wearable device 602 has limited battery power.

[0026] Typically, user 644, while wearing AR glasses 900, wants to count the number of objects 632 that user 644 can see in user view 672 of real-world scene 670. User view 672 is what user 644 sees through AR glasses 900. One example of an object 632 that user 644 wants to count is money on a table or in the hand of user 644. In another example, user 644 wants to know how many people are waiting in line to enter a movie theater.

[0027] One challenge is how to determine which objects 632 are in the user view 672. This challenge is addressed by a segmentation process, where object 632 recognition is performed on the backend 618 and selection of groups of objects 632 for counting 623 is performed on the AR wearable device 602. For example, the AR wearable device 602 captures an image 616 of the user view 672 using a front-facing camera of the AR wearable device 602. The image 616 is transmitted to the backend 618 for processing. The AR wearable device 602 receives information about the objects 632 from the backend 618, which is then used to select groups of objects 632 for counting 623. The information about the objects 632 includes a location 656 of the objects 632, which may be related to 3D coordinates in the image 616 or a world coordinate system. There may be interaction with the user 644 when selecting groups of objects 632.

[0028] Another challenge is how to indicate to the user 644 which objects 632 are selected when the user 644 may have moved their head and therefore moved the user view 672. This challenge is addressed by adjusting the position of the objects 632 based on the movement 666 of the AR wearable device 602 since the image 616 was captured. The adjustment module 626 determines the movement 666 and adjusts the position of the bounding box 660 drawn on the display 610 of the AR wearable device 602 around the counted objects 632 within the user view 672. In addition, when the 3D coordinates of the objects 632 are provided by the back end 618, the 3D coordinates of the user view 672 are used to determine where to draw the bounding box 660.

[0029] Another challenge is how to provide counting functionality with the limited physical user interface items of the AR wearable device 602. This challenge is solved by the image display module 624 determining which group of objects 632 the user 644 intends to count as part of the count 623. For example, objects 632 are identified by labels 633 such as "person", "dog", "pea", "rectangle", "money", etc. The image display module 624 groups the objects 632 by labels 633 and selects objects 632 for counting based on which objects are most likely to be what the user 644 wants to count. For example, in the example of money, the objects 632 will have labels 633 indicating the type of money such as "$1 bill", "quarter", etc. The image display module 624 will determine by their location 656 that they are close to the user 644 and occupy a significant portion of the user's view 672, and are therefore likely to be objects 632 that the user 644 wants to count. The user 644 can interact with the AR wearable device 602 to indicate that they want to count different groups of objects 632.

[0030] Networked computing environment

[0031] Figure 1 1 is a block diagram illustrating an example messaging system 100 for exchanging data (e.g., messages and associated content) over a network. The messaging system 100 includes multiple instances of a client device 102, each of which hosts multiple applications, including a messaging client 104 and other applications 106. Each messaging client 104 is communicatively coupled to other instances of the messaging client 104 (e.g., hosted on respective other client devices 102), a messaging server system 108, and a third-party server 110 via a network 112 (e.g., the Internet). The messaging client 104 may also communicate with the 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 certain messaging clients 104 via the network 112. Although certain functionality of the messaging system 100 is described herein as being performed by the messaging client 104 or by the messaging server system 108, it may be a design choice whether certain functionality is located within the messaging client 104 or within the messaging server system 108. For example, it may be technically preferred to initially deploy certain technologies and functionality within the messaging server system 108, but 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 stimulated 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 transmits 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 facilitate activating the functions of the application server 114. An application program interface (API) server 116 exposes various functions supported by the application server 114, including: account registration; login functionality; sending messages from a particular messaging client 104 to another messaging client 104 via the application server 114; sending media files (e.g., images or videos) from a messaging client 104 to a messaging server 118 and for possible access by another messaging client 104; setting up of a collection of media data (e.g., a story); retrieving a friend list of a user of a client device 102; retrieving such a collection; retrieving messages and content; adding and removing entities (e.g., friends) from an entity graph (e.g., a social graph); locating friends within a social graph; and opening application events (e.g., related to a messaging client 104).

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

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

[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 name of the object within the sensor data and the location of the object to the AR wearable device. Another request from the AR wearable device is a request for an AR application associated with a tag such as a "QR code" that can be run on the AR wearable device. The input modality server 124 can load an AR application that may be used by a user of the AR wearable device to the AR wearable device, or respond with an AR application based on criteria given from the AR wearable device to the input modality server 124. The criteria can be a restriction 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 source. The external resource can be an application 106 (e.g., a "local app") installed on the client device 102, or a small-scale version of the application (e.g., a "applet") hosted on the client device 102 or away from the client device 102 (e.g., on a third-party server 110). The small-scale version of the application includes a subset of the features and functions of the application (e.g., a full-scale, local version of the application) and is implemented using a markup language document. In one example, the small-scale version of the application (e.g., a "applet") is a web-based markup language version of the application and is embedded in the messaging client 104. In addition to using markup language documents (eg, .*ml files), applets may also 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, none of the portions of the small-scale application can be accessed outside of the messaging client 104 or limited portions of the small-scale application can be accessed outside of the messaging client 104. The small-scale application can be launched by the messaging client 104 receiving a markup language document associated with the small-scale application, such as 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 locally stored code corresponding to the external resource. In response to determining that the external resource is a web-based resource, the messaging client 104 communicates with the third-party server 110 (for example) to obtain a markup language document corresponding to the selected external resource. The messaging client 104 then processes the obtained markup language document to present the web-based external resource within the user interface of the messaging client 104.

[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 participant in a conversation (e.g., a chat session) in the messaging client 104 with a notification related to the current or recent use of an external resource by one or more members of a user group. One or more users may be invited to join an active external resource or to start an external resource (in the friend group) that was recently used but is currently inactive. The external resource may provide the participants of 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 start 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 the 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 the form of a context-sensitive menu. For example, icons representing different applications (or applets) of the application 106 (or applets) may vary based on how the user launches the menu (e.g., from a conversational interface or from a non-conversational interface).

[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 to include a messaging client 104 and an application server 114. The messaging system 100 contains a number of subsystems that are supported on the client side by the messaging client 104 and on the server side by the application server 114. These subsystems include, for example, a transient timer system 202, a collection management system 204, an enhancement system 208, a 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 a plurality of timers that selectively enable access (e.g., for presentation and display) of messages and associated content via the messaging client 104 based on duration and display parameters associated with a message or a collection of messages (e.g., a story). Further 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, image video, and audio data). Collections of content (e.g., messages, including images, videos, text, and audio) can be organized into "event galleries" or "event stories." Such collections can be made available for a specified time period, such as the duration of an event related to the content. For example, content related to a concert can be available as a "story" for the duration of the concert. The collection management system 204 can also be responsible for publishing an icon that provides notification of the existence of a particular collection to the user interface of the messaging client 104.

[0049] In addition, the collection management system 204 includes a curation interface 206 that allows a collection manager to manage and curate a particular collection of content. For example, the curation interface 206 enables an event organizer to curate a collection of content related to a particular event (e.g., to delete inappropriate content or redundant messages). In addition, the collection management system 204 uses machine vision (or image recognition technology) and content rules to automatically curate content collections. In some examples, compensation may be paid to users for including 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 generating and publishing media overlays (media overlays) for messages processed by the messaging system 100. The enhancement system 208 is operable to provide media overlays or enhancements (e.g., image filters) to the messaging client 104 based on the geographic location of the client device 102. In another example, the enhancement system 208 is operable to provide media overlays to the messaging client 104 based on other information such as social network information of the user of the client device 102. Media overlays can include audio and visual content and visual effects. Examples of audio and visual content include pictures, text, logos, animations, and sound effects. Examples of visual effects include color overlays. Audio and visual content or visual effects can be applied to media content items (e.g., photos, digital objects) at the client device 102. For example, media overlays can include text or images that can be superimposed on the top of photos taken by the client device 102. In another example, the media overlay includes a location identifier (e.g., Venice Beach) overlay, the name of a live event, or a business name (e.g., Beach Cafe) overlay. In another example, the augmentation system 208 uses the geographic location of the client device 102 to identify a media overlay that includes the name of a business at the geographic location of the client device 102. The media overlay may include other logos 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 geo-location functions and supports the presentation of map-based media content and messages by the messaging client 104. For example, the mapping system 210 enables the display of a user icon or avatar (e.g., stored in the profile data 316) on a map to indicate the current or past locations of the user's "friends" within 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, a message posted by a user to the messaging system 100 from a particular geographic location can be displayed to a particular user's "friends" on the mapping interface of the messaging client 104 within the context of that particular location on the map. The user can also share his or her location and status information with other users of the messaging system 100 (e.g., using an appropriate status avatar) via the messaging client 104, where the location and status information is similarly displayed to the selected user within the context of the mapping 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 messaging and text messaging within the context of gaming (e.g., chatting), provides leaderboards for gaming, and also supports providing in-game rewards (e.g., 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 (i.e., applications or applets). Each third-party server 110 hosts, for example, an application or a small-scale version of an application based on a markup language (e.g., HTML5) (e.g., a game application, a utility application, a payment application, or a ride-sharing application). The messaging client 104 can launch a web-based resource (e.g., an application) by accessing an HTML5 file from a third-party server 110 associated with a web-based resource. In some examples, the application hosted by the third-party server 110 is programmed with 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] To integrate the functionality of the SDK into a web-based resource, the SDK is downloaded by the third-party server 110 from the messaging server 118, or received by the third-party server 110 in other ways. Once downloaded or received, the SDK is included as part of the application code of the web-based external resource. The code of the web-based resource can then call or activate certain functions of the SDK to integrate the features of the messaging client 104 into the web-based resource.

[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 communication between the third-party server 110 and the messaging client 104. In some examples, the web view JavaScript bridge running on the client device 102 establishes two one-way communication channels between the external resources and the messaging client 104. Messages are sent asynchronously between the external resources and the messaging client 104 via these communication channels. Each SDK function activation is sent as a message and a callback. Each SDK function is implemented by constructing a unique callback identifier and sending a message with the callback identifier.

[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 instructs the messaging client 104 through the GUI of the messaging client 104 or selects a visual representation to access the features of the web-based external resource, 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 landing page or title screen) for the external resource. During, before, or after presenting a landing portion of the reading material, such as a page or title screen, the messaging client 104 determines whether the launched external resource has been previously authorized to access the user data of the messaging client 104. In response to determining that the launched external resource has been previously authorized to access the user data of the messaging client 104, the messaging client 104 presents another graphical user interface of the external resource including the functions and features of the external resource. In response to determining that the launched external resource has not been previously authorized to access the user data of the messaging client 104, after a threshold time period (e.g., 3 seconds) of displaying the landing page or title screen of the external resource, the messaging client 104 slides a menu for authorizing the external resource to access the user data (e.g., animating the menu to emerge from the bottom of the screen to the middle or other portion of the screen). The menu identifies the type of user data that the external resource will be authorized to use. In response to receiving the user selection of the accept option, the messaging client 104 adds the external resource to the list of authorized external resources and enables the external resource to access the user data from the messaging client 104. In some examples, the external resource is authorized to access the user data by the messaging client 104 according to the OAuth 2 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 with 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] The image processing system 216 supports the system 600 for the AR wearable device. The image processing system 216 receives requests from the AR wearable device 602 and responds to the requests. Figure 6 As depicted, the request includes a request to process an image, such as image 616, to generate object 632 with additional information. The AR wearable device may request other services from the voice input system 216.

[0062] Data Architecture

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

[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. Such relationships may be social, professional (e.g., working in a common company or organization), interest-based, or activity-based, by way of example only.

[0067] The profile data 316 stores multiple types of profile data about a particular entity. Based on the privacy settings specified by the particular entity, the 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, the 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 within 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 status or activity that a user can select to communicate 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. The filter can be of various types, including a user-selected filter from a set of filters presented to the sending user by the messaging client 104 when the sending user is composing a message. Other types of filters include geolocation filters (also referred to as geofilters), which can be presented to the sending user based on a geographic location. For example, a geolocation filter specific to a nearby or special location can be presented by the messaging client 104 within a user interface based on geographic location information determined by a global positioning system (GPS) unit of the client device 102.

[0071] Another type of filter is a data filter that can be selectively presented to the sending user by the messaging client 104 based on other input or information collected during the message creation process by the client device 102. Examples of data filters include the current temperature at a particular location, the current speed 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 such as video clips that can be modified in a gallery. For example, in a client device 102 that can access multiple augmented reality content items, a user can use a single video clip with multiple augmented reality content items to 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 may be displayed only on the screen and not stored in memory, or the content captured by the device sensors may be recorded and stored in memory with or without modification (or both). In some systems, a preview function may show how different augmented reality content items will look in different windows in the display at the same time. This may, for example, enable viewing of 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 using the data to modify content may involve: detection of objects (e.g., faces, hands, bodies, cats, dogs, surfaces, objects, etc.) in video frames; tracking of such objects as they leave, enter, and move around the field of view; and modification or transformation of such objects as they are tracked. In various examples, different methods for implementing such transformations may be used. Some examples may involve: generating a three-dimensional mesh model of one or more objects; and using transformations of the models and animated textures within a video to implement the transformations. In other examples, tracking of points on an object may be used to place an image or texture (which may be two-dimensional or three-dimensional) at the tracked location. In yet another example, neural network analysis of a video frame may be used to place an image, model, or texture in content (e.g., an image or video frame). Thus, augmented reality content items refer both to images, models, and textures used to create transformations in content, and to additional modeling and analysis information required to implement such transformations using object detection, tracking, and placement.

[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 a human face and parts of a human body, an animal, or a non-living thing (e.g., a chair, a car, 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 elements to be transformed are identified by a computing device, and then if the elements are present in the frame of the video, they are detected and tracked. The elements of the object are modified according to the request for modification, so the frame of the video stream is transformed. For different types of transformations, the transformation of the frame of the video stream can be performed by different methods. For example, for the transformation of the frame that mainly refers to the form of the elements of the object to be changed, the characteristic points of each element of the object are calculated (for example, using an active shape model (ASM) or other known methods). Then, a grid based on the characteristic points is generated for each element of at least one element of the object. The grid is used for the subsequent stage of tracking the elements of the object in the video stream. During the tracking process, the grid mentioned for each element is aligned with the positioning of each element. Then, additional points are generated on the grid. A first set of first points is generated for each element based on the modification request, and a set of second points is generated for each element based on the set of first points and the modification request. Then, the frame of the video stream can be transformed by modifying the elements of the object based on the set of first points and the set of second points and the grid. In such a method, the background of the modified object may also be changed or deformed 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 of 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 of ​​each element with the position of each element of at least one element, and the properties of the area can be modified based on the modification request, thereby transforming the frame of the video stream. Depending on the specific modification request, the properties of the mentioned area can be transformed in different ways. Such modifications may involve: changing the color of the area; removing at least some parts of the area from the frame of the video stream; including one or more new objects in the area based on the modification request; and modifying or deforming 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 exist in most of the images considered. For example, for facial landmarks, the location of the left pupil can be used. If the initial landmarks are not recognizable (for example, if the person wears an eye patch), secondary landmarks can be used. Such a landmark recognition process can be used for any such object. In some examples, the set of landmarks forms a shape. The shape can be represented as a vector using the coordinates of the points in the shape. One shape is aligned with another shape using a similarity transformation (allowing translation, scaling, and rotation) that minimizes the average Euclidean distance between the shape points. The mean shape is the mean of the aligned training shapes.

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

[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, computational time, and power consumption. Complex image manipulations can include size and shape changes, emotional 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 that can be implemented 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 in association with an interface described herein. The modification icon includes the following changes, which can be the basis for modifying the face of the user within the image or video stream as part of the modification operation. Once the modification icon is selected, the transformation system initiates a process of transforming the image of the user to reflect the selected modification icon (e.g., generating a smiley face on the user). Once the image or video stream is captured and the specified modification is selected, the modified image or video stream can be presented in a graphical user interface displayed on the client device 102. The transformation system can implement a complex convolutional neural network for 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 to the user in real time or near real time. In addition, the modification can be persistent while the video stream is captured, and the selected modification icon remains toggled. Machine-taught neural networks can be used to implement such modifications.

[0083] The graphical user interface presenting the modifications performed by the transformation system can provide additional interactive options to the user. Such options can be based on an interface for initiating the selection of a specific computer animation model and content capture (e.g., initiated from a content creator user interface). In various examples, the modification can be persistent after the initial selection of the modification icon. The user can switch to turn on or off the modification by tapping or otherwise selecting the face being modified by the transformation system, and store it for later viewing or browsing other areas of the imaging application. In the case where the transformation system modifies multiple faces, the user can globally switch to turn on or off the modification by tapping or selecting a single face modified and displayed in the graphical user interface. In some examples, individual faces among 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 related to a collection of messages and associated images, video or audio data that are compiled into a collection (e.g., a story or gallery). The creation of a particular collection can be initiated by a particular user (e.g., each user whose record is maintained in the entity table 306). A user can create a "personal story" in the form of a collection of content that has been created and sent / broadcasted by the user. To this end, the user interface of the messaging client 104 can include an icon that is user-selectable to enable the sending user to add specific content to his or her personal story.

[0085] A collection may also constitute a "live story," which is a collection of content from multiple users that 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 different locations and events. Users whose client devices have location services enabled and who are at a common location event at a particular time may be presented with an option, for example via a user interface of the messaging client 104, to contribute content to a particular live story. Live stories may be identified to a user by the messaging client 104 based on his or her location. The end result is a "live story" told from a community perspective.

[0086] Another type of content collection is called a "location story" that 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 embodiments, 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 the various images and videos stored in the image table 312 and the video table 304.

[0088] Data communication architecture

[0089] Figure 4is a schematic diagram illustrating the structure of a message 400 generated by a messaging client 104 for transmission to another messaging client 104 or a messaging server 118 according to some examples. The content of a particular message 400 is used to populate a message table 302 stored in a database 126 accessible by a messaging server 118. Similarly, the content of the message 400 is stored in memory as "in-transit" or "in-flight" data of a client device 102 or application server 114. The message 400 is illustrated 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 a message 400 that has been 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 . The enhancement data for a sent or received message 400 may be stored in the enhancement table 310 .

[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) is to 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 in a message video payload 408).

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

[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 (or address) to a location in image table 312. 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 5is a schematic diagram illustrating an access restriction process 500 according to which access to content (e.g., ephemeral message 502 and associated multimedia data payload) or a collection of content (e.g., ephemeral message group 504) can be time-restricted (e.g., made ephemeral).

[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 ephemeral message 502 will be displayed by the messaging client 104 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 will only be shown to the associated receiving user for a period of time determined by the value of the message duration parameter 506. The message timer 510 is shown as providing an output to a more general transient timer system 202, which is responsible for the overall timing of displaying content (e.g., the transient message 502) to the receiving user.

[0107] exist Figure 5 1. 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. Group duration parameter 508, for example, can 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) can 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 will be accessible within the context of the ephemeral message group 504. Thus, a particular ephemeral message group 504 may "expire" and become inaccessible within the context of the ephemeral message group 504 before the ephemeral message group 504 itself expires according to the group duration parameter 508. The group duration parameter 508, the group participation parameter 512, and the message recipient identifier 424 each provide inputs to a group timer 514, which is operable to first determine whether a particular ephemeral message 502 of the ephemeral message group 504 will 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 overall lifespan of the associated ephemeral message group 504 and the individual ephemeral messages 502 included in the ephemeral message group 504. In one example, each ephemeral message 502 within the ephemeral message group 504 remains viewable and accessible for a period of time specified by the group duration parameter 508. In another example, within the context of the ephemeral message group 504, a particular ephemeral message 502 may expire based on the group participation parameter 512. Note that even within the context of the ephemeral message group 504, the message duration parameter 506 may still determine the duration for which a particular ephemeral message 502 is displayed to a receiving user. Thus, the message duration parameter 506 determines the duration for which a particular ephemeral message 502 is displayed to a receiving user, regardless of whether the receiving user is viewing the ephemeral message 502 within or outside the context of the ephemeral message group 504.

[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] Object counting on AR wearables

[0114] Figure 6 A system 600 for providing object counting on an AR wearable device according to some examples is shown. The system 600 includes an AR wearable device 602, such as Fig.13 The glasses 1300 may include other devices, such as part of the messaging server system 108 or the client device 102, which may perform one or more of the operations described herein.

[0115] Input / output (IO) devices 604 include devices that enable a user 644 to provide input to the system 600 or receive output. IO devices 604 include microphones 606, displays 610, speakers, image capture devices 608, buttons 612, touchpads 613, gyroscopes, and the like. Image capture device 608 captures an image 616 of a real world scene 670, which is a front view of a user view 672, which is what the user 644 sees through the AR wearable device 602. Location (loc) 673 is a 3D coordinate of a world coordinate system with an indication of the location of the user view 672. Image capture device 608 may be a charge coupled device (CCD) or another type of photon detector. According to some embodiments, button 612 is button 1378. According to some embodiments, touchpad 613 is touchpad 1376. Button 612 and touchpad 613 enable user 644 to provide tactile 646 input. Microphone 606 enables user 644 to provide voice 650 input. Image capture device 608 enables user 644 to provide gesture 648 input via UI module 634 that analyzes image 616.

[0116] Some devices, such as a gyroscope, may be both sensors 614 and IO devices 604. For example, a user 644 (moving the AR wearable device 602 to change the position 652 of the user 644) transmits input to the AR wearable device 602 through, for example, a sensor 614 such as a gyroscope or another initial sensor that detects a change in the position 652 of the user 644. However, the user 644 may move the AR wearable device 602 without a user intent 636 to transmit input to the AR wearable device 602.

[0117] The sensors 614 include a gyroscope, a light sensor, a positioning sensor, a clock, etc. The wireless module 659 communicates 654 between the backend 618 and the AR wearable device 602. The wireless module 659 is configured to execute a wireless communication protocol with the backend 618, such as LE Bluetooth, the Institute of Electrical and Electronics Engineers (IEEE) 802.11 communication standard, a proprietary communication standard, a 3GPP communication standard, etc. The wireless module 659 establishes a wireless communication link between the AR wearable device 602 and the backend 618. In some embodiments, the wireless module 659 can be used to determine the position and / or orientation of the AR wearable device 602.

[0118] The counting state 622 is stored in the memory of the AR wearable device 602 and indicates the state of the AR wearable device 602 for processing the image 616 to count the objects 632. The counting state 622 changes based on the user 644 input. For example, the user 644 can use the button 612, the touchpad 613, the voice 650 input, the gesture 648 input to select to have the AR wearable device 602 count 623 the objects 632 in the image 616.

[0119] If the counting state 664 is in the "on" state, the image display module 624 causes the image 616 to be captured by the image capture device 608, or there may be a previously captured image 616 that the image display module 624 uses as the image 616 for counting 623 the objects 632 in the image 616. In some embodiments, 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 seen by the user 644 through, for example, the glasses 1300.

[0120] The image display module 624 is configured to cause the image 616 to be sent to the backend 618 for processing by the machine learning (ML) module 620. The backend 618 may be the messaging server system 108 or the user device 102. In some implementations, the ML module 620 resides within the AR wearable device 602. The functionality of the ML module 620 may be divided between the backend 618 and the AR wearable device 602.

[0121] ML module 620 processes image 616. ML module 620 identifies object 632 and other information of object 632. The other information includes one or more of: label 633, confidence 658, location 656, and bounding box 660. In some examples, ML module 620 is a neural network trained to identify object 623 and label object 623 633. In some implementations, ML module 620 is trained to identify a set of objects 623 that user 644 may be interested in.

[0122] The labels 633 identify objects 632, such as "cuboid," "tree," "person," "money," "$1 bill," "quarter," "$20 bill," etc. The objects 632 identified and labeled 633 may be a limited number of objects 632 that the ML module 620 is trained to recognize, where the objects 632 are selected based on the objects 632 that the user 644 would likely want to count 623.

[0123] Confidence 658 indicates a probability, likelihood, or confidence that object 632 is correctly or accurately tagged 633 by ML module 620. Location 656 indicates a location of object 632. In one example, location 656 includes three-dimensional (3D) coordinates in world coordinates. For example, AR wearable device 602 and / or backend 618 determine world coordinates of object 632 captured by AR wearable device 602. In some implementations, location 656 includes a pixel location of object 632 within image 616.

[0124] Bounding box 660 is an AR graphic for indicating object 632 within image 616 to user 644. Image display module 624 displays bounding box 660 to indicate object 632 to user 644. In some embodiments, image display module 624 displays an indication of label 633 on display 610 to indicate recognition of object 632 by AR wearable device 602 to user 644.

[0125] The image display module 624 processes the objects 632 and determines which objects 632 are included in the count 623. The objects 632 included in the count 623 also have a bounding box 660 displayed on the display 610 to indicate that the object 632 has been counted as part of the count 623. In one example, the bounding box 660 indicates the confidence 658, such as by different colors of the bounding box 660. As an example, there may be three shades of blue used, where the lighter the shade of blue, the lower the confidence 658 that the object 632 is correctly identified as the label 633. In addition, when the confidence 658 is below or exceeds another threshold (e.g., below 50%), the color of the bounding box 660 changes to a shade of red, where the "darker" the shade of red, the lower the confidence 658.

[0126] The image display module 624 excludes objects 632 having a confidence 658 that is below or exceeds a threshold. For example, if the confidence 658 is 10% and the threshold is 30%, the object 632 is excluded because 10% is less than 30%.

[0127] The image display module 624 recognizes that the tag 633 is used to count the objects 632. For example, there may be objects 632 tagged 633 as “person” and objects 632 tagged 633 as “horse”. The image display module 624 selects the tag 633 to count 623 and displays a bounding box 660 for the object 632 having the tag 633 on the display 610.

[0128] In some embodiments, when user 644 turns on count status 664, user 644 can indicate label 633 to count. For example, user 644 can use their voice 650 to say "people" and then select the option to turn on count status 664.

[0129] In some embodiments, the ML module 620 provides additional information (info) 630 about the image 616, such as indicating that the image 616 may be an indoor image. Other information 630 may include, for example, information that segments the image 616 into regions such as across a river, a river, or on the same side of a river. The information 630 may indicate regions of the image 616 where additional objects 632 with labels 633 but obscured may exist. The image display module 624 may use the information 630 to determine which objects 632 to count 623.

[0130] In some implementations, the image display module 624 uses information about the tags 628 to determine which objects 632 to count. For example, the hierarchy 662 may be used to determine that some of the objects 632 are all food, which may cause the image display module 624 to select objects 632 that are food for counting 623. In another example, the hierarchy 662 is used to determine that some of the objects 632 are all cash or currency, which may cause the image display module 624 to select those objects 632 for counting.

[0131] In addition, the information 630 may include other information about the label 628. For example, the information 630 may indicate that the object 632 with the label 633 of "$1 USD" has a monetary value of 100 cents. The image display module 624 may count not only the number of objects 632 but also the attributes of the objects 632 based on the information 630. For example, the image display module 624 counts the total amount of money as the value of the counted objects 632. Or, in another example, the image display module 624 counts the total number of calories in the object 632. For example, if there is a pile of peas on a plate, the image display module 624 counts the total number of peas and the total number of calories estimated if the peas are consumed.

[0132] In addition, the image display module 624 can determine which objects 632 to count 623 based on the placement of the objects 632. For example, the image display module 624 selects the objects 632 based on the objects 632 being within a threshold of the same size as other objects 632 having the same label 633 or based on the locations 656 of the objects 632 being within a threshold distance of each other. For example, if there are people in line to enter a theater and people who are a block or more away (e.g., walking along a sidewalk), the image display module 624 selects the people in line to enter the theater to count 623. In some implementations, the image display module 624 determines which objects 632 to count 623 based on the objects 632 being within a central portion of the image 616. In some embodiments, the image display module 624 determines which objects 632 to count 623 based on the objects 632 being within a threshold distance of the user 644, where the objects 632 being within a threshold distance of the user 644 is based on the size of the objects 632 within the image 616 or based on comparing the location 656 of the objects 632 with the location of the user 644 (which is the same as the location of the AR wearable device 602).

[0133] The UI module 634 processes input from the IO device 604 to determine the user intent 636 from the user 644. The UI module 634 determines whether the user intent 636 is to turn on or off the counting state 664. The UI module 634 determines whether a label 633 or region of the image 616 is selected to guide the image display module 624 to select an object 632 for counting 623. The user 644 can use a gesture 648 (e.g., the movement of their finger) to select an area of ​​the image 616 for counting 623. The UI module 634 analyzes the movement of the finger by analyzing the image 616 captured over time. Then, the UI module 634 passes the area of ​​the image 616 indicated by the movement of the finger where the user 644 wants to count the object 632 to the image display module 624. The area can be presented in 3D world coordinates.

[0134] When the image 616 is captured, the adjustment module 626 adjusts the position of the bounding box 660 due to the movement 666 of the AR wearable device 602 relative to the position of the AR wearable device 602. In some implementations, the motion sensor 614 is used to determine the movement 666 of the AR wearable device 602. The change in the position 656 of the object 632 is then determined based on the movement 666. The bounding box 660 can be moved by a plurality of pixels based on the movement 666 of the AR wearable device 602.

[0135] In some implementations, the position 656 is a 3D coordinate in a world coordinate system. The image display module 624 determines which objects 632 are counted and then determines the 3D coordinates of the user view 672 and where to display the bounding box 660 based on the 3D coordinates of the user view 672 and the 3D coordinates of the objects 632.

[0136] In some embodiments, the image display module 624 maintains a data structure for storing objects 632 and their locations 656 so that if the user 644 moves and requests another count 623 for object 632, the image display module 624 can check to ensure that the object 632 has not already been counted as part of the count 623 in a previous image 616.

[0137] In some embodiments, the image display module 624 displays a user interface item with a count 623 and a bounding box 660 on the display 610 for the user 644 to select a group or label 633 of objects 632 to be counted as part of the count 623. The term AR graphics includes any content displayed by the AR wearable device 602 on the display 610 for the user 644 to view in conjunction with viewing the real world through the lens. Alternatively, the user 644 can view the real world by capturing an image 616 through the AR wearable device 602 and displaying the image 616 and the AR graphics on the opaque display 610.

[0138] Figure 7 602 according to some embodiments. User view 702 is the view that user 644 would see through the optical elements of AR wearable device 602 (e.g., through optical elements 1343, 1344), where bounding box 708, count 706, and label 704 are displayed by, for example, an integrated near-eye display. Figure 7 , the image display module 624 captures an image 616 of a tree and a log and sends the image 616 to the backend 618. The backend 618 returns an object 632, which includes objects 632 of a tree and a log. The image display module 624 selects the log as the most likely label 633 that satisfies the user intent 636. The image display module 624 then displays the bounding box 708, the count 706, and the label 704 using the display 610 of the AR wearable device 602 to provide the AR graphics for the user 644 to consume.

[0139] Figure 8 6 shows object counting on an AR wearable device 602 according to some embodiments. Figure 8, the image display module 624 determines that people with bounding boxes 810 around them should be counted, and determines a count 804 of 14 people. The mask 812 indicates that the image display module 624 determines that there may be additional people that the user 644 may be interested in counting as part of the count 623. The image display module 624 determines not to count other large people 814 or other small people 808. In some embodiments, the image display module 624 determines to count 804 the label 806 "people" with bounding boxes 810 based on a selection by the user 644. In some embodiments, the image display module 624 determines to count 804 the number of people with bounding boxes 810 based on the people with bounding boxes 810 (which are presented as a row or queue waiting for an event at the event venue 830). The image display module 624 may already have information that the user 644 is heading to the event venue 830. For example, the user 644 may be following the direction to the event venue 830.

[0140] In some implementations, the image display module 624 determines to count 804 the people with bounding boxes 810 based on the people with bounding boxes 810 having a large number of objects 632, so it will be more likely that the user 644 will want to count the people with bounding boxes 810. In addition, the image display module 624 excludes other large people 814 and other small people 808 based on determining that the size of the objects 632 or the locations 656 of the other large people 814 and small people 808 are not close to the people with bounding boxes 810.

[0141] In some embodiments, the UI module 634 displays an application (APP) carousel 828 on the display 610. The user 644 selects one of the options based on the use of a gesture 648 (e.g., a pressing motion with their finger 822) or by using their voice 650. The user 644 can make a selection in other ways. The example application carousel 828 provides options for "next group" 816, "next label" 818, "execute application" 820, "cancel" 824, and display menu 826. The UI module 634 interacts with the user 644 to determine the user's intent 636. The "next group" 816 in this case will move among other large people 814, other small people 808, and people with bounding boxes 810. The "next label" 818 will select a different object 632, such as a tree or a house. In some embodiments, the UI module 634 prompts the user to select an object 632 group or label 633 to count 623. The prompt can be using the speaker of the AR wearable device 602 or by displaying information on the display 610. For example, UI module 634 displays a list of different groups of objects 632 for user 644 to select from. In another example, UI module 634 indicates numbers above the groups of objects 632 and prompts user 644 to say one of these numbers.

[0142] Fig. 9 Counting of objects on an AR wearable device 602 is shown in accordance with some embodiments. In this example, the image display module 624 counts peas with bounding boxes 908 to generate counts 902, and pizza slices with bounding boxes 912 to generate counts 904. The covers 906, 910 indicate that there may be objects 632 covered 906, 910 of interest to the user 644. The image display module 624 groups the peas and pizza together into the same label 902 or group of objects 632 using a hierarchy 662. Calories 914 are determined by the image display module 624 based on the information 630 for the label 628 pizza and the label 628 peas. A calorie estimate or total value of calories 914 is provided.

[0143] Fig.10 Counting of objects on an AR wearable device 602 according to some embodiments is shown. In this example, the image display module 624 counts the labels 1005 of the cuboids with bounding boxes 1001 to generate a count 1006. There are cuboids outside the user's view 1002, 1004 that are not captured in the image 616 and therefore not counted.

[0144] Fig.11 1 shows object counting on an AR wearable device 602 according to some embodiments. In this example, the image display module 624 counts the labels 1104 of the cuboids with bounding boxes 1108 to generate a count 1106. The count 1106 of new cuboids is 6, each with a bounding box 1108. A total of 21 cuboids have been counted, including those from Fig.10 The count of 15 cuboids is 1006 and Fig.11 The count of the 6 cuboids in the count is 1106. Fig.10 and Fig.11 is an example of a counting state 664 in a continuous counting state, where objects 632 having the same label 633 or determined to be in the same group of objects 632 are counted with a continuous total in a series of images 616 as the user 644 views different parts of the scene 670 or real world. The image display module 624 maintains information about the object 632 from the previous image 616, such as the position 656 in the 3D world coordinates. Fig.11 is Fig.10 The cuboid marked with an "X" is previously captured in the generated Fig.10 The AR graphic image 616 is counted in the count 1006. Fig.11 Some of the cuboids outside the user view 1110 in Fig.10110 are counted in the image in , but do not include the “X” because they are outside of the user view 1110 , so no AR graphic can be generated indicating that they are counted.

[0145] Fig.12 A method 1200 of counting objects on an AR wearable device 602 is shown according to some embodiments. The method 1200 begins at operation 1202 by detecting that a counting mode has been activated. For example, the user 644 selects a button 612 on the AR wearable device 602 or uses a gesture that sets the counting state 664 to the counting mode?.

[0146] The method 1200 continues at operation 1208 by capturing an image. For example, in response to the count state 664 changing to the count mode, the image display module 624 causes the image capture device 608 to capture the image 616.

[0147] The method 1200 continues at operation 1206 by detecting an object at the back end 1204. For example, the back end 1204 is the same or similar to the back end 618, which may be referred to as a back end computer, a back end server, or a host device. In some embodiments as discussed herein, the operation 1206 may be performed in whole or in part by the AR wearable device 602. The ML module 620 processes the image 616 and determines an object 632 and information about the object 632, such as a label 633, a confidence 658, a location 656, and a bounding box 660.

[0148] The method 1200 continues at operation 1212, where the backend 1204 communicates the detected object with information to the AR wearable device 602. For example, the backend 618 communicates 654 the object 632 and information about the object 632, such as the label 633, the confidence 658, the location 656, and the bounding box 660, to the AR wearable device 602.

[0149] The method 1200 continues at operation 1210 where the detected objects are filtered. For example, the image display module 624 filters out objects 632 having a confidence 658 that is below a threshold or does not cross a threshold, so that the filtered objects 632 are not counted.

[0150] The method 1200 continues at operation 1214 where the objects are grouped by label and counted by label. For example, the image display module 624 groups the objects 632 by label 633 and counts the objects 632 by label 633 to determine a count 623 for each label 633.

[0151] The method 1200 continues at operation 1216, where a label or group of objects to be counted is determined. For example, the image display module 624 selects a group or label 633 of objects 632 to be counted as part of the count 623. For example, the image display module 624 selects Figure 7 The logs in Figure 8 People in Fig. 9 Peas and pizza in Fig.10 and Fig.11 The rectangular block in .

[0152] Method 1200 continues at operation 1218, where it is determined whether a group of objects has been successfully determined. If the image display module 624 determines that the expected label is successfully determined, method 1200 continues to operation 1222. If the image display module 624 determines that the expected label is not successfully determined, then in operation 1220, the image display module 624 causes a UI item to be displayed that lists possible selections for other groups of items. For example, the image display module 624 may not be sure which group of objects 632 to count 623, so the UI module 634 queries the user 644 which group of objects 632 to count 623. In some cases, the groups of objects 632 may all have the same label 633, and all objects 632 with the same label 633 are placed in the group of objects 632. In some cases, there may be multiple groups with the same label 633. For example, in Figure 8 middle, Figure 8 All persons in the count 623 may be tagged 633 as “person” by the ML module 620. The image display module 624 groups objects 632 having the same tag 633 into three groups of objects 632. The three groups of objects 632 generated from the objects tagged 633 as “person” are persons with “bounding boxes” 810, “other small persons” 808, and “other large persons” 814. The UI module 634 provides the user 644 with an opportunity to select which of these groups of objects 632 to select. The user 644 selects the group of objects 632 they want to count as part of the count 623 by using the app carousel 828 or another form of input such as touch 646, gesture 648, voice 650, or position 652.

[0153] The method 1200 continues at operation 1222 by post-processing the results of the counting. For example, the image display module 624 uses the information 630 associated with the labels 628 of the counted objects 632 to generate additional information for the user 644. For example, in Fig. 9 , calories 914 and the number of objects 632 are counted and displayed to the user 644 .

[0154] The method 1200 continues at operation 1224 by overlaying the result onto the scene. For example, the image display module 624 displays the AR graphic on the display 610. Figure 6 As described, adjustments may need to be determined by adjustment module 626 to account for movement 666 of user 644 or AR wearable device 602 since image 616 was captured.

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

[0156] Fig.13 13 is a perspective view of a wearable electronic device in the form of glasses 1300 according to some examples. Glasses 1300 are eyewear products including electronic products that operate within a network system for transmitting image and video content. In some examples, the wearable electronic device is referred to as AR glasses. Glasses 1300 may include a frame 1332 made of any suitable material (such as plastic or metal) including any suitable shape memory alloy. Frame 1332 may have a front piece 1333, which may include a first lens or left lens, a display or optical element holder 1336 and a second lens or right lens, a display or optical element holder 1337 connected by a bridge 1338. Front piece 1333 also includes a left end 1341 and a right end 1342. A first optical element or left optical element 1344 and a second optical element or right optical element 1343 may be disposed in respective left optical element holders 1336 and right optical element holders 1337. Each of the optical elements 1343, 1344 can be a lens, a display, a display assembly, or a combination thereof. In some examples, for example, the glasses 1300 are provided with an integrated near-eye display mechanism that enables, for example, displaying a preview image of visual media captured by the camera 1369 of the glasses 1300 to the user.

[0157] The frame 1332 further includes a left arm or temple piece 1346 and a right arm or temple piece 1347, which are coupled to the respective left end 1341 and right end 1342 of the front piece 1333 by any suitable means such as a hinge (not shown) to be coupled to the front piece 1333 or rigidly or fixably fixed to the front piece 1333, thereby being integral with the front piece 1333. Each of the temple piece 1346 and the temple piece 1347 may include: a first portion 1351 coupled to the respective end 1341 or 1342 of the front piece 1333; and any suitable second portion 1352 for coupling to the ear of the user, such as a curved or arched piece. In one example, the front piece 1333 can be formed of a single piece of material to have a unitary or one-piece construction. In one example, the entire frame 1332 can be formed of a single piece of material to have a unitary or one-piece construction.

[0158] Eyeglasses 1300 include a computing device such as computer 1361, which may be of any suitable type to be carried by frame 1332 and, in one example, of a suitable size and shape to be at least partially disposed within one or more of temple pieces 1346, 1347. In one example, computer 1361 is of a size and shape similar to the size and shape of one of temple pieces 1346, 1347 and is thus disposed nearly completely, if not completely, within the structure and confines of such temple pieces 1346, 1347.

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

[0160] The computer 1361 further includes a battery 1362 or other suitable portable power supply. In one example, the battery 1362 is disposed in one of the temple pieces 1346 or the temple pieces 1347. Fig.13In the glasses 1300 shown in FIG. 1 , a battery 1362 is shown disposed in the left temple piece 1346 and electrically coupled to the remainder of the computer 1361 disposed in the right temple piece 1347 using a connector 1374. The one or more input and output devices may include a connector or port (not shown) accessible from the exterior of the frame 1332 suitable for charging the battery 1362, a wireless receiver, transmitter or transceiver (not shown), or a combination of such devices.

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

[0162] In various examples, the glasses 1300 may include any number of input sensors or peripherals in addition to the camera 1369. The front piece 1333 is provided with an outward-facing, front-facing, front or outer surface 1366 that faces forward or away from the user when the glasses 1300 are mounted on the user's face, and an opposite inward-facing, rearward-facing, rear or inner surface 1367 that faces the user's face when the glasses 1300 are mounted on the user's face. Such sensors may include an inward-facing video sensor or digital imaging module, such as a camera 1369 that may be mounted on or disposed within the inner surface 1367 of the front piece 1333 or elsewhere on the frame 1332 to face the user, and an outward-facing video sensor or digital imaging module, such as a camera 1369 that may be mounted on or disposed within the outer surface 1366 of the front piece 1333 or elsewhere on the frame 1332 to face away from the user. Such sensors, peripherals, or peripheral devices may additionally include biometric sensors, positioning sensors, accelerometers, or any other such sensors. In some examples, a projector (not shown) is used to project images on the inner surface of optical elements 1343, 1344 (or lenses) to provide a mixed reality or augmented reality experience for the user of glasses 1300.

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

[0164] 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 1332 adjacent to a surface thereof for detecting the presence of a user's finger to set the touch sensitive button into an engaged state when the user touches the finger to a corresponding point on the outer surface 1366 of the frame 1332. 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 1369, and other examples may employ different single action tactile control arrangements.

[0165] Computer 1361 is configured to perform the methods described herein. In some examples, computer 1361 is coupled to one or more antennas for receiving signals from a GNSS and circuitry for processing the signals, wherein the antennas and circuitry are housed in glasses 1300. In some examples, computer 1361 is coupled to one or more wireless antennas and circuitry for sending and receiving wireless signals, wherein the antennas and circuitry are housed in glasses 1300. In some examples, multiple sets of antennas and circuitry are housed in glasses 1300. In some examples, the antennas and circuitry are configured to receive signals based on, for example, Bluetooth. TM , Bluetooth Low Energy TM , IEEE 802, IEEE 802.11az / be, and other communication protocols. In some examples, the PDR sensor is housed in the glasses 1300 and coupled to the computer 1361. In some examples, the glasses 1300 are VR headsets, wherein the optical elements 1343 and 1344 are opaque screens for displaying images to a user of the VR headset. In some examples, the computer 1361 is coupled to user interface elements, such as a slide or touch pad 1376 and a button 1378. Long pressing the button 1378 resets the glasses 1300. The slide or touch pad 1376 and the button 1378 are used by the user to provide input to the computer 1361 and / or other electronic components of the glasses 1300. The glasses 1300 include one or more microphones 1382 coupled to the computer 1361. The glasses 1300 include one or more gyroscopes 1380.

[0166] Fig.14 A method 1400 of counting objects on an AR wearable device 602 is shown according to some embodiments. The method 1400 begins at operation 1402, where an image corresponding to a first user view of a real-world scene is captured by an image capture device of the AR wearable device. For example, in response to the user 644 selecting the counting state 664 of the counting mode, the image display module 668 causes the image capture device 608 to capture the image 616. In another example, the image 616 is captured at operation 1208 of the method 1200.

[0167] The method 1400 continues at operation 1404, where a plurality of objects within the image are identified by processing the image, the identification comprising determining locations of the plurality of objects and labels of the plurality of objects. For example, the AR wearable device 602 transmits the image 616 and instructions for the backend 618 to process the image 616 to the backend 618 via a wireless connection, and receives an indication of an object 632 having a location 656 and a label 633 from the backend 618. In some embodiments, the AR wearable device 602 processes the image 616 using the ML module 620. In another example, the backend 1204 processes the image 616 as described in conjunction with the method 1200.

[0168] In some embodiments, operation 1404 described above is replaced by an operation of sending the image to a backend computer via a wireless communication link, which in some embodiments includes instructions for the backend computer to process the image. Operation 1404 also includes an operation of receiving an indication of a plurality of objects within the image, an indication of the location of the plurality of objects, and an indication of the labels of the plurality of objects. For example, in combination with Figure 6 As described, the image display module 624 sends the image 616 to the backend 618, where the ML module 620 processes the image 616 and sends back an indication of the object 632 along with additional information. In another example, the method 1200 processes the image 616 at operations 1208, 1206, 1210, and 1212, as in combination with Fig.12 Just as described.

[0169] The method 1400 continues at operation 1406 where a group of objects in the plurality of objects is selected based at least on the tag. For example, the image display module 624 selects the group of objects 632 as disclosed herein. In another example, the method 1200 selects the group of objects 632 at operation 1216.

[0170] The method 1400 continues at operation 1408, where the number of objects in the group of objects is counted to generate a count of the group of objects. For example, the image display module 624 counts 623 the group of objects 632. In another example, the method 1200 counts the number of objects in the group of objects at operation 1222. The method 1400 continues at operation 1410, where an indication that the objects in the group of objects have been counted and an indication of the count are displayed on a display of the AR wearable device, where the position of the indication on the display is based on the position of the objects in the group of objects and the second user view of the real world scene. For example, as referenced Figure 8 As shown and described, the image display module 624 displays the bounding box 810 and the count 804. In another example, the method 1200 overlays the results at operation 1224.

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

[0172] Machine Architecture

[0173] Fig.151500 within which instructions 1510 (e.g., software, programs, applications, applet, app, or other executable code) may be executed for causing the machine 1500 to perform any one or more of the methods discussed herein. For example, the instructions 1510 may cause the machine 1500 to perform any one or more of the methods described herein. The instructions 1510 convert a general purpose, unprogrammed machine 1500 into a specific machine 1500 that is programmed to perform the functions described and illustrated in the manner described. The machine 1500 may operate as a standalone device or may be coupled (e.g., networked) to other machines. In a networked deployment, the machine 1500 may operate in the capacity of 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 1500 may include, but is not limited to, a server computer, a client computer, a personal computer (PC), a tablet computer, a laptop computer, a netbook, a set-top box (STB), a personal digital assistant (PDA), an entertainment media system, a cellular phone, a smart phone, a mobile device, a wearable device (e.g., a smart watch), a smart home device (e.g., a smart appliance), other smart devices, a web appliance, a network router, a network switch, a network bridge, or any machine capable of sequentially or otherwise executing instructions 1510 specifying actions to be taken by the machine 1500. In addition, although only a single machine 1500 is shown, the term "machine" should also be considered to include a collection of machines that individually or jointly execute instructions 1510 to perform any one or more of the methods discussed herein. For example, the machine 1500 may include any of the client device 102 or a plurality of server devices that form part of the messaging server system 108. In some examples, the machine 1500 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.

[0174] The machine 1500 may include a processor 1504, a memory 1506, and an input / output (I / O) component 1502 that may be configured to communicate with each other via a bus 1540. In an example, the processor 1504 (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 1508 that executes instructions 1510 and a processor 1512. The term "processor" is intended to include multi-core processors, which may include two or more independent processors (sometimes referred to as "cores") that may execute instructions simultaneously. Although Fig.15 Multiple processors 1504 are shown, but the machine 1500 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.

[0175] The memory 1506 includes a main memory 1514, a static memory 1516, and a storage unit 1518, which can be accessed by the processor 1504 via a bus 1540. The main memory 1506, the static memory 1516, and the storage unit 1518 store instructions 1510 that implement any one or more of the methods or functions described herein. The instructions 1510 may also reside, completely or partially, within the main memory 1514, within the static memory 1516, within the machine-readable medium 1520 within the storage unit 1518, within at least one of the processors 1504 (e.g., within a cache memory of a processor), or within any suitable combination thereof during execution thereof by the machine 1500.

[0176] I / O components 1502 may include various components for receiving input, providing output, generating output, transmitting information, exchanging information, capturing measurements, etc. The specific I / O components 1502 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 will be appreciated that I / O components 1502 may include Fig.151502. In various examples, the I / O components 1502 may include user output components 1526 and user input components 1528. The user output components 1526 may include visual components (e.g., displays such as plasma display panels (PDPs), light emitting diode (LED) displays, liquid crystal displays (LCDs), projectors, or cathode ray tubes (CRTs)), acoustic components (e.g., speakers), tactile components (e.g., vibration motors, resistance mechanisms), other signal generators, etc. The user input components 1528 may include alphanumeric input components (e.g., keyboards, touch screens configured to receive alphanumeric input, optical keyboards, or other alphanumeric input components), point-based input components (e.g., mice, touch pads, trackballs, joysticks, motion sensors, or other pointing instruments), tactile input components (e.g., physical buttons, touch screens that provide location and force of touch or touch gestures, or other tactile input components), audio input components (e.g., microphones), etc.

[0177] In another example, the I / O component 1502 may include a biometric component 1530, a motion component 1532, an environment component 1534, or a position component 1536, as well as various other components. For example, the biometric component 1530 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, perspiration, or brain waves), identifying people (e.g., voice recognition, retinal recognition, facial recognition, fingerprint recognition, or EEG-based recognition), etc. The motion component 1532 includes an acceleration sensor component (e.g., an accelerometer), a gravity sensor component, and a rotation sensor component (e.g., a gyroscope).

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

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

[0180] 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 a triple, quad, or penta rear camera configuration on the front and back sides of the client device 102. For example, these multiple camera systems may include a wide-angle camera, an ultra-wide-angle camera, a telephoto camera, a macro camera, and a depth sensor.

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

[0182] A variety of technologies may be used to achieve communication. The I / O components 1502 also include a communication component 1538 that is operable to couple the machine 1500 to the network 1522 or device 1524 via a corresponding coupling or connection. For example, the communication component 1538 may include a network interface component or another suitable device that interfaces with the network 1522. In other examples, the communication component 1538 may include a wired communication component, a wireless communication component, a cellular communication component, a near field communication (NFC) component, Parts (e.g. Low energy consumption), Device 1524 may be another machine or any of a variety of peripherals (eg, a peripheral coupled via USB).

[0183] In addition, the communication component 1538 can detect the identifier or include a component that can be operated to detect the identifier. For example, the communication component 1538 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 a one-dimensional barcode such as a universal product code (UPC) barcode, a multi-dimensional barcode such as a Quick Response (QR) code, an Aztec code, a data matrix, a data symbol (Dataglyph), a maximum code (MaxiCode), PDF417, UltraCode, UCC RSS-2D barcode, and other optical codes) or an acoustic detection component (e.g., a microphone for identifying a tagged audio signal). In addition, various information can be obtained via the communication component 1538, such as positioning via Internet Protocol (IP) geographic location, obtaining a location via Positioning is obtained through signal triangulation, positioning is obtained via detection of NFC beacon signals that can indicate a specific position, etc.

[0184] Various memories (e.g., main memory 1514, static memory 1516, and memory of processor 1504) and storage unit 1518 may store one or more sets of instructions and data structures (e.g., software) implemented or used by any one or more of the methods or functions described herein. These instructions (e.g., instructions 1510) when executed by processor 1504 cause various operations to implement the disclosed examples.

[0185] The instructions 1510 may be sent or received via a network interface device (e.g., a network interface component included in the communication component 1538) using a transmission medium and using any of several well-known transmission protocols (e.g., Hypertext Transfer Protocol (HTTP)) over the network 1522. Similarly, the instructions 1510 may be transmitted or received via a coupling (e.g., a peer-to-peer coupling) with the device 1524 using a transmission medium.

[0186] Software Architecture

[0187] Fig.161600 is a block diagram illustrating a software architecture 1604 that may be installed on any one or more of the devices described herein. The software architecture 1604 is supported by hardware, such as a machine 1602 including a processor 1620, a memory 1626, and an I / O component 1638. In this example, the software architecture 1604 may be conceptualized as a stack of layers, each of which provides specific functionality. The software architecture 1604 includes layers such as an operating system 1612, a library 1610, a framework 1608, and an application 1606. In operation, the application 1606 invokes an API call 1650 through the software stack and receives a message 1652 in response to the API call 1650.

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

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

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

[0191] In an example, applications 1606 may include a home application 1636, a contacts application 1630, a browser application 1632, a reader application 1634, a positioning application 1642, a media application 1644, a messaging application 1646, a game application 1648, and a variety of other applications such as third-party applications 1640. Application 1606 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 1606 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 1640 (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 mobile operating system of the phone or another mobile operating system. In this example, third-party application 1640 can activate API call 1650 provided by operating system 1612 to facilitate the functions described in this article.

[0192] Processing components

[0193] Now go to Fig.17 , which shows a diagrammatic representation of a processing environment 1700 that includes a processor 1702, a processor 1706, and a processor 1708 (eg, a GPU, a CPU, or a combination thereof).

[0194] Processor 1702 is shown coupled to power source 1704 and includes modules (permanently configured or temporarily instantiated), namely image processing component 1710, object counting component 1712, and user interface component 1714. Image processing component 1710 is activated to process image 616 to determine object 632 and other information about object 632. For example, ML module 620 processes image 616 to generate object 632 and additional information.

[0195] The object counting component 1712 selects the group of objects 632 and counts 623 the group of objects 632 found in the image 616 by the image processing component 1710. For example, the image display module 668 selects the objects 632 to count 623 and counts the objects 632.

[0196] The user interface component 1714 interacts with the user 644 to determine the user intent 636 of the user 644. For example, the UI module 634 processes the tactile 646, gesture 648, voice 650, and position 652 inputs of the user 644 to determine the user intent 636. The UI module 634 presents UI items such as the application carousel 828 on the display 610. As shown, the processor 1702 is communicatively coupled to both the processor 1706 and the processor 1708.

[0197] Glossary

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

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

[0200] "Client Device" refers to any machine that interfaces with a communication network to obtain resources from one or more server systems or other client devices. A client device may be, but is not limited to, a mobile phone, AR glasses, VR glasses, AR wearables, desktop computers, laptop computers, portable digital assistants (PDAs), smartphones, 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.

[0201] "Communications network" means one or more parts of a network, which may be an ad hoc network, an intranet, an extranet, a virtual private network (VPN), a local area network (LAN), a wireless LAN (WLAN), a wide area network (WAN), a wireless WAN (WWAN), a metropolitan area network (MAN), the Internet, a part of the Internet, a part of the public switched telephone network (PSTN), a plain old telephone service (POTS) network, a cellular telephone network, a wireless network, A network, another type of network, or a combination of two or more such networks. For example, the network or a portion of a 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 rates for GSM evolution (EDGE) technology, the third generation partnership project (3GPP) including 3G, fourth generation wireless (4G) networks, universal mobile telecommunications system (UMTS), high speed packet access (HSPA), world wide interoperability for microwave access (WiMAX), long term evolution (LTE) standards, other data transmission technologies defined by various standard setting organizations, other long distance protocols, or other data transmission technologies.

[0202] "Component" refers to a logic, device or physical entity 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 processing. Components can be part of a program designed for encapsulated functional hardware units used with other components, and specific functions that generally perform related functions. Components can constitute software components (e.g., codes implemented on machine-readable media) or hardware components. "Hardware components" are tangible units that can perform certain operations and can be configured or arranged in a certain physical manner. In various examples, one or more computer systems (e.g., independent computer systems, client computer systems or server computer systems) or one or more hardware components (e.g., processors or processor groups) of a computer system can be configured by software (e.g., applications or application parts) to operate to perform certain operations as described herein. Hardware components can also be implemented mechanically, electronically or in any suitable combination thereof. For example, a hardware component may include a dedicated circuit system or logic that is permanently configured to perform certain operations. The hardware component may be a dedicated processor, such as a field programmable gate array (FPGA) or an application specific integrated circuit (ASIC). The hardware component may also include a programmable logic or circuit system that is temporarily configured to perform certain operations by software. For example, the hardware component may include software executed by a general-purpose processor or other programmable processor. Once configured by such software, the hardware component becomes a specific machine (or a specific component of a machine) that is uniquely customized to perform the configured function, and is no longer a general-purpose processor. It will be recognized that it can be determined for cost and time considerations whether to mechanically implement the hardware component in a dedicated and permanently configured circuit system or in a temporarily configured (e.g., configured by software) circuit system to implement the hardware component. 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 into different special-purpose processors (e.g., including different hardware components) at different times. Software accordingly configures one or more specific processors to, for example, constitute a specific hardware component at one time and constitute different hardware components at different times. Hardware components can provide information to other hardware components and receive information from other hardware components. Therefore, the described hardware components can be considered to be communicatively coupled.In the case of multiple hardware components being present at the same time, communication can be achieved by signal transmission (e.g., by appropriate circuits and buses) between or among two or more hardware components in the 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 to which multiple hardware components have access rights and retrieving information in the memory structure. For example, a hardware component can perform an operation, and the output of the operation is stored in a memory device coupled to it in communication. Then, other hardware components can access the memory device at a subsequent time to retrieve the stored output 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 in this article can be implemented at least in part by a processor, wherein one or more specific processors are examples of hardware. For example, at least some 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 a "software as a service" (SaaS) operation. For example, at least some of the operations in the operation can be performed by a computer group (as an example of a machine including a processor), wherein these operations can be accessed via a network (for example, the Internet) and via one or more appropriate interfaces (for example, API). The execution of some operations in the operation can be distributed between processors, not only resident in a single machine, but deployed across multiple machines. In some examples, a processor or a part implemented by a processor can be located in a single geographical location (for example, in a home environment, an office environment or a server group). In other examples, a processor or a part implemented by a processor can be distributed across multiple geographical locations.

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

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

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

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

[0207] "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 facilitates the communication of software or data. The term "signal medium" should be deemed to include any form of modulated data signals, carrier waves, etc. The term "modulated data signal" means a signal that has one or more of its characteristics set or changed in such a way as to encode information in the signal. The terms "transmission medium" and "signal medium" mean the same thing and may be used interchangeably in this disclosure.

Claims

1. A method performed on an augmented reality (AR) wearable device, 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; sending the image to a backend computer via a wireless communication link; as well as receiving an indication of a plurality of objects within the image, an indication of locations of the plurality of objects, and an indication of labels of the plurality of objects; selecting a group of objects from the plurality of objects based at least on the tags; counting a number of objects in the set of objects to generate a count of the set of objects; as well as An indication that an object in the set of objects has been counted and an indication of the count are displayed on a display of the AR wearable device, wherein a position of the indication on the display is based on a position of the object in the set of objects and a second user view of the real-world scene.

2. The method according to claim 1, wherein: The indication that an object in the set of objects has been counted is a bounding box surrounding each of the objects in the set of objects.

3. The method according to claim 2, wherein: A probability is associated with the label, the probability indicating a likelihood that a corresponding object in the set of objects is correctly labeled, and wherein the bounding box indicates a probability associated with the label of the set of objects.

4. The method according to claim 2, wherein: The selection is also based on at least one of: the group of objects is located in a central portion of the image, the group of objects is located within a threshold distance of each other, the group of objects is located within a threshold distance of a user of the AR wearable device, and the group of objects has a same label.

5. The method according to claim 1, further comprising: Prior to selecting the group of objects, prompting a user of the AR wearable device as to which of the tags the user wants to count, wherein the prompting comprises displaying an indication of the tag on the display or generating an audio output using a speaker of the AR wearable device; receiving a selection of a tab from among the tabs; and A group of objects in the plurality of objects is selected based on the selected label.

6. The method according to claim 1, further comprising: Prior to identifying, a selection of a region of the image is received, and wherein the identifying is within the region of the image.

7. The method according to claim 1, wherein: The tags identify names of the plurality of objects.

8. The method according to claim 1, wherein: The identification also includes: identifying, by processing the image, areas of the image where additional objects are obscured by the set of objects; and An indication is displayed that the additional object is obscured.

9. The method according to claim 1, wherein: The identifying further comprises identifying three-dimensional coordinates of the plurality of objects within a world coordinate system, and wherein counting the number of the set of objects further comprises: determining that a subset of objects in the set of objects were previously counted; and A count of previously uncounted objects in the set of objects is generated.

10. The method according to claim 1, wherein: The image is a first image, the number is a first number, the group of objects is a first group of objects, the plurality of objects is a first plurality of objects, the label is a first label, the indication is a first indication, wherein the receiving further comprises receiving first three-dimensional coordinates in a world coordinate system of the first plurality of objects, and wherein the method further comprises: capturing, by the image capture device, a second image corresponding to a third user view of the real-world scene; sending the second image and second instructions for the back-end computer to process the second image to the back-end computer via the wireless communication link; and receiving an indication of a second plurality of objects within the second image, second three-dimensional coordinates within a world coordinate system of the second plurality of objects, and second labels of the second plurality of objects; selecting a second group of objects in the second plurality of objects based on objects in the second group of objects being in the same group of objects as the first group of objects; counting objects in the second set of objects that were not previously counted in the first set of objects to generate a second count; and A second indication that a second group of objects that were not previously counted has been counted and an indication of the second count are displayed on a display of the AR wearable device, wherein a location of the second indication is based on the three-dimensional coordinates of the second group of objects and a third user view of the real-world scene.

11. The method according to claim 10, further comprising: A third indication that a second group of objects previously counted have not yet been counted in the second count and an indication that the second count is added to the first count are displayed on the display of the AR wearable device, wherein the position of the third indication is based on the second three-dimensional coordinates of the second group of objects previously counted and a third user view of the real-world scene.

12. The method according to claim 11, wherein: The first indication is a bounding box and the second indication is an "X's".

13. The method according to claim 1, further comprising: determining a value of an object in the set of objects; determining a total value of the set of objects based on the value; as well as An indication of the total value is displayed on the display.

14. The method according to claim 13, wherein: The value of the object is a monetary value and the object is currency, or the value of the object is a calorie estimate and the object is food.

15. The method according to claim 1, wherein: The subject is a human, and wherein the method further comprises: determining a location where the person is located by processing the image; and In response to the number exceeding or crossing a threshold value for the number of persons for the venue, an indication is displayed on the display that the number of persons has been exceeded with respect to the venue.

16. The method according to claim 1, wherein: The capturing is in response to receiving a user selection of a counting mode, and wherein sending the image to the backend computer via the wireless communication link includes instructions for the backend computer to process the image.

17. An augmented reality (AR) wearable device comprising: processor; as well as A memory storing instructions, wherein the instructions, 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; sending the image and instructions for the back-end computer to process the image to a back-end computer via a wireless communication link; and receiving an indication of a plurality of objects within the image, an indication of locations of the plurality of objects, and an indication of labels of the plurality of objects; selecting a group of objects from the plurality of objects based at least on the tags; counting the number of objects in the set of objects to generate a count of the set of objects; and An indication that an object in the set of objects has been counted and an indication of the count are displayed on a display of the AR wearable device, wherein a position of the indication on the display is based on a position of the object in the set of objects and a second user view of the real-world scene.

18. The AR wearable device according to claim 17, wherein: The indication is a bounding box around each of the objects in the set of objects, and wherein a probability is associated with the label, the probability indicating a likelihood that the corresponding object in the set of objects is correctly labeled, and wherein the bounding box indication is a probability associated with the label of the set of objects.

19. A non-transitory computer-readable storage medium comprising instructions that, when executed by an augmented reality (AR) wearable device, cause the AR wearable device to perform operations comprising: capturing, by an image capture device of the AR wearable device, an image corresponding to a first user view of a real-world scene; identifying a plurality of objects within the image by processing the image, the identifying comprising determining locations of the plurality of objects and labels of the plurality of objects; selecting a group of objects from the plurality of objects based at least on the tags; counting a number of objects in the set of objects to generate a count of the set of objects; as well as An indication that an object in the set of objects has been counted and an indication of the count are displayed on a display of the AR wearable device, wherein a position of the indication on the display is based on a position of the object in the set of objects and a second user view of the real-world scene.

20. The non-transitory computer readable storage medium of claim 19, wherein: The identification also includes: sending the image and instructions for the back-end computer to process the image via a wireless communication link; and An indication of a plurality of objects within the image, an indication of the locations, and an indication of the labels are received.

Images