AGGREGATED MEDIA CONTENT IN AN ELECTRONIC MESSAGING APPLICATION

BACKGROUND

The popularity of electronic messaging, particularly instant messaging, continues to grow. Users increasingly share electronic media content items such as electronic images, audio, and video with each other, reflecting a global demand to communicate more visually. Users also increasingly utilize their mobile devices to communicate with each other using chat and message programs.

Each messaging system is presented with the challenge of providing a graphical user interface that maintains the user's engagement on the system. It is paramount that the systems have the ability to present to each user the media content items that are most interesting or relevant to that user. In addition to the need to curate the media content items, the social networking systems are also presented with the challenge of providing a graphical user interface that captivates the user's attention and allows the user to view the curated media content items as well as further interact the network of individuals on the system.

BRIEF DESCRIPTION OF THE DRAWINGS

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

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

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

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

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

FIGS. 5A-5H are screenshots of exemplary interfaces according to various aspects of the disclosure.

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 aggregating media content items and electronic messages associated with a group of users using client devices. In one embodiment, the electronic messaging system generates a group of client devices based a selection from a first client device. For example, the user of the first client device may select the users she regularly eats tacos with (e.g., the “Tacos group”). The system hosts a communication session between the two or more users in the group. The system also generates a group selectable item to be displayed on the client devices in the group. The system provides an improved user interface that allows the user to easily send media content items of interest (e.g., taco pictures) or electronic messages (e.g., chats about taco plans) to the friends in the Tacos group by broadcasting the media content item to the group via a group selectable item. The system may also alter appearance of the group selectable item based on whether there is a new media content item or electronic message that has not been viewed by the user of the client device. Accordingly, the relevant media items and communications on the user interface may be organized based on the group membership as well as by new (unseen) items and messages. With the improved visual organization of the user interface, the user engagement with the system may further increase.

FIG. 1 is a block diagram showing an example messaging system 100 for exchanging data (e.g., messages and associated content) over a network. The messaging system 100 includes multiple client devices 102, each of which hosts a number of applications including a messaging client application 104. Each messaging client application 104 is communicatively coupled to other instances of the messaging client application 104 and a messaging server system 108 via a network 106 (e.g., the Internet). As used herein, the term “client device” may refer to any machine that interfaces to a communications network (such as network 106) to obtain resources from one or more server systems or other client devices. A client device may be, but is not limited to, a mobile phone, desktop computer, laptop, portable digital assistants (PDAs), smart phones, tablets, ultra books, netbooks, laptops, multi-processor systems, microprocessor-based or programmable consumer electronics, game consoles, set-top boxes, or any other communication device that a user may use to access a network.

In the example shown in FIG. 1, each messaging client application 104 is able to communicate and exchange data with another messaging client application 104 and with the messaging server system 108 via the network 106. The data exchanged between messaging client applications 104, and between a messaging client application 104 and the messaging server system 108, includes functions (e.g., commands to invoke functions) as well as payload data (e.g., text, audio, video or other multimedia data).

The network 106 may include, or operate in conjunction with, an ad hoc network, an intranet, an extranet, a virtual private network (VPN), a local area network (LAN), a wireless LAN (WLAN), a wide area network (WAN), a wireless WAN (WWAN), a metropolitan area network (MAN), the Internet, a portion of the Internet, a portion of the Public Switched Telephone Network (PSTN), a plain old telephone service (POTS) network, a cellular telephone network, a wireless network, a Wi-Fi® network, another type of network, or a combination of two or more such networks. For example, a network or a portion of a network may include a wireless or cellular network and the coupling may be a Code Division Multiple Access (CDMA) connection, a Global System for Mobile communications (GSM) connection, or other type of cellular or wireless coupling. In this example, the coupling may implement any of a variety of types of data transfer technology, such as Single Carrier Radio Transmission Technology (1xRTT), Evolution-Data Optimized (EVDO) technology, General Packet Radio Service (CPRS) 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. 100171 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 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 media files (e.g., images or video) from a messaging client application 104 to the messaging server application 114, and for possible access by another messaging client application 104, the setting of a collection of media data (e.g., story), the retrieval of a list of friends of a user of a client device 102, the retrieval of such collections, the retrieval of messages and content, the adding and deletion of friends to a social graph, the location of friends within a social graph, opening and application event (e.g., relating to the messaging client application 104).

The application server 112 hosts a number of applications and subsystems, including a messaging server application 114, an image processing system 116 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 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, and/or any other wearable devices.

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

The ephemeral timer system 202 is responsible for enforcing the temporary access to content permitted by the messaging client application 104 and the messaging server application 114. To this end, the ephemeral timer system 202 incorporates a number of timers that, based on duration and display parameters associated with a message, or collection of messages (e.g., a 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 filter) to the messaging client application 104 based on a geolocation of the client device 102. In another example, the annotation system 206 operatively supplies a media overlay to the messaging client application 104 based on other information, such as, social network information of the user of the client device 102. A media overlay may include audio and visual content and visual effects. Examples of audio and visual content include pictures, texts, logos, animations, and sound effects. An example of a visual effect includes color overlaying. The audio and visual content or the visual effects can be applied to a media content item (e.g., a photo) at the client device 102. For example, the media overlay including text that can be overlaid on top of a photograph generated taken by the client device 102. In another example, the media overlay includes an identification of a location overlay (e.g., Venice beach), a name of a live event, or a name of a merchant overlay (e.g., Beach Coffee House). In another example, the annotation system 206 uses the geolocation of the client device 102 to identify a media overlay that includes the name of a merchant at the geolocation of the client device 102. The media overlay may include other indicia associated with the merchant. The media overlays may be stored in the database 120 and accessed through the database server 118.

In one exemplary embodiment, the annotation system 206 provides a user-based publication platform that enables users to select a geolocation on a map, and upload content associated with the selected geolocation. The user may also specify circumstances under which a particular media overlay should be offered to other users. The annotation system 206 generates a media overlay that includes the uploaded content and associates the uploaded content with the selected geolocation.

In another exemplary embodiment, the annotation system 206 provides a merchant-based publication platform that enables merchants to select a particular media overlay associated with a geolocation via a bidding process. For example, the annotation system 206 associates the media overlay of a highest bidding merchant with a corresponding geolocation for a predefined amount of time.

FIG. 3 is a schematic diagram 300 illustrating data 300 which may be 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, it will be appreciated that the data could be stored in other types of data structures (e.g., as an object-oriented database).

The database 120 includes message data stored within a message table 314. The entity table 302 stores entity data, including an entity graph 304. Entities for which records are maintained within the entity table 302 may include individuals, corporate entities, organizations, objects, places, events etc. Regardless of type, any entity regarding which the messaging server system 108 stores data may be a recognized entity. Each entity is provided with a unique identifier, as well as an entity type identifier (not shown).

The entity graph 304 furthermore stores information regarding relationships and associations between entities. Such relationships may be social, professional (e.g., work at a common corporation or organization) interested-based or activity-based, merely for example.

The database 120 also stores annotation data, in the example form of filters, in an annotation table 312. Filters for which data is stored within the annotation table 312 are associated with and applied to videos (for which data is stored in a video table 310) and/or images (for which data is stored in an image table 308). Filters, in one example, are overlays that are displayed as overlaid on an image or video during presentation to a recipient user. Filters may be of varies types, including a user-selected filters from a gallery of filters presented to a sending user by the messaging client application 104 when the sending user is composing a message. Other types of filers include geolocation filters (also known as geo-filters) which may be presented to a sending user based on geographic location. For example, geolocation filters specific to a neighborhood or special location may be presented within a user interface by the messaging client application 104, based on geolocation information determined by a GPS unit of the client device 102. Another type of filer is a data filer, which may be selectively presented to a sending user by the messaging client application 104, based on other inputs or information gathered by the client device 102 during the message creation process. Example of data filters include current temperature at a specific location, a current speed at which a sending user is traveling, battery life for a client device 102 or the current time.

Other annotation data that may be stored within the image table 308 is so-called “lens” data. A “lens” may be a real-time special effect and sound that may be added to an image or a video.

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

A story table 306 stores data regarding collections of messages and associated image, video or audio data, which are compiled into a collection (e.g., a 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).

As used herein, an “electronic message” may refer to any message in electronic form, such as an email, a short message service (SMS) message, a multimedia message service (MMS) message, an instant message (IM), Internet Relay Chat (IRC) messages, as well as any other form of real-time, near-real-time, synchronous, or asynchronous electronic messaging format. Embodiments of the present disclosure may generate and present customized images for use within electronic messages such as SMS or MMS texts and emails. The customized images may also be utilized in conjunction with the stories, filters, and ephemeral messaging functionality discussed herein.

FIGS. 4A-4C are flow diagrams illustrating example processes according to various aspects of the disclosure. Although the flowcharts may describe the operations as a sequential process, many of the operations can be performed in parallel or concurrently. In addition, the order of the operations may be re-arranged. A process is terminated when its operations are completed. A process may correspond to a method, a procedure, or the like. The steps of methods may be performed in whole or in part, may be performed in conjunction 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 FIG. 1 and/or FIG. 7.

FIGS. 4A-4C depict exemplary processes of generating aggregated media content in an electronic messaging application according to various aspects of the present disclosure. At block 401 of FIG. 4A, an application server of the messaging server system receives a first media content item from a first client device. Media content items include, for example, images, video, text and audio. In one embodiment, the media content items may be added to a collection of media data (e.g., a story).

In one example, interfaces are provided on the first client device for a user to add the first media content item to the collection of media data. For example, FIG. 5A illustrates example interfaces according to various aspects of the disclosure. The left interface 502, allows the user of the first client device to navigate through a plurality of stories 504-510 that have been generated by other client devices (e.g., other users of the system) or by other third-party servers (e.g., advertisers and companies). When the user of the first client device wants to add a media content item to his story, he may for example select an option to add a media content item, such as the plus (+) symbol 512 on the top right of the left interface 502. In response, the application server causes the right interface 520 of FIG. 5A to be displayed on the first client device. In another embodiment, in response to the user adding media content item to his story, the first client device causes the right interface to be displayed. As shown in FIG. 5A, the right interface 514 provides the user with three options of different types of the stories that he can generate. These options include a private story, a custom story and a geographical story (e.g., geo story).

In FIG. 5B, a sequence of different interfaces related to the creation of a private story are illustrated. A private story is a collection of media content items to which only the user of the first client device can add media content items. The user of the first client device also selects the users that can receive and view the private story. For example, when the user of the first client device selects to create a private story in a first interface 520 by selecting the private story selectable item, a second interface 521 is caused to be displayed on the first client device that allows the user to select other users to receive or view the private story. Once the users to receive or view the private story are selected, the third interface 522 is caused to be displayed and provides the user with the summary of the people who can add to the story only the user of the first device) and the selected users that can receive or view the private story as well as the option to save the private story to a storage (e.g., Autosave to Memories). The user may also request to edit the users to receive and view the private story in the third interface 522 and return to the second interface 521. In one embodiment, the application server or the first client device may cause the interfaces to be displayed.

In FIG. 5C, a sequence of different interfaces related to the creation of a custom story are illustrated. A custom story is a story to which the user of the first client device and selected users can add media content items. The user of the first client device and the selected users form a group of users who have access to view the custom story and who may add other users to the group. For example, when the user of the first client device selects to create a custom story in the first interface 520 by selecting the custom story selectable item, a second interface 525 is caused to be displayed on the first client device that allows the user to select other users to receive or view the custom story as well as add to the custom story. Once the users are selected, the third interface 526 is caused to be displayed and provides the user with the summary of the people who can add to the story, that can receive or view the custom story as well as the option to save the custom story to a storage (e.g., Autosave to Memories). The user may also request to edit the users to receive and view the custom story as well as to add to the custom story in the third interface 522 and return to the second interface 525. In one embodiment, the application server or the first client device may cause the interfaces to be displayed.

In FIG. 5D, a sequence of different interfaces related to the creation of a geographical story are illustrated. A geographical story is a story that can be viewed by the user of the first client device and users that are within a predetermined distance from the user of the first client device. As shown in FIG. 5D, the predetermined distance may be delineated by a geofence 531 around the user of the first client device. The user may also limit the users that can view this geographical story to only his friends (e.g., users that are connected to the user on the messaging server system) or to the friends of friends (e.g., users that are connected to the friends of the user on the messaging server system). For example, when the user of the first client device selects to create a geographical story in the first interface 520 by selecting the geographical story selectable item, a second interface 530 is caused to be displayed on the first client device that allows the user to view the geofence 531 around the user of the first client device, to select users who can view this story (e.g., friends, or friends of friends) and to save the geographical story to storage e.g., Autosave to Memories).

As shown in the interfaces 521 and 525 of FIGS. 5B and 5C, when the user of the first client device selects to generate a private story or a custom story, the user of the first client device may select the users to view the story. Returning to FIG. 4, at Block 402, the application server receives from the first client device the selection of a plurality of users. The plurality of client devices includes a second client device. In one embodiment, the application server causes a group selection interface (e.g., interfaces 521 and 525 of FIGS. 5B and 5C) to be displayed on a display screen of the first client device and receives from the first client device the selection of the plurality of users (using client devices) via the group selection interface. For example, in the interfaces 521 and 525 of FIGS. 5B and 5C, the user of the first client device may select the users associated with the plurality of client devices with whom he wishes to share the first media content item individually, or the user of the first client device may create a group that includes these selected users.

As shown in the interfaces 522 and 526 of FIGS. 5B and 5C, the user of the first client device may edit the name of the story, may edit who can add to the story or view the story, and may choose to save the story to a storage (e.g., Autosave to Memories 527). As shown in FIG. 5C, the user of the first client device may also choose to create a communication session (e.g., Create group chat 528) between the users of the plurality of client devices that are included in the group.

At Block 403 of FIG. 4A, the application server generates a group including the user of the first client device (e.g., first user) and the users of the plurality of client devices selected by the first user. For example, in FIGS. 5B and 5C, the user of the first client device has previously generated the groups “Tacozz” 529 and “Golf Buddies” 524. To generate the group, the application server may store the name of the group in association with identifiers associated with the users or the client devices that are selected to be included in the group. The application server may store the information related to the group at in a storage in the application server or a third-pasty storage communicatively coupled to the application server, Information related to the group may include the customized graphics (e.g., avatars) that associated with the users included in the group.

As used herein, an “avatar” of a user is any visual representation of user. The avatar of a user or individual may be any image resembling or otherwise associated with the user or individual. 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 (i.e., customized avatar characteristics). Such customized 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 received or retrieved from a variety of sources, such as the local memory of a client device as well as from other systems and devices, such as a database or server.

At Block 404, the application server causes a group selectable item to be displayed by client devices associated with users included in the group. The group selectable item includes a new item indication when a new media content item is added to the group. In one embodiment, the application server and/or the client device may cause the group selectable item to be displayed. For example, the application server may send data related to the group to the client device which uses the data to generate the group selectable item. Data may include the identifiers associated with the users in the group, the customized graphics (e.g., avatars) associated with the users in the group, the details and settings related to the group, and the like.

FIG. 5H illustrates an exemplary interface 540 displayed on a second client device associated with a user included in the group. The interface in FIG. 5H includes a plurality of selectable items 541-548 associated with users of other client devices that have communicated with the user of the second client device on the messaging server system. In this example, the user of the second client device is included the group “Golf Buddies.” In FIG. 5H, a group selectable item 550 is shown for the group “Golf Buddies” and the new item indication 551 is a filled in (or colored in) square in this example to indicate that a new media content item has been added to the group. In FIG. 5H, the selectable items 544-547 below the “Golf Buddies” selectable item 550 do not have a new item indication. In the example in FIG. 5H, in lieu of the new item indication, the selectable items 544-547 include indicators 553 and 554 that are grayed out.

At Block 405, the application server receives, from the second client device, a first signal that indicates that a first portion of the group selectable item has been selected. For example, in FIG. 5H, the user of the second client device may activate via a touch screen a first portion of the group selectable item that indicates that the user of the second client device wishes to view the new media content item that has been added to the “Golf Buddies” group, For example, a first portion of the group selectable item may be the portion around the words “Golf Buddies” or the new item indication 551. In one embodiment, the first signal is a request from the user of the second client device to the application server to access the new media content item.

At Block 406, in response to the first signal being received, the application server causes the first media content item to be displayed by the second client device. In one embodiment, the second client device may cause the first media content item to be displayed. The application server may provide access to or send the first media content item to the second client device. For example, when the user of the second client device selects the first portion of the “Golf Buddies” group selectable item, a first media content item that was sent from the first client device is caused to be displayed by the second client device for the user of the second client device to view. Once the first media content item is displayed for a period of time, the application server removes the new item indication from the group selectable item and causes the group selectable item to be displayed by the second client device. For example, the period of time the first media content item is displayed may be the duration of the first media content item (e.g., the length of a first media content item that is a video) or a preset time to display a first media content item that is a still image or text (e.g., 5 to 15 seconds). The user of the second client device may also provide an input to the second client device (e.g., tap on the display screen) to cause the first media content item to replay or stop being displayed (e.g., skip). The user of the second client device may also provide an input to the second client device (e.g., hold the display screen) to pause the display of the first media content item. Once the first media content item is no longer being displayed, in one embodiment, the application server will cause the interface 540 in FIG. 5H to be displayed but will remove the new item indication (e.g., gray out the square 553) of the group selectable item associated with the “Golf Buddies” group.

In FIG. 4B, the method 410 of generating aggregated media content in an electronic messaging application according to one embodiment may continue from Block 406 in FIG. 4A. At Block 411, the application server receives a second media content item from the second client device. For example, the user of the second client device that is included in the “Golf Buddies” group may add a media content item (e.g., images, video, text or audio) to the custom story associated with the “Golf Buddies” group, as shown in FIG. 5C. For example, the application server causes the sequences of interfaces 520, 525, 526 as shown in FIG. 5C to be displayed on the second client device. In one embodiment, the user of the second client device may capture a second media content item via the camera on the second client device, selects the custom story selectable item in interface 520, selects the Golf Buddies 524 selectable item in interface 525, and selects to create the custom story in interface 526 to add the second media content item to the Golf Buddies group. In one embodiment, the second media content item is sent by the second client device to the application server and the application server receives the second media content item to be included in the group story. In one embodiment, the application server stores the second media content item in association with the group in a storage included or communicatively coupled to the application server.

At Block 412, in response to the second media content item being received, the application server causes the group selectable item to be displayed by the client devices associated with the users included in the group. The group selectable item includes a new item indication to indicate that the second media content item was added to the group media collection w group story). For example, the client devices of the other users in the “Golf Buddies” group will display the “Golf Buddies” group selectable item 550 in FIG. 5H with the new item indication 551.

At Block 413, the application server receives, from the first client device, the first signal that indicates that the first portion of the group selectable item has been selected. For example, the user of the first client device that is also in the “Golf Buddies” group may select the first portion of the “Golf Buddies” group selectable item that is displayed on the first client device.

At Block 414, in response to the first signal being received, the application server causes the second media content item to be displayed by the first client device. For example, when the user of the first client device selects the first portion of the “Golf Buddies” group selectable item, the second media content item that was sent from the second client device is caused to be displayed by the first client device for the user of the first client device to view. Once the second media content item is displayed for the period of time (e.g., the duration of the second media content item, or a predetermined period of time such as 5 to 15 seconds), the application server removes the new item indication from the group selectable item and causes the group selectable item to be displayed by the first client device. In one embodiment, to replay the media content items that are included in the group story (or group media collection) that are available, the user of the first client device may select the first portion of the “Golf Buddies” group selectable item 550. In some embodiments, the media content items included in the group story are available for viewing for a limited period of time (e.g., 24 hours from when the media content item was added to the group story).

In FIG. 4C, the method 420 of generating aggregated media content in an electronic messaging application according to one embodiment may continue from Block 406 in FIG. 4A. At Block 421, the application server receives from the second client device content for an electronic message. For example, when the user of the second client device views the first media content item in the group story, the user of the second client device may provide an input (e.g., swipe up on the touchscreen that is displaying the first media content item) to indicate that the user wishes to generate an electronic message in response to the first media content item. The application server may then generate a text box that may receive the content for the electronic message (e.g., typed text input) from the user of the second client device. In one embodiment, the second client device causes the client device to generate the text box. For example, FIG. 5E illustrates an example interface 532 that is displayed on the second client device for generating content for an electronic message. As shown in FIG. 5E, the user of the second client device was viewing the first media content item that was sent to the “Golf Buddies” group and provided the input that caused the second client device to generate the text box for the user to input text for an electronic message (e.g., “Send chat to Golf Buddies”). The user of the second client device may provide text input into the text box which is the content for the electronic message.

At Block 422, in response to receiving the content for the electronic message, the application server causes a new message indication to be displayed in the group selectable item. For example, the “Golf Buddies” group selectable item 550 in FIG. 5H that is displayed by the client devices included in the “Golf Buddies” group includes the new message indication 552 (e.g., filled in or colored in text bubble).

At Block 423, the application server receives from the first client device the first signal that indicates that the first portion of the group selectable item has been selected. For example, the user of the first client device that is also in the “Golf Buddies” group may select the first portion of the “Golf Buddies” group selectable item that is displayed on the first client device. For example, a first portion of the group selectable item may be the portion around the words “Golf Buddies” or the new message indication.

At Block 424, in response to the first signal being received, the application server causes a communication interface for a communication session between the client devices included in the group to be displayed by the first client device. The communication interface includes the electronic message from the second client device. For example, when the user of the first client device selects the first portion of the “Golf Buddies” group selectable item, the electronic message (e.g., a chat message) that was sent from the second client device is caused to be displayed by the first client device for the user of the first client device to view. The communication session may be a group chat interface.

At Block 425, in response to receiving a request to close the communication interface is from the first client device, the application server causes the new message indication to be removed from the group selectable item and causes the group selectable item to be displayed by the first client device.

In addition to the new item indication and the new message indication, the application server may also cause notifications to be displayed on the client devices in the group. For example, FIG. 5F includes different examples of notifications that are displayed on the client devices in the groups.

In one embodiment, the application server causes a notification to be displayed by the second client device that indicates that the first media content item or the electronic message is received in association with the group. In the example notification 533 of FIG. 5F, a notification that a new media content item has been added to the “Brunch Homies” group is a pop-up notification when the user is engaged with the messaging server system. This notification is a text bubble that states: “added to Brunch Homies.” The notification also includes a preview 536 of the new media content item that is added. The preview in this example appears in a circle and replaces the user's avatar.

In another example in FIG. 5F, a notification 534 that a private story was created is a pop-up notification when the user is engaged with the messaging server system. This notification acts as a confirmation that the private story is created. In the example notifications 535 of FIG. 5F, the notifications are generated when the user is not engaged with the messaging server system. These notifications may appear on the client device's screen as pop-up boxes that include the name of the group and the user that sent the new media content item or electronic message.

In one embodiment, the application server receives a second signal that indicates that a second portion of the group selectable item has been selected on the second client device. For example, the user of the second client device that is part of a “Design Team” group may activate a portion of the “Design Team” group selectable item that indicates that he wants to view the details and settings associated with the “Design Team” group. In one embodiment, the second portion of the group selectable item is a circle on the group selectable item.

In response to the second signal being received, the application server may cause a group card interface to be displayed by the second client device. FIG. 5G illustrates two example group card interfaces 537 and 538 that are displayed on the second client device. The left group card interface 537 is the group card that is displayed when there is no active story in the group and the right group card interface 538 is the group card that is displayed when there is an active story in the group. An active story is a story that includes a media content item that is still accessible to be viewed. The difference between the group card interfaces in FIG. 5G appears in the selectable item 560 and 561 (e.g., “Design Team's Story”) that is at the top of each of the group card interfaces. When there is an active story (right), the preview of the media content item in the story appears in the circle 563 whereas when there is no active story (left), the circle 562 may include the avatars of the users in the group.

As shown in FIG. 5G, the group card interface 537, 538 may include selectable items 564 associated with each user of a client device included in the group, The group card interface 537, 538 also includes a map 565 that shows the locations of the client devices in the group. In one example, the map 565 includes the avatars of the users of the client devices in the group. The group card interface 537, 538 may also include, for example, a location sharing item (not shown) that allows a location of the second client device to be shared with the group (e.g., “Share My Location” item), a group name editing item 566 to edit a name of the group (e.g., “Edit Group Name” item), a mute item (not shown) that allows the second client device to stop receiving notifications associated with media content item from the group, (e.g., “Mute Story” item), a do not disturb item 567 that allows the second client device to stop receiving notifications associated with the group (e.g., “Do Not Disturb” item or toggle switch), a clear electronic messages item (not shown) that allows the second client device to clear the electronic messages in the communication session (e.g., “Clear Conversation” item), an add member item 569 that allows the second client device to add a third client device to the group (e.g., “Add to Group” item), or a leaving group item 570 that allows the second client device to remove the second client device from the group (e.g., “Leave Group” item), The group card interface 537, 538 may also include, for example, a story save item 568 that allows the second client device to automatically save the media content items that are added to the group story (e.g., “Autosave Group Story” item 568 or toggle switch).

Software Architecture

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

As used herein, the term “component” may refer to a device, physical entity or logic having boundaries defined by function or subroutine calls, branch points, application program interfaces (APIs), and/or other technologies that provide for the partitioning or modularization of particular processing or control functions. Components may he 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 circuity (e.g., configured by software) may be driven by cost and time considerations.

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

Accordingly, the phrase “hardware component”(or “hardware-implemented component”) should be understood to encompass a tangible entity, be that an entity that is physically constructed, permanently configured (e.g., hardwired), or temporarily configured (e.g., programmed) to operate in a certain manner or to perform certain operations described herein. Considering embodiments in which hardware components are temporarily configured (e.g., programmed), each of the hardware components need not be configured or instantiated at any one instance in time. For example, where a hardware component comprises a general-purpose processor configured by software to become a special-purpose processor, the general-purpose processor may be configured as respectively different special-purpose processors (e.g., comprising different hardware components) at different times. Software accordingly configures a particular processor or processors, for example, to constitute a particular hardware component at one instance of time and to constitute a different hardware component at a different instance of time. Hardware components can provide information to, and receive information from, other hardware components. Accordingly, the described hardware components may be regarded as being communicatively coupled. Where multiple hardware components exist contemporaneously, communications may be achieved through signal transmission (e.g., over appropriate circuits and buses) between or among two or more of the hardware components. In embodiments in which multiple hardware components are configured or instantiated at different times, communications between such hardware components may be achieved, for example, through the storage and retrieval of information in memory structures to which the multiple hardware components have access.

For example, one hardware component may perform an operation and store the output of that operation in a memory device to which it is communicatively coupled. A further hardware component may then, at a later time, access the memory device to retrieve and process the stored output. Hardware components may also initiate communications with input or output devices, and can operate on a resource (e.g., a collection of information). The various operations of example methods described herein may be performed, at least partially, by one or more processors that are temporarily configured (e.g., by software) or permanently configured to perform the relevant operations. Whether temporarily or permanently configured, such processors may constitute processor-implemented components that operate to perform one or more operations or functions described herein. As used herein, “processor-implemented component” refers to a hardware component implemented using one or more processors. Similarly, the methods described herein may be at least partially processor-implemented, with a particular processor or processors being an example of hardware. For example, at least some of the operations of a method may be performed by one or more processors or processor-implemented components.

Moreover, the one or more processors may also operate to support performance of the relevant operations in a “cloud computing” environment or as a “software as a service” (SaaS). For example, at least some of the operations may be performed by a group of computers (as examples of machines including processors), with these operations being accessible via a network (e.g., the Internet) and via one or more appropriate interfaces (e.g., an Application Program Interface (API)). The performance of certain of the operations may be distributed among the processors, not only residing within a single machine, but deployed across a number of machines. In some exemplary embodiments, the processors or processor-implemented components may be located in a single geographic location (e.g., within a home environment, an office environment, or a server farm). In other exemplary embodiments, the processors or processor-implemented components may be distributed across a number of geographic locations.

In the exemplary architecture of FIG. 6, the software architecture 606 may be conceptualized as a stack of layers where each layer provides particular functionality. For example, the software architecture 606 may include layers such as an operating system 602, libraries 620, applications 616 and a presentation layer 614. Operationally, the applications 616 and/or other components within the layers may invoke application programming interface (API) API calls 608 through the software stack and receive messages 612 in response to the API calls 608. The layers illustrated are representative in nature and not all software architectures have all layers. For example, some mobile or special purpose operating systems may not provide a frameworks/middleware 618, while others may provide such a layer. Other software architectures may include additional or different layers.

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

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

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

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

The applications 616 may use built in operating system functions (e.g., kernel 622, services 624 and/or drivers 626), libraries 620, and frameworks-'middleware 618 to create user interfaces to interact with users of the system. Alternatively, or additionally, in some systems interactions with a user may occur through a presentation layer, such as presentation layer 614. In these systems, the application/component “logic” can be separated from the aspects of the application/component that interact with a user.

FIG. 7 is a block diagram illustrating components (also referred to herein as “modules”) of a machine 700, according to some exemplary embodiments, able to read instructions from a machine-readable medium (e.g., a machine-readable storage medium) and perform any one or more of the methodologies discussed herein. Specifically, FIG. 7 shows a diagrammatic representation of the machine 700 in the example form of a computer system, within which instructions 710 (e.g., software, a program, an application, an apples, an app, or other executable code) for causing the machine 700 to perform any one or more of the methodologies discussed herein may be executed. As such, the instructions 710 may be used to implement modules or components described herein. The instructions 710 transform the general, non-programmed machine 700 into a particular machine 700 programmed to carry out the described and illustrated functions in the manner described. In alternative embodiments, the machine 700 operates as a standalone device or may be coupled (e.g., networked) to other machines. In a networked deployment, the machine 700 may operate in the capacity of a server machine or a client machine in a server-client network environment, or as a peer machine in a peer-to-peer (or distributed) network environment. The machine 700 may comprise, but not be limited to, a server computer, a client computer, a personal computer (PC), a tablet computer, a laptop computer, a netbook, a set-top box (STB), a personal digital assistant (PDA), an entertainment media system, a cellular telephone, a smart phone, a mobile device, a wearable device (e.g., a smart watch), a smart home device (e.g., a smart appliance other smart devices, a web appliance, a network router, a network switch, a network bridge, or any machine capable of executing the instructions 710, sequentially or otherwise, that specify actions to be taken by machine 700. Further, while only a single machine 700 is illustrated, the term “machine” shall also be taken to include a collection of machines that individually or jointly execute the instructions 710 to perform any one or more of the methodologies discussed herein.

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

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

The I/O components 718 may include a wide variety of components to provide a user interface for receiving input, providing output, producing output, transmitting information, exchanging information, capturing measurements, and so on. The specific I/O components 718 that are included in the user interface of a particular machine 700 will depend on the type of machine. For example, portable machines such as mobile phones will likely include a touch input device or other such input mechanisms, while a headless server machine will likely not include such a touch input device. It will be appreciated that the I/O components 718 may include many other components that are not shown in FIG. 7. The output components 718 are grouped according to functionality merely for simplifying the following discussion and the grouping is in no way limiting. In various exemplary embodiments, the I/O components 718 may include output components 726 and input components 728. The output components 726 may include visual components (e.g., a display such as a plasma display panel (PDP), a light emitting diode (LED) display, a liquid crystal display (LCD), a projector, or a cathode ray tube (CRT)), acoustic components (e.g., speakers), haptic components (e.g., a vibratory motor, resistance mechanisms), other signal generators, and so forth. The input components 728 may include alphanumeric input components (e.g., a keyboard, a touch screen configured to receive alphanumeric input, a photo-optical keyboard, or other alphanumeric input components), point based input components (e.g., a mouse, a touchpad, a trackball, a joystick, a motion sensor, or other pointing instrument), tactile input components (e.g., a physical button, a touch screen that provides location and/or force of touches or touch gestures, or other tactile input components), audio input components (e.g., a microphone), and the like. The input components 728 may also include one or more image-capturing devices, such as a digital camera for generating digital images and/or video.

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

For example, the biometric components 730 may include components to detect expressions (e.g., hand expressions, facial expressions, vocal expressions, body gestures, or eye tracking), measure biosignals (e.g., blood pressure, heart rate, body temperature, perspiration, or brain waves), identify a person (e.g., voice identification, retinal identification, facial identification, fingerprint identification, or electroencephalogram based identification), and the like. The motion components 734 may include acceleration sensor components (e.g., accelerometer), gravitation sensor components, rotation sensor components (e.g., gyroscope), and so forth. The environment components 736 may include, for example, illumination sensor components (e.g., photometer), temperature sensor components (e.g., one or more thermometer that detect ambient temperature), humidity sensor components, pressure sensor components (e.g., barometer), acoustic sensor components (e.g., one or more microphones that detect background noise), proximity sensor components (e.g., infrared sensors that detect nearby objects), gas sensors (e.g., gas detection sensors to detection concentrations of hazardous gases for safety or to measure pollutants in the atmosphere), or other components that may provide indications, measurements, or signals corresponding to a surrounding physical environment. The position components 738 may include location sensor components (e.g., a Global Position system (GPS) receiver component), altitude sensor components (e.g., altimeters or barometers that detect air pressure from which altitude may be derived), orientation sensor components (e.g., magnetometers), and the like. For example, the location sensor component may provide location information associated with the system 700, such as the system's 700 GPS coordinates and/or information regarding a location the system 700 is at currently (e.g., the name of a restaurant or other business)

Communication may be implemented using a wide variety of technologies. The I/O components 718 may include communication components 740 operable to couple the machine 700 to a network 732 or devices 720 via coupling 722 and coupling 724 respectively. For example, the communication components 740 may include a network interface component or other suitable device to interface with the network 732. In further examples, communication components 740 may include wired communication components, wireless communication components, cellular communication components, Near Field Communication (NFC) components, Bluetooth® components (e.g., Bluetooth® Low Energy), Wi-Fi® components, and other communication components to provide communication via other modalities. The devices 720 may be another machine or any of a wide variety of peripheral devices (e.g., a peripheral device coupled via a Universal Serial Bus (USB)).

Moreover, the communication components 740 may detect identifiers or include components operable to detect identifiers. For example, the communication components 740 may include Radio Frequency Identification (RFD) tag reader components, NFC smart tag detection components, optical reader components (e.g., an optical sensor to detect one-dimensional bar codes such as Universal Product Code (UPC) bar code, multi-dimensional bar codes such as Quick Response (QR) code, Aztec code, Data Matrix, Dataglyph, MaxiCode, PDF417, Ultra Code, UCC RSS-2D bar code, and other optical codes), or acoustic detection components (e.g., microphones to identify tagged audio signals). In addition, a variety of information may be derived via the communication components 740, such as, location via Internet Protocol (IP) geo-location, location via Wi-Fi® signal triangulation, location via detecting a NFC beacon signal that may indicate a particular location, and so forth.

Where a phrase similar to “at least one of A, B, or C,” “at least one of 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-4 and B, A and C, B and C, or A and B and C.

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.

	Number	Date	Country
Parent	16203356	Nov 2018	US
Child	17883196		US

AGGREGATED MEDIA CONTENT IN AN ELECTRONIC MESSAGING APPLICATION

Information

Publication Number

Date Filed

Date Published

Inventors

Original Assignees

CPC

International Classifications

Abstract

Description

Claims

CROSS REFERENCED TO RELATED APPLICATIONS

Provisional Applications (1)

Continuations (1)