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.
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.
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:
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 (FDA). Of course, other methods of precise location are possible, within the principles of the present invention.
In particular, as shown in
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 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/Ion) 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,
In particular, as shown in
A first range 302 shown in
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).
In particular, as shown in
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
While
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,
For ease of description and explanation, the points of interest 310-320 are depicted in the same locations in
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
In
In
In
In
In
In
In
In particular, as shown in
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.
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
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.
This application is a continuation of U.S. patent application Ser. No. 13/349,951, entitled “Device Based Trigger for Location Push Event,” filed on Jan. 13, 2012; which 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, now U.S. Pat. No. 8,099,105; which claims priority from U.S. Provisional Patent Appl. No. 60/845,627, filed Sep. 19, 2006, entitled “Device Based Triggered Location Push Event” to Drew Morin, the entirety of all three of which are expressly incorporated herein by reference.
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 | Carrol 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 | Ronen 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 et al. | 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 | 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 | 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 | Cedevall | 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 et al. | Dec 2005 | A1 |
20060003775 | Bull | Jan 2006 | A1 |
20060030350 | Mitchell | Feb 2006 | A1 |
20060058102 | Nguyen | Mar 2006 | A1 |
20060109960 | D'Evelyn et al. | May 2006 | A1 |
20060116138 | Simsek | Jun 2006 | A1 |
20060142027 | Krishnamurthi | Jun 2006 | A1 |
20060202888 | Pitt | 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 | 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 |
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 Carta, 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 VoIP Emergency Services Prototype,” Proceedings of the 3rd International ISCRAM Conference, Newark, NJ, May 2006. |
Number | Date | Country | |
---|---|---|---|
20150038177 A1 | Feb 2015 | US |
Number | Date | Country | |
---|---|---|---|
60845527 | Sep 2006 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 13349951 | Jan 2012 | US |
Child | 14518282 | US | |
Parent | 11544724 | Oct 2006 | US |
Child | 13349951 | US |