Location-based timeline media content system
Summary by NHIP
Machine learning location timeline system
The system receives content items with geohashes defining captured locations and times, then uses machine learning models to identify subsets associated with travel locations outside a user's domicile. It distinguishes items by comparing their geohash coordinates against determined geographic and time ranges, displaying the resulting collection in an interactive arrangement.
Claim Score by NHIP
Abstract
Systems and methods for receiving a set of media content items including a geohash defining a captured time and a captured location of the media content item, identifying a first subset of media content items from the set of media content items comprising a geohash that equals a precision level threshold, and identifying a second subset of media content items from the set of media content items that include a geohash that exceeds the precision level threshold. The system also includes generating a timeline media content item collection including the second subset of media content items each including a geohash that exceeds the precisions level threshold, and causing display of a media content collection interface, the media content collection interface including the timeline media content item collection.
Term
14.7 yearsleft in the term
Expires 27 May 2041.
- Priority and filed
- Granted
- Today
- Expires
16 claims: 3 independent, 13 dependent
- 1Broadest claimClaim Score 21, narrow(NHIP)A method comprising:receiving, using at least one processor of a computing device, a plurality of content items associated with a user account, each content item comprising a geohash, the geohash defining a captured location indicating a longitude value and a latitude value that together define a geographic location associated with the content item, the geohash further defining a captured time comprising a time period representing when the content item was captured;automatically determining, using one or more machine learning (ML) models and the at least one processor, that a first subset of the plurality of content items is associated with a first travel location different from a domicile location associated with the user account, the first subset of the plurality of content items comprising a further plurality of content items, the determining comprising: comparing the captured location defined by the geohash of each content item with a determined geographic range;comparing the captured time defined by the geohash of each content item with a determined time range;and identifying the first subset of the plurality of content items based on the respective captured locations falling outside the determined geographic range and the respective captured times falling outside the determined time range;generating a content item collection comprising the first subset of the plurality of content items;causing display, at the computing device, of a first view of a content collection interface comprising the content item collection presented in an interactive arrangement;and causing display, at the computing device, of a second view of the content collection interface comprising an interactive thumbnail element corresponding to the first subset of the plurality of content items, the thumbnail element comprising an indication of the first travel location, wherein the thumbnail element updates the indication upon receiving a first user input, and wherein the content collection interface displays the first subset of the plurality of content items upon receiving a second user input associated with the thumbnail element.
- 10A device comprising:one or more computer processors;and one or more computer-readable mediums storing instructions that, when executed by the one or more computer processors, cause the device to perform operations comprising: receiving, using at least one processor of a computing device, a plurality of content items associated with a user account, each content item comprising a geohash defining a captured location indicating a longitude value and a latitude value that together define a geographic location associated with the content item, the geohash further defining a captured time comprising a time period representing when the content item was captured;automatically determining, using one or more machine learning (ML) models and the at least one processor, that a first subset of the plurality of content items is associated with a first travel location different from a domicile location associated with the user account, the first subset of the plurality of content items comprising a further plurality of content items, the determining comprising: comparing the captured location defined by the geohash of each content item with a determined geographic range;comparing the captured time defined by the geohash of each content item with a determined time range;and identifying the first subset of the plurality of content items based on the respective captured locations falling outside the determined geographic range and the respective captured times falling outside the determined time range;generating a content item collection comprising the first subset of the plurality of content items;causing display, at the computing device, of a first view of a content collection interface comprising the content item collection presented in an interactive arrangement;and causing display, at the computing device, of a second view of the content collection interface comprising an interactive thumbnail element corresponding to the first subset of the plurality of content items, the thumbnail element comprising an indication of the first travel location, wherein the thumbnail element updates the indication upon receiving a first user input, and wherein the content collection interface displays the first subset of the plurality of content items upon receiving a second user input associated with the thumbnail element.
- 16A non-transitory computer-readable medium storing instructions that, when executed by one or more computer processors of a client device, cause the client device to perform operations comprising:receiving, using at least one processor, a plurality of content items associated with a user account, each content item comprising a geohash defining a captured location indicating a longitude value and a latitude value that together define a geographic location associated with the content item, the geohash further defining a captured time comprising a time period representing when the content item was captured;automatically determining, using one or more machine learning (ML) models and the at least one processor, that a first subset of the plurality of content items is associated with a first travel location different from a domicile location associated with the user account, the first subset of the plurality of content items comprising a further plurality of content items, the determining comprising: comparing the captured location defined by the geohash of each content item with a determined geographic range;comparing the captured time defined by the geohash of each content item with a determined time range;and identifying the first subset of the plurality of content items based on the respective captured locations falling outside the determined geographic range and the respective captured times falling outside the determined time range;generating a content item collection comprising the first subset of the plurality of content items;causing display, at the computing device, of a first view of a content collection interface comprising the content item collection presented in an interactive arrangement;and causing display, at the computing device, of a second view of the content collection interface comprising an interactive thumbnail element corresponding to the first subset of the plurality of content items, the thumbnail element comprising an indication of the first travel location, wherein the thumbnail element updates the indication upon receiving a first user input, and wherein the content collection interface displays the first subset of the plurality of content items upon receiving a second user input associated with the thumbnail element.
Independent claims3
145 paragraphs in 4 sections, as filed
CLAIM OF PRIORITY
0001This application is a continuation of U.S. patent application Ser. No. 17/303,382, filed on May 27, 2021, which claims the benefit of priority to U.S. Provisional Application Ser. No. 63/168,397, filed on Mar. 31, 2021, each of which is incorporated herein by reference in its entirety.
BACKGROUND
0002As the popularity of mobile based social networking systems continues to grow, users are increasingly sharing media content items, such as images, pictures, and video with each other. These media content items encourage electronic visual communication on a global scale and promote ease of use in interactive socialization. Social media sharing platforms allow users to share millions of messages between mobile devices within a social network environment.
0003Users of the social network can share media content, such as audio, photos, images, and videos between their perspective user devices (e.g., mobile devices, personal computers). The social media sharing platforms may further allow users to capture and share images and pictures with other users by exchanging text messages. Most social network systems include features that enable the user to compile and view photos and videos on their perspective mobile device.
BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS
0004In the drawings, which are not necessarily drawn to scale, like numerals may describe similar components in different views. To easily identify the discussion of any particular element or act, the most significant digit or digits in a reference number refer to the figure number in which that element is first introduced. Some nonlimiting examples are illustrated in the figures of the accompanying drawings in which:
0005<figref idref="DRAWINGS">FIG. <b>1</b></figref> is a diagrammatic representation of a networked environment in which the present disclosure may be deployed, in accordance with some examples.
0006<figref idref="DRAWINGS">FIG. <b>2</b></figref> is a diagrammatic representation of a messaging system, in accordance with some examples, that has both client-side and server-side functionality.
0007<figref idref="DRAWINGS">FIG. <b>3</b></figref> is a diagrammatic representation of a data structure as maintained in a database, in accordance with some examples.
0008<figref idref="DRAWINGS">FIG. <b>4</b></figref> is a diagrammatic representation of a message, in accordance with some examples.
0009<figref idref="DRAWINGS">FIG. <b>5</b></figref> is a flowchart for an access-limiting process, in accordance with some examples.
0010<figref idref="DRAWINGS">FIG. <b>6</b></figref> illustrates a flowchart of a process for generating a location-based media content collection in accordance with some examples.
0011<figref idref="DRAWINGS">FIG. <b>7</b></figref> is a user interface diagram illustrating an example user interface of a location-based timeline content collection in accordance with one embodiment.
0012<figref idref="DRAWINGS">FIG. <b>8</b></figref> is a user interface diagram illustrating an example user interface of an extended portion of the location-based timeline content collection in accordance with one embodiment.
0013<figref idref="DRAWINGS">FIG. <b>9</b></figref> is a diagrammatic representation of a machine in the form of a computer system within which a set of instructions may be executed for causing the machine to perform any one or more of the methodologies discussed herein, in accordance with some examples.
0014<figref idref="DRAWINGS">FIG. <b>10</b></figref> is a block diagram showing a software architecture within which examples may be implemented.
0015<figref idref="DRAWINGS">FIG. <b>11</b></figref> is a diagrammatic representation of a processing environment, in accordance with some examples.
DETAILED DESCRIPTION
0016When users in social networking systems capture and generate media content items, such as photos and videos, the media content items are stored based on the date, time, and location. A media content item typically includes metadata reflecting the date, time, and location in which it was captured by a computing device (e.g., smartphone). Users typically capture and store photos and videos while in their current or prior home location or in a temporary location (vacationing, visiting friends/family). As the media content items accumulate in the user computing device's storage, it becomes increasingly difficult to view and display specific photos and videos that were captured during a certain time or location.
0017For instance, the user enables the system to generate a graphical compilation of media content items (e.g., content collection) that were captured and stored while the user was on vacation, visiting family and friends, or while the user was located in a location that was not his or her home location. However, due to data privacy and other data security concerns, the prior or prior home location of the user of the mobile device is not stored. The system only has access to a user's current home location. In order to accurately identify media content items that were captured and stored away from the current home location during a “trip” and generate the content collection for graphical display on a mobile device, the system must know all prior home locations in order to differentiate between the media content items that were captured while away from the home locations.
0018Using an example where a user lived in New York from 2015 until 2017, in 2015 the system would recognize the user's current home location as New York. Further, while located at the current home location, the user captured hundreds of photos and videos using the social networking system. Also, while the user was living in New York, in 2016 the user went on vacation to Paris and captured multiple photos and videos during the Paris trip. In 2017, the user moved to Los Angeles. The user's prior home location in New York was no longer recognized by the system. After the move to Los Angeles, the system would recognize the user's current home location as Los Angeles.
0019Due to data privacy and security technical features, the system would not store the user's prior home location (e.g., New York) and instead would recognize all locations associated with media content, other than Los Angeles e.g., New York and Paris) as temporary/vacationing locations. The system is enabled to generate media content collections containing photos and videos of vacationing destinations or trips. Thus, the system will generate a content collection made up of the hundreds of photos and videos captured while at the user's prior home location in New York, in addition to a content collection of the photos and videos captured and stored during the Paris trip.
0020By retrieving and generating the content collection from irrelevant media content items (e.g., a user's prior home location), the system components of the computing device are subject to increased data usage, increased power consumption and excessive demand on processing power. Further, the system generates inaccurate graphical media item content collections. Accordingly, there is a need for an improved system that determines the prior home location of a user that is not stored in the computing mobile device based on analyzing the location and time of each stored media content item over a period of separate days, months, or years, and use the prior home location to determine certain photos and videos from a content collection related to a vacation destination or trip.
0021In at least one example of the present disclosure, a system is provided that generates a timeline media content item collection made up of a series of media content items, such as, photos and videos, that were captured and stored at a location and time different from prior and present home location of the user of the mobile computing device. The system analyzes the captured location and date of each media content item captured and stored by a mobile computing device and determines the media content items that were taken while at the user's current and present home location by analyzing how many media content items were captured and stored at each location across separate time periods (e.g., days, months, or years).
0022For instance, if a precision level threshold associated with the captured location and time of the stored media content items are met, the system determines that the media content items are associated with a prior home location or a present home location of the user of the computing device. The system determines the media content items that are associated with a prior home location or a present home location when generating the timeline media content item collection. The precision level threshold can be a date range in days, weeks, months, or years in which the media content items were captured and stored on the user's computing device.
0023Networked Computing Environment
0024<figref idref="DRAWINGS">FIG. <b>1</b></figref> is a block diagram showing an example messaging system <b>100</b> for exchanging data (e.g., messages and associated content) over a network. The messaging system <b>100</b> includes multiple instances of a client device <b>102</b>, each of which hosts a number of applications, including a messaging client <b>104</b> and other applications <b>106</b>. Each messaging client <b>104</b> is communicatively coupled to other instances of the messaging client <b>104</b> (e.g., hosted on respective other client devices <b>102</b>), a messaging server system <b>108</b> and third-party servers <b>110</b> via a network <b>112</b> (e.g., the Internet). A messaging client <b>104</b> can also communicate with locally-hosted applications <b>106</b> using Applications Program Interfaces (APIs).
0025A messaging client <b>104</b> is able to communicate and exchange data with other messaging clients <b>104</b> and with the messaging server system <b>108</b> via the network <b>112</b>. The data exchanged between messaging clients <b>104</b>, and between a messaging client <b>104</b> and the messaging server system <b>108</b>, includes functions (e.g., commands to invoke functions) as well as payload data (e.g., text, audio, video or other multimedia data).
0026The messaging server system <b>108</b> provides server-side functionality via the network <b>112</b> to a particular messaging client <b>104</b>. While certain functions of the messaging system <b>100</b> are described herein as being performed by either a messaging client <b>104</b> or by the messaging server system <b>108</b>, the location of certain functionality either within the messaging client <b>104</b> or the messaging server system <b>108</b> may be a design choice. For example, it may be technically preferable to initially deploy certain technology and functionality within the messaging server system <b>108</b> but to later migrate this technology and functionality to the messaging client <b>104</b> where a client device <b>102</b> has sufficient processing capacity.
0027The messaging server system <b>108</b> supports various services and operations that are provided to the messaging client <b>104</b>. Such operations include transmitting data to, receiving data from, and processing data generated by the messaging client <b>104</b>. This data may include message content, client device information, geolocation information, media augmentation and overlays, message content persistence conditions, social network information, and live event information, as examples. Data exchanges within the messaging system <b>100</b> are invoked and controlled through functions available via user interfaces (UIs) of the messaging client <b>104</b>.
0028Turning now specifically to the messaging server system <b>108</b>, an Application Program Interface (API) server <b>116</b> is coupled to, and provides a programmatic interface to, application servers <b>114</b>. The application servers <b>114</b> are communicatively coupled to a database server <b>120</b>, which facilitates access to a database <b>126</b> that stores data associated with messages processed by the application servers <b>114</b>. Similarly, a web server <b>128</b> is coupled to the application servers <b>114</b>, and provides web-based interfaces to the application servers <b>114</b>. To this end, the web server <b>128</b> processes incoming network requests over the Hypertext Transfer Protocol (HTTP) and several other related protocols.
0029The Application Program Interface (API) server <b>116</b> receives and transmits message data (e.g., commands and message payloads) between the client device <b>102</b> and the application servers <b>114</b>. Specifically, the Application Program Interface (API) server <b>116</b> provides a set of interfaces (e.g., routines and protocols) that can be called or queried by the messaging client <b>104</b> in order to invoke functionality of the application servers <b>114</b>. The Application Program Interface (API) server <b>116</b> exposes various functions supported by the application servers <b>114</b>, including account registration, login functionality, the sending of messages, via the application servers <b>114</b>, from a particular messaging client <b>104</b> to another messaging client <b>104</b>, the sending of media files (e.g., images or video) from a messaging client <b>104</b> to a messaging server <b>118</b>, and for possible access by another messaging client <b>104</b>, the settings of a collection of media data (e.g., story), the retrieval of a list of friends of a user of a client device <b>102</b>, the retrieval of such collections, the retrieval of messages and content, the addition and deletion of entities (e.g., friends) to an entity graph (e.g., a social graph), the location of friends within a social graph, and opening an application event (e.g., relating to the messaging client <b>104</b>).
0030The application servers <b>114</b> host a number of server applications and subsystems, including for example a messaging server <b>118</b>, an image processing server <b>122</b>, and a social network server <b>124</b>. The messaging server <b>118</b> 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 messaging client <b>104</b>. 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 to the messaging client <b>104</b>. Other processor and memory intensive processing of data may also be performed server-side by the messaging server <b>118</b>, in view of the hardware requirements for such processing.
0031The application servers <b>114</b> also include an image processing server <b>122</b> that is dedicated to performing various image processing operations, typically with respect to images or video within the payload of a message sent from or received at the messaging server <b>118</b>.
0032The social network server <b>124</b> supports various social networking functions and services and makes these functions and services available to the messaging server <b>118</b>. To this end, the social network server <b>124</b> maintains and accesses an entity graph <b>308</b> (as shown in <figref idref="DRAWINGS">FIG. <b>3</b></figref>) within the database <b>126</b>. Examples of functions and services supported by the social network server <b>124</b> include the identification of other users of the messaging system <b>100</b> with which a particular user has relationships or is “following,” and also the identification of other entities and interests of a particular user.
0033Returning to the messaging client <b>104</b>, features and functions of an external resource (e.g., an application <b>106</b> or applet) are made available to a user via an interface of the messaging client <b>104</b>. In this context, “external” refers to the fact that the application <b>106</b> or applet is external to the messaging client <b>104</b>. The external resource is often provided by a third party but may also be provided by the creator or provider of the messaging client <b>104</b>. The messaging client <b>104</b> receives a user selection of an option to launch or access features of such an external resource. The external resource may be the application <b>106</b> installed on the client device <b>102</b> (e.g., a “native app”), or a small-scale version of the application (e.g., an “applet”) that is hosted on the client device <b>102</b> or remote of the client device <b>102</b> (e.g., on third-party servers <b>110</b>). The small-scale version of the application includes a subset of features and functions of the application (e.g., the full-scale, native version of the application) and is implemented using a markup-language document. In one example, the small-scale version of the application (e.g., an “applet”) is a web-based, markup-language version of the application and is embedded in the messaging client <b>104</b>. In addition to using markup-language documents (e.g., a .*ml file), an applet may incorporate a scripting language (e.g., a .*js file or a .json file) and a style sheet (e.g., a .*ss file).
0034In response to receiving a user selection of the option to launch or access features of the external resource, the messaging client <b>104</b> determines whether the selected external resource is a web-based external resource or a locally-installed application <b>106</b>. In some cases, applications <b>106</b> that are locally installed on the client device <b>102</b> can be launched independently of and separately from the messaging client <b>104</b>, such as by selecting an icon, corresponding to the application <b>106</b>, on a home screen of the client device <b>102</b>. Small-scale versions of such applications can be launched or accessed via the messaging client <b>104</b> and, in some examples, no or limited portions of the small-scale application can be accessed outside of the messaging client <b>104</b>. The small-scale application can be launched by the messaging client <b>104</b> receiving, from a third-party server <b>110</b> for example, a markup-language document associated with the small-scale application and processing such a document.
0035In response to determining that the external resource is a locally-installed application <b>106</b>, the messaging client <b>104</b> instructs the client device <b>102</b> to launch the external resource by executing locally-stored code corresponding to the external resource. In response to determining that the external resource is a web-based resource, the messaging client <b>104</b> communicates with the third-party servers <b>110</b> (for example) to obtain a markup-language document corresponding to the selected external resource. The messaging client <b>104</b> then processes the obtained markup-language document to present the web-based external resource within a user interface of the messaging client <b>104</b>.
0036The messaging client <b>104</b> can notify a user of the client device <b>102</b>, or other users related to such a user (e.g., “friends”), of activity taking place in one or more external resources. For example, the messaging client <b>104</b> can provide participants in a conversation (e.g., a chat session) in the messaging client <b>104</b> with notifications relating to the current or recent use of an external resource by one or more members of a group of users. One or more users can be invited to join in an active external resource or to launch a recently-used but currently inactive (in the group of friends) external resource. The external resource can provide participants in a conversation, each using respective messaging clients <b>104</b>, with the ability to share an item, status, state, or location in an external resource with one or more members of a group of users into a chat session. The shared item may be an interactive chat card with which members of the chat can interact, for example, to launch the corresponding external resource, view specific information within the external resource, or take the member of the chat to a specific location or state within the external resource. Within a given external resource, response messages can be sent to users on the messaging client <b>104</b>. The external resource can selectively include different media items in the responses, based on a current context of the external resource.
0037The messaging client <b>104</b> can present a list of the available external resources (e.g., applications <b>106</b> or applets) to a user to launch or access a given external resource. This list can be presented in a context-sensitive menu. For example, the icons representing different ones of the application <b>106</b> (or applets) can vary based on how the menu is launched by the user (e.g., from a conversation interface or from a non-conversation interface).
0038System Architecture
0039<figref idref="DRAWINGS">FIG. <b>2</b></figref> is a block diagram illustrating further details regarding the messaging system <b>100</b>, according to some examples. Specifically, the messaging system <b>100</b> is shown to comprise the messaging client <b>104</b> and the application servers <b>114</b>. The messaging system <b>100</b> embodies a number of subsystems, which are supported on the client-side by the messaging client <b>104</b> and on the sever-side by the application servers <b>114</b>. These subsystems include, for example, an ephemeral timer system <b>202</b>, a collection management system <b>204</b>, an augmentation system <b>208</b>, a map system <b>210</b>, a game system <b>212</b>, an external resource system <b>214</b>, and location-based media content collection system <b>216</b>.
0040The ephemeral timer system <b>202</b> is responsible for enforcing the temporary or time-limited access to content by the messaging client <b>104</b> and the messaging server <b>118</b>. The ephemeral timer system <b>202</b> incorporates a number of timers that, based on duration and display parameters associated with a message, or collection of messages (e.g., a story), selectively enable access (e.g., for presentation and display) to messages and associated content via the messaging client <b>104</b>. Further details regarding the operation of the ephemeral timer system <b>202</b> are provided below.
0041The collection management system <b>204</b> is responsible for managing sets or collections of media (e.g., collections of text, image video, and audio data). A collection of content (e.g., messages, including images, video, text, and audio) may be organized into an “event gallery” or an “event story.” Such a collection may be made available for a specified time period, such as the duration of an event to which the content relates. For example, content relating to a music concert may be made available as a “story” for the duration of that music concert. The collection management system <b>204</b> may also be responsible for publishing an icon that provides notification of the existence of a particular collection to the user interface of the messaging client <b>104</b>.
0042The collection management system <b>204</b> furthermore includes a curation interface <b>206</b> that allows a collection manager to manage and curate a particular collection of content. For example, the curation interface <b>206</b> enables an event organizer to curate a collection of content relating to a specific event (e.g., delete inappropriate content or redundant messages). Additionally, the collection management system <b>204</b> employs machine vision (or image recognition technology) and content rules to automatically curate a content collection. In certain examples, compensation may be paid to a user for the inclusion of user-generated content into a collection. In such cases, the collection management system <b>204</b> operates to automatically make payments to such users for the use of their content.
0043The augmentation system <b>208</b> provides various functions that enable a user to augment (e.g., annotate or otherwise modify or edit) media content associated with a message. For example, the augmentation system <b>208</b> provides functions related to the generation and publishing of media overlays for messages processed by the messaging system <b>100</b>. The augmentation system <b>208</b> operatively supplies a media overlay or augmentation (e.g., an image filter) to the messaging client <b>104</b> based on a geolocation of the client device <b>102</b>. In another example, the augmentation system <b>208</b> operatively supplies a media overlay to the messaging client <b>104</b> based on other information, such as social network information of the user of the client device <b>102</b>. 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 <b>102</b>. For example, the media overlay may include text or image that can be overlaid on top of a photograph taken by the client device <b>102</b>. 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 augmentation system <b>208</b> uses the geolocation of the client device <b>102</b> to identify a media overlay that includes the name of a merchant at the geolocation of the client device <b>102</b>. The media overlay may include other indicia associated with the merchant. The media overlays may be stored in the database <b>126</b> and accessed through the database server <b>120</b>.
0044In some examples, the augmentation system <b>208</b> 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 augmentation system <b>208</b> generates a media overlay that includes the uploaded content and associates the uploaded content with the selected geolocation.
0045In other examples, the augmentation system <b>208</b> 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 augmentation system <b>208</b> associates the media overlay of the highest bidding merchant with a corresponding geolocation for a predefined amount of time.
0046The map system <b>210</b> provides various geographic location functions, and supports the presentation of map-based media content and messages by the messaging client <b>104</b>. For example, the map system <b>210</b> enables the display of user icons or avatars (e.g., stored in profile data <b>316</b>) on a map to indicate a current or past location of “friends” of a user, as well as media content (e.g., collections of messages including photographs and videos) generated by such friends, within the context of a map. For example, a message posted by a user to the messaging system <b>100</b> from a specific geographic location may be displayed within the context of a map at that particular location to “friends” of a specific user on a map interface of the messaging client <b>104</b>. A user can furthermore share his or her location and status information (e.g., using an appropriate status avatar) with other users of the messaging system <b>100</b> via the messaging client <b>104</b>, with this location and status information being similarly displayed within the context of a map interface of the messaging client <b>104</b> to selected users.
0047The game system <b>212</b> provides various gaming functions within the context of the messaging client <b>104</b>. The messaging client <b>104</b> provides a game interface providing a list of available games that can be launched by a user within the context of the messaging client <b>104</b>, and played with other users of the messaging system <b>100</b>. The messaging system <b>100</b> further enables a particular user to invite other users to participate in the play of a specific game, by issuing invitations to such other users from the messaging client <b>104</b>. The messaging client <b>104</b> also supports both the voice and text messaging (e.g., chats) within the context of gameplay, provides a leaderboard for the games, and also supports the provision of in-game rewards (e.g., coins and items).
0048The external resource system <b>214</b> provides an interface for the messaging client <b>104</b> to communicate with remote servers (e.g. third-party servers <b>110</b>) to launch or access external resources, i.e. applications or applets. Each third-party server <b>110</b> hosts, for example, a markup language (e.g., HTML5) based application or small-scale version of an application (e.g., game, utility, payment, or ride-sharing application). The messaging client <b>104</b> may launches a web-based resource (e.g., application) by accessing the HTML5 file from the third-party servers <b>110</b> associated with the web-based resource. In certain examples, applications hosted by third-party servers <b>110</b> are programmed in JavaScript leveraging a Software Development Kit (SDK) provided by the messaging server <b>118</b>. The SDK includes Application Programming Interfaces (APIs) with functions that can be called or invoked by the web-based application. In certain examples, the messaging server <b>118</b> includes a JavaScript library that provides a given external resource access to certain user data of the messaging client <b>104</b>. HTML5 is used as an example technology for programming games, but applications and resources programmed based on other technologies can be used.
0049In order to integrate the functions of the SDK into the web-based resource, the SDK is downloaded by a third-party server <b>110</b> from the messaging server <b>118</b> or is otherwise received by the third-party server <b>110</b>. Once downloaded or received, the SDK is included as part of the application code of a web-based external resource. The code of the web-based resource can then call or invoke certain functions of the SDK to integrate features of the messaging client <b>104</b> into the web-based resource.
0050The SDK stored on the messaging server <b>118</b> effectively provides the bridge between an external resource (e.g., applications <b>106</b> or applets and the messaging client <b>104</b>. This provides the user with a seamless experience of communicating with other users on the messaging client <b>104</b>, while also preserving the look and feel of the messaging client <b>104</b>. To bridge communications between an external resource and a messaging client <b>104</b>, in certain examples, the SDK facilitates communication between third-party servers <b>110</b> and the messaging client <b>104</b>. In certain examples, a Web ViewJavaScriptBridge running on a client device <b>102</b> establishes two one-way communication channels between an external resource and the messaging client <b>104</b>. Messages are sent between the external resource and the messaging client <b>104</b> via these communication channels asynchronously. Each SDK function invocation is sent as a message and callback. Each SDK function is implemented by constructing a unique callback identifier and sending a message with that callback identifier.
0051By using the SDK, not all information from the messaging client <b>104</b> is shared with third-party servers <b>110</b>. The SDK limits which information is shared based on the needs of the external resource. In certain examples, each third-party server <b>110</b> provides an HTML5 file corresponding to the web-based external resource to the messaging server <b>118</b>. The messaging server <b>118</b> can add a visual representation (such as a box art or other graphic) of the web-based external resource in the messaging client <b>104</b>. Once the user selects the visual representation or instructs the messaging client <b>104</b> through a GUI of the messaging client <b>104</b> to access features of the web-based external resource, the messaging client <b>104</b> obtains the HTML5 file and instantiates the resources necessary to access the features of the web-based external resource.
0052The messaging client <b>104</b> presents a graphical user interface (e.g., a landing page or title screen) for an external resource. During, before, or after presenting the landing page or title screen, the messaging client <b>104</b> determines whether the launched external resource has been previously authorized to access user data of the messaging client <b>104</b>. In response to determining that the launched external resource has been previously authorized to access user data of the messaging client <b>104</b>, the messaging client <b>104</b> presents another graphical user interface of the external resource that includes functions and features of the external resource. In response to determining that the launched external resource has not been previously authorized to access user data of the messaging client <b>104</b>, after a threshold period of time (e.g., 3 seconds) of displaying the landing page or title screen of the external resource, the messaging client <b>104</b> slides up (e.g., animates a menu as surfacing from a bottom of the screen to a middle of or other portion of the screen) a menu for authorizing the external resource to access the user data. The menu identifies the type of user data that the external resource will be authorized to use. In response to receiving a user selection of an accept option, the messaging client <b>104</b> adds the external resource to a list of authorized external resources and allows the external resource to access user data from the messaging client <b>104</b>. In some examples, the external resource is authorized by the messaging client <b>104</b> to access the user data in accordance with an OAuth 2 framework.
0053The messaging client <b>104</b> controls the type of user data that is shared with external resources based on the type of external resource being authorized. For example, external resources that include full-scale applications (e.g., an application <b>106</b>) are provided with access to a first type of user data (e.g., only two-dimensional avatars of users with or without different avatar characteristics). As another example, external resources that include small-scale versions of applications (e.g., web-based versions of applications) are provided with access to a second type of user data (e.g., payment information, two-dimensional avatars of users, three-dimensional avatars of users, and avatars with various avatar characteristics). Avatar characteristics include different ways to customize a look and feel of an avatar, such as different poses, facial features, clothing, and so forth.
0054The location-based media content collection system <b>216</b> provides various operations, routines, and functions within the context of the messaging client <b>104</b> and the application servers <b>114</b>. The operations of the location-based media content collection system <b>216</b> are executed at the messaging client <b>104</b>, application servers <b>114</b>, or a third party server. In one example, the location-based media content collection system <b>216</b> retrieves a set of media content items, such as photos and videos from a database (e.g., database <b>126</b> as explained below). Each media content item includes a geohash. In communication with the map system <b>210</b>, the geohash represents longitude and latitude location information in which the media content item was captured by a computing device, such as client device <b>102</b>, during a predetermined time period. The geohash includes the time (e.g., day, month, year, hour, minutes, and seconds) in which the media content item was captured.
0055The location-based media content collection system <b>216</b> analyzes the geohash associated with each retrieved media content item and determines and identifies, utilizing machine learning algorithms, routines, and operations, which media content item's geohash includes captured time and captured location information that exceeds a predetermined precision level threshold over a predetermined period of time. The location-based media content collection system <b>216</b> also determines and identifies which media content item's geohash includes captured time and captured location information that falls below a predetermined precision level threshold over a predetermined period of time.
0056In one example, the precision level threshold represents a value defining a predetermined time in which the media content item was captured or stored in a proximity or region associated with a user profile of the messaging client <b>104</b>. In another example, the precision level threshold is a value defining a predetermined geolocation in which the media content item was captured or stored within a proximity, radius, or region of the domicile geolocation of the user profile associated with the messaging client <b>104</b> or a value defining a predetermined distance in which the media content item was captured or stored within a proximity, radius, or region of the domicile geolocation of the user profile associated with the messaging client <b>104</b>. In other examples, the precision level threshold is a value defining a predetermined frequency in which the media content item was captured or stored within a proximity, radius, or region of the domicile geolocation of the user profile associated with the messaging client <b>104</b>.
0057In one example, when the location-based media content collection system <b>216</b> determines each media content item containing a geohash that exceeds the precision level threshold, the location-based media content collection system <b>216</b> identifies and groups each media content item into a subset of media content items and associates the subset of media content items with a domicile geolocation on a map interface from the map system <b>210</b>. The domicile geolocation represents a present or prior home location of the user associated with the messaging client <b>104</b> that defines a radius, proximity, or region of interest of the prior or present home location. In another example, when the location-based media content collection system <b>216</b> determines each media content item containing a geohash that falls below the precision level threshold, the location-based media content collection system <b>216</b> identifies and groups each media content item into second subset of media content items.
0058The location-based media content collection system <b>216</b>, in another example, generates a location based timeline media content item collection or a timeline media content item collection that is made up of the second subset of media content items which each include a geohash that represents a captured time and captured location outside of the radius, proximity, or region of interest of the domicile geolocation (e.g., present or prior home location associated with the user). The location-based media content collection system <b>216</b> causes the display of a media content collection interface that renders and presents the location-based timeline media content item collection.
0059Data Architecture
0060<figref idref="DRAWINGS">FIG. <b>3</b></figref> is a schematic diagram illustrating data structures <b>300</b>, which may be stored in the database <b>126</b> of the messaging server system <b>108</b>, according to certain examples. While the content of the database <b>126</b> 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).
0061The database <b>126</b> includes message data stored within a message table <b>302</b>. This message data includes, for any particular one message, at least message sender data, message recipient (or receiver) data, and a payload. Further details regarding information that may be included in a message, and included within the message data stored in the message table <b>302</b> is described below with reference to <figref idref="DRAWINGS">FIG. <b>4</b></figref>.
0062An entity table <b>306</b> stores entity data, and is linked (e.g., referentially) to an entity graph <b>308</b> and profile data <b>316</b>. Entities for which records are maintained within the entity table <b>306</b> may include individuals, corporate entities, organizations, objects, places, events, and so forth. Regardless of entity type, any entity regarding which the messaging server system <b>108</b> stores data may be a recognized entity. Each entity is provided with a unique identifier, as well as an entity type identifier (not shown).
0063The entity graph <b>308</b> 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.
0064The profile data <b>316</b> stores multiple types of profile data about a particular entity. The profile data <b>316</b> may be selectively used and presented to other users of the messaging system <b>100</b>, based on privacy settings specified by a particular entity. Where the entity is an individual, the profile data <b>316</b> includes, for example, a user name, telephone number, address, settings (e.g., notification and privacy settings), as well as a user-selected avatar representation (or collection of such avatar representations). A particular user may then selectively include one or more of these avatar representations within the content of messages communicated via the messaging system <b>100</b>, and on map interfaces displayed by messaging clients <b>104</b> to other users. The collection of avatar representations may include “status avatars,” which present a graphical representation of a status or activity that the user may select to communicate at a particular time.
0065Where the entity is a group, the profile data <b>316</b> for the group may similarly include one or more avatar representations associated with the group, in addition to the group name, members, and various settings (e.g., notifications) for the relevant group.
0066The database <b>126</b> also stores augmentation data, such as overlays or filters, in an augmentation table <b>310</b>. The augmentation data is associated with and applied to videos (for which data is stored in a video table <b>304</b>) and images (for which data is stored in an image table <b>312</b>).
0067Filters, 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 set of filters presented to a sending user by the messaging client <b>104</b> 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 messaging client <b>104</b>, based on geolocation information determined by a Global Positioning System (GPS) unit of the client device <b>102</b>.
0068Another type of filter is a data filter, which may be selectively presented to a sending user by the messaging client <b>104</b>, based on other inputs or information gathered by the client device <b>102</b> during the message creation process. Examples of data filters include current temperature at a specific location, a current speed at which a sending user is traveling, battery life for a client device <b>102</b>, or the current time.
0069Other augmentation data that may be stored within the image table <b>312</b> includes augmented reality content items (e.g., corresponding to applying Lenses or augmented reality experiences). An augmented reality content item may be a real-time special effect and sound that may be added to an image or a video.
0070As described above, augmentation data includes augmented reality content items, overlays, image transformations, AR images, and similar terms refer to modifications that may be applied to image data (e.g., videos or images). This includes real-time modifications, which modify an image as it is captured using device sensors (e.g., one or multiple cameras) of a client device <b>102</b> and then displayed on a screen of the client device <b>102</b> with the modifications. This also includes modifications to stored content, such as video clips in a gallery that may be modified. For example, in a client device <b>102</b> with access to multiple augmented reality content items, a user can use a single video clip with multiple augmented reality content items to see how the different augmented reality content items will modify the stored clip. For example, multiple augmented reality content items that apply different pseudorandom movement models can be applied to the same content by selecting different augmented reality content items for the content. Similarly, real-time video capture may be used with an illustrated modification to show how video images currently being captured by sensors of a client device <b>102</b> would modify the captured data. Such data may simply be displayed on the screen and not stored in memory, or the content captured by the device sensors may be recorded and stored in memory with or without the modifications (or both). In some systems, a preview feature can show how different augmented reality content items will look within different windows in a display at the same time. This can, for example, enable multiple windows with different pseudorandom animations to be viewed on a display at the same time.
0071Data and various systems using augmented reality content items or other such transform systems to modify content using this data can thus involve detection of objects (e.g., faces, hands, bodies, cats, dogs, surfaces, objects, etc.), tracking of such objects as they leave, enter, and move around the field of view in video frames, and the modification or transformation of such objects as they are tracked. In various examples, different methods for achieving such transformations may be used. Some examples may involve generating a three-dimensional mesh model of the object or objects, and using transformations and animated textures of the model within the video to achieve the transformation. In other examples, tracking of points on an object may be used to place an image or texture (which may be two dimensional or three dimensional) at the tracked position. In still further examples, neural network analysis of video frames may be used to place images, models, or textures in content (e.g., images or frames of video). Augmented reality content items thus refer both to the images, models, and textures used to create transformations in content, as well as to additional modeling and analysis information needed to achieve such transformations with object detection, tracking, and placement.
0072Real-time video processing can be performed with any kind of video data (e.g., video streams, video files, etc.) saved in a memory of a computerized system of any kind. For example, a user can load video files and save them in a memory of a device, or can generate a video stream using sensors of the device. Additionally, any objects can be processed using a computer animation model, such as a human's face and parts of a human body, animals, or non-living things such as chairs, cars, or other objects.
0073In some examples, when a particular modification is selected along with content to be transformed, elements to be transformed are identified by the computing device, and then detected and tracked if they are present in the frames of the video. The elements of the object are modified according to the request for modification, thus transforming the frames of the video stream. Transformation of frames of a video stream can be performed by different methods for different kinds of transformation. For example, for transformations of frames mostly referring to changing forms of object's elements characteristic points for each element of an object are calculated (e.g., using an Active Shape Model (ASM) or other known methods). Then, a mesh based on the characteristic points is generated for each of the at least one element of the object. This mesh used in the following stage of tracking the elements of the object in the video stream. In the process of tracking, the mentioned mesh for each element is aligned with a position of each element. Then, additional points are generated on the mesh. A first set of first points is generated for each element based on a request for modification, and a set of second points is generated for each element based on the set of first points and the request for modification. Then, the frames of the video stream can be transformed by modifying the elements of the object on the basis of the sets of first and second points and the mesh. In such method, a background of the modified object can be changed or distorted as well by tracking and modifying the background.
0074In some examples, transformations changing some areas of an object using its elements can be performed by calculating characteristic points for each element of an object and generating a mesh based on the calculated characteristic points. Points are generated on the mesh, and then various areas based on the points are generated. The elements of the object are then tracked by aligning the area for each element with a position for each of the at least one element, and properties of the areas can be modified based on the request for modification, thus transforming the frames of the video stream. Depending on the specific request for modification properties of the mentioned areas can be transformed in different ways. Such modifications may involve changing color of areas; removing at least some part of areas from the frames of the video stream; including one or more new objects into areas which are based on a request for modification; and modifying or distorting the elements of an area or object. In various examples, any combination of such modifications or other similar modifications may be used. For certain models to be animated, some characteristic points can be selected as control points to be used in determining the entire state-space of options for the model animation.
0075In some examples of a computer animation model to transform image data using face detection, the face is detected on an image with use of a specific face detection algorithm (e.g., Viola-Jones). Then, an Active Shape Model (ASM) algorithm is applied to the face region of an image to detect facial feature reference points.
0076Other methods and algorithms suitable for face detection can be used. For example, in some examples, features are located using a landmark, which represents a distinguishable point present in most of the images under consideration. For facial landmarks, for example, the location of the left eye pupil may be used. If an initial landmark is not identifiable (e.g., if a person has an eyepatch), secondary landmarks may be used. Such landmark identification procedures may be used for any such objects. In some examples, a set of landmarks forms a shape. Shapes can be represented as vectors using the coordinates of the points in the shape. One shape is aligned to another with a similarity transform (allowing translation, scaling, and rotation) that minimizes the average Euclidean distance between shape points. The mean shape is the mean of the aligned training shapes.
0077In some examples, a search for landmarks from the mean shape aligned to the position and size of the face determined by a global face detector is started. Such a search then repeats the steps of suggesting a tentative shape by adjusting the locations of shape points by template matching of the image texture around each point and then conforming the tentative shape to a global shape model until convergence occurs. In some systems, individual template matches are unreliable, and the shape model pools the results of the weak template matches to form a stronger overall classifier. The entire search is repeated at each level in an image pyramid, from coarse to fine resolution.
0078A transformation system can capture an image or video stream on a client device (e.g., the client device <b>102</b>) and perform complex image manipulations locally on the client device <b>102</b> while maintaining a suitable user experience, computation time, and power consumption. The complex image manipulations may include size and shape changes, emotion transfers (e.g., changing a face from a frown to a smile), state transfers (e.g., aging a subject, reducing apparent age, changing gender), style transfers, graphical element application, and any other suitable image or video manipulation implemented by a convolutional neural network that has been configured to execute efficiently on the client device <b>102</b>.
0079In some examples, a computer animation model to transform image data can be used by a system where a user may capture an image or video stream of the user (e.g., a selfie) using a client device <b>102</b> having a neural network operating as part of a messaging client <b>104</b> operating on the client device <b>102</b>. The transformation system operating within the messaging client <b>104</b> determines the presence of a face within the image or video stream and provides modification icons associated with a computer animation model to transform image data, or the computer animation model can be present as associated with an interface described herein. The modification icons include changes that may be the basis for modifying the user's face within the image or video stream as part of the modification operation. Once a modification icon is selected, the transform system initiates a process to convert the image of the user to reflect the selected modification icon (e.g., generate a smiling face on the user). A modified image or video stream may be presented in a graphical user interface displayed on the client device <b>102</b> as soon as the image or video stream is captured, and a specified modification is selected. The transformation system may implement a complex convolutional neural network on a portion of the image or video stream to generate and apply the selected modification. That is, the user may capture the image or video stream and be presented with a modified result in real-time or near real-time once a modification icon has been selected. Further, the modification may be persistent while the video stream is being captured, and the selected modification icon remains toggled. Machine taught neural networks may be used to enable such modifications.
0080The graphical user interface, presenting the modification performed by the transform system, may supply the user with additional interaction options. Such options may be based on the interface used to initiate the content capture and selection of a particular computer animation model (e.g., initiation from a content creator user interface). In various examples, a modification may be persistent after an initial selection of a modification icon. The user may toggle the modification on or off by tapping or otherwise selecting the face being modified by the transformation system and store it for later viewing or browse to other areas of the imaging application. Where multiple faces are modified by the transformation system, the user may toggle the modification on or off globally by tapping or selecting a single face modified and displayed within a graphical user interface. In some examples, individual faces, among a group of multiple faces, may be individually modified, or such modifications may be individually toggled by tapping or selecting the individual face or a series of individual faces displayed within the graphical user interface.
0081A story table <b>314</b> stores data regarding collections of messages and associated image, video, or audio data, which are compiled into a media content item collection (e.g., a story or a gallery). The creation of a particular collection may be initiated by a particular user (e.g., each user for which a record is maintained in the entity table <b>306</b>). A user may create a “personal story” in the form of a collection of content that has been created and sent/broadcast by that user. To this end, the user interface of the messaging client <b>104</b> may include an icon that is user-selectable to enable a sending user to add specific content to his or her personal story.
0082A media content item collection may also constitute a “live story,” which is a collection or compilation of media content items from multiple users that is created manually, automatically, or using a combination of manual and automatic techniques. For example, a “live story” may constitute a curated stream of user-submitted content from varies locations and events. Users whose client devices have location services enabled and are at a common location event at a particular time may, for example, be presented with an option, via a user interface of the messaging client <b>104</b>, to contribute content to a particular live story. The live story may be identified to the user by the messaging client <b>104</b>, based on his or her location. The end result is a “live story” told from a community perspective.
0083A further type of media content item collection is known as a “location story,” which enables a user whose client device <b>102</b> is located within a specific geographic location (e.g., on a college or university campus) to contribute to a particular collection. In some examples, 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).
0084As mentioned above, the video table <b>304</b> stores video data that, in one example, is associated with messages for which records are maintained within the message table <b>302</b>. Similarly, the image table <b>312</b> stores image data associated with messages for which message data is stored in the entity table <b>306</b>. The entity table <b>306</b> may associate various augmentations from the augmentation table <b>310</b> with various images and videos stored in the image table <b>312</b> and the video table <b>304</b>.
0085Data Communications Architecture
0086<figref idref="DRAWINGS">FIG. <b>4</b></figref> is a schematic diagram illustrating a structure of a message <b>400</b>, according to some examples, generated by a messaging client <b>104</b> for communication to a further messaging client <b>104</b> or the messaging server <b>118</b>. The content of a particular message <b>400</b> is used to populate the message table <b>302</b> stored within the database <b>126</b>, accessible by the messaging server <b>118</b>. Similarly, the content of a message <b>400</b> is stored in memory as “in-transit” or “in-flight” data of the client device <b>102</b> or the application servers <b>114</b>. A message <b>400</b> is shown to include the following example components: <ul id="ul0001" list-style="none"><li id="ul0001-0001" num="0000"><ul id="ul0002" list-style="none"><li id="ul0002-0001" num="0087">message identifier <b>402</b>: a unique identifier that identifies the message <b>400</b>.</li><li id="ul0002-0002" num="0088">message text payload <b>404</b>: text, to be generated by a user via a user interface of the client device <b>102</b>, and that is included in the message <b>400</b>.</li><li id="ul0002-0003" num="0089">message image payload <b>406</b>: image data, captured by a camera component of a client device <b>102</b> or retrieved from a memory component of a client device <b>102</b>, and that is included in the message <b>400</b>. Image data for a sent or received message <b>400</b> may be stored in the image table <b>312</b>.</li><li id="ul0002-0004" num="0090">message video payload <b>408</b>: video data, captured by a camera component or retrieved from a memory component of the client device <b>102</b>, and that is included in the message <b>400</b>. Video data for a sent or received message <b>400</b> may be stored in the video table <b>304</b>.</li><li id="ul0002-0005" num="0091">message audio payload <b>410</b>: audio data, captured by a microphone or retrieved from a memory component of the client device <b>102</b>, and that is included in the message <b>400</b>.</li><li id="ul0002-0006" num="0092">message augmentation data <b>412</b>: augmentation data (e.g., filters, stickers, or other annotations or enhancements) that represents augmentations to be applied to message image payload <b>406</b>, message video payload <b>408</b>, or message audio payload <b>410</b> of the message <b>400</b>. Augmentation data for a sent or received message <b>400</b> may be stored in the augmentation table <b>310</b>.</li><li id="ul0002-0007" num="0093">message duration parameter <b>414</b>: parameter value indicating, in seconds, the amount of time for which content of the message (e.g., the message image payload <b>406</b>, message video payload <b>408</b>, message audio payload <b>410</b>) is to be presented or made accessible to a user via the messaging client <b>104</b>.</li><li id="ul0002-0008" num="0094">message geolocation parameter <b>416</b>: geolocation data (e.g., latitudinal and longitudinal coordinates) associated with the content payload of the message. Multiple message geolocation parameter <b>416</b> values may be included in the payload, each of these parameter values being associated with respect to content items included in the content (e.g., a specific image into within the message image payload <b>406</b>, or a specific video in the message video payload <b>408</b>).</li><li id="ul0002-0009" num="0095">message story identifier <b>418</b>: identifier values identifying one or more content collections (e.g., “stories” identified in the story table <b>314</b>) with which a particular content item in the message image payload <b>406</b> of the message <b>400</b> is associated. For example, multiple images within the message image payload <b>406</b> may each be associated with multiple content collections using identifier values.</li><li id="ul0002-0010" num="0096">message tag <b>420</b>: each message <b>400</b> 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 <b>406</b> depicts an animal (e.g., a lion), a tag value may be included within the message tag <b>420</b> 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 id="ul0002-0011" num="0097">message sender identifier <b>422</b>: an identifier (e.g., a messaging system identifier, email address, or device identifier) indicative of a user of the Client device <b>102</b> on which the message <b>400</b> was generated and from which the message <b>400</b> was sent.</li><li id="ul0002-0012" num="0098">message receiver identifier <b>424</b>: an identifier (e.g., a messaging system identifier, email address, or device identifier) indicative of a user of the client device <b>102</b> to which the message <b>400</b> is addressed.</li></ul></li></ul>
0099The contents (e.g., values) of the various components of message <b>400</b> may be pointers to locations in tables within which content data values are stored. For example, an image value in the message image payload <b>406</b> may be a pointer to (or address of) a location within an image table <b>312</b>. Similarly, values within the message video payload <b>408</b> may point to data stored within a video table <b>304</b>, values stored within the message augmentations <b>412</b> may point to data stored in an augmentation table <b>310</b>, values stored within the message story identifier <b>418</b> may point to data stored in a story table <b>314</b>, and values stored within the message sender identifier <b>422</b> and the message receiver identifier <b>424</b> may point to user records stored within an entity table <b>306</b>.
0100Time-Based Access Limitation Architecture
0101<figref idref="DRAWINGS">FIG. <b>5</b></figref> is a schematic diagram illustrating an access-limiting process <b>500</b>, in terms of which access to content (e.g., an ephemeral message <b>502</b>, and associated multimedia payload of data) or a content collection (e.g., an ephemeral message group <b>504</b>) may be time-limited (e.g., made ephemeral).
0102An ephemeral message <b>502</b> is shown to be associated with a message duration parameter <b>506</b>, the value of which determines an amount of time that the ephemeral message <b>502</b> will be displayed to a receiving user of the ephemeral message <b>502</b> by the messaging client <b>104</b>. In one example, an ephemeral message <b>502</b> 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 message duration parameter <b>506</b>.
0103The message duration parameter <b>506</b> and the message receiver identifier <b>424</b> are shown to be inputs to a message timer <b>510</b>, which is responsible for determining the amount of time that the ephemeral message <b>502</b> is shown to a particular receiving user identified by the message receiver identifier <b>424</b>. In particular, the ephemeral message <b>502</b> will only be shown to the relevant receiving user for a time period determined by the value of the message duration parameter <b>506</b>. The message timer <b>510</b> is shown to provide output to a more generalized ephemeral timer system <b>202</b>, which is responsible for the overall timing of display of content (e.g., an ephemeral message <b>502</b>) to a receiving user.
0104The ephemeral message <b>502</b> is shown in <figref idref="DRAWINGS">FIG. <b>5</b></figref> to be included within an ephemeral message group <b>504</b> (e.g., a collection of messages in a personal story, or an event story). The ephemeral message group <b>504</b> has an associated group duration parameter <b>508</b>, a value of which determines a time duration for which the ephemeral message group <b>504</b> is presented and accessible to users of the messaging system <b>100</b>. The group duration parameter <b>508</b>, for example, may be the duration of a music concert, where the ephemeral message group <b>504</b> 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 group duration parameter <b>508</b> when performing the setup and creation of the ephemeral message group <b>504</b>.
0105Additionally, each ephemeral message <b>502</b> within the ephemeral message group <b>504</b> has an associated group participation parameter <b>512</b>, a value of which determines the duration of time for which the ephemeral message <b>502</b> will be accessible within the context of the ephemeral message group <b>504</b>. Accordingly, a particular ephemeral message group <b>504</b> may “expire” and become inaccessible within the context of the ephemeral message group <b>504</b>, prior to the ephemeral message group <b>504</b> itself expiring in terms of the group duration parameter <b>508</b>. The group duration parameter <b>508</b>, group participation parameter <b>512</b>, and message receiver identifier <b>424</b> each provide input to a group timer <b>514</b>, which operationally determines, firstly, whether a particular ephemeral message <b>502</b> of the ephemeral message group <b>504</b> will be displayed to a particular receiving user and, if so, for how long. Note that the ephemeral message group <b>504</b> is also aware of the identity of the particular receiving user as a result of the message receiver identifier <b>424</b>.
0106Accordingly, the group timer <b>514</b> operationally controls the overall lifespan of an associated ephemeral message group <b>504</b>, as well as an individual ephemeral message <b>502</b> included in the ephemeral message group <b>504</b>. In one example, each and every ephemeral message <b>502</b> within the ephemeral message group <b>504</b> remains viewable and accessible for a time period specified by the group duration parameter <b>508</b>. In a further example, a certain ephemeral message <b>502</b> may expire, within the context of ephemeral message group <b>504</b>, based on a group participation parameter <b>512</b>. Note that a message duration parameter <b>506</b> may still determine the duration of time for which a particular ephemeral message <b>502</b> is displayed to a receiving user, even within the context of the ephemeral message group <b>504</b>. Accordingly, the message duration parameter <b>506</b> determines the duration of time that a particular ephemeral message <b>502</b> is displayed to a receiving user, regardless of whether the receiving user is viewing that ephemeral message <b>502</b> inside or outside the context of an ephemeral message group <b>504</b>.
0107The ephemeral timer system <b>202</b> may furthermore operationally remove a particular ephemeral message <b>502</b> from the ephemeral message group <b>504</b> based on a determination that it has exceeded an associated group participation parameter <b>512</b>. For example, when a sending user has established a group participation parameter <b>512</b> of <b>24</b> hours from posting, the ephemeral timer system <b>202</b> will remove the relevant ephemeral message <b>502</b> from the ephemeral message group <b>504</b> after the specified <b>24</b> hours. The ephemeral timer system <b>202</b> also operates to remove an ephemeral message group <b>504</b> when either the group participation parameter <b>512</b> for each and every ephemeral message <b>502</b> within the ephemeral message group <b>504</b> has expired, or when the ephemeral message group <b>504</b> itself has expired in terms of the group duration parameter <b>508</b>.
0108In certain use cases, a creator of a particular ephemeral message group <b>504</b> may specify an indefinite group duration parameter <b>508</b>. In this case, the expiration of the group participation parameter <b>512</b> for the last remaining ephemeral message <b>502</b> within the ephemeral message group <b>504</b> will determine when the ephemeral message group <b>504</b> itself expires. In this case, a new ephemeral message <b>502</b>, added to the ephemeral message group <b>504</b>, with a new group participation parameter <b>512</b>, effectively extends the life of an ephemeral message group <b>504</b> to equal the value of the group participation parameter <b>512</b>.
0109Responsive to the ephemeral timer system <b>202</b> determining that an ephemeral message group <b>504</b> has expired (e.g., is no longer accessible), the ephemeral timer system <b>202</b> communicates with the messaging system <b>100</b> (and, for example, specifically the messaging client <b>104</b>) to cause an indicium (e.g., an icon) associated with the relevant ephemeral message group <b>504</b> to no longer be displayed within a user interface of the messaging client <b>104</b>. Similarly, when the ephemeral timer system <b>202</b> determines that the message duration parameter <b>506</b> for a particular ephemeral message <b>502</b> has expired, the ephemeral timer system <b>202</b> causes the messaging client <b>104</b> to no longer display an indicium (e.g., an icon or textual identification) associated with the ephemeral message <b>502</b>.
0110Location-Based Media Content Collection System
0111<figref idref="DRAWINGS">FIG. <b>6</b></figref> illustrates a flowchart of a process for generating a location-based media content collection in accordance with some examples. While certain operations of the method <b>600</b> are described as being performed by certain devices, in different examples, different devices or a combination of devices may perform these operations. For example, operations described below as being performed by the client device <b>102</b> may also be performed by or in combination with server-side computing device (e.g., the messaging server system <b>108</b>), or third-party server computing device.
0112The method commences with operation <b>602</b>, during which the client device <b>102</b> receives a set of media content items that include a media content item having a geohash. In one example, the media content items are captured by the client device <b>102</b> and retrieved from memory of the client device <b>102</b>. The media content item includes an ephemeral (e.g., as a limited accessibility time window) or non-ephemeral video, photo, audio file, image, augmented reality (AR) image transformation, augmented reality content item, AR media content item, or three-dimensional object. The geohash represents longitude and latitude coordinates of a geographic location on a map (e.g., map interface) associated with a captured time and captured location data of the media content item. The captured time represents a time at which the media content was captured and stored by a computing device, such as, client device <b>102</b>. In one example, the time corresponds to the date, year, month, hour, minute, or second in which the media content item was captured or stored by the computing device.
0113In operation <b>604</b>, client device <b>102</b> identifies a first subset of media content items from the plurality of media content items that each include a geohash that exceed or equal a precision level threshold. In one example, a geohash associated with a In another example, in order to identify the first subset of media content items that each include a geohash that falls within a precision level threshold (e.g., a date range in days, weeks, months, or years in which the media content items were captured and stored on the user's computing device.), the client device <b>102</b> analyzes and compares the captured time and captured location associated with each geohash against the precision level threshold and determines the media content items that contain the a captured time and captured location that fall within a predetermined time. If there is a match (e.g., geohashes fall within the precision level threshold) the media content items are grouped or associated with each other and determined to correspond to a domicile geolocation.
0114In operation <b>606</b>, client device <b>102</b> identifies a second subset of media content items from the plurality of media content items that includes a geohash that is below the precision level threshold. For example, in order to identify the second subset of media content items that include a geohash that is below the precision threshold, the client device <b>102</b> analyzes and compares the captured time and captured location associated with each geohash against the precision level threshold and determines whether the captured time and captured location associated with a geohash exceeds or falls below the precision level threshold. If the captured time and captured location for a media content item exceeds precision level threshold or the captured time and location of a media content item falls below the precision level threshold, the client device <b>102</b> groups each media content item into a second subset of media content items and associates the second subset of media content items with a trip geolocation displayed on a map interface from the map system <b>210</b>. The second subset of media content items can be associated with a trip geolocation displayed on the map interface based on the geohash being less than the precision level threshold. The trip geolocation represents a radius of another geolocation that is different than the first radius of an area on the map interface. For instance, the trip geolocation represents a temporary geolocation or destination associated with the client device <b>102</b>, such as a vacationing location versus a home location associated with the first radius of an area.
0115For example, the precision level threshold represents the captured time and captured location of media content items that were captured and stored across a predetermined amount of separate days, such as May 10, 2003 through Aug. 10, 2003 in Columbia, South Carolina. The client device <b>102</b> analyzes and compares each media content item's geohash against the precision level threshold “May 10, 2003 through Aug. 10, 2003 in Columbia, South Carolina” to determine which media content items were captured after the capture time period of the precision level threshold (e.g., exceed) during the capture time of the precision level threshold (e.g., match/equaling), or before the capture time of the precision level threshold (e.g., falls below) and have a capture location in Columbia, South Carolina. The media content items that are determined to contain a geohash that equal the captured time and captured location of the precision level threshold) are grouped as a first subset of media content items. The media content items that are determined to contain a geohash that either exceeds or falls below the captured time and captured location of May 10, 2003-Aug. 10, 2003 of the precision level threshold are grouped as a second subset of media content items. In one example, the media content items that are determined to contain a geohash associated with the prior home location of the user is compared against all captured media content associated with the user. If a distance (e.g., longitude and latitude) between each captured geohash associated with the prior home location is greater than the precision level threshold, the associated media content identified is considered to be a vacation destination or a “trip”.
0116In one example, the precision level threshold includes a range, a value, or set of values that define longitude and latitude coordinates for a geolocation where media content items were captured and stored based on a predetermined time period and a predetermined geolocation associated with the user of the client device <b>102</b>. The predetermined time period can include a day or multiple-day range, a week range, a month range, or a year range. The predetermined geolocation represents a waypoint, region of interest, point of interest, distance, radius, or proximity displayed on a map interface associated with the client device <b>102</b>, third party computing device, or third-party server system. In another example, the captured time data includes month information, date information, year information, or time information representing when the media content item was captured and stored by a computing device, and the captured location includes any type of geolocation information that is rendered on a map interface representing where the media content item was captured by a computing device or client device <b>102</b>.
0117In operation <b>608</b>, client device <b>102</b> determines that the first subset of media content items is associated with a domicile geolocation displayed on the map interface based on the geohash exceeding (in some examples, equaling) the precision level threshold. The domicile geolocation defines a first radius of a first area on the map interface. In one example, the domicile geolocation represents a prior or present home location associated with the user of the client device <b>102</b>. In one example, the home location is a geolocation that the user considers or previously considered his or her permanent residence during a predetermined time period. The domicile geolocation is displayed and rendered on a map interface, such as the map interface determined by the map system <b>210</b>. The first radius represents an area, region, space, or geolocation on the map interface in which the domicile geolocation is, or has been, established.
0118In operation <b>610</b>, client device <b>102</b> generates a timeline media content item collection comprising the second subset of media content items including a geohash that is outside, beside, adjacent to or within a distance function of the domicile geolocation. For example, the distance function represents distance ratio variables, such as mile-by-mile, meter-by-meter, or the like immediately besides, adjacent to, or within the geohash. The client device <b>102</b> determines those media content items of the second subset of media content items that have a captured location in the geohash that is outside of the domicile geolocation. For instance, when the geohash includes longitude and latitude geolocation information that is outside of a designated radius of the domicile geolocation.
0119In operation <b>612</b>, the client device <b>102</b> causes display of a media content collection interface. The media content collection interface includes the media content items of the timeline media content item collection. In one example, the timeline media content item collection is presented in a gallery style format and be arranged in a polygonal array, circular array, or interactive media content item arrangement.
0120<figref idref="DRAWINGS">FIG. <b>7</b></figref> illustrates an example user interface <b>700</b> of a location-based timeline content collection in accordance with one embodiment. The user interface <b>700</b>, is displayed on a mobile computing device, such as client device <b>102</b>, and depicts a display timeline media content item collection interface <b>702</b> comprising a timeline media content item collection as described above in operation <b>612</b>. The timeline media content item collection interface <b>702</b> is generated at the mobile computing device and includes a map interface <b>704</b>, an avatar depicting a trip geolocation <b>708</b>, an avatar depicting a domicile geolocation <b>710</b>, and a timeline media content item collection, such as comprising second subset of media content items <b>706</b>, as described above. The map interface <b>704</b> represents geolocation and geographic location functions, and supports the presentation of map-based media content items and messages by the messaging client <b>104</b>.
0121In one example, the map interface <b>704</b> displays an avatar or media overlay representing user associated with the user profile of client device <b>102</b>. For example, the map system <b>210</b> enables the display of user icons or avatars (e.g., stored in profile data <b>316</b>) on a map to indicate a present or prior home geolocation, domicile geolocation, or trip geolocation <b>708</b> in which media content items were captured and stored by client device <b>102</b>. In another example, the map interface <b>704</b> displays past location of “friends” of a user, as well as media content items (e.g., collections of messages including photographs and videos) generated by such friends, within the context of a map. A user can furthermore share his or her location and status information (e.g., using an appropriate status avatar) with other users of the messaging system <b>100</b> via the messaging client <b>104</b>, with this location and status information being similarly displayed within the context of a map interface of the messaging client <b>104</b> to selected users.
0122In another example, the second subset of media content items <b>706</b> represent photos, videos, and images that were captured and stored while the user of the client device <b>102</b> was located within the trip geolocation <b>708</b>. As shown in <figref idref="DRAWINGS">FIG. <b>7</b></figref>, the domicile geolocation <b>710</b> is known and utilized in order to determine media content items that exceed or fall below the precision level threshold, as explained above. In one example, the domicile geolocation <b>710</b> is the present home location of the user associated with the user profile of the client device <b>102</b>. In the example in <figref idref="DRAWINGS">FIG. <b>7</b></figref>, the precision level threshold <b>712</b> comprises a period of time representing Apr. 26-May 2, 2020 and a location representing the trip to Barcelona.
0123<figref idref="DRAWINGS">FIG. <b>8</b></figref> illustrates an example user interface <b>700</b> including an extended portion of the location-based timeline content collection shown in <figref idref="DRAWINGS">FIG. <b>7</b></figref>, in accordance with one embodiment. The user interface <b>800</b>, is displayed on a mobile computing device, such as client device <b>102</b>, and depicts the timeline media content item collection interface <b>702</b>. The timeline media content item collection interface <b>702</b> includes a thumbnail <b>804</b> representing the second media content items <b>706</b> displayed in <figref idref="DRAWINGS">FIG. <b>7</b></figref>. The timeline media content item collection interface <b>702</b> in <figref idref="DRAWINGS">FIG. <b>8</b></figref> also illustrates the precision level threshold <b>712</b> which represents the period of time representing Apr. 26-May 2, 2020 in Barcelona.
0124In another example, the first subset of media content items <b>802</b> represent photos, videos, and images that were captured and stored while the user of the client device <b>102</b> was located within a domicile geolocation <b>710</b> as shown in <figref idref="DRAWINGS">FIG. <b>7</b></figref>. The domicile geolocation <b>710</b> is known and utilized in order to determine media content items that exceed or fall below the precision level threshold. In one example, the domicile geolocation (e.g., present home location) <b>710</b> is the present home location of the user associated with the user profile of the client device <b>102</b>.
0125Machine Architecture
0126<figref idref="DRAWINGS">FIG. <b>9</b></figref> is a diagrammatic representation of the machine <b>900</b> within which instructions <b>910</b> (e.g., software, a program, an application, an applet, an app, or other executable code) for causing the machine <b>900</b> to perform any one or more of the methodologies discussed herein may be executed. For example, the instructions <b>910</b> may cause the machine <b>900</b> to execute any one or more of the methods described herein. The instructions <b>910</b> transform the general, non-programmed machine <b>900</b> into a particular machine <b>900</b> programmed to carry out the described and illustrated functions in the manner described. The machine <b>900</b> may operate as a standalone device or may be coupled (e.g., networked) to other machines. In a networked deployment, the machine <b>900</b> 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 <b>900</b> 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 smartphone, a mobile device, a wearable device (e.g., a smartwatch), 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 <b>910</b>, sequentially or otherwise, that specify actions to be taken by the machine <b>900</b>. Further, while only a single machine <b>900</b> is illustrated, the term “machine” shall also be taken to include a collection of machines that individually or jointly execute the instructions <b>910</b> to perform any one or more of the methodologies discussed herein. The machine <b>900</b>, for example, may comprise the client device <b>102</b> or any one of a number of server devices forming part of the messaging server system <b>108</b>. In some examples, the machine <b>900</b> may also comprise both client and server systems, with certain operations of a particular method or algorithm being performed on the server-side and with certain operations of the particular method or algorithm being performed on the client-side.
0127The machine <b>900</b> may include processors <b>904</b>, memory <b>906</b>, and input/output I/O components <b>902</b>, which may be configured to communicate with each other via a bus <b>940</b>. In an example, the processors <b>904</b> (e.g., a Central Processing Unit (CPU), a Reduced Instruction Set Computing (RISC) Processor, a Complex Instruction Set Computing (CISC) Processor, a Graphics Processing Unit (GPU), a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Radio-Frequency Integrated Circuit (RFIC), another processor, or any suitable combination thereof) may include, for example, a processor <b>908</b> and a processor <b>912</b> that execute the instructions <b>910</b>. The term “processor” is intended to include multi-core processors that may comprise two or more independent processors (sometimes referred to as “cores”) that may execute instructions contemporaneously. Although <figref idref="DRAWINGS">FIG. <b>9</b></figref> shows multiple processors <b>904</b>, the machine <b>900</b> may include a single processor with a single-core, a single processor with multiple cores (e.g., a multi-core processor), multiple processors with a single core, multiple processors with multiples cores, or any combination thereof.
0128The memory <b>906</b> includes a main memory <b>914</b>, a static memory <b>916</b>, and a storage unit <b>918</b>, both accessible to the processors <b>904</b> via the bus <b>940</b>. The main memory <b>906</b>, the static memory <b>916</b>, and storage unit <b>918</b> store the instructions <b>910</b> embodying any one or more of the methodologies or functions described herein. The instructions <b>910</b> may also reside, completely or partially, within the main memory <b>914</b>, within the static memory <b>916</b>, within machine-readable medium <b>920</b> within the storage unit <b>918</b>, within at least one of the processors <b>904</b> (e.g., within the Processor's cache memory), or any suitable combination thereof, during execution thereof by the machine <b>900</b>.
0129The I/O components <b>902</b> 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 <b>902</b> that are included in a particular machine will depend on the type of machine. For example, portable machines such as mobile phones may 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 <b>902</b> may include many other components that are not shown in <figref idref="DRAWINGS">FIG. <b>9</b></figref>. In various examples, the I/O components <b>902</b> may include user output components <b>926</b> and user input components <b>928</b>. The user output components <b>926</b> 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 user input components <b>928</b> may include alphanumeric input components (e.g., a keyboard, a touch screen configured to receive alphanumeric input, a photo-optical keyboard, or other alphanumeric input components), point-based input components (e.g., a mouse, a touchpad, a trackball, a joystick, a motion sensor, or another pointing instrument), tactile input components (e.g., a physical button, a touch screen that provides location and force of touches or touch gestures, or other tactile input components), audio input components (e.g., a microphone), and the like.
0130In further examples, the I/O components <b>902</b> may include biometric components <b>930</b>, motion components <b>932</b>, environmental components <b>934</b>, or position components <b>936</b>, among a wide array of other components. For example, the biometric components <b>930</b> 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 <b>932</b> include acceleration sensor components (e.g., accelerometer), gravitation sensor components, rotation sensor components (e.g., gyroscope).
0131The environmental components <b>934</b> include, for example, one or cameras (with still image/photograph and video capabilities), 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 detection sensors to detection concentrations of hazardous gases for safety or to measure pollutants in the atmosphere), or other components that may provide indications, measurements, or signals corresponding to a surrounding physical environment.
0132With respect to cameras, the client device <b>102</b> may have a camera system comprising, for example, front cameras on a front surface of the client device <b>102</b> and rear cameras on a rear surface of the client device <b>102</b>. The front cameras may, for example, be used to capture still images and video of a user of the client device <b>102</b> (e.g., “selfies”), which may then be augmented with augmentation data (e.g., filters) described above. The rear cameras may, for example, be used to capture still images and videos in a more traditional camera mode, with these images similarly being augmented with augmentation data. In addition to front and rear cameras, the client device <b>102</b> may also include a 360° camera for capturing 360° photographs and videos.
0133Further, the camera system of a client device <b>102</b> may include dual rear cameras (e.g., a primary camera as well as a depth-sensing camera), or even triple, quad or penta rear camera configurations on the front and rear sides of the client device <b>102</b>. These multiple cameras systems may include a wide camera, an ultra-wide camera, a telephoto camera, a macro camera and a depth sensor, for example.
0134The position components <b>936</b> include location sensor components (e.g., a 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.
0135Communication may be implemented using a wide variety of technologies. The I/O components <b>902</b> further include communication components <b>938</b> operable to couple the machine <b>900</b> to a network <b>922</b> or devices <b>924</b> via respective coupling or connections. For example, the communication components <b>938</b> may include a network interface Component or another suitable device to interface with the network <b>922</b>. In further examples, the communication components <b>938</b> 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 <b>924</b> may be another machine or any of a wide variety of peripheral devices (e.g., a peripheral device coupled via a USB).
0136Moreover, the communication components <b>938</b> may detect identifiers or include components operable to detect identifiers. For example, the communication components <b>938</b> 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 <b>938</b>, 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.
0137The various memories (e.g., main memory <b>914</b>, static memory <b>916</b>, and memory of the processors <b>904</b>) and storage unit <b>918</b> may store one or more sets of instructions and data structures (e.g., software) embodying or used by any one or more of the methodologies or functions described herein. These instructions (e.g., the instructions <b>910</b>), when executed by processors <b>904</b>, cause various operations to implement the disclosed examples.
0138The instructions <b>910</b> may be transmitted or received over the network <b>922</b>, using a transmission medium, via a network interface device (e.g., a network interface component included in the communication components <b>938</b>) and using any one of several well-known transfer protocols (e.g., hypertext transfer protocol (HTTP)). Similarly, the instructions <b>910</b> may be transmitted or received using a transmission medium via a coupling (e.g., a peer-to-peer coupling) to the devices <b>924</b>.
0139Software Architecture
0140<figref idref="DRAWINGS">FIG. <b>10</b></figref> is a block diagram <b>1000</b> illustrating a software architecture <b>1004</b>, which can be installed on any one or more of the devices described herein. The software architecture <b>1004</b> is supported by hardware such as a machine <b>1002</b> that includes processors <b>1020</b>, memory <b>1026</b>, and I/O components <b>1038</b>. In this example, the software architecture <b>1004</b> can be conceptualized as a stack of layers, where each layer provides a particular functionality. The software architecture <b>1004</b> includes layers such as an operating system <b>1012</b>, libraries <b>1010</b>, frameworks <b>1008</b>, and applications <b>1006</b>. Operationally, the applications <b>1006</b> invoke API calls <b>1050</b> through the software stack and receive messages <b>1052</b> in response to the API calls <b>1050</b>.
0141The operating system <b>1012</b> manages hardware resources and provides common services. The operating system <b>1012</b> includes, for example, a kernel <b>1014</b>, services <b>1016</b>, and drivers <b>1022</b>. The kernel <b>1014</b> acts as an abstraction layer between the hardware and the other software layers. For example, the kernel <b>1014</b> provides memory management, processor management (e.g., scheduling), component management, networking, and security settings, among other functionality. The services <b>1016</b> can provide other common services for the other software layers. The drivers <b>1022</b> are responsible for controlling or interfacing with the underlying hardware. For instance, the drivers <b>1022</b> can include display drivers, camera drivers, BLUETOOTH® or BLUETOOTH® Low Energy drivers, flash memory drivers, serial communication drivers (e.g., USB drivers), WI-FI® drivers, audio drivers, power management drivers, and so forth.
0142The libraries <b>1010</b> provide a common low-level infrastructure used by the applications <b>1006</b>. The libraries <b>1010</b> can include system libraries <b>1018</b> (e.g., C standard library) that provide functions such as memory allocation functions, string manipulation functions, mathematic functions, and the like. In addition, the libraries <b>1010</b> can include API libraries <b>1024</b> such as media libraries (e.g., libraries to support presentation and manipulation of various media formats such as Moving Picture Experts Group-4 (MPEG4), Advanced Video Coding (H.264 or AVC), Moving Picture Experts Group Layer-3 (MP3), Advanced Audio Coding (AAC), Adaptive Multi-Rate (AMR) audio codec, Joint Photographic Experts Group (JPEG or JPG), or Portable Network Graphics (PNG)), graphics libraries (e.g., an OpenGL framework used to render in two dimensions (2D) and three dimensions (3D) in a graphic content on a display), database libraries (e.g., SQLite to provide various relational database functions), web libraries (e.g., WebKit to provide web browsing functionality), and the like. The libraries <b>1010</b> can also include a wide variety of other libraries <b>1028</b> to provide many other APIs to the applications <b>1006</b>.
0143The frameworks <b>1008</b> provide a common high-level infrastructure that is used by the applications <b>1006</b>. For example, the frameworks <b>1008</b> provide various graphical user interface (GUI) functions, high-level resource management, and high-level location services. The frameworks <b>1008</b> can provide a broad spectrum of other APIs that can be used by the applications <b>1006</b>, some of which may be specific to a particular operating system or platform.
0144In an example, the applications <b>1006</b> may include a home application <b>1036</b>, a contacts application <b>1030</b>, a browser application <b>1032</b>, a book reader application <b>1034</b>, a location application <b>1042</b>, a media application <b>1044</b>, a messaging application <b>1046</b>, a game application <b>1048</b>, and a broad assortment of other applications such as a third-party application <b>1040</b>. The applications <b>1006</b> are programs that execute functions defined in the programs. Various programming languages can be employed to create one or more of the applications <b>1006</b>, structured in a variety of manners, such as object-oriented programming languages (e.g., Objective-C, Java, or C++) or procedural programming languages (e.g., C or assembly language). In a specific example, the third-party application <b>1040</b> (e.g., an application developed using the ANDROID™ or IOS™ software development kit (SDK) by an entity other than the vendor of the particular platform) may be mobile software running on a mobile operating system such as IOS™, ANDROID™, WINDOWS® Phone, or another mobile operating system. In this example, the third-party application <b>1040</b> can invoke the API calls <b>1050</b> provided by the operating system <b>1012</b> to facilitate functionality described herein.
0145Processing Components
0146Turning now to <figref idref="DRAWINGS">FIG. <b>11</b></figref>, there is shown a diagrammatic representation of a processing environment <b>1100</b>, which includes a processor <b>1102</b>, a processor <b>1106</b>, and a processor <b>1108</b> (e.g., a GPU, CPU or combination thereof).
0147The processor <b>1102</b> is shown to be coupled to a power source <b>1104</b>, and to include (either permanently configured or temporarily instantiated) modules, namely a location-based timeline <b>1110</b>. The location-based timeline <b>1110</b> operationally receives a plurality of media content items that include a media content item having a geohash, the geohash defining a longitude and latitude geographic location on a map interface associated with a captured time and a captured location of the media content item; identifies a first subset of media content items from the plurality of media content items comprising a geohash that equals a precision level threshold; identifies a second subset of media content items from the plurality of media content items that comprises a geohash that exceeds the precisions level threshold, identifies that the first subset of media content items is associated with a domicile geolocation on the map interface based on the geohash equaling the precision level threshold, the domicile geolocation defining a first radius of a first area on the map interface, generates a timeline media content item collection comprising the second subset of media content items comprising the geohash that exceeds the precisions level threshold; and causes display of a media content collection interface, the media content collection interface comprising the timeline media content item collection. As illustrated, the processor <b>1102</b> is communicatively coupled to both the processor <b>1106</b> and the processor <b>1108</b>.
0148Glossary
0149“Carrier signal” 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 a network using a transmission medium via a network interface device.
0150“Client device” 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 assistants (PDAs), smartphones, tablets, ultrabooks, netbooks, laptops, multi-processor systems, microprocessor-based or programmable consumer electronics, game consoles, set-top boxes, or any other communication device that a user may use to access a network.
0151“Communication network” 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 other types of cellular or wireless coupling. In this example, the coupling may implement any of a variety of types of data transfer technology, such as Single Carrier Radio Transmission Technology (1xRTT), Evolution-Data Optimized (EVDO) technology, General Packet Radio Service (GPRS) technology, Enhanced Data rates for GSM Evolution (EDGE) technology, third Generation Partnership Project (3GPP) including 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.
0152“Component” refers to a device, physical entity, or logic having boundaries defined by function or subroutine calls, branch points, 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 examples, 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 examples in which hardware components are temporarily configured (e.g., programmed), each of the hardware components need not be configured or instantiated at any one instance in time. For example, where a hardware component comprises a general-purpose processor configured by software to become a special-purpose processor, the general-purpose processor may be configured as respectively different special-purpose processors (e.g., comprising different hardware components) at different times. Software accordingly configures a particular processor or processors, for example, to constitute a particular hardware component at one instance of time and to constitute a different hardware component at a different instance of time. Hardware components can provide information to, and receive information from, other hardware components. Accordingly, the described hardware components may be regarded as being communicatively coupled. Where multiple hardware components exist contemporaneously, communications may be achieved through signal transmission (e.g., over appropriate circuits and buses) between or among two or more of the hardware components. In examples 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 <b>1004</b> 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 API). The performance of certain of the operations may be distributed among the processors, not only residing within a single machine, but deployed across a number of machines. In some examples, 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 examples, the processors or processor-implemented components may be distributed across a number of geographic locations.
0153“Computer-readable storage medium” refers to both machine-storage media and transmission media. Thus, the terms include both storage devices/media and carrier waves/modulated data signals. The terms “machine-readable medium,” “computer-readable medium” and “device-readable medium” mean the same thing and may be used interchangeably in this disclosure.
0154“Ephemeral message” 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.
0155“Machine storage medium” refers to a single or multiple storage devices and media (e.g., a centralized or distributed database, and associated caches and servers) that store executable instructions, routines and data. The term shall accordingly be taken to include, but not be limited to, solid-state memories, and optical and magnetic media, including memory internal or external to processors. Specific examples of machine-storage media, computer-storage media and device-storage media include non-volatile memory, including by way of example semiconductor memory devices, e.g., erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), FPGA, and flash memory devices; magnetic disks such as internal hard disks and removable disks; magneto-optical disks; and CD-ROM and DVD-ROM disks The terms “machine-storage medium,” “device-storage medium,” “computer-storage medium” mean the same thing and may be used interchangeably in this disclosure. The terms “machine-storage media,” “computer-storage media,” and “device-storage media” specifically exclude carrier waves, modulated data signals, and other such media, at least some of which are covered under the term “signal medium.”
0156“Non-transitory computer-readable storage medium” refers to a tangible medium that is capable of storing, encoding, or carrying the instructions for execution by a machine.
0157“Signal medium” refers to any intangible medium that is capable of storing, encoding, or carrying the instructions for execution by a machine and includes digital or analog communications signals or other intangible media to facilitate communication of software or data. The term “signal medium” shall be taken to include any form of a modulated data signal, carrier wave, and so forth. The term “modulated data signal” means a signal that has one or more of its characteristics set or changed in such a matter as to encode information in the signal. The terms “transmission medium” and “signal medium” mean the same thing and may be used interchangeably in this disclosure.
Contents4
12 sheets
Sheet 1 Sheet 2 Sheet 3 Sheet 4 Sheet 5 Sheet 6 Sheet 7 Sheet 8 Sheet 9 Sheet 10 Sheet 11 Sheet 12
Every citation, both waysCites: the store holds 1,000 of 1,049
| Document | Relation | Office | Cited during |
|---|---|---|---|
| WO0058882A1 | Cites | World Intellectual Property Organization (WIPO) | Applicant |
| WO0129642A1 | Cites | World Intellectual Property Organization (WIPO) | Applicant |
| WO0150703A2 | Cites | World Intellectual Property Organization (WIPO) | Applicant |
| US10521472B2 | Cites | United States of America | Applicant |
| US10614114B1 | Cites | United States of America | Applicant |
| KR19990073076A | Cites | Republic of Korea | Applicant |
| KR20010078417A | Cites | Republic of Korea | Applicant |
| US2002047868A1 | Cites | United States of America | Applicant |
| US2002078456A1 | Cites | United States of America | Applicant |
| US2002087631A1 | Cites | United States of America | Applicant |
| US2002097257A1 | Cites | United States of America | Applicant |
| US2002122659A1 | Cites | United States of America | Applicant |
| US2002128047A1 | Cites | United States of America | Applicant |
| US2002144154A1 | Cites | United States of America | Applicant |
| US2003001846A1 | Cites | United States of America | Applicant |
| US2003016247A1 | Cites | United States of America | Applicant |
| US2003017823A1 | Cites | United States of America | Applicant |
| US2003020623A1 | Cites | United States of America | Applicant |
| US2003023874A1 | Cites | United States of America | Applicant |
| US2003037124A1 | Cites | United States of America | Applicant |
| US2003052925A1 | Cites | United States of America | Applicant |
| US2003101230A1 | Cites | United States of America | Applicant |
| US2003110503A1 | Cites | United States of America | Applicant |
| US2003126215A1 | Cites | United States of America | Applicant |
| US2003148773A1 | Cites | United States of America | Applicant |
| US2003164856A1 | Cites | United States of America | Applicant |
| US2003229607A1 | Cites | United States of America | Applicant |
| US2004027371A1 | Cites | United States of America | Applicant |
| US2004064429A1 | Cites | United States of America | Applicant |
| US2004078367A1 | Cites | United States of America | Applicant |
| US2004111467A1 | Cites | United States of America | Applicant |
| US2004158739A1 | Cites | United States of America | Applicant |
| US2004189465A1 | Cites | United States of America | Applicant |
| US2004203959A1 | Cites | United States of America | Applicant |
| US2004215625A1 | Cites | United States of America | Applicant |
| US2004243531A1 | Cites | United States of America | Applicant |
| US2004243688A1 | Cites | United States of America | Applicant |
| US2005021444A1 | Cites | United States of America | Applicant |
| US2005022211A1 | Cites | United States of America | Applicant |
| US2005048989A1 | Cites | United States of America | Applicant |
| US2005078804A1 | Cites | United States of America | Applicant |
| US2005097176A1 | Cites | United States of America | Applicant |
| US2005102381A1 | Cites | United States of America | Applicant |
| US2005104976A1 | Cites | United States of America | Applicant |
| US2005114783A1 | Cites | United States of America | Applicant |
| US2005119936A1 | Cites | United States of America | Applicant |
| US2005122405A1 | Cites | United States of America | Applicant |
| US2005193340A1 | Cites | United States of America | Applicant |
| US2005193345A1 | Cites | United States of America | Applicant |
| US2005198128A1 | Cites | United States of America | Applicant |
| US2005223066A1 | Cites | United States of America | Applicant |
| US2005288954A1 | Cites | United States of America | Applicant |
| US2006026067A1 | Cites | United States of America | Applicant |
| US2006107297A1 | Cites | United States of America | Applicant |
| US2006114338A1 | Cites | United States of America | Applicant |
| WO2006118755A2 | Cites | World Intellectual Property Organization (WIPO) | Applicant |
| US2006119882A1 | Cites | United States of America | Applicant |
| US2006242239A1 | Cites | United States of America | Applicant |
| US2006252438A1 | Cites | United States of America | Applicant |
| US2006265417A1 | Cites | United States of America | Applicant |
| US2006270419A1 | Cites | United States of America | Applicant |
| US2006287878A1 | Cites | United States of America | Applicant |
| US2007004426A1 | Cites | United States of America | Applicant |
| US2007038715A1 | Cites | United States of America | Applicant |
| US2007040931A1 | Cites | United States of America | Applicant |
| US2007073517A1 | Cites | United States of America | Applicant |
| US2007073823A1 | Cites | United States of America | Applicant |
| US2007075898A1 | Cites | United States of America | Applicant |
| US2007082707A1 | Cites | United States of America | Applicant |
| WO2007092668A2 | Cites | World Intellectual Property Organization (WIPO) | Applicant |
| US2007136228A1 | Cites | United States of America | Applicant |
| US2007192128A1 | Cites | United States of America | Applicant |
| US2007198340A1 | Cites | United States of America | Applicant |
| US2007198495A1 | Cites | United States of America | Applicant |
| US2007208751A1 | Cites | United States of America | Applicant |
| US2007210936A1 | Cites | United States of America | Applicant |
| US2007214180A1 | Cites | United States of America | Applicant |
| US2007214216A1 | Cites | United States of America | Applicant |
| US2007233556A1 | Cites | United States of America | Applicant |
| US2007233801A1 | Cites | United States of America | Applicant |
| US2007233859A1 | Cites | United States of America | Applicant |
| US2007243887A1 | Cites | United States of America | Applicant |
| US2007244750A1 | Cites | United States of America | Applicant |
| US2007255456A1 | Cites | United States of America | Applicant |
| US2007281690A1 | Cites | United States of America | Applicant |
| US2008022329A1 | Cites | United States of America | Applicant |
| US2008025701A1 | Cites | United States of America | Applicant |
| US2008032703A1 | Cites | United States of America | Applicant |
| US2008033930A1 | Cites | United States of America | Applicant |
| US2008043041A2 | Cites | United States of America | Applicant |
| US2008049704A1 | Cites | United States of America | Applicant |
| US2008062141A1 | Cites | United States of America | Applicant |
| US2008076505A1 | Cites | United States of America | Applicant |
| US2008092233A1 | Cites | United States of America | Applicant |
| US2008094387A1 | Cites | United States of America | Applicant |
| US2008104503A1 | Cites | United States of America | Applicant |
| US2008109844A1 | Cites | United States of America | Applicant |
| US2008120409A1 | Cites | United States of America | Applicant |
| US2008147730A1 | Cites | United States of America | Applicant |
| US2008148150A1 | Cites | United States of America | Applicant |
4 members in 1 office
Members4
| Document | Office | Kind | |
|---|---|---|---|
| US2022318293A1 | United States of America | A1 | |
| US11645324B2 | United States of America | B2 | |
| US2023273950A1 | United States of America | A1 | |
| US12455917B2This record | United States of America | B2 |
73 transactions on the USPTO file
Allowed after 2 non-final rejections, 1 final rejection and 1 RCE.
- Non-final rejections
- 2
- Final rejections
- 1
- RCEs
- 1
- Appeals
- 0
Over time
Point at a mark for the transactionTransactions
| Event | Code | |
|---|---|---|
| Recordation of Patent Grant MailedPGM/ | PGM/ | |
| Email NotificationEML_NTR | EML_NTR | |
| Mail Patent eGrant NotificationMEPG_NTF | MEPG_NTF | |
| Patent eGrant NotificationEPG_NTF | EPG_NTF | |
| Recordation of Patent eGrantEPG/ | EPG/ | |
| Patent Issue Date Used in PTA CalculationAllowedPTAC | PTAC | |
| Email NotificationEML_NTR | EML_NTR | |
| Issue Notification MailedAllowedWPIR | WPIR | |
| Dispatch to FDCD1935 | D1935 | |
| Application Is Considered Ready for IssuePILS | PILS | |
| Email NotificationEML_NTR | EML_NTR | |
| Mail Response to 312 Amendment (PTO-271)MN271 | MN271 | |
| Response to Amendment under Rule 312N271 | N271 | |
| Pubs Case Remand to TCPUBTC | PUBTC | |
| Issue Fee Payment ReceivedIFEE | IFEE | |
| Issue Fee Payment VerifiedN084 | N084 | |
| Amendment after Notice of Allowance (Rule 312)AllowedA.NA | A.NA | |
| Email NotificationEML_NTR | EML_NTR | |
| Mail PUB other miscellaneous communication to applicantMM327-D | MM327-D | |
| PUB Other miscellaneous communication to applicantM327-D | M327-D | |
| Mail Notice of AllowanceAllowedMN/=. | MN/=. | |
| Notice of Allowance Data Verification CompletedAllowedN/=. | N/=. | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Paralegal or electronic terminal disclaimer approvedP574 | P574 | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Terminal Disclaimer FiledDIST | DIST | |
| Electronic Information Disclosure StatementEIDS. | EIDS. | |
| terminal disclaimer fee paidTDP | TDP | |
| Response after Non-Final ActionA... | A... | |
| Request for Extension of Time - GrantedXT/G | XT/G | |
| Electronic ReviewELC_RVW | ELC_RVW | |
| Email NotificationEML_NTF | EML_NTF | |
| Mail Non-Final RejectionNon-final rejectionMCTNF | MCTNF | |
| Non-Final RejectionNon-final rejectionCTNF | CTNF | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Disposal for a RCE / CPA / R129AbandonedABN9 | ABN9 | |
| Request for Continued Examination (RCE)RCEX | RCEX | |
| Request for Extension of Time - GrantedXT/G | XT/G | |
| Workflow - Request for RCE - BeginBRCE | BRCE | |
| Email NotificationEML_NTF | EML_NTF | |
| Mail Final Rejection (PTOL - 326)Final rejectionMCTFR | MCTFR | |
| Final RejectionFinal rejectionCTFR | CTFR | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Response after Non-Final ActionA... | A... | |
| Request for Extension of Time - GrantedXT/G | XT/G | |
| Electronic ReviewELC_RVW | ELC_RVW | |
| Electronic ReviewELC_RVW | ELC_RVW | |
| Email NotificationEML_NTF | EML_NTF | |
| Mail Non-Final RejectionNon-final rejectionMCTNF | MCTNF | |
| Email NotificationEML_NTF | EML_NTF | |
| Non-Final RejectionNon-final rejectionCTNF | CTNF | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| Email NotificationEML_NTR | EML_NTR | |
| Application ready for PDX access by participating foreign officesCCRDY | CCRDY | |
| PG-Pub Issue NotificationPG-ISSUE | PG-ISSUE | |
| Electronic ReviewELC_RVW | ELC_RVW | |
| Email NotificationEML_NTR | EML_NTR | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| Application Dispatched from OIPEOIPE | OIPE | |
| Mail Pre-Exam NoticeMPEN | MPEN | |
| Application Is Now CompleteCOMP | COMP | |
| Filing ReceiptFLRCPT.O | FLRCPT.O | |
| Sent to Classification ContractorPGPC | PGPC | |
| FITF set to YES - revise initial settingFTFS | FTFS | |
| Patent Term Adjustment - Ready for ExaminationPTA.RFE | PTA.RFE | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| PTO/SB/69-Authorize EPO Access to Search ResultsSREXR141 | SREXR141 | |
| Applicants have given acceptable permission for participating foreignAPPERMS | APPERMS | |
| Entity Status Set To Undiscounted (Initial Default Setting or Status Change)BIG. | BIG. | |
| Initial Exam Team nnIEXX | IEXX | |
| Patent Term Adjustment - Ready for ExaminationPTA.RFE | PTA.RFE |
15 legal events, as the office reported them to INPADOC
Over the term
Point at a mark for the eventEvents
| Event | Code | |
|---|---|---|
| Information on status: patent grantGrantedPATENTED CASESTCF | STCF | |
| Information on status: patent application and granting procedure in generalPUBLICATIONS -- ISSUE FEE PAYMENT VERIFIEDSTPP | STPP | |
| Information on status: patent application and granting procedure in generalAWAITING TC RESP, ISSUE FEE PAYMENT VERIFIEDSTPP | STPP | |
| Information on status: patent application and granting procedure in generalPUBLICATIONS -- ISSUE FEE PAYMENT VERIFIEDSTPP | STPP | |
| Information on status: patent application and granting procedure in generalPUBLICATIONS -- ISSUE FEE PAYMENT RECEIVEDSTPP | STPP | |
| Information on status: patent application and granting procedure in generalNOTICE OF ALLOWANCE MAILED -- APPLICATION RECEIVED IN OFFICE OF PUBLICATIONSSTPP | STPP | |
| Information on status: patent application and granting procedure in generalNON FINAL ACTION MAILEDSTPP | STPP | |
| Information on status: patent application and granting procedure in generalDOCKETED NEW CASE - READY FOR EXAMINATIONSTPP | STPP | |
| Information on status: patent application and granting procedure in generalFINAL REJECTION MAILEDSTPP | STPP | |
| Information on status: patent application and granting procedure in generalRESPONSE TO NON-FINAL OFFICE ACTION ENTERED AND FORWARDED TO EXAMINERSTPP | STPP | |
| Information on status: patent application and granting procedure in generalNON FINAL ACTION MAILEDSTPP | STPP | |
| Information on status: patent application and granting procedure in generalDOCKETED NEW CASE - READY FOR EXAMINATIONSTPP | STPP | |
| AssignmentAS | AS | |
| AssignmentAS | AS | |
| Fee payment procedureENTITY STATUS SET TO UNDISCOUNTED (ORIGINAL EVENT CODE: BIG.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITYFEPP | FEPP |
Numbers
- Publication
- 12455917
- Application
- 18311679
Titles
- English
- Location-based timeline media content system
Patent term adjustment
- Applicant delay
- −187 days
- Net adjustment
- 0 days
Classification
- CPC, 8
- G06F16/447
- G06F16/487
- G06F16/489
- H04L51/10
- H04W4/029
- H04W4/185
- H04W4/02
- H04L51/222
- IPC, 5
- G06F16 44
- G06F16 48
- G06F16 487
- H04L51 10
- H04W4 029