Apple Ex. 1027
`Apple Inc. v. Firstface Co., Ltd.
`IPR2019-00614
`Page 00001
`
`

`

`Patent Application Publication May 31, 2012 Sheet 1 of 17
`
`US 2012/0133484 A1
`
`V+
`
`S‘MIRU'M 12-6
`
`SiM/RUiM
`Interface 12::
`
`Battery
`Interface 132,
`
`Battery 139
`
`Main
`Processor
`102
`
`Rendering Short—Range
`
`—'————"'ll
`
`Auxiliary NO 112
`
`Date Port 114
`
`Keyboard 11g
`
`Speaker 11a
`
`Microphone 129
`
`Communications
`12;
`
`Other Device
`Subsystems 125
`
`
`
`Accelerometer
`111
`
`Fiash
`Memory 19—8—
`
`RAM m
`
`Decoder
`
`()3
`1....
`
`Communication
`Subsystem 194;
`au
`u
`‘3‘I:I.
`
`.
`n
`
`Operating
`System 135
`
`Programs 133‘;
`
`Message
`Application
`1.518.
`
`Device State
`Moduie 1510,
`
`PM &
`
`Connect
`Module 14.4
`
`V
`iT Policy
`Module 1&6,
`
`
`
`.
`
`..
`
`’...-
`
`.
`f
`
`WLAN Communication
`Subsystem 19.5
`
`.
`
`k,
`
`100
`
`IPR2019-00614 Page 00002
`
`IPR2019-00614 Page 00002
`
`

`

`Patent Application Publication May 31, 2012 Sheet 2 of 17
`
`US 2012/0133484 A1
`
`FIG. 2
`
`Steep 204
`
`
`User input 212
`
`
`
`Inactivity
`timeout
`202
`
`
`
`
` Active
`(unlocked)
`109
`
`Locked
`gm
`
`timeout 314
`
`input interface actuated
`302
`
`input
`Enabted
`
`timeout 322
`
`lock 324
`
`
`
`
`
`unlock input 312
`
`422 . _.‘ ............. M .1
`
`f §§K\\\\\a\
`.R?%\\\...
`
`W ”WEI,
`
`
`
`
`454
`'
`452FIG. 4
`.470
`410 454
`
`IPR2019-00614 Page 00003
`
`IPR2019-00614 Page 00003
`
`

`

`Patent Application Publication May 31, 2012 Sheet 3 of 17
`
`US 2012/0133484 A1
`
`
`
`IPR2019-00614 Page 00004
`
`IPR2019-00614 Page 00004
`
`

`

`Patent Application Publication
`
`May 31, 2012 Sheet 4 of 17
`
`US 2012/0133484 A1
`
`new
`
`maau.5
`
`1
`
`
`
`
`
`arm.We0,30.
`
`tmfl‘
`
`
`
`
`..‘&‘axi‘wfittel?>,r:.¢¢.i.<)91»!K!I!t‘riiiil99...;‘4
`
`«view.A";>‘.¢.titeb0¥xii~i+¢i£xitthtli)§§.£l!a.Ru....
`
`nmmm.a_we
`
`’,V
`
`
`
`fig.ii:ii..iiiiis.
`
`.1.
`
`wrm..;
`
`new«Po
`
`mo.05
`
`
`
`IPR2019-00614 Page 00005
`
`IPR2019-00614 Page 00005
`
`
`
`

`

`Patent Application Publication
`
`May 31, 2012 Sheet 5 0f 17
`
`US 2012/0133484 A1
`
`8N0
`some0mMw
`
`n
`
`..
`
`w7
`
`
`
`.UE«SW13¢!3i»:e!!!)Sskii080xii!1}§xifi!tii¥$11..i
`
`mgi.a
`
`
`
`
`
`
`.
`V
`. warty-“mg; axxuxm“mxx«xw«mmmmmw-~‘
`m- 4.9""
`
`VFGmma.
`
`006Nro
`
`AG.05
`
`1"...a.“
`
`time
`
`IPR2019-00614 Page 00006
`
`IPR2019-00614 Page 00006
`
`
`
`

`

`Patent Application Publication
`
`May 31, 2012 Sheet 6 0f 17
`
`US 2012/0133484 A1
`
`
`
`%on
`
`GUM}
`
`00w
`
`mmNm
`
`moN®
`
`IPR2019-00614 Page 00007
`
`IPR2019-00614 Page 00007
`
`
`

`

`Patent Application Publication May 31, 2012 Sheet 7 of 17
`
`US 2012/0133484 A1
`
`FIG. 7A
`
`30a
`
`. mull
`Hfififiwfi#fl#,
`
`715
`1{ifl'
`
`714
`
`.- ..
`
`.==IHIII:=
`LIE-“n"!f-i!
`
`_
`
`.
`
`-
`
`714
`
`IPR2019-00614 Page 00008
`
`IPR2019-00614 Page 00008
`
`

`

`Patent Application Publication May 31, 2012 Sheet 8 of 17
`
`US 2012/0133484 A1
`
`“REED »
`(-5
`>
`-
`L
`“kw
`II====::I!
`“iiiiiiiil~
`
`"II-nu.
`
`IPR2019-00614 Page 00009
`
`IPR2019-00614 Page 00009
`
`

`

`Patent Application Publication May 31, 2012 Sheet 9 of 17
`
`US 2012/0133484 A1
`
`
`
`IPR2019-00614 Page 00010
`
`IPR2019-00614 Page 00010
`
`

`

`Patent Application Publication
`
`May 31, 2012 Sheet 10 0f 17
`
`US 2012/0133484 A1
`
`m8:
`
` :mamam3ch538meno323Qmm
`2.562%ncoomm5:5SE503E8&3aam3
`38qu53>63:83S59:m332%momtmuE5%:mSq;
`Sag28$55,88:85a;
`frle
`
`
`mmfic.§989:956909855momtmfi
`
`
`N3ancommafimPcocacoamzfim
`
`Om.05
`
`
`
`
`
`<mADE7
`
`3a
`
`..........ga-
`
`...au..uo-
`
`...
`
`q‘-
`
`.--....---.-
`
`EU
`
`;.-%
`
`IPR2019-00614 Page 00011
`
`IPR2019-00614 Page 00011
`
`
`
`

`

`Patent Application Publication
`
`May 31, 2012 Sheet 11 0f 17
`
`US 2012/0133484 A1
`
`oweEng53ncoomm
`
`
`
`Nan;58E:0::
`
`
`
`VNOJ52
`
`853m
`
`
`
`govmumfiEoomccoo
`
`.\\Nvow588:
`
`
`
`vwowcarom:25szch
`
`x8?«we
`
`82mag35
`
`3.28:8ES
`
`
`
` m«orcogncoo€503
`
`
`
`NE:$5358masonxooEz9.003
`
`
`
`
`
`3.05
`
`mmormega;
`
`
`
`.858SomE:
`
`59I:$9
`
`nmxuoED
`
`awe_.
`
`6255
`
`
`
`mm?59.:.35
`
`88352
`
`oz::55
`
`98.2
`
`«mo?9238
`
`IPR2019-00614 Page 00012
`
`IPR2019-00614 Page 00012
`
`
`
`
`
`
`
`
`
`
`

`

` Detect actuation
`
`of first input
`
`mechanism 1 100
`
`
`input mechanism
`
`11D§
`
`
`
`
`
`
`
`
`
`input mechanism
`llfifl
`
`FIG. 11
`
`
`
`Wipe device
`1165
`
`Patent Application Publication May 31, 2012 Sheet 12 of 17
`
`US 2012/0133484 A1
`
`Activate second
`
`
`Deactivate second
`
`
`
`Start timer and
`count 1 1 1 O
`
`
`Timeout?
`
`lfli
`
`
`
`
`
`Detect input at
`
`
`second input
`
`
`mechanism 1 120
`
`
`
`
`
`
`Count > limit?
`Detect complete
`1180
`input mg
`
`
`
`
`
`
`
`Correct
`input detected?
`
`
`1 135
`
`yes
`
`Unlock device
`
`Reset count
`
`114i
`
`:LtfiQ
`
`IPR2019-00614 Page 00013
`
`IPR2019-00614 Page 00013
`
`

`

`Patent Application Publication May 31, 2012 Sheet 13 of 17
`
`US 2012/0133484 A1
`
`Detect actuaticn
`
`
`
`
`of first input
`
`mechanism 12.11;;
`1 20g
`
`
`
`
`Store Ul state
`
`
` Start timer 121
`
`
`
`
`Timeout
`Detect input at
`or cancel?
`second input
`
`
`
`mechanism 1220
`
`1215
`
`
`
`FIG. 12
`
`
`
`
`Detect com piete
`input 12:30
`
`
`
` Ccrrect
`
`input detected?
`
`
`1 £35
`
`
` Lock device
`
`1 240
`
`IPR2019-00614 Page 00014
`
`IPR2019-00614 Page 00014
`
`

`

`Patent Application Publication
`
`May 31, 2012 Sheet 14 0f 17
`
`US 2012/0133484 A1
`
`
`
`
`
`
` i'us .I’Irfi wohdéringgfi
`
`‘
`Wed; hwy}: 193
`§:
`v Emiiia its: as m ha '
`
`
`Q R353 Vimégamr .; ,
`i
`
`
`
`S‘
`
`1
`
`
`
`i
`
`714
`
`k) 1 vEmilio FW: Where is...
`
`8 Nana Where I left t...
`
`
`
`'
`
`_____:
`wish-{$5.1
`H
`‘fii-iif} 312%?
`x3
`" w
`2 Wm .-:Wt§r 1e ‘
`
`1300b --
`
`1310b
`
`715
`
`
`
`
`
`3 v! Emma RE"; 3:: W ha": i
`
`i
`'.
`Raga 3:23:3an
`
`
`
`
`‘ 43001:
`
`FIG. 13C
`
`IPR2019-00614 Page 00015
`
`IPR2019-00614 Page 00015
`
`

`

`Patent Application Publication May 31, 2012 Sheet 15 of 17
`
`US 2012/0133484 A1
`
`
`
`Enter
`configuration
`mode M952
`
`Detect device
`
`model 1405
`
`Store gap times
`for device
`
`parameters 141
`
`Enter tra§ning
`mode 1500
`
`Detect actuatian
`
`of first input
`mechanism 1§_Q_5_
`
`Start timer 1 1O
`
`Detect input at
`second input
`mechanism 151 _5_
`
`FIG. 14
`
`Siore gap time
`
`M
`
`
`
`Detect completion
`of secand input
`fizé
`
`
`
`Store compietion
`
`time 1530
`
`FIG. 15
`
`IPR2019-00614 Page 00016
`
`IPR2019-00614 Page 00016
`
`

`

`Patent Application Publication May 31, 2012 Sheet 16 of 17
`
`US 2012/0133484 A1
`
` FIG.16C
`
`FIG.16D
`
`IPR2019-00614 Page 00017
`
`IPR2019-00614 Page 00017
`
`

`

`Patent Application Publication May 31, 2012 Sheet 17 of 17
`
`US 2012/0133484 A1
`
` FIG. 1 7C
`
`FIG. 17D
`
`IPR2019-00614 Page 00018
`
`IPR2019-00614 Page 00018
`
`

`

`US 2012/0133484 A1
`
`May 31, 2012
`
`MULTIPLE-INPUT DEVICE LOCK AND
`UNLOCK
`
`BACKGROUND
`
`1. Technical Field
`[0001]
`[0002] The present application relates to systems and meth-
`ods forplacing 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-
`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-
`vated and, in the case of a user input interface, incapable of
`receiving input until they are activated again. Activation ofthe
`inactivated user interface may require input at a designated
`one ofthe 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
`
`In drawings which illustrate by way of example only
`[0005]
`embodiments of the present application,
`[0006]
`FIG. 1 is a block diagram ofan embodiment of an
`exemplary handheld mobile device.
`[0007]
`FIG. 2 is a state diagram illustrating two states of a
`user device.
`
`FIG. 3 is a further state diagram illustrating three
`[0008]
`states of a user device.
`
`FIG. 4 is a cross-sectional view of the handheld
`[0009]
`device of FIG. 1.
`
`FIGS. 5A to 5C are perspective views of a handheld
`[0010]
`device being unlocked or locked.
`[0011]
`FIGS. 6A to 6F are schematic diagrams ofuser input
`paths on a handheld touchscreen device.
`[0012]
`FIGS. 7A to 7E are schematic diagrams ofuser input
`paths on a further handheld device.
`[0013]
`FIGS. 8A to 8D 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-
`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-
`figuring a handheld device for use with the method of FIG. 11
`or 12.
`
`FIG. 15 is a flowchart illustrating a process for train-
`[0021]
`ing a handheld device for use with the method of FIG. 11 or
`12.
`
`FIGS. 16A to 16D are further perspective views of
`[0022]
`another embodiment of a handheld device being unlocked.
`[0023]
`FIGS. 17A to 17D are further perspective views of
`the handheld device of FIGS. 16A to 16D being locked.
`
`DETAILED DESCRIPTION
`
`It is common for user data processing devices, such
`[0024]
`as smartphones, PDAs, tablets, laptops, personal computers,
`media players, and other devices used for personal commu-
`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 ofthe
`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-
`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-
`ing device, or depressing a key on the keyboard, may be
`sufficient to “wake up” the computer and reactivate the moni-
`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-
`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-
`nience key. In the case of a device equipped with a touch-
`screen display, one of the primary user input interfaces may
`be the touchscreen interface. The entire touchscreen inter-
`
`face, including the display component as well as the touch-
`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-
`boards, and other buttons utilizing other types of switch tech-
`nology, may also be configured to be inactivated while in
`sleep mode, leaving only select ones ofthe input mechanisms
`sufficiently powered to detect a user input. When one ofthose
`active input mechanisms detects a user input, such as a key-
`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-
`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—00614 Page 00019
`
`IPR2019-00614 Page 00019
`
`

`

`US 2012/0133484 A1
`
`May 31, 2012
`
`cally, the security code can be an alphanumeric key that may
`be input using the keyboard 116 or a Virtual keyboard dis-
`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-
`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-
`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-
`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 datai
`whether it is the functionality of one of the user input inter-
`faces, the functionality of an application normally executable
`on the device, or access to the data stored on the deviceiis
`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-
`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 routineia keypress, manipulation ofthe
`scroll wheel, contact or pressure on a touch-sensitive or pres-
`sure-sensitive buttonimay 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-
`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-
`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 ofthe 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-
`faces, such as a physical button and a touchscreen. As illus-
`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-
`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-
`vation was accidental and the user was likely not aware ofthe
`activation; thus, the display must continue to consume power
`pending the timeout.
`the embodiments described herein
`[0030] Accordingly,
`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-
`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-00614 Page 00020
`
`IPR2019-00614 Page 00020
`
`

`

`US 2012/0133484 Al
`
`May 31, 2012
`
`the second input is detected within a predetermined period of
`time after completion of the first input, unlocking the elec-
`tronic device.
`
`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 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.
`[0034]
`In a further aspect, the detected first input and the
`detected second input may substantially match a predeter-
`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.
`
`Further, the within embodiments provide that the at
`[0035]
`least two input mechanisms are selected from the group con-
`sisting of: a button, a keyboard, a touchpad, an optical joy-
`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.
`[0036]
`In yet another aspect, detecting said single, continu-
`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.
`[0037]
`In still a further aspect, detecting said single, con-
`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.
`[0038]
`In another aspect, detecting said single, continuous
`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-
`tion.
`
`Further, the embodiments herein provide an elec-
`[0041]
`tronic device, comprising: a first input mechanism; a second
`input mechanism; and a processor in operative communica-
`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
`
`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.
`[0043]
`In a further aspect, the detected first input and the
`detected second input may substantially match a predeter-
`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.
`
`Further, the within embodiments provide that the at
`[0044]
`least two input mechanisms are selected from the group con-
`sisting of: a button, a keyboard, a touchpad, an optical joy-
`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.
`[0045]
`In yet another aspect, detection of said single, con-
`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-
`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.
`[0047]
`In another aspect, detection of said single, continu-
`ous unlock action comprises determining that a path repre-
`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.
`[0049]
`In a further aspect, the means adapted to detect are
`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-
`nisms was completed within either a predefined range of
`speed or a predefined range of time.
`
`IPR2019-00614 Page 00021
`
`IPR2019-00614 Page 00021
`
`

`

`US 2012/0133484 A1
`
`May 31, 2012
`
`In another aspect of the within embodiments, the
`[0050]
`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-
`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-
`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-
`tute a single actionbased on a timing or a speed ofthe 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
`predefined range of speed or a predefined range of time.
`[0054]
`In another aspect of the within methods, the elec-
`tronic device is initially in said locked state, and 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.
`[0055]
`In a further aspect, the at least two input mecha-
`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, and in yet another
`aspect the at least two input mechanisms are selected from
`different members of said group.
`[0056]
`Instructions for configuring an electronic device to
`carry out the within methods and processes may be embodied
`on a computer storage medium, which may be non-transitory.
`[0057] As used herein, an input or interface mechanism can
`include a physical feature such as a button, convenience or
`“soft” key or programmable button, keyboard, trackpad or
`touchpad, optical joystick, rocker button, scroll wheel, touch-
`screen, and the like. User input or interface elements can
`include physical features such as those mentioned above, as
`well as virtual features displayed on a device display, such as
`a virtual keyboard, a graphical user interface element such as
`a button, form field, slider, hyperlink or other HTML element,
`icon, or other text or graphics-based object displayable in a
`graphical user interface.
`[0058]
`Further, “actuation” of a user input mechanism or
`element includes physical activation ofthe user input mecha-
`nism, for example by depressing a button, releasing the but-
`ton, moving a scroll wheel, tracing a gesture or path on the
`
`surface of a touchscreen configured to receive input, and so
`forth. Typically, such actuation causes a signal to be detected
`by a controller or processor in the device, and this signal may
`be used to trigger or generate an instruction for execution by
`the device. Similarly, actuation of a user interface element
`such as a graphical user interface element, can be accom-
`plished by selection of the element, hovering over the ele-
`ment, or activating the element in the graphical user interface,
`as well as by other actions operating on the element, andusing
`a pointing, scrolling or other navigation input (for example,
`using gestures and taps on a touchscreen to select and “click”
`an icon).
`[0059] The embodiments described herein may be imple-
`mented on a communication device such as that illustrated in
`
`FIG. 1. The user device 100 may be a mobile device with
`two-way communication and advanced data communication
`capabilities including the capability to communicate with
`other mobile devices or computer systems through a network
`of transceiver stations. In such an embodiment, the user
`device 100 can also have voice communication capabilities.
`Although the embodiments herein may specifically refer to a
`user device having communication capabilities, and in par-
`ticular to a user device that is adapted for handheld usage, the
`teachings herein may be applied to any appropriate commu-
`nication or data processing device, whether portable or wire-
`lessly enabled or not, including without limitation cellular
`phones, smartphones, wireless organizers, personal digital
`assistants, desktop