Augmented reality speech balloon system

Information

  • Patent Grant
  • 11748579
  • Patent Number
    11,748,579
  • Date Filed
    Tuesday, September 14, 2021
    2 years ago
  • Date Issued
    Tuesday, September 5, 2023
    8 months ago
Abstract
Disclosed is an augmented reality system to generate and cause display of an augmented reality interface at a client device. Various embodiments may detect speech, identify a source of the speech, transcribe the speech to a text string, generate a speech bubble based on properties of the speech and that includes a presentation of the text string, and cause display of the speech bubble at a location in the augmented reality interface based on the source of the speech.
Description
TECHNICAL FIELD

Embodiments of the present disclosure relate generally to mobile computing technology and, more particularly, but not by way of limitation, to the presentation of augmented and virtual reality displays.


BACKGROUND

Augmented reality (AR) is a live direct or indirect view of a physical, real-world environment whose elements are supplemented, or “augmented,” by a computer-generated sensory input such as sound, video, graphics, or the like. As a result, the technology functions to enhance a user's perception of reality.





BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

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.



FIG. 1 is a block diagram showing an example messaging system for exchanging data (e.g., messages and associated content) over a network in accordance with some embodiments, wherein the messaging system includes an augmented reality system.



FIG. 2 is block diagram illustrating further details regarding a messaging system, according to example embodiments.



FIG. 3 is a schematic diagram illustrating data which may be stored in the database of the messaging server system, according to certain example embodiments.



FIG. 4 is a schematic diagram illustrating a structure of a message, according to some embodiments, generated by a messaging client application for communication.



FIG. 5 is a schematic diagram illustrating an example access-limiting process, in terms of which access to content (e.g., an ephemeral message, and associated multimedia payload of data) or a content collection (e.g., an ephemeral message story) may be time-limited (e.g., made ephemeral) in accordance with some embodiments.



FIG. 6 is a block diagram illustrating various modules of an augmented reality system, according to certain example embodiments.



FIG. 7 is a flowchart illustrating various operations of the augmented reality system in generating and causing display of a speech bubble in a graphical user interface (GUI), according to certain example embodiments.



FIG. 8 is a diagram illustrating various operations of the augmented reality system in generating the speech bubble based on an emotional effect, according to certain example embodiments.



FIG. 9 is a flowchart illustrating various operations of the augmented reality system in causing display of a graphical element based on an onomatopoeia, according to certain example embodiments.



FIG. 10 is an example of an augmented reality speech bubble, according to certain example embodiments.



FIG. 11 is an example of an augmented reality speech bubble, according to certain example embodiments.



FIG. 12 is an example of an augmented reality speech bubble, according to certain example embodiments.



FIG. 13 is a diagram illustrating various augmented reality speech bubbles, according to certain example embodiments.



FIG. 14 is a block diagram illustrating a representative software architecture, which may be used in conjunction with various hardware architectures herein described and used to implement various embodiments.



FIG. 15 is a block diagram illustrating components of a machine, according to some example embodiments, able to read instructions from a machine-readable medium (e.g., a machine-readable storage medium) and perform any one or more of the methodologies discussed herein.





DETAILED DESCRIPTION

Reference will now be made in detail to specific example embodiments for carrying out the inventive subject matter of the present disclosure. In the following description, specific details are set forth in order to provide a thorough understanding of the subject matter. It shall be appreciated that embodiments may be practiced without some or all of these specific details.


Disclosed is an augmented reality system to generate and cause display of an augmented reality interface at a client device. Various embodiments may detect speech, identify a source of the speech, transcribe the speech to a text string, generate a speech bubble based on properties of the speech and that includes a presentation of the text string, and cause display of the speech bubble at a location in the augmented reality interface based on the source of the speech.


Some embodiment augmented reality systems may include a video and image capture system to perform operations that include recording and acquiring images of a space, a graphical interface configured to display a presentation of the space, and a microphone to receive sound. In some example embodiments, the augmented reality system receives sounds and detects speech. For example, the augmented reality system may differentiate general ambient noises and sounds from speech based on techniques known to those skilled in the art, such as Voice Activity Detection (VAD).


In some example embodiments, the augmented reality system identifies a source of the speech in response to detecting the speech. For example, the source of the speech may include a person (e.g., a person in the space depicted in the presentation of the space), as well as a radio, television, telephone and/or mobile device, or other similar device that includes speakers and which may be configured to output a sound signal. For example, to identify a source of the speech, the augmented reality system may apply speech detection or facial landmark recognition techniques and other similar techniques to detect a person's lips moving. Based on the person's lips moving, the augmented reality system may determine that the person (specifically the person's mouth) is the source of the speech.


In instances where the source of the speech is a radio, television, telephone and/or mobile device, the augmented reality system may apply acoustic source localization techniques. Acoustic source localization include techniques for locating a source of a source given measurements of a sound field. The sound field can be described using physical quantities like sound pressure and particle velocity. By measuring these properties it is (indirectly) possible to obtain a source direction.


For example, the presentation of the space may include depictions of multiple people, each with corresponding user profiles. Having received the speech data (e.g., the speech recorded through the microphone), the augmented reality system identifies a user profile based on the speech data through speech recognition techniques. Upon determining the user profile based on the speech data, the augmented reality system determines which individual depicted in the presentation is the source of the speech based on facial landmark recognition data.


In some example embodiments, the augmented reality system transcribes the speech into a text string based on natural language speech recognition techniques. In further embodiments, the augmented reality system may translate the transcribed text string into one or more languages based on user preferences.


Having identified a source of the speech, the augmented reality system generates and causes display of a speech bubble. The size and position of the speech bubble may be based on the speech data, the text string, and the location of the source of the speech. For example, the transcribed speech data may have a length based on a total number of characters in the text string. The size of the speech bubble may thereby be based on the total number of characters in the text string. The position of the speech bubble in the GUI may be based on the location of the source of the speech. The augmented reality system may place the speech bubble adjacent to the source of the speech. In some example embodiments, the augmented reality system may identify significant and/or essential elements in the presentation (e.g., a person or persons), and place the speech bubble at a position so as not to obstruct the essential and significant elements.


In some embodiments, the augmented reality system may determine an emotional effect of the detected speech based on techniques that include, but are not limited to: analysis of attributes of the speech itself (e.g., volume and cadence of the speech); and a translation of the text string of the transcribed speech; as well as facial landmark recognition techniques (e.g., based on facial landmarks of a user). The emotional effect may include anger, sadness, happiness, love, and the like. In some embodiments, the presentation of the speech bubble and the text string generated by the augmented reality system may be based on the emotional effect.


For example, in some example embodiments, the augmented reality system may parse the text string of the transcribed speech into individual words, determine a definition of the set of words, and compare the definitions of the words to an emotional effect library. Based on the comparison, the augmented reality system may determine an intended emotional effect of the speech. For example, the text string may include a set of words that are typically associated with happiness, either literally, or based on context.


In further embodiments, the augmented reality system may determine the emotional effect of the detected speech based on the speech data, and attributes of the speech itself. For example, the speech data may indicate a volume, as well as a cadence of the speech. The augmented reality system may therefore determine the emotional effect based on the speech attributes, such as the volume and cadence.


In further embodiments, the augmented reality system may determine the emotional effect of the detected speech based on facial landmark recognition techniques. For example, having identifies a user as the source of the speech, the augmented reality system may capture facial landmarks of the user and apply facial landmark recognition techniques to determine an emotional state of the user (e.g., based on a smile, a frown, a furrowed brow, etc.). Thus, based on the emotional state, the augmented reality system determines the emotional effect of the speech.


In some example embodiments, the augmented reality system may detect non-verbal sounds and identify an appropriate onomatopoeia based on the non-verbal sounds. Onomatopoeia refers to words that phonetically imitate or suggest a non-verbal sound. Words like “bang,” “woof,” and “pop” are examples of onomatopoeia that refer to non-verbal sounds. Upon detecting a non-verbal sound, the augmented reality system may access an onomatopoeia library to select an appropriate onomatopoeia, and generates and causes display of a graphical element at a location in the GUI based on the source of the onomatopoeia.


Consider an illustrative example from a user perspective. A client device, executing an application of the augmented reality system, may display a presentation of a space (e.g., a basketball court, an office, a restroom, etc.), wherein the space includes one or more individuals (wherein each individual has a corresponding user profile). The augmented reality system may detect speech (e.g., through a microphone of the client device), and identify a source of the speech in the presentation of the space based on the techniques discussed above. For example, the augmented reality system may detect that facial landmarks of a first individual among the one or more individuals depicted in the presentation indicate that the first individual's mouth and lips were moving. Based on the facial landmarks, the augmented reality system may determine that the first individual is a source of the speech.


Having determined the source of the speech, the augmented reality system may transcribe the speech to a text string. In some example embodiments, the augmented reality system may also translate the speech to a different language based on preferences. For example, a user associated with the client device itself may specify language preferences indicating a first language, while the detected speech was in a second language. Based on the language preferences of the user associated with the client device, the augmented reality system may translate the detected speech from the second language to the first language.


The augmented reality system determines an emotional effect of the speech based on the techniques discussed above. For example, the augmented reality system may determine that based on the facial landmarks of the first individual, and definitions of the text string, the emotional effect of the speech is anger. The augmented reality system generates and causes display of a speech bubble based on a location of the first individual (the source of the speech) and the determined emotional effect. For example, the speech bubble and corresponding text may be stylized to indicate the emotional effect.



FIG. 1 is a block diagram showing an example messaging system 100 for exchanging data (e.g., messages and associated content) over a network. The messaging system 100 includes multiple client devices 102, each of which hosts a number of applications including a messaging client application 104. Each messaging client application 104 is communicatively coupled to other instances of the messaging client application 104 and a messaging server system 108 via a network 106 (e.g., the Internet).


Accordingly, each messaging client application 104 is able to communicate and exchange data with another messaging client application 104 and with the messaging server system 108 via the network 106. The data exchanged between messaging client applications 104, and between a messaging client application 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 106 to a particular messaging client application 104. While certain functions of the messaging system 100 are described herein as being performed by either a messaging client application 104 or by the messaging server system 108, it will be appreciated that the location of certain functionality either within the messaging client application 104 or the messaging server system 108 is 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 application 104 where a client device 102 has a sufficient processing capacity.


The messaging server system 108 supports various services and operations that are provided to the messaging client application 104. Such operations include transmitting data to, receiving data from, and processing data generated by the messaging client application 104. In some embodiments, this data includes, message content, client device information, geolocation information, media annotation and overlays, message content persistence conditions, social network information, and live event information, as examples. In other embodiments, other data is used. Data exchanges within the messaging system 100 are invoked and controlled through functions available via user interfaces (UIs) of the messaging client application 104.


Turning now specifically to the messaging server system 108, an Application Program Interface (API) server 110 is coupled to, and provides a programmatic interface to, an application server 112. The application server 112 is communicatively coupled to a database server(s) 118, which facilitates access to a database(s) 120 in which is stored data associated with messages processed by the application server 112.


Dealing specifically with the Application Program Interface (API) server 110, this server receives and transmits message data (e.g., commands and message payloads) between the client device 102 and the application server 112. Specifically, the Application Program Interface (API) server 110 provides a set of interfaces (e.g., routines and protocols) that can be called or queried by the messaging client application 104 in order to invoke functionality of the application server 112. The Application Program Interface (API) server 110 exposes various functions supported by the application server 112, including account registration, login functionality, the sending of messages, via the application server 112, from a particular messaging client application 104 to another messaging client application 104, the sending of media files (e.g., images or video) from a messaging client application 104 to the messaging server application 114, and for possible access by another messaging client application 104, the setting 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 adding and deletion of friends to a social graph, the location of friends within a social graph, opening and application event (e.g., relating to the messaging client application 104).


The application server 112 hosts a number of applications and subsystems, including a messaging server application 114, an image processing system 116, a social network system 122, and an augmented reality system 124. The augmented reality system 124 may be or include any instrumentality or aggregate of instrumentalities operable to compute, process, store, display, generate, communicate, or apply various forms of data for user profile building, audience derivation, control, or other purposes.


The messaging server application 114 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 application 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, by the messaging server application 114, to the messaging client application 104. Other processor and memory intensive processing of data may also be performed server-side by the messaging server application 114, in view of the hardware requirements for such processing.


The application server 112 also includes an image processing system 116 that is dedicated to performing various image processing operations, typically with respect to images or video received within the payload of a message at the messaging server application 114.


The social network system 122 supports various social networking functions services, and makes these functions and services available to the messaging server application 114. To this end, the social network system 122 maintains and accesses an entity graph 304 within the database(s) 120. Examples of functions and services supported by the social network system 122 include the identification of other users of the messaging system 100 with which a particular user has relationships or is “following,” and also the identification of other entities and interests of a particular user.


The augmented reality system 124 provides functionality to generate and cause display of augmented reality elements in a GUI, including speech bubbles, as well as graphical elements representative of onomatopoeia.


The application server 112 is communicatively coupled to one or more database server(s) 118, which facilitates access to a database(s) 120 in which is stored data associated with messages processed by the messaging server application 114.



FIG. 2 is block diagram illustrating further details regarding the messaging system 100, according to example embodiments. Specifically, the messaging system 100 is shown to comprise the messaging client application 104 and the application server 112, which in turn embody a number of some subsystems, namely an ephemeral timer system 202, a collection management system 204 and an annotation system 206.


The ephemeral timer system 202 is responsible for enforcing the temporary access to content permitted by the messaging client application 104 and the messaging server application 114. To this end, 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 SNAPCHAT story), selectively display and enable access to messages and associated content via the messaging client application 104. Further details regarding the operation of the ephemeral timer system 202 are provided below.


The collection management system 204 is responsible for managing collections of media (e.g., collections of text, image video and audio data). In some examples, 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 application 104.


The collection management system 204 furthermore includes a curation interface 208 that allows a collection manager to manage and curate a particular collection of content. For example, the curation interface 208 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 embodiments, compensation may be paid to a user for inclusion of user generated content into a collection. In such cases, the curation interface 208 operates to automatically make payments to such users for the use of their content.


The annotation system 206 provides various functions that enable a user to annotate or otherwise modify or edit media content associated with a message. For example, the annotation system 206 provides functions related to the generation and publishing of media overlays for messages processed by the messaging system 100. The annotation system 206 operatively supplies a media overlay (e.g., a SNAPCHAT filter) to the messaging client application 104 based on a geolocation of the client device 102. In another example, the annotation system 206 operatively supplies a media overlay to the messaging client application 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 including text that can be overlaid on top of a photograph generated 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 annotation system 206 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(s) 120 and accessed through the database server(s) 118.


In one example embodiment, the annotation system 206 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 annotation system 206 generates a media overlay that includes the uploaded content and associates the uploaded content with the selected geolocation.


In another example embodiment, the annotation system 206 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 annotation system 206 associates the media overlay of a highest bidding merchant with a corresponding geolocation for a predefined amount of time



FIG. 3 is a schematic diagram 300 illustrating data which may be stored in the database(s) 120 of the messaging server system 108, according to certain example embodiments. While the content of the database(s) 120 is shown to comprise a number of tables, it will be appreciated that the data could be stored in other types of data structures (e.g., as an object-oriented database).


The database(s) 120 includes message data stored within a message table 314. The entity table 302 stores entity data, including an entity graph 304. Entities for which records are maintained within the entity table 302 may include individuals, corporate entities, organizations, objects, places, events etc. Regardless of 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 304 furthermore 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 database(s) 120 also stores annotation data, in the example form of filters, in an annotation table 312. Filters for which data is stored within the annotation table 312 are associated with and applied to videos (for which data is stored in a video table 310) and/or images (for which data is stored in an image table 308). 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 varies types, including a user-selected filters from a gallery of filters presented to a sending user by the messaging client application 104 when the sending user is composing a message. Other types of filers 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 application 104, based on geolocation information determined by a GPS unit of the client device 102. Another type of filer is a data filer, which may be selectively presented to a sending user by the messaging client application 104, based on other inputs or information gathered by the client device 102 during the message creation process. Example 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 annotation data that may be stored within the image table 308 is so-called “lens” data. A “lens” may be a real-time special effect and sound that may be added to an image or a video.


As mentioned above, the video table 310 stores video data which, in one embodiment, is associated with messages for which records are maintained within the message table 314. Similarly, the image table 308 stores image data associated with messages for which message data is stored in the entity table 302. The entity table 302 may associate various annotations from the annotation table 312 with various images and videos stored in the image table 308 and the video table 310.


A story table 306 stores data regarding collections of messages and associated image, video or audio data, which are compiled into a collection (e.g., a SNAPCHAT 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 302) 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 application 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 varies 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 application 104, to contribute content to a particular live story. The live story may be identified to the user by the messaging client application 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 embodiments, 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).



FIG. 4 is a schematic diagram illustrating a structure of a message 400, according to some in some embodiments, generated by a messaging client application 104 for communication to a further messaging client application 104 or the messaging server application 114. The content of a particular message 400 is used to populate the message table 314 stored within the database(s) 120, accessible by the messaging server application 114. Similarly, the content of a message 400 is stored in memory as “in-transit” or “in-flight” data of the client device 102 or the application server 112. The message 400 is shown to include the following components:

    • A message identifier 402: a unique identifier that identifies the message 400.
    • A message text payload 404: text, to be generated by a user via a user interface of the client device 102 and that is included in the message 400.
    • A message image payload 406: image data, captured by a camera component of a client device 102 or retrieved from memory of a client device 102, and that is included in the message 400.
    • A message video payload 408: video data, captured by a camera component or retrieved from a memory component of the client device 102 and that is included in the message 400.
    • A message audio payload 410: audio data, captured by a microphone or retrieved from the memory component of the client device 102, and that is included in the message 400.
    • A message annotations 412: annotation data (e.g., filters, stickers or other enhancements) that represents annotations to be applied to message image payload 406, message video payload 408, or message audio payload 410 of the message 400.
    • A message duration parameter 414: parameter value indicating, in seconds, the amount of time for which content of the message (e.g., the message image payload 406, message video payload 408, message audio payload 410) is to be presented or made accessible to a user via the messaging client application 104.
    • A message geolocation parameter 416: geolocation data (e.g., latitudinal and longitudinal coordinates) associated with the content payload of the message. Multiple message geolocation parameter 416 values may be included in the payload, each of these parameter values being associated with respect to content items included in the content (e.g., a specific image into within the message image payload 406, or a specific video in the message video payload 408).
    • A message story identifier 418: identifier values identifying one or more content collections (e.g., “stories”) with which a particular content item in the message image payload 406 of the message 400 is associated. For example, multiple images within the message image payload 406 may each be associated with multiple content collections using identifier values.
    • A message tag 420: each message 400 may be tagged with multiple tags, each of which is indicative of the subject matter of content included in the message payload. For example, where a particular image included in the message image payload 406 depicts an animal (e.g., a lion), a tag value may be included within the message tag 420 that is indicative of the relevant animal. Tag values may be generated manually, based on user input, or may be automatically generated using, for example, image recognition.
    • A message sender identifier 422: an identifier (e.g., a messaging system identifier, email address or device identifier) indicative of a user of the client device 102 on which the message 400 was generated and from which the message 400 was sent
    • A message receiver identifier 424: an identifier (e.g., a messaging system identifier, email address or device identifier) indicative of a user of the client device 102 to which the message 400 is addressed.


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 308. Similarly, values within the message video payload 408 may point to data stored within a video table 310, values stored within the message annotations 412 may point to data stored in an annotation table 312, values stored within the message story identifier 418 may point to data stored in a story table 306, 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 302.



FIG. 5 is a schematic diagram illustrating an access-limiting process 500, in terms of which access to content (e.g., an ephemeral message 502, and associated multimedia payload of data) or a content collection (e.g., an ephemeral message story 504) may be time-limited (e.g., made ephemeral).


An ephemeral message 502 is shown to be associated with a message duration parameter 506, the value of which determines an amount of time that the ephemeral message 502 will be displayed to a receiving user of the ephemeral message 502 by the messaging client application 104. In one embodiment, where the messaging client application 104 is a SNAPCHAT application client, an ephemeral message 502 is viewable by a receiving user for up to a maximum of 10 seconds, depending on the amount of time that the sending user specifies using the message duration parameter 506.


The message duration parameter 506 and the message receiver identifier 424 are shown to be inputs to a message timer 512, which is responsible for determining the amount of time that the ephemeral message 502 is shown to a particular receiving user identified by the message receiver identifier 424. In particular, the ephemeral message 502 will only be shown to the relevant receiving user for a time period determined by the value of the message duration parameter 506. The message timer 512 is shown to provide output to a more generalized ephemeral timer system 202, which is responsible for the overall timing of display of content (e.g., an ephemeral message 502) to a receiving user.


The ephemeral message 502 is shown in FIG. 5 to be included within an ephemeral message story 504 (e.g., a personal SNAPCHAT story, or an event story). The ephemeral message story 504 has an associated story duration parameter 508, a value of which determines a time-duration for which the ephemeral message story 504 is presented and accessible to users of the messaging system 100. The story duration parameter 508, for example, may be the duration of a music concert, where the ephemeral message story 504 is a collection of content pertaining to that concert. Alternatively, a user (either the owning user or a curator user) may specify the value for the story duration parameter 508 when performing the setup and creation of the ephemeral message story 504.


Additionally, each ephemeral message 502 within the ephemeral message story 504 has an associated story participation parameter 510, a value of which determines the duration of time for which the ephemeral message 502 will be accessible within the context of the ephemeral message story 504. Accordingly, a particular ephemeral message story 504 may “expire” and become inaccessible within the context of the ephemeral message story 504, prior to the ephemeral message story 504 itself expiring in terms of the story duration parameter 508. The story duration parameter 508, story participation parameter 510, and message receiver identifier 424 each provide input to a story timer 514, which operationally determines, firstly, whether a particular ephemeral message 502 of the ephemeral message story 504 will be displayed to a particular receiving user and, if so, for how long. Note that the ephemeral message story 504 is also aware of the identity of the particular receiving user as a result of the message receiver identifier 424.


Accordingly, the story timer 514 operationally controls the overall lifespan of an associated ephemeral message story 504, as well as an individual ephemeral message 502 included in the ephemeral message story 504. In one embodiment, each and every ephemeral message 502 within the ephemeral message story 504 remains viewable and accessible for a time-period specified by the story duration parameter 508. In a further embodiment, a certain ephemeral message 502 may expire, within the context of ephemeral message story 504, based on a story participation parameter 510. Note that a message duration parameter 506 may still determine the duration of time for which a particular ephemeral message 502 is displayed to a receiving user, even within the context of the ephemeral message story 504. Accordingly, the message duration parameter 506 determines the duration of time that a particular ephemeral message 502 is displayed to a receiving user, regardless of whether the receiving user is viewing that ephemeral message 502 inside or outside the context of an ephemeral message story 504.


The ephemeral timer system 202 may furthermore operationally remove a particular ephemeral message 502 from the ephemeral message story 504 based on a determination that it has exceeded an associated story participation parameter 510. For example, when a sending user has established a story participation parameter 510 of 24 hours from posting, the ephemeral timer system 202 will remove the relevant ephemeral message 502 from the ephemeral message story 504 after the specified 24 hours. The ephemeral timer system 202 also operates to remove an ephemeral message story 504 either when the story participation parameter 510 for each and every ephemeral message 502 within the ephemeral message story 504 has expired, or when the ephemeral message story 504 itself has expired in terms of the story duration parameter 508.


In certain use cases, a creator of a particular ephemeral message story 504 may specify an indefinite story duration parameter 508. In this case, the expiration of the story participation parameter 510 for the last remaining ephemeral message 502 within the ephemeral message story 504 will determine when the ephemeral message story 504 itself expires. In this case, a new ephemeral message 502, added to the ephemeral message story 504, with a new story participation parameter 510, effectively extends the life of an ephemeral message story 504 to equal the value of the story participation parameter 510. The ephemeral message story may include a speech bubble displayed within a presentation of a space.


Responsive to the ephemeral timer system 202 determining that an ephemeral message story 504 has expired (e.g., is no longer accessible), the ephemeral timer system 202 communicates with the messaging system 100 (and, for example, specifically the messaging client application 104 to cause an indicium (e.g., an icon) associated with the relevant ephemeral message story 504 to no longer be displayed within a user interface of the messaging client application 104. Similarly, when the ephemeral timer system 202 determines that the message duration parameter 506 for a particular ephemeral message 502 has expired, the ephemeral timer system 202 causes the messaging client application 104 to no longer display an indicium (e.g., an icon or textual identification) associated with the ephemeral message 502. In some embodiments, the speech bubble may only be displayed for a period of time defined by the ephemeral timer system 202. For example, upon expiration of the time period, the speech bubble may vanish from a presentation of a space, and in further embodiments, may be replaced by a different speech bubble altogether.



FIG. 6 is a block diagram 600 illustrating one possible implementation of components of the augmented reality system 124. In various embodiments, such components configure the augmented reality system 124 to cause display of a presentation of a space, detect speech, identify a source of the speech, determine the location of a depiction of the source of the speech in the presentation of the space, transcribe the speech to a text string, generate a speech bubble based on the text string, and cause display of the speech bubble at a position in the presentation of the space. The augmented reality system 124 is shown as including a presentation module 602, a detection module 604, an identification module 606, and a transcription module 608, all, or some, configured to communicate with each other (e.g., via a bus, shared memory, or a switch). Any one or more of these modules may be implemented using one or more processors 610 (e.g., by configuring such one or more processors to perform functions described for that module) and hence may include one or more of the processors 610.


Any one or more of the modules described may be implemented using hardware alone (e.g., one or more of the processors 610 of a machine) or a combination of hardware and software. For example, any module described of the augmented reality system 124 may physically include an arrangement of one or more of the processors 610 (e.g., a subset of or among the one or more processors of the machine) configured to perform the operations described herein for that module. As another example, any module of the engagement tracking system 610 may include software, hardware, or both, that configure an arrangement of one or more processors 610 (e.g., among the one or more processors of the machine) to perform the operations described herein for that module. Accordingly, different modules of the engagement tracking system 610 may include and configure different arrangements of such processors 610 or a single arrangement of such processors 610 at different points in time. Moreover, any two or more modules of the augmented reality system 124 may be combined into a single module, and the functions described herein for a single module may be subdivided among multiple modules. Furthermore, according to various example embodiments, modules described herein as being implemented within a single machine, database, or device may be distributed across multiple machines, databases, or devices.



FIG. 7 is a flowchart illustrating various operations of the augmented reality system 124 in performing a method 700 for generating and causing display of a speech bubble in a graphical user interface, according to certain example embodiments. Operations of the method 700 may be performed by the modules described above with respect to FIG. 6. As shown in FIG. 7, the method 700 includes one or more operations 702, 704, 706, 708, 710 and 712. In some example embodiments, the method 700 may be performed by the augmented reality system 124 in real-time during a video chat between client devices. For example, as users of the client devices speak to one another, the method 700 may be performed to generate and cause display of speech bubbles within the corresponding displays of the client devices.


Operation 702 may be performed by the presentation module 602. At operation 702, the presentation module 602 generates and causes display of a presentation of a space at a client device (e.g., client device 102). For example, the client device 102 may have an integrated camera, and may capture and display an image of a space. The presentation of the space may include a depiction of a first person.


Operation 704 may be performed by the detection module 604. At operation 704, the detection module 604 detects sounds (e.g., via a microphone component of a mobile computing device) that include speech. The speech may include speech properties such as a volume, a cadence, a tone, as well as a length of the speech. For example, the detection module 604 may capture ambient sound, and detect speech in the ambient sound based on various speech detection techniques as discussed above. The detection module 604 may then extract the speech properties from the audio data that contains the speech.


Operation 706 may be performed by the identification module 606. At operation 706, the identification module 606 identifies the first person as a source of the speech. For example, the identification module 606 may detect movement of one or more facial landmarks of the first person based on the image of the space. The identification module 606 may determine that the facial landmarks of the first person indicate that their mouth was moving (i.e., indicating that they were speaking). Based on the facial landmarks of the first person indicating that a mouth of the first person was moving at the time that the speech was detected, the identification module 606 may determine that the first person was the source of the speech. In response to determining that the first person was the source of the speech, the identification module 606 determines a location of the first person in the image in order to appropriately place the speech bubble.


In further embodiments, the identification module 606 may employ speech recognition techniques to identify the first person as the source of the speech. For example, the first person may have an associated user profile that includes speech data, such that the first person may be identified based on the speech data. Upon detecting the speech, the identification module 606 may determine that based on the speech data and the speech, that the source of the speech is the first person. Upon determining that the source of the speech is the first person, the identification module 606 may determine that the image includes a depiction of the first person based on the facial landmark recognition data and the image data.


In instances where the source of the speech is a radio, television, telephone and/or mobile device, the identification module 606 may apply acoustic source localization techniques. Acoustic source localization include techniques for locating a source of a source given measurements of a sound field. For acoustic localization this means that if the source direction is measured at two or more locations in space, it is possible to triangulate its location. For example, the identification module 606 may record the speech as segments of audio data, wherein each segment of the audio data is recorded at a slightly different position, due to inherent movement of the recording device (e.g., a user holding a mobile phone will inadvertently move the mobile phone even slightly during recording). The identification module 606 determines a location of the speech based on triangulation of the segments of audio data. The identification module 606 therefore determines the source of the speech based on the location.


The sound field can be described using physical quantities like sound pressure and particle velocity. By measuring these properties it is (indirectly) possible to obtain a source direction.


Operation 708 may be performed by the transcription module 608. At operation 708, the transcription module 608 transcribes the speech to a text string. The transcription module 608 may reside within a client device 102, performing the transcription of the speech to text at the client device 102 itself, while in other example embodiments, the transcription module 608 may reside within a server system, remote from the client device 102, and delivering the transcribed speech to the client device 102.


In response to the detection module 604 detecting the speech, the transcription module 608 may record the speech to a database (e.g., database 120). In some example embodiments, the transcription module 608 may not record the speech to the database 120 at all, and may instead transcribe the speech to a text string in real time based on speech recognition technology known to persons of skill in the art.


In some example embodiments, the transcription module 608 determines appropriate punctuation to apply to the text string based on the speech properties, including the cadence of the speech. For example, based on the inflection of the speech, the transcription module 608 may select a comma, a question mark, period, exclamation point, ellipsis, or the like.


In some example embodiments, the transcription module 608 may translate the speech from a first language to a second language, based on a user language preference, or based on a user input specifying a translation request. For example, a user of the client device 102 may have an associated user profile that includes a language preference specifying a language (e.g., the second language). Upon detecting the speech, the detection module 604 determines that the speech is in a first language. The transcription module 608 may transcribe the speech into a text string, and translate the text string from the first language to the second language.


In further example embodiments, a user of the client device 102 may provide a user input specifying a translation request to translate the speech from the first language to a language specified by the user. For example, a user of the client device 102 may provide a user input requesting that the speech be translated from a first language to a second language specified by the user. In some embodiments, the transcription module 608 may automatically detect the language of the speech, while in other embodiments the user may specify the language of the speech as well as the language to translate the speech.


Operation 710 may be performed by the presentation module 602. At operation 710, the presentation module 602 generates a speech bubble that includes a presentation of the text string, based on the speech properties, a location of the source of the speech in the presentation, and the text string. The speech bubble may for example include a main body portion to include a presentation of the text string, and a tail portion to indicate a source of the speech. In instances where more than one sources of a speech have been identified, the presentation module 602 may generate a speech bubble that includes multiple tail portions, wherein each tail portion is directed at a source of the speech. In further embodiments, the shape of the speech bubble may be based on an emotional effect of the speech, wherein the emotional effect may be determined based on the speech properties.


The size of the speech bubble may be based on the length of the text string. For example, the presentation module 602 may generate the speech bubble such that the text string is entirely enclosed and encompassed by the speech bubble. In some example embodiments, the presentation module 602 may present only a portion of the text string at a given time by only displaying single sentences of the text string at a time, or by breaking the text string into portions based on natural pauses and breaks in the speech.


Operation 712 may be performed by the presentation module 602. At operations 712, the presentation module 602 causes display of the speech bubble at a position in the presentation of the space, based on the location of the source of the speech. In some example embodiments, the presentation module 602 identifies the position to display the speech bubble based on the location of the source of the speech, as well as locations of significant elements in the presentation. For example, the presentation module 602 may identify a position in the presentation of the space that does not include any significant elements (e.g., faces). The presentation module 602 may thereby display the speech bubble at the position without obstructing any significant elements in the presentation.



FIG. 8 is a diagram illustrating various operations of the augmented reality system 150 in performing a method 800 for generating the speech bubble based on an emotional effect, according to certain example embodiments. Operations of the method 800 may be performed by the modules described above with respect to FIG. 6. As shown in FIG. 8, the method 800 includes one or more operations 802, 804, and 806 that may be performed as part (e.g., a precursor task, a subroutine, or a portion) of the method 700, according to some example embodiments.


Operation 802 may be performed by the detection module 604. At operation 802, the detection module 802 determines an emotional effect of the speech based on one or more of the speech properties, facial recognition, and the speech itself. For example, to determine the emotional effect of the speech, the detection module 604 may apply facial landmark recognition techniques to analyze facial landmarks of a person identified as the source of the speech. In further embodiments, the detection module 604 determines the emotional effect of the speech based on the speech properties including the volume and cadence of the speech. For example, a high volume may indicate excitement or anger, while a low volume may indicate shyness.


In further embodiments, the detection module 604 may determine the emotional effect of the speech based on definitions of keywords in the context of the speech. For example, the detection module 604 may access the transcribed text string of the speech and determine definitions for each word of the text string. The detection module 604 may thereby compare the definitions of the speech to an emotional effect library, wherein the emotional effect library includes a set of emotions and corresponding words and definitions. The detection module 604 may thereby select an appropriate emotional effect based on the words and/or definitions.


Operation 804 may be performed by the presentation module 602. At operation 804, the presentation module 602 accesses a speech bubble library that includes a set of speech bubble themes. The speech bubble themes indicate a design and form to be applied to the speech bubble based on the emotional effect. For example, an emotional effect of “angry” may have a corresponding speech bubble theme that causes the speech bubble to display as a red jagged bubble, with red text and animated fire, while an emotional effect of “sad” may have a corresponding speech bubble theme that causes the speech bubble to display as a drooping blue bubble with frowny faces and black text. The speech bubble themes may also have corresponding graphical elements and icon to be displayed with the speech bubbles in the presentation of the space (e.g., hearts, smiley faces, frowny faces, etc.).


Operation 806 may be performed by the presentation module 602. At operation 806, the presentation module 602 selects a speech bubble theme based on the emotional effect.



FIG. 9 is a flowchart illustrating various operations of the augmented reality system 150 in performing a method 900 for causing display of a graphical element based on an onomatopoeia, according to certain example embodiments. Operations of the method 900 may be performed by the modules described above with respect to FIG. 6. As shown in FIG. 9, the method 900 includes one or more operations 902, 904, 906, and 908 that may be performed as part (e.g., a precursor task, a subroutine, or a portion) of the method 700, according to some example embodiments.


Operation 902 may be performed by the detection module 604. At operation 902, the detection module 604 detects a non-verbal sound. Non-verbal sounds may include noises described by onomatopoeic words, such as “boom,” “pop,” “snkit,” “meow,” “moo,” “woof woof,” and the like.


Operation 904 may be performed by the detection module 604. At operation 604, the detection module 604 compares the non-verbal sound to an onomatopoeia library that includes a list of onomatopoeic words. For example, the detection module 604 may record a wave form representative of the non-verbal sound and compare the wave form to a list of onomatopoeic words with corresponding wave forms in the onomatopoeia library.


Operation 906 may be performed by the detection module 604. At operation 906, the detection module 604 identifies an appropriate onomatopoeia from the onomatopoeia library based on the non-verbal sounds (e.g., the wave form representative of the non-verbal sound). In some example embodiments, the onomatopoeia library may include a list of graphical elements representative of their corresponding onomatopoetic word (e.g., an explosion for “boom”).


Operation 908 may be performed by the presentation module 602. At operation 908, the presentation module 602 causes display of the graphical element and the onomatopoetic word at a position in the presentation of the space. In some example embodiments, the detection module 604 may identify a location of the non-verbal sound. The presentation module 602 may cause display of the onomatopoetic word at a position based on the location of the non-verbal sound.



FIG. 10 is an example of an augmented reality interface 1000 configured to display a presentation 1010 of a space and a speech bubble 1020 generated by the augmented reality system 150, according to certain example embodiments. As shown, FIG. 10 includes the presentation 1010, speech bubble 1020, a first individual 1030, a text string 1040, and a second individual 1050.


As shown in FIG. 10, the presentation 1010 may include a depiction of the first individual 1030 and the second individual 1050, who may be engaged in a conversation. As discussed above, with respect to operations 704 and 706 of FIG. 7, the augmented reality system 150 detects and identifies a source of speech based on factors that may include facial landmarks of a user (e.g., the first user 1030), and/or speech and facial landmark recognition technology. As shown in FIG. 10, the augmented reality system 150 identified the first individual 1030 as the source of a speech.


As discussed in operation 708 of FIG. 7, the augmented reality system 150 transcribes the detected speech to a text string 1040, based on properties of the speech that include volume, cadence, tone, and a length of the speech. For example, the text string 1040 may be displayed in different fonts based on the speech properties for emphasis and/or to indicate an emotional effect of the speech. In some example embodiments, the first individual 1030 may have an associated user profile that includes display preferences that alter a presentation of the speech bubble 1020 and the text string 1040. The user profile may indicate that text strings associated with the user must be displayed in a specific font (e.g., Times New Roman, Wingdings, Algeria), specific color (e.g., blue, gold), specific language (e.g., English, Armenian, Chinese), etc. For example, in response to identifying the first individual 1030 as a source of the detected speech, the augmented reality system 150 may extract facial landmarks of the first individual 1030 to identify a corresponding user profile of the first individual 1030 based on speech and/or facial landmark recognition technology. The augmented reality system 150 may display the text string based on the user profile information and/or the speech properties.


The speech bubble 1020 is generated based on the speech properties and the presentation 1010. As discussed in operation 710 of FIG. 7, and the method 800 of FIG. 8, the augmented reality system 150 may generate and cause display of the speech bubble 1020 based on the speech properties of the detected speech, as well as the presentation 1010. For example, the presentation 1010 includes a depiction of the first individual 1030 and the second individual 1050 at positions in the presentation 1010. The augmented reality system 150 may identify an appropriate location in the presentation 1010 to display the speech bubble 1020 so that the speech bubble 1020 does not block or otherwise cover elements in the presentation 1010, including for example, the first individual 1030 and the second individual 1050. A size of the speech bubble 1020 may be based on available/unoccupied space in the presentation 1010, as well as based on speech properties.


Consider an illustrative explanation of FIG. 10, wherein a user of a client device 102 displays the presentation 1010 of the space. As shown in FIG. 10, the presentation 1010 includes a depiction of the first individual 1030 and the second individual 1050. As the first individual 1030 speaks, the augmented reality system 150 detects the speech and identifies the first individual 1030 as a source of the speech based on factors discussed above, including an indication that the first individual 1030 is speaking based on facial landmarks of the first individual 1030 (e.g., facial landmarks indicate that lips are moving). Upon identifying the first individual 1030 as the source of the detected speech, the augmented reality system 150 transcribes the speech to the text string 1040, and generates a speech bubble 1020 based on at least speech properties of the speech. In some example embodiments, the speech bubble 1020 may additionally be based on a length of the text string. The augmented reality system 150 displays the speech bubble 1020 at a position in the presentation 1010 based on the source of the speech and the available/unoccupied space, in real-time.



FIG. 11 is an example of an augmented reality interface 1100 configured to display an augmented reality speech bubble 1110, according to certain example embodiments. FIG. 11 includes a speech bubble 1110, an individual 1120, a text string 1130, and graphical elements 1140.


As discussed above, with respect to FIG. 8, the augmented reality system 150 may determine an emotional effect of the detected speech. In some example embodiments, the augmented reality system 150 may determine that the speech includes musical elements, indicating that the speech is singing, or a song. For example, the augmented reality system 150 may compare the detected speech to a musical library to determine if the speech matches an existing song. In response to a determination that the speech includes musical elements, the augmented reality system 150 may cause display of a graphical element to indicate that the speech has musical elements (e.g., graphical elements 1140 includes musical notes).


In some example embodiments as discussed above, the augmented reality system 150 generates the speech bubble 1110 based on speech properties and the emotional effect.



FIG. 12 is an example of an augmented reality interface 1200 configured to display augmented reality onomatopoeia 1210 as discussed in FIG. 9, according to certain example embodiments.


As discussed in FIG. 9, the augmented reality system 150 may detect a non-verbal sound, and compare the non-verbal sound to an onomatopoeia library. Upon comparing the non-verbal sound to the onomatopoeia library, the augmented reality system 150 may select an appropriate graphical element representative of the onomatopoeia to display in the augmented reality interface 1200.


In some example embodiments, the augmented reality system 150 may detect a source of the non-verbal sound based on image and video data, and/or based on audio location techniques. Audio location include techniques for performing accurate three-dimensional location sensing using audio hardware of a mobile device (e.g., client deice 102). In such embodiments, the time-of-flight of a sound is used to determine the accurate location of a source of the sound.


As depicted in FIG. 12, the augmented reality system 150 detects a non-verbal sound and identifies a location of a source of the non-verbal sound based on image and/or audio location techniques. For example, the augmented reality system 150 may detect a change in the image data that corresponds in time to the detection of the non-verbal sound. Based on the change in the image data occurring simultaneously, or near simultaneously, to the detection of the non-verbal sound, the augmented reality system 150 may determine a location of the sound.



FIG. 13 is a diagram illustrating various augmented reality speech bubbles 1300, according to certain example embodiments. FIG. 13 includes speech bubbles 1310, 1320, 1330, 1340, and 1350.


As discussed in operation 804 of FIG. 8, the augmented reality system 150 may select a speech bubble from a speech bubble library based on an emotional effect of the detected speech and the speech properties.


Software Architecture



FIG. 14 is a block diagram illustrating an example software architecture 1406, which may be used in conjunction with various hardware architectures herein described. FIG. 14 is a non-limiting example of a software architecture and it will be appreciated that many other architectures may be implemented to facilitate the functionality described herein. The software architecture 1406 may execute on hardware such as machine 1300 of FIG. 13 that includes, among other things, processors 1304, memory 1314, and I/O components 1318. A representative hardware layer 1452 is illustrated and can represent, for example, the machine 1400 of FIG. 14. The representative hardware layer 1452 includes a processing unit 1454 having associated executable instructions 1404. Executable instructions 1404 represent the executable instructions of the software architecture 1406, including implementation of the methods, components and so forth described herein. The hardware layer 1452 also includes memory and/or storage modules memory/storage 1456, which also have executable instructions 1404. The hardware layer 1452 may also comprise other hardware 1458.


In the example architecture of FIG. 14, the software architecture 1406 may be conceptualized as a stack of layers where each layer provides particular functionality. For example, the software architecture 1406 may include layers such as an operating system 1402, libraries 1420, applications 1416 and a presentation layer 1414. Operationally, the applications 1416 and/or other components within the layers may invoke application programming interface (API) API calls 1408 through the software stack and receive a response as in response to the API calls 1408. The layers illustrated are representative in nature and not all software architectures have all layers. For example, some mobile or special purpose operating systems may not provide a frameworks/middleware 1418, while others may provide such a layer. Other software architectures may include additional or different layers.


The operating system 1402 may manage hardware resources and provide common services. The operating system 1402 may include, for example, a kernel 1422, services 1424 and drivers 1426. The kernel 1422 may act as an abstraction layer between the hardware and the other software layers. For example, the kernel 1422 may be responsible for memory management, processor management (e.g., scheduling), component management, networking, security settings, and so on. The services 1424 may provide other common services for the other software layers. The drivers 1426 are responsible for controlling or interfacing with the underlying hardware. For instance, the drivers 1426 include display drivers, camera drivers, Bluetooth® drivers, flash memory drivers, serial communication drivers (e.g., Universal Serial Bus (USB) drivers), Wi-Fi® drivers, audio drivers, power management drivers, and so forth depending on the hardware configuration.


The libraries 1420 provide a common infrastructure that is used by the applications 1416 and/or other components and/or layers. The libraries 1420 provide functionality that allows other software components to perform tasks in an easier fashion than to interface directly with the underlying operating system 1402 functionality (e.g., kernel 1422, services 1424 and/or drivers 1426). The libraries 1420 may include system libraries 1444 (e.g., C standard library) that may provide functions such as memory allocation functions, string manipulation functions, mathematical functions, and the like. In addition, the libraries 1420 may include API libraries 1446 such as media libraries (e.g., libraries to support presentation and manipulation of various media format such as MPREG4, H.264, MP3, AAC, AMR, JPG, PNG), graphics libraries (e.g., an OpenGL framework that may be used to render 2D and 3D in a graphic content on a display), database libraries (e.g., SQLite that may provide various relational database functions), web libraries (e.g., WebKit that may provide web browsing functionality), and the like. The libraries 1420 may also include a wide variety of other libraries 1448 to provide many other APIs to the applications 1416 and other software components/modules.


The frameworks/middleware 1418 (also sometimes referred to as middleware) provide a higher-level common infrastructure that may be used by the applications 1416 and/or other software components/modules. For example, the frameworks/middleware 1418 may provide various graphic user interface (GUI) functions, high-level resource management, high-level location services, and so forth. The frameworks/middleware 1418 may provide a broad spectrum of other APIs that may be utilized by the applications 1416 and/or other software components/modules, some of which may be specific to a particular operating system 1402 or platform.


The applications 1416 include built-in applications 1438 and/or third-party applications 1440. Examples of representative built-in applications 1438 may include, but are not limited to, a contacts application, a browser application, a book reader application, a location application, a media application, a messaging application, and/or a game application. Third-party applications 1440 may include an application developed using the ANDROID™ or IOS™ software development kit (SDK) by an entity other than the vendor of the particular platform, and may be mobile software running on a mobile operating system such as IOS™, ANDROID™, WINDOWS® Phone, or other mobile operating systems. The third-party applications 1440 may invoke the API calls 1408 provided by the mobile operating system (such as operating system 1402) to facilitate functionality described herein.


The applications 1416 may use built in operating system functions (e.g., kernel 1422, services 1424 and/or drivers 1426), libraries 1420, and frameworks/middleware 1418 to create user interfaces to interact with users of the system. Alternatively, or additionally, in some systems interactions with a user may occur through a presentation layer, such as presentation layer 1414. In these systems, the application/component “logic” can be separated from the aspects of the application/component that interact with a user.



FIG. 15 is a block diagram illustrating components of a machine 1500, according to some example embodiments, able to read instructions from a machine-readable medium (e.g., a machine-readable storage medium) and perform any one or more of the methodologies discussed herein. Specifically, FIG. 15 shows a diagrammatic representation of the machine 1500 in the example form of a computer system, within which instructions 1510 (e.g., software, a program, an application, an applet, an app, or other executable code) for causing the machine 1500 to perform any one or more of the methodologies discussed herein may be executed. As such, the instructions 1510 may be used to implement modules or components described herein. The instructions 1510 transform the general, non-programmed machine 1500 into a particular machine 1500 programmed to carry out the described and illustrated functions in the manner described. In alternative embodiments, the machine 1500 operates as a standalone device or may be coupled (e.g., networked) to other machines. In a networked deployment, the machine 1500 may operate in the capacity of a server machine or a client machine in a server-client network environment, or as a peer machine in a peer-to-peer (or distributed) network environment. The machine 1500 may 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 smart phone, a mobile device, a wearable device (e.g., a smart watch), a smart home device (e.g., a smart appliance), other smart devices, a web appliance, a network router, a network switch, a network bridge, or any machine capable of executing the instructions 1510, sequentially or otherwise, that specify actions to be taken by machine 1500. Further, while only a single machine 1500 is illustrated, the term “machine” shall also be taken to include a collection of machines that individually or jointly execute the instructions 1510 to perform any one or more of the methodologies discussed herein.


The machine 1500 may include processors 1504, memory memory/storage 1506, and I/O components 1518, which may be configured to communicate with each other such as via a bus 1502. The memory/storage 1506 may include a memory 1514, such as a main memory, or other memory storage, and a storage unit 1516, both accessible to the processors 1504 such as via the bus 1502. The storage unit 1516 and memory 1514 store the instructions 1510 embodying any one or more of the methodologies or functions described herein. The instructions 1510 may also reside, completely or partially, within the memory 1514, within the storage unit 1516, within at least one of the processors 1504 (e.g., within the processor's cache memory), or any suitable combination thereof, during execution thereof by the machine 1500. Accordingly, the memory 1514, the storage unit 1516, and the memory of processors 1504 are examples of machine-readable media.


The I/O components 1518 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 1518 that are included in a particular machine 1500 will depend on the type of machine. For example, portable machines such as mobile phones will likely 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 1518 may include many other components that are not shown in FIG. 15. The I/O components 1518 are grouped according to functionality merely for simplifying the following discussion and the grouping is in no way limiting. In various example embodiments, the I/O components 1518 may include output components 1526 and input components 1528. The output components 1526 may include visual components (e.g., a display such as a plasma display panel (PDP), a light emitting diode (LED) display, a liquid crystal display (LCD), a projector, or a cathode ray tube (CRT)), acoustic components (e.g., speakers), haptic components (e.g., a vibratory motor, resistance mechanisms), other signal generators, and so forth. The input components 1528 may include alphanumeric input components (e.g., a keyboard, a touch screen configured to receive alphanumeric input, a photo-optical keyboard, or other alphanumeric input components), point based input components (e.g., a mouse, a touchpad, a trackball, a joystick, a motion sensor, or other pointing instrument), tactile input components (e.g., a physical button, a touch screen that provides location and/or force of touches or touch gestures, or other tactile input components), audio input components (e.g., a microphone), and the like.


In further example embodiments, the I/O components 1518 may include biometric components 1530, motion components 1534, environmental environment components 1536, or position components 1538 among a wide array of other components. For example, the biometric components 1530 may 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 1534 may include acceleration sensor components (e.g., accelerometer), gravitation sensor components, rotation sensor components (e.g., gyroscope), and so forth. The environment components 1536 may include, for example, illumination sensor components (e.g., photometer), temperature sensor components (e.g., one or more thermometer 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. The position components 1538 may include location sensor components (e.g., a Global Position system (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 1518 may include communication components 1540 operable to couple the machine 1500 to a network 1532 or devices 1520 via coupling 1522 and coupling 1524 respectively. For example, the communication components 1540 may include a network interface component or other suitable device to interface with the network 1532. In further examples, communication components 1540 may include wired communication components, wireless communication components, cellular communication components, Near Field Communication (NFC) components, Bluetooth® components (e.g., Bluetooth® Low Energy), Wi-Fi® components, and other communication components to provide communication via other modalities. The devices 1520 may be another machine or any of a wide variety of peripheral devices (e.g., a peripheral device coupled via a Universal Serial Bus (USB)).


Moreover, the communication components 1540 may detect identifiers or include components operable to detect identifiers. For example, the communication components 1540 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 1540, such as, location via Internet Protocol (IP) geo-location, location via Wi-Fi® signal triangulation, location via detecting a NFC beacon signal that may indicate a particular location, and so forth.


Glossary

“CARRIER SIGNAL” in this context 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 medium to facilitate communication of such instructions. Instructions may be transmitted or received over the network using a transmission medium via a network interface device and using any one of a number of well-known transfer protocols.


“CLIENT DEVICE” in this context 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, portable digital assistants (PDAs), smart phones, tablets, ultra books, netbooks, laptops, multi-processor systems, microprocessor-based or programmable consumer electronics, game consoles, set-top boxes, or any other communication device that a user may use to access a network.


“COMMUNICATIONS NETWORK” in this context 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 type 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.


“EPHEMERAL MESSAGE” in this context 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-READABLE MEDIUM” in this context refers to a component, device or other tangible media able to store instructions and data temporarily or permanently and may include, but is not be limited to, random-access memory (RAM), read-only memory (ROM), buffer memory, flash memory, optical media, magnetic media, cache memory, other types of storage (e.g., Erasable Programmable Read-Only Memory (EEPROM)) and/or any suitable combination thereof. The term “machine-readable medium” should be taken to include a single medium or multiple media (e.g., a centralized or distributed database, or associated caches and servers) able to store instructions. The term “machine-readable medium” shall also be taken to include any medium, or combination of multiple media, that is capable of storing instructions (e.g., code) for execution by a machine, such that the instructions, when executed by one or more processors of the machine, cause the machine to perform any one or more of the methodologies described herein. Accordingly, a “machine-readable medium” refers to a single storage apparatus or device, as well as “cloud-based” storage systems or storage networks that include multiple storage apparatus or devices. The term “machine-readable medium” excludes signals per se.


“COMPONENT” in this context refers to a device, physical entity or logic having boundaries defined by function or subroutine calls, branch points, application program interfaces (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 example embodiments, 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 Application Specific Integrated Circuit (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 embodiments 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 embodiments 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 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 Application Program Interface (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 example embodiments, 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 example embodiments, the processors or processor-implemented components may be distributed across a number of geographic locations.


“PROCESSOR” in this context refers to any circuit or virtual circuit (a physical circuit emulated by logic executing on an actual processor) that manipulates data values according to control signals (e.g., “commands”, “op codes”, “machine code”, etc.) and which produces corresponding output signals that are applied to operate a machine. A processor may, for example, be a Central Processing Unit (CPU), a Reduced Instruction Set Computing (RISC) processor, a Complex Instruction Set Computing (CISC) processor, a Graphics Processing Unit (GPU), a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Radio-Frequency Integrated Circuit (RFIC) or any combination thereof. A processor may further be a multi-core processor having two or more independent processors (sometimes referred to as “cores”) that may execute instructions contemporaneously.


“TIMESTAMP” in this context refers to a sequence of characters or encoded information identifying when a certain event occurred, for example giving date and time of day, sometimes accurate to a small fraction of a second.

Claims
  • 1. A system comprising: a memory; andat least one hardware processor coupled to the memory and comprising instructions that causes the system to perform operations comprising:causing display of a presentation of image data at a client device, the presentation of the image data comprising a depiction of a set of facial features;detecting, by the client device, a speech signal that comprises auditory properties;transcribing the speech signal to a text string based on the auditory properties;determining an emotional effect of the speech signal based on the set of facial features;selecting a graphical element based on the emotional effect; andcausing display of the text string within the graphical element within the presentation of the image data.
  • 2. The system of claim 1, wherein the auditory properties include a volume of the speech signal, and the determining the emotional effect is based on the set of facial features and the volume of the speech signal.
  • 3. The system of claim 1, wherein the graphical element includes a speech bubble that comprises a set of graphical properties, the graphical properties based on the auditory properties of the auditory signal.
  • 4. The system of claim 1, wherein the speech signal includes a non-verbal sound, and the operations further comprise: comparing the non-verbal sound to an onomatopoeia library in response to the detecting the speech signal;identifying an onomatopoeia from the onomatopoeia library based on the non-verbal sound; andselecting the graphical element based on at least the auditory properties of auditory signal and the onomatopoeia identified based on the non-verbal sound.
  • 5. The system of claim 1, wherein the speech signal corresponds with a source within the presentation of the image data, the source comprises a graphical property, and the operations further comprise: identifying the source of the speech signal within the presentation of the image data based on the auditory properties.
  • 6. The system of claim 5, wherein the selecting the graphical element is based on the emotional effect and the graphical property of the source of the speech signal.
  • 7. The system of claim 5, wherein the identifying the source of the speech signal within the presentation of the image data includes: detecting movement within the presentation of the image data; andidentifying the source of the speech signal based on the movement.
  • 8. A method comprising: causing display of a presentation of image data at a client device, the presentation of the image data comprising a depiction of a set of facial features;detecting, by the client device, a speech signal that comprises auditory properties;transcribing the speech signal to a text string based on the auditory properties;determining an emotional effect of the speech signal based on the set of facial features;selecting a graphical element based on the emotional effect; andcausing display of the text string within the graphical element within the presentation of the image data.
  • 9. The method of claim 8, wherein the auditory properties include a volume of the speech signal, and the determining the emotional effect is based on the set of facial features and the volume of the speech signal.
  • 10. The method of claim 8, wherein the graphical element includes a speech bubble that comprises a set of graphical properties, the graphical properties based on the auditory properties of the auditory signal.
  • 11. The method of claim 8, wherein the speech signal includes a non-verbal sound, and the method further comprises: comparing the non-verbal sound to an onomatopoeia library in response to the detecting the speech signal;identifying an onomatopoeia from the onomatopoeia library based on the non-verbal sound; andselecting the graphical element based on at least the auditory properties of auditory signal and the onomatopoeia identified based on the non-verbal sound.
  • 12. The method of claim 8, wherein the speech signal corresponds with a source within the presentation of the image data, the source comprises a graphical property, and the method further comprises: identifying the source of the speech signal within the presentation of the image data based on the auditory properties.
  • 13. The method of claim 12, wherein the selecting the graphical element is based on the emotional effect and the graphical property of the source of the speech signal.
  • 14. The method of claim 12, wherein the identifying the source of the speech signal within the presentation of the image data includes: detecting movement within the presentation of the image data; andidentifying the source of the speech signal based on the movement.
  • 15. A non-transitory machine-readable storage medium comprising instructions that, when executed by one or more processors of a machine, cause the machine to perform operations including: causing display of a presentation of image data at a client device, the presentation of the image data comprising a depiction of a set of facial features;detecting, by the client device, a speech signal that comprises auditory properties;transcribing the speech signal to a text string based on the auditory properties;determining an emotional effect of the speech signal based on the set of facial features;selecting a graphical element based on the emotional effect; andcausing display of the text string within the graphical element within the presentation of the image data.
  • 16. The non-transitory machine-readable storage medium of claim 15, wherein the auditory properties include a volume of the speech signal, and the determining the emotional effect is based on the set of facial features and the volume of the speech signal.
  • 17. The non-transitory machine-readable storage medium of claim 15, wherein the graphical element includes a speech bubble that comprises a set of graphical properties, the graphical properties based on the auditory properties of the auditory signal.
  • 18. The non-transitory machine-readable storage medium of claim 15, wherein the speech signal includes a non-verbal sound, and the operations further comprise: comparing the non-verbal sound to an onomatopoeia library in response to the detecting the speech signal;identifying an onomatopoeia from the onomatopoeia library based on the non-verbal sound; andselecting the graphical element based on at least the auditory properties of auditory signal and the onomatopoeia identified based on the non-verbal sound.
  • 19. The non-transitory machine-readable storage medium of claim 15, wherein the speech signal corresponds with a source within the presentation of the image data, the source comprises a graphical property, and the operations further comprise: identifying the source of the speech signal within the presentation of the image data based on the auditory properties.
  • 20. The non-transitory machine-readable storage medium of claim 19, wherein the selecting the graphical element is based on the emotional effect and the graphical property of the source of the speech signal.
PRIORITY

This application is a continuation of and claims the benefit of priority of U.S. patent application Ser. No. 16/749,678, filed on Jan. 22, 2020, which is a continuation of and claims the benefit of priority of U.S. patent application Ser. No. 16/014,193, filed on Jun. 21, 2018, which is a continuation of and claims the benefit of priority of U.S. patent application Ser. No. 15/437,018, filed on Feb. 20, 2017, which are hereby incorporated by reference herein in their entirety.

US Referenced Citations (775)
Number Name Date Kind
666223 Shedlock Jan 1901 A
4581634 Williams Apr 1986 A
4975690 Torres Dec 1990 A
5072412 Henderson, Jr. et al. Dec 1991 A
5361205 Nishino et al. Nov 1994 A
5493692 Theimer et al. Feb 1996 A
5699444 Palm Dec 1997 A
5713073 Warsta Jan 1998 A
5754939 Herz et al. May 1998 A
5855008 Goldhaber et al. Dec 1998 A
5883639 Walton et al. Mar 1999 A
5999932 Paul Dec 1999 A
6009190 Szeliski et al. Dec 1999 A
6012098 Bayeh et al. Jan 2000 A
6014090 Rosen et al. Jan 2000 A
6029141 Bezos et al. Feb 2000 A
6038295 Mattes Mar 2000 A
6049711 Yehezkel et al. Apr 2000 A
6154764 Nitta et al. Nov 2000 A
6158044 Tibbetts Dec 2000 A
6167435 Druckenmiller et al. Dec 2000 A
6204840 Petelycky et al. Mar 2001 B1
6205432 Gabbard et al. Mar 2001 B1
6216141 Straub et al. Apr 2001 B1
6285381 Sawano et al. Sep 2001 B1
6285987 Roth et al. Sep 2001 B1
6310694 Okimoto et al. Oct 2001 B1
6317789 Rakavy et al. Nov 2001 B1
6334149 Davis, Jr. et al. Dec 2001 B1
6349203 Asaoka et al. Feb 2002 B1
6353170 Eyzaguirre et al. Mar 2002 B1
6446004 Cao et al. Sep 2002 B1
6449657 Stanbach et al. Sep 2002 B2
6456852 Bar et al. Sep 2002 B2
6484196 Maurille Nov 2002 B1
6487586 Ogilvie et al. Nov 2002 B2
6487601 Hubacher et al. Nov 2002 B1
6523008 Avrunin Feb 2003 B1
6525731 Suits et al. Feb 2003 B1
6542749 Tanaka et al. Apr 2003 B2
6549768 Fraccaroli Apr 2003 B1
6618593 Drutman et al. Sep 2003 B1
6622174 Ukita et al. Sep 2003 B1
6631463 Floyd et al. Oct 2003 B1
6636247 Hamzy et al. Oct 2003 B1
6636855 Holloway et al. Oct 2003 B2
6643684 Malkin et al. Nov 2003 B1
6658095 Yoakum et al. Dec 2003 B1
6665531 Soderbacka et al. Dec 2003 B1
6668173 Greene Dec 2003 B2
6684238 Dutta Jan 2004 B1
6684257 Camut et al. Jan 2004 B1
6698020 Zigmond et al. Feb 2004 B1
6700506 Winkler Mar 2004 B1
6701347 Ogilvie Mar 2004 B1
6711608 Ogilvie Mar 2004 B1
6720860 Narayanaswami Apr 2004 B1
6724403 Santoro et al. Apr 2004 B1
6757713 Ogilvie et al. Jun 2004 B1
6832222 Zimowski Dec 2004 B1
6834195 Brandenberg et al. Dec 2004 B2
6836792 Chen Dec 2004 B1
6898626 Ohashi May 2005 B2
6959324 Kubik et al. Oct 2005 B1
6970088 Kovach Nov 2005 B2
6970907 Ullmann et al. Nov 2005 B1
6980909 Root et al. Dec 2005 B2
6981040 Konig et al. Dec 2005 B1
7020494 Spriestersbach et al. Mar 2006 B2
7027124 Foote et al. Apr 2006 B2
7072963 Anderson et al. Jul 2006 B2
7085571 Kalhan et al. Aug 2006 B2
7110744 Freeny, Jr. Sep 2006 B2
7124164 Chemtob Oct 2006 B1
7149893 Leonard et al. Dec 2006 B1
7173651 Knowles Feb 2007 B1
7188143 Szeto Mar 2007 B2
7203380 Chiu et al. Apr 2007 B2
7206568 Sudit Apr 2007 B2
7227937 Yoakum et al. Jun 2007 B1
7237002 Estrada et al. Jun 2007 B1
7240089 Boudreau Jul 2007 B2
7243163 Friend et al. Jul 2007 B1
7269426 Kokkonen et al. Sep 2007 B2
7278168 Chaudhury et al. Oct 2007 B1
7280658 Amini et al. Oct 2007 B2
7315823 Brondrup Jan 2008 B2
7349768 Bruce et al. Mar 2008 B2
7356564 Hartselle et al. Apr 2008 B2
7376715 Cunningham et al. May 2008 B2
7394345 Ehlinger et al. Jul 2008 B1
7411493 Smith Aug 2008 B2
7423580 Markhovsky et al. Sep 2008 B2
7454442 Cobleigh et al. Nov 2008 B2
7478402 Christensen et al. Jan 2009 B2
7496347 Puranik Feb 2009 B2
7508419 Toyama et al. Mar 2009 B2
7512649 Faybishenko et al. Mar 2009 B2
7519670 Hagale et al. Apr 2009 B2
7535890 Rojas May 2009 B2
7546554 Chiu et al. Jun 2009 B2
7607096 Oreizy et al. Oct 2009 B2
7639943 Kalajan Dec 2009 B1
7650231 Gadler Jan 2010 B2
7668537 DeVries Feb 2010 B2
7703140 Nath et al. Apr 2010 B2
7720554 Dibernardo et al. May 2010 B2
7737965 Alter et al. Jun 2010 B2
7770137 Forbes et al. Aug 2010 B2
7778973 Choi Aug 2010 B2
7779444 Glad Aug 2010 B2
7787886 Markhovsky et al. Aug 2010 B2
7796946 Eisenbach Sep 2010 B2
7801954 Cadiz et al. Sep 2010 B2
7856360 Kramer et al. Dec 2010 B2
7912896 Wolovitz et al. Mar 2011 B2
8001204 Burtner et al. Aug 2011 B2
8032586 Challenger et al. Oct 2011 B2
8082255 Carlson, Jr. et al. Dec 2011 B1
8090351 Klein Jan 2012 B2
8098904 Ioffe et al. Jan 2012 B2
8099109 Altman et al. Jan 2012 B2
8112716 Kobayashi Feb 2012 B2
8131597 Hudetz Mar 2012 B2
8135166 Rhoads Mar 2012 B2
8136028 Loeb et al. Mar 2012 B1
8146001 Reese Mar 2012 B1
8161115 Yamamoto Apr 2012 B2
8161417 Lee Apr 2012 B1
8170957 Richard May 2012 B2
8183997 Wong et al. May 2012 B1
8195203 Tseng Jun 2012 B1
8199747 Rojas et al. Jun 2012 B2
8208943 Petersen Jun 2012 B2
8214443 Hamburg Jul 2012 B2
8230258 Yamagami Jul 2012 B2
8234350 Gu et al. Jul 2012 B1
8238947 Lottin et al. Aug 2012 B2
8244593 Klinger et al. Aug 2012 B2
8276092 Narayanan et al. Sep 2012 B1
8279319 Date Oct 2012 B2
8280406 Ziskind et al. Oct 2012 B2
8285199 Hsu et al. Oct 2012 B2
8287380 Nguyen et al. Oct 2012 B2
8301159 Hamynen et al. Oct 2012 B2
8306922 Kunal et al. Nov 2012 B1
8312086 Velusamy et al. Nov 2012 B2
8312097 Siegel et al. Nov 2012 B1
8326315 Phillips et al. Dec 2012 B2
8326327 Hymel et al. Dec 2012 B2
8332475 Rosen et al. Dec 2012 B2
8352546 Dollard Jan 2013 B1
8379130 Forutanpour et al. Feb 2013 B2
8385950 Wagner et al. Feb 2013 B1
8402097 Szeto Mar 2013 B2
8405773 Hayashi et al. Mar 2013 B2
8418067 Cheng et al. Apr 2013 B2
8423409 Rao Apr 2013 B2
8471914 Sakiyama et al. Jun 2013 B2
8472935 Fujisaki Jun 2013 B1
8502903 Kashitani Aug 2013 B2
8510383 Hurley et al. Aug 2013 B2
8525825 Zhu et al. Sep 2013 B2
8527345 Rothschild et al. Sep 2013 B2
8554627 Svendsen et al. Oct 2013 B2
8560612 Kilmer et al. Oct 2013 B2
8564710 Nonaka et al. Oct 2013 B2
8570907 Garcia, Jr. et al. Oct 2013 B2
8594680 Ledlie et al. Nov 2013 B2
8601380 Vaittinen et al. Dec 2013 B2
8613089 Holloway et al. Dec 2013 B1
8660358 Bergboer et al. Feb 2014 B1
8660369 Llano et al. Feb 2014 B2
8660793 Ngo et al. Feb 2014 B2
8676623 Gale et al. Mar 2014 B2
8682350 Altman et al. Mar 2014 B2
8712776 Bellegarda et al. Apr 2014 B2
8718333 Wolf et al. May 2014 B2
8724622 Rojas May 2014 B2
8732168 Johnson May 2014 B2
8744523 Fan et al. Jun 2014 B2
8745132 Obradovich Jun 2014 B2
8761800 Kuwahara Jun 2014 B2
8761811 Alonzo Jun 2014 B2
8768876 Shim et al. Jul 2014 B2
8775972 Spiegel Jul 2014 B2
8788680 Naik Jul 2014 B1
8790187 Walker et al. Jul 2014 B2
8797415 Arnold Aug 2014 B2
8798646 Wang et al. Aug 2014 B1
8856349 Jain et al. Oct 2014 B2
8874677 Rosen et al. Oct 2014 B2
8886227 Schmidt et al. Nov 2014 B2
8909679 Root et al. Dec 2014 B2
8909714 Agarwal et al. Dec 2014 B2
8909725 Sehn Dec 2014 B1
8914752 Spiegel Dec 2014 B1
8933966 Oi et al. Jan 2015 B2
8965460 Rao et al. Feb 2015 B1
8972357 Shim et al. Mar 2015 B2
8995433 Rojas Mar 2015 B2
9015285 Ebsen et al. Apr 2015 B1
9020745 Johnston et al. Apr 2015 B2
9031283 Arth et al. May 2015 B2
9040574 Wang et al. May 2015 B2
9055416 Rosen et al. Jun 2015 B2
9058687 Kruglick Jun 2015 B2
9083770 Drose et al. Jul 2015 B1
9094137 Sehn et al. Jul 2015 B1
9098926 Quan et al. Aug 2015 B2
9100806 Rosen et al. Aug 2015 B2
9100807 Rosen et al. Aug 2015 B2
9113301 Spiegel et al. Aug 2015 B1
9119027 Sharon et al. Aug 2015 B2
9123074 Jacobs et al. Sep 2015 B2
9129432 Quan et al. Sep 2015 B2
9143382 Bhogal et al. Sep 2015 B2
9143681 Ebsen et al. Sep 2015 B1
9148424 Yang Sep 2015 B1
9152477 Campbell et al. Oct 2015 B1
9191776 Root et al. Nov 2015 B2
9204252 Root Dec 2015 B2
9225805 Kujawa et al. Dec 2015 B2
9225897 Sehn et al. Dec 2015 B1
9237202 Sehn Jan 2016 B1
9240074 Berkovich et al. Jan 2016 B2
9258459 Hartley Feb 2016 B2
9264463 Rubinstein et al. Feb 2016 B2
9276886 Samaranayake Mar 2016 B1
9294425 Son Mar 2016 B1
9317133 Korah et al. Apr 2016 B2
9317921 Chao et al. Apr 2016 B2
9344606 Hartley et al. May 2016 B2
9355123 Wnuk et al. May 2016 B2
9361283 Jones et al. Jun 2016 B2
9385983 Sehn Jul 2016 B1
9396354 Murphy et al. Jul 2016 B1
9407712 Sehn Aug 2016 B1
9407816 Sehn Aug 2016 B1
9430783 Sehn Aug 2016 B1
9439041 Parvizi et al. Sep 2016 B2
9443227 Evans et al. Sep 2016 B2
9450907 Pridmore et al. Sep 2016 B2
9459778 Hogeg et al. Oct 2016 B2
9465816 Johnson et al. Oct 2016 B2
9477368 Filip et al. Oct 2016 B1
9482882 Hanover et al. Nov 2016 B1
9482883 Meisenholder Nov 2016 B1
9489661 Evans et al. Nov 2016 B2
9491134 Rosen et al. Nov 2016 B2
9495783 Samarasekera et al. Nov 2016 B1
9498720 Geisner et al. Nov 2016 B2
9532171 Allen et al. Dec 2016 B2
9537811 Allen et al. Jan 2017 B2
9560006 Prado et al. Jan 2017 B2
9628950 Noeth et al. Apr 2017 B1
9652896 Jurgenson et al. May 2017 B1
9659244 Anderton et al. May 2017 B2
9693191 Sehn Jun 2017 B2
9705831 Spiegel Jul 2017 B2
9710821 Heath Jul 2017 B2
9742713 Spiegel et al. Aug 2017 B2
9761045 Cote et al. Sep 2017 B1
9785796 Murphy et al. Oct 2017 B1
9805020 Gorman et al. Oct 2017 B2
9825898 Sehn Nov 2017 B2
9836890 Jurgenson et al. Dec 2017 B2
9854219 Sehn Dec 2017 B2
9922431 Gray et al. Mar 2018 B2
9961520 Brooks et al. May 2018 B2
9965895 Gray May 2018 B1
9984499 Jurgenson et al. May 2018 B1
10074381 Cowburn Sep 2018 B1
10074981 Faley et al. Sep 2018 B2
10102680 Jurgenson et al. Oct 2018 B2
10304237 Sequeira et al. May 2019 B2
10319149 Cowburn et al. Jun 2019 B1
10366543 Jurgenson et al. Jul 2019 B1
10387730 Cowburn et al. Aug 2019 B1
10497158 Jain et al. Dec 2019 B2
10592095 Kasemset Mar 2020 B2
10614828 Cowburn Apr 2020 B1
10657708 Jurgenson et al. May 2020 B1
10733802 Jurgenson et al. Aug 2020 B2
10997783 Jurgenson et al. May 2021 B2
11189299 Cowburn Nov 2021 B1
11222325 Van Os Jan 2022 B2
11315331 Jurgenson et al. Apr 2022 B2
20020047868 Miyazawa Apr 2002 A1
20020078456 Hudson et al. Jun 2002 A1
20020087631 Sharma Jul 2002 A1
20020097257 Miller et al. Jul 2002 A1
20020122659 Mcgrath et al. Sep 2002 A1
20020128047 Gates Sep 2002 A1
20020144154 Tomkow Oct 2002 A1
20030001846 Davis et al. Jan 2003 A1
20030016247 Lai et al. Jan 2003 A1
20030017823 Mager et al. Jan 2003 A1
20030020623 Cao et al. Jan 2003 A1
20030023874 Prokupets et al. Jan 2003 A1
20030037124 Yamaura et al. Feb 2003 A1
20030040899 Ogilvie Feb 2003 A1
20030050785 Friedrich et al. Mar 2003 A1
20030052925 Daimon et al. Mar 2003 A1
20030101044 Krasnov May 2003 A1
20030101230 Benschoter et al. May 2003 A1
20030110503 Perkes Jun 2003 A1
20030126215 Udell Jul 2003 A1
20030133041 Curtis et al. Jul 2003 A1
20030148773 Spriestersbach et al. Aug 2003 A1
20030164856 Prager et al. Sep 2003 A1
20030217106 Adar et al. Nov 2003 A1
20030229607 Zellweger et al. Dec 2003 A1
20040027371 Jaeger Feb 2004 A1
20040064429 Hirstius et al. Apr 2004 A1
20040078367 Anderson et al. Apr 2004 A1
20040095357 Oh et al. May 2004 A1
20040111467 Willis Jun 2004 A1
20040158739 Wakai et al. Aug 2004 A1
20040189465 Capobianco et al. Sep 2004 A1
20040203959 Coombes Oct 2004 A1
20040215625 Svendsen et al. Oct 2004 A1
20040243531 Dean Dec 2004 A1
20040243688 Wugofski Dec 2004 A1
20050021444 Bauer et al. Jan 2005 A1
20050022211 Veselov et al. Jan 2005 A1
20050048989 Jung Mar 2005 A1
20050052339 Sprague Mar 2005 A1
20050078804 Yomoda Apr 2005 A1
20050097176 Schatz et al. May 2005 A1
20050102381 Jiang et al. May 2005 A1
20050104976 Currans May 2005 A1
20050114783 Szeto May 2005 A1
20050119936 Buchanan et al. Jun 2005 A1
20050122405 Voss et al. Jun 2005 A1
20050162523 Darrell et al. Jul 2005 A1
20050193340 Amburgey et al. Sep 2005 A1
20050193345 Klassen et al. Sep 2005 A1
20050198128 Anderson Sep 2005 A1
20050223066 Buchheit et al. Oct 2005 A1
20050288954 McCarthy et al. Dec 2005 A1
20060001758 Nam et al. Jan 2006 A1
20060026067 Nicholas et al. Feb 2006 A1
20060107297 Toyama et al. May 2006 A1
20060114338 Rothschild Jun 2006 A1
20060119882 Harris et al. Jun 2006 A1
20060242239 Morishima et al. Oct 2006 A1
20060252438 Ansamaa et al. Nov 2006 A1
20060265417 Amato et al. Nov 2006 A1
20060270419 Crowley et al. Nov 2006 A1
20060287878 Wadhwa et al. Dec 2006 A1
20070004426 Pfleging et al. Jan 2007 A1
20070038715 Collins et al. Feb 2007 A1
20070040931 Nishizawa Feb 2007 A1
20070064899 Boss et al. Mar 2007 A1
20070073517 Panje Mar 2007 A1
20070073823 Cohen et al. Mar 2007 A1
20070075898 Markhovsky et al. Apr 2007 A1
20070082707 Flynt et al. Apr 2007 A1
20070136228 Petersen Jun 2007 A1
20070192128 Celestini Aug 2007 A1
20070198340 Lucovsky et al. Aug 2007 A1
20070198495 Buron et al. Aug 2007 A1
20070208751 Cowan et al. Sep 2007 A1
20070210936 Nicholson Sep 2007 A1
20070214180 Crawford Sep 2007 A1
20070214216 Carrer et al. Sep 2007 A1
20070233556 Koningstein Oct 2007 A1
20070233801 Eren et al. Oct 2007 A1
20070233859 Zhao et al. Oct 2007 A1
20070243887 Bandhole et al. Oct 2007 A1
20070244750 Grannan et al. Oct 2007 A1
20070255456 Funayama Nov 2007 A1
20070281690 Altman et al. Dec 2007 A1
20080022329 Glad Jan 2008 A1
20080025701 Ikeda Jan 2008 A1
20080032703 Krumm et al. Feb 2008 A1
20080033930 Warren Feb 2008 A1
20080043041 Hedenstroem et al. Feb 2008 A2
20080049704 Witteman et al. Feb 2008 A1
20080055269 Lemay et al. Mar 2008 A1
20080062141 Chandhri Mar 2008 A1
20080076505 Ngyen et al. Mar 2008 A1
20080088623 Bukowski et al. Apr 2008 A1
20080092233 Tian et al. Apr 2008 A1
20080094387 Chen Apr 2008 A1
20080104503 Beall et al. May 2008 A1
20080109844 Baldeschweiler et al. May 2008 A1
20080120409 Sun et al. May 2008 A1
20080147730 Lee et al. Jun 2008 A1
20080148150 Mall Jun 2008 A1
20080158230 Sharma et al. Jul 2008 A1
20080168033 Ott et al. Jul 2008 A1
20080168489 Schraga Jul 2008 A1
20080189177 Anderton et al. Aug 2008 A1
20080207176 Brackbill et al. Aug 2008 A1
20080208692 Garaventi et al. Aug 2008 A1
20080021421 Rasanen et al. Sep 2008 A1
20080222545 Lemay Sep 2008 A1
20080255976 Altberg et al. Oct 2008 A1
20080256446 Yamamoto Oct 2008 A1
20080256577 Funaki et al. Oct 2008 A1
20080266421 Takahata et al. Oct 2008 A1
20080270938 Carlson Oct 2008 A1
20080288338 Wiseman et al. Nov 2008 A1
20080306826 Kramer et al. Dec 2008 A1
20080313329 Wang et al. Dec 2008 A1
20080313346 Kujawa et al. Dec 2008 A1
20080318616 Chipalkatti et al. Dec 2008 A1
20090006191 Arankalle et al. Jan 2009 A1
20090006565 Velusamy et al. Jan 2009 A1
20090015703 Kim et al. Jan 2009 A1
20090024956 Kobayashi Jan 2009 A1
20090030774 Rothschild et al. Jan 2009 A1
20090030999 Gatzke et al. Jan 2009 A1
20090040324 Nonaka Feb 2009 A1
20090042588 Lottin et al. Feb 2009 A1
20090058822 Chaudhri Mar 2009 A1
20090079846 Chou Mar 2009 A1
20090008971 Wood et al. Apr 2009 A1
20090089678 Sacco et al. Apr 2009 A1
20090093261 Ziskind Apr 2009 A1
20090132341 Klinger May 2009 A1
20090132453 Hangartner et al. May 2009 A1
20090132665 Thomsen et al. May 2009 A1
20090148045 Lee et al. Jun 2009 A1
20090153492 Popp Jun 2009 A1
20090157450 Athsani et al. Jun 2009 A1
20090157752 Gonzalez Jun 2009 A1
20090160970 Fredlund et al. Jun 2009 A1
20090163182 Gatti et al. Jun 2009 A1
20090177299 Van De Sluis Jul 2009 A1
20090192900 Collision Jul 2009 A1
20090199242 Johnson et al. Aug 2009 A1
20090215469 Fisher et al. Aug 2009 A1
20090232354 Camp, Jr. et al. Sep 2009 A1
20090234815 Boerries et al. Sep 2009 A1
20090239552 Churchill et al. Sep 2009 A1
20090249222 Schmidt et al. Oct 2009 A1
20090249244 Robinson et al. Oct 2009 A1
20090265647 Martin et al. Oct 2009 A1
20090288022 Almstrand et al. Nov 2009 A1
20090291672 Treves et al. Nov 2009 A1
20090292608 Polachek Nov 2009 A1
20090293012 Alter et al. Nov 2009 A1
20090319607 Belz et al. Dec 2009 A1
20090327073 Li Dec 2009 A1
20100062794 Han Mar 2010 A1
20100082427 Burgener et al. Apr 2010 A1
20100082693 Hugg et al. Apr 2010 A1
20100100568 Papin et al. Apr 2010 A1
20100113065 Narayan et al. May 2010 A1
20100130233 Parker May 2010 A1
20100131880 Lee et al. May 2010 A1
20100131895 Wohlert May 2010 A1
20100153144 Miller et al. Jun 2010 A1
20100159944 Pascal et al. Jun 2010 A1
20100161658 Hamynen et al. Jun 2010 A1
20100161831 Haas et al. Jun 2010 A1
20100162138 Pascal Jun 2010 A1
20100162149 Sheleheda et al. Jun 2010 A1
20100183280 Beauregard et al. Jul 2010 A1
20100185552 Deluca et al. Jul 2010 A1
20100185665 Horn et al. Jul 2010 A1
20100191631 Weidmann Jul 2010 A1
20100197318 Petersen et al. Aug 2010 A1
20100197319 Petersen et al. Aug 2010 A1
20100198683 Aarabi Aug 2010 A1
20100198694 Muthukrishnan Aug 2010 A1
20100198826 Petersen et al. Aug 2010 A1
20100198828 Petersen et al. Aug 2010 A1
20100198862 Jennings et al. Aug 2010 A1
20100198870 Petersen et al. Aug 2010 A1
20100198917 Petersen et al. Aug 2010 A1
20100201482 Robertson et al. Aug 2010 A1
20100201536 Robertson et al. Aug 2010 A1
20100214436 Kim et al. Aug 2010 A1
20100223128 Dukellis et al. Sep 2010 A1
20100223343 Bosan et al. Sep 2010 A1
20100250109 Johnston et al. Sep 2010 A1
20100257196 Waters et al. Oct 2010 A1
20100259386 Holley et al. Oct 2010 A1
20100273509 Sweeney et al. Oct 2010 A1
20100281045 Dean Nov 2010 A1
20100287485 Bertolami et al. Nov 2010 A1
20100306669 Della Pasqua Dec 2010 A1
20100316280 Lancaster et al. Dec 2010 A1
20110004071 Faiola et al. Jan 2011 A1
20110010205 Richards Jan 2011 A1
20110029512 Folgner et al. Feb 2011 A1
20110040783 Uemichi et al. Feb 2011 A1
20110040804 Peirce et al. Feb 2011 A1
20110050909 Ellenby et al. Mar 2011 A1
20110050915 Wang et al. Mar 2011 A1
20110064388 Brown et al. Mar 2011 A1
20110066743 Hurley et al. Mar 2011 A1
20110083101 Sharon et al. Apr 2011 A1
20110096093 Oi et al. Apr 2011 A1
20110099507 Nesladek et al. Apr 2011 A1
20110102630 Rukes May 2011 A1
20110119133 Igelman et al. May 2011 A1
20110137881 Cheng et al. Jun 2011 A1
20110145564 Moshir et al. Jun 2011 A1
20110159890 Fortescue et al. Jun 2011 A1
20110164163 Bilbrey et al. Jul 2011 A1
20110197194 D'Angelo et al. Aug 2011 A1
20110202598 Evans et al. Aug 2011 A1
20110202968 Nurmi Aug 2011 A1
20110211534 Schmidt et al. Sep 2011 A1
20110213845 Logan et al. Sep 2011 A1
20110215966 Kim et al. Sep 2011 A1
20110225048 Nair Sep 2011 A1
20110238763 Shin et al. Sep 2011 A1
20110255736 Thompson et al. Oct 2011 A1
20110270584 Plocher et al. Nov 2011 A1
20110273575 Lee Nov 2011 A1
20110279446 Castro et al. Nov 2011 A1
20110279453 Murphy et al. Nov 2011 A1
20110282799 Huston Nov 2011 A1
20110283188 Farrenkopf Nov 2011 A1
20110286586 Saylor et al. Nov 2011 A1
20110314419 Dunn et al. Dec 2011 A1
20110320373 Lee et al. Dec 2011 A1
20120028659 Whitney et al. Feb 2012 A1
20120033718 Kauffman et al. Feb 2012 A1
20120036015 Sheikh Feb 2012 A1
20120036443 Ohmori et al. Feb 2012 A1
20120041722 Quan et al. Feb 2012 A1
20120054797 Skog et al. Mar 2012 A1
20120059722 Rao Mar 2012 A1
20120062805 Candelore Mar 2012 A1
20120069233 Nonaka et al. Mar 2012 A1
20120084731 Filman et al. Apr 2012 A1
20120084835 Thomas et al. Apr 2012 A1
20120086727 Korah et al. Apr 2012 A1
20120099800 Llano et al. Apr 2012 A1
20120108293 Law et al. May 2012 A1
20120110096 Smarr et al. May 2012 A1
20120113143 Adhikari et al. May 2012 A1
20120113272 Hata May 2012 A1
20120122570 Baronoff May 2012 A1
20120123830 Svendsen et al. May 2012 A1
20120123871 Svendsen et al. May 2012 A1
20120123875 Svendsen et al. May 2012 A1
20120124126 Alcazar et al. May 2012 A1
20120124176 Curtis et al. May 2012 A1
20120124458 Cruzada May 2012 A1
20120131507 Sparandara et al. May 2012 A1
20120131512 Takeuchi et al. May 2012 A1
20120001651 Lalancette et al. Jun 2012 A1
20120143760 Abulafia et al. Jun 2012 A1
20120146991 Bala et al. Jun 2012 A1
20120150978 Monaco Jun 2012 A1
20120166971 Sachson et al. Jun 2012 A1
20120169855 Oh Jul 2012 A1
20120172062 Altman et al. Jul 2012 A1
20120173991 Roberts et al. Jul 2012 A1
20120176401 Hayward et al. Jul 2012 A1
20120181330 Kim Jul 2012 A1
20120184248 Speede Jul 2012 A1
20120197724 Kendall Aug 2012 A1
20120200743 Blanchflower et al. Aug 2012 A1
20120209921 Adafin et al. Aug 2012 A1
20120209924 Evans et al. Aug 2012 A1
20120210244 De Francisco Lopez et al. Aug 2012 A1
20120212509 Benko et al. Aug 2012 A1
20120212632 Mate et al. Aug 2012 A1
20120220264 Kawabata Aug 2012 A1
20120226748 Bosworth et al. Sep 2012 A1
20120233000 Fisher et al. Sep 2012 A1
20120236162 Imamura Sep 2012 A1
20120239761 Linner et al. Sep 2012 A1
20120250951 Chen Oct 2012 A1
20120252418 Kandekar et al. Oct 2012 A1
20120254325 Majeti et al. Oct 2012 A1
20120278387 Garcia et al. Nov 2012 A1
20120278692 Shi Nov 2012 A1
20120290637 Perantatos et al. Nov 2012 A1
20120297451 Ozzie Nov 2012 A1
20120299954 Wada et al. Nov 2012 A1
20120304052 Tanaka et al. Nov 2012 A1
20120304080 Wormald et al. Nov 2012 A1
20120307096 Ford et al. Dec 2012 A1
20120307112 Kunishige et al. Dec 2012 A1
20120314040 Kopf et al. Dec 2012 A1
20120319904 Lee et al. Dec 2012 A1
20120323933 He et al. Dec 2012 A1
20120324018 Metcalf et al. Dec 2012 A1
20130002649 Wu et al. Jan 2013 A1
20130006759 Srivastava et al. Jan 2013 A1
20130024757 Doll et al. Jan 2013 A1
20130036364 Johnson Feb 2013 A1
20130045753 Obermeyer et al. Feb 2013 A1
20130050260 Reitan Feb 2013 A1
20130055083 Fino Feb 2013 A1
20130057587 Leonard et al. Mar 2013 A1
20130059607 Herz et al. Mar 2013 A1
20130060690 Oskolkov et al. Mar 2013 A1
20130060911 Nagaraj et al. Mar 2013 A1
20130063369 Malhotra et al. Mar 2013 A1
20130067027 Song et al. Mar 2013 A1
20130071093 Hanks et al. Mar 2013 A1
20130080254 Thramann Mar 2013 A1
20130085790 Palmer et al. Apr 2013 A1
20130086072 Peng et al. Apr 2013 A1
20130090171 Holton et al. Apr 2013 A1
20130095857 Garcia et al. Apr 2013 A1
20130104053 Thornton et al. Apr 2013 A1
20130110885 Brundrett, III May 2013 A1
20130111514 Slavin et al. May 2013 A1
20130128059 Kristensson May 2013 A1
20130129252 Lauper May 2013 A1
20130132477 Bosworth et al. May 2013 A1
20130141419 Mount et al. Jun 2013 A1
20130145286 Feng et al. Jun 2013 A1
20130159110 Rajaram et al. Jun 2013 A1
20130159919 Leydon Jun 2013 A1
20130169680 Chien et al. Jul 2013 A1
20130169822 Zhu et al. Jul 2013 A1
20130173729 Starenky et al. Jul 2013 A1
20130181971 Mueller Jul 2013 A1
20130182133 Tanabe Jul 2013 A1
20130185131 Sinha et al. Jul 2013 A1
20130187952 Berkovich et al. Jul 2013 A1
20130191198 Carlson et al. Jul 2013 A1
20130194164 Sugden et al. Aug 2013 A1
20130194301 Robbins et al. Aug 2013 A1
20130198176 Kim Aug 2013 A1
20130215101 Duan Aug 2013 A1
20130218965 Abrol et al. Aug 2013 A1
20130218968 Mcevilly et al. Aug 2013 A1
20130222323 Mckenzie Aug 2013 A1
20130227476 Frey Aug 2013 A1
20130232194 Knapp et al. Sep 2013 A1
20130263031 Oshiro et al. Oct 2013 A1
20130265450 Barnes, Jr. Oct 2013 A1
20130267253 Case et al. Oct 2013 A1
20130275505 Gauglitz et al. Oct 2013 A1
20130290443 Collins et al. Oct 2013 A1
20130304646 De Geer Nov 2013 A1
20130308822 Marimon et al. Nov 2013 A1
20130311255 Cummins et al. Nov 2013 A1
20130325964 Berberat Dec 2013 A1
20130344896 Kirmse et al. Dec 2013 A1
20130346869 Asver et al. Dec 2013 A1
20130346877 Borovoy et al. Dec 2013 A1
20140006129 Heath Jan 2014 A1
20140011538 Mulcahy et al. Jan 2014 A1
20140019264 Wachman et al. Jan 2014 A1
20140029798 Flynn et al. Jan 2014 A1
20140032682 Prado et al. Jan 2014 A1
20140043204 Basnayake et al. Feb 2014 A1
20140045530 Gordon et al. Feb 2014 A1
20140047016 Rao Feb 2014 A1
20140047045 Baldwin et al. Feb 2014 A1
20140047335 Lewis et al. Feb 2014 A1
20140049652 Moon et al. Feb 2014 A1
20140052485 Shidfar Feb 2014 A1
20140052633 Gandhi Feb 2014 A1
20140057660 Wager Feb 2014 A1
20140064624 Kim et al. Mar 2014 A1
20140081634 Forutanpour Mar 2014 A1
20140082651 Sharifi Mar 2014 A1
20140086727 Xu Mar 2014 A1
20140092130 Anderson et al. Apr 2014 A1
20140096029 Schultz Apr 2014 A1
20140114565 Aziz et al. Apr 2014 A1
20140122658 Haeger et al. May 2014 A1
20140122787 Shalvi et al. May 2014 A1
20140125668 Steed et al. May 2014 A1
20140129207 Bailey et al. May 2014 A1
20140129953 Spiegel May 2014 A1
20140143143 Fasoli et al. May 2014 A1
20140149519 Redfern et al. May 2014 A1
20140155102 Cooper et al. Jun 2014 A1
20140173424 Hogeg et al. Jun 2014 A1
20140173457 Wang et al. Jun 2014 A1
20140189592 Benchenaa et al. Jul 2014 A1
20140201527 Krivorot Jul 2014 A1
20140207679 Cho Jul 2014 A1
20140214471 Schreiner, III Jul 2014 A1
20140222564 Kranendonk et al. Aug 2014 A1
20140232743 Na et al. Aug 2014 A1
20140258405 Perkin Sep 2014 A1
20140265359 Cheng et al. Sep 2014 A1
20140266703 Dalley, Jr. et al. Sep 2014 A1
20140277735 Breazeal Sep 2014 A1
20140279061 Elimeliah et al. Sep 2014 A1
20140279436 Dorsey et al. Sep 2014 A1
20140279540 Jackson Sep 2014 A1
20140280537 Pridmore et al. Sep 2014 A1
20140282096 Rubinstein et al. Sep 2014 A1
20140287779 O'keefe et al. Sep 2014 A1
20140289833 Briceno Sep 2014 A1
20140306986 Gottesman et al. Oct 2014 A1
20140317302 Naik Oct 2014 A1
20140324627 Haver et al. Oct 2014 A1
20140324629 Jacobs Oct 2014 A1
20140325383 Brown et al. Oct 2014 A1
20140359024 Spiegel Dec 2014 A1
20140359032 Spiegel et al. Dec 2014 A1
20150020086 Chen et al. Jan 2015 A1
20150040074 Hofmann et al. Feb 2015 A1
20150046278 Pei et al. Feb 2015 A1
20150071619 Brough Mar 2015 A1
20150087263 Branscomb et al. Mar 2015 A1
20150088622 Ganschow et al. Mar 2015 A1
20150092038 Jantunen Apr 2015 A1
20150095020 Leydon Apr 2015 A1
20150096042 Mizrachi Apr 2015 A1
20150116529 Wu et al. Apr 2015 A1
20150169827 Laborde Jun 2015 A1
20150172534 Miyakawa et al. Jun 2015 A1
20150178257 Jones et al. Jun 2015 A1
20150178260 Brunson Jun 2015 A1
20150193982 Mihelich et al. Jul 2015 A1
20150199082 Scholler et al. Jul 2015 A1
20150222814 Li et al. Aug 2015 A1
20150227602 Ramu et al. Aug 2015 A1
20150261917 Smith Sep 2015 A1
20150312184 Langholz et al. Oct 2015 A1
20150347854 Bare et al. Dec 2015 A1
20150350136 Flynn, III et al. Dec 2015 A1
20150365795 Allen et al. Dec 2015 A1
20150378502 Hu et al. Dec 2015 A1
20160006927 Sehn Jan 2016 A1
20160014063 Hogeg et al. Jan 2016 A1
20160019270 Jones et al. Jan 2016 A1
20160021038 Woo Jan 2016 A1
20160021039 Woo Jan 2016 A1
20160085773 Chang et al. Mar 2016 A1
20160085863 Allen et al. Mar 2016 A1
20160086670 Gross et al. Mar 2016 A1
20160099901 Allen et al. Apr 2016 A1
20160180887 Sehn Jun 2016 A1
20160182422 Sehn et al. Jun 2016 A1
20160182875 Sehn Jun 2016 A1
20160239248 Sehn Aug 2016 A1
20160253710 Publicover et al. Sep 2016 A1
20160266386 Scott et al. Sep 2016 A1
20160277419 Allen et al. Sep 2016 A1
20160321708 Sehn Nov 2016 A1
20160352791 Adams et al. Dec 2016 A1
20160359957 Laliberte Dec 2016 A1
20160359987 Laliberte Dec 2016 A1
20160371884 Benko et al. Dec 2016 A1
20170006094 Abou Mahmoud et al. Jan 2017 A1
20170061308 Chen et al. Mar 2017 A1
20170124713 Jurgenson et al. May 2017 A1
20170161382 Ouimet et al. Jun 2017 A1
20170161558 Ludwigsen et al. Jun 2017 A1
20170228878 Goldman et al. Aug 2017 A1
20170237789 Harner et al. Aug 2017 A1
20170243371 Jurgenson et al. Aug 2017 A1
20170263029 Yan et al. Sep 2017 A1
20170287006 Azmoodeh et al. Oct 2017 A1
20170295250 Samaranayake et al. Oct 2017 A1
20170374003 Allen et al. Dec 2017 A1
20170374508 Davis et al. Dec 2017 A1
20180005450 Daniels et al. Jan 2018 A1
20180061127 Gullicksen Mar 2018 A1
20180089904 Jurgenson et al. Mar 2018 A1
20180096502 Kansara Apr 2018 A1
20180300916 Barnett Oct 2018 A1
20180300917 Barnett Oct 2018 A1
20190068529 Mullins Feb 2019 A1
20190073832 Kim Mar 2019 A1
20190138597 Dowell May 2019 A1
20190156534 Chen et al. May 2019 A1
20190295326 Jurgenson et al. Sep 2019 A1
20190347323 Riesa et al. Nov 2019 A1
20200219312 Jurgenson et al. Jul 2020 A1
20200327738 Jurgenson et al. Oct 2020 A1
20210174578 Jurgenson et al. Jun 2021 A1
20220245907 Jurgenson et al. Aug 2022 A1
Foreign Referenced Citations (53)
Number Date Country
2887596 Jul 2015 CA
101893935 Nov 2010 CN
103471580 Dec 2013 CN
103513951 Jan 2014 CN
104428817 Mar 2015 CN
104899920 Sep 2015 CN
104995583 Oct 2015 CN
2051480 Apr 2009 EP
2151797 Feb 2010 EP
3369076 Sep 2018 EP
2399928 Sep 2004 GB
19990073076 Oct 1999 KR
20010078417 Aug 2001 KR
20110071210 Jun 2011 KR
20120061696 Jun 2012 KR
20130091991 Aug 2013 KR
20130137063 Dec 2013 KR
102052018 Dec 2019 KR
102205689 Jan 2021 KR
WO-1996024213 Aug 1996 WO
WO-1999063453 Dec 1999 WO
WO-2000058882 Oct 2000 WO
WO-2001029642 Apr 2001 WO
WO-2001050703 Jul 2001 WO
WO-2006118755 Nov 2006 WO
WO-2007092668 Aug 2007 WO
WO-2009043020 Apr 2009 WO
WO-2011040821 Apr 2011 WO
WO-2011119407 Sep 2011 WO
WO-2012000107 Jan 2012 WO
WO-2013008238 Jan 2013 WO
WO-2013008251 Jan 2013 WO
WO-2013045753 Apr 2013 WO
WO-2014006129 Jan 2014 WO
WO-2014011346 Jan 2014 WO
WO-2014068573 May 2014 WO
WO-2014115136 Jul 2014 WO
WO-2014194262 Dec 2014 WO
WO-2015192026 Dec 2015 WO
WO-2016044424 Mar 2016 WO
WO-2016054562 Apr 2016 WO
WO-2016065131 Apr 2016 WO
WO-2016100318 Jun 2016 WO
WO-2016100318 Jun 2016 WO
WO-2016100342 Jun 2016 WO
WO-2016112299 Jul 2016 WO
WO-2016149594 Sep 2016 WO
WO-2016179166 Nov 2016 WO
WO-2016179235 Nov 2016 WO
WO-2017075476 May 2017 WO
WO-2017176739 Oct 2017 WO
WO-2017176992 Oct 2017 WO
WO-2018005644 Jan 2018 WO
Non-Patent Literature Citations (153)
Entry
U.S. Appl. No. 14/954,090 U.S. Pat. No. 9,652,896, filed Nov. 30, 2015, Image Based Tracking in Augmented Reality Systems.
U.S. Appl. No. 15/591,887 U.S. Pat. No. 9,836,890, filed May 10, 2017, Image Based Tracking in Augmented Reality Systems.
U.S. Appl. No. 15/830,965 U.S. Pat. No. 10,102,680, filed Dec. 4, 2017, Image Based Tracking in Augmented Reality Systems.
U.S. Appl. No. 16/136,849 U.S. Pat. No. 10,366,543, filed Sep. 20, 2018, Image Based Tracking in Augmented Reality Systems.
U.S. Appl. No. 16/438,226 U.S. Pat. No. 10,733,802, filed Jun. 11, 2019, Image Based Tracking in Augmented Reality Systems.
U.S. Appl. No. 16/913,503, filed Jun. 26, 2020, Image Based Tracking in Augmented Reality Systems.
U.S. Appl. No. 15/437,018 U.S. Pat. No. 10,074,381, filed Feb. 20, 2017, Augmented Reality Speech Balloon System.
U.S. Appl. No. 16/014,193 U.S. Pat. No. 10,614,828, filed Jun. 21, 2018, Augmented Reality Speech Balloon System.
U.S. Appl. No. 16/749,678, filed Jan. 22, 2020, Augmented Reality Speech Balloon System.
“U.S. Appl. No. 15/971,566, Notice of Allowability dated Apr. 13, 2020”, 2 pgs.
“U.S. Appl. No. 16/265,382, Non Final Office Action dated Mar. 3, 2020”, 18 pgs.
“U.S. Appl. No. 16/277,626, Examiner Interview Summary dated Apr. 7, 2020”, 3 pgs.
“U.S. Appl. No. 16/277,626, Final Office Action dated Feb. 22, 2021”, 18 pgs.
“U.S. Appl. No. 16/277,626, Final Office Action dated May 18, 2020”, 30 pgs.
“U.S. Appl. No. 16/277,626, Final Office Action dated Aug. 10, 2020”, 35 pgs.
“U.S. Appl. No. 16/277,626, Final Office Action dated Aug. 20, 2021”, 24 pgs.
“U.S. Appl. No. 16/277,626, Non Final Office Action dated Mar. 24, 2020”, 28 pgs.
“U.S. Appl. No. 16/277,626, Non Final Office Action dated Jul. 12, 2021”, 20 pgs.
“U.S. Appl. No. 16/277,626, Non Final Office Action dated Jul. 13, 2020”, 34 pgs.
“U.S. Appl. No. 16/277,626, Non Final Office Action dated Nov. 30, 2020”, 19 pgs.
“U.S. Appl. No. 16/277,626, Response filed Jan. 28, 2021 to Non Final Office Action dated Nov. 30, 2020”, 9 pgs.
“U.S. Appl. No. 16/277,626, Response filed Apr. 28, 2020 to Non Final Office Action dated Mar. 24, 2020”, 12 pgs.
“U.S. Appl. No. 16/277,626, Response filed May 11, 2021 to Final Office Action dated Feb. 22, 2021”, 10 pgs.
“U.S. Appl. No. 16/277,626, Response filed May 29, 2020 to Final Office Action dated May 18, 2020”, 12 pgs.
“U.S. Appl. No. 16/277,626, Response filed Jul. 16, 2020 to Non Final Office Action dated Jul. 13, 2020”, 10 pgs.
“U.S. Appl. No. 16/277,626, Response filed Aug. 10, 2021 to Non Final Office Action dated Jul. 12, 2021”, 9 pgs.
“U.S. Appl. No. 16/277,626, Response filed Aug. 19, 2020 to Final Office Action dated Aug. 10, 2020”, 10 pgs.
“U.S. Appl. No. 16/433,793, Final Office Action dated Apr. 30, 2021”, 9 pgs.
“U.S. Appl. No. 16/433,793, Non Final Office Action dated Jan. 21, 2021”, 26 pgs.
“U.S. Appl. No. 16/433,793, Notice of Allowance dated Aug. 6, 2021”, 14 pgs.
“U.S. Appl. No. 16/433,793, Response filed Apr. 21, 2021 to Non Final Office Action dated Jan. 21, 2021”, 12 pgs.
“U.S. Appl. No. 16/433,793, Response filed Jun. 30, 2021 to Final Office Action dated Apr. 30, 2021”, 9 pgs.
“U.S. Appl. No. 16/824,297, Notice of Allowance dated Dec. 30, 2020”, 9 pgs.
“U.S. Appl. No. 16/824,297, Supplemental Notice of Allowability dated Jan. 25, 2021”, 2 pgs.
“U.S. Appl. No. 16/824,297, Supplemental Notice of Allowability dated Feb. 18, 2021”, 2 pgs.
“U.S. Appl. No. 16/913,503, 312 Amendment filed Mar. 23, 2022”, 9 pgs.
“U.S. Appl. No. 16/913,503, Notice of Allowance dated Dec. 23, 2021”, 8 pgs.
“U.S. Appl. No. 16/913,503, PTO Response to Rule 312 Communication dated Apr. 1, 2022”, 2 pgs.
“Chinese Application Serial No. 201680035045.X, Office Action dated Mar. 24, 2021”, w/o English Translation, 19 pgs.
“Chinese Application Serial No. 201680035045.X, Office Action dated Aug. 5, 2020”, w/English Translation, 11 pgs.
“Chinese Application Serial No. 201680035045.X, Response filed Dec. 18, 2020 to Office Action dated Aug. 5, 2020”, w/ English Claims, 50 pgs.
“European Application Serial No. 16795488.2, Communication Pursuant to Article 94(3) EPC dated Jun. 30, 2021”, 6 pgs.
“European Application Serial No. 16795488.2, Communication Pursuant to Article 94(3) EPC dated Nov. 11, 2020”, 6 pgs.
“European Application Serial No. 16795488.2, Response filed Mar. 22, 2021 to Communication Pursuant to Article 94(3) EPC dated Nov. 11, 2020”, 23 pgs.
“Korean Application Serial No. 10-2019-7035272, Notice of Preliminary Rejection dated Feb. 5, 2020”, w/ English Translation, 9 pgs.
“Korean Application Serial No. 10-2019-7035272, Response filed May 4, 2020 to Notice of Preliminary Rejection dated Feb. 5, 2020”, w/ English Claims, 21 pgs.
Nahar, Prakhar, et al., “Autonomous UAV Forced Graffiti Detection and Removal System Based on Machine Learning”, IEEE 2017 SmartWorld/SCALCOM/UIC/ATC/CBDCom/IOP/SCI, (2017), 8 pgs.
Narhare, Ashwini D, et al., “Trademark detection using SIFT features matching”, IEEE 2015 International Conference on Computing Communication Control and Automation, (2015), 684-688.
Sheikh, MD. Abdul Alim, et al., “Traffic Sign Detection and Classification using Colour Feature and Neural Network”, IEEE 2016 International Conference on Intelligent Control Power and Instrumentation (ICICPI), (2016), 307-311.
Wei, Guan, “Hybrid methods for robust image matching and its applications in augmented reality”, PhD diss., University of Southern California, (2014), 131 pgs.
“A Whole New Story”, Snap, Inc., [Online] Retrieved from the Internet: <URL: https://www.snap.com/en-US/news/>, (2017), 13 pgs.
“Adding photos to your listing”, eBay, [Online] Retrieved from the Internet: <URL: http://pages.ebay.com/help/sell/pictures.html>, (accessed May 24, 2017), 4 pgs.
“U.S. Appl. No. 14/053,913, Response filed Nov. 13, 2017 to Non Final Office Action dated Jun. 12, 2017”, 11 pgs.
“U.S. Appl. No. 14/953,913, Non Final Office Action dated Jun. 12, 2017”, 35 pgs.
“U.S. Appl. No. 14/953,913, Notice of Allowance dated Jan. 30, 2018”, 23 pgs.
“U.S. Appl. No. 14/954,090, Corrected Notice of Allowance dated Feb. 3, 2017”, 4 pgs.
“U.S. Appl. No. 14/954,090, Corrected Notice of Allowance dated Apr. 18, 2017”, 4 pgs.
“U.S. Appl. No. 14/954,090, Notice of Allowance dated Jan. 11, 2017”, 11 pgs.
“U.S. Appl. No. 14/954,090, Preliminary Amendment filed Dec. 28, 2016”, 10 pgs.
“U.S. Appl. No. 15/436,363, Examiner Interview Summary dated Nov. 28, 2018”, 3 pgs.
“U.S. Appl. No. 15/436,363, Non Final Office Action dated Oct. 9, 2018”, 15 pgs.
“U.S. Appl. No. 15/436,363, Notice of Allowance dated Jan. 29, 2019”, 8 pgs.
“U.S. Appl. No. 15/436,363, Response filed Nov. 28, 2018 to Non Final Office Action dated Oct. 9, 2018”, 15 pgs.
“U.S. Appl. No. 15/437,018, Corrected Notice of Allowability dated Jul. 11, 2018”, 2 pgs.
“U.S. Appl. No. 15/437,018, Corrected Notice of Allowance dated Jun. 6, 2018”, 5 pgs.
“U.S. Appl. No. 15/437,018, Examiner Interview Summary dated Feb. 16, 2018”, 3 pgs.
“U.S. Appl. No. 15/437,018, Non Final Office Action dated Jan. 26, 2018”, 9 pgs.
“U.S. Appl. No. 15/437,018, Notice of Allowance dated May 18, 2018”, 7 pgs.
“U.S. Appl. No. 15/437,018, Response Filed Mar. 21, 2018 to Non Final Office Action dated Jan. 26, 2018”, 9 pgs.
“U.S. Appl. No. 15/492,089, Corrected Notice of Allowability dated May 24, 2019”, 2 pgs.
“U.S. Appl. No. 15/492,089, Non Final Office Action dated Jan. 25, 2019”, 7 pgs.
“U.S. Appl. No. 15/492,089, Notice of Allowance dated Apr. 4, 2019”, 9 pgs.
“U.S. Appl. No. 15/492,089, Response filed Feb. 26, 2019 to Non Final Office Action dated Jan. 25, 2019”, 11 pgs.
“U.S. Appl. No. 15/591,887, Corrected Notice of Allowance dated Sep. 8, 2017”, 4 pgs.
“U.S. Appl. No. 15/591,887, Notice of Allowance dated Aug. 25, 2017”, 10 pgs.
“U.S. Appl. No. 15/591,887, Preliminary Amendment filed Jun. 12, 2017”, 10 pgs.
“U.S. Appl. No. 15/591,887, PTO Response to Rule 312 Communication dated Sep. 19, 2017”, 2 pgs.
“U.S. Appl. No. 15/706,074, Final Office Action dated May 10, 2019”, 28 pgs.
“U.S. Appl. No. 15/706,074, Non Final Office Action dated Nov. 7, 2018”, 26 pgs.
“U.S. Appl. No. 15/706,074, Response filed Mar. 28, 2019 to Non Final Office Action dated Nov. 7, 2018”, 14 pgs.
“U.S. Appl. No. 15/830,965, Corrected Notice of Allowability dated Aug. 6, 2018”, 4 pgs.
“U.S. Appl. No. 15/830,965, Non Final Office Action dated Feb. 16, 2018”, 7 pgs.
“U.S. Appl. No. 15/830,965, Notice of Allowability dated Jul. 5, 2018”, 5 pgs.
“U.S. Appl. No. 15/830,965, Notice of Allowance dated Jun. 13, 2018”, 8 pgs.
“U.S. Appl. No. 15/830,965, Response filed May 16, 2018 to Non Final Office Action dated Feb. 16, 2018”, 10 pgs.
“U.S. Appl. No. 15/971,566, Advisory Action dated Nov. 22, 2019”, 2 pgs.
“U.S. Appl. No. 15/971,566, Final Office Action dated Jul. 16, 2019”, 9 pgs.
“U.S. Appl. No. 15/971,566, Final Office Action dated Oct. 31, 2018”, 38 pgs.
“U.S. Appl. No. 15/971,566, Non Final Office Action dated Feb. 12, 2019”, 12 pgs.
“U.S. Appl. No. 15/971,566, Non Final Office Action dated Jun. 14, 2018”, 7 pgs.
“U.S. Appl. No. 15/971,566, Notice of Allowance dated Jan. 13, 2020”, 8 pgs.
“U.S. Appl. No. 15/971,566, Response filed Jan. 31, 2019 to Final Office Action dated Oct. 31, 2018”, 12 pgs.
“U.S. Appl. No. 15/971,566, Response filed Jun. 12, 2019 to Non Final Office Action dated Feb. 12, 2019”, 11 pgs.
“U.S. Appl. No. 15/971,566, Response filed Oct. 15, 2018 to Non Final Office Action dated Jun. 14, 2018”, 11 pgs.
“U.S. Appl. No. 15/971,566, Response filed Nov. 15, 2019 to Final Office Action dated Jul. 16, 2019”, 13 pgs.
“U.S. Appl. No. 16/014,193, Corrected Notice of Allowability dated Jan. 28, 2020”, 2 pgs.
“U.S. Appl. No. 16/014,193, Non Final Office Action dated Jun. 28, 2019”, 22 pgs.
“U.S. Appl. No. 16/014,193, Notice of Allowance dated Nov. 27, 2019”, 5 pgs.
“U.S. Appl. No. 16/014,193, Response filed Aug. 22, 2019 to Non-Final Office Action dated Jun. 28, 2019”, 12 pgs.
“U.S. Appl. No. 16/135,849, Preliminary Amendment filed Oct. 15, 2018”, 10 pgs.
“U.S. Appl. No. 16/136,849, Corrected Notice of Allowability dated Apr. 25, 2019”, 4 pgs.
“U.S. Appl. No. 16/136,849, Non Final Office Action dated Oct. 17, 2018”, 4 pgs.
“U.S. Appl. No. 16/136,849, Notice of Allowance dated Mar. 5, 2019”, 7 pgs.
“U.S. Appl. No. 16/136,849, Response filed Jan. 17, 2019 to Non Final Office Action dated Oct. 17, 2018”, 9 pgs.
“U.S. Appl. No. 16/438,226, Corrected Notice of Allowability dated May 1, 2020”, 4 pgs.
“U.S. Appl. No. 16/438,226, Final Office Action dated Jan. 3, 2020”, 10 pgs.
“U.S. Appl. No. 16/438,226, Non Final Office Action dated Jul. 10, 2019”, 6 pgs.
“U.S. Appl. No. 16/438,226, Notice of Allowance dated Mar. 26, 2020”, 8 pgs.
“U.S. Appl. No. 16/438,226, Response filed Mar. 16, 2020 to Final Office Action dated Jan. 3, 2020”, 11 pgs.
“U.S. Appl. No. 16/438,226, Response filed Oct. 8, 2019 to Non-Final Office Action dated Jul. 10, 2019”, 11 pgs.
“U.S. Appl. No. 16/749,678, Final Office Action dated May 13, 2021”, 17 pgs.
“U.S. Appl. No. 16/749,678, Non Final Office Action dated Jan. 22, 2021”, 19 pgs.
“U.S. Appl. No. 16/749,678, Notice of Allowance dated Jul. 26, 2021”, 8 pgs.
“U.S. Appl. No. 16/749,678, Response filed Apr. 21, 2021 to Non Final Office Action dated Jan. 22, 2021”, 10 pgs.
“U.S. Appl. No. 16/749,678, Response filed Jul. 13, 2021 to Final Office Action dated May 13, 2021”, 8 pages.
“BlogStomp”, StompSoftware, [Online] Retrieved from the Internet: <URL: http://stompsoftware.com/blogstomp>, (accessed May 24, 2017), 12 pgs.
“Cup Magic Starbucks Holiday Red Cups come to life with AR app”, Blast Radius, [Online] Retrieved from the Internet: <URL: https://web.archive.org/web/20160711202454/http://www.blastradius.com/work/cup-magic>, (2016), 7 pgs.
“Daily App: InstaPlace (iOS/Android): Give Pictures a Sense of Place”, TechPP, [Online] Retrieved from the Internet: <URL: http://techpp.com/2013/02/15/instaplace-app-review>, (2013), 13 pgs.
“deltatre and Vizrt expanding partnership for Magma Pro Football solution”, Vizrt, [Online] Retrieved from the Internet: <URL: http://www.vizrt.com/news/newsgrid/39609/deltatre_and_Vizrt_expanding_partnership_for_Magma_Pro_Football_solution>, (2013), 5 pgs.
“European Application Serial No. 16795488.2, Response filed Dec. 7, 2018 to Communication Pursuant to Rules 161(1) and 162 EPC dated Jun. 7, 2018”, w/ English Claims, 114 pgs.
“InstaPlace Photo App Tell The Whole Story”, [Online] Retrieved from the Internet: <URL: youtu.be/uF_gFkg1hBM>, (Nov. 8, 2013), 113 pgs., 1:02 min.
“International Application Serial No. PCT/US2015/037251, International Search Report dated Sep. 29, 2015”, 2 pgs.
“International Application Serial No. PCT/US2016/059503, International Preliminary Report on Patentability dated May 11, 2018”, 7 pgs.
“International Application Serial No. PCT/US2016/059503, International Search Report dated Jan. 23, 2017”, 4 pgs.
“International Application Serial No. PCT/US2016/059503, Written Opinion dated Jan. 23, 2017”, 5 pgs.
“Introducing Snapchat Stories”, [Online] Retrieved from the Internet: <URL: https://web.archive.org/web/20131026084921/https://www.youtube.com/watch?v=88Cu3yN-LIM>, (Oct. 3, 2013), 92 pgs.; 00:47 min.
“Korean Application Serial No. 10-2017-7035785, Notice of Preliminary Rejection dated Dec. 28, 2018”, w/ English Translation, 10 pgs.
“Korean Application Serial No. 10-2017-7035785, Response filed Mar. 12, 2019 to Notice of Preliminary Rejection dated Dec. 28, 2018”, w/ English Claims, 25 pgs.
“Macy's Believe-o-Magic”, [Online] Retrieved from the Internet: <URL: https://web.archive.org/web/20190422101854/https://www.youtube.com/watch?v=xvzRXy3J0Z0&feature=youtu.be>, (Nov. 7, 2011), 102 pgs.; 00:51 min.
“Macy's Introduces Augmented Reality Experience in Stores across Country as Part of Its 2011 Believe Campaign”, Business Wire, [Online] Retrieved from the Internet: <URL: https://www.businesswire.com/news/home/20111102006759/en/Macys-Introduces-Augmented-Reality-Experience-Stores-Country>, (Nov. 2, 2011), 6 pgs.
“Starbucks Cup Magic”, [Online] Retrieved from the Internet: <URL: https://www.youtube.com/watch?v=RWwQXi9RG0w>, (Nov. 8, 2011), 87 pgs.; 00:47 min.
“Starbucks Cup Magic for Valentine's Day”, [Online] Retrieved from the Internet: <URL: https://www.youtube.com/watch?v=8nvqOzjq10w>, (Feb. 6, 2012), 88 pgs.; 00:45 min.
“Starbucks Holiday Red Cups Come to Life, Signaling the Return of the Merriest Season”, Business Wire, [Online] Retrieved from the Internet: <URL: http://www.businesswire.com/news/home/20111115005744/en/2479513/Starbucks-Holiday-Red-Cups-Life-Signaling-Return>, (Nov. 15, 2011), 5 pgs.
Carthy, Roi, “Dear All Photo Apps: Mobli Just Won Filters”, TechCrunch, [Online] Retrieved from the Internet: <URL: https://techcrunch.com/2011/09/08/mobli-filters>, (Sep. 8, 2011), 10 pgs.
Castelluccia, Claude, et al., “EphPub: Toward robust Ephemeral Publishing”, 19th IEEE International Conference on Network Protocols (ICNP), (Oct. 17, 2011), 18 pgs.
Fajman, “An Extensible Message Format for Message Disposition Notifications”, Request for Comments: 2298, National Institutes of Health, (Mar. 1998), 28 pgs.
Janthong, Isaranu, “Instaplace ready on Android Google Play store”, Android App Review Thailand, [Online] Retrieved from the Internet: <URL: http://www.android-free-app-review.com/2013/01/instaplace-android-google-play-store.html>, (Jan. 23, 2013), 9 pgs.
Klein, Georg, “Parallel Tracking and Mapping for Small AR Workspaces—Source Code”, PTAM Blog, [Online] Retrieved from the Internet on Apr. 3, 2019: <URL: www.robots.ox.ac.uk/˜gk/PTAM/>, (Feb. 2014), 2 pgs.
Leyden, John, “This SMS will self-destruct in 40 seconds”, [Online] Retrieved from the Internet: <URL: http://www.theregister.co.uk/2005/12/12/stealthtext/>, (Dec. 12, 2005), 1 pg.
Macleod, Duncan, “Macys Believe-o-Magic App”, [Online] Retrieved from the Internet: <URL: http://theinspirationroom.com/daily/2011/macys-believe-o-magic-app>, (Nov. 14, 2011), 10 pgs.
Macleod, Duncan, “Starbucks Cup Magic Lets Merry”, [Online] Retrieved from the Internet: <URL: http://theinspirationroom.com/daily/2011/starbucks-cup-magic>, (Nov. 12, 2011), 8 pgs.
Maher, Mary Lou, et al., “Designworld: An Augmented 3D Virtual World for Multidisciplinary, Collaborative Design”, University of Sydney, Key Centre for Design Computing and Cognition, (2006), 10 pgs.
Melanson, Mike, “This text message will self destruct in 60 seconds”, [Online] Retrieved from the Internet: <URL: http://readwrite.com/2011/02/11/this_text_message_will_self_destruct_in_60_seconds>, (Feb. 18, 2015), 4 pgs.
Notopoulos, Katie, “A Guide To The New Snapchat Filters And Big Fonts”, [Online] Retrieved from the Internet: <URL: https://www.buzzfeed.com/katienotopoulos/a-guide-to-the-new-snapchat-filters-and-big-fonts?utm_term-.bkQ9qVZWe#.nv58YXpkV>, (Dec. 22, 2013), 13 pgs.
Panzarino, Matthew, “Snapchat Adds Filters, A Replay Function And For Whatever Reason, Time, Temperature And Speed Overlays”, TechCrunch, [Online] Retrieved form the Internet: <URL: https://techcrunch.com/2013/12/20/snapchat-adds-filters-new-font-and-for-some-reason-time-temperature-and-speed-overlays/>, (Dec. 20, 2013), 12 pgs.
Rosten, Edward, “FAST Corner Detection”, Edwardrosten.com, [Online] Retrieved from the Internet on Apr. 3, 2019: <URL: https://www.edwardrosten.com/work/fast.html>, (Feb. 25, 2018), 5 pgs.
Sawers, Paul, “Snapchat for iOS Lets You Send Photos to Friends and Set How long They're Visible For”, [Online] Retrieved from the Internet: <URL: https://thenextweb.com/apps/2012/05/07/snapchat-for-ios-lets-you-send-photos-to-friends-and-set-how-long-theyre-visible-for/>, (May 7, 2012), 5 pgs.
Shein, Esther, “Ephemeral Data”, Communications of the ACM, vol. 56, No. 9, (Sep. 2013), 3 pgs.
Tripathi, Rohit, “Watermark Images in PHP And Save File on Server”, [Online] Retrieved from the Internet: <URL: http://code.rohitink.com/2012/12/28/watermark-images-in-php-and-save-file-on-server>, (Dec. 28, 2012), 4 pgs.
Vaas, Lisa, “StealthText, Should You Choose to Accept It”, [Online] Retrieved from the Internet: <URL: http://www.eweek.com/print/c/a/MessagingandCollaboration/StealthTextShouldYouChoosetoAcceptIt>, (Dec. 13, 2005), 2 pgs.
Wagner, Daniel, et al., “Pose Tracking from Natural Features on Mobile Phones”, Proc. of the 7th IEEE/ACM Intl. Symposium on Mixed and Augmented Reality, IEEE Computer Society, (2008), 10 pgs.
“U.S. Appl. No. 17/728,553, Non Final Office Action dated Oct. 14, 2022”, 5 pgs.
“U.S. Appl. No. 17/728,553, Response filed Jan. 17, 2023 to Non Final Office Action dated Oct. 14, 2022”, 12 pgs.
Related Publications (1)
Number Date Country
20210407533 A1 Dec 2021 US
Continuations (3)
Number Date Country
Parent 16749678 Jan 2020 US
Child 17474392 US
Parent 16014193 Jun 2018 US
Child 16749678 US
Parent 15437018 Feb 2017 US
Child 16014193 US