Location based proximity alert

Abstract
A method of location based proximity alert retrieves, from a location based proximity alert physical server, a current location of wireless client devices and determines if it is within a given area. The method accesses, from the location based proximity alert physical server, a physical law enforcement database comprising a restraining order target identifier and a restraining order limit identifier. A geo-proximity alert message is transmitted if the current location of the restraining order target identifier matches the restraining order limit identifier.
Description
BACKGROUND OF THE INVENTION

1. Field of the Invention


This invention relates generally to wireless communications. More particularly, it relates to location based services (LBS).


2. Background


Courts routinely order restraining orders for any of a number of reasons. For example, persons can be issued a restraining order ordering them to remain a fixed distance from another person, to remain a fixed distance from schools, parks, or other establishments related to children. No matter the type of restraining order issued, there persists a problem in enforcing restraining orders.


Generally, restraining orders require persons viewing a restraining order violation to report such a violation to the police. The restraining order violator that is reported to the police is generally arrested for violating the restraining order.


In extreme cases, a tracking device, such as an ankle tracking device, can be court ordered attached to a person to electronically monitor their compliance with a restraining order. However, such electronic monitors are costly and require dedicated monitoring devices to detect a restraining order violation.


There is a need for a method and apparatus that allows for cost effective automated tracking of persons subject to a restraining order. This would eliminate human initiated reporting of a restraining order violation that is limited by a requirement for a human to view a restraining order violator and the ability of the viewer to contact the police.


SUMMARY OF THE INVENTION

In accordance with the principles of the present invention, method of providing location based proximity alert services comprises retrieving, at a location based proximity alert physical server, a current location of a wireless client device associated with a given restraining order target identifier. A law enforcement database comprising a plurality of restraining order target identifiers, each associated with a corresponding restraining order limit identifier, is accessed to obtain a relevant restraining order limit identifier associated with the given restraining order target identifier. A geo-proximity alert message is generated when the current location is within a prohibited geographic area associated with the given restraining order target identifier.


A location based proximity alert physical server in accordance with another aspect of the invention comprises a law enforcement database access module to access a physical law enforcement database comprising a plurality of restraining order target identifiers each associated with a restraining order limit identifier. A location access module retrieves, from the location based proximity alert physical server, a current location of the restraining order target. A restraining order violation module generates a geo-proximity alert message if the current location for the restraining order target enters a prohibited geographic area associated with the restraining order limit identifier.





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:



FIG. 1 shows a location based proximity alert system, in accordance with the principles of the present invention.



FIG. 2 shows an example entry in the law enforcement database shown in FIG. 1, in accordance with the principles of the present invention.



FIG. 3 shows an exemplary flow chart for a process of triggering a geo-proximity alert message, in accordance with the principles of the present invention.





DETAILED DESCRIPTION OF ILLUSTRATIVE EMBODIMENTS

With respect to law enforcement, a restraining order is a protection device whereby a Court establishes it to be unsafe for two individuals to have contact. Each state in the United States has some form of domestic “stay away” law.


The present invention applies location enabled cell or other wireless equipment to a long-felt but unsolved need in today's society. Namely, in accordance with the principles disclosed herein a proximity alert server monitors for violations of such a restraining order.


In an alternate embodiment, in an everyday case a subscriber might just want to get a notification when another subscriber is in their vicinity. The Subscriber Proximity notification disclosed herein is a system that notifies a subscriber via SMS, or any other messaging system, when another subscriber is using the same or geographically close cell equipment.


The present invention is a service whereby a given subscriber, e.g., subscriber 1, provisions their phone number (or other unique identifying number) of another subscriber (e.g., subscriber 2) and a range, radius or other proximity defining value. Examples of the radius or other proximity defining value might be within 100 yards, within 1 mile, etc. In this example, subscriber 1 receives notification when subscriber 2 gets within a pre-set range, radius or other proximity defining distance of subscriber 1.


The present invention has particular applicability for use when a court ordered restraining order is imposed, and preferably includes a time frame for enforcement of a subject restraining order. For instance, if a given restraining order is valid for 30 days, the geo-proximity alert service in accordance with the present invention preferably automatically expires after 30 days or other appropriate time.


In one given application, each time subscriber 1 registers call-routing information in the appropriate Home Location Register (HLR), the system uses the pre-set proximity defining value to create a proximity-list of cell equipment that is within the perimeter. This system then preferably compares the registered call-routing information for subscriber 2 with the proximity-list. If the subscriber 2 registered call-routing is in the proximity-list, the system then sends an appropriate geo-proximity alert message (e.g., SMS, IM, etc.) to subscriber 1, a law enforcement facility, and/or a public safety access point (PSAP), etc., alerting them to the situation.


This invention has particular relevance and use with a cell phone or personal digital assistant (PDA). In addition to the important law enforcement aspects of the invention, it is also applicable to social networking applications, e.g., if two consenting parties want to know when they are within proximity to one another, or simply in a same general area.


The present invention can also be used to provide information regarding entry of a user's wireless device within an unauthorized proximity to certain types of locations, e.g., schools, a park, playgrounds, and/or other places where children gather, etc. The proximity message may be sent to an appropriate person, e.g., police personnel, along with identifying information sufficient for the police personnel to respond to the situation.


With appropriate sensitivity to privacy issues addressed, the present invention has applicability in non-law enforcement scenarios as well as the law enforcement embodiments disclosed herein.



FIG. 1 shows a location based proximity alert system, in accordance with the principles of the present invention.


In particular, the location based proximity alert (LBPA) system 101 disclosed herein, includes a location based proximity alert (LBPA) server 100, a law enforcement database 110, a home location register (HLR) 120, a communication network 130, various messaging servers 142-146, a gateway 150, and a cellular tower 160. The location based proximity alert (LBPA) system 101 disclosed herein can further include various wireless clients (WCs), such as in particular a cellular telephone 180a, a smart phone 180b, a personal data assistant 180c, and a laptop computer 180d (collectively and individually described herein as wireless client(s) 180).


The location based proximity alert server 100 provides the backbone for location monitoring and message alerting functions disclosed herein. In particular, the location based proximity alert server 100 accesses law enforcement database 110 for parameters with which to base wireless client 180 monitoring, as well as limitations that dictate when a message is to be issued to pre-configured recipients, e.g., in the event of a restraining order violation.


The location based proximity alert server 100 accesses a location service, such as home location register 120. Each time a wireless client 180 registers call-routing information in the home location register 120, the location based proximity alert server 100 can use a pre-set proximity value retrieved from an appropriate law enforcement database 110 to create a proximity-list of wireless clients 180, as defined in the law enforcement database 110. This location based proximity alert system 101 then preferably compares the registered call-routing information for the wireless client 180a with the proximity-list of wireless clients 180. If the registered wireless client's 180 call-routing is in the proximity-list, the location based proximity alert server 100 then sends an appropriate geo-proximity alert message (e.g., SMS, IM, etc.) to the preconfigured point, e.g., wireless client 180a alerting them of the situation, e.g., a restraining order violation.


A digital communication network 130 allows the location based proximity alert server 100 to send an appropriate geo-proximity alert message. The digital communication network 130 is preferably an open IP based communication network, such as the Internet. Alternately, the digital communication network 130 is a closed IP based communication network, relying on locally assigned IP addresses. Irrespective of the type of communication network used, the location based proximity alert server 100 communicates with any of a variety of messaging servers, such as e-mail server 142, Short Message Service (SMS) server 144, Instant Message (IM) server 146, etc. through IP packet addressing, as is otherwise known within the art.


An IP gateway 150 provides gateway functions to allow the communication network 130 to send and receive digital data packets to and from a cellular network 160. The cellular network 160 transmits an appropriate geo-proximity alert message from any of e-mail server 142, Short Message Service (SMS) server 144, Instant Message (IM) server 146, etc., to a pre-designated wireless client 180 over the communication network 130.


For example purposes only, the wireless client 180a is shown as having an entry in the law enforcement database 110. However, any number of wireless clients 180 can have simultaneous entries in the restraining order database 110. The wireless client 180a is shown as having an entry in the law enforcement database 110 that corresponds to the radius distance 184.


The radius distance 184 can be a distance measured in any unit of measurement that allows for a determination of a restraining order violation. The radius distance 184 from the wireless client 180a produces a zone of protection 182 around the relevant wireless client 180a.


If the location based proximity alert server 100 determines that a location of the relevant wireless client 180b, as identified in the home location register 130, is within radius distance 184, or if the location based proximity alert server 100 identifies the same wireless client 180b as having restricted status in the law enforcement database 110 for that particular wireless client 180a, the location based proximity alert server 100 triggers transmission of an appropriate geo-proximity alert message. As shown in more detail in FIG. 2, the specific type of geo-proximity alert message can be specified as an entry in the law enforcement database 110.


The radius distance 184 is described above as being a protective zone 182 that when breached, e.g., by the wireless client 180b, triggers an appropriate geo-proximity alert message. However, in an alternate embodiment, radius distance 184 can be a restrictive zone that when breached by a geographically stationary point, causes triggering of an appropriate geo-proximity alert message. In this type of embodiment, if the wireless client 180a is the subject of a restraining order that prevents its holder from getting within a configured distance 184 of any school grounds 170, a breach of any of the geographic points associated with school grounds 170 within a given distance 184 results in an appropriate geo-proximity alert message being transmitted to the proper authority(ies). The proper authorities can be preconfigured as an entry in the law enforcement database 110, as shown in more detail in FIG. 2.


The law enforcement database 110 preferably is a highly secure database that requires encrypted and password protected access. Law enforcement personnel are preferably provided remote access to the law enforcement database 110 through a secure digital connection. A web page can be used to populate the entries within the law enforcement database 110, as well as to review and correct entries within the law enforcement database 110.


Although the location based proximity alert server 100 relies on access to a home location register (HLR) to monitor the location of wireless clients 180, any of a number of location services can be employed to determine the location of a given wireless client 180. For instance, the Global Positioning System (GPS) is becoming commonly integrated within wireless clients 180, and if available can be used to directly provide location information for the relevant wireless client 180 to the location based proximity alert server 100. Alternately, within the principles disclosed herein, cellular triangulation, signal strength monitoring, etc. may alternatively be used to provide location information for a wireless client 180 to the location based proximity alert server 100.



FIG. 2 shows an example entry 200 in the law enforcement database 110 shown in FIG. 1, in accordance with the principles of the present invention.


In particular, entry 200 can include a requestor field 210, an enforcement period field 220, an identity of restriction field 230, a limits of restriction field 240, and a type of alert field 250.


The example requestor field 210 is shown as being “MIN of John Doe”, MIN being a mobile identification number (MIN). However, the requestor field 210 could include a state, a county, a country, etc. that issued a restraining order.


The example enforcement period field 220 is shown as being “Sep. 1, 2009-Sep. 30, 2009”. However, the enforcement period field 220 could include specific times of a day, specific days of the week, specific months of the year, and even years of enforcement, all in accordance within the principles disclosed herein.


The example identity of the restriction field 230 is shown as being “MIN of Alice Smith”. However, in accordance with the principles disclosed herein, the identity of the restriction field 230 could include telephone numbers, specific longitude(s) and latitude(s), ranges of longitudes and latitudes, names of geographic places that can be cross-referenced to their geographic locations, etc.


The limits of restriction field 240 is shown in the exemplary embodiments as being “100 yards”. However, in accordance with the principles disclosed herein, the limits of the restriction field 240 could be a zero value requiring direct contact with the identity of the value associated with the identity of the restriction field 230, a measurement in miles, a city limits value, a state value, etc.


The type of alert field 250 is shown in the exemplary embodiments as being “SMS XXX-XXX-XXXX”. However, in accordance with the principles disclosed herein, the type of alert field 250 can designate e-mail and an e-mail address, can designate IM and an IM address, can designate the police, can designate a relative of the restraining order requestor, can designate any desired telephone number to call, etc. Preferably, if the location based proximity alert server 100 dials a telephone number to provide a location based proximity alert relating to a violation of a restraining order, a pre-recorded message may be played, and a further option may be provided to connect with a public access safety point (PSAP), police station, etc., to avoid delay in responding to the restraining order violation. Likewise, if the location based proximity alert server 100 transmits a text message to provide a location based proximity alert relating to violation of a restraining order, information useful to police or other authorities is preferably provided with the text message.


Alternately, within the scope of the principles disclosed herein, the type of alert field 250 could designate a list of services to contact in the event that a given restraining order is being violated, with contact to authorities such as police, a private security company, etc. The location based proximity alert server 100 can use the designated list of services to trigger transmission of a plurality of geo-proximity alert messages in response to a single restraining order violation. The type of alert field 250 can even include a mobile identification number (MIN) to assist in reaching a wireless client 180 in the event an alternate designated method fails to reach the wireless client 180.



FIG. 3 shows an exemplary flow chart for a process of triggering a geo-proximity alert message 300, in accordance with the principles of the present invention.


In particular, as shown in step 310 of FIG. 3, a determination is made of which wireless client(s) 180 exist within in a particular area. The location based proximity alert server 100 can access a home location register 120 to retrieve a list of wireless clients 180 and their respective locations that have registered call-routing information in the home location register 120.


In step 320, a determination is made if any of the wireless clients 180 that were determined to be within a particular area in step 310 are subject to a restraining order. The location based proximity alert server 100 can use the list of wireless clients 180, e.g., MINs, that were determined to be within a particular area in step 310 as a database query issued to law enforcement database 110. Any matched wireless clients 180 returned from the database query provides a list of wireless clients 180 that are subject to a restraining order and their respective restrictions.


In step 330, a decision is made if the wireless client 180 that is subject to a restraining order is in violation of its respective restrictions. The location based proximity alert server 100 compares the geographic location of the wireless client 180 (e.g., wireless phone) that is subject to a restraining order, to the geographic location of the identity of the restriction, as retrieved from law enforcement database 110. The identity of the restriction can be, e.g., proximity to another wireless client WC 180 (such as a wireless phone carried by an ex-girlfriend), or within geographic boundary coordinates corresponding to a restricted perimeter around an area where children would be, e.g., a school, a playground, a daycare center, etc.


If the result of the decision from step 330 is that a restraining order violation has occurred, step 330 branches to step 340. Otherwise, step 330 branches back to step 310 to continuously monitor for a restraining order violation.


In step 340, an appropriate geo-proximity alert message is generated and transmitted (e.g., via SMS, IM, etc.) to whatever alert destination that is pre-configured by specification in the type of alert field 250 in the restraining database entry 200. The location based proximity alert server 100 initiates transmission of an appropriate geo-proximity alert message to the pre-configured alert destination that is associated with the wireless client 180 that was determined to have violated its restraining order in step 330.


Step 340 branches back to the beginning of the, process of triggering a geo-proximity alert message 300 to allow for continuous monitoring of restraining order violations, in accordance with the principles disclosed herein.


Although the embodiments described herein provide for a location based proximity alert based on movement of a wireless client (e.g., a wireless phone) carried by an offender subject to a restraining order, the principles disclosed herein can be applied to alert a subscriber of a wireless client 180 of proximity to another wireless client 180 and/or proximity to a specific geographic location. The identity of other wireless clients 180 and/or specific geographic locations can be stored in a database entry, e.g., in an entry in the law enforcement database shown in FIG. 2. In this manner, law enforcement or even another subscriber can be alerted when they come within a preconfigured radius distance 184 of a select wireless client carried by, e.g., a friend or family member.


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 method of providing location-based proximity alert services, comprising: retrieving, by a location-based proximity alert physical server, a current location of a wireless client device, said current location being based on call-routing information associated with said wireless client device, said call-routing information being registered in a location device servicing said wireless client device device, and said wireless client device associated with a given restraining order target identifier from a plurality of restraining order target identifiers;accessing a law enforcement database comprising said plurality of restraining order target identifiers, each associated with a corresponding restraining order limit identifier, to obtain a relevant restraining order limit identifier associated with said given restraining order target identifier; andgenerating a geo-proximity alert message when said current location is within a prohibited geographic area associated with said given restraining order target identifier.
  • 2. The method of providing location-based proximity alert services according to claim 1, wherein: said given restraining order target identifier is a mobile identification number (MIN).
  • 3. The method of providing location-based proximity alert services according to claim 1, wherein: said given restraining order target identifier is a mobile telephone number.
  • 4. The method of providing location-based proximity alert services according to claim 1, further comprising: determining a distance between said wireless client device associated with said given restraining order target identifier, and a wireless client device requesting said geo-proximity alert message.
  • 5. The method of providing location-based proximity alert services according to claim 1, wherein: said prohibited geographic area associated with said given restraining order target identifier is a prohibited perimeter around a given school.
  • 6. The method of providing location-based proximity alert services according to claim 1, wherein: said prohibited geographic area associated with said given restraining order target identifier is a prohibited perimeter around a given park.
  • 7. The method of providing location-based proximity alert services according to claim 1, wherein: said geo-proximity alert message is an email message.
  • 8. A location-based proximity alert physical server, comprising: a law enforcement database access module to access a physical law enforcement database comprising a plurality of restraining order target identifiers each associated with a given restraining order limit identifier;a location access module, at said location-based proximity alert physical server, to retrieve a current location of a wireless client device, said current location being based on call-routing information associated with said wireless client device, said call-routing information being registered in a location device servicing said wireless client device, and said wireless client device associated with a given restraining order target identifier from said plurality of restraining order target identifiers; anda restraining order violation module to generate a geo-proximity alert message when said current location for a restraining order target enters a prohibited geographic area associated with said given restraining order limit identifier.
  • 9. The location-based proximity alert physical server according to claim 8, wherein: said given restraining order target identifier is a mobile identification number (MIN).
  • 10. The location-based proximity alert physical server according to claim 8, wherein: said restraining order violation module generates said geo-proximity alert message when said wireless client device associated with said restraining order target is less than a preconfigured minimum distance from another wireless client device requesting said geo-proximity alert message.
  • 11. The location-based proximity alert physical server according to claim 8, wherein: said prohibited geographic area associated with said given restraining order target identifier is a prohibited perimeter around a given school.
  • 12. The location-based proximity alert physical server according to claim 8, wherein: said prohibited geographic area associated with said given restraining order target identifier is a prohibited perimeter around a given park.
  • 13. The location-based proximity alert physical server according to claim 8, wherein: said geo-proximity alert message is an email message.
Parent Case Info

The present invention claims priority from U.S. Provisional Application 61/136,918, filed Oct. 14, 2008, entitled “LOCATION BASED PROXIMITY ALERT”, to GEHRKE et al., the entirety of which is expressly incorporated herein by reference.

US Referenced Citations (358)
Number Name Date Kind
4445118 Taylor Apr 1984 A
4928107 Kuroda May 1990 A
4972484 Theile Nov 1990 A
5126722 Kamis Jun 1992 A
5283570 DeLuca Feb 1994 A
5301354 Schwendeman Apr 1994 A
5311516 Kuznicki May 1994 A
5327529 Fults Jul 1994 A
5335246 Yokev Aug 1994 A
5351235 Lahtinen Sep 1994 A
5365451 Wang Nov 1994 A
5418537 Bird May 1995 A
5422813 Schuchman Jun 1995 A
5479408 Will Dec 1995 A
5485163 Singer Jan 1996 A
5504491 Chapman Apr 1996 A
5506886 Maine Apr 1996 A
5517199 DiMattei May 1996 A
5530655 Lokhoff Jun 1996 A
5530914 McPheters Jun 1996 A
5539395 Buss Jul 1996 A
5539829 Lokhoff Jul 1996 A
5546445 Dennison Aug 1996 A
5568153 Beliveau Oct 1996 A
5583774 Diesel Dec 1996 A
5594780 Wiedeman Jan 1997 A
5606618 Lokhoff Feb 1997 A
5629693 Janky May 1997 A
5633630 Park May 1997 A
5636276 Brugger Jun 1997 A
5661652 Sprague Aug 1997 A
5661755 Van de Kerkhof Aug 1997 A
5689245 Noreen Nov 1997 A
5699053 Jonsson Dec 1997 A
5704029 Wright, Jr. Dec 1997 A
5721781 Deo Feb 1998 A
5727057 Emery Mar 1998 A
5731785 Lemelson Mar 1998 A
5765152 Erickson Jun 1998 A
5771353 Eggleston Jun 1998 A
5774670 Montulli Jun 1998 A
5809415 Rossmann Sep 1998 A
5812086 Bertiger Sep 1998 A
5812087 Krasner Sep 1998 A
5841396 Krasner Nov 1998 A
5857201 Wright, Jr. Jan 1999 A
5864667 Barkan Jan 1999 A
5874914 Krasner Feb 1999 A
5896369 Warsta Apr 1999 A
5898391 Jefferies Apr 1999 A
5922074 Richard Jul 1999 A
5930250 Klok Jul 1999 A
5945944 Krasner Aug 1999 A
5946629 Sawyer Aug 1999 A
5950137 Kim Sep 1999 A
5960362 Grob Sep 1999 A
5983099 Yao Nov 1999 A
5999124 Sheynblat Dec 1999 A
6032051 Hall Feb 2000 A
6049718 Stewart Apr 2000 A
6052081 Krasner Apr 2000 A
6058338 Agashe May 2000 A
6061018 Sheynblat May 2000 A
6064336 Krasner May 2000 A
6067045 Castelloe May 2000 A
6081229 Soliman Jun 2000 A
6085320 Kaliski, Jr. Jul 2000 A
6118403 Lang Sep 2000 A
6121923 King Sep 2000 A
6124810 Segal Sep 2000 A
6131067 Girerd Oct 2000 A
6133874 Krasner Oct 2000 A
6134483 Vayanos Oct 2000 A
6147598 Murphy Nov 2000 A
6150980 Krasner Nov 2000 A
6154172 Piccionelli Nov 2000 A
6169901 Boucher Jan 2001 B1
6169902 Kawamoto Jan 2001 B1
6178506 Quick, Jr. Jan 2001 B1
6185427 Krasner Feb 2001 B1
6188354 Soliman Feb 2001 B1
6188909 Alanara Feb 2001 B1
6189098 Kaliski, Jr. Feb 2001 B1
6195557 Havinis Feb 2001 B1
6204798 Fleming Mar 2001 B1
6205330 Winbladh Mar 2001 B1
6208290 Krasner Mar 2001 B1
6215441 Moeglein Apr 2001 B1
6239742 Krasner May 2001 B1
6247135 Feague Jun 2001 B1
6249873 Richard Jun 2001 B1
6253203 O'Flaherty Jun 2001 B1
6260147 Quick, Jr. Jul 2001 B1
6275692 Skog Aug 2001 B1
6275849 Ludwig Aug 2001 B1
6297768 Allen, Jr. Oct 2001 B1
6307504 Sheynblat Oct 2001 B1
6308269 Proidl Oct 2001 B2
6313786 Sheynblat Nov 2001 B1
6321257 Kotola Nov 2001 B1
6324524 Lent Nov 2001 B1
6327473 Soliman Dec 2001 B1
6333919 Gaffney Dec 2001 B2
6360093 Ross Mar 2002 B1
6360102 Havinis Mar 2002 B1
6363254 Jones Mar 2002 B1
6367019 Ansell Apr 2002 B1
6377209 Krasner Apr 2002 B1
6400314 Krasner Jun 2002 B1
6400958 Isomursu Jun 2002 B1
6411254 Moeglein Jun 2002 B1
6421002 Krasner Jul 2002 B2
6430504 Gilbert Aug 2002 B1
6433734 Krasner Aug 2002 B1
6442391 Johansson Aug 2002 B1
6449473 Raivisto Sep 2002 B1
6449476 Hutchison, IV Sep 2002 B1
6456852 Bar Sep 2002 B2
6463272 Wallace Oct 2002 B1
6477150 Maggenti Nov 2002 B1
6504491 Christians Jan 2003 B1
6510387 Fuchs Jan 2003 B2
6512922 Burg Jan 2003 B1
6512930 Sandegren Jan 2003 B2
6515623 Johnson Feb 2003 B2
6519466 Pande Feb 2003 B2
6522682 Kohli Feb 2003 B1
6525687 Roy Feb 2003 B2
6525688 Chou Feb 2003 B2
6529829 Turetzky Mar 2003 B2
6531982 White Mar 2003 B1
6538757 Sansone Mar 2003 B1
6539200 Schiff Mar 2003 B1
6539304 Chansarkar Mar 2003 B1
6542464 Takeda Apr 2003 B1
6542734 Abrol Apr 2003 B1
6542743 Soliman Apr 2003 B1
6549776 Joong Apr 2003 B1
6549844 Egberts Apr 2003 B1
6556832 Soliman Apr 2003 B1
6560461 Fomukong May 2003 B1
6560534 Abraham May 2003 B2
6567035 Elliott May 2003 B1
6570530 Gaal May 2003 B2
6574558 Kohli Jun 2003 B2
6580390 Hay Jun 2003 B1
6584552 Kuno et al. Jun 2003 B1
6594500 Bender Jul 2003 B2
6597311 Sheynblat Jul 2003 B2
6603973 Foladare Aug 2003 B1
6606495 Korpi Aug 2003 B1
6606554 Edge Aug 2003 B2
6609004 Morse Aug 2003 B1
6611757 Brodie Aug 2003 B2
6618670 Chansarkar Sep 2003 B1
6621452 Knockeart Sep 2003 B2
6628233 Knockeart Sep 2003 B2
6633255 Krasner Oct 2003 B2
6640184 Rabe Oct 2003 B1
6650288 Pitt et al. Nov 2003 B1
6661372 Girerd Dec 2003 B1
6665539 Sih Dec 2003 B2
6665541 Krasner Dec 2003 B1
6671620 Garin Dec 2003 B1
6677894 Sheynblat Jan 2004 B2
6680694 Knockheart Jan 2004 B1
6680695 Turetzky Jan 2004 B2
6691019 Seeley Feb 2004 B2
6694258 Johnson Feb 2004 B2
6697629 Grilli Feb 2004 B1
6698195 Hellinger Mar 2004 B1
6701144 Kirbas Mar 2004 B2
6703971 Pande Mar 2004 B2
6703972 van Diggelen Mar 2004 B2
6704651 Van Diggelen Mar 2004 B2
6707421 Drury Mar 2004 B1
6714793 Carey Mar 2004 B1
6718174 Vayanos Apr 2004 B2
6720915 Sheynblat Apr 2004 B2
6721578 Minear Apr 2004 B2
6721871 Piispanen Apr 2004 B2
6724342 Bloebaum Apr 2004 B2
6725159 Krasner Apr 2004 B2
6731940 Nagendran May 2004 B1
6734821 Van Diggelen May 2004 B2
6738013 Orler May 2004 B2
6738800 Aquilon May 2004 B1
6741842 Goldberg May 2004 B2
6745038 Callaway, Jr. Jun 2004 B2
6747596 Orler Jun 2004 B2
6748195 Phillips Jun 2004 B1
6751464 Burg Jun 2004 B1
6756938 Zhao Jun 2004 B2
6757544 Rangarajan Jun 2004 B2
6772340 Peinado Aug 2004 B1
6775655 Peinado Aug 2004 B1
6775802 Gaal Aug 2004 B2
6778136 Gronomeyer Aug 2004 B2
6778885 Agashe Aug 2004 B2
6781963 Crockett Aug 2004 B2
6788249 Farmer Sep 2004 B1
6795699 McCraw Sep 2004 B1
6799050 Krasner Sep 2004 B1
6801124 Naitou Oct 2004 B2
6801159 Swope Oct 2004 B2
6804524 Vandermeijden Oct 2004 B1
6807534 Erickson Oct 2004 B1
6810323 Bullock Oct 2004 B1
6813560 van Diggelen Nov 2004 B2
6816111 Krasner Nov 2004 B2
6816710 Krasner Nov 2004 B2
6816719 Heinonen et al. Nov 2004 B1
6816734 Wong Nov 2004 B2
6820069 Kogan Nov 2004 B1
6829475 Lee Dec 2004 B1
6832373 O'Neill Dec 2004 B2
6833785 Brown Dec 2004 B2
6839020 Geier Jan 2005 B2
6839021 Sheynblat Jan 2005 B2
6842715 Gaal Jan 2005 B1
6853849 Tognazzini Feb 2005 B1
6853916 Fuchs Feb 2005 B2
6856282 Mauro Feb 2005 B2
6861980 Rowitch et al. Mar 2005 B1
6865171 Nilsson Mar 2005 B1
6865395 Riley Mar 2005 B2
6867734 Voor et al. Mar 2005 B2
6873854 Crockett et al. Mar 2005 B2
6885940 Brodie et al. Apr 2005 B2
6888497 King et al. May 2005 B2
6888932 Snip et al. May 2005 B2
6895238 Newell et al. May 2005 B2
6895249 Gaal May 2005 B2
6895324 Straub May 2005 B2
6900758 Mann et al. May 2005 B1
6903684 Simic et al. Jun 2005 B1
6904029 Fors Jun 2005 B2
6907224 Younis Jun 2005 B2
6907238 Leung Jun 2005 B2
6912395 Benes Jun 2005 B2
6915208 Garin Jul 2005 B2
6917331 Gronemeyer Jul 2005 B2
6930634 Peng Aug 2005 B2
6937187 Van Diggelen Aug 2005 B2
6937872 Krasner Aug 2005 B2
6941144 Stein Sep 2005 B2
6944540 King Sep 2005 B2
6947772 Minear Sep 2005 B2
6950058 Davis Sep 2005 B1
6956467 Mercado, Jr. Oct 2005 B1
6957073 Bye Oct 2005 B2
6961562 Ross Nov 2005 B2
6965754 King Nov 2005 B2
6965767 Maggenti Nov 2005 B2
6970917 Kushwaha Nov 2005 B1
6973166 Tsumpes Dec 2005 B1
6973320 Brown Dec 2005 B2
6975266 Abraham Dec 2005 B2
6978453 Rao Dec 2005 B2
6980816 Rohles Dec 2005 B2
6985105 Pitt et al. Jan 2006 B1
6996720 DeMello Feb 2006 B1
6999782 Shaughnessy Feb 2006 B2
7024321 Deniger et al. Apr 2006 B1
7024393 Peinado Apr 2006 B1
7047411 DeMello May 2006 B1
7058358 Cannon Jun 2006 B2
7064656 Bekcher Jun 2006 B2
7065351 Carter Jun 2006 B2
7065507 Mohammed Jun 2006 B2
7071814 Schorman Jul 2006 B1
7079857 Maggenti Jul 2006 B2
7103018 Hasen Sep 2006 B1
7103574 Peinado Sep 2006 B1
7106717 Rosseau Sep 2006 B2
7136838 Peinado Nov 2006 B1
7151946 Magennti Dec 2006 B2
7177623 Baldwin Feb 2007 B2
7209969 Lahti Apr 2007 B2
7218940 Niemenna May 2007 B2
7221959 Lindquist May 2007 B2
7269413 Kraft Sep 2007 B2
7301494 Waters Nov 2007 B2
7324823 Rosen Jan 2008 B1
7372839 Relan May 2008 B2
7739402 Roese Jun 2010 B2
8190169 Shim May 2012 B2
20020037735 Maggenti Mar 2002 A1
20020052214 Maggenti May 2002 A1
20020061760 Maggenti May 2002 A1
20020069529 Wieres Jun 2002 A1
20020102999 Maggenti Aug 2002 A1
20020112047 Kushwaha Aug 2002 A1
20020135504 Singer Sep 2002 A1
20020173317 Nykanen Nov 2002 A1
20020198632 Breed et al. Dec 2002 A1
20030009602 Jacobs Jan 2003 A1
20030037163 Kitada Feb 2003 A1
20030065788 Salomaki Apr 2003 A1
20030078064 Chan Apr 2003 A1
20030081557 Mettala May 2003 A1
20030101329 Lahti May 2003 A1
20030101341 Kettler May 2003 A1
20030103484 Oommen Jun 2003 A1
20030114157 Spitz Jun 2003 A1
20030119528 Pew Jun 2003 A1
20030153340 Crockett Aug 2003 A1
20030153341 Crockett Aug 2003 A1
20030153342 Crockett Aug 2003 A1
20030153343 Crockett Aug 2003 A1
20030161298 Bergman Aug 2003 A1
20030204640 Sahinaja Oct 2003 A1
20030223381 Schroderus Dec 2003 A1
20040002326 Maher Jan 2004 A1
20040044623 Wake Mar 2004 A1
20040046667 Copley Mar 2004 A1
20040064550 Sakata Apr 2004 A1
20040068724 Gardner Apr 2004 A1
20040090121 Simonds May 2004 A1
20040204806 Chen Oct 2004 A1
20040205151 Sprigg Oct 2004 A1
20040229632 Flynn Nov 2004 A1
20040257273 Benco Dec 2004 A1
20050003797 Baldwin Jan 2005 A1
20050028034 Gantman Feb 2005 A1
20050039178 Marolia Feb 2005 A1
20050041578 Huotari Feb 2005 A1
20050086340 Kang Apr 2005 A1
20050086467 Asokan Apr 2005 A1
20050112030 Gauss May 2005 A1
20050136895 Thenthiruperai Jun 2005 A1
20050172217 Leung Aug 2005 A1
20050174987 Raghav Aug 2005 A1
20050209995 Aksu Sep 2005 A1
20050246217 Horn Nov 2005 A1
20050259675 Tuohino Nov 2005 A1
20060053225 Poikselka Mar 2006 A1
20060058045 Nilsen Mar 2006 A1
20060058948 Blass Mar 2006 A1
20060074618 Miller Apr 2006 A1
20060090136 Miller Apr 2006 A1
20060097866 Adamczyk et al. May 2006 A1
20060212558 Sahinoja Sep 2006 A1
20060212562 Kushwaha Sep 2006 A1
20060234639 Kushwaha Oct 2006 A1
20060234698 Fok Oct 2006 A1
20070026854 Nath Feb 2007 A1
20070030116 Feher Feb 2007 A1
20070030539 Nath Feb 2007 A1
20070030973 Mikan Feb 2007 A1
20070186105 Bailey Aug 2007 A1
20070271596 Boubion Nov 2007 A1
20080026723 Han Jan 2008 A1
20080198989 Contractor Aug 2008 A1
20080227467 Barnes Sep 2008 A1
20090058830 Herz Mar 2009 A1
20090204815 Dennis Aug 2009 A1
20100050251 Speyer Feb 2010 A1
Non-Patent Literature Citations (4)
Entry
International Search Report received in PCT/US2011/00671 dated Apr. 25, 2012.
Search Report received in PCT/US2011/00950 dated Sep. 16, 2011.
Search Report received in PCT/US2009/05575 dated Dec. 3, 2009.
Search report received in PCT/US2009/05575 dated Jan. 14, 2011.
Related Publications (1)
Number Date Country
20100090827 A1 Apr 2010 US
Provisional Applications (1)
Number Date Country
61136918 Oct 2008 US