US20120066303A1 - Synchronized group location updates - Google Patents
Synchronized group location updates Download PDFInfo
- Publication number
- US20120066303A1 US20120066303A1 US13/027,756 US201113027756A US2012066303A1 US 20120066303 A1 US20120066303 A1 US 20120066303A1 US 201113027756 A US201113027756 A US 201113027756A US 2012066303 A1 US2012066303 A1 US 2012066303A1
- Authority
- US
- United States
- Prior art keywords
- user
- location
- synchronized
- users
- programmatically determining
- 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.)
- Abandoned
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/10—File systems; File servers
- G06F16/17—Details of further file system functions
- G06F16/1734—Details of monitoring file system events, e.g. by the use of hooks, filter drivers, logs
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/10—File systems; File servers
- G06F16/18—File system types
- G06F16/1805—Append-only file systems, e.g. using logs or journals to store data
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/10—File systems; File servers
- G06F16/18—File system types
- G06F16/182—Distributed file systems
- G06F16/1834—Distributed file systems implemented based on peer-to-peer networks, e.g. gnutella
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/40—Information retrieval; Database structures therefor; File system structures therefor of multimedia data, e.g. slideshows comprising image and additional audio data
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/95—Retrieval from the web
- G06F16/953—Querying, e.g. by the use of web search engines
- G06F16/9537—Spatial or temporal dependent retrieval, e.g. spatiotemporal queries
-
- 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/222—Monitoring or handling of messages using geographical location information, e.g. messages transmitted or received in proximity of a certain spot or area
-
- 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
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/2866—Architectures; Arrangements
- H04L67/30—Profiles
- H04L67/306—User profiles
-
- 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/535—Tracking the activity of the user
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q50/00—Information and communication technology [ICT] specially adapted for implementation of business processes of specific business sectors, e.g. utilities or tourism
- G06Q50/01—Social networking
Definitions
- the present disclosure relates to location updates.
- SLBSs Social Location-Based Services
- Gowalla® and FourSquareTM check-in services require constant location updates to be accurate and useful.
- users either are not capable of providing location updates (e.g., they do not have their mobile device with them or turned on) or do not desire to provide location updates (e.g., they are too busy talking with friends).
- SLBSs Social Location-Based Services
- users either are not capable of providing location updates (e.g., they do not have their mobile device with them or turned on) or do not desire to provide location updates (e.g., they are too busy talking with friends).
- SLBSs Social Location-Based Services
- a location update for a user is utilized as a location update for the user and one or more additional users that have been location-synchronized to the user.
- a location update is received for a first user.
- One or more second users that have been location-synchronized to the first user are then identified.
- a location reported by the location update for the first user is recorded, or stored, as a current location of the first user and a current location of each of the one or more second users that have been location-synchronized to the first user.
- a location-based service such as a social location-based service, may then be provided based on the current locations of the first and the one or more second users.
- FIG. 1 illustrates an exemplary system in which a location update for a user is utilized as a location update for a corresponding location-synchronized group of users according to one embodiment of the present disclosure
- FIG. 2 illustrates the operation of the system of FIG. 1 according to one embodiment of the present disclosure
- FIG. 3 illustrates the operation of a location update server of the Social Location-Based Service (SLBS) of FIG. 1 to receive and process a location update according to one embodiment of the present disclosure
- SLBS Social Location-Based Service
- FIG. 4 illustrates the operation of the location update server of the SLBS of FIG. 1 to create and maintain location-synchronized groups of users according to one embodiment of the present disclosure
- FIG. 5 illustrates the operation of the location update server of the SLBS of FIG. 1 to create and maintain location-synchronized groups of users according to another embodiment of the present disclosure
- FIG. 6 illustrates the operation of the location update server of the SLBS of FIG. 1 to create and maintain location-synchronized groups of users according to yet another embodiment of the present disclosure
- FIG. 7 illustrates the operation of the location update server of the SLBS of FIG. 1 to de-synchronize users in location-synchronized groups of users according to one embodiment of the present disclosure
- FIG. 8 illustrates the operation of the location update server of the SLBS of FIG. 1 to de-synchronize users in location-synchronized groups of users according to another embodiment of the present disclosure
- FIG. 9 illustrates the operation of the location update server of the SLBS of FIG. 1 to de-synchronize users in location-synchronized groups of users according to yet another embodiment of the present disclosure
- FIG. 10 is a block diagram of a computer server that hosts the SLBS of FIG. 1 according to one embodiment of the present disclosure.
- FIG. 11 is a block diagram of one of the mobile devices in the system of FIG. 1 according to one embodiment of the present disclosure.
- FIG. 1 illustrates a system 10 in which a location update for a user is utilized as a location update for a corresponding location-synchronized group of users according to one embodiment of the present disclosure.
- the system 10 includes a Social Location-Based Service (SLBS) 12 and a number of mobile devices 14 - 1 through 14 -N having associated users 16 - 1 through 16 -N connected by a network 18 .
- the mobile devices 14 - 1 through 14 -N are more generally referred to herein collectively as mobile devices 14 and individually as mobile device 14 .
- the users 16 - 1 through 16 -N are more generally referred to herein collectively as users 16 and individually as user 16 .
- the network 18 may be any type of Wide Area Network (WAN) or Local Area Network (LAN), or any combination thereof.
- the network 18 is a distributed public network, such as the Internet, where the mobile devices 16 are connected to the network 18 via local wireless connections (e.g., IEEE 802.11x connections through corresponding IEEE 802.11x base stations or access points) or mobile communications connections.
- Mobile communications connections may be, for example, 3 G wireless connections such as, for example, Global System for Mobile communications (GSM) or Code Division Multiple Access (CDMA) wireless connections, 4 G wireless connections such as, for example, Wideband CDMA (W-CDMA) or Long Term Evolution (LTE) wireless connections, or the like.
- GSM Global System for Mobile communications
- CDMA Code Division Multiple Access
- W-CDMA Wideband CDMA
- LTE Long Term Evolution
- the SLBS 12 is generally any type of social location-based service and is preferably implemented in software hosted by a computer server or a number of computer servers operating in a collaborative manner for purposes of load sharing and/or redundancy.
- the SLBS 12 may be a Mobile Aggregate Profile (MAP) service such as that described in U.S. patent application Ser. No. 12/645,532, entitled FORMING CROWDS AND PROVIDING ACCESS TO CROWD DATA IN A MOBILE ENVIRONMENT, which was filed Dec. 23, 2009; U.S. patent application Ser. No. 12/645,539, entitled ANONYMOUS CROWD TRACKING, which was filed Dec. 23, 2009; U.S. patent application Ser. No.
- the MAP service operates to, among other things, create and maintain a historical record of anonymized user profile data by geographic location and to create and track crowds of users all based on location updates received for users of the MAP service.
- the SLBS 12 is not limited to the MAP service.
- the SLBS 12 may alternatively be a check-in service similar to the FourSquareTM check-in service or the Gowalla® check-in service.
- Other types of social location-based services will be apparent to one of ordinary skill in the art upon reading this disclosure and are to be considered within the scope of the present disclosure.
- the SLBS 12 includes a location update server 20 and a user records repository 22 .
- the location update server 20 is preferably implemented in software and generally operates to receive location updates, process the location updates, and update user records of the users 16 stored in the user records repository 22 .
- location-synchronized groups of users are created either manually by the users 16 or programmatically by the location update server 20 .
- the location-synchronized groups of users are recorded in the user records of the users 16 stored in the user records repository 22 .
- the user records repository 22 generally includes a user record for each of the users 16 , where each of the users 16 is a registered user of the SLBS 12 .
- the user record of each of the users 16 includes a current location of the user 16 .
- the user record of the user 16 includes a list of other users that are location-synchronized to the user 16 and/or an identifier of another user 16 to which the user 16 is location-synchronized. Note that, in one embodiment, the other users that are location-synchronized to the user 16 may all be users 16 of the SLBS 12 .
- the other users that are location-synchronized to the user 16 may include one or more of the users 16 of the SLBS 12 and/or users (e.g., user 32 , discussed below) that are not registered with the SLBS 12 .
- the user record of the user 16 may also include a historical record of location updates received for the user 16 that includes one or more previous locations of the user 16 as defined by one or more previous location updates for the user 16 .
- the user record of the user 16 may include one or more user settings defined by the user 16 for use by the location update server 20 in programmatically location-synchronizing the user 16 to other users 16 , programmatically location-synchronizing other users 16 to the user 16 , programmatically de-synchronizing the user 16 from other users 16 , and/or programmatically de-synchronizing other users 16 from the user 16 .
- the user records repository 22 may also store user records for each of a number of non-registered users of the SLBS 12 such as, for example, user 32 (discussed below).
- the user record of that non-registered user includes a current location of the non-registered user.
- the current location of the non-registered user is the current location of the user 16 to which the non-registered user has been location-synchronized.
- the user record of the non-registered user may also include user profile data, which may be provided by the non-registered user or obtained from a third-party source (e.g., the non-registered user's Facebook® profile).
- the mobile devices 14 may be mobile smart phones, portable media player devices, mobile gaming devices, mobile computers (e.g., laptop computers), or the like.
- Some exemplary mobile devices that may be programmed or otherwise configured to operate as the mobile devices 14 are the Apple® iPhone®, the Palm Pre®, the Samsung RogueTM, the Blackberry StormTM, the Motorola DROID or similar phone running Google's AndroidTM Operating System, an Apple® iPad®, and the Apple® iPod Touch® device.
- this list of exemplary mobile devices is not exhaustive and is not intended to limit the scope of the present disclosure.
- the mobile devices 14 - 1 through 14 -N include SLBS clients 24 - 1 through 24 -N (generally referred to herein collectively as SLBS clients 24 or individually as SLBS client 24 ) which include corresponding location update clients 26 - 1 through 26 -N (generally referred to herein collectively as location update clients 26 and individually as location update client 26 ).
- the mobile devices 14 - 1 through 14 -N also include location functions 28 - 1 through 28 -N (generally referred to herein collectively as location functions 28 and individually as location function 28 ).
- the SLBS clients 24 are preferably implemented in software and generally operate to provide an interface by which the mobile devices 14 and the users 16 interact with the SLBS 12 .
- the location update clients 26 generally operate to obtain current locations of the mobile devices 14 , and thus the users 16 , from the location functions 28 and send corresponding location updates to the location update server 20 of the SLBS 12 .
- the location update clients 26 may send the location updates periodically, in response to triggering events such as a change in the location of the users 16 , or in response to a request from the location update server 20 .
- the location updates may be for geographic locations at which the users 16 are located (e.g., latitude and longitude, street address, or the like) or for “check-in” locations.
- Check-in locations are Points of Interest (POIs) at or near the current geographic locations of the users 16 that have been selected by the users 16 , or programmatically selected on behalf of the users 16 , for “check-in” in a manner similar to that done for check-in services such as, for example, the FourSquareTM and Gowalla® check-in services.
- POIs Points of Interest
- the location function 28 of the mobile device 14 may be implemented in hardware, software, or a combination thereof.
- the location function 28 of the mobile device 14 operates to determine or otherwise obtain the geographic location of the mobile device 14 .
- the location function 28 of the mobile device 14 may be, or include, a Global Positioning System (GPS) receiver.
- GPS Global Positioning System
- the location function 28 may include hardware and/or software that enables improved location tracking in indoor environments such as, for example, shopping malls.
- the location function 28 may be part of, or compatible with, the InvisiTrack Location System provided by InvisiTrack and described in U.S. Pat. No.
- the system 10 also includes a guest device 30 having an associated user 32 .
- the guest device 30 may be a mobile device similar to the mobile devices 14 or other computing device (e.g., a personal computer).
- the user 32 is enabled to access the SLBS 12 via the guest device 30 to, for example, request to be location-synchronized with a select one of the users 16 .
- the user 32 is not a registered user of the SLBS 12 .
- the system 10 may include multiple guest devices 30 and associated users 32 .
- FIG. 2 illustrates the operation of the system 10 of FIG. 1 according to one embodiment of the present disclosure.
- the mobile device 14 and more specifically the location update client 26 of the SLBS client 24 of the mobile device 14 , sends a location update to the SLBS 12 for the user 16 of the mobile device 14 (step 100 ).
- the location update includes a current location of the user 16 .
- the current location of the user 16 is the current geographic location of the mobile device 14 , and thus the user 16 , as determined by the location function 28 of the mobile device 14 .
- the current location of the user 16 may be expressed as any data that defines the location of the user 16 in 2-dimensional or 3-dimensional space.
- the current location of the user 16 may be expressed as a latitude and longitude coordinate pair and, in some embodiments, an altitude.
- the current location of the user 16 may be expressed as a street address.
- the current location of the user 16 may be a “check-in” location selected by the user 16 or programmatically selected by the SLBS client 24 on behalf of the user 16 . More specifically, the SLBS client 24 may interact with the SLBS 12 to obtain a list of one or more POIs at or near the current geographical location of the user 16 (e.g., street address, latitude and longitude, or the like) as determined by the location function 28 .
- the SLBS client 24 may then present the list of POIs to the user 16 , and the user 16 may select a POI for which to “check-in.”
- the location update for the user 16 may then be expressed as data that identifies the POI selected by the user 16 for check-in.
- the location update server 20 of the SLBS 12 identifies one or more other users that are location-synchronized to the user 16 (step 102 ).
- the other users that are location-synchronized to the user 16 may include only other ones of the users 16 of the SLBS 12 , only non-registered users of the SLBS 12 such as the user 32 , or one or more of the other users 16 of the SLBS 12 and non-registered users of the SLBS such as the user 32 depending on the particular implementation.
- the location update server 20 of the SLBS 12 then records the location of the user 16 of the mobile device 14 reported in the location update as the current location of the user 16 of the mobile device 14 and the current location(s) of the other user(s) that are location-synchronized to the user 16 (step 104 ).
- the location reported in the location update is recorded as the current locations of the user 16 and the other user(s) that are location-synchronized to the user 16 by storing the location as the current locations in the user records of those users 16 .
- the SLBS 12 provides a desired social location-based service to the users 16 of the SLBS 12 using the current locations of the users 16 and, in some embodiments, the current locations of non-registered users (step 106 ).
- FIG. 3 illustrates the operation of the location update server 20 of the SLBS 12 of FIG. 1 to receive and process location updates according to one embodiment of the present disclosure.
- the location update server 20 receives a location update for one of the users 16 (step 200 ).
- the location update server 20 determines whether any users are location-synchronized to the user 16 (step 202 ). If not, the process proceeds to step 206 . If so, then the location update server 20 records, or stores, the location reported by the location update as the current location of the user(s) that are location-synchronized to the user 16 (step 204 ). In addition, the location update server 20 records, or stores, the location reported by the location update as the current location of the user 16 for which the location update was received (step 206 ). The process then returns to step 200 and is repeated for the next received location update from one of the users 16 .
- FIG. 4 illustrates the operation of the location update server 20 of the SLBS 12 of FIG. 1 to create and maintain location-synchronized groups of users according to one embodiment of the present disclosure.
- requesting users manually request other users 16 to which to be location-synchronized.
- the location update server 20 of the SLBS 12 first receives a location-synchronization request from a requesting user (step 300 ).
- the requesting user may be one of the users 16 of the SLBS 12 .
- the requesting user may alternatively be a non-registered user such as, for example, the user 32 of the guest device 30 .
- the location-synchronization request is a request from the requesting user to be location-synchronized to a select one of the users 16 of the SLBS 12 (referred to herein as the “select user”).
- the select user is identified in the location-synchronization request.
- the manner in which the select user is selected by the requesting user may vary depending on the particular implementation. For example, the requesting user may select the select user by entering an identifier (ID) of the select user for the SLBS 12 , entering an e-mail address that may be utilized by the SLBS 12 to identify one of the users 16 as the select user, selecting the select user from a list of users such as, for example, a contact list of the requesting user maintained by the SLBS 12 , or the like.
- ID identifier
- the location-synchronization request may also include one or more settings configured by the requesting user that define when the requesting user is to be de-synchronized from the select user (i.e., define when the requesting user is to no longer be location-synchronized to the select user).
- the settings may include one or more time-based settings.
- the settings may include a setting that defines an amount of time that the requesting user is to be location-synchronized to the select user or an end-time that defines the time at which the requesting user is to be de-synchronized from the select user. It should be noted that while the settings may be included in the location-synchronization request, the settings may alternatively be predefined by the requesting user and included in the user record of the requesting user.
- the location update server 20 of the SLBS 12 records, or stores, the requesting user as a location-synchronized user of the select user (step 302 ). More specifically, in one embodiment, the location update server 20 adds the requesting user to a list of location-synchronized users of the select user maintained in the user record of the select user. In another embodiment, the location update server 20 adds the select user as the user to which the requesting user is location-synchronized, which may be maintained in the user record of the requesting user. From this time and until the requesting user and the select user are de-synchronized, location updates for the select user will also be recorded as location updates for the requesting user.
- FIG. 5 illustrates the operation of the location update server 20 of the SLBS 12 of FIG. 1 to create and maintain location-synchronized groups of users according to another embodiment of the present disclosure.
- the users 16 manually request other users that are to be location-synchronized to the users 16 .
- the location update server 20 of the SLBS 12 first receives a location-synchronization request from a requesting user, which in this embodiment is one of the users 16 of the SLBS 12 (step 400 ).
- the location-synchronization request is a request from the requesting user for a select user, or possibly multiple select users, to be location-synchronized to the requesting user.
- the select user is identified in the location-synchronization request.
- the select user may be a select one of the users 16 of the SLBS 12 , a non-registered user such as but not limited to the user 32 of the guest device 30 , or either a select one of the users 16 of the SLBS 12 or a non-registered user.
- the manner in which the select user is selected by the requesting user may vary depending on the particular implementation. For example, the requesting user may select the select user by entering an ID of the select user for the SLBS 12 , entering an e-mail address that may be utilized by the SLBS 12 to identify the select user, selecting the select user from a list of users such as, for example, a contact list of the requesting user, or the like.
- the location-synchronization request may also include one or more settings configured by the requesting user that define when the select user is to be de-synchronized from the requesting user (i.e., define when the select user is to no longer be location-synchronized to the requesting user).
- the settings may include one or more time-based settings.
- the settings may include a setting that defines an amount of time that the select user is to be location-synchronized to the requesting user or an end-time that defines the time at which the select user is to be de-synchronized from the requesting user. It should be noted that while the settings may be included in the location-synchronization request, the settings may alternatively be predefined by the requesting user and included in the user record of the requesting user.
- the location update server 20 of the SLBS 12 records, or stores, the select user as a location-synchronized user of the requesting user (step 402 ). More specifically, in one embodiment, the location update server 20 adds the select user to a list of location-synchronized users of the requesting user maintained in the user record of the requesting user. In another embodiment, the location update server 20 adds the requesting user as the user to which the select user is location-synchronized, which may be maintained in the user record of the select user. From this time and until the requesting user and the select user are de-synchronized, location updates for the requesting user will also be recorded as location updates for the select user.
- FIG. 6 illustrates the operation of the location update server 20 of the SLBS 12 of FIG. 1 to create and maintain location-synchronized groups of users according to yet another embodiment of the present disclosure.
- the location update server 20 programmatically selects users to be location-synchronized. As illustrated, the location update server 20 first determines whether a particular user pair should be location-synchronized (step 500 ). More specifically, the location update server 20 determines whether a first user in the user pair should be location-synchronized to a second user in the user pair.
- the determination may be made based on user settings of one or both of the users in the user pair, one or more system-defined rules, the current location of one or both of the users in the user pair, historical locations of one or both of the users in the user pair, information obtained from one or more third-party sources that is indicative of spatial proximity of the first and second user at the current time or historically, or a combination thereof.
- the third-party source may include, for example, the Twitter® micro-blogging and social networking service where current and/or historical tweets from the two users that are tagged with the geographic locations of the users in the user pair at the time of sending the tweets are utilized to determine the current and/or historical spatial proximity of the two users.
- a text analysis of the tweet may additionally or alternatively be analyzed to determine users that the sending user is near at that time.
- user settings of one or both of the users in the user pair may indicate that the first user is to be location-synchronized to the second user if a location update has not been received from the first user within a defined amount of time (e.g., 30 minutes) and the two users have been located together for at least a defined amount of time (e.g., past 2 hours).
- user settings of one or both of the users in the user pair may indicate that the first user is to be location-synchronized to the second user if the first user has historically been located at the same location as the second user.
- the user settings of one or both of the users may indicate that the first user is to be location-synchronized to the second user if the first user has been located at the same location as the second user on each of the last three Friday evenings from 7 pm to 10 pm.
- system-defined rules may additionally or alternatively be used.
- the location update server 20 determines that the first user is to be location-synchronized to the second user, then the location update server 20 records the first user as a location-synchronized user of the second user (step 502 ).
- a weight may be assigned to the first user as a location-synchronized user of the second user that reflects a degree of certainty, or sureness, that the first user should be location-synchronized to the second user. This weighting may subsequently be adjusted by users, such as but not limited to the first user or the second user, or other entities.
- Such feedback may be utilized by the location update server 20 to improve its methods of determining when it is appropriate to location-synchronize these particular users and/or users in the system in general based on, for example, a statistical analysis of the feedback.
- the process of FIG. 6 may be performed in response to a triggering event and may also be repeated for additional user pairs.
- the process of FIG. 6 may be performed in response to receiving a location update for the second user and may be repeated for a number of user pairs that each include the second user (e.g., N ⁇ 1 user pairs that each include the second user and a different one of the users 16 ).
- the process of FIG. 6 may be performed between steps 200 and 202 of the process of FIG. 3 such that any additional users that should be location-synchronized to the second user are identified before the location reported in the location update for the second user is recorded as the current locations of the other users 16 that are location-synchronized to the second user.
- FIG. 7 illustrates the operation of the location update server 20 of the SLBS 12 of FIG. 1 to de-synchronize users in location-synchronized groups of users according to one embodiment of the present disclosure.
- requesting users manually request users 16 from which to be de-synchronized.
- the location update server 20 of the SLBS 12 first receives a de-synchronization request from a requesting user (step 600 ).
- the requesting user is one of the users 16 of the SLBS 12 .
- the requesting user is a non-registered user of the SLBS 12 .
- the requesting user is either one of the users 16 of the SLBS 12 or a non-registered user of the SLBS 12 .
- the de-synchronization request is a request from the requesting user to be de-synchronized, or removed, as a location-synchronized user of a select user.
- the select user is a select one of the users 16 and is identified in the de-synchronization request.
- the manner in which the select user is selected by the requesting user may vary depending on the particular implementation. For example, the requesting user may select the select user by entering an ID of the select user for the SLBS 12 , entering an e-mail address that may be utilized by the SLBS 12 to identify one of the users 16 as the select user, selecting the select user from a list of users such as, for example, a contact list of the requesting user maintained by the SLBS 12 , or the like.
- the location update server 20 of the SLBS 12 removes the requesting user as a location-synchronized user of the select user (step 602 ). More specifically, in one embodiment, the location update server 20 removes the requesting user from a list of location-synchronized users of the select user maintained in the user record of the select user. In another embodiment, the location update server 20 removes the select user as the user to which the requesting user is location-synchronized as maintained in the user record of the requesting user.
- FIG. 8 illustrates the operation of the location update server 20 of the SLBS 12 of FIG. 1 to de-synchronize users in location-synchronized groups of users according to another embodiment of the present disclosure.
- requesting users manually request users 16 that are to be de-synchronized from the requesting user.
- the location update server 20 of the SLBS 12 first receives a de-synchronization request from a requesting user, which in this embodiment is one of the users 16 of the SLBS 12 (step 700 ).
- the de-synchronization request is a request from the requesting user for a select user, or possibly multiple select users, to be de-synchronized from the requesting user.
- the select user is identified in the de-synchronization request and may be another one of the users 16 of the SLBS 12 or a non-registered user depending on the particular implementation. Further, the manner in which the select user is selected by the requesting user may vary depending on the particular implementation. For example, the requesting user may select the select user by entering an ID of the select user for the SLBS 12 , entering an e-mail address that may be utilized by the SLBS 12 to identify the select user, selecting the select user from a list of users such as, for example, a contact list of the requesting user, or the like.
- the location update server 20 of the SLBS 12 removes the select user as a location-synchronized user of the requesting user (step 702 ). More specifically, in one embodiment, the location update server 20 removes the select user from a list of location-synchronized users of the requesting user maintained in the user record of the requesting user. In another embodiment, the location update server 20 removes the requesting user as the user to which the select user is location-synchronized as maintained in the user record of the select user.
- FIG. 9 illustrates the operation of the location update server 20 of the SLBS 12 of FIG. 1 to de-synchronize users in location-synchronized groups of users according to yet another embodiment of the present disclosure.
- the location update server 20 programmatically de-synchronizes users. As illustrated, the location update server 20 first determines whether a particular user pair should be de-synchronized (step 800 ). More specifically, the location update server 20 determines whether a first user in the user pair should be de-synchronized from second user in the user pair.
- the determination may be made based on user settings of one or both of the users in the user pair, one or more system-defined rules, the current location of one or both of the users in the user pair, historical locations of one or both of the users in the user pair, information obtained from one or more third-party sources that is indicative of spatial proximity of the first and second users, or a combination thereof.
- user settings of one or both of the users in the user pair may indicate that the first user is to be de-synchronized from the second user if a location update is received from the first user and the reported location of the first user is different from (e.g., more than a pre-defined distance from) the current location of the second user.
- system-defined rules may additionally or alternatively be used.
- the user settings may indicate that the first user is to be de-synchronized from the second user once the first user is no longer spatially proximate to the second user (e.g., not within a predefined distance from the second user, not at the same street address as the second user, or the like).
- the location update server 20 determines that the first user is to be de-synchronized from the second user, then the location update server 20 de-synchronizes the users by removing the first user as a location-synchronized user of the second user (step 802 ). In this example, the process ends, at least with respect to this particular user pair. It should be noted that the process of FIG. 9 may be performed in response to a triggering event and may also be repeated for additional user pairs. For example, the process of FIG. 9 may be performed in response to receiving a location update for the second user and may be repeated for a number of location-synchronized user pairs that each include the second user and a different user that is location-synchronized to the second user. As a more specific example, the process of FIG.
- steps 200 and 202 of the process of FIG. 3 may be performed between steps 200 and 202 of the process of FIG. 3 such that any users that should be de-synchronized from the second user are identified and removed before the location reported in the location update for the second user is recorded as the current locations of the location-synchronized users of the second user.
- FIGS. 7 through 9 illustrate three exemplary processes by which users are de-synchronized
- de-synchronization of those users is scheduled for a defined point in time in the future.
- a synchronization request from a requesting user may define an amount of time that the users are to be location-synchronized or define a specific time at which de-synchronization is to occur.
- the location update server 20 may schedule de-synchronization at the appropriate time and perform de-synchronization at that time.
- the user settings of one or both of the users or system-defined settings may define an amount of time that the users are to be synchronized. The location update server 20 may then schedule de-synchronization at the appropriate time and then de-synchronize the users at that time.
- FIG. 10 is a block diagram of a computer server 36 hosting the SLBS 12 according to one embodiment of the present disclosure.
- the computer server 36 includes a controller 38 connected to memory 40 , one or more secondary storage devices 42 , and a communication interface 44 by a bus 46 or similar mechanism.
- the controller 38 is a microprocessor, digital Application Specific Integrated Circuit (ASIC), Field Programmable Gate Array (FPGA), or similar hardware component.
- the controller 38 is a microprocessor
- the SLBS 12 is implemented in software and stored in the memory 40 for execution by the controller 38 .
- the user records repository 22 may be stored in the memory 40 or the one or more secondary storage devices 42 .
- the secondary storage devices 42 are digital data storage devices such as, for example, one or more hard disk drives.
- the communication interface 44 is a wired or wireless communication interface that communicatively couples the computer server 36 to the network 18 ( FIG. 1 ).
- the communication interface 44 may be an Ethernet interface, local wireless interface such as a wireless interface operating according to one of the suite of IEEE 802.11 standards, or the like.
- FIG. 11 is a block diagram of one of the mobile devices 14 according to one embodiment of the present disclosure. This discussion is equally applicable to the other mobile devices 14 .
- the mobile device 14 includes a controller 48 connected to memory 50 , a communication interface 52 , one or more user interface components 54 , and the location function 28 by a bus 56 or similar mechanism.
- the controller 48 is a microprocessor, digital ASIC, FPGA, or similar hardware component.
- the controller 48 is a microprocessor, and the SLBS client 24 is implemented in software and stored in the memory 50 for execution by the controller 48 .
- the location function 28 is a hardware component such as, for example, a GPS receiver.
- the communication interface 52 is a wireless communication interface that communicatively couples the mobile device 14 to the network 18 ( FIG. 1 ).
- the communication interface 52 may be a local wireless interface such as a wireless interface operating according to one of the suite of IEEE 802.11 standards, a mobile communications interface such as a cellular telecommunications interface (e.g., 3 G telecommunications interface such as a GSM interface or the like, or a 4 G telecommunications interface such as a LTE interface or the like).
- the one or more user interface components 54 include, for example, a touchscreen, a display, one or more user input components (e.g., a keypad), a speaker, or the like, or any combination thereof.
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Databases & Information Systems (AREA)
- General Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Data Mining & Analysis (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computing Systems (AREA)
- Computer Hardware Design (AREA)
- Multimedia (AREA)
- Telephonic Communication Services (AREA)
- Information Transfer Between Computers (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
Description
- This application claims the benefit of provisional patent application Ser. No. 61/309,903, filed Mar. 3, 2010, the disclosure of which is hereby incorporated herein by reference in its entirety.
- The present disclosure relates to location updates.
- Social Location-Based Services (SLBSs), such as the Gowalla® and FourSquare™ check-in services, require constant location updates to be accurate and useful. However, in many situations, users either are not capable of providing location updates (e.g., they do not have their mobile device with them or turned on) or do not desire to provide location updates (e.g., they are too busy talking with friends). As such, there is a need for a system and method that enables location updates from users even in situations where those users are not capable of providing or do not desire to provide location updates.
- Systems and methods are disclosed in which a location update for a user is utilized as a location update for the user and one or more additional users that have been location-synchronized to the user. In general, a location update is received for a first user. One or more second users that have been location-synchronized to the first user are then identified. A location reported by the location update for the first user is recorded, or stored, as a current location of the first user and a current location of each of the one or more second users that have been location-synchronized to the first user. A location-based service, such as a social location-based service, may then be provided based on the current locations of the first and the one or more second users.
- Those skilled in the art will appreciate the scope of the present disclosure and realize additional aspects thereof after reading the following detailed description of the preferred embodiments in association with the accompanying drawing figures.
- The accompanying drawing figures incorporated in and forming a part of this specification illustrate several aspects of the disclosure, and together with the description serve to explain the principles of the disclosure.
-
FIG. 1 illustrates an exemplary system in which a location update for a user is utilized as a location update for a corresponding location-synchronized group of users according to one embodiment of the present disclosure; -
FIG. 2 illustrates the operation of the system ofFIG. 1 according to one embodiment of the present disclosure; -
FIG. 3 illustrates the operation of a location update server of the Social Location-Based Service (SLBS) ofFIG. 1 to receive and process a location update according to one embodiment of the present disclosure; -
FIG. 4 illustrates the operation of the location update server of the SLBS ofFIG. 1 to create and maintain location-synchronized groups of users according to one embodiment of the present disclosure; -
FIG. 5 illustrates the operation of the location update server of the SLBS ofFIG. 1 to create and maintain location-synchronized groups of users according to another embodiment of the present disclosure; -
FIG. 6 illustrates the operation of the location update server of the SLBS ofFIG. 1 to create and maintain location-synchronized groups of users according to yet another embodiment of the present disclosure; -
FIG. 7 illustrates the operation of the location update server of the SLBS ofFIG. 1 to de-synchronize users in location-synchronized groups of users according to one embodiment of the present disclosure; -
FIG. 8 illustrates the operation of the location update server of the SLBS ofFIG. 1 to de-synchronize users in location-synchronized groups of users according to another embodiment of the present disclosure; -
FIG. 9 illustrates the operation of the location update server of the SLBS ofFIG. 1 to de-synchronize users in location-synchronized groups of users according to yet another embodiment of the present disclosure; -
FIG. 10 is a block diagram of a computer server that hosts the SLBS ofFIG. 1 according to one embodiment of the present disclosure; and -
FIG. 11 is a block diagram of one of the mobile devices in the system ofFIG. 1 according to one embodiment of the present disclosure. - The embodiments set forth below represent the necessary information to enable those skilled in the art to practice the embodiments and illustrate the best mode of practicing the embodiments. Upon reading the following description in light of the accompanying drawing figures, those skilled in the art will understand the concepts of the disclosure and will recognize applications of these concepts not particularly addressed herein. It should be understood that these concepts and applications fall within the scope of the disclosure and the accompanying claims.
-
FIG. 1 illustrates asystem 10 in which a location update for a user is utilized as a location update for a corresponding location-synchronized group of users according to one embodiment of the present disclosure. As illustrated, thesystem 10 includes a Social Location-Based Service (SLBS) 12 and a number of mobile devices 14-1 through 14-N having associated users 16-1 through 16-N connected by anetwork 18. The mobile devices 14-1 through 14-N are more generally referred to herein collectively asmobile devices 14 and individually asmobile device 14. Similarly, the users 16-1 through 16-N are more generally referred to herein collectively asusers 16 and individually asuser 16. Thenetwork 18 may be any type of Wide Area Network (WAN) or Local Area Network (LAN), or any combination thereof. For example, in one preferred embodiment, thenetwork 18 is a distributed public network, such as the Internet, where themobile devices 16 are connected to thenetwork 18 via local wireless connections (e.g., IEEE 802.11x connections through corresponding IEEE 802.11x base stations or access points) or mobile communications connections. Mobile communications connections may be, for example, 3 G wireless connections such as, for example, Global System for Mobile communications (GSM) or Code Division Multiple Access (CDMA) wireless connections, 4 G wireless connections such as, for example, Wideband CDMA (W-CDMA) or Long Term Evolution (LTE) wireless connections, or the like. - The SLBS 12 is generally any type of social location-based service and is preferably implemented in software hosted by a computer server or a number of computer servers operating in a collaborative manner for purposes of load sharing and/or redundancy. As an example, the SLBS 12 may be a Mobile Aggregate Profile (MAP) service such as that described in U.S. patent application Ser. No. 12/645,532, entitled FORMING CROWDS AND PROVIDING ACCESS TO CROWD DATA IN A MOBILE ENVIRONMENT, which was filed Dec. 23, 2009; U.S. patent application Ser. No. 12/645,539, entitled ANONYMOUS CROWD TRACKING, which was filed Dec. 23, 2009; U.S. patent application Ser. No. 12/645,535, entitled MAINTAINING A HISTORICAL RECORD OF ANONYMIZED USER PROFILE DATA BY LOCATION FOR USERS IN A MOBILE ENVIRONMENT, which was filed Dec. 23, 2009; U.S. patent application Ser. No. 12/645,546, entitled CROWD FORMATION FOR MOBILE DEVICE USERS, which was filed Dec. 23, 2009; U.S. patent application Ser. No. 12/645,556, entitled SERVING A REQUEST FOR DATA FROM A HISTORICAL RECORD OF ANONYMIZED USER PROFILE DATA IN A MOBILE ENVIRONMENT, which was filed Dec. 23, 2009; U.S. patent application Ser. No. 12/645,560, entitled HANDLING CROWD REQUESTS FOR LARGE GEOGRAPHIC AREAS, which was filed Dec. 23, 2009; and U.S. patent application Ser. No. 12/645,544, entitled MODIFYING A USER'S CONTRIBUTION TO AN AGGREGATE PROFILE BASED ON TIME BETWEEN LOCATION UPDATES AND EXTERNAL EVENTS, which was filed Dec. 23, 2009; all of which are hereby incorporated herein by reference in their entireties. As described in the aforementioned published U.S. patent applications, the MAP service operates to, among other things, create and maintain a historical record of anonymized user profile data by geographic location and to create and track crowds of users all based on location updates received for users of the MAP service. Note, however, that the SLBS 12 is not limited to the MAP service. For example, the SLBS 12 may alternatively be a check-in service similar to the FourSquare™ check-in service or the Gowalla® check-in service. Other types of social location-based services will be apparent to one of ordinary skill in the art upon reading this disclosure and are to be considered within the scope of the present disclosure.
- As illustrated, the SLBS 12 includes a
location update server 20 and a user records repository 22. Thelocation update server 20 is preferably implemented in software and generally operates to receive location updates, process the location updates, and update user records of theusers 16 stored in the user records repository 22. As described below in detail, location-synchronized groups of users are created either manually by theusers 16 or programmatically by thelocation update server 20. The location-synchronized groups of users are recorded in the user records of theusers 16 stored in the user records repository 22. - The user records repository 22 generally includes a user record for each of the
users 16, where each of theusers 16 is a registered user of the SLBS 12. The user record of each of theusers 16 includes a current location of theuser 16. In addition, the user record of theuser 16 includes a list of other users that are location-synchronized to theuser 16 and/or an identifier of anotheruser 16 to which theuser 16 is location-synchronized. Note that, in one embodiment, the other users that are location-synchronized to theuser 16 may all beusers 16 of theSLBS 12. However, in another embodiment, the other users that are location-synchronized to theuser 16 may include one or more of theusers 16 of theSLBS 12 and/or users (e.g.,user 32, discussed below) that are not registered with theSLBS 12. In some embodiments, the user record of theuser 16 may also include a historical record of location updates received for theuser 16 that includes one or more previous locations of theuser 16 as defined by one or more previous location updates for theuser 16. Still further, in some embodiments, the user record of theuser 16 may include one or more user settings defined by theuser 16 for use by thelocation update server 20 in programmatically location-synchronizing theuser 16 toother users 16, programmatically location-synchronizingother users 16 to theuser 16, programmatically de-synchronizing theuser 16 fromother users 16, and/or programmatically de-synchronizingother users 16 from theuser 16. - In some embodiments, the user records repository 22 may also store user records for each of a number of non-registered users of the
SLBS 12 such as, for example, user 32 (discussed below). For each non-registered user, the user record of that non-registered user includes a current location of the non-registered user. Further, the current location of the non-registered user is the current location of theuser 16 to which the non-registered user has been location-synchronized. The user record of the non-registered user may also include user profile data, which may be provided by the non-registered user or obtained from a third-party source (e.g., the non-registered user's Facebook® profile). - The
mobile devices 14 may be mobile smart phones, portable media player devices, mobile gaming devices, mobile computers (e.g., laptop computers), or the like. Some exemplary mobile devices that may be programmed or otherwise configured to operate as themobile devices 14 are the Apple® iPhone®, the Palm Pre®, the Samsung Rogue™, the Blackberry Storm™, the Motorola DROID or similar phone running Google's Android™ Operating System, an Apple® iPad®, and the Apple® iPod Touch® device. However, this list of exemplary mobile devices is not exhaustive and is not intended to limit the scope of the present disclosure. - The mobile devices 14-1 through 14-N include SLBS clients 24-1 through 24-N (generally referred to herein collectively as
SLBS clients 24 or individually as SLBS client 24) which include corresponding location update clients 26-1 through 26-N (generally referred to herein collectively aslocation update clients 26 and individually as location update client 26). The mobile devices 14-1 through 14-N also include location functions 28-1 through 28-N (generally referred to herein collectively as location functions 28 and individually as location function 28). - The
SLBS clients 24 are preferably implemented in software and generally operate to provide an interface by which themobile devices 14 and theusers 16 interact with theSLBS 12. Thelocation update clients 26 generally operate to obtain current locations of themobile devices 14, and thus theusers 16, from the location functions 28 and send corresponding location updates to thelocation update server 20 of theSLBS 12. Thelocation update clients 26 may send the location updates periodically, in response to triggering events such as a change in the location of theusers 16, or in response to a request from thelocation update server 20. As discussed below, the location updates may be for geographic locations at which theusers 16 are located (e.g., latitude and longitude, street address, or the like) or for “check-in” locations. “Check-in” locations are Points of Interest (POIs) at or near the current geographic locations of theusers 16 that have been selected by theusers 16, or programmatically selected on behalf of theusers 16, for “check-in” in a manner similar to that done for check-in services such as, for example, the FourSquare™ and Gowalla® check-in services. - For each
mobile device 14, thelocation function 28 of themobile device 14 may be implemented in hardware, software, or a combination thereof. In general, thelocation function 28 of themobile device 14 operates to determine or otherwise obtain the geographic location of themobile device 14. For example, thelocation function 28 of themobile device 14 may be, or include, a Global Positioning System (GPS) receiver. In addition or alternatively, thelocation function 28 may include hardware and/or software that enables improved location tracking in indoor environments such as, for example, shopping malls. For example, thelocation function 28 may be part of, or compatible with, the InvisiTrack Location System provided by InvisiTrack and described in U.S. Pat. No. 7,423,580 entitled “Method and System of Three-Dimensional Positional Finding” which issued on Sep. 9, 2008, U.S. Pat. No. 7,787,886 entitled “System and Method for Locating a Target using RFID” which issued on Aug. 31, 2010, and U.S. Patent Application Publication No. 2007/0075898 entitled “Method and System for Positional Finding Using RF, Continuous and/or Combined Movement” which published on Apr. 5, 2007, all of which are hereby incorporated herein by reference for their teachings regarding location tracking. - In this embodiment, the
system 10 also includes aguest device 30 having an associateduser 32. Theguest device 30 may be a mobile device similar to themobile devices 14 or other computing device (e.g., a personal computer). Theuser 32 is enabled to access theSLBS 12 via theguest device 30 to, for example, request to be location-synchronized with a select one of theusers 16. Notably, theuser 32 is not a registered user of theSLBS 12. Further, while only oneguest device 30 and associateduser 32 are illustrated, thesystem 10 may includemultiple guest devices 30 and associatedusers 32. -
FIG. 2 illustrates the operation of thesystem 10 ofFIG. 1 according to one embodiment of the present disclosure. As illustrated, themobile device 14, and more specifically thelocation update client 26 of theSLBS client 24 of themobile device 14, sends a location update to theSLBS 12 for theuser 16 of the mobile device 14 (step 100). The location update includes a current location of theuser 16. In one embodiment, the current location of theuser 16 is the current geographic location of themobile device 14, and thus theuser 16, as determined by thelocation function 28 of themobile device 14. In this case, the current location of theuser 16 may be expressed as any data that defines the location of theuser 16 in 2-dimensional or 3-dimensional space. For example, in one embodiment, the current location of theuser 16 may be expressed as a latitude and longitude coordinate pair and, in some embodiments, an altitude. As another example, the current location of theuser 16 may be expressed as a street address. In another embodiment, the current location of theuser 16 may be a “check-in” location selected by theuser 16 or programmatically selected by theSLBS client 24 on behalf of theuser 16. More specifically, theSLBS client 24 may interact with theSLBS 12 to obtain a list of one or more POIs at or near the current geographical location of the user 16 (e.g., street address, latitude and longitude, or the like) as determined by thelocation function 28. In one embodiment, theSLBS client 24 may then present the list of POIs to theuser 16, and theuser 16 may select a POI for which to “check-in.” The location update for theuser 16 may then be expressed as data that identifies the POI selected by theuser 16 for check-in. - Next, the
location update server 20 of theSLBS 12 identifies one or more other users that are location-synchronized to the user 16 (step 102). The other users that are location-synchronized to theuser 16 may include only other ones of theusers 16 of theSLBS 12, only non-registered users of theSLBS 12 such as theuser 32, or one or more of theother users 16 of theSLBS 12 and non-registered users of the SLBS such as theuser 32 depending on the particular implementation. Several embodiments of a process by which other users are location-synchronized to theuser 16 are described below in detail. Thelocation update server 20 of theSLBS 12 then records the location of theuser 16 of themobile device 14 reported in the location update as the current location of theuser 16 of themobile device 14 and the current location(s) of the other user(s) that are location-synchronized to the user 16 (step 104). The location reported in the location update is recorded as the current locations of theuser 16 and the other user(s) that are location-synchronized to theuser 16 by storing the location as the current locations in the user records of thoseusers 16. TheSLBS 12 provides a desired social location-based service to theusers 16 of theSLBS 12 using the current locations of theusers 16 and, in some embodiments, the current locations of non-registered users (step 106). -
FIG. 3 illustrates the operation of thelocation update server 20 of theSLBS 12 ofFIG. 1 to receive and process location updates according to one embodiment of the present disclosure. As illustrated, thelocation update server 20 receives a location update for one of the users 16 (step 200). Thelocation update server 20 then determines whether any users are location-synchronized to the user 16 (step 202). If not, the process proceeds to step 206. If so, then thelocation update server 20 records, or stores, the location reported by the location update as the current location of the user(s) that are location-synchronized to the user 16 (step 204). In addition, thelocation update server 20 records, or stores, the location reported by the location update as the current location of theuser 16 for which the location update was received (step 206). The process then returns to step 200 and is repeated for the next received location update from one of theusers 16. -
FIG. 4 illustrates the operation of thelocation update server 20 of theSLBS 12 ofFIG. 1 to create and maintain location-synchronized groups of users according to one embodiment of the present disclosure. In this embodiment, requesting users manually requestother users 16 to which to be location-synchronized. More specifically, thelocation update server 20 of theSLBS 12 first receives a location-synchronization request from a requesting user (step 300). The requesting user may be one of theusers 16 of theSLBS 12. In some embodiments, the requesting user may alternatively be a non-registered user such as, for example, theuser 32 of theguest device 30. The location-synchronization request is a request from the requesting user to be location-synchronized to a select one of theusers 16 of the SLBS 12 (referred to herein as the “select user”). The select user is identified in the location-synchronization request. Further, the manner in which the select user is selected by the requesting user may vary depending on the particular implementation. For example, the requesting user may select the select user by entering an identifier (ID) of the select user for theSLBS 12, entering an e-mail address that may be utilized by theSLBS 12 to identify one of theusers 16 as the select user, selecting the select user from a list of users such as, for example, a contact list of the requesting user maintained by theSLBS 12, or the like. - In some embodiments, the location-synchronization request may also include one or more settings configured by the requesting user that define when the requesting user is to be de-synchronized from the select user (i.e., define when the requesting user is to no longer be location-synchronized to the select user). The settings may include one or more time-based settings. For example, the settings may include a setting that defines an amount of time that the requesting user is to be location-synchronized to the select user or an end-time that defines the time at which the requesting user is to be de-synchronized from the select user. It should be noted that while the settings may be included in the location-synchronization request, the settings may alternatively be predefined by the requesting user and included in the user record of the requesting user.
- In response to receiving the location-synchronization request, the
location update server 20 of theSLBS 12 records, or stores, the requesting user as a location-synchronized user of the select user (step 302). More specifically, in one embodiment, thelocation update server 20 adds the requesting user to a list of location-synchronized users of the select user maintained in the user record of the select user. In another embodiment, thelocation update server 20 adds the select user as the user to which the requesting user is location-synchronized, which may be maintained in the user record of the requesting user. From this time and until the requesting user and the select user are de-synchronized, location updates for the select user will also be recorded as location updates for the requesting user. -
FIG. 5 illustrates the operation of thelocation update server 20 of theSLBS 12 ofFIG. 1 to create and maintain location-synchronized groups of users according to another embodiment of the present disclosure. In this embodiment, theusers 16 manually request other users that are to be location-synchronized to theusers 16. More specifically, thelocation update server 20 of theSLBS 12 first receives a location-synchronization request from a requesting user, which in this embodiment is one of theusers 16 of the SLBS 12 (step 400). In this embodiment, the location-synchronization request is a request from the requesting user for a select user, or possibly multiple select users, to be location-synchronized to the requesting user. The select user is identified in the location-synchronization request. Depending on the embodiment, the select user may be a select one of theusers 16 of theSLBS 12, a non-registered user such as but not limited to theuser 32 of theguest device 30, or either a select one of theusers 16 of theSLBS 12 or a non-registered user. Further, the manner in which the select user is selected by the requesting user may vary depending on the particular implementation. For example, the requesting user may select the select user by entering an ID of the select user for theSLBS 12, entering an e-mail address that may be utilized by theSLBS 12 to identify the select user, selecting the select user from a list of users such as, for example, a contact list of the requesting user, or the like. - In some embodiments, the location-synchronization request may also include one or more settings configured by the requesting user that define when the select user is to be de-synchronized from the requesting user (i.e., define when the select user is to no longer be location-synchronized to the requesting user). The settings may include one or more time-based settings. For example, the settings may include a setting that defines an amount of time that the select user is to be location-synchronized to the requesting user or an end-time that defines the time at which the select user is to be de-synchronized from the requesting user. It should be noted that while the settings may be included in the location-synchronization request, the settings may alternatively be predefined by the requesting user and included in the user record of the requesting user.
- In response to receiving the location-synchronization request, the
location update server 20 of theSLBS 12 records, or stores, the select user as a location-synchronized user of the requesting user (step 402). More specifically, in one embodiment, thelocation update server 20 adds the select user to a list of location-synchronized users of the requesting user maintained in the user record of the requesting user. In another embodiment, thelocation update server 20 adds the requesting user as the user to which the select user is location-synchronized, which may be maintained in the user record of the select user. From this time and until the requesting user and the select user are de-synchronized, location updates for the requesting user will also be recorded as location updates for the select user. -
FIG. 6 illustrates the operation of thelocation update server 20 of theSLBS 12 ofFIG. 1 to create and maintain location-synchronized groups of users according to yet another embodiment of the present disclosure. In this embodiment, thelocation update server 20 programmatically selects users to be location-synchronized. As illustrated, thelocation update server 20 first determines whether a particular user pair should be location-synchronized (step 500). More specifically, thelocation update server 20 determines whether a first user in the user pair should be location-synchronized to a second user in the user pair. The determination may be made based on user settings of one or both of the users in the user pair, one or more system-defined rules, the current location of one or both of the users in the user pair, historical locations of one or both of the users in the user pair, information obtained from one or more third-party sources that is indicative of spatial proximity of the first and second user at the current time or historically, or a combination thereof. The third-party source may include, for example, the Twitter® micro-blogging and social networking service where current and/or historical tweets from the two users that are tagged with the geographic locations of the users in the user pair at the time of sending the tweets are utilized to determine the current and/or historical spatial proximity of the two users. A text analysis of the tweet may additionally or alternatively be analyzed to determine users that the sending user is near at that time. As an example, user settings of one or both of the users in the user pair may indicate that the first user is to be location-synchronized to the second user if a location update has not been received from the first user within a defined amount of time (e.g., 30 minutes) and the two users have been located together for at least a defined amount of time (e.g., past 2 hours). As another example, user settings of one or both of the users in the user pair may indicate that the first user is to be location-synchronized to the second user if the first user has historically been located at the same location as the second user. As a more specific example, if the current time is 7 pm on a Friday evening, the user settings of one or both of the users may indicate that the first user is to be location-synchronized to the second user if the first user has been located at the same location as the second user on each of the last three Friday evenings from 7 pm to 10 pm. Note that while the examples above are based on user settings, system-defined rules may additionally or alternatively be used. - If the
location update server 20 determines that the first user is to be location-synchronized to the second user, then thelocation update server 20 records the first user as a location-synchronized user of the second user (step 502). In some embodiments, a weight may be assigned to the first user as a location-synchronized user of the second user that reflects a degree of certainty, or sureness, that the first user should be location-synchronized to the second user. This weighting may subsequently be adjusted by users, such as but not limited to the first user or the second user, or other entities. Such feedback may be utilized by thelocation update server 20 to improve its methods of determining when it is appropriate to location-synchronize these particular users and/or users in the system in general based on, for example, a statistical analysis of the feedback. In this example, the process ends, at least with respect to this particular user pair. It should be noted that the process ofFIG. 6 may be performed in response to a triggering event and may also be repeated for additional user pairs. For example, the process ofFIG. 6 may be performed in response to receiving a location update for the second user and may be repeated for a number of user pairs that each include the second user (e.g., N−1 user pairs that each include the second user and a different one of the users 16). As a more specific example, the process ofFIG. 6 may be performed betweensteps 200 and 202 of the process ofFIG. 3 such that any additional users that should be location-synchronized to the second user are identified before the location reported in the location update for the second user is recorded as the current locations of theother users 16 that are location-synchronized to the second user. -
FIG. 7 illustrates the operation of thelocation update server 20 of theSLBS 12 ofFIG. 1 to de-synchronize users in location-synchronized groups of users according to one embodiment of the present disclosure. In this embodiment, requesting users manually requestusers 16 from which to be de-synchronized. More specifically, thelocation update server 20 of theSLBS 12 first receives a de-synchronization request from a requesting user (step 600). In one embodiment, the requesting user is one of theusers 16 of theSLBS 12. In another embodiment, the requesting user is a non-registered user of theSLBS 12. In yet another embodiment, the requesting user is either one of theusers 16 of theSLBS 12 or a non-registered user of theSLBS 12. The de-synchronization request is a request from the requesting user to be de-synchronized, or removed, as a location-synchronized user of a select user. The select user is a select one of theusers 16 and is identified in the de-synchronization request. Further, the manner in which the select user is selected by the requesting user may vary depending on the particular implementation. For example, the requesting user may select the select user by entering an ID of the select user for theSLBS 12, entering an e-mail address that may be utilized by theSLBS 12 to identify one of theusers 16 as the select user, selecting the select user from a list of users such as, for example, a contact list of the requesting user maintained by theSLBS 12, or the like. - In response to receiving the de-synchronization request, the
location update server 20 of theSLBS 12 removes the requesting user as a location-synchronized user of the select user (step 602). More specifically, in one embodiment, thelocation update server 20 removes the requesting user from a list of location-synchronized users of the select user maintained in the user record of the select user. In another embodiment, thelocation update server 20 removes the select user as the user to which the requesting user is location-synchronized as maintained in the user record of the requesting user. -
FIG. 8 illustrates the operation of thelocation update server 20 of theSLBS 12 ofFIG. 1 to de-synchronize users in location-synchronized groups of users according to another embodiment of the present disclosure. In this embodiment, requesting users manually requestusers 16 that are to be de-synchronized from the requesting user. More specifically, thelocation update server 20 of theSLBS 12 first receives a de-synchronization request from a requesting user, which in this embodiment is one of theusers 16 of the SLBS 12 (step 700). In this embodiment, the de-synchronization request is a request from the requesting user for a select user, or possibly multiple select users, to be de-synchronized from the requesting user. The select user is identified in the de-synchronization request and may be another one of theusers 16 of theSLBS 12 or a non-registered user depending on the particular implementation. Further, the manner in which the select user is selected by the requesting user may vary depending on the particular implementation. For example, the requesting user may select the select user by entering an ID of the select user for theSLBS 12, entering an e-mail address that may be utilized by theSLBS 12 to identify the select user, selecting the select user from a list of users such as, for example, a contact list of the requesting user, or the like. - In response to receiving the de-synchronization request, the
location update server 20 of theSLBS 12 removes the select user as a location-synchronized user of the requesting user (step 702). More specifically, in one embodiment, thelocation update server 20 removes the select user from a list of location-synchronized users of the requesting user maintained in the user record of the requesting user. In another embodiment, thelocation update server 20 removes the requesting user as the user to which the select user is location-synchronized as maintained in the user record of the select user. -
FIG. 9 illustrates the operation of thelocation update server 20 of theSLBS 12 ofFIG. 1 to de-synchronize users in location-synchronized groups of users according to yet another embodiment of the present disclosure. In this embodiment, thelocation update server 20 programmatically de-synchronizes users. As illustrated, thelocation update server 20 first determines whether a particular user pair should be de-synchronized (step 800). More specifically, thelocation update server 20 determines whether a first user in the user pair should be de-synchronized from second user in the user pair. The determination may be made based on user settings of one or both of the users in the user pair, one or more system-defined rules, the current location of one or both of the users in the user pair, historical locations of one or both of the users in the user pair, information obtained from one or more third-party sources that is indicative of spatial proximity of the first and second users, or a combination thereof. For example, user settings of one or both of the users in the user pair may indicate that the first user is to be de-synchronized from the second user if a location update is received from the first user and the reported location of the first user is different from (e.g., more than a pre-defined distance from) the current location of the second user. Note that while the examples above are based on user settings, system-defined rules may additionally or alternatively be used. As another example, the user settings may indicate that the first user is to be de-synchronized from the second user once the first user is no longer spatially proximate to the second user (e.g., not within a predefined distance from the second user, not at the same street address as the second user, or the like). - If the
location update server 20 determines that the first user is to be de-synchronized from the second user, then thelocation update server 20 de-synchronizes the users by removing the first user as a location-synchronized user of the second user (step 802). In this example, the process ends, at least with respect to this particular user pair. It should be noted that the process ofFIG. 9 may be performed in response to a triggering event and may also be repeated for additional user pairs. For example, the process ofFIG. 9 may be performed in response to receiving a location update for the second user and may be repeated for a number of location-synchronized user pairs that each include the second user and a different user that is location-synchronized to the second user. As a more specific example, the process ofFIG. 9 may be performed betweensteps 200 and 202 of the process ofFIG. 3 such that any users that should be de-synchronized from the second user are identified and removed before the location reported in the location update for the second user is recorded as the current locations of the location-synchronized users of the second user. - While
FIGS. 7 through 9 illustrate three exemplary processes by which users are de-synchronized, other processes may be used. For example, in one embodiment, when users are location-synchronized, de-synchronization of those users is scheduled for a defined point in time in the future. For instance, a synchronization request from a requesting user may define an amount of time that the users are to be location-synchronized or define a specific time at which de-synchronization is to occur. In this case, thelocation update server 20 may schedule de-synchronization at the appropriate time and perform de-synchronization at that time. In a similar manner, when users are programmatically location-synchronized, the user settings of one or both of the users or system-defined settings may define an amount of time that the users are to be synchronized. Thelocation update server 20 may then schedule de-synchronization at the appropriate time and then de-synchronize the users at that time. -
FIG. 10 is a block diagram of acomputer server 36 hosting theSLBS 12 according to one embodiment of the present disclosure. As illustrated, thecomputer server 36 includes acontroller 38 connected tomemory 40, one or moresecondary storage devices 42, and acommunication interface 44 by abus 46 or similar mechanism. Thecontroller 38 is a microprocessor, digital Application Specific Integrated Circuit (ASIC), Field Programmable Gate Array (FPGA), or similar hardware component. In this embodiment, thecontroller 38 is a microprocessor, and theSLBS 12 is implemented in software and stored in thememory 40 for execution by thecontroller 38. Further, the user records repository 22 may be stored in thememory 40 or the one or moresecondary storage devices 42. Thesecondary storage devices 42 are digital data storage devices such as, for example, one or more hard disk drives. Thecommunication interface 44 is a wired or wireless communication interface that communicatively couples thecomputer server 36 to the network 18 (FIG. 1 ). For example, thecommunication interface 44 may be an Ethernet interface, local wireless interface such as a wireless interface operating according to one of the suite of IEEE 802.11 standards, or the like. -
FIG. 11 is a block diagram of one of themobile devices 14 according to one embodiment of the present disclosure. This discussion is equally applicable to the othermobile devices 14. As illustrated, themobile device 14 includes acontroller 48 connected tomemory 50, acommunication interface 52, one or more user interface components 54, and thelocation function 28 by abus 56 or similar mechanism. Thecontroller 48 is a microprocessor, digital ASIC, FPGA, or similar hardware component. In this embodiment, thecontroller 48 is a microprocessor, and theSLBS client 24 is implemented in software and stored in thememory 50 for execution by thecontroller 48. In this embodiment, thelocation function 28 is a hardware component such as, for example, a GPS receiver. Thecommunication interface 52 is a wireless communication interface that communicatively couples themobile device 14 to the network 18 (FIG. 1 ). For example, thecommunication interface 52 may be a local wireless interface such as a wireless interface operating according to one of the suite of IEEE 802.11 standards, a mobile communications interface such as a cellular telecommunications interface (e.g., 3 G telecommunications interface such as a GSM interface or the like, or a 4 G telecommunications interface such as a LTE interface or the like). The one or more user interface components 54 include, for example, a touchscreen, a display, one or more user input components (e.g., a keypad), a speaker, or the like, or any combination thereof. - The following use case is provided to illustrate some, but not necessarily all, of the embodiments described above. This use case is provided for illustrative purposes only and is not intended to limit the scope of the present disclosure in any manner whatsoever.
-
- 1. Jack is planning a night on the town with his girlfriend, Sarah, and his friends Sam, Jessica, Frank, and Charlene. Sarah, Jessica, Sam, and Jack are all
users 16 of theSLBS 12. Since Sarah and Jessica are dressed up and did not want to have to bother with purses and Sam did not want to potentially lose hismobile device 14, they have all opted to leave theirmobile devices 14 in Jack's car and let Jack represent them to theSLBS 12. - 2. Before they leave for downtown, Sarah, Jessica, and Sam all log into the
SLBS 12 via theirmobile devices 14 and request to be synchronized with Jack for the night. Jack logs into theSLBS 12 and accepts their requests and requests that theSLBS 12 also synchronize two more friends, namely Frank and Charlene, to him for the night. - 3. Using the
SLBS 12, Jack peruses crowds downtown, particularly paying attention to crowds at a few potentially desirable POIs. Jack eventually chooses one POI and has theSLBS 12 give him directions to that POI. - 4. The
SLBS 12 sends an alert that includes information about Jack and his group to advanced users (e.g., owners or managers) of the POIs in which he has shown an interest. TheSLBS 12 also gives the advanced user of the POI chosen by Jack an estimate for time of arrival. - 5. The advanced users of the POIs in which Jack has expressed an interest may send some incentives to Jack and his group of synchronized users in hopes of attracting them.
- 6. Jack and his group end up going to the chosen POI, and they are able to get a dollar off admission each for going there.
- 7. They run into their friend Randolph, who is also a
user 16 of theSBLS 12. Randolph decides to hang with Jack and his group for the evening. - 8. As the night goes on and Jack updates his location, the
SLBS 12 automatically updates the locations of all of the other users that are synchronized to Jack. - 9. After Randolph updates his location at one of the same locations as Jack, the
SLBS 12 determines that Randolph has been part of Jack, Sarah, Sam, and Jessica's groups in the past. In response, theSLBS 12 programmatically, or automatically, synchronizes Randolph to Jack. Since theSLBS 12 is not certain that Randolph should be synchronized with Jack, location updates received from Jack are also stored for Randolph but with a lower weighting or sureness value. - 10. After the
SLBS 12 finds a tweet by Randolph that theSLBS 12 determines means he is hanging out with Jack's group, theSLBS 12 increases the sureness value of location updates from Jack that are stored as Randolph's location. - 11. Jessica had made plans to meet up with some other friends later on in the evening, so she takes her
mobile device 14 from Jack's car and heads out to hang out with her other friends. TheSLBS 12 sees that Jessica updates her location at least a predefined threshold distance from Jack, so it automatically de-synchronizes her from Jack. - 12. Finally, Jack's group heads their separate ways for the evening. After a specified amount of time has expired, the
SLBS 12 automatically de-synchronizes the rest of the group from Jack.
- 1. Jack is planning a night on the town with his girlfriend, Sarah, and his friends Sam, Jessica, Frank, and Charlene. Sarah, Jessica, Sam, and Jack are all
- Those skilled in the art will recognize improvements and modifications to the preferred embodiments of the present disclosure. All such improvements and modifications are considered within the scope of the concepts disclosed herein and the claims that follow.
Claims (26)
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US13/027,756 US20120066303A1 (en) | 2010-03-03 | 2011-02-15 | Synchronized group location updates |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US30990310P | 2010-03-03 | 2010-03-03 | |
US13/027,756 US20120066303A1 (en) | 2010-03-03 | 2011-02-15 | Synchronized group location updates |
Publications (1)
Publication Number | Publication Date |
---|---|
US20120066303A1 true US20120066303A1 (en) | 2012-03-15 |
Family
ID=45807686
Family Applications (8)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US13/027,756 Abandoned US20120066303A1 (en) | 2010-03-03 | 2011-02-15 | Synchronized group location updates |
US13/032,744 Abandoned US20120066614A1 (en) | 2010-03-03 | 2011-02-23 | Methods and systems for following crowds |
US13/037,546 Active 2032-02-24 US9203793B2 (en) | 2010-03-03 | 2011-03-01 | Ad-hoc micro-blogging groups |
US13/037,520 Expired - Fee Related US8898288B2 (en) | 2010-03-03 | 2011-03-01 | Status update propagation based on crowd or POI similarity |
US13/039,356 Expired - Fee Related US8566309B2 (en) | 2010-03-03 | 2011-03-03 | Monitoring hashtags in micro-blog posts to provide one or more crowd-based features |
US14/028,866 Expired - Fee Related US9407590B2 (en) | 2010-03-03 | 2013-09-17 | Monitoring hashtags in micro-blog posts to provide one or more crowd-based features |
US14/546,580 Abandoned US20150074214A1 (en) | 2010-03-03 | 2014-11-18 | Status Update Propagation Based On Crowd Or POI Similarity |
US14/954,084 Active US9407598B2 (en) | 2010-03-03 | 2015-11-30 | Ad-hoc micro-blogging groups |
Family Applications After (7)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US13/032,744 Abandoned US20120066614A1 (en) | 2010-03-03 | 2011-02-23 | Methods and systems for following crowds |
US13/037,546 Active 2032-02-24 US9203793B2 (en) | 2010-03-03 | 2011-03-01 | Ad-hoc micro-blogging groups |
US13/037,520 Expired - Fee Related US8898288B2 (en) | 2010-03-03 | 2011-03-01 | Status update propagation based on crowd or POI similarity |
US13/039,356 Expired - Fee Related US8566309B2 (en) | 2010-03-03 | 2011-03-03 | Monitoring hashtags in micro-blog posts to provide one or more crowd-based features |
US14/028,866 Expired - Fee Related US9407590B2 (en) | 2010-03-03 | 2013-09-17 | Monitoring hashtags in micro-blog posts to provide one or more crowd-based features |
US14/546,580 Abandoned US20150074214A1 (en) | 2010-03-03 | 2014-11-18 | Status Update Propagation Based On Crowd Or POI Similarity |
US14/954,084 Active US9407598B2 (en) | 2010-03-03 | 2015-11-30 | Ad-hoc micro-blogging groups |
Country Status (1)
Country | Link |
---|---|
US (8) | US20120066303A1 (en) |
Cited By (8)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20110217965A1 (en) * | 2010-03-03 | 2011-09-08 | Htc Corporation | Method, system and computer-readable medium for synchronizing spot information |
US20120115473A1 (en) * | 2010-11-04 | 2012-05-10 | Samsung Electronics Co., Ltd. | Method and apparatus for supporting location information in machine to machine communication system |
US20120302162A1 (en) * | 2011-05-23 | 2012-11-29 | Chao-Feng Chueh | Method of Performing a Data Transaction Between a Portable Storage Device and an Electronic Device |
US20130262706A1 (en) * | 2012-04-02 | 2013-10-03 | F-Secure Corporation | Data Syncronisation |
US20150219458A1 (en) * | 2014-01-31 | 2015-08-06 | Aruba Networks Inc. | Navigating to a moving target |
CN106372557A (en) * | 2016-08-30 | 2017-02-01 | 李明 | Method, device and system for acquiring certificate card information |
US20170332343A1 (en) * | 2015-03-03 | 2017-11-16 | Facebook, Inc. | Techniques to manage client location detection |
US10096041B2 (en) | 2012-07-31 | 2018-10-09 | The Spoken Thought, Inc. | Method of advertising to a targeted buyer |
Families Citing this family (226)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8677377B2 (en) | 2005-09-08 | 2014-03-18 | Apple Inc. | Method and apparatus for building an intelligent automated assistant |
US9318108B2 (en) | 2010-01-18 | 2016-04-19 | Apple Inc. | Intelligent automated assistant |
US8977255B2 (en) | 2007-04-03 | 2015-03-10 | Apple Inc. | Method and system for operating a multi-function portable electronic device using voice-activation |
US10002189B2 (en) | 2007-12-20 | 2018-06-19 | Apple Inc. | Method and apparatus for searching using an active ontology |
US9330720B2 (en) | 2008-01-03 | 2016-05-03 | Apple Inc. | Methods and apparatus for altering audio output signals |
US8745056B1 (en) | 2008-03-31 | 2014-06-03 | Google Inc. | Spam detection for user-generated multimedia items based on concept clustering |
US8676704B2 (en) | 2008-03-13 | 2014-03-18 | Giftya Llc | Method for transferring funds |
US20100023341A1 (en) * | 2008-05-29 | 2010-01-28 | Reel Drinks Llc | Method for rule-based gift giving |
US20140249902A1 (en) | 2008-03-13 | 2014-09-04 | Giftya Llc | System and method for providing a customer survey |
US10489776B2 (en) | 2008-03-13 | 2019-11-26 | Giftya Llc | System and method for managing gift credits |
US20120150740A1 (en) * | 2010-12-14 | 2012-06-14 | Moneyhoney Llc | System and method for processing gift transfers via a social network |
US20140214666A1 (en) | 2008-03-13 | 2014-07-31 | Giftya Llc | System and method for managing gifts |
US10949833B2 (en) | 2008-03-13 | 2021-03-16 | Giftya Llc | Technologies for generating and displaying virtual and interactive egifts |
US20140207662A1 (en) | 2008-03-13 | 2014-07-24 | Giftya Llc | System and method for managing gifts |
US8996376B2 (en) | 2008-04-05 | 2015-03-31 | Apple Inc. | Intelligent text-to-speech conversion |
US9123022B2 (en) | 2008-05-28 | 2015-09-01 | Aptima, Inc. | Systems and methods for analyzing entity profiles |
US20100030549A1 (en) | 2008-07-31 | 2010-02-04 | Lee Michael M | Mobile device having human language translation capability with positional feedback |
US8676904B2 (en) | 2008-10-02 | 2014-03-18 | Apple Inc. | Electronic devices with voice command and contextual data processing capabilities |
US12235918B2 (en) * | 2009-02-02 | 2025-02-25 | Stripe, Inc. | System and method for filtering and creating points-of-interest |
US9602444B2 (en) * | 2009-05-28 | 2017-03-21 | Google Inc. | Participant suggestion system |
US10241752B2 (en) | 2011-09-30 | 2019-03-26 | Apple Inc. | Interface for a virtual digital assistant |
US20120309363A1 (en) | 2011-06-03 | 2012-12-06 | Apple Inc. | Triggering notifications associated with tasks items that represent tasks to perform |
US10276170B2 (en) | 2010-01-18 | 2019-04-30 | Apple Inc. | Intelligent automated assistant |
US8582801B2 (en) | 2010-02-08 | 2013-11-12 | Google Inc. | Assisting the authoring of posts to an asymmetric social network |
US9729352B1 (en) | 2010-02-08 | 2017-08-08 | Google Inc. | Assisting participation in a social network |
US8825759B1 (en) | 2010-02-08 | 2014-09-02 | Google Inc. | Recommending posts to non-subscribing users |
US8682667B2 (en) | 2010-02-25 | 2014-03-25 | Apple Inc. | User profiling for selecting user specific voice input processing information |
US20120066303A1 (en) | 2010-03-03 | 2012-03-15 | Waldeck Technology, Llc | Synchronized group location updates |
US20110231296A1 (en) * | 2010-03-16 | 2011-09-22 | UberMedia, Inc. | Systems and methods for interacting with messages, authors, and followers |
US9160806B1 (en) * | 2010-08-04 | 2015-10-13 | Open Invention Network, Llc | Method and apparatus of organizing and delivering data to intended recipients |
US20120054277A1 (en) * | 2010-08-31 | 2012-03-01 | Gedikian Steve S | Classification and status of users of networking and social activity systems |
US9275001B1 (en) | 2010-12-01 | 2016-03-01 | Google Inc. | Updating personal content streams based on feedback |
US8527597B2 (en) * | 2010-12-07 | 2013-09-03 | Google Inc. | Determining message prominence |
US20120150908A1 (en) * | 2010-12-09 | 2012-06-14 | Microsoft Corporation | Microblog-based customer support |
US9418160B2 (en) * | 2010-12-17 | 2016-08-16 | Microsoft Technology Licensing, Llc | Hash tag management in a microblogging infrastructure |
US20130339465A1 (en) * | 2011-02-21 | 2013-12-19 | Tencent Technology (Shenzhen) Company Limited | Method, apparatus and system for spreading a microblog list |
CN102685020B (en) * | 2011-03-09 | 2015-07-29 | 腾讯科技(北京)有限公司 | Microblog wall display method and system |
US9262612B2 (en) | 2011-03-21 | 2016-02-16 | Apple Inc. | Device access using voice authentication |
IL212511A (en) * | 2011-04-27 | 2016-03-31 | Verint Systems Ltd | System and method for keyword spotting using multiple character encoding schemes |
CN102790951B (en) * | 2011-05-20 | 2015-09-02 | 腾讯科技(深圳)有限公司 | A kind of data inputting method of mobile terminal, system and mobile terminal |
US10057736B2 (en) | 2011-06-03 | 2018-08-21 | Apple Inc. | Active transport based notifications |
JP5938170B2 (en) * | 2011-06-08 | 2016-06-22 | キヤノン株式会社 | Image processing apparatus, control method thereof, and program |
US8312056B1 (en) * | 2011-09-13 | 2012-11-13 | Xerox Corporation | Method and system for identifying a key influencer in social media utilizing topic modeling and social diffusion analysis |
US8839423B2 (en) * | 2011-09-20 | 2014-09-16 | Netqin Mobile, Inc. | Method and system for sharing mobile security information |
US9466086B2 (en) * | 2011-09-22 | 2016-10-11 | Genband Us Llc | Methods, systems, and computer readable media for affecting user associations in over the top (OTT) service platforms |
US11252690B2 (en) * | 2011-10-11 | 2022-02-15 | Match Group, Llc | System and method for matching using location information |
US8825515B1 (en) * | 2011-10-27 | 2014-09-02 | PulsePopuli, LLC | Sentiment collection and association system |
US10108927B2 (en) * | 2011-11-19 | 2018-10-23 | Oath Inc. | Method and system for enhancing user experience on a web content page by categorizing contacts and relevant posts |
US9058573B2 (en) * | 2011-11-21 | 2015-06-16 | Facebook, Inc. | Network traffic-analysis-based suggestion generation |
DE202012100620U1 (en) | 2011-11-22 | 2012-06-13 | Square, Inc. | System for processing cardless payment transactions |
US9690443B2 (en) * | 2011-11-29 | 2017-06-27 | Funny Or Die, Inc. | Computer-implemented systems and methods for facilitating a micro-blog post |
CN103297471B (en) * | 2012-03-01 | 2016-06-15 | 腾讯科技(深圳)有限公司 | A kind of method mentioning many people in microblogging and device |
US10134385B2 (en) | 2012-03-02 | 2018-11-20 | Apple Inc. | Systems and methods for name pronunciation |
US9082154B2 (en) * | 2012-03-15 | 2015-07-14 | Sap Se | Aggregation and semantic modeling of tagged content |
US9621504B2 (en) * | 2012-04-04 | 2017-04-11 | Intelmate Llc | Method and system for secure social networking on feature phones |
CN103379024B (en) * | 2012-04-26 | 2018-07-10 | 腾讯科技(深圳)有限公司 | Micro-blog information dissemination method and server |
US10417037B2 (en) | 2012-05-15 | 2019-09-17 | Apple Inc. | Systems and methods for integrating third party services with a digital assistant |
US9792285B2 (en) * | 2012-06-01 | 2017-10-17 | Excalibur Ip, Llc | Creating a content index using data on user actions |
US10019994B2 (en) * | 2012-06-08 | 2018-07-10 | Apple Inc. | Systems and methods for recognizing textual identifiers within a plurality of words |
US9721563B2 (en) | 2012-06-08 | 2017-08-01 | Apple Inc. | Name recognition system |
US20140006408A1 (en) * | 2012-06-29 | 2014-01-02 | Yahoo! Inc. | Identifying points of interest via social media |
US9226105B2 (en) * | 2012-08-09 | 2015-12-29 | Microsoft Technology Licensing, Llc | Mutual interest location matching |
JP5895777B2 (en) * | 2012-09-06 | 2016-03-30 | 富士ゼロックス株式会社 | Information classification program and information processing apparatus |
US9547647B2 (en) | 2012-09-19 | 2017-01-17 | Apple Inc. | Voice-based media searching |
CN103780590B (en) * | 2012-10-24 | 2016-08-03 | 腾讯科技(深圳)有限公司 | Automatically prompting user the registration method of microblogging, Apparatus and system |
US9047315B1 (en) * | 2012-12-05 | 2015-06-02 | Google Inc. | Geotagged hashtags |
IL224482B (en) | 2013-01-29 | 2018-08-30 | Verint Systems Ltd | System and method for keyword spotting using representative dictionary |
CN104969289B (en) | 2013-02-07 | 2021-05-28 | 苹果公司 | Voice triggers for digital assistants |
US9836461B1 (en) * | 2013-03-05 | 2017-12-05 | Twitter, Inc. | Search relevance using messages of a messaging platform |
US9081797B2 (en) * | 2013-03-06 | 2015-07-14 | Google Inc. | Systems and methods for associating microposts with geographic locations |
US10652394B2 (en) | 2013-03-14 | 2020-05-12 | Apple Inc. | System and method for processing voicemail |
WO2014159548A1 (en) * | 2013-03-14 | 2014-10-02 | Telcom Ventures, Llc | Verifying a user identity using location |
US20140279061A1 (en) * | 2013-03-15 | 2014-09-18 | Rapp Worldwide Inc. | Social Media Branding |
US10748529B1 (en) | 2013-03-15 | 2020-08-18 | Apple Inc. | Voice activated device for use with a voice-based digital assistant |
US9270847B2 (en) * | 2013-04-22 | 2016-02-23 | Socialmatic LLC | System and method for sharing photographic content |
WO2014197334A2 (en) | 2013-06-07 | 2014-12-11 | Apple Inc. | System and method for user-specified pronunciation of words for speech synthesis and recognition |
WO2014197335A1 (en) | 2013-06-08 | 2014-12-11 | Apple Inc. | Interpreting and acting upon commands that involve sharing information with remote devices |
EP3937002A1 (en) | 2013-06-09 | 2022-01-12 | Apple Inc. | Device, method, and graphical user interface for enabling conversation persistence across two or more instances of a digital assistant |
CN104142963B (en) * | 2013-06-09 | 2018-05-15 | 腾讯科技(北京)有限公司 | A kind of method, system and the client of the issue of microblogging orientation |
US10176167B2 (en) | 2013-06-09 | 2019-01-08 | Apple Inc. | System and method for inferring user intent from speech inputs |
CN104252461B (en) * | 2013-06-26 | 2017-12-05 | 国际商业机器公司 | Monitor the method and system of subject of interest |
CN104281610B (en) * | 2013-07-08 | 2019-03-29 | 腾讯科技(深圳)有限公司 | The method and apparatus for filtering microblogging |
US20150019653A1 (en) * | 2013-07-15 | 2015-01-15 | Civolution B.V. | Method and system for adding an identifier |
US10791216B2 (en) | 2013-08-06 | 2020-09-29 | Apple Inc. | Auto-activating smart responses based on activities from remote devices |
US9565234B1 (en) * | 2013-08-30 | 2017-02-07 | Google Inc. | Content request identification via a computer network |
CN104035947B (en) * | 2013-09-16 | 2016-04-13 | 腾讯科技(深圳)有限公司 | Point of interest recommend method and device, acquisition recommend method and the device of point of interest |
US10319013B2 (en) | 2013-10-28 | 2019-06-11 | Square, Inc. | Electronic ordering system |
US10296160B2 (en) | 2013-12-06 | 2019-05-21 | Apple Inc. | Method for extracting salient dialog usage from live data |
CA2939757A1 (en) * | 2014-02-28 | 2015-09-03 | Wal-Mart Stores, Inc. | Crowd planning tool |
US10567253B1 (en) * | 2014-04-03 | 2020-02-18 | Stad.Io Llc | Method and system for collection, data-mining and display of information regarding and relating to attendees of live events for management decisions |
US10762514B1 (en) * | 2014-04-03 | 2020-09-01 | Stad.Io, Llc | Filtering and stratification for identification of high value participants at live events in real-time |
US9648089B2 (en) | 2014-04-25 | 2017-05-09 | Samsung Electronics Co., Ltd. | Context-aware hypothesis-driven aggregation of crowd-sourced evidence for a subscription-based service |
US9430463B2 (en) | 2014-05-30 | 2016-08-30 | Apple Inc. | Exemplar-based natural language processing |
US10170123B2 (en) | 2014-05-30 | 2019-01-01 | Apple Inc. | Intelligent assistant for home automation |
US9715875B2 (en) | 2014-05-30 | 2017-07-25 | Apple Inc. | Reducing the need for manual start/end-pointing and trigger phrases |
US9633004B2 (en) | 2014-05-30 | 2017-04-25 | Apple Inc. | Better resolution when referencing to concepts |
CN110797019B (en) | 2014-05-30 | 2023-08-29 | 苹果公司 | Multi-command single speech input method |
US9338493B2 (en) | 2014-06-30 | 2016-05-10 | Apple Inc. | Intelligent automated assistant for TV user interactions |
CN105224582B (en) * | 2014-07-03 | 2018-11-09 | 联想(北京)有限公司 | Information processing method and equipment |
US10410272B1 (en) | 2014-08-20 | 2019-09-10 | Square, Inc. | Predicting orders from buyer behavior |
US9818400B2 (en) | 2014-09-11 | 2017-11-14 | Apple Inc. | Method and apparatus for discovering trending terms in speech requests |
US10074360B2 (en) | 2014-09-30 | 2018-09-11 | Apple Inc. | Providing an indication of the suitability of speech recognition |
US10127911B2 (en) | 2014-09-30 | 2018-11-13 | Apple Inc. | Speaker identification and unsupervised speaker adaptation techniques |
US9668121B2 (en) | 2014-09-30 | 2017-05-30 | Apple Inc. | Social reminders |
US10852151B2 (en) | 2014-12-12 | 2020-12-01 | Square, Inc. | Dynamic reconfiguring of geo-fences |
US9589290B1 (en) | 2014-12-31 | 2017-03-07 | Square, Inc. | Client-side use of customer preferences |
US10366436B1 (en) | 2014-12-31 | 2019-07-30 | Square, Inc. | Categorization of items based on item delivery time |
US10430849B1 (en) | 2014-12-31 | 2019-10-01 | Square, Inc. | Propagation of customer preferences |
US10127595B1 (en) * | 2014-12-31 | 2018-11-13 | Square, Inc. | Categorization of items based on attributes |
US10872111B2 (en) * | 2015-01-14 | 2020-12-22 | Lenovo Enterprise Solutions (Singapore) Pte. Ltd | User generated data based map search |
US10152299B2 (en) | 2015-03-06 | 2018-12-11 | Apple Inc. | Reducing response latency of intelligent automated assistants |
US10567477B2 (en) | 2015-03-08 | 2020-02-18 | Apple Inc. | Virtual assistant continuity |
US9721566B2 (en) | 2015-03-08 | 2017-08-01 | Apple Inc. | Competing devices responding to voice triggers |
US9886953B2 (en) | 2015-03-08 | 2018-02-06 | Apple Inc. | Virtual assistant activation |
US10460227B2 (en) | 2015-05-15 | 2019-10-29 | Apple Inc. | Virtual assistant in a communication session |
US10083688B2 (en) | 2015-05-27 | 2018-09-25 | Apple Inc. | Device voice control for selecting a displayed affordance |
US10200824B2 (en) | 2015-05-27 | 2019-02-05 | Apple Inc. | Systems and methods for proactively identifying and surfacing relevant content on a touch-sensitive device |
US9578173B2 (en) | 2015-06-05 | 2017-02-21 | Apple Inc. | Virtual assistant aided communication with 3rd party service in a communication session |
US11025565B2 (en) | 2015-06-07 | 2021-06-01 | Apple Inc. | Personalized prediction of responses for instant messaging |
CN106294516A (en) * | 2015-06-12 | 2017-01-04 | 阿里巴巴集团控股有限公司 | Method for providing position information and device |
US20160378747A1 (en) | 2015-06-29 | 2016-12-29 | Apple Inc. | Virtual assistant for media playback |
CN105045880B (en) * | 2015-07-22 | 2018-09-18 | 福州大学 | A kind of Method of Fuzzy Matching of the point of interest of different data sources |
US10234305B2 (en) * | 2015-08-27 | 2019-03-19 | Here Global B.V. | Method and apparatus for providing a targeted map display from a plurality of data sources |
CN106484748B (en) | 2015-09-02 | 2019-07-23 | 阿里巴巴集团控股有限公司 | A kind of determining point of interest POI lays the method and device of demand |
US10331312B2 (en) | 2015-09-08 | 2019-06-25 | Apple Inc. | Intelligent automated assistant in a media environment |
US10671428B2 (en) | 2015-09-08 | 2020-06-02 | Apple Inc. | Distributed personal assistant |
US10747498B2 (en) | 2015-09-08 | 2020-08-18 | Apple Inc. | Zero latency digital assistant |
US10740384B2 (en) | 2015-09-08 | 2020-08-11 | Apple Inc. | Intelligent automated assistant for media search and playback |
US11587559B2 (en) | 2015-09-30 | 2023-02-21 | Apple Inc. | Intelligent device identification |
US10268780B2 (en) * | 2015-10-07 | 2019-04-23 | International Business Machines Corporation | Learning hashtag relevance |
IL242219B (en) | 2015-10-22 | 2020-11-30 | Verint Systems Ltd | System and method for keyword searching using both static and dynamic dictionaries |
IL242218B (en) | 2015-10-22 | 2020-11-30 | Verint Systems Ltd | System and method for maintaining a dynamic dictionary |
US10691473B2 (en) | 2015-11-06 | 2020-06-23 | Apple Inc. | Intelligent automated assistant in a messaging environment |
US10956666B2 (en) | 2015-11-09 | 2021-03-23 | Apple Inc. | Unconventional virtual assistant interactions |
US10419554B2 (en) * | 2015-11-12 | 2019-09-17 | Facebook, Inc. | Systems and methods for sharing information |
US10049668B2 (en) | 2015-12-02 | 2018-08-14 | Apple Inc. | Applying neural network language models to weighted finite state transducers for automatic speech recognition |
US9747174B2 (en) | 2015-12-11 | 2017-08-29 | Microsoft Technology Licensing, Llc | Tail of logs in persistent main memory |
US10223066B2 (en) | 2015-12-23 | 2019-03-05 | Apple Inc. | Proactive assistance based on dialog communication between devices |
US10210274B2 (en) | 2016-01-04 | 2019-02-19 | International Business Machines Corporation | Method, system and computer product for filtering audience viewing of URL data utilizing hashtags |
US10705721B2 (en) * | 2016-01-21 | 2020-07-07 | Samsung Electronics Co., Ltd. | Method and system for providing topic view in electronic device |
US11227589B2 (en) | 2016-06-06 | 2022-01-18 | Apple Inc. | Intelligent list reading |
US10049663B2 (en) | 2016-06-08 | 2018-08-14 | Apple, Inc. | Intelligent automated assistant for media exploration |
US12223282B2 (en) | 2016-06-09 | 2025-02-11 | Apple Inc. | Intelligent automated assistant in a home environment |
US10067938B2 (en) | 2016-06-10 | 2018-09-04 | Apple Inc. | Multilingual word prediction |
US10586535B2 (en) | 2016-06-10 | 2020-03-10 | Apple Inc. | Intelligent digital assistant in a multi-tasking environment |
DK179415B1 (en) | 2016-06-11 | 2018-06-14 | Apple Inc | Intelligent device arbitration and control |
DK201670540A1 (en) | 2016-06-11 | 2018-01-08 | Apple Inc | Application integration with a digital assistant |
CN109891190B (en) * | 2016-08-11 | 2020-12-29 | 阿克森维伯股份公司 | Geo-locating individuals based on derived social networks |
US10474753B2 (en) | 2016-09-07 | 2019-11-12 | Apple Inc. | Language identification using recurrent neural networks |
US10043516B2 (en) | 2016-09-23 | 2018-08-07 | Apple Inc. | Intelligent automated assistant |
US11281993B2 (en) | 2016-12-05 | 2022-03-22 | Apple Inc. | Model and ensemble compression for metric learning |
US11076034B2 (en) * | 2016-12-06 | 2021-07-27 | Airwatch, Llc | Initiating application execution with trigger characters |
KR102524674B1 (en) * | 2016-12-14 | 2023-04-21 | 삼성전자주식회사 | Electronic apparatus and notification service providing method thereof |
US10593346B2 (en) | 2016-12-22 | 2020-03-17 | Apple Inc. | Rank-reduced token representation for automatic speech recognition |
CN108241630A (en) * | 2016-12-23 | 2018-07-03 | 武汉四维图新科技有限公司 | Recommend method and device in a kind of driving destination |
CN108243178B (en) * | 2016-12-27 | 2021-05-28 | 武汉斗鱼网络科技有限公司 | A method and system for obtaining the attention status of an anchor |
US11204787B2 (en) | 2017-01-09 | 2021-12-21 | Apple Inc. | Application integration with a digital assistant |
DK201770383A1 (en) | 2017-05-09 | 2018-12-14 | Apple Inc. | User interface for correcting recognition errors |
US10417266B2 (en) | 2017-05-09 | 2019-09-17 | Apple Inc. | Context-aware ranking of intelligent response suggestions |
DK201770439A1 (en) | 2017-05-11 | 2018-12-13 | Apple Inc. | Offline personal assistant |
US10395654B2 (en) | 2017-05-11 | 2019-08-27 | Apple Inc. | Text normalization based on a data-driven learning network |
US10726832B2 (en) | 2017-05-11 | 2020-07-28 | Apple Inc. | Maintaining privacy of personal information |
DK180048B1 (en) | 2017-05-11 | 2020-02-04 | Apple Inc. | MAINTAINING THE DATA PROTECTION OF PERSONAL INFORMATION |
DK179496B1 (en) | 2017-05-12 | 2019-01-15 | Apple Inc. | USER-SPECIFIC Acoustic Models |
US11301477B2 (en) | 2017-05-12 | 2022-04-12 | Apple Inc. | Feedback analysis of a digital assistant |
DK201770428A1 (en) | 2017-05-12 | 2019-02-18 | Apple Inc. | Low-latency intelligent automated assistant |
DK179745B1 (en) | 2017-05-12 | 2019-05-01 | Apple Inc. | SYNCHRONIZATION AND TASK DELEGATION OF A DIGITAL ASSISTANT |
DK201770411A1 (en) | 2017-05-15 | 2018-12-20 | Apple Inc. | MULTI-MODAL INTERFACES |
DK201770432A1 (en) | 2017-05-15 | 2018-12-21 | Apple Inc. | Hierarchical belief states for digital assistants |
DK201770431A1 (en) | 2017-05-15 | 2018-12-20 | Apple Inc. | Optimizing dialogue policy decisions for digital assistants using implicit feedback |
US10311144B2 (en) | 2017-05-16 | 2019-06-04 | Apple Inc. | Emoji word sense disambiguation |
US20180336275A1 (en) | 2017-05-16 | 2018-11-22 | Apple Inc. | Intelligent automated assistant for media exploration |
DK179560B1 (en) | 2017-05-16 | 2019-02-18 | Apple Inc. | Far-field extension for digital assistant services |
US10403278B2 (en) | 2017-05-16 | 2019-09-03 | Apple Inc. | Methods and systems for phonetic matching in digital assistant services |
US20180336892A1 (en) | 2017-05-16 | 2018-11-22 | Apple Inc. | Detecting a trigger of a digital assistant |
CN107181802B (en) * | 2017-05-22 | 2020-09-25 | 北京百度网讯科技有限公司 | Intelligent hardware control method and device, server and storage medium |
US10657328B2 (en) | 2017-06-02 | 2020-05-19 | Apple Inc. | Multi-task recurrent neural network architecture for efficient morphology handling in neural language modeling |
US10445429B2 (en) | 2017-09-21 | 2019-10-15 | Apple Inc. | Natural language understanding using vocabularies with compressed serialized tries |
US10755051B2 (en) | 2017-09-29 | 2020-08-25 | Apple Inc. | Rule-based natural language processing |
US10585728B2 (en) * | 2017-11-28 | 2020-03-10 | International Business Machines Corporation | Transforming sensor data streamed to applications |
US10636424B2 (en) | 2017-11-30 | 2020-04-28 | Apple Inc. | Multi-turn canned dialog |
US10733982B2 (en) | 2018-01-08 | 2020-08-04 | Apple Inc. | Multi-directional dialog |
US10733375B2 (en) | 2018-01-31 | 2020-08-04 | Apple Inc. | Knowledge-based framework for improving natural language understanding |
US10789959B2 (en) | 2018-03-02 | 2020-09-29 | Apple Inc. | Training speaker recognition models for digital assistants |
US10592604B2 (en) | 2018-03-12 | 2020-03-17 | Apple Inc. | Inverse text normalization for automatic speech recognition |
US10818288B2 (en) | 2018-03-26 | 2020-10-27 | Apple Inc. | Natural assistant interaction |
US10909331B2 (en) | 2018-03-30 | 2021-02-02 | Apple Inc. | Implicit identification of translation payload with neural machine translation |
US11145294B2 (en) | 2018-05-07 | 2021-10-12 | Apple Inc. | Intelligent automated assistant for delivering content from user experiences |
US10928918B2 (en) | 2018-05-07 | 2021-02-23 | Apple Inc. | Raise to speak |
US10984780B2 (en) | 2018-05-21 | 2021-04-20 | Apple Inc. | Global semantic word embeddings using bi-directional recurrent neural networks |
DK179822B1 (en) | 2018-06-01 | 2019-07-12 | Apple Inc. | Voice interaction at a primary device to access call functionality of a companion device |
DK180639B1 (en) | 2018-06-01 | 2021-11-04 | Apple Inc | DISABILITY OF ATTENTION-ATTENTIVE VIRTUAL ASSISTANT |
DK201870355A1 (en) | 2018-06-01 | 2019-12-16 | Apple Inc. | Virtual assistant operation in multi-device environments |
US11386266B2 (en) | 2018-06-01 | 2022-07-12 | Apple Inc. | Text correction |
US10892996B2 (en) | 2018-06-01 | 2021-01-12 | Apple Inc. | Variable latency device coordination |
US10496705B1 (en) | 2018-06-03 | 2019-12-03 | Apple Inc. | Accelerated task performance |
US11010561B2 (en) | 2018-09-27 | 2021-05-18 | Apple Inc. | Sentiment prediction from textual data |
US11462215B2 (en) | 2018-09-28 | 2022-10-04 | Apple Inc. | Multi-modal inputs for voice commands |
US10839159B2 (en) | 2018-09-28 | 2020-11-17 | Apple Inc. | Named entity normalization in a spoken dialog system |
US11170166B2 (en) | 2018-09-28 | 2021-11-09 | Apple Inc. | Neural typographical error modeling via generative adversarial networks |
US11475898B2 (en) | 2018-10-26 | 2022-10-18 | Apple Inc. | Low-latency multi-speaker speech recognition |
CN109657163B (en) * | 2018-12-19 | 2022-01-18 | 拉扎斯网络科技(上海)有限公司 | Destination address determining method and device, electronic equipment and storage medium |
US11638059B2 (en) | 2019-01-04 | 2023-04-25 | Apple Inc. | Content playback on multiple devices |
US11348573B2 (en) | 2019-03-18 | 2022-05-31 | Apple Inc. | Multimodality in digital assistant systems |
US11307752B2 (en) | 2019-05-06 | 2022-04-19 | Apple Inc. | User configurable task triggers |
US11423908B2 (en) | 2019-05-06 | 2022-08-23 | Apple Inc. | Interpreting spoken requests |
DK201970509A1 (en) | 2019-05-06 | 2021-01-15 | Apple Inc | Spoken notifications |
US11475884B2 (en) | 2019-05-06 | 2022-10-18 | Apple Inc. | Reducing digital assistant latency when a language is incorrectly determined |
US11140099B2 (en) | 2019-05-21 | 2021-10-05 | Apple Inc. | Providing message response suggestions |
DK201970511A1 (en) | 2019-05-31 | 2021-02-15 | Apple Inc | Voice identification in digital assistant systems |
DK180129B1 (en) | 2019-05-31 | 2020-06-02 | Apple Inc. | USER ACTIVITY SHORTCUT SUGGESTIONS |
US11496600B2 (en) | 2019-05-31 | 2022-11-08 | Apple Inc. | Remote execution of machine-learned models |
US11289073B2 (en) | 2019-05-31 | 2022-03-29 | Apple Inc. | Device text to speech |
US11360641B2 (en) | 2019-06-01 | 2022-06-14 | Apple Inc. | Increasing the relevance of new available information |
US11468890B2 (en) | 2019-06-01 | 2022-10-11 | Apple Inc. | Methods and user interfaces for voice-based control of electronic devices |
WO2021056255A1 (en) | 2019-09-25 | 2021-04-01 | Apple Inc. | Text detection using global geometry estimators |
US11061543B1 (en) | 2020-05-11 | 2021-07-13 | Apple Inc. | Providing relevant data items based on context |
US11038934B1 (en) | 2020-05-11 | 2021-06-15 | Apple Inc. | Digital assistant hardware abstraction |
US11755276B2 (en) | 2020-05-12 | 2023-09-12 | Apple Inc. | Reducing description length based on confidence |
US11490204B2 (en) | 2020-07-20 | 2022-11-01 | Apple Inc. | Multi-device audio adjustment coordination |
US11438683B2 (en) | 2020-07-21 | 2022-09-06 | Apple Inc. | User identification using headphones |
US20220130003A1 (en) | 2020-10-26 | 2022-04-28 | Near Pte. Ltd. | Method for automatically inferring place properties based on spatial activity data using bayesian models |
WO2022159735A1 (en) * | 2021-01-22 | 2022-07-28 | Thomson Reuters Enterprise Centre Gmbh | System and method for automated hashtag hierarchical ontology generation from social media data |
US11200306B1 (en) | 2021-02-25 | 2021-12-14 | Telcom Ventures, Llc | Methods, devices, and systems for authenticating user identity for location-based deliveries |
CN117280373A (en) * | 2021-04-28 | 2023-12-22 | 日产自动车株式会社 | Information processing apparatus and information processing method |
US20240273060A1 (en) * | 2023-02-09 | 2024-08-15 | Inner-Machinations, Inc. | Micro-forum network |
Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20090164574A1 (en) * | 2007-12-21 | 2009-06-25 | Concert Technology Corporation | System and method for identifying transient friends |
US20090312033A1 (en) * | 2008-06-16 | 2009-12-17 | Microsoft Corporation | Mashup application and service for wireless devices |
Family Cites Families (214)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JPH0756933A (en) | 1993-06-24 | 1995-03-03 | Xerox Corp | Method for retrieval of document |
US5519608A (en) | 1993-06-24 | 1996-05-21 | Xerox Corporation | Method for extracting from a text corpus answers to questions stated in natural language by using linguistic analysis and hypothesis generation |
US5539232A (en) | 1994-05-31 | 1996-07-23 | Kabushiki Kaisha Toshiba | MOS composite type semiconductor device |
US7432830B2 (en) * | 1994-06-24 | 2008-10-07 | Navteq North America, Llc | Electronic navigation system and method |
US20010013009A1 (en) | 1997-05-20 | 2001-08-09 | Daniel R. Greening | System and method for computer-based marketing |
US6161149A (en) | 1998-03-13 | 2000-12-12 | Groupserve, Inc. | Centrifugal communication and collaboration method |
US6189008B1 (en) | 1998-04-03 | 2001-02-13 | Intertainer, Inc. | Dynamic digital asset management |
US6240069B1 (en) | 1998-06-16 | 2001-05-29 | Ericsson Inc. | System and method for location-based group services |
AU6392899A (en) * | 1998-09-15 | 2000-04-03 | Local2Me.Com, Inc. | Dynamic matching TM of users for group communication |
US6385602B1 (en) | 1998-11-03 | 2002-05-07 | E-Centives, Inc. | Presentation of search results using dynamic categorization |
US20040181668A1 (en) | 1999-06-30 | 2004-09-16 | Blew Edwin O. | Methods for conducting server-side encryption/decryption-on-demand |
US6549768B1 (en) | 1999-08-24 | 2003-04-15 | Nokia Corp | Mobile communications matching system |
ES2211156T3 (en) | 1999-09-29 | 2004-07-01 | Swisscom Mobile Ag | PROCEDURE TO FIND MEMBERS OF A SAME GROUP OF INTEREST. |
US6204844B1 (en) | 1999-10-08 | 2001-03-20 | Motorola, Inc. | Method and apparatus for dynamically grouping communication units in a communication system |
US6819919B1 (en) | 1999-10-29 | 2004-11-16 | Telcontar | Method for providing matching and introduction services to proximate mobile users and service providers |
WO2001039506A2 (en) | 1999-11-22 | 2001-05-31 | Spiderdance, Inc. | System and method for synchronizing online activities with broadcast programming |
US6708172B1 (en) | 1999-12-22 | 2004-03-16 | Urbanpixel, Inc. | Community-based shared multiple browser environment |
MXPA02010760A (en) | 2000-05-01 | 2004-05-17 | Netoncourse Inc | Large group interactions. |
US20020010628A1 (en) | 2000-05-24 | 2002-01-24 | Alan Burns | Method of advertising and polling |
AU2001267779A1 (en) * | 2000-05-30 | 2001-12-11 | Koki Uchiyama | Distributed monitoring system providing knowledge services |
US6539232B2 (en) | 2000-06-10 | 2003-03-25 | Telcontar | Method and system for connecting mobile users based on degree of separation |
US20020049690A1 (en) | 2000-06-16 | 2002-04-25 | Masanori Takano | Method of expressing crowd movement in game, storage medium, and information processing apparatus |
US6968179B1 (en) | 2000-07-27 | 2005-11-22 | Microsoft Corporation | Place specific buddy list services |
US8117281B2 (en) | 2006-11-02 | 2012-02-14 | Addnclick, Inc. | Using internet content as a means to establish live social networks by linking internet users to each other who are simultaneously engaged in the same and/or similar content |
US7062469B2 (en) | 2001-01-02 | 2006-06-13 | Nokia Corporation | System and method for public wireless network access subsidized by dynamic display advertising |
US6529136B2 (en) | 2001-02-28 | 2003-03-04 | International Business Machines Corporation | Group notification system and method for implementing and indicating the proximity of individuals or groups to other individuals or groups |
US6820081B1 (en) | 2001-03-19 | 2004-11-16 | Attenex Corporation | System and method for evaluating a structured message store for message redundancy |
US6757517B2 (en) | 2001-05-10 | 2004-06-29 | Chin-Chi Chang | Apparatus and method for coordinated music playback in wireless ad-hoc networks |
US7398195B2 (en) | 2001-06-01 | 2008-07-08 | Progress Software Corporation | One to many mapping of application service provision |
JP2003203084A (en) | 2001-06-29 | 2003-07-18 | Hitachi Ltd | Information terminal device, server, information distribution device, and information distribution method |
US7123918B1 (en) | 2001-08-20 | 2006-10-17 | Verizon Services Corp. | Methods and apparatus for extrapolating person and device counts |
US20050231425A1 (en) | 2001-09-10 | 2005-10-20 | American Gnc Corporation | Wireless wide area networked precision geolocation |
US6999783B2 (en) | 2001-11-01 | 2006-02-14 | Nokia Corporation | Method for creating a dynamic talk group |
US20040025185A1 (en) | 2002-04-29 | 2004-02-05 | John Goci | Digital video jukebox network enterprise system |
US7024207B2 (en) | 2002-04-30 | 2006-04-04 | Motorola, Inc. | Method of targeting a message to a communication device selected from among a set of communication devices |
US7254406B2 (en) * | 2002-06-10 | 2007-08-07 | Suman Beros | Method and apparatus for effecting a detection of mobile devices that are proximate and exhibit commonalities between specific data sets, or profiles, associated with the persons transporting the mobile devices |
US7444655B2 (en) | 2002-06-11 | 2008-10-28 | Microsoft Corporation | Anonymous aggregated data collection |
US7116985B2 (en) | 2002-06-14 | 2006-10-03 | Cingular Wireless Ii, Llc | Method for providing location-based services in a wireless network, such as varying levels of services |
US9563708B2 (en) * | 2002-11-18 | 2017-02-07 | Aol Inc. | Matching members with shared interests |
US7247024B2 (en) | 2002-11-22 | 2007-07-24 | Ut-Battelle, Llc | Method for spatially distributing a population |
US8019874B2 (en) * | 2003-01-31 | 2011-09-13 | Fujitsu Limited | Apparatus for delivering information and method therefor |
JP2004241866A (en) | 2003-02-03 | 2004-08-26 | Alpine Electronics Inc | Inter-vehicle communication system |
US8423042B2 (en) | 2004-02-24 | 2013-04-16 | Invisitrack, Inc. | Method and system for positional finding using RF, continuous and/or combined movement |
US7787886B2 (en) | 2003-02-24 | 2010-08-31 | Invisitrack, Inc. | System and method for locating a target using RFID |
US7158798B2 (en) | 2003-02-28 | 2007-01-02 | Lucent Technologies Inc. | Location-based ad-hoc game services |
FI118494B (en) | 2003-03-26 | 2007-11-30 | Teliasonera Finland Oyj | Procedure for observing the mobile user's traffic streams |
EP1631932A4 (en) | 2003-06-12 | 2010-10-27 | Honda Motor Co Ltd | Systems and methods for using visual hulls to determine the number of people in a crowd |
WO2005002265A1 (en) * | 2003-06-30 | 2005-01-06 | Nokia Corporation | Method and device for determining and notifying users having matching preference profiles for accessing a multiple access online application |
US20050038876A1 (en) * | 2003-08-15 | 2005-02-17 | Aloke Chaudhuri | System and method for instant match based on location, presence, personalization and communication |
US7428417B2 (en) | 2003-09-26 | 2008-09-23 | Siemens Communications, Inc. | System and method for presence perimeter rule downloading |
US20040107283A1 (en) | 2003-10-06 | 2004-06-03 | Trilibis Inc. | System and method for the aggregation and matching of personal information |
US20050130634A1 (en) | 2003-10-31 | 2005-06-16 | Globespanvirata, Inc. | Location awareness in wireless networks |
US7359724B2 (en) | 2003-11-20 | 2008-04-15 | Nokia Corporation | Method and system for location based group formation |
US20050130676A1 (en) * | 2003-12-11 | 2005-06-16 | International Business Machines Corporation | Methods, systems, and media for acquiring ratings for points of interest |
US7398081B2 (en) | 2004-02-04 | 2008-07-08 | Modu Ltd. | Device and system for selective wireless communication with contact list memory |
US7310676B2 (en) * | 2004-02-09 | 2007-12-18 | Proxpro, Inc. | Method and computer system for matching mobile device users for business and social networking |
US7545784B2 (en) | 2004-02-11 | 2009-06-09 | Yahoo! Inc. | System and method for wireless communication between previously known and unknown users |
US8014763B2 (en) | 2004-02-28 | 2011-09-06 | Charles Martin Hymes | Wireless communications with proximal targets identified visually, aurally, or positionally |
US7818394B1 (en) | 2004-04-07 | 2010-10-19 | Cisco Techology, Inc. | Social network augmentation of search results methods and apparatus |
US7676585B1 (en) | 2004-04-29 | 2010-03-09 | Cisco Technology, Inc. | System and method for dynamically adjusting a refresh interval |
US7593740B2 (en) * | 2004-05-12 | 2009-09-22 | Google, Inc. | Location-based social software for mobile devices |
US7509131B2 (en) | 2004-06-29 | 2009-03-24 | Microsoft Corporation | Proximity detection using wireless signal strengths |
US20080126476A1 (en) | 2004-08-04 | 2008-05-29 | Nicholas Frank C | Method and System for the Creating, Managing, and Delivery of Enhanced Feed Formatted Content |
US20060046743A1 (en) * | 2004-08-24 | 2006-03-02 | Mirho Charles A | Group organization according to device location |
US8126441B2 (en) | 2004-09-21 | 2012-02-28 | Advanced Ground Information Systems, Inc. | Method of establishing a cell phone network of participants with a common interest |
CN101044504A (en) * | 2004-10-19 | 2007-09-26 | 雅虎公司 | System and method for location based social networking |
US11283885B2 (en) * | 2004-10-19 | 2022-03-22 | Verizon Patent And Licensing Inc. | System and method for location based matching and promotion |
US20060229058A1 (en) | 2005-10-29 | 2006-10-12 | Outland Research | Real-time person-to-person communication using geospatial addressing |
US20060195361A1 (en) * | 2005-10-01 | 2006-08-31 | Outland Research | Location-based demographic profiling system and method of use |
US7853268B2 (en) | 2005-01-26 | 2010-12-14 | Broadcom Corporation | GPS enabled cell phone location tracking for security purposes |
WO2006090395A2 (en) | 2005-02-28 | 2006-08-31 | Inlive Interactive Ltd. | Method and apparatus for conducting real time dialogues with mass viewer audiences during live programs |
US7423580B2 (en) | 2005-03-14 | 2008-09-09 | Invisitrack, Inc. | Method and system of three-dimensional positional finding |
US20060218153A1 (en) | 2005-03-28 | 2006-09-28 | Voon George H H | Building social networks using shared content data relating to a common interest |
US20060256008A1 (en) * | 2005-05-13 | 2006-11-16 | Outland Research, Llc | Pointing interface for person-to-person information exchange |
US7353034B2 (en) | 2005-04-04 | 2008-04-01 | X One, Inc. | Location sharing and tracking using mobile phones or other wireless devices |
US20070210937A1 (en) | 2005-04-21 | 2007-09-13 | Microsoft Corporation | Dynamic rendering of map information |
KR100679045B1 (en) * | 2005-06-15 | 2007-02-05 | 삼성전자주식회사 | Method of determining a point of interest of a mobile terminal user and apparatus for providing geographic information using the same |
US20060287765A1 (en) | 2005-06-20 | 2006-12-21 | Kraft Harold H | Privacy Information Reporting Systems with Broad Search Scope and Integration |
US20070005419A1 (en) | 2005-06-30 | 2007-01-04 | Microsoft Corporation | Recommending location and services via geospatial collaborative filtering |
US20070015518A1 (en) | 2005-07-15 | 2007-01-18 | Agilis Systems, Inc. | Mobile resource location-based customer contact systems |
US8150416B2 (en) | 2005-08-08 | 2012-04-03 | Jambo Networks, Inc. | System and method for providing communication services to mobile device users incorporating proximity determination |
US20070050128A1 (en) * | 2005-08-31 | 2007-03-01 | Garmin Ltd., A Cayman Islands Corporation | Method and system for off-board navigation with a portable device |
US20080215623A1 (en) | 2005-09-14 | 2008-09-04 | Jorey Ramer | Mobile communication facility usage and social network creation |
US20090276500A1 (en) | 2005-09-21 | 2009-11-05 | Amit Vishram Karmarkar | Microblog search engine system and method |
US8489132B2 (en) | 2005-09-21 | 2013-07-16 | Buckyball Mobile Inc. | Context-enriched microblog posting |
US7412534B2 (en) * | 2005-09-30 | 2008-08-12 | Yahoo! Inc. | Subscription control panel |
WO2007059241A2 (en) * | 2005-11-15 | 2007-05-24 | Enpresence, Inc. | Proximity-a ware virtual agents for use with wireless mobile devices |
WO2007062044A2 (en) | 2005-11-23 | 2007-05-31 | Object Video, Inc | Object density estimation in video |
US7558404B2 (en) | 2005-11-28 | 2009-07-07 | Honeywell International Inc. | Detection of abnormal crowd behavior |
WO2007070505A2 (en) | 2005-12-13 | 2007-06-21 | Squareloop, Inc. | System, apparatus, and methods for location managed message processing |
US20070135138A1 (en) * | 2005-12-13 | 2007-06-14 | Internation Business Machines Corporation | Methods, systems, and computer program products for providing location based subscription services |
US7809805B2 (en) * | 2007-02-28 | 2010-10-05 | Facebook, Inc. | Systems and methods for automatically locating web-based social network members |
US7774001B2 (en) | 2005-12-16 | 2010-08-10 | Sony Ericsson Mobile Communications Ab | Device and method for determining where crowds exist |
US7801542B1 (en) | 2005-12-19 | 2010-09-21 | Stewart Brett B | Automatic management of geographic information pertaining to social networks, groups of users, or assets |
US7620404B2 (en) | 2005-12-22 | 2009-11-17 | Pascal Chesnais | Methods and apparatus for organizing and presenting contact information in a mobile communication system |
US20070218900A1 (en) | 2006-03-17 | 2007-09-20 | Raj Vasant Abhyanker | Map based neighborhood search and community contribution |
US20070220090A1 (en) | 2006-01-14 | 2007-09-20 | Hall Rohan R | System and method for online group networks |
US7466986B2 (en) | 2006-01-19 | 2008-12-16 | International Business Machines Corporation | On-device mapping of WIFI hotspots via direct connection of WIFI-enabled and GPS-enabled mobile devices |
US20070174243A1 (en) | 2006-01-20 | 2007-07-26 | Fritz Charles W | Mobile social search using physical identifiers |
US7856360B2 (en) | 2006-01-30 | 2010-12-21 | Hoozware, Inc. | System for providing a service to venues where people aggregate |
US20070179863A1 (en) | 2006-01-30 | 2007-08-02 | Goseetell Network, Inc. | Collective intelligence recommender system for travel information and travel industry marketing platform |
US8352183B2 (en) | 2006-02-04 | 2013-01-08 | Microsoft Corporation | Maps for social networking and geo blogs |
US8145719B2 (en) * | 2006-03-03 | 2012-03-27 | Gogroups | Method and system for messaging and communication based on groups |
US20070233736A1 (en) | 2006-03-28 | 2007-10-04 | Heyletsgo, Inc. | Method and system for social and leisure life management |
US8645991B2 (en) | 2006-03-30 | 2014-02-04 | Tout Industries, Inc. | Method and apparatus for annotating media streams |
US7761350B1 (en) * | 2006-04-26 | 2010-07-20 | Aol Inc. | Biasing of search result clustering to ensure more effective point of interest (POI) targeting |
US8843560B2 (en) | 2006-04-28 | 2014-09-23 | Yahoo! Inc. | Social networking for mobile devices |
US8046411B2 (en) | 2006-04-28 | 2011-10-25 | Yahoo! Inc. | Multimedia sharing in social networks for mobile devices |
US20070282621A1 (en) | 2006-06-01 | 2007-12-06 | Flipt, Inc | Mobile dating system incorporating user location information |
US8571580B2 (en) | 2006-06-01 | 2013-10-29 | Loopt Llc. | Displaying the location of individuals on an interactive map display on a mobile communication device |
US20070281716A1 (en) | 2006-06-01 | 2007-12-06 | Flipt, Inc | Message transmission system for users of location-aware mobile communication devices in a local area network |
US20070290832A1 (en) | 2006-06-16 | 2007-12-20 | Fmr Corp. | Invoking actionable alerts |
AU2007264420B8 (en) | 2006-06-29 | 2012-04-12 | International Business Machines Corporation | Cyberpersonalities in artificial reality |
WO2008000043A1 (en) * | 2006-06-30 | 2008-01-03 | Eccosphere International Pty Ltd | Method of social interaction between communication device users |
US20080005227A1 (en) | 2006-07-03 | 2008-01-03 | Srinivasan Subbian | Method and system for content processing |
US7932831B2 (en) | 2006-07-11 | 2011-04-26 | At&T Intellectual Property I, L.P. | Crowd determination |
US7680959B2 (en) | 2006-07-11 | 2010-03-16 | Napo Enterprises, Llc | P2P network for providing real time media recommendations |
US20100153213A1 (en) | 2006-08-24 | 2010-06-17 | Kevin Pomplun | Systems and Methods for Dynamic Content Selection and Distribution |
US20080182563A1 (en) | 2006-09-15 | 2008-07-31 | Wugofski Theodore D | Method and system for social networking over mobile devices using profiles |
US20080086741A1 (en) | 2006-10-10 | 2008-04-10 | Quantcast Corporation | Audience commonality and measurement |
US20080097999A1 (en) | 2006-10-10 | 2008-04-24 | Tim Horan | Dynamic creation of information sharing social networks |
US8064934B2 (en) | 2006-10-19 | 2011-11-22 | Research In Motion Limited | Method, system and apparatus for automatic notification to a plurality of communication nodes |
US20080113674A1 (en) | 2006-11-10 | 2008-05-15 | Mohammad Faisal Baig | Vicinity-based community for wireless users |
US20080242317A1 (en) | 2007-03-26 | 2008-10-02 | Fatdoor, Inc. | Mobile content creation, sharing, and commerce in a geo-spatial environment |
US8116564B2 (en) | 2006-11-22 | 2012-02-14 | Regents Of The University Of Minnesota | Crowd counting and monitoring |
US8108414B2 (en) * | 2006-11-29 | 2012-01-31 | David Stackpole | Dynamic location-based social networking |
US8571787B2 (en) * | 2006-12-06 | 2013-10-29 | Sony Corporation | Dynamic routing |
US20080182591A1 (en) | 2006-12-13 | 2008-07-31 | Synthesis Studios, Inc. | Mobile Proximity-Based Notifications |
US20080146250A1 (en) | 2006-12-15 | 2008-06-19 | Jeffrey Aaron | Method and System for Creating and Using a Location Safety Indicator |
US8224359B2 (en) * | 2006-12-22 | 2012-07-17 | Yahoo! Inc. | Provisioning my status information to others in my social network |
US20080183816A1 (en) | 2007-01-31 | 2008-07-31 | Morris Robert P | Method and system for associating a tag with a status value of a principal associated with a presence client |
US20080188261A1 (en) | 2007-02-02 | 2008-08-07 | Miles Arnone | Mediated social network |
US20080228719A1 (en) * | 2007-03-13 | 2008-09-18 | Fatdoor, Inc. | People and business search result optimization |
US20080234929A1 (en) * | 2007-03-20 | 2008-09-25 | Ford Motor Company | System and method to determine, in a vehicle, locations of interest |
US8073474B1 (en) * | 2007-03-23 | 2011-12-06 | Zumobi, Inc. | Systems and methods for controlling group messaging |
US8112720B2 (en) | 2007-04-05 | 2012-02-07 | Napo Enterprises, Llc | System and method for automatically and graphically associating programmatically-generated media item recommendations related to a user's socially recommended media items |
US9140552B2 (en) | 2008-07-02 | 2015-09-22 | Qualcomm Incorporated | User defined names for displaying monitored location |
US20080294663A1 (en) | 2007-05-14 | 2008-11-27 | Heinley Brandon J | Creation and management of visual timelines |
WO2008154492A2 (en) * | 2007-06-08 | 2008-12-18 | Network Communications, Inc. | Systems and methods for sales lead ranking based on assessment of internet behavior |
US7818396B2 (en) | 2007-06-21 | 2010-10-19 | Microsoft Corporation | Aggregating and searching profile data from multiple services |
US8185137B2 (en) | 2007-06-25 | 2012-05-22 | Microsoft Corporation | Intensity-based maps |
US20090006551A1 (en) | 2007-06-29 | 2009-01-01 | Microsoft Corporation | Dynamic awareness of people |
US8533269B2 (en) | 2007-12-03 | 2013-09-10 | Stephen J. Brown | User-calibrated activity newsfeed on a social network |
US8165808B2 (en) | 2007-07-17 | 2012-04-24 | Yahoo! Inc. | Techniques for representing location information |
US7962155B2 (en) | 2007-07-18 | 2011-06-14 | Hewlett-Packard Development Company, L.P. | Location awareness of devices |
WO2009017702A1 (en) | 2007-07-27 | 2009-02-05 | Intertrust Technologies Corporation | Content publishing systems and methods |
US20090030999A1 (en) | 2007-07-27 | 2009-01-29 | Gatzke Alan D | Contact Proximity Notification |
US8050690B2 (en) * | 2007-08-14 | 2011-11-01 | Mpanion, Inc. | Location based presence and privacy management |
US8924250B2 (en) | 2007-09-13 | 2014-12-30 | International Business Machines Corporation | Advertising in virtual environments based on crowd statistics |
CA2670021A1 (en) | 2007-09-19 | 2009-03-26 | Micro Target Media Holdings Inc. | System and method for estimating characteristics of persons or things |
US8923887B2 (en) | 2007-09-24 | 2014-12-30 | Alcatel Lucent | Social networking on a wireless communication system |
JP4858400B2 (en) | 2007-10-17 | 2012-01-18 | ソニー株式会社 | Information providing system, information providing apparatus, and information providing method |
WO2009055501A1 (en) | 2007-10-22 | 2009-04-30 | Pelago, Inc. | Providing aggregate user-supplied information related to locations on a map |
US8031175B2 (en) * | 2008-04-21 | 2011-10-04 | Panasonic Corporation | Touch sensitive remote control system that detects hand size characteristics of user and adapts mapping to screen display |
US8467955B2 (en) | 2007-10-31 | 2013-06-18 | Microsoft Corporation | Map-centric service for social events |
US8624733B2 (en) | 2007-11-05 | 2014-01-07 | Francis John Cusack, JR. | Device for electronic access control with integrated surveillance |
US20090119603A1 (en) | 2007-11-05 | 2009-05-07 | David Scott Stackpole | Interaction Scheduling Based On Activity Status Updates |
US8620996B2 (en) | 2007-11-19 | 2013-12-31 | Motorola Mobility Llc | Method and apparatus for determining a group preference in a social network |
US9269089B2 (en) | 2007-11-22 | 2016-02-23 | Yahoo! Inc. | Method and system for media promotion |
US20100020776A1 (en) | 2007-11-27 | 2010-01-28 | Google Inc. | Wireless network-based location approximation |
US7895049B2 (en) | 2007-11-30 | 2011-02-22 | Yahoo! Inc. | Dynamic representation of group activity through reactive personas |
US9215217B2 (en) | 2008-12-05 | 2015-12-15 | Suhayya Abu-Hakima and Kenneth E. Grigg | Auto-discovery of diverse communications devices for alert broadcasting |
US8862622B2 (en) | 2007-12-10 | 2014-10-14 | Sprylogics International Corp. | Analysis, inference, and visualization of social networks |
US8307029B2 (en) | 2007-12-10 | 2012-11-06 | Yahoo! Inc. | System and method for conditional delivery of messages |
FI20085399A0 (en) | 2007-12-14 | 2008-04-30 | Xtract Oy | A method and arrangement for segmenting clients in a client management system |
US8010601B2 (en) | 2007-12-21 | 2011-08-30 | Waldeck Technology, Llc | Contiguous location-based user networks |
US8117193B2 (en) * | 2007-12-21 | 2012-02-14 | Lemi Technology, Llc | Tunersphere |
EP2245770A1 (en) * | 2008-01-23 | 2010-11-03 | LiveU Ltd. | Live uplink transmissions and broadcasting management system and method |
US8060018B2 (en) | 2008-02-08 | 2011-11-15 | Yahoo! Inc. | Data sharing based on proximity-based ad hoc network |
US20090210480A1 (en) | 2008-02-14 | 2009-08-20 | Suthaharan Sivasubramaniam | Method and system for collective socializing using a mobile social network |
US8078197B2 (en) * | 2008-02-20 | 2011-12-13 | Agere Systems Inc. | Location-based search-result ranking for blog documents and the like |
US8634796B2 (en) | 2008-03-14 | 2014-01-21 | William J. Johnson | System and method for location based exchanges of data facilitating distributed location applications |
EP2107761A1 (en) | 2008-03-31 | 2009-10-07 | Sony Corporation | Method to determine a subgroup of users |
WO2009126231A1 (en) * | 2008-04-07 | 2009-10-15 | Telecommunication Systems, Inc | Proximity search for point-of-interest names combining inexact string match with an expanding radius search |
US8655382B2 (en) * | 2008-04-10 | 2014-02-18 | Sharp Laboratories Of America, Inc. | Wireless event notification system and methods for use therein |
US20090287687A1 (en) | 2008-04-14 | 2009-11-19 | Gianni Martire | System and method for recommending venues and events of interest to a user |
US20090265604A1 (en) | 2008-04-21 | 2009-10-22 | Microsoft Corporation | Graphical representation of social network vitality |
US10867133B2 (en) * | 2008-05-01 | 2020-12-15 | Primal Fusion Inc. | System and method for using a knowledge representation to provide information based on environmental inputs |
US7962444B2 (en) | 2008-05-19 | 2011-06-14 | Qualcomm Incorporated | System and method for presenting a contextual action for an indicator |
WO2009149063A1 (en) | 2008-06-02 | 2009-12-10 | Azuki Systems, Inc. | Media mashup system |
US20090307263A1 (en) | 2008-06-06 | 2009-12-10 | Sense Networks, Inc. | System And Method Of Performing Location Analytics |
EP2289234A4 (en) | 2008-07-09 | 2014-02-12 | Loopt Inc | Social networking services for a location-aware mobile communication device |
US20100017261A1 (en) | 2008-07-17 | 2010-01-21 | Kota Enterprises, Llc | Expert system and service for location-based content influence for narrowcast |
US8806516B2 (en) * | 2008-08-19 | 2014-08-12 | Porto Technology, Llc | Method and system for constructing and presenting a consumption profile for a media item |
US20100057577A1 (en) | 2008-08-28 | 2010-03-04 | Palo Alto Research Center Incorporated | System And Method For Providing Topic-Guided Broadening Of Advertising Targets In Social Indexing |
US20100070875A1 (en) | 2008-09-10 | 2010-03-18 | Microsoft Corporation | Interactive profile presentation |
US8762459B2 (en) | 2008-09-16 | 2014-06-24 | Verizon Patent And Licensing Inc. | Selectable mode based social networking interaction systems and methods |
US20100088187A1 (en) | 2008-09-24 | 2010-04-08 | Chris Courtney | System and method for localized and/or topic-driven content distribution for mobile devices |
US8260858B2 (en) | 2008-11-06 | 2012-09-04 | At&T Intellectual Property I, L.P. | Hosting massively multiplayer online gaming via mobile devices |
US8645283B2 (en) | 2008-11-24 | 2014-02-04 | Nokia Corporation | Determination of event of interest |
US20100131502A1 (en) | 2008-11-25 | 2010-05-27 | Fordham Bradley S | Cohort group generation and automatic updating |
US9397890B2 (en) | 2009-02-02 | 2016-07-19 | Waldeck Technology Llc | Serving a request for data from a historical record of anonymized user profile data in a mobile environment |
US10275530B2 (en) | 2009-02-02 | 2019-04-30 | Excalibur Ip, Llc | System and method for communal search |
US20100205242A1 (en) * | 2009-02-12 | 2010-08-12 | Garmin Ltd. | Friend-finding system |
US20100228582A1 (en) * | 2009-03-06 | 2010-09-09 | Yahoo! Inc. | System and method for contextual advertising based on status messages |
US20120047087A1 (en) * | 2009-03-25 | 2012-02-23 | Waldeck Technology Llc | Smart encounters |
WO2010116371A1 (en) | 2009-04-06 | 2010-10-14 | Tracx Systems Ltd. | Method and system for tracking online social interactions |
US9097553B2 (en) * | 2009-04-20 | 2015-08-04 | Verizon Patent And Licensing Inc. | Navigation based on direction of travel/user-defined path |
US20120046995A1 (en) * | 2009-04-29 | 2012-02-23 | Waldeck Technology, Llc | Anonymous crowd comparison |
US20100287256A1 (en) * | 2009-05-05 | 2010-11-11 | Nokia Corporation | Method and apparatus for providing social networking content |
US10217085B2 (en) * | 2009-06-22 | 2019-02-26 | Nokia Technologies Oy | Method and apparatus for determining social networking relationships |
US20110004692A1 (en) * | 2009-07-01 | 2011-01-06 | Tom Occhino | Gathering Information about Connections in a Social Networking Service |
US20120064919A1 (en) * | 2009-08-24 | 2012-03-15 | Waldeck Technology, Llc | Crowd creation system for an aggregate profiling service |
US20110055723A1 (en) * | 2009-08-25 | 2011-03-03 | Simon Samuel Lightstone | Collaboratively interactive micro-blog posts |
US9119027B2 (en) * | 2009-10-06 | 2015-08-25 | Facebook, Inc. | Sharing of location-based content item in social networking service |
US8560608B2 (en) | 2009-11-06 | 2013-10-15 | Waldeck Technology, Llc | Crowd formation based on physical boundaries and other rules |
US8990708B2 (en) * | 2009-12-09 | 2015-03-24 | Disney Enterprises, Inc. | User generated media list interfaces with social networking |
US20120063367A1 (en) * | 2009-12-22 | 2012-03-15 | Waldeck Technology, Llc | Crowd and profile based communication addresses |
US8543143B2 (en) * | 2009-12-23 | 2013-09-24 | Nokia Corporation | Method and apparatus for grouping points-of-interest according to area names |
US20110161427A1 (en) * | 2009-12-28 | 2011-06-30 | Nokia Corporation | Method and apparatus for location-aware messaging |
US8200247B1 (en) * | 2010-02-08 | 2012-06-12 | Google Inc. | Confirming a venue of user location |
US8156240B2 (en) * | 2010-03-01 | 2012-04-10 | Yahoo! Inc. | Mechanism for supporting user content feeds |
US20120066303A1 (en) | 2010-03-03 | 2012-03-15 | Waldeck Technology, Llc | Synchronized group location updates |
US20130332279A1 (en) * | 2012-06-07 | 2013-12-12 | Nokia Corporation | Method and apparatus for location-based advertisements for dynamic points of interest |
-
2011
- 2011-02-15 US US13/027,756 patent/US20120066303A1/en not_active Abandoned
- 2011-02-23 US US13/032,744 patent/US20120066614A1/en not_active Abandoned
- 2011-03-01 US US13/037,546 patent/US9203793B2/en active Active
- 2011-03-01 US US13/037,520 patent/US8898288B2/en not_active Expired - Fee Related
- 2011-03-03 US US13/039,356 patent/US8566309B2/en not_active Expired - Fee Related
-
2013
- 2013-09-17 US US14/028,866 patent/US9407590B2/en not_active Expired - Fee Related
-
2014
- 2014-11-18 US US14/546,580 patent/US20150074214A1/en not_active Abandoned
-
2015
- 2015-11-30 US US14/954,084 patent/US9407598B2/en active Active
Patent Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20090164574A1 (en) * | 2007-12-21 | 2009-06-25 | Concert Technology Corporation | System and method for identifying transient friends |
US20090312033A1 (en) * | 2008-06-16 | 2009-12-17 | Microsoft Corporation | Mashup application and service for wireless devices |
Cited By (12)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20110217965A1 (en) * | 2010-03-03 | 2011-09-08 | Htc Corporation | Method, system and computer-readable medium for synchronizing spot information |
US8666377B2 (en) * | 2010-03-03 | 2014-03-04 | Htc Corporation | Method, system and computer-readable medium for synchronizing spot information |
US20120115473A1 (en) * | 2010-11-04 | 2012-05-10 | Samsung Electronics Co., Ltd. | Method and apparatus for supporting location information in machine to machine communication system |
US20120302162A1 (en) * | 2011-05-23 | 2012-11-29 | Chao-Feng Chueh | Method of Performing a Data Transaction Between a Portable Storage Device and an Electronic Device |
US8676227B2 (en) * | 2011-05-23 | 2014-03-18 | Transcend Information, Inc. | Method of performing a data transaction between a portable storage device and an electronic device |
US20130262706A1 (en) * | 2012-04-02 | 2013-10-03 | F-Secure Corporation | Data Syncronisation |
US9021136B2 (en) * | 2012-04-02 | 2015-04-28 | F-Secure Corporation | Data synchronisation |
US10096041B2 (en) | 2012-07-31 | 2018-10-09 | The Spoken Thought, Inc. | Method of advertising to a targeted buyer |
US20150219458A1 (en) * | 2014-01-31 | 2015-08-06 | Aruba Networks Inc. | Navigating to a moving target |
US20170332343A1 (en) * | 2015-03-03 | 2017-11-16 | Facebook, Inc. | Techniques to manage client location detection |
US10123299B2 (en) * | 2015-03-03 | 2018-11-06 | Facebook, Inc. | Techniques to manage client location detection |
CN106372557A (en) * | 2016-08-30 | 2017-02-01 | 李明 | Method, device and system for acquiring certificate card information |
Also Published As
Publication number | Publication date |
---|---|
US20120066212A1 (en) | 2012-03-15 |
US8898288B2 (en) | 2014-11-25 |
US8566309B2 (en) | 2013-10-22 |
US9407590B2 (en) | 2016-08-02 |
US9407598B2 (en) | 2016-08-02 |
US20160099905A1 (en) | 2016-04-07 |
US20120066614A1 (en) | 2012-03-15 |
US20120066316A1 (en) | 2012-03-15 |
US20120066312A1 (en) | 2012-03-15 |
US20140019615A1 (en) | 2014-01-16 |
US9203793B2 (en) | 2015-12-01 |
US20150074214A1 (en) | 2015-03-12 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US20120066303A1 (en) | Synchronized group location updates | |
US12051120B1 (en) | Medium and device for generating an image for a geographic location | |
US8711737B2 (en) | Crowd formation based on wireless context information | |
US8880101B2 (en) | Method and apparatus for managing attributes and functionalities of predetermined geographical areas | |
US8560608B2 (en) | Crowd formation based on physical boundaries and other rules | |
JP5653647B2 (en) | Predicting the presence of mobile user equipment | |
KR101891669B1 (en) | Mobile ad hoc networking | |
US8260553B2 (en) | Methods, apparatuses, and computer program products for providing user location information | |
US20160234060A1 (en) | Setting a reminder that is triggered by a target user device | |
US10491473B2 (en) | Role and proximity-based management of networks | |
KR20110028216A (en) | Dynamic event planning with location awareness | |
US9270634B1 (en) | Building a proximate social networking database based on relative distance profiling of two or more operably coupled computers | |
US9949069B2 (en) | Population estimation apparatus, program and population estimation method | |
US20130101110A1 (en) | System and method for attaching geographic information to customer reports | |
US20180195867A1 (en) | Systems and methods for indoor and outdoor mobile device navigation | |
US20110264615A1 (en) | Location source determination | |
WO2012088667A1 (en) | Estimating the geographical position of an apparatus based on its proximity to other apparatuses | |
CN106534382B (en) | Method, system and home gateway for determining location information of a home group | |
US20140329211A1 (en) | Providing location-relevant goal fulfillment recommendations while inside a non-residential location | |
WO2013184334A2 (en) | Setting a reminder that is triggered by a target user device | |
US11995212B2 (en) | System and process for selective location-based anonymity and privacy |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: WALDECK TECHNOLOGY, LLC, DELAWARE Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:PURDY, SEAN T.;REEL/FRAME:025811/0307 Effective date: 20110211 |
|
AS | Assignment |
Owner name: CONCERT DEBT, LLC, NEW HAMPSHIRE Free format text: SECURITY INTEREST;ASSIGNOR:WALDECK TECHNOLOGY, LLC;REEL/FRAME:036433/0313 Effective date: 20150501 Owner name: CONCERT DEBT, LLC, NEW HAMPSHIRE Free format text: SECURITY INTEREST;ASSIGNOR:WALDECK TECHNOLOGY, LLC;REEL/FRAME:036433/0382 Effective date: 20150801 |
|
AS | Assignment |
Owner name: CONCERT DEBT, LLC, NEW HAMPSHIRE Free format text: SECURITY INTEREST;ASSIGNOR:CONCERT TECHNOLOGY CORPORATION;REEL/FRAME:036515/0471 Effective date: 20150501 Owner name: CONCERT DEBT, LLC, NEW HAMPSHIRE Free format text: SECURITY INTEREST;ASSIGNOR:CONCERT TECHNOLOGY CORPORATION;REEL/FRAME:036515/0495 Effective date: 20150801 |
|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- AFTER EXAMINER'S ANSWER OR BOARD OF APPEALS DECISION |
|
AS | Assignment |
Owner name: CONCERT TECHNOLOGY CORPORATION, NEW HAMPSHIRE Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:WALDECK TECHNOLOGY, LLC;REEL/FRAME:051395/0425 Effective date: 20191203 |