Source: http://www.google.com/patents/US20040063423?dq=6480844
Timestamp: 2016-02-12 02:27:57
Document Index: 259434982

Matched Legal Cases: ['art 20', 'art 20', 'art 30', 'art 30', 'art 30', 'art 40', 'art 40', 'art 20', 'art 40']

Patent US20040063423 - Method and apparatus for operating a lost mobile communication device - Google PatentsSearch Images Maps Play YouTube News Gmail Drive More »Sign inPatentsAn apparatus and method of operating a lost mobile communication device. A lost mobile communication device message can be received at the receiver of the mobile communication device. Operation of specified functions of the mobile communication device can be suspended based on information in the lost...http://www.google.com/patents/US20040063423?utm_source=gb-gplus-sharePatent US20040063423 - Method and apparatus for operating a lost mobile communication deviceAdvanced Patent SearchPublication numberUS20040063423 A1Publication typeApplicationApplication numberUS 10/255,340Publication dateApr 1, 2004Filing dateSep 26, 2002Priority dateSep 26, 2002Also published asCN1685744A, US6782251, WO2004030382A1Publication number10255340, 255340, US 2004/0063423 A1, US 2004/063423 A1, US 20040063423 A1, US 20040063423A1, US 2004063423 A1, US 2004063423A1, US-A1-20040063423, US-A1-2004063423, US2004/0063423A1, US2004/063423A1, US20040063423 A1, US20040063423A1, US2004063423 A1, US2004063423A1InventorsHoward KagayOriginal AssigneeKagay Howard EdwardExport CitationBiBTeX, EndNote, RefManPatent Citations (9), Referenced by (29), Classifications (6), Legal Events (6) External Links: USPTO, USPTO Assignment, EspacenetMethod and apparatus for operating a lost mobile communication device
US 20040063423 A1Abstract
An apparatus and method of operating a lost mobile communication device. A lost mobile communication device message can be received at the receiver of the mobile communication device. Operation of specified functions of the mobile communication device can be suspended based on information in the lost mobile communication device message. Lost mobile communication device status information can then be displayed on the display of the mobile communication device. Images(6) Claims(20)
What is claimed is: 1. A method of operating a mobile communication device including a display, an input, and a receiver comprising: receiving a lost mobile communication device message at the receiver of the mobile communication device; suspending operation of specified functions of the mobile communication device; and displaying lost mobile communication device status information on the display of the mobile communication device. 2. The method of operating a mobile communication device according to claim 1, wherein the lost mobile communication device message includes a suspend mode activation command, and a callback number. 3. The method of operating a mobile communication device according to claim 1, wherein the lost mobile communication device status information includes a lost mobile communication device message, and a callback number. 4. The method of operating a mobile communication device according to claim 1, wherein the step of suspending operation of specific functions comprises: blocking access to personal information in the mobile communication device; and blocking access to wireless data services in the mobile communication device. 5. The method of operating a mobile communication device according to claim 1, further comprising: enabling an alert sequence; and disabling alert sequence after a specified callback number is dialed. 6. The method of operating a mobile communication device according to claim 5, further comprising re-enabling the alert sequence upon power up if a security code is not entered. 7. The method of operating a mobile communication device according to claim 1, further comprising: detecting a connection attempt to a number other than a specified lost mobile communication device callback number; and attempting a connection to the specified lost mobile communication device callback number upon detection of the connection attempt. 8. The method of operating a mobile communication device according to claim 1, further comprising: detecting an operation at the input of the mobile communication device; and attempting a connection to a specified lost mobile communication device callback number upon detection of the operation at the input of the mobile communication device. 9. The method of operating a mobile communication device according to claim 1, further comprising: attempting a connection to a specified lost mobile communication device callback number; and transmitting a found mobile communication device message upon connection to the specified lost mobile communication device callback number. 10. The method of operating a mobile communication device according to claim 1, further comprising: attempting a connection to a specified lost mobile communication device callback number; and providing a ring tone at the mobile communication device upon connection to the specified lost mobile communication device callback number. 11. A mobile communication device comprising: a display; a receiver; an input; an output; and a security module coupled to the display, the receiver, the input, and the output, the security module being configured to receive a lost mobile communication device message from the receiver of the mobile communication device, suspend operation of specified functions of the mobile communication device, and display lost mobile communication device status information on the display of the mobile communication device. 12. The mobile communication device according to claim 11, wherein the security module is further configured to enable an alert sequence at the output, and disable alert sequence after a specified callback number is dialed. 13. The mobile communication device according to claim 11, wherein the security module is further configured to detect an operation at the input of the mobile communication device, and attempt a connection to a specified lost mobile communication device callback number upon detection of the operation at the input of the mobile communication device. 14. The mobile communication device according to claim 11, wherein the security module is further configured to attempt a connection to a specified lost mobile communication device callback number and transmit a found mobile communication device message upon connection to the specified lost mobile communication device callback number. 15. The mobile communication device according to claim 11, wherein the security module is further configured to attempt a connection to a specified lost mobile communication device callback number, and provide a ring tone at the output of the mobile communication device upon connection to the specified lost mobile communication device callback number. 16. A mobile communication device comprising: a lost mobile communication device message receiver; a lost mobile communication device suspend module coupled to the lost mobile communication device message receiver; a lost mobile communication device display module coupled to the lost mobile communication device suspend module; a lost mobile communication device message display coupled to the lost mobile communication device display module. 17. The mobile communication device according to claim 16, further comprising: a lost mobile communication device audible alert module; and an audible alert control module coupled to the a lost mobile communication device suspend module and selectively coupled to the lost mobile communication device audible alert module. 18. The mobile communication device according to claim 16, further comprising: a lost mobile communication device information database coupled to the lost mobile communication device suspend module, the lost mobile communication device information database including a lost mobile communication device status entry, and a callback number entry. 19. The mobile communication device according to claim 16, further comprising: a transmitter; and a voice tag insertion module coupled to the lost mobile communication device suspend module and the transmitter. 20. The mobile communication device according to claim 16, further comprising: an input coupled to the lost mobile communication device suspend module, wherein the lost mobile communication device suspend module attempts a connection to a lost mobile communication device callback number upon detection of an operation at the input. Description
BACKGROUND OF THE INVENTION [0001] 1. Field of Invention [0002] The present invention is directed to a method and apparatus for operating a lost mobile communication device. In particular, the present invention is directed to a method and apparatus for security of a lost mobile communication device. [0003] 2. Description of Related Art [0004] Presently, mobile communication devices such as portable phones, pagers, personal digital assistants, laptop computers, or the like are becoming smaller and more portable. Unfortunately, this portability and size reduction increases the probability of an owner losing the mobile communication device. For example, a portable phone may fall out of an owner's pocket or a notebook computer may be left on a plane. A person finding the mobile communication device may find it difficult to determine the owner and how to contact the owner. Also, the finder may also fraudulently use the mobile communication device. For example, the finder may make numerous long distance calls on a portable phone. The finder may also obtain confidential personal information about the owner in a calendar, datebook, or phonebook on the mobile communication device. [0005] Thus, there is a need for suspending operation of specified functions of a mobile communication device if the mobile communication device is lost. There is also a need for assisting the finder of a lost mobile communication device in contacting the actual owner of the mobile communication device. These, and many other needs are satisfied by the present invention. SUMMARY OF THE INVENTION [0006] The invention provides an apparatus and method of operating a lost mobile communication device. A lost mobile communication device message is received at the receiver of the mobile communication device. Operation of specified functions of the mobile communication device are suspended. Lost mobile communication device status information is then displayed on the display of the mobile communication device. Also, an alert sequence can be enabled. The alert sequence can be disabled after a specified callback number is dialed. Furthermore, an operation at the input of the mobile communication device can be detected. A connection to the specified lost mobile communication device callback number can be attempted upon detection of the operation at the input of the mobile communication device. A found mobile communication device message can then be transmitted to the owner upon connection to the specified lost mobile communication device callback number. A ring tone can be provided at the mobile communication device upon connection to the specified lost mobile communication device callback number to instruct a finder to communicate with the owner of the lost mobile communication device.
BRIEF DESCRIPTION OF THE DRAWINGS [0007] The preferred embodiments of the present invention will be described with reference to the following figures, wherein like numerals designate like elements, and wherein: [0008] [0008]FIG. 1 is an exemplary block diagram of a mobile communication device according to a first embodiment; [0009] [0009]FIG. 2 is an exemplary flowchart outlining the operations of a security module of FIG. 1 according to a first embodiment; [0010] [0010]FIG. 3 is an exemplary flowchart outlining the operations of a security module of FIG. 1 according to a second embodiment; [0011] [0011]FIG. 4 is an exemplary flowchart outlining the operations of a security module of FIG. 1 according to a third embodiment; and [0012] [0012]FIG. 5 is an exemplary block diagram of a security module of a mobile communication device according to a fourth embodiment.
DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS [0013] [0013]FIG. 1 is an exemplary block diagram of a mobile communication device 10 according to a first embodiment. The mobile communication device 10 can include a controller 110 which can include a security module 120. The mobile communication device 10 can also include audio output circuitry 130, a display 140, an input 150, audio input circuitry 160, a transmitter 170, a receiver 180, and an antenna 190. The display 140 may be a liquid crystal display, a light emitting diode display, a plasma display, or any other display useful for outputting visual information. The input 150 may include a keypad, various buttons, a joystick, a rotary dial, a touchpad, or any other devices useful for inputting commands and data. All of the functions of the security module 120 may be performed by the controller 110 and all of the functions of the controller 110 may be performed by the security module 120. [0014] In operation, the transmitter 170 can transmit signals and the receiver 180 can receive signals across a mobile communication network via the antenna 190. The audio output circuitry 130 can output audio signals such as speech or tones and the audio input circuitry 160 can receive audio signals. The input 150 can receive commands and data. The display 140 can display visual information. For example, the display 140 can display a signal strength, a battery charge, a telephone number, animated graphics, Internet information, or any other visual information. [0015] The controller 110 and the security module 120 can control the operations of the mobile communication device 10. For example, the controller 110 can control the inputs and outputs of the mobile communication device. The controller 110 may also control incoming signals via the receiver 180 and outgoing signals via the transmitter 170. [0016] The security module 120 can control security operations of the mobile communication device 10. For example, when a user realizes the mobile communication device 10 is lost, the user can remotely activate a suspend mode. The user may activate this suspend mode by sending the mobile communication device 10 a lost communication device message such as a short messaging service message, a page, a telephone call including lost device information, a telephone call including a DTMF signal, or any other communication useful for communicating that the mobile communication device 10 has been lost. The lost communication device message can include callback information such as a callback number indicating a number for reaching the owner at if the mobile communication device 10 is found. The lost communication device message can also include a code, such as a suspend mode activation command, for enabling a suspend mode. The security module 120 can then store suspend mode information and callback information for use if the mobile communication device 10 is found. In the suspend mode, the security module 120 can suspend operation of specific functions. For example, the security module 120 can lock out use of personal features such as a phonebook, a datebook, a web browser, and any other features that can or should be locked out if the mobile communication device 10 is lost. [0017] The security module 120 can display lost mobile communication device status information on the display 140. This information can include a banner informing a finder of a lost mobile communication device that the device is lost. This information can also include a callback number for the finder to dial to contact the owner of a lost mobile communication device. This information can also include any other instructions useful for a finder of a lost mobile communication device. The security module 120 may suspend all outgoing calls except for the callback number, other designated numbers stored in the mobile communication device 10, and/or emergency numbers, such as 911. For example, the owner can designate numbers in the phonebook to be activated as callback numbers if the security module 120 enables a suspend mode. [0018] The security module 120 may automatically dial the callback number regardless of the entry of a number that a finder wishes to dial. For example, the security module 120 may allow entry of alternate numbers, but will force a call to the callback number. The security module 120 may also automatically dial the callback number after any key is pressed or any input is triggered. Additionally, the security module 120 may disable the audio output circuitry 130 until the call is connected with the callback number. When the call is connected with the callback number, the security module 120 may then provide a ring alert tone via to audio output circuitry 130 to prompt the finder to communicate with the owner. [0019] The security module 120 may also enable an alert sequence such as a sequence of loud beeps via the audio output 130 or a sequence of other audio, visual, or tactile signals to assist in locating the mobile communication device 10. For example, the security module 120 can initiate the alert sequence every ten seconds to assist in locating a lost mobile communication device if the owner is in a local area. The security module 120 can then eventually revert to the alert sequence every five minutes to conserve battery power. The alert sequence may stop when a key is pressed on the input 150. Alternately, the alert sequence may continue until the callback number is dialed, thus forcing a finder to call the callback number. Additionally, the alert sequence may continue until a security code is entered. For example, the security module 120 may temporarily stop the alert sequence when a call is placed to the callback number. The security module 120 may then revert to the alert sequence if a security code is not entered within a predetermined time after callback. Also, if a battery in the mobile communication device 10 is removed to stop the alert sequence, the security module 120 can restart the suspend mode and the alert sequence when the battery is replaced. The security code may be entered via the input 150, the audio input circuitry 160, via a call including a code to the receiver 180, or any other means useful for providing a code to the mobile communication device 10. [0020] [0020]FIG. 2 is an exemplary flowchart 20 outlining the operations of the security module 120 of FIG. 1 according to a first embodiment. In step 210, the flowchart begins. In step 220, the security module 120 can receive a suspend message such as a lost mobile communication device message that can include a callback number and a suspend code. In step 230, the security module 120 can enable a suspend mode. In the suspend mode, the security module 120 can disable operations of select mobile communication device functions including phonebook functions, select outgoing call functions, web browsing functions, or any other functions that should be suspended when a mobile communication device is lost. In step 240, the security module 120 can display lost mobile communication device status information on the display 140. For example, the security module 120 can display instructions for a finder of the mobile communication device 10, a callback number, or any other information useful for display on a lost mobile communication device. In step 250, the security module 120 can enable lost device functions. These functions can include automatically placing calls to a callback number, enabling audible alert sequences, or any other functions useful in a lost mobile communication device. In step 260, the flowchart 20 ends. [0021] [0021]FIG. 3 is an exemplary flowchart 30 outlining the operations of the security module 120 of FIG. 1 according to a second embodiment. This flowchart 30 illustrates one method of automatically placing calls to a callback number. In step 310, the flowchart begins. In step 320, the security module 120 receives an input. This input may be received via the input 150. For example, a finder of the mobile communication device 10 may provide input by attempting to place a call, by pressing a specific button such as a “send” button, by pressing any other button or key, or by any other means of providing input. In step 330, the security module 120 places a call to the callback number. For example, the security module 120 can ignore an attempt to place a call to a number other than the callback number and can force a connection attempt to the callback number. During this connection attempt, the security module 120 may disable an audio path including the audio input 160 and the audio output 130, or may play a message to a finder that a call attempt is being made to the owner of the mobile communication device 10. In step 340, if the call connects to the callback number, the security module 120 can insert a found mobile communication device message such as a voice tag. For example, the security module 120 can inform the owner that the call is from the lost mobile communication device 10. In step 350, the security module 120 can output a ring tone through the audio output circuitry 130. Thus, the finder will be prompted to pick up the mobile communication device 10 as if the finder is answering an incoming call. This ring tone may be a standard ring tone, a audible message that the owner is calling, or any other indication of a communication connection. In step 360, the security module 120 connects the audio path when the finder picks up the mobile communication device 10 to “answer” the connected communication. In step 370, the flowchart 30 ends. [0022] [0022]FIG. 4 is an exemplary flowchart 40 outlining the operations of the security module 120 of FIG. 1 according to a third embodiment. The flowchart 40 illustrates an audible alert sequence that can be initiated in step 250 of flowchart 20. In step 410, the flowchart begins. In step 420, the security module 120 begins the audible alert sequence described above. In step 430, the security module 120 determines if the callback number is dialed. If so, the security module 120 suspends the audible alert sequence in step 440 and returns to step 450. If the callback number is not dialed, the security module 120 advances to step 450. In step 450, the security module 120 determines if a security code has been entered. The security code may be entered via the input 150, via a communication through the receiver 180, via fingerprint recognition via the input 150, or by any other means of entering a security code. If the security code has not been entered, the security module 120 continues the audible alert sequence in step 460. For example, if the callback number was dialed, but the security code has not been entered for a predetermined time, the security module 120 can resume the audible alert sequence. If the security code has been entered, the security module 120 ends the audible alert sequence in step 470. For example, if the callback number has not been dialed and the owner finds the mobile communication device 10, the owner can end the audible alert sequence. In step 480, the security module 120 exits suspend mode. In step 490, the flowchart 40 ends. [0023] [0023]FIG. 5 is an exemplary block diagram of a security module 50 of a mobile communication device according to a fourth embodiment. The security module 50 can employ hardware to perform the functions of the security module 120. The security module 50 may be utilized in the mobile communication device 10 or in any other portable device. The security module 50 can include a suspend module 510, a lost device display module 520, a lost device information database 530, a voice tag insertion module 540, audible alert control circuitry 550, and an audible alert module 560. In operation, the suspend module 510 detects the receipt of a lost mobile communication device message and initiates a suspend mode of the mobile communication device 10. The lost device information database 530 can store information used when the suspend mode is activated. For example, the lost device information database 530 can store a callback number, information regarding which features should be suspended and which features can be accessed in suspend mode, lost mobile communication status information to be displayed on the display 140, a voice tag, or any other useful information. Some or all of the information in the lost device information database 530 may be obtained from the lost mobile communication device message. The suspend module 510 can send a signal to the lost device display module 520 to instruct the lost device display module 520 to display lost mobile communication device status information on the display 140. [0024] The suspend module 510 can also send a signal to the audible alert control circuitry 550. The audible alert control circuitry 550 can act as a switch to turn on the audible alert module 560, which generates an audible alert such as the alert sequence. The audible alert control circuitry 550 can also control the timing of the audible alert. For example, the audible alert module 560 can initiate the alert sequence every ten seconds to assist in locating a lost mobile communication device 10 if the owner is in a local area. The audible alert module 560 can then eventually revert to the alert sequence every five minutes to conserve battery power. The alert sequence may stop when a key is pressed on the input 150. Alternately, the alert sequence may continue until the callback number is dialed, thus forcing a finder to call the callback number. Additionally, the alert sequence may continue until a security code is entered. [0025] The suspend module 510 can also control the callback functions of the mobile communication device 10 described above. For example, the suspend module 510 can make a connection attempt to the callback number when a key is pressed on the mobile communication device 10. Upon callback, the suspend module 510 can instruct the voice tag insertion module 540 to insert a voice tag informing the owner that a call is being received from the lost mobile communication device 10. The voice tag insertion module 540 may then connect an audio path to allow the owner to communicate with the finder of the lost mobile communication device 10. [0026] The method of this invention is preferably implemented on a programmed processor. However, the controller 110, the security module 120, or the security module 50 may also be implemented on a general purpose or special purpose computer, a programmed microprocessor or microcontroller and peripheral integrated circuit elements, an ASIC or other integrated circuit, a hardware electronic or logic circuit such as a discrete element circuit, a programmable logic device such as a PLD, PLA, FPGA or PAL, or the like. In general, any device on which resides a finite state machine capable of implementing the flowcharts shown in the Figures may be used to implement the processor functions of this invention. [0027] While this invention has been described with specific embodiments thereof, it is evident that many alternatives, modifications, and variations will be apparent to those skilled in the art. For example, various components of the embodiments may be interchanged, added, or substituted in the other embodiments. Accordingly, the preferred embodiments of the invention as set forth herein are intended to be illustrative, not limiting. Various changes may be made without departing from the spirit and scope of the invention. Patent CitationsCited PatentFiling datePublication dateApplicantTitleUS5600708 *Aug 4, 1995Feb 4, 1997Nokia Mobile Phones LimitedOver the air locking of user identity modules for mobile telephonesUS5734978 *Dec 15, 1995Mar 31, 1998Nec CorporationMobile telephone with function to prevent illegal use and method and system for preventing illegal use of mobile telephone using the functionUS5809413 *Dec 19, 1996Sep 15, 1998Nokia Mobile Phones LimitedOver the air locking of user identity modules for mobile telephonesUS5864757 *Dec 12, 1995Jan 26, 1999Bellsouth CorporationMethods and apparatus for locking communications devicesUS5887250 *Jul 12, 1996Mar 23, 1999Nokia Mobile Phones LimitedMobile station having lock code based on secure valueUS6092133 *Oct 28, 1997Jul 18, 2000Nokia Mobile Phones LtdMethod for conveying control commands for SIM card from external apparatus to SIM cardUS6314283 *Apr 28, 1999Nov 6, 2001Nec America, Inc.Cellular phone subsidy lockUS6393270 *Oct 14, 1997May 21, 2002Bellsouth Intellectual Property Corp.Network authentication method for over the air activationUS6550010 *Feb 3, 2000Apr 15, 2003Bellsouth Intellectual Property Corp.Method and apparatus for a unit locked against use until unlocked and/or activated on a selected network* Cited by examinerReferenced byCiting PatentFiling datePublication dateApplicantTitleUS7454194 *Mar 25, 2004Nov 18, 2008Sharp Kabushiki KaishaMobile terminal with personal authentication function and mobile terminal systemUS7463889Aug 10, 2005Dec 9, 2008At&T Mobility Ii LlcIntelligent customer care support using network CAMEL subscription informationUS7602377 *Nov 9, 2004Oct 13, 2009Lg Electronics Inc.Mobile device and method for preventing undesired key depression in the sameUS7706792Aug 10, 2005Apr 27, 2010At&T Mobility Ii LlcIntelligent customer care supportUS7783281 *Apr 22, 2004Aug 24, 2010Sprint Spectrum L.P.Method and system for securing a mobile deviceUS7907937Dec 26, 2007Mar 15, 2011At&T Mobility Ii LlcPrepaid communication services utilizing a prepaid identifier combined with another identifierUS7983655Jun 20, 2007Jul 19, 2011At&T Mobility Ii LlcConditional call treatment for prepaid callsUS8090343May 29, 2007Jan 3, 2012At&T Mobility Ii LlcOptimized camel triggering for prepaid callingUS8090344Jul 23, 2007Jan 3, 2012At&T Mobility Ii LlcDynamic location-based rating for prepaid callsUS8112064 *Sep 7, 2007Feb 7, 2012Vodafone Group PlcFunction lock information notification method and mobile communication terminalUS8150396Dec 30, 2009Apr 3, 2012At&T Mobility Ii LlcIntelligent customer care supportUS8180321Sep 26, 2007May 15, 2012At&T Mobility Ii LlcRecovery of lost revenue in prepaid callsUS8601606Sep 20, 2004Dec 3, 2013Carolyn W. HafemanComputer recovery or returnUS8774798Aug 28, 2007Jul 8, 2014At&T Mobility Ii LlcDetermining capability to provide dynamic local time updates in a prepaid terminating callUS8892084Sep 10, 2012Nov 18, 2014The Invention Science Fund I, LlcDeactivation system and method for a transferable deviceUS9020466 *Aug 8, 2007Apr 28, 2015Yahoo! Inc.Remote profile modification for device recovery assistUS9106740Jun 23, 2006Aug 11, 2015The Invention Science Fund I, LlcTransferable device with alterable usage functionalityUS20040192256 *Mar 25, 2004Sep 30, 2004Hidenori KuwajimaMobile terminal with personal authentication function and mobile terminal systemUS20050107126 *Nov 9, 2004May 19, 2005Lg Electronics, Inc.Mobile device and method for preventing undesired key depression in the sameUS20060293090 *Jul 21, 2006Dec 28, 2006Sbc Knowledge Ventures, L.P.Network-based services for misplaced cellular mobile stationsUS20080014967 *Jul 9, 2007Jan 17, 2008Ntt Docomo, Inc.Mobile communication terminalUS20080032682 *Jun 23, 2006Feb 7, 2008Searete, LlcTransferable device with alterable usage functionalityUS20080064370 *Sep 7, 2007Mar 13, 2008Vodafone K.K.Function lock information notification method and mobile communication terminalUS20080096525 *Dec 26, 2007Apr 24, 2008At&T Mobility Ii LlcMulti-standard prepaid communication servicesUS20090042598 *Aug 8, 2007Feb 12, 2009Yahoo! Inc.Remote profile modification for device recovery assistUS20090291636 *Nov 26, 2009James Roger Morley-SmithSystem and method for locating a deviceUS20120084553 *Apr 5, 2012Searete Llc, A Limited Liability Corporation Of The State Of DelawareTransferable device with alterable usage functionalityUS20140199966 *Jan 11, 2013Jul 17, 2014Apple Inc.Bypassing security authentication scheme on a lost device to return the device to the ownerEP1792432A1 *Aug 22, 2005Jun 6, 2007Carolyn W. HafemanComputer recovery or return* Cited by examinerClassifications U.S. Classification455/410, 455/458, 455/565International ClassificationH04W88/02Cooperative ClassificationH04W88/02European ClassificationH04W88/02Legal EventsDateCodeEventDescriptionSep 26, 2002ASAssignmentJan 17, 2008FPAYFee paymentYear of fee payment: 4Nov 9, 2010ASAssignmentOwner name: MOTOROLA MOBILITY, INC., ILLINOISFree format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:MOTOROLA, INC.;REEL/FRAME:025337/0299Effective date: 20100731Jan 27, 2012FPAYFee paymentYear of fee payment: 8Oct 2, 2012ASAssignmentOwner name: MOTOROLA MOBILITY LLC, ILLINOISFree format text: CHANGE OF NAME;ASSIGNOR:MOTOROLA MOBILITY, INC.;REEL/FRAME:029216/0282Effective date: 20120622Nov 24, 2014ASAssignmentOwner name: GOOGLE TECHNOLOGY HOLDINGS LLC, CALIFORNIAFree format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:MOTOROLA MOBILITY LLC;REEL/FRAME:034432/0001Effective date: 20141028RotateOriginal ImageGoogle Home - Sitemap - USPTO Bulk Downloads - Privacy Policy - Terms of Service - About Google Patents - Send FeedbackData provided by IFI CLAIMS Patent Services