U.S. patent number 11,069,103 [Application Number 15/492,077] was granted by the patent office on 2021-07-20 for customized user interface for electronic communications.
This patent grant is currently assigned to Snap Inc.. The grantee listed for this patent is Snap Inc.. Invention is credited to Jacob Edward Blackstock, Diego Munoz Escalante, Matthew Colin Grantham, William Wu.
United States Patent |
11,069,103 |
Blackstock , et al. |
July 20, 2021 |
Customized user interface for electronic communications
Abstract
Among other things, embodiments of the present disclosure
improve the functionality of electronic messaging software and
systems by providing a customized display of avatars corresponding
to users exchanging electronic communications, such as short
message service (SMS) or multimedia service (MMS) texts and emails.
The appearance of the displayed avatars may be dynamically altered
based on the actions taken by the users, as well as based on the
content of the messages between the users or information from other
sources.
Inventors: |
Blackstock; Jacob Edward
(Toronto, CA), Escalante; Diego Munoz (Toronto,
CA), Grantham; Matthew Colin (Toronto, CA),
Wu; William (Venice, CA) |
Applicant: |
Name |
City |
State |
Country |
Type |
Snap Inc. |
Santa Monica |
CA |
US |
|
|
Assignee: |
Snap Inc. (Santa Monica,
CA)
|
Family
ID: |
76861472 |
Appl.
No.: |
15/492,077 |
Filed: |
April 20, 2017 |
Current U.S.
Class: |
1/1 |
Current CPC
Class: |
G06T
11/60 (20130101); G06F 16/9535 (20190101); G06F
16/436 (20190101); G06V 40/161 (20220101) |
Current International
Class: |
G06F
3/048 (20130101); G06T 11/60 (20060101); G06K
9/00 (20060101) |
References Cited
[Referenced By]
U.S. Patent Documents
Foreign Patent Documents
|
|
|
|
|
|
|
2887596 |
|
Jul 2015 |
|
CA |
|
109863532 |
|
Jun 2019 |
|
CN |
|
110168478 |
|
Aug 2019 |
|
CN |
|
2184092 |
|
May 2010 |
|
EP |
|
2001230801 |
|
Aug 2001 |
|
JP |
|
5497931 |
|
Mar 2014 |
|
JP |
|
101445263 |
|
Sep 2014 |
|
KR |
|
WO-2003094072 |
|
Nov 2003 |
|
WO |
|
WO-2004095308 |
|
Nov 2004 |
|
WO |
|
WO-2006107182 |
|
Oct 2006 |
|
WO |
|
WO-2007134402 |
|
Nov 2007 |
|
WO |
|
WO-2012139276 |
|
Oct 2012 |
|
WO |
|
WO-2013027893 |
|
Feb 2013 |
|
WO |
|
WO-2013152454 |
|
Oct 2013 |
|
WO |
|
WO-2013166588 |
|
Oct 2013 |
|
WO |
|
WO-2014031899 |
|
Feb 2014 |
|
WO |
|
WO-2014194439 |
|
Dec 2014 |
|
WO |
|
WO-2016090605 |
|
Jun 2016 |
|
WO |
|
WO-2018081013 |
|
May 2018 |
|
WO |
|
WO-2018102562 |
|
Jun 2018 |
|
WO |
|
WO-2018129531 |
|
Jul 2018 |
|
WO |
|
WO-2019089613 |
|
May 2019 |
|
WO |
|
Other References
Leyden, John, "This SMS will self-destruct in 40 seconds",
[Online]. Retrieved from the Internet: <URL:
http://www.theregister.co.uk/2005/12/12/stealthtext/, (Dec. 12,
2005), 1 pg. cited by applicant.
|
Primary Examiner: Vu; Thanh T
Attorney, Agent or Firm: Schwegman Lundberg & Woessner,
P.A.
Claims
What is claimed is:
1. A system comprising: a processor; and memory coupled to the
processor and storing instructions that, when executed by the
processor, cause the system to perform operations comprising:
receiving, over the Internet, an electronic communication from a
first computing device of a first user; transmitting, over the
Internet, the electronic communication to a second computing device
of a second user; analyzing content within the electronic
communication to identify a tone associated with the content;
determining, based on the identified tone, a mood of the first
user; retrieving, from a database in communication with system,
avatar characteristics associated with the first user; generating a
media overlay which includes an avatar of the first user, the
avatar of the first user being based on the retrieved avatar
characteristics associated with the first user, the media overlay
including additional image or text content that is based on the
determined mood of the first user; generating a media content item
which includes the media overlay combined with an image feed
captured by a camera coupled to the first computing device; causing
presentation of the electronic communication and the media content
item within a chat interface window displayed on a respective
display screen coupled to the first computing device and the second
computing device, wherein the chat interface window corresponds to
a group conversation between participants including the first user
and the second user, and wherein the chat interface window includes
a border along which respective avatars of the participants are
displayed.
2. The system of claim 1, wherein the memory further stores
instructions for causing the system to perform operations
comprising: analyzing content within a plurality of electronic
communications exchanged between the first computing device and the
second computing device to identify a tone associated with the
content; determining the mood of the first user and a mood of the
second user based on the identified tone of the content;
retrieving, from the database coupled to the system, avatar
characteristics associated with the second user; and generating an
avatar of the second user based on the retrieved avatar
characteristics associated with the second user and the determined
mood of the second user.
3. The system of claim 1, wherein generating the avatar of the
first user includes: retrieving an image of the first user's face
via the camera coupled to the first computing device; and
generating facial features of the avatar based on the image of the
first user's face.
4. The system of claim 1, wherein the content within the electronic
communication includes audio content, and wherein determining the
mood of the first user includes performing a voice analysis on the
audio content.
5. The system of claim 1, wherein the content within the electronic
communication includes text input, and wherein determining the mood
of the first user includes performing a text analysis on the text
input.
6. The system of claim 1, wherein determining the mood of the first
user is based on input from the first user via the first computing
device, the input comprising one or more mood selections.
7. The system of claim 1, further comprising: receiving
supplemental information specific to the first user, wherein
determining the mood of the first user is further based on the
supplemental information, and wherein the supplemental information
corresponds to at least one of: a calendar entry stored on the
first computing device, the calendar entry being specific to the
first user, a social network entry stored in association with a
user account corresponding to the first user, or motion sensor data
which is associated with the first computing device and which
corresponds to a user activity of the first user.
8. The system of claim 1, wherein determining the mood of the first
user includes determining a level of the mood among a plurality of
mood levels, the level of the mood comprising a numeric scale, and
wherein the plurality of mood levels includes a first mood level
and a second mood level, the first mood level having a lesser mood
level than the second mood level.
9. The system of claim 8, wherein the system determines the mood
level for the first user as the first mood level, and wherein
generating the avatar of the first user includes depicting a first
expression on a face of the avatar corresponding to the first mood
level.
10. The system of claim 9, wherein the system determines the mood
level for the first user as the second mood level, and wherein
generating the avatar of the first user includes depicting a second
expression on the face of the avatar corresponding to the second
mood level, the second expression being different from the first
expression.
11. The system of claim 1, wherein determining the mood for the
first user is further based on a relationship between the first
user and the second user.
12. The system of claim 11, wherein the group conversation is
between the first user, the second user, and a third user, wherein
determining the mood for the first user includes determining a
second mood for the first user based on the identified tone and a
relationship between the first user and the third user, and wherein
generating the avatar of the first user includes: generating a
first avatar for the first user based on the retrieved avatar
characteristics and the determined mood of the first user; and
generating a second avatar for the first user based on the
retrieved avatar characteristics and the second determined mood of
the first user.
13. The system of claim 12, wherein causing presentation of the
avatar of the first user includes: causing presentation of the
first avatar of the first user on the display screen of the second
computing device; and causing presentation of the second avatar of
the first user on a display screen of a third computing device of
the third user.
14. The system of claim 1, further comprising: determining that the
first user has muted the group conversation; and causing, based on
the first user muting the group conversation, presentation of the
avatar of the first user to be in a contracted state with respect
to the border of the chat interface window.
15. A computer-implemented method comprising: receiving, by a
computer system over the Internet, an electronic communication from
a first computing device of a first user; transmitting, by the
computer system over the Internet, the electronic communication to
a second computing device of a second user; analyzing, by the
computer system, content within the electronic communication to
identify a tone associated with the content; determining, by the
computer system based on the identified tone, a mood of the first
user; retrieving, by the computer system from a database in
communication with computer system, avatar characteristics
associated with the first user; generating, by the computer system,
a media overlay which includes an avatar of the first user, the
avatar of the first user being based on the retrieved avatar
characteristics associated with the first user, the media overlay
including additional image or text content that is based on the
determined mood of the first user; generating, by the computer
system, a media content item which includes the media overlay
combined with an image feed captured by a camera coupled to the
first computing device; causing, by the computer system,
presentation of the electronic communication and the media content
item within a chat interface window displayed on a respective
display screen coupled to the first computing device and the second
computing device, wherein the chat interface window corresponds to
a group conversation between participants including the first user
and the second user, and wherein the chat interface window includes
a border along which respective avatars of the participants are
displayed.
16. A non-transitory computer-readable medium storing instructions
that, when executed by a computer system, cause the computer system
to perform operations comprising: receiving, over the Internet, an
electronic communication from a first computing device of a first
user; transmitting, over the Internet, the electronic communication
to a second computing device of a second user; analyzing content
within the electronic communication to identify a tone associated
with the content; determining, based on the identified tone, a mood
of the first user; retrieving, from a database in communication
with computer system, avatar characteristics associated with the
first user; generating a media overlay which includes an avatar of
the first user, the avatar of the first user being based on the
retrieved avatar characteristics associated with the first user,
the media overlay including additional image or text content that
is based on the determined mood of the first user; generating a
media content item which includes the media overlay combined with
an image feed captured by a camera coupled to the first computing
device; causing presentation of the electronic communication and
the media content item within a chat interface window displayed on
a respective display screen coupled to the first computing device
and the second computing device, wherein the chat interface window
corresponds to a group conversation between participants including
the first user and the second user, and wherein the chat interface
window includes a border along which respective avatars of the
participants are displayed.
Description
BACKGROUND
The popularity of electronic communications, particularly instant
messaging, continues to grow. Users increasingly share media
content items such as electronic images and videos with each other,
reflecting a global demand to communicate more visually. Similarly,
users increasingly seek to communicate with each other in more
interactive ways via electronic communications, thus providing
challenges to social networking systems seeking to facilitate such
communications between their members. 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.
FIG. 4 is a flow diagram of an exemplary process according to
various aspects of the disclosure.
FIGS. 5A-5D are screenshots illustrating the aspects of the method
described in FIG. 4.
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 software and systems by
providing a customized display of avatars corresponding to users
exchanging electronic communications, such as short message service
(SMS) or multimedia service (MMS) texts and emails. The appearance
of the displayed avatars may be dynamically altered based on the
actions taken by the users, as well as based on the content of the
messages between the users or information from other sources.
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.RTM. 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.times.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 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 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, 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.RTM. 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.RTM. 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, embodiments of the present
disclosure may generate, display, distribute, and apply media
overlays to media content items. For example, embodiments may
utilize media content items generated by a client device 102 (e.g.,
an image or video captured using a digital camera coupled to the
client device 102) to generate media overlays that can be applied
to other media content items.
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)
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.RTM. 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. 4 depicts an exemplary process according to various aspects of
the present disclosure. In this example, method 400 includes
receiving an electronic communication (405), transmitting the
electronic communication to one or more computing devices (410),
analyzing the content of the electronic communication to identify a
tone associated with the content (415), determining a mood of one
or more users based on the identified tone (420), retrieving avatar
characteristics for one or more users from a database (425),
generating one or more avatars based on the avatar characteristics
and the identified tone (430), and presenting the generated
avatar(s) on the respective display screens of one or more
computing devices (435). The steps of method 400 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 7.
In method 400, the system may receive (405) an electronic
communication from, and transmit the electronic communication to
(410), a variety of different systems and devices. For example,
messaging system 108 in FIG. 1 may receive a electronic
communication from a first client computing device 102 via a
network 106 (e.g., the Internet) and transmit the electronic
communication to a second client computing device 102 via the
network 106.
Electronic communications (and their content) exchanged between
computing devices (which may also be referred to as a
"conversation" in this Application) may be analyzed (415) to
identify a tone associated with the conversation and to determine a
mood (420) of a user associated with the communication. As a
threshold matter, the system may, prior to performing the steps of
method 400, confirm authorization by one or more users to analyze
the user's communications. Such authorization may be obtained via
acceptance of a terms of service for utilizing an online social
network or other service provided by the system, by acceptance on a
case-by-case basis by the user (e.g., via popups displayed on the
user's computing device) or using any other suitable method for
obtaining authorization by the user(s).
The system may identify any number of different tones associated
with an electronic communication or group of electronic
communications. In this context, the "tone" identified for a
communication may include any attitude, sentiment, emotional state,
and the like. For example, the system may analyze a series of
communications between a first user and a second user regarding a
successful interview by the first user that resulted in a job
offer. In this example, the system may identify various "positive"
tones such as "excitement," "pride," "relief," and the like in the
messages by the first user. Messages from the second user may
likewise be positive (e.g., "congratulatory," "happy," etc.). The
communications may include various other tones (e.g., broadly
classified as "neutral," or "negative").
For example, the first user may, along with the positive comments,
include some content in the communications having a generally
negative tone. The user might convey "apprehension," or
"nervousness" at the prospect of switching jobs, as well as
"sadness" or "loss" at the prospect of leaving friends and
co-workers at his/her current job. Likewise, the second user may
include comments in the communications that are "neutral" (e.g., a
question such as "when do you start?" or "how long was the
interview?") as well as comments that are "negative" (e.g., sadness
over the prospect of the first user moving out of town for the new
job, etc.).
The tone of a communication or group of communications in a
conversation may be determined based on any desired scale, and
comments having different tones within the same conversation may be
analyzed to determine an overall tone of the conversation. For
example, "positive," "neutral," and "negative" tones may each
include different numeric scales and weights. Continuing the new
job example above, the first user's communications to the second
user might include five positive statements, eight neutral
statements, and two negative statements. The system may give
neutral statements less weight than positive statements or negative
statements, and determine that the overall tone of the conversation
is positive based on the greater number of positive statements
compared to negative statements.
The system may determine the mood (420) of the user based on the
identified tones. Moods may be characterized on a numeric scale,
may be associated with different key words or terms, and may
overlap any of the values or keywords assigned to the tone of a
conversation. For example, if the tone of a conversation is
determined to be "sad," the mood of one or more of the users
involved in the conversation may likewise be determined to be
"sad."
The system may analyze the content of electronic communications
based on the form of the content in the communications. For
example, electronic communications containing text content provided
by a user (e.g., via the input device of the user's computing
device and transmitted in text messages, emails, etc.) may be
analyzed by a text analysis software application to identify words
and phrases and the respective tone/sentiment of such words and
phrases in the context of the communication. Similarly, voice or
audio input provided by a user in an electronic communication
(e.g., in a voice communication or an audio file attached to or
embedded in an email or text message) may be analyzed using a voice
analysis software application. Image analysis software and video
analysis software could likewise be used by embodiments of the
disclosure to analyze image and video content in communications
between users.
The system may determine a user's mood based on data from
additional sources, such as from calendar entries on the user's
computing device, information retrieved from social media networks
to which a user belongs, and information retrieved from a sensor
coupled to the user's computing device. For example, the system may
identify an event, (such as a party, birthday, anniversary, etc.)
on the user's calendar and determine the user's mood based on the
event. Relatively "positive" events (e.g., a birthday party) may
thus be reflected by showing the user's avatar smiling, along with
clothing or other accessories (e.g., a birthday cake in front of
the user's avatar) appropriate to the event. Relatively "negative"
events (e.g., a scheduled root canal) may be identified by the
system and reflected by showing the user frowning in pain and
holding his/her jaw.
The system may also analyze data from sensors coupled to the user's
computing device (e.g., GPS sensors, accelerometers, etc.) to
determine the user's mood based on the user's location and
activities. For example, the system may use location and
accelerometer data from the user's mobile device to determine the
user is currently jogging or working out, and depict the user's
avatar as sweating, lifting weights, exhausted, etc. as a result.
In this manner, the system can automatically provide visual
representations of events involving the users in a conversation,
thus helping to spur additional conversation about such events.
In some embodiments, the system may determine the mood for a user,
or generate a particular avatar, based on the user's relationship
with other users. For example, the system may identify the
relationships between a first user and other users to which the
user communicates. For example, the system may identify
friendships, romantic relationships, work colleagues, etc. In such
a case, the system may determine from the tone of a communication
involving the first user that a first user's mood as "sad" and
generate a first avatar of the first user that is crying. The
system may display this first (crying) avatar of the first user to
the computing devices of users having a relatively close
relationship with the user (e.g., friends, family, romantic
interests). By contrast, the system may generate a second avatar
having a relatively neutral expression to display to the computing
devices of users having a relatively distant relationship with the
user (e.g., acquaintances, work colleagues, etc.). Accordingly,
some users may see the first avatar of the user, while other users
will see the second avatar. In this manner, the system can help
convey the first user's mood to other users with whom the first
user is close, but present the second avatar to maintain a more
neutral posture with users with whom the user has a more distant
relationship.
In method 400, the system retrieves avatar characteristics (425)
for one or more users associated with the electronic communications
received (405) and transmitted (410) by the system. Additionally or
alternatively, the system may retrieve avatar characteristics for a
user unrelated to an electronic communication, 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.
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. The avatar characteristics may be retrieved (425)
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 an avatar of a user (430) based on the
retrieved avatar characteristics, as well as the identified mood
for the user. In some embodiments, the system may generate features
of the avatar of a user, such as the user's hairstyle, eyeglasses,
skin tone, clothing, and other features using the avatar
characteristics, while varying the user's facial expressions, body
language, and other features based on the identified mood. For
example, if the user's mood is determined to be "positive" or
"happy" the system may generate the avatar as smiling, as depicted
in FIG. 5A. By contrast, if the user's mood is determined to be
"negative" or "sad," the system may generate the avatar as
frowning. In some embodiments, the system may also generate a
"neutral" expression or body language to correspond, for example,
to a user who hasn't made any positive or negative statements in a
conversation.
An avatar for a user may be generated (430) based on an image
(still or video) of the user. Likewise, the mood of the user may be
determined based on such an image. For example, a user may capture
a "selfie" (an image of the user's face captured using a camera
coupled to the user's mobile computing device) and submit it to the
system. The system may perform a software facial recognition
analysis on the image to generate the avatar of the user, as well
as to examine the user's facial features and apparent actions
within the image (e.g., smiling, frowning, laughing, crying, etc.)
to determine the user's mood. The system may then generate the
facial features of the user's avatar in accordance with the
identified facial features from the user's image. The mood of the
user may also be determined based on other input from the user,
such as an explicit selection (e.g., from the user's mobile
computing device) by the user to display a "happy," "sad," or
"neutral" avatar appearance. In this manner, the user can override
the system's interpretation of the user's mood and display the
specific avatar appearance the user wishes to show other users.
The mood of a user may be determined on any desired scale. In some
embodiments, for example, the user's mood may first be
characterized with a categorical term, such as "happy," "sad,"
"angry," "neutral," "tired," "scared," etc. Within each categorical
term, the system may then determine the user's mood among a
plurality of mood levels to reflect the degree to which a user is
"happy," "sad," etc. In some embodiments the mood levels may be
ranged on a numerical scale (e.g., 1-10). The level of a user's
mood may in turn affect the facial expression or other features on
the user's avatar generated by the system and presented on the
display screens of the users' computing devices.
For example, the system may determine a user is slightly sad (e.g.,
a 1 on a scale of 1-10) and represent this emotion with a slight
frown on the avatar's face. By contrast, where the system
determines the user is very happy (e.g., a 10 on a 1-10 scale), the
system may depict the user's avatar with a large smile, laughing,
with the avatar's arms raised overhead. Other features, such as
text and images, may be displayed to help convey the user's mood as
well. In FIG. 5D, for example, the system adds the "quittin' time"
content to convey the user is happy to be leaving work for the
day.
The avatar may be generated in conjunction with a media content
item. The media content item may include static (i.e., non-moving)
avatars as well as dynamic (i.e., moving) avatars. In FIGS. 5A-5C,
for example, user avatars involved in a conversation (e.g., an
electronic group chat) are displayed along the top of the chat
interface window, and presented on the display screens of the
computing devices of the users in the chat. The display of avatars
may be dynamic, and can extend from displaying the avatar of a
single user (e.g., starting a chat) in FIG. 5A, to displaying the
avatars of multiple users involved in the chat, as shown in FIG.
5C. Likewise, the facial expressions and other features of the
users may change dynamically as the conversation progresses and as
the users' moods are reassessed by the system.
The appearance of the avatars generated by the system and presented
on the display screens of the users' devices may further be
modified based on actions taken by the respective users during a
conversation. For example, a user may select an option within the
group chat displayed in FIGS. 5A-5C to change the user's status
from "online" to "away" or "do not disturb." In response, the
system may modify the avatar corresponding to the user from
displaying the user's avatar above the top line of the chat window
(in FIG. 5A) to showing the user's avatar "hiding" below the top
line of the chat window in a contracted state. The contracted state
could also be shown in response to the user not participating in
the chat for a predetermined period of time, muting the group
conversation the user is involved in, or other actions. Other
representations, such as showing the avatar turning his/her back
could also be used to indicate a user is unavailable, or not
participating, in a conversation.
The system may alter the appearance of the avatars to correspond to
any desired action (or inaction) by the users. In some embodiments,
for example, the system may generate avatars based on a user's
interaction with software applications on the user's computing
device. In a specific example, the system may detect that a user
has opened a software application on the users' computing device
for displaying a live image from a camera coupled to the user's
computing device. In response, the system may generate an avatar as
part of a media overlay applied to the live image, as depicted in
FIG. 5D. The image and media overlay in FIG. 5D may be displayed
within the chat window depicted in FIGS. 5A-5C, or attached to
another form of electronic communication (e.g., email, text, etc.)
to another user.
A variety of media content items containing the avatars of users
may be generated and displayed in conjunction with embodiments of
the present disclosure. 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 may include
content that 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 some embodiments, the media content item generated by the system
may be included in a media overlay such as a "sticker" (i.e., an
image that can be overlaid onto other images), filter (discussed
above), or another media overlay. Such overlays may include static
(i.e., non-moving) features as well as dynamic (i.e., moving)
features.
Embodiments of the present disclosure may transmit and receive
electronic communications containing avatars, media content items,
media overlays, or other content any form of electronic
communication, such as SMS texts, MMS texts, emails, and other
communications. Avatars and media content items included in such
communications may be provided as attachments, displayed inline in
the message, within media overlays, or conveyed in any other
suitable manner.
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 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), 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 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.RTM.
drivers, flash memory drivers, serial communication drivers (e.g.,
Universal Serial Bus (USB) drivers), Wi-Fi.RTM. 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 or other components 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 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 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 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 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,
or a game application. Third-party applications 640 may include an
application developed using the ANDROID.TM. or IOS.TM. 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.TM., ANDROID.TM., WINDOWS.RTM. 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 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)) 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 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 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 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.RTM. components (e.g.,
Bluetooth.RTM. Low Energy), Wi-Fi.RTM. 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.RTM. 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, SNAP,
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.
* * * * *
References