Augmented reality experience event metrics system

Abstract

Methods and systems for performing generation of an AR experience on a messaging platform are disclosed. Methods and systems receive a request from a client device to access an augmented reality (AR) experience, and access a list of event types associated with the AR experience for generating one or more metrics. Methods and systems determine that an interaction associated with an AR experience corresponds to a first event type in a list of event types, and generate interaction data representing the interaction for the first event type. In response to receiving a request to terminate the AR experience, the systems and methods send interaction data to a remote server.

Description

[0001] Priority claim

[0002] This application claims the benefit of priority to U.S. patent application Ser. No. 17 / 727,972, filed on Apr. 25, 2022, which is incorporated herein by reference in its entirety. Technical Field

[0003] The present disclosure generally relates to generating augmented reality (AR) experiences on messaging applications. Background Art

[0004] Augmented reality (AR) is a modification of a virtual environment. For example, in virtual reality (VR), the user is completely immersed in a virtual world, while in AR, the user is immersed in a world that combines virtual objects with the real world or superimposes virtual objects on the real world. AR systems are designed to generate and present virtual objects that interact realistically with the real world environment and with each other. Examples of AR applications can include single or multiplayer video games, instant messaging systems, etc. BRIEF DESCRIPTION OF THE DRAWINGS

[0005] In the accompanying drawings (which are not necessarily drawn to scale), like numbers may describe similar components in different views. To easily identify the discussion of any particular element or action, the highest digit or digits in the reference numeral refer to the figure number in which the element is first introduced. Some non-limiting examples are shown in the 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 client application according to some examples.

[0008] Figure 3 is a diagrammatic representation of data structures 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 block diagram illustrating an example AR event tracking system according to some examples.

[0011] Figures 6 to 8 is a graphical representation of the output of an AR event tracking system according to some examples.

[0012] Fig. 9 is a flow diagram illustrating example operation of an AR event tracking system according to some examples.

[0013] Fig.10 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.

[0014] Fig.11 is a block diagram illustrating a software architecture in which examples may be implemented. DETAILED DESCRIPTION

[0015] The following description includes systems, methods, techniques, instruction sequences and computing machine program products that implement 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 various examples. However, it will be apparent to those skilled in the art that examples can be practiced without these specific details. Typically, it is not necessary to show in detail known instruction instances, protocols, structures and techniques.

[0016] Messaging applications typically enable end users to access various AR experiences by launching an AR experience bundle or package that includes AR content associated with the AR experience. AR experiences typically present AR elements that are animated or anchored to specific locations. This enables users to move around in the real world and keep AR elements in place or move around in a similar manner. In order to ensure that the AR experience remains in a fully operational state with a minimum number of errors and improve certain features of the AR experience, AR experience developers seek information about how the AR experience works as a whole. Specifically, AR experience developers need feedback on which features of the AR experience are used and which features have problems. However, current systems can only provide general metrics about AR experiences and cannot track the level of interaction with AR experiences on a feature-by-feature basis. General metrics are the same for all AR experiences developed by many different entities and do not represent the unique properties and features of each specific AR experience. Therefore, AR experience developers still do not know how certain features of the AR experience work and how end users access and interact with these features. This forces AR developers to guess what improvements should be made to the AR experience, which can be both time-consuming and a waste of resources. This could reduce the end-user’s interest level in revisiting the AR experience, leading to missed opportunities.

[0017] The disclosed technology solves these technical problems by tracking interactions with certain features selected by an AR experience developer across devices and across different times or instances when an AR experience is launched. To this end, the disclosed technology executed on a computing system receives a request to access an AR experience from a client device. The disclosed technology accesses a list of event types associated with the AR experience for generating one or more metrics. The disclosed technology determines that an interaction associated with the AR experience corresponds to a first event type in the list of event types, and generates interaction data representing the interaction for the first event type. In one example, the AR developer selects the first event type as the AR event to be tracked. The disclosed technology receives a request to terminate the AR experience, and in response, sends interaction data to a remote server. The interaction data can provide feedback to the AR experience developer on a feature-by-feature level about the user's interaction with certain features of the AR experience.

[0018] In some examples, an AR development platform is provided to an AR experience developer. The AR development platform may present a user interface to the AR experience developer that enables the AR developer to select which AR elements are tracked and used to generate metrics for the AR experience. The graphical user interface presents a list of AR events associated with the AR experience and includes a first option associated with a first AR event in the list of AR elements. The first option is configured to cause an interaction corresponding to the first AR event to be tracked and provided to a remote server for aggregation after the AR experience is terminated in response to selecting the first option.

[0019] In some examples, the list of AR events includes predefined AR events that can be tracked. In some examples, the list of AR events includes a list of custom AR events generated by an AR developer. The list can include a mix of predefined events to be tracked and custom AR events that are not included in the list of predefined events and are selected by the AR developer to be tracked. The graphical user interface also includes a second option associated with the first AR event, the second option being used to specify one or more conditions for triggering the first AR event in response to selecting the second option. This provides developers with greater flexibility to create useful, interesting, and engaging AR experiences without being limited by the resource constraints of the messaging application and / or client device running the AR experience.

[0020] The technology described herein improves the efficiency of using electronic devices and the overall experience of users when using electronic devices. In addition, by customizing and automating the tracking of AR features or events across devices, the total amount of system resources required to complete tasks is reduced.

[0021] Networked computing environment

[0022] Figure 11 is a block diagram illustrating an example messaging system 100 for exchanging data (e.g., messages and associated content) over a network. The messaging system 100 includes multiple instances of a client device 102, each of the multiple instances hosting several applications including a client application 104 and other external applications 109 (e.g., third-party applications). Each client application 104 is communicatively coupled to other instances of the client application 104 (e.g., hosted on corresponding other client devices 102), a messaging server system 108, and an external application server 110 via a network 112 (e.g., the Internet). The client application 104 may also communicate with locally hosted third-party applications such as the external application 109 using an application program interface (API). The client application 104 may include a messaging client, a messaging application, and / or an AR developer application or an AR development client.

[0023] The client device 102 can operate as a standalone device, or can be coupled (e.g., networked) to other machines. In a networked deployment, the client device 102 can operate as a server machine or a client machine in a server-client network environment, or as a peer machine in a peer (or distributed) network environment. The client device 102 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 (network) device, a network router, a network switch, a network bridge, or any machine capable of performing the disclosed operations. In addition, although only a single client device 102 is shown, the term "client device" should also be considered to include a collection of machines that perform the disclosed operations individually or jointly.

[0024] In some examples, client device 102 may include AR glasses or AR headsets, where virtual content is displayed within the lenses of the glasses while the user views the real world environment through the lenses. For example, an image may be presented on a transparent display, which enables the user to view content presented on the display and real-world objects simultaneously.

[0025] In some examples, the client device 102 may be operated by an AR experience developer. In this case, the AR experience developer (or AR developer) accesses an AR experience development platform. The AR experience development platform allows the AR developer to generate an AR experience package that includes a set of AR elements and different types of events or triggers. In some examples, the AR developer can specify under which conditions the set of AR events or triggers are tracked and aggregated into a set of metrics. In some examples, various standard events or triggers are tracked in an automatic manner without input from the AR developer. In some examples, in response to determining that certain AR components have been enabled, configured, or included in the AR experience package, a set of custom events or triggers are added to the list of custom events for automatic tracking. In this case, events or triggers are automatically tracked separately for each AR experience for which the corresponding AR component has been enabled. The AR component may include any type of functionality available on the AR experience, such as object tracking, facial tracking, location tracking, camera view, etc.

[0026] In some examples, when an AR experience is launched or accessed on an end-user client device 102, interactions corresponding to events or triggers performed by the end-user are tracked and aggregated into a set of metrics in response to determining that the performed interactions correspond to one of the event or trigger types associated with the AR experience (e.g., those events or triggers manually specified or programmed by an AR experience developer, standard events or triggers automatically included for tracking, and / or events or triggers automatically added for tracking in response to certain components being enabled). After the AR experience is terminated, any tracked interactions (based on predefined event or trigger types) are added to a batch message and sent to a remote server for presentation to the AR experience developer.

[0027] In some examples, the conditions may include a geographic location, a level in a game application or AR experience, a view or depiction of a portion of a real-world environment, a time, a time of day, a client device type, a user type, a user account type, a location tag, an image tag, or any other suitable condition. The type of event or trigger may include any unique feature of an AR experience. In some examples, the type of event or trigger that may be tracked and used to generate one or more metrics may include any combination of: a face discovery event, a face loss event, an object tracking standard, a 3D object tracking standard, a marker tracking component, a click event, a touch start event, a touch move event, a touch end event, a shared session event, a shared session join event, a voice command event, a voice transcription event, and / or a language event. In some examples, the conditions may be manually programmed and stored as part of an AR experience package. In some examples, the conditions are set by the AR developer selecting between various options for setting certain conditions associated with a component and / or an event or trigger. In some examples, the conditions are predetermined and set when a given component is added to an AR experience package. In this way, a given AR experience package can be associated with standard events that are tracked, and either individually or together with custom events or triggers that are added in response to adding certain components to the AR experience package. In some examples, the AR developer cannot disable the standard list of events and triggers for tracking. In this case, only custom events or triggers can be disabled for tracking, such as by removing the AR component or deselecting the tracking option for the corresponding custom event or trigger.

[0028] In some examples, a face-finding event may be associated with a condition or trigger that is satisfied when a new face (or other specified object) is detected by a camera of client device 102. In this case, a first counter may be started to count or measure the total number of face-finding events or the average number of face-finding events per session (e.g., each period of time between starting an AR experience and ending the AR experience). In some examples, a face-lost event may be associated with a condition or trigger that is satisfied when a face (or other specified object) is no longer detected and tracked (e.g., if the face is blocked from view of the camera or is too far away). In this case, a second counter may be started to count or measure the total number of face-lost events per session or the average number of faces lost in a session.

[0029] In some examples, the object tracking criteria are associated with a condition or trigger that is satisfied when the object is currently being tracked by the camera of the end user's client device 102. A third counter may be used to count the total or average number of times the object is tracked in a given session. In some examples, a separate 3D object tracking criterion may be used to separately track the number of 3D objects tracked by the camera of the client device 102. In some examples, the marker tracking criterion may be associated with a condition or trigger that is satisfied when a marker image is currently being tracked by the camera. A fourth counter may be used to count the total or average number of times the marker image is tracked.

[0030] In some examples, a tap event is associated with a condition or trigger that is satisfied when a touch input is detected by the client device 102. A fifth counter may be used to count the total or average number of times a touch input is detected during a given session. Similar conditions or triggers may be used to track the number of times a user begins touching the screen, or when a user moves a finger (dragging across the screen) while maintaining touch of the screen, and / or when a user ends touch of the screen (e.g., by lifting a finger from the screen).

[0031] In some examples, a shared or multi-user AR sharing session is associated with a condition or trigger that is satisfied when the shared AR session is shared with another user. A sixth counter may be used to count the total or average number of times the AR session has been shared with other users. Similar conditions or triggers may be used to track the number of times a shared AR session has been joined by other users.

[0032] In some examples, a voice command event is associated with a condition or trigger that is satisfied when a voice navigation command is detected by the client device 102 (e.g., using natural language processing). A seventh counter may be used to count the total or average number of times a voice command event is detected during a given session. A voice transcription event is associated with a condition or trigger that is satisfied when a speech is transcribed in real time during a recording or for a stored video clip. An eighth counter may be used to count the total or average number of times a voice transcription event is detected during a given session. A language displayed event may be used to track the distribution and location of languages. This event enables AR experience developers to locate text in an AR experience that will automatically use correctly located strings.

[0033] AR experience developers may choose any other custom or predefined event or trigger type to track separately and use to accumulate or generate metrics for a given AR experience.

[0034] The client applications 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 client applications 104 and between client applications 104 and messaging server systems 108 includes functions (e.g., commands to activate functions) and payload data (e.g., text, audio, video, or other multimedia data).

[0035] The messaging server system 108 provides server-side functionality to certain client applications 104 via the network 112. Although certain functions of the messaging system 100 are described herein as being performed by either the client application 104 or the messaging server system 108, it may be a design choice whether certain functions are located within the client application 104 or within the messaging server system 108. For example, it may be technically preferable to initially deploy certain technologies and functions within the messaging server system 108 but later migrate the technologies and functions to the client application 104 where the client device 102 has sufficient processing power.

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

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

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

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

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

[0041] The image processing server 122 is used to implement the enhancement system 208 ( Figure 2). The scanning function includes activating and providing one or more augmented reality experiences on the client device 102 when the client device 102 captures an image. Specifically, the client application 104 on the client device 102 can be used to activate the camera. The camera displays one or more real-time images or videos and one or more icons or identifiers of one or more augmented reality experiences to the user. The user can select a given identifier in the identifier to start the corresponding augmented reality experience or perform the desired image modification (for example, replace the clothing worn by the user in the video or recolor the clothing worn by the user in the video or modify the clothing based on the gesture performed by the user).

[0042] The social network server 124 supports various social networking functions and services and makes them available to the messaging server 118. To this end, the social network server 124 maintains and accesses an entity graph 308 (e.g., Figure 3 ). Examples of functions and services supported by the social networking server 124 include identifying other users of the messaging system 100 that have a relationship with a particular user or that the particular user is "following," and also include identifying interests and other entities of a particular user.

[0043] Returning to the client application 104, the features and functions of the external resource (e.g., a third-party application 109 or an applet) are available to the user via the interface of the client application 104. The client application 104 receives a user selection of an option for launching or accessing features of an external resource (e.g., a third-party resource) such as an external application 109. The external resource can be a third-party application (external application 109) installed on the client device 102 (e.g., a "native application"), or a small-scale version of a third-party application (e.g., a "mini program") hosted on the client device 102 or located at a remote end of the client device 102 (e.g., on a third-party server 110). The small-scale version of the third-party application includes a subset of the features and functions of the third-party application (e.g., a full-scale, native version of a third-party standalone application) and is implemented using a markup language document. In one example, the small-scale version of the third-party application (e.g., a "mini program") is a web-based markup language version of the third-party application and is embedded in the client application 104. In addition to using markup language documents (eg, *ml files), applets may include scripting languages ​​(eg, .*js files or .json files) and style sheets (eg, *ss files).

[0044] In response to receiving a user selection of an option for launching or accessing a feature of an external resource (external application 109), the client application 104 determines whether the selected external resource is a web-based external resource or a locally installed external application. In some cases, the external application 109 installed locally on the client device 102 can be independently and separately launched from the client application 104, such as by selecting an icon corresponding to the external application 109 on the home screen of the client device 102. A small-scale version of such an external application can be launched or accessed via the client application 104, and in some examples, no part of the small-scale external application or only a limited part can be accessed outside the client application 104. The small-scale external application can be launched by the client application 104 receiving a markup language document associated with the small-scale external application from the external application server 110 and processing such a document.

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

[0046] The client application 104 can notify the user of the client device 102 or other users (e.g., "friends") associated with such a user of one or more external resources of activities occurring. For example, the client application 104 can provide a notification related to the current or recent use of an external resource by one or more members of a user group to a participant in a conversation (e.g., a chat session) in the client application 104. One or more users can be invited to join an active external resource or to start an external resource that has been recently used but is currently inactive (in the friend group). The external resource can provide the participants in the conversation who each use the corresponding client application 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 can be an interactive chat card, and the members of the chat can interact with the interactive chat card to, for example, start the corresponding external resource, view specific information in the external resource, or bring the members of the chat to a specific location or state in the external resource. Within a given external resource, a response message can be sent to the user on the client application 104. The external resource can selectively include different media items in the response based on the current context of the external resource.

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

[0048] The client application 104 may allow a user to launch an AR experience with different types of AR elements or events. Specifically, the client application 104 may receive a request to access an AR experience. In response to receiving the request to access the AR experience, the client application 104 launches an AR experience package associated with the AR experience. As part of the AR experience package, the client application 104 accesses a list of event types associated with the AR experience for generating one or more metrics. The list may include predefined event types and / or event types specifically configured and selected by the AR developer and / or event types for tracking that are automatically added when certain AR components are added to the AR experience package.

[0049] The client application 104 may determine that an interaction associated with the AR experience corresponds to a first event type in a list of event types. The client application 104 may generate interaction data representing the interaction for the first event type and receive a request to terminate the AR experience. In response to receiving the request to terminate the AR experience, the client application 104 may send the interaction data to a remote server. The remote server may collect the interaction data from many client devices 102 and generate feature-specific metrics for the AR experience. The remote server may present the feature-specific metrics to the AR experience developer. This may enable the AR experience developer to enhance or improve certain features of the AR experience, thereby improving the overall experience of the end user. The list of interactions associated with the AR experience may be defined by the AR developer, so that each AR experience may have a unique list of interactions that may be tracked. Such interactions may correspond to different events tracked for each AR experience based on a configuration specified by the AR developer.

[0050] In some examples, the client application 104 may present an AR developer interface. In this case, the client application 104 may be operated by an AR developer to develop and create one or more AR experiences, as discussed below.

[0051] System Architecture

[0052] Figure 21 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 client application 104 and an application server 114. The messaging system 100 contains several subsystems that are supported on the client side by the client application 104 and on the server side by the application server 114. These subsystems include, for example, a transient timer system 202, a collection management system 204, an enhancement system 208, a map system 210, a game system 212, and an external resource system 220.

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

[0054] 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 available for a specified period of time (such as, for the duration of an event related to the content). For example, content related to a concert can be made 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 client application 104.

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

[0056] 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 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 client application 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 client application 104 based on other information such as social network information of the user of the client device 102. The media overlay 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) at the client device 102. For example, the media overlay can include text, graphic elements, or images that can be overlaid on photos taken by the client device 102. In another example, the media overlay includes a location identification overlay (e.g., Venice Beach), the name of a live event, or a business name overlay (e.g., Beach Cafe). In another example, the enhancement system 208 uses the geographic location of the client device 102 to identify a media overlay that includes the name of the business at the geographic location of the client device 102. The media overlay may include other tags associated with the business. The media overlay may be stored in the database 126 and accessed through the database server 120.

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

[0058] In other examples, the augmentation system 208 provides a merchant-based publishing platform that enables merchants to select specific media overlays associated with a geographic location via a bidding process. For example, the augmentation system 208 associates the media overlay of the highest bidding merchant with the corresponding geographic location for a predefined amount of time. The augmentation system 208 communicates with the image processing server 122 to obtain an augmented reality experience, and presents an identifier of such an experience in one or more user interfaces (e.g., as an icon on a real-time image or video, or as a thumbnail or icon in an interface dedicated to an identifier of the presented augmented reality experience). Once an augmented reality experience is selected, one or more images, videos, or augmented reality graphical elements are retrieved and presented as an overlay on top of an image or video captured by the client device 102. In some cases, the camera is switched to a front view (e.g., the front camera of the client device 102 is activated in response to activation of a particular augmented reality experience), and an image from the front camera of the client device 102, rather than the rear camera of the client device 102, begins to be displayed on the client device 102. One or more images, videos, or augmented reality graphical elements are retrieved and presented as an overlay on top of the image captured and displayed by the front-facing camera of the client device 102 .

[0059] In other examples, the augmentation system 208 can communicate and exchange data with another augmentation system 208 on another client device 102 and with a server via the network 112. The exchanged data may include: a session identifier identifying the shared AR session; a transformation between a first client device 102 and a second client device 102 (e.g., a plurality of client devices 102, including the first device and the second device) for aligning the shared AR session to a common origin; a common coordinate system; functionality (e.g., commands for activating functions), and other payload data (e.g., text, audio, video, or other multimedia data), such as during a video call between multiple users or participants.

[0060] The augmentation system 208 sends the transformation to the second client device 102 so that the second client device 102 can adjust the AR coordinate system based on the transformation. In this way, the first client device 102 and the second client device 102 synchronize their coordinate systems and frames to display the content in the AR session. Specifically, the augmentation system 208 calculates the origin of the second client device 102 in the coordinate system of the first client device 102. The augmentation system 208 can then determine an offset in the coordinate system of the second client device 102 based on the location of the origin in the coordinate system of the second client device 102 from the perspective of the second client device 102. The transformation is generated using the offset so that the second client device 102 generates AR content according to a common coordinate system with the first client device 102.

[0061] The augmentation system 208 can communicate with the client device 102 to establish a separate or shared AR session. The augmentation system 208 can also be coupled to the messaging server 118 to establish an electronic group communication session (e.g., group chat, instant messaging, video call, group video call, etc.) for the client device 102 in the shared AR session. The electronic group communication session can be associated with a session identifier provided by the client device 102 to obtain access rights to the electronic group communication session and the shared AR session. In one example, the client device 102 first obtains access rights to the electronic group communication session, and then obtains a session identifier in the electronic group communication session that allows the client device 102 to access the shared AR session. In some examples, the client device 102 is able to access the shared AR session without the assistance of the augmentation system 208 in the application server 114 or communication with the augmentation system 208 in the application server 114.

[0062] The mapping system 210 provides various geo-location functions and supports presentation of map-based media content and messages by the client application 104. For example, the mapping system 210 enables display of (e.g., stored in the profile data 316, in Figure 3) to indicate the current or past locations of the user's "friends," as well as media content (e.g., a collection of messages including photos and videos) generated by such friends within the context of the map. For example, messages 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 map interface of the client application 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 via the client application 104 (e.g., using an appropriate status avatar), where the location and status information is similarly displayed to selected users within the context of the map interface of the client application 104.

[0063] The gaming system 212 provides various gaming functions within the context of the client application 104. The client application 104 provides a gaming interface that provides a list of available games (e.g., web-based games or web-based applications) that can be launched by a user within the context of the client application 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 client application 104. The client application 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., gaming coins and items).

[0064] The external resource system 220 provides the client application 104 with an interface for communicating with the external application server 110 to launch or access external resources. Each external resource (application) server 110 hosts, for example, an application based on a markup language (e.g., HTML5) or a small-scale version of an external application (e.g., a game, utility, payment, or ride-sharing application external to the client application 104). The client application 104 can launch a web-based resource (e.g., application) by accessing an HTML5 file from an external resource (application) server 110 associated with a web-based resource. In some examples, the application hosted by the external resource server 110 is programmed in JavaScript using a software development kit (SDK) provided by the messaging server 118. The SDK includes an application program interface (API) with 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 access to certain user data of the client application 104 to a given third-party resource. HTML5 is used as an example technology for programming games, but applications and resources programmed based on other technologies can be used.

[0065] In order to integrate the functions of the SDK into the web-based resource, the SDK is downloaded from the messaging server 118 by the external resource (application) server 110 or received by the external resource (application) 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 client application 104 into the web-based resource.

[0066] The SDK stored on the messaging server 118 effectively provides a bridge between external resources (e.g., a third party or external application 109 or applet and a client application 104). This provides users with a seamless experience of communicating with other users on the client application 104 while retaining the look and feel of the client application 104. In order to bridge the communication between the external resources and the client application 104, in some examples, the SDK facilitates the communication between the external resource server 110 and the client application 104. In some examples, the WebViewJavaScriptBridge running on the client device 102 establishes two one-way communication channels between the external resources and the client application 104. Messages are sent asynchronously between the external resources and the client application 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.

[0067] By using the SDK, not all information from the client application 104 is shared with the external resource server 110. The SDK limits which information is shared based on the needs of the external resource. In some examples, each external resource 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 (such as a box art or other graphics) of the web-based external resource in the client application 104. Once the user selects the visual representation or instructs the client application 104 to access the features of the web-based external resource through the GUI of the client application 104, the client application 104 obtains the HTML5 file and instantiates the resources required to access the features of the web-based external resource.

[0068] The client application 104 presents a graphical user interface (e.g., a login page or title screen) for the external resource. During, before, or after presenting the login page or title screen, the client application 104 determines whether the launched external resource has been previously authorized to access the user data of the client application 104. In response to determining that the launched external resource has been previously authorized to access the user data of the client application 104, the client application 104 presents another graphical user interface of the external resource, which includes 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 client application 104, after a threshold time period (e.g., 3 seconds) of displaying the login page or title screen of the external resource, the client application 104 slides out 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 part of the screen). The menu identifies the type of user data that the external resource will be authorized to use. In response to receiving a user selection of the acceptance option, the client application 104 adds the external resource to the list of authorized external resources and enables the external resource to access the user data from the client application 104. In some examples, external resources are authorized to access user data by client application 104 according to the O Auth 2 framework.

[0069] The client application 104 controls the type of user data shared with the external resource based on the type of external resource that is authorized. For example, access to a first type of user data (e.g., only a two-dimensional avatar of a user with or without different avatar characteristics) is provided to an external resource including a full-scale external application (e.g., a third party or external application 109). As another example, 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) is provided to an external resource including a small-scale version of an external application (e.g., a web-based version of a third-party application). Avatar characteristics include different ways to customize the look and feel of an avatar (such as different poses, facial features, clothing, etc.).

[0070] The AR event tracking system 224 may receive a request to access an AR experience and may access a list of event types associated with the AR experience for generating one or more metrics from an AR experience package associated with the AR experience. The AR event tracking system 224 may determine that an interaction associated with the AR experience corresponds to a first event type in the list of event types. The AR event tracking system 224 may generate interaction data representing the interaction for the first event type and receive a request to terminate the AR experience. In response to receiving the request to terminate the AR experience, the AR event tracking system 224 may send the interaction data to a remote server. The AR event tracking system 224 may collect the interaction data from many client devices 102 and generate feature-specific metrics for the AR experience. The AR event tracking system 224 may present feature-specific metrics to the AR experience developer. This may enable the AR experience developer to enhance or improve certain features of the AR experience, thereby improving the overall experience of the end user.

[0071] The AR event tracking system 224 can allow AR developers to create AR experiences with tracked AR event types or trigger types. The AR types that can be tracked can include any combination of the following: custom events, face discovery events, face loss events, object tracking standards, 3D object tracking standards, marker tracking components, click events, touch start events, touch move events, touch end events, shared session events, shared session join events, voice command events, voice transcription events, and / or language events. The AR event tracking system 224 can present a user interface for the AR developer platform. The user interface can be used to select which AR events to be tracked and collected after the AR experience is terminated or closed. The user interface can be used to select which AR components to include or program into the AR experience package in order to automatically generate a custom list of events to be tracked and collected after the AR experience is terminated or closed.

[0072] In some examples, the graphical user interface presents a list of AR events associated with the AR experience, and includes a first option associated with a first AR event in the list of AR elements, in response to selecting the first option, to track the first AR event to be collected and sent or stored after the AR experience is terminated. The user interface also includes a second option associated with the first AR event for specifying a condition for tracking the first AR event. The user interface also includes a third option for specifying a custom name for the first event type being tracked, which can be used to generate a graph, chart, or other representation of the metrics collected for the event. In some examples, the user interface only includes an option for specifying a custom name for the event to be tracked, and provides an option for linking to Javascript code that defines parameters of the event or a trigger for the event. In some cases, the graphical user interface allows an AR developer to add an AR component to the AR experience, and the AR development platform automatically adds or generates an event or trigger for tracking the interaction for the added AR component.

[0073] This functionality provides developers with greater flexibility to create useful, interesting, and engaging AR experiences without being limited by the resource constraints of the messaging application and / or client device running the AR experience. Specifically, each AR developer can uniquely configure what event metrics are tracked for each of their respective AR experiences, including any predetermined events provided by the system and unique events that the AR developer wants to track.

[0074] Data Architecture

[0075] 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 several tables, it will be appreciated that data may be stored in other types of data structures (e.g., as an object-oriented database).

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

[0077] The entity table 306 stores entity data and is linked (e.g., by reference) to the entity graph 308 and profile data 316. The entities for which 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 for 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).

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

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

[0080] 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 (eg, notifications) of the relevant group.

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

[0082] The database 126 may also store data related to individual and shared AR sessions. The data may include data transmitted between an AR session client controller of a first client device 102 and another AR session client controller of a second client device 102, and data transmitted between an AR session client controller and an augmented system 208. The data may include data used to establish a common coordinate system for a shared AR scene, transformations between devices, session identifiers, images depicting the body, skeletal joint positions, wrist positioning, feet, and the like.

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

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

[0085] Other augmented data that may be stored in the image table 312 include augmented reality content items (eg, corresponding to an applied augmented reality experience). Augmented reality content items or augmented reality items may be real-time special effects and sounds that may be added to an image or video.

[0086] As described above, augmented data includes augmented reality content items, overlays, image transformations, AR images, AR signs or logos, and similar items involving modifications that can be applied to image data (e.g., videos or images). This includes real-time modifications that modify the image when it is captured using a device sensor (e.g., one or more cameras) of the client device 102 and then display the image with the modification on the screen of the client device 102. This also includes modifications to stored content (such as video clips that can be modified in the gallery). For example, in a client device 102 that accesses multiple augmented reality content items, a user can use a single video clip with multiple augmented reality content items to see how different augmented reality content items will modify the stored clips. For example, by selecting different augmented reality content items for the same content, multiple augmented reality content items that apply different pseudo-random motion 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 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 content captured by the device sensors may be recorded and stored in memory with or without modification (or both). In some systems, a preview feature may simultaneously show how different augmented reality content items will look in different windows in the display. This may, for example, enable viewing of multiple windows with different pseudo-random animations on the display at the same time.

[0087] 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.); tracking such objects in video frames as they leave, enter, and move around the field of view; and modifying or transforming 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 frame of a video). 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.

[0088] Real-time video processing can be performed using any type of video data (e.g., video streams, video files, etc.) stored in the memory of any type of computerized system. For example, a user can load a video file and save it in the memory of the device, or a sensor of the device can be used to generate a video stream. In addition, computer animation models can be used to process any object, such as human faces and body parts, animals, or inanimate objects (such as chairs, cars, or other objects).

[0089] 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 modification request, thereby transforming the frame of the video stream. For different types of transformations, the transformation of the frame of the video stream can be performed by different methods. For example, for a frame transformation that mainly involves changing the form of the elements of the object, the characteristic points of each element of the object are calculated (for example, using an active shape model (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 group of first points is generated for each element based on the modification request, and a group of second points is generated for each element based on the group of first points and the modification request. Then, the frame of the video stream can be transformed by modifying the elements of the object based on the group of first points, the group of second points and the grid. In such an approach, the background of the modified object may also be changed or distorted by tracking and modifying the background.

[0090] 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 are generated based on the points. The elements of the object are then tracked by aligning the area for each element with the positioning for 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 into the area based on the modification request; and modifying or distorting the elements of the area or object. In various examples, any combination of such modifications or other similar modifications may be used. For certain models to be animated, some characteristic points may be selected as control points for the entire state space to be used to determine options for model animation.

[0091] In some examples of computer animation models for transforming image data using face detection, 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.

[0092] Other methods and algorithms suitable for face detection may be used. For example, in some examples, landmarks are used to locate features, and the landmarks represent distinguishable points that are present in most of the images considered. For example, for facial landmarks, the location of the left pupil can be used. If the initial landmarks are not identifiable (for example, when a person is wearing an eye patch), secondary landmarks can be used. Such a landmark identification process can be used for any such object. In some examples, a set of landmarks forms a shape. The coordinates of the points in the shape can be used to represent the shape as a vector. A similarity transformation (which allows translation, scaling, and rotation) that minimizes the average Euclidean distance between the shape points is used to align one shape with another. The mean shape is the average of the aligned training shapes.

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

[0094] 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 enabled by a convolutional neural network that has been configured to execute efficiently on the client device 102.

[0095] 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, where the neural network operates as part of a client application 104 operating on the client device 102. A transformation system operating within the client application 104 determines the presence of a face within the image or video stream and provides a modification icon associated with the computer animation model for transforming the image data, or the computer animation model can exist in association with an interface described herein. The modification icon includes the following changes, which can be the basis for modifying the user's face 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 user's image to reflect the selected modification icon (e.g., generating a smiling face for the user). Once the image or video stream is captured and the specified modification is selected, the modified image or video stream can be presented in a graphical user interface displayed on the client device 102. The transformation system can implement a complex convolutional neural network on a portion of the image or video stream to generate and apply the selected modification. That is, a user can capture an image or video stream, and once a modification icon is selected, the modified result can be presented to the user in real time or near real time. In addition, the modification can be persistent while the video stream is being captured and the selected modification icon remains toggled. A machine learning neural network can be used to implement such modification.

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

[0097] 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 client application 104 may include a user-selectable icon to enable the sending user to add specific content to his or her personal story.

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

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

[0100] 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 whose message data is stored in the entity table 306. The entity table 306 can 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.

[0101] Data communication architecture

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

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

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

[0105] 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 sent or received message 400 may be stored in the image table 312 .

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

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

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

[0109] • Message duration parameter 414: A parameter value indicating the amount of time in seconds that the content of the message (eg, message image payload 406, message video payload 408, message audio payload 410) will be presented to or made accessible to the user via the client application 104.

[0110] Message geolocation parameters 416: Geolocation data (e.g., latitude and longitude coordinates) associated with the content payload of the message. Multiple message geolocation parameter 416 values ​​may be included in the payload, each of which is associated with a content item included in the content (e.g., a specific image within a message image payload 406, or a specific video within a message video payload 408).

[0111] 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, an identifier value may be used to associate multiple images within message image payload 406 with each of multiple content collections.

[0112] 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 indicating the relevant animal may be included within the message tags 420. The tag values ​​may be manually generated based on user input, or may be automatically generated using, for example, image recognition.

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

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

[0115] The content (e.g., value) of each component of message 400 may be a pointer to a location in a table in which the content data value is stored. For example, the image value in message image payload 406 may be a pointer to a location in image table 312 (or the address of a location in image table 312). Similarly, the value in message video payload 408 may point to data stored in video table 304, the value stored in message enhancement data 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.

[0116] AR Event Tracking System

[0117] Figure 5 is a block diagram illustrating an example AR event tracking system 224 according to some examples. The AR event tracking system 224 includes an AR experience development module 500 , an AR event tracking module 510 , and an AR metric generation module 520 .

[0118] The AR experience development module 500 may generate a user interface for presentation to an AR developer on an AR developer client device 102. The user interface may enable an AR developer to select AR events to be tracked for an AR experience launched on one or more client devices 102. In some examples, the user interface enables an AR developer to add an AR component, and AR events associated with the AR component are automatically added for tracking interactions. In this way, the AR developer does not need to manually define and program code for tracking interactions with the added AR components. The user interface enables AR developers to define unique event tracking for each of their AR experiences, such as by providing Javascript code that defines the manner and process of tracking events (such as conditions for triggering tracking and counting). Event tracking may correspond to predefined events or custom events generated by the AR developer. In this way, one AR experience may be associated with a first list of tracked AR event types, which is the same or different from a second list of tracked AR event types for a second AR experience. This enables AR developers to better control which types of events are tracked and used to generate metrics, and which types of events are not tracked and used to generate metrics, and how to track or trigger events.

[0119] As referred to herein, an “AR experience package” or “AR package” refers to a set of AR elements (including standard AR elements and linked AR elements) and corresponding code that dictates the visual appearance, interactions, and behavior of each of the AR elements. An AR package includes code required for a client device 102 to launch and execute an AR experience associated with the AR package.

[0120] In some examples, AR experience development module 500 receives a request to access a developer user interface from developer client device 102. AR experience development module 500 may receive login credentials from developer client device 102. AR experience development module 500 may search for an account associated with the login credentials and may generate a graphical user interface associated with the account for presentation to developer client device 102. AR experience development module 500 may present multiple AR experience packages associated with the account in the graphical user interface. In some cases, an account may be accessible by an organization, in which case multiple users within the organization may share access to the account and may view the same set of AR experience packages.

[0121] AR experience development module 500 may receive input from developer client device 102 selecting a given AR experience package. In response to receiving the input, AR experience development module 500 may present graphical user interface 600 ( Figure 6 ). The AR experience development module 500 may include in the graphical user interface 600 an identifier of the AR experience package and a list 620 of AR events or triggers included in the AR experience package. In some cases, instead of presenting a list of AR events or triggers or in addition to presenting a list of AR events or triggers, the graphical user interface 600 lists AR components that are available for addition or have been added to the AR experience package. For each AR component or portion of the AR components included in the AR experience package, a set of events or triggers are automatically added for tracking interactions. In some cases, the graphical user interface 600 provides an option for specifying a custom name for the event to be tracked. The graphical user interface 600 may allow an AR developer to enter a custom name and link Javascript code that defines operations and conditions for tracking interactions with the AR experience associated with the custom name.

[0122] An AR event or trigger may include or represent a specified action or object associated with an AR experience. For example, an AR event or trigger may include any combination of the following: a custom event, a camera event (specifying activation of a front camera or rear setting device), a face discovery event, a face loss event, an object tracking standard, a 3D object tracking standard, a marker tracking component, a click event, a touch start event, a touch move event, a touch end event, a shared session event, a shared session join event, a voice command event, a voice transcription event, and / or a language event. The list may also include one or more AR elements or objects. AR elements may include 2D meshes, 3D meshes, videos, audio files, image files, and / or machine learning models.

[0123] AR experience development module 500 may also present in graphical user interface 600 an option (not shown) for accessing or viewing metrics associated with the selected AR experience package. In response to receiving a selection of this option, AR experience development module 500 may communicate with AR metric generation module 520 to obtain one or more metrics associated with the AR experience. AR experience development module 500 may then generate a user interface including a graph or chart representing the one or more metrics. Figure 8 An example graph or chart is depicted in the example graphical user interface 800 shown in FIG. 8 and discussed below.

[0124] The AR experience development module 500 may receive input selecting a given AR event 622 or AR component from a list 620 of AR events or triggers. In response, the AR experience development module 500 presents a prompt 610 listing options for generating metrics associated with the given AR event 622. The list of options may include: a custom event name option 634, an enable event tracking option 630, and one or more conditional options 632 for event tracking. In some cases, the conditional option 632 for event tracking may be displayed in response to receiving a selection to enable event tracking option 630. The selection to enable event tracking option 630 generates a counter associated with the given AR event 622. Each time a given AR event 622 is detected to be executed or satisfied on an end-user client device 102, the counter is incremented. The counter may be specific to a client device 102, or may be a counter associated with many client devices 102. The value of the counter may be used to generate or represent a metric for an AR experience including the AR event 622 in a graphical user interface depicting a graph or chart. In some cases, each client device 102 provides a cumulative value of the counter, and the cumulative values ​​received from multiple client devices 102 are averaged by the server (e.g., AR metric generation module 520). In some examples, each client device 102 calculates the average locally and provides the average value of the counter to AR experience development module 500.

[0125] In response to receiving a selection of enable event tracking option 630, a new field is added to a graph or chart representing a metric associated with the AR experience. The new field may be visually represented using a name that matches the name entered in custom event name option 634. In some cases, in response to adding an AR component that is automatically associated with an event or trigger, a new field is added to a graph or chart representing a metric associated with the AR experience component.

[0126] Prompt 610 may include an event tracking condition option 632. In response to receiving a selection of option 632, one or more fields for entering one or more conditions that trigger counting of events associated with a given event AR event 622 may be presented. For example, the condition may specify a subscription level of an end user, a geographic region associated with the end user, a time of day, a type of AR experience, a geographic location, a level in a game application or AR experience, a view or depiction of a portion of a real-world environment, a request from an end user to enable AR objects or elements to be persistent, a time, a location tag, an image tag, or any other suitable condition. In some examples, prompt 610 may not be displayed at all, and a custom event may be automatically added for tracking in response to certain associated AR components being added, generated, or enabled by an AR developer.

[0127] To ensure user data privacy, the client device 102 (or an application implemented on the client device 102) can inform the user about the type of information that can be collected and prompt the user to choose whether to opt in before the data is collected. If the user refuses to opt in and does not give consent, the system will not collect the data. If the user opts in, the data will be securely stored on the server in an encrypted manner.

[0128] In some examples, the conditions may be the same or different for each event type that is tracked to generate a metric. For example, a first event 622 may be associated with a first set of conditions (e.g., a certain subscription level of an end user), and a second event may be associated with a second set of conditions (e.g., a geographic region of a client device 102). When the criteria for the first event are met and when the first set of conditions are met, the first event 622 increments or adjusts a counter associated with the first event 622. When the criteria for the second event are met and when the second set of conditions are met, the second event increments or adjusts a corresponding counter associated with the second event.

[0129] In some examples, a given event 622 may be associated with or represent a face discovery event. A face discovery event may be associated with a condition or trigger that is satisfied when a camera of a client device 102 detects a new face (or other specified object). For example, an AR experience may be initiated by an end-user client device 102. In response, a graphical user interface such as Figure 7 , and the graphical user interface may include a first real-world object 710 and a second real-world object 712 and one or more AR objects (not shown). The client device 102 may monitor interactions occurring during an AR experience session initiated on the client device 102. The client device 102 may obtain a list of events including a given event 622 that triggers generation of a metric for the AR experience from the associated AR experience package.

[0130] In some examples, client device 102 may determine that a particular interaction (e.g., a face in a camera feed) corresponds to a given event 622 included in a list of events. That is, client device 102 may determine that a particular interaction corresponds to a first event type in a list of event types associated with an AR experience. For example, a given event 622 may be a face discovery event enabled for tracking and generating metrics. In this case, client device 102 may generate interaction data for a face discovery event to represent the detected interaction. This may be performed by aggregating interactions into an entity associated with a given event 622. The entity may include a first counter that is instantiated to calculate or measure the total number of face discovery events or the average number of face discovery events per session (e.g., each period of time between starting an AR experience and ending an AR experience). In some examples, in response to detecting a face in a camera feed of client device 102, client device 102 may determine that an AR event 622 has been triggered, and may present a message 720 of an AR event trigger. Client device 102 may also access one or more conditions associated with a given event 622. If one or more conditions are specified or met, client device 102 may increment the value of the first counter each time a face discovery event is triggered. In some cases, the first counter represents the total number of times a face discovery event has been triggered. In some cases, the first counter represents the average number of times a face discovery event has been triggered. In some cases, the total number of times is provided by client device 102 to AR metric generation module 520, and AR metric generation module 520 generates the average number of times.

[0131] As another example, a given event 622 may additionally or alternatively be associated with or represent a face loss event. A face loss event may be associated with a condition or trigger that is satisfied when a face (or other specified object) is no longer detected and tracked (such as if the face is blocked from view of the camera or is too far away). In this case, a second entity associated with the face loss event may be used to track events of that particular type. For example, a second counter may be turned on to calculate or measure the total number of face loss events per session or the average number of faces lost in a session. In some cases, the second counter represents the total number of times a face discovery event has been triggered. In some cases, the second counter represents the average number of times a face discovery event has been triggered. In some cases, the first counter represents the total number, and the second counter represents the average value of the associated event type. In some cases, the total number is provided by the client device 102 to the AR metric generation module 520, and the AR metric generation module 520 generates the average number.

[0132] In some examples, client device 102 may determine that a particular interaction (e.g., a particular camera view, such as a front camera view, a rear camera view, or a specified real-world object is detected in a captured image) corresponds to a given event 622 included in a list of events. That is, client device 102 may determine that a particular interaction corresponds to a given event type in a list of event types associated with an AR experience corresponding to a particular camera view. For example, given event 622 may be a camera view event that is enabled to track and generate metrics, such as to represent the number of times a front camera view is activated, a rear camera view is activated, or a specified real-world object is detected in a captured image. In this case, client device 102 may generate interaction data for the camera view event to represent the detected interaction. This may be performed by aggregating interactions into an entity associated with a given event 622. The entity may include a particular counter that is instantiated to count or measure the total or average number of times a front camera view is activated, a rear camera view is activated, or a specified real-world object is detected in a captured image. The client device 102 may also access one or more conditions associated with a given event 622. If one or more conditions are specified or met, the client device 102 may increment the value of a particular counter each time a camera view event is triggered. In some cases, the total number of times is provided by the client device 102 to the AR metric generation module 520, and the AR metric generation module 520 generates an average number of times.

[0133] The client device 102 may determine that the AR experience has been terminated. In response, the client device 102 may generate a message including any of the entities associated with the event types being tracked. For example, the client device 102 may generate a metric or counter for each of the events being tracked. The message is then sent from the client device 102 to the AR event tracking module 510. The AR event tracking module 510 may receive similar messages from many other client devices 102 that initiated the same AR experience, and may aggregate the corresponding entities or counters to generate a metric for each event type being tracked.

[0134] For example, the AR event tracking module 510 may receive a first value of a first counter associated with a facial discovery event from a first end-user client device 102, and may receive a second value of the first counter from a second end-user client device 102. The AR event tracking module 510 may combine or sum the first value and the second value to generate a metric of the first counter of facial discovery events representing the AR experience. In some examples, the AR event tracking module 510 may calculate an average of the first value and the second value to generate a metric of the first counter of facial discovery events representing the AR experience. The AR event tracking module 510 stores the metric associated with the AR experience and provides the metric to the AR metric generation module 520. In some examples, the AR event tracking module 510 provides the raw total of the first value and the second value to the AR metric generation module 520, which then calculates the average.

[0135] In some examples, a given event 622 includes or represents an object tracking criterion associated with a condition or trigger that is satisfied when the object is currently being tracked by a camera of a client device 102 of a terminal user. A third counter may be used to count the total or average number of times an object is tracked in a given session. In some examples, a separate 3D object tracking criterion may be used to separately track the number of 3D objects tracked by a camera of a client device 102. In some examples, a marker tracking criterion may be associated with a condition or trigger that is satisfied when a marker image is currently being tracked by a camera. A fourth counter may be used to count the total or average number of times a marker image is tracked. In some cases, the total number is provided by the client device 102 to the AR metric generation module 520, and the AR metric generation module 520 generates the average number.

[0136] In some examples, the click event is associated with a condition or trigger that is satisfied when the client device 102 detects a touch input. A fifth counter may be used to count the total or average number of times a touch input is detected during a given session. Similar conditions or triggers may be used to track the number of times a user begins touching the screen, or when a user moves a finger (dragging across the screen) while maintaining touch of the screen, and / or when a user ends touch of the screen (e.g., by lifting a finger from the screen).

[0137] In some examples, a shared or multi-user AR sharing session is associated with a condition or trigger that is satisfied when the shared AR session is shared with another user. A sixth counter may be used to count the total or average number of times the AR session has been shared with other users. Similar conditions or triggers may be used to track the number of times a shared AR session has been joined by other users.

[0138] In some examples, a voice command event is associated with a condition or trigger that is satisfied when a voice navigation command is detected by the client device 102 (e.g., using natural language processing). A seventh counter may be used to count the total or average number of times that a voice command event is detected during a given session. A voice transcription event is associated with a condition or trigger that is satisfied when speaking is transcribed in real time during recording or for a stored video clip. An eighth counter may be used to count the total or average number of times that a voice transcription event is detected during a given session. A language display event may be used to track the distribution and location of languages. This event enables AR experience developers to locate text in an AR experience that will automatically use correctly located strings. In some cases, the total number of times is provided by the client device 102 to the AR metric generation module 520, and the AR metric generation module 520 generates the average number of times.

[0139] The AR experience developer may select any other custom or predefined event or trigger type to be tracked separately and used to accumulate or generate metrics for a given AR experience. Similar to the first counter and the second counter (discussed above), any or all of these additional counters may be added to the message sent to the remote server in response to terminating the AR experience on the client device 102. The remote server (e.g., AR event tracking module 510) applies one or more statistical functions (e.g., averages) to each specific counter received from one or more client devices 102 to generate metrics for the AR experience.

[0140] In some examples, the AR event tracking module 510 can generate a list of generic events that can be tracked (e.g., using entities or counters) on the corresponding client device 102. The AR event tracking module 510 can receive input from the developer specifying a custom event name via option 634. In response, the AR event tracking module 510 can search the generic events for triggers that match the conditions and attributes of the given event 622. In response to determining that a particular generic event includes conditions and attributes that match the attributes of the given event 622, the AR event tracking module 510 generates a mapping that stores associations between custom event names and particular generic events. The AR event tracking module 510 can instruct the client device 102 to track the occurrence of a particular generic event while the AR experience is launched. The client device 102 can provide an entity or counter associated with a particular generic event triggered by the AR experience after the AR experience is terminated. The AR event tracking module 510 can search the mapping to identify a custom event name associated with the particular generic event. The AR event tracking module 510 may then store the tracked occurrences of the particular generic event as part of the interaction data for a given event 622 corresponding to the custom event name.

[0141] The developer client device 102 presents a user interface such as Figure 8 800 that represents metrics corresponding to one or more interactions or event types detected on one or more client devices 102 while a given AR experience is launched. User interface 800 is generated by AR metrics generation module 520 based on entities received from one or more client devices 102 that represent interactions that occurred while the AR experience was launched. An interaction may represent an occurrence of one or more event types that a developer has previously enabled for tracking.

[0142] In some examples, the user interface 800 includes a list of each event type that was previously enabled by the developer for tracking (e.g., by selecting option 630). The user interface 800 may receive a selection of a first region 820 from the developer. The first region 820 may be associated with a first type of event being tracked. For example, the first region 820 may be associated with a face discovery event. In response to receiving the selection of the first region 820, the AR metric generation module 520 presents a first graph or chart 810 indicating counter values ​​or entity values ​​received daily from one or more client devices 102. The counter value may represent the total number of face discovery events that occurred on each particular day 814. The AR metric generation module 520 may receive a user selection of an average number region 812. In response, the AR metric generation module 520 may replace the first graph or chart 810 with a different graph or chart representing the average number of times face discovery events were detected on each particular day (or some other statistical representation). Each region may represent a raw counter value (e.g., the total number of times a particular event type was triggered in a given time period (such as 28 days) and / or the average number of times a particular event type was triggered in a given time period (such as 28 days)).

[0143] The user interface 800 may receive a selection of a second event type 830. The second event type may be associated with an object tracking event. In response to receiving a selection of the second event type 830, the AR metric generation module 520 presents a second graph or chart 832 indicating a counter value or entity value received daily from one or more client devices 102. The counter value may represent the total number of object tracking events that occur on each specific day. Each area of ​​the second event type 830 may represent a raw counter value (e.g., the total number of times a specific event type is triggered in a given time period (such as 28 days) and / or the average number of times a specific event type is triggered in a given time period (such as 28 days)). The first graph or chart 810 and the second graph or chart 832 may be presented simultaneously to enable developers to seamlessly and easily compare interaction data of different event types. When an additional event type is selected in the user interface 800, the corresponding entity value or counter value is retrieved, and the display area is expanded to present a graph or chart representing the counter value.

[0144] In this way, user interface 800 can enable developers to track usage and interaction data across different custom event types selected by the developer. This enables developers to monitor and track interactions with different features of the AR experience.

[0145] Fig. 9is a flowchart of a process 900 performed by the AR event tracking system 224 according to some examples. Although the flowchart may describe the operations as a sequential process, many of these operations may be performed in parallel or simultaneously. In addition, the order of the operations may be rearranged. When the operations of the process are completed, the process is terminated. A process may correspond to a method, a procedure, etc. The steps of a method may be performed in whole or in part, may be performed in combination with some or all of the steps in other methods, and may be performed by any number of different systems or any part thereof (such as, a processor included in any system).

[0146] At operation 901 , as discussed above, the AR event tracking system 224 (eg, the client device 102 or a server) receives a request from a client device to access an AR experience.

[0147] At operation 902 , as discussed above, the AR event tracking system 224 accesses a list of event types associated with an AR experience for generating one or more metrics.

[0148] At operation 903 , as discussed above, the AR event tracking system 224 determines that the interaction associated with the AR experience corresponds to a first event type in the list of event types.

[0149] At operation 904 , the AR event tracking system 224 generates interaction data representing the interaction for the first event type, as discussed above.

[0150] At operation 905 , in response to receiving the request to terminate the AR experience, the AR event tracking system 224 sends the interaction data to a remote server, as discussed above.

[0151] Machine Architecture

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

[0153] The machine 1000 may include a processor 1002, a memory 1004, and an input / output (I / O) component 1038 that may be configured to communicate with each other via a bus 1040. In an example, the processor 1002 (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 1006 that executes instructions 1008 and a processor 1010. 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.10 Multiple processors 1002 are shown, but the machine 1000 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.

[0154] The memory 1004 includes a main memory 1012, a static memory 1014, and a storage unit 1016, which are all accessible by the processor 1002 via the bus 1040. The main memory 1012, the static memory 1014, and the storage unit 1016 store instructions 1008 that embody any one or more of the methodologies or functions described herein. The instructions 1008 may also reside, completely or partially, within the main memory 1012, within the static memory 1014, within a machine-readable medium within the storage unit 1016, within at least one of the processors 1002 (e.g., within a cache memory of a processor), or within any suitable combination thereof during execution thereof by the machine 1000.

[0155] I / O components 1038 may include various components for receiving input, providing output, generating output, sending information, exchanging information, capturing measurements, etc. The specific I / O components 1038 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 most likely not include such a touch input device. It should be appreciated that I / O components 1038 may include Fig.10, many other components not shown in the figure. In various examples, the I / O components 1038 may include a user output component 1024 and a user input component 1026. The user output component 1024 may include a visual component (e.g., a display such as a plasma display panel (PDP), a light emitting diode (LED) display, a liquid crystal display (LCD), a projector, or a cathode ray tube (CRT)), an acoustic component (e.g., a speaker), a tactile component (e.g., a vibration motor, a resistance mechanism), other signal generators, etc. The user input component 1026 may include an alphanumeric input component (e.g., a keyboard, a touch screen configured to receive alphanumeric input, an optical keyboard, or other alphanumeric input component), a point-based input component (e.g., a mouse, a touch pad, a trackball, a joystick, a motion sensor, or other pointing instrument), a tactile input component (e.g., a physical button, a touch screen or other tactile input component that provides the location and force of a touch or touch gesture), an audio input component (e.g., a microphone), etc.

[0156] In other examples, the I / O component 1038 may include a biometric component 1028, a motion component 1030, an environmental component 1032, or a positioning component 1034, as well as various other components. For example, the biometric component 1028 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, sweat, or brain waves), identifying people (e.g., voice recognition, retinal recognition, facial recognition, fingerprint recognition, or EEG-based recognition), etc. The motion component 1030 includes an acceleration sensor component (e.g., an accelerometer), a gravity sensor component, and a rotation sensor component (e.g., a gyroscope).

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

[0158] 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. For example, the rear-facing camera may be used to capture still images and videos in a more traditional camera mode, where these images are similarly enhanced with 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.

[0159] Additionally, the camera system of the client device 102 may include dual rear cameras (e.g., a main camera and a depth sensing camera), or even triple, quad, or quintuple rear camera configurations on the front and back sides of the client device 102. For example, these multiple camera systems may include a wide-angle camera, an ultra-wide-angle camera, a telephoto camera, a macro camera, and a depth sensor.

[0160] The positioning component 1034 includes a position sensor component (for example, a GPS receiver component), an altitude sensor component (for example, an altimeter or a barometer that detects air pressure, and the altitude can be obtained based on the air pressure), an orientation sensor component (for example, a magnetometer), etc.

[0161] Various technologies may be used to implement communications. The I / O components 1038 also include a communication component 1036 that is operable to couple the machine 1000 to the network 1020 or device 1022 via a corresponding coupling or connection. For example, the communication component 1036 may include a network interface component or other suitable device that interfaces with the network 1020. In other examples, the communication component 1036 may include a wired communication component, a wireless communication component, a cellular communication component, a near field communication (NFC) component, Components (e.g. Low energy consumption), Device 1022 may be another machine or any of a variety of peripheral devices (eg, a peripheral device coupled via USB).

[0162] In addition, the communication component 1036 can detect the identifier or include a component that can be operated to detect the identifier. For example, the communication component 1036 can include a radio frequency identification (RFID) tag reader component, an NFC smart tag detection component, an optical reader component (e.g., an optical sensor for detecting one-dimensional bar codes such as universal product code (UPC) bar codes, multi-dimensional bar codes such as quick response (QR) codes, Aztec codes, data matrix, data symbol (Dataglyph), MaxiCode, PDF417, Ultra Code, UCC RSS-2D bar codes 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 1036, such as location via Internet Protocol (IP) geolocation, ... Signal triangulation to derive location, location via detection of NFC beacon signals that can indicate a specific location, etc.

[0163] Various memories (e.g., main memory 1012, static memory 1014, and memory of processor 1002) and storage unit 1016 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. When executed by processor 1002, these instructions (e.g., instructions 1008) cause various operations to implement the disclosed examples.

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

[0165] Software Architecture

[0166] Fig.111100 is a block diagram illustrating a software architecture 1104 that may be installed on any one or more of the devices described herein. The software architecture 1104 is supported by hardware, such as a machine 1102 including a processor 1120, a memory 1126, and an I / O component 1138. In this example, the software architecture 1104 may be conceptualized as a stack of layers, each of which provides specific functionality. The software architecture 1104 includes layers such as an operating system 1112, a library 1110, a framework 1108, and an application 1106. In operation, the application 1106 invokes an API call 1150 through the software stack and receives a message 1152 in response to the API call 1150.

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

[0168] The libraries 1110 provide a common low-level infrastructure used by the applications 1106. The libraries 1110 may include a system library 1118 (e.g., a C standard library) that provides functions such as memory allocation functions, string manipulation functions, mathematical functions, etc. In addition, the libraries 1110 may include an API library 1124, such as a media library (e.g., a library for supporting the 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 presenting in two dimensions (2D) and three dimensions (3D) in graphical 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 1110 may also include various other libraries 1128 to provide many other APIs to the application 1106 .

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

[0170] In an example, applications 1106 may include a home application 1136, a contacts application 1130, a browser application 1132, a book reader application 1134, a location application 1142, a media application 1144, a messaging application 1146, a game application 1148, and a variety of other applications such as external applications 1140. Applications 1106 are programs that perform functions defined in the program. Various programming languages ​​may be used to create one or more of the applications 1106 structured 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 or assembly language). In a specific example, external applications 1140 (e.g., those created by an entity other than the vendor of a particular platform using ANDROID TM or IOS TM Software Development Kit (SDK) can be used to develop applications for mobile operating systems such as IOS TM ANDROID TM , Phone, or another mobile operating system running on the mobile software. In this example, the external application 1140 can activate the API call 1150 provided by the operating system 1112 to facilitate the functions described herein.

[0171] Glossary

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

[0173] "Client Device" refers to any machine that interfaces with a communications 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, a desktop computer, a laptop computer, a portable digital assistant (PDA), a smart phone, a tablet computer, an ultrabook, a netbook, a laptop computer, a multiprocessor system, a microprocessor-based or programmable consumer electronics product, a game console, a set-top box, or any other communications device that a user may use to access a network.

[0174] "Communications Network" means one or more parts of a network, which may be an ad hoc network, an intranet, an extranet, a virtual private network (VPN), a local area network (LAN), a wireless LAN (WLAN), a wide area network (WAN), a wireless WAN (WWAN), a metropolitan area network (MAN), the Internet, a part of the Internet, a part of the Public Switched Telephone Network (PSTN), a Plain Old Telephone Service (POTS) network, a cellular telephone network, a wireless network, A network, other type of network, or a combination of two or more such networks. For example, the network or a portion of the network may include a wireless network or a cellular network, and the coupling may be a code division multiple access (CDMA) connection, a global system for mobile communications (GSM) connection, or other type of cellular or wireless coupling. In this example, the coupling may implement any of various types of data transmission technologies, such as single carrier radio transmission technology (1xRTT), evolution data optimized (EVDO) technology, general packet radio service (GPRS) technology, enhanced data 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.

[0175] "Component" means a device, physical entity, or logic having boundaries defined by function or subroutine calls, branch points, APIs, or other techniques that provide partitioning or modularization of specific processing or control functions. Components may interface with other components via their interfaces to perform machine processes. A component may be a packaged functional hardware unit designed for use with other components and is part of a program that typically performs a specific one of the related functions.

[0176] Components may constitute software components (e.g., code implemented on a machine-readable medium) or hardware components. A "hardware component" is a tangible unit that is capable of performing certain operations and that can be configured or arranged in some physical manner. In various examples, one or more computer systems (e.g., stand-alone computer systems, client computer systems, or server computer systems) or one or more hardware components of a computer system (e.g., a processor or group of processors) may be configured by software (e.g., an application or application portion) as hardware components that operate to perform certain operations described herein.

[0177] 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. A hardware component may be a dedicated processor, such as a field programmable gate array (FPGA) or an application specific integrated circuit (ASIC). A hardware component may also include a programmable logic or circuit system that is temporarily configured to perform certain operations by software. For example, a 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 implement the hardware component mechanically in a dedicated and permanently configured circuit system or in a temporarily configured (e.g., configured by software) circuit system. 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.

[0178] Consider an example where hardware components are temporarily configured (e.g., programmed), without configuring or instantiating each of the hardware components at any one time. For example, where the hardware components include a general-purpose processor that is configured by software to become a special-purpose processor, the general-purpose processor can be configured as different special-purpose processors (e.g., including different hardware components) at different times. The software configures one or more specific processors accordingly, for example, to constitute a specific hardware component at one time and to constitute different hardware components at different times.

[0179] 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 simultaneously, communication can be realized by signal transmission (e.g., by appropriate circuits and buses) between or among two or more hardware components in the hardware components. In the example where multiple hardware components are configured or instantiated at different times, communication between such hardware components can be realized, 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 store the output of the operation in a memory device communicatively coupled thereto. Then, other hardware components can access the memory device at a subsequent time to retrieve the stored output and process it. Hardware components can also initiate communication with input devices or output devices, and can operate resources (e.g., a collection of information).

[0180] The various operations of the example methods described herein may 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 temporarily or permanently configured, such a processor may constitute a processor-implemented component that operates to perform one or more operations or functions described herein. As used herein, a "processor-implemented component" refers to a hardware component implemented using one or more processors. Similarly, the method described herein may be implemented at least in part by a processor, wherein a specific one or more processors are examples of hardware. For example, at least some operations of the method may be performed by one or more processors 1002 or a processor-implemented component. In addition, one or more processors may 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 may be performed by a group of computers (as an example of a machine including a processor), wherein these operations may be accessed via a network (e.g., the Internet) and via one or more appropriate interfaces (e.g., API). The execution of certain operations may be distributed among processors, not just residing in a single machine, but deployed across several machines. In some examples, the processor or processor-implemented components may be located in a single geographic location (e.g., in a home environment, an office environment, or a server farm). In other examples, the processor or processor-implemented components may be distributed across several geographic locations.

[0181] "Computer-readable storage media" refers to both machine storage media and transmission media. Thus, the term includes 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.

[0182] "Transient message" refers to a message that is accessible for a limited duration. Transient messages can be text, images, videos, etc. The access time of a transient message can be set by the sender of the message. 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.

[0183] “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.”

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

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

[0186] Changes and modifications may be made to the disclosed examples without departing from the scope of the present disclosure. These and other changes or modifications are intended to be included within the scope of the present disclosure as expressed in the appended claims.

Claims

1. A method comprising: receiving a request from a client device to access an augmented reality (AR) experience; accessing a list of event types associated with the AR experience for generating one or more metrics, the list of event types comprising one or more event types configured by a developer of the AR experience; Determining that an interaction associated with the AR experience corresponds to a first event type in the list of event types; generating interaction data representing the interaction for the first event type; Receiving a request to terminate the AR experience; as well as In response to receiving the request to terminate the AR experience, the interaction data is sent to a remote server.

2. The method according to claim 1, further comprising: In response to determining that the interaction corresponds to the first event type, aggregating the interaction into an entity associated with the first event type; as well as The entity is stored as part of the interaction data.

3. The method according to claim 2, wherein: Aggregating the interaction includes accumulating the interaction with one or more previous interactions associated with the first event type.

4. The method according to claim 3, further comprising: One or more statistical functions are applied to the accumulated interactions associated with the first event type to generate the interaction data.

5. The method according to claim 1, wherein: The interaction is a first interaction, and wherein the interaction data includes first interaction data, the method further comprising: determining that a second interaction associated with the AR experience corresponds to a second event type in the list of event types; and Second interaction data representing the second interaction for the second event type is generated.

6. The method according to claim 5, further comprising: tracking the first interaction and the second interaction using the first interaction data and the second interaction data, respectively; as well as In response to receiving the request to terminate the AR experience, a message including the first interaction data and the second interaction data is generated, and the message is sent to the remote server.

7. The method according to claim 6, further comprising: The first interaction data and the second interaction data are presented to the developer of the AR experience by: Obtaining a mapping that associates a list of generic events with a list of custom events for the AR experience; Determining that the first event type of the first interaction data corresponds to a first general event in the list of general events; Determining that the second event type of the second interaction data corresponds to a second general event in the list of general events; as well as A graphical user interface is generated based on the mapping that visually depicts the first interaction data and the second interaction data in association with a custom event of the AR experience.

8. The method according to claim 7, further comprising: Identifying a first custom event corresponding to the first general event; Identifying a second custom event corresponding to the second general event; as well as The first custom event and the second custom event are visually depicted in the graphical user interface in association with the first interaction data and the second interaction data.

9. The method according to claim 1, wherein: The interaction data represents an average or total count of the first event type.

10. The method according to claim 9, wherein: The average or total count corresponds to interactions associated with the first event type performed on the client device and on other client devices.

11. The method according to claim 1, wherein: The first event type is triggered in response to determining that a designated camera view is activated during the AR experience.

12. The method according to claim 11, wherein: The specified camera view includes at least one of: a front camera view, a rear camera view, or a specified real-world object detected in a captured image.

13. The method according to claim 1, wherein: The AR experience is developed using an AR developer platform that includes a graphical user interface for enabling selection of event types to trigger interaction data tracking.

14. The method according to claim 13, wherein: The graphical user interface comprises: a list of AR events associated with the AR experience, the graphical user interface comprising a first option associated with a first AR event in the list of AR events, the first option causing an interaction corresponding to the first AR event to be tracked in response to selecting the first option, the graphical user interface comprising a second option associated with the first AR event for specifying one or more conditions for triggering the first AR event.

15. The method according to claim 14, wherein: The graphical user interface includes a third option for specifying a custom name for the first AR event.

16. The method according to claim 1, wherein: The list of event types is a first list of event types, and the AR experience is a first AR experience, the method further comprising: receiving a request from the client device to access a second AR experience; accessing a second list of event types associated with the second AR experience for generating a set of metrics, the second list of event types comprising one or more event types configured by a developer of the second AR experience; determining that an interaction associated with the second AR experience corresponds to a second event type in the second list of event types; generating interaction data representing the interaction for the second event type; and The interaction data is sent to the remote server.

17. The method according to claim 16, wherein: The first list of event types includes one or more event types that are different from the second list of event types, such that the first list of event types includes the one or more event types that are excluded from the second list of event types.

18. A system comprising: processor; as well as A memory component having instructions stored thereon, wherein when the instructions are executed by the processor, the processor performs operations, the operations comprising: receiving a request from a client device to access an augmented reality (AR) experience; accessing a list of event types associated with the AR experience for generating one or more metrics, the list of event types comprising one or more event types configured by a developer of the AR experience; Determining that an interaction associated with the AR experience corresponds to a first event type in the list of event types; generating interaction data representing the interaction for the first event type; Receiving a request to terminate the AR experience; and In response to receiving the request to terminate the AR experience, the interaction data is sent to a remote server.

19. The system of claim 16, the operations further comprising: In response to determining that the interaction corresponds to the first event type, aggregating the interaction into an entity associated with the first event type; as well as The entity is stored as part of the interaction data.

20. A non-transitory computer-readable storage medium having stored thereon instructions, the instructions, when executed by a processor, causing the processor to perform operations comprising: receiving a request from a client device to access an augmented reality (AR) experience; accessing a list of event types associated with the AR experience for generating one or more metrics, the list of event types comprising one or more event types configured by a developer of the AR experience; Determining that an interaction associated with the AR experience corresponds to a first event type in the list of event types; generating interaction data representing the interaction for the first event type; Receiving a request to terminate the AR experience; as well as In response to receiving the request to terminate the AR experience, the interaction data is sent to a remote server.

Images