throbber
US007657849B2
`
`a2z United States Patent (10) Patent No.: US 7,657,849 B2
`Chaudhri et al. 45) Date of Patent: Feb. 2, 2010
`(54) UNLOCKING A DEVICE BY PERFORMING 5,907,327 A 5/1999 Oguraetal. .....cco.c..... 345/339
`GESTURES ON AN UNLOCK IMAGE 6,151,208 A 11/2000 Bartlett .......... ... 361/683
`6,160,555 A 12/2000 Kangetal. ... ... 345/358
`(75) Inventors: Imran Chaudhri, San Francisco, CA 2’535’2(7)2 g} éggg} El'le(liget;j """ ;(l)gfigg
`R . . ,249, iraly et al. ................
`823 FBas d(;“i;ll‘lg’ Szn Franmssco’ CA 6,323,846 Bl 11/2001 Westerman etal. ......... 345/173
`Franéiscrg CX (Ugl)l Mn:;lcr:ls’VaiHOs 6347290 Bl 2/2002 Bartlett ......cooocoovvenn.n.. 702/150
`San Francisco, CA (US); Stephen O. (Continued)
`Lemay, San Francisco, CA (US); Scott
`Forstall, Mountain View, CA (US); FOREIGN PATENT DOCUMENTS
`Greg Christie, San Jose, CA (US) EP 1284450 A2 2/2003
`(73) Assignee: Apple Inc., Cupertino, CA (US) (Continued)
`(*) Notice: Subject to any disclaimer, the term of this OTHER PUBLICATIONS
`patent is extended or adjusted under 35 GridLock 1.32, Oct. 8, 2003, pp. 1-2, http:/gridlock.en.softonic.
`U.S.C. 154(b) by 394 days. com/palm.*
`1) Appl. No.: 11/322,549 (Continued)
`rimary Examiner—Dennis-Doon Chow
`] Primary Exami Dennis-Doon Ch
`(22) Filed: Dec. 23, 2005 Assistant Examiner—Andres E Gutierrez
`. L (74) Attorney, Agent, or Firm—Morgan, Lewis & Bockius
`(65) Prior Publication Data LLP
`US 2007/0150842 A1l Jun. 28, 2007
`(57) ABSTRACT
`(51) Imt.ClL . . L .
`GO6F 3/033 (2006.01) A device with a touch-sensitive display may be unlocked via
`estures performed on the touch-sensitive display. The device
`(52) USCl oo 715/863; 345/173; 345/179 B performed on the touch-sensitive display. The devi
`5%) Field of Classification S h ’ ’713/154 is unlocked if contact with the display corresponds to a pre-
`(58) Fieldo 7 la3s/51156call$;)2n~ 7ela;/§ 5 3 863345 173 17 9’ defined gesture for unlocking the device. The device displays
`’ ’ ’ ’ 3 4’5 5 6’ one or more unlock images with respect to which the pre-
`See application file for complete search histo defined gesture is to be performed in order to unlock the
`PP P 1y device. The performance of the predefined gesture with
`(56) References Cited respect to the unlock image may include moving the unlock
`image to a predefined location and/or moving the unlock
`U.S. PATENT DOCUMENTS image along a predefined path. The device may also display
`5465084 A 11/1995 Cottrell ...vveeeen.... 340/82531 Visual cues of the predefined gesture on the touch screen to
`5559961 A 9/1996 Blonder ................. 395/188.01 remind a user of the gesture.
`5,677,710 A 10/1997 Thompson-Rohrlich .... 345/173
`5,821,933 A * 10/1998 Kelleretal. ................ 715/741 23 Claims, 15 Drawing Sheets
`1) P D)
`100 \1006 \100 4
`2 ) )
`Device \1 012 \“ 010
`1000 100!
`\ LJ
`.
`.
`Touch Screen 1014
`
`Apple Inc. v. Smith Interface Techs., LLC
`IPR2024-01256 | Smith EX2009 | Page 1 of 31
`
`
`
`
`
`
`
`
`US 7,657,849 B2
`
`Page 2
`U.S. PATENT DOCUMENTS WO WO 2004/021108 A2 3/2004
`6,421,453 Bl 7/2002 Kanevskyetal. ........... 382/115 OTHER PUBLICATIONS
`6,570,557 Bl 5/2003 Westerman et al. ......... 345/173 A Passive-Style Buttonless Mobile Terminal; Youichi Horry, Issyu
`6,573,883 Bl 6/2003 Bartlett ..c.oceoveveereennn.. 345/156¢ ~ Nakajima, Takeshi Hoshino, and Yukinobu Maruyama; IEEE Trans-
`6,633,310 Bl 10/2003 Andrew et al. ....ocove.. 345/728 Actions on Consumer Flectronics; vol. 49; No. 3; Aug. 2003; pp.
`530-535.
`6,677,932 Bl 12004 Westerman T 345/173 PCT International Search Report for International Application No.
`6,720,860 Bl 4/2004 Narayana.swam1 ......... 340/5.54 PCT/US2006/061370, mailed May 25, 2007.
`6,735,695 Bl 5/2004 Gopalakrishnan et al. ... 713/186 IBM Corp., “Access/Control Icons (Icon Keys),” IBM Technical
`7,124,433 B2 10/2006 Little ...... v 72602 Disclosure Bulletin, vol. 38, No. 4, Apr. 1995, pp. 407-409.
`7,151,843 B2 12/2006 Ruietal. .... . 382/103 “Touch Password Protection,” JGUI Professional, http://www.jgui.
`7,174,462 B2 2/2007 Peringetal. ... ... 713/182 net/touch/index.html, Dec. 8, 2003.
`7,263,670 B2 8/2007 Rekimoto ...... . 715/837 Office Action dated Oct. 31, 2007 for related U.S. Appl. No.
`2001/0011308 Al 82001 Clarketal. ... .. 71020 11322550, filed Dec. 23, 2005, pp. 1-26.
`2001/0012022 Al 82001 Smith coveneee...... . 3451768 ~ Office Action dated Apr. 21, 2008 for related U.S. Appl. No.
`2002/0015024 Al 2/2002 Westerman et al. ......... 345173 11322550, filed Dec. 23, 2005, pp. 1-22. o
`International Search Report for International Application No. PCT/
`2002/0196274 Al 12/2002 Comfortetal. ...... ... 345/741 US2006/061380, mailed Apr. 23, 2007.
`2003/0142138 Al 7/2003 Brownetal. ... ... 345/797 Notice of Allowance dated Sep. 19, 2008, for related U.S. Appl. No.
`2004/0030934 Al 2/2004 Mizoguchi et al. ... 713/202 11/322,550.
`2004/0034801 Al 2/2004 Jaeger ........ccccceeeeeeenn.. 713/202 Bardram, J., “The Trouble with Login: on usability and computer
`2004/0085351 Al 5/2004 Tokkonen ................... 345/741 security in Ubiquitous Computing,” Centre for Pervasive Healthcare,
`2004/0088568 Al 5/2004 Tokkonen ................... 713/200 Department of Computer Science, University of Aahus, Published
`2004/0230843 Al 11/2004 Jansen .........cco...... 713/202 online: Jul. 23, 2005. _ _
`2004/0250138 Al 12/2004 Schneider .................. 713202 Fitzpatrick, G. et al., “Method for Access Control via Gestural Veri-
`2004/0260955 Al 12/2004 Mantyla ..oooovoeeeene.. 713/202 ?;gg"g’pigx Technical Disclosure Bulletin, vol. 36, No. 09B, Sep.
`2004/0268267 Al 12/2004 Moravesik ....o.oe......... 715/821 IBM, “Touch Pad Authentication.” Sep. 21, 2004, 2 pages.
`2005/0050477 Al 3/2005 Robertson etal. ........... 715/853 Jansen, W., “Authenticating Users on Handheld Devices;” The
`2005/0060554 Al 3/2005 O’Donoghue ............... 713/183 National Institute of Standards and Technology, Gaithersburg, Mary-
`2005/0079896 Al 4/2005 Kokkoetal. ................ 455/566 land, 2003, 13 pages.
`2005/0212760 Al 9/2005 Marvitetal. ............... 345/156 Jermyn, L. et al., “The Design and Analysis of Graphical Passwords,”
`2005/0216862 Al 9/2005 Shinohara et al. ........... 715/825 Submission to the 8th Usenix Security Symposium, Aug. 1999, 15
`2005/0248542 Al 11/2005 Sawanobofi ................ 345/173 pages. . o )
`2005/0253817 AL* 11/2005 Rytivaaraetal. ......... 345/173 ?’It‘_’nr"sf’gyé’ §°Wa§dsk5t[rj"9ger Ut;er A;lflg‘z)f}g;a;‘m’f g}_Ld ftlsts_er'
`. ation, N €W YOI niversity, vol. - 0 1ssertation
`2005/0264833 Al 12/2005 Hiraoka etal. ............... 358/1.9 Abstract Interational, Order No. AAD99-30229, 115 pages.
`2006/0174339 AL 8/2006 TAO w.oovoiovrrsscrre 726/18 Najiar, L., “Graphical Passwords.” International Technology Disclo-
`2006/0267955 Al 11/2006 HIno .ovvvviiieieiennnes 345/173 sures VOl. 10’ No. 1’ Jan. 25, 1992’ lpage.
`2008/0034292 Al 2/2008 Brunneretal. ............. 715/700 Renaud, K. et al., “My Password is Here! An Investigation into
`2008/0072172 Al 3/2008 Shinoharaetal. ........... 715/772 Visuo-Spatial Authentication Mechanisms,” 2004, 25 pages, www.
`
`FOREIGN PATENT DOCUMENTS
`
`GB
`JP
`JP
`JP
`WO
`WO
`
`2313460 A
`
`60 171560
`
`2 249062
`6 214954
`
`WO 02/33882 Al
`WO 04/001560 Al
`
`11/1997
`9/1985
`10/1990
`8/1994
`4/2002
`12/2003
`
`sciencedirect.com.
`
`Wiedenbeck, S., et al. “PassPoints: Design and Longitudinal Evalu-
`ation of a Graphical Password System,” International Journal of
`Human-Computer Studies, vol. 63, Issues 1-2, Jul. 2005, pp. 102-
`127.
`
`Office Action dated Feb. 4, 2009, received in the German patent
`application which corresponds to U.S. Appl. No. 11/322,549.
`Office Action dated Mar. 25, 2009, received in the European patent
`application which corresponds to U.S. Appl. No. 11/322,549.
`
`* cited by examiner
`
`Page 2 of 31
`
`
`
`
`
`
`
`
`U.S. Patent Feb. 2, 2010 Sheet 1 of 15 US 7,657,849 B2
`
`Memory 102 \ Figure 1 Device 100
`Operating System 132 A)
`Communication Module | ~134
`Contact/Motion Module | ~138
`Graphics Module r/'140
`Optical Intensity Module |-/~ 142 130
`User Interface State Module |_144 Power |—’
`System
`Lock Module | ~150
`Unlock Module | ~152
`Application(s) | 146
`A
`110~/ 108 110 T
`! { RF Circuitry
`104\ Memory <—A—> 12
`] Controller 110
`
`1 1L Peripherals <——kL> Exter1n4a81 Port Speaker
`110 Interface 116
`106 110 -
`CPU Audio —m/
`M A» Circuitry
`114 —[)\
`
`Microphone
`110 118
`
`=
`
`I/0O Subsystem 120
`
`Touch-Screen Other Input
`Controller 122 Controller(s) 124
`) )
`110 110
`
`Other input /
`Control Devices
`128
`
`Touch Screen
`126
`
`Page 3 of 31
`
`
`
`
`
`
`
`
`U.S. Patent Feb. 2, 2010
`
`c
`[7]
`[
`=
`
`Sheet 2
`
`200 —\‘
`
`202
`
`of 15 US 7,657,849 B2
`
`Device
`
`Device set to user
`interface lock state by
`
`\ any predefined
`
`204
`
`manner, prevent
`device from
`performing predefined
`set of actions
`
`'
`
`\ Display visual cue(s)
`
`206 l
`N
`
`Contact the touch
`sensitive display
`
`208
`
`Figure 2
`
`Yes
`
`212
`
`214
`
`v[
`
`of unlock action (e.g.,
`gesture)
`
`Detect contact with
`touch sensitive
`display
`
`Does contact
`correspond to
`unlock gesture?
`
`Maintain device in
`user interface lock
`state
`
`Transition device to
`
`| user interface unlock
`
`state
`
`Page 4 of 31
`
`
`
`
`
`
`
`
`U.S. Patent Feb. 2, 2010 Sheet 3 of 15 US 7,657,849 B2
`
`c
`n
`[
`=
`
`300 \‘ Device
`
`Device set to user
`interface lock state by
`any predefined
`\. manner, prevent —
`device from
`performing predefined
`set of actions
`
`304 l
`
`\\ Display unlock image
`and visual cue(s) of
`unlock action using the
`image (e.g., gesture,
`moving image to
`location, moving
`image along path)
`
`302
`
`306
`N
`
`Contact the touch
`sensitive display
`
`308
`
`touch sensitive display
`
`Does contact
`correspond to unlock
`gesture using the
`image?
`
`312
`
`k Maintain device in
`user interface lock
`state
`
`Figure 3
`
`314
`
`Transition device to
`——— user interface unlock
`state
`
`|
`|
`|
`|
`|
`|
`|
`|
`|
`|
`! Detect contact with
`|
`|
`|
`|
`|
`|
`|
`|
`|
`|
`|
`|
`
`Page 5 of 31
`
`
`
`
`
`
`
`
`U.S. Patent Feb. 2, 2010 Sheet 4 of 15 US 7,657,849 B2
`
`Device
`400
`\ Touch Screen 408
`Figure 4A
`Menu
`Button 410
`Touch Screen 408
`Device
`400
`> ) ]
`K Figure 4B
`406 404
`Menu
`Button 410
`
`Page 6 of 31
`
`
`
`
`
`
`
`
`U.S. Patent
`
`Device
`400
`
`Device
`400
`
`Feb. 2, 2010 Sheet 5 of 15
`
`Touch Screen 408
`
`402
`
`Menu
`Button 410
`
`Touch Screen 408
`
`402
`
`404 \ /&
`
`( )
`
`é/
`
`Movement
`
`502 3 504
`
`Menu
`Button 410
`
`US 7,657,849 B2
`
`Figure SA
`
`Figure SB
`
`Page 7 of 31
`
`
`
`
`
`
`
`
`U.S. Patent
`
`Device
`400
`
`>
`
`Device
`400
`
`>
`
`506
`
`Feb. 2, 2010 Sheet 6 of 15
`
`Touch Screen 408
`
`404
`\
`
`502
`
`C
`
`Movement
`
`504 ;
`
`Menu
`Button 410
`
`Touch Screen 408
`
`App App App App
`1 2 3 4
`App App App App
`5 6 7 8
`App App App App
`9 10 11 12
`
`Menu
`Button 410
`
`US 7,657,849 B2
`
`Figure 5C
`
`Figure SD
`
`Page 8 of 31
`
`
`
`
`
`
`
`
`U.S. Patent
`
`602
`
`604
`
`600 —\‘
`
`While an electronic device is in a first user-
`interface state, detect progress towards
`satisfaction of a user input condition needed to
`transition to a second user-interface state
`
`While the device is in the first user-interface
`
`\_ state, indicate progress towards satisfaction of
`
`606
`
`the condition by transitioning an optical intensity
`of one or more user interface objects associated
`with the second user-interface state
`
`Transition the device to the second user-
`interface state if the condition is satisfied
`
`Figure 6
`
`Feb. 2, 2010 Sheet 7 of 15 US 7,657,849 B2
`
`Page 9 of 31
`
`
`
`
`
`
`
`
`U.S. Patent Feb. 2, 2010 Sheet 8 of 15 US 7,657,849 B2
`
`Touch screen 714
`
`Incoming call from:
`John Doe
`mobile
`Device j
`700 706 .
`N Figure 7A
`)
`Touch screen 714 706\
`Incoming call from:
`Device John Doe Figure 7B
`700 mobile
`
`Movement
`712
`
`Page 10 of 31
`
`
`
`
`
`
`
`
`U.S. Patent Feb. 2, 2010 Sheet 9 of 15 US 7,657,849 B2
`
`Touch screen 714 706
`
`N
`
`Incoming call from:
`Device John poe Figure 7C
`700 mobile
`- (Declind) (TL\ZEeBD} 708
`Movement
`) 712
`710 =
`
`C
`704J 702
`
`Touch screen 714 706
`
`Incoming call from:
`
`Device John Qoe Figure D
`700 mobile
`
`he G | 708
`
`Page 11 of 31
`
`
`
`
`
`
`
`
`U.S. Patent Feb. 2, 2010 Sheet 10 of 15 US 7,657,849 B2
`
`Figure 8A
`
`Optical Intensity
`
`0% Completion 100%
`
`Figure 8B
`
`Optical Intensity
`
`0% Completion 160%
`
`Figure 8C
`
`Optical Intensity
`
`Completion 100%
`
`Page 12 of 31
`
`
`
`
`
`
`
`
`U.S. Patent Feb. 2, 2010 Sheet 11 of 15 US 7,657,849 B2
`
`c
`»n
`(D
`P
`
`900 \‘ Device
`
`Device set to user
`902 interface lock state by
`\ any predefined manner,
`prevent device from
`performing predefined
`set of actions
`
`904 L
`
`\ Display 2 (or more)
`unlock images and
`visual cue(s) of manner
`of transitioning to active
`state using the images
`
`906
`|
`
`Contact the touch
`
`sensitive display
`
`908
`
`Detect contact with
`touch sensitive display
`
`Does contact
`correspond to unlock
`gesture using an
`image?
`
`Figure 9
`912
`
`Maintain device in user
`interface lock state
`
`914
`
`\ Transition device to
`active state
`corresponding to the
`——» image used (e.g., first
`image -> first active
`state, second image ->
`second active state, ...)
`
`Page 13 of 31
`
`
`
`
`
`
`
`
`U.S. Patent Feb. 2, 2010 Sheet 12 of 15 US 7,657,849 B2
`
`1) )
`\1006 K
`100 1004
`2 ) > )
`Device \1012 \1 010
`1000 100
`
`— .
`
`Touch Screen 1014
`
`Figure 10
`
`Page 14 of 31
`
`
`
`
`
`
`
`
`U.S. Patent
`
`Feb. 2, 2010 Sheet 13 of 15
`
`Device
`1000
`
`Touch Screen 1014
`
`1) )
`
`100 1004
`
`=
`, 008 k1010
`
`mOZ
`
`Device
`1000
`
`N
`
`Touch Screen 1014
`
`1) D)
`1008
`100 1004
`C (2) )
`1010
`Movement
`
`110 :/:>‘1104
`
`US 7,657,849 B2
`
`Figure 11A
`
`Figure 11B
`
`Page 15 of 31
`
`
`
`
`
`
`
`
`U.S. Patent
`
`Feb. 2, 2010 Sheet 14 of 15
`
`Device
`1000
`
`Touch Screen 1014
`
`9) : )
`100 1004 100
`C
`
`(2
`Movement 1102
`
`1104
`
`Device
`1000
`
`>
`
`Touch Screen 1014
`
`New text message!
`Read message?
`
`1106)
`
`US 7,657,849 B2
`
`Figure 11C
`
`Figure 11D
`
`Page 16 of 31
`
`
`
`
`
`
`
`
`U.S. Patent
`
`Feb. 2, 2010 Sheet 15 of 15
`
`Device
`1000
`
`N
`
`Touch Screen 1014 1002
`
`C ( 1
`1004j
`, 1102
`2 ) )
`100 1010’/
`Movement
`
`1104 ;
`
`Device
`1000
`
`Music Player
`
`Song A
`Artist X
`
`2:05/4:21
`
`L®®@®@@®J
`
`1108
`Touch Screen 1014
`
`US 7,657,849 B2
`
`Figure 11E
`
`Figure 11F
`
`Page 17 of 31
`
`
`
`
`
`
`
`
`US 7,657,849 B2
`
`1
`
`UNLOCKING A DEVICE BY PERFORMING
`GESTURES ON AN UNLOCK IMAGE
`
`RELATED APPLICATIONS
`
`This application is related to U.S. patent application Ser.
`No. 11/322,550, titled “Indication of Progress Towards Sat-
`isfaction of a User Input Condition,” filed Dec. 23, 2005,
`which application is incorporated by reference herein in its
`entirety.
`
`TECHNICAL FIELD
`
`The disclosed embodiments relate generally to user inter-
`faces that employ touch-sensitive displays, and more particu-
`larly, to the unlocking of user interfaces on portable electronic
`devices.
`
`BACKGROUND
`
`Touch-sensitive displays (also known as “touch screens” or
`“touchscreens”) are well known in the art. Touch screens are
`used in many electronic devices to display graphics and text,
`and to provide a user interface through which a user may
`interact with the devices. A touch screen detects and responds
`to contact on the touch screen. A device may display one or
`more soft keys, menus, and other user-interface objects on the
`touch screen. A user may interact with the device by contact-
`ing the touch screen at locations corresponding to the user-
`interface objects with which she wishes to interact.
`
`Touch screens are becoming more popular for use as dis-
`plays and as user input devices on portable devices, such as
`mobile telephones and personal digital assistants (PDAs).
`One problem associated with using touch screens on portable
`devices is the unintentional activation or deactivation of func-
`tions due to unintentional contact with the touch screen. Thus,
`portable devices, touch screens on such devices, and/or appli-
`cations running on such devices may be locked upon satis-
`faction of predefined lock conditions, such as upon entering
`an active call, after a predetermined time of idleness has
`elapsed, or upon manual locking by a user.
`
`Devices with touch screens and/or applications running on
`such devices may be unlocked by any of several well-known
`unlocking procedures, such as pressing a predefined set of
`buttons (simultaneously or sequentially) or entering a code or
`password. These unlock procedures, however, have draw-
`backs. The button combinations may be hard to perform.
`Creating, memorizing, and recalling passwords, codes, and
`the like can be quite burdensome. These drawbacks may
`reduce the ease of use of the unlocking process and, as a
`consequence, the ease of use of the device in general.
`
`Accordingly, there is a need for more efficient, user-
`friendly procedures for unlocking such devices, touch
`screens, and/or applications. More generally, there is a need
`for more efficient, user-friendly procedures for transitioning
`such devices, touch screens, and/or applications between user
`interface states (e.g., from a user interface state for a first
`application to a user interface state for a second application,
`between user interface states in the same application, or
`between locked and unlocked states). In addition, there is a
`need for sensory feedback to the user regarding progress
`towards satisfaction of a user input condition that is required
`for the transition to occur.
`
`SUMMARY
`
`In some embodiments, a method of controlling an elec-
`tronic device with a touch-sensitive display includes: detect-
`
`20
`
`25
`
`30
`
`35
`
`40
`
`45
`
`50
`
`55
`
`60
`
`65
`
`2
`
`ing contact with the touch-sensitive display while the device
`is in a user-interface lock state; moving an image correspond-
`ing to a user-interface unlock state of the device in accordance
`with the contact; transitioning the device to the user-interface
`unlock state if the detected contact corresponds to a pre-
`defined gesture; and maintaining the device in the user-inter-
`face lock state if the detected contact does not correspond to
`the predefined gesture.
`
`In some embodiments, a method of controlling a device
`with a touch-sensitive display includes: displaying an image
`on the touch-sensitive display while the device is in a user-
`interface lock state; detecting contact with the touch-sensitive
`display; transitioning the device to a user-interface unlock
`state if the detected contact corresponds to moving the image
`to a predefined location on the touch-sensitive display; and
`maintaining the device in the user-interface lock state if the
`detected contact does not correspond to moving the image to
`the predefined location.
`
`In some embodiments, a method of controlling a device
`with a touch-sensitive display includes: displaying an image
`on the touch-sensitive display while the device is in a user-
`interface lock state; detecting contact with the touch-sensitive
`display; and transitioning the device to a user-interface
`unlock state if the detected contact corresponds to moving the
`image on the touch-sensitive display according to a pre-
`defined path on the touch-sensitive display; and maintaining
`the device in the user-interface lock state if the detected
`contact does not correspond to moving the image according to
`the predefined path.
`
`In some embodiments, a method of controlling a device
`with a touch-sensitive display includes: displaying first and
`second images on the touch-sensitive display while the device
`is in a user-interface lock state; detecting contact with the
`touch-sensitive display; transitioning the device to a first
`active state corresponding to the first image if the detected
`contact corresponds to a predefined gesture with respect to
`the first image; and transitioning the device to a second active
`state distinct from the first active state if the detected contact
`corresponds to a predefined gesture with respect to the second
`image.
`
`The aforementioned methods may be performed by a por-
`table electronic device having a touch-sensitive display with
`a graphical user interface (GUI), one or more processors,
`memory and one or more modules, programs or sets of
`instructions stored in the memory for performing these meth-
`ods. In some embodiments, the portable electronic device
`provides a plurality of functions, including wireless commu-
`nication.
`
`Instructions for performing the aforementioned methods
`may be included in a computer program product configured
`for execution by one or more processors. In some embodi-
`ments, the executable computer program product includes a
`computer readable storage medium (e.g., one or more mag-
`netic disk storage devices, flash memory devices, or other
`non-volatile solid state memory devices) and an executable
`computer program mechanism embedded therein.
`
`BRIEF DESCRIPTION OF THE DRAWINGS
`
`For a better understanding of the aforementioned embodi-
`ments of the invention as well as additional embodiments
`thereof, reference should be made to the Description of
`Embodiments below, in conjunction with the following draw-
`ings in which like reference numerals refer to corresponding
`parts throughout the figures.
`
`FIG. 1 is a block diagram illustrating a portable electronic
`device, according to some embodiments of the invention.
`
`Page 18 of 31
`
`
`
`
`
`
`
`
`US 7,657,849 B2
`
`3
`
`FIG. 2 is a flow diagram illustrating a process for transi-
`tioning a device to a user-interface unlock state, according to
`some embodiments of the invention.
`
`FIG. 3 is a flow diagram illustrating a process for transi-
`tioning a device to a user-interface unlock state, according to
`some embodiments of the invention.
`
`FIGS. 4A-4B illustrate the GUI display of a device in a
`user-interface lock state, according to some embodiments of
`the invention.
`
`FIGS. 5A-5D illustrate the GUI display of a device at
`various points of the performance of an unlock action gesture,
`according to some embodiments of the invention.
`
`FIG. 6 is a flow diagram illustrating a process for indicating
`progress towards satisfaction of a user input condition
`according to some embodiments of the invention.
`
`FIGS. 7A-7D illustrate the GUI display of a device that is
`transitioning the optical intensity of user-interface objects,
`according to some embodiments of the invention.
`
`FIGS. 8A-8C are graphs illustrating optical intensity as a
`function of the completion of the user input condition,
`according to some embodiments of the invention.
`
`FIG. 9 is a flow diagram illustrating a process for transi-
`tioning a device to a user interface active state, according to
`some embodiments of the invention.
`
`FIG. 10 illustrates the GUI of a device in a user-interface
`lock state that displays a plurality of unlock images, accord-
`ing to some embodiments of the invention.
`
`FIGS. 11A-11F illustrate the GUI display of a device at
`various points in the performance of an unlock action gesture,
`according to some embodiments of the invention.
`
`DESCRIPTION OF EMBODIMENTS
`
`Reference will now be made in detail to embodiments,
`examples of which are illustrated in the accompanying draw-
`ings. In the following detailed description, numerous specific
`details are set forth in order to provide a thorough understand-
`ing of the present invention. However, it will be apparent to
`one of ordinary skill in the art that the present invention may
`be practiced without these specific details. In other instances,
`well-known methods, procedures, components, and circuits
`have not been described in detail so as not to unnecessarily
`obscure aspects of the embodiments.
`
`FIG. 1 illustrates a portable electronic device, according to
`some embodiments of the invention. The device 100 includes
`a memory 102, a memory controller 104, one or more pro-
`cessing units (CPU’s) 106, a peripherals interface 108, RF
`circuitry 112, audio circuitry 114, a speaker 116, a micro-
`phone 118, an input/output (I/O) subsystem 120, a touch
`screen 126, other input or control devices 128, and an external
`port 148. These components communicate over the one or
`more communication buses or signal lines 110. The device
`100 can be any portable electronic device, including but not
`limited to a handheld computer, a tablet computer, a mobile
`phone, a media player, a personal digital assistant (PDA), or
`the like, including a combination of two or more of these
`items. It should be appreciated that the device 100 is only one
`example of a portable electronic device 100, and that the
`device 100 may have more or fewer components than shown,
`or a different configuration of components. The various com-
`ponents shown in FIG. 1 may be implemented in hardware,
`software or a combination of both hardware and software,
`including one or more signal processing and/or application
`specific integrated circuits.
`
`The memory 102 may include high speed random access
`memory and may also include non-volatile memory, such as
`one or more magnetic disk storage devices, flash memory
`
`20
`
`25
`
`30
`
`35
`
`40
`
`45
`
`50
`
`55
`
`60
`
`65
`
`4
`
`devices, or other non-volatile solid state memory devices. In
`some embodiments, the memory 102 may further include
`storage remotely located from the one or more processors
`106, for instance network attached storage accessed via the
`RF circuitry 112 or external port 148 and a communications
`network (not shown) such as the Internet, intranet(s), Local
`Area Networks (LANs), Wide Local Area Networks
`(WLANSs), Storage Area Networks (SANs) and the like, or
`any suitable combination thereof. Access to the memory 102
`by other components of the device 100, such as the CPU 106
`and the peripherals interface 108, may be controlled by the
`memory controller 104.
`
`The peripherals interface 108 couples the input and output
`peripherals of the device to the CPU 106 and the memory 102.
`The one or more processors 106 run various software pro-
`grams and/or sets of instructions stored in the memory 102 to
`perform various functions for the device 100 and to process
`data.
`
`In some embodiments, the peripherals interface 108, the
`CPU 106, and the memory controller 104 may be imple-
`mented on a single chip, such as a chip 111. In some other
`embodiments, they may be implemented on separate chips.
`
`The RF (radio frequency) circuitry 112 receives and sends
`electromagnetic waves. The RF circuitry 112 converts elec-
`trical signals to/from electromagnetic waves and communi-
`cates with communications networks and other communica-
`tions devices via the electromagnetic waves. The RF circuitry
`112 may include well-known circuitry for performing these
`functions, including but not limited to an antenna system, an
`RF transceiver, one or more amplifiers, a tuner, one or more
`oscillators, a digital signal processor, a CODEC chipset, a
`subscriber identity module (SIM) card, memory, and so forth.
`The RF circuitry 112 may communicate with the networks,
`such as the Internet, also referred to as the World Wide Web
`(WWW), an Intranet and/or a wireless network, such as a
`cellular telephone network, a wireless local area network
`(LAN) and/or a metropolitan area network (MAN), and other
`devices by wireless communication. The wireless communi-
`cation may use any of a plurality of communications stan-
`dards, protocols and technologies, including but not limited
`to Global System for Mobile Communications (GSM),
`Enhanced Data GSM Environment (EDGE), wideband code
`division multiple access (W-CDMA), code division multiple
`access (CDMA), time division multiple access (TDMA),
`Bluetooth, Wireless Fidelity (Wi-Fi) (e.g., IEEE 802.11a,
`IEEE 802.11b, IEEE 802.11g and/or IEEE 802.11n), voice
`over Internet Protocol (VoIP), Wi-MAX, a protocol for email,
`instant messaging, and/or Short Message Service (SMS)), or
`any other suitable communication protocol, including com-
`munication protocols not yet developed as of the filing date of
`this document.
`
`The audio circuitry 114, the speaker 116, and the micro-
`phone 118 provide an audio interface between a user and the
`device 100. The audio circuitry 114 receives audio data from
`the peripherals interface 108, converts the audio data to an
`electrical signal, and transmits the electrical signal to the
`speaker 116. The speaker converts the electrical signal to
`human-audible sound waves. The audio circuitry 114 also
`receives electrical signals converted by the microphone 116
`from sound waves. The audio circuitry 114 converts the elec-
`trical signal to audio data and transmits the audio data to the
`peripherals interface 108 for processing. Audio data may be
`may be retrieved from and/or transmitted to the memory 102
`and/or the RF circuitry 112 by the peripherals interface 108.
`In some embodiments, the audio circuitry 114 also includes a
`headset jack (not shown). The headset jack provides an inter-
`face between the audio circuitry 114 and removable audio
`
`Page 19 of 31
`
`
`
`
`
`
`
`
`US 7,657,849 B2
`
`5
`
`input/output peripherals, such as output-only headphones or a
`headset with both output (headphone for one or both ears) and
`input (microphone).
`
`The /O subsystem 120 provides the interface between
`input/output peripherals on the device 100, such as the touch
`screen 126 and other input/control devices 128, and the
`peripherals interface 108. The 1/O subsystem 120 includes a
`touch-screen controller 122 and one or more input controllers
`124 for other input or control devices. The one or more input
`controllers 124 receive/send electrical signals from/to other
`input or control devices 128. The other input/control devices
`128 may include physical buttons (e.g., push buttons, rocker
`buttons, etc.), dials, slider switches, sticks, and so forth.
`
`The touch screen 126 provides both an output interface and
`an input interface between the device and a user. The touch-
`screen controller 122 receives/sends electrical signals from/
`to the touch screen 126. The touch screen 126 displays visual
`output to the user. The visual output may include text, graph-
`ics, video, and any combination thereof. Some or all of the
`visual output may correspond to user-interface objects, fur-
`ther details of which are described below.
`
`The touch screen 126 also accepts input from the user
`based on haptic and/or tactile contact. The touch screen 126
`forms a touch-sensitive surface that accepts user input. The
`touch screen 126 and the touch screen controller 122 (along
`with any associated modules and/or sets of instructions in the
`memory 102) detects contact (and any movement or break of
`the contact) on the touch screen 126 and converts the detected
`contact into interaction with user-interface objects, such as
`one or more soft keys, that are displayed on the touch screen.
`In an exemplary embodiment, a point of contact between the
`touch screen 126 and the user corresponds to one or more
`digits of the user. The touch screen 126 may use LCD (liquid
`crystal display) technology, or LPD (light emitting polymer
`display) technology, although other display technologies may
`be used in other embodiments. The touch screen 126 and
`touch screen controller 122 may detect contact and any move-
`ment or break thereof using any of a plurality of touch sensi-
`tivity technologies, including but not limited to capacitive,
`resistive, infrared, and surface acoustic wave technologies, as
`well as other proximity sensor arrays or other elements for
`determining one or more points of contact with the touch
`screen 126. The touch-sensitive display may be analogous to
`the multi-touch sensitive tablets described in the following
`U.S. Pat. Nos. 6,323,846 (Westerman et al.), 6,570,557 (Wes-
`terman et al.), and/or 6,677,932 (Westerman), and/or U.S.
`Patent Publication 2002/0015024 A1, each of which is hereby
`incorporated by reference. However, the touch screen 126
`displays visual output from the portable device, whereas
`touch sensitive tablets do not provide visual output. The touch
`screen 126 may have a resolution in excess of 100 dpi. In an
`exemplary embodiment, the touch screen 126 may have a
`resolution of approximately 168 dpi. The user may make
`contact with the touch screen 126 using any suitable object or
`appendage, such as a stylus, finger, and so forth.
`
`In some embodiments, in addition to the touch screen, the
`device 100 may include a touchpad (not shown) for activating
`or deactivating particular functions. In some embodiments,
`the touchpad is a touch-sensitive area of the device that,
`unlike the touch screen, does not display visual output. The
`touchpad may be a touch-sensitive surface that is separate
`from the touch screen 126 or an extension of the touch-
`sensitive surface formed by the touch screen 126.
`
`The device 100 also includes a power system 130 for pow-
`ering the various components. The power system 130 may
`include a power management system, one or more power
`sources (e.g., battery, alternating current (AC)), a recharging
`
`20
`
`25
`
`30
`
`35
`
`40
`
`45
`
`50
`
`55
`
`60
`
`65
`
`6
`
`system, a power failure detection circuit, a power converter or
`inverter, a power status indicator (e.g., a light-emitting diode
`(LED)) and any other components associated with the gen-
`eration, management and distribution of power in portable
`devices.
`
`In some embodiments, the software components include
`an operating system 132, a communication module (or set of
`instructions) 134, a contact/motion module (or set of instruc-
`tions) 138, a graphics module (or set of instructions) 140, a
`user interface state module (or set of instructions) 144, and
`one or more applications (or set of instructions) 146.
`
`The operating system 132 (e.g., Darwin, RTXC, LINUX,
`UNIX, OS X, WINDOWS, or an embedded operatin

This document is available on Docket Alarm but you must sign up to view it.


Or .

Accessing this document will incur an additional charge of $.

After purchase, you can access this document again without charge.

Accept $ Charge
throbber

Still Working On It

This document is taking longer than usual to download. This can happen if we need to contact the court directly to obtain the document and their servers are running slowly.

Give it another minute or two to complete, and then try the refresh button.

throbber

A few More Minutes ... Still Working

It can take up to 5 minutes for us to download a document if the court servers are running slowly.

Thank you for your continued patience.

This document could not be displayed.

We could not find this document within its docket. Please go back to the docket page and check the link. If that does not work, go back to the docket and refresh it to pull the newest information.

Your account does not support viewing this document.

You need a Paid Account to view this document. Click here to change your account type.

Your account does not support viewing this document.

Set your membership status to view this document.

With a Docket Alarm membership, you'll get a whole lot more, including:

  • Up-to-date information for this case.
  • Email alerts whenever there is an update.
  • Full text search for other cases.
  • Get email alerts whenever a new case matches your search.

Become a Member

One Moment Please

The filing “” is large (MB) and is being downloaded.

Please refresh this page in a few minutes to see if the filing has been downloaded. The filing will also be emailed to you when the download completes.

Your document is on its way!

If you do not receive the document in five minutes, contact support at support@docketalarm.com.

Sealed Document

We are unable to display this document, it may be under a court ordered seal.

If you have proper credentials to access the file, you may proceed directly to the court's system using your government issued username and password.


Access Government Site

We are redirecting you
to a mobile optimized page.





Document Unreadable or Corrupt

Refresh this Document
Go to the Docket

We are unable to display this document.

Refresh this Document
Go to the Docket