U.S. patent application number 17/567397 was filed with the patent office on 2022-04-21 for multichannel system.
The applicant listed for this patent is Snap Inc.. Invention is credited to Nicholas Richard Allen, Nicholas James Bell, Andrew Cooper, Chamal Samaranayake, William Wu.
Application Number | 20220121332 17/567397 |
Document ID | / |
Family ID | |
Filed Date | 2022-04-21 |
View All Diagrams
United States Patent
Application |
20220121332 |
Kind Code |
A1 |
Allen; Nicholas Richard ; et
al. |
April 21, 2022 |
MULTICHANNEL SYSTEM
Abstract
Systems and methods for presenting content that depicts one or
more stories are provided. Content that depicts one or more stories
is received from a first client device. The content that depicts
the one or more stories is grouped into an edition being used to
represent the one or more stories. A discovery page that enables
selection of the edition is generated. Presentation of the
discovery page is caused on a second client device.
Inventors: |
Allen; Nicholas Richard;
(Venice, CA) ; Bell; Nicholas James; (Venice,
CA) ; Cooper; Andrew; (Los Angeles, CA) ;
Samaranayake; Chamal; (Venice, CA) ; Wu; William;
(Marina del Rey, CA) |
|
Applicant: |
Name |
City |
State |
Country |
Type |
Snap Inc. |
Santa Monica |
CA |
US |
|
|
Appl. No.: |
17/567397 |
Filed: |
January 3, 2022 |
Related U.S. Patent Documents
|
|
|
|
|
|
Application
Number |
Filing Date |
Patent Number |
|
|
16529461 |
Aug 1, 2019 |
11249617 |
|
|
17567397 |
|
|
|
|
15152975 |
May 12, 2016 |
10416845 |
|
|
16529461 |
|
|
|
|
14612692 |
Feb 3, 2015 |
10133705 |
|
|
15152975 |
|
|
|
|
62105199 |
Jan 19, 2015 |
|
|
|
International
Class: |
G06F 3/0482 20060101
G06F003/0482; G06F 3/0485 20060101 G06F003/0485; G06F 3/04883
20060101 G06F003/04883; G06F 40/169 20060101 G06F040/169; G06F
3/04845 20060101 G06F003/04845; G06F 40/106 20060101 G06F040/106;
G06F 3/04842 20060101 G06F003/04842; G06F 3/04817 20060101
G06F003/04817 |
Claims
1. A method comprising: receiving, a first plurality of content
items from a first user account of a social networking system, the
first plurality of content items comprising multiple files each
corresponding to a different layer of content, a first file of the
multiple files received from the first user account comprising a
first video including video content, and a second file of the
multiple files received from the first user account comprising
shortened video content of the first video, the second file being
received separately from the first file from the first user
account; generating a first layer of content that includes the
second video and a second layer of content that includes the first
video; causing display of the first layer of content on a client
device; receiving, from the client device, a user interaction with
the first layer of content; responsive to the receiving of the user
interaction, causing display of the second layer of content.
2. The method of claim 1, wherein: the first layer of content is
configured to display the second layer of content in response to
receiving a particular user input; the user interaction comprises
touch input at a particular area of the display; the second video
includes less than all of the video content of the first video, and
the method further comprises: receiving a second plurality of
content items from a second user account of the social networking
system; generating a first graphic in response to the reception of
the first plurality of content items received from the first user
account; generating a second graphic in response to the reception
of the second plurality of content items received from the second
user account; generating a graphical user interface to include the
first graphic; configuring the graphical user interface to display
content from the first user account upon selection of the first
graphic based, in part, on the first plurality of content items
being received from the first user account; further generating the
graphical user interface to include the second graphic; configuring
the graphical user interface to display content from the second
user account upon selection of the second graphic based, in part,
on the second plurality of content items being received from the
second user account; and causing presentation, via a server of the
social networking system, of the graphical user interface in a
social networking client application of a third user account.
3. The method of claim 1, further comprising: causing display of an
indication of an area of the display that is configured to receive
the user interaction to cause display of the second layer;
receiving, from a first user of the client device, an annotation to
the second layer of content displayed; and modifying the second
layer of content based on the received annotation, wherein the
annotated second layer of content is presented to a second user of
another client device.
4. The method of claim 1, further comprising: receiving a plurality
of content items from a plurality of additional user accounts of
the social networking system; generating a corresponding plurality
of graphics corresponding to each of the additional user accounts;
and generating a graphical user interface to display each of the
plurality of graphics, each of the plurality of graphics configured
to display content from the corresponding user account in response
to a selection of the graphic.
5. The method of claim 1, further comprising: grouping the first
plurality of content items based on the first plurality of content
items being received within a predetermined window of elapsed
time.
6. The method of claim 1, further comprising: receiving additional
content from a device of a provider; and generating a link in a
generated home page that corresponds to the additional content.
7. The method of claim 6, further comprising: generating a
thumbnail image in the generated home page that corresponds to the
provider, an appearance of the thumbnail image being subject to
change based on display of the additional content.
8. The method of claim 1, wherein: the first layer of content is
displayed on a screen of the client device; and the user
interaction includes a swipe across the first layer of content
displayed on the screen of the client device.
9. The method of claim 1, further comprising receiving third and
fourth files of the multiple files from the first user account, the
third file comprising an image or video associated with a travel
destination, and the fourth file comprising descriptive information
about the travel destination.
10. The method of claim 1, further comprising presenting, together
with the second layer of content, a visual indication of an amount
of time remaining before an annotation associated with the second
layer of content is deleted.
11. The method of claim 1, wherein the second video comprises a
video clip corresponding to the first video, further comprising
overlaying one or more images on top of the video clip as the video
clip is being played in the first layer of content.
12. The method of claim 1, further comprising: causing display of a
plurality of indicators of different subsets of content, wherein
the first layer of content corresponding to a first subset of the
different subsets of content is displayed in response to receiving
input that selects a given indicator of the plurality of indicators
that is associated with the first video, and wherein the given
indicator is animated to change an appearance of the given
indicator in response to determining that all content associated
with the first subset has been viewed.
13. The method of claim 1, further comprising: generating a third
layer of content that includes an image or video associated with a
travel destination; receiving, from the client device, a user
interaction with the third layer of content; and responsive to the
receiving of the user interaction with the third layer of content,
causing display of a fourth layer of content that includes a
plurality of description comprising descriptive information about
the travel destination.
14. The method of claim 13, wherein the plurality of descriptions
in the fourth layer of content comprising a story about the travel
destination, one or more events at the travel destination, and food
associated with the travel destination.
15. The method of claim 1, further comprising: causing an upload
page to be presented to a user associated with the first user
account; receiving, via the upload page, the first file in response
receiving first input from the user that drags the first file into
a first section of the upload page corresponding to the second
layer; and receiving, via the upload page, the second file in
response receiving second input from the user that drags the second
file into a second section of the upload page corresponding to the
first layer.
16. The method of claim 1, further comprising: receiving a
scheduled time for presenting the first layer of content from a
first user associated with the first user account; and causing
presentation of the first layer of content to a second user,
associated with a second user account, during the scheduled
time.
17. The method of claim 1, further comprising: causing display of a
plurality of indicators of different subsets of content, wherein
the first layer of content is displayed in response to receiving
input that selects a given indicator of the plurality of indicators
that is associated with the first video; and causing display of a
selectable link in the second layer of content together with the
first video, wherein the plurality of indicators are displayed in
response detecting activation of the selectable link, and wherein
an animation is displayed in response to detecting activation of
the selectable link.
18. The method of claim 17, wherein each of the subsets of content
is associated with a different day of the week.
19. A system comprising: one or more hardware processors and
executable instructions accessible on a non-transitory
computer-readable medium that, when executed, configure the one or
more hardware processors to perform operations comprising:
receiving, a first plurality of content items from a first user
account of a social networking system, the first plurality of
content items comprising multiple files each corresponding to a
different layer of content, a first file of the multiple files
received from the first user account comprising a first video
including video content, and a second file of the multiple files
received from the first user account comprising shortened video
content of the first video, the second file being received
separately from the first file from the first user account;
generating a first layer of content that includes the second video
and a second layer of content that includes the first video;
causing display of the first layer of content on a client device;
receiving, from the client device, a user interaction with the
first layer of content; responsive to the receiving of the user
interaction, causing display of the second layer of content.
20. A non-transitory machine-readable medium storing instructions
that, when executed by one or more processors of a machine, cause
the machine to perform operations comprising: receiving, a first
plurality of content items from a first user account of a social
networking system, the first plurality of content items comprising
multiple files each corresponding to a different layer of content,
a first file of the multiple files received from the first user
account comprising a first video including video content, and a
second file of the multiple files received from the first user
account comprising shortened video content of the first video, the
second file being received separately from the first file from the
first user account; generating a first layer of content that
includes the second video and a second layer of content that
includes the first video; causing display of the first layer of
content on a client device; receiving, from the client device, a
user interaction with the first layer of content; responsive to the
receiving of the user interaction, causing display of the second
layer of content.
Description
CROSS-REFERENCE TO RELATED APPLICATIONS
[0001] This application is a continuation of U.S. patent
application Ser. No. 16/529,461, filed on Aug. 1, 2019, which is a
continuation of U.S. patent application Ser. No. 15/152,975, filed
on May 12, 2016, which is a continuation of U.S. patent application
Ser. No. 14/612,692, filed on Feb. 3, 2015, which claims the
priority benefit of U.S. Provisional Application Ser. No.
62/105,199, filed on Jan. 19, 2015, each of which are hereby
incorporated herein by reference in their entireties.
TECHNICAL FIELD
[0002] Embodiments of the present disclosure relate generally to
data processing and, more particularly, but not by way of
limitation, to discovery of content grouped into an edition.
BACKGROUND
[0003] In recent years, use of mobile devices, wearable devices,
smart devices, and the like have each increased among consumers. In
fact, these devices pervade nearly every aspect of modern life.
Further, the use of mobile devices for messaging and consumption of
information has also increased.
BRIEF DESCRIPTION OF THE DRAWINGS
[0004] Various ones of the appended drawings merely illustrate
example embodiments of the present disclosure and should not be
considered as limiting its scope.
[0005] FIG. 1 is a block diagram illustrating a networked system,
according to some example embodiments.
[0006] FIG. 2 is a block diagram illustrating components of a
discovery system, according to some example embodiments.
[0007] FIG. 3 is a user interface of a discovery page, according to
some example embodiments.
[0008] FIGS. 4-7 are user interfaces of a story from an edition,
according to some example embodiments.
[0009] FIG. 8 is a user interface of annotated content, according
to some example embodiments.
[0010] FIG. 9 is a user interface of an upload page, according some
example embodiments.
[0011] FIGS. 10-12 are flowcharts illustrating operations of a
discovery system in performing a method of presentation of content
that depicts one or more stories, according to some example
embodiments.
[0012] FIG. 13 is a user interface diagram depicting an example
mobile device and mobile operating system interface, according to
some example embodiments.
[0013] FIG. 14 is a block diagram illustrating an example of a
software architecture that may be installed on a machine, according
to some example embodiments.
[0014] FIG. 15 is a block diagram presenting a diagrammatic
representation of a machine in the form of a computer system within
which a set of instructions may be executed for causing the machine
to perform any of the methodologies discussed herein, according to
an example embodiment.
[0015] The headings provided herein are merely for convenience and
do not necessarily affect the scope or meaning of the terms
used.
DETAILED DESCRIPTION
[0016] 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.
[0017] In various example embodiments, a system makes an edition
available for a user to view in a user interface of a messaging
application on a client device. In some instances, the edition is a
group of stories that are bundled together. Moreover, the system
may generate a discovery page featuring a variety of channels. The
user may access the edition from one of the channels featured in
the discovery page. In other words, the channel featured on the
discovery page serves as a link to the edition. As stated, the
edition can include one or more stories. For example, each story
can include an article, multimedia items, and the like. Moreover,
each story may correspond to a specific topic. As soon as the user
selects the edition from the discovery page, the user may view the
one or more stories from the edition. Also, the content within each
story may include more than one layer. For example, the content
within a story may include a first layer, also known as a top-snap,
and a second layer, also known as longform content. In some
embodiments, the top-snap for each story may be viewed by tapping
or swiping horizontally across the screen of the client device and
the longform content may be viewed by selection of the top-snap.
For instance, the user may swipe vertically on the top-snap in
order to view the longform content.
[0018] In various example embodiments, upon viewing the edition,
the user may share the content from the edition with another user.
The user may send a request to the system to share the content with
the other user. In some instances, the user may also annotate the
content prior to sharing it with other users. Once shared, the
other users may view the annotated content from their client
devices. In some cases, the annotated content is sent as an
ephemeral message and is only available for a predefined duration
of time.
[0019] In various example embodiments, the system includes a
publication application that enables editions to be uploaded to the
discovery page from a content publisher or an uploading party. The
system may present an upload page to the uploading party. The
upload page of the publication application may assist the uploading
party in uploading the content for the edition to a database
server. Once the content for the edition is uploaded at the
database server, the content is made available to view from the
discovery page. Accordingly, the system generates a channel on the
discovery page which provides access to the one or more editions.
In some embodiments, channels may be implemented to correspond to
uploading parties. Although the discovery page provides access to
the one or more editions, in some instances, only one edition may
be viewed at a time on the client device.
[0020] FIG. 1 is a network diagram depicting a network system 100
having a client-server architecture configured for exchanging data
over a network, according to one embodiment. For example, the
network system 100 may be a messaging system where clients
communicate and exchange data within the network system 100. The
data may pertain to various functions (e.g., sending and receiving
text and media communication, determining geolocation, etc.) and
aspects (e.g., publication of media content, management of media
content, etc.) associated with the network system 100 and its
users. Although illustrated herein as client-server architecture,
other embodiments may include other network architectures, such as
peer-to-peer or distributed network environments.
[0021] As shown in FIG. 1, the network system 100 includes a social
messaging system 130. The social messaging system 130 is generally
based on a three-tiered architecture, consisting of an interface
layer 124, an application logic layer 126, and a data layer 128. As
is understood by skilled artisans in the relevant computer and
Internet-related arts, each module or engine shown in FIG. 1
represents a set of executable software instructions and the
corresponding hardware (e.g., memory and processor) for executing
the instructions. To avoid obscuring the inventive subject matter
with unnecessary detail, various functional modules and engines
that are not germane to conveying an understanding of the inventive
subject matter have been omitted from FIG. 1. Of course, additional
functional modules and engines may be used with a social messaging
system, such as that illustrated in FIG. 1, to facilitate
additional functionality that is not specifically described herein.
Furthermore, the various functional modules and engines depicted in
FIG. 1 may reside on a single server computer, or may be
distributed across several server computers in various
arrangements. Moreover, although the social messaging system 130 is
depicted in FIG. 1 as a three-tiered architecture, the inventive
subject matter is by no means limited to such an architecture.
[0022] As shown in FIG. 1, the interface layer 124 consists of
interface module(s) (e.g., a web server) 140, which receives
requests from various client-computing devices and servers, such as
client device(s) 110 executing client application(s) 112, and third
party server(s) 120 executing third party application(s) 122. In
response to received requests, the interface module(s) 140
communicates appropriate responses to requesting devices via a
network 104. For example, the interface module(s) 140 can receive
requests such as Hypertext Transfer Protocol (HTTP) requests, or
other web-based, Application Programming Interface (API)
requests.
[0023] The client device(s) 110 can execute conventional web
browser applications or applications (also referred to as "apps")
that have been developed for a specific platform to include any of
a wide variety of mobile computing devices and mobile-specific
operating systems (e.g., IOS.TM., ANDROID.TM., WINDOWS.RTM. PHONE).
In an example, the client device(s) 110 are executing the client
application(s) 112. The client application(s) 112 can provide
functionality to present information to a user 106 and communicate
via the network 104 to exchange information with the social
messaging system 130. Each of the client device(s) 110 can comprise
a computing device that includes at least a display and
communication capabilities with the network 104 to access the
social messaging system 130. The client device(s) 110 comprise, but
are not limited to, remote devices, work stations, computers,
general purpose computers, Internet appliances, hand-held devices,
wireless devices, portable devices, wearable computers, cellular or
mobile phones, personal digital assistants (PDAs), smart phones,
tablets, ultrabooks, netbooks, laptops, desktops, multi-processor
systems, microprocessor-based or programmable consumer electronics,
game consoles, set-top boxes, network PCs, mini-computers, and the
like. User(s) 106 can be a person, a machine, or other means of
interacting with the client device(s) 110. In some embodiments, the
user(s) 106 interact with the social messaging system 130 via the
client device(s) 110.
[0024] As shown in FIG. 1, the data layer 128 has database
server(s) 132 that facilitate access to information storage
repositories or database(s) 134. The database(s) 134 are storage
devices that store data such as member profile data, social graph
data (e.g., relationships between members of the social messaging
system 130), and other user data.
[0025] An individual can register with the social messaging system
130 to become a member of the social messaging system 130. Once
registered, a member can form social network relationships (e.g.,
friends, followers, or contacts) on the social messaging system 130
and interact with a broad range of applications provided by the
social messaging system 130.
[0026] The application logic layer 126 includes various application
logic module(s) 150, which, in conjunction with the interface
module(s) 140, generate various user interfaces with data retrieved
from various data sources or data services in the data layer 128.
Individual application logic module(s) 150 may be used to implement
the functionality associated with various applications, services,
and features of the social messaging system 130. For instance, a
social messaging application can be implemented with one or more of
the application logic module(s) 150. The social messaging
application provides a messaging mechanism for users of the client
device(s) 110 to send and receive messages that include text and
media content such as pictures and video. The client device(s) 110
may access and view the messages from the social messaging
application for a specified period of time (e.g., limited or
unlimited). In an example, a particular message is accessible to a
message recipient for a predefined duration (e.g., specified by a
message sender) that begins when the particular message is first
accessed. After the predefined duration elapses, the message is
deleted and is no longer accessible to the message recipient. Of
course, other applications and services may be separately embodied
in their own application server module(s) 150. As another example,
a publication application can be implemented with one or more of
the application logic module(s) 150. The publication application
provides a messaging mechanism for users (e.g., content publishers)
of the client device(s) 110 to upload media content to the social
messaging system 130.
[0027] As illustrated in FIG. 1, the social messaging system 130
includes a discovery system 160. In various embodiments, the
discovery system 160 can be implemented as a standalone system and
is not necessarily included in the social messaging system 130. In
some embodiments, the client device(s) 110 includes a portion of
the discovery system 160 (e.g., a portion of the discovery system
may be included in the client application(s) 112). In these
embodiments, the client device(s) 110 can work alone or in
conjunction with the portion of the discovery system 160 included
in a particular application server or the social messaging system
130.
[0028] The communication module 250 provides various communications
functionality. For example, the communication module 250 may be
configured to exchange network communications with database
server(s) 132, clients device(s) 110, as well as any third party
server(s) 120. The types of information and data exchanged may
include configuration data for media content, such as pictograph
data (e.g., an image file); geographic indications (e.g., a
particular latitude and longitude); data associated with the user
(e.g., member profile data from an online account or social network
service data); or other data to facilitate the functionality
described herein.
[0029] The presentation module 240 provides various presentation
and user interface functionalities and allows the transmission of
information to and from the user (e.g., visually displaying
information on a screen, acoustic output, haptic feedback). For
instance, the presentation module 240 may present content depicting
one or more stories on a user interface or in a display of a user
device. The user may provide input to interact with the user
interface in many possible manners, such as alphanumeric, point
based (e.g., cursor), tactile, or other input (e.g., touch screen,
tactile sensor, light sensor, infrared sensor, biometric sensor,
microphone, gyroscope, accelerometer, or other sensors), and the
like.
[0030] FIG. 2 is a block diagram illustrating components of a
discovery system 160, according to some example embodiments. The
discovery system 160 is shown as including a reception module 210,
a group module 220, a generation module 230, and a presentation
module 240, all configured to communicate with each other (e.g.,
via a bus, network coupling, shared memory, a switch, and the
like). Any one or more of the modules described herein may be
implemented using hardware (e.g., one or more processors of a
machine) or a combination of hardware and software. For example,
any module described herein may configure a processor (e.g., among
one or more processors of a machine) to perform the operations
described herein for that module. Moreover, multiple modules may be
combined into a single module, and the functions described herein
for a single module may be subdivided among multiple modules.
Furthermore, according to various example embodiments, modules
described herein as being implemented within a single machine,
database, or device may be distributed across multiple machines,
databases, or devices. Other modules not pertinent to example
embodiments can also be included, but are not shown.
[0031] In various example embodiments, the reception module 210 is
configured to receive content that depicts one or more stories. The
reception module 210 may receive the content from a first client
device which is operated by a first user. The first user may be an
individual, a group of users or any other entity. The content may
include a video clip, an image, a description, and the like. Each
story may revolve around a specific topic or idea. For instance, a
story may include information about a particular travel
destination. Accordingly, the content for the travel destination
may include pictures and descriptions of the travel destination. In
some instances, the content may include multiple layers (e.g., a
first layer, a second layer, etc.). A user a may view the first
layer, also known as a top-snap, prior to the second layer, also
known as longform content. In some instances, the first layer is
selectable to cause display of the second layer. For example, the
first layer content for a music video may be a ten second preview
of the entire music video. The second layer content for the music
video may be a full length clip of the music video. As another
example, the first layer content for the travel destination may be
a picture of the travel destination. The second layer content for
the travel destination may be descriptions about things to do at
the travel destination.
[0032] In various example embodiments, the reception module 210 is
further configured to receive a request from the first client
device to upload the content into the edition. The first device may
have client application software (e.g., a messaging application)
installed which includes a feature to send the request to the
reception module 210. In response, the presentation module 240 is
configured to display an upload page on the first client device, as
further explained below.
[0033] In various example embodiments, the group module 220 is
configured to group the content that depicts the one or more
stories into an edition. In example embodiments, these editions may
be presented as part of the messaging application installed on a
client device. Each story of the edition may occupy an entire
screen when viewed on the client device. Moreover, a user may
scroll through each story of the edition using a tapping or swiping
gesture or motion. Specifically, the first layer (e.g., top-snap)
for each story may be viewed by tapping or swiping horizontally
across the screen of the client device. Similarly, the second layer
(e.g., longform content) may be viewed by selection of the
top-snap. In various example embodiments, the reception module 210
is further configured to store the received content in a database,
such as database(s) 134. Once stored, the group module 220 can
retrieve the content from the database and group the content into
the edition.
[0034] The group module 220 may be further configured to identify
that the content is received from the first client device within a
specific predefined window of time. For instance, all of the
stories grouped into the edition may be identified by the group
module 220 as being received within a span of a week. Therefore,
these stories within the edition may remain current or up to
date.
[0035] In various example embodiments, the generation module 230 is
configured to generate a discovery page that allows a user to
select an edition. In some embodiments, the discovery page is a
landing page that includes a link or channel to an edition. For
instance, each link/channel may be generated by generation module
230. In order to select an edition for viewing, a user may activate
or select the desired link on the discovery page. In some
embodiments, the channels may correspond to (or serve to identify)
the source of the content in the edition.
[0036] In various example embodiments, the presentation module 240
may present the discovery page on a second client device, operated
by a second user. Thus, the presentation module 240 is further
configured to present the icon of the channel as part of the
discovery page. The channel may also serve as a link to other
editions that are received from the same source. In various example
embodiments, the presentation module 240 may present the content on
the second client device based on the selection of the channel.
Therefore, the presentation of the content is performed based on
selection of the edition from the discovery page. The presentation
module 240 may also present the multiple layers of the content
(e.g., the first layer and the second layer) on the second client
device.
[0037] In various example embodiments, the presentation module 240
is further configured to present the upload page on the first
client device. The presentation of the upload page may be performed
in response to the received request to upload content. The upload
page enables a user (e.g., the first user operating the first
client device) to upload content that depicts the one or more
stories. For instance, the upload page may include a section where
the user can drag content to indicate that the content is to be
uploaded into the edition.
[0038] In various example embodiments, the reception module 210 is
further configured to receive an annotated version of the content
that depicts the one or more stories. The reception module 210 may
also receive an indication to share the annotated version of the
content with another or third client device. In this regard, the
annotated version of the content may be received from the second
client device. The annotated version of the content may include
additional markings added by the second user to the original
content that was displayed on the second client device.
Specifically, upon viewing the content on the second client device,
the second user may edit or alter the content in order to generate
an annotated version of the content. Annotations may include:
adding a further description, a drawing, an animation or a picture,
adding a layer on top of original content (including e.g., any
number of photofilters), deleting a portion of the original
content, and the like. Accordingly, the presentation module 240 is
configured to cause presentation of the annotated version of the
content on the third client device for a predefined duration of
time. Therefore, the third user on the third client device will be
able to view the annotated version of the content sent from the
second user on the second client device. In some instances, the
annotated version of the content is an ephemeral message that is
available for the predefined duration of time. After the predefined
duration of time elapses, the message may be deleted, and no longer
able to be viewed, on the third client device.
[0039] In various example embodiments, the reception module 210 is
further configured to receive a scheduled time from the first
client device. The scheduled time is used to indicate when to
present the edition on the second client device. Therefore, in some
instances, the presentation module 240 is further configured to
present the edition on the second client device during the
scheduled time. For example, the edition is made available on the
discovery page during the scheduled time. Thus, when the scheduled
time elapses, the second user is no longer able to select the
edition for viewing from the discovery page.
[0040] FIG. 3 is a user interface 300 of a discovery page,
according to some example embodiments. The discovery page is
displayed on a client device belonging to a user. As shown, the
user interface 300 includes a variety of channels. Each channel
represents an icon and can be used to access an edition. In some
instances, each channel corresponds to a source for the content or
editions included in the channel. As shown, the user interface 300
includes a first channel 310 and a second channel 320. The first
channel 310 may be a link that is selectable by the user to view an
edition from the first channel 310. Likewise, the second channel
320 is a link that is selectable by the user to view an edition
from the second channel 320. Selection of a channel may include a
touch or a gesture over the portion of the discovery page that
displays the channel.
[0041] FIG. 4 is a user interface 400 of a story from an edition,
according to some example embodiments. The user interface 400 is
displayed on a client device belonging to a user. Further, the user
interface 400 may be displayed after selection of a channel from
the discovery page of FIG. 3. As shown, the user interface 400 of
the story displays content that includes a description 410 and a
video clip 420. For example, the story may be a rock music video,
as indicated by the description 410. Further included in the user
interface 400 is a video clip 420 of the rock music video. In some
instances, the video clip 420 is a preview of the entire rock music
video and therefore a shortened version of the rock music video.
Also included in the content displayed in the user interface 400 is
a description 405 to indicate that the story for the rock music
video belongs to the edition.
[0042] FIG. 5 is a user interface 500 of a story from an edition,
depicting a second layer of a story, according to some example
embodiments. The user interface 500 is displayed on a client device
belonging to a user. Further, the user interface 500 may be
displayed after selection of the content displayed in the user
interface 400 shown in FIG. 4. For example, the user may swipe
vertically on the user interface 400 in order to view the user
interface 500. As shown, the content displayed in the user
interface 500 is the second layer of the story for the rock music
video. Moreover, the content displayed in the user interface 500
includes a description 510 and a video clip 520. The video clip 520
may be the entire version of the rock music video, as indicated by
the description 510. Also included in the content displayed in the
user interface 500 is a description 505 to indicate that the story
for the rock music video belongs to the edition. The video clip 520
may also be included with an image 525. Specifically, embodiments
of the invention contemplate allowing portable network graphics
images ("PNG images") or the like to be overlaid on top of video.
Thus, the image 525 may appear in front of the video clip 520 as
the video clip 520 is playing. Because the PNG image is able to
present text, icons, colors, etc. in a more detailed manner than a
video counterpart, the content appears more tightly integrated than
other methods.
[0043] FIG. 6 is a user interface 600 of a story from an edition,
according to some example embodiments. The user interface 600 is
displayed on a client device belonging to a user and displays a
story for a travel destination (e.g., Chicago). The content
displayed in the user interface 600 includes a description 610 and
an image 620. In this example, the description 610 indicates that
the story is about visiting Chicago. Further, the image 620 is used
to depict the Chicago skyline. Also included in the content
displayed in the user interface 600 is a description 605 to
indicate that the story for the travel destination belongs to the
edition.
[0044] FIG. 7 is a user interface 700 of a story from an edition,
according to some example embodiments. The user interface 700 is
displayed on a client device belonging to a user. Further, the user
interface 700 may be displayed after selection of the user
interface 600 shown in FIG. 6. For example, the user may swipe
vertically on the content displayed in the user interface 600 in
order to view the user interface 700. As shown, the content
displayed in the user interface 700 is the second layer of the
story for the travel destination. Moreover, the content displayed
in the user interface 700 includes a first description 710, a
second description 720, and a third description 730. The first
description indicates that the story is about visiting Chicago. The
second description 720 provides information about events in
Chicago. The third description 730 provides information about food
in Chicago. Also included in the content displayed in the user
interface 700 is a description 705 to indicate that the story for
the travel destination belongs to the edition.
[0045] FIG. 8 is a user interface 800 of annotated content,
according to some example embodiments. The user interface 800 is
displayed on a client device belonging to a recipient. Further, the
user interface 800 includes content that was intended to be shared
with the recipient and received from a sender. As shown, the
content displayed in the user interface 800 includes a first
description 810, a second description 820, and a third description
830. In some instances, the first description 810, the second
description 820, and the third description 830 are respectively
identical to the first description 710, the second description 720,
and the third description 730 of FIG. 7. Also shown in FIG. 8 is a
fourth description 850. The fourth description 850 may be
additional content that is added by the sender. For instance, the
sender may edit the content displayed in the user interface 700 of
FIG. 7 by adding the fourth description 850 (e.g., by typing using
a keyboard or handwriting via the touch sensitive display screen).
As shown, the fourth description 850 may include text, as well as
graphics, animations, emojis, photo filters, etc. Thereafter, the
sender will send the annotated content to the recipient to be
displayed on the client device belonging to the recipient. Also
shown in FIG. 8 is a timer 840 to indicate an amount of time
remaining before the annotated content disappears. Therefore, the
annotated content may appear on the screen on the client device for
the length of time indicated by the timer 840. Also shown in FIG. 8
is a link 860 in the form of an arrow. In some instances, the link
is selectable to cause navigation to the discovery page. For
example, upon selection of the link, an animation may appear on the
screen of the client device which will eventually display the
discovery page.
[0046] FIG. 9 is a user interface 900 of an upload page, according
some example embodiments. The user interface 900 is displayed on a
device belonging to a user, such as a desktop computer or a mobile
device. For example, as shown in FIG. 9, the user interface 900 of
the upload page is displayed on a desktop computer. Moreover, the
user is able to upload original content by interacting with the
user interface 900. Specifically, the user interface 900 includes a
portion 910 where the user is able to upload specific content. In
particular, the user is able to upload content for one or more
stories by moving files over to the portion 910 of the user
interface. For example, the user may upload a video clip by moving
the video clip to the portion 910 of the user interface. As another
example, the user may upload an image by moving the image to the
portion 910 of the user interface. The user interface 900 further
includes a scheduling window 920 that enables the user to input a
scheduled time. The scheduled time corresponds to when the edition
is made available on the discovery page. Although not shown in FIG.
9, in some instances, the upload page may include editing tools,
such as a text or video editor, to facilitate the creation and/or
editing of content.
[0047] FIG. 10-12 are flowcharts illustrating operations of the
discovery system 160 in performing a method 1000 of presentation of
content that depicts one or more stories, according to some example
embodiments. Operations in the method 1000 may be performed by the
discovery system 160, using modules described above with respect to
FIG. 2. As shown in FIG. 10, the method 1000 includes operations
1010, 1020, 1030, 1040, and 1050.
[0048] At operation 1010, the reception module 210 receives content
that depicts one or more stories. The reception module 210 receives
the content from a first client device which is operated by a first
user. As an example, the reception module 210 receives first
content that depicts a first story and second content that depicts
a second story. The first user may upload the content from an
upload page that is displayed on the first client device. Further,
the content may include a video clip, an image, a description, and
the like.
[0049] At operation 1020, the group module 220 groups the content
into an edition used to represent the one or more stories. As an
example, the group module 220 groups the first content and the
second content received at operation 1020 into the edition used to
represent the one or more stories.
[0050] At operation 1030, the generation module 230 generates a
discovery page that enables selection of the edition. A second user
may select the link on the discovery page in order to view the
edition. The link to the edition may be a channel. As shown in FIG.
3, the discovery page includes a variety of channels for the second
user to choose from.
[0051] At operation 1040, the presentation module 240 causes
presentation of the discovery page. The presentation of the
discovery page may be on a second client device belonging to the
second user (e.g., the discovery page may be broadcast to multiple
recipient or target devices). In some instances, the discovery page
is a feature of a messaging application installed on the second
client device.
[0052] At operation 1050, the presentation module 240 causes
presentation of the content. In some cases, the presentation module
240 is further configured to cause presentation of the multiple
layers of the content (e.g., the first layer and the second layer)
on the screen of the second client device belonging to the second
user. Once displayed on the screen of the second client device, the
second user may select the first layer to cause display of the
second layer of the content. For instance, the second user may
swipe vertically on the first layer displayed on the screen of the
second client device. Alternatively, the second user may tap on the
first layer displayed on the screen of the second client device. In
some instances, the first layer indicates an area where the second
user may tap in order to cause display of the second layer.
[0053] In some instances, the presentation module 240
simultaneously displays a video clip and one or more images. For
example, the presentation module 240 may cause the one or more
images (e.g., the PNG images described above) to be displayed over
the video clip as the video clip is being played. Referring back to
FIG. 5, the video clip 520 of the rock music video includes an
image (e.g., image 525) that is overlaid on top of the video clip
520.
[0054] As shown in FIG. 11, the method 1000 may include one or more
of sub-operations 1110, 1120, 1130, and 1140. Operations 1110 and
1120 may be performed as part of operation 1020. Further, operation
1130 may be performed as part of operation 1030 and operation 1140
may be performed prior to operation 1040.
[0055] At operation 1110, the group module 220 may be used to
associate a time setting to the content. For example, a user may be
able to identify a time span, after which the content may no longer
be `current` or accessible. Thus, the content included within the
edition may correspond to a certain day of the week. As shown in
FIGS. 4-8, each piece of content displayed in the user interfaces
is indicated as being part of an edition that corresponds to a day
of the week (e.g., Monday).
[0056] At operation 1120, the group module 220 generates a
collection of stories depicted by the content, which may be
displayed on a client device. As an example, the pieces of content
displayed in FIGS. 3-8 may represent a story within the collection
of stories. Further, a user may be able to navigate through each
story by performing a tapping or swiping gesture.
[0057] At operation 1130, the generation module 230 generates an
icon of a channel selectable to result in the presentation of the
edition. Moreover, the icon of the channel may include a thumbnail
image related to the source of the content included in the edition.
Also, as shown in FIG. 3, the generated icon may be displayed on a
discovery page. Although FIG. 3 does not specifically show
thumbnail images, each of the icons may include a thumbnail image
that is related to the source of the content for the edition. In
some cases, when all the editions from a channel have been viewed
on a client device, the icon of the channel will change appearance
(e.g., an animation that modifies a color of the icon).
[0058] At operation 1140, the reception module 210 receives a
scheduled time, which may be used to indicate when the edition is
available on the discovery page. In some instances, the scheduled
time is indicated by a user from the upload page. For example, as
shown in FIG. 9, the upload page includes a section where a user
may input the scheduled time.
[0059] As shown in FIG. 12, the method 1000 may include one or more
of sub-operations 1210, 1220, 1230, and 1240. Operations 1210 and
1220 may be performed prior to operation 1010. Further, operations
1230 and 1240 may be performed after operation 1050.
[0060] At operation 1210, the reception module 210 receives a
request to upload content to the edition. The request may be
received from the first client device. For instance, client
application software installed on the first client device may
include a feature which sends a request to the reception module
210. Moreover, the operation 1020 may be performed based on the
request received at operation 1210.
[0061] At operation 1220, the presentation module 240 causes
presentation of an upload page. The upload page enables the user of
the first client device to upload the content that depicts the one
or more stories. For instance, the upload page may include a
section where a user can drag content to indicate that the content
is to be uploaded into the edition. From the upload page, the user
is also able to upload multiple layers (e.g., a first layer and a
second layer) of content that depicts one or more stories which
will be grouped into the edition. For example, the user may upload
each layer by dragging the content (e.g., a file that includes the
content) into the appropriate section of the upload page. Further,
the user may continue dragging multiple files until the multiple
layers of the content have been uploaded.
[0062] At operation 1230, the reception module 210 receives an
annotated version of the content that depicts the one or more
stories. For instance, the reception module 210 receives the
annotated version of the content from the second client device. The
second user of the second device, upon viewing the content
displayed on the second client device, may alter or edit the
content. Subsequently, the second user may send the annotated
content from the second client device to the reception module 210.
As an example, as shown in FIG. 8, the annotated version of the
content may include an additional description that is added to the
original content. Further, the reception module 210 receives an
indication to share the annotated version of the content with a
third client device. For example, the second user of the second
client device may double tap on the screen of the second device in
order to share the annotated version of the content.
[0063] At operation 1240, the presentation module 240 causes
presentation of the annotated version of the content. The
presentation module 240 may cause presentation of the annotated
version of the content on the third client device as indicated at
operation 1230. Further, the annotated version of the content is
viewable on the third client device for a predefined duration of
time. This is because the annotated version of the content can be
an ephemeral message that is available for the predefined duration
of time. For example, as shown in FIG. 8, the annotated content
includes a timer which indicates an amount of time remaining before
the annotated content disappears.
Modules, Components, and Logic
[0064] Certain embodiments are described herein as including logic
or a number of components, modules, or mechanisms. Modules can
constitute either software modules (e.g., code embodied on a
machine-readable medium or in a transmission signal) or hardware
modules. A "hardware module" is a tangible unit capable of
performing certain operations and can be configured or arranged in
a certain physical manner. In various example embodiments, one or
more computer systems (e.g., a standalone computer system, a client
computer system, or a server computer system) or one or more
hardware modules of a computer system (e.g., a processor or a group
of processors) is configured by software (e.g., an application or
application portion) as a hardware module that operates to perform
certain operations as described herein.
[0065] In some embodiments, a hardware module is implemented
mechanically, electronically, or any suitable combination thereof.
For example, a hardware module can include dedicated circuitry or
logic that is permanently configured to perform certain operations.
For example, a hardware module can be a special-purpose processor,
such as a Field-Programmable Gate Array (FPGA) or an Application
Specific Integrated Circuit (ASIC). A hardware module may also
include programmable logic or circuitry that is temporarily
configured by software to perform certain operations. For example,
a hardware module can include software encompassed within a
general-purpose processor or other programmable processor. It will
be appreciated that the decision to implement a hardware module
mechanically, in dedicated and permanently configured circuitry, or
in temporarily configured circuitry (e.g., configured by software)
can be driven by cost and time considerations.
[0066] Accordingly, the phrase "hardware module" 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. As used herein, "hardware-implemented module" refers to a
hardware module. Considering embodiments in which hardware modules
are temporarily configured (e.g., programmed), each of the hardware
modules need not be configured or instantiated at any one instance
in time. For example, where a hardware module 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 modules) at different times.
Software can accordingly configure a particular processor or
processors, for example, to constitute a particular hardware module
at one instance of time and to constitute a different hardware
module at a different instance of time.
[0067] Hardware modules can provide information to, and receive
information from, other hardware modules. Accordingly, the
described hardware modules can be regarded as being communicatively
coupled. Where multiple hardware modules exist contemporaneously,
communications can be achieved through signal transmission (e.g.,
over appropriate circuits and buses) between or among two or more
of the hardware modules. In embodiments in which multiple hardware
modules are configured or instantiated at different times,
communications between such hardware modules may be achieved, for
example, through the storage and retrieval of information in memory
structures to which the multiple hardware modules have access. For
example, one hardware module performs an operation and stores the
output of that operation in a memory device to which it is
communicatively coupled. A further hardware module can then, at a
later time, access the memory device to retrieve and process the
stored output. Hardware modules can also initiate communications
with input or output devices, and can operate on a resource (e.g.,
a collection of information).
[0068] The various operations of example methods described herein
can 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 constitute
processor-implemented modules that operate to perform one or more
operations or functions described herein. As used herein,
"processor-implemented module" refers to a hardware module
implemented using one or more processors.
[0069] Similarly, the methods described herein can 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 can be performed by one or more
processors or processor-implemented modules. 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)).
[0070] The performance of certain of the operations may be
distributed among the processors, not only residing within a single
machine, but deployed across a number of machines. In some example
embodiments, the processors or processor-implemented modules are
located in a single geographic location (e.g., within a home
environment, an office environment, or a server farm). In other
example embodiments, the processors or processor-implemented
modules are distributed across a number of geographic
locations.
Applications
[0071] FIG. 13 illustrates an example mobile device 1300 executing
a mobile operating system (e.g., IOS.TM., ANDROID.TM., WINDOWS.RTM.
Phone, or other mobile operating systems), consistent with some
embodiments. In one embodiment, the mobile device 1300 includes a
touch screen operable to receive tactile data from a user 1302. For
instance, the user 1302 may physically touch 1304 the mobile device
1300, and in response to the touch 1304, the mobile device 1300 may
determine tactile data such as touch location, touch force, or
gesture motion. In various example embodiments, the mobile device
1300 displays a home screen 1306 (e.g., Springboard on IOS.TM.)
operable to launch applications or otherwise manage various aspects
of the mobile device 1300. In some example embodiments, the home
screen 1306 provides status information such as battery life,
connectivity, or other hardware statuses. The user 1302 can
activate user interface elements by touching an area occupied by a
respective user interface element. In this manner, the user 1302
interacts with the applications of the mobile device 1300. For
example, touching the area occupied by a particular icon included
in the home screen 1306 causes launching of an application
corresponding to the particular icon.
[0072] Many varieties of applications (also referred to as "apps")
can be executing on the mobile device 1300, such as native
applications (e.g., applications programmed in Objective-C, Swift,
or another suitable language running on IOS.TM., or applications
programmed in Java running on ANDROID.TM.), mobile web applications
(e.g., applications written in Hypertext Markup Language-5
(HTML5)), or hybrid applications (e.g., a native shell application
that launches an HTML5 session). For example, the mobile device
1300 includes a messaging app, an audio recording app, a camera
app, a book reader app, a media app, a fitness app, a file
management app, a location app, a browser app, a settings app, a
contacts app, a telephone call app, or other apps (e.g., gaming
apps, social networking apps, biometric monitoring apps). In
another example, the mobile device 1300 includes a social messaging
app 1308 such as SNAPCHAT.RTM. that, consistent with some
embodiments, allows users to exchange ephemeral messages that
include media content. In this example, the social messaging app
1308 can incorporate aspects of embodiments described herein.
Software Architecture
[0073] FIG. 14 is a block diagram 1400 illustrating an architecture
of software 1402, which can be installed on any one or more of the
devices described above. FIG. 14 is merely a non-limiting example
of a software architecture, and it will be appreciated that many
other architectures can be implemented to facilitate the
functionality described herein. In various embodiments, the
software 1402 is implemented by hardware such as machine a 1500 of
FIG. 15 that includes processors 1510, memory 1530, and I/O
components 1550. In this example architecture, the software 1402
can be conceptualized as a stack of layers where each layer may
provide a particular functionality. For example, the software 1402
includes layers such as an operating system 1404, libraries 1406,
frameworks 1408, and applications 1410. Operationally, the
applications 1410 invoke application programming interface (API)
calls 1412 through the software stack and receive messages 1414 in
response to the API calls 1412, consistent with some
embodiments.
[0074] In various implementations, the operating system 1404
manages hardware resources and provides common services. The
operating system 1404 includes, for example, a kernel 1420,
services 1422, and drivers 1424. The kernel 1420 acts as an
abstraction layer between the hardware and the other software
layers consistent with some embodiments. For example, the kernel
1420 provides memory management, processor management (e.g.,
scheduling), component management, networking, and security
settings, among other functionality. The services 1422 can provide
other common services for the other software layers. The drivers
1424 are responsible for controlling or interfacing with the
underlying hardware, according to some embodiments. For instance,
the drivers 1424 can 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.
[0075] In some embodiments, the libraries 1406 provide a low-level
common infrastructure utilized by the applications 1410. The
libraries 1406 can include system libraries 1430 (e.g., C standard
library) that can provide functions such as memory allocation
functions, string manipulation functions, mathematic functions, and
the like. In addition, the libraries 1406 can include API libraries
1432 such as media libraries (e.g., libraries to support
presentation and manipulation of various media formats such as
Moving Picture Experts Group-4 (MPEG4), Advanced Video Coding
(H.264 or AVC), Moving Picture Experts Group Layer-3 (MP3),
Advanced Audio Coding (AAC), Adaptive Multi-Rate (AMR) audio codec,
Joint Photographic Experts Group (JPEG or JPG), or Portable Network
Graphics (PNG)), graphics libraries (e.g., an OpenGL framework used
to render in two dimensions (2D) and three dimensions (3D) in a
graphic content on a display), database libraries (e.g., SQLite to
provide various relational database functions), web libraries
(e.g., WebKit to provide web browsing functionality), and the like.
The libraries 1406 can also include a wide variety of other
libraries 1434 to provide many other APIs to the applications
1410.
[0076] The frameworks 1408 provide a high-level common
infrastructure that can be utilized by the applications 1410,
according to some embodiments. For example, the frameworks 1408
provide various graphic user interface (GUI) functions, high-level
resource management, high-level location services, and so forth.
The frameworks 1408 can provide a broad spectrum of other APIs that
can be utilized by the applications 1410, some of which may be
specific to a particular operating system or platform.
[0077] In an example embodiment, the applications 1410 include a
home application 1450, a contacts application 1452, a browser
application 1454, a book reader application 1456, a location
application 1458, a media application 1460, a messaging application
1462, a game application 1464, and a broad assortment of other
applications such as a third party application 1466. According to
some embodiments, the applications 1410 are programs that execute
functions defined in the programs. Various programming languages
can be employed to create one or more of the applications 1410,
structured in a variety of manners, such as object-oriented
programming languages (e.g., Objective-C, Java, or C++) or
procedural programming languages (e.g., C or assembly language). In
a specific example, the third party application 1466 (e.g., 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) may be mobile software running on a mobile
operating system such as IOS.TM., ANDROID.TM., WINDOWS.RTM. PHONE,
or another mobile operating systems. In this example, the third
party application 1466 can invoke the API calls 1412 provided by
the operating system 1404 to facilitate functionality described
herein.
Example Machine Architecture and Machine-Readable Medium
[0078] FIG. 15 is a block diagram illustrating components of a
machine 1500, according to some embodiments, able to read
instructions from a machine-readable medium (e.g., a
machine-readable storage medium) and perform any one or more of the
methodologies discussed herein. Specifically, FIG. 15 shows a
diagrammatic representation of the machine 1500 in the example form
of a computer system, within which instructions 1516 (e.g.,
software, a program, an application, an applet, an app, or other
executable code) for causing the machine 1500 to perform any one or
more of the methodologies discussed herein can be executed. In
alternative embodiments, the machine 1500 operates as a standalone
device or can be coupled (e.g., networked) to other machines. In a
networked deployment, the machine 1500 may operate in the capacity
of a server machine or a client machine in a server-client network
environment, or as a peer machine in a peer-to-peer (or
distributed) network environment. The machine 1500 can 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 1516,
sequentially or otherwise, that specify actions to be taken by the
machine 1500. Further, while only a single machine 1500 is
illustrated, the term "machine" shall also be taken to include a
collection of machines 1500 that individually or jointly execute
the instructions 1516 to perform any one or more of the
methodologies discussed herein.
[0079] In various embodiments, the machine 1500 comprises
processors 1510, memory 1530, and I/O components 1550, which can be
configured to communicate with each other via a bus 1502. In an
example embodiment, the processors 1510 (e.g., a Central Processing
Unit (CPU), a Reduced Instruction Set Computing (RISC) processor, a
Complex Instruction Set Computing (CISC) processor, a Graphics
Processing Unit (GPU), a Digital Signal Processor (DSP), an
Application Specific Integrated Circuit (ASIC), a Radio-Frequency
Integrated Circuit (RFIC), another processor, or any suitable
combination thereof) includes, for example, a processor 1512 and a
processor 1514 that may execute the instructions 1516. The term
"processor" is intended to include multi-core processors that may
comprise two or more independent processors (also referred to as
"cores") that can execute instructions contemporaneously. Although
FIG. 15 shows multiple processors, the machine 1500 may include a
single processor with a single core, a single processor with
multiple cores (e.g., a multi-core processor), multiple processors
with a single core, multiple processors with multiples cores, or
any combination thereof.
[0080] The memory 1530 comprises a main memory 1532, a static
memory 1534, and a storage unit 1536 accessible to the processors
1510 via the bus 1502, according to some embodiments. The storage
unit 1536 can include a machine-readable medium 1538 on which are
stored the instructions 1516 embodying any one or more of the
methodologies or functions described herein. The instructions 1516
can also reside, completely or at least partially, within the main
memory 1532, within the static memory 1534, within at least one of
the processors 1510 (e.g., within the processor's cache memory), or
any suitable combination thereof, during execution thereof by the
machine 1500. Accordingly, in various embodiments, the main memory
1532, the static memory 1534, and the processors 1510 are
considered machine-readable media 1538.
[0081] As used herein, the term "memory" refers to a
machine-readable medium 1538 able to store data temporarily or
permanently and may be taken to include, but not be limited to,
random-access memory (RAM), read-only memory (ROM), buffer memory,
flash memory, and cache memory. While the machine-readable medium
1538 is shown in an example embodiment to be a single medium, 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 the
instructions 1516. The term "machine-readable medium" shall also be
taken to include any medium, or combination of multiple media, that
is capable of storing instructions (e.g., instructions 1516) for
execution by a machine (e.g., machine 1500), such that the
instructions, when executed by one or more processors of the
machine 1500 (e.g., processors 1510), cause the machine 1500 to
perform any one or more of the methodologies described herein.
Accordingly, a "machine-readable medium" refers to a single storage
apparatus or device, as well as "cloud-based" storage systems or
storage networks that include multiple storage apparatus or
devices. The term "machine-readable medium" shall accordingly be
taken to include, but not be limited to, one or more data
repositories in the form of a solid-state memory (e.g., flash
memory), an optical medium, a magnetic medium, other non-volatile
memory (e.g., Erasable Programmable Read-Only Memory (EPROM)), or
any suitable combination thereof. The term "machine-readable
medium" specifically excludes non-statutory signals per se.
[0082] The I/O components 1550 include a wide variety of components
to receive input, provide output, produce output, transmit
information, exchange information, capture measurements, and so on.
In general, it will be appreciated that the I/O components 1550 can
include many other components that are not shown in FIG. 15. The
I/O components 1550 are grouped according to functionality merely
for simplifying the following discussion, and the grouping is in no
way limiting. In various example embodiments, the I/O components
1550 include output components 1552 and input components 1554. The
output components 1552 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), other signal generators, and
so forth. The input components 1554 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 instruments), tactile input components (e.g., a physical
button, a touch screen that provides location and force of touches
or touch gestures, or other tactile input components), audio input
components (e.g., a microphone), and the like.
[0083] In some further example embodiments, the I/O components 1550
include biometric components 1556, motion components 1558,
environmental components 1560, or position components 1562, among a
wide array of other components. For example, the biometric
components 1556 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 1558 include acceleration sensor components
(e.g., accelerometer), gravitation sensor components, rotation
sensor components (e.g., gyroscope), and so forth. The
environmental components 1560 include, for example, illumination
sensor components (e.g., photometer), temperature sensor components
(e.g., one or more thermometers that detect ambient temperature),
humidity sensor components, pressure sensor components (e.g.,
barometer), acoustic sensor components (e.g., one or more
microphones that detect background noise), proximity sensor
components (e.g., infrared sensors that detect nearby objects), gas
sensor components (e.g., machine olfaction detection sensors, gas
detection sensors to detect 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 1562 include location sensor components (e.g., a Global
Positioning 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.
[0084] Communication can be implemented using a wide variety of
technologies. The I/O components 1550 may include communication
components 1564 operable to couple the machine 1500 to a network
1580 or devices 1570 via a coupling 1582 and a coupling 1572,
respectively. For example, the communication components 1564
include a network interface component or another suitable device to
interface with the network 1580. In further examples, communication
components 1564 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 1570 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)).
[0085] Moreover, in some embodiments, the communication components
1564 detect identifiers or include components operable to detect
identifiers. For example, the communication components 1564 include
Radio Frequency Identification (RFID) tag reader components, NFC
smart tag detection components, optical reader components (e.g., an
optical sensor to detect a one-dimensional bar codes such as a
Universal Product Code (UPC) bar code, multi-dimensional bar codes
such as a Quick Response (QR) code, Aztec Code, Data Matrix,
Dataglyph, MaxiCode, PDF417, Ultra Code, Uniform Commercial Code
Reduced Space Symbology (UCC RSS)-2D bar codes, and other optical
codes), acoustic detection components (e.g., microphones to
identify tagged audio signals), or any suitable combination
thereof. In addition, a variety of information can be derived via
the communication components 1564, such as location via Internet
Protocol (IP) geolocation, location via WI-FI.RTM. signal
triangulation, location via detecting a BLUETOOTH.RTM. or NFC
beacon signal that may indicate a particular location, and so
forth.
Transmission Medium
[0086] In various example embodiments, one or more portions of the
network 1580 can be an ad hoc network, an intranet, an extranet, a
virtual private network (VPN), a local area network (LAN), a
wireless LAN (WLAN), a wide area network (WAN), a wireless WAN
(WWAN), a metropolitan area network (MAN), the Internet, a portion
of the Internet, a portion of the Public Switched Telephone Network
(PSTN), a plain old telephone service (POTS) network, a cellular
telephone network, a wireless network, a WI-FI.RTM. network,
another type of network, or a combination of two or more such
networks. For example, the network 1580 or a portion of the network
1580 may include a wireless or cellular network, and the coupling
1582 may be a Code Division Multiple Access (CDMA) connection, a
Global System for Mobile communications (GSM) connection, or
another type of cellular or wireless coupling. In this example, the
coupling 1582 can 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.
[0087] In example embodiments, the instructions 1516 are
transmitted or received over the network 1580 using a transmission
medium via a network interface device (e.g., a network interface
component included in the communication components 1564) and
utilizing any one of a number of well-known transfer protocols
(e.g., Hypertext Transfer Protocol (HTTP)). Similarly, in other
example embodiments, the instructions 1516 are transmitted or
received using a transmission medium via the coupling 1572 (e.g., a
peer-to-peer coupling) to the devices 1570. The term "transmission
medium" shall be taken to include any intangible medium that is
capable of storing, encoding, or carrying the instructions 1516 for
execution by the machine 1500, and includes digital or analog
communications signals or other intangible media to facilitate
communication of such software.
[0088] Furthermore, the machine-readable medium 1538 is
non-transitory (in other words, not having any transitory signals)
in that it does not embody a propagating signal. However, labeling
the machine-readable medium 1538 "non-transitory" should not be
construed to mean that the medium is incapable of movement; the
medium should be considered as being transportable from one
physical location to another. Additionally, since the
machine-readable medium 1538 is tangible, the medium may be
considered to be a machine-readable device.
Language
[0089] Throughout this specification, plural instances may
implement components, operations, or structures described as a
single instance. Although individual operations of one or more
methods are illustrated and described as separate operations, one
or more of the individual operations may be performed concurrently,
and nothing requires that the operations be performed in the order
illustrated. Structures and functionality presented as separate
components in example configurations may be implemented as a
combined structure or component. Similarly, structures and
functionality presented as a single component may be implemented as
separate components. These and other variations, modifications,
additions, and improvements fall within the scope of the subject
matter herein.
[0090] Although an overview of the inventive subject matter has
been described with reference to specific example embodiments,
various modifications and changes may be made to these embodiments
without departing from the broader scope of embodiments of the
present disclosure. Such embodiments of the inventive subject
matter may be referred to herein, individually or collectively, by
the term "invention" merely for convenience and without intending
to voluntarily limit the scope of this application to any single
disclosure or inventive concept if more than one is, in fact,
disclosed.
[0091] The embodiments illustrated herein are described in
sufficient detail to enable those skilled in the art to practice
the teachings disclosed. Other embodiments may be used and derived
therefrom, such that structural and logical substitutions and
changes may be made without departing from the scope of this
disclosure. The Detailed Description, therefore, is not to be taken
in a limiting sense, and the scope of various embodiments is
defined only by the appended claims, along with the full range of
equivalents to which such claims are entitled.
[0092] As used herein, the term "or" may be construed in either an
inclusive or exclusive sense. Moreover, plural instances may be
provided for resources, operations, or structures described herein
as a single instance. Additionally, boundaries between various
resources, operations, modules, engines, and data stores are
somewhat arbitrary, and particular operations are illustrated in a
context of specific illustrative configurations. Other allocations
of functionality are envisioned and may fall within a scope of
various embodiments of the present disclosure. In general,
structures and functionality presented as separate resources in the
example configurations may be implemented as a combined structure
or resource. Similarly, structures and functionality presented as a
single resource may be implemented as separate resources. These and
other variations, modifications, additions, and improvements fall
within a scope of embodiments of the present disclosure as
represented by the appended claims. The specification and drawings
are, accordingly, to be regarded in an illustrative rather than a
restrictive sense.
* * * * *