Patent Description:
The popularity of electronic messaging, particularly instant messaging, continues to grow. Users increasingly share media content items such as electronic images and videos with each other, reflecting a global demand to communicate more visually.

Users also increasingly use customized avatars that can be personalized to represent the users in various applications, video games, messaging services, etc. Since the customized avatars can be generated in a different array of situations, displaying various emotions, or even be animated, the users are able to communicate their feelings and actions more accurately in the systems using the customized avatars.

With the increasing number of users on social networking systems, each user also has a growing network of individuals that she follows. Therefore, in order to maintain the user's engagement on social networking systems, 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 her. 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 her to view the curated media content items and further interact the network of individuals that she follows.

<CIT> concerns generation of customized media content items based on location sensor information from users' computing devices. The media content items can be generated for a variety of topics and shared with other users. For example, media content (e.g., images or video) can be generated and displayed on a user's computing device, as well as transmitted to other users via electronic communications, such as short message service (SMS) or multimedia service (MMS) texts and emails.

<CIT> relates to a map-based graphical user interface indicating geospatial activity metrics. The interface is a server-side administrative interface for a social media platform that allows for restriction of defined geographical areas. Social media items originating from such restricted areas are automatically filtered or age-restricted for availability via a map-based graphical user interface of the social media platform.

<CIT> concerns organization of meetings using a server, a global positioning system (GPS), and the mobile devices of a user and one or more other participants.

The invention is a system, method and computer-readable storage medium as defined in the appended claims.

Among other things, embodiments of the present disclosure improve the functionality of electronic messaging software and systems by generating a map interface that is personalized to the user. Currently, users can consult maps to visually locate given establishments (e.g., restaurants, bars, gyms, etc.) and obtain the coordinates or address of the establishments. These current maps are generally identical for each user that consults the map.

As an improvement, in some embodiments, each user's map interface can be personalized based on the user's habits and visits to specific establishments. For example, the map interface can include avatars of the user and the user's friends (e.g., connections on a social network, contacts in the user's mobile device, etc.) at locations on the map interface that corresponds to their current locations, respectively. The map interface can also include icons associated with establishments that are private spaces or public spaces. When a user saves an establishment via the map interface, the icon associated with the saved establishment can change into an enhanced icon. For example, the icon can be a two-dimensional image and the enhanced icon can be a three-dimensional image. In one embodiment, the enhanced icon can be a larger, more detailed version of the icon or an animated version of the icon. The system can also personalize the user's map interface automatically based on determining that a user frequents an establishment regularly. The system can also determine that an establishment should be recommended to the user based on the similarity to other establishments that were saved by the user on the map interface. The system can also determine that an establishment should be recommended to the user based on locations that the user's friends have saved on their map interfaces or that are previously recommended to the user's friends. The system can thus personalize the user's map interface automatically by generating an enhanced icon for the establishment that it is recommending. By engaging with the system, the user's map will, over time, include a growing number of enhanced icons such that the user can visually assess the locations of his preferred establishments or establishments that were recommended to him by his friends or by the system. The system thus improves the operation of a client device by generating a map interface which provides efficient use of screen resources (e.g., icons, enhanced icons, avatars, etc.) and reduces interface actions and operations to access information that is provided visually. This improvement also will increase the engagement of users with the system to further develop their map interface and to view and interact with the automatic enhancements that are added by the system to their map interface.

<FIG> is a block diagram showing an example messaging system <NUM> for exchanging data (e.g., messages and associated content) over a network. The messaging system <NUM> includes multiple client devices <NUM>, each of which hosts a number of applications including a messaging client application <NUM>. Each messaging client application <NUM> is communicatively coupled to other instances of the messaging client application <NUM> and a messaging server system <NUM> via a network <NUM> (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 <NUM>) 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>, each messaging client application <NUM> is able to communicate and exchange data with another messaging client application <NUM> and with the messaging server system <NUM> via the network <NUM>. The data exchanged between messaging client applications <NUM>, and between a messaging client application <NUM> and the messaging server system <NUM>, includes functions (e.g., commands to invoke functions) as well as payload data (e.g., text, audio, video or other multimedia data).

The network <NUM> 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 (GPRS) technology, Enhanced Data rates for GSM Evolution (EDGE) technology, third Generation Partnership Project (3GPP) including <NUM>, fourth generation wireless (<NUM>) networks, Universal Mobile Telecommunications System (UMTS), High Speed Packet Access (HSPA), Worldwide Interoperability for Microwave Access (WiMAX), Long Term Evolution (LTE) standard, others defined by various standard setting organizations, other long range protocols, or other data transfer technology.

The messaging server system <NUM> provides server-side functionality via the network <NUM> to a particular messaging client application <NUM>. While certain functions of the messaging system <NUM> are described herein as being performed by either a messaging client application <NUM> or by the messaging server system <NUM>, it will be appreciated that the location of certain functionality either within the messaging client application <NUM> or the messaging server system <NUM> is a design choice. For example, it may be technically preferable to initially deploy certain technology and functionality within the messaging server system <NUM>, but to later migrate this technology and functionality to the messaging client application <NUM> where a client device <NUM> has a sufficient processing capacity.

The messaging server system <NUM> supports various services and operations that are provided to the messaging client application <NUM>. Such operations include transmitting data to, receiving data from, and processing data generated by the messaging client application <NUM>. 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 <NUM> are invoked and controlled through functions available via user interfaces (UIs) of the messaging client application <NUM>.

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

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

The application server <NUM> hosts a number of applications and subsystems, including a messaging server application <NUM>, an image processing system <NUM> and a social network system <NUM>. The messaging server application <NUM> 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 <NUM>. 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 <NUM>, to the messaging client application <NUM>. Other processor and memory intensive processing of data may also be performed server-side by the messaging server application <NUM>, in view of the hardware requirements for such processing.

The application server <NUM> also includes an image processing system <NUM> 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 <NUM>.

The social network system <NUM> supports various social networking functions services and makes these functions and services available to the messaging server application <NUM>. To this end, the social network system <NUM> maintains and accesses an entity graph <NUM> within the database <NUM>. Examples of functions and services supported by the social network system <NUM> include the identification of other users of the messaging system <NUM> 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 <NUM> is communicatively coupled to a database server <NUM>, which facilitates access to a database <NUM> in which is stored data associated with messages processed by the messaging server application <NUM>.

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 <NUM>. 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> is block diagram illustrating further details regarding the messaging system <NUM>, according to exemplary embodiments. Specifically, the messaging system <NUM> is shown to comprise the messaging client application <NUM> and the application server <NUM>, which in turn embody a number of some subsystems, namely an ephemeral timer system <NUM>, a collection management system <NUM> and an annotation system <NUM>.

The ephemeral timer system <NUM> is responsible for enforcing the temporary access to content permitted by the messaging client application <NUM> and the messaging server application <NUM>. To this end, the ephemeral timer system <NUM> 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 <NUM>.

The collection management system <NUM> 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 <NUM> 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 <NUM>.

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 <NUM> operates to automatically make payments to such users for the use of their content.

The annotation system <NUM> 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 <NUM> provides functions related to the generation and publishing of media overlays for messages processed by the messaging system <NUM>. The annotation system <NUM> operatively supplies a media overlay (e.g., a filter) to the messaging client application <NUM> based on a geolocation of the client device <NUM>. In another example, the annotation system <NUM> operatively supplies a media overlay to the messaging client application <NUM> based on other information, such as, social network information of the user of the client device <NUM>. 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 <NUM>. For example, the media overlay including text that can be overlaid on top of a photograph generated taken by the client device <NUM>. 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 <NUM> uses the geolocation of the client device <NUM> to identify a media overlay that includes the name of a merchant at the geolocation of the client device <NUM>. The media overlay may include other indicia associated with the merchant. The media overlays may be stored in the database <NUM> and accessed through the database server <NUM>.

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

<FIG> is a schematic diagram <NUM> illustrating data <NUM> which may be stored in the database <NUM> of the messaging server system <NUM>, according to certain exemplary embodiments. While the content of the database <NUM> 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 <NUM> includes message data stored within a message table <NUM>. The entity table <NUM> stores entity data, including an entity graph <NUM>. Entities for which records are maintained within the entity table <NUM> may include individuals, corporate entities, organizations, objects, places, events etc. Regardless of type, any entity regarding which the messaging server system <NUM> 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 <NUM> 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 <NUM> also stores annotation data, in the example form of filters, in an annotation table <NUM>. Filters for which data is stored within the annotation table <NUM> are associated with and applied to videos (for which data is stored in a video table <NUM>) and/or images (for which data is stored in an image table <NUM>). 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 <NUM> 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 <NUM>, based on geolocation information determined by a GPS unit of the client device <NUM>. Another type of filer is a data filer, which may be selectively presented to a sending user by the messaging client application <NUM>, based on other inputs or information gathered by the client device <NUM> 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 <NUM> or the current time.

Other annotation data that may be stored within the image table <NUM> 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 <NUM> stores video data which, in one embodiment, is associated with messages for which records are maintained within the message table <NUM>. Similarly, the image table <NUM> stores image data associated with messages for which message data is stored in the entity table <NUM>. The entity table <NUM> may associate various annotations from the annotation table <NUM> with various images and videos stored in the image table <NUM> and the video table <NUM>.

A story table <NUM> 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 <NUM>). 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 <NUM> 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 <NUM>, to contribute content to a particular live story. The live story may be identified to the user by the messaging client application <NUM>, 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 <NUM> 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.

<FIG> depicts an exemplary process <NUM> of generating a personalized map interface with enhanced icons according to various aspects of the present disclosure. The process <NUM> may be performed by a processor included in the application server of the messaging server system or by a processor included in a client device.

At operation <NUM> of process in <FIG>, the processor receives from a first client device associated with a first user a location information that includes a location of the first client device. The location information can be received from a location sensor included in the first client device. For example, the first client device may include a GPS unit that provides coordinates of the location of the first client device to the processor.

At operation <NUM>, the processor causes a map interface to be displayed on the first client device. The map interface can include an avatar of the first user at a location on the map display based on the location information and an icon corresponding to an establishment.

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 <NUM> as well as from other systems and devices, such as a database or server.

At operation <NUM>, the processor causes the icon included in the map interface to change to an enhanced icon. In one embodiment, each of the establishments that are located within the map interface are associated with an icon. For example, the icon associated with a pizza restaurant can be a pizza slice. The pizza slice icon is included in the map interface at the location corresponding to the location of the pizza restaurant. In one embodiment, the icon is a two-dimensional image whereas the enhanced icon is a three-dimensional image. The processor can cause the icon to change to the enhanced icon in response to receiving a first selection from the first client device that indicates a request to save the establishment in a database associated with the first user. For example, the database associated with the first user can include a list of favorite establishments. The list of favorite establishments can be a list of establishments that have been previously saved by the first user via the map interface. In one embodiment, the list of favorite establishments can include establishments that have been previously saved by a second user. The second user can be associated to the first user in the messaging system <NUM> (e.g., friends, connections, followers, etc.).

According to the invention, the processor can also cause the icon to change to the enhanced icon at operation <NUM> in response to the processor determining that the establishment is saved in a database associated with the second user that is associated with the first user. For example, the database associated with the second user can include a list of establishments that were previously saved by the second user via the second user's map interface. In one embodiment, the system causes the second client device to display a map interface that is personalized for the second user. The map interface displayed on the second client device includes a second user's avatar and enhanced icons for establishments that are in the second user's list of favorite establishments.

<FIG> illustrate examples of map interface <NUM> that is displayed on the first client device. <FIG> illustrate examples of the map interface <NUM> when the processor automatically adds an establishment to the first user's database and causes the map interface <NUM> to include an enhanced icon associated with the establishment. In this embodiment, the processor performs the updates to the map interface without the receiving the inputs from the first client device. <FIG> illustrates examples of the map interface <NUM> when the processor receives a selection from the first client device requesting to save the establishment to the first user's database and in response, causes the map interface <NUM> to include an enhanced icon associated with the establishment.

In <FIG>, an example of a map interface <NUM> that is displayed on the first client device is illustrated. The map interface <NUM> includes a first avatar <NUM> associated with the user of the first client device ("first user"), and a plurality of avatars 502_1 to 502_N (N><NUM>) associated with users of other client devices that are connected to the first user on the messaging system.

As shown in <FIG>, the first avatar <NUM> is illustrated at the location on the map interface <NUM> that corresponds to the current location of the first client device. The processor uses the location information received at Block <NUM> in <FIG> to determine the location of the map interface <NUM> at which to place the first user's avatar <NUM>. Similarly, the avatars 502_1 to 502_N are illustrated on the map interface at locations corresponding to the locations of their client devices. The avatars 502_1 to 502_N do not appear in the map interface <NUM> when the locations corresponding to the locations of their client devices are not within the current view of the map interface <NUM>. For example, the map interface <NUM> includes a view of a portion of Manhattan, New York. Users that are associated with the first user but that are located in Brooklyn, New York, are outside of the current view of the map interface <NUM> such that their avatars do not appear on the current view of the map interface <NUM>. While not shown, the avatars 502_1 to 502_N can be illustrated in a cluster of avatars which indicates that the users associated with clustered avatars are currently assembled together at the location corresponding to the location on the map interface <NUM>.

The map interface <NUM> includes an enhanced icon <NUM> associated with an establishment (e.g., "The Saratoga" in <FIG>). The enhanced icon <NUM> appears at a location on the map interface <NUM> that corresponds to the address of the establishment (e.g., "<NUM> W <NUM>th Street, New York" in <FIG>). While the establishment in <FIG>5D is a restaurant, the establishments associated with icons and enhanced icons in the map interface <NUM> can be any private or public space. For example, the establishment can be a restaurant, a bar, a museum, a venue, a movie theatre, a theatre, a school, a gym, a dance studio, a yoga studio, a national park, a ski resort, or a park.

As shown in <FIG>, the processor can automatically cause the map interface <NUM> to include the enhanced icon associated with "The Saratoga" establishment. For example, the processor can determine that the first user has frequented the establishment predetermined number of times or at a predetermined frequency and in response, the processor can automatically cause the map interface to include the enhanced icon associated with the establishment.

<FIG> illustrates a map interface <NUM> including an establishment detail interface. When the first user selects the enhanced icon <NUM> on from the map interface <NUM>, the processor receives the selection of the enhanced icon <NUM> from the first client device. In response the processor causes the establishment detail interface to be displayed on the first client device. As shown in <FIG>, the establishment detail interface can include, for example, a name of the establishment (e.g., "The Saratoga") and a message <NUM> indicating why the establishment is recommended to the first user (e.g. "Most Visited Restaurant"). When the processor determines that the establishment should be recommended to the first user because a second user that is associated with the first user in the messaging system has the establishment saved in the second user's database, the message <NUM> can indicate the establishment as a recommendation based on the second user (e.g., "Second User's Favorite Restaurant"). The processor can also determine that the establishment should be recommended based on the establishment being saved by a predetermined number of users that are associated with the first user. The message <NUM> can indicate, for example, "Ten of your friends have favorited".

The establishment details interface can include an identity card <NUM> associated with the establishment. The identity card <NUM> can include the name of the establishment, a type of establishment (e.g., "American Restaurant"), the price level associated with the restaurant (e.g., "$$"), a selectable save image <NUM>, and a selectable preview <NUM>. The processor having automatically saved the establishment for the first user in <FIG> will cause the selectable save image <NUM> in <FIG> to appear activated (e.g., the selectable save image <NUM> is a filled image of a star). When the first user selects the selectable preview <NUM>, the processor causes the first client device to display media content items that are associated with the establishment. For example, a collection of the media content items (e.g., pictures, videos, text, etc.) that were taken at "The Saratoga" during a preset timeframe (e.g., <NUM> hours) will be accessible to users of the messaging system <NUM> via the selectable preview <NUM>. The collection of media content items can be the "story" associated with the establishment. As shown in <FIG>, the identity card <NUM> can also include a timestamp of the media content item that was last added to the establishment's story (e.g., "<NUM> minutes ago in New York"). The establishment details interface can also include a message <NUM> providing news or details about the establishment.

In <FIG>, the map interface <NUM> includes the first avatar <NUM> and the icon <NUM> associated with the establishment (e.g., "The Saratoga"). When the first user selects the icon <NUM>, the processor receives the selection of the icon <NUM> from the first client device and causes the establishment details interface shown in <FIG> to be displayed on the first client device. The establishment details interface in <FIG> includes a message <NUM> that includes the name and the address of the establishment. The establishment details interface in <FIG> also includes the identity card <NUM> associated with the establishment. The identity card <NUM> includes the name of the establishment, the type of establishment, the price level associated with the restaurant, the selectable save image <NUM>, and the selectable preview <NUM>. The identity card <NUM> can also include the timestamp of the media content item that was last added to the establishment's story (e.g., "<NUM> minutes ago in New York") and a message <NUM> providing news or details about the establishment. In contrast to <FIG>, the selectable save image <NUM> is not active in <FIG> (e.g., the selectable save image <NUM> is an unfilled image of a star). The identity card <NUM> can further include the prompt message <NUM> (e.g., "Add to favorites"). In order to send a request to save the establishment to the first user's database, the first user can select the selectable save image <NUM> on the map interface <NUM> of <FIG>. When the first user selects the selectable save image <NUM>, the processor can cause the first client device to display the map interface <NUM> shown in <FIG>.

In <FIG>, the map interface <NUM> includes the identity card <NUM> with the selectable save image <NUM> that is active to indicate that the establishment is added to the first user's list of favorite establishments. The establishment is thus added to the first user's database. The active selectable save image <NUM> can be a filled image of a star. The map interface <NUM> in <FIG> further includes the enhanced icon <NUM> in place of the icon <NUM>. In one example, the icon <NUM> can be a two-dimensional image while the enhanced icon <NUM> can be a three-dimensional image. In one embodiment, the enhanced icon <NUM> can be a larger, more detailed version of the icon <NUM> or an animated version of the icon <NUM>.

In one embodiment, the first user can request a list of the favorite establishments via a selectable image (not shown) on the map interface <NUM>. When the first user selects the selectable image to request the list, the processor receives the request and causes the list of favorite establishments to be displayed on the first client device. The processor can retrieve the list of favorite establishments from the database associated with the first user. The first user can also select a selectable image (not shown) on the map interface <NUM> to request the list of the favorite establishments of a second user. The processor receives the request, retrieves the list of favorite establishments from the database associated with the second user, and cause the list of favorite establishments of the second user to be displayed by the first client device.

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

As used herein, the term "component" may refer to a device, physical entity or logic having boundaries defined by function or subroutine calls, branch points, application program interfaces (APIs), and/or other technologies that provide for the partitioning or modularization of particular processing or control functions. Components may be combined via their interfaces with other components to carry out a machine process. A component may be a packaged functional hardware unit designed for use with other components and a part of a program that usually performs a particular function of related functions.

Components may constitute either software components (e.g., code embodied on a machine-readable medium) or hardware components. A "hardware component" is a tangible unit capable of performing certain operations and may be configured or arranged in a certain physical manner. In various exemplary embodiments, one or more computer systems (e.g., a standalone computer system, a client computer system, or a server computer system) or one or more hardware components of a computer system (e.g., a processor or a group of processors) may be configured by software (e.g., an application or application portion) as a hardware component that operates to perform certain operations as described herein. A hardware component may also be implemented mechanically, electronically, or any suitable combination thereof. For example, a hardware component may include dedicated circuitry or logic that is permanently configured to perform certain operations.

A hardware component may be a special-purpose processor, such as a Field-Programmable Gate Array (FPGA) or an Application Specific Integrated Circuit (ASIC). A hardware component may also include programmable logic or circuitry that is temporarily configured by software to perform certain operations. For example, a hardware component may include software executed by a general-purpose processor or other programmable processor. Once configured by such software, hardware components become specific machines (or specific components of a machine) uniquely tailored to perform the configured functions and are no longer general-purpose processors. It will be appreciated that the decision to implement a hardware component mechanically, in dedicated and permanently configured circuitry, or in temporarily configured circuitry (e.g., configured by software) may be driven by cost and time considerations.

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

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

For example, one hardware component may perform an operation and store the output of that operation in a memory device to which it is communicatively coupled. A further hardware component may then, at a later time, access the memory device to retrieve and process the stored output. Hardware components may also initiate communications with input or output devices, and can operate on a resource (e.g., a collection of information). 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.

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

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

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

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

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

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

The machine <NUM> may include processors <NUM>, memory memory/storage <NUM>, and I/O components <NUM>, which may be configured to communicate with each other such as via a bus <NUM>. The memory/storage <NUM> may include a memory <NUM>, such as a main memory, or other memory storage, and a storage unit <NUM>, both accessible to the processors <NUM> such as via the bus <NUM>. The storage unit <NUM> and memory <NUM> store the instructions <NUM> embodying any one or more of the methodologies or functions described herein. The instructions <NUM> may also reside, completely or partially, within the memory <NUM>, within the storage unit <NUM>, within at least one of the processors <NUM> (e.g., within the processor's cache memory), or any suitable combination thereof, during execution thereof by the machine <NUM>. Accordingly, the memory <NUM>, the storage unit <NUM>, and the memory of processors <NUM> 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 <NUM> 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 <NUM> that are included in the user interface of a particular machine <NUM> 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 <NUM> may include many other components that are not shown in <FIG>. The I/O components <NUM> 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 <NUM> may include output components <NUM> and input components <NUM>. The output components <NUM> 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 <NUM> 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 <NUM> 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 <NUM> may include biometric components <NUM>, motion components <NUM>, environmental environment components <NUM>, or position components <NUM>, 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 <NUM>, the environment of the machine <NUM>, a user of the machine <NUM>, or a combination thereof.

For example, the biometric components <NUM> 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 <NUM> may include acceleration sensor components (e.g., accelerometer), gravitation sensor components, rotation sensor components (e.g., gyroscope), and so forth. The environment components <NUM> 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 <NUM> 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 <NUM>, such as the system's <NUM> GPS coordinates and/or information regarding a location the system <NUM> 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 <NUM> may include communication components <NUM> operable to couple the machine <NUM> to a network <NUM> or devices <NUM> via coupling <NUM> and coupling <NUM> respectively. For example, the communication components <NUM> may include a network interface component or other suitable device to interface with the network <NUM>. In further examples, communication components <NUM> 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 <NUM> 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)).

Claim 1:
A system comprising:
a messaging server system (<NUM>) including:
an application server (<NUM>) configured to:
receive from a first client device (<NUM>) location information including a location of the first client device, wherein a first user is associated with the first client device;
cause a map interface (<NUM>) to be displayed on the first client device (<NUM>), the map interface including an avatar (<NUM>) of the first user at a location on the map display based on the location information and an icon (<NUM>) corresponding to an establishment; and
cause the icon (<NUM>) included in the map interface (<NUM>) to change to an enhanced icon (<NUM>) in response to determining that the establishment is saved in a database associated with a second user with whom the first user has an association in the messaging server system.