Location privacy management on map-based social media platforms

BACKGROUND

0001Social media applications implement computer-mediated technologies allowing for the creating and sharing of content that communicates information, ideas, career interests, and other forms of expression via virtual communities and networks. Social media platforms use web-based technologies, desktop computers, and mobile technologies (e.g., smart phones and tablet computers) to create highly interactive platforms through which individuals, communities, and organizations can share, co-create, discuss, and modify user-generated content or pre-made content posted online.

0002Mobile electronic devices on which end-user social media applications can be executed typically provide geolocation services that determine the geographic location of the mobile electronic device, by extension indicating the geographic location of the associated user. Social media content posted by users is often geo-tagged based on the geolocation of a mobile electronic device (such as a mobile phone) by use of which the social media content is captured and/or posted to the social media platform. In other embodiments, social media content may explicitly be geo-tagged by a user using a computer device that does not have activated geolocation services and/or that is not a mobile device (such as a desktop PC).

0003In many social media platforms, the total number of individual social media items that are available for viewing by any particular user can be very large. Search mechanisms that enable users to locate social media content that may be of interest to them can consume significant server-side resources and often provide less than satisfactory search results.

0004Examples of conventional social media platforms are described in <patcit id="pcit0001" dnum="US2014199970A1"><text>US2014/199970A1</text></patcit>, <patcit id="pcit0002" dnum="US20110238762A1"><text>US20110238762A1</text></patcit>, <patcit id="pcit0003" dnum="US20130129084A1"><text>US20130129084A1</text></patcit> and <patcit id="pcit0004" dnum="US8655389B1"><text>US8655389B1</text></patcit>.

SUMMARY

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

BRIEF DESCRIPTION OF THE DRAWINGS

0006Some aspects of the disclosure are illustrated in the appended drawings. Note that the appended drawings illustrate example embodiments of the present disclosure and cannot be considered as limiting the scope of the disclosure. <ul id="ul0001" list-style="none" compact="compact"><li><figref idref="f0001">FIG. 1</figref> is a block diagram showing an example social media platform system for exchanging, posting, and consuming social media data (e.g., messages and associated content) over a network.</li><li><figref idref="f0002">FIG. 2</figref> is a block diagram illustrating further details regarding a social media platform system, according to example embodiments.</li><li><figref idref="f0003">FIG. 3</figref> is a schematic diagram illustrating data which may be stored in a database of the social media platform system, according to certain example embodiments.</li><li><figref idref="f0004">FIG. 4</figref> is a schematic diagram illustrating a structure of a message, according to some embodiments, generated by a social media client application according to example embodiments.</li><li><figref idref="f0005">FIG. 5</figref> is a schematic diagram illustrating an example access-limiting process, in terms of which access to content (e.g., an ephemeral message, and associated multimedia payload of data) or a content collection (e.g., an ephemeral message gallery or story) may be time-limited (e.g., made ephemeral).</li><li><figref idref="f0006">FIGS. 6A</figref> and <figref idref="f0007">6B</figref> are respective schematic views of a client device providing a map-based graphical user interface for a social media application, according to different respective example embodiments.</li><li><figref idref="f0008 f0009">FIGS. 7A-7C</figref> are respective schematic views of a client device providing a destination selection interface forming part of a map-based graphical user interface for a social media application, according to some example embodiments.</li><li><figref idref="f0010">FIGS. 8A-8C</figref> are respective screenshots of a map-based graphical user interface, providing features relating to display of user icons in a map forming part of the interface, according to an example embodiment.</li><li><figref idref="f0012">FIGS. 9A and 9B</figref> are respective screenshots of the functionalities of a map-based graphical user interface that provides access to a chat interface and to friend content via a friend icon displayed as part of the map, according to an example embodiment.</li><li><figref idref="f0013 f0014 f0015">FIG. 10A-10D</figref> are a series of screenshots of search interfaces provided as part of a map-based graphical user interface, according to respective example embodiments.</li><li><figref idref="f0016 f0017">FIGS. 11A-11B</figref> are a series of schematic screenshots illustrating a location-based search mechanism provided by a map-based graphical user interface, according to one example embodiment.</li><li><figref idref="f0018">FIG. 12</figref> is a schematic view of a social media platform system for providing a map-based graphical user interface for a social media application, according to one example embodiment.</li><li><figref idref="f0019 f0020">FIGS. 13A-13B</figref> show respective flow charts illustrating an example embodiment of a method of providing a map-based graphical user interface for a social media application that includes an activity heat map, according to an example embodiment.</li><li><figref idref="f0021">FIG. 14</figref> shows a flowchart illustrating a method of representing a method of representing location-based user activity in a map-based graphical user interface, according to an example embodiment.</li><li><figref idref="f0022">FIG. 15</figref> shows a high-level flowchart illustrating a method of identifying geo-spatially anomalous social media activity, and consequent surfacing of content in a map-based graphical user interface, according to an example embodiment.</li><li><figref idref="f0023">FIG. 16</figref> is a flowchart illustrating a method of identifying anomalous activity on a social media platform based on construction of a historical model, according to an example embodiment.</li><li><figref idref="f0024">FIG. 17</figref> is a flowchart illustrating a method of extracting clusters of unusual social media activity based on calculation of geographically distributed anomality metrics for a target area, according to an example embodiment.</li><li><figref idref="f0025">FIGS. 18A</figref> and <figref idref="f0026">18B</figref> are map views illustrating an estimated density distribution calculated based on a set of social media items, according to an example embodiment.</li><li><figref idref="f0027">FIG. 19</figref> is a flowchart illustrating a method of providing a map-based graphical user interface in which collection icons have visual attributes that are variable based on an underlying social media activity metric, according to an example embodiment.</li><li><figref idref="f0028">FIG. 20</figref> is a block diagram illustrating a representative software architecture, which may be used in conjunction with various hardware architectures herein described.</li><li><figref idref="f0029">FIG. 21</figref> is a block diagram illustrating components of a machine, according to some example 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.</li></ul>

0007The headings provided herein are merely for convenience and do not necessarily affect the scope or meaning of the terms used.

DESCRIPTION

0008One aspect of the disclosure provides a geographical map-based graphical user interface (GUI) for a social media platform or application, to allow user access via the map-based GUI to ephemeral social media content. Such an interface is also referred to herein as a "map GUI."

0009As will be described in greater detail below, ephemeral social media content comprises social media items that are available for viewing via the social media application for only a limited period. For example, an ephemeral social media item or message (also referred to herein as a "snap") submitted by a user to the social media application may be available for viewing by other users via the map GUI of the social media application for only a predefined period subsequent to submission. In one example embodiment, each ephemeral item or snap has an availability lifetime (also referred to herein as a "gallery participation timer") of 24 hours after submission, after which the ephemeral item "disappears" and is no longer available for viewing by other users via the map GUI. Such ephemeral social media items (also referred to herein as ephemeral messages) typically comprise photographic or video content, which may be submitted with or without augmentations made by the user to the underlying photogtaphic or video content.

0010Ephemeral messages submitted by multiple different users may be available on a map forming part of the map GUI based at least in part on respective location information (e.g., geotag information) of the ephemeral messages. In some embodiments, the map GUI may provide location-based access to one or more collections of ephemeral social media items (also known as and referred to herein as galleries or "stories"). In some example embodiments, a plurality of ephemeral messages submitted by different users are included in a common geo-anchored gallery or story based at least in part on respective gcotaggmg information of the plurality of ephemeral messages. Such a location-based gallery or story is in some embodiments represented on the map GUI by a respective gallery icon displayed at a corresponding map location, the gallery icon being selectable by the user to trigger automated sequential display of the plurality of ephemeral messages in the gallery on the user device on which the map GUI is rendered.

0011In some embodiments, such a map GUI includes representations (e.g. by means of friend icons or bitmojis) of at least approximate respective positions of a user's friends in a social network graph accessed by the social media application, with the social media application enabling the user to explore the world around friends' locations by use of the GUI. Thus, the map GUI can in some embodiments enable the user to explore uploaded social media content (e.g., individual photos or video clips/snaps, or social media galleries such as stories comprising respective collections of photos, messages, or snaps).

0012These and additional aspects of the disclosure will be described below with reference to specific example embodiments. First, platform architecture and a technical background to implementation of the various embodiments will be described with reference to <figref idref="f0001 f0002 f0003 f0004 f0005">FIGS. 1-5</figref>. Thereafter, specific example embodiments are described with reference to <figref idref="f0006 f0007 f0008 f0009 f0010 f0011 f0012 f0013 f0014 f0015 f0016 f0017 f0018 f0019 f0020 f0021 f0022 f0023 f0024 f0025 f0026 f0027">FIGS. 6A-19</figref>. <figref idref="f0028 f0029">FIGS. 20-21</figref> finally describe aspects of software and hardware components that are in some instances used in the implementation of the described example embodiments.

DETAILED DESCRIPTION

0013The description that follows includes systems, methods, devices, 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 disclosed 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.

System Architecture and Operating Environment

0014<figref idref="f0001">FIG. 1</figref> is a block diagram showing an example social media platform system 100 for exchanging data (e.g., social media items or messages and associated content) over a network. In this description, items communicated from one user to one or more other users via a social media application or platform, as well as items uploaded or provided by users to a social media application or platform for availability to or consumption by other users via the social media application or platform, are referred to as "messages." Thus, the term "messages" as used herein is not limited to communications from one user to specified recipient users, but includes messages made available for public consumption via the relevant social media platform.

0015The social media platform system 100 includes multiple client devices 102, each of which hosts a number of applications including a social media client application 104. Each social media client application 104 is communicatively coupled to other instances of the social media client application 104 and a social media application server system 108 via a network 106 (e.g., the Internet).

0016Accordingly, each social media client application 104 is able to communicate and exchange data with another social media client application 104 and with the social media application server system 108 via the network 106. The data exchanged between social media client applications 104, and between a social media client application 104 and the social media application 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).

0017The social media application server system 108 provides server-side functionality via the network 106 to a particular social media client application 104. While certain functions of the social media platform system 100 are described herein as being performed by either a social media client application 104 or by the social media application server system 108, it will be appreciated that the location of certain functionality either within the social media client application 104 or the social media application server system 108 is a design choice. For example, it may be technically expedient to initially deploy certain technology and functionality within the social media application server system 108, but to later migrate this technology and functionality to the social media client application 104 where a client device 102 has a sufficient processing capacity.

0018The social media application server system 108 supports various services and operations that are provided to the social media client application 104. Such operations include transmitting data to, receiving data from, and processing data generated by the social media client application 104. This data may include message content, client device information, geolocation information, media annotations and overlays, message content persistence conditions, social network information, and live event information, as examples. Data exchanges within the social media platform system 100 are invoked and controlled through functions available via user interfaces (UIs) of the social media client application 104.

0019Turning now specifically to the social media application server system 108, an application programming 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.

0020Dealing specifically with the 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 API server 110 provides a set of interfaces (e.g., routines and protocols) that can be called or queried by the social media client application 104 in order to invoke functionality of the application server 112. The 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 social media client application 104 to another social media client application 104; the sending of media files (e.g., images or video) from a social media client application 104 to a social media server application 1 14, for possible access by another social media client application 104; the setting of a collection of media data (e.g., a story or gallery); the retrieval of such collections; the retrieval of a list of friends of a user of a client device 102; the retrieval of messages and content; the adding and deletion of friends to and from a social graph; the location of friends within a social graph; opening an application event (e.g., relating to the social media client application 104); and so forth.

0021The application server 112 hosts a number of applications and subsystems, including the social media server application 114, an image processing system 116, and a social network system 122. The social media 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) included in messages received from multiple instances of the social media 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 social media server application 114, to the social media client application 104. Other processor- and memory-intensive processing of data may also be performed server-side by the social media server application 114, in view of the hardware requirements for such processing.

0022The application server 112 also includes the image processing system 116, which is dedicated to performing various image processing operations, typically with respect to images or video received within the payload of a message at the social media server application 114.

0023The social network system 122 supports various social networking functions and services, and makes these functions and services available to the social media server application 114. To this end, the social network system 122 maintains and accesses an entity graph 304 (described below with reference to <figref idref="f0003">FIG. 3</figref>) within the database 120. Examples of functions and services supported by the social network system 122 include the identification of other users of the social media platform system 100 with whom a particular user has relationships or whom the particular user is "following," and also the identification of other attributes and interests of a particular user. In some embodiments, the social, network system 122 includes an identification of other users whose location is available for viewing by a particular user via a map-based GUI displayable on a client device 102 using the corresponding social media client application 104.

0024<figref idref="f0002">FIG. 2</figref> is a block diagram illustrating further details regarding the social media platform system 100, according to example embodiments. Specifically, the social media platform system 100 is shown to comprise the social media 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.

0025The ephemeral timer system 202 is responsible for enforcing the temporary access to content permitted by the social media client application 104 and the social media 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/gallery of messages (e.g., a SNAPCHAT story), selectively display and enable access to messages and associated content via the social media client application 104. Further details regarding the operation of the ephemeral timer system 202 are provided below.

0026The 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, or until expiry of a last message or snap in the gallery. 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 social media client application 104. As will be described in greater detail with reference to the specific example embodiments that follow, the collection management system 204 may also be responsible for compiling and managing multiple location-based social media galleries based at least in part on geo-tag data of social media items or messages uploaded to the social media platform by multiple users. Other types of galleries that may be provided by the collection management system 204 include a "place story" that collects ephemeral messages having geotag data indicating a location within a predefined associated geographical area; and an ad-hoc story or spike story that is dynamically surfaced on a map GUI as described herein based on underlying location-based social media activity, e.g., based on geo-temporal volume or anomality/unusualness of social media items submitted by users for public consumption (e.g., for inclusion in a "Live Story" or "Our Story"). With "anomality" is meant is metric indicating a how anomalous something is.

0027The collection management system 204 furthermore includes a curation interface 208 that allows a human operator (e.g., 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., to delete inappropriate content or redundant messages). Instead, or in addition, the collection management system 204 may employ machine vision (or image recognition technology), geotag data, and/or content rules to automatically compile and/or 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.

0028The annotation system 206 provides various functions that enable a user to annotate or otherwise augment, 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 social media platform system 100. The annotation system 206 operatively supplies a media overlay (e.g., a SNAPCHAT filter) to the social media 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 social media 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 includes text that can be overlaid on top of a photograph 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.

0029In one example 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.

0030In another example 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

0031<figref idref="f0003">FIG. 3</figref> is a schematic diagram illustrating data 300 which may be stored in the database 120 of the social media application server system 108, according to certain example 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).

0032The database 120 includes message data stored within a message table 314. An 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 social media application 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).

0033The 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,

0034The database 120 also stores annotation data, including 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 various types, including user-selected filters from a gallery of filters presented to a sending user by the social media client application 104 when the sending user is composing a message. Other types of filters 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 social media client application 104, based on geolocation information determined by a Global Positioning System (UPS) unit of the client device 102. Another type of filter is a data filter, which may be selectively presented to a sending user by the social media client application 104, based on other inputs or information gathered by the client device 102 during the message creation process. Examples of data filters include a current temperature at a specific location, a current speed at which a sending user is traveling, a battery life for a client device 102, or the current time.

0035Other 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.

0036Yet further annotation data that may be stored within the annotation table 312 is user-generated annotations or augmentations provided by the user to overlay an underlying photographic image or video. Such augmentations/annotations can include, for example, text annotations and drawing annotations or augmentations provided by the user, e.g., via a client device touchscreen.

0037As 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 stutes image data associated with messages for which message data is stored in the message table 314. 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.

0038A story table 306 stores data regarding collections of messages and associated image, video, or audio data, which are compiled into a collection (e.g., a SNAPCHAT story or a gallery). The creation of a particular collection may be initiated by a particular user (e.g., any user for whom 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 social media 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. In the context of this description, such messages and stories/galleries are understood to be for private consumption, being limited for viewing via the social media application to particular users identified by the submitting user or to users who are members of a social network of the submitting user. This is to be contrasted with social media items provided for public or non-private consumption via the social media application, not being limited to a user-specific or user-specified subset of all users of the social media application. An example of a publicly viewable collection or gallery is a "Live Story" or "Our Story."

0039As mentioned, 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 various locations and events. Users whose client devices have location services enabled and are at a common event location at a particular time may, for example, be presented with an option, via a user interface of the social media client application 104, to contribute content to a particular Live Story. The Live Story may be identified to the user by the social media client application 104, based on his or her location. The end result is a "Live Story" told from a community perspective. In accordance with some example embodiments of this disclosure, a submitting user can submit social media items or messages to a non-specific common Live Story. Such content is accessible to other users via a map-based graphical user interface, with such social media items or messages being accessible via the map GUI based on a respective location indicated by corresponding geo-tag data, either by forming part of a location-based gallery or story, or by such other users using location-based search mechanisms forming part of the map GUI.

0040A 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). In some embodiments of this disclosure, a message uploaded to a Live Story or Our Story generally, without the user specifying a particular location story in which the message is to be included, can automatically or semiautomatically be included in a location story based at least in part on geo-tag data of the message.

0041A map tile table 320 stores multiple map tiles that can be used for presenting a map in a map viewport of a map-based GUI, according to some embodiments of this disclosure. In a particular example embodiment, each map view is composed of 9 or 16 map tiles stitched together. A plurality of sets of map tiles may be maintained for different map zoom levels. In some example embodiments, a superset of map tiles is maintained server-side, being forwarded to a requesting client device 102 for composing a map representation of specific requested areas.

0042A user location table 326 stores current or most recent user location data for multiple users of the social media application. The user location data may be based on location data received from respective client devices 102 associated with the respective users. Such user location data is in some example embodiments used to display in a map-based GUI respective locations of a plurality of users who form part of the social network of the requesting user and/or who have provided permission for the requesting user to view their locations. Each such user may be represented on a map forming part of the map GUI by a respective user icon or bitmoji.

0043<figref idref="f0004">FIG. 4</figref> is a schematic diagram illustrating a structure of a social media item or message 400, according to some embodiments, generated by one instance of the social media client application 104 for communication to a further instance of the social media client application 104 or to the social media server application 114. The content of a particular message 400 is used to populate the message table 314 stored within the database 120, accessible by the social media server application 114. Similarly, the content of a message 400 is stored in memory as "in-transit" or "in-flight" data of the client device 102 or the application server 112. The message 400 is shown to include the following components: <ul id="ul0002" list-style="none" compact="compact"><li>A message identifier 402: a unique identifier that identifies the message 400.</li><li>A message text payload 404: text, to be generated by a user via a user interface of the client device 102 and that is included in the message 400.</li><li>A message image payload 406: image data, captured by a camera component of a client device 102 or retrieved from memory of a client device 102, and that is included in the message 400.</li><li>A message video payload 408: video data, captured by a camera component or retrieved from a memory component of the client device 102 and that is included in the message 400.</li><li>A message audio payload 410: audio data, captured by a microphone or retrieved from the memory component of the client device 102, and that is included in the message 400.</li><li>A message annotation 412: annotation data (e.g., filters, stickers, or other enhancements) that represents annotations to be applied to the message image payload 406, message video payload 408, or message audio payload 410 of the message 400.</li><li>A display duration parameter 414: a parameter value indicating, in seconds, the amount of time for which content of the message (e.g., the message image payload 406, message video payload 408, and message audio payload 410) is to be presented or made accessible to a user via the social media client application 104. The display duration parameter 414 is also referred to herein as a "display duration timer."</li><li>A message geolocation parameter 416: geolocation data or geo-tag data (e.g., latitudinal and longitudinal coordinates) associated with the content payload of the message 400. Multiple message geolocation parameter 416 values may be included in the payload, each of these parameter values being associated with respective content items included in the content (e.g., a specific image within the message image payload 406, or a specific video in the message video payload 408).</li><li>A message story identifier 418: identifier values identifying one or more content collections (e.g., "stories") with which a particular content item in the message image payload 406 of the message 400 is associated. For example, multiple images within the message image payload 406 may each be associated with multiple content collections using identifier values. An example of such a message story identifier 418 can in some embodiments comprise one or more thumbnail images.</li><li>A message tag 420: each message 400 may be tagged with multiple tags, each of which is indicative of the subject matter of content included in the message payload. For example, where a particular image included in the message image payload 406 depicts an animal (e.g., a lion), a tag value may be included within the message tag 420 that is indicative of the relevant animal. Tag values may be generated manually, based on user input, or may be automatically generated using, for example, image recognition.</li><li>A message sender identifier 422: an identifier (e.g., a messaging system identifier, email address, or device identifier) indicative of a user of the client device 102 on which the message 400 was generated and from which the message 400 was sent.</li><li>A message receiver identifier 424: an identifier (e.g., a messaging system identifier, email address, or device identifier) indicative of a user of the client device 102 to which the message 400 is addressed.</li></ul>

0044The contents (e.g., values) of the various components of the message 400 may be pointers to locations in tables within which content data values are stored. For example, an image value in the message image payload 406 may be a pointer to (or address of) a location within an image table 308. Similarly, values within the message video payload 408 may point to data stored within a video table 310, values stored within the message annotation 412 may point to data stored in an annotation table 312, values stored within the message story identifier 418 may point to data stored in a story table 306, and values stored within the message sender identifier 422 and the message receiver identifier 424 may point to user records stored within an entity table 302.

0045<figref idref="f0005">FIG. 5</figref> is a schematic diagram illustrating an access-limiting process 500, in terms of which access to content (e.g., an ephemeral message 502, and associated multimedia payload of data) or a content collection (e.g., an ephemeral message story 504) may be time-limited (e.g., made ephemeral).

0046An ephemeral message 502 is shown to be associated with a display duration parameter 506, the value of which determines an amount of time that the ephemeral message 502 will be displayed to a receiving user of the ephemeral message 502 by the social media client application 104. In one embodiment, where the social media client application 104 is a SNAPCHAT client application, an ephemeral message 502 is viewable by a receiving user for up to a maximum of 10 seconds, depending on the amount of time that the sending user specifies using the display duration parameter 506. In some embodiments, the system automatically attaches a default display duration parameter 506 to photographic or still-image messages, e.g., having a default display duration of 5 seconds. The display duration parameter 506 of video-based messages may automatically correspond to the duration of the underlying video, with an automatically enforced upper limit. Thus, in an example embodiment in which an upper limit of 10 seconds is enforced, a 7-second video message will have a display duration parameter of 7 seconds.

0047The display duration parameter 506 and the message receiver identifier 424 are shown to be inputs to a message timer 512, which is responsible for determining the amount of time that the ephemeral message 502 is shown to a particular receiving user identified by the message receiver identifier 424. In particular, the ephemeral message 502 will only be shown to the relevant receiving user for a time period determined by the value of the display duration parameter 506. The message timer 512 is shown to provide output to a more generalized ephemeral timer system 202, which is responsible for the overall timing of display of content (e.g., an ephemeral message 502) to a receiving user.

0048The ephemeral message 502 is shown in <figref idref="f0005">FIG. 5</figref> to be included within a social media gallery in the form of an ephemeral message story 504 (e.g., a personal SNAPCHAT story, or an event stuiy). The ephemeral message story 504 has a story duration parameter 508, a value of which determines a time duration for which the ephemeral message story 504 is made available and is accessible to users of the social media platform system 100. The story duration parameter 508, for example, may be the duration of a music concert, where the ephemeral message story 504 is a collection of content pertaining to that concert. Alternatively, a user (either the owning user or a curator user) may specify the value for the story duration parameter 508 when performing the setup and creation of the ephemeral message story 504. In some embodiments, the story duration parameter 508 is determined based at least in part on respective story participation parameters 510 (or lifetimes) of one or more of the ephemeral messages 502 forming part of the particular ephemeral message story 504. In one example embodiment, the story duration parameter 508 corresponds to a story participation parameter 510 or lifetime of a last-posted one of the ephemeral messages 502 in the relevant ephemeral message story 504. In such a case, the ephemeral message story 504 expires (e.g., by becoming unavailable for viewing via the social media platform) when the last-posted ephemeral message 502 therein expires (e.g., when a story participation parameter 510 or lifetime of the last ephemeral message 502 expires).

0049As alluded to above, each ephemeral message 502 within the ephemeral message story 504 has an associated story participation parameter 510 (also referred to herein as a "gallery participation parameter" or a "gallery participation timer"), a value of which determines the duration of time for which the ephemeral message 502 will be accessible within the context of the ephemeral message story 504. Accordingly, a particular ephemeral message 502 may "expire" and become inaccessible within the context of the ephemeral message story 504, prior to the ephemeral message story 504 itself expiring in terms of the story duration parameter 508. The story duration parameter 508, story participation parameter 510, and message receiver identifier 424 each provide input to a story timer 514, which operationally determines, first, whether a particular ephemeral message 502 of the ephemeral message story 504 will be displayed to a particular receiving user, and, if so, for how long. Note that the ephemeral message story 504 is also aware of the identity of the particular receiving user as a result of the message receiver identifier 424.

0050Accordingly, the story timer 514 in some embodiments operationally controls the overall lifespan of an associated ephemeral message story 504, as well as an individual ephemeral message 502 included in the ephemeral message story 504. In one embodiment, each and every ephemeral message 502 within the ephemeral message story 504 remains viewable and accessible for a time period specified by the story duration parameter 508. In a further embodiment, a certain ephemeral message 502 may expire, within the context of the ephemeral message story 504, based on a story participation parameter 510. Note that a respective display duration parameter 506 may still determine the duration of time for which a particular ephemeral message 502 is displayed to a receiving user upon replay of the ephemeral message 502, even within the context of the ephemeral message story 504. Accordingly, the display duration parameter 506 determines the duration of time that a particular ephemeral message 502 is displayed to a receiving user, regardless of whether the receiving user is viewing that ephemeral message 502 inside or outside the context of an ephemeral message story 504.

0051The ephemeral timer system 202 may furthermore operationally remove a particular ephemeral message 502 from the ephemeral message story 504 based on a determination that it has exceeded an associated story participation parameter 510. For example, when a sending user has established a story participation parameter 510 of 24 hours from posting, the ephemeral timer system 202 will remove the relevant ephemeral message 502 from the ephemeral message story 504 after the specified 24 hours. The ephemeral timer system 202 also operates to remove an ephemeral message story 504 either when the story participation parameter 510 for each and every ephemeral message 502 within the ephemeral message story 504 has expired, or when the ephemeral message story 504 itself has expired in terms of the story duration parameter 508. Note that in this disclosure, at least some ephemeral messages 502 may be submitted by the user to the social media application for general or public viewing via the map-based GUI, without being included by the user in any particular event gallery and without being included in any location-based gallery represented by a respective gallery icon on the map GUI. Such ephemeral messages 502 in some embodiments also have respective story participation parameters 510 specifying time periods for which the ephemeral messages 502 are accessible via the map GUI as part of a collective Live Story or Our Story, as described with reference to specific example embodiments below. In a particular example embodiment, each ephemeral message 502 thus submitted for public or non-private view has a default gallery participation parameter or story participation parameter 510 of 24 hours. Such ephemeral messages 502 are thus viewable via the map GUI for only 24 hours after submission.

0052In certain use cases, a creator of a particular ephemeral message story 504 may specify an indefinite story duration parameter 508. In this case, the expiration of the story participation parameter 510 for the last remaining ephemeral message 502 within the ephemeral message story 504 will determine when the ephemeral message story 504 itself expires. In this case, a new ephemeral message 502, added to the ephemeral message story 504, with a new story participation parameter 510, effectively extends the life of an ephemeral message story 504 to equal the value of the story participation parameter 510.

0053In response to the ephemeral timer system 202 determining that an ephemeral message story 504 has expired (e.g., is no longer accessible), the ephemeral timer system 202 communicates with the social media platform system 100 (and, for example, specifically the social media client application 104) to cause an indicium (e.g., an icon) associated with the relevant ephemeral message story 504 to no longer be displayed within a user interface of the social media client application 104. Similarly, when the ephemeral timer system 202 determines that the story participation parameter 510 for a particular ephemeral message 502 has expired, the ephemeral timer system 202 causes the social media client application 104 to no longer display an indicium (e.g., an icon or textual identification) associated with the ephemeral message 502.

<u>Example Embodiments of Map GUI Functionality</u>

0054First, various aspects and features of the disclosure will be described conceptually with respect to specific example embodiments discussed with reference to and illustrated in <figref idref="f0006 f0007 f0008 f0009 f0010 f0011 f0012 f0013 f0014 f0015 f0016 f0017">FIGS. 6A-11B</figref>.

<u>Ba</u>sic Map <u>GUI Architecture</u>

0055<figref idref="f0006">FIG. 6A</figref> shows an example embodiment of a map-based graphical user interface, further referred to as a map GUI 612, displayed on a client device 102 in the example form of a mobile phone. In this example embodiment, the map GUI 612 is generated on a display in the form of a touchscreen 606 capable of receiving haptic input. The map GUI 612 includes an interactive map 618 showing a stylized aerial or satellite representation of a particular geographical area. The map 618 is displayed within a map viewport 621 which, in this example embodiment, uses the full available area of the touchscreen 606. In other example embodiments, the map viewport 621 may be a bounded panel or window within a larger display screen. The map GUI 612 further comprises a plurality of user-selectable graphical user interface elements displayed at specific respective geographic locations on the map 618. Each such geo-anchored GUI element is in this example embodiment represented by a respective indicium or icon overlaid on the map 618. The different types of icons and their respective functionalities will be described in greater detail below. As will also be described briefly, the map GUI 612 may further include one or more informational overlays rendered over the underlying geographical map 618, in this example embodiment including a heatmap 625 representative of the geographical distribution of underlying social media activity on the social media platform provided by the relevant social media application.

0056As mentioned, the map GUI 612 includes a number of different user-selectable icons or UI elements that indicate different geographically based content or information. In this example embodiment, the map GUI 612 includes a plurality of different gallery icons, also referred to in this description as "story icons." Each story icon corresponds in location on the map 618 to a respective location-based social media gallery or collection, in this example embodiment corresponding to a location-based story of ephemeral messages in the example form of so-called "snaps," as discussed elsewhere herein. Each of these stories that are represented by respective story icons on the map 618 consists of a respective set of snaps (respectively comprising augmented or unaugmented photographic or video content) that are grouped together based at least in part on respective geo-tag data associated with respective snaps.

0057In the example embodiment of <figref idref="f0006">FIG. 6A</figref>, the map GUI 612 includes two different types of gallery icons for two different respective types of location-based social media galleries, namely place icons 631 for place galleries/stories, and spike icons 633 for spike galleries/stories that are dynamically surfaced on the map GUI 612 based on one or more metrics of underlying social media activity relating to the submission of social media ilems/snaps to the social media platform with geo-tag data indicating the respectively associated geographical areas. Note that these different types of galleries are represented by different types of icons 631, 633. The differences between these different types of galleries and the corresponding visually distinct gallery icons 631, 633 are discussed later herein. The map GUI 612 in this example embodiment further includes friend icons in the example form of bitmojis 640 that are displayed on the map GUI 612 based on the current or last known geographic location of respective friends of the user associated with the client device 102.

<i>Message and</i>/<i>or Story Ephemerality</i>

0058In this example embodiment, the social media items that are selectively playable by selection of the corresponding story icons 631, 633 in the map GUI 612 are ephemeral social media items or messages. As described previously, ephemeral content is social media content (e.g., augmented and/or unaugmented video clips, pictures, and/or other messages) that is available for viewing by social media users via the map GUI 612 for only a predetermined limited period, also referred to herein as a respective gallery participation parameter or timer. After expiry of a respective gallery participation parameter or timer for any ephemeral message or snap uploaded by a particular user, that ephemeral message or snap is no longer available for viewing by other users via the map GUI 612 generated on their respective client devices 102. Current examples of such ephemeral social media content include the respective snaps or messages included in so-called "stories" in the SNAPCHAT or the INSTAGRAM social media applications.

0059Instead of, or in addition to, management of ephemerality on a per-snap level using respective gallery participation timers, availability of the ephemeral messages by the map GUI 612 can in some instances be managed collectively, e.g., on a per-story level. In such instances, each story can have a respective story duration parameter 508 (e.g., being based on a corresponding story timer 514 see <figref idref="f0005">FIG. 5</figref>), at the expiry of which availability of the corresponding story for viewing via the map GUI 612 is terminated. In some embodiments, the story duration parameter 508 is calculated based on the story participation parameter 510 of one of the ephemeral messages included in the relevant story. For example, a story may in some embodiments expire when a last uploaded item within the story expires, in response to which the corresponding story icon 631, 633 is no longer displayed on the map GUI 612. In one example embodiment, the map GUI 612 may include one or more event icons (e.g., similar in appearance to the place icons 631 of <figref idref="f0006">FIG. 6A</figref>) corresponding to respective event stories, with the story duration parameter 508 of the event story being set to expire a predetermined period of time from the start or conclusion of the underlying event. At expiry of the story duration parameter 508, the corresponding gallery icon 631, 633 is removed from the map GUI 612, irrespective of individual timers associated with respective snaps included in the event story.

<u>Story Playback</u>

0060The user can select any one of the gallery icons 631, 633 by haptic contact with the touchscreen 606 at the on-screen location of the selected gallery icon 631/633. In response to such selection, automated sequential playback of the corresponding set of ephemeral messages or snaps in the selected story is performed by the client device 102 on the touchscreen 606. Such automated sequential playback of the selected story consists of : <ul id="ul0003" list-style="dash"><li>displaying on the touchscreen 606 the content or media payload of a first one of the ephemeral messages for a corresponding display duration (e.g., a default value of five seconds for photo-based messages and a maximum value of 10 seconds for video-based snaps), in this example embodiment temporarily replacing the map GUI 612 on the touchscreen 606 with a full-screen replay of the relevant snap;</li><li>at expiry of the display duration, displaying the content of the next snap/message for its display duration; and</li><li>thus progressing in sequence through all of the ephemeral messages in the selected story until all of the snaps in the story have been replayed or until the user selectively dismisses the playback sequence.</li></ul>

0061In some embodiments, not all of the snaps in a particular story/gallery are necessarily included in the replay sequence. For example, if there are many overlapping snaps (e.g., snaps showing substantially identical content), some of those snaps are automatically skipped to keep a continuous narrative and not repeat some sections of an event commonly captured by the different snaps. Instead, or in addition, the social media server application 114 can in some embodiments be programmed automatically to identify and curate overlapping or contemporaneous snaps based on timestamp information associated with respective snaps.

0062In this example embodiment, the snaps automatically collected together in a replayable spike story or place story are arranged automatically to be played back in chronological order based on respective timestamps (e.g., being played in sequence from oldest to newest or earliest posted to most recently posted). A benefit of such chronological playback is that viewing of the story provides a user with sequentially arranged views of events transpiring at the relevant location. In some instances, however, a human curator may choose to rearrange snaps out of chronological order, for example to improve the narrative flow of the story. In other embodiments, the snaps may be played in reverse chronological order, from newest to oldest.

0063It can thus be seen that the example map GUI 612 includes multiple location-based gallery icons in the example form of story icons 631, 633 that are user-selectable to trigger playback of respective collections of ephemeral social media items, in this example embodiment being respective ephemeral stories consisting of respective sets of ephemeral messages (also referred to in this description as "snaps"). In this example embodiment, each of the plurality of location-based stories represented by the respective story icons 631, 633 may comprise media content contributed by multiple different users.

<u>Our Story and Publication of Ephemeral Messages to Our Story</u>

0064The respective ephemeral stories are in this example embodiment compiled from ephemeral messages submitted by multiple users based at least in part on geo-tagging of the respective snaps. Note that the ephemeral messages made available for viewing via the map GUI 612 are in this example embodiment not limited to content provided by other users who are members of an in application social network uf the user on whose client device 102 the map GUI 612 is generated. Instead, the social media content to which the map GUI 612 allows access is in this example embodiment provided by snaps uploaded or submitted by any user to be publicly accessible via the map GUI 612.

0065One aspect of the example map GUI 612 provides for the functionality for users to submit social media content that is publicly viewable via the map GUI 612. Turning briefly to <figref idref="f0008">FIG. 7A</figref>, therein is shown an example embodiment of a destination selection interface 707 forming part of the map GUI 612 to provide a mechanism that gives the user a selectable option to make a snap publicly viewable via the map GUI 612 upon capturing of the snap.

0066In this example embodiment, snaps can be captured via the map GUI 612 while the map viewport 621 is displayed (as seen in <figref idref="f0006">FIG. 6A</figref>) by operation of a camera soft button 650 (<figref idref="f0006">FIG. 6A</figref>) forming part of the map GUI 612. After capturing of photo or video content by operation of the camera soft button 650, the captured media content is displayed on the touchscreen 606 (<figref idref="f0008">FIG. 7A</figref>) together with the destination selection interface 707. In this example embodiment, the user can select one or both destination options identified in <figref idref="f0008">FIG. 7A</figref> as "My Story" and "Our Story," represented in <figref idref="f0008">FIG. 7A</figref> by respective radio buttons 714, 721. By selecting the Our Story radio button 721 and thereafter selecting a "Send" soft button 728, the user can submit the snap over the network 106 to the application server 112 with an indication that the snap is available for non-private publication via the map GUI 612. If the snap is not so marked by the user, for example being associated with selection of the My Story radio button 714 only, then the snap is not available for inclusion in any of the stories associated with the story icons 631, 633 and is not available for inclusion in search results of a location-based search via the map GUI 612, as described later herein. Snaps included only in the My Story gallery are available only to friends of the user (e.g., members of the uploading user's social network). The My Story gallery is a per-user location-agnostic gallery of ephemeral messages available to friend users only, thus being a non-public or private gallery.

0067In other example embodiments described herein, the superset of ephemeral messages made available by multiple users for public viewing via the map GUI 612 is alternatively referred to as the "Live Story" or simply as a "Live" gallery. For the purposes of the description of example embodiments herein, "Live Story" and "Our Story" are thus to be read as being synonymous. In the present example embodiment, the compilation and/or surfacing of gallery icons 631, 633 and the rendering of the heatmap 625 are based exclusively on publicly available social media content provided by snaps uploaded to Our Story. Calculation of metrics or attributes of social media activity upon which one or more aspects of the map GUI 612 are based (e.g., an unusualness or anomality metric indicating geo-temporal unusualness or anomality of social media activity within respective geographical areas) is in this example embodiment likewise based exclusively on snaps uploaded to Our Story.

<u>Visual Distinctions between Story Icons for Different Story Types</u>

0068Returning now to the visual distinctions or differences between the different types of gallery icons 631, 633, it will be noted that each gallery icon 631/633 in this example embodiment comprises a circular graphical user interface element bearing a thumbnail image provided by the one of the snaps contained in the respective story. Each place icon 631, however, also includes an associated label 635 bearing a text indication of the associated place. In this example embodiment, the labels 635 indicate the respective places of the place stories surfaced in the geographic window presently displayed in the example map 618 as being the Rockefeller Center, Bryant Park, and the Empire State Building, respectively.

0069In other example embodiments, the visual distinctions between different types of story icons may be provided in a different manner. <figref idref="f0007">FIG. 6B</figref>, for example, shows another example embodiment of a map GUI 612 that is analogous to the example embodiment of <figref idref="f0006">FIG. 6A</figref>, a major difference being that the visual distinction between place icons 631 and spike icons 633 is provided at least in part by differently shaped thumbnail images. In the example of <figref idref="f0007">FIG. 6B</figref>, the thumbnails of the place icons 631 are rectangular, while the thumbnails of the spike icons 633 are circular.

0070The respective thumbnail images that are used for the spike icons 633 arc in the example embodiments of <figref idref="f0006">FIGS. 6A</figref> and <figref idref="f0007">6B</figref> automatically selected by the social media server application 114. In this instance, the thumbnail image for a spike icon 633 is automatically selected based on the posting time of the respective snaps forming part of the corresponding spike story, in this case being selected as a most recently posted snap in the relevant story. In other embodiments, automatic selection of the thumbnail image to be used in the spike icon 633 can be based on selecting the earliest-posted ephemeral message/snap that is still available for viewing as part of the spike story. The thumbnail images for the place icons 631 (or for icons associated with other curated stories, such as event stories) can in some embodiments likewise be selected automatically. In this embodiment, however, the thumbnail images for the place icons 631 can be selected from the snaps included in the corresponding story/gallery by a human operator via a content management interface forming part of the social media server application 114. Absent such an explicit designation of a particular snap to be used for the thumbnail image, thumbnail selection may revert to an automatic default selection as described previously.

<u>Differences between Different Story Types</u>

Place Stories

0071Returning to <figref idref="f0006">FIG. 6A</figref>, the differences between the different types of social media galleries or stories accessible via respective story icons 631, 633 on the map GUI 612 will now be briefly discussed.

0072Place stories, represented by respective place icons 631, are social media galleries for defined locations or places, typically being places that consistently have relatively large activity volumes (e.g., Times Square, Universal Studios, etc.). Note that, in this example embodiment, not all defined places are by default surfaced in the map GUI 612 by respective place icons 631. Instead, the geo-anchored place stories are surfaced based on the amount of activity (e.g., the raw number of uploaded snaps) captured within a defined geographical area associated with the relevant place, as indicated by associated geo-tag data. This ensures that places that regularly or always attract relatively large volumes of snaps are identified as such on the map 618.

0073Defined places for which place icons 631 may be surfaced in the map GUI 612 are in this example embodiment manually created by one or more human operators using a server-side gallery management system or content management system (CMS) 1224 provided by a server-side social media platform system 1200 (<figref idref="f0018">FIG. 12</figref>). In this example embodiment, each defined place has: <ol id="ol0001" compact="compact"><li>(a) an associated operator-defined polygon marking its geographical boundaries, that specify a particular geographical area for the place story;</li><li>(b) a thumbnail location or icon location, typically lying within the associated polygon, that specifies the on-map position at which the place icon 631 for a gallery or story associated with that place is displayed in the map 618; and</li><li>(c) a name by which the place is identified. In the example embodiment of <figref idref="f0006">FIG. 6A</figref>, this is the name that is displayed on the associated label 635 of the place icon 631.</li></ol> In other embodiments, such places and associated place stories are automatically identified by historical snap volume. In some such embodiments, the defined places and their associated stories/galleries are created and curated automatically by server-side procedures.

0074In some instances, each place story includes all of the snaps having geotag information indicating a geographic location lying within the associated polygon. Selection of a particular place icon 631 (e.g., by clicking in a desktop application or by tapping on the touchscreen 606 in the example embodiment of <figref idref="f0006">FIG. 6A</figref>) in such cases plays all the snaps from within the corresponding polygon. In this example embodiment, the CMS 1224 provides functionality to operators or administrators to curate the collection of snaps associated with any operator-selected defined place (e.g., a particular geographical area defined by the corresponding polygon). The operator or one or more automated procedures can thus, for example, delete individual snaps from the place story, or can select individual snaps for inclusion in the place story.

0075When snaps are played in response to selection of a place icon 631, the name of the place appears on-screen together with the replayed content or payload of the respective snaps. As mentioned, in this example embodiment, the snap represented by a corresponding thumbnail within the relevant place icon 631 is played first, then the rest in time order.

Spike Stories

0076The unlabeled circular spike icons 633 are automatically surfaced for geographical areas of unusually high activity, with the respective associated spike stories or ad hoc galleries including unexpired snaps within the associated geographical area. In the example embodiment of <figref idref="f0006">FIG. 6A</figref>, all ad hoc galleries associated with spike icons 633 are unmoderated, so that selecting a spike icon 633 triggers automated sequential replay of all of the snaps within a geographical area associated with the spike icon 633. In a particular example embodiment, the geographical area associated with the spike icon 633 includes all geographical points located within a predefined radius of the on-map location of the selected spike icon 633.

0077Thus, clicking or tapping on the spike icon 633 plays all the snaps in that cluster, showing the snap in the thumbnail first and then the rest of the snaps in time order. Note, again, that the snaps clustered under the common spike icon 633 are in this example uploaded by multiple different respective social media users to Our Story, and are uncurated by moderators. In other embodiments, the stories collected under such spike thumbnails may be curated.

0078Automated selection of spike icons 633 (and therefore of the associated social media gallery, collection, or story) for surfacing in the map GUI 612 is in this example embodiment based at least in part on calculation of respective anomality or unusualness metric values for different geographical areas. Thus, a higher level of unusualness or anomality of user activity in a particular geo-temporal space would in such instances increase the likelihood of a particular spike story being surfaced on the map GUI 612 by display of a corresponding spike icon 633. As mentioned, the anomality metric provides an indication of the level of geo-temporal unusualness or anomality of social media activity. Calculation of anomality metrics can in some embodiments comprise calculating a level or percentage of difference between historical activity levels in a given area, and activity levels in a current time window. It will be appreciated that heat map coloration and content surfacing increases with an increase in positive anomality levels (i.e., indicating unusually high social media activity). Also note that, in some embodiments, a social media activity metric upon which heat map generation and/or content surfacing is based on a combination of factors that include an anomality metric. In a particular example embodiment, the social media activity metric is provided by a combination of a raw activity metric and an anomality metric.

0079Instead, or in addition, human curators can, via the CMS 1224, also mark specific spike stories or clusters as "interesting," thereby boosting the unusualness or anomality score of the respective spike.

0080Note that, in the example embodiment described with reference to <figref idref="f0006">FIG. 6A</figref>, different social media activity attributes or metrics are used for surfacing of the place icons 631 and the spike icons 633 respectively. As discussed, spike icons 633 are in this example embodiment surfaced based on anomality metric values, while place icons 631 are surfaced based on raw snap volume. In other embodiments, surfacing of the place icons 631 may also be based at least in part on associated anomality values. Note that in some embodiments, various aspects of social media surfacing as described herein (including heatmap calculation and generation, story surfacing, etc.) are based on attributes other than anomality. For example, the heatmap 625 and story surfacing are in one embodiment based on raw activity levels. Therefore, discussion herein of aspects of the disclosure relating to informational overlays (such as the heatmap 625) and content surfacing based on the anomality metric is to be read as, in other embodiments, being performed based on a different social media activity value, such as raw snap numbers in a given time period, snap frequency, snap density, or the like.

Other Types of Stories or Ephemeral Social Media Galleries

0081Other embodiments can instead, or in addition, provide for social media gallery types different from the place stories and the spike stories described with reference to <figref idref="f0006">FIGS. 6A</figref> and <figref idref="f0007">6B</figref>. Each such different type of gallery may be represented on the map 618 by a visually distinct type of icon or other user interface element.

0082One example embodiment provides for event galleries pertaining to particular events occurring at a specific location. Such events can include, for example, concerts, festivals, sports events, or the like. These event galleries are in one embodiment created and curated server-side by human operators using the CMS 1224.

0083Some embodiments provide for surfacing on the map 618 story icons or thumbnails with respect to non-public snaps, e.g., snaps or stories that are access-restricted based at least in part on social network information. Fur example, individual stories uploaded by friend users may in some embodiments be represented on the map 618 by a respective icon or thumbnail. For example, the My Story of friend users may in some embodiments be directly accessible via the map 618. Such story icons are in some embodiments indicated by a respective friend icon or bitmoji 640 located on the map 618 corresponding to the location at which the corresponding story was generated. In other embodiments, each such user story icon may be indicated on the map GUI 612 by a circular thumbnail analogous to the previously described example story icons 631, 633.

<u>Snap Submission to User-Selected Location-Based Stories</u>

0084Another feature of the disclosure enables users to submit publicly viewable snaps designated for inclusion in any and all Live Stories or ephemeral galleries that might be happening at locations where the user is eligible to post, e.g., being geographically proximate to the current location of the user as indicated by the associated client device 102. In this manner, the user can specify snaps for inclusion in place stories, event stories, or other location-based ephemeral social media galleries as discussed above.

0085<figref idref="f0009">FIGS. 7B and 7C</figref> show an example embodiment of a destination selection interface 707 that provides a mechanism for such destination selection alternative to the example embodiment previously described with reference to <figref idref="f0008">FIG. 7A</figref>. The destination selection interface 707 of <figref idref="f0009">FIG. 7B</figref> is displayed on the client device 102 in response to the user initiating a snap submission flow, e.g., by capturing a snap.

0086The destination selection interface 707 of <figref idref="f0009">FIG. 7B</figref> is similar to that of the example embodiment of <figref idref="f0008">FIG. 7A</figref>, in that two different user-selectable user interface elements in the form of respective radio buttons 714, 721 are presented for posting a snap to a user-specific My Story (radio button 714) or to a publicly viewable Our Story (radio button 721). A distinction between the destination selection interface 707 of <figref idref="f0008">FIG. 7A</figref> and that of <figref idref="f0009">FIG. 7B</figref> is that the Our Story cell of <figref idref="f0009">FIG. 7B</figref> automatically expands upon selection of the radio button 721 to show subtitles of local place stories and/or event stories to which the snap could be submitted based on device location or the geo-tag of the associated snap.

0087<figref idref="f0009">FIG. 7C</figref> shows additional options presented as a result of selecting the Our Story radio button 721, which opens up a list showing the respective local stories for which the snap is eligible. In this example embodiment, all suboptions are selected by default via respective radio buttons 750. In other embodiments, separate selection of individual suboptions may be required. If the user chooses to submit the snap with all of the options selected, that snap is automatically associated with each of the selected suboptions as well as being made available for geographically based viewing as part of Our Story, separate from any curated location-based place or event gallery/story, as described above.

0088The user can deselect any particular suboptions by clicking or tapping on the corresponding default-selected radio button 750, as shown in <figref idref="f0009">FIG. 7C</figref>, in which the lowermost one of the suboptions has been deselected. If all suboptions are deselected, the snap is not posted to any curated location-based story, but is posted only to Our Story to be publicly viewable via the map GUI 612, as described elsewhere herein.

<u>Heatmap Considerations</u>

0089As shown in <figref idref="f0006">FIG. 6A</figref>, the social media application map GUI 612 in this example embodiment includes a heat map layer overlaid on the geographical map 618, thus providing the heatmap 625 that indicates geographical distribution of one or more attributes of user activity within the social media application. As discussed previously, the heatmap 625 indicates user activity levels with respect to posting geotagged content that is publicly viewable (e.g., Live Stories/Our Story). Instead, or in addition, the heatmap 625 can in some embodiments be based on snaps that are available for viewing by the particular user on whose client device 102 the map GUI 612 is displayed, in which case the heatmap 625 may differ from person to person depending on who gave the viewer permission to see their snaps.

0090In this example embodiment, the map 618 is color-coded, with warmer colors corresponding to higher levels of unusualness, as indicated by higher anomality metric values. Thus, in the map 618 illustrated in <figref idref="f0006">FIG. 6A</figref>, the red areas of the heatmap 625 indicate those geographical areas with snap clusters corresponding to the highest anomality metric values. Again, different metrics or attributes for generation of the heatmap 625 may be used in other embodiments, for example being based on snap density (e.g., raw snap volume per unit area of the map 618).

0091In some embodiments, the map GUI 612 displays information pertaining to the heatmap 625 differently at different magnification levels. For example, calculation of anomality metrics and consequent rendering of the heatmap 625 based thereon is in some embodiments performed separately for each of a plurality of zoom levels. In addition, different sets of spike icons 633 may be surfaced at different magnification levels. In one example embodiment, the heatmap 625 may be displayed at a first zoom level without individual spike icons 633 surfaced in the map GUI 612, while multiple gallery or story icons 631, 633 are automatically surfaced in response to user-controlled zooming in on a particular portion of the map 618 shown at the first zoom level.

<u>Anomality Metric Calculation</u>

0092Some features of the map GUI 612 in this example embodiment provide for calculating with respect to social media content an anomality metric that quantifies geospatial anomality or unusualness of the social media content, and for surfacing the social media content in the map GUI 612 based on respective values for the anomality metric. In this example embodiment, respective collections of snaps associated with different geographical locations are ranked based at least in part on corresponding anomality metric values, and a predetermined number of the collections are automatically selected based on their anomality rankings for surfacing on the map GUI 612 with respective spike icons 633. Instead, or in addition, all spike stories with a positive anomality metric value (i.e., reflecting anomalously high, not low, activity) higher than a predefined threshold value can automatically be surfaced by the display of a corresponding spike icon 633. As described elsewhere herein, the calculation and display of heatmap information is in some embodiments based at least in part on anomality metric calculation.

0093Anomality metrics may in some embodiments be calculated for individual social media items. In this example embodiment, however, anomality metrics are calculated for collective user behavior. In particular, anomality metrics are calculated for multiple snaps (in this example being respective geotagged social media submissions) based on a comparison between geo-temporal distribution of the multiple snaps and historic geo-temporal social media behavior in or around the relevant geographic location.

0094Note that the calculation of anomality metrics is in this example embodiment time sensitive. Thus, the same volume of snaps in a particular location may be identified as being anomalous at one time of the day but not at another time. For example, a certain level of social media activity (here, posting of snaps to Our Story) at the Empire State Building would be flagged as above-threshold anomalous at 4 AM, but would not be thus identified as anomalous during daytime.

0095An aspect of the disclosure provides for determining one or more geo-temporal attributes of social media activity by a process comprising, for each of multiple social media postings, representing the posting as having a distribution in time and/or in space. In some embodiments, representing respective postings as having a geo-temporal distribution comprises treating respective social media items as a probability cloud, for example having a Gaussian distribution. Instead, or in addition, the method may comprise generating or extrapolating a historical model or historical representation of social media activity based at least in part on a resampling procedure executed with respect to a multiplicity of historical geo-tagged social media items. In one example embodiment, the resampling procedure comprises a bootstrapping operation.

0096In some embodiments, the representation of social media postings as having respective distributions in time and/or space is performed as part of an operation to represent a geo-temporal reference profile or model for historical social media activity for a particular geographical area. Instead, or in addition, the representation of social media postings as having respective distributions in time and/or space may be performed as part of a procedure to represent recent or near-live social media activity in the particular geographical area. In such cases, the geo-temporal reference profile and the representation of the recent or near-live social media activity may be used in combination to identify within the geographical area one or more regions of interesting or anomalous social media activity, e.g., by calculating a geographical distribution of a quantified anomality metric based on differences between the geo-temporal reference profile and the corresponding representation of recent or near-live social media activity.

<u>Dynamic Variation of Icon Size</u>

0097Turning briefly to <figref idref="f0007">FIG. 6B</figref>, it will be seen that the map GUI 612 illustrated therein provides an example embodiment of an aspect of the disclosure that provides for automated variation in one or more visual attributes of user interface elements associated with respective social media content based at least in part on a quantified attribute of underlying social media activity. In particular, the example embodiment of <figref idref="f0007">FIG. 6B</figref> provides for dynamic variation in the on-screen size of respective spike icons 633 based on respective anomality metric values for the corresponding clusters or spike galleries. On-screen size of the respective spike icons 633 thus indicates a level of unusualness or anomality of the underlying social media activity. Worded differently, the size of a spike icon 633 represents how unusual it is for there to be the relevant amount of activity in that spot, with a larger spike icon 633 indicating a greater level of unusualness.

0098Instead, or in addition, a visual attribute (such as its on-screen size) of the place icons 631 may likewise be variable based on a corresponding anomality value. In the example embodiment of <figref idref="f0007">FIG. 6B</figref>, however, the on-screen size of the place icons 631 is variable based on snap volume, with a greater number of snaps included in any place story corresponding to a larger on-screen size of the associated place icon 631. Thus, it is intuitively intelligible from the example screenshot shown in <figref idref="f0007">FIG. 6B</figref> that the Universal Studios story has a greater number of snaps than the Venice Boardwalk story.

<u>Location Sharing and User Icons</u>

User Location Display

0099As mentioned previously, the map GUI 612 includes a graphical representation of associated locations of the user associated with the client device 102 and/or other users, each user being represented by a respective user icon or friend icon (for users who are members of an in-application social graph associated with the viewing user), in the illustrated embodiments being in the form of respective bitmojis 640. In this example embodiment, a user of the social media platform will not be sharing their location if they have never interacted with the map GUI 612. The first time the user interacts with the map GUI 612, the user is taken through an on-boarding flow which allows for the setting of individual location sharing preferences.

0100Regardless of whether the user has selected to show their location to anyone, the user can see their own current location on the map at all times, and, if the user's bitmoji 640 is no longer in view, snap back to it, causing the map focus to re-center on the user location. <figref idref="f0010">FIG. 8A</figref> shows an example embodiment in which the viewing user's location is indicated by a custom user-selected or user-generated user interface element in the form of the user's bitmoji 640.

0101Location sharing preferences can be changed from the graphical user interface of <figref idref="f0010">FIG. 8A</figref>. In this embodiment, changes to location sharing preferences can be affected by (a) entering an invisible mode in which the user's location is not visible by any other user (also referred to herein as Ghost Mode), and (b) changing default location sharing settings and/or respective settings for different friend users and/or groups of friend users.

0102Location sharing can be turned off or on from within the map GUI 612, thereby to enter or exit Ghost Mode. In this embodiment, Ghost Mode can be toggled on/off via a map pin icon 808 in the top right (see <figref idref="f0010">FIG. 8A</figref>). When location sharing is off (i.e., when in Ghost Mode), the user's location is no longer displayed in the map GUI 612 on other user's client devices 102. The user can still, however, see his/her location in the map GUI on his/her own device. When in Ghost Mode, a ghost icon (not shown) slowly pulses in the top right of the screen in replacement of the map pin icon 808.

0103Note that the Ghost Mode functionality described herein is to be distinguished from turning off location services on a mobile user device. Thus, when Ghost Mode is turned on, the device location services of the client device 102 are still functioning, so that the user location can still be determined and displayed on the map GUI 612 of the user's own device 102, with social media content captured in Ghost Mode still being geo-tagged.

0104When the user turns on Ghost Mode after previously being present on the map, the user's bitmoji 640 disappears within seconds from other people's maps. When in Ghost Mode, the user can still see anyone on the map who has chosen to share their location with the user.

0105If the user selects their own bitmoji 640, a user bubble or user panel 816 is launched at the bottom of the touchscreen 606, enabling the user to access location sharing preferences via a settings soft button 824. The user panel 816 further includes a location-agnostic collection icon in the form of a My Story icon 832. The My Story icon 832 is selectable to launch replay of the viewing user's My Story, being a location-agnostic collection of social media items (here, ephemeral snaps) submitted by the user. Analogous to other location-agnostic GUI features disclosed herein, location-agnostic in this context means that the collection of social media items playable via the My Story icon 832 is collated and displayed without regard to any location constraint, thus being unaffected by geo-tagging information associated with the respective items, by the user's current location, or by the current focus of the map 618.

Location Sharing Preferences

0106Selecting the settings soft button 824 causes display in the map GUI 612 of a location sharing preferences interface 840 (<figref idref="f0011">FIG. 8B</figref>) that, in this example embodiment, provides the user with options for specifying who will get to see their location, and at what granularity. Default sharing granularity options provided in this example embodiment include: <ul id="ul0004" list-style="dash"><li>Precise, meaning in this embodiment is that the user's bitmoji 640 is displayed to friend users via their map GUIs 612 at the user's actual location (e.g., as indicated by the location services of the client device 102). In other words, the display location and the actual location for the user is substantially the same; and</li><li>City, meaning that the display location of the user's bitmoji 640 will be different from the actual location, but will be located within a defined geographical region corresponding to the current actual location. In this example embodiment, the defined geographical region within which the user's location is displayed is at a city level (e.g., Venice, CA, London, etc.).</li></ul>

0107When the city option is selected for a particular group of users or for particular individuals, the user's bitmoji 640 will in this example embodiment be shown in the map GUI 612 generated on the user devices 102 of the selected persons (or persons within the selected group) at a random location within that city, and which will in this embodiment not change if the user does not leave that city. <figref idref="f0010">FIG. 8C</figref> shows an example of display of a user bitmoji 640 in the interactive map 618 of the map GUI 612 at such a city-level display granularity, in which the user bitmoji 640 is shown at the random location in the city, together with an associated label 860 specifying, broadly, the city in which the user is located (in the illustrated example embodiment being Santa Monica).

0108Note that the features related to intentionally inaccurate display of the user's location has the effect that the user's location is displayed differently on, the one hand, an instance of the map GUI 612 generated on their own device 102 (e.g., <figref idref="f0010">FIG. 8A</figref>, in which the display location of the user bitmoji 640 corresponds to the actual location of the user) and, on the other hand, instances of the map GUI 612 generated on the user devices 102 of friend users having a non-precise viewing permission (e.g., labeled city-level display such as that illustrated in <figref idref="f0010">FIG. 8C</figref>, in which the display location of the user bitmoji 640 differs from the user's actual location). In this example embodiment, the display location of the user bitmoji 640 at a non-precise regional level (e.g., at city-level) is the same across different friend user devices 102, so that different friends see the user bitmoji 640 as being displayed at the same random location. In other embodiments, the display location can be different for different friend users.

0109It will be seen that this aspect of the disclosure thus provides for a method comprising: determining a location of a user device associated with the user of a social media application; determining a user-selected location display setting that specifies a manner in which the user location is to be displayed on a map-based GUI displayed to other users of the social media application, the location display setting being selected from a predetermined set of location display settings that correspond to display of the user location at different respective levels of precision on the map-based GUI; and representing the user on the map-based GUI of the friend user by rendering a UI element associated with the user at a location on the map-based GUI in accordance with the selected location display setting.

0110The defined geographic region is in the example embodiment of <figref idref="f0011">FIG. 8B</figref> as being available only at city level. In other embodiments, different or additional levels of display granularity can be provided, for example identifying different levels of cartographically and/or politically defined geographical regions, such as county-, city-, town-, or neighborhood level. Note that, in the example embodiment of FIG. RR, Ghost Mode can not only be toggled at a general level (via a Ghost Mode toggle 841), but can be selected for groups of users or for individual friend users via a group selector 842 and a friend selector 843 respectively. In some embodiments, the displayed user location remains fixed at the randomly selected display position until the user device 102 leaves the defined geographic area. Thus, a new display location is in some embodiments determined each time the user enters the relevant area.

0111As mentioned, the user can also via the location sharing preferences interface 840 select different groups of other users to which his location will be displayed, and may in some embodiments specify different display attributes for the different respective groups or for different respective individuals. In this example, audience options available via the group selector 842 include: Best Friends, Friends, and Custom (which is an individual-level whitelist of people specified by the friend selector 843).

0112If Friends are selected, all new people added to the user's friends list will automatically be able to see their location, consistent with the granularity level selected in the group selector 842 (e.g., being selectable as precise or at city level in the group selector 842 of <figref idref="f0011">FIG. 8B</figref>). If they are already sharing with the user, they appear within seconds on the user's map.

0113In this example embodiment, the location sharing relationships are two-way - if John is sharing his location with Jack, Jack will not see John on his map 618 unless he has added him as a friend. The user cannot add anyone who is not a friend to the Custom section. The user can furthermore, via the friend selector 843 43, define more specialized permissions for specific people, which override the default setting

0114When viewing the map GUI 612, the user will thus be able to see the locations of all his/her friends that have shared their location with him/her on the map 618. As discussed, each user is in this example embodiment represented by a bitmoji 640. If the friend does not have a bitmoji 640, a profile picture within a generic UI element is shown. If no profile pictures available for a particular friend, a default icon (e.g., a blank profile) is displayed at the corresponding location.

Friend-Level Access via Friend Icon

/

Friend Carousel

0115In this example embodiment, friend-level access to friend information and friend-specific content is enabled via the interactive map 618. Such friend-level access is distinguished from location-based access mechanisms such as a location-based search or snap collections accessible via respective geo-anchored story icons 631, 633. One example of such a friend-level access mechanism is a friend bubble or friend panel 909 (<figref idref="f0012">FIG. 9A</figref> that pops up at the bottom of the screen when the user taps on the bitmoji 640 of a displayed friend. The friend panel 909 and a friend carousel 918 of which it forms part, provide a number of functionalities to the user.

0116In the example embodiment of <figref idref="f0012">FIG. 9A</figref>, the friend panel 909 displays summary information about the user. As illustrated in <figref idref="f0012">FIG. 9A</figref>, the friend panel 909 forms part of a friend carousel 918 that enables the user selectively to switch focus between different friends. Note that, in addition to the main friend panel 909, the friend carousel 918 includes a next friend panel 909 whose left edge is exposed on the right-hand side of the touchscreen 606.

0117The user can swipe between friends on the map 618 via the friend carousel 918. In this example embodiment, switching between friends is achieved by swiping the current focus friend panel 909 left or right. Swiping left or right on the friend panel 909 brings into view the next or previous friend panel 909, as the case may be. In this example embodiment, swiping to a particular friend automatically centers the map 618 on the bitmoji 640 of that friend. Note that all of the friends for whom the user has viewing permission should be available as part of the friend carousel 918, not just those friends who are visible in the map viewport 621. Friends are in this embodiment ordered in the carousel by update recency.

0118The friend panel 909 also includes a chat soft button 918 that can be selected to launch a chat interface 950 (see <figref idref="f0012">FIG. 9B</figref>) in temporary replacement of the interactive map 618, but without leaving the map GUI 612. In other embodiments, tapping on the friend bitmojis 640 causes a fly-out menu to be displayed, with initiation of a chat session being one of the selectable options.

0119In this example embodiment, selection of the chat soft button 918 causes the chat interface 950 to pop up in a modal over the map 618, which modal can be swiped down to dismiss. Incoming chat notifications can be opened in this modal view.

0120The friend carousel 918 additionally provides location-agnostic access to social media content piuvided by respective friend users via the map GUI 612. In this example embodiment, such location-agnostic access is available via a location-agnostic collection icon in the form of a respective Friend Story icon 932 displayed in the friend panel 909 The Friend Story icon 932 is selectable to trigger replay of a corresponding story (in this example being that the My Story of the selected friend) comprising a series of snaps uploaded by the corresponding friend user, without any location constraint on the replayed material. In other words, no location information has any effect on the availability and identity of these snaps. The friend carousel 918, via the Friend Story icon 932 thus provides a link from the user location to social media content that is not located anywhere, in that the snaps or stories thus available will be the same irrespective of the friend user's current location, the current focus of the map viewport 621, or the current location of the viewing user. Worded differently, this and other location-agnostic access features of the map GUI 612 provide for access to friend content via the map GUI 612 in a manner similar to that which would be provided by a GUI that is not map-based. Thus, in one example embodiment, selecting a particular friend bitmoji 640 causes display of a menu or user interface element (in the example embodiment of <figref idref="f0012">FIG. 9A</figref>, the respective Friend Story icon 932 of the selected user) through which available snaps and/or stories of the target user can be viewed, without regard to any geo-tagging information of the respective snaps/stories.

0121As will be described below, certain aspects of the search mechanisms provided by the map GUI 612 similarly provide access to location-agnostic social media content of friend users via the map GUI 612.

<u>Search Functionalities</u>

0122In addition to viewing clustered stories by selection of the story icons 631, 633, the user can access snaps by use of one or more search functionalities provided by the map GUI 612. In this example embodiment, the map GUI 612 provides a number of different search mechanisms through which the user can access targeted social media content, the search mechanisms including: <ul id="ul0005" list-style="dash"><li>a search bar 665 (<figref idref="f0006">FIG. 6A</figref>) that enables the entry of a text string search query to cause display of search results comprising a list of entries satislying the search query (<figref idref="f0015">FIG. 10C</figref>);</li><li>location-based searches to search for social media content based at least in part on their respective geo-tag information. In some embodiments, these location-based search mechanisms include: <ul id="ul0006" list-style="none" compact="compact"><li>o a location-targeted search triggered by clicking or tapping at a target location on the map 618 (illustrated schematically in <figref idref="f0016">FIGS 11A</figref> and <figref idref="f0017">11B</figref>); and</li><li>o a friend-based location search to locate social media content based at least in part on the location of a selected friend user; and</li></ul></li><li>one or more friend-level access mechanisms that provide access to social media content of the selected friend users. In a particular embodiment, these include: <ul id="ul0007" list-style="none"><li>o access to location-agnostic friend content via the user icons, friend carousel 918 and/or individual friend panels 909; and</li><li>o location-agnostic collection icons (e.g., Friend Story icons 932, as described below with reference to <figref idref="f0013 f0014 f0015">FIGS. 10A-10C</figref>) displayed in association with respective friend users in a list of search results.</li></ul></li></ul>

Search Bar Mechanism

0123Two example embodiments of operation of a search mechanism provided via the search bar 665 is illustrated schematically with reference to <figref idref="f0013">FIG. 10A</figref> and <figref idref="f0014 f0015">FIGS. 10B-10D</figref> respectively. Discussing first the example embodiment of <figref idref="f0013">FIG. 10A</figref>, it will be seen that selection of the search bar 665 (<figref idref="f0006">FIG. 6A</figref>) causes display of a drop-down search interface 1010 that includes a search box 1020 for entering a text-based search query, and a number of lists of suggestions 1030 in respective user interface cells displayed below the search box 1020. In the example embodiments of <figref idref="f0014 f0015">FIGS. 10B-10D</figref>, individual suggestion cells correspond to individual snaps, stories, places, and/or friends. As can be seen with reference to a corresponding screenshot of the search interface 1010 in <figref idref="f0015">FIG. 10C</figref>, the particular cells displayed as part of the suggestions 1030 are dynamically filtered in response to text entry in the search box 1020, to include only stories, friends, or places that satisfy the entered search query.

0124When the user clicks on a selected cell in the list of suggestions 1030, the map GUI 612 in this example automatically navigates with a fly-over to the corresponding point on the map 618. If the selected cell is for a spike collection or cluster (also referred elsewhere herein as a spike story), the snaps in the corresponding story starts playing sequentially. If the selected cell is a friend cell, the map viewport 621 navigates to the corresponding friend bitmoji 640, and the associated a friend panel 909 pops up, as the case may be. In the example embodiment of <figref idref="f0013">FIG. 10A</figref>, at least some aspects of the display search results or suggestions 1030 are location-agnostic, returning search results from any location, without any constraint based on the user current location or the display area of the map 618. In particular, the "My Friends" section of the suggestions 1030 in the embodiment of <figref idref="f0013">FIG. 10A</figref> includes any friends for whom the user has viewing permission.

0125Thus, features provided by the search interface 1010 of <figref idref="f0013">FIG. 10A</figref> include: <ul id="ul0008" list-style="dash"><li>Searching for a location anywhere in the world, and navigating to it by selecting the corresponding suggestion cell; and</li><li>Viewing, before typing, suggestions 1030 of interesting social media content, and, while or after typing, suggestions that dynamically satisfies the search query. In the example embodiment of <figref idref="f0013">FIG. 10A</figref>, these include: <ul id="ul0009" list-style="none"><li>o Friends of the user, in section 1032, identified as a "My Friends";</li><li>o Trending place stories, event stories, and/or spike stories or clusters, irrespective of location, identified as "Trending Locations" in section 1034,</li><li>o Nearby place stories, event stories, and/or spike stories or clusters, in section 1036, identified as "Popular Nearby."</li></ul></li></ul>

0126Note that the "My Friends" and "Trending Locations" in the example embodiment of <figref idref="f0013">FIG. 10A</figref> shows friends/content from all over the world, not just friends/content that shows up in your viewport. All friends are shown section 1032 in order of how recently seen. In contrast, the "Popular Nearby" entries have a location restraint, being in this example embodiment limited to stories falling within the area of the current map viewport 621. In other embodiments, the location restraint is based on the user's current location, as indicated by the client device 102.

0127The "Trending Locations" and "Popular Nearby" stories are ranked globally according to a metric based on the underlying social media activity, in this example embodiment being ranked according to the number of unique users contributing to a story. In some embodiments, the trending locations may be ranked according to anomality metrics or interestingness scores. In yet further embodiments, surfacing of stories in the search interface 1010 can be based on raw snap volume, snap density over time, rate of increase in snap volume, or the like.

0128When users click on an entry in the search box dropdown, the map GUI navigates with a fly-over to the corresponding point on the map 618, after which the story/spike cluster starts playing, or friend panel 909 pops up, as the case may be.

0129Searching functionality available via other example embodiments of the map GUI 612 will now be described with reference to <figref idref="f0014 f0015">FIGS. 10B-10D</figref>. <figref idref="f0015">FIGS. 10C and 10D</figref> show behavior of the search interface during and after typing by the user in a search box forming part of the search interface 1010. It will appreciated that items listed during and after typing are limited to items (e.g., friends, places, events, or stories) that satisfy the search string entered thus far. Each one of a number of different sections of suggestions 1030, in which respective entries are ranked by priority, will be described separately below. Different embodiments may employ different combinations of these suggestions sections.

0130FRIENDS ON THE MAP - This section, indicated by reference numeral 1040 in <figref idref="f0014">FIG. 10B</figref>, shows friends that are that are on the map 618. In this example embodiment, the displayed friends are limited to friends who are visible in the map viewport 621 (i.e., in the geographical area of the map 618 displayed immediately before launching the search interface 1010). In other embodiments, the displayed friends include any friends who are currently available somewhere on the map 618. In this example, the top four friends are listed, followed by a View More button if necessary. The user can tap on a friend cell to locate them on the map 618.

0131Each friend cell includes, if available, a location-agnostic collection icon in the form of a Friend Story icon 932. Any of the Friend Story icons 932 can be tapped to view the corresponding friend story modally. Viewing of a story comprises sequential replay of the series of snaps included in the story. Each Friend Story icon 932 in this example embodiment comprises a user interface element in the form of a circular thumbnail to the right of the respective friend name. In this example, the stories thus playable include any of the friend's stories, without regard to any location information that may be associated with the story or with any snaps forming part of the story, thus being in accordance with the disclosed feature of map-based access to location-agnostic social media content of a target friend user. In other embodiments, however, the stories surfaced for replay are limited to those geo-tagged on the current map view.

0132In addition to the Friend Story icon 932, each friend entry in this example embodiment comprises an associated bitmoji, name, last seen timestamp, and associated location indicator. The listed friends are ordered by update recency.

0133ALL FRIENDS - This section, identified by reference numeral 1050 in <figref idref="f0015">FIG. 10C</figref> is similar to the My Friends section 1032 of <figref idref="f0013">FIG. 10A</figref>, in that it surfaces friends that satisfy the search string, irrespective of whether or not that friend is present on the map. In addition to a My Story icon 832 were available, a user name and a score indicator is shown as subtext for each friend. In this example embodiment, the indicated score is a user score that is used throughout the application to represent a user's engagement level. In some embodiments, as previously described, tapping on a friend cell navigates the map to focus on the display location of that friend. In this example embodiment, however, tapping on cell launches the chat interface 950 modally (see <figref idref="f0012">FIG. 9B</figref>). Dismissing the chat brings the user back to the search interface 1010.

0134TOP STORIES - This section, identified by reference numeral 1042 in the example embodiment of <figref idref="f0014">FIG. 10B</figref>, showcases the top stories from around the world (selected by curators daily or ranked by quality score or viewer volume).

0135NEARBY STORIES - This section, identified by reference numeral 1044 in <figref idref="f0014">FIG. 10B</figref>, shows interesting event clusters nearby or within the viewport. These will be ranked by descending quality score. In some embodiments, the nearby stories can be ranked according to the anomality metric, or according to a ranking score based at least in part on the anomality metric. Thus, it will be seen that some embodiments of the disclosure provide for social media application search interface that automatically surfaces ephemeral galleries based at least in part on geographical proximity between the user device and geolocations associated with the respective galleries. Ranking of the surfaced ephemeral galleries may be based at least in part on respective anomality metrics.

0136LOCATIONS - This section, identified by reference numeral 1060 in <figref idref="f0015">FIG. 10D</figref>, shows all points of interest (POIs) or places (as defined by the CMS 1224) that matches the search query. In some embodiments, surfacing and ranking of locations satisfying the search string includes locations with stories available for replay, i.e. having an associated place story. Thus, for example, in the screenshot of <figref idref="f0015">FIG. 10D</figref>, Blue Lagoon is ranked above Blue Bottle Coffee because it has an associated collaborative story, even though the latter is closer to the location of the user device 102.

0137If the place has a story, a story icon 1063 in the form of a thumbnail is in this example embodiment shown before the title (see <figref idref="f0015">FIG. 10D</figref>). Tapping the story icon 1063 (or anywhere in the cell) centers the place on the map and auto-plays the story, If the place does not have a thumbnail, tapping the cell in this example embodiment reverts to the map viewport 621, focusing on the relevant location, without playing any story. Fallback prioritization is by proximity to current viewport (after POIs and/or places with playable stories have been prioritized to the top).

Location-Based Search Via Target Location on Map

0138As an alternative to entering a text-based search query, the user can initiate a location-based search by selecting a target location on the map 618 separate from any of the story icons 631, 633, friend bitmojis 640, or any other selectable user interface element overlaid on the map 618. In this manner, the map 618 itself provides an interactive search mechanism. An example embodiment of such a location-based search is illustrated schematically with reference to <figref idref="f0016">FIGS. 11A</figref> and <figref idref="f0017">11B</figref>.

0139In response to the user's clicking or tapping on a particular location on the map viewport 621, a search is conducted for social media items within a predefined radius from the click- or tap location. In this example embodiment, such a location-based search does not return a list of graphical user interface elements that are selectable to play respective items, but instead automatically triggers automated sequential replay of items returned as a result of the search.

0140In the example embodiment of <figref idref="f0016">FIG. 11A</figref>, selection of a target location 1110 is by haptic contact at the selected on-screen position, consisting of tapping the touchscreen 606 with a single finger 1120 of the user. Thus, tapping on a non-thumbnail place on the map 618 will radiate out a search around the target location 1110, as illustrated schematically in <figref idref="f0017">FIG. 11B</figref> by a substantially circular geographical search area 1130 centered on the target location 1110. Such a location-based search can have a predefined search radius from the tap location. If any snaps are found in the geographical search area 1130, they are automatically played back in sequence, as described before. If there are no snaps in that area, the search bounces back to show no results found.

0141In some embodiments, such a location-based search is dynamically restrained by a predefined search limit, so that the size of the geographical search area 1130 can be variable in different instances. In some embodiments, the search limit for a location-based search is a predefined maximum size defined by the number of snaps located in the search. In an example embodiment, the geographical search area 1130 will thus radiate out from the target location 1110 to a point where a predefined maximum number of snaps are found, after which all snaps from that area will start playing in sequence. Worded differently, a predefined search metric or limit is provided in some embodiments to determine when the search should be stopped. As mentioned, the search limit may be an upper limit to the number of snaps located, with the search radiating out no further from the target location once the number of snaps located reaches the upper limit. Thus, it will be seen that different location-based searches can return snaps from geographical search areas 1130 that differ in size, depending on the density of snaps in the vicinity of the target location 1110.

0142In some example embodiments, such a location-triggered social media content search (i.e., a search for social media content uploaded by other users triggered by a user click/tap at the target location 1110 that does not coincide with a story icon 631/633 or friend bitmoji 640) can be configured automatically to exclude social media items included in one or more of the clustered collections represented by respective icons 631, 633 on the map. Thus, in this embodiment, the social media application will not include in search results or replay any snaps that are included in any of the place stories or any of the spike stories on the map.

0143As mentioned, initiating a location-based search by clicking or tapping on a non-thumbnail area in this example embodiment triggers automatic replay of snaps located within a geographical search area 1130 centered on the target location 1110. In other embodiments, such a search input by target location selection may cause display of a graphical user interface element listing the snaps found within the search area, for example including a thumbnail and username for each found snap. The user can thereafter select from the list of found snaps those which are to be replayed.

0144In some embodiments, the snaps located in a location-based search are played back in chronological sequence, as indicated by respective timestamp data indicating when the corresponding snap was uploaded. In some example embodiments, a sequencing operation may be performed on the subset of snaps identified in a location-based search, so that the replay sequence does not strictly follow chronological sequence. In one example embodiment, an improved sequence for media playback in response to a user tap on the map viewport is achieved by a sequence of operations comprising (a) finding all snaps in a fixed radius of the tap point, (b) doing geo-temporal clustering of those snaps, (c) sorting those clusters by distance from tap, and (d) sorting within the clusters by time.

0145In some embodiments, the location-based search is by default performed for material uploaded within a predefined default time period. For example, the location-based search may identify all snaps that (a) are located within the geographical search area 1130; (b) are not included in any story represented by a corresponding story icon 631/633; and (c) have timestamps within a default preceding ephemeral timespan. Thus, in an example embodiment in which a snap is by default available for 24 hours via the map GUI 612, the location-based search may by default locate snaps having timestamps indicating upload dates within the past 24 hours.

0146In some embodiments, however, the preceding period with icsptcl to which the search is performed is selectively variable by the user. For example, the search period timespan is automatically variable in response to an interval for which a search input gesture or signal is provided by the user.

0147In embodiments in which the map GUI 612 is displayed on a touchscreen 606 (as is the case in the example embodiment of <figref idref="f0016">FIGS. 11A</figref> and <figref idref="f0017">11B</figref>), a geo-temporal search is triggered by haptic contact at a particular location within the map 618, with the search being geographically centered on a target location 1110 defined by the on-screen position of the haptic contact. In some embodiments, an input interval indicated by the time period for which the haptic contact is maintained with the touchscreen 606 automatically determines the preceding timespan with respect to which the search is carried out. In such a case, for example, a tap on the screen triggers a geo-temporal search for material within the default time period, while a press and hold automatically triggers a geo-temporal search for material within an extended time period which is longer than the default time period. In one example embodiment, a tap input triggers a geo-temporal search with a 12-hour timespan, while a tap and hold triggers a geo-temporal search with a 24-hour timespan. In other embodiments, the extended timespan is variable in graduated fashion, so that multiple different search timespans are selectable based on the press-and-hold interval. Note that the operations described with reference to the haptic contact on the touchscreen 606 can be performed analogously by a click-and-hold input in instances where user input is provided by a cursor control mechanism, such as a mouse.

0148Instead, or in addition, the search radius (i.e., the size of the geographical search area 1 130) may be variable based on the length of the input interval, with longer input intervals (e.g., a longer hold period) corresponding to a larger search radius.

Location-Based Searching via Friend Location or for Friend Content

0149Some embodiments of the map GUI 612 provide functionalities for searching for social media content with a location restraint based at least in part on a location attribute of the selected friend user. The location restraint may, for example, operate to limit the search to social media content geo-tagged within a predefined geographic range centered on a geographic location of the selected friend user.

0150For example, the user can in some example embodiments trigger a location-based search with a location constraint based on the location of a selected friend user. In one example embodiment, such a location-based search with respect to a particular friend location can be performed in a manner analogous to that described below with respect to a general location-based search as described with reference to <figref idref="f0016">FIGS. 11A</figref> and <figref idref="f0017">11B</figref>. The various considerations and features discussed for general location-based searching can thus in some example embodiments apply, mutatis mutandis, to location-based searching based on friend location.

0151In one example embodiment, a friend-targeted location-based search can be triggered by user interaction with the friend icon or bitmoji 640 of a target friend user. In such an example embodiment, a click or tap input on the bitmoji 640 surfaces a menu or friend panel 909, while a press-and-hold input or a click-and-hold input automatically triggers a location-based search such as that previously described, the search area being centered on the location of the selected user. Instead, or in addition, a menu or friend panel 909 launched responsive to selection of the bitmoji 640 in some embodiments include a selectable user interface element to trigger a search for social media content targeted with a location constraint defined with respect to the location of the selected user.

0152In some embodiments, the friend-based social media content search additionally has an owner constraint such that the search results are limited to social media items of the selected friend user. In other embodiments or instances, the friend-based social media content search may search for content including but not limited to that uploaded or provided by the selected friend user.

0153Other example embodiments in which social media content searches via the map GUI 612 has a location constraint based on a selected friend user's location include instances where (while map focus is on a selected user) search results are limited to items currently displayed in the map viewport 621. The result section 1030 in the embodiment of <figref idref="f0014">FIG. 10B</figref> provides one such example. In other instances, the map GUI 612 provides for the option of searching for content exclusively contributed by a selected target user. Responsive to triggering such a friend-specific search, the user can change the focus and/or zoom level of the map viewport 621, with social media items surfaced in the map viewport 621 being limited to social media content posted by the target friend user.

0154As described with reference to some example embodiments herein, a social media application executing on the user device in some embodiments generates a map GUI having a map viewport on which displayed geographic locations of at least some friend users may differ from the actual geographic locations of those users. In some embodiments, the friend-centered location-based social media content search may be centered on the actual geographic location of the selected friend user, being distinct from a displayed location of the selected friend user on the map GUI. In other embodiments, the search may be performed with reference to the displayed location of the selected friend user.

<u>Overview of Map GUI Functionality</u>

0155In use, the map GUI 612 thus surfaces different types of location-based stories, which the user can view from the map 618. In the example embodiment of <figref idref="f0006">FIGS. 6A</figref> and <figref idref="f0007">6B</figref>, the user can access via the map GUI 612 snaps posted to Our Story from anywhere in the world. This can be achieved by navigating to different geographical areas displayed within the map viewport 621. In particular, the displayed geographical area can be changed by zooming in or zooming out, and by moving the focus area of the map viewport 621. In the example embodiment of <figref idref="f0006">FIGS. 6A</figref> and <figref idref="f0007">6B</figref>, in which the map GUI 612 is provided on a touchscreen 606, zooming in and zooming out can be achieved by haptic gestures in the form of a pinch-out or a pinch-in haptic input. Movement of the map 618 within the map viewport 621, so as to change the displayed geographical area, is achieved by a haptic dragging gesture at any point on the map 618.

0156In this example embodiment, the map 618 is not selectively rotatable by the user, having a fixed default orientation relative to the touchscreen 606. In other embodiments, the map 618 may have a fixed orientation relative to the Earth. In some embodiments, the map 618 is selectively rotatable, e.g., with all map content rotating around a fixed anchor.

0157As discussed at length above, in any particular map viewport 621, the displayed information can include: <ul id="ul0010" list-style="dash" compact="compact"><li>the color-coded heatmap 625, visually displaying the geographical distribution of snap uploading activity within a preceding window (for example the default snap lifetime, in this example 24 hours), allowing the user readily to identify places with more or less activity. This enables the user more effectively to target location-based searches via the map GUI 612. In some embodiments, the color-coded heatmap 625 is shown only at a highest level of magnification. In this example embodiment, however, the color-coded heatmap 625 is rendered at all zoom levels.</li><li>Thumbnail icons 631, 633 for surfaced content forming part of ephemeral galleries or stories. As described previously, these include in this example embodiment place icons 631 for geo-anchored stories associated with particular labeled locations, and spike icons 633 for location-based stories surfaced based on anomalous levels of geo-spatial activity.</li><li>Friend bitmojis 640 of friend users most frequently contacted by the user who is logged in to the social media client application 104 executing on the client device 102 and by which the map GUI 612 is generated.</li></ul>

0158In some embodiments, no spike icons 633 are shown at some levels of magnification. In a particular example embodiment, no spike icons 633 are shown at the original zoom level at which the map GUI 612 loads by default. In such an example, only the heatmap 625, friend bitmojis 640, and a number of place icons 631 are displayed on the map 618 at the original zoom level. As the user zooms in, spike icons 633 are surfaced, representing respective clusters of activity.

0159It will be appreciated that different icons 631, 633 are surfaced at different zoom levels. In this example embodiment, the map GUI 612 displays no more than a predefined maximum number of place icons 631 and no more than a predefined maximum number of spike icons 633 in any particular view. For example, at any zoom level, the top three place stories (ranked by snap volume) are surfaced by displaying respective place icons 631 in the map viewport 621. Likewise, at any zoom level, the top three spike stories (ranked by anomality or unusualness metric value) are surfaced by displaying respective spike icons 633 in the map viewport 621.

0160In addition to viewing stories surfaced in the map 618 by respective story icons 631, 633, the user can use one or more of the search functionalities described above to access any snap uploaded to Our Story and whose gallery participation timer or availability lifetime has not yet expired.

0161It will be appreciated that the map GUI 612 is dynamic, in that the information displayed therein changes dynamically with time. New snaps may continually be uploaded to Our Story, while the underlying social media items upon which surfacing of the story icons 631, 633 and generation of the heatmap 625 is based can further continually change due to the expiration of the availability of snaps. In this example embodiment, however, the information displayed in the map viewport 621 is not dynamically updated during display of any particular geographical area. Instead, changing of the focus of the map viewport 621 is associated with receiving updated information with respect to the story icons 631, 633 and heatmap 625 from the application server 112.

0162It is a benefit of the map GUI 612 as described with the example embodiments that it provides for user-friendly and intuitive interaction with geographically distributed social media content. The provision of different types of social media galleries (e.g., represented respectively by spike icons 633 and place icons 631) provides a system that automatically surfaces only content which is most relevant for user-selection in such a manner that the very large number of individual social media items that may be available via a social media platform is reduced in complexity, and that allows selection of targeted content in which the user might be interested.

EXAMPLE SYSTEM

0163<figref idref="f0018">FIG. 12</figref> shows an example embodiment of a social media platform system 1200 configured to provide a map-based graphical user interface for a social media application, such as the map GUI 612 described with reference to <figref idref="f0006 f0007 f0008 f0009 f0010 f0011 f0012 f0013 f0014 f0015 f0016 f0017">FIGS. 6A-11B</figref>. The system 1200 and its associated components can in some embodiments be provided server-side, for example by the social media application server system 108 (<figref idref="f0001">FIG. 1</figref>). In such instances, the respective components of the system 1200 can be provided by execution of the social media server application 114 on the application server 112. In other embodiments, one or more components of the system 1200 are provided client-side, for example by execution of the social media client application 104 on a respective client device 102 (<figref idref="f0001">FIG. 1</figref>). In yet further embodiments, the system 1200 is provided collaboratively server-side and client-side, the application server 112 and a client device 102 in communication therewith being configured to provide the respective system components by execution of the social media client application 104 on the client device 102 and by execution of the social media server application 114 on the application server 112.

0164The system 1200 includes a map engine 1208 to generate the map GUI 612, including the location-based social media information displayed in the map GUI 612. Thus, the map engine 1208 is configured to generate or to facilitate generation of the map 618 (<figref idref="f0006">FIG. 6A</figref>) in the map viewport 621 of the client device 102. To this end, the map engine 1208 can be configured to surface and cause display particular story icons 631, 633, to identify and cause display of respective friend bitmojis 640, to generate heatmap information and display or cause display of a heatmap 625 overlaid on the map 618, and to perform operations that provide other related functionalities of the map GUI 612 described with reference to <figref idref="f0006 f0007 f0008 f0009 f0010 f0011 f0012 f0013 f0014 f0015 f0016 f0017">FIGS. 6A-11B</figref>.

0165The system 1200 further includes a replay mechanism 1216 configured to cause automated sequential replay of the content of a set of social media items or snaps on the client device 102. The replay mechanism 1216 can thus cause sequential display of all of the snaps in a selected place story or spike story, as described previously herein. In some embodiments, the replay mechanism 1216 may provide for transmission of the set of snaps to the client device 102 in response to selection of a corresponding story icon 631/633. In some such embodiments, information automatically transmitted by the application server 112 to the client device 102 upon initial rendering of a map view in the map GUI 612 can include a first few (e.g., 2 or 3) snaps for each of the story icons 631, 633 surfaced in the map viewport 621. Upon selection of a particular story icon 631/633, the first few snaps in the story are immediately available for replay, with the subsequent snaps in the story being pulled from the application server 112 during presentation of the first few snaps.

0166The system 1200 also includes a content management system (CMS) 1224 enabling server-side administrative functionalities. The CMS 1224 provides an administration interface enabling operators to manage content, for example by defining various attributes of different place and/or event stories. The CMS 1224 in this example embodiment also includes the collection management system 204 (<figref idref="f0002">FIG. 2</figref>) as previously described. The CMS 1224 is configured for the automated or semiautomated compilation of the respective social media galleries or stories as previously described. This may include curation or moderation uf respective stories by use of a server-side curation interface provided by the CMS 1224.

0167The system 1200 further includes a search engine 1233 configured to provide search functionalities with respect in social media content via the map GUI 612. In particular, the search engine 1233 in this example embodiment provides for user-directed searching both via the search interface 1010 (<figref idref="f0013 f0014 f0015">FIGS. 10A-10D</figref>) and via location-based searching by direct selection of a target location on the map 618 (<figref idref="f0016 f0017">FIGS. 11A-11B</figref>).

0168The system 1200 further includes a user location serving mechanism 1237 configured to determine respective user locations, in this example embodiment indicated by the respective device locations, to determine for each user the particular friend users who are viewable via the map GUI 612, and to provide the respective user location information for display of associated user icons at corresponding display locations. The user location serving mechanism 1237 in some embodiments comprise, as part of the server system 108, a user location datastore and a per-user access control list (ACL) that lists the particular friend users viewable by each user. In some embodiments, the per-user ACL specifies respective viewing level granularity for each viewable user. The user location serving mechanism 1237 in such example embodiments is additionally configured to determine and manage respective user display granularity. This includes calculating non-precise display locations for some users, and causing display of a corresponding user icons at the non-precise display locations.

0169The system 1200 also includes an analyzer 1250 that is configured to process social media activity data to calculate anomality metric values for different areas that is to be served by the map GUI 612. In some embodiments, the analyzer 1250 generates a historical model of the geospatial distribution of social media activity, using a probabilistic rendering of individual snaps. Activity data from a current or near live time window is mapped to the historical model and a respective anomality score for different respective locations in the map is calculated. Such anomality scores can be used by the map engine 1208 to surface content via the map GUI 612, to determine the size of spike icons 633, and the rendering of heatmap information, or the like.

EXAMPLE METHODS

<u>Provision and Rendering of Heatmap</u>

0170Example methods relating to the rendering of social media nativity information in the form of a heat map in a graphical user interface will now be described. The description that follows is with reference to the map GUI 612 having a heatmap 625, according to the earlier described example embodiment. It will be borne in mind that implementation details may vary between different embodiments.

0171As mentioned, the heatmap 625 is displayed to guide users to places where there is content available to be viewed (see, for example, <figref idref="f0006">FIG. 6A</figref>), in particular guiding the user to profitable target locations for location-based searches, as described with reference to <figref idref="f0016 f0017">FIGS. 11A-11B</figref>. In this manner, provision of the heatmap 625 serves to minimize the number of fruitless or minimally effective location-based searches that would otherwise have been performed, thus reducing processing load on the server system 108. The frequency and repetition rate of searches with small or no result sets tends to be significantly greater than is the case for successful searches.

0172<figref idref="f0019">FIG. 13A</figref> is a schematic flow chart illustrating a high-level view of a method 1300 of providing a map-based GUI for a social media application, according to an example embodiment. The method 1300 is in this example embodiment executed by a system 1200 as described with reference to <figref idref="f0018">FIG. 12</figref>, using the system architecture and environment described with reference to <figref idref="f0001 f0002 f0003 f0004 f0005">FIGS. 1-5</figref>. Moreover, the example method 1300 in this example embodiment provides the various map-based functionalities, including location-based search functionalities, described with reference to <figref idref="f0006 f0007 f0008 f0009 f0010 f0011 f0012 f0013 f0014 f0015 f0016 f0017">FIGS. 6A-11B</figref>. The various operations that provide the respective functionalities described with reference to the example map GUI 612 of <figref idref="f0006 f0007 f0008 f0009 f0010 f0011 f0012 f0013 f0014 f0015 f0016 f0017">FIGS. 6A-11B</figref> are to be read as forming part of the method 1300, even though, for avoidance of repetition, not all of the different operations previously described are repeated in the description that follows.

0173At operation 1302, the map engine 1208 causes display of a map GUI 612 for social media platform on a client device 102. This includes, at operation 1304, providing for display of the map 618 as part of the map GUI 612. To this end, stylized map tiles for a geographical area in the map viewport 621 are served to the client device 102, and are rendered on the touchscreen 606.

0174At operation 1506, a heatmap 625 is displayed so as to be overlaid on the map 618 and to be geographically registered to the map 618. The heatmap 625 illustrates a geographical distribution of a particular social media activity metric. As discussed previously, the heatmap 625 in this example embodiment represents relative snap density at different locations within the displayed area. Rendering of the heatmap 625 is in this example embodiment performed by the social media client application 104, using heatmap data served to the client device 102 by the map server system 108.

0175In some embodiments, rendering of a pixelated heatmap distribution based on underlying social media activity data is done server-side, with pixel data or vector data for rendering the mapping transmitted to the client device 102. In this example embodiment, however, individual heatmap data points are served to the client device 102 by the map engine 1208. The heatmap 625 is 10 rendered by the social media client application 104 on the client device 102 based on these heatmap data points.

0176In this example embodiment, the heatmap is rendered using a set of data points based on timestamp and GPS coordinates from all snaps posted to Our Story. As shown in the more detailed flowchart of <figref idref="f0020">FIG. 13B</figref>, the map engine, at operation 1512, accesses the social media activity data representing the set of snaps upon which the heatmap is to be rendered, and, at operation 1514, generates and stores heatmap data points representative of the social media activity metric to be represented (here, distribution of snap volume).

0177In some embodiments, the generation of the heatmap data points comprises a pruning or filtering operation in which some snaps are excluded from the original data set based on predefined exclusion criteria . In this example embodiment, a per user limit is imposed on the number of snaps in the original data set, so that the pruned data set includes no more than a predefined maximum number of snaps from any one user. In this example embodiment, each user is represented in the pruned data set by no more than one snap. This serves to prevent skewing of the represented activity data by high-volume individual posters. Instead, or in addition, an age limit may be imposed, so that snaps from users younger than a certain age are excluded.

0178In this example embodiment, different heatmap data sets is, in an aggregation procedure, generated for different zoom levels. The underlying activity data is thus aggregated into tiles at various geographic zoom levels. The data format in this instance is: <img file="EP3616079B1_D0001.tif" /><img file="EP3616079B1_D0002.tif" />

0179At operation 1316, a request for a particular map view is received from the client device 102, responsive to which the heatmap data points for the particular requested zoom level and geographical area are served to the client device from the map engine 1208, at operation 1320.

0180After the heatmap data is received, the client device 102, at operation 1322, renders each point according to the location, radius, and weight parameters. The renderer in this example embodiment draws a Gaussian distribution with that radius and intensity into a pixel buffer for every point. Note that, in this example embodiment, the map is generated based on considering each individual social media item (here, snaps) probabilistically, rendered as a geographically distributed events. This typically applies at very high zoom levels and/or for isolated areas. At higher zoom and/or density, each heatmap data point is typically and aggregated representation of multiple underlying snaps.

0181After all points are rendered to the pixel buffer, the renderer does some normalization of the intensities in the pixel buffer based on calculated maximum values and HeatmapPeak values calculated on the server. After normalization is complete, the pixel buffer is converted to an OpenGL texture, a palette transformation is applied to convert to our desired color space, and the result is displayed on the touchscreen 606.

<u>Location Fuzzing</u>

0182Another aspect of the disclosure relates to intentionally displaying visual representation of some social media activity at non-accurate locations in a map-based GUI. In particular, the visual representation of social media activity that can allow other users to identify the actual location of a user is in some embodiments, to protect user privacy, displayed at an intentionally non-accurate locations from the actual geographic location. In this description, this aspect of the disclosure is referred to as location fuzzing, with the intentionally non-accurate location being referred to as the fuzzed location.

0183In the description that follows, the particular map feature to which location fuzzing is applied is heatmap data, for example individual heatmap data points representative of snaps meeting predefined fuzzing criteria. In other embodiments, different map features with similar location revealing potential are instead, or in addition, submitted to location fuzzing.

0184<figref idref="f0021">FIG. 14</figref> shows a method 1400 of a method for providing a map-based graphical user interface such as to apply location fuzzing to at least some representations of underlying social media activity. The method 1400 is in this example embodiment executed by a system 1200 as described with reference to <figref idref="f0018">FIG. 12</figref>, using the system architecture and environment described with reference to <figref idref="f0001 f0002 f0003 f0004 f0005">FIGS. 1-5</figref>. Moreover, the example method 1300 in this example embodiment provides the various map-based functionalities, including location-based search functionalities, described with reference to <figref idref="f0006 f0007 f0008 f0009 f0010 f0011 f0012 f0013 f0014 f0015 f0016 f0017">FIGS. 6A-11B</figref>. The various operations that provide the respective functionalities described with reference to the example map GUI 612 of <figref idref="f0006 f0007 f0008 f0009 f0010 f0011 f0012 f0013 f0014 f0015 f0016 f0017">FIGS. 6A-11B</figref> are to be read as forming part of the method 1400, even though, for avoidance of repetition, not all of the different operations previously described are repeated in the description that follows.

0185At operation 1410, the map engine 1208 accesses underlying geo-tagged social media activity for rendering various map features. In this example embodiment, similar to that described with reference to <figref idref="f0020">FIG. 13B</figref>, the activity information comprises a set of geo-tag snaps uploaded to Our Story for general accessibility. Location data associated with each snap thus indicates the actual location of the associated user device when capturing the snap.

0186At operation 1420, it is determined for each snap in the set (operation 1405) whether or not that snap satisfies predefined fuzzing criteria. A number of different examples of such fuzzing criteria is described later below.

0187If the snap does not satisfy the fuzzing criteria, then its actual location is used, at operation 1430, to render a corresponding visual representation in the map GUI 612. In this example embodiment, the respective snap is used at its actual location as a heatmap data point.

0188If, however, it is determined that the snap does satisfy the fuzzing criteria, a non-accurate or fuzzed display location is determined for the snap, at operation 1440, in an automated fuzzing procedure executed by the map engine 1208. A number of different considerations for such fuzzing procedures are described later below.

0189At operation 1460, the fuzzed location of the snap is used to render a corresponding visual representation on the map 618. In this example embodiment, the snap is represented in heatmap data served to client devices 102 at its intentionally inaccurate, fuzzed location.

0190The following terms and concepts are in this embodiment pertinent to some example fuzzing criteria:

0191"Isolated snap" - if a snap is posted and there are not many unique users posting snaps around that time and location. An exact definition is given below for one example in which the fuzzing criteria identifies isolated snaps.

0192"Fuzzing" -normally, a snap is represented as a blob of color on the heatmap at its true location. In some embodiments, the locations of isolated snaps is moved, as discussed, to a fuzzed location in order to protect the privacy of the user.

0193"Enhanced fuzzing" - certain countries or jurisdictions are considered more sensitive than other, or have different applicable regulations. "Enhanced fuzzing" will be employed there, which some example embodiments means that the distance by which isolated snaps are moved is increased..

0194"Minor" - a user under the age of 18. Special considerations for snaps posted by minors. Different definitions can apply in.

0195For any snap that is posted and subsequently displayed on the map GUI, a location of the user is potentially disclosed within 0.11 m of accuracy (give or take based on cell GPS accuracy). In public spaces, this less of an issue, but for people posting from their own homes, this could be undesirable.

0196To mitigate the potential safety implications of showing users' exact locations when posting snaps to Our Story, the system in this example embodiment, as discussed with reference to <figref idref="f0021">FIG. 14</figref>, automatically fuzzes the location of snaps that satisfy the predefined fuzzing criteria. Here, snaps are fuzzed when posted by users in 'isolation' (as defined below).

0197For these isolated snaps, the map engine 1208 renders a large radius, low intensity Gaussian distribution centered at the fuzzed location. The distance for which fuzzing occurs is in this example based on population density in that location. Note that the fuzzing distance is thus in some embodiments based at least in part on an associated population density, such that the fuzzing distance is smaller for areas of greater density.

0198Several considerations apply to such location fuzzing: <ul id="ul0011" list-style="bullet"><li>For events with many unique users posting to Our Story, high accuracy nf heatmap points is preferable.</li><li>For isolated users, low accuracy of heatmap points is preferable.</li><li>In some embodiments, the fuzzing procedure such as to prevent discovery by someone who has aggregate data of an isolated user posting many times.</li><li>The rendered heat map is to maintain a pleasant aesthetic.</li></ul>

0199An example fuzzing procedure used in the described embodiment, comprises: <ul id="ul0012" list-style="bullet" compact="compact"><li>Snaps are deemed to be 'isolated' if there are fewer than 2 other unique users posting content within a 30 minute period and 50 meter radius of the snap. In other embodiments, different isolation criteria can be used, for example having different phones for at least one of the proximity radius (here, 50 m), the threshold number of users (here, 2), and the measured time interval (here, 30 minutes).</li><li>For any snap that is identified as being isolated, the location of that snap is modified by a delta by automatically selecting a direction and distance that is based on a 16-bit hash of: <ul id="ul0013" list-style="none"><li>o The hash of the posting user's userId;</li><li>o The geohash of length 4 of the snaps's location (so that the geohash is constant for a constant position, meaning that different snaps originating from the same spot has the same fuzzed location, making detection of the true location more difficult); and/or</li><li>o A 2048-bit cryptographic secret from a registry key</li></ul></li><li>The first 8-bits of the hash is used to choose from 1 of 256 possible directions.</li><li>A distance from 100-2000m is chosen based on unique user app open density of the S2 cell the snap falls into <ul id="ul0014" list-style="none" compact="compact"><li>o For "enhanced fuzzing countries", the distance is doubled.</li></ul></li><li>The distance is then slightly jittered based on the remaining 8-bits of the hash.</li></ul>

0200Special considerations for minors, popular and/or Official Accounts may apply in some embodiments. In some embodiments, exclusion criteria are applied to some such accounts. For example, for minors posting content to Our Story, their snaps will not be shown on the map 618 unless there are more than 7 unique users posting within a 30 minute period within a 50m radius and, 30% of the posting users are non-minor accounts. For Popular and Official Accounts, their snaps are not represented on the map 618 unless there are more than a threshold number of unique users (here, 100) posting within a 30 minute period within a defined proximity radius (here, 50 m).

<u>Identifying and Surfacing Interesting Content based on Geospatial Anomality</u>

0201Considering the sheer volume of snaps that can at some times and at some places be uploaded to a social media platform, it can be problematic for users and for administrators of the platform to identify posting activity that users will find interesting. Some aspects of this disclosure provides for surfacing or making visible content based on underlying snap volume. One disadvantage of such surfacing is that some areas (like tourist locations) have consistently high volume but is seldom particularly interesting to nonparticipants. Interestingness per se is typically largely subjective, but one aspect of the disclosure operates on the insight that activity that is unusual or anomalous is more likely to be interesting than non-anomalous activity. This aspect of the disclosure thus proposes an anomality metric that provides a quantified value for a level of unusualness of activity in a particular area. Bearing in mind these distinctions, the terms anomality, unusualness, and interestingness are further in this description used substantially synonymously, unless the context clearly indicates otherwise.

0202The following section of the disclosure describes an example technique for finding interesting clusters of snaps in space and time by mining the stream of snaps sent to a live story or uploaded to Live Anywhere. Surfacing of clusters and/or stories in the map GUI 612, as described above with respect to spike stories or in a search interface 1010 is in some embodiments based at least in part on the identification of interesting snap clusters as described below.

0203The problem of finding interesting events is in the present example embodiment broken down into sub-problems: <ol id="ol0002"><li>1) Describing the amount of activity happening "now" at a particular place, or more generally, describing the amount of activity in a given window of space and time.</li><li>2) Describing what is "normal" activity in a given window of space and time. Then, "interesting" is when there is more activity than normal.</li></ol>

0204The more the level of activity exceeds normal, the more interesting that window of space and time is.

0205<figref idref="f0022">FIG. 15</figref> shows a high-level view of an example method 1500 for identifying and surfacing potentially interesting content in a social media platform. At operation 1510, a historical geo-temporal model for posting activity is created based on historical activity data (see operation 1505). As will be seen from the description that follows, the model is described as being geotemporal, in that it represents a geographical distribution of estimated snap density (e.g., snap volume per unit surface area) for each of a plurality of time windows. In some embodiments, the historical model may be two-dimensional only.

0206At operation 1515, target activity data (e.g., all snaps in a target area within a recent time window) is retrieved. Geographical distribution of snap density for the target activity is, at operation 1520, compared with the historical model, for example applying a statistical comparison between the target time window and a corresponding time window of the historical model. A respective anomality score a statistically calculated for different locations or portions of the compared target area, thus identifying one or more areas of anomalously high activity. Such areas arc also referred to herein as spikes or spike clusters. Note that surfacing is based on high anomality scores, considering that low levels of unusualness is unlikely to be interesting.

0207At operation 1535, social media content (in this case, one or more subsets of the underlying set of snaps) is extracted and surfaced in the map GUI 612 based on the identified geospatial activity anomalies. This can be by the formation and surfacing of spike stories (such as those described previously as being represented on the map 618 by respective spike icons 633), or by suggestions of interesting content in a search interface 1010.

0208A snap is identified as having three dimensions: a location defined by a lat-long pair, and a timestamp, fixing it in space and time. An aspect of anomality identification according to this embodiment is that those attributes are not viewed as a specific point in space and time, but rather as a probability cloud.

0209This is based on the insight that any single snap of an event could have been taken from a slightly different location or at a slightly different time and be functionally the same as the one observed. With this in mind, a set of snaps is not created as a census in the statistical sense. Rather it is considered a sample drawn from a random process. If we were able to somehow repeat last Monday between 10:00 and 10:30 in NYC, we can imagine observing a similar but different set of snaps from the random process of people moving about in the world and posting snaps.

0210When computing what "normal" looks like, we cut the world up into small cells (in one example embodiment, squares on the surface of the earth about 30 meters on a side) and spread the weight of each snap across many such cells, centered on the cell the snap actually fell into. In other embodiments, each snap may be centered at its precise location.

0211These accumulated weights become the parameters of a weight distribution that tells indicates where snaps are likely to occur in the future. Similarly, when computing when "now" looks like, the weight of each snap is distributed across many cells.

0212Anomality metric calculation (see operation 1520) in this embodiment comprises comparing those results to the range of possibilities we might have observed based on the "normal" weights. The more the current weights exceed the expected weights, as indicated by the model, the more anonymous (and therefore likely interesting) that cell is.

0213A more detailed overview of these operations in an example embodiment will now be described with reference to <figref idref="f0023 f0024">FIGS. 16-17</figref>, after which example implementation details are discussed with greater specificity.

0214<figref idref="f0023">FIG. 16</figref> shows a flowchart for identifying areas of anomalous activity (e.g., spike clusters) according to an example embodiment. At operation 1603, the surface of the earth is cut into a grid of cells. In this example embodiment, Google's S2 geometry is used, having cells with a pitch of about 35 m.

0215At operation 1606, historical snap activity data is retrieved for generating the historical model. In this example embodiment, historical activity is modeled on the grid as a Dirichlet distribution, where there is a parameter for each cell representing the concentration of snaps in that cell for a window of time. Persons of ordinary skill in the art of statistical analysis will be familiar with Dirichlet distributions, and with using a Dirichlet-multinomial with respect to such a distribution. Worded differently, the distribution of snap density across the grid is not smoothed within the cells, but provides a single density value for each cell.

0216At operation 1612, each snap in the set of historical snaps is represented in the model as having a smoothed density estimate (e.g., a weight distribution) in three dimensions - two dimensions on the surface of the earth, and one in time. In this example embodiment, spatial distribution or smoothing of the snap is performed using a radially symmetric two-dimensional Epanechnikov kernel that is 90 m wide each direction. For distribution in time, an Epanechnikov kernel that is six hours wide is employed in this example embodiment. It will be appreciated that other smoothing parameters can be employed in other embodiments.

0217Considering that the time windows or time slices are in this example embodiment one hour long, it will be seen that each snap thus adds to several cells in several times slices. Further, modeling the weight distribution using a kerneling procedure means that the snap adds most to the cell it was taken in at the time it was taken, but influences other cells less and less the further away those cells are in space and in time. In other embodiments, a Gaussian distribution or kernel can be employed. Use of an Epanechnikov kernel, however, has computational benefits.

0218Such representation of a snap as having a weight distribution time and in space is repeated, at operation 1609, for each snap in the historical set.

0219At operation 618, respective weight parameter or density value is calculated for each cell based on the contributions of all distributed snaps whose weight distributions at least partially fall thereon. This is repeated, at operation 1615, tor each time window, thus producing a set of historical models showing geographical distribution of historical activity for respective time windows.

0220It will be seen that, as summarized by operation 1621, the solution for each time window is a Dirichlet distribution whose parameters describe the concentration of snap density in S2 cells within a particular time window.

0221Describing what is happening currently, at operation 1520 (<figref idref="f0023">FIG. 16</figref>) is similar. At operation 1624, live or near live activity data showing the most recent hour of snaps is extracted. In this example embodiment, the process is filtered by imposing a per user limit of three snaps. In this instance, at most three snaps (chosen randomly) is selected from each user. From the filtered set, each snap (at operation 1609) is again represented probabilistically, at operation 1630, as having a density distribution. In this instance, however, a density estimate is calculated for each snap with the same space parameters (a 90 m Epanechnikov kernel), but with no time-based decay. In other words, the snaps have no time distribution and are represented as a probability cloud in two-dimensional space only.

0222At operation 1618, a density value is calculated for each cell similar to that described previously, giving a pseudo-count of snaps in each cell, where each individual snap has been "broken up" and smoothly applied to many cells in its neighborhood. Note again, in this instance that the weight distribution is applied across cells, but is not applied within a cell. Each cell has a single pseudo-count value.

0223The geographically distributed representation of the currently considered snaps is then scored, at operation 1640. For deviation/anomality based on a corresponding time window of the historical model (retrieved at operation 1 633). Entering the historical Dirichlet distribution into a Dirichlet-multinomial, where the sample-size parameter is the number of snaps observed in the current window, solves the problem directly. The 25th, 50th and 75th percentiles of counts in each S2 cell can now be determined, considered for a sample of snaps the same as currently observed, given the historical distribution of snaps as indicated by the corresponding model time slice. Then the score for each cell is calculated as the currently observed pseudo-count (O), less the median (M) divided by the interquartile range (IQR), that is, the 75th percentile minus the 25th. <maths id="math0001"><math display="block"><mi mathvariant="italic">anomality</mi><mspace width="1ex" /><mi mathvariant="italic">score</mi><mo>=</mo><mfrac><mrow><mi>O</mi><mo>−</mo><mi>M</mi></mrow><mi mathvariant="italic">IQR</mi></mfrac></math><img file="EP3616079B1_D0003.tif" /></maths>

0224This anomality score is roughly analogous to a number of standard deviations above the mean, a ratio that is common in settings where Gaussian distributions can be used or assumed. Calculating the quartiles of the beta-binomial in order to derive the respective cell anomality scores is described separately below.

0225<figref idref="f0024">FIG. 17</figref> shows a more detailed view of procedure 1535 fui, based on the cell-wise anomality scores, extracting spike clusters (being high-anomality groups of cells clustered together) and identifying associated snaps for surfacing in the map GUI 612. In this example embodiment, extraction of a spike cluster comprises, at operation 1705, identifying a spike cell as that cell with the highest anomality score in a target area. At operation 1710, the cluster is then flood filled out to a minimum threshold score (in this example embodiment being an anomality score of 2.5 as cutoff).

0226The resultant group of clustered cells is extracted as a spike cluster, at operation 1720, and is removed from consideration, at operation 1725. At operation 1730, it is considered whether or not there are any remaining cells with an anomality scores above the threshold value. If so, the process is repeated to extract further spike clusters until there are no more above- threshold cells remaining, at which cluster extraction ends, at operation 1735.

0227Thereafter, snaps from the cell clusters are surfaced on the map GUI 612, at operation 1740. This can comprise compiling respective collections or spike stories based on the snaps located within the cells of the spike clusters. Such spike stories can, at operation 1745, be surfaced on the map 618 by respective spike icons 633. Instead, or in addition, spike stories may be surfaced as suggestions in the search interface 1010.

0228The particular embodiment described for identifying spatial clusters with the Dirichlet-multinomial scales to the planet on two 16-core and one 8-core Gougle Compute Engine (GCE) instances. In this manner, effective identification and surfacing of potentially interesting social media content via the Map GUI can be achieved in fully automated fashion.

Additional Considerations

0229Bearing in mind the described unusualness cluster identification and extraction procedure described with reference to <figref idref="f0022 f0023 f0024">FIGS. 15-17</figref>, selected statistical considerations and implementation choices of the particular example embodiment now follows.

0230With respect to probabilistic modeling of snaps as kernels, there are theoretical reasons to prefer the Epanechnikov kernel over the Gaussian. In the present embodiment, however, this also has practical benefits. The Epanechnikov kernel has finite support, meaning that outside of a certain domain its density drops to zero. The Gaussian has infinite support, which requires choosing a cutoff beyond which we ignore further contributions. Significantly, the Epanechnikov is very efficient to compute, requiring just a handful of floating point operations.

0231A sense of scale and of the modeled Dirichlet distributions for an example set of snaps is provided in <figref idref="f0025">FIGS. 18A</figref> and <figref idref="f0026">18B</figref>, in which the respective locations of a set of snaps 1807 is shown overlaid on the Olympic Stadium in Berlin, a soccer and track and field venue. A corresponding portion of a grid 1815 provided by S2 level 18 is also shown. In <figref idref="f0011">FIG. 8B</figref>, a derived Dirichlet distribution 1829 based on the set of snaps 1807 is shown. Note that the drawings counterintuitively illustrated higher density values in lighter shades than lower density values.

0232Pertaining to selection of time window size and historical model size, a number of considerations apply. In this embodiment, the model identifies two types of day - weekdays and weekend days. Further, we break the world up into IANA timezones, making a model for each one separately. Thus, there is a model for each combination of a) time of day, b) day-class (weekend or weekday), and c) IANA timezone. That makes 24 · 4 · 2 = 192 models for each timezone. There are about 360 timezones in the IANA database that are tracked in this implementation, making for a total of roughly 70,000 models.

0233A further implementation detail is that a given user can contribute only a single snap (chosen randomly) to any one model. This prevents any one user from having undue influence, particularly in areas with sparse coverage.

Quartiles of the beta-binomial

0234To derive the score on based on the Dirichlet-multinomial, the quartiles - the 25th, 50th and 75th percentiles - for each bucket of a Dirichlet-multinomial is to be computed. Bear in mind that the Dirichlet distribution can be understood as indicating the probability of a single snap falling any one of the respective cells. Therefore, one way of calculating the quartiles (which is used in some embodiments) is to simulate a vast number of draws from the Dirichlet-multinomial, keeping track of the counts in each cell in each draw. Thereafter, the quartiles of the accumulated data in each cell can be computed.

0235In this example embodiment, however, the Dirichlet-multinomial is collapsed to a series of beta-binomials. Each cell's quartiles are the quartiles of a beta-binomial where one of the two shape parameters, <i>alpha,</i> is the value of the Dirichlet parameter for that cell. The other shape parameter, <i>beta,</i> is the sum of the Dirichlet parameters for all the other cells. In notation, if you have a Dirichlet-multinomial distribution, Dirichlet-multinomial (<i>α, n</i>)

0236Where <i>α</i> is a vector of concentration parameters <i>α</i>1, . . . , <i>α</i>n, then the density in the kth bin is distributed as beta-binomial, <maths id="math0002"><math display="block"><mi mathvariant="italic">Beta</mi><mo>−</mo><mi mathvariant="italic">binomial</mi><mfenced><msub><mi>α</mi><mi>k</mi></msub><mstyle displaystyle="true"><munder><mo>∑</mo><mrow><mi>i</mi><mo>≠</mo><mi>k</mi></mrow></munder><mrow><msub><mi>α</mi><mi>k</mi></msub><mo>,</mo><mi>n</mi></mrow></mstyle></mfenced></math><img file="EP3616079B1_D0004.tif" /></maths>

0237There is no simple analytic function that gives quantiles of the Beta-binomial, so the quartiles are found by summing up the density of the beta-binomial (given above) as we sweep over its range, noting where it crosses the quantiles of interest. Technically, the quantiles of the Beta-binomial can only be integers, but to achieve smoother scores the system in this example embodiment linearly interpolates for values greater than zero.

0238The procedure outlined above experiences difficulties when no snaps have been observed in the history of a given S2 cell, but one or more snaps are observed in the current time slice. All three of the quartile will be zero, and the score will be infinity. This can also happen when <i>α</i>_k is non-zero but sufficiently small. To this end, a lower bound is put on the IQR used in the score calculation.

0239In the present embodiment, the minimum IQR is set at 0.25, which requires three snaps all directly on top of one another in order to pass the minimum score threshold for cluster creation (2.5). More snaps are required if they are not directly on top of one another.

0240In another example embodiment, current snaps are distributed using a Gaussian kernel and a bandwidth of 35 meters in each direction. A different method to characterize the range of normal activity is via resampling. Bootstrapping is one example method. Because most of space is very thinly populated with snaps, a smooth bootstrap is used, adding Gaussian noise to each snap (a standard deviation of 1 ,800s in time, and 25m in each dimension of 2D-space) in resampling.

0241Thus, a number of example embodiments for surfacing content based on an unusualness metric is described above.

<u>Probabilistic Geo-Temporal Representation of Social Media Activity</u>

0242As evident from the above example embodiments described with reference to <figref idref="f0022 f0023 f0024 f0025 f0026">FIGS. 15-18B</figref>, an aspect of the disclosure provides for determining one or more geo-temporal attributes of social media activity by a process comprising, for each of multiple social media postings, representing the posting as having a distribution in time and/or in space.

0243Thus, in some embodiments, representing respective postings as having a geo-temporal distribution comprises treating respective social media items as a probability cloud, for example having a Gaussian distribution or as an Epanechikov kernel. Instead, or in addition, the method in some embodiments comprise generating or extrapolating a historical model or historical representation of social media activity based at least in part on a resampling procedure executed with respect to a multiplicity of historical geo-tagged social media items. In one example embodiment, the resampling procedure comprises a bootstrapping operation.

0244In some embodiments, the representation of social media postings as having respective distributions in time and/or space is performed as part of an operation to represent a geo-temporal reference profile or model for historical social media activity for a particular geographical area. Instead, or in addition, the representation of social media postings as having respective distributions in time and/or space may be performed as part of a procedure to represent recent or near-live social media activity in the particular geographical area. In such cases, the geo-temporal reference profile and the representation of the recent or near-live social media activity may be used in combination to identify within the geographic area one or more regions of interesting or anomalous social media activity.

0245Thus, a number of example embodiments based on representing social media items probabilistically has been described above.

<u>Icon Variation Based on Activity Value</u>

0246As described previously, one aspect of the disclosure provides for automated variation of a visual attribute of user selectable user interface elements for respective collections of social media items based on respectively associated social media activity metrics. <figref idref="f0027">FIG. 19</figref> is a a schematic flow chart illustrating a high-level view of a method 1900 of providing such dynamic variation in appearance of collection icons in a map-based GUI for a social media platform, according to an example embodiment.

0247The method 1900 is in this example embodiment executed by a system 1200 as described with reference to <figref idref="f0018">FIG. 12</figref>, using the system architecture and environment described with reference to <figref idref="f0001 f0002 f0003 f0004 f0005">FIGS. 1-5</figref>. Moreover, the example method 1900 in this example embodiment provides the particular example embodiment described previously with reference to <figref idref="f0007">FIG. 6B</figref>, in which an on-screen size of respective story icons 631, 633 is variable based on respectively associated activity values. The various operations that provide the respective functionalities described with reference to the example map GUI 612 of <figref idref="f0006 f0007 f0008 f0009 f0010 f0011 f0012 f0013 f0014 f0015 f0016 f0017">FIGS. 6A-11B</figref> are to be read as forming part of the method 1900, even though, for avoidance of repetition, not all of the different operations previously described are repeated in the description that follows.

0248At operations 1910 and 1920, the social media platform system 1200 determines an associated social media activity metric value for each of a number of social media collections (here, stories) that are to be represented on the map 618 by respective geo-anchored user interface elements, in this example story icons 631, 633 (<figref idref="f0007">FIG. 6B</figref>).

0249In this example embodiment, the method 1900 provides for variation in icon size, and provides for variation of place icons 631 and spike icons 633 on different activity metrics. In particular, the size of place icons 631 is variable based on associated snap volume (with greater snap volume corresponding to greater display size), while the size of spike icons 633 is variable based on associated unusualness as indicated by a corresponding anomality score. The operation 1920 of determining respective activity metric scores in this example embodiment thus includes calculation of respective anomality scores for respective spike stories using the methods described with reference to <figref idref="f0022 f0023 f0024 f0025 f0026">FIGS. 15-18</figref>. In another example embodiment, place icons 631 have a consistent, invariable on-screen size, while the size of only spike icons 633 is variable.

0250At operation 1930, the map engine 1208 determines a respective display size for each of the variable of icons 631, 633, based on predefined criteria using snap volume tor the place icons 631 and anomality score for the spike icons 633. In this example embodiment, respective icon size values are generated by the map engine 1208 and written to respective map data tiles that defines the location and size of each of the icons 631, 633 that is to be displayed in a corresponding geographical area.

0251At operation 1940, the map engine 1208 causes display of an instance of the map GUI 612 for a particular geographical area corresponding to the map viewport 621, in which the on-screen sizes of the respective icons 631, 633 vary according to the previously determined values. In this example embodiment, this is achieved by serving to the requesting client device 102 the map data tiles corresponding to the requested view, thus communicating to the client device 102 respective sizes at which the different icons 631, 633 are to be rendered.

0252In this manner, the respective story icons; 631, 633 serve the dual purpose not only of providing geographically anchored elements that can be selected to perform one or more functions with respect to the associated story (e.g., to replay the story), but also communicates in a minimally invasive manner information of significant importance with respect to the associated story. For example, the user is immediately and intuitively informed how unusual a spike story is based on the size of the corresponding spike icon 633. Thus, the limited available screen area, used in the example embodiment of the map GUI 612 to convey a large amount and variety of information, is used more effectively than would otherwise be the case.

0253Thus, a number of example embodiments based on automated variance of icon appearance based on an associated activity metric have been described.

MACHINE AND SOFTWARE ARCHITECTURE

0254These systems, system components, methods, applications, and so forth described in conjunction with <figref idref="f0001 f0002 f0003 f0004 f0005 f0006 f0007 f0008 f0009 f0010 f0011 f0012 f0013 f0014 f0015 f0016 f0017 f0018">FIGS. 1- 12</figref> are implemented in some embodiments in the context of a machine and an associated software architecture. The sections below describe representative software architecture(s) and machine (e.g., hardware) architecture(s) that are suitable for use with the disclosed embodiments.

0255Software architectures are used in conjunction with hardware architectures to create devices and machines configured for particular purposes. For example, a particular hardware architecture coupled with a particular software architecture will create a mobile device, such as a mobile phone, tablet device, or so forth. A slightly different hardware and software architecture may yield a smart device for use in the "internet of things," while yet another combination produces a server computer for use within a cloud computing architecture. The software and hardware architectures presented here are example architectures for implementing the disclosure, and are not exhaustive as to possible architectures that can be employed for implementing the disclosure.

<u>Software architecture</u>

0256<figref idref="f0028">FIG. 20</figref> is a block diagram illustrating an example software architecture 2006, which may be used in conjunction with various hardware architectures herein described. <figref idref="f0028">FIG. 20</figref> 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 2006 may execute on hardware such as a machine 2100 of <figref idref="f0029">FIG. 21</figref> that includes, among other things, processors 2104, memory 2114, and I/O components 21 18. A representative hardware layer 2052 is illustrated and can represent, for example, the machine 2100 of <figref idref="f0029">FIG. 21</figref>. The representative hardware layer 2052 includes a processing unit 2054 having associated executable instructions 2004. The executable instructions 2004 represent the executable instructions of the software architecture 2006, including implementation of the methods, components, and so forth described herein. The hardware layer 2052 also includes memory and/or storage modules memory/storage 2056, which also have the executable instructions 2004. The hardware layer 2052 may also comprise other hardware 2058.

0257In the example architecture of <figref idref="f0028">FIG. 20</figref>, the software architecture 2006 may be conceptualized as a stack of layers where each layer provides particular functionality. For example, the software architecture 2006 may include layers such as an operating system 2002, libraries 2020, frameworks/middleware 2018, applications 2016, and a presentation layer 2014. Operationally, the applications 2016 and/or other components within the layers may invoke application programming interface (API) calls 2008 through the software stack and receive a response in the form of messages 2008. 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 2018, while others may provide such a layer. Other software architectures may include additional or different layers.

0258The operating system 2002 may manage hardware resources and provide common services. The operating system 2002 may include, for example, a kernel 2022, services 2024, and drivers 2026. The kernel 2022 may act as an abstraction layer between the hardware and the other software layers. For example, the kernel 2022 may be responsible for memory management, processor management (e.g., scheduling), component management, networking, security settings, and so on. The services 2024 may provide other common services for the other software layers. The drivers 2026 are responsible for controlling or interfacing with the underlying hardware. For instance, the drivers 2026 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.

0259The libraries 2020 provide a common infrastructure that is used by the applications 2016 and/or other components and/or layers. The libraries 2020 provide functionality that allows other software components to perform tasks in an easier fashion than by interfacing directly with the underlying operating system 2002 functionality (e.g., kernel 2022, services 2024, and/or drivers 2026). The libraries 2020 may include system libraries 2044 (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 2020 may include API libraries 2046 such as media libraries (e.g., libraries to support presentation and manipulation of various media formats such as MPEG4, H.264, MP3, AAC, AMR, JPG, PNG), graphics libraries (e.g., an OpenGL framework that may be used to render 2D and 3D 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 2020 may also include a wide variety of other libraries 2048 to provide many other APIs to the applications 2016 and other software components/modules.

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

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

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

<u>Hardware Architecture</u>

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

0264The machine 2100 may include processors 2104, memory/storage 2106, and I/O components 2118, which may be configured to communicate with each other such as via a bus 2102. The memory/storage 2106 may include a memory 2114. such as a main memory, or other memory storage, and a storage unit 2116, both accessible to the processors 2104 such as via the bus 2102. The storage unit 2116 and memory 2114 store the instructions 2110 embodying any one or more of the methodologies or functions described herein. The instructions 2110 may also reside, completely or partially, within the memory 2114, within the storage unit 2116, within at least one of the processors 2104 (e.g., within the processor's cache memory), or any suitable combination thereof, during execution thereof by the machine 2100. Accordingly, the memory 2114, the storage unit 2116, and the memory of the processors 2104 are examples of machine-readable media. In some embodiments, the processors 2104 comprise a number of distributed processors 2108-2112, each of which have access to associated memories storing instructions 2110.

0265The I/O components 2118 may include a wide variety of components to receive input, provide output, produce output, transmit information, exchange information, capture measurements, and so on. The specific I/O components 2118 that are included in a particular machine 2100 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 2118 may include many other components that are not shown in <figref idref="f0029">FIG. 21</figref>. The I/O components 2118 are grouped according to functionality merely for simplifying the following discussion, and the grouping is in no way limiting. In various example embodiments, the I/O components 2118 may include output components 2126 and input components 2128. The output components 2126 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 2128 may include alphanumeric input components (e.g., a keyboard, a touchscreen configured to receive alphanumeric input, a photo-optical keyboard, or other alphanumeric input components), point-based input components (e.g., a mouse, a touchpad, a trackball, a joystick, a motion sensor, or other pointing instruments), tactile input components (e.g., a physical button, a touchscreen 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.

0266In further example embodiments, the I/O components 2118 may include biometric components 2130, motion components 2134, environment components 2136, or position components 2138 among a wide array of other components. For example, the biometric components 2130 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 2134 may include acceleration sensor components (e.g., accelerometer), gravitation sensor components, rotation sensor components (e.g., gyroscope), and so forth. The environment components 2136 may include, for example, illumination sensor components (e.g., photometer), temperature sensor components (e.g., one or more thermometers that detect ambient temperature), humidity sensor components, pressure sensor components (e.g., barometer), acoustic sensor components (e.g., one or more microphones that detect background noise), proximity sensor components (e.g., infrared sensors that detect nearby objects), gas sensors (e.g., gas sensors to detect concentrations of hazardous gases for safety or to measure pollutants in the atmosphere), or other components that may provide indications, measurements, or signals corresponding to a surrounding physical environment. The position components 2138 may include location sensor components (e.g., a Global Positioning System (GPS) receiver component), altitude sensor components (e.g., altimeters or barometers that detect air pressure from which altitude may be derived), orientation sensor components (e.g., magnetometers), and the like.

0267Communication may be implemented using a wide variety of technologies. The I/O components 2118 may include communication components 2140 operable to couple the machine 2100 to a network 2132 or devices 2120 via a coupling 2124 and a coupling 2122 respectively. For example, the communication components 2140 may include a network interface component or other suitable device to interface with the network 2132. In further examples, the communication components 2140 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 2120 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)).

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

GLOSSARY

0269"CARRIER SIGNAL" in this context refers to any intangible medium that is capable of storing, encoding, or carrying instructions for execution by the machine, and includes digital or analog communications signals or other intangible media to facilitate communication of such instructions. Instructions may be transmitted or received over the network using a transmission medium via a network interface device and using any one of a number of well-known transfer protocols.

0270"CLIENT DEVICE" in this context refers to any machine that interfaces to a communications network 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 assistant (PDA), smart phone, tablet, ultra book, netbook, laptop, multi-processor system, microprocessor-based or programmable consumer electronic system, game console, set-top box, or any other communication device that a user may use to access a network.

0271"COMMUNICATIONS NETWORK" in this context refers to one or more portions of a network that may be an ad hoc network, an intranet, an extranet, a virtual private network (VPN), a local area network (LAN), a wireless LAN (WLAN), a wide area network (WAN), a wireless WAN (WWAN), a metropolitan area network (MAN), the Internet, a portion of the Internet, a portion of the Public Switched Telephone Network (PSTN), a plain old telephone service (POTS) network, a cellular telephone network, a wireless network, a Wi-Fi^® 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 another type of cellular or wireless coupling. In this example, the coupling may implement any of a variety of types of data transfer technology, such as Single Carrier Radio Transmission Technology (1 xRTT), Evolution-Data Optimized (EVDO) technology, General Packet Radio Service (GPRS) technology, Enhanced Data rates for GSM Evolution (EDGE) technology, third Generation Partnership Project (3GPP) including 3G, fourth generation wireless (4G) networks, Universal Mobile Telecommunications System (UMTS), High-Speed Packet Access (HSPA), Worldwide Interoperability for Microwave Access (WiMAX), Long-Term Evolution (LTE) standard, others defined by various standard-setting organizations, other long-range protocols, or other data-transfer technology.

0272"EMPHEMERAL MESSAGE" in this context refers to a message that is accessible for a time-limited duration. An ephemeral message may be a text, an image, a video and the like. The access time for the ephemeral message may be set by the message sender. Alternatively, the access time may be a default setting or a setting specified by the recipient. Regardless of the setting technique, the message is transitory. "Snaps" as referenced in the description are ephemeral messages. Ephemeral messages are not limited to communications having specified individual recipients, but include social media items uploaded to a gallery or a collection for viewing by multiple users. Thus, the term ephemeral message includes a photo or video clip (which may be augmented or unaugmented) made available for a time-limited duration for viewing public or by a

0273"MACHINE-READABLE MEDIUM" in this context refers to a component, a device, or other tangible media able to store instructions and data temporarily or permanently and 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 (EPROM)), 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" shall 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" refers to a single storage apparatus or device, as well as "cloud-based" storage systems or storage networks that include multiple storage apparatus or devices. The term "machine-readable medium" excludes signals per se.

0274"COMPONENT" in this context refers to a device, a physical entity, or logic having boundaries defined by function or subroutine calls, branch points, application programming interfaces (APIs), or other technologies that provide for the partitioning or modularization of particular processing or control functions. Components may be combined via their interfaces with other components to carry out a machine process. A component may be a packaged functional hardware unit designed for use with other components and a part of a program that usually performs a particular function of related functions. Components may constitute either software components (e.g., code embodied on a machine-readable medium) or hardware components. A "hardware component" is a tangible unit capable of performing certain operations and may be configured or arranged in a certain physical manner. In various example embodiments, one or more computer systems (e.g., a standalone computer system, a client computer system, or a server computer system) or one or more hardware 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. 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 haidware 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 programming interface (API)). The performance of certain uf the operations may be distributed among the processors, not only residing within a single machine, but deployed across a number of machines. In some example embodiments, the processors or processor-implemented components may be located in a single geographic location (e.g., within a home environment, an office environment, or a server farm). In other example embodiments, the processors or processor-implemented components may be distributed across a number of geographic locations.

0275"PROCESSOR" in this context refers to 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 RadioFrequency 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.

0276"TIMESTAMP" in this context refers to a sequence of characters or encoded information identifying when a certain event occurred, for example giving date and time of day, sometimes accurate to a small fraction of a second.

LANGUAGE

0277Throughout this specification, plural instances may implement components, operations, or structures described as a single instance. Although individual operations of one or more methods are illustrated and described as separate operations, one or more of the individual operations may be performed concurrently, and nothing requires that the operations be performed in the order illustrated, unless that the context and/or logic clearly indicates otherwise. Structures and functionality presented as separate components in example configurations may be implemented as a combined structure or component. Similarly, structures and functionality presented as a single component may be implemented as separate components. These and other variations, modifications, additions, and improvements fall within the scope of the subject matter herein.

0278Although an overview of the disclosed subject matter has been described with reference to specific example embodiments, various modifications and changes may be made to these embodiments without departing from the broader scope of embodiments of the present disclosure.

0279The embodiments illustrated herein are described in sufficient detail to enable those skilled in the art to practice the teachings disclosed. Other embodiments may be used and derived therefrom, such that structural and logical substitutions and changes may be made without departing from the scope of this disclosure. The Detailed Description, therefore, is not to be taken in a limiting sense, and the scope of various embodiments is defined only by the appended claims.

0280As used herein, the term "or" may be construed in either an inclusive or exclusive sense. Moreover, plural instances may be provided for resources, operations, or structures described herein as a single instance. Additionally, boundaries between various resources, operations, modules, engines, and data stores are somewhat arbitrary, and particular operations are illustrated in a context of specific illustrative configurations. The specification and drawings are, accordingly, to be regarded in an illustrative rather than a restrictive sense.