as) United States
`a2) Patent Application Publication co) Pub. No.: US 2007/0150842 Al
`
` Chaudhrietal. (43) Pub. Date: Jun. 28, 2007
`
`
`US 20070150842A1
`
`(54) UNLOCKING A DEVICE BY PERFORMING
`GESTURES ON AN UNLOCK IMAGE
`
`Publication Classification
`
`(76)
`
`Inventors: Imran Chaudhri, San Francisco, CA
`(US); Bas Ording, San Francisco, CA
`(US); Freddy Allen Anzures, San
`Francisco, CA (US); Marcel Van Os,
`San Francisco, CA (US); Stephen O.
`Lemay, San Francisco, CA (US); Scott
`Forstall, Mountain Vi
`CA (US);
`
`Greg‘Christie, San Tove, CA lus,;
`Correspondence Address:
`MORGAN LEWIS & BOCKIUS LLP/ APPLE
`COMPUTERINC.
`2 PALO ALTO SQUARE
`3000 EL CAMINO REAL
`PALO ALTO, CA 94306 (US)
`
`(21) Appl. No.:
`
`11/322,549
`
`(22)
`
`Filed:
`
`Dec. 23, 2005
`
`(51)
`
`Int. CL
`(2006.01)
`GO6F 3/00
`(52) US. Ce ec ceeesecssncesecsssscecesencesenessscecsenceseeneaee 715/863
`
`(57)
`
`ABSTRACT
`
`Adevice with a touch-sensitive display may be unlockedvia
`gestures performed on the touch-sensitive display. The
`device is unlocked if contact with the display correspondsto
`a predefined gesture for unlocking the device. The device
`displays one or more unlock images with respect to which
`the predefined gesture is to be performed in order to unlock
`the device. The performanceof the predefined gesture with
`respect to the unlock image may include moving the unlock
`image to a predefined location and/or moving the unlock
`image along a predefined path. The device mayalso display
`visual cues of the predefined gesture on the touch screen to
`remind a user of the gesture.
`
`Button410
`
`Device
`400
`\n
`
`Touch Screen 408
`
`Menu
`
`1
`
`APPLE 1005
`
`APPLE 1005
`
`1
`
`

`

`Patent Application Publication Jun. 28,2007 Sheet 1 of 15
`
`US 2007/0150842 A1
`
`Memory 102
`
`Figure 1
`
`Device 100
`
`Operating System
`Communication Module
`Contact/Motion Module
`Graphics Module
`Optical Intensity Module
`
`
`UserInterface State Module
`
`Lock Module
`
`Unlock Module
`
`Application(s)
`
`132
`134
`138
`140
`142
`144
`150
`152
`146
`
`1
`
`10
`104 i Memory
`
`Controller
`
`114
`
`106
`
`CPU
`
`108
`
`Peripherals
`Interface
`
`
`
`
`Speaker
`116
`
`130
`
`RF Circuitry
`112
`
`External Port
`148
`
`Audio =a
`Circuitry
`114
`
`@ M
`
`110
`
`110
`
`110
`
`icrophone
`118
`
`110
`
`1/0 Subsystem 120
`
`Controller(s) 124
`
`Touch-Screen
`Controller 122
`
`OtherInput
`
`440
`
`110
`
`Touch Screen
`
`126 Other Input /
`
`Control Devices
`128
`
`2
`
`

`

`Patent Application Publication Jun. 28,2007 Sheet 2 of 15
`
`US 2007/0150842 Al
`
`Cc an Oo4
`
`200 —™~
`
`Device
`
`
`
`
`
`
`Device set to user
`interface lock state by
`any predefined
`manner, prevent
`device from
`performing predefined
`set of actions
`
`
` Display visual cue(s)
`of unlock action (e.g.,
`
`206
`gesture)
`
`
`Contact the touch
`sensitive display
`
`Detect contact with
`touch sensitive
`display
`
`Yes
`
`
`Doescontact
`
`correspond to
`unlock gesture?
`
`Figure 2
`
`user interface lock
`state
`
`
`
`
` Maintain device in
`
`
`
`Transition device to
`user interface unlock
`
`state
`
`3
`
`

`

`Patent Application Publication Jun. 28,2007 Sheet 3 of 15
`
`US 2007/0150842 Al
`
`User
`
`300 ™™~
`
`302
`
`Device
`
`
`
`
`
`Device set to user
`interface lock state by
`any predefined
`manner, prevent
`device from
`performing predefined
`set of actions
`
`Display unlock image
`andvisual cue(s) of
`unlock action using the
`image (e.g., gesture,
`moving image to
`location, moving
`
`Contact the touch
`image along path)
`
`sensitive display
`
`
` Detect contact with ©
`touch sensitive display
`
`
`Does contact
`correspondto unlock
`gesture using the
`
`image?
`
`Figure 3
`
`
`
`
`
`
`
`Maintain device in
`user interface lock
`
`state
`
`
`Transition device to
`user interface unlock
`
`state
`
`4
`
`

`

`Patent Application Publication Jun. 28,2007 Sheet 4 of 15
`
`US 2007/0150842 Al
`
`400
`
`wy
`
`Touch Screen 408
`
`Figure 4A
`
` Device
`Figure 4B
`
`
`
`TouchScreen408
`
`Device
`400
`
`5
`
`

`

`Patent Application Publication Jun. 28,2007 Sheet 5 of 15
`
`US 2007/0150842 Al
`
`Figure 5A
`
`Device
`Screen408
`400
`
`400 Touch
`
`
`TouchScreen408
`Device
`
`Figure 5B
`
`6
`
`

`

`Patent Application Publication Jun. 28,2007 Sheet 6 of 15
`
`400
`YQ
`
`US 2007/0150842 Al
`
`Figure 5C
`
`Movement
`504
`
`Menu
`Button 410
`
`Touch Screen 408
`
`|||©@@O@
`OOO®
`
`A
`
`A
`
`A
`
`A
`
`Touch Screen 408 Device
`Button 410
`
`Device
`400
`
`Figure 5D
`
`App
`9
`
`App
`10
`
`App
`14
`
`App
`12
`
`506
`
`Menu
`
`7
`
`

`

`Patent Application Publication Jun. 28,2007 Sheet 7 of 15
`
`US 2007/0150842 Al
`
`600 —™~\
`
`While an electronic deviceis in a first user-
`interface state, detect progress towards
`satisfaction of a user input condition needed to
`transition to a second user-interface state
`
`interface state if the condition is satisfied
`
`While the deviceis in the first user-interface
`state, indicate progress towards satisfaction of
`the condition by transitioning an optical intensity
`of one or moreuserinterface objects associated
`with the second user-interface state
`
`Transition the device to the second user-
`
`Figure 6
`
`8
`
`

`

`Patent Application Publication Jun. 28,2007 Sheet 8 of 15
`
`US 2007/0150842 Al
`
`
`
`Touchscreen714
`
`mobile
`
`Device
`700
`
`\Y
`
`.
`
`Figure 7A
`
`Incoming call from: John Doe
`712
`
`Touch screen 714
`
`706
`
`Incoming call from:
`John Doe
`
`mobile
`
`Figure 7B
`
`Movement
`
`9
`
`

`

`Patent Application Publication Jun. 28,2007 Sheet 9 of 15
`
`US 2007/0150842 Al
`
`Touch screen 714
`
`706
`
`Incoming call from:
`John Doe
`
`Figure 7C
`
`Device
`700
`
`Device
`700
`
`mobile Movement
`mobile
`
`712
`
`Touch screen 714
`
`706
`
`Incoming call from:
`John Doe
`
`Figure 7D
`
`10
`
`

`

`Patent Application Publication Jun. 28,2007 Sheet 10 of 15
`
`US 2007/0150842 Al
`
`Figure 8A
`
`Figure 8B
`
`Figure 8C
`
`
`
`OpticalIntensity
`
`
`
`OpticalIntensity
`
`
`
`OpticalIntensity
`
`
`Completion
`100%
`
`0%
`
`Completion
`
`100%
`
`0
`
`0%
`
`Completion
`
`100%
`
`11
`
`

`

`Patent Application Publication Jun. 28,2007 Sheet 11 of 15
`
`US 2007/0150842 Al
`
`User
`
`900 —™~
`
`Device
`
`
`
`Device set to user
`
`interface lock state by
`any predefined manner,
`prevent device from
`
`
`performing predefined
`
`set of actions
`
`
`906
`
`Display 2 (or more)
`unlock images and
`visual cue(s) of manner
`
`of transitioning to active
`
`state using the images
`
`
`
`Contact the touch
`
`|
`908
`
`sensitive display
`
`
` Detect contact with
`touch sensitive display
`
`
`
`
`
`
`
`
`
`Does contact
`correspond to unlock
`gesture using an
`image?
`
`Figure 9
`
`Maintain device in user
`interface lock state
`
`
`Transition device to
`
`
`active state
`
`
`corresponding to the
`image used (e.g., first
`
`
`image -> first active
`
`
`state, second image ->
`second active state,...)
`
`
`
`12
`
`12
`
`

`

`US 2007/0150842 Al
`
`Patent Application Publication Jun. 28,2007 Sheet 12 of 15
`
`TouchScreen1014
`
`Device
`1000
`
`Figure 10
`
`13
`
`

`

`US 2007/0150842 Al
`
`°
`Figure 11A
`
`Figure 11B
`
`Patent Application Publication Jun. 28,2007 Sheet 13 of 15
`
`1000
`
`\
`
`e.
`Doz
`
`008
`
`Touch Screen 1014
`
`Device
`1000
`
`Touch Screen 1014 Device
`1104
`
`Movement
`
`410
`
`14
`
`14
`
`

`

`Patent Application Publication Jun. 28,2007 Sheet 14 of 15
`
`US 2007/0150842 Al
`
`Touch Screen 1014
`
`Device
`
`4000
`
`&Movement
`
`1102
`
`Figure 11C
`
`1104
`Figure 11D
`
`
`
`TouchScreen1014
`
`New text message!
`Read message?
`
`Device
`1000
`
`15
`
`

`

`Patent Application Publication Jun. 28,2007 Sheet 15 of 15
`
`US 2007/0150842 Al
`
`1000
`
`Movement
`1104
`
`Touch Screen 1014 Device
`Touch Screen 1014
`
`Device
`1000
`Ne
`
`Artist X
`2:05/4: 21
`
`©DOHOO®
`Lo
`
`1108
`
`.
`Figure 11E
`
`Figure 11F
`
`16
`
`

`

`US 2007/0150842 Al
`
`Jun. 28, 2007
`
`UNLOCKING A DEVICE BY PERFORMING
`GESTURES ON AN UNLOCK IMAGE
`
`RELATED APPLICATIONS
`
`[0001] This application is related to U.S. patent applica-
`tion Ser. No.
`, attorney docket number 063266-5010-
`US, titled “Indication of Progress Towards Satisfaction of a
`User Input Condition,”filed
`, 2005, which applica-
`tion is incorporated by reference herein in its entirety.
`
`TECHNICAL FIELD
`
`[0002] The disclosed embodimentsrelate generally to user
`interfaces that employ touch-sensitive displays, and more
`particularly, to the unlocking of user interfaces on portable
`electronic devices.
`
`BACKGROUND
`
`[0003] Touch-sensitive displays (also known as “touch
`screens”or “touchscreens’’) are well knownin 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 contacting the touch screen at
`locations corresponding to the user-interface objects with
`which she wishesto interact.
`
`[0004] Touch screens are becoming more popular for use
`as displays 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 deac-
`tivation of functions due to unintentional contact with the
`
`touch screen. Thus, portable devices, touch screens on such
`devices, and/or applications running on such devices may be
`locked uponsatisfaction of predefined lock conditions, such
`as upon entering an activecall, after a predetermined time of
`idleness has elapsed, or upon manual locking by a user.
`
`[0005] Devices with touch screens and/or applications
`running on such devices may be unlockedbyanyof several
`well-known unlocking procedures, such as pressing a pre-
`defined set of buttons (simultaneously or sequentially) or
`entering a code or password. These unlock procedures,
`however, have drawbacks. The button combinations may be
`hard to perform. Creating, memorizing, and recalling pass-
`words, 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.
`
`there is a need for more efficient,
`[0006] Accordingly,
`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 appli-
`cation, between user interface states in the same application,
`or between locked and unlockedstates). In addition, there is
`a need for sensory feedback to the user regarding progress
`towardssatisfaction of a user input condition thatis required
`for the transition to occur.
`
`SUMMARY
`
`In some embodiments, a method of controlling an
`[0007]
`electronic device with a touch-sensitive display includes:
`detecting contact with the touch-sensitive display while the
`device is in a user-interface lock state; moving an image
`corresponding 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 corre-
`sponds to a predefined gesture; and maintaining the device
`in the user-interface lock state if the detected contact does
`not correspond to the predefined gesture.
`
`In some embodiments, a method of controlling a
`[0008]
`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
`[0009]
`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 predefined 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
`[0010]
`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.
`
`[0011] The aforementioned methods may be performed by
`a portable electronic device having a touch-sensitive display
`with a graphical user interface (GUI), one or more proces-
`sors, memory and one or more modules, programsorsets of
`instructions stored in the memory for performing these
`methods.
`In some embodiments,
`the portable electronic
`device provides a plurality of functions, including wireless
`communication.
`
`Instructions for performing the aforementioned
`[0012]
`methods may be included in a computer program product
`configured for execution by one or more processors.
`
`BRIEF DESCRIPTION OF THE DRAWINGS
`
`[0013] For a better understanding of the aforementioned
`embodiments of the invention as well as additional embodi-
`ments thereof, reference should be madeto the Description
`of Embodiments below, in conjunction with the following
`
`17
`
`17
`
`

`

`US 2007/0150842 Al
`
`Jun. 28, 2007
`
`drawings in which like reference numerals refer to corre-
`sponding parts throughout the figures.
`
`[0014] FIG. 1 is a block diagram illustrating a portable
`electronic device, according to some embodiments of the
`invention.
`
`[0015] FIG. 2 is a flow diagram illustrating a process for
`transitioning a device to a user-interface unlock state,
`according to some embodiments of the invention.
`
`[0016] FIG. 3 is a flow diagram illustrating a process for
`transitioning a device to a user-interface unlock state,
`according to some embodiments of the invention.
`
`[0017] FIGS. 4A-4Billustrate the GUIdisplay of a device
`in a user-interface lock state, according to some embodi-
`ments of the invention.
`
`[0018] FIGS. 5A-5Dillustrate the GUI display of a device
`at various points of the performance of an unlock action
`gesture, according to some embodiments of the invention.
`
`[0019] 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.
`
`[0020] 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.
`
`[0021] FIGS. 8A-8C are graphsillustrating optical inten-
`sity as a function of the completion of the user input
`condition, according to some embodiments ofthe invention.
`
`[0022] FIG. 9 is a flow diagram illustrating a process for
`transitioning a deviceto a user interface active state, accord-
`ing to some embodiments of the invention.
`
`[0023] FIG. 10 illustrates the GUI of a device in a user-
`interface lock state that displays a plurality of unlock
`images, according to some embodiments of the invention.
`
`[0024] 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
`
`[0025] Reference will now be made in detail to embodi-
`ments, examples of whichare illustrated in the accompany-
`ing drawings. In the following detailed description, numer-
`ous specific details are set forth in order to provide a
`thorough understanding 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 embodi-
`ments.
`
`[0026] 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 processing units (CPU’s) 106, a periph-
`erals interface 108, RF circuitry 112, audio circuitry 114, a
`speaker 116, a microphone 118, an input/output (I/O) sub-
`system 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
`
`lines 110. The device 100 can be any portable
`signal
`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 components
`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.
`
`[0027] The memory 102 mayinclude high speed random
`access memory and mayalso include non-volatile memory,
`such as one or more magnetic disk storage devices, flash
`memory 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 (WLANs), 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.
`
`[0028] The peripherals interface 108 couples the input and
`output peripherals of the device to the CPU 106 andthe
`memory 102. The one or more processors 106 run various
`software programs and/or sets of instructions stored in the
`memory 102 to perform various functions for the device 100
`and to process data.
`
`the peripherals interface
`In some embodiments,
`[0029]
`108, the CPU 106, and the memory controller 104 may be
`implemented on a single chip, such as a chip 111. In some
`other embodiments, they may be implemented on separate
`chips.
`
`[0030] The RF (radio frequency) circuitry 112 receives
`and sends electromagnetic waves. The RF circuitry 112
`converts electrical signals to/from electromagnetic waves
`and communicates with communications networks and other
`communications 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 moreoscillators, a digital signal processor, a
`CODECchipset, a subscriber identity module (SIM)card,
`memory, and so forth. The RF circuitry 112 may commu-
`nicate 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 com-
`munication. The wireless communication may use any of a
`plurality of communications standards, protocols and tech-
`nologies, 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
`
`18
`
`18
`
`

`

`US 2007/0150842 Al
`
`Jun. 28, 2007
`
`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 communication proto-
`cols not yet developedas ofthefiling date of this document.
`
`[0031] The audio circuitry 114, the speaker 116, and the
`microphone 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 transmitsthe electrical signal
`to the speaker 116. The speaker convertsthe 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
`electrical signal to audio data and transmits the audio data to
`the peripherals interface 108 for processing. Audio data may
`be maybe 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 interface between the audio circuitry 114 and
`removable audio input/output peripherals, such as output-
`only headphonesor a headset with both output (headphone
`for one or both ears) and input (microphone).
`
`[0032] The I/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 I/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 mayinclude physical buttons (e.g., push
`buttons, rocker buttons, etc.), dials, slider switches, sticks,
`and so forth.
`
`[0033] 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 elec-
`trical signals from/to the touch screen 126. The touch screen
`126 displays visual output to the user. The visual output may
`include text, graphics, video, and any combination thereof.
`Someorall of the visual output may correspond to user-
`interface objects, further details of which are described
`below.
`
`[0034] The touch screen 126 also accepts input from the
`user based on haptic and/ortactile 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 instruc-
`tions in the memory 102) detects contact (and any move-
`ment 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 con-
`
`troller 122 may detect contact and any movementor break
`
`thereof using any of a plurality of touch sensitivity tech-
`nologies, including but not limited to capacitive, resistive,
`infrared, and surface acoustic wave technologies, as well as
`other proximity sensor arrays or other elements for deter-
`mining 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 (Westermanet al.), 6,570,557 (Wester-
`man et al.), and/or 6,677,932 (Westerman), and/or U.S.
`Patent Publication 2002/0015024A1, 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 havea 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 addition to the touch
`In some embodiments,
`[0035]
`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 maybe 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.
`
`[0036] The device 100 also includes a power system 130
`for powering 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 system, a powerfailure detection circuit, a power
`converter or inverter, a powerstatus indicator (e.g., a light-
`emitting diode (LED)) and any other components associated
`with the generation, managementand distribution of power
`in portable devices.
`
`In some embodiments, the software components
`[0037]
`include an operating system 132, a communication module
`(or set of instructions) 134, a contact/motion module (or set
`of instructions) 138, a graphics module (or set of instruc-
`tions) 140, a user interface state module (or set of instruc-
`tions) 144, and one or more applications (or set of instruc-
`tions) 146.
`
`[0038] The operating system 132 (e.g., Darwin, RTXC,
`LINUX, UNIX, OS X, WINDOWS, or an embeddedoper-
`ating system such as VxWorks) includes various software
`components and/or drivers for controlling and managing
`general system tasks (e.g., memory management, storage
`device control, power management, etc.) and facilitates
`communication between various hardware and software
`components.
`
`[0039] The communication module 134 facilitates com-
`munication with other devices over one or more external
`ports 148 andalso includes various software components for
`handling data received by the RF circuitry 112 and/or the
`external port 148. The external port 148 (e.g., Universal
`Serial Bus (USB), FIREWIRE,etc.) is adapted for coupling
`directly to other devices or indirectly over a network(e.g.,
`the Internet, wireless LAN,etc.).
`
`[0040] The contact/motion module 138 detects contact
`with the touch screen 126, in conjunction with the touch-
`screen controller 122. The contact/motion module 138
`
`19
`
`19
`
`

`

`US 2007/0150842 Al
`
`Jun. 28, 2007
`
`includes various software components for performing vari-
`ous operations related to detection of contact with the touch
`screen 122, such as determining if contact has occurred,
`determining if there is movementof the contact and tracking
`the movement across the touch screen, and determining if
`the contact has been broken(i.e., if the contact has ceased).
`Determining movementof the point of contact may include
`determining speed (magnitude), velocity (magnitude and
`direction), and/or an acceleration (including magnitude and/
`or direction) of the point of contact. In some embodiments,
`the contact/motion module 126 and the touch screen con-
`
`troller 122 also detects contact on the touchpad.
`
`[0041] The graphics module 140 includes various known
`software components for rendering and displaying graphics
`on the touch screen 126. Note that the term “graphics”
`includes any object that can be displayedto a user, including
`without limitation text, web pages,
`icons (such as user-
`interface objects including soft keys), digital images, videos,
`animations andthelike.
`
`In some embodiments, the graphics module 140
`[0042]
`includes an optical intensity module 142. The optical inten-
`sity module 142 controls the optical intensity of graphical
`objects, such as user-interface objects, displayed on the
`touch screen 126. Controlling the optical
`intensity may
`include increasing or decreasing the optical intensity of a
`graphical object. In some embodiments,
`the increase or
`decrease may follow predefined functions.
`
`[0043] The user interface state module 144 controls the
`userinterface state of the device 100. The user interface state
`module 144 may include a lock module 150 and an unlock
`module 152. The lock module detects satisfaction of any of
`one or more conditions to transition the device 100 to a
`user-interface lock state and to transition the device 100 to
`the lock state. The unlock module detects satisfaction of any
`of one or more conditions to transition the device to a
`user-interface unlock state and to transition the device 100
`to the unlock state. Further details regarding the user inter-
`face states are described below.
`
`[0044] The one or more applications 130 can include any
`applications installed on the device 100, including without
`limitation, a browser, address book, contact
`list, email,
`instant messaging, word processing, keyboard emulation,
`widgets,
`JAVA-enabled applications, encryption, digital
`rights management, voice recognition, voice replication,
`location determination capability (such as that provided by
`the global positioning system (GPS)), a music player (which
`plays back recorded music stored in one or morefiles, such
`as MP3 or AACfiles), etc.
`
`In some embodiments, the device 100 may include
`[0045]
`the functionality of an MP3 player, such as an iPod(trade-
`mark of Apple Computer, Inc.). The device 100 may, there-
`fore, include a 36-pin connector that is compatible with the
`iPod. In some embodiments, the device 100 may include one
`or more optional optical sensors (not shown), such as CMOS
`or CCD image sensors, for use in imaging applications.
`
`In some embodiments, the device 100 is a device
`[0046]
`where operation of a predefined set of functions on the
`device is performed exclusively through the touch screen
`126 and, if included on the device 100, the touchpad. By
`using the touch screen and touchpad as the primary input/
`control device for operation of the device 100, the number
`
`input/control devices (such as push buttons,
`of physical
`dials, and the like) on the device 100 maybe reduced. In one
`embodiment, the device 100 includes the touch screen 126,
`the touchpad, a push button for powering the device on/off
`and locking the device, a volume adjustment rocker button
`and a slider switch for toggling ringer profiles. The push
`button may be used to turn the power on/off on the device
`by depressing the button and holding the button in the
`depressed state for a predefined time interval, or may be
`used to lock the device by depressing the button and
`releasing the button before the predefined time interval has
`elapsed. In an alternative embodiment, the device 100 also
`may accept verbal input for activation or deactivation of
`some functions through the microphone 118.
`
`[0047] The predefined set of functions that are performed
`exclusively through the touch screen and the touchpad
`include navigation between user interfaces. In some embodi-
`ments, the touchpad, when touchedbythe user, navigates the
`device 100 to a main, home, or root menu from any user
`interface that may be displayed on the device 100. In such
`embodiments, the touchpad may bereferred to as a “menu
`button.” In some other embodiments, the menu button may
`be a physical push button or other physical input/control
`device instead of a touchpad.
`
`UserInterface States
`
`[0048] The device 100 may have a plurality of user
`interface states. A user interface state is a state in which the
`
`device 100 responds in a predefined mannerto user input. In
`some embodiments,
`the plurality of user interface states
`includes a user-interface lock state and a user-interface
`
`unlock state. In some embodiments, the plurality of user
`interface states includesstates for a plurality of applications.
`
`In the user-interface lock state (hereinafter the
`[0049]
`“lock state”), the device 100 is powered on and operational
`but ignores most, if notall, user input. Thatis, the device 100
`takes no action in response to user input and/or the device
`100 is prevented from performing a predefined set of opera-
`tions in response to the user input. The predefined set of
`operations may include navigation between user interfaces
`and activation or deactivation of a predefined set of func-
`tions. The lock stat