US20140259113A1 - System and method for targeted messaging, workflow management, and digital rights management for geofeeds - Google Patents
System and method for targeted messaging, workflow management, and digital rights management for geofeeds Download PDFInfo
- Publication number
- US20140259113A1 US20140259113A1 US13/788,909 US201313788909A US2014259113A1 US 20140259113 A1 US20140259113 A1 US 20140259113A1 US 201313788909 A US201313788909 A US 201313788909A US 2014259113 A1 US2014259113 A1 US 2014259113A1
- Authority
- US
- United States
- Prior art keywords
- content
- social media
- users
- content item
- media content
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
- 238000000034 method Methods 0.000 title claims abstract description 91
- 230000008569 process Effects 0.000 claims abstract description 49
- 238000004891 communication Methods 0.000 claims description 35
- 238000012545 processing Methods 0.000 claims description 6
- 230000004931 aggregating effect Effects 0.000 claims description 3
- 238000004590 computer program Methods 0.000 claims 3
- 230000001737 promoting effect Effects 0.000 abstract description 9
- 239000008186 active pharmaceutical agent Substances 0.000 description 7
- 238000013475 authorization Methods 0.000 description 5
- 230000008520 organization Effects 0.000 description 5
- 230000006870 function Effects 0.000 description 4
- 238000012552 review Methods 0.000 description 3
- 230000003993 interaction Effects 0.000 description 2
- 230000010267 cellular communication Effects 0.000 description 1
- 238000010586 diagram Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 238000001914 filtration Methods 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 239000000463 material Substances 0.000 description 1
- 238000012544 monitoring process Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000002093 peripheral effect Effects 0.000 description 1
- 230000004044 response Effects 0.000 description 1
- 238000013518 transcription Methods 0.000 description 1
- 230000035897 transcription Effects 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/10—Network architectures or network communication protocols for network security for controlling access to devices or network resources
- H04L63/107—Network architectures or network communication protocols for network security for controlling access to devices or network resources wherein the security policies are location-dependent, e.g. entities privileges depend on current location or allowing specific operations only from locally connected terminals
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
- H04L51/21—Monitoring or handling of messages
- H04L51/214—Monitoring or handling of messages using selective forwarding
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/29—Geographical information databases
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/10—Protecting distributed programs or content, e.g. vending or licensing of copyrighted material ; Digital rights management [DRM]
- G06F21/105—Arrangements for software license management or administration, e.g. for managing licenses at corporate level
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/60—Protecting data
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
- H04L51/04—Real-time or near real-time messaging, e.g. instant messaging [IM]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/10—Network architectures or network communication protocols for network security for controlling access to devices or network resources
- H04L63/101—Access control lists [ACL]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/18—Information format or content conversion, e.g. adaptation by the network of the transmitted or received information for the purpose of wireless delivery to users or terminals
- H04W4/185—Information format or content conversion, e.g. adaptation by the network of the transmitted or received information for the purpose of wireless delivery to users or terminals by embedding added-value information into content, e.g. geo-tagging
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/10—Protecting distributed programs or content, e.g. vending or licensing of copyrighted material ; Digital rights management [DRM]
- G06F21/107—License processing; Key processing
- G06F21/1078—Logging; Metering
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L2463/00—Additional details relating to network architectures or network communication protocols for network security covered by H04L63/00
- H04L2463/101—Additional details relating to network architectures or network communication protocols for network security covered by H04L63/00 applying security measures for digital rights management
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
- H04L51/52—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail for supporting social networking services
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/10—Network architectures or network communication protocols for network security for controlling access to devices or network resources
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/55—Push-based network services
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/12—Messaging; Mailboxes; Announcements
Definitions
- the disclosure relates to systems and methods for targeted messaging, workflow management, and digital rights management for geofeeds, including content that is related to geographically definable locations and aggregated from a plurality of social media or other content providers.
- the disclosure relates to systems and methods for targeted messaging, workflow management, and digital rights management for geofeeds, including content that is related to geographically definable locations (“geo-locations”) and aggregated from a plurality of social media or other content providers.
- a geofeed may include content that is aggregated from a plurality of content providers using respective requests formatted specifically for individual ones of the plurality of content providers, where an individual set of a plurality of content is relevant to one or more geo-locations.
- the system may facilitate targeted messaging to users who create content.
- the targeted messages may include, for example, messages to obtain permission to use content from an owner of the content, messages to request additional information about a breaking news event, messages to seek further information about an experience, messages to obtain a following on TWITTER for one-on-one communications, messages that offer a promotion or coupon, and/or other types of messages.
- the system may generate workflows that allow management of the content with respect to one or more operational processes of an entity such as a user, an organization, and/or other entity that wishes to use the content.
- the workflows allow creation and tracking of workflow items to be performed with respect to the content, thereby allowing the entity to manage and integrate the content with its own assets such as a website, a mobile application, and/or other asset.
- the system facilitates the management of usage rights related to the content. For example, the system may store whether content requires permission to use the content and/or whether such permission was obtained. By doing so, the system may facilitate a database of content that has been permitted to be used.
- the system may leverage permission information, geo-location information associated with the content, keyword information, and/or other information known by the system to build a robust and searchable clearinghouse database of content that may be permissibly used and/or licensed to others. For example, a news agency or others who wish to obtain content such as photographs related to a particular geo-location may obtain such content from the clearinghouse database. Thus, content related to rioting in a particular geo-location and obtained from social media and other providers may be found and/or licensed for use from the clearinghouse database.
- the system may facilitate various requirements that are to be satisfied in order to use the content. For example, the system may facilitate payment of royalty or other fees, attribution notices, and/or other requirements that are to be satisfied to use the content.
- the system may include a computer that includes one or more processors configured to perform some or all of a functionality of a plurality of modules.
- the one or more processors may be configured to execute a geofeed creation module, a unified message module, a workflow module, a clearinghouse module, an administration module, a communication module, a user interface module, and/or other modules.
- the geofeed creation module may be configured to receive a request to create a geofeed based on a specification of one or more geo-locations.
- the request may include one or more geofeed parameters, and/or other parameters.
- the one or geofeed parameters may be used to filter content into the geofeed and/or out of the geofeed.
- the geofeed creation module may generate a geofeed definition that includes the specification of the one or more geo-locations, the one or more geofeed parameters, and/or other information related to the geofeed.
- the geofeed definition may be updated.
- the specification of the one or more geo-locations, the one or more geofeed parameters, and/or other information of the geofeed definition may be updated.
- various parameters related to geofeeds may be defined or updated at the time of specifying the geofeeds and/or after the geofeeds have been specified.
- the geofeed creation module may obtain the specification of the one or more geo-locations from the geofeed definition and generate requests that specify the one or more geo-locations specifically for individual ones of the plurality of content providers.
- the geofeed creation module may create a single geofeed having a plurality of geo-locations that are grouped with respect to one another.
- the geofeed creation module may create multiple distinct geofeeds, which may each be associated with one or more geo-locations that are grouped with respect to one another. In these embodiments, each set of individual content may correspond to a single geofeed.
- the unified message module may be configured to generate one or more messages to be communicated to a message recipient, which may include a system user (e.g., a user who is registered to use the system), a content creator (who may or may not include a system user), and/or other message recipient.
- a system user e.g., a user who is registered to use the system
- a content creator who may or may not include a system user
- the unified message module may facilitate targeted messaging to the message recipient.
- the workflow module may be configured to generate workflows that allow management of the content with respect to operational processes of an entity such as a user, an organization, and/or other entity that wishes to use the content.
- the workflows allow creation and tracking of workflow items to be performed with respect to the content, thereby allowing the entity to manage and integrate the content with its own assets such as a website, a mobile application, and/or other asset.
- the content may be subject to one or more requirements that should be met before using (e.g., copying, modifying, distributing, etc.) the content.
- the one or more requirements may include a royalty to be paid, an attribution requirement, and/or other requirement.
- the clearinghouse module may be configured to store and provide the requirements and the content, either or both of which may be searchable.
- the clearinghouse module may generate a clearinghouse database that includes the content (or links to the content) and requirements of the content. In this manner, a user may view content related to a geo-location and determine whether the content may be used.
- the clearinghouse module may facilitate payments in relation to an authorization to use the content.
- the payment may include a one-time payment, a recurring payment, a payment based on use of the content, and/or other payment.
- Payments may be facilitated via one or more accounts related to the clearinghouse module, conventional electronic payments, paper billing, and/or other payment methods. In this manner, the clearinghouse module may facilitate the use of content that may be otherwise subject to ownership rights of the content.
- the administration module may be configured to manage user accounts, set user roles such as security access roles, and/or perform other administrative operations. For example, the administration module may be used to set which user may access different views, curate geofeeds, view and manage curated content, decide whether to burn a geofeed such as by storing content or information related to the content, and/or provide other security roles.
- the communication module may be configured to share a geofeed via a content provider such as a social media provider, email, SMS text, and/or other communication channels.
- the communication module may be configured to communicate a geofeed via various feeds such as Really Simple Syndication (“RSS”) and ATOM feeds, a vanity Uniform Resource Locator (“URL”) using a name of the geofeed (e.g., a name assigned by the content consumer), and/or other communication channels.
- RSS Really Simple Syndication
- ATOM ATOM feeds
- URL Uniform Resource Locator
- the user interface module may be configured to generate user interfaces that allow viewing and interaction with the geofeeds.
- the user interface module may present various displays for sending/receiving messages, managing workflows, managing information related to ownership rights of the content, displaying geofeeds, requesting geofeeds, and/or otherwise displaying information related to the content.
- FIG. 1 illustrates a system of targeted messaging, workflow management, and digital rights management for geofeeds, according to an aspect of the invention.
- FIG. 2 illustrates a process of targeted messaging related to geofeeds, according to an aspect of the invention.
- FIG. 3 illustrates a process of automated messaging related to geofeeds, according to an aspect of the invention.
- FIG. 4 illustrates a process of managing permission to use content, according to an aspect of the invention.
- FIG. 5 illustrates a process of managing payments related to use of content, according to an aspect of the invention.
- FIG. 6 illustrates a process of managing workflows related to geofeeds, according to an aspect of the invention.
- FIG. 7 illustrates a process of identifying content to be managed in a workflow, according to an aspect of the invention.
- FIG. 8 illustrates a process of annotating content of a geofeed, according to an aspect of the invention.
- FIG. 9 illustrates a screenshot of an interface for displaying content items with access to targeted messaging, workflows, and rights management, according to an aspect of the invention.
- FIG. 1 illustrates a system 100 of targeted messaging, workflow management, and digital rights management for geofeeds, according to an aspect of the invention.
- a geofeed includes a collection of content (also referred to herein as “geofeed content”), aggregated from various content providers, that is relevant to a geographically definable location (hereinafter, a “geo-location”).
- the content providers may include, for example, social media platforms (e.g., FACEBOOK, TWITTER, INSTAGRAM, FLICKR, etc.), online knowledge databases, and/or other providers that can distribute content that may be relevant to a geo-location.
- the geo-location may be specified by a boundary, geo coordinates (e.g., latitude, longitude, altitude/depth), an address, a school, a place name, a point of interest, a zip code, a city, a state, a country, and/or other information that can spatially identify an area.
- the content may be generated by content sources such as individuals, corporations, and/or other entities that may create content.
- a location As used hereinafter, “a location,” “a geo-location,” “a geographically definable location,” and similar language is not limited to a single location but may also refer to one or more such locations.
- the content can be automatically tagged with information.
- the information may include a user identification, date/time information related to the content (e.g., a date and/or time that indicates when the content was created, uploaded, etc.), geographic information that specifies a location where the content was created, uploaded, etc., and/or other information.
- GPS Global Positioning Satellite
- cameras equipped with a Global Positioning Satellite (“GPS”) unit and/or other location-aware system may embed into an image file latitude/longitude coordinates that indicate where a picture was taken.
- GPS Global Positioning Satellite
- modern hand-held devices such as smartphones may be equipped with a GPS sensor, which allows users to generate content with their devices and share the content through a plurality of social networks and other providers.
- some devices allow users to manually input the foregoing and other information for embedding into the content.
- editing software may allow a user to embed or otherwise manually and/or automatically include information along with the content after the content was created.
- System 100 may include a computer 110 , a geofeed API 111 , a content consumer device 130 , provider APIs 140 , content providers 150 , and/or other components.
- computer 110 may include one or more processors 120 configured to perform some or all of a functionality of a plurality of modules, which may be stored in a memory 121 .
- the one or more processors 120 may be configured to execute a geofeed creation module 112 , a unified message module 113 , a workflow module 114 , a clearinghouse module 115 , an administration module 116 , a communication module 117 , a user interface module 118 , and/or other modules 119 .
- Geofeed API 111 may be used to interface with computer 110 to interface with computer 110 in relation to the geofeeds.
- Geofeed creation module 112 may be configured to create one or more geofeeds, as described in U.S. patent application Ser. No. 13/284,455, filed Oct. 28, 2011, entitled “SYSTEM AND METHOD FOR AGGREGATING AND DISTRIBUTING GEOTAGGED CONTENT,” and U.S. patent application Ser. No. 13/619,888, filed Sep. 14, 2012, entitled “SYSTEM AND METHOD FOR GENERATING, ACCESSING, AND UPDATING GEOFEEDS” both of which are incorporated by reference herein in their entireties.
- Geofeed creation module 112 may be configured to generate one or more geofeeds based on content that is relevant to one or more geographically definable locations (“geo-locations”). The geofeed creation module may format requests that specify one or more geo-locations specifically for individual ones of the plurality of content providers and aggregate the content to form a geofeed. In some embodiments, geofeed creation module 112 may create a single geofeed having a plurality of geo-locations that are grouped with respect to one another. In other embodiments, geofeed creation module 112 may create multiple distinct geofeeds, which may each be associated with one or more geo-locations and may be grouped with respect to one another. In these embodiments, each set of individual content may correspond to a single geofeed.
- geofeed creation module 112 may format requests to individual ones of a plurality of APIs 140 (illustrated in FIG. 1 as API 140 A, 140 B, . . . , 140 N).
- the provider APIs 140 may facilitate receiving content from corresponding content providers 150 (illustrated in FIG. 1 as content providers 150 A, 150 B, 150 C).
- geofeed creation module 110 may format a request directly for content provider 150 N without using a corresponding API.
- a content consumer device 130 may request and view geofeeds created by geofeed creation module 112 .
- the formatting instructions may be stored in and recalled from a memory such as provider database 134 .
- Preferences for creating, viewing, and/or managing information related to geofeeds may be stored in and recalled from a memory such as user profile database 132 .
- geofeed creation module 112 may generate a geofeed definition that describes a geofeed such that a geofeed may be dynamically generated based on the geofeed definition.
- the geofeed definition may include the geo-location specification, one or more geofeed parameters used to filter content aggregated from content providers 150 , and/or other information related to the geofeed that can be used to aggregate content from various content providers.
- the one or geofeed parameters may be used to view only particular types of content, content from particular content providers, and/or other parameter by which to filter in or out content.
- the geofeed definition may be identified by a geofeed identifier and stored (e.g., in database 136 ) for later retrieval so that a content consumer or others may select and obtain a geofeed that was previously defined.
- geofeed creation module 112 may store the geofeed (e.g., in database 136 ).
- geofeed creation module 112 may be configured to store the geofeed by aggregating content from content providers 150 in relation to the geofeed and store the content in association with a geofeed identifier and/or a geofeed definition.
- geofeed creation module 112 may use the credentials of a user for social media or other platform to access content. In this manner, geofeed creation module 112 may obtain content from a content provider using the credentials of the user. For example, geofeed creation module 112 may obtain from the user a username and password (with permission from the user) for the user's TWITTER account and obtain content from TWITTER to which the user has access.
- unified message module 113 may be configured to generate one or more targeted messages to be communicated to a message recipient, which may include a system user (e.g., a user who is registered to use the system), a content creator (who may or may not include a system user), and/or other message recipient.
- a system user e.g., a user who is registered to use the system
- a content creator who may or may not include a system user
- unified message module 113 may facilitate targeted messaging to the message recipient.
- Unified message module 113 may be used to generate different types of targeted messages such as, for example, messages to obtain permission to use content from an owner of the content, messages to gather more information about a breaking news event, messages to seek further information about an experience, messages to obtain a following on TWITTER for one-on-one communications, messages to offer a promotion or coupon; and/or other types of messages.
- the targeted message may be generated based on one or more characteristics of the content that was generated by the message recipient.
- the targeted message may be based on a topic, an event, a geo-location, and/or other characteristic of the content.
- a content item such as a TWEET may be related to a particular topic such as shoes.
- the targeted message may include a promotional message based on the topic “shoes.”
- a content item may be related to a particular event such as “rioting.”
- the targeted message may include questions related to obtaining more information about the rioting event.
- a content item may be geo-tagged associated with a particular geo-location.
- Unified message module 113 may determine the geo-location and generate a targeted message based on the geo-location.
- various characteristics of the content item may be combined to generate a targeted message.
- a TWEET that is geo-tagged with a particular geo-coordinate may indicate that the user who made the TWEET is at the particular geo-coordinate.
- the geo-coordinate may be associated with breaking news or otherwise event of interest.
- a user may cause a message to be generated that requests a picture or other content from the user who made the TWEET (who in this case is the message recipient).
- unified message module 113 may generate a message based on one or more message templates.
- a message template may be provided by various template sources such as the system, a user, and/or other template source.
- the message template may specify a format, a communication channel to be used, a message type, and/or other information related to a message.
- Different types of message templates may be defined for different types of messages.
- Different types of messages may include, for example, a request for permission to use content, a promotional message that includes promotional content such as an indication of a sale, a coupon, a promotional offer, and/or other types of promotional content.
- unified message module 113 may automatically generate a message based on one or more message rules.
- the one or more message rules may be defined by the system, a user, and/or other source of a message rule.
- the message rule may include instructions or other logic that specifies when a message should be generated, to whom the message should be targeted, and/or other instruction related to the message.
- a message rule may indicate that a user who created content of a geofeed that covers a particular retail location of a retail chain should be targeted with a promotional message related to the retail location and/or retail chain.
- unified message module 113 may automatically generate messages directed to particular users based on the content.
- unified message module 113 may communicate the message in various ways. For example, unified message module 113 may communicate the message via email, SMS text, a message related to a social media account of the user (e.g., a post to a FACEBOOK wall), and/or other channels.
- unified message module 113 may communicate the message via email, SMS text, a message related to a social media account of the user (e.g., a post to a FACEBOOK wall), and/or other channels.
- the targeted message may include a poll that is broadcast to one or more users. For example, based on various social media and other content posted by users who are attending a baseball game, unified message module 113 may determine that the users are attending the baseball game at a particular location such as a baseball stadium. Unified message module 113 may target such users to receive a poll that includes questions about the game, players, and/or other topics. In this example, other messages described herein may be communicated to the users as well.
- the targeted message may include an interface (or a link to such interface) that allows the recipient to respond to the message.
- the interface may include an interface for redeeming a coupon, an interface for selling or otherwise permitting user of content, an upload interface for providing additional content such as new photographs, and/or other interfaces for responding to the message.
- unified message module 113 may facilitate an exchange of communications to and from one or more recipients of the targeted messages.
- the exchange of communications may be stored for later retrieval and communication.
- workflow module 114 may be configured to generate workflows that allow management of the content with respect to operational processes of an entity such as a user, an organization, and/or other entity.
- the workflows allow creation and tracking of workflow items that represent operational processes to be performed with respect to the content, thereby allowing the entity to manage and integrate the content with its own assets such as a website, a mobile application, and/or other asset.
- workflow module 114 may filter and/or rank content for inclusion into a workflow based on various parameters. For example, users may select from among ranked content items for inclusion into a workflow. Examples of filtering and ranking content is described in co-pending U.S.
- the operational processes may include various processes that an entity such as an organization performs in relation to using, annotating, and/or otherwise dealing with one or more content items.
- an operational process may include a process for approving content items for use in an online asset such as a website, a process for obtaining permission to use a content item from an owner of the content item, a process for appending annotation information to the content item for later retrieval, a process for generating promotional or marketing materials in relation to the content, and/or other operational processes.
- a workflow item may include or be associated with a workflow item identifier that identifies the workflow item, a description of the operational processes that are to be performed, a status of the workflow item, relevant dates associated with the workflow item (e.g., when an operational process was performed) and/or other information.
- Workflow module 114 may receive a request to generate a workflow item from a requester such as a user, a computer (e.g., a process executing on the computer), and/or other requester.
- the request to generate the workflow item may include workflow item information such as an identification of the content related to the workflow item, a resolver who is to handle the workflow item, a description of the operational process performed or to be performed, and/or other workflow item information.
- Workflow module 114 may generate the workflow item based on the request and assign a workflow item identifier for the generated workflow item.
- An association of the workflow item identifier and a content identifier that identifies the content related to the workflow item may be stored in a memory such as workflow database 138 .
- the content identifier may include an internal content identifier generated by the system and/or an external content identifier assigned by the content provider who provided the content.
- Workflow module 114 may assign the workflow item to the resolver such as a user, a computer, and/or other resolver who is to handle the workflow item.
- workflow module 114 may obtain user roles associated with various users.
- the user roles may specify system access in relation to workflow items such as who may submit a workflow item request, who may handle a workflow item request, who may view workflow item requests of others, and/or other system access information.
- workflow module 114 may obtain relationships between users such as, for example, a subordinate-boss relationship, a team relationship, and/or other relationships.
- workflow module 114 may determine appropriate actions with respect to the workflow items. For example, workflow module 114 may assign a workflow item from a subordinate to a boss (or vice versa), allow a boss to view workflow items related to a subordinate, and/or automatically make other decisions with respect to workflow items.
- workflow module 114 may track a lifecycle of a workflow item.
- Workflow module 114 may update a workflow item status as processing operations are performed on the workflow item.
- the workflow item status may indicate that the workflow item has been generated, is assigned, is currently in progress, is resolved, and/or indicate other workflow item status.
- workflow management will be described in the context of a news service for illustrative purposes.
- Other examples and embodiments of workflow module 114 will be apparent to those having skill in the art.
- a news service may wish to maintain certain standards for work published using its assets such as its website and therefore may require approval by an editor prior to publishing work on the website. Thus, an operational process of approving such works may be required by the news service.
- Workflow module 114 may manage the operational process of approving work prior to publication. For example, using various interfaces provided by the system described herein, a first user such as a reporter may review various content items, which may be included in one or more geofeeds. The first user may wish to use a content item such as a photograph from INSTAGRAM. The first user may generate a workflow item request related to approval of the photograph for use in the website of the news service. Workflow module 114 may generate the workflow item based on the workflow item request.
- the workflow item may be assigned to a second user such as the editor for approving the photograph.
- workflow module 114 may automatically assign the workflow item to the second user based on user roles and/or relationships.
- the second user may be associated with a user role “editor” such that workflow module 114 may recognize that the second user should be assigned the workflow item.
- the first user and the second user may share a relationship “reporter-editor” such that workflow module 114 may recognize that the second user should be assigned the workflow item.
- workflow module 114 may identify content items that reflect negative consumer sentiment and, in response, automatically generate and assign a workflow item to a customer service representative.
- the workflow item request may indicate that the second user should be assigned the workflow item.
- the second user may view the workflow item, review the content to be approved, which may be displayed in association with the workflow item, and provide an indication that the content is approved, rejected, deferred until further discussion, and/or other indication.
- workflow module 114 may store the indication such that content that is not yet approved is prevented from being used.
- workflow module 114 may communicate one or more status updates as the workflow item progresses through its lifecycle.
- the status updates may be communicated to interested parties such as the requester, the resolver, and/or other interested parties.
- workflow module 114 may use unified message module 113 to communicate the workflow item update as a message.
- status updates may be communicated via messages based on templates that are suited for workflow item status updates.
- workflow module 114 may facilitate identification of particular content for use by the entity by allowing the entity to rank or otherwise identify particular content or content creators who create interesting content. For example, continuing the non-limiting example above, a reporter may flag favorite ones of content creators (e.g., social media users who post content) that the reporter believes creates or posts interesting content. Workflow module 114 may store an association of content creators and the reporter such that content from the flagged content creators may be highlighted or otherwise emphasized to the reporter. Such highlighting/emphasis may include displaying content from the flagged content creators at the top of a list, including graphical elements that emphasize the content, and/or other highlighting/emphasis.
- content creators e.g., social media users who post content
- Workflow module 114 may store an association of content creators and the reporter such that content from the flagged content creators may be highlighted or otherwise emphasized to the reporter.
- Such highlighting/emphasis may include displaying content from the flagged content creators at the top of
- workflow module 114 may be configured to annotate the content with proprietary or otherwise private information, which may be provided by the entity during the course of managing the content with respect to the workflows.
- Workflow module 114 may store annotation information in association with the identifier that identifies the content. In this manner, users may provide annotations related to the content that may be stored for later retrieval.
- the annotations may include internal comments (e.g., “this is a good photo posted by a user”) made within an organization in relation to the content.
- a reporter may be interested in content from a content creator and establish communication with the content creator such as by using unified message module 113 .
- the content creator may provide the reporter with a phone number or other information so that the reporter may contact the content creator at a later time.
- the reporter may provide the phone number, a meeting time, and/or other information as an annotation to the content.
- Other information such as a text or audio transcription of the interview, interview notes, and/or other information may be provided as an annotation as well.
- Workflow module 114 may store the annotation information in association with the content.
- access to the annotation information may be restricted using user roles and/or other security information. In this manner, entities such as news services and/or others may provide annotations that may be secure and private in relation to content using workflow module 114 .
- the use of content may be subject to various requirements such as permission requirements, attribution requirements, and/or other requirements.
- the requirements may be related to ownership rights associated with the content such that different owners may impose one or more different requirements for using the content.
- clearinghouse module 115 may be configured to manage the requirements, compliance with the requirements, payments, and/or other information related to the requirements.
- Clearinghouse module 115 may store an association of the content (e.g., the identifier that identifies the content) with an indicator that indicates whether the content is clear to use (e.g., one or more requirements of the content has been satisfied). In this manner, a user may view the content and determine whether the content may be used.
- clearinghouse module 115 may store an association of the content with the one or more requirements and display the requirements. For example, using clearinghouse module 115 , a user may view the requirements associated with the content to determine what, if anything, is required in order to use the content.
- clearinghouse module 115 may facilitate messages to owners of the content to obtain permission to use the content.
- the authorization may include consent to use the content, consent to use the content with attribution, consent to use the content with payment of a fee, a sale of the content for a fee, and/or other authorization to use the content.
- Clearinghouse module 115 may store the request, consent, non-consent, various communications to and from the owners of the content, and/or other information related to authorization to use the content.
- clearinghouse module 115 may facilitate a database of content that has been permitted to be used.
- Clearinghouse module 115 may leverage permission information, geo-location information associated with the content, keyword information, and/or other information known to the system to build a robust and searchable clearinghouse database of content that may be permissibly used and/or licensed to others. For example, a news agency or others who wish to obtain content such as photographs related to a particular geo-location may obtain such content from the clearinghouse database. Thus, content related to rioting in a particular geo-location and obtained from social media and other providers may be found and/or licensed for use from the clearinghouse database.
- clearinghouse module 115 may be configured to receive a request for content.
- the request for content may include a search query run on the clearinghouse database and having one or more parameters that specify the search for content.
- the parameters may include a location parameter, a subject matter parameter, a permission parameter, and/or other parameters.
- the location parameter may be used to specify one or more geo-locations of interest such that social media and/or other content related to the geo-locations of interest may be returned in the search results.
- the subject matter parameter may be used to specify one or more subject matter of interest such that social media and/or other content related to the subject matter of interest may be returned in the search results.
- Subject matter may be determined based on keywords of the content, hashtags, and/or other information related to the content.
- the permission parameter may be used to filter in or out the content based on whether the content is permitted to be used. Other parameters may be used as well.
- Clearinghouse module 115 may identify at least one content item based on the request for content, which may be subject to one or more requirements. Clearinghouse module 115 may obtain and communicate the one or more requirements. The requester may review the requirements and decide that the requirements are acceptable (e.g., the requester is willing to satisfy the requirements in exchange for permission to use the content item). As such, clearinghouse module 115 may receive an indication that the one or more requirements are satisfactory and that the content item is desired. Clearinghouse module 115 may facilitate provision of the at least one content item and satisfaction of the one or more requirements. For example, clearinghouse module 115 may provide the content item from a memory (e.g., when the content item is stored by the system) and/or from the one or more content providers 150 .
- a memory e.g., when the content item is stored by the system
- clearinghouse module 115 may facilitate payment of a fee to use the at least one content item to thereby facilitate satisfaction of the one or more requirements.
- the payment may include a one-time payment, a recurring payment, a payment based on use of the content, and/or other payment.
- Payments may be facilitated via one or more accounts related to clearinghouse module 115 , conventional electronic payments, paper billing, and/or other payment methods. In this manner, clearinghouse module 115 may facilitate the use of content that may be otherwise subject to ownership rights of the content.
- clearinghouse module 115 may provide an attribution notice to accompany the at least one content to thereby facilitate satisfaction of the one or more requirements.
- clearinghouse module 115 may provide a platform by which owners of content and parties wishing to use the content may use to engage one another and facilitate permission, payments, and/or other activities related to use of the content.
- administration module 116 may be configured to manage user accounts, set user roles such as security access roles, and/or perform other administrative operations.
- the administration module may be used to define which users may generate messages using the unified message module, generate workflow items, view workflow items of others, annotate content, enter into agreements with respect to ownership rights of the content, and/or set other user roles.
- communication module 117 may be configured to share a geofeed via a content provider such as a social media provider, email, SMS text, and/or other communication channels.
- the communication module may be configured to communicate a geofeed via various feeds such as Really Simple Syndication (“RSS”) and ATOM feeds, a vanity Uniform Resource Locator (“URL”) using a name of the geofeed (e.g., a name assigned by the content consumer), and/or other communication channels.
- RSS Really Simple Syndication
- ATOM ATOM feeds
- URL Uniform Resource Locator
- the user interface module 118 may be configured to generate user interfaces that allow viewing and interaction with the geofeeds.
- the user interface module may present various displays for sending/receiving messages, managing workflows, managing information related to ownership rights of the content, displaying geofeeds, requesting geofeeds, and/or otherwise displaying information related to the content.
- computer 110 and content consumer device 130 may each comprise one or more processors, one or more interfaces (to various peripheral devices or components), memory, one or more storage devices, and/or other components coupled via a bus.
- the memory may comprise random access memory (RAM), read only memory (ROM), or other memory.
- RAM random access memory
- ROM read only memory
- the memory may store computer-executable instructions to be executed by the processor as well as data that may be manipulated by the processor.
- the storage devices may comprise floppy disks, hard disks, optical disks, tapes, or other storage devices for storing computer-executable instructions and/or data.
- One or more applications may be loaded into memory and run on an operating system of computer 110 and/or consumer device 130 .
- computer 110 and consumer device 130 may each comprise a server device, a desktop computer, a laptop, a cell phone, a smart phone, a Personal Digital Assistant, a pocket PC, or other device.
- Network 102 may include any one or more of, for instance, the Internet, an intranet, a PAN (Personal Area Network), a LAN (Local Area Network), a WAN (Wide Area Network), a SAN (Storage Area Network), a MAN (Metropolitan Area Network), a wireless network, a cellular communications network, a Public Switched Telephone Network, and/or other network.
- a PAN Personal Area Network
- LAN Local Area Network
- WAN Wide Area Network
- SAN Storage Area Network
- MAN Metropolitan Area Network
- wireless network a wireless network
- cellular communications network a cellular communications network
- Public Switched Telephone Network and/or other network.
- FIG. 2 illustrates a process 200 of targeted messaging related to geofeeds, according to an aspect of the invention.
- the various processing operations and/or data flows depicted in FIG. 2 are described in greater detail herein.
- the described operations may be accomplished using some or all of the system components described in detail above and, in some embodiments, various operations may be performed in different sequences and various operations may be omitted. Additional operations may be performed along with some or all of the operations shown in the depicted flow diagrams. One or more operations may be performed simultaneously. Accordingly, the operations as illustrated (and described in greater detail below) are exemplary by nature and, as such, should not be viewed as limiting.
- a selection of one or more content items may be received.
- the one or more content items may be identified by an internal identifier (e.g., system-generated) and/or an external identifier (e.g., generated by a content provider).
- the selection may be received from a user viewing one or more geofeeds and selecting the one or more content items, from an automated process such as a process that selects the one or more content items based on keywords, and/or other source.
- a user that created the one or more content items may be identified.
- operation 204 may identify the user who generated the TWEET.
- a mode of communication may be identified.
- the mode of communication may include, for example, email, social media communication (e.g., a TWEET directed to a TWITTER handle), SMS text, and/or other mode of communication.
- the mode of communication may be identified in various ways.
- the mode of communication may be predefined by one or more rules specified by an entity that wishes to communicate targeted messages, be indicated by a user, and/or other method by which the mode of communication may be identified.
- a message to be communicated may be obtained.
- the message may be obtained from various message sources such as a user, one or more message rules (e.g., send a coupon to a user who TWEETS from a restaurant location), and/or other message source.
- the message may be communicated to the identified user via the identified mode of communication.
- Process 200 may be used to automatically and/or manually target messages to users who create content (e.g., post social media or other content that is relevant to a geo-location).
- content e.g., post social media or other content that is relevant to a geo-location.
- an entity may target messages to the users based on the content.
- the messages may serve various purposes such as, for example, requesting authorization to use the content, requesting the user to provide additional content (e.g., the user is at a location where breaking news is occurring and the message requests additional content), providing one or more promotional messages based on the content, and/or other providing other information based on the content.
- FIG. 3 illustrates a process 300 of automated messaging related to geofeeds, according to an aspect of the invention.
- one or more message rules may be obtained.
- content may be monitored.
- an entity may create one or more geofeed definitions that include one or more parameters that specify that the one or more geofeeds should be monitored for automatic messaging.
- the content related to such geofeed definitions may be obtained “live” from one or more content providers and monitored and/or stored and monitored.
- a determination of whether the monitored content satisfies the one or more message rules may be made.
- a message rule may indicate that an automated message should be communicated to users who TWEET or otherwise provide content from a particular location.
- a message rule may indicate that an automated message should be communication to users who provide content that includes certain keywords.
- Other message rules may be used as well.
- the one or more message rules may specify whether to automatically send a message when the content satisfies the message rules, specify the content of the messages, specify who should receive alerts related to the messages, and/or other information related to the message.
- processing may return to operation 304 , where content is monitored.
- a determination of whether to automatically send a message may be made in an operation 308 .
- the user who created the content that satisfies the one or more message rules may be identified in an operation 310 .
- the message may be communicated to the identified user.
- a user who should receive an alert that the message satisfied the one or more message rules may be identified in an operation 314 .
- an alert to the identified user may be communicated via one or more communication channels.
- FIG. 4 illustrates a process 400 of managing permission to use content, according to an aspect of the invention.
- a selection of one or more content items may be received.
- the one or more content items may be identified by an internal identifier and/or an external identifier.
- the selection may be received from a user, an automated process, and/or other source.
- a determination of whether permission is required prior to using (e.g., publishing) the selected content items may be made.
- an indication that the content items are usable may be stored in an operation 414 .
- a determination of whether to obtain permission to use the content may be made in an operation 406 .
- an indication that the content items are unusable may be stored in an operation 412 .
- a message to obtain the permission may be generated in an operation 408 . For example, an owner of or other holder of rights to the content may be identified and a message to the owner that requests permission to use the content may be generated.
- a determination of whether permission has been obtained may be made. For example, the owner of the content may provide permission to use the content. If permission has not been obtained (e.g., permission has been denied), an indication that the content is unusable may be stored in operation 412 . If permission has been obtained, an indication that the content is usable may be stored in operation 414 .
- Process 400 may be used to ensure that permissions with respect to using content is verified and obtained when such permission may be necessary.
- the usable and unusable indicators may be used to verify that use of such content is permitted before publishing or otherwise using the content.
- the usable and/or unusable indicator (which may be stored in one or more fields of a database, for example) may be referenced to determine whether the content may be published without potentially overstepping use rights (e.g., copyright) related to the content.
- the indicators may be automatically and/or manually maintained.
- FIG. 5 illustrates a process 500 of managing payments related to use of content, according to an aspect of the invention.
- an indication that content is permitted may be obtained.
- the indication may be stored.
- an indication that the content was used may be received.
- a determination of whether a royalty or payment is associated with the use may be made.
- an indication of the use may be stored in an operation 514 .
- the indication may be stored solely for informational purposes.
- a royalty is associated with the use, a determination of whether the royalty is related to a royalty per use may be made.
- an indication of the use may be stored in operation 514 .
- a royalty payment for the use may be facilitated in an operation 512 .
- a royalty fee based on the use may be determined.
- the royalty fee may be determined based on a count of the number of uses of the content in a time period and a per use fee associated with the content.
- process 500 may facilitate various payment methods from the user of the content to the holder of rights of the content, whether the royalty is a lump sum fee, per use fee, and/or other type of fee arrangement.
- FIG. 6 illustrates a process 600 of managing workflows related to geofeeds, according to an aspect of the invention.
- a workflow item request for a workflow item to be resolved in relation to content may be received.
- the workflow item may be generated and stored.
- the workflow item may be assigned with a workflow item identifier and the workflow item identifier may be stored in association with a workflow item description, a workflow item type, a date, a workflow item status, a requester, a resolver, and/or other information related to the workflow item.
- an identification of a resolver may be obtained.
- the requester and the resolver may be the same or different user.
- the identification may be obtained from the workflow item request (e.g., the requester may specify who should handle the workflow item), automatically obtained based on user roles, user relationships, or other information, and/or from other information sources.
- the workflow item may be assigned to the identified resolver.
- an indication of the progress of the workflow item may be received in an operation 610 .
- the indication of the progress may be received from the requester, the resolver, an automated process that monitors the workflow item, and/or other source of information.
- the workflow item status may be updated based on the indication of progress.
- process 600 may include communicating information to the requester, the resolver, and/or others.
- the information may relate to a progress of the workflow item (e.g., status updates), information relevant to the workflow item, and/or other information.
- FIG. 7 illustrates a process 700 of identifying content to be managed in a workflow, according to an aspect of the invention.
- a selection of one or more content items may be received.
- the one or more content items may be identified by an internal identifier and/or an external identifier.
- the selection may be received from a user, an automated process, and/or other source.
- proximate content related to a location within a predefined or otherwise configurable proximity of a location related to the selected content items may be obtained. For example, for a selected content item that is relevant to a geo-location, proximate content within a five mile radius or other proximity may be obtained. In this manner, process 700 facilitates using particular content items of interest to potentially discover other related content items of interest.
- the proximate content may be communicated.
- the proximate content may be communicated via a display and/or other communication channels.
- one or more workflow items to be resolved in relation to the content items and/or the proximate content items may be received.
- the one or more workflow items may be managed, such as in a manner similar to process 600 .
- FIG. 8 illustrates a process 800 of annotating content of a geofeed, according to an aspect of the invention.
- a selection of one or more content items may be received.
- the one or more content items may be identified by an internal identifier and/or an external identifier.
- the selection may be received from a user, an automated process, and/or other source.
- one or more annotations to the selected content items may be received.
- the one or more annotations may include information added to the selected content items (and/or updates or removal of information from the selected content items).
- the annotations may facilitate internal workflows. For example, a reporter may annotate a TWEET with a user's phone number that the reporter obtained. Process 800 may receive such annotations for processing.
- the one or more annotations may be stored in association with the selected content items.
- one or more security settings may be applied to control access to the one or more annotations.
- the security settings may restrict access (e.g., read, write, delete, and/or other types of access) to the annotations to only a user who made the annotations, particular users of an entity, users having particular user roles, and/or other users.
- a request to view the content items may be received.
- a determination of whether the requester is authorized to access the annotations made be made.
- the annotations may be communicated in an operation 814 and the content items may be communicated in an operation 816 .
- the requester is not authorized to access the annotations, only the content items may be communicated in operation 816 .
- FIG. 9 illustrates a screenshot of an interface 900 for displaying content items with access to targeted messaging, workflows, and rights management, according to an aspect of the invention.
- the screenshots illustrated in FIG. 9 are for illustrative purposes only. Various components may be added, deleted, moved, or otherwise changed so that the configuration, appearance, and/or content of the screenshots may be different than as illustrated in the figures. Accordingly, the graphical user interface objects as illustrated (and described in greater detail below) are exemplary by nature and, as such, should not be viewed as limiting.
- Interface 900 may be implemented as a web page communicated from computer 110 to a client, an application such as a mobile application executing on the client that receives generates the interface based on information communicated from computer 110 , and/or other interface. Whichever type of interface is used, computer 110 may communicate the data and/or formatting instructions related to the interface to the client, causing the client to generate the interface of FIG. 9 and other drawing figures. Furthermore, computer 110 may receive data from the client via the various interfaces, as would be appreciated.
- a navigation element 904 having links or other controls that switch between the “MAP” display illustrated in FIG. 9 , a “COLLAGE” display, and a “LIST” display.
- the geofeed as illustrated includes content indicators 932 and 634 , which provide graphical indicia of aggregated content of the geofeed.
- the content may be provided from different or the same content provider.
- Content indicators 932 and 934 may each include an icon, a logo, and/or other identifying indicia that indicates the source of the content and/or a type of content.
- interface 900 may cause workflow interface 940 to appear.
- Workflow interface 940 may include a component 941 that includes information related to the content such as, for example, the content itself, a content creator (e.g., social media user who posted the content), an identification of the content provider that provided the content, a time associated with the content (e.g., create time, publication time, etc.), a location where the content was created (e.g., address, geo-coordinates, etc.), and/or other information known or determined about the content.
- a content creator e.g., social media user who posted the content
- an identification of the content provider that provided the content e.g., a time associated with the content (e.g., create time, publication time, etc.), a location where the content was created (e.g., address, geo-coordinates, etc.), and/or other information known or determined about the content.
- a time associated with the content e.g., create time, publication time, etc.
- location where the content was created e.g., address, geo-
- component 942 may include an interface or links to an interface that provides targeted messaging functions. For example, using component 942 , a targeted message may be directed to the content creator associated with the content indicated by content indicator 932 .
- component 943 may include an interface or links to an interface that provides digital rights or other functions relation to permission to use content. For example, using component 943 , whether content indicated by content indicator 932 is permitted to be used in an entity's website may be determined. If such permission is required and not yet obtained, component 943 may be used to obtain such permission.
- component 944 may include an interface or links to an interface that provides workflow functions. For example, using component 944 , various workflow items related to the content indicated by content indicator 932 may be generated and tracked. Other components 945 related to other features related to the content indicated by content indicator 932 may be provided as well.
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- General Engineering & Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Computer Hardware Design (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Software Systems (AREA)
- Databases & Information Systems (AREA)
- Computing Systems (AREA)
- Data Mining & Analysis (AREA)
- Remote Sensing (AREA)
- Health & Medical Sciences (AREA)
- Bioethics (AREA)
- General Health & Medical Sciences (AREA)
- Technology Law (AREA)
- Multimedia (AREA)
- Information Transfer Between Computers (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
Description
- The disclosure relates to systems and methods for targeted messaging, workflow management, and digital rights management for geofeeds, including content that is related to geographically definable locations and aggregated from a plurality of social media or other content providers.
- The availability of content such as videos, audio files, photos, text, and/or other content over networks such as the Internet has grown at impressive rates. Many Internet and other online service providers make this type of content available to enable users to post and share such content through their services. However, various limitations exist with respect to how this vast amount of information can be effectively monitored and/or selectively displayed.
- Because of the vast amount of information and different ways in which to communicate with users, it can be difficult to communicate with creators of the content. Furthermore, it may be difficult to incorporate the content into operational processes of entities that wish to use the content. For example, use of the content may require approval processes that may be difficult to manage for re-syndication or re-publication as required by law and/or terms of service of content providers. Even when a decision to use the content is made, in many instances the content may be subject to requirements that are to be satisfied prior to using the content, which may be unknown to decision makers.
- These and other problems exist.
- The disclosure relates to systems and methods for targeted messaging, workflow management, and digital rights management for geofeeds, including content that is related to geographically definable locations (“geo-locations”) and aggregated from a plurality of social media or other content providers. A geofeed may include content that is aggregated from a plurality of content providers using respective requests formatted specifically for individual ones of the plurality of content providers, where an individual set of a plurality of content is relevant to one or more geo-locations.
- In some embodiments, the system may facilitate targeted messaging to users who create content. The targeted messages may include, for example, messages to obtain permission to use content from an owner of the content, messages to request additional information about a breaking news event, messages to seek further information about an experience, messages to obtain a following on TWITTER for one-on-one communications, messages that offer a promotion or coupon, and/or other types of messages.
- In some embodiments, the system may generate workflows that allow management of the content with respect to one or more operational processes of an entity such as a user, an organization, and/or other entity that wishes to use the content. The workflows allow creation and tracking of workflow items to be performed with respect to the content, thereby allowing the entity to manage and integrate the content with its own assets such as a website, a mobile application, and/or other asset.
- In some embodiments, the system facilitates the management of usage rights related to the content. For example, the system may store whether content requires permission to use the content and/or whether such permission was obtained. By doing so, the system may facilitate a database of content that has been permitted to be used.
- The system may leverage permission information, geo-location information associated with the content, keyword information, and/or other information known by the system to build a robust and searchable clearinghouse database of content that may be permissibly used and/or licensed to others. For example, a news agency or others who wish to obtain content such as photographs related to a particular geo-location may obtain such content from the clearinghouse database. Thus, content related to rioting in a particular geo-location and obtained from social media and other providers may be found and/or licensed for use from the clearinghouse database.
- The system may facilitate various requirements that are to be satisfied in order to use the content. For example, the system may facilitate payment of royalty or other fees, attribution notices, and/or other requirements that are to be satisfied to use the content.
- In some embodiments, the system may include a computer that includes one or more processors configured to perform some or all of a functionality of a plurality of modules. For example, the one or more processors may be configured to execute a geofeed creation module, a unified message module, a workflow module, a clearinghouse module, an administration module, a communication module, a user interface module, and/or other modules.
- The geofeed creation module may be configured to receive a request to create a geofeed based on a specification of one or more geo-locations. The request may include one or more geofeed parameters, and/or other parameters. The one or geofeed parameters may be used to filter content into the geofeed and/or out of the geofeed.
- The geofeed creation module may generate a geofeed definition that includes the specification of the one or more geo-locations, the one or more geofeed parameters, and/or other information related to the geofeed. The geofeed definition may be updated. For example, the specification of the one or more geo-locations, the one or more geofeed parameters, and/or other information of the geofeed definition may be updated. In this manner, various parameters related to geofeeds may be defined or updated at the time of specifying the geofeeds and/or after the geofeeds have been specified.
- To create the geofeed, the geofeed creation module may obtain the specification of the one or more geo-locations from the geofeed definition and generate requests that specify the one or more geo-locations specifically for individual ones of the plurality of content providers. In some embodiments, the geofeed creation module may create a single geofeed having a plurality of geo-locations that are grouped with respect to one another. In other embodiments, the geofeed creation module may create multiple distinct geofeeds, which may each be associated with one or more geo-locations that are grouped with respect to one another. In these embodiments, each set of individual content may correspond to a single geofeed.
- In some embodiments, the unified message module may be configured to generate one or more messages to be communicated to a message recipient, which may include a system user (e.g., a user who is registered to use the system), a content creator (who may or may not include a system user), and/or other message recipient. For example, the unified message module may facilitate targeted messaging to the message recipient.
- In some embodiments, the workflow module may be configured to generate workflows that allow management of the content with respect to operational processes of an entity such as a user, an organization, and/or other entity that wishes to use the content. The workflows allow creation and tracking of workflow items to be performed with respect to the content, thereby allowing the entity to manage and integrate the content with its own assets such as a website, a mobile application, and/or other asset.
- In some embodiments, the content may be subject to one or more requirements that should be met before using (e.g., copying, modifying, distributing, etc.) the content. The one or more requirements may include a royalty to be paid, an attribution requirement, and/or other requirement. The clearinghouse module may be configured to store and provide the requirements and the content, either or both of which may be searchable. Thus, the clearinghouse module may generate a clearinghouse database that includes the content (or links to the content) and requirements of the content. In this manner, a user may view content related to a geo-location and determine whether the content may be used.
- In some embodiments, the clearinghouse module may facilitate payments in relation to an authorization to use the content. For example, the payment may include a one-time payment, a recurring payment, a payment based on use of the content, and/or other payment. Payments may be facilitated via one or more accounts related to the clearinghouse module, conventional electronic payments, paper billing, and/or other payment methods. In this manner, the clearinghouse module may facilitate the use of content that may be otherwise subject to ownership rights of the content.
- In some embodiments, the administration module may be configured to manage user accounts, set user roles such as security access roles, and/or perform other administrative operations. For example, the administration module may be used to set which user may access different views, curate geofeeds, view and manage curated content, decide whether to burn a geofeed such as by storing content or information related to the content, and/or provide other security roles.
- In some embodiments, the communication module may be configured to share a geofeed via a content provider such as a social media provider, email, SMS text, and/or other communication channels. In some embodiments, the communication module may be configured to communicate a geofeed via various feeds such as Really Simple Syndication (“RSS”) and ATOM feeds, a vanity Uniform Resource Locator (“URL”) using a name of the geofeed (e.g., a name assigned by the content consumer), and/or other communication channels.
- In some embodiments, the user interface module may be configured to generate user interfaces that allow viewing and interaction with the geofeeds. For example, the user interface module may present various displays for sending/receiving messages, managing workflows, managing information related to ownership rights of the content, displaying geofeeds, requesting geofeeds, and/or otherwise displaying information related to the content.
- These and other objects, features, and characteristics of the system and/or method disclosed herein, as well as the methods of operation and functions of the related elements of structure and the combination of parts and economies of manufacture, will become more apparent upon consideration of the following description and the appended claims with reference to the accompanying drawings, all of which form a part of this specification, wherein like reference numerals designate corresponding parts in the various figures. It is to be expressly understood, however, that the drawings are for the purpose of illustration and description only and are not intended as a definition of the limits of the invention. As used in the specification and in the claims, the singular form of “a”, “an”, and “the” include plural referents unless the context clearly dictates otherwise.
-
FIG. 1 illustrates a system of targeted messaging, workflow management, and digital rights management for geofeeds, according to an aspect of the invention. -
FIG. 2 illustrates a process of targeted messaging related to geofeeds, according to an aspect of the invention. -
FIG. 3 illustrates a process of automated messaging related to geofeeds, according to an aspect of the invention. -
FIG. 4 illustrates a process of managing permission to use content, according to an aspect of the invention. -
FIG. 5 illustrates a process of managing payments related to use of content, according to an aspect of the invention. -
FIG. 6 illustrates a process of managing workflows related to geofeeds, according to an aspect of the invention. -
FIG. 7 illustrates a process of identifying content to be managed in a workflow, according to an aspect of the invention. -
FIG. 8 illustrates a process of annotating content of a geofeed, according to an aspect of the invention. -
FIG. 9 illustrates a screenshot of an interface for displaying content items with access to targeted messaging, workflows, and rights management, according to an aspect of the invention. -
FIG. 1 illustrates asystem 100 of targeted messaging, workflow management, and digital rights management for geofeeds, according to an aspect of the invention. A geofeed includes a collection of content (also referred to herein as “geofeed content”), aggregated from various content providers, that is relevant to a geographically definable location (hereinafter, a “geo-location”). The content providers may include, for example, social media platforms (e.g., FACEBOOK, TWITTER, INSTAGRAM, FLICKR, etc.), online knowledge databases, and/or other providers that can distribute content that may be relevant to a geo-location. - The geo-location may be specified by a boundary, geo coordinates (e.g., latitude, longitude, altitude/depth), an address, a school, a place name, a point of interest, a zip code, a city, a state, a country, and/or other information that can spatially identify an area. The content may be generated by content sources such as individuals, corporations, and/or other entities that may create content. As used hereinafter, “a location,” “a geo-location,” “a geographically definable location,” and similar language is not limited to a single location but may also refer to one or more such locations.
- In many instances the content can be automatically tagged with information. The information may include a user identification, date/time information related to the content (e.g., a date and/or time that indicates when the content was created, uploaded, etc.), geographic information that specifies a location where the content was created, uploaded, etc., and/or other information. For example, cameras equipped with a Global Positioning Satellite (“GPS”) unit and/or other location-aware system may embed into an image file latitude/longitude coordinates that indicate where a picture was taken. In addition, modern hand-held devices such as smartphones may be equipped with a GPS sensor, which allows users to generate content with their devices and share the content through a plurality of social networks and other providers. Moreover, some devices allow users to manually input the foregoing and other information for embedding into the content. Furthermore, editing software may allow a user to embed or otherwise manually and/or automatically include information along with the content after the content was created.
-
System 100 may include acomputer 110, ageofeed API 111, acontent consumer device 130, provider APIs 140, content providers 150, and/or other components. In some embodiments,computer 110 may include one ormore processors 120 configured to perform some or all of a functionality of a plurality of modules, which may be stored in amemory 121. For example, the one ormore processors 120 may be configured to execute ageofeed creation module 112, aunified message module 113, aworkflow module 114, aclearinghouse module 115, anadministration module 116, acommunication module 117, auser interface module 118, and/orother modules 119.Geofeed API 111 may be used to interface withcomputer 110 to interface withcomputer 110 in relation to the geofeeds. -
Geofeed creation module 112 may be configured to create one or more geofeeds, as described in U.S. patent application Ser. No. 13/284,455, filed Oct. 28, 2011, entitled “SYSTEM AND METHOD FOR AGGREGATING AND DISTRIBUTING GEOTAGGED CONTENT,” and U.S. patent application Ser. No. 13/619,888, filed Sep. 14, 2012, entitled “SYSTEM AND METHOD FOR GENERATING, ACCESSING, AND UPDATING GEOFEEDS” both of which are incorporated by reference herein in their entireties. - Co-pending applications filed concurrently herewith, entitled “SYSTEM AND METHOD FOR DIFFERENTIALLY PROCESSING A LOCATION INPUT FOR CONTENT PROVIDERS THAT USE DIFFERENT LOCATION INPUT FORMATS,” Attorney Docket No. 075620-0417948, and co-pending application filed concurrently herewith, entitled “SYSTEM AND METHOD FOR CREATING AND MANAGING GEOFEEDS,” Attorney Docket No. 075620-0417937, are all incorporated by reference in their entireties herein.
- Co-pending U.S. patent application Ser. No. 13/708,516, filed Dec. 7, 2012, entitled “SYSTEM AND METHOD FOR LOCATION MONITORING BASED ON ORGANIZED GEOFEEDS,” and co-pending U.S. patent application Ser. No. 13/708,466, filed Dec. 7, 2012, entitled “SYSTEM AND METHOD FOR GENERATING AND MANAGING GEOFEED-BASED ALERTS” are all incorporated by reference in their entireties herein.
-
Geofeed creation module 112 may be configured to generate one or more geofeeds based on content that is relevant to one or more geographically definable locations (“geo-locations”). The geofeed creation module may format requests that specify one or more geo-locations specifically for individual ones of the plurality of content providers and aggregate the content to form a geofeed. In some embodiments,geofeed creation module 112 may create a single geofeed having a plurality of geo-locations that are grouped with respect to one another. In other embodiments,geofeed creation module 112 may create multiple distinct geofeeds, which may each be associated with one or more geo-locations and may be grouped with respect to one another. In these embodiments, each set of individual content may correspond to a single geofeed. - For example,
geofeed creation module 112 may format requests to individual ones of a plurality of APIs 140 (illustrated inFIG. 1 asAPI FIG. 1 ascontent providers geofeed creation module 110 may format a request directly forcontent provider 150N without using a corresponding API. Acontent consumer device 130 may request and view geofeeds created bygeofeed creation module 112. The formatting instructions may be stored in and recalled from a memory such asprovider database 134. Preferences for creating, viewing, and/or managing information related to geofeeds may be stored in and recalled from a memory such asuser profile database 132. - In some embodiments,
geofeed creation module 112 may generate a geofeed definition that describes a geofeed such that a geofeed may be dynamically generated based on the geofeed definition. For example, the geofeed definition may include the geo-location specification, one or more geofeed parameters used to filter content aggregated from content providers 150, and/or other information related to the geofeed that can be used to aggregate content from various content providers. For example, the one or geofeed parameters may be used to view only particular types of content, content from particular content providers, and/or other parameter by which to filter in or out content. The geofeed definition may be identified by a geofeed identifier and stored (e.g., in database 136) for later retrieval so that a content consumer or others may select and obtain a geofeed that was previously defined. - In some embodiments,
geofeed creation module 112 may store the geofeed (e.g., in database 136). For example,geofeed creation module 112 may be configured to store the geofeed by aggregating content from content providers 150 in relation to the geofeed and store the content in association with a geofeed identifier and/or a geofeed definition. - In some embodiments,
geofeed creation module 112 may use the credentials of a user for social media or other platform to access content. In this manner,geofeed creation module 112 may obtain content from a content provider using the credentials of the user. For example,geofeed creation module 112 may obtain from the user a username and password (with permission from the user) for the user's TWITTER account and obtain content from TWITTER to which the user has access. - In some embodiments,
unified message module 113 may be configured to generate one or more targeted messages to be communicated to a message recipient, which may include a system user (e.g., a user who is registered to use the system), a content creator (who may or may not include a system user), and/or other message recipient. For example,unified message module 113 may facilitate targeted messaging to the message recipient. -
Unified message module 113 may be used to generate different types of targeted messages such as, for example, messages to obtain permission to use content from an owner of the content, messages to gather more information about a breaking news event, messages to seek further information about an experience, messages to obtain a following on TWITTER for one-on-one communications, messages to offer a promotion or coupon; and/or other types of messages. - In some embodiments, the targeted message may be generated based on one or more characteristics of the content that was generated by the message recipient. For example, the targeted message may be based on a topic, an event, a geo-location, and/or other characteristic of the content. Various non-limiting examples are provided for illustrative purposes. A content item such as a TWEET may be related to a particular topic such as shoes. The targeted message may include a promotional message based on the topic “shoes.” A content item may be related to a particular event such as “rioting.” The targeted message may include questions related to obtaining more information about the rioting event. A content item may be geo-tagged associated with a particular geo-location.
Unified message module 113 may determine the geo-location and generate a targeted message based on the geo-location. - In some embodiments, various characteristics of the content item may be combined to generate a targeted message. For example, a TWEET that is geo-tagged with a particular geo-coordinate may indicate that the user who made the TWEET is at the particular geo-coordinate. The geo-coordinate may be associated with breaking news or otherwise event of interest. A user may cause a message to be generated that requests a picture or other content from the user who made the TWEET (who in this case is the message recipient).
- In some embodiments,
unified message module 113 may generate a message based on one or more message templates. A message template may be provided by various template sources such as the system, a user, and/or other template source. The message template may specify a format, a communication channel to be used, a message type, and/or other information related to a message. Different types of message templates may be defined for different types of messages. Different types of messages may include, for example, a request for permission to use content, a promotional message that includes promotional content such as an indication of a sale, a coupon, a promotional offer, and/or other types of promotional content. - In some embodiments,
unified message module 113 may automatically generate a message based on one or more message rules. The one or more message rules may be defined by the system, a user, and/or other source of a message rule. The message rule may include instructions or other logic that specifies when a message should be generated, to whom the message should be targeted, and/or other instruction related to the message. - For example, a message rule may indicate that a user who created content of a geofeed that covers a particular retail location of a retail chain should be targeted with a promotional message related to the retail location and/or retail chain. Thus, in this manner,
unified message module 113 may automatically generate messages directed to particular users based on the content. - In some embodiments,
unified message module 113 may communicate the message in various ways. For example,unified message module 113 may communicate the message via email, SMS text, a message related to a social media account of the user (e.g., a post to a FACEBOOK wall), and/or other channels. - In some embodiments, the targeted message may include a poll that is broadcast to one or more users. For example, based on various social media and other content posted by users who are attending a baseball game,
unified message module 113 may determine that the users are attending the baseball game at a particular location such as a baseball stadium.Unified message module 113 may target such users to receive a poll that includes questions about the game, players, and/or other topics. In this example, other messages described herein may be communicated to the users as well. - In some embodiments, the targeted message may include an interface (or a link to such interface) that allows the recipient to respond to the message. For example, the interface may include an interface for redeeming a coupon, an interface for selling or otherwise permitting user of content, an upload interface for providing additional content such as new photographs, and/or other interfaces for responding to the message. In this manner,
unified message module 113 may facilitate an exchange of communications to and from one or more recipients of the targeted messages. In some embodiments, the exchange of communications may be stored for later retrieval and communication. - In some embodiments,
workflow module 114 may be configured to generate workflows that allow management of the content with respect to operational processes of an entity such as a user, an organization, and/or other entity. The workflows allow creation and tracking of workflow items that represent operational processes to be performed with respect to the content, thereby allowing the entity to manage and integrate the content with its own assets such as a website, a mobile application, and/or other asset. In some embodiments,workflow module 114 may filter and/or rank content for inclusion into a workflow based on various parameters. For example, users may select from among ranked content items for inclusion into a workflow. Examples of filtering and ranking content is described in co-pending U.S. patent application Ser. No. 13/708,404, filed Dec. 7, 2012, entitled “SYSTEM AND METHOD FOR RANKING GEOFEEDS AND CONTENT WITHIN GEOFEEDS,” which is incorporated by reference in its entirety herein. - The operational processes may include various processes that an entity such as an organization performs in relation to using, annotating, and/or otherwise dealing with one or more content items. For example, an operational process may include a process for approving content items for use in an online asset such as a website, a process for obtaining permission to use a content item from an owner of the content item, a process for appending annotation information to the content item for later retrieval, a process for generating promotional or marketing materials in relation to the content, and/or other operational processes.
- In some embodiments, a workflow item may include or be associated with a workflow item identifier that identifies the workflow item, a description of the operational processes that are to be performed, a status of the workflow item, relevant dates associated with the workflow item (e.g., when an operational process was performed) and/or other information.
-
Workflow module 114 may receive a request to generate a workflow item from a requester such as a user, a computer (e.g., a process executing on the computer), and/or other requester. The request to generate the workflow item may include workflow item information such as an identification of the content related to the workflow item, a resolver who is to handle the workflow item, a description of the operational process performed or to be performed, and/or other workflow item information. -
Workflow module 114 may generate the workflow item based on the request and assign a workflow item identifier for the generated workflow item. An association of the workflow item identifier and a content identifier that identifies the content related to the workflow item may be stored in a memory such asworkflow database 138. The content identifier may include an internal content identifier generated by the system and/or an external content identifier assigned by the content provider who provided the content.Workflow module 114 may assign the workflow item to the resolver such as a user, a computer, and/or other resolver who is to handle the workflow item. - In some embodiments,
workflow module 114 may obtain user roles associated with various users. The user roles may specify system access in relation to workflow items such as who may submit a workflow item request, who may handle a workflow item request, who may view workflow item requests of others, and/or other system access information. In some embodiments,workflow module 114 may obtain relationships between users such as, for example, a subordinate-boss relationship, a team relationship, and/or other relationships. Using the user roles and/or relationships,workflow module 114 may determine appropriate actions with respect to the workflow items. For example,workflow module 114 may assign a workflow item from a subordinate to a boss (or vice versa), allow a boss to view workflow items related to a subordinate, and/or automatically make other decisions with respect to workflow items. - In some embodiments,
workflow module 114 may track a lifecycle of a workflow item.Workflow module 114 may update a workflow item status as processing operations are performed on the workflow item. For example, the workflow item status may indicate that the workflow item has been generated, is assigned, is currently in progress, is resolved, and/or indicate other workflow item status. - A non-limiting example of workflow management will be described in the context of a news service for illustrative purposes. Other examples and embodiments of
workflow module 114 will be apparent to those having skill in the art. A news service may wish to maintain certain standards for work published using its assets such as its website and therefore may require approval by an editor prior to publishing work on the website. Thus, an operational process of approving such works may be required by the news service. -
Workflow module 114 may manage the operational process of approving work prior to publication. For example, using various interfaces provided by the system described herein, a first user such as a reporter may review various content items, which may be included in one or more geofeeds. The first user may wish to use a content item such as a photograph from INSTAGRAM. The first user may generate a workflow item request related to approval of the photograph for use in the website of the news service.Workflow module 114 may generate the workflow item based on the workflow item request. - The workflow item may be assigned to a second user such as the editor for approving the photograph. In some embodiments,
workflow module 114 may automatically assign the workflow item to the second user based on user roles and/or relationships. For example, the second user may be associated with a user role “editor” such thatworkflow module 114 may recognize that the second user should be assigned the workflow item. In another example, the first user and the second user may share a relationship “reporter-editor” such thatworkflow module 114 may recognize that the second user should be assigned the workflow item. In another example,workflow module 114 may identify content items that reflect negative consumer sentiment and, in response, automatically generate and assign a workflow item to a customer service representative. - In some embodiments, the workflow item request may indicate that the second user should be assigned the workflow item. The second user may view the workflow item, review the content to be approved, which may be displayed in association with the workflow item, and provide an indication that the content is approved, rejected, deferred until further discussion, and/or other indication. In some embodiments,
workflow module 114 may store the indication such that content that is not yet approved is prevented from being used. - In some embodiments,
workflow module 114 may communicate one or more status updates as the workflow item progresses through its lifecycle. The status updates may be communicated to interested parties such as the requester, the resolver, and/or other interested parties. In some embodiments,workflow module 114 may useunified message module 113 to communicate the workflow item update as a message. As such, status updates may be communicated via messages based on templates that are suited for workflow item status updates. - In some embodiments,
workflow module 114 may facilitate identification of particular content for use by the entity by allowing the entity to rank or otherwise identify particular content or content creators who create interesting content. For example, continuing the non-limiting example above, a reporter may flag favorite ones of content creators (e.g., social media users who post content) that the reporter believes creates or posts interesting content.Workflow module 114 may store an association of content creators and the reporter such that content from the flagged content creators may be highlighted or otherwise emphasized to the reporter. Such highlighting/emphasis may include displaying content from the flagged content creators at the top of a list, including graphical elements that emphasize the content, and/or other highlighting/emphasis. - In some embodiments,
workflow module 114 may be configured to annotate the content with proprietary or otherwise private information, which may be provided by the entity during the course of managing the content with respect to the workflows.Workflow module 114 may store annotation information in association with the identifier that identifies the content. In this manner, users may provide annotations related to the content that may be stored for later retrieval. In some embodiments, the annotations may include internal comments (e.g., “this is a good photo posted by a user”) made within an organization in relation to the content. - For example, a reporter may be interested in content from a content creator and establish communication with the content creator such as by using
unified message module 113. The content creator may provide the reporter with a phone number or other information so that the reporter may contact the content creator at a later time. The reporter may provide the phone number, a meeting time, and/or other information as an annotation to the content. Other information, such as a text or audio transcription of the interview, interview notes, and/or other information may be provided as an annotation as well.Workflow module 114 may store the annotation information in association with the content. In some embodiments, access to the annotation information may be restricted using user roles and/or other security information. In this manner, entities such as news services and/or others may provide annotations that may be secure and private in relation to content usingworkflow module 114. - The use of content may be subject to various requirements such as permission requirements, attribution requirements, and/or other requirements. The requirements may be related to ownership rights associated with the content such that different owners may impose one or more different requirements for using the content.
- In some embodiments,
clearinghouse module 115 may be configured to manage the requirements, compliance with the requirements, payments, and/or other information related to the requirements.Clearinghouse module 115 may store an association of the content (e.g., the identifier that identifies the content) with an indicator that indicates whether the content is clear to use (e.g., one or more requirements of the content has been satisfied). In this manner, a user may view the content and determine whether the content may be used. - In some embodiments,
clearinghouse module 115 may store an association of the content with the one or more requirements and display the requirements. For example, usingclearinghouse module 115, a user may view the requirements associated with the content to determine what, if anything, is required in order to use the content. - In some embodiments,
clearinghouse module 115 may facilitate messages to owners of the content to obtain permission to use the content. The authorization may include consent to use the content, consent to use the content with attribution, consent to use the content with payment of a fee, a sale of the content for a fee, and/or other authorization to use the content.Clearinghouse module 115 may store the request, consent, non-consent, various communications to and from the owners of the content, and/or other information related to authorization to use the content. - By storing whether content requires permission to use and/or whether such permission has been granted with respect to the content,
clearinghouse module 115 may facilitate a database of content that has been permitted to be used.Clearinghouse module 115 may leverage permission information, geo-location information associated with the content, keyword information, and/or other information known to the system to build a robust and searchable clearinghouse database of content that may be permissibly used and/or licensed to others. For example, a news agency or others who wish to obtain content such as photographs related to a particular geo-location may obtain such content from the clearinghouse database. Thus, content related to rioting in a particular geo-location and obtained from social media and other providers may be found and/or licensed for use from the clearinghouse database. - In some embodiments, for example,
clearinghouse module 115 may be configured to receive a request for content. For example, the request for content may include a search query run on the clearinghouse database and having one or more parameters that specify the search for content. The parameters may include a location parameter, a subject matter parameter, a permission parameter, and/or other parameters. For example, the location parameter may be used to specify one or more geo-locations of interest such that social media and/or other content related to the geo-locations of interest may be returned in the search results. The subject matter parameter may be used to specify one or more subject matter of interest such that social media and/or other content related to the subject matter of interest may be returned in the search results. Subject matter may be determined based on keywords of the content, hashtags, and/or other information related to the content. The permission parameter may be used to filter in or out the content based on whether the content is permitted to be used. Other parameters may be used as well. -
Clearinghouse module 115 may identify at least one content item based on the request for content, which may be subject to one or more requirements.Clearinghouse module 115 may obtain and communicate the one or more requirements. The requester may review the requirements and decide that the requirements are acceptable (e.g., the requester is willing to satisfy the requirements in exchange for permission to use the content item). As such,clearinghouse module 115 may receive an indication that the one or more requirements are satisfactory and that the content item is desired.Clearinghouse module 115 may facilitate provision of the at least one content item and satisfaction of the one or more requirements. For example,clearinghouse module 115 may provide the content item from a memory (e.g., when the content item is stored by the system) and/or from the one or more content providers 150. - In some embodiments,
clearinghouse module 115 may facilitate payment of a fee to use the at least one content item to thereby facilitate satisfaction of the one or more requirements. For example, the payment may include a one-time payment, a recurring payment, a payment based on use of the content, and/or other payment. Payments may be facilitated via one or more accounts related toclearinghouse module 115, conventional electronic payments, paper billing, and/or other payment methods. In this manner,clearinghouse module 115 may facilitate the use of content that may be otherwise subject to ownership rights of the content. - In some embodiments,
clearinghouse module 115 may provide an attribution notice to accompany the at least one content to thereby facilitate satisfaction of the one or more requirements. - In this manner,
clearinghouse module 115 may provide a platform by which owners of content and parties wishing to use the content may use to engage one another and facilitate permission, payments, and/or other activities related to use of the content. - In some embodiments,
administration module 116 may be configured to manage user accounts, set user roles such as security access roles, and/or perform other administrative operations. For example, the administration module may be used to define which users may generate messages using the unified message module, generate workflow items, view workflow items of others, annotate content, enter into agreements with respect to ownership rights of the content, and/or set other user roles. - In some embodiments,
communication module 117 may be configured to share a geofeed via a content provider such as a social media provider, email, SMS text, and/or other communication channels. In some embodiments, the communication module may be configured to communicate a geofeed via various feeds such as Really Simple Syndication (“RSS”) and ATOM feeds, a vanity Uniform Resource Locator (“URL”) using a name of the geofeed (e.g., a name assigned by the content consumer), and/or other communication channels. - In some embodiments, the
user interface module 118 may be configured to generate user interfaces that allow viewing and interaction with the geofeeds. For example, the user interface module may present various displays for sending/receiving messages, managing workflows, managing information related to ownership rights of the content, displaying geofeeds, requesting geofeeds, and/or otherwise displaying information related to the content. - Those having skill in the art will recognize that
computer 110 andcontent consumer device 130 may each comprise one or more processors, one or more interfaces (to various peripheral devices or components), memory, one or more storage devices, and/or other components coupled via a bus. The memory may comprise random access memory (RAM), read only memory (ROM), or other memory. The memory may store computer-executable instructions to be executed by the processor as well as data that may be manipulated by the processor. The storage devices may comprise floppy disks, hard disks, optical disks, tapes, or other storage devices for storing computer-executable instructions and/or data. - One or more applications, including various modules, may be loaded into memory and run on an operating system of
computer 110 and/orconsumer device 130. In one implementation,computer 110 andconsumer device 130 may each comprise a server device, a desktop computer, a laptop, a cell phone, a smart phone, a Personal Digital Assistant, a pocket PC, or other device. -
Network 102 may include any one or more of, for instance, the Internet, an intranet, a PAN (Personal Area Network), a LAN (Local Area Network), a WAN (Wide Area Network), a SAN (Storage Area Network), a MAN (Metropolitan Area Network), a wireless network, a cellular communications network, a Public Switched Telephone Network, and/or other network. -
FIG. 2 illustrates aprocess 200 of targeted messaging related to geofeeds, according to an aspect of the invention. The various processing operations and/or data flows depicted inFIG. 2 (and in the other drawing figures) are described in greater detail herein. The described operations may be accomplished using some or all of the system components described in detail above and, in some embodiments, various operations may be performed in different sequences and various operations may be omitted. Additional operations may be performed along with some or all of the operations shown in the depicted flow diagrams. One or more operations may be performed simultaneously. Accordingly, the operations as illustrated (and described in greater detail below) are exemplary by nature and, as such, should not be viewed as limiting. - In an
operation 202, a selection of one or more content items may be received. The one or more content items may be identified by an internal identifier (e.g., system-generated) and/or an external identifier (e.g., generated by a content provider). The selection may be received from a user viewing one or more geofeeds and selecting the one or more content items, from an automated process such as a process that selects the one or more content items based on keywords, and/or other source. - In an
operation 204, a user that created the one or more content items may be identified. In an example where the one or more content items includes a TWEET,operation 204 may identify the user who generated the TWEET. - In an
operation 206, a mode of communication may be identified. The mode of communication may include, for example, email, social media communication (e.g., a TWEET directed to a TWITTER handle), SMS text, and/or other mode of communication. In some embodiments, the mode of communication may be identified in various ways. For example, the mode of communication may be predefined by one or more rules specified by an entity that wishes to communicate targeted messages, be indicated by a user, and/or other method by which the mode of communication may be identified. - In an
operation 208, a message to be communicated may be obtained. The message may be obtained from various message sources such as a user, one or more message rules (e.g., send a coupon to a user who TWEETS from a restaurant location), and/or other message source. In anoperation 210, the message may be communicated to the identified user via the identified mode of communication. -
Process 200 may be used to automatically and/or manually target messages to users who create content (e.g., post social media or other content that is relevant to a geo-location). In this manner, an entity may target messages to the users based on the content. The messages may serve various purposes such as, for example, requesting authorization to use the content, requesting the user to provide additional content (e.g., the user is at a location where breaking news is occurring and the message requests additional content), providing one or more promotional messages based on the content, and/or other providing other information based on the content. -
FIG. 3 illustrates aprocess 300 of automated messaging related to geofeeds, according to an aspect of the invention. In anoperation 302, one or more message rules may be obtained. In anoperation 304, content may be monitored. For example, an entity may create one or more geofeed definitions that include one or more parameters that specify that the one or more geofeeds should be monitored for automatic messaging. The content related to such geofeed definitions may be obtained “live” from one or more content providers and monitored and/or stored and monitored. - In an
operation 306, a determination of whether the monitored content satisfies the one or more message rules may be made. For example, a message rule may indicate that an automated message should be communicated to users who TWEET or otherwise provide content from a particular location. In another, example, a message rule may indicate that an automated message should be communication to users who provide content that includes certain keywords. Other message rules may be used as well. In some embodiments, the one or more message rules may specify whether to automatically send a message when the content satisfies the message rules, specify the content of the messages, specify who should receive alerts related to the messages, and/or other information related to the message. - When the obtained content does not satisfy the message rules, processing may return to
operation 304, where content is monitored. On the other hand, when the obtained content satisfies the message rules, a determination of whether to automatically send a message may be made in anoperation 308. - When an automated message is to be sent, the user who created the content that satisfies the one or more message rules may be identified in an
operation 310. In anoperation 312, the message may be communicated to the identified user. - Returning to
operation 308, when a message is not to be automatically sent, a user who should receive an alert that the message satisfied the one or more message rules may be identified in anoperation 314. In anoperation 316, an alert to the identified user may be communicated via one or more communication channels. -
FIG. 4 illustrates aprocess 400 of managing permission to use content, according to an aspect of the invention. In anoperation 402, a selection of one or more content items may be received. The one or more content items may be identified by an internal identifier and/or an external identifier. The selection may be received from a user, an automated process, and/or other source. - In an
operation 404, a determination of whether permission is required prior to using (e.g., publishing) the selected content items may be made. When the content items may be used without permission, an indication that the content items are usable may be stored in anoperation 414. - When the content may not be used without permission, a determination of whether to obtain permission to use the content may be made in an
operation 406. When permission to use the content should not be obtained, an indication that the content items are unusable may be stored in anoperation 412. Returning tooperation 406, when permission to use the content should be obtained, a message to obtain the permission may be generated in anoperation 408. For example, an owner of or other holder of rights to the content may be identified and a message to the owner that requests permission to use the content may be generated. - In an
operation 412, a determination of whether permission has been obtained may be made. For example, the owner of the content may provide permission to use the content. If permission has not been obtained (e.g., permission has been denied), an indication that the content is unusable may be stored inoperation 412. If permission has been obtained, an indication that the content is usable may be stored inoperation 414. -
Process 400 may be used to ensure that permissions with respect to using content is verified and obtained when such permission may be necessary. The usable and unusable indicators may be used to verify that use of such content is permitted before publishing or otherwise using the content. For example, prior to content being published, the usable and/or unusable indicator (which may be stored in one or more fields of a database, for example) may be referenced to determine whether the content may be published without potentially overstepping use rights (e.g., copyright) related to the content. In some embodiments, the indicators may be automatically and/or manually maintained. -
FIG. 5 illustrates aprocess 500 of managing payments related to use of content, according to an aspect of the invention. In anoperation 502, an indication that content is permitted may be obtained. In anoperation 504, the indication may be stored. In anoperation 506, an indication that the content was used may be received. In anoperation 508, a determination of whether a royalty or payment is associated with the use may be made. When a royalty is not associated with the use, an indication of the use may be stored in anoperation 514. The indication may be stored solely for informational purposes. When a royalty is associated with the use, a determination of whether the royalty is related to a royalty per use may be made. When the royalty is not a per use royalty (e.g., a lump sum payment was made in exchange for permission to use the content), an indication of the use may be stored inoperation 514. - When the royalty include a per use royalty, a royalty payment for the use may be facilitated in an
operation 512. For example, a royalty fee based on the use may be determined. In some embodiments, the royalty fee may be determined based on a count of the number of uses of the content in a time period and a per use fee associated with the content. In some embodiments,process 500 may facilitate various payment methods from the user of the content to the holder of rights of the content, whether the royalty is a lump sum fee, per use fee, and/or other type of fee arrangement. -
FIG. 6 illustrates a process 600 of managing workflows related to geofeeds, according to an aspect of the invention. In anoperation 602, a workflow item request for a workflow item to be resolved in relation to content may be received. In anoperation 604, the workflow item may be generated and stored. For example, the workflow item may be assigned with a workflow item identifier and the workflow item identifier may be stored in association with a workflow item description, a workflow item type, a date, a workflow item status, a requester, a resolver, and/or other information related to the workflow item. - In an
operation 606, an identification of a resolver may be obtained. In some embodiments, the requester and the resolver may be the same or different user. The identification may be obtained from the workflow item request (e.g., the requester may specify who should handle the workflow item), automatically obtained based on user roles, user relationships, or other information, and/or from other information sources. In anoperation 608, the workflow item may be assigned to the identified resolver. In some embodiments, an indication of the progress of the workflow item may be received in anoperation 610. The indication of the progress may be received from the requester, the resolver, an automated process that monitors the workflow item, and/or other source of information. In anoperation 612, the workflow item status may be updated based on the indication of progress. - In some embodiments, process 600 may include communicating information to the requester, the resolver, and/or others. The information may relate to a progress of the workflow item (e.g., status updates), information relevant to the workflow item, and/or other information.
-
FIG. 7 illustrates a process 700 of identifying content to be managed in a workflow, according to an aspect of the invention. In anoperation 702, a selection of one or more content items may be received. The one or more content items may be identified by an internal identifier and/or an external identifier. The selection may be received from a user, an automated process, and/or other source. - In an
operation 704, proximate content related to a location within a predefined or otherwise configurable proximity of a location related to the selected content items may be obtained. For example, for a selected content item that is relevant to a geo-location, proximate content within a five mile radius or other proximity may be obtained. In this manner, process 700 facilitates using particular content items of interest to potentially discover other related content items of interest. - In an
operation 706, the proximate content may be communicated. For example, the proximate content may be communicated via a display and/or other communication channels. In anoperation 708, one or more workflow items to be resolved in relation to the content items and/or the proximate content items may be received. In anoperation 710, the one or more workflow items may be managed, such as in a manner similar to process 600. -
FIG. 8 illustrates aprocess 800 of annotating content of a geofeed, according to an aspect of the invention. In anoperation 802, a selection of one or more content items may be received. The one or more content items may be identified by an internal identifier and/or an external identifier. The selection may be received from a user, an automated process, and/or other source. - In an
operation 804, one or more annotations to the selected content items may be received. The one or more annotations may include information added to the selected content items (and/or updates or removal of information from the selected content items). Typically although not necessarily, the annotations may facilitate internal workflows. For example, a reporter may annotate a TWEET with a user's phone number that the reporter obtained.Process 800 may receive such annotations for processing. - In an
operation 806, the one or more annotations may be stored in association with the selected content items. In anoperation 808, one or more security settings may be applied to control access to the one or more annotations. For example, the security settings may restrict access (e.g., read, write, delete, and/or other types of access) to the annotations to only a user who made the annotations, particular users of an entity, users having particular user roles, and/or other users. - In an
operation 810, a request to view the content items may be received. In anoperation 812, a determination of whether the requester is authorized to access the annotations made be made. When the requester is authorized to access the annotations, the annotations may be communicated in anoperation 814 and the content items may be communicated in anoperation 816. When the requester is not authorized to access the annotations, only the content items may be communicated inoperation 816. -
FIG. 9 illustrates a screenshot of aninterface 900 for displaying content items with access to targeted messaging, workflows, and rights management, according to an aspect of the invention. The screenshots illustrated inFIG. 9 are for illustrative purposes only. Various components may be added, deleted, moved, or otherwise changed so that the configuration, appearance, and/or content of the screenshots may be different than as illustrated in the figures. Accordingly, the graphical user interface objects as illustrated (and described in greater detail below) are exemplary by nature and, as such, should not be viewed as limiting. -
Interface 900 may be implemented as a web page communicated fromcomputer 110 to a client, an application such as a mobile application executing on the client that receives generates the interface based on information communicated fromcomputer 110, and/or other interface. Whichever type of interface is used,computer 110 may communicate the data and/or formatting instructions related to the interface to the client, causing the client to generate the interface ofFIG. 9 and other drawing figures. Furthermore,computer 110 may receive data from the client via the various interfaces, as would be appreciated. - To switch between the different views of geofeeds, a
navigation element 904 having links or other controls that switch between the “MAP” display illustrated inFIG. 9 , a “COLLAGE” display, and a “LIST” display. - The geofeed as illustrated (bounded by circle 930) includes
content indicators 932 and 634, which provide graphical indicia of aggregated content of the geofeed. The content may be provided from different or the same content provider.Content indicators content indicator 932 is selected (e.g., moused over, clicked, touched, or otherwise interacted with)interface 900 may causeworkflow interface 940 to appear.Workflow interface 940 may include acomponent 941 that includes information related to the content such as, for example, the content itself, a content creator (e.g., social media user who posted the content), an identification of the content provider that provided the content, a time associated with the content (e.g., create time, publication time, etc.), a location where the content was created (e.g., address, geo-coordinates, etc.), and/or other information known or determined about the content. - In some embodiments,
component 942 may include an interface or links to an interface that provides targeted messaging functions. For example, usingcomponent 942, a targeted message may be directed to the content creator associated with the content indicated bycontent indicator 932. - In some embodiments,
component 943 may include an interface or links to an interface that provides digital rights or other functions relation to permission to use content. For example, usingcomponent 943, whether content indicated bycontent indicator 932 is permitted to be used in an entity's website may be determined. If such permission is required and not yet obtained,component 943 may be used to obtain such permission. - In some embodiments,
component 944 may include an interface or links to an interface that provides workflow functions. For example, usingcomponent 944, various workflow items related to the content indicated bycontent indicator 932 may be generated and tracked.Other components 945 related to other features related to the content indicated bycontent indicator 932 may be provided as well. - Other embodiments, uses and advantages of the invention will be apparent to those skilled in the art from consideration of the specification and practice of the invention disclosed herein. The specification should be considered exemplary only, and the scope of the invention is accordingly intended to be limited only by the following claims.
Claims (32)
Priority Applications (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US13/788,909 US8850531B1 (en) | 2013-03-07 | 2013-03-07 | System and method for targeted messaging, workflow management, and digital rights management for geofeeds |
US14/500,881 US9443090B2 (en) | 2013-03-07 | 2014-09-29 | System and method for targeted messaging, workflow management, and digital rights management for geofeeds |
US15/241,926 US10044732B2 (en) | 2013-03-07 | 2016-08-19 | System and method for targeted messaging, workflow management, and digital rights management for geofeeds |
US16/056,336 US10530783B2 (en) | 2013-03-07 | 2018-08-06 | System and method for targeted messaging, workflow management, and digital rights management for geofeeds |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US13/788,909 US8850531B1 (en) | 2013-03-07 | 2013-03-07 | System and method for targeted messaging, workflow management, and digital rights management for geofeeds |
Related Child Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US14/500,881 Continuation US9443090B2 (en) | 2013-03-07 | 2014-09-29 | System and method for targeted messaging, workflow management, and digital rights management for geofeeds |
Publications (2)
Publication Number | Publication Date |
---|---|
US20140259113A1 true US20140259113A1 (en) | 2014-09-11 |
US8850531B1 US8850531B1 (en) | 2014-09-30 |
Family
ID=51489614
Family Applications (4)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US13/788,909 Active US8850531B1 (en) | 2013-03-07 | 2013-03-07 | System and method for targeted messaging, workflow management, and digital rights management for geofeeds |
US14/500,881 Active US9443090B2 (en) | 2013-03-07 | 2014-09-29 | System and method for targeted messaging, workflow management, and digital rights management for geofeeds |
US15/241,926 Active US10044732B2 (en) | 2013-03-07 | 2016-08-19 | System and method for targeted messaging, workflow management, and digital rights management for geofeeds |
US16/056,336 Active US10530783B2 (en) | 2013-03-07 | 2018-08-06 | System and method for targeted messaging, workflow management, and digital rights management for geofeeds |
Family Applications After (3)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US14/500,881 Active US9443090B2 (en) | 2013-03-07 | 2014-09-29 | System and method for targeted messaging, workflow management, and digital rights management for geofeeds |
US15/241,926 Active US10044732B2 (en) | 2013-03-07 | 2016-08-19 | System and method for targeted messaging, workflow management, and digital rights management for geofeeds |
US16/056,336 Active US10530783B2 (en) | 2013-03-07 | 2018-08-06 | System and method for targeted messaging, workflow management, and digital rights management for geofeeds |
Country Status (1)
Country | Link |
---|---|
US (4) | US8850531B1 (en) |
Cited By (20)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20140359023A1 (en) * | 2013-05-30 | 2014-12-04 | Dropbox, Inc. | Content-item relationship messaging system |
US20150046452A1 (en) * | 2013-08-06 | 2015-02-12 | International Business Machines Corporation | Geotagging unstructured text |
US8990346B2 (en) | 2012-12-07 | 2015-03-24 | Geofeedia, Inc. | System and method for location monitoring based on organized geofeeds |
US9055074B2 (en) | 2012-09-14 | 2015-06-09 | Geofeedia, Inc. | System and method for generating, accessing, and updating geofeeds |
US9077782B2 (en) | 2013-03-07 | 2015-07-07 | Geofeedia, Inc. | System and method for creating and managing geofeeds |
US9077675B2 (en) | 2012-12-07 | 2015-07-07 | Geofeedia, Inc. | System and method for generating and managing geofeed-based alerts |
WO2016003728A1 (en) * | 2014-07-01 | 2016-01-07 | Tuul, Inc. | System and method for implementing workflow management using messaging |
US9258373B2 (en) | 2013-03-15 | 2016-02-09 | Geofeedia, Inc. | System and method for generating three-dimensional geofeeds, orientation-based geofeeds, and geofeeds based on ambient conditions based on content provided by social media content providers |
US9307353B2 (en) | 2013-03-07 | 2016-04-05 | Geofeedia, Inc. | System and method for differentially processing a location input for content providers that use different location input formats |
US9317600B2 (en) | 2013-03-15 | 2016-04-19 | Geofeedia, Inc. | View of a physical space augmented with social media content originating from a geo-location of the physical space |
US9436690B2 (en) | 2013-03-15 | 2016-09-06 | Geofeedia, Inc. | System and method for predicting a geographic origin of content and accuracy of geotags related to content obtained from social media and other content providers |
US9443090B2 (en) | 2013-03-07 | 2016-09-13 | Geofeedia, Inc. | System and method for targeted messaging, workflow management, and digital rights management for geofeeds |
US9485318B1 (en) | 2015-07-29 | 2016-11-01 | Geofeedia, Inc. | System and method for identifying influential social media and providing location-based alerts |
US20170019450A1 (en) * | 2015-07-17 | 2017-01-19 | Tribune Broadcasting Company, Llc | Media production system with social media feature |
CN107317812A (en) * | 2017-06-27 | 2017-11-03 | 福建中金在线信息科技有限公司 | A kind of method, device, electronic equipment and storage medium for searching pirate user |
US10373212B2 (en) * | 2013-03-14 | 2019-08-06 | Facebook, Inc. | Methods for linking images in social feeds to branded content |
EP3467692A4 (en) * | 2016-05-27 | 2019-11-27 | Tencent Technology (Shenzhen) Company Limited | Message permission management method and device, and storage medium |
US10726090B1 (en) | 2013-04-05 | 2020-07-28 | Hrl Laboratories, Llc | Per-user accuracy measure for social network based geocoding algorithms |
US20200273225A1 (en) * | 2019-02-25 | 2020-08-27 | Life Impact Solutions, Inc. | Media Alteration Based On Variable Geolocation Metadata |
US20210182890A1 (en) * | 2015-12-30 | 2021-06-17 | Paypal, Inc. | Data structures for categorizing and filtering content |
Families Citing this family (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20150332318A1 (en) * | 2014-05-15 | 2015-11-19 | CDK Global, Inc. | System and method for obtaining a release authorization |
US10650621B1 (en) | 2016-09-13 | 2020-05-12 | Iocurrents, Inc. | Interfacing with a vehicular controller area network |
Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20070121843A1 (en) * | 2005-09-02 | 2007-05-31 | Ron Atazky | Advertising and incentives over a social network |
US20120259791A1 (en) * | 2011-04-07 | 2012-10-11 | Sabina Zoidze | System and method for social networking |
US20120323687A1 (en) * | 2011-06-20 | 2012-12-20 | Shopping Made Mobile, Inc. | Mobile Messaging and Data Tracking Platform |
US8341223B1 (en) * | 2011-06-07 | 2012-12-25 | Banjo, Inc. | Method for relevant content discovery |
US8595317B1 (en) * | 2012-09-14 | 2013-11-26 | Geofeedr, Inc. | System and method for generating, accessing, and updating geofeeds |
Family Cites Families (167)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6026368A (en) * | 1995-07-17 | 2000-02-15 | 24/7 Media, Inc. | On-line interactive system and method for providing content and advertising information to a targeted set of viewers |
US6535878B1 (en) | 1997-05-02 | 2003-03-18 | Roxio, Inc. | Method and system for providing on-line interactivity over a server-client network |
US5983267A (en) | 1997-09-23 | 1999-11-09 | Information Architects Corporation | System for indexing and displaying requested data having heterogeneous content and representation |
US6128655A (en) | 1998-07-10 | 2000-10-03 | International Business Machines Corporation | Distribution mechanism for filtering, formatting and reuse of web based content |
US6226618B1 (en) | 1998-08-13 | 2001-05-01 | International Business Machines Corporation | Electronic content delivery system |
US7076737B2 (en) | 1998-12-18 | 2006-07-11 | Tangis Corporation | Thematic response to a computer user's context, such as by a wearable personal computer |
EP1045345A1 (en) | 1999-04-13 | 2000-10-18 | Idc Ltd. | Navigation system display of search engine retrieved data selected according to user-given geographical criteria |
US6591266B1 (en) | 2000-07-14 | 2003-07-08 | Nec Corporation | System and method for intelligent caching and refresh of dynamically generated and static web content |
US20020029384A1 (en) | 2000-07-20 | 2002-03-07 | Griggs Theodore L. | Mechanism for distributing content data |
AUPQ921400A0 (en) | 2000-08-04 | 2000-08-31 | Canon Kabushiki Kaisha | Method of enabling browse and search access to electronically-accessible multimedia databases |
US6363320B1 (en) | 2000-08-18 | 2002-03-26 | Geospatial Technologies Inc. | Thin-client real-time interpretive object tracking system |
US20020029226A1 (en) | 2000-09-05 | 2002-03-07 | Gang Li | Method for combining data with maps |
WO2002023444A1 (en) * | 2000-09-15 | 2002-03-21 | Mobliss, Inc. | System for conducting user-specific promotional campaigns using multiple communications device platforms |
EP1233590A1 (en) | 2001-02-19 | 2002-08-21 | Sun Microsystems, Inc. | Content provider for a computer system |
US20020188669A1 (en) | 2001-06-11 | 2002-12-12 | Levine Marc Jay | Integrated method for disseminating large spatial data sets in a distributed form via the internet |
US7383561B2 (en) | 2001-06-29 | 2008-06-03 | Nokia Corporation | Conditional access system |
US7908628B2 (en) | 2001-08-03 | 2011-03-15 | Comcast Ip Holdings I, Llc | Video and digital multimedia aggregator content coding and formatting |
US7089198B2 (en) | 2001-08-21 | 2006-08-08 | Itt Manufacturing Enterprises, Inc. | User selectable earth imagery on-line e-commerce and fulfillment system |
US7680796B2 (en) * | 2003-09-03 | 2010-03-16 | Google, Inc. | Determining and/or using location information in an ad system |
US20040203854A1 (en) | 2002-04-26 | 2004-10-14 | Nowak Steven P. | Formatting location information based on output device specifications |
US6996571B2 (en) | 2002-06-28 | 2006-02-07 | Microsoft Corporation | XML storage solution and data interchange file format structure |
US7475060B2 (en) | 2003-05-09 | 2009-01-06 | Planeteye Company Ulc | Browsing user interface for a geo-coded media database |
US7636901B2 (en) | 2003-06-27 | 2009-12-22 | Cds Business Mapping, Llc | System for increasing accuracy of geocode data |
US20060002317A1 (en) | 2004-07-01 | 2006-01-05 | Punaganti Venkata Murali Krish | Information feeder framework |
US8953887B2 (en) | 2004-07-09 | 2015-02-10 | Terrago Technologies, Inc. | Processing time-based geospatial data |
US8675995B2 (en) | 2004-07-09 | 2014-03-18 | Terrago Technologies, Inc. | Precisely locating features on geospatial imagery |
US20060059227A1 (en) | 2004-09-14 | 2006-03-16 | Randy Zimler | Methods, systems and storage medium for displaying content in response to a consumer format preference |
US7743048B2 (en) | 2004-10-29 | 2010-06-22 | Microsoft Corporation | System and method for providing a geographic search function |
US7522940B2 (en) | 2004-11-16 | 2009-04-21 | Sony Ericsson Mobile Communications Ab | Methods and mobile terminals for display of mobile terminal density information |
US7584449B2 (en) | 2004-11-22 | 2009-09-01 | Fulcrum Microsystems, Inc. | Logic synthesis of multi-level domino asynchronous pipelines |
US20080189099A1 (en) | 2005-01-12 | 2008-08-07 | Howard Friedman | Customizable Delivery of Audio Information |
US20060184968A1 (en) | 2005-02-11 | 2006-08-17 | Clayton Richard M | Automatic content update for a target device |
AU2006220547B2 (en) | 2005-03-07 | 2010-12-02 | Telecommunication Systems, Inc. | Method and system for identifying and defining geofences |
US20070210937A1 (en) | 2005-04-21 | 2007-09-13 | Microsoft Corporation | Dynamic rendering of map information |
US8417697B2 (en) | 2005-08-22 | 2013-04-09 | Google Inc. | Permitting users to remove documents |
US7933897B2 (en) | 2005-10-12 | 2011-04-26 | Google Inc. | Entity display priority in a distributed geographic information system |
US7840558B2 (en) | 2005-11-04 | 2010-11-23 | Microsoft Corporation | Geo-tagged based listing service and mapping engine |
CA2637567A1 (en) | 2006-01-17 | 2007-07-26 | Carbon Project, Inc. | Methods for using geospatial information as geospatial session files |
WO2007100743A2 (en) | 2006-02-24 | 2007-09-07 | Verisign, Inc. | System and method for cross-carrier mobile device capability discovery |
US8099431B2 (en) | 2006-05-12 | 2012-01-17 | Sap Ag | Services for data access based on a data ownership directory in distributed system landscapes |
US20090300528A1 (en) | 2006-09-29 | 2009-12-03 | Stambaugh Thomas M | Browser event tracking for distributed web-based processing, spatial organization and display of information |
US8756510B2 (en) | 2006-10-17 | 2014-06-17 | Cooliris, Inc. | Method and system for displaying photos, videos, RSS and other media content in full-screen immersive view and grid-view using a browser feature |
US7698336B2 (en) | 2006-10-26 | 2010-04-13 | Microsoft Corporation | Associating geographic-related information with objects |
WO2008064171A1 (en) | 2006-11-20 | 2008-05-29 | At & T Corp. | Method and apparatus for providing geospatial and temporal navigation |
US9282446B2 (en) | 2009-08-06 | 2016-03-08 | Golba Llc | Location-aware content and location-based advertising with a mobile device |
US8280871B2 (en) | 2006-12-29 | 2012-10-02 | Yahoo! Inc. | Identifying offensive content using user click data |
US7912451B2 (en) | 2007-02-26 | 2011-03-22 | Sony Ericsson Mobile Communications Ab | Limiting use of electronic equipment features based on location |
US10528629B2 (en) | 2007-04-03 | 2020-01-07 | Oath Inc. | Systems and methods for providing syndicated content |
WO2008128133A1 (en) | 2007-04-13 | 2008-10-23 | Pelago, Inc. | Location-based information determination |
US20080294607A1 (en) * | 2007-05-23 | 2008-11-27 | Ali Partovi | System, apparatus, and method to provide targeted content to users of social networks |
US7984068B2 (en) | 2007-05-25 | 2011-07-19 | Google Inc. | Providing profile information to partner content providers |
EP2154481B1 (en) | 2007-05-31 | 2024-07-03 | Panasonic Intellectual Property Corporation of America | Image capturing device, additional information providing server, and additional information filtering system |
US8180396B2 (en) | 2007-10-18 | 2012-05-15 | Yahoo! Inc. | User augmented reality for camera-enabled mobile devices |
RU2010123016A (en) | 2007-11-06 | 2011-12-20 | Теле Атлас Норт Америка Инк. (Us) | METHOD AND SYSTEM FOR USING MEASUREMENT DATA FROM MANY VEHICLES FOR DETECTING REAL-WORLD CHANGES FOR USE WHEN MAP UPDATES |
US20090132435A1 (en) | 2007-11-21 | 2009-05-21 | Microsoft Corporation | Popularity based licensing of user generated content |
US7778967B2 (en) | 2008-02-14 | 2010-08-17 | Ambercore Software Inc. | System and method for efficient management of distributed spatial data |
US8635192B2 (en) | 2008-02-28 | 2014-01-21 | Blackberry Limited | Method of automatically geotagging data |
US7882201B2 (en) | 2008-03-31 | 2011-02-01 | Verizon Patent And Licensing Inc. | Location based content aggregation and distribution systems and methods |
US8238891B1 (en) * | 2008-05-01 | 2012-08-07 | Wendy W. Tam | Method and system for interactive delivery of data content to mobile devices |
US9646025B2 (en) | 2008-05-27 | 2017-05-09 | Qualcomm Incorporated | Method and apparatus for aggregating and presenting data associated with geographic locations |
US8566353B2 (en) | 2008-06-03 | 2013-10-22 | Google Inc. | Web-based system for collaborative generation of interactive videos |
US8396883B2 (en) | 2008-06-23 | 2013-03-12 | Hewlett-Packard Development Company, L.P. | Spatial querying in a data warehouse |
US8103618B2 (en) | 2008-06-27 | 2012-01-24 | Surfmap, Inc. | Hosted system for enabling enterprises to build and operate online communities |
US9129317B2 (en) | 2008-07-08 | 2015-09-08 | Verizon Patent And Licensing Inc. | Method, medium, and system for providing location aware classified content |
US20100030648A1 (en) | 2008-08-01 | 2010-02-04 | Microsoft Corporation | Social media driven advertisement targeting |
GB2457968A (en) | 2008-08-06 | 2009-09-02 | John W Hannay & Co Ltd | Forming a presentation of content |
US8578274B2 (en) | 2008-09-26 | 2013-11-05 | Radius Intelligence. Inc. | System and method for aggregating web feeds relevant to a geographical locale from multiple sources |
US20100079338A1 (en) * | 2008-09-30 | 2010-04-01 | Clear Channel Management Services, Inc. | Promotion Using Geopositioning Technology |
WO2010049918A1 (en) | 2008-10-31 | 2010-05-06 | France Telecom | User interface to provide plurality of inter-related geo-content |
US20100121707A1 (en) | 2008-11-13 | 2010-05-13 | Buzzient, Inc. | Displaying analytic measurement of online social media content in a graphical user interface |
EP2187594A1 (en) | 2008-11-18 | 2010-05-19 | Alcatel Lucent | Open content distribution platform for media delivery systems |
US9100223B2 (en) | 2008-12-01 | 2015-08-04 | Google Inc. | Selecting format for content distribution |
US20100145947A1 (en) | 2008-12-05 | 2010-06-10 | Bliin B.V. | Method and apparatus for an inventive geo-network |
US8122024B2 (en) | 2008-12-12 | 2012-02-21 | Research In Motion Limited | Method and system for storing multiple geo-tagged media files and rendering the same |
US8965920B2 (en) | 2008-12-15 | 2015-02-24 | Verizon Patent Licensing Inc. | Distributing and sharing content in a network |
US20100174998A1 (en) | 2009-01-06 | 2010-07-08 | Kiha Software Inc. | Calendaring Location-Based Events and Associated Travel |
US20100180001A1 (en) | 2009-01-11 | 2010-07-15 | Dick Clarence Hardt | Contextual messaging and notification system |
US20100177120A1 (en) | 2009-01-13 | 2010-07-15 | Balfour Technologies Llc | System and method for stretching 3d/4d spatial hierarchy models for improved viewing |
WO2010144395A2 (en) | 2009-06-10 | 2010-12-16 | Ancestralhunt Partners, Llc | System and method for the collaborative collection, assignment, visualization, analysis and modification of probable genealogical relationships based on geo-spatial and temporal proximity |
US20120150901A1 (en) | 2009-07-10 | 2012-06-14 | Geodex, Llc | Computerized System and Method for Tracking the Geographic Relevance of Website Listings and Providing Graphics and Data Regarding the Same |
US8558847B2 (en) | 2009-07-13 | 2013-10-15 | Raytheon Company | Displaying situational information based on geospatial data |
US8380878B2 (en) | 2009-08-13 | 2013-02-19 | Cox Communications, Inc. | Side loading |
US20120109752A1 (en) * | 2009-08-19 | 2012-05-03 | Vitrue, Inc. | Systems and methods for delivering targeted content to a consumer's mobile device based on the consumer's physical location and social media memberships |
KR101105970B1 (en) | 2009-09-02 | 2012-01-17 | 한국전자통신연구원 | Media mediator system and method for managing contents of various format |
US8312079B2 (en) | 2009-09-22 | 2012-11-13 | Thwapr, Inc. | Adaptive rendering for mobile media sharing |
GB0916989D0 (en) | 2009-09-29 | 2009-11-11 | Winterstein Daniel B | The use of machine learning in a social media workflow tool |
US8312273B2 (en) | 2009-10-07 | 2012-11-13 | Microsoft Corporation | Privacy vault for maintaining the privacy of user profiles |
AU2010319685A1 (en) | 2009-11-10 | 2012-06-21 | Youdiligence Llc | System and method for monitoring activity of a specified user on internet-based social networks |
US11122009B2 (en) | 2009-12-01 | 2021-09-14 | Apple Inc. | Systems and methods for identifying geographic locations of social media content collected over social networks |
US20110137561A1 (en) | 2009-12-04 | 2011-06-09 | Nokia Corporation | Method and apparatus for measuring geographic coordinates of a point of interest in an image |
US20110153368A1 (en) | 2009-12-17 | 2011-06-23 | XtremeGIS, Inc. | User Interactive Reinsurance Risk Analysis Application |
US9747604B2 (en) | 2010-01-22 | 2017-08-29 | Google Inc. | Automated agent for social media systems |
US20110202544A1 (en) | 2010-02-12 | 2011-08-18 | Praized Media Inc. | Real time aggregation and filtering of local data feeds |
US8477425B2 (en) | 2010-02-28 | 2013-07-02 | Osterhout Group, Inc. | See-through near-eye display glasses including a partially reflective, partially transmitting optical element |
US8909629B2 (en) | 2010-03-22 | 2014-12-09 | Google Inc. | Personalized location tags |
US8788606B2 (en) | 2010-04-09 | 2014-07-22 | Weather Decision Technologies, Inc. | Multimedia alerting |
US20110288917A1 (en) * | 2010-05-21 | 2011-11-24 | James Wanek | Systems and methods for providing mobile targeted advertisements |
US20110307307A1 (en) | 2010-06-09 | 2011-12-15 | Akram Benmbarek | Systems and methods for location based branding |
US8963954B2 (en) | 2010-06-30 | 2015-02-24 | Nokia Corporation | Methods, apparatuses and computer program products for providing a constant level of information in augmented reality |
US9262517B2 (en) | 2010-08-18 | 2016-02-16 | At&T Intellectual Property I, L.P. | Systems and methods for social media data mining |
US9008693B2 (en) | 2010-09-24 | 2015-04-14 | Nokia Corporation | Method and apparatus for information aggregation around locations |
US20120084323A1 (en) | 2010-10-02 | 2012-04-05 | Microsoft Corporation | Geographic text search using image-mined data |
US20120101880A1 (en) * | 2010-10-05 | 2012-04-26 | WeatherAlpha, LLC. | Digital Communication Management System |
US9009770B2 (en) | 2010-11-11 | 2015-04-14 | Turner Broadcasting System, Inc. | Methods and systems for media consumption |
US10148623B2 (en) | 2010-11-12 | 2018-12-04 | Time Warner Cable Enterprises Llc | Apparatus and methods ensuring data privacy in a content distribution network |
US20120158536A1 (en) | 2010-12-16 | 2012-06-21 | Dish Network L.L.C. | Identifying content purchasing options based on user preferences |
US8478701B2 (en) | 2010-12-22 | 2013-07-02 | Yahoo! Inc. | Locating a user based on aggregated tweet content associated with a location |
US8812951B1 (en) | 2010-12-28 | 2014-08-19 | Amazon Technologies, Inc. | Publisher formatting controls |
US8572157B2 (en) | 2011-01-31 | 2013-10-29 | Microsoft Corporation | Configuration based approach to unify web services |
US20120200403A1 (en) | 2011-02-09 | 2012-08-09 | Robert Paul Morris | Methods, systems, and computer program products for directing attention to a sequence of viewports of an automotive vehicle |
US20120209826A1 (en) | 2011-02-10 | 2012-08-16 | Nokia Corporation | Method and apparatus for providing location based information |
US20120221687A1 (en) * | 2011-02-27 | 2012-08-30 | Broadcastr, Inc. | Systems, Methods and Apparatus for Providing a Geotagged Media Experience |
US9083747B2 (en) | 2011-03-07 | 2015-07-14 | Facebook, Inc. | Automated location check-in for geo-social networking system |
US9342851B2 (en) | 2011-03-14 | 2016-05-17 | Shazam Entertainment Ltd. | Systems and methods for aggregating and filtering content of social media activity |
US20120254774A1 (en) | 2011-03-30 | 2012-10-04 | Banjo, Inc. | Method for managing a local messaging platform |
US8694010B2 (en) | 2011-04-26 | 2014-04-08 | Xirrus, Inc. | Wireless array device and system for managing wireless arrays having magnetometers |
US9392573B2 (en) | 2011-04-26 | 2016-07-12 | Xirrius, Inc. | Method for determining a geospatial location of a client in signal communication with a wireless array |
US8977964B2 (en) * | 2011-05-17 | 2015-03-10 | Next Issue Media | Media content device, system and method |
US20120330959A1 (en) | 2011-06-27 | 2012-12-27 | Raytheon Company | Method and Apparatus for Assessing a Person's Security Risk |
US20130018838A1 (en) | 2011-07-14 | 2013-01-17 | Parnaby Tracey J | System and Method for Social Influence Credentialing within a Sentiment Sharing Community |
US8917902B2 (en) | 2011-08-24 | 2014-12-23 | The Nielsen Company (Us), Llc | Image overlaying and comparison for inventory display auditing |
US8806188B2 (en) | 2011-08-31 | 2014-08-12 | Sonic Ip, Inc. | Systems and methods for performing adaptive bitrate streaming using automatically generated top level index files |
US20130054672A1 (en) | 2011-08-31 | 2013-02-28 | Roy Peter John Stilling | Systems and methods for contextualizing a toolbar |
US20130060796A1 (en) | 2011-09-07 | 2013-03-07 | Thomas J. Gilg | Content aggregation and mapping |
US20130060744A1 (en) | 2011-09-07 | 2013-03-07 | Microsoft Corporation | Personalized Event Search Experience using Social data |
US10127564B2 (en) | 2011-09-15 | 2018-11-13 | Stephan HEATH | System and method for using impressions tracking and analysis, location information, 2D and 3D mapping, mobile mapping, social media, and user behavior and information for generating mobile and internet posted promotions or offers for, and/or sales of, products and/or services |
US10127563B2 (en) | 2011-09-15 | 2018-11-13 | Stephan HEATH | System and method for providing sports and sporting events related social/geo/promo link promotional data sets for end user display of interactive ad links, promotions and sale of products, goods, gambling and/or services integrated with 3D spatial geomapping, company and local information for selected worldwide locations and social networking |
US8566517B1 (en) | 2011-10-06 | 2013-10-22 | Crossroads Systems, Inc. | System, method and computer program product for optimization of tape performance using distributed file copies |
US20130110583A1 (en) | 2011-10-28 | 2013-05-02 | Justin Ormont | Multiple social media network analysis for user conflation and related advertising methods |
US8655873B2 (en) * | 2011-10-28 | 2014-02-18 | Geofeedr, Inc. | System and method for aggregating and distributing geotagged content |
DE102011118157A1 (en) | 2011-11-10 | 2013-05-16 | GM Global Technology Operations LLC (n. d. Gesetzen des Staates Delaware) | Method for operating an information and entertainment system of a motor vehicle and information and entertainment system |
US9466071B2 (en) | 2011-11-16 | 2016-10-11 | Yahoo! Inc. | Social media user recommendation system and method |
US20130132194A1 (en) | 2011-11-17 | 2013-05-23 | Giridhar Rajaram | Targeting advertisements to users of a social networking system based on events |
PL2605144T3 (en) | 2011-12-13 | 2020-11-16 | Telefonaktiebolaget Lm Ericsson (Publ) | Method and apparatus for caching |
US9286642B2 (en) * | 2011-12-16 | 2016-03-15 | Facebook, Inc. | Content access management in a social networking system for externally stored content |
US20130159463A1 (en) * | 2011-12-20 | 2013-06-20 | Frisco Smartapps, LLC | Method and system for targeted transmission of content |
JP2013162487A (en) | 2012-02-08 | 2013-08-19 | Canon Inc | Image display apparatus and imaging apparatus |
US20130268558A1 (en) | 2012-03-07 | 2013-10-10 | Snap Trends, Inc. | Methods and Systems of Aggregating Information of Social Networks Based on Changing Geographical Locations of a Computing Device Via a Network |
US9626446B2 (en) | 2012-03-07 | 2017-04-18 | Snap Trends, Inc. | Methods and systems of advertising based on aggregated information of social networks within geographical locations via a network |
US9230257B2 (en) | 2012-03-30 | 2016-01-05 | Sap Se | Systems and methods for customer relationship management |
US9338061B2 (en) | 2012-04-26 | 2016-05-10 | Hewlett Packard Enterprise Development Lp | Open station as a stream analysis operator container |
US20130290207A1 (en) | 2012-04-30 | 2013-10-31 | Gild, Inc. | Method, apparatus and computer program product to generate psychological, emotional, and personality information for electronic job recruiting |
US8612348B1 (en) | 2012-05-23 | 2013-12-17 | Mp Platforms, Llc | Systems and methods for interfacing merchants with third-party service providers |
US9319470B2 (en) | 2012-05-30 | 2016-04-19 | Henry Berberat | Location-based social networking system |
CN102710789B (en) | 2012-06-20 | 2017-03-22 | 腾讯科技(深圳)有限公司 | Interaction method, system and device for data between intelligent terminals |
US8910220B2 (en) | 2012-07-12 | 2014-12-09 | Time Warner Cable Enterprises Llc | Multi-format distribution of content |
US8428228B1 (en) * | 2012-09-18 | 2013-04-23 | Weerawan Wongmanee | Unified communication system |
US20140089343A1 (en) | 2012-09-25 | 2014-03-27 | Snap Trends, Inc. | Methods and Systems for Monitoring and Controlling Social Network Communications Over a Network at a Secure Location |
US20140095509A1 (en) | 2012-10-02 | 2014-04-03 | Banjo, Inc. | Method of tagging content lacking geotags with a location |
US20140143346A1 (en) | 2012-11-16 | 2014-05-22 | International Business Machines Corporation | Identifying And Classifying Travelers Via Social Media Messages |
US8484224B1 (en) | 2012-12-07 | 2013-07-09 | Geofeedr, Inc. | System and method for ranking geofeeds and content within geofeeds |
US8639767B1 (en) | 2012-12-07 | 2014-01-28 | Geofeedr, Inc. | System and method for generating and managing geofeed-based alerts |
US8655983B1 (en) | 2012-12-07 | 2014-02-18 | Geofeedr, Inc. | System and method for location monitoring based on organized geofeeds |
US8971930B2 (en) | 2012-12-11 | 2015-03-03 | Blackberry Limited | Geofencing system and method |
US20140195918A1 (en) | 2013-01-07 | 2014-07-10 | Steven Friedlander | Eye tracking user interface |
US20140222950A1 (en) | 2013-02-04 | 2014-08-07 | Navteq B.V. | Predictive Mobile Map Download |
US10191945B2 (en) | 2013-02-20 | 2019-01-29 | The Florida International University Board Of Trustees | Geolocating social media |
US8850531B1 (en) | 2013-03-07 | 2014-09-30 | Geofeedia, Inc. | System and method for targeted messaging, workflow management, and digital rights management for geofeeds |
US8612533B1 (en) | 2013-03-07 | 2013-12-17 | Geofeedr, Inc. | System and method for creating and managing geofeeds |
US9307353B2 (en) | 2013-03-07 | 2016-04-05 | Geofeedia, Inc. | System and method for differentially processing a location input for content providers that use different location input formats |
US8862589B2 (en) | 2013-03-15 | 2014-10-14 | Geofeedia, Inc. | System and method for predicting a geographic origin of content and accuracy of geotags related to content obtained from social media and other content providers |
US9317600B2 (en) | 2013-03-15 | 2016-04-19 | Geofeedia, Inc. | View of a physical space augmented with social media content originating from a geo-location of the physical space |
US8849935B1 (en) | 2013-03-15 | 2014-09-30 | Geofeedia, Inc. | Systems and method for generating three-dimensional geofeeds, orientation-based geofeeds, and geofeeds based on ambient conditions based on content provided by social media content providers |
US10397363B2 (en) | 2013-03-27 | 2019-08-27 | Facebook, Inc. | Scoring user characteristics |
US20150172396A1 (en) | 2013-12-16 | 2015-06-18 | Co Everywhere, Inc. | Systems and methods for enriching geographically delineated content |
US20170032384A1 (en) | 2015-07-29 | 2017-02-02 | Geofeedia, Inc. | System and Method for Analyzing Social Media Users Based on User Content Posted from Monitored Locations |
US9485318B1 (en) | 2015-07-29 | 2016-11-01 | Geofeedia, Inc. | System and method for identifying influential social media and providing location-based alerts |
-
2013
- 2013-03-07 US US13/788,909 patent/US8850531B1/en active Active
-
2014
- 2014-09-29 US US14/500,881 patent/US9443090B2/en active Active
-
2016
- 2016-08-19 US US15/241,926 patent/US10044732B2/en active Active
-
2018
- 2018-08-06 US US16/056,336 patent/US10530783B2/en active Active
Patent Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20070121843A1 (en) * | 2005-09-02 | 2007-05-31 | Ron Atazky | Advertising and incentives over a social network |
US20120259791A1 (en) * | 2011-04-07 | 2012-10-11 | Sabina Zoidze | System and method for social networking |
US8341223B1 (en) * | 2011-06-07 | 2012-12-25 | Banjo, Inc. | Method for relevant content discovery |
US20120323687A1 (en) * | 2011-06-20 | 2012-12-20 | Shopping Made Mobile, Inc. | Mobile Messaging and Data Tracking Platform |
US8595317B1 (en) * | 2012-09-14 | 2013-11-26 | Geofeedr, Inc. | System and method for generating, accessing, and updating geofeeds |
Cited By (38)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US10523768B2 (en) | 2012-09-14 | 2019-12-31 | Tai Technologies, Inc. | System and method for generating, accessing, and updating geofeeds |
US9055074B2 (en) | 2012-09-14 | 2015-06-09 | Geofeedia, Inc. | System and method for generating, accessing, and updating geofeeds |
US9077675B2 (en) | 2012-12-07 | 2015-07-07 | Geofeedia, Inc. | System and method for generating and managing geofeed-based alerts |
US8990346B2 (en) | 2012-12-07 | 2015-03-24 | Geofeedia, Inc. | System and method for location monitoring based on organized geofeeds |
US9369533B2 (en) | 2012-12-07 | 2016-06-14 | Geofeedia, Inc. | System and method for location monitoring based on organized geofeeds |
US9307353B2 (en) | 2013-03-07 | 2016-04-05 | Geofeedia, Inc. | System and method for differentially processing a location input for content providers that use different location input formats |
US10530783B2 (en) | 2013-03-07 | 2020-01-07 | Tai Technologies, Inc. | System and method for targeted messaging, workflow management, and digital rights management for geofeeds |
US10044732B2 (en) | 2013-03-07 | 2018-08-07 | Tai Technologies, Inc. | System and method for targeted messaging, workflow management, and digital rights management for geofeeds |
US9443090B2 (en) | 2013-03-07 | 2016-09-13 | Geofeedia, Inc. | System and method for targeted messaging, workflow management, and digital rights management for geofeeds |
US9906576B2 (en) | 2013-03-07 | 2018-02-27 | Tai Technologies, Inc. | System and method for creating and managing geofeeds |
US9077782B2 (en) | 2013-03-07 | 2015-07-07 | Geofeedia, Inc. | System and method for creating and managing geofeeds |
US9479557B2 (en) | 2013-03-07 | 2016-10-25 | Geofeedia, Inc. | System and method for creating and managing geofeeds |
US10373212B2 (en) * | 2013-03-14 | 2019-08-06 | Facebook, Inc. | Methods for linking images in social feeds to branded content |
US9258373B2 (en) | 2013-03-15 | 2016-02-09 | Geofeedia, Inc. | System and method for generating three-dimensional geofeeds, orientation-based geofeeds, and geofeeds based on ambient conditions based on content provided by social media content providers |
US9805060B2 (en) | 2013-03-15 | 2017-10-31 | Tai Technologies, Inc. | System and method for predicting a geographic origin of content and accuracy of geotags related to content obtained from social media and other content providers |
US9317600B2 (en) | 2013-03-15 | 2016-04-19 | Geofeedia, Inc. | View of a physical space augmented with social media content originating from a geo-location of the physical space |
US9838485B2 (en) | 2013-03-15 | 2017-12-05 | Tai Technologies, Inc. | System and method for generating three-dimensional geofeeds, orientation-based geofeeds, and geofeeds based on ambient conditions based on content provided by social media content providers |
US9497275B2 (en) | 2013-03-15 | 2016-11-15 | Geofeedia, Inc. | System and method for generating three-dimensional geofeeds, orientation-based geofeeds, and geofeeds based on ambient conditions based on content provided by social media content providers |
US9436690B2 (en) | 2013-03-15 | 2016-09-06 | Geofeedia, Inc. | System and method for predicting a geographic origin of content and accuracy of geotags related to content obtained from social media and other content providers |
US9619489B2 (en) | 2013-03-15 | 2017-04-11 | Geofeedia, Inc. | View of a physical space augmented with social media content originating from a geo-location of the physical space |
US10726090B1 (en) | 2013-04-05 | 2020-07-28 | Hrl Laboratories, Llc | Per-user accuracy measure for social network based geocoding algorithms |
US20140359023A1 (en) * | 2013-05-30 | 2014-12-04 | Dropbox, Inc. | Content-item relationship messaging system |
US11502980B2 (en) | 2013-05-30 | 2022-11-15 | Dropbox, Inc. | Content-item relationship messaging system |
US11991129B2 (en) | 2013-05-30 | 2024-05-21 | Dropbox, Inc. | Content-item relationship messaging system |
US10243899B2 (en) * | 2013-05-30 | 2019-03-26 | Dropbox, Inc. | Content-item relationship messaging system |
US9262438B2 (en) * | 2013-08-06 | 2016-02-16 | International Business Machines Corporation | Geotagging unstructured text |
US20150046452A1 (en) * | 2013-08-06 | 2015-02-12 | International Business Machines Corporation | Geotagging unstructured text |
US9477522B2 (en) | 2014-07-01 | 2016-10-25 | Tuul, Inc. | System and method for implementing workflow management using messaging |
WO2016003728A1 (en) * | 2014-07-01 | 2016-01-07 | Tuul, Inc. | System and method for implementing workflow management using messaging |
US20170019450A1 (en) * | 2015-07-17 | 2017-01-19 | Tribune Broadcasting Company, Llc | Media production system with social media feature |
US9485318B1 (en) | 2015-07-29 | 2016-11-01 | Geofeedia, Inc. | System and method for identifying influential social media and providing location-based alerts |
US20210182890A1 (en) * | 2015-12-30 | 2021-06-17 | Paypal, Inc. | Data structures for categorizing and filtering content |
US11521224B2 (en) * | 2015-12-30 | 2022-12-06 | Paypal, Inc. | Data structures for categorizing and filtering content |
EP3467692A4 (en) * | 2016-05-27 | 2019-11-27 | Tencent Technology (Shenzhen) Company Limited | Message permission management method and device, and storage medium |
US11539687B2 (en) * | 2016-05-27 | 2022-12-27 | Tencent Technology (Shenzhen) Company Limited | Message right management method, device and storage medium |
CN107317812A (en) * | 2017-06-27 | 2017-11-03 | 福建中金在线信息科技有限公司 | A kind of method, device, electronic equipment and storage medium for searching pirate user |
US20200273225A1 (en) * | 2019-02-25 | 2020-08-27 | Life Impact Solutions, Inc. | Media Alteration Based On Variable Geolocation Metadata |
US11763503B2 (en) * | 2019-02-25 | 2023-09-19 | Life Impact Solutions | Media alteration based on variable geolocation metadata |
Also Published As
Publication number | Publication date |
---|---|
US20180343268A1 (en) | 2018-11-29 |
US9443090B2 (en) | 2016-09-13 |
US20160359868A1 (en) | 2016-12-08 |
US10530783B2 (en) | 2020-01-07 |
US8850531B1 (en) | 2014-09-30 |
US20150020208A1 (en) | 2015-01-15 |
US10044732B2 (en) | 2018-08-07 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US10530783B2 (en) | System and method for targeted messaging, workflow management, and digital rights management for geofeeds | |
US9906576B2 (en) | System and method for creating and managing geofeeds | |
JP6480993B2 (en) | Assessing claims in social networking systems | |
US20180351895A1 (en) | In the event of selection of message, invoking camera to enabling to capture media and relating, attaching, integrating, overlay message with/on/in captured media and send to message sender | |
US20180293669A1 (en) | System and method of collecting and providing service provider records | |
US8843528B1 (en) | Query-based user groups in social networks | |
US20180247380A1 (en) | Managing copyrights of content for sharing on a social networking system | |
US10325323B2 (en) | Providing a claims-based profile in a social networking system | |
JP2019003668A (en) | Privacy-reinforced and customizing function-integrated social platform | |
US10839468B2 (en) | Graphical platform for interacting with unstructured data | |
US20140215578A1 (en) | Adaptive Audiences For Claims In A Social Networking System | |
US20130282813A1 (en) | Collaborative management of contacts across multiple platforms | |
JP2017519312A (en) | A global exchange platform for film industry professionals | |
US10462640B1 (en) | Systems and methods for hierarchical communication channels | |
US20160350297A1 (en) | Location Based Social Media System | |
US20170220999A1 (en) | Techniques for document management workflows | |
US11562014B1 (en) | Generating visual media collections for a dynamic social networking account | |
US9924310B2 (en) | Location-driven social networking system and method | |
Gong et al. | DC-04-Social Media Platforms |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: GEOFEEDR, INC., FLORIDA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:HARRIS, PHILIP B.;MITCHELL, SCOTT K.;MULROY, MICHAEL J.;REEL/FRAME:029944/0848 Effective date: 20130306 |
|
AS | Assignment |
Owner name: GEOFEEDIA, INC., FLORIDA Free format text: MERGER;ASSIGNOR:GEOFEEDR, INC.;REEL/FRAME:031948/0251 Effective date: 20120628 |
|
STCF | Information on status: patent grant |
Free format text: PATENTED CASE |
|
FEPP | Fee payment procedure |
Free format text: PAYOR NUMBER ASSIGNED (ORIGINAL EVENT CODE: ASPN); ENTITY STATUS OF PATENT OWNER: SMALL ENTITY |
|
AS | Assignment |
Owner name: TAI TECHNOLOGIES, INC., FLORIDA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:GEOFEEDIA, INC.;REEL/FRAME:042250/0195 Effective date: 20170428 |
|
MAFP | Maintenance fee payment |
Free format text: PAYMENT OF MAINTENANCE FEE, 4TH YR, SMALL ENTITY (ORIGINAL EVENT CODE: M2551) Year of fee payment: 4 |
|
AS | Assignment |
Owner name: TRIPLEPOINT CAPITAL LLC, CALIFORNIA Free format text: SECURITY INTEREST;ASSIGNOR:SOCIAL SENTINEL, INC.;REEL/FRAME:052287/0700 Effective date: 20200324 |
|
AS | Assignment |
Owner name: SOCIAL SENTINEL, INC., VERMONT Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:TRIPLEPOINT CAPITAL LLC;REEL/FRAME:054267/0098 Effective date: 20201019 |
|
MAFP | Maintenance fee payment |
Free format text: PAYMENT OF MAINTENANCE FEE, 8TH YR, SMALL ENTITY (ORIGINAL EVENT CODE: M2552); ENTITY STATUS OF PATENT OWNER: SMALL ENTITY Year of fee payment: 8 |