Mobile phone locator

Information

  • Patent Grant
  • 9510128
  • Patent Number
    9,510,128
  • Date Filed
    Wednesday, February 27, 2013
    11 years ago
  • Date Issued
    Tuesday, November 29, 2016
    8 years ago
Abstract
A mobile phone, including a protocol sniffer for capturing a beacon from a wireless access point, a beacon parser, coupled with the protocol sniffer, for identifying an alert request within the captured beacon, and at least one speaker, coupled with the beacon parser, for sounding an audible alert in response to the beacon parser identifying the alert request.
Description
FIELD OF THE INVENTION

The field of the present invention is mobile phones.


BACKGROUND OF THE INVENTION

A common problem that arises with mobile electronic devices is locating a misplaced device. Cell phones, for example, are notorious for getting lost.


Conventionally there are two types of methods for locating a misplaced phone. One method, used primarily with cordless phones, involves paging the cordless phone from the phone's base station. When paged, the cordless phone generates an audible alert which enables a user to find the phone. This method generally does not apply to cell phones, since although cell phones are paged by operators via base stations, they do not have personal base station paging capability.


Another method for locating a misplaced phone is to call the phone from another phone. The misplaced phone can be tracked by its ringing sound. This method is commonly used for locating cell phones. However, this method does not work if the misplaced phone has been set to an inaudible ring mode, such as a silent or vibrating ring, or to a very low volume ring.


U.S. Patent Application Publication No. 2007/0072620 A1 of Levitan, entitled SYSTEM AND METHOD FOR RECOVERING A LOST OR STOLEN WIRELESS DEVICE, describes use of a location server for storing user-associated location information. U.S. Patent Application No. 2007/0077924 A1 of Bhogal et al., entitled SYSTEM AND METHOD TO LOCATE MOBILE DEVICES HAVING INAUDIBLE SETTINGS, describes remotely adjusting the ring tone volume of a mobile phone, so that the ring tone is audible enough for a user to hear it. According to Bhogal et al., a user calls his misplaced phone from another phone. Upon connection to his misplaced phone, the user has command options to remotely change the misplaced phone's ring tone volume.


SUMMARY OF THE DESCRIPTION

Aspects of the present invention provide a method and system for locating a misplaced phone by sending an alert request message to the phone. The alert request message may be sent as an SMS or MMS message. Alternatively, the alert request message may be sent via Bluetooth or via Wi-Fi. Yet alternatively, the alert request message may be sent via Wireless Application Protocol (WAP) from a mobile phone or from a PDA. Yet alternatively, the alert request message may be sent via a web server.


In response to receipt of the alert request message, the mobile phone sounds an audible alert, irrespective of whether the phone is set to silent, vibrate or audible ring mode. In addition, the phone may display a pre-designated message, such as “Please contact John at 123-456-7890”, so that whoever finds the phone knows how to contact its owner. The phone may also play a pre-designated audio or video segment. The phone may also vibrate.


There is thus provided in accordance with an embodiment of the present invention a method for locating a misplaced mobile phone, including receiving, by a mobile phone, a transmitted message, identifying, by the mobile phone, the transmitted message as being an alert request, and in response to the identifying, generating, by the mobile phone, an alert.


There is additionally provided in accordance with an embodiment of the present invention a mobile phone, including a receiver for receiving a transmitted message, a message parser, coupled with the receiver, for identifying the transmitted message as being an alert request, and at least one speaker, coupled with the message parser, for sounding an audible alert, in response to the message parser identifying the alert request.


There is further provided in accordance with an embodiment of the present invention a method for locating a misplaced electronic communication device, including receiving, by an electronic communication device, a transmitted message, identifying, by the electronic communication device, the transmitted message as being an alert request, and in response to the identifying, generating, by the electronic communication device, an alert.


There is yet further provided in accordance with an embodiment of the present invention an electronic communication device, including a receiver for receiving a transmitted message a message parser, coupled with the receiver, for identifying the transmitted message as being an alert request, and at least one speaker, coupled with the message parser, for sounding an audible alert in response to the message parser identifying the alert request.





BRIEF DESCRIPTION OF THE DRAWINGS

The present invention will be more fully understood and appreciated from the following detailed description, taken in conjunction with the drawings in which:



FIG. 1 is a simplified flowchart of a method for locating a misplaced phone, in accordance with an embodiment of the present invention; and



FIG. 2 is a simplified block diagram of a mobile phone with circuitry for generating an alert that aids in locating the phone, in accordance with an embodiment of the present invention.





DETAILED DESCRIPTION

Aspects of the present invention relate to locating a misplaced mobile phone.


Reference is now made to FIG. 1, which is a simplified flowchart of a method for locating a misplace phone, in accordance with an embodiment of the present invention. The method of FIG. 1 is performed by a mobile phone. At step 110 the mobile phone receives a transmitted message. At step 120 the mobile phone parses the transmitted message and identifies the message as being an alert request.


Generally, an alert request includes a recognizable header and one or more parameter values. A user, at step 10, sets the parameter values by means of a message editor, such as message editor 201 (FIG. 2), to specify how the mobile phone responds to an alert request. A sample alert request is


“LocateMyPhone <personal identification #><time><volume><alert type>”,


where


the personal identification # parameter is a unique ID for the user,


the time parameter designates a time duration for an audible alert,


the volume parameter designates a sound volume for an audible alert, and


the alert type parameter designates a sound pattern for an audible alert. A sound pattern may be, for example, a repetitive “3 beeps+silence” pattern, or a rising volume alert that starts with an initial volume and increases the volume over time.


If the time parameter is not set, then the audible alert may be sounded for a default amount of time, or alternatively may be sounded until manually stopped. If the volume parameter is not set, then the audible alert may be sounded at a default sound volume. If the alert type parameter is not set, then the alert may be sounded according to a default sound pattern.


If the transmitted message is identified at step 120 as being an alert request, then at step 130 the mobile phone sounds an audible alert. The time, volume and alert type parameters described above govern the audible alert sounded at step 130. In addition, at step 140 the mobile phone displays a visible pre-designated message, such as “Please contact John at 123-456-7890” so that whoever finds the phone knows how to contact its owner. The pre-designated message displayed at step 140 may also be set using a parameter value.


Optionally, at step 150 the mobile phone may play a pre-designated audio/video recording, in addition to or instead of displaying the pre-designated message at step 140. As above, the pre-designated audio/video recording may be set using a parameter value. The pre-designated audio/video recording may indicate that the phone is lost, and describe how to contact the phone's owner.


Optionally, the mobile phone may vibrate, so as to assist people in finding it.


According to various embodiments of the present invention, the transmitted message received at step 110 may be transmitted at step 20, by means of a transmitter such as transmitter 202 (FIG. 2), in a number of different ways. The transmitted message may be transmitted inter alia as an SMS message, or as an MMS message. Use of an MMS message facilitates transmission of a pre-designated audio/video recording.


The transmitted message may be transmitted via Wireless Application Protocol (WAP) from a mobile phone or from a PDA.


The transmitted message may be transmitted via a web server.


The transmitted message may be transmitted over a Bluetooth connection, or over a Wi-Fi connection. For Bluetooth transmission, the transmitted message may be sent as a vCard, which generally includes a message in the name field, from a Bluetooth transmitter to the mobile phone using the Object Exchange (OBEX) protocol. Bluetooth generally has a limited range of approximately 10 meters, for transmissions made by a mobile phone, and has a larger range of up to 200 meters for transmissions made by computers with Class 1 transmitters.


For Wi-Fi transmission, the transmitted message may be included in a data section of an element of an 802.11 IEEE standard beacon. Beacon element ID 221 in the 802.11 standard is a vendor-specific element and, as such, can be used for adding data to the Wi-Fi protocol. In accordance with an embodiment of the present invention, the alert request message may be embedded in the data section of element ID 221, as follows.












Element ID 221 in 802.11 Beacon










Field
Value







Element ID
221



Length



OUI
Hex vendor code



Data
Alert request message











The field OUI represents a three-octet Organizationally Unique Identifier. For example, the OUI for Microsoft Corporation is 00:50:f2. The OUI is unique for each vendor. It will thus be appreciated by those skilled in the art that for Wi-Fi transmission, step 120 may be performed using an 802.11 protocol sniffer (element 210 of FIG. 2) that captures a beacon from a wireless access point, searches for element ID 221 (element 220 of FIG. 2), and determines whether or not the data field contains an alert request message.


Reference is now made to FIG. 2, which is a simplified block diagram of a mobile phone 200 with circuitry for generating an alert that aids in locating the phone, in accordance with an embodiment of the present invention. As shown in FIG. 2, mobile phone 200 includes a receiver 210, a message parser 220, at least one speaker 230, a display 240 and an optional audio/video player 250. Receiver 210 receives a transmitted message and forwards the message to message parser 220. Receiver 210 may be inter alia an SMS message receiver or an MMS message receiver. Receiver 210 may be inter alia a Bluetooth receiver or a Wi-Fi receiver.


Message parser 220 receives a message as input, parses the message to determine whether or not the message is an alert request, and generates as output an indicator if the message is an alert request.


Speaker(s) 230 receives as input the indicator from message parser 220 and generates as output an audible alert. As indicated hereinabove, the alert request may include parameter values that govern the time duration, sound volume and sound pattern of the audible alert. Display 240 receives as input the indicator from message parser 220, and generates as output a pre-designated display message. As indicated hereinabove, the pre-designated display message may be a parameter value in the alert request. Audio/video player 250 receives as input the indicator from message parser 220, and generates as output a pre-designated audio/video recording.


In reading the above description, persons skilled in the art will realize that there are many apparent variations that can be applied to the methods and systems described. Thus it may be appreciated from FIGS. 1 and 2 that embodiments of the present invention are not limited to mobile phones, and apply generally to electronic devices that have communication capability, such as portable digital assistants (PDAs) and pagers.


In the foregoing specification, the invention has been described with reference to specific exemplary embodiments thereof. It will, however, be evident that various modifications and changes may be made to the specific exemplary embodiments without departing from the broader spirit and scope of the invention as set forth in the appended claims. Accordingly, the specification and drawings are to be regarded in an illustrative rather than a restrictive sense.

Claims
  • 1. A mobile phone, comprising: a Wi-Fi receiver configured to capture a beacon from a wireless access point over a local network;a parser, coupled with said Wi-Fi receiver, configured to identify a misplaced phone alert request within the captured beacon, the misplaced phone alert request including at least one user-defined parameter value that specifies a setting for an audible alert; andcircuitry coupled with said parser, the circuitry configured to generate the audible the misplaced phone alert in response to identification of the misplaced phone alert request and based on the setting specified by the at least one user-defined parameter value.
  • 2. The mobile phone of claim 1, wherein said parser is configured to search for a vendor-specific element within the captured beacon, and identify the misplaced phone alert request within the vendor-specific element.
  • 3. The mobile phone of claim 1, wherein the circuitry is configured to generate the audible alert for an amount of time specified by the at least one user-defined parameter value.
  • 4. The mobile phone of claim 1, wherein the circuitry is configured to generate the audible alert at a volume specified by the at least one user-defined parameter value.
  • 5. The mobile phone of claim 1, wherein the circuitry is configured to generate the audible alert according to a sound pattern specified by the at least one user-defined parameter value.
  • 6. The mobile phone of claim 1, further comprising a display, coupled with said parser, configured to display a pre-designated image in response to the identification of the misplaced phone alert request.
  • 7. The mobile phone of claim 1, further comprising a light emitter, coupled with said parser, configured to emit light in response to the identification of the misplaced phone alert request.
  • 8. The mobile phone of claim 1, wherein the audible alert includes a vibration of the mobile phone.
  • 9. The mobile phone of claim 1, further comprising an audio player configured to play a pre-designated audio recording in response to the identification of the misplaced phone alert request.
  • 10. The mobile phone of claim 1, further comprising a video player configured to play a pre-designated video recording in response to the identification of the misplaced phone alert request.
  • 11. A method for locating a misplaced mobile phone, comprising: capturing, by a mobile phone and via a local network, a beacon from a wireless access point;identifying, by the mobile phone, a request within the captured beacon for a misplace phone alert, the request including at least one user-defined parameter value specifying a setting for the misplaced phone alert; andin response to said identifying, generating, by the mobile phone, the misplaced phone alert using the setting specified by the at least one user-defined parameter value.
  • 12. The method of claim 11, further comprising searching for a vendor-specific element within the captured beacon, and wherein said identifying identifies the request within the vendor-specific element.
  • 13. The method of claim 11, wherein said generating comprises sounding the misplaced phone alert for an amount of time specified by the at least one user-defined parameter value.
  • 14. The method of claim 11, wherein said generating comprises sounding the misplaced phone alert at a volume specified by the at least one user-defined parameter value.
  • 15. The method of claim 11, wherein said generating comprises sounding the misplaced phone alert according to a sound pattern specified by the at least one user-defined parameter value.
  • 16. The method of claim 11, wherein said generating the misplaced phone alert comprises emitting light.
  • 17. The method of claim 11, wherein said generating the misplaced phone alert comprises vibrating the mobile phone.
  • 18. The method of claim 11, further comprising, in response to said identifying, displaying, by the mobile phone, a pre-designated image.
  • 19. The method of claim 11, further comprising, in response to said identifying, playing, by the mobile phone, at least one of a pre-designated audio recording or a pre-designated video recording.
  • 20. The mobile device of claim 1, wherein the circuitry is configured to generate the audible alert by using at least one of a speaker or a vibrator.
Parent Case Info

This application is a continuation of assignee's application U.S. Ser. No. 12/144,671, entitled MOBILE PHONE LOCATOR, filed on Jun. 24, 2008 by Uri Ron, Eyal Bychkov, Itay Sherman and Nataly Kremer.

US Referenced Citations (260)
Number Name Date Kind
4969180 Watterson et al. Nov 1990 A
5313557 Osterhout May 1994 A
5381086 Aslan Jan 1995 A
5418448 Aslan May 1995 A
5625673 Grewe et al. Apr 1997 A
5628055 Stein May 1997 A
5729213 Ferrari Mar 1998 A
5758280 Kimura May 1998 A
5809115 Inkinen Sep 1998 A
5890016 Tso Mar 1999 A
5893037 Reele et al. Apr 1999 A
5898758 Rosenberg Apr 1999 A
5907815 Grimm et al. May 1999 A
5913227 Raz et al. Jun 1999 A
5928367 Nelson et al. Jul 1999 A
5983073 Ditzik Nov 1999 A
6029074 Irvin Feb 2000 A
6158884 Lebby et al. Dec 2000 A
6188917 Laureanti Feb 2001 B1
6195562 Pirhonen et al. Feb 2001 B1
6201867 Koike Mar 2001 B1
6209011 Vong et al. Mar 2001 B1
6212414 Alameh et al. Apr 2001 B1
6224254 Hayek et al. May 2001 B1
6236969 Ruppert et al. May 2001 B1
6243578 Koike Jun 2001 B1
6263218 Kita Jul 2001 B1
6272359 Kivela et al. Aug 2001 B1
6307348 Green Oct 2001 B1
6477357 Cook Nov 2002 B1
6516202 Hawkins et al. Feb 2003 B1
6553567 Wugofski et al. Apr 2003 B1
6565608 Fein et al. May 2003 B1
6594370 Anderson Jul 2003 B1
6600929 Toncich et al. Jul 2003 B1
6640113 Shin et al. Oct 2003 B1
6665802 Ober Dec 2003 B1
6690947 Tom Feb 2004 B1
6694125 White et al. Feb 2004 B2
6696941 Baker Feb 2004 B2
6751474 Lin et al. Jun 2004 B1
6757551 Newman et al. Jun 2004 B2
6760600 Nickum Jul 2004 B2
6775206 Karhu Aug 2004 B2
6778436 Piau et al. Aug 2004 B2
6882870 Kivela et al. Apr 2005 B2
6888202 Kang et al. May 2005 B2
6898283 Wycherley et al. May 2005 B2
6901245 Boyle May 2005 B1
6907264 Sterkel Jun 2005 B1
6912287 Fukumoto et al. Jun 2005 B1
6952181 Karr et al. Oct 2005 B2
6957049 Takeda Oct 2005 B1
6968394 El-Rafie Nov 2005 B1
6978160 Hutchison et al. Dec 2005 B2
6983244 Junqua et al. Jan 2006 B2
6999792 Warren Feb 2006 B2
7016481 McElvaney Mar 2006 B2
7016707 Fujisawa et al. Mar 2006 B2
7031692 Zanzi Apr 2006 B1
7076272 Ikeda et al. Jul 2006 B2
7085542 Dietrich et al. Aug 2006 B2
7089035 Ando et al. Aug 2006 B2
7103380 Ditzik Sep 2006 B1
7127053 Laljiani Oct 2006 B1
7130664 Williams Oct 2006 B1
7146139 Nevermann Dec 2006 B2
7155745 Shin et al. Dec 2006 B1
7194285 Tom Mar 2007 B2
7200416 Aisenberg Apr 2007 B2
7215980 Chai et al. May 2007 B2
7231181 Kohli et al. Jun 2007 B2
7233809 Kanevsky et al. Jun 2007 B2
7242963 Karstens et al. Jul 2007 B1
7266391 Warren Sep 2007 B2
7308272 Wortham Dec 2007 B1
7311551 Krula Dec 2007 B1
7313423 Griffin et al. Dec 2007 B2
7373179 Stine et al. May 2008 B2
7383061 Hawkins Jun 2008 B1
7383362 Yu et al. Jun 2008 B2
7395313 Ketola Jul 2008 B2
7428429 Gantz et al. Sep 2008 B2
7450461 Kotani et al. Nov 2008 B2
7477919 Warren Jan 2009 B2
7499722 McDowell et al. Mar 2009 B2
7499729 Lie et al. Mar 2009 B2
7509094 Moran et al. Mar 2009 B2
7512402 Narayanaswami et al. Mar 2009 B2
7515937 Lee Apr 2009 B2
7555264 Ishiwata et al. Jun 2009 B2
7596666 Ahn et al. Sep 2009 B2
7623892 Hawkins Nov 2009 B2
7706850 Parivash Apr 2010 B2
7739738 Sobel et al. Jun 2010 B1
7742787 Nghiem et al. Jun 2010 B2
7746409 Okamoto et al. Jun 2010 B2
7774027 Parikh et al. Aug 2010 B2
7783318 Wilson et al. Aug 2010 B2
7787405 Dettinger et al. Aug 2010 B2
7813697 McKillop Oct 2010 B2
7814304 Cornwell et al. Oct 2010 B2
7827337 Jeong Nov 2010 B2
7835827 Peed Nov 2010 B2
7873385 Boireau et al. Jan 2011 B2
7890947 Toyoshima Feb 2011 B2
7953455 Moran et al. May 2011 B2
7970433 Sherman et al. Jun 2011 B2
7971046 Moran et al. Jun 2011 B2
8058988 Medina Nov 2011 B1
8063888 McFarlane Nov 2011 B2
8069282 Sherman et al. Nov 2011 B2
8180395 Moran et al. May 2012 B2
8238961 Bychkov et al. Aug 2012 B2
8260348 Sherman Sep 2012 B2
8327124 Sherman et al. Dec 2012 B2
8356062 Shinohara et al. Jan 2013 B2
8391921 Moran et al. Mar 2013 B2
8406814 Bychkov et al. Mar 2013 B2
8412226 Ron Apr 2013 B2
8750928 Moran et al. Jun 2014 B2
8750936 Bychkov et al. Jun 2014 B2
8755846 Moran et al. Jun 2014 B2
8811363 Velasco Aug 2014 B2
8850086 Sherman et al. Sep 2014 B2
8892164 Sherman Nov 2014 B2
9288292 Bychkov et al. Mar 2016 B2
20020075189 Carillo et al. Jun 2002 A1
20020090980 Wilcox et al. Jul 2002 A1
20020151327 Levitt Oct 2002 A1
20020183004 Fulton Dec 2002 A1
20030078036 Chang et al. Apr 2003 A1
20030084287 Wang et al. May 2003 A1
20030115930 Kappi et al. Jun 2003 A1
20030191818 Rankin Oct 2003 A1
20030214780 Oh-Yang et al. Nov 2003 A1
20030228875 Alapuranen Dec 2003 A1
20040057578 Brewer Mar 2004 A1
20040063475 Weng Apr 2004 A1
20040068653 Fascenda Apr 2004 A1
20040233930 Colby, Jr. Nov 2004 A1
20040236997 Poo Nov 2004 A1
20040248623 Nelson et al. Dec 2004 A1
20040266424 Park et al. Dec 2004 A1
20040268005 Dickie Dec 2004 A1
20050059429 Liu et al. Mar 2005 A1
20050070225 Lee Mar 2005 A1
20050124305 Stichelbout Jun 2005 A1
20050141700 Takeda et al. Jun 2005 A1
20050150122 Cho et al. Jul 2005 A1
20050150697 Altman et al. Jul 2005 A1
20050159184 Kerner et al. Jul 2005 A1
20050207599 Fukumoto et al. Sep 2005 A1
20050228980 Brokish et al. Oct 2005 A1
20050233749 Karaoguz et al. Oct 2005 A1
20050239404 Karabinis Oct 2005 A1
20060003804 Liu Jan 2006 A1
20060025158 Leblanc et al. Feb 2006 A1
20060035663 Cheng Feb 2006 A1
20060056446 Lee et al. Mar 2006 A1
20060078122 Dacosta Apr 2006 A1
20060094481 Gullickson May 2006 A1
20060105722 Kumar May 2006 A1
20060116113 Gass Jun 2006 A1
20060128376 Alexis Jun 2006 A1
20060154688 Chai et al. Jul 2006 A1
20060163493 Antanouski Jul 2006 A1
20060190321 Martins Nicho et al. Aug 2006 A1
20060200843 Morgan Sep 2006 A1
20060209809 Ellingham et al. Sep 2006 A1
20060241353 Makino et al. Oct 2006 A1
20060245585 Yin et al. Nov 2006 A1
20060271678 Jessup Nov 2006 A1
20060273914 Carreras et al. Dec 2006 A1
20070004446 Moran et al. Jan 2007 A1
20070004450 Parikh Jan 2007 A1
20070008582 Cheng Jan 2007 A1
20070018957 Seo Jan 2007 A1
20070072620 Levitan Mar 2007 A1
20070073868 Nelson Mar 2007 A1
20070077924 Bhogal et al. Apr 2007 A1
20070079030 Okuley et al. Apr 2007 A1
20070085743 Eberhardt et al. Apr 2007 A1
20070105572 Kim May 2007 A1
20070115180 Kish May 2007 A1
20070124536 Carper May 2007 A1
20070145152 Jogand-Coulomb et al. Jun 2007 A1
20070149240 Brok Jun 2007 A1
20070161404 Yasujima et al. Jul 2007 A1
20070167167 Jiang Jul 2007 A1
20070168652 Mylly et al. Jul 2007 A1
20070175994 Fruhauf Aug 2007 A1
20070197266 Chang Aug 2007 A1
20070232233 Liu et al. Oct 2007 A1
20070233955 Luo et al. Oct 2007 A1
20070241261 Wendt Oct 2007 A1
20070263811 Lin et al. Nov 2007 A1
20070282471 Lee Dec 2007 A1
20070285326 McKinzie Dec 2007 A1
20070288583 Rensin et al. Dec 2007 A1
20080008142 Aldaz et al. Jan 2008 A1
20080009325 Zinn et al. Jan 2008 A1
20080026794 Warren Jan 2008 A1
20080031201 Lee Feb 2008 A1
20080040354 Ray et al. Feb 2008 A1
20080063193 Nishioka Mar 2008 A1
20080070501 Wyld Mar 2008 A1
20080076437 Wilson et al. Mar 2008 A1
20080125189 Tomoda May 2008 A1
20080130604 Boyd Jun 2008 A1
20080140886 Izutsu Jun 2008 A1
20080186162 Rajan et al. Aug 2008 A1
20080198138 McFarlane Aug 2008 A1
20080205379 Naqvi Aug 2008 A1
20080279359 Tiliks et al. Nov 2008 A1
20080305833 Sherman et al. Dec 2008 A1
20080312780 Peed Dec 2008 A1
20090009478 Badali et al. Jan 2009 A1
20090011794 Seo Jan 2009 A1
20090033487 McFadden et al. Feb 2009 A1
20090043963 Lahcanski et al. Feb 2009 A1
20090088151 Karabinis Apr 2009 A1
20090109897 Woo Apr 2009 A1
20090147758 Kumar Jun 2009 A1
20090167678 Orr et al. Jul 2009 A1
20090176528 Moran et al. Jul 2009 A1
20090177884 Bieh et al. Jul 2009 A1
20090239470 Sherman Sep 2009 A1
20090243397 Cook Oct 2009 A1
20090318197 Ron Dec 2009 A1
20100006764 Bushberg Jan 2010 A1
20100013714 Azhari Jan 2010 A1
20100013730 Azhari Jan 2010 A1
20100033397 Narasimhan et al. Feb 2010 A1
20100056210 Bychkov et al. Mar 2010 A1
20100061431 Jyrkka et al. Mar 2010 A1
20100075704 McHenry et al. Mar 2010 A1
20100081402 Itkin et al. Apr 2010 A1
20100093401 Moran et al. Apr 2010 A1
20100146256 Luo et al. Jun 2010 A1
20110014951 Sherman et al. Jan 2011 A1
20110298589 McFarlane Dec 2011 A1
20110314268 Sherman et al. Dec 2011 A1
20120231778 Chen et al. Sep 2012 A1
20120282912 Bychkov et al. Nov 2012 A1
20120289291 Moran et al. Nov 2012 A1
20120295614 Sherman Nov 2012 A1
20130005399 Moran et al. Jan 2013 A1
20130023246 Ellingham et al. Jan 2013 A9
20130040702 Sherman et al. Feb 2013 A1
20130165100 Moran et al. Jun 2013 A1
20130183929 Bychkov et al. Jul 2013 A1
20130183955 Ron Jul 2013 A1
20140071967 Velasco Mar 2014 A1
20140274206 Moran et al. Sep 2014 A1
20140295911 Bychkov et al. Oct 2014 A1
20150050959 Sherman et al. Feb 2015 A1
20150078363 Sherman Mar 2015 A1
20150237191 Moran et al. Aug 2015 A1
20160028864 Moran et al. Jan 2016 A1
Foreign Referenced Citations (8)
Number Date Country
1871075 Dec 2007 EP
9421058 Sep 1994 WO
0059247 Oct 2000 WO
0186922 Nov 2001 WO
03103174 Dec 2003 WO
WO-2006126777 Nov 2006 WO
WO-2009040796 Apr 2009 WO
WO-2009101618 Aug 2009 WO
Non-Patent Literature Citations (64)
Entry
Helleseth, H., Wi-Fi Security, How to Break and Exploit, Thesis for the degree Master of Science, Department of Informatics, University of Bergen, Jun. 2006.
“Advisory Action”, U.S. Appl. No. 13/612,900, Jan. 14, 2014, 3 pages.
“Final Office Action”, U.S. Appl. No. 12/151,079, Nov. 10, 2010, 21 pages.
“Final Office Action”, U.S. Appl. No. 13/564,728, Jan. 28, 2013, 25 pages.
“Final Office Action”, U.S. Appl. No. 13/564,728, Feb. 6, 2014, 29 pages.
“Final Office Action”, U.S. Appl. No. 13/612,900, Oct. 1, 2013, 6 pages.
“Final Office Action”, U.S. Appl. No. 14/280,879, Jan. 22, 2015, 10 pages.
“Final Office Action”, U.S. Appl. No. 14/540,568, Dec. 3, 2015, 9 pages.
“Mobile Phones”, Federal Office of Public Health http://www.bag.admin.ch/themen/strahlung/00053/00673/04265/index.html?lang=en, Feb. 5, 2009, 11 pages.
“Non-Final Office Action”, U.S. Appl. No. 11/380,944, Oct. 16, 2008, 6 pages.
“Non-Final Office Action”, U.S. Appl. No. 11/827,525, Dec. 3, 2010, 8 pages.
“Non-Final Office Action”, U.S. Appl. No. 12/151,079, Aug. 25, 2010, 17 pages.
“Non-Final Office Action”, U.S. Appl. No. 12/151,079, Nov. 22, 2011, 25 pages.
“Non-Final Office Action”, U.S. Appl. No. 12/406,327, Dec. 13, 2010, 5 pages.
“Non-Final Office Action”, U.S. Appl. No. 12/525,820, Dec. 16, 2011, 11 pages.
“Non-Final Office Action”, U.S. Appl. No. 12/876,129, Jul. 15, 2011, 10 pages.
“Non-Final Office Action”, U.S. Appl. No. 13/106,863, Oct. 20, 2011, 4 pages.
“Non-Final Office Action”, U.S. Appl. No. 13/170,169, Apr. 27, 2012, 6 pages.
“Non-Final Office Action”, U.S. Appl. No. 13/471,751, Oct. 22, 2012, 10 pages.
“Non-Final Office Action”, U.S. Appl. No. 13/564,728, Jul. 11, 2013, 30 pages.
“Non-Final Office Action”, U.S. Appl. No. 13/564,728, Oct. 11, 2012, 19 pages.
“Non-Final Office Action”, U.S. Appl. No. 13/607,819, Nov. 8, 2013, 9 pages.
“Non-Final Office Action”, U.S. Appl. No. 13/612,900, Feb. 3, 2014, 10 pages.
“Non-Final Office Action”, U.S. Appl. No. 13/612,900, Aug. 16, 2013, 13 pages.
“Non-Final Office Action”, U.S. Appl. No. 13/761,188, Sep. 10, 2013, 9 pages.
“Non-Final Office Action”, U.S. Appl. No. 13/778,145, Jul. 5, 2013, 12 pages.
“Non-Final Office Action”, U.S. Appl. No. 14/282,332, Sep. 18, 2014, 6 pages.
“Non-Final Office Action”, U.S. Appl. No. 14/283,231, Mar. 23, 2015, 14 pages.
“Non-Final Office Action”, U.S. Appl. No. 14/499,273, Jan. 25, 2016, 8 pages.
“Non-Final Office Action”, U.S. Appl. No. 14/540,568, Aug. 14, 2015, 10 pages.
“Notice of Allowance”, U.S. Appl. No. 11/380,944, Feb. 9, 2009, 7 pages.
“Notice of Allowance ”, U.S. Appl. No. 11/380,944, Feb. 9, 2009, 7 pages.
“Notice of Allowance”, U.S. Appl. No. 11/827,525, Mar. 3, 2011, 9 pages.
“Notice of Allowance”, U.S. Appl. No. 12/151,079, May 8, 2012, 10 pages.
“Notice of Allowance”, U.S. Appl. No. 12/406,327, Feb. 4, 2011, 4 pages.
“Notice of Allowance”, U.S. Appl. No. 12/525,820, Mar. 6, 2012, 7 pages.
“Notice of Allowance”, U.S. Appl. No. 12/552,440, Apr. 3, 2012, 10 pages.
“Notice of Allowance”, U.S. Appl. No. 12/876,129, Oct. 17, 2011, 5 pages.
“Notice of Allowance”, U.S. Appl. No. 13/106,863, Jun. 13, 2012, 5 pages.
“Notice of Allowance”, U.S. Appl. No. 13/170,169, Aug. 8, 2012, 5 pages.
“Notice of Allowance”, U.S. Appl. No. 13/471,751, Nov. 2, 2012, 8 pages.
“Notice of Allowance”, U.S. Appl. No. 13/553,837, Dec. 10, 2012, 11 pages.
“Notice of Allowance”, U.S. Appl. No. 13/564,728, Aug. 4, 2014, 12 pages.
“Notice of Allowance”, U.S. Appl. No. 13/607,819, Feb. 10, 2014, 5 pages.
“Notice of Allowance”, U.S. Appl. No. 13/612,900, Jun. 2, 2014, 7 pages.
“Notice of Allowance”, U.S. Appl. No. 13/761,188, Feb. 4, 2014, 7 pages.
“Notice of Allowance”, U.S. Appl. No. 13/778,145, Feb. 14, 2014, 8 pages.
“Notice of Allowance”, U.S. Appl. No. 14/282,332, Jan. 14, 2015, 7 pages.
“Notice of Allowance”, U.S. Appl. No. 14/283,231, Jun. 26, 2015, 5 pages.
“Notice of Allowance”, U.S. Appl. No. 14/283,231, Oct. 27, 2015, 4 pages.
“Restriction Requirement”, U.S. Appl. No. 11/380,944, Oct. 2, 2008, 6 pages.
“Restriction Requirement”, U.S. Appl. No. 11/827,525, Aug. 17, 2010, 6 pages.
“Restriction Requirement”, U.S. Appl. No. 12/151,079, Aug. 4, 2010, 8 pages.
“Restriction Requirement”, U.S. Appl. No. 12/552,440, Jan. 5, 2012, 7 pages.
“Restriction Requirement”, U.S. Appl. No. 13/553,837, Nov. 5, 2012, 6 pages.
Friedman,“R., Mechanism of short-term ERK activation by electromagnetic fields at mobile phone frequency”, Manuscript BJ20061653, BJ Immediate Publication http://www.biochemj.org/bj/405/0559/4050559.pdf, Apr. 25, 2007, 33 pages.
Hondou,, “Passive exposure to mobile phones: enhancement of intensity by reflection”, Journal of the Physical Society of Japan, vol. 75, No. 8 Retrieved at: http://www.empt.phys.tohoku.ac.jp/-hondou/JPSJ-75-084801.pdf, Aug. 2006, 5 pages.
Kuhn,“Assessment of the radio-frequency electromagnetic fields induced in the human body from mobile phones user with hands-free kits”, Phys. Med. Biol., vol. 54, pp. 5493-5508, Aug. 26, 2009, 16 pages.
“Non-Final Office Action”, U.S. Appl. No. 14/803,129, Feb. 2, 2016, 11 pages.
“Non-Final Office Action”, U.S. Appl. No. 14/540,568, Apr. 27, 201, 23 pages.
“Non-Final Office Action”, U.S. Appl. No. 14/696,438, Feb. 12, 2016, 8 pages.
“Final Office Action”, U.S. Appl. No. 14/499,273, Jul. 8, 2016, 9 pages.
“Final Office Action”, U.S. Appl. No. 14/540,568, Aug. 26, 2016, 21 pages.
“Notice of Allowance”, U.S. Appl. No. 14/696,438, Jul. 26, 2016, 7 pages.
Related Publications (1)
Number Date Country
20130183955 A1 Jul 2013 US
Continuations (1)
Number Date Country
Parent 12144671 Jun 2008 US
Child 13778155 US