Device based trigger for location push event

Information

  • Patent Grant
  • 8892121
  • Patent Number
    8,892,121
  • Date Filed
    Friday, January 13, 2012
    12 years ago
  • Date Issued
    Tuesday, November 18, 2014
    9 years ago
Abstract
A software LBS trigger is initiated by a wireless device to request a set of proximate location information points relating to, e.g., points of interest, location tagged blogs, etc., based on the user's current location. The LBS trigger may be initiated when the user moves, and may include speed of the user to define a proximate area within which the user's device will be presented with relevant location information upon reaching. The size of the proximate area may be based on available memory in the wireless device, and/or on network bandwidth limitations. If walking, a smaller proximate area is defined, or if moving fast, the area of close proximity is larger. The location-based information points are stored locally on the user's device, and presentation to the user when the user gets closely proximate to the relevant information point.
Description
BACKGROUND OF THE INVENTION

1. Field of the Invention


This invention relates to wireless telecommunication with location based services (LBS) applications, with particular relevance to the provision of local points of interest, location based advertising, location based blogs, location based commerce, etc.


2. Background of Related Art


Marketers are always trying to reach customers in new and innovative ways. To this end, certain technologies are emerging to allow targeted marketing and advertising to consumers based on their location.


For instance, a conventional Bluetooth MediaServer (available from www.wiremedia.com) distributes advertising content via Bluetooth communication to proximate wireless devices that use compatible Bluetooth wireless technology. But such systems require the relevant wireless device to get very close, i.e., within range of the given Bluetooth MediaServer transmitter. And even then, a willing customer must have a compatible Bluetooth enabled wireless devices to receive the marketing or advertising.


Other methods require a user to directly input their location into a web page via a computer browser application, e.g., Internet based advertising systems (e.g., a Google search). The search engine web page (e.g., Google) provides results of the search, together with location-specific sponsored advertising based on a zip code entered by a user. This method requires the user to have a browser-capable device, to manually enter their own location in very broad terms (e.g., zip code), and depends upon the user to not make an input mistake.


There is a need for a method and apparatus for sending marketing, advertising, blogs, etc. information directed to relevant users based on their location, without unduly burdening a relevant wireless network.


SUMMARY OF THE INVENTION

In accordance with the principles of the present invention, a location based service comprises a location information database comprising a plurality of location information points. A trigger response module is adapted to respond to a received location based services (LBS) trigger by obtaining proximate ones of the plurality of location information points culled into a sub-plurality corresponding to those of the plurality of location information points that are within a given proximity to a current location of a triggering wireless device. The assembled proximate location information points are downloaded to a wireless device in response to the generated LBS trigger. The trigger could come from a network element as well as from a wireless device, e.g., a registration notification to a new cell site.


A method of providing location based information to a wireless device according to another aspect comprises receiving a location based services (LBS) trigger generated by a wireless device. A current location of the wireless device is obtained. A plurality of location information points that are within a given proximity to the current location of the triggering wireless device are obtained. The plurality of location information points are downloaded to the wireless device that generated the LBS trigger.


A method of obtaining location based information for use by a wireless device according to yet another aspect comprises obtaining a current location of a wireless device. A location based services (LBS) trigger is generated. The LBS trigger is passed over a wireless network to a location information database. A plurality of location information points that are all substantially within a given range of the current location of the triggering wireless device is received.


A method of using location information points obtained by a wireless device comprise those points whose information has been downloaded based on a trigger associated with locality, velocity or some combination of other criteria. A location update is obtained at the wireless device. This location update is compared to the plurality of location information points previously downloaded using a defined set of criteria. If a match is found, an LBS trigger is generated and results in a specific action. That action could include passing the trigger or other identifying information over a wireless network to a receiving server, application or network element for further processing.


A method of using location information points obtained by a wireless device comprise those points whose information has been downloaded based on a trigger associated with locality, velocity or some combination of other criteria. A location update is obtained at the wireless device. This location update is compared to the plurality of location information points previously downloaded using a defined set of criteria. If a match is found, an LBS trigger is generated and results in the display of information downloaded with the location information point.





BRIEF DESCRIPTION OF THE DRAWINGS

Features and advantages of the present invention will become apparent to those skilled in the art from the following description with reference to the drawings, in which:



FIG. 1 depicts device based triggering of a location push event, triggering transmission of proximate points of interest within a range of the device, to the device, in accordance with the principles of the present invention.



FIG. 2 shows in a first embodiment a grid of gross location areas, some (or all) of which contain one or more points of interest, in accordance with the principles of the present invention.



FIG. 3 shows in a first embodiment, detail of an exemplary gross location area, or range, shown in FIG. 2, with proximate areas surrounding each point of interest sized based upon a current relatively slow motion speed (e.g., walking) of the relevant device, in accordance with the principles of the present invention.



FIG. 4 shows in detail an exemplary gross location area, or range, shown in FIG. 2, with proximate areas surrounding each point of interest sized based upon a current relatively fast motion speed (e.g., driving) of the relevant device, in accordance with the principles of the present invention.



FIGS. 5A to 5H show in another embodiment, detail of gross location areas determined based on a current location of the device, and relative speed of the device (e.g., driving speed), in accordance with the principles of the present invention.



FIG. 6 shows a state diagram of the device based triggered push location event, in accordance with the principles of the present invention.



FIG. 7 shows a flow chart of exemplary device based triggered push location event, in accordance with the principles of the present invention.





DETAILED DESCRIPTION OF ILLUSTRATIVE EMBODIMENTS

There are multiple methods for determining precise location (e.g., assisted GPS (AGPS), Time Difference of Arrival (TDOA), etc.), some of which are network centric and some of which are device centric. The recent trend in wireless devices has been driving more and more processing power into the device. This trend has been driven by a combination of Moore's Law and the desire to continue to offer more sophisticated applications to the wireless end user. The inventor herein has appreciated that the end result will be that the device is more active and in some cases the primary engine to calculate its own precise location; it is more likely to be the source or retainer of this location information; and it is more capable of using this locally maintained location information.


Accordingly, the invention provides a method for providing location triggered information, e.g., location specific advertising, blog, video, multimedia content, web page, automatically dialed phone call, pop-up, or other relevant location-based content using a triggered push when the handset itself determines that it has reached the vicinity of a previously downloaded point of interest. The pre-fetching and queuing of points of interest location information based on general location reduces the traffic on the network associated with repeatedly communicating location for comparison to network hosted location points. The present invention leverages increased processing capacity of a wireless device coupled with the increasing role of wireless devices in determining its precise location to facilitate local, autonomous triggering of location specific events at the device.


As a device traverses a wireless network, its active connection is “handed off” between radio network communications endpoints. These endpoints can be towers for PCS, satellites for LEOs or paging networks, wireless routers for WiFi, or other radio network controller components. Regardless of the network, data is typically maintained either within the network or at the device (typically both) such that the device can be located to deliver calls, messages, data, etc. Similarly, the device retains this information such that it can provide this as part of a device endpoint specific transaction. For means of simplicity, the radio connection endpoint will be generically referred to as the “gross location”. An example of this “gross location” is a cell site and sector combination for a terrestrial PCS network. An important aspect is that the device knows its location and tracks its “gross location”, not just the network. In this manner, the device is capable of having a “kernel” that tracks the gross location to trigger on the change. This enables the invention to be implemented solely in software in the wireless device.


The term location based services (LBS) generally relates to consumer and commercial applications that utilize the knowledge of a wireless device user's geographic position. Location information such as street address can be entered directly by a user, but as referred to herein location based services (LBS) relates to location information that is automatically obtained electronically, e.g., using a global positioning system (GPS) in a user's wireless device such as a cell phone or personal digital assistant (PDA). Of course, other methods of precise location are possible, within the principles of the present invention.



FIG. 1 depicts device based triggering of a location push event, triggering transmission of proximate points of interest within a range of the device, to the device, in accordance with the principles of the present invention.


In particular, as shown in FIG. 1, a wireless device 113 having the ability to be located notes a change in location and generates an LBS trigger 100. The device passes the same to an appropriate location based information database 150. The gross location could also be determined by the network such as a cell site/sector hand off. In response to a triggered event on the handset, requested location information 102 (e.g., proximate points of interest) relating to the location of the handset is extracted from the location information database 150 and downloaded to the wireless device 113.


The disclosed embodiments describe use of a software LBS trigger 100 initiated by a user's wireless device 113 and passed to a network database 150. The trigger 100 may take one of two forms. The trigger 100 may request the network database 150 to provide the triggering wireless device 113 with a revised set of proximate location information points within a given region surrounding the user's wireless device 113 current location, based on the user's current location. As the user moves about, from time to time the user will download a revised set of locations of points of interest to provide a sufficient buffer around the handset's current position such that the device can move about and push triggers autonomously for a significant period of time. Alternatively, the trigger 100 may request location based information (e.g., a blog, text, pop-up, video, etc.) relating to the handset having reached a vicinity of a location information point of interest previously downloaded.


Yet another variant is also anticipated wherein the trigger requests a specific application to launch. This can be local to the device, or launched within the network. downloaded.


The location information points comprise information relevant to a particular location. They may comprise only a lat/lon of the location, and specific direction as to what to request in a location push upon reaching a vicinity of the lat/lon of the location information point. The location information point may include additional information previously downloaded to the handset, e.g., text message, video, etc. The additional information may be downloaded to the handset over time, in the background of other operations on the handset, to appear to the user to operate more smoothly.


Thus, the location information points can be abstracted to represent only the XY (latitude/longitude) of the point of interest (POI). The key is to let the handset know when it has reached a triggering location.


Location information points may be points of interest, location tagged blogs, commercial locations with advertising focused on the surrounding area serviced by that commercial location, video, multimedia, audio, a phone number to automatically dial, a web page to automatically access, a pop-up to automatically present to the user, an application to launch, etc.


The LBS trigger 100 is initiated at appropriate times by the user's wireless device 113 in response to its detection of significant movement of the user, e.g., the mover is walking, driving, etc. as detected by a locating device (e.g., GPS). The LBS trigger 100 may of course be initiated at additional other times by the user's wireless device 113, e.g., at the startup of a relevant location based services application on the user's wireless device 113, etc.


The LBS trigger 100 to request a revised set of surrounding points of interest is occasionally transmitted as necessary, but preferably is transmitted only when the ‘gross location’ changes. The ‘gross location’ represents a geographic region that could be network topology driven such as a cell site and sector. If it does not change, no triggered event has occurred.


Sufficient location based information is returned by the network database 150 to the triggering wireless device 113, such that the triggering wireless device 113 will receive and buffer location based lat/lon information (and potentially content to be presented to the user upon reaching a vicinity of that lat/lon) relating to areas that the wireless device 113 is not yet proximate to, but which the wireless device 113 may become proximate to, e.g., all of those triggered locations within the region defined as the ‘gross location’. The idea is to provide the wireless device 113 with the anticipated location based information that it immediately needs based on proximity, both to reduce network traffic over time, as well as to provide the user with a smoother, faster operating user interface.


The location based information may be maintained and presented in pre-defined fixed grids, or it may be determined to be proximate to a user's current location on a trigger-by-trigger basis.


With respect to the use of pre-defined fixed grids, FIG. 2 shows in a first embodiment a grid of gross location areas, or ranges, some (or all) of which contain one or more points of interest, in accordance with the principles of the present invention.


In particular, as shown in FIG. 2, a given geographical area is shown graphically broken into a grid of gross location areas, or ranges. FIG. 2 is shown graphically for ease of description: the location based information may be maintained in an appropriate database in any suitable form, e.g., textual, as latitude/longitude with textual information, textual and photographic, videographic, etc.


A first range 302 shown in FIG. 2 includes three location relevant information points 310-312. For explanation, a number of ranges are shown, some of which include no information points, and others of which contain various numbers of additional information points 313-320.


The information points 310-320 each may contain location based information in any suitable electronic media form (e.g., text, photo, video, audio, short message, email, etc.), but importantly ties that information to a respective given location 310-312. The information point can be a trigger for initiating a different application on the device or in the network, as well as information such as text, photo, email, etc.


The given locations 310-312 may be an exact latitude/longitudinal point, a range of latitude/longitudinal values, or even a vectored range or geometric shape (e.g., a perimeter of a building).



FIG. 3 shows in a first embodiment, detail of an exemplary gross location area, or range, shown in FIG. 2, with proximate areas surrounding each point of interest sized based upon a current relatively slow motion speed (e.g., walking) of the relevant device, in accordance with the principles of the present invention.


In particular, as shown in FIG. 3, the exemplary range 302 of location based information points 310-312 are shown graphically with respective proximate distances 310a-312a depicted around each location based information point 310-312. The proximate distances 310a-312a may be fixed by the network, configurable by the user or network, specific to the needs of an application (such as a walking tour guide application versus a friend finder. The tour guide wants you at a specific point while friend finder might be within a specific range.), or determined based on additional information relating to the user (e.g., their speed).


In particular, the LBS trigger 100 from the triggering wireless device 113 may include additional information relating to the user's wireless device 113 and/or location. For example, the LBS trigger 100 may include information relating to a current or recent speed of the user (e.g., a current speed, average speed, median speed, range of speed, etc.) Speed of the user information may be used to define a suitable range around the user's current location for which the triggering wireless device 113 will be presented with relevant location information. The size of the range 302 for which location information points is provided is preferably based on network topology (to minimize traffic overhead), but may also make use of additional information, as well as any relevant physical equipment limitations such as the available amount of memory in the triggering wireless device 113, network bandwidth limitations, etc.


If the user is moving slowly (e.g., walking) as depicted in FIG. 3, a smaller proximate area 310a-312a may be defined, with relevant location-based information points (e.g., triggers for either presenting previously downloaded content relating to points of interest, location tagged blogs, video, audio, pop-up, etc.) within that smaller proximate area 310a-312a being provided so that the device application can autonomously present the same to the user at an appropriate time in the future if/when the user becomes proximate to a location point 310-312 for which location information was previously obtained. On the other hand, if the user is moving fast (e.g., driving), a larger area of proximity 310b-312b may be defined (FIG. 4), as compared to a smaller area of proximity 310a-312a (FIG. 3) defined for a slow moving user (e.g., walking), providing the user with the location information for locations that are comparatively farther from the user's current location. In particular, FIG. 4 shows in detail an exemplary gross location area, or range, shown in FIG. 2, with proximate areas surrounding each point of interest sized based upon a current relatively fast motion speed (e.g., driving) of the relevant device 113, in accordance with the principles of the present invention.


While FIGS. 3 and 4 depict modification of a range of location information point triggers based on velocity, other information may be additionally or alternatively considered. For instance, network topology of the area surrounding the user's current location may additionally or alternatively be considered. If the network is considered to be a series of overlapping cells with points of interest in each of the cells, then as a person/device traverses the cells, a handoff occurs as normal network operation. This handoff provides gross location based on network topology. Thus, speed is essential to consider since if the user/device is moving at a high rate of speed (e.g., in a car, high speed train, airplane, etc.), it may likely necessitate the delivery of location point of interest data for multiple network cells so that the handset will have previously downloaded location information point triggers relating to the multiple cells.


Importantly, the embodiments describe storage of the location-based information points 310-312 and associated location based information locally on the user's device subject to network and device limitations, and presentation of the location based information to the user when the user gets closely proximate, i.e., within the proximate area 310a-312a associated with to the respective information point 310-312. Alternatively, the downloaded and locally stored location-based information points 310-312 and associated information may comprise the location point, proximate area 310a-312a, and a reference or semaphore representing a downloaded local or network resident application to trigger based on proximity to the respective information point


Location based information may alternatively be provided in a custom fashion centered on a user's current location on a trigger-by-trigger basis. For instance, FIGS. 5A to 5H show in another embodiment, detail of a proximate range 510 determined for a given wireless device 113 as it moves about. The size (and shape) of the proximate range 510 may be pre-determined by the service provider or user, configured by the service provider and/or user, and/or adjusted based on current information received from the wireless device 113 (e.g., based on the speed of the wireless device 113).


For ease of description and explanation, the points of interest 310-320 are depicted in the same locations in FIGS. 5A to 5H as they were in the grid of ranges shown in FIG. 2, but without a pre-defined grid. Instead, in this embodiment, the range for which location information points are provided to the user is determined based on a current location of the wireless device 113 at the time that the LBS trigger 100 is sent.


Note that more frequent transmission of the LBS trigger 100 from the wireless device 113 will ensure that the wireless device 113 will not come upon a particular location for which location information is in the location based information database 150 but for which the wireless device 113 had not received location information relating to that location. The size of the proximate range 510 should be sized to allow the wireless device 113 a significant amount of time to move about without having to send another LBS trigger 100 in a way that it won't ordinarily be in a location outside the proximate range 510 at the time of the last download of location based information.


As shown in FIG. 5A, the wireless device 113 generates an LBS trigger 100, and receives location information for any/all location points within the proximate range 510a at that time. At that time, the proximate range 510a includes location points 310-312.


In FIG. 5B, the wireless device 113 again generates an LBS trigger 100 after having moved from its location shown in FIG. 5A. At this time, the wireless device 113 receives location information relating to location points 310, 311 and 313 contained within the proximate range 510b at the time that the LBS trigger 100 was generated.


In FIG. 5C, the wireless device 113 has again moved, again generated an LBS trigger 100, and this time received location information relating to location point 313 located within the proximate range 510c.


In FIG. 5D, the proximate range 510d defined at the time that yet another LBS trigger 100 is generated, includes location points 314 and 315.


In FIG. 5E, the wireless device 113 has moved south, has generated another LBS trigger 100, causing the definition of a proximate range 510e including information points 314 and 315.


In FIG. 5F, a proximate range 510f is defined in response to another LBS trigger 100, the proximate range 510f including location point 319 only.


In FIG. 5G, the new proximate range 510g includes location point 319 only (again).


In FIG. 5H, the wireless device 113 has generated an LBS trigger 100, defining a proximate range 510h, but this time there are no location points in the database with latitude/longitude location points located within this proximate range 510h.



FIG. 6 shows a state diagram of the device based triggered push location event, in accordance with the principles of the present invention.


In particular, as shown in FIG. 6, in accordance with the invention, as shown by state 600, an application (e.g., a small application) is activated on the device that sends an LBS trigger 100 that requests download of “point of interest” trigger points based on changes in the current location, or “gross location”, of the wireless device 113.


The request preferably not only includes the current location of the wireless device 113, since this is maintained by the device 113, but it also preferably includes a unique identifier of the device 113. The format of this tuple may be defined in any appropriate manner.


The device provided information is used to pre-fetch a table of location information points based on a device/user specified profile. As described, the table of location information points includes only those precise location information points X/Y coordinates within a proximity of the current location of the wireless device 113.


As the wireless device 113 traverses the network, the device 113 updates (tracks) precise location at the device level but does not need to communicate this data to the network. (This can be said to infer that assistance data has been downloaded, that precise location is enabled, etc.) The LBS application compares the current location X/Y of the wireless device 113 to currently held location information points (e.g., 310-312) to determine if/when to trigger an event at the wireless device 113 based on a proximity calculation between the current location X/Y of the wireless device 113 and the relevant location information point X/Y 310-312. In this embodiment, a match between the current location of the wireless device 113 and a stored location information point 310-312 results in a request to the serving network with a request to download relevant location information for that location. In this way, a specific trigger for download of location relevant information occurs only when a wireless device 113 first reaches a proximity of a given location information point. The appropriate trigger action is then taken, whether it is to download a location specific application, advertisement, coupon, game trigger event, blog, etc. to the handset. In this manner, the desired location specific event has been triggered by the device and executed while minimizing the amount of communications and data required for download to the handset.



FIG. 7 shows a flow chart of exemplary device based triggered push location event, in accordance with the principles of the present invention.


In particular, LBS triggers 100 may be generated when a significant change in location is detected by the wireless device 113. As shown in step 700 of FIG. 7, a periodic timer in the wireless device 113 occasionally determines if the current location of the wireless device 113 is within a proximate area of any location information points that have been previously downloaded to the wireless device 113. The idea is that the device is recalculating location periodically anyway, so the trigger can be based on time or some other factor such as motion, velocity, or user action.


In step 702, upon expiration of the timer, a current location of the wireless device 113 is determined.


In step 704, the current location of the wireless device 113 is compared to the X/Y longitude/latitude, plus any relevant proximate area surrounding each location information points, of any/all location information points (e.g., 310-312).


In step 706, the current location of the wireless device 113 is compared to a proximate area around each location information point stored in a local trigger table.


In step 708, it is determined if the current location of the wireless device 113 matched a given location information point. If not, the process sits idle until the timer in step 700 again times out.


However, if so, then the process proceeds to step 710, appropriate action is taken to present the associated location information to the user. The trigger could also kick off an entirely new application within the network, e.g., a tracking software application if a person of interest moves outside of a defined perimeter.


For example, specific text, video, or audio information may be requested for download from the location information database 150 at that time to the wireless device 113. This process of obtaining the location information, or kickstarting as shown in step 712, is referred to herein as a kickstart trigger application. This process may be a semaphore, though it need not be.


Note that the timer in step 700 continues to run and check matches with other location points, regardless of whether or not previously location information is being presented to the user (i.e., the location information may overlap).


In step 714, the handset or network application that is waiting for a trigger event to occur (i.e., a match to a location information point) is started, and does its independent processing. This may include location fixes, etc. that are also used for trigger evaluation. It is preferably an independent application that terminates upon completion according to its own rules.


In step 716, the LBS application ends.


The LBS application in the wireless device 113 can take the form of an applet (j2me), a BREW extension, a symbian application, or other coded logic that could be embedded or downloaded and executed on the device. In either case, the LBS application may be made available to other application developers to take advantage of a common XY downloadable table.


The applet table, or list of location information points, can include context when downloaded to the wireless device 113. This is similar to the XY table except that the table instead is a set of “tuples” that define specific characteristics useful to other applications. This information may include privacy settings, user, device info, location, speed, etc. that can be provided as part of the trigger to the network. Alternatively, a match between current location and a previously loaded location information point can be served by the downloaded application on the wireless device 113 if the specific actionable location based information has already been provided as part of a response to the LBS trigger 100.


The present invention is of particular use by developers to create applications that leverage location specific content for mobile users, with particular benefit in a proximity application.


While the invention has been described with reference to the exemplary embodiments thereof, those skilled in the art will be able to make various modifications to the described embodiments of the invention without departing from the true spirit and scope of the invention.

Claims
  • 1. A wireless device location based service, comprising: a location based services (LBS) trigger module, in a given wireless device, to locally trigger retrieval of a plurality of point of interest (POI) information proximate to a predicted future position of said given wireless device;a culled memory module to cull said plurality of POI information into a future proximate sub-plurality of POI information based on a current path of travel, and speed, of said wireless device; andproviding only said sub-plurality of POI information for display.
  • 2. The wireless device location based service according to claim 1, wherein: said sub-plurality of said POI information is inversely proportional to said speed of said wireless device.
  • 3. The wireless device location based service according to claim 1, wherein said POI information comprises: textual content.
  • 4. The wireless device location based service according to claim 1, wherein said POI information comprises: audio content.
  • 5. The wireless device location based service according to claim 1, wherein said POI information comprises: video content.
  • 6. The wireless device location based service according to claim 1, wherein said POI information comprises: a pointer reference to uniquely identify a separate application.
  • 7. The wireless device location based service according to claim 1, wherein said POI information comprises: a universal resource locator (URL) link.
  • 8. A method of retrieving location based information in a wireless device, comprising: locally triggering, by said wireless device, retrieval of a plurality of point of interest (POI) information proximate to a predicted future position of a given wireless device;culling said plurality of POI information into a future proximate sub-plurality of POI information based on a current path of travel, and speed, of said given wireless device; andproviding only said sub-plurality of POI information for display.
  • 9. The method of retrieving location based information in a wireless device according to claim 8, wherein: said proximity is inversely proportional to said speed of said given wireless device.
  • 10. The method of retrieving location based information in a wireless device according to claim 8, wherein said POI information comprises: textual content.
  • 11. The method of retrieving location based information in a wireless device according to claim 8, wherein said POI information comprises: audio content.
  • 12. The method of retrieving location based information in a wireless device according to claim 8, wherein said POI information comprises: video content.
  • 13. The method of retrieving location based information in a wireless device according to claim 8, wherein said POI information comprises: a pointer reference to uniquely identify a separate application.
  • 14. The method of retrieving location based information in a wireless device according to claim 8, wherein said POI information comprises: a universal resource locator (URL) link.
  • 15. The method of retrieving location based information in a wireless device according to claim 8, further comprising: obtaining a unique identifier of said (liven wireless device.
  • 16. The method of retrieving location based information in a wireless device according to claim 8, further comprising: providing a unique identifier associated with said (liven wireless device prior to retrieval of said plurality of POI information.
Parent Case Info

This application is a continuation of U.S. patent application Ser. No. 11/544,724, entitled “Device Based Trigger for Location Push Event,” filed on Oct. 10, 2006; which claims priority from U.S. Provisional Patent Appl. No. 60/845,527, filed Sep. 19, 2006, entitled “Device Based Triggered Location Push Event” to Drew Morin, the entirety of both of which is are expressly incorporated herein by reference.

US Referenced Citations (203)
Number Name Date Kind
1103073 O'Connel Jul 1914 A
4494119 Wimbush Jan 1985 A
4651156 Martinez Mar 1987 A
4706275 Kamil Nov 1987 A
4891638 Davis Jan 1990 A
4891650 Sheffer Jan 1990 A
4952928 Carroll et al. Aug 1990 A
5014206 Scribner et al. May 1991 A
5043736 Darnell et al. Aug 1991 A
5055851 Sheffer Oct 1991 A
5068656 Sutherland Nov 1991 A
5068891 Marshall Nov 1991 A
5070329 Jasinaki Dec 1991 A
5081667 Droro et al. Jan 1992 A
5119104 Heller Jun 1992 A
5144283 Arens et al. Sep 1992 A
5177478 Wagai et al. Jan 1993 A
5193215 Olmer Mar 1993 A
5208756 Song May 1993 A
5214789 George May 1993 A
5218367 Sheffer et al. Jun 1993 A
5223844 Mansell et al. Jun 1993 A
5235630 Moodey et al. Aug 1993 A
5266944 Carroll et al. Nov 1993 A
5289527 Tiedemann, Jr. Feb 1994 A
5293642 Lo Mar 1994 A
5299132 Wortham Mar 1994 A
5325302 Izidon et al. Jun 1994 A
5334974 Simms et al. Aug 1994 A
5343493 Karimullah Aug 1994 A
5347568 Moody et al. Sep 1994 A
5351235 Lahtinen Sep 1994 A
5361212 Class et al. Nov 1994 A
5363425 Mufti et al. Nov 1994 A
5374936 Feng Dec 1994 A
5379451 Nakagoshi et al. Jan 1995 A
5381338 Wysocki et al. Jan 1995 A
5387993 Heller et al. Feb 1995 A
5388147 Grimes Feb 1995 A
5390339 Bruckert et al. Feb 1995 A
5394158 Chia Feb 1995 A
5396227 Carroll et al. Mar 1995 A
5398190 Wortham Mar 1995 A
5406614 Hara Apr 1995 A
5418537 Bird May 1995 A
5423076 Westergreen et al. Jun 1995 A
5432841 Rimer Jul 1995 A
5434789 Fraker et al. Jul 1995 A
5454024 Lebowitz Sep 1995 A
5461390 Hoshen Oct 1995 A
5470233 Fruchterman et al. Nov 1995 A
5479408 Will Dec 1995 A
5479482 Grimes Dec 1995 A
5485161 Vaughn Jan 1996 A
5485163 Singer et al. Jan 1996 A
5488563 Chazelle et al. Jan 1996 A
5497149 Fast Mar 1996 A
5508931 Snider Apr 1996 A
5513243 Kage Apr 1996 A
5515287 Hakoyama et al. May 1996 A
5519403 Bickley et al. May 1996 A
5532690 Hertel Jul 1996 A
5535434 Siddoway et al. Jul 1996 A
5539398 Hall et al. Jul 1996 A
5543776 L'Esperance et al. Aug 1996 A
5552772 Janky et al. Sep 1996 A
5555286 Tendler Sep 1996 A
5568119 Schipper et al. Oct 1996 A
5574648 Pilley Nov 1996 A
5579372 Astrom Nov 1996 A
5588009 Will Dec 1996 A
5590417 Rydbeck Dec 1996 A
5592535 Klotz Jan 1997 A
5604486 Lauro Feb 1997 A
5606313 Allen et al. Feb 1997 A
5606850 Nakamura Mar 1997 A
5610815 Gudat et al. Mar 1997 A
5614890 Fox Mar 1997 A
5615116 Gudat et al. Mar 1997 A
5621793 Bednarek et al. Apr 1997 A
5628051 Salin May 1997 A
5633912 Tsoi May 1997 A
5673306 Amadon et al. Sep 1997 A
5682600 Salin Oct 1997 A
5692037 Friend Nov 1997 A
5694546 Reisman Dec 1997 A
5724667 Furuno Mar 1998 A
5740534 Ayerst et al. Apr 1998 A
5761618 Lynch et al. Jun 1998 A
5767795 Schaphorst Jun 1998 A
5768509 Gunluk Jun 1998 A
5774533 Patel Jun 1998 A
5787357 Salin Jul 1998 A
5794142 Vantilla et al. Aug 1998 A
5797091 Clise et al. Aug 1998 A
5797094 Houde et al. Aug 1998 A
5797096 Lupien et al. Aug 1998 A
5802492 DeLorme et al. Sep 1998 A
5806000 Vo et al. Sep 1998 A
5822700 Hult et al. Oct 1998 A
5828740 Khuc et al. Oct 1998 A
5867495 Elliott et al. Feb 1999 A
5905736 Rohen et al. May 1999 A
5920821 Seazholtz et al. Jul 1999 A
5930701 Skog Jul 1999 A
5943399 Bannister et al. Aug 1999 A
5946629 Sawyer et al. Aug 1999 A
5946630 Willars et al. Aug 1999 A
5949326 Wicks et al. Sep 1999 A
5950130 Coursey Sep 1999 A
5953398 Hill Sep 1999 A
5960074 Clark Sep 1999 A
5966663 Gleason Oct 1999 A
5974054 Couts et al. Oct 1999 A
5978685 Laiho Nov 1999 A
5987323 Huotari Nov 1999 A
5999811 Molne Dec 1999 A
6035025 Hanson Mar 2000 A
6049710 Nilsson Apr 2000 A
6058300 Hanson May 2000 A
6064875 Morgan May 2000 A
6070067 Nguyen et al. May 2000 A
6075982 Donovan et al. Jun 2000 A
6078583 Takahara Jun 2000 A
6081508 West et al. Jun 2000 A
6101378 Barabash et al. Aug 2000 A
6122503 Daly Sep 2000 A
6122520 Want et al. Sep 2000 A
6148197 Bridges et al. Nov 2000 A
6148198 Anderson et al. Nov 2000 A
6149353 Nilsson Nov 2000 A
6169891 Gorham et al. Jan 2001 B1
6173181 Losh Jan 2001 B1
6178331 Holmes et al. Jan 2001 B1
6181935 Gossman et al. Jan 2001 B1
6185602 Bayrakeri Feb 2001 B1
6188752 Lesley Feb 2001 B1
6198431 Gibson Mar 2001 B1
6199045 Giniger et al. Mar 2001 B1
6205330 Winbladh Mar 2001 B1
6208854 Roberts et al. Mar 2001 B1
6223046 Hamill-Keays et al. Apr 2001 B1
6226529 Bruno et al. May 2001 B1
6249680 Wax et al. Jun 2001 B1
6249744 Morita Jun 2001 B1
6266614 Alumbaugh Jul 2001 B1
6289373 Dezonno Sep 2001 B1
6314108 Ramasubramani et al. Nov 2001 B1
6317594 Gossman et al. Nov 2001 B1
6327479 Mikkola Dec 2001 B1
6353614 Borella et al. Mar 2002 B1
6393461 Okada et al. May 2002 B1
6396913 Perkins, III May 2002 B1
6459892 Burgan et al. Oct 2002 B2
6499053 Marquette et al. Dec 2002 B1
6564261 Gudjonsson et al. May 2003 B1
6677894 Sheynblat Jan 2004 B2
6690940 Brown Feb 2004 B1
6842449 Hardjono Jan 2005 B2
6970871 Rayburn Nov 2005 B1
7054659 Gioscia et al. May 2006 B2
7123874 Brennan Oct 2006 B1
7444342 Hall Oct 2008 B1
7522182 Bang Apr 2009 B2
7565155 Sheha et al. Jul 2009 B2
7603148 Michalak Oct 2009 B2
7693546 Gioscia et al. Apr 2010 B1
7925246 McKibben Apr 2011 B2
8200291 Steinmetz Jun 2012 B2
8265326 Singh Sep 2012 B2
8284980 Parker et al. Oct 2012 B2
20020155844 Rankin et al. Oct 2002 A1
20030060214 Hendrey Mar 2003 A1
20030157942 Osmo Aug 2003 A1
20030169881 Niedermeyer Sep 2003 A1
20030220835 Barnes, Jr. Nov 2003 A1
20040077359 Bernas Apr 2004 A1
20040137921 Valloppillil Jul 2004 A1
20040203863 Huomo Oct 2004 A1
20040203900 Cedervall Oct 2004 A1
20040209594 Naboulsi Oct 2004 A1
20050079877 Ichimura Apr 2005 A1
20050149430 Williams Jul 2005 A1
20050197775 Smith Sep 2005 A1
20050277432 Viana Dec 2005 A1
20050282518 D'Evelyn Dec 2005 A1
20060003775 Bull Jan 2006 A1
20060030350 Mitchell Feb 2006 A1
20060058102 Nguyen Mar 2006 A1
20060109960 D'Evelyn May 2006 A1
20060116138 Simsek Jun 2006 A1
20060142027 Krishnamurthi Jun 2006 A1
20060202888 Pitt et al. Sep 2006 A1
20060233317 Coster Oct 2006 A1
20070004424 Sheen Jan 2007 A1
20070021098 Rhodes Jan 2007 A1
20070149208 Syrbe Jun 2007 A1
20080014964 Sudit et al. Jan 2008 A1
20080268769 Brown Oct 2008 A1
20090029675 Steinmetz Jan 2009 A1
20100167691 Howarter Jul 2010 A1
20110109468 Hirschfeld May 2011 A1
20120223134 Smith Sep 2012 A1
Non-Patent Literature Citations (9)
Entry
PCT Search Report issued in PCT/US008/13690 and mailed on Jan. 29, 2009.
International Search Report in PCT/US2007/20207 dated Apr. 1, 2008.
International Search Report in PCT/US2007/026132 dated Jun. 6, 2008.
International Search Report in PCT/US2007/20207 dated Oct. 30, 2008.
International Search Report in PCT/US2007/21133 dated Apr. 21, 2008.
de Carla, Powering Location Based Solutions, Marketpalce, 2006, pp. 1-2.
Proximity Media, How the Bluetooth Media Server Works, Aug. 23, 2006 pp. 1-3.
PCT International Search Report (PCTUS2007/16138) and Written Opinion of International Searching Authority, Feb. 7, 2008.
Kim, J.Y., et al., “An Enhanced VolP Emergency Services Prototype,” Proceedings of the 3rd International ISCRAM Conference, Newark, NJ, May 2006.
Related Publications (1)
Number Date Country
20120108265 A1 May 2012 US
Provisional Applications (1)
Number Date Country
60845527 Sep 2006 US
Continuations (1)
Number Date Country
Parent 11544724 Oct 2006 US
Child 13349951 US