Patent Grant
12136160
The present disclosure relates generally to providing augmented reality experiences using a messaging application.
Augmented Reality (AR) is a modification of a virtual environment. For example, in Virtual Reality (VR), a user is completely immersed in a virtual world, whereas in AR, the user is immersed in a world where virtual objects are combined or superimposed on the real world. An AR system aims to generate and present virtual objects that interact realistically with a real-world environment and with each other. Examples of AR applications can include single or multiple player video games, instant messaging systems, and the like.
In the drawings, which are not necessarily drawn to scale, like numerals may describe similar components in different views. To easily identify the discussion of any particular element or act, the most significant digit or digits in a reference number refer to the figure number in which that element is first introduced. Some nonlimiting examples are illustrated in the figures of the accompanying drawings in which:
The description that follows includes systems, methods, techniques, instruction sequences, and computing machine program products that embody illustrative examples of the disclosure. In the following description, for the purposes of explanation, numerous specific details are set forth in order to provide an understanding of various examples. It will be evident, however, to those skilled in the art, that examples may be practiced without these specific details. In general, well-known instruction instances, protocols, structures, and techniques are not necessarily shown in detail.
Typical user devices are capable of running a wide variety of complex AR experiences ranging from music playback to complex depth and object tracking to rich graphics intensive experiences. Such AR experiences can be limited in terms of battery life due to a target device size and weight restrictions. The power consumed by these AR experiences largely depends on the complexity of the AR experiences that are being run. Typical systems may lack mechanisms for AR experience creators or consumers to determine how much power a given AR experience will consume on a given device. This can result in AR experiences that drain the batteries of the devices on which they execute very quickly, which takes away from the overall use and enjoyment of the AR experiences. This results in such AR experiences going unused and wasting system resources.
Some typical systems allow AR experience designers to run a given AR experience on a particular device to determine the overall power consumed by the AR experience. To do so, a specialized hardware circuit board is typically connected to the target device and to the hardware components of the target device to physically measure the voltage and/or current to obtain the accurate power measurement. These specialized hardware circuits can be expensive, difficult to use, and do not scale well for use by most AR experience developers.
The disclosed techniques improve the efficiency of using the electronic device by providing a machine learning technique (model) that can predict or estimate power consumption of a given AR experience that is to be executed on a target client device. This avoids the need for AR experience developers to use specialized hardware resources to measure the power consumption, reduces the overall cost, and expedites the development of AR experiences by allowing such AR experiences to be developed by a larger audience. In this way, the AR experience developers can modify operations of the AR experiences based on the estimated power consumption to operate at a target or threshold power consumption range. In some examples, the machine learning technique can be operated at run time on a given client device to inform or alert a user when a given AR experience is consuming or is going to consume an amount of power that exceeds a threshold. This allows the user of the given client device to select an option to automatically scale down the AR experience or turn OFF the AR experience to change its operations to reduce the overall power consumed.
As referred to herein, “power consumption” can refer to the amount of power consumed by an AR experience over a specified period of time. In such cases, the power consumption represents an average measure of power consumed over the specified period of time. In some examples, the power consumption can represent an instantaneous energy consumption at a particular point in time.
Specifically, the disclosed techniques access resource utilization data associated with execution of an AR experience. The disclosed techniques apply a machine learning technique (e.g., neural network) to the resource utilization data to estimate power consumption of the AR experience. The machine learning technique can be trained to establish a relationship between a plurality of training resource utilization data associated with training AR experiences and corresponding ground-truth power consumption of the training AR experiences. The disclosed techniques can adjust one or more operations of the AR experience to reduce power consumption based on the estimated power consumption of the AR experience. This improves the overall experience of the user in using the electronic device and reduces the overall amount of system resources needed to accomplish a task.
Networked Computing Environment
The client device 102 may operate as a standalone device or may be coupled (e.g., networked) to other machines. In a networked deployment, the client device 102 may operate in the capacity of a server machine or a client machine in a server-client network environment, or as a peer machine in a peer-to-peer (or distributed) network environment. The client device 102 may comprise, but not be 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 telephone, a smartphone, a mobile device, a wearable device (e.g., a smartwatch), 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 executing the disclosed operations. Further, while only a single client device 102 is illustrated, the term “client device” shall also be taken to include a collection of machines that individually or jointly execute the disclosed operations.
In some examples, the client device 102 can include AR glasses or an AR headset in which virtual content is displayed within lenses of the glasses while a user views a real-world environment through the lenses. For example, an image can be presented on a transparent display that allows a user to simultaneously view content presented on the display and real-world objects.
A messaging client 104 is able to communicate and exchange data with other messaging clients 104 and with the messaging server system 108 via the network 112. The data exchanged between messaging clients 104, and between a messaging client 104 and the messaging server system 108, includes functions (e.g., commands to invoke functions) as well as payload data (e.g., text, audio, video, or other multimedia data).
The messaging server system 108 provides server-side functionality via the network 112 to a particular messaging client 104. While certain functions of the messaging system 100 are described herein as being performed by either a messaging client 104 or by the messaging server system 108, the location of certain functionality either within the messaging client 104 or the messaging server system 108 may be a design choice. For example, it may be technically preferable to initially deploy certain technology and functionality within the messaging server system 108 but to later migrate this technology and functionality to the messaging client 104 where a client device 102 has sufficient processing capacity.
The messaging server system 108 supports various services and operations that are provided to the messaging client 104. Such operations include transmitting data to, receiving data from, and processing data generated by the messaging client 104. This data may include message content, client device information, geolocation information, media augmentation and overlays, message content persistence conditions, social network information, and live event information, as examples. Data exchanges within the messaging system 100 are invoked and controlled through functions available via user interfaces (UIs) of the messaging client 104.
Turning now specifically to the messaging server system 108, an API server 116 is coupled to, and provides a programmatic interface to, application servers 114. The application servers 114 are communicatively coupled to a database server 120, which facilitates access to a database 126 that stores data associated with messages processed by the application servers 114. Similarly, a web server 128 is coupled to the application servers 114 and provides web-based interfaces to the application servers 114. To this end, the web server 128 processes incoming network requests over the Hypertext Transfer Protocol (HTTP) and several other related protocols.
The API server 116 receives and transmits message data (e.g., commands and message payloads) between the client device 102 and the application servers 114. Specifically, the API server 116 provides a set of interfaces (e.g., routines and protocols) that can be called or queried by the messaging client 104 in order to invoke functionality of the application servers 114. The API server 116 exposes various functions supported by the application servers 114, including account registration; login functionality; the sending of messages, via the application servers 114, from a particular messaging client 104 to another messaging client 104; the sending of media files (e.g., images or video) from a messaging client 104 to a messaging server 118, and for possible access by another messaging client 104; the settings of a collection of media data (e.g., story); the retrieval of a list of friends of a user of a client device 102; the retrieval of such collections; the retrieval of messages and content; the addition and deletion of entities (e.g., friends) to an entity graph (e.g., a social graph); the location of friends within a social graph; and opening an application event (e.g., relating to the messaging client 104).
The application servers 114 host a number of 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 a number of message processing technologies and functions, particularly related to the aggregation and other processing of content (e.g., textual and multimedia content) included in messages received from multiple instances of the messaging client 104. As will be described in further detail, the text and media content from multiple sources may be aggregated into collections of content (e.g., called stories or galleries). These collections are then made available to the messaging client 104. Other processor- and memory-intensive processing of data may also be performed server-side by the messaging server 118, in view of the hardware requirements for such processing.
The application servers 114 include an image processing server 122 that is dedicated to performing various image processing operations, typically with respect to images or video within the payload of a message sent from or received at the messaging server 118.
Image processing server 122 is used to implement scan functionality of the augmentation system 208 (shown in
The social network server 124 supports various social networking functions and services and makes these functions and services available to the messaging server 118. To this end, the social network server 124 maintains and accesses an entity graph 308 (as shown in
Returning to the messaging client 104, features and functions of an external resource (e.g., a third-party application 109 or applet) are made available to a user via an interface of the messaging client 104. The messaging client 104 receives a user selection of an option to launch or access features of an external resource (e.g., a third-party resource), such as external apps 109. The external resource may be a third-party application (external apps 109) installed on the client device 102 (e.g., a “native app”), or a small-scale version of the third-party application (e.g., an “applet”) that is hosted on the client device 102 or remote of the client device 102 (e.g., on third-party servers 110). The small-scale version of the third-party application includes a subset of features and functions of the third-party application (e.g., the full-scale, native version of the 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., an “applet”) is a web-based, markup-language version of the third-party application and is embedded in the messaging client 104. In addition to using markup-language documents (e.g., a .*ml file), an applet may incorporate a scripting language (e.g., a .*js file or a .json file) and a style sheet (e.g., a .*ss file).
In response to receiving a user selection of the option to launch or access features of the external resource (external app 109), the messaging client 104 determines whether the selected external resource is a web-based external resource or a locally-installed external application. In some cases, external applications 109 that are locally installed on the client device 102 can be launched independently of and separately from the messaging client 104, such as by selecting an icon, corresponding to the external application 109, on a home screen of the client device 102. Small-scale versions of such external applications can be launched or accessed via the messaging client 104 and, in some examples, no or limited portions of the small-scale external application can be accessed outside of the messaging client 104. The small-scale external application can be launched by the messaging client 104 receiving, from an external app(s) server 110, a markup-language document associated with the small-scale external application and processing such a document.
In response to determining that the external resource is a locally-installed external application 109, the messaging client 104 instructs the client device 102 to launch the external application 109 by executing locally-stored code corresponding to the external application 109. In response to determining that the external resource is a web-based resource, the messaging client 104 communicates with the external app(s) servers 110 to obtain a markup-language document corresponding to the selected resource. The messaging client 104 then processes the obtained markup-language document to present the web-based external resource within a user interface of the messaging client 104.
The messaging client 104 can notify a user of the client device 102, or other users related to such a user (e.g., “friends”), of activity taking place in one or more external resources. For example, the messaging client 104 can provide participants in a conversation (e.g., a chat session) in the messaging client 104 with notifications relating to the current or recent use of an external resource by one or more members of a group of users. One or more users can be invited to join in an active external resource or to launch a recently-used but currently inactive (in the group of friends) external resource. The external resource can provide participants in a conversation, each using a respective messaging client 104, with the ability to share an item, status, state, or location in an external resource with one or more members of a group of users into a chat session. The shared item may be an interactive chat card with which members of the chat can interact, for example, to launch the corresponding external resource, view specific information within the external resource, or take the member of the chat to a specific location or state within the external resource. Within a given external resource, response messages can be sent to users on the messaging client 104. The external resource can selectively include different media items in the responses, based on a current context of the external resource.
The messaging client 104 can present a list of the available external resources (e.g., third-party or external applications 109 or applets) to a user to launch or access a given external resource. This list can be presented in a context-sensitive menu. For example, the icons representing different ones of the external application 109 (or applets) can vary based on how the menu is launched by the user (e.g., from a conversation interface or from a non-conversation interface).
System Architecture
The ephemeral timer system 202 is responsible for enforcing the temporary or time-limited access to content by the messaging client 104 and the messaging server 118. The ephemeral timer system 202 incorporates a number of timers that, based on duration and display parameters associated with a message, or collection of messages (e.g., a story), selectively enable access (e.g., for presentation and display) to messages and associated content via the messaging client 104. Further details regarding the operation of the ephemeral timer system 202 are provided below.
The collection management system 204 is responsible for managing sets or collections of media (e.g., collections of text, image, video, and audio data). A collection of content (e.g., messages, including images, video, text, and audio) may be organized into an “event gallery” or an “event story.” Such a collection may be made available for a specified time period, such as the duration of an event to which the content relates. For example, content relating to a music concert may be made available as a “story” for the duration of that music concert. The collection management system 204 may also be responsible for publishing an icon that provides notification of the existence of a particular collection to the user interface of the messaging client 104.
The collection management system 204 further includes a curation interface 206 that allows a collection manager to manage and curate a particular collection of content. For example, the curation interface 206 enables an event organizer to curate a collection of content relating to a specific event (e.g., delete inappropriate content or redundant messages). Additionally, the collection management system 204 employs machine vision (or image recognition technology) and content rules to automatically curate a content collection. In certain examples, compensation may be paid to a user for the inclusion of user-generated content into a collection. In such cases, the collection management system 204 operates to automatically make payments to such users for the use of their content.
The augmentation system 208 provides various functions that enable a user to augment (e.g., annotate or otherwise modify or edit) media content associated with a message. For example, the augmentation system 208 provides functions related to the generation and publishing of media overlays for messages processed by the messaging system 100. The augmentation system 208 operatively supplies a media overlay or augmentation (e.g., an image filter) to the messaging client 104 based on a geolocation of the client device 102. In another example, the augmentation system 208 operatively supplies a media overlay to the messaging client 104 based on other information, such as social network information of the user of the client device 102. A media overlay may include audio and visual content and visual effects. Examples of audio and visual content include pictures, texts, logos, animations, and sound effects. An example of a visual effect includes color overlaying. The audio and visual content or the visual effects can be applied to a media content item (e.g., a photo) at the client device 102. For example, the media overlay may include text, a graphical element, or an image that can be overlaid on top of a photograph taken by the client device 102. In another example, the media overlay includes an identification of a location overlay (e.g., Venice beach), a name of a live event, or a name of a merchant overlay (e.g., Beach Coffee House). In another example, the augmentation system 208 uses the geolocation of the client device 102 to identify a media overlay that includes the name of a merchant at the geolocation of the client device 102. The media overlay may include other indicia associated with the merchant. The media overlays may be stored in the database 126 and accessed through the database server 120.
In some examples, the augmentation system 208 provides a user-based publication platform that enables users to select a geolocation on a map and upload content associated with the selected geolocation. The user may also specify circumstances under which a particular media overlay should be offered to other users. The augmentation system 208 generates a media overlay that includes the uploaded content and associates the uploaded content with the selected geolocation.
In other examples, the augmentation system 208 provides a merchant-based publication platform that enables merchants to select a particular media overlay associated with a geolocation via a bidding process. For example, the augmentation system 208 associates the media overlay of the highest bidding merchant with a corresponding geolocation for a predefined amount of time. The augmentation system 208 communicates with the image processing server 122 to obtain AR experiences and presents identifiers of such experiences in one or more user interfaces (e.g., as icons over a real-time image or video or as thumbnails or icons in interfaces dedicated for presented identifiers of AR experiences). Once an AR experience is selected, one or more images, videos, or AR graphical elements are retrieved and presented as an overlay on top of the images or video captured by the client device 102. In some cases, the camera is switched to a front-facing view (e.g., the front-facing camera of the client device 102 is activated in response to activation of a particular AR experience) and the images from the front-facing camera of the client device 102 start being displayed on the client device 102 instead of the rear-facing camera of the client device 102. The one or more images, videos, or AR graphical elements are retrieved and presented as an overlay on top of the images that are captured and displayed by the front-facing camera of the client device 102.
In other examples, the augmentation system 208 is able to communicate and exchange data with another augmentation system 208 on another client device 102 and with the server via the network 112. The data exchanged can include a session identifier that identifies 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 include the first and second devices) that is used to align the shared AR session to a common point of origin, a common coordinate frame, functions (e.g., commands to invoke functions) as well as other payload data (e.g., text, audio, video or other multimedia data).
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 and second client devices 102 synch up their coordinate systems and frames for displaying content in the AR session. Specifically, the augmentation system 208 computes the point of 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 position of the point of origin from the perspective of the second client device 102 in the coordinate system of the second client device 102. This offset is used to generate the transformation so that the second client device 102 generates AR content according to a common coordinate system or frame as the first client device 102.
The augmentation system 208 can communicate with the client device 102 to establish individual or shared AR sessions. 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) for the client devices 102 in a shared AR session. The electronic group communication session can be associated with a session identifier provided by the client devices 102 to gain access to the electronic group communication session and to the shared AR session. In some examples, the client devices 102 first gain access to the electronic group communication session and then obtain the session identifier in the electronic group communication session that allows the client devices 102 to access the shared AR session. In some examples, the client devices 102 are able to access the shared AR session without aid or communication with the augmentation system 208 in the application servers 114.
The map system 210 provides various geographic location functions and supports the presentation of map-based media content and messages by the messaging client 104. For example, the map system 210 enables the display of user icons or avatars (e.g., stored in profile data 316) on a map to indicate a current or past location of “friends” of a user, as well as media content (e.g., collections of messages including photographs and videos) generated by such friends, within the context of a map. For example, a message posted by a user to the messaging system 100 from a specific geographic location may be displayed within the context of a map at that particular location to “friends” of a specific user on a map interface of the messaging client 104. A user can furthermore share his or her location and status information (e.g., using an appropriate status avatar) with other users of the messaging system 100 via the messaging client 104, with this location and status information being similarly displayed within the context of a map interface of the messaging client 104 to selected users.
The game system 212 provides various gaming functions within the context of the messaging client 104. The messaging client 104 provides a game interface providing 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 messaging client 104 and played with other users of the messaging system 100. The messaging system 100 further enables a particular user to invite other users to participate in the play of a specific game, by issuing invitations to such other users from the messaging client 104. The messaging client 104 also supports both voice and text messaging (e.g., chats) within the context of gameplay, provides a leaderboard for the games, and also supports the provision of in-game rewards (e.g., coins and items).
The external resource system 220 provides an interface for the messaging client 104 to communicate with external app(s) servers 110 to launch or access external resources. Each external resource (apps) server 110 hosts, for example, a markup language (e.g., HTML5) based application or small-scale version of an external application (e.g., game, utility, payment, or ride-sharing application that is external to the messaging client 104). The messaging client 104 may launch a web-based resource (e.g., application) by accessing the HTML5 file from the external resource (apps) servers 110 associated with the web-based resource. In certain examples, applications hosted by external resource servers 110 are programmed in JavaScript leveraging a Software Development Kit (SDK) provided by the messaging server 118. The SDK includes APIs with functions that can be called or invoked by the web-based application. In certain examples, the messaging server 118 includes a JavaScript library that provides a given third-party resource access to certain user data of the messaging client 104. HTML5 is used as an example technology for programming games, but applications and resources programmed based on other technologies can be used.
In order to integrate the functions of the SDK into the web-based resource, the SDK is downloaded by an external resource (apps) server 110 from the messaging server 118 or is otherwise received by the external resource (apps) server 110. Once downloaded or received, the SDK is included as part of the application code of a web-based external resource. The code of the web-based resource can then call or invoke certain functions of the SDK to integrate features of the messaging client 104 into the web-based resource.
The SDK stored on the messaging server 118 effectively provides the bridge between an external resource (e.g., third-party or external applications 109 or applets and the messaging client 104). This provides the user with a seamless experience of communicating with other users on the messaging client 104, while also preserving the look and feel of the messaging client 104. To bridge communications between an external resource and a messaging client 104, in certain examples, the SDK facilitates communication between external resource servers 110 and the messaging client 104. In certain examples, a WebViewJavaScriptBridge running on a client device 102 establishes two one-way communication channels between a external resource and the messaging client 104. Messages are sent between the external resource and the messaging client 104 via these communication channels asynchronously. Each SDK function invocation is sent as a message and callback. Each SDK function is implemented by constructing a unique callback identifier and sending a message with that callback identifier.
By using the SDK, not all information from the messaging client 104 is shared with external resource servers 110. The SDK limits which information is shared based on the needs of the external resource. In certain examples, each external resource server 110 provides an HTML5 file corresponding to the web-based external resource to the messaging server 118. The messaging server 118 can add a visual representation (such as a box art or other graphic) of the web-based external resource in the messaging client 104. Once the user selects the visual representation or instructs the messaging client 104 through a graphical user interface (GUI) of the messaging client 104 to access features of the web-based external resource, the messaging client 104 obtains the HTML5 file and instantiates the resources necessary to access the features of the web-based external resource.
The messaging client 104 presents a GUI (e.g., a landing page or title screen) for an external resource. During, before, or after presenting the landing page or title screen, the messaging client 104 determines whether the launched external resource has been previously authorized to access user data of the messaging client 104. In response to determining that the launched external resource has been previously authorized to access user data of the messaging client 104, the messaging client 104 presents another GUI of the external resource that includes functions and features of the external resource. In response to determining that the launched external resource has not been previously authorized to access user data of the messaging client 104, after a threshold period of time (e.g., 3 seconds) of displaying the landing page or title screen of the external resource, the messaging client 104 slides up (e.g., animates a menu as surfacing from a bottom of the screen to a middle of or other portion of the screen) a menu for authorizing the external resource to access the user data. The menu identifies the type of user data that the external resource will be authorized to use. In response to receiving a user selection of an accept option, the messaging client 104 adds the external resource to a list of authorized external resources and allows the external resource to access user data from the messaging client 104. In some examples, the external resource is authorized by the messaging client 104 to access the user data in accordance with an OAuth 2 framework.
The messaging client 104 controls the type of user data that is shared with external resources based on the type of external resource being authorized. For example, external resources that include full-scale external applications (e.g., a third-party or external application 109) are provided with access to a first type of user data (e.g., only two-dimensional (2D) avatars of users with or without different avatar characteristics). As another example, external resources that include small-scale versions of external applications (e.g., web-based versions of third-party applications) are provided with access to a second type of user data (e.g., payment information, 2D avatars of users, three-dimensional (3D) avatars of users, and avatars with various avatar characteristics). Avatar characteristics include different ways to customize a look and feel of an avatar, such as different poses, facial features, clothing, and so forth.
A power estimation system 224 can be used by a developer of an AR experience or an end user of the AR experience on a messaging client 104. The power estimation system 224 can apply one or more resource utilization parameters or data (e.g., hardware resource consumption information) to a machine learning technique to estimate power consumption of a given AR experience.
In case of a developer, the power estimation system 224 can receive a selection of an AR experience and can access one or more resource utilization parameters or data associated with running or executing the AR experience on a specified type of device (e.g., a mobile phone or wearable headset or AR glasses). The power estimation system 224 applies the resource utilization parameters to a machine learning technique (e.g., a trained neural network) to estimate power consumption of the AR experience. The estimated power consumption can be presented to the developer and input can be received from the developer changing one or more operations of the AR experience to modify (increase or decrease) the power consumption.
In the case of an end user, a selection of an AR experience can be received from the messaging client 104. The AR experience can be executed by the messaging client 104 and the power estimation system 224 can use a trained machine learning technique to collect and/or access resource utilization data associated with executing the AR experience to estimate power consumption of the AR experience. The power estimation system 224 can present the estimated power consumption to the user of the messaging client 104. Input can be received from the messaging client 104 selecting an alternate version of the AR experience that is associated with lower or greater power consumption (e.g., the AR experience can be changed from presenting 3D virtual objects to presenting 2D virtual objects).
Data Architecture
The database 126 includes message data stored within a message table 302. This message data includes, for any particular one message, at least message sender data, message recipient (or receiver) data, and a payload. Further details regarding information that may be included in a message, and included within the message data stored in the message table 302, are described below with reference to
An entity table 306 stores entity data, and is linked (e.g., referentially) to an entity graph 308 and profile data 316. Entities for which records are maintained within the entity table 306 may include individuals, corporate entities, organizations, objects, places, events, and so forth. Regardless of entity type, any entity regarding which the messaging server system 108 stores data may be a recognized entity. Each entity is provided with a unique identifier, as well as an entity type identifier (not shown).
The entity graph 308 stores information regarding relationships and associations between entities. Such relationships may be social, professional (e.g., work at a common corporation or organization) interested-based, or activity-based, merely for example.
The profile data 316 stores multiple types of profile data about a particular entity. The profile data 316 may be selectively used and presented to other users of the messaging system 100, based on privacy settings specified by a particular entity. Where the entity is an individual, the profile data 316 includes, for example, a user name, telephone number, address, settings (e.g., notification and privacy settings), as well as a user-selected avatar representation (or collection of such avatar representations). A particular user may then selectively include one or more of these avatar representations within the content of messages communicated via the messaging system 100, and on map interfaces displayed by messaging clients 104 to other users. The collection of avatar representations may include “status avatars,” which present a graphical representation of a status or activity that the user may select to communicate at a particular time.
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 (e.g., notifications) for the relevant group.
The database 126 also stores augmentation data, such as overlays or filters, in an augmentation table 310. The augmentation data is associated with and applied to videos (for which data is stored in a video table 304) and images (for which data is stored in an image table 312).
The database 126 can also store data pertaining to individual and shared AR sessions. This data can include data communicated 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 communicated between the AR session client controller and the augmentation system 208. Data can include data used to establish the common coordinate frame of the shared AR scene, the transformation between the devices, the session identifier, images depicting a body, skeletal joint positions, wrist joint positions, feet, and so forth.
Filters, in one example, are overlays that are displayed as overlaid on an image or video during presentation to a recipient user. Filters may be of various types, including user-selected filters from a set of filters presented to a sending user by the messaging client 104 when the sending user is composing a message. Other types of filters include geolocation filters (also known as geo-filters), which may be presented to a sending user based on geographic location. For example, geolocation filters specific to a neighborhood or special location may be presented within a user interface by the messaging client 104, based on geolocation information determined by a Global Positioning System (GPS) unit of the client device 102.
Another type of filter is a data filter, which may be selectively presented to a sending user by the messaging client 104 based on other inputs or information gathered by the client device 102 during the message creation process. Examples of data filters include current temperature at a specific location, a current speed at which a sending user is traveling, battery life for a client device 102, or the current time.
Other augmentation data that may be stored within the image table 312 includes AR content items (e.g., corresponding to applying AR experiences). An AR content item or AR item may be a real-time special effect and sound that may be added to an image or a video.
As described above, augmentation data includes AR content items, overlays, image transformations, AR images, AR logos or emblems, and similar terms that refer to modifications that may be applied to image data (e.g., videos or images). This includes real-time modifications, which modify an image as it is captured using device sensors (e.g., one or multiple cameras) of a client device 102 and then displayed on a screen of the client device 102 with the modifications. This also includes modifications to stored content, such as video clips in a gallery that may be modified. For example, in a client device 102 with access to multiple AR content items, a user can use a single video clip with multiple AR content items to see how the different AR content items will modify the stored clip. For example, multiple AR content items that apply different pseudorandom movement models can be applied to the same content by selecting different AR content items for the content. Similarly, real-time video capture may be used with an illustrated modification to show how video images currently being captured by sensors of a client device 102 would modify the captured data. Such data may simply be displayed on the screen and not stored in memory, or the content captured by the device sensors may be recorded and stored in memory with or without the modifications (or both). In some systems, a preview feature can show how different AR content items will look within different windows in a display at the same time. This can, for example, enable multiple windows with different pseudorandom animations to be viewed on a display at the same time.
Data and various systems using AR content items or other such transform systems to modify content using this data can thus involve detection of objects (e.g., faces, hands, bodies, cats, dogs, surfaces, objects, etc.), tracking of such objects as they leave, enter, and move around the field of view in video frames, and the modification or transformation of such objects as they are tracked. In various examples, different methods for achieving such transformations may be used. Some examples may involve generating a 3D mesh model of the object or objects and using transformations and animated textures of the model within the video to achieve the transformation. In other examples, tracking of points on an object may be used to place an image or texture (which may be 2D or 3D) at the tracked position. In still further examples, neural network analysis of video frames may be used to place images, models, or textures in content (e.g., images or frames of video). AR content items thus refer both to the images, models, and textures used to create transformations in content, as well as to additional modeling and analysis information needed to achieve such transformations with object detection, tracking, and placement.
Real-time video processing can be performed with any kind of video data (e.g., video streams, video files, etc.) saved in a memory of a computerized system of any kind. For example, a user can load video files and save them in a memory of a device or can generate a video stream using sensors of the device. Additionally, any objects can be processed using a computer animation model, such as a human's face and parts of a human body, animals, or non-living things such as chairs, cars, or other objects.
In some examples, when a particular modification is selected along with content to be transformed, elements to be transformed are identified by the computing device and then detected and tracked if they are present in the frames of the video. The elements of the object are modified according to the request for modification, thus transforming the frames of the video stream. Transformation of frames of a video stream can be performed by different methods for different kinds of transformation. For example, for transformations of frames mostly referring to changing forms of an object's elements, characteristic points for each element of an object are calculated (e.g., using an Active Shape Model (ASM) or other known methods). Then, a mesh based on the characteristic points is generated for each of the at least one element of the object. This mesh is used in the following stage of tracking the elements of the object in the video stream. In the process of tracking, the mentioned mesh for each element is aligned with a position of each element. Then, additional points are generated on the mesh. A first set of first points is generated for each element based on a request for modification, and a set of second points is generated for each element based on the set of first points and the request for modification. Then, the frames of the video stream can be transformed by modifying the elements of the object on the basis of the sets of first and second points and the mesh. In such method, a background of the modified object can be changed or distorted as well by tracking and modifying the background.
In some examples, transformations changing some areas of an object using its elements can be performed by calculating characteristic points for each element of an object and generating a mesh based on the calculated characteristic points. Points are generated on the mesh and then various areas based on the points are generated. The elements of the object are then tracked by aligning the area for each element with a position for each of the at least one element, and properties of the areas can be modified based on the request for modification, thus transforming the frames of the video stream. Depending on the specific request for modification, properties of the mentioned areas can be transformed in different ways. Such modifications may involve changing color of areas; removing at least some part of areas from the frames of the video stream; including one or more new objects into areas which are based on a request for modification; and modifying or distorting the elements of an 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 can be selected as control points to be used in determining the entire state-space of options for the model animation.
In some examples of a computer animation model to transform image data using face detection, the face is detected on an image with use of a specific face detection algorithm (e.g., Viola-Jones). Then, an ASM algorithm is applied to the face region of an image to detect facial feature reference points.
Other methods and algorithms suitable for face detection can be used. For example, in some examples, features are located using a landmark, which represents a distinguishable point present in most of the images under consideration. For facial landmarks, for example, the location of the left eye pupil may be used. If an initial landmark is not identifiable (e.g., if a person has an eyepatch), secondary landmarks may be used. Such landmark identification procedures may be used for any such objects. In some examples, a set of landmarks forms a shape. Shapes can be represented as vectors using the coordinates of the points in the shape. One shape is aligned to another with a similarity transform (allowing translation, scaling, and rotation) that minimizes the average Euclidean distance between shape points. The mean shape is the mean of the aligned training shapes.
In some examples, a search is started for landmarks from the mean shape aligned to the position and size of the face determined by a global face detector. Such a search then repeats the steps of suggesting a tentative shape by adjusting the locations of shape points by template matching of the image texture around each point and then conforming the tentative shape to a global shape model until convergence occurs. In some systems, individual template matches are unreliable, and the shape model pools the results of the weak template matches to form a stronger overall classifier. The entire search is repeated at each level in an image pyramid, from coarse to fine resolution.
A transformation system can capture an image or video stream on a client device (e.g., the client device 102) and perform complex image manipulations locally on the client device 102 while maintaining a suitable user experience, computation time, and power consumption. The complex image manipulations may include size and shape changes, emotion transfers (e.g., changing a face from a frown to a smile), state transfers (e.g., aging a subject, reducing apparent age, changing gender), style transfers, graphical element application, and any other suitable image or video manipulation implemented by a convolutional neural network that has been configured to execute efficiently on the client device 102.
In some examples, a computer animation model to transform image data can be used by a system where a user may capture an image or video stream of the user (e.g., a selfie) using a client device 102 having a neural network operating as part of a messaging client 104 operating on the client device 102. The transformation system operating within the messaging client 104 determines the presence of a face within the image or video stream and provides modification icons associated with a computer animation model to transform image data, or the computer animation model can be present as associated with an interface described herein. The modification icons include changes that may be the basis for modifying the user's face within the image or video stream as part of the modification operation. Once a modification icon is selected, the transformation system initiates a process to convert the image of the user to reflect the selected modification icon (e.g., generate a smiling face on the user). A modified image or video stream may be presented in a GUI displayed on the client device 102 as soon as the image or video stream is captured and a specified modification is selected. The transformation system may implement a complex convolutional neural network on a portion of the image or video stream to generate and apply the selected modification. That is, the user may capture the image or video stream and be presented with a modified result in real-time or near real-time once a modification icon has been selected. Further, the modification may be persistent while the video stream is being captured, and the selected modification icon remains toggled. Machine-taught neural networks may be used to enable such modifications.
The GUI, presenting the modification performed by the transformation system, may supply the user with additional interaction options. Such options may be based on the interface used to initiate the content capture and selection of a particular computer animation model (e.g., initiation from a content creator user interface). In various examples, a modification may be persistent after an initial selection of a modification icon. The user may toggle 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 browse to other areas of the imaging application. Where multiple faces are modified by the transformation system, the user may toggle the modification on or off globally by tapping or selecting a single face modified and displayed within a GUI. In some examples, individual faces, among a group of multiple faces, may be individually modified, or such modifications may be individually toggled by tapping or selecting the individual face or a series of individual faces displayed within the GUI.
A story table 314 stores data regarding collections of messages and associated image, video, or audio data, which are compiled into a collection (e.g., a story or a gallery). The creation of a particular collection may be initiated by a particular user (e.g., each user for which a record is maintained in the entity table 306). A user may create a “personal story” in the form of a collection of content that has been created and sent/broadcast by that user. To this end, the user interface of the messaging client 104 may include an icon that is user-selectable to enable a sending user to add specific content to his or her personal story.
A collection may also constitute a “live story,” which is a collection of content from multiple users that is created manually, automatically, or using a combination of manual and automatic techniques. For example, a “live story” may constitute a curated stream of user-submitted content from various locations and events. Users whose client devices have location services enabled and are at a common location event at a particular time may, for example, be presented with an option, via a user interface of the messaging client 104, to contribute content to a particular live story. The live story may be identified to the user by the messaging client 104, based on his or her location. The end result is a “live story” told from a community perspective.
A further type of content collection is known as a “location story,” which enables a user whose client device 102 is located within a specific geographic location (e.g., on a college or university campus) to contribute to a particular collection. In some examples, a contribution to a location story may require a second degree of authentication to verify that the end user belongs to a specific organization or other entity (e.g., is a student on the university campus).
As mentioned above, the video table 304 stores video data that, in one example, is associated with messages for which records are maintained within the message table 302. Similarly, the image table 312 stores image data associated with messages for which message data is stored in the entity table 306. The entity table 306 may associate various augmentations from the augmentation table 310 with various images and videos stored in the image table 312 and the video table 304.
Trained machine learning technique(s) 307 stores parameters that have been trained during training of the power estimation system 224. For example, trained machine learning techniques 307 stores the trained parameters of one or more neural network machine learning techniques. The neural network machine learning techniques can be trained to establish a relationship between a plurality of training resource utilization data associated with execution of training AR experiences and corresponding ground-truth power consumption of the training AR experiences.
Training data 309 stores a plurality of training resource utilization data associated with execution of training AR experiences and corresponding ground-truth power consumption of the training AR experiences. This training data 309 can be used by the power estimation system 224 to train the machine learning technique used to estimate power consumption of a given AR experience.
Data Communications Architecture
The contents (e.g., values) of the various components of message 400 may be pointers to locations in tables within which content data values are stored. For example, an image value in the message image payload 406 may be a pointer to (or address of) a location within an image table 312. Similarly, values within the message video payload 408 may point to data stored within a video table 304, values stored within the message augmentation data 412 may point to data stored in an augmentation table 310, values stored within the message story identifier 418 may point to data stored in a story table 314, and values stored within the message sender identifier 422 and the message receiver identifier 424 may point to user records stored within an entity table 306.
Power Estimation System
During training, the power estimation system 224 receives a given training AR experience associated with a given set of resource utilization data from the training data 502, such as using the resource utilization data module 512. The power estimation system 224 applies one or more machine learning techniques using the power prediction module 514 to the given set of resource utilization data to estimate a power consumption of the given training AR experience. In some examples, the power prediction module 514 estimates the power consumption by classifying the estimated power consumption into one of a plurality of power bins. For example, the plurality of power bins can include a first power bin representing a first power range and a second power bin can represent a second power range. The plurality of power bins can include eight or more power bins. The power range covered by each power bin can be equal or unequal such that an entire power consumption range is covered by all of the power bins. In some examples, the power bins are each 500 mW (milliwatt) in width. A first power bin can range from 0 mW-500 mW; a second power bin can range from 501 mW-1000 mW; a third power bin can range from 1001 mW-1500 mW; a fourth power bin can range from 1501 mW-2000 mW; a fifth power bin can range from 2001 mW-2500 mW; a sixth power bin can range from 2501 mW-3000 mW; a seventh power bin can range from 3001 mW-3500 mW; an eighth power bin can range from 3501 mW-4000 mW; and a ninth power bin can cover power consumption greater than 4001 mW. Any other power bin classification can be provided.
The power prediction module 514 retrieves a ground-truth power consumption (or the power bin classification) of the given training AR experience from the training data 502. The power prediction module 514 compares the estimated power consumption (or power bin classification) with the ground-truth power consumption (or the power bin classification). Based on a difference threshold or deviation of the comparison, the power prediction module 514 updates one or more coefficients or parameters of the power prediction module 514. The power prediction module 514 can determine whether the difference threshold or deviation of the comparison satisfies a stopping criterion. In response to determining that the difference threshold or deviation of the comparison fails to satisfy the stopping criterion, the power prediction module 514 retrieves another training AR experience and associated resource utilization data to again estimate power consumption and update parameters of the power prediction module 514.
In response to determining that the difference threshold or deviation of the comparison satisfies the stopping criterion or after a specified number of epochs or batches of training data have been processed and/or when the difference threshold or deviation reaches a specified value, the power prediction module 514 completes training and the parameters and coefficients of the power prediction module 514 are stored in the trained machine learning technique(s) 307 (e.g., as the machine learning technique).
In some examples, the power prediction module 514 is trained to generate or estimate different power consumption values for different types of devices. In such cases, the power prediction module 514 can receive a type of device on which the given AR experience is executed and can provide the power consumption estimation for the type of device. The power prediction module 514 can retrieve the corresponding ground-truth power consumption information for the type of device to compute a deviation and update parameters of the power prediction module 514. In some cases, multiple neural networks can be trained, with each associated with a different type of target device. A first neural network can be trained to estimate power consumption of a given AR experience executing on a first type of device (e.g., a wearable device) and a second neural network can be trained to estimate power consumption of the same given AR experience executing on a second type of device (e.g., a mobile phone).
In some cases, the training data 502 is generated by accessing a given AR experience and running the AR experience on a target device of a particular type. The target device can be connected to an external power monitoring circuit or device. The external power monitoring circuit or device can periodically collect power consumption information. The target device can also collect resource utilization data associated with running or executing the AR experience. After a threshold period of time of running the AR experience, the power consumption measurements collected over the period of time are averaged and stored in association with the given AR experience and the collected resource utilization data. In this way, the power consumption represents the average power consumed by the AR experience. In other implementations, the maximum or minimum power consumption measurement can be stored in association with the given AR experience as the power consumption of the AR experience. This process repeats for multiple AR experiences and across many different types of target devices (e.g., desktop computers, mobile phones, mobile watches, wearable devices, and so forth).
After training, power estimation system 224 receives a selection of an AR experience, such as from a developer or an end user. For example, as shown in
The power estimation system 224 receives a user selection of a particular build from the AR experience build selection region 610. Then, the power estimation system 224 can receive a user selection of a target device type from the target device type selection region 620. For example, the target device type selection region 620 can list many different types of target devices (e.g., mobile phone, wearable headset, AR glasses, smartwatch, and so forth). In response to receiving the build selection of the AR experience and the target device selection, the power estimation system 224 can launch the build of the AR experience on the selected target device. In some examples, the power estimation system 224 can send, over a network, the build of the AR experience to a physical device associated with the selected device type. The physical device can execute the AR experience and can collect resource utilization data while the AR experience is being executed or running.
The resource utilization data that is collected can include graphics processing unit (GPU) performance counters of a GPU of a client device used to execute the AR experience, operations performed by one or more hardware resources, such as a central processing unit (CPU), a GPU, a volatile memory, a camera, a display, an encoder, and/or a non-volatile memory. The resource utilization data can include a quantity of arithmetic logic unit instructions that have been executed. The resource utilization data can include any combination of GPU average frequency, GPU utilization, number of busy cycles, number of working cycles, number of arithmetic logic unit (ALU) working cycles, number of stall cycles, and/or number of stage duration cycles or any other resource utilization metric representing hardware performance of a target device.
In some examples, the resource utilization data module 512 accesses internal counters of the target device while the AR experience is being executed to obtain the resource utilization data. In some cases, the physical device executing the AR experience provides the resource utilization data to the resource utilization data module 512. The resource utilization data module 512 provides the selected target device type and the collected resource utilization data to the power prediction module 514. The power prediction module 514 selects a neural network from a plurality of neural networks that was trained based on the selected target device type. The selected neural network is applied to the collected resource utilization data to estimate power consumption or to provide a power consumption classification. The estimated power consumption or power consumption classification is presented to the developer in an estimated power consumption region 630.
In some examples, the resource utilization data module 512 can process the resource utilization data to identify one or more operations of the AR experience that are associated with a large amount of resource utilization (e.g., an operation that resulted in a resource utilization counter value that exceeds a threshold). The resource utilization data module 512 can present the identified one or more operations in a list of suggested operations to change region 640.
The AR experience operation adjustment module 519 can receive input from the developer, via the list of suggested operations to change region 640, that removes or modifies the identified one or more operations. Any changes that are made can be stored as a new build of the AR experience or can modify the current build of the AR experience selected in the AR experience build selection region 610. For example, the list of suggested operations to change region 640 can specify a 3D virtual object that consumed an amount of resource utilization that exceeds a threshold. The list of suggested operations to change region 640 can receive input from the developer changing the 3D virtual object to a 2D virtual object to generate a revised build of the AR experience. The revised build of the AR experience can be launched again on the target physical device to obtain and display updated estimated power consumption in the estimated power consumption region 630.
In some examples, the power estimation system 224 is implemented on a client device 102, such as by a messaging client 104. In such cases, the power estimation system 224 receives a selection of an AR experience, such as from an end user. For example, as shown in
The power estimation system 224 can access internal counters of the client device 102 while the AR experience is being executed to obtain the resource utilization data. The power prediction module 514 selects a neural network from a plurality of neural networks that was trained based on the client device 102 type being used to execute the AR experience shown in
In response to the power estimation system 224 determining that the estimated power consumption or power consumption classification transgresses or exceeds the threshold power consumption value, the power estimation system 224 presents a notification 730. The notification 730 includes a textual message informing the user that the estimated power consumption of the AR experience currently being executed by the client device 102 exceeds a threshold value. The notification 730 can include a modify operations option 732. The modify operations option 732 allows the user to provide input to change one or more operations of the AR experience to reduce or increase power consumption of the AR experience.
In some examples, the AR experience operation adjustment module 519 can receive input from the user that selects the modify operations option 732. In response, the power estimation system 224 retrieves a different build of the AR experience that is associated with a lower power consumption value. Specifically, the client device 102 can store multiple builds of the same AR experience, with each associated with a different power consumption amount. The client device 102 can receive input from the user launching the AR experience and, in response, the power estimation system 224 accesses and launches the build associated with the greatest power consumption amount. After receiving input that selects the modify operations option 732, the power estimation system 224 accesses a second build of the same AR experience and launches the second build, which can be associated with a lower power consumption value. For example, as shown in
In some examples, the power estimation system 224 can again access internal counters of the client device 102 while the AR experience associated with the newly selected build is being executed to obtain the resource utilization data. A selected neural network is applied to the collected resource utilization data to estimate power consumption or to provide a power consumption classification. The estimated power consumption or power consumption classification is compared to the threshold power consumption value. In response to the power estimation system 224 determining that the estimated power consumption or power consumption classification fails to transgress or exceed the threshold power consumption value, the power estimation system 224 presents a notification 820 indicating that the power consumption estimation of the AR experience is below the threshold.
At operation 901, the power estimation system 224 (e.g., a client device 102 or a server) accesses resource utilization data associated with execution of an AR experience, as discussed above.
At operation 902, the power estimation system 224 applies a machine learning technique to the resource utilization data to estimate power consumption of the AR experience, the machine learning technique being trained to establish a relationship between a plurality of training resource utilization data associated with training AR experiences and corresponding ground-truth power consumption of the training AR experiences, as discussed above.
At operation 903, the power estimation system 224 adjusts one or more operations of the AR experience to reduce power consumption based on the estimated power consumption of the AR experience, as discussed above.
Machine Architecture
The machine 1000 may include processors 1002, memory 1004, and input/output (I/O) components 1038, which may be configured to communicate with each other via a bus 1040. In an example, the processors 1002 (e.g., a CPU, a Reduced Instruction Set Computing (RISC) Processor, a Complex Instruction Set Computing (CISC) Processor, a 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 and a processor 1010 that execute the instructions 1008. The term “processor” is intended to include multi-core processors that may comprise two or more independent processors (sometimes referred to as “cores”) that may execute instructions contemporaneously. Although
The memory 1004 includes a main memory 1012, a static memory 1014, and a storage unit 1016, all accessible to the processors 1002 via the bus 1040. The main memory 1004, the static memory 1014, and the storage unit 1016 store the instructions 1008 embodying 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 machine-readable medium 1018 within the storage unit 1016, within at least one of the processors 1002 (e.g., within the processor's cache memory), or any suitable combination thereof, during execution thereof by the machine 1000.
The I/O components 1038 may include a wide variety of components to receive input, provide output, produce output, transmit information, exchange information, capture measurements, and so on. The specific I/O components 1038 that are included in a particular machine will depend on the type of machine. For example, portable machines such as mobile phones may include a touch input device or other such input mechanisms, while a headless server machine will likely not include such a touch input device. It will be appreciated that the I/O components 1038 may include many other components that are not shown in
In further examples, the I/O components 1038 may include biometric components 1028, motion components 1030, environmental components 1032, or position components 1034, among a wide array of other components. For example, the biometric components 1028 include components to detect expressions (e.g., hand expressions, facial expressions, vocal expressions, body gestures, or eye-tracking), measure biosignals (e.g., blood pressure, heart rate, body temperature, perspiration, or brain waves), identify a person (e.g., voice identification, retinal identification, facial identification, fingerprint identification, or electroencephalogram-based identification), and the like. The motion components 1030 include acceleration sensor components (e.g., accelerometer), gravitation sensor components, rotation sensor components (e.g., gyroscope).
The environmental components 1032 include, for example, one or more cameras (with still image/photograph and video capabilities), illumination sensor components (e.g., photometer), temperature sensor components (e.g., one or more thermometers that detect ambient temperature), humidity sensor components, pressure sensor components (e.g., barometer), 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 to detection concentrations of hazardous gases for safety or to measure pollutants in the atmosphere), or other components that may provide indications, measurements, or signals corresponding to a surrounding physical environment.
With respect to cameras, the client device 102 may have a camera system comprising, for example, front cameras on a front surface of the client device 102 and rear cameras on a rear surface of the client device 102. The front cameras may, for example, be used to capture still images and video of a user of the client device 102 (e.g., “selfies”), which may then be augmented with augmentation data (e.g., filters) described above. The rear cameras may, for example, be used to capture still images and videos in a more traditional camera mode, with these images similarly being augmented with augmentation data. In addition to front and rear cameras, the client device 102 may also include a 360° camera for capturing 360° photographs and videos.
Further, the camera system of a client device 102 may include dual rear cameras (e.g., a primary camera as well as a depth-sensing camera), or even triple, quad, or penta rear camera configurations on the front and rear sides of the client device 102. These multiple cameras systems may include a wide camera, an ultra-wide camera, a telephoto camera, a macro camera, and a depth sensor, for example.
The position components 1034 may include location sensor components (e.g., a GPS receiver component), altitude sensor components (e.g., altimeters or barometers that detect air pressure from which altitude may be derived), orientation sensor components (e.g., magnetometers), and the like.
Communication may be implemented using a wide variety of technologies. The I/O components 1038 further include communication components 1036 operable to couple the machine 1000 to a network 1020 or devices 1022 via respective coupling or connections. For example, the communication components 1036 may include a network interface component or another suitable device to interface with the network 1020. In further examples, the communication components 1036 may include wired communication components, wireless communication components, cellular communication components, Near Field Communication (NFC) components, Bluetooth® components (e.g., Bluetooth® Low Energy), WiFi® components, and other communication components to provide communication via other modalities. The devices 1022 may be another machine or any of a wide variety of peripheral devices (e.g., a peripheral device coupled via a USB).
Moreover, the communication components 1036 may detect identifiers or include components operable to detect identifiers. For example, the communication components 1036 may include Radio Frequency Identification (RFID) tag reader components, NFC smart tag detection components, optical reader components (e.g., an optical sensor to detect one-dimensional bar codes such as Universal Product Code (UPC) bar code, multi-dimensional bar codes such as Quick Response (QR) code, Aztec code, Data Matrix, Dataglyph, MaxiCode, PDF417, Ultra Code, UCC RSS-2D bar code, and other optical codes), or acoustic detection components (e.g., microphones to identify tagged audio signals). In addition, a variety of information may be derived via the communication components 1036, such as location via Internet Protocol (IP) geolocation, location via Wi-Fi® signal triangulation, location via detecting an NFC beacon signal that may indicate a particular location, and so forth.
The various memories (e.g., main memory 1012, static memory 1014, and memory of the processors 1002) and storage unit 1016 may store one or more sets of instructions and data structures (e.g., software) embodying or used by any one or more of the methodologies or functions described herein. These instructions (e.g., the instructions 1008), when executed by processors 1002, cause various operations to implement the disclosed examples.
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 components 1036) and using any one of several well-known transfer protocols (e.g., HTTP). Similarly, the instructions 1008 may be transmitted or received using a transmission medium via a coupling (e.g., a peer-to-peer coupling) to the devices 1022.
Software Architecture
The operating system 1112 manages hardware resources and provides common services. The operating system 1112 includes, for example, a kernel 1114, services 1116, and drivers 1122. The kernel 1114 acts as an abstraction layer between the hardware and the other software layers. For example, the kernel 1114 provides memory management, processor management (e.g., scheduling), component management, networking, and security settings, among other functionality. The services 1116 can provide other common services for the other software layers. The drivers 1122 are responsible for controlling or interfacing with the underlying hardware. For instance, the drivers 1122 can include display drivers, camera drivers, BLUETOOTH® or BLUETOOTH® Low Energy drivers, flash memory drivers, serial communication drivers (e.g., USB drivers), WI-FI® drivers, audio drivers, power management drivers, and so forth.
The libraries 1110 provide a common low-level infrastructure used by applications 1106. The libraries 1110 can include system libraries 1118 (e.g., C standard library) that provide functions such as memory allocation functions, string manipulation functions, mathematic functions, and the like. In addition, the libraries 1110 can include API libraries 1124 such as media libraries (e.g., libraries to support 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)), graphics libraries (e.g., an OpenGL framework used to render in 2D and 3D in a graphic content on a display), database libraries (e.g., SQLite to provide various relational database functions), web libraries (e.g., WebKit to provide web browsing functionality), and the like. The libraries 1110 can also include a wide variety of other libraries 1128 to provide many other APIs to the applications 1106.
The frameworks 1108 provide a common high-level infrastructure that is used by the applications 1106. For example, the frameworks 1108 provide various GUI functions, high-level resource management, and high-level location services. The frameworks 1108 can provide a broad spectrum of other APIs that can be used by the applications 1106, some of which may be specific to a particular operating system or platform.
In an example, the 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 broad assortment of other applications such as an external application 1140. The applications 1106 are programs that execute functions defined in the programs. Various programming languages can be employed to create one or more of the applications 1106, structured in a variety of manners, such as object-oriented programming languages (e.g., Objective-C, Java, or C++) or procedural programming languages (e.g., C or assembly language). In a specific example, the external application 1140 (e.g., an application developed using the ANDROID™ or IOS™ SDK by an entity other than the vendor of the particular platform) may be mobile software running on a mobile operating system such as IOS™, ANDROID™, WINDOWS® Phone, or another mobile operating system. In this example, the external application 1140 can invoke the API calls 1150 provided by the operating system 1112 to facilitate functionality described herein.
“Carrier signal” refers to any intangible medium that is capable of storing, encoding, or carrying instructions for execution by the machine, and includes digital or analog communications signals or other intangible media to facilitate communication of such instructions. Instructions may be transmitted or received over a network using a transmission medium via a network interface device.
“Client device” refers to any machine that interfaces to 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, desktop computer, laptop, PDAs, smartphones, tablets, ultrabooks, netbooks, laptops, multi-processor systems, microprocessor-based or programmable consumer electronics, game consoles, STBs, or any other communication device that a user may use to access a network.
“Communication network” refers to one or more portions of a network that 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 portion of the Internet, a portion of the Public Switched Telephone Network (PSTN), a plain old telephone service (POTS) network, a cellular telephone network, a wireless network, a Wi-Fi® network, another type of network, or a combination of two or more such networks. For example, a network or a portion of a network may include a wireless or cellular network and the coupling may be a Code Division Multiple Access (CDMA) connection, a Global System for Mobile communications (GSM) connection, or other types of cellular or wireless coupling. In this example, the coupling may implement any of a variety of types of data transfer technology, such as Single Carrier Radio Transmission Technology (1×RTT), Evolution-Data Optimized (EVDO) technology, General Packet Radio Service (GPRS) technology, Enhanced Data rates for GSM Evolution (EDGE) technology, third Generation Partnership Project (3GPP) including 3G, fourth generation wireless (4G) networks, Universal Mobile Telecommunications System (UMTS), High Speed Packet Access (HSPA), Worldwide Interoperability for Microwave Access (WiMAX), Long Term Evolution (LTE) standard, others defined by various standard-setting organizations, other long-range protocols, or other data transfer technology.
“Component” refers to a device, physical entity, or logic having boundaries defined by function or subroutine calls, branch points, APIs, or other technologies that provide for the partitioning or modularization of particular processing or control functions. Components may be combined via their interfaces with other components to carry out a machine process. A component may be a packaged functional hardware unit designed for use with other components and a part of a program that usually performs a particular function of related functions.
Components may constitute either software components (e.g., code embodied on a machine-readable medium) or hardware components. A “hardware component” is a tangible unit capable of performing certain operations and may be configured or arranged in a certain physical manner. In various examples, one or more computer systems (e.g., a standalone computer system, a client computer system, or a server computer system) or one or more hardware components of a computer system (e.g., a processor or a group of processors) may be configured by software (e.g., an application or application portion) as a hardware component that operates to perform certain operations as described herein.
A hardware component may also be implemented mechanically, electronically, or any suitable combination thereof. For example, a hardware component may include dedicated circuitry or logic that is permanently configured to perform certain operations. A hardware component may be a special-purpose processor, such as a field-programmable gate array (FPGA) or an ASIC. A hardware component may also include programmable logic or circuitry that is temporarily configured by software to perform certain operations. For example, a hardware component may include software executed by a general-purpose processor or other programmable processor. Once configured by such software, hardware components become specific machines (or specific components of a machine) uniquely tailored to perform the configured functions and are no longer general-purpose processors. It will be appreciated that the decision to implement a hardware component mechanically, in dedicated and permanently configured circuitry, or in temporarily configured circuitry (e.g., configured by software), may be driven by cost and time considerations. Accordingly, the phrase “hardware component” (or “hardware-implemented component”) should be understood to encompass a tangible entity, be that an entity that is physically constructed, permanently configured (e.g., hardwired), or temporarily configured (e.g., programmed) to operate in a certain manner or to perform certain operations described herein.
Considering examples in which hardware components are temporarily configured (e.g., programmed), each of the hardware components need not be configured or instantiated at any one instance in time. For example, where a hardware component comprises a general-purpose processor configured by software to become a special-purpose processor, the general-purpose processor may be configured as respectively different special-purpose processors (e.g., comprising different hardware components) at different times. Software accordingly configures a particular processor or processors, for example, to constitute a particular hardware component at one instance of time and to constitute a different hardware component at a different instance of time.
Hardware components can provide information to, and receive information from, other hardware components. Accordingly, the described hardware components may be regarded as being communicatively coupled. Where multiple hardware components exist contemporaneously, communications may be achieved through signal transmission (e.g., over appropriate circuits and buses) between or among two or more of the hardware components. In examples in which multiple hardware components are configured or instantiated at different times, communications between such hardware components may be achieved, for example, through the storage and retrieval of information in memory structures to which the multiple hardware components have access. For example, one hardware component may perform an operation and store the output of that operation in a memory device to which it is communicatively coupled. A further hardware component may then, at a later time, access the memory device to retrieve and process the stored output. Hardware components may also initiate communications with input or output devices, and can operate on a resource (e.g., a collection of information).
The various operations of example methods described herein may be performed, at least partially, by one or more processors that are temporarily configured (e.g., by software) or permanently configured to perform the relevant operations. Whether temporarily or permanently configured, such processors may constitute processor-implemented components that operate to perform one or more operations or functions described herein. As used herein, “processor-implemented component” refers to a hardware component implemented using one or more processors. Similarly, the methods described herein may be at least partially processor-implemented, with a particular processor or processors being an example of hardware. For example, at least some of the operations of a method may be performed by one or more processors 1002 or processor-implemented components. Moreover, the one or more processors may also operate to support performance of the relevant operations in a “cloud computing” environment or as a “software as a service” (SaaS). For example, at least some of the operations may be performed by a group of computers (as examples of machines including processors), with these operations being accessible via a network (e.g., the Internet) and via one or more appropriate interfaces (e.g., an API). The performance of certain of the operations may be distributed among the processors, not only residing within a single machine, but deployed across a number of machines. In some examples, the processors or processor-implemented components may be located in a single geographic location (e.g., within a home environment, an office environment, or a server farm). In other examples, the processors or processor-implemented components may be distributed across a number of geographic locations.
“Computer-readable storage medium” refers to both machine-storage media and transmission media. Thus, the terms include both storage devices/media and carrier waves/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.
“Ephemeral message” refers to a message that is accessible for a time-limited duration. An ephemeral message may be a text, an image, a video, and the like. The access time for the ephemeral message may be set by the message sender. Alternatively, the access time may be a default setting or a setting specified by the recipient. Regardless of the setting technique, the message is transitory.
“Machine storage medium” refers to a single or multiple storage devices and media (e.g., a centralized or distributed database, and associated caches and servers) that store executable instructions, routines and data. The term shall accordingly be taken to include, but not be limited to, solid-state memories, and optical and magnetic media, including memory internal or external to processors. Specific examples of machine-storage media, computer-storage media and device-storage media include non-volatile memory, including by way of example semiconductor memory devices, e.g., 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 medium,” “device-storage medium,” and “computer-storage medium” mean the same thing and may be used interchangeably in this disclosure. The terms “machine-storage media,” “computer-storage media,” and “device-storage media” specifically exclude carrier waves, modulated data signals, and other such media, at least some of which are covered under the term “signal medium.”
“Non-transitory computer-readable storage medium” refers to a tangible medium that is capable of storing, encoding, or carrying the instructions for execution by a machine.
“Signal medium” refers to any intangible medium that is capable of storing, encoding, or carrying the instructions for execution by a machine and includes digital or analog communications signals or other intangible media to facilitate communication of software or data. The term “signal medium” shall be taken to include any form of a modulated data signal, carrier wave, and so forth. The term “modulated data signal” means a signal that has one or more of its characteristics set or changed in such a matter 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.
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 following claims.
| Number | Name | Date | Kind |
|---|---|---|---|
| 1115928 | Hansen | Nov 1914 | A |
| 4125894 | Cashel et al. | Nov 1978 | A |
| 4144573 | Trussell et al. | Mar 1979 | A |
| 4145746 | Trussell et al. | Mar 1979 | A |
| 4180326 | Chang | Dec 1979 | A |
| 4267730 | Curchod et al. | May 1981 | A |
| 4285240 | Gold | Aug 1981 | A |
| 4333337 | Marten | Jun 1982 | A |
| 4338818 | Hill et al. | Jul 1982 | A |
| 4369660 | Lentz et al. | Jan 1983 | A |
| 4394742 | Crummer et al. | Jul 1983 | A |
| 4402222 | Olson et al. | Sep 1983 | A |
| 4423379 | Jacobs et al. | Dec 1983 | A |
| 4507964 | Borner et al. | Apr 1985 | A |
| 4512220 | Barnhill, III et al. | Apr 1985 | A |
| 4523844 | Titsworth et al. | Jun 1985 | A |
| RE31971 | Gold | Aug 1985 | E |
| 4578755 | Quinn et al. | Mar 1986 | A |
| 4600827 | Linwood et al. | Jul 1986 | A |
| 4643030 | Becker et al. | Feb 1987 | A |
| 4713617 | Michalski | Dec 1987 | A |
| 4761749 | Titsworth et al. | Aug 1988 | A |
| 4800378 | Putrow et al. | Jan 1989 | A |
| 4804921 | Putrow et al. | Feb 1989 | A |
| 4812768 | Quinn | Mar 1989 | A |
| 4849744 | Putrow et al. | Jul 1989 | A |
| 4851833 | Putrow et al. | Jul 1989 | A |
| 4931964 | Titsworth et al. | Jun 1990 | A |
| 4980845 | Putrow et al. | Dec 1990 | A |
| 4982612 | Rittmann | Jan 1991 | A |
| 5220399 | Christian et al. | Jun 1993 | A |
| 5245324 | Jonker et al. | Sep 1993 | A |
| 5247287 | Jonker et al. | Sep 1993 | A |
| 5258753 | Jonker et al. | Nov 1993 | A |
| 5296869 | Jonker et al. | Mar 1994 | A |
| 5307279 | Christian et al. | Apr 1994 | A |
| 5317903 | Mcclelland et al. | Jun 1994 | A |
| 5426371 | Salley et al. | Jun 1995 | A |
| 5535522 | Jackson | Jul 1996 | A |
| 5574645 | Meeker et al. | Nov 1996 | A |
| 5677632 | Meeker | Oct 1997 | A |
| 5784284 | Taraki | Jul 1998 | A |
| 5898108 | Mieczkowski et al. | Apr 1999 | A |
| 6018245 | Villa et al. | Jan 2000 | A |
| 6148528 | Jackson | Nov 2000 | A |
| 6360273 | Beurket et al. | Mar 2002 | B1 |
| 6442661 | Dreszer | Aug 2002 | B1 |
| 6560516 | Baird et al. | May 2003 | B1 |
| 6651098 | Carroll et al. | Nov 2003 | B1 |
| 6720860 | Narayanaswami | Apr 2004 | B1 |
| 6745286 | Staub et al. | Jun 2004 | B2 |
| 6816885 | Raghunandan | Nov 2004 | B1 |
| 6862692 | Ulrich et al. | Mar 2005 | B2 |
| 6873902 | Welch | Mar 2005 | B2 |
| 6990547 | Ulrich et al. | Jan 2006 | B2 |
| 6990667 | Ulrich et al. | Jan 2006 | B2 |
| 7054927 | Ulrich et al. | May 2006 | B2 |
| 7209850 | Brott et al. | Apr 2007 | B2 |
| 7215130 | Thibedeau et al. | May 2007 | B2 |
| 7225064 | Fudali et al. | May 2007 | B2 |
| 7286927 | Decarlo et al. | Oct 2007 | B2 |
| 7359990 | Munir et al. | Apr 2008 | B2 |
| 7373226 | Cancilla et al. | May 2008 | B1 |
| 7551993 | Cancilla et al. | Jun 2009 | B1 |
| 7565844 | Crass et al. | Jul 2009 | B2 |
| 7644616 | Cullum et al. | Jan 2010 | B1 |
| 7657386 | Thibedeau et al. | Feb 2010 | B2 |
| 7684026 | Rogers et al. | Mar 2010 | B2 |
| 7703213 | Rogers | Apr 2010 | B2 |
| 7729880 | Mashburn | Jun 2010 | B1 |
| 7843167 | Derome et al. | Nov 2010 | B2 |
| 7957860 | Grier et al. | Jun 2011 | B2 |
| 7971156 | Albertson et al. | Jun 2011 | B2 |
| 8104185 | Gray et al. | Jan 2012 | B2 |
| 8528050 | Kashima et al. | Sep 2013 | B2 |
| 8560168 | Krzystofczyk et al. | Oct 2013 | B2 |
| 8588431 | Aggarwal et al. | Nov 2013 | B2 |
| 8656062 | Krzystofczyk et al. | Feb 2014 | B2 |
| 8693286 | Rogers et al. | Apr 2014 | B1 |
| 9228819 | Pruitt et al. | Jan 2016 | B2 |
| 9242356 | King et al. | Jan 2016 | B2 |
| 9477950 | Johnson et al. | Oct 2016 | B2 |
| 9634966 | Bostick et al. | Apr 2017 | B2 |
| 9742997 | Bamberger et al. | Aug 2017 | B1 |
| 9747573 | Shaburov et al. | Aug 2017 | B2 |
| 9811923 | Wang et al. | Nov 2017 | B2 |
| 9911073 | Spiegel et al. | Mar 2018 | B1 |
| 10062050 | Lipsey et al. | Aug 2018 | B2 |
| 10102423 | Shaburov et al. | Oct 2018 | B2 |
| 10127290 | Armstrong | Nov 2018 | B1 |
| 10164975 | Son et al. | Dec 2018 | B1 |
| 10198671 | Yang et al. | Feb 2019 | B1 |
| 10212356 | Lerner | Feb 2019 | B1 |
| 10219110 | Davis et al. | Feb 2019 | B2 |
| 10284777 | Rogers et al. | May 2019 | B2 |
| 10285001 | Allen et al. | May 2019 | B2 |
| 10311644 | Rodriguez, II | Jun 2019 | B2 |
| 10324942 | Yang et al. | Jun 2019 | B2 |
| 10345987 | Andreou | Jul 2019 | B1 |
| 10346985 | Poliakov | Jul 2019 | B1 |
| 10387514 | Yang et al. | Aug 2019 | B1 |
| 10397469 | Yan et al. | Aug 2019 | B1 |
| 10410028 | Cansizoglu et al. | Sep 2019 | B1 |
| 10417258 | Ogievetsky et al. | Sep 2019 | B2 |
| 10427266 | Greenwald et al. | Oct 2019 | B2 |
| 10445938 | Poliakov et al. | Oct 2019 | B1 |
| 10448199 | Chen et al. | Oct 2019 | B1 |
| 10467147 | Ahmed et al. | Nov 2019 | B1 |
| 10474321 | Patel et al. | Nov 2019 | B2 |
| 10508907 | Rogers et al. | Dec 2019 | B2 |
| 10552968 | Wang et al. | Feb 2020 | B1 |
| 10582277 | Tang | Mar 2020 | B2 |
| 10586570 | Shaburova et al. | Mar 2020 | B2 |
| 10592839 | Behringer et al. | Mar 2020 | B2 |
| 10607053 | Boyd et al. | Mar 2020 | B1 |
| 10664873 | Son et al. | May 2020 | B1 |
| 10678849 | Ouimet et al. | Jun 2020 | B1 |
| 10679389 | Allen et al. | Jun 2020 | B2 |
| 10679428 | Chen et al. | Jun 2020 | B1 |
| 10685507 | Merg et al. | Jun 2020 | B2 |
| 10692241 | Kunert et al. | Jun 2020 | B2 |
| 10726059 | Ren et al. | Jul 2020 | B1 |
| 10726872 | Boyd et al. | Jul 2020 | B1 |
| 10735890 | Akhoondi et al. | Aug 2020 | B1 |
| 10740974 | Cowburn et al. | Aug 2020 | B1 |
| 10762121 | Denton et al. | Sep 2020 | B2 |
| 10764053 | Brook et al. | Sep 2020 | B2 |
| 10764514 | Hoevenaar et al. | Sep 2020 | B1 |
| 10776993 | Chen et al. | Sep 2020 | B1 |
| 10778884 | Yan et al. | Sep 2020 | B2 |
| 10803664 | McPhee et al. | Oct 2020 | B2 |
| 10805254 | Allen et al. | Oct 2020 | B1 |
| 10809304 | Larson et al. | Oct 2020 | B1 |
| 10817898 | Waldron et al. | Oct 2020 | B2 |
| 10818308 | Chu | Oct 2020 | B1 |
| 10823553 | Ruther et al. | Nov 2020 | B1 |
| 10836020 | King et al. | Nov 2020 | B2 |
| 10861170 | Li et al. | Dec 2020 | B1 |
| 10885559 | Andreou | Jan 2021 | B1 |
| 10896346 | Gusarov | Jan 2021 | B1 |
| 10904484 | Eirinberg et al. | Jan 2021 | B1 |
| 10915924 | Soloff | Feb 2021 | B1 |
| 10939236 | Fung et al. | Mar 2021 | B1 |
| 10943393 | Eastham et al. | Mar 2021 | B2 |
| 10944730 | Boutros et al. | Mar 2021 | B1 |
| 10972984 | Tham et al. | Apr 2021 | B1 |
| 10993069 | Son et al. | Apr 2021 | B2 |
| 10997787 | Ge et al. | May 2021 | B2 |
| 11003997 | Blackwood et al. | May 2021 | B1 |
| 11017233 | Charlton et al. | May 2021 | B2 |
| 11023496 | Chklovski et al. | Jun 2021 | B1 |
| 11023514 | Allen et al. | Jun 2021 | B2 |
| 11024058 | Rehfeld et al. | Jun 2021 | B2 |
| 11024101 | Chepizhenko et al. | Jun 2021 | B1 |
| 11030793 | Katz | Jun 2021 | B2 |
| 11032670 | Baylin et al. | Jun 2021 | B1 |
| 11039113 | Katz | Jun 2021 | B2 |
| 11039394 | Tham et al. | Jun 2021 | B2 |
| 11055514 | Cao et al. | Jul 2021 | B1 |
| 11081141 | Li et al. | Aug 2021 | B2 |
| 11087513 | Duan et al. | Aug 2021 | B1 |
| 11087728 | Canberk et al. | Aug 2021 | B1 |
| 11089427 | Canberk et al. | Aug 2021 | B1 |
| 11092998 | Castañeda et al. | Aug 2021 | B1 |
| 11099643 | Miller et al. | Aug 2021 | B1 |
| 11106343 | Duan et al. | Aug 2021 | B1 |
| 11107185 | Duan et al. | Aug 2021 | B2 |
| 11112945 | Al Majid et al. | Sep 2021 | B1 |
| 11115928 | Bamberger et al. | Sep 2021 | B2 |
| 11120597 | Cao et al. | Sep 2021 | B2 |
| 11126206 | Meisenholder et al. | Sep 2021 | B2 |
| 11126266 | Xiao et al. | Sep 2021 | B1 |
| 11132763 | Katz et al. | Sep 2021 | B2 |
| 11140515 | Voss et al. | Oct 2021 | B1 |
| 11143867 | Rodriguez, II | Oct 2021 | B2 |
| 11144780 | Hoevenaar | Oct 2021 | B2 |
| 11146763 | Katz | Oct 2021 | B1 |
| 11157076 | Tham | Oct 2021 | B1 |
| 11158351 | Ren et al. | Oct 2021 | B1 |
| 11159743 | Li et al. | Oct 2021 | B2 |
| 11164353 | Luo et al. | Nov 2021 | B2 |
| 11165734 | Desserrey et al. | Nov 2021 | B1 |
| 11169600 | Canberk et al. | Nov 2021 | B1 |
| 11169658 | Al Majid et al. | Nov 2021 | B2 |
| 11169675 | Anvaripour et al. | Nov 2021 | B1 |
| 11170393 | Ma et al. | Nov 2021 | B1 |
| 11171908 | Barton et al. | Nov 2021 | B1 |
| 11176723 | Krishnan Gorumkonda et al. | Nov 2021 | B2 |
| 11178089 | Voss | Nov 2021 | B1 |
| 11178375 | Katz et al. | Nov 2021 | B1 |
| 11182603 | Li et al. | Nov 2021 | B1 |
| 11189098 | Hare et al. | Nov 2021 | B2 |
| 11190534 | Shah et al. | Nov 2021 | B1 |
| 11195341 | Canberk et al. | Dec 2021 | B1 |
| 11204949 | Brewer et al. | Dec 2021 | B1 |
| 11210467 | Carvalho et al. | Dec 2021 | B1 |
| 11210850 | Goodrich et al. | Dec 2021 | B2 |
| 11212509 | Ardisana, II et al. | Dec 2021 | B2 |
| 11216949 | Poliakov | Jan 2022 | B1 |
| 11217020 | Goodrich et al. | Jan 2022 | B2 |
| 11217022 | Woodford | Jan 2022 | B1 |
| 11218834 | Akhoondi et al. | Jan 2022 | B2 |
| 11218838 | Al Majid et al. | Jan 2022 | B2 |
| 20020004694 | Mcleod et al. | Jan 2002 | A1 |
| 20020124137 | Ulrich et al. | Sep 2002 | A1 |
| 20020138559 | Ulrich et al. | Sep 2002 | A1 |
| 20020169827 | Ulrich et al. | Nov 2002 | A1 |
| 20020191311 | Ulrich et al. | Dec 2002 | A1 |
| 20050005463 | Omahony et al. | Jan 2005 | A1 |
| 20050065678 | Smith et al. | Mar 2005 | A1 |
| 20050248357 | Mcqueeney et al. | Nov 2005 | A1 |
| 20060095230 | Grier et al. | May 2006 | A1 |
| 20060142907 | Cancilla et al. | Jun 2006 | A1 |
| 20060287785 | Decarlo et al. | Dec 2006 | A1 |
| 20070083303 | Osullivan et al. | Apr 2007 | A1 |
| 20070227237 | Brott et al. | Oct 2007 | A1 |
| 20080215693 | Bostick et al. | Sep 2008 | A1 |
| 20090030558 | Rogers et al. | Jan 2009 | A1 |
| 20090073425 | Kling, III et al. | Mar 2009 | A1 |
| 20120044527 | Panko | Feb 2012 | A1 |
| 20120158859 | Saxena et al. | Jun 2012 | A1 |
| 20120254634 | Chakra et al. | Oct 2012 | A1 |
| 20150066781 | Johnson et al. | Mar 2015 | A1 |
| 20150066901 | Burris et al. | Mar 2015 | A1 |
| 20150066916 | Burris et al. | Mar 2015 | A1 |
| 20150286858 | Shaburov et al. | Oct 2015 | A1 |
| 20160048869 | Shim et al. | Feb 2016 | A1 |
| 20170140581 | Rogers et al. | May 2017 | A1 |
| 20170169617 | Rodriguez, II | Jun 2017 | A1 |
| 20170286752 | Gusarov et al. | Oct 2017 | A1 |
| 20170287006 | Azmoodeh et al. | Oct 2017 | A1 |
| 20170289234 | Andreou et al. | Oct 2017 | A1 |
| 20180075651 | Hare et al. | Mar 2018 | A1 |
| 20180075672 | Lewis et al. | Mar 2018 | A1 |
| 20180124300 | Brook | May 2018 | A1 |
| 20180174221 | Merg et al. | Jun 2018 | A1 |
| 20180225687 | Ahmed et al. | Aug 2018 | A1 |
| 20180357614 | Merg et al. | Dec 2018 | A1 |
| 20190146973 | Merg et al. | May 2019 | A1 |
| 20190206061 | Kudriashov et al. | Jul 2019 | A1 |
| 20190222723 | Harrell et al. | Jul 2019 | A1 |
| 20190279046 | Han et al. | Sep 2019 | A1 |
| 20190319899 | Dos Santos et al. | Oct 2019 | A1 |
| 20200013022 | Lewis et al. | Jan 2020 | A1 |
| 20200088515 | Rogers et al. | Mar 2020 | A1 |
| 20200112531 | Tang | Apr 2020 | A1 |
| 20200143238 | Ramnath | May 2020 | A1 |
| 20200167995 | Hare et al. | May 2020 | A1 |
| 20200219312 | Jurgenson et al. | Jul 2020 | A1 |
| 20200234223 | Merg et al. | Jul 2020 | A1 |
| 20200314586 | Bouba et al. | Oct 2020 | A1 |
| 20200334283 | Cook et al. | Oct 2020 | A1 |
| 20200342389 | Merg et al. | Oct 2020 | A1 |
| 20200351353 | Al Majid et al. | Nov 2020 | A1 |
| 20200356760 | Li et al. | Nov 2020 | A1 |
| 20200358731 | Boyd et al. | Nov 2020 | A1 |
| 20200379614 | Al Majid et al. | Dec 2020 | A1 |
| 20200380747 | Canberk et al. | Dec 2020 | A1 |
| 20200389466 | Sankuratripati | Dec 2020 | A1 |
| 20200401225 | Jaureguiberry et al. | Dec 2020 | A1 |
| 20200401838 | Gusarov | Dec 2020 | A1 |
| 20200402312 | Gratz | Dec 2020 | A1 |
| 20200409457 | Terrano | Dec 2020 | A1 |
| 20200410458 | Merg et al. | Dec 2020 | A1 |
| 20200412864 | Al Majid et al. | Dec 2020 | A1 |
| 20200412975 | Al Majid et al. | Dec 2020 | A1 |
| 20200413030 | Zak et al. | Dec 2020 | A1 |
| 20200413233 | Cieslak et al. | Dec 2020 | A1 |
| 20210003453 | Ruther et al. | Jan 2021 | A1 |
| 20210003454 | Ruther et al. | Jan 2021 | A1 |
| 20210004970 | Ruther et al. | Jan 2021 | A1 |
| 20210006759 | Monastyrshyn | Jan 2021 | A1 |
| 20210027100 | Bogdanovych et al. | Jan 2021 | A1 |
| 20210034202 | Chand | Feb 2021 | A1 |
| 20210049836 | Covington et al. | Feb 2021 | A1 |
| 20210049844 | Covington | Feb 2021 | A1 |
| 20210065448 | Goodrich et al. | Mar 2021 | A1 |
| 20210065454 | Goodrich et al. | Mar 2021 | A1 |
| 20210065464 | Goodrich et al. | Mar 2021 | A1 |
| 20210067756 | Goodrich et al. | Mar 2021 | A1 |
| 20210067836 | Hornsby et al. | Mar 2021 | A1 |
| 20210076173 | Monroy-Hernandez et al. | Mar 2021 | A1 |
| 20210081088 | Voss | Mar 2021 | A1 |
| 20210089522 | Costantino et al. | Mar 2021 | A1 |
| 20210089599 | Jahangiri et al. | Mar 2021 | A1 |
| 20210097245 | Monroy-Hernández | Apr 2021 | A1 |
| 20210097742 | Krishnan Gorumkonda et al. | Apr 2021 | A1 |
| 20210097743 | Krishnan Gorumkonda et al. | Apr 2021 | A1 |
| 20210099551 | Cieslak et al. | Apr 2021 | A1 |
| 20210099639 | Bartow et al. | Apr 2021 | A1 |
| 20210105415 | Zhang et al. | Apr 2021 | A1 |
| 20210109584 | Guim Bernat | Apr 2021 | A1 |
| 20210136521 | Al Majid et al. | May 2021 | A1 |
| 20210142586 | Covington et al. | May 2021 | A1 |
| 20210158389 | Andreou | May 2021 | A1 |
| 20210165998 | Cao et al. | Jun 2021 | A1 |
| 20210173880 | Cooper et al. | Jun 2021 | A1 |
| 20210182331 | Al Majid et al. | Jun 2021 | A1 |
| 20210192744 | Vij et al. | Jun 2021 | A1 |
| 20210200390 | Luo et al. | Jul 2021 | A1 |
| 20210200426 | Al Majid et al. | Jul 2021 | A1 |
| 20210201036 | Gupta et al. | Jul 2021 | A1 |
| 20210201392 | Aghdaii et al. | Jul 2021 | A1 |
| 20210203627 | Luo et al. | Jul 2021 | A1 |
| 20210203628 | Luo et al. | Jul 2021 | A1 |
| 20210203909 | Ryuma et al. | Jul 2021 | A1 |
| 20210209825 | Assouline et al. | Jul 2021 | A1 |
| 20210218821 | Lonkar et al. | Jul 2021 | A1 |
| 20210224050 | Wang et al. | Jul 2021 | A1 |
| 20210235225 | Strand et al. | Jul 2021 | A1 |
| 20210240315 | Alvi et al. | Aug 2021 | A1 |
| 20210241529 | Cowburn et al. | Aug 2021 | A1 |
| 20210247729 | Merg et al. | Aug 2021 | A1 |
| 20210255763 | Robertson et al. | Aug 2021 | A1 |
| 20210258511 | Goodrich et al. | Aug 2021 | A1 |
| 20210264949 | Huang | Aug 2021 | A1 |
| 20210279155 | Theriot et al. | Sep 2021 | A1 |
| 20210279842 | Anilkumar et al. | Sep 2021 | A1 |
| 20210281632 | Brewer et al. | Sep 2021 | A1 |
| 20210297811 | Meisenholder et al. | Sep 2021 | A1 |
| 20210299630 | Kozhemiak et al. | Sep 2021 | A1 |
| 20210303077 | Anvaripour et al. | Sep 2021 | A1 |
| 20210303110 | Giacalone et al. | Sep 2021 | A1 |
| 20210303114 | Apanovych et al. | Sep 2021 | A1 |
| 20210303855 | Anvaripour et al. | Sep 2021 | A1 |
| 20210303860 | Anvaripour et al. | Sep 2021 | A1 |
| 20210304429 | Cowburn et al. | Sep 2021 | A1 |
| 20210304449 | Mourkogiannis | Sep 2021 | A1 |
| 20210304451 | Fortier et al. | Sep 2021 | A1 |
| 20210304505 | Anvaripour et al. | Sep 2021 | A1 |
| 20210304506 | Mourkogiannis et al. | Sep 2021 | A1 |
| 20210304507 | Smith et al. | Sep 2021 | A1 |
| 20210304629 | Barron et al. | Sep 2021 | A1 |
| 20210304754 | Fortier et al. | Sep 2021 | A1 |
| 20210306451 | Heikkinen et al. | Sep 2021 | A1 |
| 20210306839 | Baron et al. | Sep 2021 | A1 |
| 20210312523 | Luo et al. | Oct 2021 | A1 |
| 20210312533 | Luo et al. | Oct 2021 | A1 |
| 20210312672 | Luo et al. | Oct 2021 | A1 |
| 20210312678 | Luo et al. | Oct 2021 | A1 |
| 20210312690 | Krishnan Gorumkonda et al. | Oct 2021 | A1 |
| 20210319540 | Cao et al. | Oct 2021 | A1 |
| 20210319586 | Rogers et al. | Oct 2021 | A1 |
| 20210319612 | Monroy-Hernandez et al. | Oct 2021 | A1 |
| 20210328955 | Collins et al. | Oct 2021 | A1 |
| 20210334993 | Woodford | Oct 2021 | A1 |
| 20210335350 | Ribas Machado Das Neves et al. | Oct 2021 | A1 |
| 20210336909 | Taitz | Oct 2021 | A1 |
| 20210337351 | Tham et al. | Oct 2021 | A1 |
| 20210352262 | Buslaev | Nov 2021 | A1 |
| 20210357075 | Nayar et al. | Nov 2021 | A1 |
| 20210365309 | Merg | Nov 2021 | A1 |
| 20210367798 | Giacalone et al. | Nov 2021 | A1 |
| 20210367914 | Collins et al. | Nov 2021 | A1 |
| 20210374839 | Luo et al. | Dec 2021 | A1 |
| 20210382585 | Collins et al. | Dec 2021 | A1 |
| 20210382587 | Heikkinen et al. | Dec 2021 | A1 |
| 20210382616 | Gale et al. | Dec 2021 | A1 |
| 20210383373 | Eirinberg et al. | Dec 2021 | A1 |
| 20210383509 | Demyanov et al. | Dec 2021 | A1 |
| 20210385179 | Heikkinen et al. | Dec 2021 | A1 |
| 20210387090 | Eirinberg et al. | Dec 2021 | A1 |
| 20210387097 | Desserrey et al. | Dec 2021 | A1 |
| 20210387099 | Desserrey et al. | Dec 2021 | A1 |
| 20210387637 | Rogers et al. | Dec 2021 | A1 |
| 20210389851 | Al Majid et al. | Dec 2021 | A1 |
| 20210389852 | Desserrey et al. | Dec 2021 | A1 |
| 20210390118 | Gorkin et al. | Dec 2021 | A1 |
| 20210390729 | Fox-Roberts et al. | Dec 2021 | A1 |
| 20210390745 | Rykhliuk et al. | Dec 2021 | A1 |
| 20210390784 | Smith et al. | Dec 2021 | A1 |
| 20210392096 | Desserrey et al. | Dec 2021 | A1 |
| 20210392098 | Gorkin et al. | Dec 2021 | A1 |
| 20210392459 | Gorkin et al. | Dec 2021 | A1 |
| 20210392460 | Gorkin et al. | Dec 2021 | A1 |
| 20210397000 | Rodriguez, II | Dec 2021 | A1 |
| 20210400442 | Cieslak et al. | Dec 2021 | A1 |
| 20210404831 | Drummond et al. | Dec 2021 | A1 |
| 20210405363 | Canberk et al. | Dec 2021 | A1 |
| 20210405747 | Tham | Dec 2021 | A1 |
| 20210405831 | Mourkogiannis et al. | Dec 2021 | A1 |
| 20210405832 | Brown et al. | Dec 2021 | A1 |
| 20210406447 | Hermann et al. | Dec 2021 | A1 |
| 20210406543 | Drummond et al. | Dec 2021 | A1 |
| 20210406585 | Hoevenaar | Dec 2021 | A1 |
| 20210406965 | Anvaripour et al. | Dec 2021 | A1 |
| 20210407163 | Chai et al. | Dec 2021 | A1 |
| 20210407178 | Zhou et al. | Dec 2021 | A1 |
| 20210407205 | Canberk et al. | Dec 2021 | A1 |
| 20210407506 | Drummond et al. | Dec 2021 | A1 |
| 20210407548 | Ren et al. | Dec 2021 | A1 |
| 20210409356 | Luo et al. | Dec 2021 | A1 |
| 20210409357 | Brody et al. | Dec 2021 | A1 |
| 20210409502 | Chepizhenko et al. | Dec 2021 | A1 |
| 20210409517 | Luo et al. | Dec 2021 | A1 |
| 20210409535 | Mourkogiannis et al. | Dec 2021 | A1 |
| 20210409610 | Mandia et al. | Dec 2021 | A1 |
| 20210409612 | Mandia et al. | Dec 2021 | A1 |
| 20210409614 | Luo et al. | Dec 2021 | A1 |
| 20210409616 | Chan et al. | Dec 2021 | A1 |
| 20210409898 | Fung et al. | Dec 2021 | A1 |
| 20210409904 | Baylin et al. | Dec 2021 | A1 |
| 20220004260 | Xiao et al. | Jan 2022 | A1 |
| Number | Date | Country |
|---|---|---|
| 667737 | Apr 1996 | AU |
| 739822 | Oct 2001 | AU |
| 2009255971 | Dec 2009 | AU |
| 1246223 | Dec 1988 | CA |
| 1304162 | Jun 1992 | CA |
| 1307050 | Sep 1992 | CA |
| 2239912 | Feb 2000 | CA |
| 2100545 | Jan 2002 | CA |
| 2166673 | Apr 2004 | CA |
| 2642852 | Oct 2007 | CA |
| 2849522 | Nov 2014 | CA |
| 1110624 | Jun 2003 | CN |
| 1427945 | Jul 2003 | CN |
| 1511230 | Jul 2004 | CN |
| 1522340 | Aug 2004 | CN |
| 1533496 | Sep 2004 | CN |
| 1187715 | Feb 2005 | CN |
| 1189861 | Feb 2005 | CN |
| 1592842 | Mar 2005 | CN |
| 1695063 | Nov 2005 | CN |
| 1708678 | Dec 2005 | CN |
| 1255665 | May 2006 | CN |
| 1265207 | Jul 2006 | CN |
| 1306246 | Mar 2007 | CN |
| 101095029 | Dec 2007 | CN |
| 100360893 | Jan 2008 | CN |
| 100360897 | Jan 2008 | CN |
| 100538257 | Sep 2009 | CN |
| 100565100 | Dec 2009 | CN |
| 100565154 | Dec 2009 | CN |
| 1742193 | Apr 2010 | CN |
| 101802547 | Aug 2010 | CN |
| 101809404 | Jun 2012 | CN |
| 103217129 | Jul 2013 | CN |
| 103226010 | Jul 2013 | CN |
| 103453857 | Dec 2013 | CN |
| 104025159 | Sep 2014 | CN |
| 104139365 | Nov 2014 | CN |
| 102177524 | Apr 2015 | CN |
| 102369560 | Apr 2015 | CN |
| 105209853 | Dec 2015 | CN |
| 102803017 | Apr 2016 | CN |
| 205483598 | Aug 2016 | CN |
| 104142204 | Jan 2017 | CN |
| 106408237 | Feb 2017 | CN |
| 104488004 | Apr 2017 | CN |
| 104487207 | May 2017 | CN |
| 107110647 | Aug 2017 | CN |
| 107111428 | Aug 2017 | CN |
| 107124532 | Sep 2017 | CN |
| 107273415 | Oct 2017 | CN |
| 107278317 | Oct 2017 | CN |
| 107430697 | Dec 2017 | CN |
| 107637072 | Jan 2018 | CN |
| 107710772 | Feb 2018 | CN |
| 107924494 | Apr 2018 | CN |
| 108140148 | Jun 2018 | CN |
| 108351988 | Jul 2018 | CN |
| 108351989 | Jul 2018 | CN |
| 108351997 | Jul 2018 | CN |
| 104142903 | Sep 2018 | CN |
| 104937557 | Nov 2018 | CN |
| 108798273 | Nov 2018 | CN |
| 108832799 | Nov 2018 | CN |
| 108942767 | Dec 2018 | CN |
| 109314659 | Feb 2019 | CN |
| 109416805 | Mar 2019 | CN |
| 109716264 | May 2019 | CN |
| 109791346 | May 2019 | CN |
| 109791404 | May 2019 | CN |
| 109791635 | May 2019 | CN |
| 109791650 | May 2019 | CN |
| 109791668 | May 2019 | CN |
| 105593880 | Jun 2019 | CN |
| 109844761 | Jun 2019 | CN |
| 109863532 | Jun 2019 | CN |
| 109952610 | Jun 2019 | CN |
| 105683970 | Jul 2019 | CN |
| 109997129 | Jul 2019 | CN |
| 110050283 | Jul 2019 | CN |
| 110089117 | Aug 2019 | CN |
| 110168476 | Aug 2019 | CN |
| 110168478 | Aug 2019 | CN |
| 110168586 | Aug 2019 | CN |
| 110192395 | Aug 2019 | CN |
| 108351988 | Sep 2019 | CN |
| 110199245 | Sep 2019 | CN |
| 110268437 | Sep 2019 | CN |
| 110300951 | Oct 2019 | CN |
| 110383344 | Oct 2019 | CN |
| 110383579 | Oct 2019 | CN |
| 110394758 | Nov 2019 | CN |
| 110462616 | Nov 2019 | CN |
| 110800012 | Feb 2020 | CN |
| 111386547 | Jul 2020 | CN |
| 111630550 | Sep 2020 | CN |
| 111771156 | Oct 2020 | CN |
| 107111434 | Nov 2020 | CN |
| 112335148 | Feb 2021 | CN |
| 112771438 | May 2021 | CN |
| 112771856 | May 2021 | CN |
| 109699186 | Jun 2021 | CN |
| 113168425 | Jul 2021 | CN |
| 113260951 | Aug 2021 | CN |
| 105358934 | Sep 2021 | CN |
| 113544682 | Oct 2021 | CN |
| 113631886 | Nov 2021 | CN |
| 113825091 | Dec 2021 | CN |
| 113874757 | Dec 2021 | CN |
| 113874813 | Dec 2021 | CN |
| 113875161 | Dec 2021 | CN |
| 113906413 | Jan 2022 | CN |
| 4300112 | Dec 1998 | DE |
| 6031380 | Jun 2007 | DE |
| 69814132 | Jul 2007 | DE |
| 0762135 | Mar 1997 | EP |
| 0789457 | Aug 1997 | EP |
| 1071930 | Jan 2001 | EP |
| 0724159 | Aug 2001 | EP |
| 0701134 | Dec 2001 | EP |
| 0927335 | Apr 2003 | EP |
| 1307701 | May 2003 | EP |
| 0789244 | Apr 2004 | EP |
| 1481254 | Dec 2004 | EP |
| 1620700 | Feb 2006 | EP |
| 1783570 | May 2007 | EP |
| 1958311 | Aug 2008 | EP |
| 2179249 | Apr 2010 | EP |
| 2174201 | Feb 2013 | EP |
| 2841876 | Mar 2015 | EP |
| 1573671 | Sep 2016 | EP |
| 2965167 | Jul 2018 | EP |
| 2171418 | Jan 2020 | EP |
| 3507772 | Dec 2020 | EP |
| 3420474 | Apr 2021 | EP |
| 3871198 | Sep 2021 | EP |
| 3899917 | Oct 2021 | EP |
| 3903500 | Nov 2021 | EP |
| 3909029 | Nov 2021 | EP |
| 2317267 | Apr 2009 | ES |
| 2508099 | May 2014 | GB |
| 2528741 | Feb 2016 | GB |
| 2587491 | Mar 2021 | GB |
| 217933 | May 2000 | HU |
| 20190119115 | Oct 2019 | KR |
| 20190125520 | Nov 2019 | KR |
| 20190139311 | Dec 2019 | KR |
| 20200043462 | Apr 2020 | KR |
| 20210008939 | Jan 2021 | KR |
| 20210025690 | Mar 2021 | KR |
| 20210046760 | Apr 2021 | KR |
| 20210103541 | Aug 2021 | KR |
| 20210107139 | Aug 2021 | KR |
| 20210116652 | Sep 2021 | KR |
| 587349 | May 2004 | TW |
| 200416115 | Sep 2004 | TW |
| I626750 | Jun 2018 | TW |
| I637381 | Oct 2018 | TW |
| WO-0070304 | Nov 2001 | WO |
| WO-02061737 | Aug 2002 | WO |
| WO-2005033628 | Apr 2005 | WO |
| WO-2012067832 | May 2012 | WO |
| WO-2012082807 | Jun 2012 | WO |
| WO-2015030737 | Mar 2015 | WO |
| WO-2020047261 | Mar 2020 | WO |
| WO-2020051086 | Mar 2020 | WO |
| WO-2020132541 | Jun 2020 | WO |
| WO-2020160261 | Aug 2020 | WO |
| WO-2021042134 | Mar 2021 | WO |
| WO-2021051131 | Mar 2021 | WO |
| WO-2021061326 | Apr 2021 | WO |
| WO-2021062439 | Apr 2021 | WO |
| WO-2021067988 | Apr 2021 | WO |
| WO-2021119408 | Jun 2021 | WO |
| WO-2021119662 | Jun 2021 | WO |
| WO-2021138630 | Jul 2021 | WO |
| WO-2021189068 | Sep 2021 | WO |
| WO-2021194755 | Sep 2021 | WO |
| WO-2021194855 | Sep 2021 | WO |
| WO-2021195192 | Sep 2021 | WO |
| WO-2021195404 | Sep 2021 | WO |
| WO-2021203118 | Oct 2021 | WO |
| WO-2021203119 | Oct 2021 | WO |
| WO-2021203133 | Oct 2021 | WO |
| WO-2021212133 | Oct 2021 | WO |
| WO-2021216999 | Oct 2021 | WO |
| WO-2021222107 | Nov 2021 | WO |
| WO-2021222225 | Nov 2021 | WO |
| WO-2021226341 | Nov 2021 | WO |
| WO-2021242634 | Dec 2021 | WO |
| WO-2021242688 | Dec 2021 | WO |
| WO-2021242771 | Dec 2021 | WO |
| WO-2021247362 | Dec 2021 | WO |
| WO-2021252201 | Dec 2021 | WO |
| WO-2021252242 | Dec 2021 | WO |
| WO-2021252386 | Dec 2021 | WO |
| WO-2021252763 | Dec 2021 | WO |
| WO-2021257280 | Dec 2021 | WO |
| WO-2021257401 | Dec 2021 | WO |
| WO-2021257450 | Dec 2021 | WO |
| WO-2021257455 | Dec 2021 | WO |
| WO-2021257616 | Dec 2021 | WO |
| WO-2021257619 | Dec 2021 | WO |
| WO-2021263208 | Dec 2021 | WO |
| WO-2021263210 | Dec 2021 | WO |
| WO-2022005687 | Jan 2022 | WO |
| WO-2022005693 | Jan 2022 | WO |
| WO-2022005698 | Jan 2022 | WO |
| WO-2022005708 | Jan 2022 | WO |
| WO-2022005715 | Jan 2022 | WO |
| WO-2022005717 | Jan 2022 | WO |
| WO-2022005720 | Jan 2022 | WO |
| WO-2022005726 | Jan 2022 | WO |
| WO-2022005733 | Jan 2022 | WO |
| WO-2022005734 | Jan 2022 | WO |
| WO-2022005794 | Jan 2022 | WO |
| WO-2022005838 | Jan 2022 | WO |
| WO-2022005841 | Jan 2022 | WO |
| WO-2022005843 | Jan 2022 | WO |
| WO-2022005845 | Jan 2022 | WO |
| WO-2022005946 | Jan 2022 | WO |
| WO-2022006116 | Jan 2022 | WO |
| WO-2022006138 | Jan 2022 | WO |
| WO-2022006162 | Jan 2022 | WO |
| WO-2022006170 | Jan 2022 | WO |
| WO-2022006249 | Jan 2022 | WO |
| WO-2022006279 | Jan 2022 | WO |
| WO-2022006289 | Jan 2022 | WO |
| WO-2022006299 | Jan 2022 | WO |
| WO-2022006318 | Jan 2022 | WO |
| WO-2023211739 | Nov 2023 | WO |
| Entry |
|---|
| “International Application Serial No. PCT/US2023/019128, International Search Report mailed Aug. 29, 2023”, 2 pgs. |
| “International Application Serial No. PCT/US2023/019128, Written Opinion mailed Aug. 29, 2023”, 6 pgs. |
| Number | Date | Country | |
|---|---|---|---|
| 20230351666 A1 | Nov 2023 | US |
