Customizable content for distribution in social networks

Information

  • Patent Grant
  • 9224172
  • Patent Number
    9,224,172
  • Date Filed
    Tuesday, December 2, 2008
    15 years ago
  • Date Issued
    Tuesday, December 29, 2015
    8 years ago
Abstract
Particular embodiments of the present invention are related to customizing content based on a social context associated with the viewer of the content. The social context may include information regarding the viewer's friends or contacts in a social network, and information regarding the interaction of such friends or contacts with the customizable content.
Description
TECHNICAL FIELD

The present disclosure generally relates to customized advertising systems.


BACKGROUND

As the popularity of the Internet has increased, so has the prevalence of social networking websites and applications. Generally speaking, a social network refers to an application or service that facilitates the building online communities of people who share interests and activities, or who are interested in exploring the interests and activities of others. Many social network services are web-based and provide a variety of ways for users to interact, such as e-mail and instant messaging services. Some examples of social networking websites are delicious (http://delicious.com), facebook (http://www.facebook.com), Yahoo! Movies (http://movies.yahoo.com), Yahoo! Music (http://music.yahoo.com), Flickr (http://www.flickr.com), and others.


Advertisers often leverage social networks to market an increase awareness of their products and services. For example, advertisers often use “viral marketing” which generally refers to marketing techniques that use pre-existing social networks to produce increases in brand awareness or to achieve other marketing objectives (such as product sales) either through word-of-mouth or through self-replicating viral processes, analogous to the spread of pathological and computer viruses. Viral marketing promotions may take many forms, including video clips, interactive Flash games, advergames, ebooks, brandable software, images, or even text messages.


In addition, advertisers often deliver advertising using contextual advertising. Contextual advertising is marketing targeted to the specific individual visiting a website or a page within the website. A contextual advertising system may scan the text of a website for keywords, scan metadata related to the individual (e.g., geographical or other demographic data based on cookies or other metadata associated with the user) and return “personalized” advertisements to the webpage based on such keywords and/or metadata. For example, if the individual is viewing a website pertaining to sports and that website uses contextual advertising, the individual may see advertisements for sports-related companies, such as memorabilia dealers or ticket sellers. In addition, the advertisements may be for such companies physically located in the same geographical region as the individual. Contextual advertising may also be used by search engines to display advertisements on their search results pages based on the keywords in a user's search query.


SUMMARY

The present invention provides methods, apparatuses and systems directed to customizing content based on a social context associated with the viewer of the content. The social context may include information regarding the viewer's friends or contacts in a social network, and information regarding the interaction of such friends or contacts with the customizable content.





DESCRIPTION OF THE DRAWINGS


FIG. 1 is a schematic diagram that illustrates an example network environment in which particular implementations of the invention may operate.



FIG. 2 is a schematic diagram illustrating a client host environment to which implementations of the invention may have application.



FIG. 3 illustrates a flow chart of an example method that may be implemented to deliver social context-based content to a client node.



FIG. 4 illustrates a flow chart of an example method that may be implemented to create social context-based content.



FIG. 5 illustrates a flow chart of another example method that may be implemented to create and deliver social context-based content.



FIG. 6 is a schematic diagram illustrating an example computing system architecture that may be used to implement one or more of physical servers depicted in FIG. 1.



FIG. 7 is a schematic diagram illustrating an example network that may be used to provide context-based context.





DESCRIPTION OF EXAMPLE EMBODIMENT(S)
A. Overview

Particular embodiments of the present invention are related to targeting content (e.g., advertising and/or other content) to an individual based on a social context of the individual. The social context may include the individual's social network profile information (e.g., name, schools attended, favorite teams, favorite music, etc.), the individual's preferences, information regarding the individual's friends or contacts in one or more social networks, and such friends' or contacts' interaction with the particular content. For example, targeted content may be delivered to an individual based upon triggering events and/or other behavior of other users in the individual's social network. As another example, targeted content may be customized, augmented and/or annotated by one or more particular friends or contacts of an individual in a social network, and presented to the individual based on the customizations, augmentations, and/or annotations.


The present invention can be implemented in a variety of manners, as discussed in more detail below. Other implementations of the invention may be practiced without some or all of specific details set forth below. In some instances, well known structures and/or processes have not been described in detail so that the present invention is not unnecessarily obscured.


A. Example Network Environment

Particular implementations of the invention operate in a wide area network environment, such as the Internet, including multiple network addressable systems. Network cloud 60 generally represents one or more interconnected networks, over which the systems and hosts described herein can communicate. Network cloud 60 may include packet-based wide area networks (such as the Internet), private networks, wireless networks, satellite networks, cellular networks, paging networks, and the like.


As FIG. 1 illustrates, a particular implementation of the invention can operate in a network environment 10 comprising network application hosting site 20, such as an informational web site, social network site and the like. Although FIG. 1 illustrates only one network application hosting site, implementations of the invention may operate in network environments that include multiples of one or more of the individual systems and sites disclosed herein. Client nodes 82 are operably connected to the network environment via a network service provider or any other suitable means.


Network application hosting site 20 is a network addressable system that hosts a network application accessible to one or more users over a computer network. The network application may be an informational web site where users request and receive identified web pages and other content over the computer network. The network application may also be a search platform, an on-line forum or blogging application where users may submit or otherwise configure content for display to other users. The network application may also be a social network application allowing users to configure and maintain personal web pages. The network application may also be a content distribution application, such as Yahoo! Music Engine®, Apple® iTunes®, podcasting servers, that displays available content, and transmits content to users.


Network application hosting site 20, in one implementation, comprises one or more physical servers 22 and content data store 24. The one or more physical servers 22 are operably connected to computer network 60 via a router 26. The one or more physical servers 22 host functionality that provides a network application (e.g., a news content site, etc.) to a user. As discussed in connection with FIG. 2, in one implementation, the functionality hosted by the one or more physical servers 22 may include web or HTTP servers, ad serving systems, geo-targeting systems, and the like. Still further, some or all of the functionality described herein may be accessible using an HTTP interface or presented as a web service using SOAP or other suitable protocols.


Content data store 24 stores content as digital content data objects. A content data object or content object, in particular implementations, is an individual item of digital information typically stored or embodied in a data file or record. Content objects may take many forms, including: text (e.g., ASCII, SGML, HTML), images (e.g., jpeg, tif and gif), graphics (vector-based or bitmap), audio, video (e.g., mpeg), or other multimedia, and combinations thereof. Content object data may also include executable code objects (e.g., games executable within a browser window or frame), podcasts, etc. Structurally, content data store 24 connotes a large class of data storage and management systems. In particular implementations, content data store 24 may be implemented by any suitable physical system including components, such as database servers, mass storage media, media library systems, and the like.


Network application hosting site 20, in one implementation, provides web pages, such as front pages, that include an information package or module describing one or more attributes of a network addressable resource, such as a web page containing an article or product description, a downloadable or streaming media file, and the like. The web page may also include one or more ads, such as banner ads, text-based ads, sponsored videos, games, and the like. Generally, web pages and other resources include hypertext links or other controls that a user can activate to retrieve additional web pages or resources. A user “clicks” on the hyperlink with a computer input device to initiate a retrieval request to retrieve the information associated with the hyperlink or control.


As described in greater detail below, network application hosting site 20 may be configured to deliver, and one or more of client nodes 82 may be configured to receive, social context-based content. Social context-based content may refer to any content (e.g., audio, images, text, video, ringtones, coupons, interactive games, rich media content files, etc.) for which the appearance of the content to a user is based at least on the user's social context (e.g., information regarding the user's social network profile information, the user's preferences, the user's contacts in a social network, and/or information regarding the interaction of such contacts with content previously delivered to the contacts). Also as described in greater detail below, one or more of client nodes 82 may be configured to allow a user to enhance content delivered to the client node, and network application hosting site 20 may be configured to receive and/or store such enhancements to the content.



FIG. 2 illustrates the functional modules of a client host server environment 100 within network application hosting site 20 according to one particular implementation. As FIG. 2 illustrates, network application hosting site 20 may comprise one or more network clients 105 and one or more client hosts 110 operating in conjunction with one or more server hosts 120. The foregoing functional modules may be realized by hardware, executable modules stored on a computer readable medium, or a combination of both. The functional mcdules, for example, may be hosted on one or more physical servers 22 and/or one or more client nodes 82.


Network client 105 may be a web client hosted on client nodes 82, a client host 110 located on physical server 22, or a server host located on physical server 22. Client host 110 may be an executable web or HTTP server module that accepts HyperText Transport Protocol (HTTP) requests from network clients 105 acting as a web clients, such web browser client applications hosted on client nodes 82, and serving HTTP responses including contents, such as HyperText Markup Language (HTML) documents and linked objects (images, advertisements, etc.). Client host 110 may also be an executable module that accepts Simple Object Access Protocol (SOAP) requests from one or more client hosts 110 or one or more server hosts 120. In one implementation, client host 110 has the capability of delegating all or part of single or multiple requests from network client 105 to one or more server hosts 120. Client host 110, as discussed above, may operate to deliver a network application, such as an informational web page or an internet search service.


In a particular implementation, client host 110 may act as a server host 120 to another client host 110 and may function to further delegate requests to one or more server hosts 120 and/or one or more client hosts 110. Server hosts 120 host one or more server applications, such as an ad selection server, sponsored search server, content customization server, and the like.


B. Client Nodes & Example Protocol Environment

A client node is a computer or computing device including functionality for communicating over a computer network. A client node may be a desktop computer 82a, 82b, laptop computer 82c, 82d, as well as mobile devices 82e, 82f, such as cellular telephones and personal digital assistants. A client node may execute one or more client applications, such as a web browser, to access and view content over a computer network. In particular implementations, the client applications allow users to enter addresses of specific network resources to be retrieved. These addresses can be Uniform Resource Locators, or URLs. In addition, once a page or other resource has been retrieved, the client applications may provide access to other pages or records when the user “clicks” on hyperlinks to other resources. In some implementations, such hyperlinks are located within web pages and provide an automated way for the user to enter the URL of another page and to retrieve that page. The pages or resources can be data records including as content plain textual information, or more complex digitally encoded multimedia content, such as software programs or other code objects, graphics, images, audio signals, videos, and so forth.


The networked systems described herein can communicate over the network 60 using any suitable communications protocols. For example, client nodes 82a-d, as well as various servers of the systems described herein, may include Transport Control Protocol/Internet Protocol (TCP/IP) networking stacks to provide for datagram and transport functions. Of course, any other suitable network and transport layer protocols can be utilized.


In addition, hosts or end-systems described herein may use a variety of higher layer communications protocols, including client-server (or request-response) protocols, such as the HyperText Transfer Protocol (HTTP) and other communications protocols, such as HTTP-S, FTP, SNMP, TELNET, and a number of other protocols, may be used. In addition, a server in one interaction context may be a client in another interaction context. Still further, in particular implementations, the information transmitted between hosts may be formatted as HyperText Markup Language (HTML) documents. Other structured document languages or formats can be used, such as XML, and the like.


In some client-server protocols, such as the use of HTML over HTTP, a server generally transmits a response to a request from a client. The response may comprise one or more data objects. For example, the response may comprise a first data object, followed by subsequently transmitted data objects. In one implementation, for example, a client request may cause a server to respond with a first data object, such as an HTML page, which itself refers to other data objects. A client application, such as a browser, will request these additional data objects as it parses or otherwise processes the first data object.


Mobile client nodes 82e-f may use other communications protocols and data formats. For example, mobile client nodes 82e-f, in some implementations, may include mobile web browser. The use of other wireless or mobile device protocol suites are also possible, such as NTT DoCoMo's i-mode wireless network service protocol suites. In addition, the network environment may also include protocol translation gateways, proxies or other systems to allow mobile client nodes 84, for example, to access other network protocol environments. For example, a user may use a mobile client node 82e-f to capture an image and upload the image over the carrier network to a content site connected to the Internet.


C. Example Operation

In a social networking service (e.g., facebook, MySpace, LinkedIn, etc.), each user of the social network may create a network profile (e.g., username, password, and/or biographical information) via a client node 82. For example, a user may access the social network via an application program available at the client node 82 (e.g., a web browser) and/or via a website for the social network. Using client nodes 82, each user may also specify other users in the social network to which the user has a social tie. In this disclosure, the terms “social tie” and “tie” may be used to indicate a social relationship between two users in a social network (e.g., a “friend,” “buddy,” “connection,” “link,” etc.), while the term “contact” may be used to indicate any user for which a particular user has a social tie. In addition to a social tie existing based on a declared relationship between users, a social tie may also be derived by the social networking service on the basis of shared interests, biographical information, and/or other common aspects of the users. The social networking application, user biographical information, social ties, and contact information may be hosted at network application hosting site 20. Users using client nodes 82 may access the social networking application via network cloud 60. Once a user's contacts have been identified, a user may be able to access the social networking application website and/or application to view some or all of the profile information of his or her contacts, including, for example, actions performed by the contacts.


In addition, content may be delivered to users using network environment 10 or a similar network environment. For example, content in any suitable form (e.g., audio, images, text, video, ringtones, coupons, interactive games, rich media content files, etc.) may be hosted at network application hosting site 20 or a similar hosting site. Network application hosting site may communicate such content via network cloud 60 to a client node 82 and displayed to a user thereof.



FIG. 3 illustrates a flow chart of an example method 300 that may be implemented to deliver social context-based content to client node 82. Method 300 may be implemented by a social networking application and/or other application (e.g., a social networking application and/or other application executing on network application hosting site 20).


At step 302, network application hosting site 20 may deliver content (e.g., an advertisement for goods or services) to one or more client nodes 82. In some embodiments, the content may include rich media content (e.g., an Adobe® Flash file) allowing a user at a client node 82 receiving the content to interact with the content.


At step 304, one or more users of client nodes 82 may interact with the delivered content. For example, when delivered to a client node 82, the content may present an option to a user, such as a preferred method of viewing the content (e.g., as a movie, as audio, as an interactive game, etc.), and the user may interact by selecting the preferred viewing method. At step 306, the interactions of the users of the one or more client nodes 82 may be communicated to network application hosting site 20 and/or stored on a data store (e.g., content data store 24).


At step 308, network application hosting site 20 may determine a social context for a particular user. The particular user may or may not be one of the one or more users that received the content at step 302. The social context may comprise a collection of data that may include information regarding the user's social network profile information (e.g., name, schools attended, favorite teams, favorite music, etc.), the user's preferences, the user's contacts in a social network, and/or information regarding the interaction of such contacts with content previously delivered to the contacts of client nodes 82.


At step 310, network application hosting site 20 may deliver content (e.g., content identical or related to the content delivered at step 302) to a user wherein the delivered content is based at least on the determined social context (e.g., based on the particular user's social network profile information, the particular user's preferences, the particular user's social contacts and/or interaction of such contacts with the content).


In addition to delivery of content based on a user's social context, content may also be delivered based on other contextual parameters associated with a user. For example, content may be delivered based on a temporal or time-based context (e.g., certain portions of content may be displayed to a certain user before a certain time, and other portions may be displayed after the certain time). As another example, content may be delivered based on spatial or geographic context (e.g., displayed portions of content may be dependent upon the user's geographical location, as determined by global positioning system (GPS), location in cellular network, Internet Protocol (IP) address, Bluetooth, radio frequency identification (RFID), and/or the user's explicitly provided information). As a further example, portions of content may be delivered based on a behavioral context (e.g., a user's most recently or often-visited websites, a user's currently visited website, etc.).


As a specific example of method 300, the content delivered to one or more users of clients nodes 82 may include a rich media (e.g., Adobe® Flash file) advertisement along with an option to play an interactive game associated with the advertisement or to watch a video associated with the advertisement. Some users may interact by opting to play the interactive game. Accordingly, when the same advertisement is later delivered to another user whose contacts have chosen to play the interactive game, the advertisement may no longer query for a delivery method (e.g., the option of interactive game or video), but may instead automatically display the interactive game. Thus, the content displays the interactive game based on the later user's contacts and the contacts' earlier interaction with the content.



FIG. 4 illustrates a flow chart of an example method 400 that may be implemented to create social context-based content. Method 400 may be implemented by a social networking application and/or other application (e.g., a social networking application and/or other application executing on network application hosting site 20).


At step 402, network application hosting site 20 may deliver content (e.g., an advertisement for goods or services) to a client node 82. In some embodiments, the content may include rich media content (e.g., a Flash file) allowing a user at a client node 82 receiving the content to interact with the content.


At step 404, a user of the client node 82 to which the content was delivered may enhance the delivered content. “Enhancing” the delivered content may refer to any modification, change, addition, deletion, augmentation, annotation, interaction or any other suitable alteration of the content. For example, the user may add an annotation to the content (e.g., “I like this product,” “I think those who like the Beatles may also like this product,” “I am voting for this candidate because of the reasons in this ad.”). As another example, the user may tag the content to indicate which of the user's contacts the user feels may be interested in the content or the subject matter of the content. As a further example, the user may alter the content such that particular video and/or audio portions of the content are replaced with user-added content. As an additional example, a user's interaction with content (e.g., answering a question asked by the content) may also be considered an enhancement, as such interaction may modify metadata associated with the content.


At step 406, information regarding enhancements to the content (e.g., actual enhancements made and/or the identity of the user making such enhancements) may be communicated to network application hosting site 20 and/or stored on a data store (e.g, content data store 24).



FIG. 5 illustrates a flow chart of another example method 500 that may be implemented to deliver social context-based content to a user. Method 500 may be implemented by a social networking application and/or other application (e.g., a social networking application and/or other application executing on network application hosting site 20).


At step 502, network hosting site 20 may detect the presence of a user. The user's presence may be detected in any suitable manner. For example, the presence of the user may be detected by determining the user is logged into a client node 82 and/or a networked application executed thereon. As another example, the presence of the user may be detected by determining that a second client node 82 associated with a user is proximate to another client node 82 (e.g., an advertising kiosk, etc.) to which content may be displayed. The user's proximity may be determined in any suitable manner, including, e.g., GPS, the user's location in cellular network, the user's IP address, and/or the presence of a client node 82 associated with the user within the communication range of Bluetooth, RFID, and/or another short-range communications standard of the second client node 82, for example.


At step 504, network hosting site 20 may determine a social context associated with the user. The determined social context may include information regarding the user's social network profile information (e.g., name, schools attended, favorite teams, favorite music, etc.), a user's preferences, the identity of the user's social contacts, identity of content that may have been enhanced by the user's social contacts (e.g., in a method or manner similar to that of method 400, above), and/or the nature of enhancements by the user's social contacts (e.g., whether enhancements to content made in a method or manner similar to that of 400 include a tag or other reference regarding the user).


At step 506, network hosting site 20 may, based at least on the determined social context, display at least a portion of content (e.g., original content, enhanced content, metadata associated with content) to a user via a client node 82 associated with the user and/or a second client node 82 in proximity to the user's associated client node 82. In addition to delivery of a portion of content based on a user's social context, portions of content may also be delivered based on other contextual parameters associated with a user. For example, content may be delivered based on a temporal or time-based context (e.g., certain portions of content may be displayed to a certain user before a certain time, and other portions may be displayed after the certain time). As another example, content may be delivered based on spatial or geographic context (e.g., displayed portions of content may be dependent upon the user's geographical location, as determined by global positioning system (GPS), location in cellular network, Internet Protocol (IP) address, Bluetooth, radio frequency identification (RFID), and/or the user's explicitly provided information). As a further example, portions of content may be delivered based on a behavioral context (e.g., a user's most recently or often-visited websites, a user's currently visited website, etc.).


In order to illustrate the application of methods 400 and 500, numerous non-limiting examples are set forth below. Such examples are for clarity and exposition only, and shall not limit the applicability of the systems and methods disclosed herein to other examples and/or implementations.


Scenario 1: User A enhances content (e.g., adding a video to a rich media advertisement) and indicates the enhancement is intended to be viewed by User B. The enhanced content is stored on a network hosting site 20. User B comes within proximity to a particular client node 82 upon which the enhanced content may be displayed (e.g., an advertising kiosk including a monitor configured to display the content). After detecting User B's presence (e.g., by detecting that a client node 82 associated with User B is within the communication range of client node 82 associated with the kiosk), the enhanced content may be displayed at the particular client node 82 (e.g., the rich media advertisement displayed to User B may include User A's video).


Scenario 2: User A has User B, User C, and User D as contacts in a social network. Each of Users B, C, and D may download an item of content (e.g., a rich media advertisement) and each make their own enhancements to it (e.g., remix the advertisement, answer a question associated with the advertisement). User A may then be prompted at a client node 82 with an alert and/or other message indicating that other users in User A's social network have enhanced the content and may display at a least a portion of the content and/or the enhancements thereto made by Users B, C, and D. Alternatively, User A may receive via a client node 82 an alert and/or other message that other users closely matching User A's social context, temporal context, spatial context, or behavioral context have enhanced and/or otherwise interacted with the content (e.g., the interactions of earlier users may modify metadata associated with the content, and such metadata regarding the interactions or other elements related to such metadata may be displayed to the user).


Scenario 3: User A approaches a client node 82 and the client node displays content based on User A's social context (e.g., the user's social network profile information, a user's preferences, preferences and profile information regarding the user's contacts, etc.). For example, the content displayed to User A may be customized based on social network profile settings of User A (e.g., a sports apparel advertisement may be customized to include apparel for User A's favorite team) or customized based on social network profile settings of another user in User A's social network. In certain embodiments, certain content (e.g., ringtones, rich media, etc.) may be automatically delivered to User A based on preferences, enhancements, or interactions of other users in User A's social network.


D. Example Computing System Architectures

While the foregoing systems and methods can be implemented by a wide variety of physical systems and in a wide variety of network environments, the client and server host systems described below provide example computing architectures for didactic, rather than limiting, purposes.



FIG. 6 illustrates an example computing system architecture, which may be used to implement a physical server. In one embodiment, hardware system 200 comprises a processor 202, a cache memory 204, and one or more software applications and drivers directed to the functions described herein. Additionally, hardware system 200 includes a high performance input/output (I/O) bus 206 and a standard I/O bus 208. A host bridge 210 couples processor 202 to high performance I/O bus 206, whereas I/O bus bridge 212 couples the two buses 206 and 208 to each other. A system memory 214 and a network/communication interface 216 couple to bus 206. Hardware system 200 may further include video memory (not shown) and a display device coupled to the video memory. Mass storage 218, and I/O ports 220 couple to bus 208. Hardware system 200 may optionally include a keyboard and pointing device, and a display device (not shown) coupled to bus 208. Collectively, these elements are intended to represent a broad category of computer hardware systems, including but not limited to general purpose computer systems based on the x86-compatible processors manufactured by Intel Corporation of Santa Clara, Calif., and the x86-compatible processors manufactured by Advanced Micro Devices (AMD), Inc., of Sunnyvale, Calif., as well as any other suitable processor.


The elements of hardware system 200 are described in greater detail below. In particular, network interface 216 provides communication between hardware system 200 and any of a wide range of networks, such as an Ethernet (e.g., IEEE 802.3) network, etc. Mass storage 218 provides permanent storage for the data and programming instructions to perform the above described functions implemented in the location server 22, whereas system memory 214 (e.g., DRAM) provides temporary storage for the data and programming instructions when executed by processor 202. I/O ports 220 are one or more serial and/or parallel communication ports that provide communication between additional peripheral devices, which may be coupled to hardware system 200.


Hardware system 200 may include a variety of system architectures; and various components of hardware system 200 may be rearranged. For example, cache 204 may be on-chip with processor 202. Alternatively, cache 204 and processor 202 may be packed together as a “processor module,” with processor 202 being referred to as the “processor core.” Furthermore, certain embodiments of the present invention may not require nor include all of the above components. For example, the peripheral devices shown coupled to standard I/O bus 208 may couple to high performance I/O bus 206. In addition, in some embodiments only a single bus may exist, with the components of hardware system 200 being coupled to the single bus. Furthermore, hardware system 200 may include additional components, such as additional processors, storage devices, or memories.


As discussed below, in one implementation, the operations of one or more of the physical servers described herein are implemented as a series of software routines run by hardware system 200. These software routines comprise a plurality or series of instructions to be executed by a processor in a hardware system, such as processor 202. Initially, the series of instructions may be stored on a storage device, such as mass storage 218. However, the series of instructions can be stored on any suitable storage medium, such as a diskette, CD-ROM, ROM, EEPROM, etc. Furthermore, the series of instructions need not be stored locally, and could be received from a remote storage device, such as a server on a network, via network/communication interface 216. The instructions are copied from the storage device, such as mass storage 218, into memory 214 and then accessed and executed by processor 202.


An operating system manages and controls the operation of hardware system 200, including the input and output of data to and from software applications (not shown). The operating system provides an interface between the software applications being executed on the system and the hardware components of the system. According to one embodiment of the present invention, the operating system may include a Windows®-based operating system, available from Microsoft Corporation of Redmond, Wash. However, the present invention may be used with other suitable operating systems, such as an Apple Macintosh-based Operating System, available from Apple Computer Inc. of Cupertino, Calif., a UNIX-based operating system, a LINUX-based operating system, and the like. Of course, other implementations are possible. For example, the server functionalities described herein may be implemented by a plurality of server blades communicating over a backplane.


Furthermore, the above-described elements and operations can be comprised of instructions that are stored on storage media. The instructions can be retrieved and executed by a processing system. Some examples of instructions are software, program code, and firmware. Some examples of storage media are memory devices, tape, disks, integrated circuits, servers, mass storage devices, disk arrays, and storage area networks (SANs). The instructions are operational when executed by the processing system to direct the processing system to operate in accord with the invention. The term “processing system” refers to a single processing device or a group of inter-operational processing devices. Some examples of processing devices are integrated circuits and logic circuitry. Those skilled in the art are familiar with instructions, computers, and storage media.



FIG. 7 is a schematic diagram illustrating an example system 600 that may be used to provide context-based content in accordance with the present disclosure. In certain embodiments of system 600, system 600 may be used to provide context-based content based on temporal, spatial, social, topical, and/or behavioral data for a plurality of users, devices and locations within system 600. As depicted in FIG. 7, a user 610 may access context-based content from network 602 via a client 614 associated with the user. In certain embodiments, network 602 may be a “W4 communications network” of W4 COMN, which may provide information related to the “Who, What, When and Where” of interactions within system 600.



FIG. 7 illustrates how the entities shown may be defined to a network, for example a W4 COMN. A “W4 Communications Network” or W4 COMN, provides information related to the “Who, What, When and Where” of interactions within the network. Network 602 may interface a collection of users, devices and processes and foster both synchronous and asynchronous communications between users and their associated clients and providing an instrumented network of sensors providing data recognition and collection in real-world environments about any subject, location, or user of network, or any combination thereof. For example, content may be delivered to user 610 based on a geographical area 620 in which user 610 is located or which is otherwise associated with user 610. Such content may also be based on entities present with geographical area 620, such as, for example, tourist attractions and other points of interest 624, auditoriums and other public venues 628, businesses of various types 632, parks and recreation areas 636, and persons 640. In addition, content delivered to a user 610 may be based on other entities known to network 602, including without limitation, persons within the user's social networks 650, other persons known to network 602, and third party data sources 670 which can include free and premium information services which may provide data about other entities and topics, including reviews, ratings, rankings, or other feedback by users, and/or content associated with locations, events, objects, and/or people. Using the methods and systems disclosed herein, network 602 may collect spatial, temporal, social, and/or topical data (including behavioral and interaction data) about such entities that may be used to enhance or otherwise affect content delivered to user 610.


The present invention has been explained with reference to specific embodiments. For example, while embodiments of the present invention have been described as operating in connection with HTML and HTTP, the present invention can be used in connection with any suitable protocol environment. Furthermore, implementations of the invention can be used in systems directed to serving geo-targeted content other than ads to users. Other embodiments will be evident to those of ordinary skill in the art. It is therefore not intended that the present invention be limited, except as indicated by the appended claims.

Claims
  • 1. A method comprising: detecting, by a computing device, the presence of a first user of an online social network;delivering, by a computing device, content to the first user, the content allowing enhancement by the first user;receiving, by the computing device, one or more enhancements to the content by the first user;detecting, by the computing device, the presence of a second user on the social network, the second user different than the first user, the detecting the presence of the second user comprising detecting that a first client node to which the content may be displayed is geographically proximate to a second client node associated with the second user;determining, by the computing device, a social context of the second user, the social context comprising data associated with the second user with respect to the social network, the data associated with the second user with respect to the social network comprising data related to an interaction with the particular content by friends or contacts of the second user;modifying, by the computing device, the content, the modifying based on the determined social context of the second user and the one or more enhancements to the content by the first user;notifying, by the computing device, the second user that the content has been modified by the first user, the notifying comprising displaying at least a portion of the modified content; anddelivering, by the computing device, the modified content to the second user, the delivering comprising displaying the modified content to the first client node in response to the determination that the first client node is geographically proximate to the second client node.
  • 2. The method of claim 1, wherein the content includes an interactive rich media file.
  • 3. The method of claim 1, wherein the content includes an interactive advertisement.
  • 4. The method of claim 1, wherein the social context includes at least one of: information regarding contacts of the second user with respect to the social networks; andinformation regarding enhancements of the content by contacts of the second user with respect to the social network.
  • 5. The method of claim 1, wherein the determined social context indicates that the first user and the second user are contacts with respect to the social network, and the modified content delivered to the second user includes the one or more enhancements of the first user.
  • 6. The method of claim 1, wherein detecting that the first client node is proximate to the second client node is based on at least one of: the second client node's geographic location as determined by a global positioning system;the second client node's geographic location in a cellular network;the second client node's Internet protocol address; andthe second client node's presence within a communication range of a short-range communication standard associated with the first client node.
  • 7. The method of claim 1, wherein the delivered modified content is based on at least one of a temporal context, a geographical context, and a behavioral context of at least one of the first user and the second user.
  • 8. An apparatus, comprising: one or more processors;one or more network interfaces;a memory for tangibly storing thereon program logic for execution by the processor, the program logic comprising: detecting logic executed by the processor for detecting the presence of a first user of an online social network;delivering logic executed by the processor for delivering content to the first user via the one or more network interfaces, the content allowing enhancement by the first user;receiving logic executed by the processor for receiving via the one or more network interfaces one or more enhancements to the content by the first user;detecting logic executed by the processor for detecting via the one or more network interfaces the presence of a second user on the social network, the second user different than the first user, the detecting the presence of the second user comprising detecting that a first client node to which the content may be displayed is geographically proximate to a second client node associated with the second user;determining logic executed by the processor for determining a social context of the second user, the social context comprising data associated with the second user with respect to the social network, the data associated with the second user with respect to the social network comprising data related to an interaction with the particular content by friends or contacts of the second user;modifying logic executed by the processor for modifying the content, the modifying based on the determined social context of the second user and the one or more enhancements to the content by the first user;notifying logic executed by the processor for notifying the second user that the content has been modified by the first user, the notifying comprising displaying at least a portion of the modified content; anddelivering logic executed by the processor for delivering the modified content to the second user via the one or more network interfaces, the delivering comprising displaying the modified content to the first client node in response to the determination that the first client node is geographically proximate to the second client node.
  • 9. The apparatus of claim 8, wherein the content includes an interactive rich media file.
  • 10. The apparatus of claim 8, wherein the content includes an interactive advertisement.
  • 11. The apparatus of claim 8, wherein the social context includes at least one of: information regarding contacts of the second user with respect to the social networks; andinformation regarding enhancements of the content by contacts of the second user with respect to the social network.
  • 12. The apparatus of claim 8, wherein the determined social context indicates that the first user and the second user are contacts with respect to the social network, and the modified content delivered to the second user includes the one or more enhancements of the first user.
  • 13. The apparatus of claim 8, wherein detecting that the first node is proximate to the second client node is based on at least one of: the second client node's geographic location as determined by a global positioning system;the second client node's geographic location in a cellular network;the second client node's Internet protocol address; andthe second client node's presence within a communication range of a short-range communication standard associated with the first client node.
  • 14. The apparatus of claim 8, wherein the delivered modified content is based on at least one of a temporal context, a geographical context, and a behavioral context of at least one of the first user and the second user.
  • 15. A non-transitory computer readable storage medium comprising computer-executable instructions carried on the computer readable storage medium, the instructions readable by a processor, the instructions, when read and executed, for causing the processor to: detect via the one or more network interfaces the presence of a first user of an online social network;deliver content to the first user via the one or more network interfaces, the content allowing enhancement by the first user;receive via the one or more network interfaces one or more enhancements to the content by the first user;detect via the one or more network interfaces the presence of a second user on the social network, the second user different than the first user, the detecting the presence of the second user comprising detecting that a first client node to which the content may be displayed is geographically proximate to a second client node associated with the second user;determine a social context of the second user, the social context comprising data associated with the second user with respect to the social network, the data associated with the second user with respect to the social network comprising data related to an interaction with the particular content by friends or contacts of the second user;modify the content, the modifying based on the determined social context of the second user and the one or more enhancements to the content by the first user;notify the second user that the content has been modified by the first user, the notifying comprising displaying at least a portion of the modified content; anddeliver the modified content to the second user via the one or more network interfaces, the delivering comprising displaying the modified content to the first client node in response to the determination that the first client node is geographically proximate to the second client node.
  • 16. The non-transitory computer readable storage medium of claim 15 wherein the social context includes at least one of: information regarding contacts of the second user with respect to the social networks; andinformation regarding enhancements of the content by contacts of the second user with respect to the social network.
  • 17. The non-transitory computer readable storage medium of claim 15, wherein the determined social context indicates that the first user and the second user are contacts with respect to the social network, and the modified content delivered to the second user includes the one or more enhancements of the first user.
US Referenced Citations (410)
Number Name Date Kind
5446891 Kaplan et al. Aug 1995 A
5493692 Theimer et al. Feb 1996 A
5583763 Atcheson et al. Dec 1996 A
5651068 Klemba et al. Jul 1997 A
5761662 Dasan Jun 1998 A
5764906 Edelstein et al. Jun 1998 A
5781879 Arnold et al. Jul 1998 A
5784365 Ikeda Jul 1998 A
5794210 Goldhaber et al. Aug 1998 A
5802510 Jones Sep 1998 A
5835087 Herz Nov 1998 A
5903848 Takahashi May 1999 A
5920854 Kirsch et al. Jul 1999 A
6014638 Burge et al. Jan 2000 A
6021403 Horvitz et al. Feb 2000 A
6047234 Cherveny et al. Apr 2000 A
6098065 Skillen et al. Aug 2000 A
6112181 Shear et al. Aug 2000 A
6157924 Austin Dec 2000 A
6169992 Beall et al. Jan 2001 B1
6212552 Biliris et al. Apr 2001 B1
6266667 Olsson Jul 2001 B1
6314365 Smith Nov 2001 B1
6314399 Deligne et al. Nov 2001 B1
6324519 Eldering Nov 2001 B1
6327590 Chidlovskii et al. Dec 2001 B1
6446065 Nishioka et al. Sep 2002 B1
6490698 Horvitz et al. Dec 2002 B1
6502033 Phuyal Dec 2002 B1
6523172 Martinez-Guerra et al. Feb 2003 B1
6571279 Herz et al. May 2003 B1
6601012 Horvitz et al. Jul 2003 B1
6662195 Langseth et al. Dec 2003 B1
6665640 Bennett et al. Dec 2003 B1
6694316 Langseth et al. Feb 2004 B1
6701311 Biebesheimer et al. Mar 2004 B2
6701315 Austin Mar 2004 B1
6708203 Maker et al. Mar 2004 B1
6731940 Nagendran May 2004 B1
6741980 Langseth et al. May 2004 B1
6757661 Blaser et al. Jun 2004 B1
6773344 Gabai et al. Aug 2004 B1
6781920 Bates et al. Aug 2004 B2
6785670 Chiang et al. Aug 2004 B1
6789073 Lunenfeld Sep 2004 B1
6813501 Kinnunen et al. Nov 2004 B2
6816850 Culliss Nov 2004 B2
6829333 Frazier Dec 2004 B1
6834195 Brandenberg et al. Dec 2004 B2
6842761 Diamond et al. Jan 2005 B2
6845370 Burkey et al. Jan 2005 B2
6850252 Hoffberg Feb 2005 B1
6853913 Cherveny et al. Feb 2005 B2
6853982 Smith et al. Feb 2005 B2
6882977 Miller Apr 2005 B1
6904160 Burgess Jun 2005 B2
6931254 Egner et al. Aug 2005 B1
6961660 Underbrink et al. Nov 2005 B2
6961731 Holbrook Nov 2005 B2
6985839 Motamedi et al. Jan 2006 B1
7010492 Bassett et al. Mar 2006 B1
7027801 Hall et al. Apr 2006 B1
7058508 Combs et al. Jun 2006 B2
7058626 Pan et al. Jun 2006 B1
7062510 Eldering Jun 2006 B1
7065345 Carlton et al. Jun 2006 B2
7065483 Decary et al. Jun 2006 B2
7069308 Abrams Jun 2006 B2
7073129 Robarts et al. Jul 2006 B1
7110776 Sambin Sep 2006 B2
7143091 Charnock et al. Nov 2006 B2
7149696 Shimizu et al. Dec 2006 B2
7181438 Szabo Feb 2007 B1
7185286 Zondervan Feb 2007 B2
7194512 Creemer et al. Mar 2007 B1
7203597 Sato et al. Apr 2007 B2
7209915 Taboada et al. Apr 2007 B1
7219013 Young et al. May 2007 B1
7236969 Skillen et al. Jun 2007 B1
7254581 Johnson et al. Aug 2007 B2
7257570 Riise et al. Aug 2007 B2
7305445 Singh et al. Dec 2007 B2
7320025 Steinberg et al. Jan 2008 B1
7343364 Bram et al. Mar 2008 B2
7395507 Robarts et al. Jul 2008 B2
7404084 Fransdonk Jul 2008 B2
7437312 Bhatia et al. Oct 2008 B2
7451102 Nowak Nov 2008 B2
7461168 Wan Dec 2008 B1
7496548 Ershov Feb 2009 B1
7522995 Nortrup Apr 2009 B2
7529811 Thompson May 2009 B2
7562122 Oliver et al. Jul 2009 B2
7577665 Rameer et al. Aug 2009 B2
7584215 Saari et al. Sep 2009 B2
7624104 Berkhin et al. Nov 2009 B2
7624146 Brogne et al. Nov 2009 B1
7634465 Sareen et al. Dec 2009 B2
7657907 Fennan et al. Feb 2010 B2
7681147 Richardson-Bunbury et al. Mar 2010 B2
7725492 Sittig et al. May 2010 B2
7729901 Richardson-Bunbury et al. Jun 2010 B2
7769740 Martinez Aug 2010 B2
7769745 Naaman Aug 2010 B2
7783622 Vandermolen et al. Aug 2010 B1
7792040 Nair Sep 2010 B2
7802724 Nohr Sep 2010 B1
7822871 Stolorz et al. Oct 2010 B2
7831586 Reitter et al. Nov 2010 B2
7865308 Athsani Jan 2011 B2
7925708 Davis Apr 2011 B2
20010013009 Greening et al. Aug 2001 A1
20010035880 Musatov et al. Nov 2001 A1
20010047384 Croy Nov 2001 A1
20010052058 Ohran Dec 2001 A1
20020014742 Conte et al. Feb 2002 A1
20020019849 Tuvey et al. Feb 2002 A1
20020019857 Harjanto Feb 2002 A1
20020023091 Silberberg et al. Feb 2002 A1
20020023230 Bolnick et al. Feb 2002 A1
20020035605 McDowell et al. Mar 2002 A1
20020049968 Wilson et al. Apr 2002 A1
20020052786 Kim et al. May 2002 A1
20020052875 Smith et al. May 2002 A1
20020054089 Nicholas May 2002 A1
20020065844 Robinson et al. May 2002 A1
20020069218 Sull et al. Jun 2002 A1
20020099695 Abaijian et al. Jul 2002 A1
20020103870 Shouji Aug 2002 A1
20020111956 Yeo et al. Aug 2002 A1
20020112035 Carey Aug 2002 A1
20020133400 Terry et al. Sep 2002 A1
20020138331 Hosea et al. Sep 2002 A1
20020152267 Lennon Oct 2002 A1
20020169840 Sheldon et al. Nov 2002 A1
20020173971 Stirpe et al. Nov 2002 A1
20020178161 Brezin et al. Nov 2002 A1
20020198786 Tripp et al. Dec 2002 A1
20030008661 Joyce et al. Jan 2003 A1
20030009367 Morrison Jan 2003 A1
20030009495 Adjaoute Jan 2003 A1
20030027558 Eisinger Feb 2003 A1
20030032409 Hutcheson et al. Feb 2003 A1
20030033331 Sena et al. Feb 2003 A1
20030033394 Stine et al. Feb 2003 A1
20030065762 Stolorz et al. Apr 2003 A1
20030069877 Grefenstette et al. Apr 2003 A1
20030069880 Harrison et al. Apr 2003 A1
20030078978 Lardin et al. Apr 2003 A1
20030080992 Haines May 2003 A1
20030126250 Jhanji Jul 2003 A1
20030149574 Rudman Aug 2003 A1
20030154293 Zmolek Aug 2003 A1
20030165241 Fransdonk Sep 2003 A1
20030191816 Landress et al. Oct 2003 A1
20040010492 Zhao et al. Jan 2004 A1
20040015588 Cotte Jan 2004 A1
20040030798 Andersson et al. Feb 2004 A1
20040034752 Ohran Feb 2004 A1
20040041836 Zaner et al. Mar 2004 A1
20040043758 Sorvari et al. Mar 2004 A1
20040044736 Austin-Lane et al. Mar 2004 A1
20040070602 Kobuya et al. Apr 2004 A1
20040139025 Coleman Jul 2004 A1
20040139047 Rechsteiner Jul 2004 A1
20040148341 Cotte Jul 2004 A1
20040152477 Wu et al. Aug 2004 A1
20040183829 Kontny et al. Sep 2004 A1
20040201683 Murashita et al. Oct 2004 A1
20040203851 Vetro et al. Oct 2004 A1
20040203909 Koster Oct 2004 A1
20040209602 Joyce et al. Oct 2004 A1
20040243623 Ozer et al. Dec 2004 A1
20040260804 Grabarnik et al. Dec 2004 A1
20040267880 Patiejunas Dec 2004 A1
20050005242 Hoyle Jan 2005 A1
20050015451 Sheldon et al. Jan 2005 A1
20050015599 Wang et al. Jan 2005 A1
20050050027 Yeh Mar 2005 A1
20050050043 Pyhalammi et al. Mar 2005 A1
20050055321 Fratkina Mar 2005 A1
20050060381 Huynh et al. Mar 2005 A1
20050065950 Chaganti et al. Mar 2005 A1
20050065980 Hyatt et al. Mar 2005 A1
20050076060 Finn et al. Apr 2005 A1
20050086187 Grosser et al. Apr 2005 A1
20050105552 Osterling May 2005 A1
20050108213 Riise et al. May 2005 A1
20050120006 Nye Jun 2005 A1
20050131727 Sezan et al. Jun 2005 A1
20050149397 Morgenstern et al. Jul 2005 A1
20050151849 Fitzhugh et al. Jul 2005 A1
20050159220 Wilson et al. Jul 2005 A1
20050159970 Buyukkokten et al. Jul 2005 A1
20050160080 Dawson Jul 2005 A1
20050165699 Hahn-Carlson Jul 2005 A1
20050166240 Kim Jul 2005 A1
20050171955 Hull et al. Aug 2005 A1
20050177385 Hull et al. Aug 2005 A1
20050182824 Cotte Aug 2005 A1
20050183110 Anderson Aug 2005 A1
20050187786 Tsai Aug 2005 A1
20050192025 Kaplan Sep 2005 A1
20050198031 Pezaris et al. Sep 2005 A1
20050198305 Pezaris et al. Sep 2005 A1
20050203801 Morgenstern et al. Sep 2005 A1
20050216295 Abrahamsohn Sep 2005 A1
20050216300 Appelman et al. Sep 2005 A1
20050219375 Hasegawa et al. Oct 2005 A1
20050234781 Morgenstern Oct 2005 A1
20050256866 Lu et al. Nov 2005 A1
20050273510 Schuh Dec 2005 A1
20060020631 Cheong Wan et al. Jan 2006 A1
20060026013 Kraft Feb 2006 A1
20060026067 Nicholas et al. Feb 2006 A1
20060031108 Oran Feb 2006 A1
20060040719 Plimi Feb 2006 A1
20060047563 Wardell Mar 2006 A1
20060047615 Ravin Mar 2006 A1
20060053058 Hotchkiss et al. Mar 2006 A1
20060064346 Steenstra et al. Mar 2006 A1
20060069612 Hurt et al. Mar 2006 A1
20060069616 Bau Mar 2006 A1
20060069749 Herz et al. Mar 2006 A1
20060074853 Liu et al. Apr 2006 A1
20060085392 Wang et al. Apr 2006 A1
20060085419 Rosen Apr 2006 A1
20060089876 Boys Apr 2006 A1
20060116924 Angeles et al. Jun 2006 A1
20060123053 Scannell, Jr. Jun 2006 A1
20060129313 Becker Jun 2006 A1
20060129605 Doshi Jun 2006 A1
20060143081 Argaiz Jun 2006 A1
20060161894 Oustiougov et al. Jul 2006 A1
20060168591 Hunsinger et al. Jul 2006 A1
20060173838 Garg et al. Aug 2006 A1
20060173985 Moore Aug 2006 A1
20060178822 Lee Aug 2006 A1
20060184508 Fuselier et al. Aug 2006 A1
20060184579 Mills Aug 2006 A1
20060212330 Savilampi Sep 2006 A1
20060212401 Amerally et al. Sep 2006 A1
20060218577 Goodman et al. Sep 2006 A1
20060227945 Runge et al. Oct 2006 A1
20060235816 Yang et al. Oct 2006 A1
20060236257 Othmer et al. Oct 2006 A1
20060242139 Butterfield et al. Oct 2006 A1
20060242178 Butterfield et al. Oct 2006 A1
20060242259 Vallath et al. Oct 2006 A1
20060248573 Pannu et al. Nov 2006 A1
20060258368 Granito et al. Nov 2006 A1
20060271953 Jacoby Nov 2006 A1
20060271997 Jacoby et al. Nov 2006 A1
20060282455 Lee Dec 2006 A1
20070005654 Schachar et al. Jan 2007 A1
20070013560 Casey Jan 2007 A1
20070015519 Casey Jan 2007 A1
20070043766 Nicholas et al. Feb 2007 A1
20070067104 Mays Mar 2007 A1
20070067210 Rishell et al. Mar 2007 A1
20070067267 Ives Mar 2007 A1
20070072591 McGary et al. Mar 2007 A1
20070073583 Grouf et al. Mar 2007 A1
20070073641 Perry et al. Mar 2007 A1
20070086061 Robbins Apr 2007 A1
20070087756 Hoffberg Apr 2007 A1
20070088852 Levkovitz Apr 2007 A1
20070100956 Kumar May 2007 A1
20070112762 Brubaker May 2007 A1
20070121843 Atazky et al. May 2007 A1
20070130137 Oliver et al. Jun 2007 A1
20070136048 Richardson-Bunbury et al. Jun 2007 A1
20070136235 Hess Jun 2007 A1
20070136256 Kapur et al. Jun 2007 A1
20070136689 Richardson-Bunbury et al. Jun 2007 A1
20070143345 Jones et al. Jun 2007 A1
20070150168 Balcom et al. Jun 2007 A1
20070150359 Lim et al. Jun 2007 A1
20070150537 Graham Jun 2007 A1
20070155411 Morrison Jul 2007 A1
20070161382 Melinger et al. Jul 2007 A1
20070162432 Armstrong et al. Jul 2007 A1
20070162850 Adler Jul 2007 A1
20070168430 Brun et al. Jul 2007 A1
20070173266 Barnes Jul 2007 A1
20070179792 Kramer Aug 2007 A1
20070179863 Stoll Aug 2007 A1
20070185599 Robinson et al. Aug 2007 A1
20070192299 Zuckerberg et al. Aug 2007 A1
20070198506 Attaran Rezaei et al. Aug 2007 A1
20070198563 Apparao et al. Aug 2007 A1
20070203591 Bowerman Aug 2007 A1
20070219708 Brasche et al. Sep 2007 A1
20070233585 Ben Simon et al. Oct 2007 A1
20070233736 Xiong et al. Oct 2007 A1
20070239348 Cheung Oct 2007 A1
20070239517 Chung et al. Oct 2007 A1
20070255807 Hayashi et al. Nov 2007 A1
20070259653 Tang et al. Nov 2007 A1
20070260508 Barry et al. Nov 2007 A1
20070260520 Jha et al. Nov 2007 A1
20070260604 Haeuser et al. Nov 2007 A1
20070266097 Harik et al. Nov 2007 A1
20070271297 Jaffe et al. Nov 2007 A1
20070271340 Goodman et al. Nov 2007 A1
20070273758 Mendoza et al. Nov 2007 A1
20070276940 Abraham et al. Nov 2007 A1
20070282621 Altman et al. Dec 2007 A1
20070282675 Varghese Dec 2007 A1
20070288278 Alexander et al. Dec 2007 A1
20080005313 Flake et al. Jan 2008 A1
20080005651 Grefenstette et al. Jan 2008 A1
20080010206 Coleman Jan 2008 A1
20080021957 Medved et al. Jan 2008 A1
20080026804 Baray et al. Jan 2008 A1
20080028031 Bailey et al. Jan 2008 A1
20080040283 Morris Feb 2008 A1
20080045236 Nahon et al. Feb 2008 A1
20080046298 Ben-Yehuda et al. Feb 2008 A1
20080070588 Morin Mar 2008 A1
20080086356 Glassman et al. Apr 2008 A1
20080086431 Robinson et al. Apr 2008 A1
20080086458 Robinson et al. Apr 2008 A1
20080091796 Story et al. Apr 2008 A1
20080096664 Baray et al. Apr 2008 A1
20080102911 Campbell et al. May 2008 A1
20080104061 Rezaei May 2008 A1
20080104225 Zhang et al. May 2008 A1
20080104227 Birnie et al. May 2008 A1
20080109761 Stambaugh May 2008 A1
20080109843 Ullah May 2008 A1
20080114751 Cramer et al. May 2008 A1
20080120183 Park May 2008 A1
20080120308 Martinez et al. May 2008 A1
20080120690 Norlander et al. May 2008 A1
20080126476 Nicholas et al. May 2008 A1
20080132252 Altman et al. Jun 2008 A1
20080133750 Grabarnik et al. Jun 2008 A1
20080147655 Sinha et al. Jun 2008 A1
20080147743 Taylor et al. Jun 2008 A1
20080148175 Naaman et al. Jun 2008 A1
20080154720 Gounares Jun 2008 A1
20080163284 Martinez et al. Jul 2008 A1
20080172464 Thattai Jul 2008 A1
20080172632 Stambaugh Jul 2008 A1
20080177706 Yuen Jul 2008 A1
20080182563 Wugofski et al. Jul 2008 A1
20080189169 Turpin et al. Aug 2008 A1
20080195466 Wright Aug 2008 A1
20080222295 Robinson et al. Sep 2008 A1
20080255989 Altberg et al. Oct 2008 A1
20080270579 Herz et al. Oct 2008 A1
20080285886 Allen Nov 2008 A1
20080294663 Heinley et al. Nov 2008 A1
20080294678 Gorman et al. Nov 2008 A1
20080301250 Hardy et al. Dec 2008 A1
20080320001 Gaddam Dec 2008 A1
20090005987 Vengroff et al. Jan 2009 A1
20090006336 Forstall et al. Jan 2009 A1
20090012934 Yerigan Jan 2009 A1
20090012965 Franken Jan 2009 A1
20090043844 Zimmet et al. Feb 2009 A1
20090044132 Combel et al. Feb 2009 A1
20090063254 Paul et al. Mar 2009 A1
20090070186 Buiten et al. Mar 2009 A1
20090073191 Smith et al. Mar 2009 A1
20090076889 Jhanji Mar 2009 A1
20090100052 Stern et al. Apr 2009 A1
20090106356 Brase et al. Apr 2009 A1
20090125517 Krishnaswamy et al. May 2009 A1
20090132941 Pilskalns et al. May 2009 A1
20090138348 Higgins et al. May 2009 A1
20090144141 Dominowska et al. Jun 2009 A1
20090150501 Davis et al. Jun 2009 A1
20090150507 Davis et al. Jun 2009 A1
20090165051 Armaly Jun 2009 A1
20090171939 Athsani et al. Jul 2009 A1
20090177603 Honisch Jul 2009 A1
20090187637 Wu et al. Jul 2009 A1
20090204484 Johnson Aug 2009 A1
20090204672 Jetha et al. Aug 2009 A1
20090204676 Parkinson et al. Aug 2009 A1
20090216606 Coffman et al. Aug 2009 A1
20090216806 Feuerstein et al. Aug 2009 A1
20090222302 Higgins Sep 2009 A1
20090222303 Higgins Sep 2009 A1
20090234814 Boerries et al. Sep 2009 A1
20090234909 Strandeil et al. Sep 2009 A1
20090249482 Sarathy Oct 2009 A1
20090265431 Janie et al. Oct 2009 A1
20090281997 Jain Nov 2009 A1
20090299837 Steelberg et al. Dec 2009 A1
20090313546 Katpelly et al. Dec 2009 A1
20090320047 Khan et al. Dec 2009 A1
20090323519 Pun Dec 2009 A1
20090328087 Higgins et al. Dec 2009 A1
20100002635 Eklund Jan 2010 A1
20100014444 Ghanadan et al. Jan 2010 A1
20100049852 Whitnah et al. Feb 2010 A1
20100063993 Higgins et al. Mar 2010 A1
20100070368 Choi et al. Mar 2010 A1
20100118025 Smith et al. May 2010 A1
20100125563 Nair et al. May 2010 A1
20100125569 Nair et al. May 2010 A1
20100125604 Martinez et al. May 2010 A1
20100125605 Nair et al. May 2010 A1
20100185642 Higgins et al. Jul 2010 A1
20100250359 Gillenson et al. Sep 2010 A1
20100257028 Hillerbrand Oct 2010 A1
20130066963 Odio et al. Mar 2013 A1
Foreign Referenced Citations (17)
Number Date Country
101238730 Aug 2008 CN
1362302 Nov 2003 EP
2002312559 Oct 2002 JP
1020000036897 Jul 2000 KR
1020000054319 Sep 2000 KR
10-2000-0064105 Nov 2000 KR
1020030049173 Jun 2003 KR
10-0801662 Feb 2005 KR
1020060043333 May 2006 KR
102007034094 Mar 2007 KR
1020070073180 Jul 2007 KR
1020080048802 Jun 2008 KR
WO2006116196 Nov 2006 WO
WO 2007022137 Feb 2007 WO
WO 2007027453 Mar 2007 WO
WO 2007070358 Jun 2007 WO
WO2007113546 Oct 2007 WO
Non-Patent Literature Citations (181)
Entry
International Search report for PCT/US2009/055505, Apr. 9, 2010.
U.S. Appl. No. 11/593,668, filed Nov. 6, 2006 for Naaman, et al.
U.S. Appl. No. 11/593,869, filed Nov. 6, 2006 for Naaman, et al.
“Gutenkarte” Book Catalog, 2006 MetaCarta, Inc., www.gutenkarte.org 11pgs.
Baron, N.S. et al. (Aug. 30, 2005). “Tethered or Mobile? Use of Away Messages in Instant Messaging by American College Students,” Chapter 20.1 in Mobile Communication, Springer: London, England, 31:293-297.
Jones, C. et al. (2004). “Ad-Hoc Meeting System,” Final Presentation from Project Group #7, SIMS 202, Fall 2004 Class, UC Berkley School of Information Management & Systems, located at <http://www2.sims.berkeley.edu/academics/courses/is202/f04/phone—project/Group7/ >, last visited on Feb. 2, 2010, thirteen pages.
Manguy, L. et al. (2006). “iTour—Packing the World Into Your Mobile Device,” Final Presentation from Project Group #6, SIMS 202, Fall 2004 Class, UC Berkley School of Information Management & Systems, located at <http://www2.sims.berkeley.edu/academics/courses/is202/f04/phone—project/Group6/index.h > . . . , last visited on Feb. 2, 2010, ten pages.
Mitnick, S. et al. (2004). “Pillbox,” Final Presentation from Project Group #8, SIMS: 02: Fall 2004 Class, UC Berkley School of Information Management & Systems, located at <http://www2.sims.berkeley.edu/academics/courses/is202/f04/phone—project/Group8/about.p . . . ,> last visited on Feb. 2, 2010, seventeen pages.
Wooldridge, M. et al. (2005). “STALK. The Camera-phone Scavenger Hunt!” located at <http://www.stalk.com >, last visited on Dec. 28, 2009, two pages.
www.stalk.com (retrieved on Dec. 29, 2009) pp. 1-2.
Anonymous. (Date Unknown). “CommunityWalk—About,” located at <http://www.communitywalk.com/about >, last visited on Mar. 3, 2008, one page.
Anonymous. (Date Unknown). “CommunityWalk Mapping Made Easy,” located at <http://www.communitywalk.com/>, last visited on Mar. 3, 2008, one page.
Anonymous. (Date Unknown). “Google Earth User Guide” located at <http://earth.google.com/userguide/v4/>, last visited on Feb. 27, 2008, twelve pages.
Anonymous. (Date Unknown). “Google Earth—Wikipedia, the Free Encyclopedia,” located at <http://en.wikipedia.org/wiki/Google—earth >, last visited on Mar. 3, 2008, fourteen pages.
Anonymous. (Date Unknown). “Google Earth User Guide—Using Image Overlays and 3D Models,” located at <http://earth.google.com/userguide/v4/ug—imageoverlays.html >, nine pages.
Anonymous. (Date Unknown). “Google Maps,” located at <http://en.wikipedia.org/wiki/Google—maps >, last visited on Feb. 27, 2008, eleven pages.
Anonymous. (Date Unknown). “Live Search Maps,” located at <http://en.wikipedia.org/wiki/Windows—live—maps >, last visited on Mar. 3, 2008, six pages.
Anonymous. (Date Unknown). “WikiMapia,” located at <http://en.wikipedia.org/wiki/WikiMapia >, last visited on Mar. 3, 2008, three pages.
Anonymous. (2007). “Ask.com Maps & Directions,” located at <http://maps.ask.com/maps >, last visited on Mar. 3, 2008, one page.
Anonymous. (2007). “Wayfaring Follow You, Follow Me,” located at <http://www.wayfaring.com/>, last visited on Mar. 3, 2008, three pages.
Anonymous. (2008). “Platial the People's Atlas,” located at <www.platial.com >, last visited on Mar. 3, 2008, one page.
Anonymous. (2008). “Wikimpaia.org ,” located at <http://wikimpaia.org/>, last visited on Mar. 3, 2008, one page.
International Search Report and Written Opinion (PCT/US2009/046258) dated Dec. 23, 2009; 7 pages.
Almieda, R.B. et al. “A Community-Aware Search Engine,” WWW2004, New York., NY, May. 17-22, 2004, pp. 413-421.
Anonymous. (Jul. 16, 2006). MyFantasyLeague Fantasy Football League Management—Features, located at <http://web.archive.org/web/20060716072900/www.myfantasyleague.com/features.htm >, last visited on Feb. 10, 2009, four pages.
Anonymous. (Jul. 17, 2006). “Fantasy Football Lineup Analyzer—Tips for Who to Start & Who to Bench each Week,” located at http://web.archive.org/web/200607171633529/www.fantasyfootballstarters.com/lineupAnalyzer.jsp>, last visited on Feb. 10, 2009, one page.
Bharat, K. (Date Unknown). “SearchPad: Explicit Capture of Search Context to Support Web Search,” located at <http://www9.org/w9cdrom/173/173.html >, last visited Aug. 1, 2007, 13 pages.
Budzik, J. et al. (2000). “User Interactions with Everyday Applications as Context for Just-in-Time Information Access,” Proceeding of the 2000 Conference on Intelligent User Interfaces, eight pages.
Finkelstein, L. et al. (2001). “Placing Search in Context: The Concept Revisited,” WWW/O, Hong Kong, May 2-5, 2001, pp. 406-414.
Freyne, J. et al. (2004). “Further Experiments on Collaborative Ranking in Community-Based Web Search,” Artificial Intelligence Review, pp. 1-23.
Lieberman, H. (1995) “Letizia: An Agent that Assists Web Browsing,” Proceedings of the Fourteenth International Joint Conference on Artificial Intelligence, Aug. 20-25, 1995, six pages.
Mitra, M. et al. (1998). “Improving Automatic Query Expansion,” Proceedings of the AMC SIGIR, nine pages.
Rhodes, B.J. et al. (1996). “Remembrance Agent: A Continuously Running Automated Information Retrieval System,” Proceedings of the First International Conference on the Practical Application of Intelligent Agents and Multi Agent Technology (PAAM), pp. 487-495, located at <http://www.cc.gatech.edu/fac/Thad.Starner/p/032—40—agents&ubicomp/remembrance-agent . . . >, last visited Aug. 1, 2007, six pages.
Sansbury, C. (Sep. 13, 2005). “Yahoo! Widget for BBC Sports News—Scotland,” 32. located at <http://widgets.yahoo.com/gallery/view.php?widget=37220 >, last visited on Feb. 7, 2007, one page.
Yahoo! Inc. (Dec. 7, 2005). “Yahoo! Widget Engine 3.0 Reference Manual Version 3.0,” 300 pages.
U.S. Appl. No. 12/407,690, filed Mar. 19, 2009; 50 pages.
U.S. Appl. No. 12/407,681, filed Mar. 19, 2009; 56 pages.
International Search Report PCT/US2008/088228 dated Sep. 30, 2009—2 pages.
Written Opinion PCT/US2008/088228 dated Sep. 30, 2009—5 pages.
U.S. Appl. No. 12/409,867, filed Mar. 24, 2009, King.
U.S. Appl. No. 12/540,098, filed Aug. 12, 2009, Martinez.
U.S. Appl. No. 12/536,892, filed Aug. 6, 2009, King.
U.S. Appl. No. 12/540,588, filed Aug. 13, 2009, Tendjoukian.
U.S. Appl. No. 12/015,155, filed Jan. 1, 2006, Higgins.
U.S. Appl. No. 12/180,486, filed Jul. 25, 2008, Higgins.
U.S. Appl. No. 12/180,499, filed Jul. 25, 2008, Higgins.
U.S. Appl. No. 12/015,146, filed Jan. 16, 2008, Higgins.
U.S. Appl. No. 12/041,088, filed Mar. 3, 2008, Higgins.
U.S. Appl. No. 12/041,062, filed Mar. 3, 2008, Higgins.
U.S. Appl. No. 12/041,054, filed Mar. 3, 2008, Higgins.
U.S. Appl. No. 12/540,269, filed Aug. 12, 2009, Kalaboukis.
U.S. Appl. No. 11/969,815, filed Jan. 4, 2004, Davis.
U.S. Appl. No. 12/182,111, filed Jul. 29, 2008, Davis.
U.S. Appl. No. 12/434,575, filed May 1, 2009, O'Sullivan.
U.S. Appl. No. 12/434,580, filed May 1, 2009, O'Sullivan.
U.S. Appl. No. 12/407,690, filed Mar. 19, 2009, Davis.
U.S. Appl. No. 12/407,681, filed Mar. 19, 2009, Athsani.
International Search Report (PCT/US2009/030405) dated Sep. 23, 2009; 2 pages.
U.S. Appl. No. 12/041,054 file history dated Mar. 3, 2008; 64 pgs.
U.S. Appl. No. 12/041,062 file history dated Mar. 3, 2008; 66 pgs.
U.S. Appl. No. 12/041,088 file history dated Mar. 3, 2008; 66 pgs.
U.S. Appl. No. 12/169,931 file history dated Jul. 9, 2008; 66 pgs.
U.S. Appl. No. 12/170,025 file history dated Jul. 9, 2008; 67 pgs.
U.S. Appl. No. 12/180,499 file history dated Jul. 25, 2008; 67 pgs.
U.S. Appl. No. 12/180,486 file history dated Jul. 25, 2008; 65 pgs.
International Search Report PCT/US2009/030406 dated Sep. 29, 2009; 5 pages.
International Search Report and Written Opinion PCT/US2009/034445 dated Oct. 12, 2009; 7 pages.
Office Action U.S. Appl. No. 12/041,054 dated Oct. 27, 2010; 15 pages.
Office Action U.S. Appl. No. 12/041,062 dated Oct. 28, 2010; 12 pages.
International Search Report PCT/US2009/034444 dated Sep. 18, 2009; 2 pages.
Office Action U.S. Appl. No. 12/041,088 dated Oct. 4, 2010; 18 pages.
U.S. Appl. No. 11/617,451, filed Dec. 28, 2006, Kalaboukis.
U.S. Appl. No. 11/562,973, filed Nov. 22, 2006, Martinez.
U.S. Appl. No. 11/562,974, filed Nov. 22, 2006, Martinez.
U.S. Appl. No. 11/562,976, filed Nov. 22, 2006, Martinez.
U.S. Appl. No. 11/562,979, filed Nov. 22, 2006, Martinez.
U.S. Appl. No. 12/237,709, filed Sep. 25, 2008, Martinez.
U.S. Appl. No. 12/399,669, filed Mar. 6, 2009, King.
U.S. Appl. No. 11/353,657, filed Feb. 13, 2006, Mor Naaman.
U.S. Appl. No. 11/437,344, filed May 19, 2006, Jaffe.
U.S. Appl. No. 11/593,869, filed Nov. 6, 2006, Mor Naaman.
U.S. Appl. No. 11/593,668, filed Nov. 6, 2006, Mor Naaman.
Allen James F., “Maintaining Knowledge About Temporal Intervals”, Communications of the ACM, Nov. 1983, vol. 26, No. 11 pp. 832-843; 12 pages.
Press Release, “QUALCOMM Conducts First Live Demonstration of FL Technology On A Wireless Handset”, Qualcomm Inc., San Diego, Sep. 27, 2005; 3 pages.
MediaFlo, FLO Technology Overview, Qualcomm Inc. Copyright 2007; 24 pages.
Axup, Jeff et al., “Conceptualizing New Mobile Devices By Observing Gossip and Social Network Formation Amongst the Extremely Mobile”, ITEE Technical Report #459, Dec. 19, 2005, pp. 1-71.
Conhaim, Wallys W., “Social networks: the Internet continues to evolve: where is the money in all this? That is what venture capitalists are asking. (Perspectives)”, Information Today, 22, 9, 35(2), Oct. 2005.
Davis, Marc et al., “From Context to Content: Leveraging Context to Infer Media Metadata”, ACM Press, Oct. 10, 2004, pp. 1-8.
Kaasinen, E., “Behaviour & Information Technology”, Taylor & Francis, vol. 24, No. 1, Jan./Feb. 2005, pp. 37-49.
Konomi, Shin'ichi et al., “Supporting Colocated Interactions Using RFID and Social Network Displays”, Pervasive Computing, Jul.-Sep. 2006, vol. 5, No. 3, pp. 48-56.
Lin, F. et al., “A unified framework for managing Web-based services.”, Information Systems and e-Business Management, vol. 3, Oct. 2005, p. 299.
Metz, Cade, “MySpace Nation”, PC Magazine, Jun. 21, 2006.
Perkowitz, Mike et al., “Utilizing Online Communities to Facilitate Physical World Interactions”, The International Conference on Communities and Technologies, Sep. 19, 2003, Amsterdam, pp. 1 6.
Roush, Wade, “Social Machines”, Continuous Computing Blog, Jul. 5, 2005, pp. 1-21.
Roush, Wade, “Social Machines”, Technology Review, Aug. 2005, pp. 45-51.
Sheppard, Brett, “The Rights Stuff: The Integration of Enterprise Digital Rights Management Into an Enterprise Architecture”, ECantent, vol. 29, No. 9, Nov. 2006, p. 38, 40-44.
Voight, Joan et al., “Lessons for Today's Digital Market”, Adweekcom, Oct. 2, 2006, pp. 1-6.
“Companies add new communication features to photo sharing.”, Digital Imaging Digest, Feb. 2006, pp. 1-2.
“Dave.tv and Eye Music Network Empower Users to Create Their Own Music TV Channel on Their Sites With New IPTV Channel”, www.davenw.com/2006, Sep. 13, 2006, pp. 1-2.
“Digital rights management: a primer: developing a user-friendly means of protecting content.(Profile)”, Screen Digest, No. 420, p. 305, Sep. 2006.
“Emerging Markets: What media 2.0 can offer advertisers.”, Campaign, Oct. 27, 2006, p. 26.
“Reality Digital Debuts Opus”, www.lightreading.com. Sep. 25, 2006, pp. 1.
“Reality Digital—Making Media Move”, www.realitydigital.com, Nov. 28, 2006, pp. 1-2.
Notification of Transmittal of The International Search Report and The Written Opinion Of The International Search Authority, Or Declaration (PCT/US2007/'084797) dated Mar. 21, 2008; 11 pages.
International Search Report (PCT/US2007/084807) dated May 27, 2008; 3 pages.
International Preliminary Report on Patentability (PCT/US2007/084807) dated May 26, 2009; 5 pages.
International Search Report (PCT/US2010/026063) dated May 27, 2008; 3 pages.
Rekimoto, et al., “CyberCode: designing augmented reality environments with visual tags.” Proceedings of DARE 2000 on Designing augmented reality environments, Elsinore, Denmark, pp. 1-11 Apr. 12-14, 2000.
“Semacode—URL Barcodes—practical ubiquitous computing”, located at http://semacode.org visited on Apr. 13, 2007; 3 pages.
“Technical White Paper: Choosing the best 2D barcode format for mobile apps,” Semacode, Jul. 15, 2006; pp. 1-7 located at http://semacode.org/about/technical/whitepaper/best2—d—code.pdf.
Carbonell, J. et al. (Aug. 24-28, 1998). “The Use of MMR, Diversity-Based Reranking for Reordering Documents and Producing Summaries,” SIGIR '98: Proceedings of the 21 S Annual International ACM SIGIR Conference on Research and Development in Information Retrieval: Melbourne, Australia W.B. Croft et al. eds., pp. 335-336.
Cooper, M. et al. (Nov. 2-8, 2003). “Temporal Event Clustering for Digital Photo Collections,” MM'03 Berkeley, California, pp. 364-373.
Davis, M. et al. (Oct. 10-16, 2004). “From Context to Content: Leveraging Context to Infer Media Metadata,” MM'04 New York, New York. 9 pages.
Davis, M. et al. “From Context to Content: Leveraging Context for Mobile Media Metadata.” 9 pages.
Davis. M. et al. (Apr. 2-7, 2005). “MMM2: Mobile Media Metadata for Media Sharing,” CHI 2005 Portland, Oregon. 4 pages.
Davis, M. et al. “Mobile Media Metadata for Mobile Imaging.” Jun. 27-30, 2004; 4 pages.
Davis, M. et al. “Using Context and Similarity for Face and Location Identification.” 10 pages.
Flickr. “Welcome to Flickr—Photo Sharing,” located at <http://www.flickr.com> visited on Feb. 26, 2007, one page.
Gargi, U. (Aug. 7, 2003). “Consumer Media Capture: Time-Based Analysis and Event Clustering,” Technical Report HPL-2003-165 HP Laboratories Palo Alto, pp. 1-15.
Goldberger, J. et al. The Hungarian Clustering Method, located at <http://scholar.googles.com/scholar?num=20&h1=en&lr=&9=cache:vbwslsm1CisJ:www.openu .acil/Personal—sites/tamirtassa/Publications/hcm.pdf+goldberger+clustering+method+hungarian> visited on Mar. 1, 2007, twelve pages.
Graham, A. et al. (Jul. 13-17, 2002). Time as Essence for Photo Browsing Through Personal Digital Libraries, JCDL '02 Portland, Oregon. 11 pages.
Jaffe, A. et al. (May 23-26, 2006). “Generating Summaries for Large Collections of Geo-Referenced Photographs,” WWW 2006 Edinburgh, Scotland. 2 pages.
Jaffe, A. et al. (Oct. 26-27, 2006). “Generating Summaries and Visualization for Large Collections of Geo-Referenced Photographs,” MIR '06 Santa Barbara, California. 11 pages.
Joshi, D. et al. (Oct. 15-16, 2004). “The Story Picturing Engine: Finding Elite Images to Illustrate a Story Using Miitual Reinforcement,” MIR '04 New York. 9 pages.
Naaman, M. et al. (Nov. 2003). “From Where to What: Metadata Sharing for Digital Photographs with Geographic Coordinates,” In On the Move to Meaningful Internet Systems 2003: Coop/S, DOA, and ODBASE R. Meersman et al. eds., pp. 196-217.
Naaman, M. et al. (Jun. 7-11, 2004). “Automatic Organization for Digital Photographs with Geographic Coordinates” Proceedings of the Fourth ACM/IEEE Joint Conference on Digital Libraries Global Reach and Diverse Impact: Tucson, Arizona, pp. 53-62.
Nair, R. et al. (Nov. 6-11, 2005). “Photo L01: Browsing Multi-User Photo Collections,” MM'05 Singapore, pp. 223-224.
0'Hare, N. et al. “Combination of Content Analysis and Context Features for Digital Photograph Retrieval.” 7 pages.
Pigeau, A. et al. (Jun. 17, 2005). “Organizing a Personal Image Collection with Statistical Model-Based ICL Clustering on Spatio-Temporal Camera Phone Meta-Data.” 25 pages.
Sarvas, R. et al. (Jun. 6-9, 2004). “Metadata Creation System for Mobile Images,” MobiSys'04 Boiton, Massachusetts, pp. 36-48.
Toyama, K. et al. (Nov. 2-8, 2003). “Geographic Location Tags on Digital Images,” MM ‘03’Berkeley: California. 12 pages.
U.S. Appl. No. 11/952,007, filed Dec. 6, 2007, Davis.
U.S. Appl. No. 11/958,157, filed Dec. 17, 2007, Hayashi.
U.S. Appl. No. 11/952,875, filed Dec. 7, 2007, Davis.
U.S. Appl. No. 11/960,368, filed Dec. 19, 2007, Madsen.
U.S. Appl. No. 11/953,454, filed Dec. 10, 2007, Davis.
U.S. Appl. No. 11/953,494, filed Dec. 10, 2007, Davis.
U.S. Appl. No. 12/236,668, filed Sep. 24, 2008, Davis.
U.S. Appl. No. 12/059,594, filed Mar. 31, 2008, Martinez.
U.S. Appl. No. 12/057,878, filed Mar. 28, 2008, Martinez.
U.S. Appl. No. 12/057,943, filed Mar. 28, 2008, Martinez.
U.S. Appl. No. 11/969,751, filed Jan. 4, 2008, Martinez.
U.S. Appl. No. 12/145,145, filed Jun. 24, 2008, Davis.
U.S. Appl. No. 12/163,249, filed Jun. 27, 2008, Kalaboukis.
U.S. Appl. No. 12/182,969, filed Jul. 30, 2008, Higgins.
U.S. Appl. No. 12/182,813, filed Jul. 30, 2008, Higgins.
U.S. Appl. No. 12/163,314, filed Jun. 27, 2008, Higgins.
U.S. Appl. No. 12/163,396, filed Jun. 27, 2008, Higgins.
U.S. Appl. No. 12/195,969, filed Aug. 21, 2008, Martinez.
U.S. Appl. No. 12/234,000, filed Sep. 19, 2008, Martinez.
U.S. Appl. No. 12/241,590, filed Sep. 30, 2008, Athsani.
U.S. Appl. No. 12/241,687, filed Sep. 30, 2008, Davis.
U.S. Appl. No. 12/206,172, filed Sep. 8, 2008, Higgins.
U.S. Appl. No. 12/273,291, filed Nov. 18, 2008, Nair.
U.S. Appl. No. 12/273,317, filed Nov. 18, 2008, Nair.
U.S. Appl. No. 12/273,345, filed Nov. 18, 2008, Nair.
U.S. Appl. No. 12/273,259, filed Nov. 18, 2008, Martinez.
U.S. Appl. No. 12/241,198, filed Sep. 30, 2008, Higgins.
U.S. Appl. No. 12/339,355, filed Dec. 19, 2008, Higgins.
U.S. Appl. No. 12/329,038, filed Dec. 5, 2008, Higgins.
U.S. Appl. No. 12/242,656, filed Sep. 30, 2008, Burgener.
U.S. Appl. No. 12/273,371, filed Nov. 18, 2008, Nair.
U.S. Appl. No. 12/357,311, filed Jan. 21, 2009, Higgins.
U.S. Appl. No. 12/357,332, filed Jan. 21, 2009, Higgins.
U.S. Appl. No. 12/357,345, filed Jan. 21, 2009, Higgins.
U.S. Appl. No. 12/357,285, filed Jan. 21, 2009, Higgins.
Nedos, A; Singh K., Clarke S, Proximity Based Group Communications for Mobile Ad Hoc Networks; Proximity-Based Group Communication; Global Smart Spaces; D.14; Oct. 3, 2003; 31 pages.
Brunato, M; Battiti R. “Pilgrim: A Location Broker and Mobility-Aware Recommendation System”; Technical report DIT-02-0092, Universita di Trento, Oct. 2002; 8 pages.
Backstrom et al., Spatial Variation in Search Engine Queries, WWW•2008, Beijing, China (Apr. 21-25, 2008).
Gan et al., Analysis of Geographic Queries in a Search Engine Log, LocWeb 2008, Beijing, China (Apr. 22, 2008).
Jones et al., Geographic Intention and Modification in Web Search, International Journal of Geographical Information Science, vol. 22, No. 3, pp. 1-20 (Jul. 2008).
Sanderson et al., Analyzing Geographic Queries; Department of Information Studies; University of Sheffield, UK; 2 pages.
Go With the Flow, The Economist Technology Quarterly, vol. 382, Issue 8519, 4 pages, (Mar. 10, 2007).
International Search Report and Written Opinion (PCT/US2009/060476) dated May 4, 2010; 12 pages.
International Search Report and Written Opinion (PCT/US2009/060374) dated Apr. 30, 2010; 12 pages.
International Search Report (PCT/US2009/060379) dated Apr. 30, 2010; 3 pages.
International Search Report and Written Opinion (PCT/US2008/085135) dated May 25, 2009; 7 pages.
International Search Report (PCT/US2009/055503) dated Apr. 8, 2010; 3 pages.
Written Opinion (PCT/US2008/085915) dated Jun. 29, 2009; 4 pages.
Written Opinion (PCT/US2008/086948) dated May 21, 2009; 5 pages.
International Search Report and Written Opinion (PCT/US2009/051247) dated Jan. 25, 2010; 9 pages.
Related Publications (1)
Number Date Country
20100138491 A1 Jun 2010 US