Method to unlock a screen using a touch input
Claim Score by NHIP
Abstract
A computer-implemented method is provided for executing an action on an electronic device. The method includes outputting, at a touch screen of the mobile device, a lock screen view configured to prevent unauthorized or inadvertent access to the electronic device. The access is conditioned to a predefined shape of a user touch input. The method further includes, while the lock screen view is displayed at the touch screen, detecting, at the touch screen, a touch input having a first shape, verifying if the first shape has the predefined shape, in response to detecting that the touch input has the predefined shape, executing, by the electronic device, a particular action determined, at least in part on the predefined shape, if detecting a further touch input at least prior or subsequent the predefined shape.

Term
8.4 yearsto projected expiry
Projected expiry 10 February 2035, counted from filing; an application has no term until it is granted.
- Priority and filed
- Published
- Today
- Projected expiry
9 claims: 3 independent, 6 dependent
- 1A computer-implemented method for executing an action on an electronic device, comprising:outputting, at a touch screen of the electronic device, a lock screen view configured to prevent unauthorized or inadvertent access to the electronic device;the access being conditioned to a predefined shape of a user touch input, while the lock screen view is displayed at the touch screen: detecting, at the touch screen, a touch input having a first shape, verifying if the first shape comprises the predefined shape, in response to detecting that the touch input comprises the predefined shape, executing, by the electronic device, a particular action determined, at least in part on the predefined shape, if detecting further touch input at least prior or subsequent the predefined shape.
- 8Broadest claimClaim Score 64, broad(NHIP)An electronic device for executing an action, the electronic device comprising a processor arranged to:output, at a touch screen of the electronic device, a lock screen view configured to prevent unauthorized or inadvertent access to the electronic device;the access being conditioned to a predefined shape of a user touch input, while the lock screen view is displayed at the touch screen, the processor is further arranged to: detect, at the touch screen, a touch input having a first shape, verify if the first shape comprises the predefined shape, in response to detecting that the touch input comprises the predefined shape, execute a particular action determined, at least in part on the predefined shape, if detecting further touch input at least prior or subsequent the predefined shape.
- 9A non-transitory computer-readable medium comprising a program product stored thereon and executable by a computer in the form of a software agent including at least one software module set up to implement a method for executing an action on an electronic device, the method comprising:outputting, at a touch screen of the electronic device, a lock screen view configured to prevent unauthorized or inadvertent access to the electronic device;the access being conditioned to a predefined shape of a user touch input, while the lock screen view is displayed at the touch screen: detecting, at the touch screen, a touch input having a first shape, verifying if the first shape comprises the predefined shape, in response to detecting that the touch input comprises the predefined shape, executing, by the electronic device, a particular action determined, at least in part on the predefined shape, if detecting further touch input at least prior or subsequent the predefined shape.
Independent claims3
77 paragraphs in 5 sections, as filed
FIELD OF THE PRESENT SYSTEM
0001The present invention generally relates to electronic devices, and more specifically to graphical user interfaces displayed by such devices.
BACKGROUND OF THE PRESENT SYSTEM
0002Mobile handsets have an inherently impoverished graphical user interface (GUI) with respect to desktop computers. Small screens and tiny keyboards are typical of mobile handsets that fit in your pocket. Recent so called smart phones have introduced the use of a touch screen in an attempt to simplify the user experience with his mobile handset. For instance, the touch interface of the iPhone® has revolutionized the mobile handset industry and brought whole new mobile user experiences. Touch-based interfaces have now become common-place through the adoption of smartphone and tablet touch screens.
0003In existing smart phones, application programs (AP) may be controlled through interactions such as touch inputs. Different touch inputs may control the AP in different ways. For instance, a user touching an AP icon will cause a control of the desktop GUI that will launch the AP corresponding to the touched icon.
0004A common interaction on a smart phone is to use a continuous, directional gesture or touch input to draw on the touch screen a continuous sequence to unlock the device. Such a known interaction is described in U.S. Pat. No. 8,136,053B1. A lock screen is a Graphical User Interface (GUI) displayed to the user when trying to reuse his electronic device after he activates its lock (screen) mode against unwanted use. An illustration of a known lock screen is displayed in <figref idref="DRAWINGS">FIGS. 4A-4B</figref>.
0005One implementation uses a series of nine circles form an unlock pattern and are displayed to the user in the lock screen GUI of <figref idref="DRAWINGS">FIG. 4A</figref>. These circles are presented to the user as guides to draw a line with his finger. While configuring the lock screen mode, the user is invited as in <figref idref="DRAWINGS">FIG. 4B</figref> to draw at the touch screen of the electronic device a continuous sequence joining a plurality of the nine circles. The continuous sequence—referred here after as the unlock sequence is characterized by a predefined shape <b>430</b> (here illustrated as a W shape). It is saved by the electronic device and will be requested with each user attempt to unlock his device. To facilitate the entry of the unlock sequence, the processor of the device may render a visual feedback (like the thick line <b>430</b>) to the user by showing a line joining the circles as the user's finger <b>410</b> moves across the circles.
0006When detecting at the touch screen a touch input, the processor of the electronic device, when in the lock mode, will compare the shape of the detected touch input to the predefined shape after the user has discontinued his touch input. Provided the shapes are identical, the processor will unlock the device screen and the user will be able to resume interactions with the electronic device.
0007A problem with such a solution is that the unlock sequence may be visible to other people. Existing lock modes do not prevent undesired witnesses from seeing the unlock sequence nor being able to repeat it after stealing the electronic device.
0008Today there is still a need to an improved lock mode for an electronic device such as a smartphone. There is a further need for a lock mode that do not bring additional complexity to the unlocking of the device.
SUMMARY OF THE PRESENT SYSTEM
0009It is an object of the present system to overcome disadvantages and/or make improvements in the prior art.
0010The present system relates to a computer-implemented method for executing an action on an electronic device, comprising: <ul id="ul0001" list-style="none"><li id="ul0001-0001" num="0000"><ul id="ul0002" list-style="none"><li id="ul0002-0001" num="0011">outputting, at a touch screen of the electronic device, a lock screen view configured to prevent unauthorized or inadvertent access to the electronic device; the access being conditioned to a predefined shape of a user touch input,</li></ul></li></ul>
0012while the lock screen view is displayed at the touch screen: <ul id="ul0003" list-style="none"><li id="ul0003-0001" num="0000"><ul id="ul0004" list-style="none"><li id="ul0004-0001" num="0013">detecting, at the touch screen, a touch input having a first shape,</li><li id="ul0004-0002" num="0014">verifying if the first shape comprises the predefined shape,</li><li id="ul0004-0003" num="0015">in response to detecting that the touch input comprises the predefined shape, executing, by the electronic device, a particular action determined, at least in part on the predefined shape, if detecting further touch input at least prior or subsequent the predefined shape.</li></ul></li></ul>
0016Thanks to the present method, the unlock sequence, i.e. the predefined sequence is hidden or obscured in a much longer sequence provided by the user. A longer sequence will be harder to remember for an unwanted witness. Furthermore, the screen may be unlocked only when a longer sequence is detected. Indeed, if the user just enters the unlock sequence, for instance because there is no one around, the screen will not unlock, or a particular action won't be carried out. In other words, the action will be carried out by the electronic device only if the first shape, i.e. the user input, comprises the predefined shape and further touch input.
0017The present system also relates to an electronic device for executing an action, the electronic device comprising a processor arranged to: <ul id="ul0005" list-style="none"><li id="ul0005-0001" num="0000"><ul id="ul0006" list-style="none"><li id="ul0006-0001" num="0018">output, at a touch screen of the electronic device, a lock screen view configured to prevent unauthorized or inadvertent access to the electronic device; the access being conditioned to a predefined shape of a user touch input,</li></ul></li></ul>
0019while the lock screen view is displayed at the touch screen, the processor is further arranged to: <ul id="ul0007" list-style="none"><li id="ul0007-0001" num="0000"><ul id="ul0008" list-style="none"><li id="ul0008-0001" num="0020">detect, at the touch screen, a touch input having a first shape,</li><li id="ul0008-0002" num="0021">verify if the first shape comprises the predefined shape,</li><li id="ul0008-0003" num="0022">in response to detecting that the touch input comprises the predefined shape, execute a particular action determined, at least in part on the predefined shape, if detecting further touch input at least prior or subsequent the predefined shape.</li></ul></li></ul>
0023The present system also relates to an application embodied on a non transitory computer readable storage medium and executable by an electronic device in the form of a software agent including at least one software module comprising instructions to: <ul id="ul0009" list-style="none"><li id="ul0009-0001" num="0000"><ul id="ul0010" list-style="none"><li id="ul0010-0001" num="0024">output, at a touch screen of the electronic device, a lock screen view configured to prevent unauthorized or inadvertent access to the electronic device; the access being conditioned to a predefined shape of a user touch input,</li></ul></li></ul>
0025while the lock screen view is displayed at the touch screen: <ul id="ul0011" list-style="none"><li id="ul0011-0001" num="0000"><ul id="ul0012" list-style="none"><li id="ul0012-0001" num="0026">detect, at the touch screen, a touch input having a first shape,</li><li id="ul0012-0002" num="0027">verify if the first shape comprises the predefined shape,</li><li id="ul0012-0003" num="0028">in response to detecting that the touch input comprises the predefined shape, execute a particular action determined, at least in part on the predefined shape, if detecting further touch input at least prior or subsequent the predefined shape.</li></ul></li></ul>
BRIEF DESCRIPTION OF THE DRAWINGS
0029The invention is explained in further detail, and by way of example, with reference to the accompanying drawings wherein:
0030<figref idref="DRAWINGS">FIG. 1</figref> shows a mobile device in accordance with an embodiment of the present system;
0031<figref idref="DRAWINGS">FIGS. 2A</figref>, <b>2</b>B show lock screen GUIs in accordance with an embodiment of the present electronic device;
0032<figref idref="DRAWINGS">FIGS. 3A-3C</figref>, shows exemplary flowcharts in accordance with an embodiment of the present system,
0033<figref idref="DRAWINGS">FIGS. 4A-4B</figref> show a known lock GUI of an electronic device, and;
0034<figref idref="DRAWINGS">FIGS. 5A-5B</figref> shows unlock sequences according to the present system.
DETAILED DESCRIPTION OF THE PRESENT SYSTEM
0035The following are descriptions of illustrative embodiments that when taken in conjunction with the following drawings will demonstrate the above noted features and advantages, as well as further ones. In the following description, for purposes of explanation rather than limitation, illustrative details are set forth such as architecture, interfaces, techniques, element attributes, etc. However, it will be apparent to those of ordinary skill in the art that other embodiments that depart from these details would still be understood to be within the scope of the appended claims. Moreover, for the purpose of clarity, detailed descriptions of well known devices, circuits, tools, techniques and methods are omitted so as not to obscure the description of the present system. It should be expressly understood that the drawings are included for illustrative purposes and do not represent the scope of the present system. In the accompanying drawings, like reference numbers in different drawings may designate similar elements.
0036For purposes of simplifying a description of the present system, the terms “operatively coupled”, “coupled” and formatives thereof as utilized herein refer to a connection between devices and/or portions thereof that enables operation in accordance with the present system. For example, an operative coupling may include one or more of a wired connection and/or a wireless connection between two or more devices that enables a one and/or two-way communication path between the devices and/or portions thereof. An operative coupling may also include a wired and/or wireless coupling to enable communication between a media content platform and one or more user devices in accordance with an embodiment of the present system. An operative coupling may also relate to an interaction between program portions and thereby may not describe a physical connection so much as an interaction based coupling.
0037The term rendering and formatives thereof as utilized herein refer to providing content, such as digital media or a graphical user interface (GUI), such that it may be perceived by at least one user sense, such as a sense of sight and/or a sense of hearing. For example, the present system may render a user interface such as a lock screen on a display device so that it may be seen and interacted with by a user. The term rendering may also comprise all the actions required to generate a GUI prior to the display, like e.g. a map representation generated on a server side for a browser application on a user device.
0038The system, device(s), method, user interface, etc., described herein address problems in prior art systems. The man skilled in the art may easily apply the present teachings to any electronic device presenting a touch sensitive panel, (referred also hereafter as a touch sensitive display or screen), a pointing device (like a mouse) or a keyboard.
0039In accordance with an embodiment of the present system, an electronic device provides a lock screen GUI for controlling through user inputs, such e.g. as a continuous gesture, the access to the device. In the description hereafter, reference will be made to a mobile device or handsets. This is in no way a limitation of the present method as the teaching herein may be applied to any electronic device presenting a touch interface.
0040A graphical user interface (GUI) may be provided in accordance with an embodiment of the present system:
0041by an application program running locally on a device processor, such as part of a computer system of a mobile device, and/or,
0042as provided by a network connected device or web based server, such as a content server providing content to the user device, the GUI being rendered on user device through a local application program (e.g. a browser or web application) connected to media content server.
0043For instance, the present GUI enabling the lock screen mode may be generated by generating locally a lock screen GUI. Alternatively, the present GUI may be the rendering by a local AP of a preprocessed lock interface. The provided visual environment may be displayed by the processor on a display device of the user device, e.g. a touch sensitive panel (touch panel in short), which a user may use to provide a number of touch inputs such as a continuous touch input.
0044A GUI is a type of user interface which allows a user to interact with electronic devices such as computers, hand-held devices such as smartphones or tablets, household appliances, office equipment and the likes. GUIs are typically used to render visual and textual images which describe various visual metaphors of an operating system, an application, etc., and implemented on a processor/computer including rendering on a display device. Furthermore, GUIs can represent programs, files and operational functions with graphical images, objects, or vector representations. The graphical images can include windows, fields, dialog boxes, menus, icons, buttons, cursors, scroll bars, maps, etc. Such images can be arranged in predefined layouts, or can be created dynamically (by the device itself or by a web-based server) to serve the specific actions being taken by a user. In general, the user can select and/or activate various graphical images in order to initiate functions and tasks, i.e. controls, associated therewith. By way of example, a user can select a button that opens, closes, minimizes, or maximizes a window, a virtual representation or an icon that launches a particular application program. By way of another example, the GUI may present a typical user interface including a windowing environment and as such, may include menu items, pull-down menu items, icons, pop-up windows, etc., that are typical of those provided in a windowing environment, such as may be represented within a Windows™ Operating System GUI as provided by Microsoft Corporation and/or an OS X™ Operating System GUI, such as provided on an iPhone™, MacBook™, iMac™, etc., as provided by Apple, Inc., and/or another operating system (OS).
0045In the description here after, an application program (AP)—or software—may be seen as any tool that functions and is operated by means of a computer, with the purpose of performing one or more functions or tasks for a user or another application program. To interact with and control an AP, a GUI of the AP may be displayed on the user device display.
0046A lock screen is a user interface used by various operating systems to regulate immediate access to a device by requiring that the user performs a certain action in order to receive access. The action may be one of entering a password, using a certain button combination, or by performing a certain continuous gesture using the device's touch screen. In the hereafter description, reference will be made to a lock screen (mode) using a continuous gesture to to unlock.
0047<figref idref="DRAWINGS">FIG. 1</figref> is an illustration of an exemplary user device <b>100</b> used in the present system. In the here after description, the user or electronic device will be illustrated as a mobile device <b>100</b> with a touch interface. This illustration is in no way limiting as the present teaching would work for any user devices such as laptops, pads, desktops and the likes, enabling the user to interact through a touch interface, a pointing device and/or a keyboard. The mobile device <b>100</b> comprises a display device <b>140</b>, a processor <b>110</b>, a controller <b>113</b> of the display device, and an input device <b>115</b>.
0048In the present system, the user interaction with and manipulation of the application program rendered on a GUI is achieved using the display device <b>140</b>, or screen, which is presently a touch panel operationally coupled to the processor <b>112</b> controlling the displayed interface.
0049Processor <b>110</b> may control the rendering and/or the display of the GUI on the display device <b>140</b> depending on the type of application program, i.e. resident or web-based. Processor <b>110</b> may also handle the user entries according to the present method. The user entries to interact with an application program may be provided through interactions with the touch panel <b>140</b>.
0050The touch panel <b>140</b> can be seen as an input device allowing interactions with a finger of a user or other devices such as a stylus. Touch sensor interface or touch panel <b>140</b> may include any suitable circuitry to convert analog signals corresponding to touch input received over its surface into any suitable digital touch input data. Such touch input data can, for example, be used to make selections of portions of the GUI of an AP or draw in continuous sequence on the display device <b>140</b> as explained here after. The input received from a user's touch is sent to the processor <b>110</b>. The touch panel <b>140</b> is configured to detect and report the (location of the) touches to the processor <b>110</b>, that can further characterize the touch input through its shape, length, duration, coordinates . . . It will also interpret the touches in accordance with the application program and the currently displayed GUI. For example, the processor <b>110</b> can initiate a task, e.g. a control of the AP to seek a subportion of an hidden portion of an electronic document subsequent to a scrolling input received on the touch panel <b>140</b>.
0051The controller <b>113</b>, e.g. a dedicated processor, may be provided to process input touches locally and reduce demand for the main processor <b>110</b> of the mobile device. The touch panel <b>140</b> can be based on sensing technologies including but not limited to capacitive sensing, resistive sensing, surface acoustic wave sensing, pressure sensing, optical sensing, and/or the likes. Here after, for simplification purpose, reference will be made to a finger of the user touching panel <b>140</b>, other devices such as a stylus may be used in place of the user finger.
0052In the present system, a number of different applications may be provided with the mobile device <b>100</b>, like AP<b>1</b><b>131</b>, AP<b>2</b><b>132</b> and Lock AP <b>133</b>. AP<b>1</b> and AP<b>2</b> may be for instance web applications like news or sports applications. The lock mode of the present system may be controlled by a lock AP or module <b>133</b> under the control of the processor <b>110</b>.
0053The Lock AP <b>133</b> will be arranged to: <ul id="ul0013" list-style="none"><li id="ul0013-0001" num="0000"><ul id="ul0014" list-style="none"><li id="ul0014-0001" num="0054">request from the user to define a continuous sequence corresponding to the unlock or unlocking sequence. This corresponds to the configuration of the lock mode. The unlocking sequence is characterized with an unlock shape, referred too here after as the predefined shape. When starting configuration of the lock screen mode, the Lock AP <b>133</b> may render e.g. a nine circle lock GUI like the known lock interface of <figref idref="DRAWINGS">FIG. 4A</figref>. The user is then invited to enter a continuous gesture or user input to draw a line <b>230</b> e.g. joining the bottom left corner circle <b>211</b> to the top right corner circle <b>213</b>. The Lock AP <b>133</b> may render a visual feedback to the user by showing the line <b>230</b> joining the circles as the user's finger <b>210</b> moves diagonally across the lock GUI <b>200</b>,</li><li id="ul0014-0002" num="0055">save the received continuous sequence as the unlock sequence, as characterized through its length L, and shape (e.g. a series of coordinates on the touch screen for the continuous sequence),</li><li id="ul0014-0003" num="0056">receive from the user association of the unlock sequence to a particular action. Indeed, it is commonly known to use the provided continuous sequence to simply unlock the whole electronic device. The user may be invited to provide several different unlock sequences, each being associated to a particular action. Indeed, a particular sequence may be associated to just unlocking texting or emailing or web browsing. Another sequence may be associated to unlocking the call function or the camera</li><li id="ul0014-0004" num="0057">start the lock mode upon receiving a specific trigger from the user, like the pressing of a specific button on the electronic device, as with known smartphones, or after a certain preconfigured time out,</li><li id="ul0014-0005" num="0058">render the lock screen, e.g. the interface showing the 9 circles as in the known Android™ environment,</li><li id="ul0014-0006" num="0059">detect at the touch screen any user touch inputs having a first shape,</li><li id="ul0014-0007" num="0060">verify if the first shape comprises the predefined shape of the unlock sequence,</li><li id="ul0014-0008" num="0061">in response to detecting that the touch input comprises the predefined shape, confirming authorized access to the processor <b>110</b>, if detecting further touch input on top of the predefined shape, i.e. before or after the predefined shape.</li></ul></li></ul>
0062Provided authorized access is confirmed, i.e. that the provided gesture input has a first shape comprising the predefined shape of the unlock sequence, the processor <b>110</b> may execute as mentioned before a particular action determined, at least in part, on the predefined shape,
0063In the proposed system, further touch input must be detected on top of the detection of the predefined shape. The further touch input may correspond to further touch input of a given length or captured during a predefined time, as detailed hereafter. Such further touch input from the user will disguise the actual predefined shape in a much longer continuous user input. Another user witnessing the longer sequence will not be able to guess which part of the sequence actually triggers the predefined action such as discontinuing the lock mode.
0064<figref idref="DRAWINGS">FIG. 3A</figref> is a flowchart illustrating an exemplary embodiment of the present method. Flowchart of <figref idref="DRAWINGS">FIG. 3A</figref> will be described in relation with exemplary illustrations of <figref idref="DRAWINGS">FIGS. 2A and 2B</figref>. The present unlock mode is implemented on the mobile device through its processor <b>110</b> seen in <figref idref="DRAWINGS">FIG. 1</figref>.
0065In an initiation act <b>300</b>, the user trigger the lock AP <b>133</b> to configure the lock mode with an unlock sequence. To do so, he will enter in an act <b>305</b> a lock sequence <b>230</b> through a user touch input using for instance his finger <b>210</b> as seen in <figref idref="DRAWINGS">FIG. 2A</figref>. As mentioned before, the processor <b>110</b> may, through the lock AP <b>133</b>, render a visual feedback such as a thick line <b>230</b> joining the different circles that the entered unlock sequence crosses. Upon releasing his finger, i.e. discontinuing the touch input, the processor will save the continuous sequence provided before release of the finger as the unlock sequence. An illustration of an unlock sequence may be found in <figref idref="DRAWINGS">FIG. 2A</figref>, wherein the unlock sequence <b>230</b> joins diagonally the lower left circle <b>211</b> to the upper right circle <b>212</b>.
0066In a further act <b>310</b>, the electronic device will enter the lock mode, either through a user activation, or after a time out for instance. Each time the user will try to re-access the device, the processor <b>110</b> will display the known lock interface—as already seen in FIG. <b>4</b>A—in a further act <b>320</b>. To trigger the lock interface, different techniques are readily available to the man skilled in the act like pressing of a dedicated button (the same for instance as the one that locks the device), or the sliding of the interface using a touch input in one direction to reveal the lock interface.
0067In a further act <b>330</b>, the processor will monitor and detect a touch input having, i.e. characterized with, a first shape. In a further act <b>340</b>, the processor will verify if the first shape comprises the predefined shape entered in the initiation acts <b>300</b>-<b>305</b>.
0068The verifying <b>340</b> may be triggered in different ways. In an additional embodiment of the present system, the verifying may be performed as the touch input is received from the user. This may be seen as a verifying “on the fly”. This may be triggered from the very beginning of the touch input on the lock screen. Alternatively, the verifying may be triggered once the length of the touch input L<b>1</b> reaches the length L of the predefined shape.
0069Indeed, in an alternative embodiment of the present system, illustrated in <figref idref="DRAWINGS">FIG. 3B</figref>, the length of the touch input will determine when the verifying is triggered. The predefined shape is of a predefined length L, while the first shape of the user input is of a first length L<b>1</b>. In this embodiment, the verifying <b>340</b> is carried out in response to detecting (Yes to act <b>335</b>) that the first length L<b>1</b> is at least greater than the predefined length L. In other words, as long as the length of the continuous input from the user has not reached the length L of the predefined shape (No to act <b>335</b>), the verifying of act <b>340</b> will not be carried out, and the processor will monitor the user input in act <b>330</b>and its length L<b>1</b>.
0070Provided the first shape does not comprise the predefined shape (answer No to act <b>340</b>), the processor will resume with detecting further touch input from the user in act <b>330</b> as seen in <figref idref="DRAWINGS">FIGS. 3A and 3B</figref>. This resuming of act <b>330</b> will be carried out as long as the first shape does not comprise the predefined shape. If the embodiment of <figref idref="DRAWINGS">FIG. 3B</figref> is implemented, the act <b>335</b> is no longer needed once L<b>1</b> has reached L (dotted line between acts <b>330</b> and <b>340</b> in <figref idref="DRAWINGS">FIG. 3B</figref>).
0071In order to avoid looping between acts <b>330</b> and <b>340</b>, in an additional embodiment of the present system (not shown in <figref idref="DRAWINGS">FIG. 3A</figref> nor <b>3</b>B), the verifying may be carried out for only a predefined amount of time T<b>1</b>. Once T<b>1</b> is lapsed, and the first shape still does not comprise the predefined shape (answer No to act <b>340</b>), the processor <b>110</b> will control the Lock AP <b>133</b> to return to the lock screen in act <b>320</b> (dotted lines from act <b>340</b> to act <b>320</b> in <figref idref="DRAWINGS">FIG. 3A</figref>).
0072Alternatively, the user may decides to discontinue his touch input. Provided the predefined shape still cannot be found in the first shape, the processor will also control the Lock AP <b>133</b> to return to the lock screen in act <b>320</b> (dotted lines from act <b>340</b> to act <b>320</b> in <figref idref="DRAWINGS">FIG. 3A</figref>).
0073In an alternative embodiment of the present system, illustrated in <figref idref="DRAWINGS">FIG. 3C</figref>, the verifying of act <b>340</b> may be carried out only in response to detecting a discontinuation of the touch input in act <b>336</b>. Indeed, as in known methods, the verifying <b>340</b> may be carried out only when the finger is released from the screen, i.e. that the touch input is discontinued (Yes to act <b>336</b>). Contrary to the previous embodiments, such an alternative one allows to postpone the comparison after the touch input from the user is complete (according to the user). As long as the touch input is continued (No to act <b>336</b>), the processor will further monitor the user touch input in act <b>330</b>. In this specific embodiment of <figref idref="DRAWINGS">FIG. 3C</figref>, if the predefined shape cannot be found in the first shape (No to act <b>340</b>), the processor will control the Lock AP <b>133</b> to return to the lock screen in act <b>320</b> as seen in <figref idref="DRAWINGS">FIG. 3B</figref>.
0074In the present system, the user will need to provide an additional sequence on top of the predefined sequence. In other words, once the processor has identified the predefined sequence in the user input, it will monitor if further touch input is provided by the user either before or after the unlock sequence (corresponding to the predefined shape). In order to do so, it will verify in act <b>350</b> if the further touch input is found on top of, i.e. at least prior or subsequent, the predefined shape.
0075A low security approach would consist in verifying if further touch input of a predefined length L<b>2</b> is found before the unlock sequence. In this approach, as soon as the predefined shape is detected in the first shape, the processor will trigger the particular action the moment the first shape comprises a portion longer than L<b>2</b> prior the unlock sequence.
0076An approach with increased security would consist in verifying if further touch input of a predefined length L<b>3</b> is found after the unlock sequence. In this approach, once the predefined shape is detected in the first shape, the processor will delay the particular action by waiting further touch input of a length L<b>3</b>.
0077The present system may verify that further touch inputs of respective length L<b>2</b> and L<b>3</b> are found prior and subsequent the unlock sequence in the user input. An illustration of such an implementation may be found in <figref idref="DRAWINGS">FIG. 2B</figref>, wherein the unlock sequence <b>230</b> of <figref idref="DRAWINGS">FIG. 2A</figref> is surrounded by a first sequence <b>232</b> and a second sequence <b>234</b> of length respectively L<b>2</b> and L<b>3</b> (here illustrated as L<b>2</b>=L<b>3</b>=distance between three consecutive circles on a side of the unlock pattern). In this illustration, the processor <b>110</b> is configured to detect further touch input of a length L<b>2</b>=L<b>3</b> respectively prior and subsequent the unlock sequence <b>230</b> before authorizing the particular action.
0078In an alternative embodiment of the present system, the further touch input may be monitored for a second predefined amount of time T<b>2</b> after the unlock sequence is found in the first shape. This is illustrated in <figref idref="DRAWINGS">FIG. 2B</figref>, wherein the sequence prior to the unlock sequence may or may not be monitored, and the sequence <b>234</b> after the unlock sequence corresponds to how far the user's finger <b>210</b> may go in the second predefined amount of time T<b>2</b>.
0079The present system may combine the monitoring of a sequence of length L<b>2</b> prior to the unlock sequence, while monitoring further touch input for the time T<b>2</b> after the unlock sequence.
0080Once further touch input is found prior or/and after the unlock sequence (answer Yes to act <b>350</b>), the processor <b>110</b> will execute a particular action determined, at least in part on the predefined shape.
0081Provided no further touch input is found according to the act <b>350</b>, the processor will configure the Lock AP <b>320</b> to display the lock screen again.
0082In the present description, reference was made to an lock screen GUI comprising nine circles (arrange 3 by 3) to help the user configure and draw an unlocking sequence. A more complex 2D sequence may be provided by the user either using a grid as a guidance or no grid at all. The identification of the predefined shape in the provided user input may then use some confidence margin to determine if the provided shape is sufficiently similar to the predefined shape. The verifying of act <b>340</b> then encompasses if the first shape comprises the predefined shape to a predefined degree of confidence. Comparison software may be used for the verifying act <b>340</b> and are beyond the scope of the present system.
0083More complex 2D sequences are illustrated in <figref idref="DRAWINGS">FIGS. 5A-5B</figref>. As seen in these figures, a common sequence <b>530</b> is surrounded by very different sequences prior and after the unlocking sequence <b>530</b>. In <figref idref="DRAWINGS">FIG. 5A</figref>, the additional sequences <b>532</b> (prior) and <b>534</b> (after) to the unlocking sequence are of similar length. The shape of the unlocking sequence will be monitored. In an additional embodiment of the present system, the processor <b>110</b> may also monitor the absolute position on the touch interface of the unlocking sequence as comprised in the user input. In other words, if the user reproduces the predefined shape, but in a different position than the one initial entered by the user during the initiation act <b>300</b>, the device will consider the access as unauthorized and return to the lock screen. As can be seen from <figref idref="DRAWINGS">FIGS. 5A and 5B</figref>, the unlocking sequence <b>530</b> are substantially located at the same place within the touch interface <b>500</b> on both figures. Alternatively, only the shape of the unlocking sequence may be monitored, regardless of its position as the user draws the shape on the interface <b>500</b>.
0084The user input in <figref idref="DRAWINGS">FIG. 5B</figref> presents a fairly longer sequence <b>532</b> prior to the unlocking sequence <b>530</b>. Yet the unlocking will still be authorized. Such a complex shape over all (including the 3 sequences <b>532</b>, <b>530</b> and <b>534</b>) would be virtually impossible for an undesired witness to reproduce.
0085The present embodiments were illustrated mostly using reference to touch inputs on a touch interface. The presents teaching may easily be implemented using a pointing device a stylus.
0086Finally, the above discussion is intended to be merely illustrative of the present system and should not be construed as limiting the appended claims to any particular embodiment or group of embodiments. Thus, while the present system has been described with reference to exemplary embodiments, including user interfaces, it should also be appreciated that numerous modifications and alternative embodiments may be devised by those having ordinary skill in the art without departing from the broader and intended spirit and scope of the present system as set forth in the claims that follow.
0087The section headings included herein are intended to facilitate a review but are not intended to limit the scope of the present system. Accordingly, the specification and drawings are to be regarded in an illustrative manner and are not intended to limit the scope of the appended claims.
0088In interpreting the appended claims, it should be understood that:
0089a) the word “comprising” does not exclude the presence of other elements or acts than those listed in a given claim;
0090b) the word “a” or an preceding an element does not exclude the presence of a plurality of such elements,
0091c) any reference signs in the claims do not limit their scope;
0092d) several “means” may be represented by the same item or hardware or software implemented structure or function;
0093e) any of the disclosed elements may be comprised of hardware portions (e.g., including discrete and integrated electronic circuitry), software portions (e.g., computer programming), and any combination thereof;
0094f) hardware portions may be comprised of one or both of analog and digital portions;
0095g) any of the disclosed devices or portions thereof may be combined together or separated into further portions unless specifically stated otherwise;
0096h) no specific sequence of acts or steps is intended to be required unless specifically indicated; and
0097i) the term “plurality of” an element includes two or more of the claimed element, and does not imply any particular range of number of elements; that is, a plurality of elements may be as few as two elements, and may include an immeasurable number of elements.
Contents5
7 sheets
Sheet 1 Sheet 2 Sheet 3 Sheet 4 Sheet 5 Sheet 6 Sheet 7
Every citation, both ways
| Document | Relation | Office | Cited during |
|---|---|---|---|
| US2016180067A1 | Cited by | United States of America | Pre-grant |
| US9760707B2 | Cited by | United States of America | Search report |
| US2017116408A1 | Cited by | United States of America | Pre-grant |
| US2016042172A1 | Cited by | United States of America | Search report |
| US2017185856A1 | Cited by | United States of America | Search report |
| WO2019184865A1 | Cited by | World Intellectual Property Organization (WIPO) | International search |
| CN109104759A | Cited by | China | Search report |
| US2018239882A1 | Cited by | United States of America | Search report |
| US9679121B2 | Cited by | United States of America | Applicant |
| US2017185856A1 | Cited by | United States of America | Search report |
| US2017185856A1 | Cited by | United States of America | Pre-grant |
| US2017116407A1 | Cited by | United States of America | Pre-grant |
| US2016291804A1 | Cited by | United States of America | Search report |
| US10558355B2 | Cited by | United States of America | Search report |
| US2017185856A1 | Cited by | United States of America | Search report |
| US2016042172A1 | Cited by | United States of America | Search report |
| US11119648B2 | Cited by | United States of America | Applicant |
| US2016042172A1 | Cited by | United States of America | Pre-grant |
| US9471761B2 | Cited by | United States of America | Search report |
| US9754095B2 | Cited by | United States of America | Search report |
| US2017185856A1 | Cited by | United States of America | Search report |
| US2011041102A1 | Cites | United States of America | Pre-grant |
| US2011130170A1 | Cites | United States of America | Pre-grant |
| US2011187497A1 | Cites | United States of America | Pre-grant |
| US2011279384A1 | Cites | United States of America | Pre-grant |
| US2011283241A1 | Cites | United States of America | Pre-grant |
| US2011294467A1 | Cites | United States of America | Pre-grant |
| US2012262388A1 | Cites | United States of America | Pre-grant |
| US2012313848A1 | Cites | United States of America | Pre-grant |
| US2013111408A1 | Cites | United States of America | Pre-grant |
| US2013160110A1 | Cites | United States of America | Pre-grant |
| US2013194206A1 | Cites | United States of America | Pre-grant |
| US2013229367A1 | Cites | United States of America | Pre-grant |
| US2013239058A1 | Cites | United States of America | Pre-grant |
| US2013271360A1 | Cites | United States of America | Pre-grant |
| US2013283199A1 | Cites | United States of America | Pre-grant |
| US2013305352A1 | Cites | United States of America | Pre-grant |
| US2013312083A1 | Cites | United States of America | Pre-grant |
| US2014002375A1 | Cites | United States of America | Pre-grant |
| US2014033136A1 | Cites | United States of America | Pre-grant |
| US2014267064A1 | Cites | United States of America | Pre-grant |
| US9606643B2 | Cites | United States of America | Pre-grant |
| US9619037B2 | Cites | United States of America | Pre-grant |
| US9665178B2 | Cites | United States of America | Pre-grant |
5 members in 3 offices
Members5
| Document | Office | Kind | |
|---|---|---|---|
| WO2014155196A1 | World Intellectual Property Organization (WIPO) | A1 | |
| EP2979477A1 | European Patent Office (EPO) | A1 | |
| US2016054884A1 | United States of America | A1 | |
| US10216403B2 | United States of America | B2 | |
| EP2979477B1 | European Patent Office (EPO) | B1 |
81 transactions on the USPTO file
Allowed after 1 non-final rejection, 1 final rejection and 1 RCE.
- Non-final rejections
- 1
- Final rejections
- 1
- RCEs
- 1
- Appeals
- 0
Over time
Point at a mark for the transactionTransactions
| Event | Code | |
|---|---|---|
| Payment of Maintenance Fee, 4th Year, Large EntityM1551 | M1551 | |
| Recordation of Patent Grant MailedPGM/ | PGM/ | |
| Patent Issue Date Used in PTA CalculationAllowedPTAC | PTAC | |
| Email NotificationEML_NTR | EML_NTR | |
| Issue Notification MailedAllowedWPIR | WPIR | |
| Dispatch to FDCD1935 | D1935 | |
| Email NotificationEML_NTR | EML_NTR | |
| Printer Rush- No mailingTCPB | TCPB | |
| Mail Miscellaneous Communication to ApplicantMM327 | MM327 | |
| Application Is Considered Ready for IssuePILS | PILS | |
| Miscellaneous Communication to Applicant - No Action CountM327 | M327 | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Pubs Case Remand to TCPUBTC | PUBTC | |
| Information Disclosure Statement (IDS) FiledM844 | M844 | |
| Response to Reasons for AllowanceREAS | REAS | |
| Issue Fee Payment VerifiedN084 | N084 | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Issue Fee Payment ReceivedIFEE | IFEE | |
| Email NotificationEML_NTR | EML_NTR | |
| Printer Rush- No mailingTCPB | TCPB | |
| Mail Miscellaneous Communication to ApplicantMM327 | MM327 | |
| Miscellaneous Communication to Applicant - No Action CountM327 | M327 | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Pubs Case Remand to TCPUBTC | PUBTC | |
| Electronic ReviewELC_RVW | ELC_RVW | |
| Email NotificationEML_NTF | EML_NTF | |
| Mail Notice of AllowanceAllowedMN/=. | MN/=. | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Notice of Allowance Data Verification CompletedAllowedN/=. | N/=. | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Disposal for a RCE / CPA / R129AbandonedABN9 | ABN9 | |
| Request for Continued Examination (RCE)RCEX | RCEX | |
| Workflow - Request for RCE - BeginBRCE | BRCE | |
| Email NotificationEML_NTR | EML_NTR | |
| Mail Advisory Action (PTOL - 303)MCTAV | MCTAV | |
| After Final Consideration Program Amendment too ExtensiveAFNE | AFNE | |
| Advisory Action (PTOL-303)CTAV | CTAV | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Response after Final ActionA.NE | A.NE | |
| PILOT- Request for After Final Consideration ProgramRAFC | RAFC | |
| Electronic ReviewELC_RVW | ELC_RVW | |
| Email NotificationEML_NTF | EML_NTF | |
| Mail Final Rejection (PTOL - 326)Final rejectionMCTFR | MCTFR | |
| Final RejectionFinal rejectionCTFR | CTFR | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Response after Non-Final ActionA... | A... | |
| Request for Extension of Time - GrantedXT/G | XT/G | |
| Electronic ReviewELC_RVW | ELC_RVW | |
| Email NotificationEML_NTF | EML_NTF | |
| Mail Non-Final RejectionNon-final rejectionMCTNF | MCTNF | |
| Non-Final RejectionNon-final rejectionCTNF | CTNF | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| Electronic Information Disclosure StatementEIDS. | EIDS. | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Electronic Information Disclosure StatementEIDS. | EIDS. | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Electronic Information Disclosure StatementEIDS. | EIDS. | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| PG-Pub Issue NotificationPG-ISSUE | PG-ISSUE | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| Application Is Now CompleteCOMP | COMP | |
| Application Dispatched from OIPEOIPE | OIPE | |
| Application ready for PDX access by participating foreign officesCCRDY | CCRDY | |
| Sent to Classification ContractorPGPC | PGPC | |
| FITF set to YES - revise initial settingFTFS | FTFS | |
| Notice of DO/EO Acceptance MailedM903 | M903 | |
| Filing ReceiptFLRCPT.O | FLRCPT.O | |
| Request for Foreign Priority (Priority Papers May Be Included)RQPR | RQPR | |
| Electronic Information Disclosure StatementEIDS. | EIDS. | |
| Preliminary AmendmentA.PE | A.PE | |
| 371 Completion Date371COMP | 371COMP | |
| Patent Term Adjustment - Ready for ExaminationPTA.RFE | PTA.RFE | |
| Applicants have given acceptable permission for participating foreignAPPERMS | APPERMS | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Cleared by OIPE CSRL194 | L194 | |
| Entity Status Set To Undiscounted (Initial Default Setting or Status Change)BIG. | BIG. | |
| Initial Exam Team nnIEXX | IEXX |
4 legal events, as the office reported them to INPADOC
Over the term
Point at a mark for the eventEvents
| Event | Code | |
|---|---|---|
| Maintenance fee paymentMAFP | MAFP | |
| Maintenance fee paymentMAFP | MAFP | |
| Information on status: patent grantGrantedPATENTED CASESTCF | STCF | |
| AssignmentAS | AS |
Numbers
- Publication
- 20160054884
- Application
- 14781250
Titles
- English
- METHOD TO UNLOCK A SCREEN USING A TOUCH INPUT
Patent term adjustment
- A delay
- +306 daysthe office missed an examination deadline
- B delay
- +105 dayspendency past three years
- Applicant delay
- −90 days
- Net adjustment
- 321 days
Classification
- CPC, 8
- G06F3/0488
- G06F3/0484
- G06F21/36
- H04W88/02
- H04M1/72577
- G06F3/04883
- H04W12/68
- H04M1/724631
- IPC, 2
- G06F3 0488
- H04M1 725
- USPC, 1
- 715863000