Generating and displaying customized avatars in media overlays

Information

  • Patent Grant
  • 11876762
  • Patent Number
    11,876,762
  • Date Filed
    Tuesday, August 28, 2018
    6 years ago
  • Date Issued
    Tuesday, January 16, 2024
    10 months ago
Abstract
Among other things, embodiments of the present disclosure improve the functionality of electronic messaging and imaging software and systems by generating and displaying media overlays with avatars of different users. For example, media overlays can be generated by the system and displayed in conjunction with media content (e.g., images and/or video) generated by an image-capturing device (e.g., a digital camera).
Description
BACKGROUND

The popularity of electronic messaging, particularly instant messaging, continues to grow. Users increasingly use “emoji” (which are ideograms and icons) within electronic messages such as texts and emails. Users also increasingly share media content items such as electronic images and videos with each other, reflecting a global demand to communicate more visually. However, conventional emoji and similar graphics that may be used in conjunction with electronic messages, images, and video are typically generic and lacking in diversity: every individual user is represented by the same set of faces, irrespective of appearance, gender or ethnicity. Furthermore, every conversation that uses conventional emoji looks identical, and there is no visual personality or cue to identify the participants or distinguish one interaction from the next. Embodiments of the present disclosure address these and other issues.





BRIEF DESCRIPTION OF THE DRAWINGS

In the drawings, which are not necessarily drawn to scale, like numerals may describe similar components in different views. Like numerals having different letter suffixes may represent different instances of similar components. Some embodiments are illustrated by way of example, and not limitation, in the figures of the accompanying drawings in which:



FIG. 1 is a block diagram showing an example messaging system for exchanging data (e.g., messages and associated content) over a network.



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



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



FIGS. 4A and 4B are flow diagrams of exemplary processes according to various aspects of the disclosure.



FIGS. 5A-5F are screenshots illustrating the steps of the methods described in FIGS. 4A and 4B.



FIG. 6 is a block diagram illustrating a representative software architecture, which may be used in conjunction with various hardware architectures herein described.



FIG. 7 is a block diagram illustrating components of a machine, according to some exemplary 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

The description that follows includes systems, methods, techniques, instruction sequences, and computing machine program products that embody illustrative embodiments of the disclosure. In the following description, for the purposes of explanation, numerous specific details are set forth in order to provide an understanding of various embodiments of the inventive subject matter. It will be evident, however, to those skilled in the art, that embodiments of the inventive subject matter may be practiced without these specific details. In general, well-known instruction instances, protocols, structures, and techniques are not necessarily shown in detail.


Among other things, embodiments of the present disclosure improve the functionality of electronic messaging and imaging software and systems by generating and displaying media overlays with avatars of different users. For example, media overlays can be generated by the system and displayed in conjunction with media content (e.g., images and/or video) generated by an image-capturing device (e.g., a digital camera).


In some embodiments, media overlays may also be generated that contain avatars of users who exchange electronic communications, such as SMS or MMS texts and emails. Such overlays may be automatically generated based on the history of communications between users, the users' locations, and events the users are engaged in. The appearance of users' avatars in such overlays may likewise be modified based on location and event information. In some embodiments, media overlays may be presented to a user in a gallery or carousel that include customized avatars of the user and the user's friends/contacts.



FIG. 1 is a block diagram showing an example of a 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). As used herein, the term “client device” may refer to any machine that interfaces to a communications network (such as network 106) 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.


In the example shown in FIG. 1, 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 network 106 may include, or operate in conjunction with, 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.


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. This data may include, message content, client device information, geolocation information, media annotation and overlays, message content persistence conditions, social network information, and live event information, as examples. Data exchanges within the messaging system 100 are invoked and controlled through functions available via user interfaces (UIs) of the messaging client 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 118, which facilitates access to a database 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 electronic media files (e.g., electronic images and/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 and a social network system 122. 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 including images and video clips) 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 electronic images and/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 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 application server 112 is communicatively coupled to a database server 118, which facilitates access to a database 120 in which is stored data associated with messages processed by the messaging server application 114.


Some embodiments may include one or more wearable devices, such as a pendant with an integrated camera that is integrated with, in communication with, or coupled to, a client device 102. Any desired wearable device may be used in conjunction with the embodiments of the present disclosure, such as a watch, eyeglasses, goggles, a headset, a wristband, earbuds, clothing (such as a hat or jacket with integrated electronics), a clip-on electronic device, and/or any other wearable devices.



FIG. 2 is block diagram illustrating further details regarding the messaging system 100, according to exemplary 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.


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., an image or video) at the client device 102. For example, the media overlay including text that can be overlaid on top of a photograph/electronic image generated 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 120 and accessed through the database server 118.


In some exemplary embodiments, as discussed in more detail below, embodiments of the present disclosure may generate, display, and apply media overlays to media content items where the media overlays include customized avatars of one or more users. For example, the avatar may represent the user of a computing device performing functionality of the embodiments of the present disclosure. Additionally or alternatively, the media overlay can include an avatar representing one or more other users, such as friends of the user in the user's contact list, as well as one or more users with whom the user of a computing device exchanges electronic communications such as text messages, emails, and media content.


In one exemplary 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 exemplary 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 300 that is stored in the database 120 of the messaging server system 108, according to certain exemplary embodiments. While the content of the database 120 is shown to comprise a number of tables, the data could be stored in other types of data structures (e.g., as an object-oriented database).


The database 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 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 filters include geolocation filters (also known as Geofilters) 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 filter is a data filter, 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).


Embodiments of the present disclosure may generate and present customized images for use within electronic messages/communications such as short message service (SMS) or multimedia message service (MMS) texts and emails. The customized images may also be utilized in conjunction with the SNAPCHAT stories, SNAPCHAT filters, and ephemeral messaging functionality discussed herein.



FIG. 4A depicts an exemplary process according to various aspects of the present disclosure. In this example, method 400 includes receiving a media content item (402), retrieving avatar characteristics for a user (404), generating a media overlay (406), displaying the media overlay with the media content item (408), and applying the media overlay to the media content item (410). Method 400 further includes storing a history of overlaid media content items (412), retrieving the history of media content items (414), and displaying the history of overlaid media content items (416).



FIG. 4B depicts another exemplary process 420 that includes retrieving communication data regarding communications between one or more users (420), determining a relationship between the users based on the communication data (424), generating avatar characteristics based on the relationship (426), generating a media overlay containing avatars representing the users based on the avatar characteristics (428), displaying the media overlay with a media content item on a display (430), and transmitting an electronic communication containing the media overlay (432). Method 420 further includes receiving an electronic communication containing a media overlay (434), generating an event story based on communications between users (436), and providing temporary access to the event story (438). The steps of method 400 and 420 may be performed in whole or in part, may be performed in conjunction each other as well as with some or all of the steps in other methods, and may be performed by any number of different systems, such as the systems described in FIGS. 1 and/or 7.


A variety of media content items may be received (402) from a variety of sources. In this context, a “media content item” may include any type of electronic media in any format. For example, a media content item may include an image in JPG format, an image in PNG format, a video in FLV format, a video in AVI format, etc. In some exemplary embodiments, a media content item is captured using an image capture device or component (such as a digital camera) coupled to, or in communication with, a system performing the functionality of method 400. In the exemplary system 700 depicted in FIG. 7 may include a digital camera as one of input components 728. Additionally or alternatively, the media content item may be received from another system or device. In FIG. 1, for example, a client device 102 performing the functionality of method 400 may receive a media content item from another client device 102 or other system via network 106.


In method 400, the system retrieves avatar characteristics (404) for a user. In some cases, the user for whom avatar characteristics are retrieved may be a user of the system performing the steps of method 400 (such as client device 102 in FIG. 1). Additionally or alternatively, the system may retrieve avatar characteristics for a user of another device, a user listed in the contact list of the user of the system, a user of a social network identified by the user of the system, or any other individual. In one exemplary embodiment, the system (e.g., client device 102 in FIG. 1) transmits a request to a server (e.g., application server 112) for a media overlay that includes the avatar characteristics for the user. The server may then transmit the media overlay that includes the avatar of the user to the system. In this manner, the system may distribute the creation/generation of some or all of the media overlay with other connected systems and devices.


As used herein, an “avatar” of a user is any visual representation of user. The avatar of a user may be based on characteristics derived from images of the user in conjunction with the avatar characteristics identified from the user's relationships with other users. Alternatively or additionally, the user may select and customize characteristics of the user's avatar via the user's computing device. Such avatar characteristics may include, for example, the user's bodily features (e.g., muscular, thin, etc.), facial features, clothing and accessories, text displayed in conjunction with the avatar, and images displayed in conjunction with the avatar. As discussed in more detail below (with reference to method 420), the system may also generate (426) avatar characteristics for one or more users based on various factors. The avatar characteristics may be retrieved (404) from a variety of sources, such as the local memory of a device performing the steps of method 400 (e.g., client device 102 in FIG. 1) as well as from other systems and devices, such as a database or server.


The system generates a media overlay (406) based on the retrieved avatar characteristics to generate an overlay that includes the avatar of one or more users and displays (408) the media overlay in conjunction with a media content item. The overlay may include static (i.e., non-moving) avatars as well as dynamic (i.e., moving) avatars. In some embodiments, application of the overlay (410) may change the format of the image. For example, where the media content item is in a static image format such a JPG, and where the media overlay includes a dynamic component, such as an animated GIF, the system may convert the media content item to an animated GIF to apply the media overlay to the media content item.


The system may also generate and modify other features of the media overlay as part of generating the overlay, such as starting with a template media overlay and modifying the setting, colors, text, avatars, and other features displayed within the media overlay. Among other things, this allows embodiments of the present disclosure to use some standard template features in a media overlay (and thus do not need to recreate each media overlay from scratch) while also allowing the system to customize media overlays to provide a unique graphical experience to each user.


In some embodiments, the system may provide a user with access to a media overlay for a predetermined time period. In some embodiments, media overlays may be received from another system or device (e.g., by client device 102 from application server 112 in FIG. 1) and made available for a limited time. Among other things, this helps provide users with new material and encourages them to check the gallery/carousel of media overlays for new content. In some embodiments, the gallery/carousel of media overlays may include one or more dedicated slots for avatar-based media overlays. Some filters/media overlays might appear in a particular week for as little as 1 minute, giving users who had the luck to find the media overlay a special opportunity to use the media overlay as well as a reason to “tune into” the gallery/carousel throughout the day to see what's new. Among other things, the customized media overlays/filters of the present disclosure help introduce personalization to the media overlays for different users, an opportunity for surprise and serendipity in applying the media overlay to a media content item, the ability to add character to a media content item beyond its original content, and encourage users to check out the gallery/carousel of media overlays to view new content.


Accordingly, display of the media overlay (408) may include presenting a plurality of media overlays on the display screen of a computing device and receiving a selection of one or more media overlays from the plurality of media overlays to display in conjunction with the media content item. The user may then add, remove, and/or modify the displayed media overlays before applying the media overlay(s) to the content item.


In some embodiments, a first media overlay may be redundant or otherwise incompatible with a second media overlay in a selection of media overlays in a gallery/carousel. In such embodiments, the system may receive (e.g., via an input device of a user interface) selection of a first overlay by a user and, in response to the selection of the first media overlay, remove (or disable selection of by, for example, graying out the selection) a second media overlay from the plurality of media overlays presented to the user.


The system may generate the media overlay based on information in addition to, or other than, the avatar characteristics. For example, the media overlay may be generated based on location information for the system (e.g., received from a location sensor coupled to the device performing the steps of method 400), the time of day, the date, an event (such as a holiday or a birthday of the user), and other information. Time and date information can be determined based on time and time zone information from a clock coupled to the system. In FIG. 5E for example, the upper-left media overlay may be displayed in the morning relative to the system on which it is displayed, while the media overlay in the lower right can be displayed in the evening based on the system's time. Likewise, the “Happy Friday” or similar media overlay in FIG. 5F can be generated based on the day of the week as determined from the system's clock.


Embodiments of the present disclosure can also generate a media overlay based on information retrieved/received from one or more sensors coupled to, or in communication with, the system, such as any of the sensor components 730, 734, 736, 738 in system 700 depicted in FIG. 7. Accordingly, the media overlay may thus be generated based on data from a temperature sensor, velocity sensor, acceleration sensor, altitude sensor, and/or any other sensor information.


Embodiments of the present disclosure may generate any desired content in conjunction with generating (406) the media overlay, including images, video, text, visual effects, etc. In some embodiments, the generation of text and other content may be generated based on identifying a location for the system (e.g., based on location information from a location sensor coupled to the system), identifying a language associated with the system's location, and generating text for the media overlay in the identified language.


In some embodiments the actual time for the system can be displayed as part of the media overlay, such as is shown on the clock around the neck of the avatar in the lower-left media overlay in FIG. 5E. Media overlays can also be generated based on information stored in the user's calendar on the system, such as birthday information (e.g., a “happy birthday” overlay) as well as scheduling information that could be used to determine when the user leaves work, as shown in the upper-right media overlay in FIG. 5E. Location information for the system in conjunction with date and time information may be used to generate media overlays based on holidays in the location where the system is present, such as the “Happy Halloween” media overlay in FIG. 5F


The media overlay can be displayed (408) in conjunction with the media content item on the display screen of a computing device to allow a user to determine if he/she wishes to apply the overlay to the content item, to select from among a plurality of media overlays, as well as to allow the user to modify parameters of the media overlay. For example, a user may be presented the media overlays depicted in FIGS. 5E and 5F in a carousel or gallery to allow the user to see how the overlay will affect the media content item. The user may also be given an interface to modify the color and/or size of features of the media overlay, as well as to edit text in the overlay. In the four media overlays in FIG. 5E, for example, the user may be given an interface to change the text and/or the font/colors of the text prior to application of the overlay to the media content item. In some embodiments, editing of a media overlay or media content item can be performed by a user after the media overlay is applied to the media content item. The user may provide selections (e.g., via the input device of a user interface on the user's computing device) to edit and/or apply (410) the media overlay to the media content item.


As described above, a collection of content, including media content items with applied media overlays may be organized into an “event gallery” or an “event story” and such collections may be made available for a predetermined time period, such as the duration of an event to which the content relates. The system may store (412) a history of media content items with applied media overlays in the memory of the system, a database in communication with the system, and/or another system or device in communication with the system performing the functionality of method 400. The system may retrieve (414) and display (416) some or all of the media content items in such a history as well.


A history of media content items may be stored in any desired format and in any desired manner. In one exemplary embodiment, the media content items store an identifier for the media overlay and an identifier for the user's avatar, rather than a copy of the rendered media content item with the media overlay applied. Upon retrieval (414) the system looks up the media overlay and avatar information and generates the combined media content item/media overlay combination on demand. Among other things, this helps save memory on the user's device as well as on servers and databases that may store the information.


In some embodiments, the avatar of a user may include a version number. If the user or system modifies the user's avatar after a media content item/media overlay combination is saved to a history, the system may use the previous (i.e., originally saved) version of the user's avatar in any rendered media content based on the stored content. In other embodiments, the system may render the filter/media overlay using the current version of the user's avatar.


In the exemplary method 420 shown in FIG. 4B, Embodiments of the present disclosure can retrieve (422) a variety of communication data from a variety of sources. For example, communication data may be retrieved from the memory of a computing device (such as client computing device 102 in FIG. 1) performing some or all of the functionality of method 420. Alternately or additionally, communication data may be retrieved from another computing device (e.g., over a network). Communication data may include a history of electronic communications (such as emails, text messages, and the like) between a plurality of users. For example, consider two users, a first user and a second user, who exchange a series of text messages with each other using their respective mobile computing devices (e.g., client computing devices 102 in FIG. 1). The computing device of the first user may be adapted to store the messages in its memory for later retrieval, or to request the messages (or information regarding them) from another source (such as application server 112 in FIG. 1).


The communication data may include meta data associated with one or more communications, such as the size of the communication, the date/time it was sent, one or more languages used in the communication, identifiers for the sender and/or recipient(s), information regarding the computing devices (e.g. the mobile devices of the sender or recipient or a messaging server) involved in transmitting or receiving the communication, and other information. In the case of identification information, any such identifier may be used, such as the user's full name or a username associated with the user. The user identifier may also be an identifier associated with the user's computing device, such as a Unique Device Identifier (UDID) or Identifier for Advertising (IDFA). The communication data may also include text, images, video, and other content within a communication. For example, the communication data may include terms used by users within one or more communications to address each other, such as “hi mom,” “hey buddy,” “how's my favorite nephew,” and the like. Such terms (and other communication data) may be used to help identify a relationship between users based on their communications with each other as discussed below.


The system may request authorization from a user to analyze communication data associated with the user's communications. The authorization request may be presented to the user via the user's computing device and may allow the user to select the types of communication data the system may analyze as well as allowing the user to entirely disable the system from analyzing the user's communication data altogether. In cases where the user grants the system access to analyze the user's communication data, the system can analyze the communication data to automatically determine (424) a relationship between the user and other users with whom the user communicates.


Embodiments of the present disclosure can identify any number of different relationships between any number of users. Examples of such relationships may include family relationships, friendships, or romantic relationships, as well as others. Embodiments of the disclosure may also identify other aspects of relationships between users, such as whether the users are work colleagues, classmates, roommates, and/or acquaintances. Analysis of communication data to identify relationships between users may also be supplemented with other information, such as data retrieved from social networking sites, as well as direct input from the user providing information on his/her relationships with various users.


Based on the relationship between different users, the system can generate characteristics for avatars (426) that represent the different users and use such avatar characteristics to generate media overlays (428) containing the avatars of the users. Embodiments of the present disclosure may generate (428) images within media overlays containing any number of avatars. For example, an image containing a single avatar may be generated in some cases, while an image containing multiple user avatars may be generated in other cases. FIGS. 5A-5E illustrate exemplary images that include a first avatar representing a first user and a second avatar representing a second user according to various aspects of the disclosure. Such images may be displayed (430) within a media overlay on the display screen of one or more computing devices. Media overlays generated by embodiments of the present disclosure may include any number of user avatars in a variety of forms. For example, FIG. 5A depicts an avatar of a first user with the avatar of a second user on his shirt.


In some embodiments, besides using images containing avatars within media overlays, such images may be used in conjunction with displaying the avatars within a video game. In some cases, the images may be displayed in a single-person game (e.g., played alone by a first user on the first user's computing device) or in a multi-player game (e.g., the game is accessed by the computing device of a first user and the computing device of a second user) played over a network or other connection. During the game, various events may occur and the avatars of one or more users may be modified as a result. For example, an avatar who experiences an injury may be depicted with a black eye, while an avatar who finds an item in the game (e.g., a sword) can be modified to show the avatar carrying the item. In this manner, embodiments of the disclosure allow users to have their own customized avatars (which may be based on their own likenesses) appear in video games as well as in other contexts, such as text messages or other electronic communications.


Generation of the images containing user avatars may be based on an event. The event may affect one user (such as the user's birthday) or be common to multiple users. For example, referring to FIG. 5B, an image depicting avatars of two users is generated based on a day of the week.


Generation of the images containing user avatars may be based on the locations of different users. For example, embodiments of the present disclosure may retrieve location information from the computing devices of two different users. In embodiments where a client computing device (such as client device 102) is performing the image/media overlay generation, location information for the device can be retrieved from the device's global positioning system and location information for the device of another can be requested over a network.


The avatars of different users in different locations can be generated to reflect their respective locations. For example, the avatar of a first user whose mobile computing device indicates is in the tropics could be depicted standing in a bathing suit on a beach, while the avatar of a second user whose mobile device indicates is in an area with snow could be depicted wearing a jacket and shivering. Accordingly, the location information from a device associated with a user can be combined with information regarding the location and/or an event occurring at the location to generate the avatar and/or image. Such location-based information may include weather information, time of day, local customs (such as language and/or dress), and other information.


In some cases, the system can identify that two or more users are in a common location. In this context, a “common location” may be identified as being within any predetermined boundary, such as within the same building, the same city, the same two-block radius, the same state, etc. In such cases, the image in the media overlay can be generated to depict the avatars of multiple users based on the common location. As described above, the image containing multiple avatars may be generated based on information regarding the location as well as identifying an event taking place at the common location. Such events may include, for example, a sporting event, a business meeting, an educational event, a pre-arranged meeting between the user and another person (such as a lunch meeting), and other events.


In one exemplary embodiment, referring to FIG. 5C, the system identifies that a first user and second user are both participating in a race, and that the first user finished the race ahead of the second user. The system then automatically generates a media overlay containing the image in FIG. 5C and presents the media overlay to the first user and/or second user via their mobile computing devices for application with a media content item, such as an image or video of the two users racing. In this example, the details of the event (i.e., race in this case) can be identified by the system based on information from a combination of different sources, such as location information from each user's mobile computing device, information about the race occurring collected from a website hosted by the race's sponsor based on a web search using the identified location, posts by the first and second user to a social media website, and a history of electronic communications between the first and second user where the second user congratulates the first user on winning and the first user consoling the second user. In this manner, the system can utilize a combination of publically-available information and information the system is authorized by the user to access (such as the content of the user's communications) to automatically generate images and media overlays including the user's avatar and/or the avatars of other users.


In some embodiments, the system may modify various features of an avatar, as well as features of an image containing an avatar, based on location information and/or event information. In FIG. 5B, for example, a similar image could be generated for other days of the week where the setting or background of the image displaying the name of the day of the week (e.g., Wednesday vs. Tuesday) can be modified. Likewise, either avatar can be modified based on various information. For example, referring now to FIG. 5D, the system may identify an event taking place at a common location (a cupcake festival in this example) and generate an image of the first user standing next to the second user, where the second user's body is depicted as a cupcake. As above, the image can be generated based on content of communications between the users, such as based on a comment by the second user in a text message to the first user that “I ate so many cupcakes, I feel like one.”


The system can modify avatars and images based on identified events and locations in any suitable manner. For example, avatars of users attending the same sporting event could be depicted in an image wearing the jersey of one of the teams playing at the event. Users attending a paintball event together could result in an image being generated showing avatars of the users holding paintguns and covered in paint. Users attending a mud obstacle race could result in an image being generated showing avatars of the users covered in mud. Furthermore, information from users' electronic communications between each other and/or social network posts can be used to identify an event attended by the user and use such information to generate avatar attributes and images.


In some exemplary embodiments, the system can identify users at a common location, generate images containing the avatars of such users, and initiate (automatically or in response to user activation) the transmission of electronic communications to such users. For example, if a first user and second user attend an event (such as a baseball game at a stadium) together, the system (e.g., via the first user's mobile computing device) may (e.g., automatically with the first user's authorization or in response to the first user's instruction) search for other users in the contact list of the first user's mobile device who are also at the stadium. In response to identifying a third user, the system may then generate an image containing avatars representing the first, second, and third users (e.g., all wearing team jerseys) and transmit an electronic message/communication containing the image (e.g., a part of a media overlay) to a mobile computing device carried by the third user (e.g., in a text message). Among other things, this can help users quickly identify and reach out to people they know at various events and locations.


Embodiments of the present disclosure may transmit (432) and/or receive (434) electronic communications containing images with avatars, including within media overlays. Any form of electronic communication may be utilized by embodiments of the present disclosure, such as SMS texts, MMS texts, emails, and other communications. Images included in such communications may be provided as attachments, displayed inline in the message, within media overlays, or conveyed in any other suitable manner.


In some embodiments, the system may generate a plurality of images containing one or more avatars and allow a user of the system to select which image(s) he/she wishes to include in an electronic communication and/or in a media overlay. In some embodiments, the generation of such images may be based on the content of communications sent or received by the system, as well as on other communication data as discussed above. In one particular embodiment, a computing device operated by a first user receives (434) an electronic communication from the computing device of a second user, where the communication contains an image that includes avatars representing the first and second user. In this example, the computing device of the first user is adapted to utilize the received image in generating (as in step 406 from FIG. 4A) a media overlay.


As described in more detail above, embodiments of the disclosure may generate an event story or event gallery (436) based on a collection or series of electronic communications (e.g., containing media content items with media overlays applied) between users and provide temporary access to the event story or gallery (438). Any collection of such communications may be selected based on any criteria, and one or more users may be granted access to an event story or gallery for any desired predetermined period of time. Likewise, the system may grant access to images generated by the system or received from other system for a predetermined period of time as described above. Such images may also be presented in conjunction with a media overlay (e.g., a SNAPCHAT filter).


Software Architecture



FIG. 6 is a block diagram illustrating an exemplary software architecture 606, which may be used in conjunction with various hardware architectures herein described. FIG. 6 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 606 may execute on hardware such as machine 700 of FIG. 7 that includes, among other things, processors 704, memory 714, and I/O components 718. A representative hardware layer 652 is illustrated and can represent, for example, the machine 700 of FIG. 7. The representative hardware layer 652 includes a processing unit 654 having associated executable instructions 604. Executable instructions 604 represent the executable instructions of the software architecture 606, including implementation of the methods, components and so forth described herein. The hardware layer 652 also includes memory and/or storage modules memory/storage 656, which also have executable instructions 604. The hardware layer 652 may also comprise other hardware 658.


As used herein, the term “component” may refer to a device, physical entity or logic having boundaries defined by function or subroutine calls, branch points, application program interfaces (APIs), and/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 exemplary 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.


A processor may be, or in include, 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.


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 exemplary 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 exemplary embodiments, the processors or processor-implemented components may be distributed across a number of geographic locations.


In the exemplary architecture of FIG. 6, the software architecture 606 may be conceptualized as a stack of layers where each layer provides particular functionality. For example, the software architecture 606 may include layers such as an operating system 602, libraries 620, applications 616 and a presentation layer 614. Operationally, the applications 616 and/or other components within the layers may invoke application programming interface (API) API calls 608 through the software stack and receive messages 612 in response to the API calls 608. 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 618, while others may provide such a layer. Other software architectures may include additional or different layers.


The operating system 602 may manage hardware resources and provide common services. The operating system 602 may include, for example, a kernel 622, services 624 and drivers 626. The kernel 622 may act as an abstraction layer between the hardware and the other software layers. For example, the kernel 622 may be responsible for memory management, processor management (e.g., scheduling), component management, networking, security settings, and so on. The services 624 may provide other common services for the other software layers. The drivers 626 are responsible for controlling or interfacing with the underlying hardware. For instance, the drivers 626 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 620 provide a common infrastructure that is used by the applications 616 and/or other components and/or layers. The libraries 620 provide functionality that allows other software components to perform tasks in an easier fashion than to interface directly with the underlying operating system 602 functionality (e.g., kernel 622, services 624 and/or drivers 626). The libraries 620 may include system libraries 644 (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 620 may include API libraries 646 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 620 may also include a wide variety of other libraries 648 to provide many other APIs to the applications 616 and other software components/modules.


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


The applications 616 include built-in applications 638 and/or third-party applications 640. Examples of representative built-in applications 638 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 640 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 640 may invoke the API calls 608 provided by the mobile operating system (such as operating system 602) to facilitate functionality described herein.


The applications 616 may use built in operating system functions (e.g., kernel 622, services 624 and/or drivers 626), libraries 620, and frameworks/middleware 618 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 614. In these systems, the application/component “logic” can be separated from the aspects of the application/component that interact with a user.



FIG. 7 is a block diagram illustrating components (also referred to herein as “modules”) of a machine 700, according to some exemplary 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. 7 shows a diagrammatic representation of the machine 700 in the example form of a computer system, within which instructions 710 (e.g., software, a program, an application, an applet, an app, or other executable code) for causing the machine 700 to perform any one or more of the methodologies discussed herein may be executed. As such, the instructions 710 may be used to implement modules or components described herein. The instructions 710 transform the general, non-programmed machine 700 into a particular machine 700 programmed to carry out the described and illustrated functions in the manner described. In alternative embodiments, the machine 700 operates as a standalone device or may be coupled (e.g., networked) to other machines. In a networked deployment, the machine 700 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 700 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 710, sequentially or otherwise, that specify actions to be taken by machine 700. Further, while only a single machine 700 is illustrated, the term “machine” shall also be taken to include a collection of machines that individually or jointly execute the instructions 710 to perform any one or more of the methodologies discussed herein.


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


As used herein, the term “machine-readable medium,” “computer-readable medium,” or the like may refer to any component, device or other tangible media able to store instructions and data temporarily or permanently. Examples of such media may include, but is not 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” may 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” may refer 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.


The I/O components 718 may include a wide variety of components to provide a user interface for receiving input, providing output, producing output, transmitting information, exchanging information, capturing measurements, and so on. The specific I/O components 718 that are included in the user interface of a particular machine 700 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 718 may include many other components that are not shown in FIG. 7. The I/O components 718 are grouped according to functionality merely for simplifying the following discussion and the grouping is in no way limiting. In various exemplary embodiments, the I/O components 718 may include output components 726 and input components 728. The output components 726 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 728 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. The input components 728 may also include one or more image-capturing devices, such as a digital camera for generating digital images and/or video.


In further exemplary embodiments, the I/O components 718 may include biometric components 730, motion components 734, environmental environment components 736, or position components 738, as well as a wide array of other components. One or more of such components (or portions thereof) may collectively be referred to herein as a “sensor component” or “sensor” for collecting various data related to the machine 700, the environment of the machine 700, a user of the machine 700, or a combinations thereof.


For example, the biometric components 730 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 734 may include acceleration sensor components (e.g., accelerometer), gravitation sensor components, velocity sensor components (e.g., speedometer), rotation sensor components (e.g., gyroscope), and so forth. The environment components 736 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 738 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. For example, the location sensor component may provide location information associated with the system 700, such as the system's 700 GPS coordinates and/or information regarding a location the system 700 is at currently (e.g., the name of a restaurant or other business).


Communication may be implemented using a wide variety of technologies. The I/O components 718 may include communication components 740 operable to couple the machine 700 to a network 732 or devices 720 via coupling 722 and coupling 724 respectively. For example, the communication components 740 may include a network interface component or other suitable device to interface with the network 732. In further examples, communication components 740 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 720 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 740 may detect identifiers or include components operable to detect identifiers. For example, the communication components 740 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 740, 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.


Where a phrase similar to “at least one of A, B, or C,” “at least one of A, B, and C,” “one or more A, B, or C,” or “one or more of A, B, and C” is used, it is intended that the phrase be interpreted to mean that A alone may be present in an embodiment, B alone may be present in an embodiment, C alone may be present in an embodiment, or that any combination of the elements A, B and C may be present in a single embodiment; for example, A and B, A and C, B and C, or A and B and C.


A portion of the disclosure of this patent document contains material that is subject to copyright protection. The copyright owner has no objection to the facsimile reproduction by anyone of the patent document or the patent disclosure, as it appears in the Patent and Trademark Office patent files or records, but otherwise reserves all copyright rights whatsoever. The following notice applies to the software and data as described below and in the drawings that form a part of this document: Copyright 2016, SNAPCHAT, INC. 2016, All Rights Reserved.


Changes and modifications may be made to the disclosed embodiments without departing from the scope of the present disclosure. These and other changes or modifications are intended to be included within the scope of the present disclosure, as expressed in the following claims.

Claims
  • 1. A first client device comprising: a processor; andmemory coupled to the processor and storing instructions that, when executed by the processor, cause the first client device to perform operations comprising:displaying a media content item on a display screen of the first client device, wherein the first client device is associated with a first user, wherein the media content item is a still image or video of depicting a physical environment captured using an image capturing device included in the first client device;generating a media overlay that comprises a customized version of an avatar of a second user associated with a second client device, wherein the customized version of the avatar of the second user is a customized visual representation of the second user that has been selected, by the second user, from a plurality of customized versions of avatars of the second user, each customized version of an avatar of the second user derived to reflect a location of the second user as determined, in part, by geolocation information derived by a location sensor of the second client device;generating a modified media content item in real-time by incorporating the media overlay with the media content item, wherein incorporating the media overlay with the media content item comprises overlaying the customized version of the avatar of the second user on the media content item; andcausing the modified media content item to be displayed on the display screen of the first client device.
  • 2. The first client device of claim 1, wherein the operations further comprise: receiving the media content item from the image capturing device included in the first client device.
  • 3. The first client device of claim 1, wherein generating the media overlay further comprises: generating the media overlay to include an avatar of the first user and the customized version of the avatar of the second user, wherein the avatar of the first user is a visual representation of the first user.
  • 4. The first client device of claim 1, wherein the customized version of the avatar of the second user has been generated as a dynamic avatar, wherein movement of the avatar reflects an activity associated with an event occurring at the location of the second user.
  • 5. The first client device of claim 1, wherein generating the media overlay further comprises generating the media overlay to include, in addition to the customized version of the avatar of the second user, a graphic or text, wherein the graphic or text is selected for inclusion with the media overlay based on an identified event occurring at the location of the second user.
  • 6. The first client device of claim 1, wherein the media overlay is accessible to the media overlay selected customized version of the avatar of the second user is available for selection by the second user for a predetermined time period that corresponds with a time period of an event occurring in the location of the second user.
  • 7. The first client device of claim 1, wherein the operations further comprise: generating multiple media overlays; andgenerating the modified media content item by overlaying the multiple media overlays on the media content item.
  • 8. The first client device of claim 7, wherein the multiple media overlays are selected from a plurality of media overlays displayed on the display screen of the first client device.
  • 9. The first client device of claim 8, wherein displaying the plurality of media overlays comprises: receiving a selection of a first media overlay from the plurality of media overlays; andin response to the selection of the first media overlay, removing a second media overlay from the plurality of media overlays presented via the display screen of the first client device.
  • 10. The first client device of claim 1, wherein generating the media overlay further comprises: transmitting, to a server, a request for the media overlay that includes the customized version of the avatar of the second user; andreceiving, from the server, the media overlay including the avatar of the second user.
  • 11. A computer-implemented method comprising: displaying, by a processor of a first client device, a media content item on a display screen of the first client device, the first client device associated with a first user, wherein the media content item is a still image or video depicting a physical environment captured using an image capturing device included in the first client device;generating a media overlay that comprises a customized version of an avatar of a second user associated with a second client device, wherein the customized version of the avatar of the second user is a customized visual representation of the second user that has been selected, by the second user, from a plurality of customized versions of avatars of the second user, each customized version of an avatar of the second user derived to reflect a location of the second user as determined, in part, by geolocation information derived by a location sensor of the second client device;generating a modified media content item in real-time by incorporating the media overlay with the media content item, wherein incorporating the media overlay with the media content item comprises overlaying the customized version of the avatar of the second user on the media content item; andcausing the modified media content item to be displayed on the display screen of the first client device.
  • 12. The computer-implemented method of claim 11, further comprising: receiving the media content item from the image capturing device included in the first client device.
  • 13. The computer-implemented method of claim 11, wherein generating the media overlay further comprise: generating the media overlay to include an avatar of the first user and the customized version of the avatar of the second user, wherein the avatar of the first user is a visual representation of the first user.
  • 14. The computer-implemented method of claim 11, wherein the customized version of the avatar of the second user has been generated as a dynamic avatar, wherein movement of the avatar reflects an activity associated with an event occurring at the location of the second user.
  • 15. A non-transitory computer-readable medium storing instructions that, when executed by a first client device, cause the first client device to perform operations comprising: displaying a media content item on a display screen of the first client device, the first client device is associated with a first user, wherein the media content item is a still image or video of depicting a physical environment captured using an image capturing device included in the first client device;generating a media overlay that comprises a customized version of an avatar of a second user associated with a second client device, wherein the customized version of the avatar of the second user is a customized visual representation of the second user that has been selected, by the second user, from a plurality of customized versions of avatars of the second user, each customized version of an avatar of the second user derived to reflect a location of the second user as determined, in part, by geolocation information derived by a location sensor of the second client device;generating a modified media content item in real-time by incorporating the media overlay with the media content item, wherein incorporating the media overlay with the media content item comprises overlaying the customized version of the avatar of the second user on the media content item; andcausing the modified media content item to be displayed on the display screen of the first client device.
CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims priority to U.S. patent application Ser. No. 15/369,499, filed Dec. 5, 2016, which claims priority to U.S. Provisional Patent Application Ser. No. 62/412,115, filed Oct. 24, 2016 the disclosure of each of which are incorporated by reference.

US Referenced Citations (1015)
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
5493692 Theimer et al. Feb 1996 A
5713073 Warsta Jan 1998 A
5754939 Herz et al. May 1998 A
5826269 Hussey Oct 1998 A
5855008 Goldhaber et al. Dec 1998 A
5880731 Liles et al. Mar 1999 A
5883639 Walton et al. Mar 1999 A
5999932 Paul Dec 1999 A
6012098 Bayeh et al. Jan 2000 A
6014090 Rosen et al. Jan 2000 A
6023270 Brush, II et al. Feb 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
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
6223165 Lauffer Apr 2001 B1
6233318 Picard et al. May 2001 B1
6283858 Hayes, Jr. et al. Sep 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
6374292 Srivastava et al. Apr 2002 B1
6446004 Cao et al. Sep 2002 B1
6449657 Stanbach et al. Sep 2002 B2
6456852 Bar et al. Sep 2002 B2
6473794 Guheen et al. Oct 2002 B1
6484196 Maurille Nov 2002 B1
6487601 Hubacher et al. Nov 2002 B1
6523008 Avrunin Feb 2003 B1
6542749 Tanaka et al. Apr 2003 B2
6549768 Fraccaroli Apr 2003 B1
6590674 Orton Jul 2003 B1
6618593 Drutman et al. Sep 2003 B1
6622174 Ukita et al. Sep 2003 B1
6631463 Floyd et al. Oct 2003 B1
6633289 Lotens 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
6720860 Narayanaswami Apr 2004 B1
6724403 Santoro et al. Apr 2004 B1
6757713 Ogilvie et al. Jun 2004 B1
6772195 Hatlelid et al. Aug 2004 B1
6832222 Zimowski Dec 2004 B1
6834195 Brandenberg et al. Dec 2004 B2
6836792 Chen Dec 2004 B1
6839411 Saltanov et al. Jan 2005 B1
6842779 Nishizawa Jan 2005 B1
6898626 Ohashi May 2005 B2
6954728 Kusumoto et al. Oct 2005 B1
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
7073129 Robarts et al. Jul 2006 B1
7079158 Lambertsen 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
7269426 Kokkonen et al. Sep 2007 B2
7280123 Bentley et al. Oct 2007 B2
7280658 Amini et al. Oct 2007 B2
7315823 Brondrup Jan 2008 B2
7342587 Danzig et al. Mar 2008 B2
7349768 Bruce et al. Mar 2008 B2
7356564 Hartselle et al. Apr 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
7468729 Levinson Dec 2008 B1
7508419 Toyama et al. Mar 2009 B2
7519670 Hagale et al. Apr 2009 B2
7535469 Kim et al. May 2009 B2
7535890 Rojas May 2009 B2
7546554 Chiu et al. Jun 2009 B2
7607096 Oreizy et al. Oct 2009 B2
7627828 Collison et al. Dec 2009 B1
7636755 Blattner et al. Dec 2009 B2
7639251 Gu et al. Dec 2009 B2
7639943 Kalajan Dec 2009 B1
7650231 Gadler Jan 2010 B2
7668537 DeVries Feb 2010 B2
7689649 Heikes et al. Mar 2010 B2
7711155 Sharma et al. May 2010 B1
7770137 Forbes et al. Aug 2010 B2
7775885 Van et al. Aug 2010 B2
7778973 Choi Aug 2010 B2
7779444 Glad Aug 2010 B2
7787886 Markhovsky et al. Aug 2010 B2
7792789 Prahlad et al. Sep 2010 B2
7796946 Eisenbach Sep 2010 B2
7801954 Cadiz et al. Sep 2010 B2
7856360 Kramer et al. Dec 2010 B2
7859551 Bulman et al. Dec 2010 B2
7885931 Seo et al. Feb 2011 B2
7925703 Dinan et al. Apr 2011 B2
8001204 Burtner et al. Aug 2011 B2
8032586 Challenger et al. Oct 2011 B2
8077931 Chatman et al. Dec 2011 B1
8082255 Carlson, Jr. et al. Dec 2011 B1
8088044 Tchao et al. Jan 2012 B2
8090351 Klein Jan 2012 B2
8095878 Bates et al. Jan 2012 B2
8098904 Ioffe et al. Jan 2012 B2
8099109 Altman et al. Jan 2012 B2
8108774 Finn et al. Jan 2012 B2
8112716 Kobayashi Feb 2012 B2
8117281 Robinson et al. Feb 2012 B2
8130219 Fleury et al. Mar 2012 B2
8131597 Hudetz Mar 2012 B2
8135166 Rhoads Mar 2012 B2
8136028 Loeb et al. Mar 2012 B1
8146001 Reese Mar 2012 B1
8146005 Jones et al. Mar 2012 B2
8151191 Nicol Apr 2012 B2
8161115 Yamamoto Apr 2012 B2
8161417 Lee Apr 2012 B1
8170957 Richard May 2012 B2
8195203 Tseng Jun 2012 B1
8199747 Rojas et al. Jun 2012 B2
8208943 Petersen Jun 2012 B2
8214443 Hamburg Jul 2012 B2
8234350 Gu et al. Jul 2012 B1
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
8384719 Reville et al. Feb 2013 B2
8385950 Wagner et al. Feb 2013 B1
RE44054 Kim Mar 2013 E
8396708 Park et al. Mar 2013 B2
8402097 Szeto Mar 2013 B2
8405773 Hayashi et al. Mar 2013 B2
8413059 Lee et al. Apr 2013 B2
8418067 Cheng et al. Apr 2013 B2
8423409 Rao Apr 2013 B2
8425322 Gillo et al. Apr 2013 B2
8457367 Sipe et al. Jun 2013 B1
8458601 Castelli et al. Jun 2013 B2
8462198 Lin et al. Jun 2013 B2
8471914 Sakiyama et al. Jun 2013 B2
8472935 Fujisaki Jun 2013 B1
8484158 Deluca et al. Jul 2013 B2
8495503 Brown et al. Jul 2013 B2
8495505 Smith et al. Jul 2013 B2
8504926 Wolf Aug 2013 B2
8510383 Hurley et al. Aug 2013 B2
8527345 Rothschild et al. Sep 2013 B2
8554627 Svendsen et al. Oct 2013 B2
8559980 Pujol Oct 2013 B2
8560612 Kilmer et al. Oct 2013 B2
8564621 Branson et al. Oct 2013 B2
8564710 Nonaka et al. Oct 2013 B2
8570326 Gorev Oct 2013 B2
8581911 Becker et al. Nov 2013 B2
8594680 Ledlie et al. Nov 2013 B2
8597121 Andres Dec 2013 B2
8601051 Wang Dec 2013 B2
8601379 Marks et al. Dec 2013 B2
8613089 Holloway et al. Dec 2013 B1
8632408 Gillo et al. Jan 2014 B2
8648865 Dawson et al. Feb 2014 B2
8659548 Hildreth Feb 2014 B2
8660358 Bergboer et al. Feb 2014 B1
8660369 Llano et al. Feb 2014 B2
8660793 Ngo et al. Feb 2014 B2
8682350 Altman et al. Mar 2014 B2
8683354 Khandelwal et al. Mar 2014 B2
8692830 Nelson et al. Apr 2014 B2
8700012 Ferren et al. Apr 2014 B2
8718333 Wolf et al. May 2014 B2
8724622 Rojas May 2014 B2
8730231 Snoddy et al. May 2014 B2
8732168 Johnson May 2014 B2
8738719 Lee et al. May 2014 B2
8744523 Fan et al. Jun 2014 B2
8745132 Obradovich Jun 2014 B2
8761800 Kuwahara 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
8810513 Ptucha et al. Aug 2014 B2
8812171 Filev et al. Aug 2014 B2
8832201 Wall Sep 2014 B2
8832552 Arrasvuori et al. Sep 2014 B2
8834267 Fujii et al. Sep 2014 B2
8839327 Amento et al. Sep 2014 B2
8856349 Jain et al. Oct 2014 B2
8874677 Rosen et al. Oct 2014 B2
8886227 Schmidt et al. Nov 2014 B2
8890926 Tandon et al. Nov 2014 B2
8892999 Nims et al. Nov 2014 B2
8909679 Root et al. Dec 2014 B2
8909725 Sehn Dec 2014 B1
8924250 Bates et al. Dec 2014 B2
8935656 Dandia et al. Jan 2015 B2
8963926 Brown et al. Feb 2015 B2
8972357 Shim et al. Mar 2015 B2
8989786 Feghali Mar 2015 B2
8995433 Rojas Mar 2015 B2
9015285 Ebsen et al. Apr 2015 B1
9020745 Johnston et al. Apr 2015 B2
9040574 Wang et al. May 2015 B2
9055416 Rosen et al. Jun 2015 B2
9086776 Ye et al. Jul 2015 B2
9094137 Sehn et al. Jul 2015 B1
9100806 Rosen et al. Aug 2015 B2
9100807 Rosen et al. Aug 2015 B2
9105014 Collet 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
9135726 Kafuku Sep 2015 B2
9143382 Bhogal et al. Sep 2015 B2
9143681 Ebsen et al. Sep 2015 B1
9152477 Campbell et al. Oct 2015 B1
9191776 Root et al. Nov 2015 B2
9204252 Root Dec 2015 B2
9224220 Toyoda et al. Dec 2015 B2
9225897 Sehn et al. Dec 2015 B1
9241184 Weerasinghe Jan 2016 B2
9256860 Herger et al. Feb 2016 B2
9256950 Xu et al. Feb 2016 B1
9258459 Hartley Feb 2016 B2
9285951 Makofsky et al. Mar 2016 B2
9298257 Hwang et al. Mar 2016 B2
9314692 Konoplev et al. Apr 2016 B2
9330483 Du et al. May 2016 B2
9344606 Hartley et al. May 2016 B2
9357174 Li et al. May 2016 B2
9361510 Yao et al. Jun 2016 B2
9378576 Bouaziz et al. Jun 2016 B2
9385983 Sehn Jul 2016 B1
9392308 Ahmed et al. Jul 2016 B2
9396354 Murphy et al. Jul 2016 B1
9402057 Kaytaz et al. Jul 2016 B2
9407712 Sehn Aug 2016 B1
9407816 Sehn Aug 2016 B1
9412192 Mandel et al. Aug 2016 B2
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
9460541 Li et al. Oct 2016 B2
9480924 Haslam Nov 2016 B2
9485747 Rodoper et al. Nov 2016 B1
9489661 Evans et al. Nov 2016 B2
9489760 Li et al. Nov 2016 B2
9491134 Rosen et al. Nov 2016 B2
9503845 Vincent Nov 2016 B2
9508197 Quinn et al. Nov 2016 B2
9532171 Allen et al. Dec 2016 B2
9537811 Allen et al. Jan 2017 B2
9544257 Ogundokun et al. Jan 2017 B2
9576400 Van Os et al. Feb 2017 B2
9589357 Li et al. Mar 2017 B2
9592449 Barbalet et al. Mar 2017 B2
9628950 Noeth et al. Apr 2017 B1
9635195 Green et al. Apr 2017 B1
9641870 Cormie et al. May 2017 B1
9648376 Chang et al. May 2017 B2
9697635 Quinn et al. Jul 2017 B2
9706040 Kadirvel et al. Jul 2017 B2
9710821 Heath Jul 2017 B2
9744466 Fujioka Aug 2017 B2
9746990 Anderson et al. Aug 2017 B2
9749270 Collet et al. Aug 2017 B2
9792714 Li et al. Oct 2017 B2
9839844 Dunstan et al. Dec 2017 B2
9854219 Sehn Dec 2017 B2
9883838 Kaleal, III et al. Feb 2018 B2
9898849 Du et al. Feb 2018 B2
9911073 Spiegel et al. Mar 2018 B1
9936165 Li et al. Apr 2018 B2
9959037 Chaudhri et al. May 2018 B2
9980100 Charlton et al. May 2018 B1
9990373 Fortkort Jun 2018 B2
10039988 Lobb et al. Aug 2018 B2
10097492 Tsuda et al. Oct 2018 B2
10116598 Tucker et al. Oct 2018 B2
10121055 Savvides et al. Nov 2018 B1
10127945 Ho et al. Nov 2018 B2
10155168 Blackstock et al. Dec 2018 B2
10158589 Collet et al. Dec 2018 B2
10242477 Charlton et al. Mar 2019 B1
10242503 McPhee et al. Mar 2019 B2
10262250 Spiegel et al. Apr 2019 B1
10325417 Scapel et al. Jun 2019 B1
10339365 Gusarov et al. Jul 2019 B2
10360708 Bondich et al. Jul 2019 B2
10362219 Wilson et al. Jul 2019 B2
10375519 Pai et al. Aug 2019 B2
10382378 Garcia et al. Aug 2019 B2
10432559 Baldwin et al. Oct 2019 B2
10454857 Blackstock et al. Oct 2019 B1
10475225 Park et al. Nov 2019 B2
10504266 Blattner et al. Dec 2019 B2
10573048 Ni et al. Feb 2020 B2
10657701 Osman et al. May 2020 B2
10880246 Baldwin et al. Dec 2020 B2
10938758 Allen et al. Mar 2021 B2
10984569 Bondich et al. Apr 2021 B2
11048916 Gusarov et al. Jun 2021 B2
11218433 Baldwin et al. Jan 2022 B2
11229849 Blackstock et al. Jan 2022 B2
11425068 Collet et al. Aug 2022 B2
20020022506 Rifkin Feb 2002 A1
20020024528 Lambertsen Feb 2002 A1
20020029252 Segan et al. Mar 2002 A1
20020035607 Checkoway et al. Mar 2002 A1
20020047868 Miyazawa Apr 2002 A1
20020059193 Decime et al. May 2002 A1
20020067362 Agostino Nocera et al. Jun 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
20020169644 Greene Nov 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
20030045334 Hosokawa Mar 2003 A1
20030052925 Daimon et al. Mar 2003 A1
20030101230 Benschoter et al. May 2003 A1
20030110503 Perkes Jun 2003 A1
20030126215 Udell Jul 2003 A1
20030148773 Spriestersbach et al. Aug 2003 A1
20030164856 Prager et al. Sep 2003 A1
20030206171 Kim 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
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
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
20050143136 Lev et al. Jun 2005 A1
20050144241 Stata et al. Jun 2005 A1
20050162419 Kim et al. Jul 2005 A1
20050193340 Amburgey et al. Sep 2005 A1
20050193345 Klassen et al. Sep 2005 A1
20050198128 Anderson Sep 2005 A1
20050206610 Cordelli Sep 2005 A1
20050223066 Buchheit et al. Oct 2005 A1
20050280660 Seo et al. Dec 2005 A1
20050288954 McCarthy et al. Dec 2005 A1
20060026067 Nicholas et al. Feb 2006 A1
20060031412 Adams et al. Feb 2006 A1
20060107297 Toyama et al. May 2006 A1
20060114338 Rothschild Jun 2006 A1
20060119882 Harris et al. Jun 2006 A1
20060145944 Tarlton et al. Jul 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
20060294465 Ronen et al. Dec 2006 A1
20070004426 Pfleging et al. Jan 2007 A1
20070011270 Klein et al. Jan 2007 A1
20070038715 Collins et al. Feb 2007 A1
20070040931 Nishizawa Feb 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
20070113181 Blattner et al. May 2007 A1
20070136228 Petersen Jun 2007 A1
20070168863 Blattner et al. Jul 2007 A1
20070174273 Jones et al. Jul 2007 A1
20070176921 Iwasaki et al. Aug 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
20070218987 Luchene 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
20070258656 Aarabi et al. Nov 2007 A1
20070260984 Marks et al. 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
20080062141 Chandhri Mar 2008 A1
20080076505 Ngyen et al. Mar 2008 A1
20080092233 Tian et al. Apr 2008 A1
20080094387 Chen Apr 2008 A1
20080097979 Heidloff et al. 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
20080158222 Li et al. Jul 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
20080195699 Min et al. Aug 2008 A1
20080201638 Nair Aug 2008 A1
20080207176 Brackbill et al. Aug 2008 A1
20080208692 Garaventi et al. Aug 2008 A1
20080209329 Defranco et al. Aug 2008 A1
20080214210 Rasanen et al. Sep 2008 A1
20080216092 Serlet Sep 2008 A1
20080222108 Prahlad 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
20080309617 Kong et al. Dec 2008 A1
20080309675 Fleury 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
20090013268 Amit Jan 2009 A1
20090015703 Kim et al. Jan 2009 A1
20090016617 Bregman-amitai et al. Jan 2009 A1
20090024956 Kobayashi Jan 2009 A1
20090030774 Rothschild et al. Jan 2009 A1
20090030884 Pulfer et al. Jan 2009 A1
20090030999 Gatzke et al. Jan 2009 A1
20090040324 Nonaka Feb 2009 A1
20090042588 Lottin et al. Feb 2009 A1
20090044113 Jones et al. Feb 2009 A1
20090047972 Neeraj Feb 2009 A1
20090055484 Vuong et al. Feb 2009 A1
20090058822 Chaudhri Mar 2009 A1
20090070688 Gyorfi et al. Mar 2009 A1
20090079743 Pearson et al. Mar 2009 A1
20090079846 Chou Mar 2009 A1
20090087035 Wen et al. Apr 2009 A1
20090089678 Sacco et al. Apr 2009 A1
20090089710 Wood et al. Apr 2009 A1
20090093261 Ziskind Apr 2009 A1
20090099925 Mehta et al. Apr 2009 A1
20090100367 Dargahi et al. Apr 2009 A1
20090106672 Burstrom Apr 2009 A1
20090132341 Klinger May 2009 A1
20090132371 Strietzel et al. May 2009 A1
20090132453 Hangartner et al. May 2009 A1
20090132665 Thomsen et al. May 2009 A1
20090144639 Nims et al. Jun 2009 A1
20090148045 Lee et al. Jun 2009 A1
20090150778 Nicol Jun 2009 A1
20090153492 Popp Jun 2009 A1
20090153552 Fidaleo et al. Jun 2009 A1
20090157450 Athsani et al. Jun 2009 A1
20090157752 Gonzalez Jun 2009 A1
20090158170 Narayanan et al. Jun 2009 A1
20090160970 Fredlund et al. Jun 2009 A1
20090163182 Gatti et al. Jun 2009 A1
20090175521 Shadan et al. Jul 2009 A1
20090177299 Bartel Marinus Jul 2009 A1
20090177976 Bokor et al. Jul 2009 A1
20090192900 Collision Jul 2009 A1
20090199242 Johnson et al. Aug 2009 A1
20090202114 Morin et al. Aug 2009 A1
20090215469 Fisher et al. Aug 2009 A1
20090228811 Adams et al. Sep 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
20090254840 Churchill et al. Oct 2009 A1
20090254859 Arrasvuori et al. Oct 2009 A1
20090265604 Howard 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
20090300525 Jolliff et al. Dec 2009 A1
20090303984 Clark et al. Dec 2009 A1
20090319178 Khosravy Dec 2009 A1
20090319607 Belz et al. Dec 2009 A1
20090327073 Li Dec 2009 A1
20090328122 Amento Dec 2009 A1
20100010951 Miyazaki et al. Jan 2010 A1
20100011422 Mason et al. Jan 2010 A1
20100023885 Reville et al. Jan 2010 A1
20100026698 Reville et al. Feb 2010 A1
20100045660 Dettinger et al. Feb 2010 A1
20100048358 Tchao et al. Feb 2010 A1
20100062794 Han Mar 2010 A1
20100066746 Fujioka Mar 2010 A1
20100070858 Malik et al. Mar 2010 A1
20100073458 Pace Mar 2010 A1
20100082427 Burgener et al. Apr 2010 A1
20100082693 Hugg et al. Apr 2010 A1
20100083138 Dawson et al. Apr 2010 A1
20100083140 Dawson et al. Apr 2010 A1
20100083148 Finn et al. Apr 2010 A1
20100100568 Papin et al. Apr 2010 A1
20100100828 Khandelwal et al. Apr 2010 A1
20100113065 Narayan et al. May 2010 A1
20100115422 Schroeter et al. May 2010 A1
20100115426 Liu et al. May 2010 A1
20100121915 Wang May 2010 A1
20100130233 Lansing May 2010 A1
20100131880 Lee et al. May 2010 A1
20100131895 Wohlert May 2010 A1
20100138755 Kulkarni et al. Jun 2010 A1
20100146407 Bokor et al. Jun 2010 A1
20100153144 Miller et al. Jun 2010 A1
20100153868 Allen 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
20100162149 Sheleheda et al. Jun 2010 A1
20100179991 Lorch et al. Jul 2010 A1
20100183280 Beauregard et al. Jul 2010 A1
20100185552 Deluca et al. Jul 2010 A1
20100185640 Dettinger 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
20100197396 Fujii 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
20100203968 Gill 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
20100227682 Reville 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
20100274724 Bible, Jr. et al. Oct 2010 A1
20100281045 Dean Nov 2010 A1
20100281433 Moody et al. Nov 2010 A1
20100290756 Karaoguz et al. Nov 2010 A1
20100306669 Della Pasqua Dec 2010 A1
20100332980 Sun Dec 2010 A1
20110004071 Faiola et al. Jan 2011 A1
20110010205 Richards Jan 2011 A1
20110022965 Lawrence et al. Jan 2011 A1
20110029512 Folgner et al. Feb 2011 A1
20110040783 Uemichi et al. Feb 2011 A1
20110040804 Peirce et al. Feb 2011 A1
20110047404 Metzler et al. Feb 2011 A1
20110047505 Fillion 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
20110066664 Goldman et al. Mar 2011 A1
20110066743 Hurley et al. Mar 2011 A1
20110083101 Sharon et al. Apr 2011 A1
20110093780 Dunn Apr 2011 A1
20110102630 Rukes May 2011 A1
20110113323 Fillion et al. May 2011 A1
20110115798 Nayar et al. May 2011 A1
20110119133 Igelman et al. May 2011 A1
20110137881 Cheng et al. Jun 2011 A1
20110145564 Moshir et al. Jun 2011 A1
20110148864 Lee et al. Jun 2011 A1
20110153759 Rathod Jun 2011 A1
20110159890 Fortescue et al. Jun 2011 A1
20110161076 Davis 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
20110211764 Krupka et al. Sep 2011 A1
20110213845 Logan et al. Sep 2011 A1
20110215966 Kim et al. Sep 2011 A1
20110225048 Nair Sep 2011 A1
20110238762 Soni et al. Sep 2011 A1
20110238763 Shin et al. Sep 2011 A1
20110239136 Goldman et al. Sep 2011 A1
20110239143 Ye et al. Sep 2011 A1
20110244952 Schueller et al. Oct 2011 A1
20110246330 Tikku et al. Oct 2011 A1
20110248992 van Os Oct 2011 A1
20110249891 Li Oct 2011 A1
20110255736 Thompson et al. Oct 2011 A1
20110273575 Lee Nov 2011 A1
20110282799 Huston Nov 2011 A1
20110283188 Farrenkopf Nov 2011 A1
20110285703 Jin Nov 2011 A1
20110292051 Nelson et al. Dec 2011 A1
20110314419 Dunn et al. Dec 2011 A1
20110320373 Lee et al. Dec 2011 A1
20120013770 Stafford Jan 2012 A1
20120015673 Klassen et al. Jan 2012 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
20120054797 Skog et al. Mar 2012 A1
20120059722 Rao Mar 2012 A1
20120062805 Candelore Mar 2012 A1
20120069028 Bouguerra Mar 2012 A1
20120084731 Filman et al. Apr 2012 A1
20120084835 Thomas et al. Apr 2012 A1
20120099800 Llano et al. Apr 2012 A1
20120108293 Law et al. May 2012 A1
20120110002 Giambalvo et al. May 2012 A1
20120110096 Smarr et al. May 2012 A1
20120113106 Choi et al. May 2012 A1
20120113143 Adhikari et al. May 2012 A1
20120113272 Hata 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
20120130717 Xu et al. May 2012 A1
20120131502 Bock et al. May 2012 A1
20120131507 Sparandara et al. May 2012 A1
20120131512 Takeuchi et al. May 2012 A1
20120139830 Hwang et al. Jun 2012 A1
20120143760 Abulafia et al. Jun 2012 A1
20120150978 Monaco Jun 2012 A1
20120165100 Lalancette et al. 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
20120184248 Speede Jul 2012 A1
20120197724 Kendall Aug 2012 A1
20120200743 Blanchflower et al. Aug 2012 A1
20120209924 Evans et al. Aug 2012 A1
20120210244 De Francisco et al. Aug 2012 A1
20120212632 Mate et al. Aug 2012 A1
20120215879 Bozo Aug 2012 A1
20120220264 Kawabata Aug 2012 A1
20120223940 Dunstan et al. Sep 2012 A1
20120226748 Bosworth et al. Sep 2012 A1
20120229506 Nishikawa 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
20120271883 Montoya et al. Oct 2012 A1
20120278387 Garcia et al. Nov 2012 A1
20120278692 Shi Nov 2012 A1
20120290637 Perantatos et al. Nov 2012 A1
20120290977 Devecka 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
20120309520 Evertt et al. Dec 2012 A1
20120310791 Weerasinghe Dec 2012 A1
20120315987 Walling Dec 2012 A1
20120319904 Lee et al. Dec 2012 A1
20120323933 He et al. Dec 2012 A1
20120324018 Metcalf et al. Dec 2012 A1
20130006759 Srivastava et al. Jan 2013 A1
20130024757 Doll et al. Jan 2013 A1
20130031180 Abendroth et al. Jan 2013 A1
20130036165 Tseng et al. Feb 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
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
20130097547 Ohwa et al. Apr 2013 A1
20130103760 Golding et al. Apr 2013 A1
20130103766 Gupta Apr 2013 A1
20130104053 Thornton et al. Apr 2013 A1
20130110885 Brundrett, III May 2013 A1
20130111354 Marra et al. 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
20130145286 Feng et al. Jun 2013 A1
20130152000 Liu et al. Jun 2013 A1
20130155169 Hoover et al. Jun 2013 A1
20130159110 Rajaram et al. Jun 2013 A1
20130159919 Leydon Jun 2013 A1
20130169822 Zhu et al. Jul 2013 A1
20130173729 Starenky et al. Jul 2013 A1
20130174059 Van Wie et al. Jul 2013 A1
20130179520 Lee et al. Jul 2013 A1
20130182133 Tanabe Jul 2013 A1
20130185131 Sinha et al. Jul 2013 A1
20130191198 Carlson et al. Jul 2013 A1
20130194280 Kwon et al. Aug 2013 A1
20130194301 Robbins et al. Aug 2013 A1
20130198176 Kim Aug 2013 A1
20130198210 Lee et al. Aug 2013 A1
20130201187 Tong et al. 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
20130249948 Reitan Sep 2013 A1
20130257876 Davis Oct 2013 A1
20130257877 Davis Oct 2013 A1
20130258040 Kaytaz et al. Oct 2013 A1
20130258117 Penov et al. Oct 2013 A1
20130260800 Asakawa et al. Oct 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
20130311255 Cummins et al. Nov 2013 A1
20130325964 Berberat Dec 2013 A1
20130332068 Kesar et al. Dec 2013 A1
20130344896 Kirmse et al. Dec 2013 A1
20130344961 Iannetta 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
20140011576 Barbalet et al. Jan 2014 A1
20140019264 Wachman et al. Jan 2014 A1
20140032682 Prado et al. Jan 2014 A1
20140035913 Higgins et al. Feb 2014 A1
20140040066 Fujioka Feb 2014 A1
20140043204 Basnayake et al. Feb 2014 A1
20140043329 Wang 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
20140055554 Du et al. Feb 2014 A1
20140057660 Wager Feb 2014 A1
20140082651 Sharifi Mar 2014 A1
20140085293 Konoplev et al. Mar 2014 A1
20140092130 Anderson et al. Apr 2014 A1
20140095293 Abhyanker 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
20140125678 Wang et al. May 2014 A1
20140128166 Tam et al. May 2014 A1
20140129343 Finster 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
20140160149 Blackstock Jun 2014 A1
20140173424 Hogeg et al. Jun 2014 A1
20140173457 Wang et al. Jun 2014 A1
20140176662 Goodman Jun 2014 A1
20140189592 Benchenaa et al. Jul 2014 A1
20140207679 Cho Jul 2014 A1
20140214471 Schreiner, III Jul 2014 A1
20140221089 Fortkort Aug 2014 A1
20140222564 Kranendonk 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
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
20140306884 Sano et al. Oct 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
20140347368 Kishore Nov 2014 A1
20140362091 Bouaziz et al. Dec 2014 A1
20140372420 Slep Dec 2014 A1
20150020086 Chen et al. Jan 2015 A1
20150042663 Mandel et al. Feb 2015 A1
20150046278 Pei et al. Feb 2015 A1
20150071619 Brough Mar 2015 A1
20150084984 Tomii et al. Mar 2015 A1
20150086087 Ricanek, Jr. et al. Mar 2015 A1
20150087263 Branscomb et al. Mar 2015 A1
20150088464 Yuen et al. Mar 2015 A1
20150088622 Ganschow et al. Mar 2015 A1
20150095020 Leydon Apr 2015 A1
20150096042 Mizrachi Apr 2015 A1
20150116529 Wu et al. Apr 2015 A1
20150121251 Kadirvel Apr 2015 A1
20150123967 Quinn et al. May 2015 A1
20150155007 Barfield, Jr. et al. Jun 2015 A1
20150169142 Longo et al. Jun 2015 A1
20150169827 Laborde Jun 2015 A1
20150169938 Yao et al. Jun 2015 A1
20150172393 Oplinger et al. Jun 2015 A1
20150172534 Miyakawaa et al. Jun 2015 A1
20150178260 Brunson Jun 2015 A1
20150193522 Choi et al. Jul 2015 A1
20150193819 Chang Jul 2015 A1
20150195235 Trussel et al. Jul 2015 A1
20150206349 Rosenthal et al. Jul 2015 A1
20150213604 Li et al. Jul 2015 A1
20150220774 Ebersman et al. Aug 2015 A1
20150222814 Li et al. Aug 2015 A1
20150232065 Ricci et al. Aug 2015 A1
20150234942 Harmon Aug 2015 A1
20150245168 Martin Aug 2015 A1
20150261917 Smith Sep 2015 A1
20150264432 Cheng Sep 2015 A1
20150279098 Kim et al. Oct 2015 A1
20150295866 Collet et al. Oct 2015 A1
20150304806 Vincent Oct 2015 A1
20150312184 Langholz et al. Oct 2015 A1
20150342266 Cooper et al. Dec 2015 A1
20150347519 Hornkvist 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
20160045834 Burns Feb 2016 A1
20160050169 Ben et al. Feb 2016 A1
20160077603 Rinfret et al. Mar 2016 A1
20160078095 Man et al. Mar 2016 A1
20160085773 Chang et al. Mar 2016 A1
20160085863 Allen et al. Mar 2016 A1
20160086500 Kaleal, III Mar 2016 A1
20160092035 Crocker et al. Mar 2016 A1
20160093078 Davis et al. Mar 2016 A1
20160099901 Allen et al. Apr 2016 A1
20160110922 Haring Apr 2016 A1
20160134840 Mcculloch May 2016 A1
20160158600 Rolley Jun 2016 A1
20160163084 Corazza et al. Jun 2016 A1
20160164823 Nordstrom et al. Jun 2016 A1
20160179297 Lundin et al. Jun 2016 A1
20160180391 Zabaneh Jun 2016 A1
20160180447 Kamalie et al. Jun 2016 A1
20160180887 Sehn Jun 2016 A1
20160182422 Sehn et al. Jun 2016 A1
20160182875 Sehn Jun 2016 A1
20160188997 Desnoyer et al. Jun 2016 A1
20160189310 O'kane Jun 2016 A1
20160210500 Feng et al. Jul 2016 A1
20160217292 Faaborg et al. Jul 2016 A1
20160234149 Tsuda et al. Aug 2016 A1
20160239248 Sehn Aug 2016 A1
20160241504 Raji et al. Aug 2016 A1
20160253807 Jones et al. Sep 2016 A1
20160275721 Park et al. Sep 2016 A1
20160277419 Allen et al. Sep 2016 A1
20160292905 Nehmadi et al. Oct 2016 A1
20160321708 Sehn Nov 2016 A1
20160343160 Blattner et al. Nov 2016 A1
20160350297 Riza Dec 2016 A1
20160357578 Kim et al. Dec 2016 A1
20160379415 Espeset Dec 2016 A1
20170006094 Abou Mahmoud et al. Jan 2017 A1
20170006322 Dury Jan 2017 A1
20170027528 Kaleal, III et al. Feb 2017 A1
20170039752 Quinn et al. Feb 2017 A1
20170061308 Chen et al. Mar 2017 A1
20170064240 Mangat et al. Mar 2017 A1
20170069124 Tong et al. Mar 2017 A1
20170076011 Gannon Mar 2017 A1
20170080346 Abbas Mar 2017 A1
20170087473 Siegel et al. Mar 2017 A1
20170113140 Blackstock et al. Apr 2017 A1
20170118145 Aittoniemi et al. Apr 2017 A1
20170147185 Milvaney et al. May 2017 A1
20170199855 Fishbeck Jul 2017 A1
20170235848 Van Dusen et al. Aug 2017 A1
20170270970 Ho et al. Sep 2017 A1
20170286752 Gusarov et al. Oct 2017 A1
20170287006 Azmoodeh et al. Oct 2017 A1
20170310934 Du et al. Oct 2017 A1
20170312634 Ledoux Nov 2017 A1
20170324688 Collet et al. Nov 2017 A1
20170336960 Chaudhri et al. Nov 2017 A1
20170344807 Jillela et al. Nov 2017 A1
20170352179 Hardee et al. Dec 2017 A1
20180005420 Bondich et al. Jan 2018 A1
20180024726 Hviding Jan 2018 A1
20180047200 O'hara et al. Feb 2018 A1
20180088777 Daze et al. Mar 2018 A1
20180091732 Wilson et al. Mar 2018 A1
20180113587 Allen et al. Apr 2018 A1
20180115503 Baldwin et al. Apr 2018 A1
20180167468 Johnson et al. Jun 2018 A1
20180205681 Gong et al. Jul 2018 A1
20180315076 Andreou Nov 2018 A1
20180315133 Brody et al. Nov 2018 A1
20180315134 Amitay et al. Nov 2018 A1
20180352150 Purwar et al. Dec 2018 A1
20180373924 Yoo et al. Dec 2018 A1
20180374242 Li et al. Dec 2018 A1
20190001223 Blackstock et al. Jan 2019 A1
20190057616 Cohen et al. Feb 2019 A1
20190097958 Collet et al. Mar 2019 A1
20190188920 Mcphee et al. Jun 2019 A1
20190220932 Amitay et al. Jul 2019 A1
20190266390 Gusarov et al. Aug 2019 A1
20190287287 Bondich et al. Sep 2019 A1
20190332851 Han et al. Oct 2019 A1
20190386941 Baldwin et al. Dec 2019 A1
20200226848 Van Os et al. Jul 2020 A1
20210027513 Choi et al. Jan 2021 A1
20210152505 Baldwin et al. May 2021 A1
20210217217 Bondich et al. Jul 2021 A1
20210266277 Allen et al. Aug 2021 A1
20210295018 Gusarov et al. Sep 2021 A1
20220109648 Baldwin et al. Apr 2022 A1
20220134236 Blackstock et al. May 2022 A1
20220270322 Huang et al. Aug 2022 A1
Foreign Referenced Citations (104)
Number Date Country
2009283063 Feb 2010 AU
2887596 Jul 2015 CA
1455374 Nov 2003 CN
101098241 Jan 2008 CN
101884036 Nov 2010 CN
102016887 Apr 2011 CN
102289796 Dec 2011 CN
102609247 Jul 2012 CN
102985951 Mar 2013 CN
103412885 Nov 2013 CN
103426194 Dec 2013 CN
103635892 Mar 2014 CN
104717366 Jun 2015 CN
104782120 Jul 2015 CN
105118023 Dec 2015 CN
105190700 Dec 2015 CN
105279354 Jan 2016 CN
105359162 Feb 2016 CN
105409197 Mar 2016 CN
105630846 Jun 2016 CN
108885795 Nov 2018 CN
109643370 Apr 2019 CN
109863532 Jun 2019 CN
110023985 Jul 2019 CN
110168478 Aug 2019 CN
110799937 Feb 2020 CN
1736931 Dec 2006 EP
2051480 Apr 2009 EP
2151797 Feb 2010 EP
2184092 May 2010 EP
2399928 Sep 2004 GB
2001230801 Aug 2001 JP
2014006881 Jan 2014 JP
5497931 Mar 2014 JP
19990073076 Oct 1999 KR
20000063919 Nov 2000 KR
20010078417 Aug 2001 KR
20040063436 Jul 2004 KR
1020050036963 Apr 2005 KR
20060124865 Dec 2006 KR
20070008417 Jan 2007 KR
20110014224 Feb 2011 KR
20110054492 May 2011 KR
1020120070898 Jul 2012 KR
20140033088 Mar 2014 KR
101445263 Sep 2014 KR
20160016532 Feb 2016 KR
20160025365 Mar 2016 KR
20160028028 Mar 2016 KR
20160051536 May 2016 KR
20170091803 Aug 2017 KR
102233700 Mar 2021 KR
102253891 May 2021 KR
102335138 Dec 2021 KR
102372756 Mar 2022 KR
102444789 Sep 2022 KR
102459610 Oct 2022 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-03094072 Nov 2003 WO
WO-2003094072 Nov 2003 WO
WO-2004079530 Sep 2004 WO
WO-2004095308 Nov 2004 WO
WO-2006107182 Oct 2006 WO
WO-2006118755 Nov 2006 WO
WO-2007092668 Aug 2007 WO
WO-2007134402 Nov 2007 WO
WO-2009043020 Apr 2009 WO
WO-2011040821 Apr 2011 WO
WO-2011119407 Sep 2011 WO
WO-2012139276 Oct 2012 WO
WO-2013008238 Jan 2013 WO
WO-2013027893 Feb 2013 WO
WO-2013045753 Apr 2013 WO
WO-2013152454 Oct 2013 WO
WO-2013166588 Nov 2013 WO
WO-2014006129 Jan 2014 WO
WO-2014031899 Feb 2014 WO
WO-2014068573 May 2014 WO
WO-2014115136 Jul 2014 WO
2014194439 Dec 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-2016090605 Jun 2016 WO
WO-2016100318 Jun 2016 WO
WO-2016100318 Jun 2016 WO
WO-2016100342 Jun 2016 WO
WO-2016149594 Sep 2016 WO
WO-2016179166 Nov 2016 WO
WO-2017173319 Oct 2017 WO
WO-2018005644 Jan 2018 WO
WO-2018006053 Jan 2018 WO
WO-2018081013 May 2018 WO
WO-2018102562 Jun 2018 WO
WO-2018129531 Jul 2018 WO
WO-2018200042 Nov 2018 WO
WO-2018201107 Nov 2018 WO
WO-2019089613 May 2019 WO
Non-Patent Literature Citations (361)
Entry
“U.S. Appl. No. 12/471,811, Advisory Action dated Mar. 28, 2012”, 6 pgs.
“U.S. Appl. No. 12/471,811, Examiner Interview Summary dated Feb. 2, 2012”, 3 pgs.
“U.S. Appl. No. 12/471,811, Examiner Interview Summary dated Apr. 18, 2011”, 3 pgs.
“U.S. Appl. No. 12/471,811, Examiner Interview Summary dated May 27, 2014”, 2 pgs.
“U.S. Appl. No. 12/471,811, Final Office Action dated Dec. 23, 2011”, 20 pgs.
“U.S. Appl. No. 12/471,811, Non Final Office Action dated Jan. 13, 2011”, 15 pgs.
“U.S. Appl. No. 12/471,811, Non Final Office Action dated Jun. 28, 2011”, 26 pgs.
“U.S. Appl. No. 12/471,811, Non Final Office Action dated Oct. 24, 2014”, 21 pgs.
“U.S. Appl. No. 12/471,811, Notice of Allowance dated Apr. 1, 2015”, 6 pgs.
“U.S. Appl. No. 12/471,811, Response filed Jan. 26, 2015 to Non Final Office Action dated Oct. 24, 2014”, 18 pgs.
“U.S. Appl. No. 12/471,811, Response filed Feb. 23, 2012 to Final Office Action dated Dec. 23, 2011”, 12 pgs.
“U.S. Appl. No. 12/471,811, Response filed Mar. 28, 2012 to Advisory Action dated Mar. 28, 2012”, 14 pgs.
“U.S. Appl. No. 12/471,811, Response filed Apr. 13, 2011 to Non Final Office Action dated Jan. 13, 2011”, 5 pgs.
“U.S. Appl. No. 12/471,811, Response filed Sep. 28, 2011 to Non Final Office Action dated Jun. 28, 2011”, 19 pgs.
“U.S. Appl. No. 13/979,974, Corrected Notice of Allowability dated Nov. 19, 2018”, 2 pgs.
“U.S. Appl. No. 13/979,974, Examiner Interview Summary dated Jun. 29, 2017”, 3 pgs.
“U.S. Appl. No. 13/979,974, Examiner Interview Summary dated Sep. 15, 2017”, 3 pgs.
“U.S. Appl. No. 13/979,974, Final Office Action dated Apr. 25, 2018”, 18 pgs.
“U.S. Appl. No. 13/979,974, Final Office Action dated Jun. 9, 2017”, 20 pgs.
“U.S. Appl. No. 13/979,974, Final Office Action dated Oct. 12, 2016”, 13 pgs.
“U.S. Appl. No. 13/979,974, Non Final Office Action dated Feb. 22, 2017”, 17 pgs.
“U.S. Appl. No. 13/979,974, Non Final Office Action dated Apr. 27, 2016”, 16 pgs.
“U.S. Appl. No. 13/979,974, Non Final Office Action dated Oct. 3, 2017”, 17 pgs.
“U.S. Appl. No. 13/979,974, Notice of Allowance dated Aug. 10, 2018”, 9 pgs.
“U.S. Appl. No. 13/979,974, Response filed Jan. 3, 2018 to Non Final Office Action dated Oct. 3, 2017”, 8 pgs.
“U.S. Appl. No. 13/979,974, Response filed May 22, 2017 to Non Final Office Action dated Feb. 22, 2017”, 10 pgs.
“U.S. Appl. No. 13/979,974, Response filed Jul. 25, 2018 to Final Office Action dated Apr. 25, 208”, 10 pgs.
“U.S. Appl. No. 13/979,974, Response filed Jul. 26, 2016 to Non Final Office Action dated Apr. 27, 2016”, 8 pgs.
“U.S. Appl. No. 13/979,974, Response filed Sep. 11, 2017 to Final Office Action dated Jun. 9, 2017”, 8 pgs.
“U.S. Appl. No. 13/979,974, Response filed Jan. 12, 2017 to Non Final Office Action dated Apr. 27, 2016”, 8 pgs.
“U.S. Appl. No. 14/753,200, Non Final Office Action dated Oct. 11, 2016”, 6 pgs.
“U.S. Appl. No. 14/753,200, Notice of Allowance dated Apr. 27, 2017”, 7 pgs.
“U.S. Appl. No. 14/753,200, Response filed Feb. 13, 2017 to Non Final Office Action dated Oct. 11, 2016”, 9 pgs.
“U.S. Appl. No. 15/086,749, Final Office Action dated Oct. 31, 2017”, 15 pgs.
“U.S. Appl. No. 15/086,749, Non Final Office Action dated Mar. 13, 2017”, 12 pgs.
“U.S. Appl. No. 15/086,749, Non Final Office Action dated Apr. 30, 2018”, 14 pgs.
“U.S. Appl. No. 15/086,749, Response filed Apr. 2, 2018 to Final Office Action dated Oct. 31, 2017”, 14 pgs.
“U.S. Appl. No. 15/086,749, Response filed Aug. 29, 2018 to Non Final Office Action dated Apr. 30, 2018”, 12 pgs.
“U.S. Appl. No. 15/199,472, Final Office Action dated Mar. 1, 2018”, 31 pgs.
“U.S. Appl. No. 15/199,472, Final Office Action dated Nov. 15, 2018”, 37 pgs.
“U.S. Appl. No. 15/199,472, Non Final Office Action dated Jul. 25, 2017”, 30 pgs.
“U.S. Appl. No. 15/199,472, Non Final Office Action dated Sep. 21, 2018”, 33 pgs.
“U.S. Appl. No. 15/199,472, Response filed Jan. 25, 2018 to Non Final Office Action dated Jul. 25, 2017”, 13 pgs.
“U.S. Appl. No. 15/199,472, Response filed Aug. 31, 2018 to Final Office Action dated Mar. 1, 2018”, 14 pgs.
“U.S. Appl. No. 15/199,472, Response filed Oct. 17, 2018 to Non Final Office Action dated Sep. 31, 2018”, 11 pgs.
“U.S. Appl. No. 15/369,499, Non Final Office Action dated Aug. 15, 2018”, 22 pgs.
“U.S. Appl. No. 15/369,499, Response filed Nov. 15, 2018 to Non Final Office Action dated Aug. 15, 2018”, 10 pgs.
“U.S. Appl. No. 15/583,142, Non Final Office Action dated Oct. 25, 2018”, 14 pgs.
“U.S. Appl. No. 15/661,953, Examiner Interview Summary dated Nov. 13, 2018”, 3 pgs.
“U.S. Appl. No. 15/661,953, Non Final Office Action dated Mar. 26, 2018”, 6 pgs.
“U.S. Appl. No. 15/661,953, Notice of Allowance dated Aug. 10, 2018”, 7 pgs.
“U.S. Appl. No. 15/661,953, PTO Response to Rule 312 Communication dated Oct. 30, 2018”, 2 pgs.
“U.S. Appl. No. 15/661,953, PTO Response to Rule 312 Communication dated Nov. 7, 2018”, 2 pgs.
“U.S. Appl. No. 15/661,953, Response Filed Jun. 26, 2018 to Non Final Office Action dated Mar. 26, 2018”, 13 pgs.
“International Application Serial No. PCT/CA2013/000454, International Preliminary Report on Patentability dated Nov. 20, 2014”, 9 pgs.
“International Application Serial No. PCT/CA2013/000454, International Search Report dated Aug. 20, 2013”, 3 pgs.
“International Application Serial No. PCT/CA2013/000454, Written Opinion dated Aug. 20, 2013”, 7 pgs.
“International Application Serial No. PCT/US2017/025460, International Preliminary Report on Patentability dated Oct. 11, 2018”, 9 pgs.
“International Application Serial No. PCT/US2017/025460, International Search Report dated Jun. 20, 2017”, 2 pgs.
“International Application Serial No. PCT/US2017/025460, Written Opinion dated Jun. 20, 2017”, 7 pgs.
“International Application Serial No. PCT/US2017/040447, International Search Report dated Oct. 2, 2017”, 4 pgs.
“International Application Serial No. PCT/US2017/040447, Written Opinion dated Oct. 2, 2017”, 6 pgs.
“International Application Serial No. PCT/US2017/057918, International Search Report dated Jan. 19, 2018”, 3 pgs.
“International Application Serial No. PCT/US2017/057918, Written Opinion dated Jan. 19, 2018”, 7 pgs.
“International Application Serial No. PCT/US2017/063981, International Search Report dated Mar. 22, 2018”, 3 pgs.
“International Application Serial No. PCT/US2017/063981, Written Opinion dated Mar. 22, 2018”, 8 pgs.
“International Application Serial No. PCT/US2018/000112, International Search Report dated Jul. 20, 2018”, 2 pgs.
“International Application Serial No. PCT/US2018/000112, Written Opinion dated Jul. 20, 2018”, 4 pgs.
“International Application Serial No. PCT/US2018/000113, International Search Report dated Jul. 13, 2018”, 2 pgs.
“International Application Serial No. PCT/US2018/000113, Written Opinion dated Jul. 13, 2018”, 4 pgs.
“International Application Serial No. PCT/US2018/030039, International Search Report dated Jul. 11, 2018”, 2 pgs.
“International Application Serial No. PCT/US2018/030039, Written Opinion dated Jul. 11, 2018”, 4 pgs.
“International Application Serial No. PCT/US2018/030043, International Search Report dated Jul. 23, 2018”, 2 pgs.
“International Application Serial No. PCT/US2018/030043, Written Opinion dated Jul. 23, 2018”, 5 pgs.
“International Application Serial No. PCT/US2018/030044, International Search Report dated Jun. 26, 2018”, 2 pgs.
“International Application Serial No. PCT/US2018/030044, Written Opinion dated Jun. 26, 2018”, 6 pgs.
“International Application Serial No. PCT/US2018/030045, International Search Report dated Jul. 3, 2018”, 2 pgs.
“International Application Serial No. PCT/US2018/030045, Written Opinion dated Jul. 3, 2018”, 6 pgs.
“International Application Serial No. PCT/US2018/030046, International Search Report dated Jul. 6, 2018”, 2 pgs.
“International Application Serial No. PCT/US2018/030046, Written Opinion dated Jul. 6, 2018”, 6 pgs.
“List of IBM Patents or Patent Applications Treated as Related”, (Jun. 29, 2015), 2 pgs.
Broderick, Ryan, “Every thing You Need to Know About Japan's Amazing Photo Booths”, URL: https://www.buzzfeed.com/ryanhatesthis/look-how-kawaii-i-am?utm_term=.kra5QwGNZ#.muYoVB7qJ, (Jan. 22, 2016), 30 pgs.
Chan, Connie, “The Elements of Stickers”, URL: https://a16z.com/2016/06/17/stickers/, (Jun. 20, 2016), 15 pgs.
Collet, Jean Luc, et al., “Interactive avatar in messaging environment”, U.S. Appl. No. 12/471,811, filed May 26, 2009, (May 26, 2009), 31 pgs.
Dillet, Romain, “Zenly proves that location sharing isn't dead”, URL: https://techcrunch.com/2016/05/19/zenly-solomoyolo/, (accessed Jun. 27, 2018), 6 pgs.
Leyden, John, “This SMS will self-destruct in 40 seconds”, URL: http://www.theregister.co.uk/2005/12/12/stealthtext/, (Dec. 12, 2005), 1 pg.
Rhee, Chi-Hyoung, et al., “Cartoon-like Avatar Generation Using Facial Component Matching”, International Journal of Multimedia and Ubiquitous Engineering, (Jul. 30, 2013), 69-78.
“U.S. Appl. No. 15/369,499, Response filed Mar. 14, 2019 to Final Office Action dated Jan. 31, 2019”, 12 pgs.
“U.S. Appl. No. 15/365,046, Response filed Mar. 20, 2019 to Non Final Office Action dated Dec. 20, 2018”, 20 pgs.
“U.S. Appl. No. 15/365,046, Notice of Allowance dated May 21, 2019”, 14 pgs.
“European Application Serial No. 17751497.3, Response filed May 20, 2019 to Communication pursuant to Rules 161(1) and 162 EPC dated May 20, 2019”, w/ English Claims, 24 pgs.
“European Application Serial No. 17776809.0, Extended European Search Report dated Feb. 27, 2019”, 7 pgs.
“U.S. Appl. No. 15/086,749, Notice of Allowance dated Feb. 26, 2019”, 7 pgs.
“U.S. Appl. No. 15/401,926, Restriction Requirement dated Mar. 29, 2019”, 7 pgs.
“U.S. Appl. No. 15/628,408, Supplemental Amendment filed Apr. 4, 2019 to Non Final Office Action dated Jan. 2, 2019”, 12 pgs.
“International Application Serial No. PCT US2017 057918, International Preliminary Report on Patentability dated May 9, 2019”, 9 pgs.
“U.S. Appl. No. 15/199,472, Notice of Allowability dated May 13, 2019”, 3 pgs.
“U.S. Appl. No. 15/583,142, Response filed May 9, 2019 to Final Office Action dated Mar. 22, 2019”, 8 pgs.
“U.S. Appl. No. 15/401,926, Response filed May 20, 2019 to Restriction Requirement dated Mar. 29, 2019”, 9 pgs.
“U.S. Appl. No. 15/199,472, Notice of Allowance dated Mar. 18, 2019”, 23 pgs.
“U.S. Appl. No. 15/583,142, Final Office Action dated Mar. 22, 2019”, 11 pgs.
“U.S. Appl. No. 15/628,408, Response filed Apr. 2, 2019 to Non Final Office Action dated Jan. 2, 2019”, 15 pgs.
“U.S. Appl. No. 16/193,938, Preliminary Amendment filed Nov. 27, 2018”, 7 pgs.
“U.S. Appl. No. 15/365,046, Non Final Office Action dated Dec. 20, 2018”, 36 pgs.
“U.S. Appl. No. 15/086,749, Final Office Action dated Dec. 31, 2018”, 14 pgs.
“U.S. Appl. No. 15/628,408, Non Final Office Action dated Jan. 2, 2019”, 28 pgs.
“International Application Serial No. PCT US2017 040447, International Preliminary Report on Patentability dated Jan. 10, 2019”, 8 pgs.
“U.S. Appl. No. 15/199,472, Response filed Jan. 15, 2019 to Final Office Action dated Nov. 15, 2018”, 14 pgs.
“U.S. Appl. No. 15/369,499, Final Office Action dated Jan. 31, 2019”, 22 pgs.
“U.S. Appl. No. 15/583,142, filed Jan. 28, 2019 to Response Filed Non Final Office Action dated Oct. 25, 2018”.
“U.S. Appl. No. 15/086,749, Response filed Feb. 11, 2019 to Final Office Action dated Dec. 31, 2018”, 10 pgs.
Petovello, Mark, “How does a GNSS receiver estimate velocity?”, [Online] Retrieved from the internet:http:insidegnss.com wp-content uploads 2018 01 marapr15-SOLUTIONS.pdf., (Mar.-Apr. 2015), 3 pgs.
“A Guide to Advertising on Campus With Snapchat Geofilters”, College Marketing Group, [Online] Retrieved from the Internet : <URL: https://collegemarketinggroup.com/blog/a-guide-toadvertising-on-campus-with-snapchat-geofilters/>, (Jul. 25, 2016), 5 pgs.
“U.S. Appl. No. 15/369,499, Final Office Action dated Oct. 1, 2019”, 17 pgs.
“U.S. Appl. No. 15/369,499, Non Final Office Action dated Jun. 17, 2019”, 17 pgs.
“U.S. Appl. No. 15/369,499, Response filed Sep. 10, 2019 to Non-Final Office Action dated Jun. 17, 2019”, 9 pgs.
“U.S. Appl. No. 15/401,926, Non Final Office Action dated Aug. 6, 2019”, 9 pgs.
“U.S. Appl. No. 15/401,926, Response filed Nov. 6, 2019 to Non Final Office Action dated Aug. 6, 2019”, 10 pgs.
“U.S. Appl. No. 15/583,142, Notice of Allowance dated Jun. 6, 2019”, 8 pgs.
“U.S. Appl. No. 15/628,408, Final Office Action dated Jun. 10, 2019”, 44 pgs.
“U.S. Appl. No. 15/628,408, Non Final Office Action dated Oct. 30, 2019”, 45 pgs.
“U.S. Appl. No. 15/628,408, Response filed Aug. 12, 2019 to Final Office Action dated Jun. 10, 2019”, 12 pgs.
“U.S. Appl. No. 15/901,387, Non Final Office Action dated Oct. 30, 2019”, 40 pgs.
“U.S. Appl. No. 16/365,300, Non Final Office Action dated Oct. 30, 2019”, 40 pgs.
“European Application Serial No. 17876226.6, Extended European Search Report dated Sep. 5, 2019”, 10 pgs.
“International Application Serial No. PCT/US2017/063981, International Preliminary Report on Patentability dated Jun. 13, 2019”, 10 pgs.
“Introducing Google Latitude”, Google UK, [Online] Retrieved from the Internet: <URL: https://www.youtube.com/watch?v=XecGMKqiA5A>, [Retrieved on: Oct. 23, 2019], (Feb. 3, 2009), 1 pg.
“Korean Application Serial No. 10-2018-7031055, Notice of Preliminary Rejection dated Aug. 6, 2019”, w/ English Translation, 13 pgs.
“Korean Application Serial No. 10-2018-7031055, Response filed Oct. 7, 2019 to Notice of Preliminary Rejection dated Aug. 6, 2019”, w/o English Claims, 26 pgs.
Alex, Heath, “What do Snapchat's emojis mean?—Understanding these emojis will turn you into a Snapchat pro”, Business Insider, [Online] Retrieved from the Internet: <URL: https://www.businessinsider.com/what-do-snapchats-emojismean-2016-5?international=true&r=US&IR=T>, (May 28, 2016), 1 pg.
Finn, Greg, “Miss Google Latitude? Google Plus With Location Sharing Is Now a Suitable Alternative”, Cypress North, [Online] Retrieved from the Internet: <URL: https://cypressnorth.com/social-media/miss-google-latitude-google-location-sharing-now-suitable-alternative/>, [Retrieved on: Oct. 24, 2019], (Nov. 27, 2013), 10 pgs.
Karen, Tumbokon, “Snapchat Update: How to Add Bitmoji to Customizable Geofilters”, International Business Times, [Online] Retrieved from the Internet: <URL: https://www.ibtimes.com/snapchat-update-how-add-bitmojicustomizable-geofilters-2448152>, (Nov. 18, 2016), 6 pgs.
Lapenna, Joe, “The Official Google Blog. Check in with Google Latitude”, Google Blog, [Online] Retrieved from the Internet: <https://web.archive.org/web/20110201201006/https://googleblog.blogspot.com/2011/02/check-in-with-google-latitude.html>, [Retrieved on: Oct. 23, 2019], (Feb. 1, 2011), 6 pgs.
Neis, Pascal, “The OpenStreetMap Contributors Map aka Who's around me?”, [Online] Retrieved from the Internet by the examiner on Jun. 5, 2019: <URL: https://neis-one.org/2013/01/oooc/>, (Jan. 6, 2013), 7 pgs.
Sophia, Bernazzani, “A Brief History of Snapchat”, Hubspot, [Online] Retrieved from the Internet: <URL: https://blog.hubspot.com/marketing/history-of-snapchat>, (Feb. 10, 2017), 12 pgs.
Sulleyman, Aatif, “Google Maps Could Let Strangers Track Your Real-Time Location for Days at a Time”, The Independent, [Online] Retrieved from the Internet by the examiner on Jun. 5, 2019: <URL: https://www.independent.co.uk/life-style/gadgets-and-tech/news/google-maps-track-location-real-time-days-privacy-security-stalk-gps-days-a7645721.html>, (Mar. 23, 2017), 5 pgs.
Zibreg, “How to share your real time location on Google Maps”, idownloadblog.com, [Online] Retrieved from the Internet: <URL: https://www.idownloadblog.com/2017/04/12/how-to-share-location-google-maps/>; [Retrieved on: Oct. 23, 2019], (Apr. 12, 2017), 23 pgs.
“U.S. Appl. No. 15/369,499, Non Final Office Action dated Mar. 2, 2020”, 17 pgs.
“U.S. Appl. No. 15/369,499, Response filed Feb. 3, 2020 to Final Office Action dated Oct. 1, 2019”, 10 pgs.
“U.S. Appl. No. 15/401,926, Advisory Action dated Mar. 11, 2020”, 2 pgs.
“U.S. Appl. No. 15/401,926, Final Office Action dated Nov. 21, 2019”, 9 pgs.
“U.S. Appl. No. 15/401,926, Response filed Feb. 21, 2020 to Final Office Action dated Nov. 21, 2019”, 9 pgs.
“U.S. Appl. No. 15/628,408, Response filed Jan. 30, 2020 to Non Final Office Action dated Oct. 30, 2019”, 17 pgs.
“U.S. Appl. No. 16/126,869, Non Final Office Action dated Feb. 5, 2020”, 7 pgs.
“U.S. Appl. No. 16/193,938, Non Final Office Action dated Jan. 16, 2020”, 11 pgs.
“U.S. Appl. No. 16/365,300, Response filed Jan. 30, 2020 to Non Final Office Action dated Oct. 30, 2019”, 16 pgs.
“U.S. Appl. No. 16/409,390, Non Final Office Action dated Jan. 8, 2020”, 14 pgs.
“U.S. Appl. No. 16/433,725, Non Final Office Action dated Feb. 27, 2020”, 34 pgs.
“European Application Serial No. 17776809.0, Communication Pursuant to Article 94(3) EPC dated Dec. 9, 2019”, 4 pgs.
“European Application Serial No. 18791925.3, Extended European Search Report dated Jan. 2, 2020”, 6 pgs.
“International Application Serial No. PCT/US2018/000112, International Preliminary Report on Patentability dated Nov. 7, 2019”, 6 pgs.
“International Application Serial No. PCT/US2018/030044, International Preliminary Report on Patentability dated Nov. 7, 2019”, 8 pgs.
“Korean Application Serial No. 10-2018-7031055, Office Action dated Feb. 25, 2020”, w/ English Translation, 7 pgs.
“U.S. Appl. No. 15/369,499, Final Office Action dated Jun. 15, 2020”, 17 pgs.
“U.S. Appl. No. 15/369,499, Response filed Jun. 2, 2020 to Non Final Office Action dated Mar. 2, 2020”, 9 pgs.
“U.S. Appl. No. 15/401,926, Non Final Office Action dated Mar. 30, 2020”, 9 pgs.
“U.S. Appl. No. 15/628,408, Final Office Action dated Apr. 13, 2020”, 45 pgs.
“U.S. Appl. No. 15/628,408, Response filed Jul. 13, 2020 to Final Office Action dated Apr. 13, 2020”, 20 pgs.
“U.S. Appl. No. 16/126,869, Final Office Action dated Jul. 7, 2020”, 8 pgs.
“U.S. Appl. No. 16/126,869, Response filed May 5, 2020 to Non Final Office Action dated Feb. 5, 2020”, 8 pgs.
“U.S. Appl. No. 16/193,938, Response filed Mar. 24, 2020 to Non Final Office Action dated Jan. 16, 2020”, 10 pgs.
“U.S. Appl. No. 16/365,300, Final Office Action dated May 13, 2020”, 44 pgs.
“U.S. Appl. No. 16/409,390, Final Office Action dated Jun. 15, 2020”, 12 pgs.
“U.S. Appl. No. 16/409,390, Response filed Apr. 2, 2020 to Non Final Office Action dated Jan. 8, 2020”, 10 pgs.
“U.S. Appl. No. 16/433,725, Final Office Action dated Jun. 2, 2020”, 29 pgs.
“U.S. Appl. No. 16/433,725, Response filed May 8, 2020 to Non Final Office Action dated Feb. 27, 2020”, 13 pgs.
“European Application Serial No. 17776809.0, Response filed Mar. 19, 2020 to Communication Pursuant to Article 94(3) EPC dated Dec. 9, 2019”, 25 pgs.
“European Application Serial No. 17876226.6, Communication Pursuant to Article 94(3) EPC dated May 29, 2020”, 5 pgs.
“European Application Serial No. 17876226.6, Response filed Mar. 30, 2020 to Extended European Search Report dated Sep. 5, 2019”, 22 pgs.
“Korean Application Serial No. 10-2018-7031055, Response filed Mar. 27, 2020 to Office Action dated Feb. 25, 2020”, w/ English claims, 24 pgs.
“Korean Application Serial No. 10-2019-7002736, Notice of Preliminary Rejection dated May 25, 2020”, w/ English Translation, 16 pgs.
“Korean Application Serial No. 10-2019-7018501, Notice of Preliminary Rejection dated Apr. 16, 2020”, w/ English Translation, 20 pgs.
“Korean Application Serial No. 10-2019-7018501, Response filed Jun. 16, 2020 to Notice of Preliminary Rejection dated Apr. 16, 2020”, w/ English Claims, 17 pgs.
Gundersen, Eric, “Foursquare Switches to MapBox Streets, Joins the OpenStreetMap Movement”, [Online] Retrieved from the Internet: <URL: https://blog.mapbox.com/foursquare-switches-to-mapbox-streets-joins-the-openstreetmap-movement-29e6a17f4464>, (Mar. 6, 2012), 4 pgs.
Perez, Sarah, “Life 360, The Family Locator With More Users Than Foursquare, Raises a $10 Million Series B”, [Online] Retrieved from the Internet: <URL: https://techcrunch.com/2013/07/10/life360-the-family-locator-with-more-users-than-foursquare-raises-10-million-series-b/>, (Jul. 10, 2013), 2 pgs.
“U.S. Appl. No. 15/369,499, Examiner Interview Summary dated Sep. 21, 2020”, 3 pgs.
“U.S. Appl. No. 15/369,499, Examiner Interview Summary dated Oct. 9, 2020”, 2 pgs.
“U.S. Appl. No. 15/369,499, Notice of Allowance dated Oct. 26, 2020”, 16 pgs.
“U.S. Appl. No. 15/369,499, Response filed Sep. 15, 2020 to Final Office Action dated Jun. 15, 2020”, 10 pgs.
“U.S. Appl. No. 15/401,926, Response filed Jul. 30, 2020 to Non Final Office Action dated Mar. 30, 2020”, 10 pgs.
“U.S. Appl. No. 15/628,408, Notice of Allowance dated Sep. 29, 2020”, 13 pgs.
“U.S. Appl. No. 16/126,869, Response filed Oct. 7, 2020 to Final Office Action dated Jul. 7, 2020”, 10 pgs.
“U.S. Appl. No. 16/193,938, Final Office Action dated Aug. 28, 2020”, 10 pgs.
“U.S. Appl. No. 16/365,300, Non Final Office Action dated Sep. 28, 2020”, 40 pgs.
“U.S. Appl. No. 16/365,300, Response filed Aug. 13, 2020 to Final Office Action dated May 13, 2020”, 16 pgs.
“U.S. Appl. No. 16/409,390, Non Final Office Action dated Sep. 11, 2020”, 15 pgs.
“U.S. Appl. No. 16/409,390, Response filed Aug. 5, 2020 to Final Office Action dated Jun. 15, 2020”, 11 pgs.
“U.S. Appl. No. 16/433,725, Examiner Interview Summary dated Jul. 20, 2020”, 4 pgs.
“U.S. Appl. No. 16/433,725, Non Final Office Action dated Aug. 20, 2020”, 29 pgs.
“U.S. Appl. No. 16/433,725, Response filed Aug. 3, 2020 to Final Office Action dated Jun. 2, 2020”, 12 pgs.
“U.S. Appl. No. 16/552,003, Notice of Allowance dated Aug. 27, 2020”, 15 pgs.
“U.S. Appl. No. 16/563,445, Non Final Office Action dated Sep. 29, 2020”, 11 pgs.
“European Application Serial No. 17876226.6, Response filed Oct. 2, 2020 to Communication Pursuant to Article 94(3) EPC dated May 29, 2020”, 22 pgs.
“European Application Serial No. 18791925.3, Response Filed Jul. 27, 2020 to Extended European Search Report dated Jan. 2, 2020”, 19 pgs.
“Korean Application Serial No. 10-2019-7002736, Response filed Jul. 9, 2020 to Notice of Preliminary Rejection dated May 25, 2020”, w/ English Claims, 29 pgs.
“Korean Application Serial No. 10-2019-7014555, Notice of Preliminary Rejection dated Jul. 20, 2020”, w/ English Translation, 12 pgs.
“Korean Application Serial No. 10-2019-7018501, Final Office Action dated Sep. 8, 2020”, w/ English translation, 9 pgs.
“Korean Application Serial No. 10-2020-7022773, Notice of Preliminary Rejection dated Aug. 23, 2020”, w/ English translation, 11 pgs.
“U.S. Appl. No. 15/369,499, Corrected Notice of Allowability dated Jan. 28, 2021”, 3 pgs.
“U.S. Appl. No. 15/401,926, Final Office Action dated Feb. 12, 2021”, 10 pgs.
“U.S. Appl. No. 15/401,926, Non Final Office Action dated Oct. 27, 2020”, 10 pgs.
“U.S. Appl. No. 15/401,926, Response filed Jan. 27, 2021 to Non Final Office Action dated Oct. 27, 2020”, 9 pgs.
“U.S. Appl. No. 16/126,869, Final Office Action dated Feb. 8, 2021”, 8 pgs.
“U.S. Appl. No. 16/126,869, Non Final Office Action dated Oct. 30, 2020”, 9 pgs.
“U.S. Appl. No. 16/126,869, Response filed Feb. 1, 2021 to Non Final Office Action dated Oct. 30, 2020”, 9 pgs.
“U.S. Appl. No. 16/193,938, Non Final Office Action dated Feb. 24, 2021”, 10 pgs.
“U.S. Appl. No. 16/193,938, Response filed Nov. 30, 2020 to Final Office Action dated Aug. 28, 2020”, 9 pgs.
“U.S. Appl. No. 16/365,300, Final Office Action dated Apr. 15, 2021”, 31 pgs.
“U.S. Appl. No. 16/365,300, Response filed Jan. 28, 2021 to Non Final Office Action dated Sep. 28, 2020”, 17 pgs.
“U.S. Appl. No. 16/409,390, Final Office Action dated Dec. 23, 2020”, 15 pgs.
“U.S. Appl. No. 16/409,390, Notice of Allowance dated Feb. 22, 2021”, 7 pgs.
“U.S. Appl. No. 16/409,390, Response filed Feb. 8, 2021 to Final Office Action dated Dec. 23, 2020”, 11 pgs.
“U.S. Appl. No. 16/409,390, Response filed Dec. 8, 2020 to Non Final Office Action dated Sep. 11, 2020”, 12 pgs.
“U.S. Appl. No. 16/433,725, Notice of Allowance dated Dec. 16, 2020”, 8 pgs.
“U.S. Appl. No. 16/433,725, Response filed Nov. 16, 2020 to Non Final Office Action dated Aug. 20, 2020”, 12 pgs.
“U.S. Appl. No. 16/433,725, Supplemental Notice of Allowability dated Jan. 25, 2021”, 2 pgs.
“U.S. Appl. No. 16/563,445, Final Office Action dated Mar. 8, 2021”, 11 pgs.
“U.S. Appl. No. 16/563,445, Response filed Jan. 29, 2021 to Non Final Office Action dated Sep. 29, 2020”, 9 pgs.
“U.S. Appl. No. 17/247,169, Preliminary Amendment filed Feb. 2, 2021”, 7 pgs.
“European Application Serial No. 17776809.0, Communication Pursuant to Article 94(3) EPC dated Apr. 23, 2021”, 4 pgs.
“Korean Application Serial No. 10-2019-7002736, Final Office Action dated Nov. 26, 2020”, w/ English Translation, 8 pgs.
“Korean Application Serial No. 10-2019-7002736, Response filed Dec. 28, 2020 to Final Office Action dated Nov. 26, 2020”, w/ English Claims, 16 pgs.
“Korean Application Serial No. 10-2019-7018501, Response filed Dec. 7, 2020 to Final Office Action dated Sep. 8, 20”, w/ English Claims, 27 pgs.
“Korean Application Serial No. 10-2020-7022773, Notice of Preliminary Rejection dated Feb. 26, 2021”, w/ English Translation, 11 pgs.
“Korean Application Serial No. 10-2020-7022773, Response filed Oct. 19, 2020 to Notice of Preliminary Rejection dated Aug. 23, 2020”, w/ English Claims, 26 pgs.
“Korean Application Serial No. 10-2020-7035136, Notice of Preliminary Rejection dated Feb. 25, 2021”, w/ English Translation, 5 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. 17/247,169, Corrected Notice of Allowability dated Oct. 15, 2021”, 7 pgs.
“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.
“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.
“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.
“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.
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.
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.
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.
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.
“U.S. Appl. No. 15/401,926, Notice of Allowance dated May 26, 2021”, 8 pgs.
“U.S. Appl. No. 15/401,926, Response filed May 12, 2021 to Final Office Action dated Feb. 12, 2021”, 9 pgs.
“U.S. Appl. No. 15/628,408, Corrected Notice of Allowability dated Jul. 21, 2021”, 7 pgs.
“U.S. Appl. No. 15/628,408, Notice of Allowance dated Jul. 8, 2021”, 11 pgs.
“U.S. Appl. No. 16/126,869, Non Final Office Action dated May 19, 2021”, 8 pgs.
“U.S. Appl. No. 16/126,869, Response filed May 10, 2021 to Final Office Action dated Feb. 8, 2021”, 10 pgs.
“U.S. Appl. No. 16/126,869, Response filed Aug. 19, 2021 to Non Final Office Action dated May 19, 2021”, 10 pgs.
“U.S. Appl. No. 16/193,938, Advisory Action dated Aug. 17, 2021”, 2 pgs.
“U.S. Appl. No. 16/193,938, Final Office Action dated Jun. 10, 2021”, 11 pgs.
“U.S. Appl. No. 16/193,938, Response filed May 24, 2021 to Non Final Office Action dated Feb. 24, 2021”, 9 pgs.
“U.S. Appl. No. 16/193,938, Response filed Aug. 10, 2021 to Final Office Action dated Jun. 10, 2021”, 10 pgs.
“U.S. Appl. No. 16/365,300, Non Final Office Action dated Aug. 3, 2021”, 29 pgs.
“U.S. Appl. No. 16/365,300, Response filed Jul. 15, 2021 to Final Office Action dated Apr. 15, 2021”, 11 pgs.
“U.S. Appl. No. 16/409,390, Corrected Notice of Allowability dated May 19, 2021”, 4 pgs.
“U.S. Appl. No. 16/563,445, Non Final Office Action dated Aug. 20, 2021”, 15 pgs.
“U.S. Appl. No. 16/563,445, Response filed Jun. 8, 2021 to Final Office Action dated Mar. 8, 2021”, 8 pages.
“U.S. Appl. No. 17/247,169, Corrected Notice of Allowability dated Jul. 9, 2021”, 2 pgs.
“U.S. Appl. No. 17/247,169, Notice of Allowance dated Jul. 2, 2021”, 14 pgs.
“European Application Serial No. 17751497.3, Communication Pursuant to Article 94(3) EPC dated Jun. 2, 2021”, 4 pgs.
“European Application Serial No. 17776809.0, Response filed Aug. 20, 2021 to Communication Pursuant to Article 94(3) EPC dated Apr. 23, 2021”, 7 pgs.
“European Application Serial No. 18791925.3, Communication Pursuant to Article 94(3) EPC dated May 11, 2021”, 7 pgs.
“Korean Application Serial No. 10-2019-7034899, Notice of Preliminary Rejection dated May 27, 2021”, w/ English Translation, 17 pgs.
“Korean Application Serial No. 10-2019-7034899, Response filed Aug. 11, 2021 to Notice of Preliminary Rejection dated May 27, 2021”, w/ English claims, 26 pgs.
“Korean Application Serial No. 10-2020-7022773, Response filed Apr. 7, 2021 to Notice of Preliminary Rejection dated Feb. 26, 2021”, w/ English Claims, 12 pgs.
“Korean Application Serial No. 10-2021-7008607, Notice of Preliminary Rejection dated Jun. 1, 2021”, w/ English Translation, 5 pgs.
“Korean Application Serial No. 10-2021-7008607, Response filed Aug. 2, 2021 to Notice of Preliminary Rejection dated Jun. 1, 2021”, w/ English Claims, 17 pgs.
“Korean Application Serial No. 10-2021-7010821, Notice of Preliminary Rejection dated May 28, 2021”, w/ English Translation, 18 pgs.
“Korean Application Serial No. 10-2021-7010821, Response filed Jul. 28, 2021 to Notice of Preliminary Rejection dated May 28, 2021”, w/ English Claims, 31 pgs.
“Korean Application Serial No. 10-2021-7014438, Notice of Preliminary Rejection dated Aug. 9, 2021”, w/ English Translation, 4 pgs.
Wilmott, Clancy, et al., “Playful Mapping in the Digital Age”, Playful Mapping Collective, Institute of Network Cultures, Amsterdam, (2016), 158 pgs.
“U.S. Appl. No. 15/401,926, Corrected Notice of Allowability dated Nov. 15, 2021”, 2 pgs.
“U.S. Appl. No. 15/401,926, Corrected Notice of Allowability dated Nov. 16, 2021”, 2 pgs.
“U.S. Appl. No. 15/401,926, Corrected Notice of Allowability dated Dec. 22, 2021”, 2 pgs.
“U.S. Appl. No. 15/628,408, Non Final Office Action dated Feb. 4, 2022”, 30 pgs.
“U.S. Appl. No. 15/628,408, Supplemental Notice of Allowability dated Oct. 21, 2021”, 2 pgs.
“U.S. Appl. No. 16/126,869, Final Office Action dated Nov. 29, 2021”, 9 pgs.
“U.S. Appl. No. 16/193,938, Non Final Office Action dated Nov. 12, 2021”, 5 pgs.
“U.S. Appl. No. 16/365,300, Examiner Interview Summary dated Nov. 29, 2021”, 2 pgs.
“U.S. Appl. No. 16/365,300, Response filed Dec. 2, 2021 to Non Final Office Action dated Aug. 3, 2021”, 10 pgs.
“U.S. Appl. No. 16/563,445, Final Office Action dated Jan. 11, 2022”, 17 pgs.
“U.S. Appl. No. 16/563,445, Response filed Nov. 22, 2021 to Non Final Office Action dated Aug. 20, 2021”, 10 pgs.
“U.S. Appl. No. 17/247,169, Corrected Notice of Allowability dated Nov. 30, 2021”, 2 pgs.
“U.S. Appl. No. 17/314,963, Non Final Office Action dated Feb. 2, 2022”, 24 pgs.
“U.S. Appl. No. 17/450,040, Preliminary Amendment filed Jan. 19, 2022”, 7 pgs.
“U.S. Appl. No. 17/451,285, Preliminary Amendment filed Dec. 28, 2021”, 7 pgs.
“European Application Serial No. 17751497.3, Response filed Sep. 16, 2021 to Communication Pursuant to Article 94(3) EPC dated Jun. 2, 2021”, 15 pgs.
“European Application Serial No. 17876226.6, Communication Pursuant to Article 94(3) EPC dated Dec. 14, 2021”, 4 pgs.
“Korean Application Serial No. 10-2019-7034899, Final Office Action dated Dec. 3, 2021”, With English translation, 10 pgs.
“Korean Application Serial No. 10-2021-7008607, Notice of Preliminary Rejection dated Dec. 7, 2021”, w/ English translation, 6 pgs.
“Korean Application Serial No. 10-2021-7010821, Final Office Action dated Nov. 29, 2021”, w/ English translation, 7 pgs.
“Korean Application Serial No. 10-2021-7014438, Response filed Oct. 12, 2021 to Notice of Preliminary Rejection dated Aug. 9, 2021”, w/ English Claims, 15 pgs.
“U.S. Appl. No. 15/628,408, Examiner Interview Summary dated Jul. 27, 2022”, 2 pgs.
“U.S. Appl. No. 15/628,408, Final Office Action dated Jun. 10, 2022”, 33 pgs.
“U.S. Appl. No. 15/628,408, Response filed May 4, 2022 to Non Final Office Action dated Feb. 4, 2022”, 9 pgs.
“U.S. Appl. No. 15/628,408, Response filed Aug. 10, 2022 to Final Office Action dated Jun. 10, 2022”, 14 pgs.
“U.S. Appl. No. 16/126,869, Decision on Pre-Appeal Brief Request for Review dated May 13, 2022”, 2 pgs.
“U.S. Appl. No. 16/126,869, Pre-Appeal Brief Request for Review filed Mar. 29, 2022”, 4 pgs.
“U.S. Appl. No. 16/193,938, Notice of Allowance dated Mar. 3, 2022”, 8 pgs.
“U.S. Appl. No. 16/193,938, PTO Response to Rule 312 Communication dated Jul. 13, 2022”, 2 pgs.
“U.S. Appl. No. 16/193,938, Response filed Feb. 14, 2022 to Non Final Office Action dated Nov. 12, 2021”, 3 pgs.
“U.S. Appl. No. 16/365,300, Examiner Interview Summary dated Jul. 29, 2022”, 2 pgs.
“U.S. Appl. No. 16/365,300, Final Office Action dated Mar. 25, 2022”, 29 pgs.
“U.S. Appl. No. 16/365,300, Non Final Office Action dated Aug. 18, 2022”, 31 pgs.
“U.S. Appl. No. 16/365,300, Response filed Jul. 25, 2022 to Final Office Action dated Mar. 25, 2022”, 13 pgs.
“U.S. Appl. No. 16/563,445, Non Final Office Action dated May 19, 2022”, 17 pgs.
“U.S. Appl. No. 16/563,445, Response filed Apr. 11, 2022 to Final Office Action dated Jan. 11, 2022”, 10 pgs.
“U.S. Appl. No. 17/215,152, Final Office Action dated Jul. 6, 2022”, 24 pgs.
“U.S. Appl. No. 17/215,152, Non Final Office Action dated Mar. 14, 2022”, 28 pgs.
“U.S. Appl. No. 17/215,152, Response filed Jun. 14, 2022 to Non Final Office Action dated Mar. 14, 2022”, 12 pgs.
“U.S. Appl. No. 17/314,963, Final Office Action dated Jul. 11, 2022”, 25 pgs.
“U.S. Appl. No. 17/314,963, Response filed May 2, 2022 to Non Final Office Action dated Feb. 2, 2022”, 10 pgs.
“Chinese Application Serial No. 201780022014.5, Office Action dated Dec. 22, 2021”, w/ English Translation, 13 pgs.
“Chinese Application Serial No. 201780022014.5, Response filed May 6, 2022 to Office Action filed Dec. 22, 2021”, w/ English Claims, 15 pgs.
“European Application Serial No. 17876226.6, Response Filed Apr. 22, 2022 Communication Pursuant to Article 94(3) EPC dated Dec. 14, 2021”, 16 pgs.
“Korean Application Serial No. 10-2021-7008607, Response filed Jan. 11, 2022 to Notice of Preliminary Rejection dated Dec. 7, 2021”, w/English Claims, 12 pgs.
“Korean Application Serial No. 10-2021-7039311, Notice of Preliminary Rejection dated Jan. 24, 2022”, w/ English Translation, 11 pgs.
“Korean Application Serial No. 10-2021-7039311, Response Filed Feb. 23, 2022 to Notice of Preliminary Rejection dated Jan. 24, 2022”, w/ English Claims, 24 pgs.
“Korean Application Serial No. 10-2022-7015893, Notice of Preliminary Rejection dated Aug. 11, 2022”, W/English Translation, 6 pgs.
“Korean Application Serial No. 10-2019-7034899, Office Action dated Jan. 24, 2022”, w/ English Translation, 12 pgs.
“Korean Application Serial No. 10-2019-7034899, Response filed Jan. 5, 2022 to Office Action dated Dec. 3, 2021”, w/ English Translation of Claims, 12 pgs.
“Korean Application Serial No. 10-2021-7010821, Response filed Dec. 30, 2021 to Office Action dated Nov. 29, 2021”, w/ English Translation of Claims, 22 pgs.
Frisch, Mathias, et al., “Grids & guides: multi-touch layout and alignment tools”, Proceedings of the ACM SIGCHI Conference on Human Factors in Computing Systems, Vancouver, BC, CA, (2011), 4 pgs.
Xu, B, et al., “Automatic archiving versus default deletion: what Snapchat tells us about ephemerality in design”, In Proceedings of the 19th ACM conference on computer-supported cooperative work & social computing, (Feb. 2016), 1662-1675.
“U.S. Appl. No. 15/628,408, Non Final Office Action dated Dec. 27, 2022”, 36 pgs.
“U.S. Appl. No. 16/126,869, Appeal Brief filed Sep. 13, 2022”, 14 pgs.
“U.S. Appl. No. 16/126,869, Corrected Notice of Allowability dated Nov. 16, 2022”, 2 pgs.
“U.S. Appl. No. 16/126,869, Notice of Allowance dated Nov. 9, 2022”, 7 pgs.
“U.S. Appl. No. 16/126,869, Supplemental Notice of Allowability dated Feb. 16, 2023”, 2 pgs.
“U.S. Appl. No. 16/365,300, Final Office Action dated Dec. 30, 2022”, 31 pgs.
“U.S. Appl. No. 16/365,300, Response filed Dec. 19, 2022 to Non Final Office Action dated Aug. 18, 2022”, 11 pgs.
“U.S. Appl. No. 16/563,445, Final Office Action dated Nov. 18, 2022”, 20 pgs.
“U.S. Appl. No. 16/563,445, Pre-Appeal Brief Request filed Feb. 21, 2023”. 10 pgs.
“U.S. Appl. No. 16/563,445, Response filed Oct. 19, 2022 to Non Final Office Action dated May 19, 2022”, 13 pgs.
“U.S. Appl. No. 17/215,152, Final Office Action dated Jan. 6, 2023”, 23 pgs.
“U.S. Appl. No. 17/215,152, Non Final Office Action dated Oct. 12, 2022”, 24 pgs.
“U.S. Appl. No. 17/215,152, Response Filed Sep. 2, 2022 to Final Office Action dated Jul. 6, 2022”, 11 pgs.
“U.S. Appl. No. 17/215,152, Response filed Dec. 21, 2022 to Non Final Office Action dated Oct. 12, 2022”, 11 pgs.
“U.S. Appl. No. 17/303,875, Corrected Notice of Allowability dated Dec. 21, 2022”, 5 pgs.
“U.S. Appl. No. 17/303,875, Notice of Allowance dated Dec. 9, 2022”, 9 pgs.
“U.S. Appl. No. 17/314,963, Advisory Action dated Sep. 27, 2022”, 3 pgs.
“U.S. Appl. No. 17/314,963, Corrected Notice of Allowability dated Jan. 26, 2023”, 2 pgs.
“U.S. Appl. No. 17/314,963, Notice of Allowance dated Jan. 13, 2023”, 6 pgs.
“U.S. Appl. No. 17/314,963, Response filed Sep. 12, 2022 to Final Office Action dated Jul. 11, 2022”, 11 pgs.
“U.S. Appl. No. 17/314,963, Response filed Oct. 11, 2022 to Advisory Action dated Sep. 27, 2022”, 10 pgs.
“Chinese Application Serial No. 201780022014.5, Decision of Rejection dated Sep. 28, 2022”, w/ English Translation, 10 pgs.
“Chinese Application Serial No. 201780052571.1, Office Action dated Dec. 5, 2022”, w/ English Translation, 15 pgs.
“Chinese Application Serial No. 201780065441.1, Office Action dated Dec. 2, 2022”, w/ English translation, 13 pgs.
“Chinese Application Serial No. 201780073911.9, Office Action dated Nov. 2, 2022”, W/ English Translation, 7 pgs.
“European Application Serial No. 17751497.3, Summons to Attend Oral Proceedings mailed Dec. 20, 2022”, 5 pgs.
“European Application Serial No. 17776809.0, Communication Pursuant to Article 94(3) EPC dated Dec. 19, 2022”, 7 pgs.
“Korean Application Serial No. 10-2022-7013956, Notice of Preliminary Rejection dated Jan. 13, 2023”, w/ English Translation, 22 pgs.
“Korean Application Serial No. 10-2022-7015893, Response filed Oct. 7, 2022 to Notice of Preliminary Rejection dated Aug. 11, 2022”, w/ English Claims, 17 pgs.
Heath, Alex, “What do Snapcht's emoji mean?—Understanding these emoji will turn you into a Snapchat pro”. [Online]. Retrieved from the Internet: <URL:http://www.businessinsider.com/what-do-snapchats-emojis-mean-2016-5?international=true&r=US&IR=T>, (May 28, 2016), 3 pgs.
Vaynerchuk, Gary, “How to Create and Use Snapchat's New Custom Geofilters”, [Online] Retrieved from the Internet: <https://garyvaynerchuk.com/how-to-create-and-use-snapchats-new-custom-geofilters//>. (Mar. 15, 2016), 15 pgs.
Provisional Applications (1)
Number Date Country
62412115 Oct 2016 US
Continuations (1)
Number Date Country
Parent 15369499 Dec 2016 US
Child 16115259 US