`US 20120133484Al
`
`c19) United States
`c12) Patent Application Publication
`GRIFFIN
`
`c10) Pub. No.: US 2012/0133484 Al
`May 31, 2012
`(43) Pub. Date:
`
`(54) MULTIPLE-INPUT DEVICE LOCK AND
`UNLOCK
`
`(75)
`
`Inventor:
`
`Jason Tyler GRIFFIN, Kitchener
`(CA)
`
`(73) Assignee:
`
`RESEARCH IN MOTION
`LIMITED, Waterloo (CA)
`
`(21) Appl. No.:
`
`12/955,350
`
`(22) Filed:
`
`Nov. 29, 2010
`
`Publication Classification
`
`(51)
`
`Int. Cl.
`G06F 7104
`
`(2006.01)
`
`(52) U.S. Cl. ....................................... 340/5.54; 340/5.51
`ABSTRACT
`(57)
`
`A device, such as a connnunication device or data processing
`device, is configured to transition between a locked and
`unlocked state in response to a detected action that is inter(cid:173)
`preted as a continuous or single action. In an embodiment a
`first input is detected at a first input mechanism of the device
`when the device is locked, then a second input is detected at
`the second input. If the inputs are determined to be continu(cid:173)
`ous, for example if the second input is detected within a
`predetermined period after completion of the first input, the
`device is unlocked. The input may also be combined or inter(cid:173)
`preted as a password or security code. Conversely, if a
`detected action is interpreted as a continuous or single action
`by an unlocked device, the device may enter the locked state
`in response to the detected action. Methods for implementing
`this transition between locked and unlocked states are also
`provided.
`
`Detect actuation
`of first input
`mechanism 12.QQ
`
`Store UI state
`12Q!i
`
`Start timer 1210
`
`Detect input at
`second input
`mechanism 1220
`
`no
`
`Detect complete
`input~
`
`Lock device
`1240
`
`Apple Ex. 1027
`Apple Inc. v. Firstface Co. Ltd.
`IPR2019-00613
`Page 00001
`
`
`
`Patent Application Publication May 31, 2012 Sheet 1 of 17
`
`US 2012/0133484 Al
`
`SIM/RUIM 126 .__--11...i
`
`SIM/RUIM
`Interface 128
`
`: Controller~ :
`
`.
`.
`.
`.
`·-----·
`1 Overl~y ill ,
`Display ill
`. _________ 11Q ---------.
`
`Operating
`System 134
`
`Programs 136
`
`Message
`Application
`138
`
`Device State
`Module 140
`
`PIM 142
`
`Connect
`Module 144
`
`IT Policy
`Module 146
`
`V+
`
`Battery
`Interface 132
`
`Battery 130
`
`Auxiliary 1/0112
`
`Data Port 114
`
`Keyboard 116
`
`Speaker ill
`
`Microphone 12.Q
`
`Rendering ~
`
`Short-Range
`Communications
`122
`
`Other Device
`Subsystems ill
`
`Main
`Processor
`102
`
`Accelerometer
`.111
`
`Flash
`Memory 108
`
`RAM 106
`
`Decoder 103
`
`Communication
`Subsystem 104
`
`.I
`
`I',..,,-.,"
`
`.__ ____ __. ./\l
`.. /-··.···~-.... --.. __ _
`:. Network
`:
`.
`(_
`200
`)
`~·
`\,. __ ,,"'., ................... •'
`
`WLAN Communication
`Subsystem 105
`
`~ 1 0 0
`
`FIG. 1
`
`IPR2019-00613 Page 00002
`
`
`
`Patent Application Publication May 31, 2012 Sheet 2 of 17
`
`US 2012/0133484 Al
`
`FIG. 2
`
`User input 212
`
`Sleep204
`
`(
`
`Inactivity
`timeout
`202
`
`timeout 314
`
`input interface actuated
`302
`
`lock 324
`
`FIG. 3
`
`100~
`
`F
`
`414
`
`454
`
`470
`
`410 454
`
`IPR2019-00613 Page 00003
`
`
`
`Patent Application Publication May 31, 2012 Sheet 3 of 17
`
`US 2012/0133484 Al
`
`FIG.SA
`
`500
`
`FIG.SB
`
`FIG.SC
`
`IPR2019-00613 Page 00004
`
`
`
`Patent Application Publication
`
`May 31, 2012 Sheet 4 of 17
`
`US 2012/0133484 Al
`
`(0
`~
`(0
`
`(X)
`
`.c
`0
`N
`(0
`
`..a
`l.O
`N
`(0
`
`.._,..
`
`~~-...._.._.._,,,,_~-,., ......... " ..... :· .·f
`
`I
`
`l •• . . • •
`
`time
`
`' ' ' '11\
`'Ill ---
`
`~,
`
`----
`
`,..!::
`
`9W!i
`
`-
`- ..':z
`
`<
`"° • 0 ,-..f
`
`~
`
`l.O
`0
`(0
`
`N
`~
`(0
`
`IPR2019-00613 Page 00005
`
`
`
`Patent Application Publication May 31, 2012 Sheet 5 of 17
`
`US 2012/0133484 Al
`
`"Ls
`
`~
`
`..;1..!;
`
`•
`t
`• I
`I
`•
`•
`•
`*
`•
`'
`~ ..::}
`
`time
`
`8W!l
`
`(cid:141)
`
`I
`
`I
`
`I •
`• • • •
`• • I • •
`• I • •
`,
`• • ,
`"
`'
`:,
`I l~
`i
`
`I
`
`~
`<O
`
`u
`\0
`•
`c:,
`11-f
`~
`
`IPR2019-00613 Page 00006
`
`
`
`Patent Application Publication May 31, 2012 Sheet 6 of 17
`
`US 2012/0133484 Al
`
`aw1i
`(cid:141)
`
`~
`
`SW!l
`
`,...
`......
`
`-.&
`
`., .
`' (cid:141)-' ~ ' I ~-., ' \. ' ' .. _
`
`,.,
`\~
`'
`I
`,
`'c
`-
`, ,.~
`
`~
`
`I
`
`I ' :
`
`I
`
`.
`
`"q"
`
`lO
`0
`(0
`
`~
`
`'° • 0
`
`~
`~
`
`C])
`a
`~
`
`IPR2019-00613 Page 00007
`
`
`
`Patent Application Publication May 31, 2012 Sheet 7 of 17
`
`US 2012/0133484 Al
`
`~
`100
`
`· I
`
`Z1Q.
`
`FIG. 7A
`
`FIG. 7B
`
`100
`
`)
`
`710
`
`714
`
`714
`
`100
`
`~
`
`715
`
`Z1Q
`
`705
`
`FIG. 7C
`
`714
`
`IPR2019-00613 Page 00008
`
`
`
`Patent Application Publication May 31, 2012 Sheet 8 of 17
`
`US 2012/0133484 Al
`
`~~--------
`
`100 (
`
`l1..Q
`
`FIG. 7D
`
`730d
`
`(cid:141)
`
`f 1
`
`time
`
`I
`
`.
`I !
`:
`'
`to
`
`715
`
`100
`
`)
`
`730e
`
`l1.Q
`
`FIG. 7E
`
`to
`
`time
`
`t1
`
`(cid:141)
`
`IPR2019-00613 Page 00009
`
`
`
`Patent Application Publication May 31, 2012 Sheet 9 of 17
`
`US 2012/0133484 Al
`
`FIG.8D
`
`IPR2019-00613 Page 00010
`
`
`
`,i;a..
`QO
`,i;a..
`~
`~
`
`> ....
`
`N --- 0 ....
`0 ....
`N
`rJJ
`c
`
`-....J
`
`....
`0 ....
`0
`....
`.....
`rJJ =(cid:173)
`0 ....
`~ .... ~
`~
`~
`
`('D
`('D
`
`N
`
`N
`
`.... 0 =
`.... 0 = ""O = O' -....
`~ -e -....
`('D = .....
`~ .....
`""O
`
`~ .....
`
`(')
`
`~ .....
`
`(')
`
`912
`
`920b
`
`916
`
`input
`
`input interface detected
`
`interface terminates
`
`contact with second input
`
`t3
`
`interface (not detected)
`contact with second input
`
`t1
`
`input
`
`. . ...
`
`detect third
`
`time
`
`905
`
`activation period 2
`
`.
`
`to
`t4
`gap period
`detection period gap period
`~ y
`'\
`_______ A.._ _____ ~----A.._ ____ __
`
`t
`,
`, ,
`········:~,
`,
`......................
`--•------··············· ············1'
`---~-i
`
`filQ
`
`I
`
`t4
`t3
`
`(I)
`~§'
`....
`t2
`
`t1
`to
`
`~
`
`FIG. 9B
`100
`
`I
`
`I
`
`-·-r y,,
`
`#
`
`925a
`
`100 J
`
`to•···,
`t1
`
`t2
`:;:;
`E
`(I)
`
`t3
`
`920a
`
`contact with second
`
`t2
`
`detect first
`
`activation period 1
`
`FIG. 9C
`
`X23
`
`905
`
`. .
`
`...
`...
`j JU' FIG. 9A
`i a
`I
`.
`'
`.
`'
`, .
`'
`.
`.
`, .
`'
`,:
`:
`........... __ ..,..,..,., ..................................................... ..!.
`,
`:
`i
`i
`,
`:
`,.
`
`IPR2019-00613 Page 00011
`
`
`
`....
`0 ....
`....
`....
`.....
`rJJ =(cid:173)
`0 ....
`~ .... ~
`~
`~
`
`('D
`('D
`
`N
`
`N
`
`.i;...
`QO
`.i;...
`~
`~
`
`> ....
`
`N --- 0 ....
`0 ....
`N
`rJJ
`c
`
`-....J
`
`second lock input 1066
`
`.... 0 =
`.... 0 = ""O = O" -....
`('D = ..... t "e -....
`
`~ .....
`
`(')
`
`~ .....
`
`(')
`
`~ .....
`""O
`
`FIG. 10
`
`input 1029
`first lock
`
`1062
`timeout
`
`training 1026
`
`enter
`
`complete 1032
`
`training
`
`1016
`
`security condition
`
`timeout 1022
`
`lock 1024
`
`I
`
`inpuf 1002
`first unlock
`
`cancellation action 1014
`
`/
`
`timeout 1012
`
`IPR2019-00613 Page 00012
`
`
`
`Patent Application Publication
`
`May 31, 2012 Sheet 12 of 17
`
`US 2012/0133484 Al
`
`Detect actuation
`of first input
`mechanism 1100
`
`Activate second
`input mechanism
`1105
`
`Start timer and
`count 1110
`
`Detect input at
`second input
`mechanism 1120
`
`FIG. 11
`
`Deactivate second
`input mechanism
`.11fill
`
`yes
`
`Detect complete
`input.11.aQ
`
`Wipe device
`1165
`
`no
`
`no
`
`Count=
`count +1
`1155
`
`no
`
`Unlock device
`.lliQ
`
`Reset count
`1145
`
`IPR2019-00613 Page 00013
`
`
`
`Patent Application Publication May 31, 2012 Sheet 13 of 17
`
`US 2012/0133484 Al
`
`Detect actuation
`of first input
`mechanism12.QQ
`
`Store U I state
`~
`
`Start timer 1210
`
`Detect input at
`second input
`mechanism 1220
`
`no
`
`yes
`
`Detect complete
`input 1230
`
`FIG. 12
`
`no
`
`no
`
`yes
`
`Lock device
`1240
`
`IPR2019-00613 Page 00014
`
`
`
`Patent Application Publication May 31, 2012 Sheet 14 of 17
`
`US 2012/0133484 Al
`
`100
`
`)
`
`FIG. 13A
`
`1310a
`
`1300a
`
`FIG. 13B
`
`100
`
`/
`
`~
`
`-, Emilio FW: Where is ...
`(81 Nena Where I left t. ..
`Julius I'm wondering ...
`Wed, August 18
`
`'{_,~
`
`I
`
`i
`
`1300b
`
`715
`
`"\ 100
`
`)
`
`Julius rm worlderlng,.,
`Wed, August 18
`
`1310c
`
`1300c
`
`705
`
`714
`
`FIG. 13C
`
`IPR2019-00613 Page 00015
`
`
`
`Patent Application Publication May 31, 2012 Sheet 15 of 17
`
`US 2012/0133484 Al
`
`Enter
`configuration
`mode 1400
`
`, .
`
`Detect device
`model 1405
`
`~ ,
`Store gap times
`for device
`parameters 1410
`
`FIG. 14
`
`Enter training
`mode 1500
`
`, ,
`
`Detect actuation
`of first input
`mechanism 1505
`
`1 ,
`
`Start timer 1510
`
`,
`Detect input at
`second input
`mechanism 1515
`
`' ,
`
`Store gap time
`~
`
`, I'
`
`Detect completion
`of second input
`~
`
`1 ,
`
`Store completion
`time 1530
`
`FIG. 15
`
`IPR2019-00613 Page 00016
`
`
`
`Patent Application Publication May 31, 2012 Sheet 16 of 17
`
`US 2012/0133484 Al
`
`100"\__
`
`FIG.16A
`
`FIG.16C
`
`1620
`
`FIG.16D
`
`IPR2019-00613 Page 00017
`
`
`
`Patent Application Publication May 31, 2012 Sheet 17 of 17
`
`US 2012/0133484 Al
`
`FIG.17A
`
`1770
`
`FIG.17C
`
`FIG.17D
`
`FIG.17B
`
`1770
`
`IPR2019-00613 Page 00018
`
`
`
`US 2012/0133484 Al
`
`May 31, 2012
`
`1
`
`MULTIPLE-INPUT DEVICE LOCK AND
`UNLOCK
`
`BACKGROUND
`
`[0001]
`1. Technical Field
`[0002] The present application relates to systems and meth(cid:173)
`ods for placing a mobile device in locked and unlocked states.
`[0003] 2. Description of the Related Art
`[0004] To enhance security and to conserve battery life,
`mobile devices such as smartphones, personal digital assis(cid:173)
`tants (PDAs), tablet computers, laptop computers, and the
`like, are typically configured to enter into a secure mode or a
`sleep mode after a period of inactivity or in response to an
`express command. In a secure mode, the device's functions
`and stored data are inaccessible until the user inputs the
`required code, such as a personal identification number
`(PIN), or sequence of key presses. In a sleep mode, one or
`more of the device's user interfaces (such as the display,
`trackball, touchscreen interface, and so forth) may be inacti(cid:173)
`vated and, in the case of a user input interface, incapable of
`receiving input until they are activated again. Activation of the
`inactivated user interface may require input at a designated
`one of the user input interfaces provided on the device, which
`is maintained in an awake state in which it is provided with
`sufficient power to detect user input.
`
`BRIEF DESCRIPTION OF THE DRAWINGS
`
`[0005]
`In drawings which illustrate by way of example only
`embodiments of the present application,
`[0006] FIG. 1 is a block diagram of an embodiment of an
`exemplary handheld mobile device.
`[0007] FIG. 2 is a state diagram illustrating two states of a
`user device.
`[0008] FIG. 3 is a further state diagram illustrating three
`states of a user device.
`[0009] FIG. 4 is a cross-sectional view of the handheld
`device of FIG. 1.
`[0010] FIGS. SA to SC are perspective views ofahandheld
`device being unlocked or locked.
`[0011] FIGS. 6A to 6F are schematic diagrams ofuserinput
`paths on a handheld touchscreen device.
`[0012] FIGS. 7 A to 7E are schematic diagrams ofuserinput
`paths on a further handheld device.
`[0013] FIGS. SA to SD are perspective views of a further
`embodiment of a handheld device being unlocked or locked.
`[0014] FIGS. 9A and 9B are further schematic diagrams of
`user input paths on a handheld device.
`[0015] FIG. 9C is a timeline illustrating gap, activation and
`detection periods for detected user input.
`[0016] FIG. 10 is a state diagram illustrating various states
`of a handheld device including unlocked and locked states.
`[0017] FIG. 11 is a flowchart illustrating a process for
`unlocking a handheld device.
`[0018] FIG. 12 is a flowchart illustrating a process for lock(cid:173)
`ing a handheld device.
`[0019] FIGS. 13A to 13C are illustrations of exemplary
`graphical user interfaces displayable on a handheld device
`during a locking process.
`[0020] FIG. 14 is a flowchart illustrating a process for con(cid:173)
`figuring a handheld device foruse with the method of FIG. 11
`or 12.
`
`[0021] FIG. 15 is a flowchart illustrating a process for train(cid:173)
`ing a handheld device for use with the method of FIG. 11 or
`12.
`[0022] FIGS. 16A to 16D are further perspective views of
`another embodiment of a handheld device being unlocked.
`[0023] FIGS. 17 A to 17D are further perspective views of
`the handheld device of FIGS. 16A to 16D being locked.
`
`DETAILED DESCRIPTION
`
`[0024]
`It is common for user data processing devices, such
`as smartphones, PDAs, tablets, laptops, personal computers,
`media players, and other devices used for personal commu(cid:173)
`nication, productivity or entertainment to preserve battery life
`or otherwise reduce power consumption by entering into a
`sleep mode or inactive mode, in which certain functions of the
`device or its peripherals are halted or suspended pending
`reactivation by the user. For example, in a personal computer
`including a separate processor unit, monitor, keyboard and
`pointing device, after a predetermined period of inactivity
`detected by the computer's processor, a signal may be sent to
`the monitor to enter into a screen saver mode, reducing its
`power consumption, or to enter a sleep mode, in which it
`receives little to no power. The processor itself may also halt
`certain processes or disk activity until a signal is received
`from the user to "wake up", or to reactivate the various pro(cid:173)
`cesses or the monitor. The signal may be received from one of
`the user input interface devices, such as the keyboard or the
`pointing device; for example, clicking a button on the point(cid:173)
`ing device, or depressing a key on the keyboard, may be
`sufficient to "wake up" the computer and reactivate the moni(cid:173)
`tor and other processes.
`[0025] Similarly, with reference to FIG. 2, in a handheld
`mobile device such as a smartphone or tablet computer, to
`conserve the battery the device may be configured to enter a
`sleep mode 210 in which the screen is blanked, either auto(cid:173)
`matically upon detection of a period of inactivity 202 or in
`response to an express command 204, from an initial active
`state 200. The screen may be reactivated upon detection of an
`input 212 received via a user input interface that may also be
`integrated into the device, such as the keypad or a conve(cid:173)
`nience key. In the case of a device equipped with a touch(cid:173)
`screen display, one of the primary user input interfaces may
`be the touchscreen interface. The entire touchscreen inter(cid:173)
`face, including the display component as well as the touch(cid:173)
`sensitive component, may be inactivated in sleep mode to
`reduce power consumption. Other user input interfaces on the
`device, such as optical joysticks, trackballs, scroll wheels,
`capacitive components such as touchpads and buttons, key(cid:173)
`boards, and other buttons utilizing other types of switch tech(cid:173)
`nology, may also be configured to be inactivated while in
`sleep mode, leaving only select ones of the input mechanisms
`sufficiently powered to detect a user input. When one of those
`active input mechanisms detects a user input, such as a key(cid:173)
`press, the processor can then be signaled to reactivate the
`other input interfaces on the device and return the device to an
`awake and operative state.
`[0026]
`In a simple embodiment, the sleep mode simply
`conserves power. Sleep mode may be combined with a secure
`mode and optionally content protection. To enhance the secu(cid:173)
`rity of the device, the device's functions or data, or both may
`be made accessible only if the correct security code, such as
`a PIN or password, has been entered by the user. Correct entry
`of the security code places the device in an insecure state in
`which the device's data and functions are accessible. Typi-
`
`IPR2019-00613 Page 00019
`
`
`
`US 2012/0133484 Al
`
`May 31, 2012
`
`2
`
`cally, the security code can be an alphanumeric key that may
`be input using the keyboard 116 or a virtual keyboard dis(cid:173)
`played on a touchscreen interface, or it may be a defined
`sequence of user manipulation of various input mechanisms
`(for example, a particular sequence of button presses). In the
`case of a computing device with a touchscreen or touchpad
`interface, the security code may be a gesture or symbol traced
`on the touchscreen or touchpad surface, and detected by sens(cid:173)
`ing the contact or pressure by the interface. In this secure
`mode, data may not be encrypted; effectively, the secure
`mode prevents access to data and functions because access to
`the device's user interface is restricted. This secure mode may
`be referred to as a "screen lock" mode, as typically the
`device's display is a primary user interface means for gaining
`access to functions and data, and while in secure mode, the
`device's display can display only a user interface for the user
`to enter credentials.
`[0027] The secure or "locked" mode can include a content
`protected state, if content protection is enabled on the device.
`The PIN or password can be used to encrypt user data stored
`on the device as well. For example, the security code or a
`value derived therefrom may be used to decrypt an encryption
`key stored at the computing device, which can then be stored
`in temporary memory and used to decrypt encrypted data and
`encrypt plaintext data during the current session a. Again,
`after a period of user input inactivity or in response to an
`instruction, the device may automatically return to the secure
`state, which any unencrypted data that is marked for content
`protection is encrypted, and the encryption key ( and the secu(cid:173)
`rity code, if it is still stored in memory) deleted from memory.
`In addition, the device may automatically enter sleep mode
`upon detecting the inactivity timeout ( or in response to the
`express instruction) and entering the secure mode, thus pro(cid:173)
`viding security and reduced power consumption. Thus, when
`the user subsequently wishes to use the computing device, the
`user must again input the security code to obtain access to
`functions or data on the device. Generically, either the sleep
`mode or the secure mode ( or "screen lock" mode) may be
`referred to as a "locked" state, where some function or data(cid:173)
`whether it is the functionality of one of the user input inter(cid:173)
`faces, the functionality of an application normally executable
`on the device, or access to the data stored on the device-is
`disabled or inactivated, whether because an input mechanism
`is in a low power state, the function or data is inaccessible
`without entry of the appropriate security code, data is
`encrypted, or a combination of two or more of these condi(cid:173)
`tions. The awake mode or insecure mode may then be referred
`to as an "unlocked" state, as the user input interfaces are
`generally all available, as well as the stored data and other
`functionality of the device. The "locked" and "unlocked"
`states described herein are intended to include both the sleep,
`screen lock and awake modes, and the secure and insecure
`modes, described above unless otherwise indicated.
`[0028] Particularly with a handheld device, the action used
`to invoke the unlock routine-a keypress, manipulation of the
`scroll wheel, contact or pressure on a touch-sensitive or pres(cid:173)
`sure-sensitive button-may be invoked accidentally, thus
`waking up the device and increasing power consumption
`when it was in fact not required by the user. Small user devices
`may be carried by the user in holsters or cases, which can
`reduce the likelihood of accidental manipulation of input
`mechanisms, but if the user carries the device in a pocket,
`purse, knapsack, briefcase, or other carrier in which the
`device may be jostled or come into contact with other objects
`
`or surfaces, the user input mechanism used to trigger the
`device to come out of sleep mode may be inadvertently actu(cid:173)
`ated. Accordingly, a more complex wake-up or unlock action
`may be required to completely activate the device. For
`example, the required input from the user may involve a
`sequence of keypresses, which, as will be appreciated by
`those skilled in the art, can be the PIN or password required to
`place the device in the insecure mode. Thus, with a device
`where the device keyboard continues to be capable of receiv(cid:173)
`ing input while the device is in sleep mode, the user may bring
`the device out of sleep mode by typing in the complete PIN on
`the keyboard. This process is somewhat cumbersome for the
`user, as it requires multiple distinct actions as the user locates
`and depresses each key representative of the PIN digits, and it
`prolongs the time required to bring the device out of sleep
`mode and into an unlocked mode compared to a simpler
`wake-up process involving only a single keypress or single
`manipulation of another input device.
`[0029] The wake-up input may also be made more complex
`by requiring the user to engage two different user input inter(cid:173)
`faces, such as a physical button and a touchscreen. As illus(cid:173)
`trated in FIG. 3, in the locked state one input interface such as
`a physical button may remain active, and detection of input
`302 at the button can be used to trigger the device to activate
`the touchscreen interface, placing the device in an input
`enabled state 310 in which it can receive a security code or
`other input such as a gesture. When the second input 312 is
`detected while the touchscreen is active, the device is brought
`out of sleep or locked mode and into an active or unlocked
`state 320. This process may add slightly to the time required
`to bring the device out of sleep mode, since two distinct inputs
`or actions are required on the user's part. Furthermore, it is
`possible in such scenarios that the wake-up inputs may still be
`invoked accidentally, since for example the physical button
`may be accidentally depressed in the user's pocket, and sub(cid:173)
`sequently, inadvertent contact on the touchscreen surface
`would unlock the device. Even where the second input
`(whether a PIN or a gesture) is not input at the device, the
`accidental activation of the first input interface can increase
`battery consumption. Again, if the physical button remains
`active in sleep mode and is accidentally depressed, the device
`display would then be activated. Once the device display is
`activated, it remains in the active state unless an express
`instruction to lock the device ( and thus deactivate the display)
`or a user activity timeout is detected, as discussed above. In
`this scenario, it is more likely that the timeout would have to
`occur before the display is deactivated, since the initial acti(cid:173)
`vation was accidental and the user was likely not aware of the
`activation; thus, the display must continue to consume power
`pending the timeout.
`[0030] Accordingly, the embodiments described herein
`provide a method, comprising: detecting a single, continuous
`unlock action applied to at least two input mechanisms on a
`locked electronic device; and unlocking the electronic device
`in response to said detecting.
`[0031] The embodiments herein also provide a method
`comprising: detecting a single, continuous lock action
`applied to at least two input mechanisms on a locked elec(cid:173)
`tronic device; and locking the electronic device in response to
`said detecting.
`[0032] The embodiments herein further provide a method,
`comprising detecting a first input at a first input mechanism in
`a locked electronic device; detecting a second input at a
`second input mechanism in the electronic device; and when
`
`IPR2019-00613 Page 00020
`
`
`
`US 2012/0133484 Al
`
`May 31, 2012
`
`3
`
`the second input is detected within a predetermined period of
`time after completion of the first input, unlocking the elec(cid:173)
`tronic device.
`In an aspect of these methods, sufficient power is
`[0033]
`provided to the first input mechanism such that the first input
`mechanism is capable of detecting the first input. In a further
`aspect, upon detection of the first input at the first input
`mechanism, the second input mechanism is activated such
`that the second input mechanism is capable of detecting the
`second input.
`In a further aspect, the detected first input and the
`[0034]
`detected second input may substantially match a predeter(cid:173)
`mined input action. In some embodiments, the second input
`mechanism is a touchscreen, and the electronic device is
`configured to further interpret the second input as a password
`for user authentication.
`[0035] Further, the within embodiments provide that the at
`least two input mechanisms are selected from the group con(cid:173)
`sisting of: a button, a keyboard, a touchpad, an optical joy(cid:173)
`stick, a scroll wheel, a touchscreen, and a slider mechanism.
`In one aspect, the at least two input mechanisms are selected
`from different members of said group. In a further aspect, the
`single, continuous unlock action is applied to two input
`mechanisms. In still a further aspect, the single, continuous
`unlock action is applied to three input mechanisms. The first
`input mechanism may be a button.
`In yet another aspect, detecting said single, continu(cid:173)
`[0036]
`ous unlock action comprises determining that inputs applied
`to said at least two input mechanisms constitute a single
`action based on a timing or a speed of the detected inputs.
`In still a further aspect, detecting said single, con(cid:173)
`[0037]
`tinuous unlock action comprises determining that a duration
`of time between a detected first input at a first one of said at
`least two input mechanisms and a detected second input at a
`second one of said at least two input mechanisms is within an
`expected range.
`In another aspect, detecting said single, continuous
`[0038]
`unlock action comprises determining that a path represented
`by inputs applied to said at least two input mechanisms was
`completed within either a predefined range of speed or a
`predefined range of time.
`[0039] The embodiments described herein also provide an
`electronic device, comprising at least two input mechanisms;
`and a processor in operative communication with the at least
`two input mechanisms, the processor being configured to:
`while the electronic device is in a locked state, detect, using
`said at least two input mechanisms, a single, continuous
`unlock action applied to said at least two input mechanisms;
`and unlock the electronic device in response to said detecting.
`[0040] The embodiments further provide an electronic
`device, comprising: at least two input mechanisms; and a
`processor in operative communication with said at least two
`input mechanisms, the processor being configured to: detect a
`single, continuous lock action applied to said at least two
`input mechanisms while the electronic device is in a locked
`state; and lock the electronic device in response to said detec(cid:173)
`tion.
`[0041] Further, the embodiments herein provide an elec(cid:173)
`tronic device, comprising: a first input mechanism; a second
`input mechanism; and a processor in operative communica(cid:173)
`tion with said at least two input mechanisms, the processor
`being configured to: detect a first input at the first input
`mechanism while the electronic device is in a locked state;
`detect a second input at the second input mechanism; when
`
`the second input is detected within a predetermined period of
`time after completion of the first input, unlock the electronic
`device.
`In an aspect of these electronic devices, sufficient
`[0042]
`power is provided to the first input mechanism such that the
`first input mechanism is capable of detecting the first input. In
`a further aspect, upon detection of the first input at the first
`input mechanism, the second input mechanism is activated
`such that the second input mechanism is capable of detecting
`the second input.
`In a further aspect, the detected first input and the
`[0043]
`detected second input may substantially match a predeter(cid:173)
`mined input action. In some embodiments, the second input
`mechanism is a touchscreen, and the electronic device is
`configured to further interpret the second input as a password
`for user authentication.
`[0044] Further, the within embodiments provide that the at
`least two input mechanisms are selected from the group con(cid:173)
`sisting of: a button, a keyboard, a touchpad, an optical joy(cid:173)
`stick, a scroll wheel, a touchscreen, and a slider mechanism.
`In one aspect, the at least two input mechanisms are selected
`from different members of said group. In a further aspect, the
`single, continuous unlock action is applied to two input
`mechanisms. In still a further aspect, the single, continuous
`unlock action is applied to three input mechanisms. The first
`input mechanism may be a button.
`In yet another aspect, detection of said single, con(cid:173)
`[0045]
`tinuous unlock action comprises determining that inputs
`applied to said at least two input mechanisms constitute a
`single action based on a timing or a speed of the detected
`inputs.
`In still a further aspect, detection of said single,
`[0046]
`continuous unlock action comprises determining that a dura(cid:173)
`tion of time between a detected first input at a first one of said
`at least two input mechanisms and a detected second input at
`a second one of said at least two input mechanisms is within
`an expected range.
`In another aspect, detection of said single, continu(cid:173)
`[0047]
`ous unlock action comprises determining that a path repre(cid:173)
`sented by inputs applied to said at least two input mechanisms
`was completed within either a predefined range of speed or a
`predefined range of time.
`[0048] The embodiments described herein further provide
`an electronic device adapted to have locked and unlocked
`states, the electronic device comprising at least two input
`mechanisms; and means adapted to, while the electronic
`device is in one of said locked and unlocked states, detect a
`single, continuous action applied to said at least two input
`mechanisms; and means adapted to transition the electronic
`device to the other of said locked and unlocked states in
`response to said detecting.
`In a further aspect, the means adapted to detect are
`[0049]
`adapted to determine that inputs applied to said at least two
`input mechanisms constitute a single action based on a timing
`or a speed of the detected inputs. In another aspect, said
`means adapted to detect are further adapted to determine that
`a duration of time between a detected first input at a first one
`of said at least two input mechanisms and a detected second
`input at a second one of said at least two input mechanisms is
`within an expected range. In still a further aspect, said means
`adapted to detect are further adapted to determine that a path
`represented by inputs applied to said at least two input mecha(cid:173)
`nisms was completed within either a predefined range of
`speed or a predefined range of time.
`
`IPR2019-00613 Page 00021
`
`
`
`US 2012/0133484 Al
`
`May 31, 2012
`
`4
`
`[0050]
`In another aspect of the within embodiments, the
`electronic device is initially in said locked state, and further
`wherein a first one of the at least two input mechanisms is
`sufficiently powered to detect a first input, and upon detection
`of the first input, the second input mechanism is activated
`such that the second input mechanism is capable of detecting
`the second input.
`[0051]
`In still another aspect, the at least two input mecha(cid:173)
`nisms are selected from the group consisting of: a button, a
`keyboard, a touchpad, an optical joystick, a scroll wheel, a
`touchscreen, and a slider mechanism. The at least two input
`mechanisms may be selected from different members of said
`group.
`[0052] The within embodiments further provide a method
`of transitioning an electronic device between a locked and an
`unlocked state, comprising: detecting a single, continuous
`action applied to at least two input mechanisms on the elec(cid:173)
`tronic device when the electronic device is in one of said
`locked and unlocked states; and transitioning the electronic
`device to the other of said locked and unlocked states in
`response to said detecting.
`[0053] An aspect of this method provides that detecting
`said single, continuous action comprises determining that
`inputs applied to said at least two input mechanisms consti(cid:173)
`tute a single action based on a timing or a speed of the detected
`inputs. Further, another aspect provides that said detecting
`further comprises determining that a duration of time
`between a detected first input at a first one of said at least two
`input mechanisms and a detected second input at a second one
`of said at least two input mechanisms is within an expected
`range. In still another aspect, said detecting further comprises
`determining that a path represented by inputs applied to said
`at least two input mechanisms was completed within either a
`pre