# Patent

## Title
Mobile device authentication through touch-based gestures

## Abstract

A method, system, and apparatus of a touch-based authentication of a mobile device through user generated pattern creation are disclosed. In one embodiment, a method of a mobile device includes recognizing a tactile force on a touch screen without a visual aid as an unlocking gesture, storing the unlocking gesture to a memory of the mobile device, associating another tactile force on the touch screen with the unlocking gesture, and transforming the mobile device from an initial state to an unlocked state based on the association between the another tactile force and the unlocking gesture. The method may include transforming the mobile device to operate as a telephonic communication device in the unlocked state.

## Background
CROSS REFERENCE TO RELATED APPLICATIONS
This application is a continuation of: pending U.S. patent application Ser. No. 13/864,281 titled “Touch Screen Security Gesture Shared Between Mobile Devices” filed on Apr. 17, 2013; which is a continuation-in-part of pending U.S. patent application Ser. No. 13/083,632 titled “Comparison of an Applied Gesture on a Touch Screen of a Mobile Device with a Remotely Stored Security Gesture” filed on Apr. 11, 2011; which is a continuation-in-part of U.S. Pat. No. 8,174,503 B2 titled “Touch-Based Authentication of a Mobile Device Through User Generated Pattern Creation” filed May 17, 2008. This application is a continuation of: pending U.S. patent application Ser. No. 13/189,592 titled “Gesture Based Authentication for Wireless Payment” filed on Jul. 25, 2011; which is a continuation-in-part of U.S. Pat. No. 8,174,503 B2 titled “Touch-Based Authentication of a Mobile Device through User Generated Pattern Creation” filed on May 17, 2008. The methods of U.S. patent application Ser. No. 13/083,632 titled ‘Comparison of an Applied Gesture on a Touch Screen of a Mobile Device with a Remotely Stored Security Gesture’ filed on Apr. 11, 2011 are herein incorporated by reference. The methods of U.S. patent application Ser. No. 13/864,281 titled “Touch Screen Security Gesture Shared Between Mobile Devices” filed on Apr. 17, 2013 are herein incorporated by reference. The methods of U.S. patent application Ser. No. 13/189,592 titled “Gesture Based Authentication for Wireless Payment” filed on Jul. 25, 2011 are herein incorporated by reference.


FIELD OF TECHNOLOGY
This disclosure relates generally to an enterprise method, a technical field of software and/or hardware technology and, in one example embodiment, to touch-based authentication of a mobile device through user generated pattern creation.
BACKGROUND
Security of a mobile device (e.g., a mobile phone, a mobile player, an Apple® iPhone®, etc.) may be of concern to a user. Furthermore, the user may utilize the mobile device in manner similar to a personal computer (e.g., browse the Internet, access email, etc.). Consequently, the mobile device may include confidential information (e.g., a web browser history, an email account, a past call history, a text message, a voice message, etc.). Due to the nature of this type of information, a security breach may be costly to the user or his/her organization (e.g., a difficulty in recreating lost information).
A design of the mobile device may make it problematic to implement an additional security protocol. For example, the mobile device may utilize a touchscreen (e.g., a display which can detect a location of forces in a display area) for user input rather than a physical keypad. The user may be able to access the mobile device utilizing the touchscreen simply by tapping a surface of the touchscreen in an arbitrary manner and/or performing a templated gesture (e.g., a pattern such as movement from left to right) on a surface of the touch screen. As a result, confidential information may be accessed by anyone merely in physical possession of the mobile device.
The touchscreen mobile device may include a virtual keypad (e.g., a form of a template to guide the user, an alpha-numeric virtual key pad, etc.). The user may use the virtual keypad to enter a pass code to access information. This process may be slow and/or cumbersome (e.g., a fingertip of the user may be of comparatively same size as an area of a virtual keypad symbol, the virtual keypad may not have the same tactile feel as the physical keypad, etc.). Use of a virtual keypad may also be inconvenient and/or dangerous when an attention of the user is diverted (e.g., walking, working, eating, etc.). A handicapped user (e.g., a sight-impaired person, a person with out fingers or hands, a person with impaired dexterity, etc.) may have difficulty inputting information with the virtual keypad. Furthermore, the alpha-numeric pass code may be difficult to remember for a primary user and/or secondary users of the mobile device. Thus, security of the mobile device may be breached resulting in theft and/or misappropriation of the confidential information that may be stored in the mobile device.
SUMMARY
A method, system, and/or apparatus of a touch-based authentication of a mobile device through user generated pattern creation are disclosed. In one aspect, a method of a mobile device includes recognizing a tactile force on a touch screen without a visual aid as an unlocking gesture, storing the unlocking gesture to a memory (e.g., may be a local memory of the mobile device that may be internal to the mobile device) of the mobile device, associating another tactile force on the touch screen with the unlocking gesture, and transforming the mobile device from an initial state to an unlocked state based on the association between the another tactile force and the unlocking gesture.
The method may include transforming the mobile device to operate as a telephonic communication device in the unlocked state. The method may also include accessing a contact list and/or a greeting message based on a user profile of the telephonic communication device associated with the unlocking gesture to transform the mobile device to operate as the telephonic communication device. In addition, the method may include accessing a media playlist based on the user profile of the telephonic communication device associated with the unlocking gesture to transform the mobile device to operate as a media player.
The method may include accessing a set of bookmarks based on the user profile of the telephonic communication device associated with the unlocking gesture to enable customized settings on a browser application of the mobile device. The method may also include determining that the tactile force may be placed at multiple distinct locations on the touch screen while recognizing the tactile force as the unlocking gesture. The multiple distinct locations may be simultaneously and/or serially placed.
The method may include designating a region of the touch screen as available to receive the another tactile force, such that the another tactile force may be algorithmically determinable to be the unlocking gesture when recognized in the designated region. The method may also include determining a duration of the another tactile force at a particular location of the touch screen to determine whether it may be the unlocking gesture. In addition, the method may include determining that a total time to create the another tactile force may be within a permitted amount of time when determining whether it is the unlocking gesture.
The method may include operating the mobile device in the initial state such that certain functions may be disabled in the initial state to conserve battery consumption of the mobile device through a power management circuitry of the mobile device. The method may also include determining that a next tactile force is unrelated with the unlocking gesture. In addition, the method may transform the mobile device from the initial state to a locked state based on the determination that the next tactile force that may be unrelated with the unlocking gesture.
The method may include permitting the mobile device to communicate with an emergency service provider even when in the locked state. The method may also include determining that the unlocking gesture may be similar to a stored gesture beyond a tolerance value. The method may request a different gesture to be stored when the determination may be made that the unlocking gesture may be similar beyond the tolerance value. In addition, the method may include determining that the another tactile force may be unique but within an acceptance range of as sociability with the unlocking gesture when associating the another tactile force with the unlocking gesture.
In another aspect, a method of a mobile device includes determining whether a tactile force on a touch screen without any visual aid on the touch screen is associated with a security gesture (e.g., may be a user-generated gesture that may be stored in a memory that is internal to the mobile device), permitting access to a set of applications of the mobile device when an association is made between the tactile force and the security gesture, and denying access to the set of applications of the mobile device when the association fails to be made between the tactile force and the security gesture.
The method may also include directly opening a particular application of the mobile device when the association may be made between the tactile force and the security gesture.
In yet another aspect, a mobile device includes a touchscreen to recognize a tactile force using a processor of the mobile device, a security module interfaced with the processor to associate the tactile force with a security gesture, and to determine access to a set of features on the mobile device based on the association, and a user module of the security module to create security gestures based on a user input.
The methods, systems, and apparatuses disclosed herein may be implemented in any means for achieving various aspects, and may be executed in a form of a machine-readable medium embodying a set of instructions that, when executed by a machine, cause the machine to perform any of the operations disclosed herein. Other features will be apparent from the accompanying drawings and from the detailed description that follows.



BRIEF DESCRIPTION OF THE DRAWINGS
Example embodiments are illustrated by way of example and not limitation in the figures of the accompanying drawings, in which like references indicate similar elements and in which:
FIGS. 1A, 1B, 1C and 1D is a system view of a mobile device recognizing an application of force in a designated region through a tactile force on a touch screen, according to one embodiment.
FIG. 2 is a diagrammatic system view of a data processing system in which any of the embodiments disclosed herein may be performed, according to one embodiment.
FIG. 3 is an exploded view of a security module, according to one embodiment.
FIG. 4 is a table view illustrating various fields such as user, an initial state, security gesture, rules, etc., according to one embodiment.
FIG. 5 is a flow chart of a process of a cell phone touch screen unlocking using a tactile force/gesture, according to one embodiment.
FIG. 6 is a flow chart of a process of a cell phone touch screen unlocking, according to one embodiment.
FIG. 7 is a table view illustrating example rules/reference gestures, accepted, and rejected gestures, according to one embodiment.
FIG. 8A is a process of recognizing a tactile force on a touch screen without a visual aid as an unlocking gesture, according to one embodiment.
FIG. 8B is a continuation of process flow of FIG. 8A, illustrating additional operations, according to one embodiment.
FIG. 8C is a continuation of process flow of FIG. 8B, illustrating additional operations, according to one embodiment.
FIG. 9 is a process flow of an opening a particular application of the mobile device when the association is made between the tactile force and the security gesture, according to one embodiment.



Other features of the present embodiments will be apparent from the accompanying drawings and from the detailed description that follows.
DETAILED DESCRIPTION
A method, system, and apparatus of a touch-based authentication of a mobile device through user generated pattern creation are disclosed. Although the present embodiments have been described with reference to specific example embodiments, it will be evident that various modifications and changes may be made to these embodiments without departing from the broader spirit and scope of the various embodiments.
In one embodiment, a method of a mobile device (e.g., the mobile device 100 of FIG. 1) includes recognizing a tactile force (e.g., the tactile force 106 of FIG. 1) on a touch screen (e.g., the touchscreen 108 of FIG. 1) without a visual aid as an unlocking gesture, storing the unlocking gesture to a memory (e.g., may be a local memory of the mobile device that may be internal to the mobile device) of the mobile device 100, associating another tactile force on the touchscreen 108 with the unlocking gesture, and transforming the mobile device 100 from an initial state to an unlocked state based on the association between the another tactile force and the unlocking gesture.
In another embodiment, a method of a mobile device (e.g., the mobile device 100 of FIG. 1) includes determining whether a tactile force (e.g., the tactile force 106 of FIG. 1) on a touch screen (e.g., the touchscreen 108 of FIG. 1) without any visual aid on the touchscreen 108 is associated with a security gesture (e.g., may be a user-generated gesture that may be stored in a memory that is internal to the mobile device), permitting access to a set of applications of the mobile device 100 when an association is made between the tactile force 106 and the security gesture, and denying access to the set of applications of the mobile device 100 when the association fails to be made between the tactile force 106 and the security gesture.
In yet another embodiment, a mobile device (e.g., the mobile device 100 of FIG. 1) includes a touchscreen (e.g., the touchscreen 108 of FIG. 1) to recognize a tactile forced (e.g., the tactile force 106 of FIG. 1) using a processor (e.g., the processor 202 of FIG. 2) of the mobile device 100, a security module (e.g., the security module 110 of FIG. 2) interfaced with the processor 202 to associate the tactile force 106 with a security gesture, and to determine access to a set of features on the mobile device 100 based on the association, and a user module (e.g., the user module 320 of FIG. 3) of the security module 110 to create security gestures based on a user input.
FIGS. 1A, 1B, 1C and 1D is a system view of a mobile device recognizing an application of force in a designated region through a tactile force on a touchscreen, according to one embodiment. Particularly, FIG. 1 illustrates a mobile device 100, a force applicator 102, a designated region 104, a tactile force 106, a touchscreen 108, and a security module 110, according to one embodiment.
The mobile device 100 may be a device used for communication and/or for processing information (e.g., browsing, forums, mail, chat, etc.) through the network (e.g., internet network). The force applicator 102 (e.g., finger, stylus, etc.) may apply contact forces to the fingertip to enable the force used with or without the secondary fingertip force applicator (e.g., may be stylus, etc.). The designated region 104 may be the region on the touch screen which may receive tactile force. The tactile force 106 may be a force applied physically by the user (e.g., by touching, by using a stylus, etc.). The touchscreen 108 may be an input/output interface which may detect a location of touch within the display area. The security module 110 may provide security to the mobile device 100 based on the tactile force 106 (e.g., the security gesture).
In example embodiment, the mobile device 100 may recognize the force applicator 102 (e.g., may be in the form of touch, etc.) in the designated region 104 of the touchscreen 108. The force may be an unlocking gesture/tactile force 106 that may be used for unlocking the mobile device 100.
FIG. 2 is a diagrammatic system view 200 of a data processing system in which any of the embodiments disclosed herein may be performed, according to one embodiment. Particularly, the diagrammatic system view 200 of FIG. 2 illustrates a security module 110, a processor 202, a main memory 204, a static memory 206, a bus 208, a video display 210, an alpha-numeric input device 212, a cursor control device 214, a drive unit 216, a signal generation device 218, a network interface device 220, a machine readable medium 222, instructions 224, and a network 226, according to one embodiment.
The diagrammatic system view 200 may indicate a personal computer and/or the data processing system in which one or more operations disclosed herein are performed. The security module 110 may provide security to the device from unauthorized access (e.g., may be mishandled, misused, stolen, etc.). The processor 202 may be a microprocessor, a state machine, an application specific integrated circuit, a field programmable gate array, etc. (e.g., Intel® Pentium® processor, 620 MHz ARM 1176, etc.). The main memory 204 may be a dynamic random access memory and/or a primary memory of a computer system.
The static memory 206 may be a hard drive, a flash drive, and/or other memory information associated with the data processing system. The bus 208 may be an interconnection between various circuits and/or structures of the data processing system. The video display 210 may provide graphical representation of information on the data processing system. The alpha-numeric input device 212 may be a keypad, a keyboard, a virtual keypad of a touchscreen and/or any other input device of text (e.g., a special device to aid the physically handicapped).
The cursor control device 214 may be a pointing device such as a mouse. The drive unit 216 may be the hard drive, a storage system, and/or other longer term storage subsystem. The signal generation device 218 may be a bios and/or a functional operating system of the data processing system. The network interface device 220 may be a device that performs interface functions such as code conversion, protocol conversion and/or buffering required for communication to and from the network 226. The machine readable medium 222 may provide instructions on which any of the methods disclosed herein may be performed. The instructions 224 may provide source code and/or data code to the processor 202 to enable any one or more operations disclosed herein.
FIG. 3 is an exploded view of a security module 110, according to one embodiment. Particularly, FIG. 3 illustrates a recognition module 300, a tactile force module 302, an association module 304, a store module 306, a transform module 308, an initial state module 310, an unlock module 312, a deny module 314, a determination module 316, a permit module 318, a user module 320, and a region module 322, according to one embodiment.
The recognition module 300 may enable the mobile device 100 to recognize the application of force (e.g., tactile force 106) as the unlocking gesture. The tactile force module 302 may detect tactile force as an unlocking gesture on the touchscreen 108. The association module 304 may associate another tactile force (e.g., may be different kind of force, etc.) on the touchscreen along with the unlocking gesture (e.g., unlocking command, mechanism, etc.). The store module 306 may enable storing the unlocking gesture to the memory of the mobile device 100. The transform module 308 may transform the mobile device 100 to function as the telephonic communication device when unlocked through recognition and validating unlocking gesture. The initial state module 310 may conserve the battery consumption of the mobile device 100 through a power management circuitry of the mobile device 100 (e.g., by putting the mobile device into s low power state, etc.). The unlock module 312 may unlock the mobile device 100 after recognizing and validating the unlocking gesture.
The deny module 314 may deny access to the set of applications of the mobile device 100 when the association module 304 fails to associate between the tactile force 106 and the security gesture. The determination module 316 may determine the accuracy of the association and may determine the total time to create the another tactile force within the permitted amount of time. The permit module 318 may permit the mobile device 100 to communicate with the emergency service provider in the locked state. The user module 320 may create security gestures based on the user input. The region module 322 may recognize the region of the touchscreen 108 on which the application of the force (e.g., may be the tactile force) has taken place.
In example embodiment, the recognition module 300 may communicate with the association module 304 to recognize the tactile force 106 (e.g., using the tactile force module 302) matching with the security gesture. The association module 304 may communicate with the store module 306, the transform module 308, the deny module 314, the determination module 316, the permit module 318, the user module 320, and the region module 322. The unlock module 312 may communicate with the transform module 308 for changing the state (e.g., locked to unlocked, unlocked to locked, etc.) of the mobile device 100.
In one embodiment, the touchscreen 108 may recognize the tactile force 106 (e.g., using the recognition module 300 of FIG. 3) using the processor 202 of the mobile device 100. The security module 110 interfaced with the processor 202 to associate the tactile force 106 with a security gesture, and may determine access to a set of features on the mobile device 100 based on the association. The user module 320 of the security module 110 may create security gestures based on a user input (e.g., using the user module 320 of FIG. 3). The mobile device 100 may be transformed to operate as a telephonic communication device in the unlocked state.
The contact list and/or a greeting message based on the user profile of the telephonic communication device (e.g., using the user module 320 of FIG. 3) associated with the unlocking gesture may be accessed to transform the mobile device 100 (e.g., using the transform module 308 of FIG. 3) to operate as the telephonic communication device. The media playlist based on the user profile (e.g., using the user module 320 of FIG. 3) of the telephonic communication device associated with the unlocking gesture (e.g., using the unlock module 312 of FIG. 3) may be generated to transform the mobile device 100 to operate as a media player. The region of the touchscreen 108 as available (e.g., using the region module 322 of FIG. 3) may be designated to receive the another tactile force, such that the another tactile force may be algorithmically determinable to be the unlocking gesture when recognized in the designated region (e.g., using the recognition module 300 of FIG. 3).
The duration of the another tactile force may be determined (e.g., using the determination module 316 of FIG. 3) at a particular location of the touchscreen 108 to determine whether it may be the unlocking gesture. The total time may be determined (e.g., using the determination module 316 of FIG. 3) to create the another tactile force may be within a permitted amount of time when determining whether it may be the unlocking gesture. The mobile device 100 in the initial state may be operated such that certain functions may be disabled in the initial state (e.g., using the initial state module 310 of FIG. 3) to conserve battery consumption of the mobile device 100 through a power management circuitry of the mobile device 100.
The memory may be a local memory of the mobile device 100 that may be internal to the mobile device 100. It may be determined that the next tactile force may be unrelated with the unlocking gesture. The mobile device 100 may be transformed (e.g., using the transform module 308 of FIG. 3) from the initial state to a locked state based on the determination that the next tactile force may be unrelated with the unlocking gesture (e.g., using the unlock module 312 of FIG. 3). The mobile device 100 may be permitted (e.g., using the permit module 318 of FIG. 3) to communicate with an emergency service provider even when in the locked state.
It may be determined (e.g., using the determination module 316 of FIG. 3) that the unlocking gesture may be similar to a stored gesture beyond a tolerance value. The different gesture may be requested to be stored (e.g., using the store module 306 of FIG. 3) when the determination may be made that the unlocking gesture may be similar beyond the tolerance value. It may be determined (e.g., using the determination module 316 of FIG. 3) that the another tactile force may be unique but within an acceptance range of associability with the unlocking gesture when associating the another tactile force with the unlocking gesture. The security gesture may be the user-generated gesture that may be stored (e.g., using the store module 306 of FIG. 3) in a memory that may be internal to the mobile device 100.
FIG. 4 is a table view illustrating various fields such as user, security gesture, user profile permissions, rules, etc., according to one embodiment. Particularly, FIG. 4 illustrates a user field 400, a security gesture field 402, an user profile permissions field 404, a rules filed 406, an user profile personalized settings field 408, all access 410, telephonic communication device 412, browser application 422, media playlist 401, five seconds total time 418, customized browser settings 420, bookmarks, simultaneous and serial 424, multiple distinct 426, hold at bottom of gesture one second duration 428, tolerance field 430, unlocked state field 432, media player 434, initial state 436, emergency calls only state 438, and battery conservation mode 440, according with one embodiment.
The user field 400 may illustrate the user (e.g., John, Jane, Jose, etc. as illustrated in FIG. 4) who may have security gestures to unlock the mobile device 100. The security gesture field 402 may illustrate various unlocking gesture associated to the particular users. The user profile permissions field 404 may display various types of the access in the mobile device 100 to the user. The rules field 406 may be a rules set by the user for unlocking procedure. The user profile personalized settings field 408 may illustrate various personalized settings associated with the user in the mobile device 100. The all access 410 may be a permission to access all the applications (e.g., telephone book, message, email, etc.) in the mobile device 100.
The telephonic communication device 412 may be a permission of the user to use the mobile device 100 to use as a telephonic device. The browser application 422 may be a permission to access created by the user to use the mobile device 100 for browsing. The media playlist 401 may be a personalized setting of the user for playlist. The five seconds total time 418 may be a rule created by the user for locking the mobile device 100 when idle. The customized browser settings 420 may be personalized setting for the browser in the mobile device 100. The bookmarks may be a setting of the user in the mobile device 100 to manage bookmarks.
The simultaneous and serial 424 may be a rule that may be created by the user for input of tactile gestures simultaneously and/or serially in order to unlock the mobile device 100. The multiple distinct 426 may be may be a rule that may enable the user to see distinct multiple communication data (e.g., missed calls, messages, received calls, etc.) simultaneously. The hold at bottom of gesture one second duration 428 may be a rule created by the user for unlocking the mobile device 100. The tolerance field 430 may illustrate capability of the mobile device 100 to recognize slight variations in the security gesture.
The unlocked state field 432 may be a state in the mobile device 100 that may enable the user to use applications that may be customized by the user itself. The media player 434 may be an application that may enable the user to play the media data (e.g., video, audio, etc.) in the mobile device 100. The initial state 436 may be the state that the mobile device would be before unlocking (e.g., power saving mode, etc.). The emergency calls only state 438 may be a state in which the mobile device 100 can only make emergency calls. The battery conservation mode 440 may be the state in which the mobile device 100 may not be used by the user and power consumption in the mobile device 100 may be reduced by internal logic (e.g., by shutting down light, display, etc.).
In example embodiment, FIG. 4 illustrates users and their settings (e.g., may be personalized settings, rules, etc.) in the in the mobile devices 100. The user field 400 may illustrate John, John, Jane, Jose, Raj, and Ray. The security gesture field 402 may illustrate various gestures (e.g., 106, 104 as illustrated in FIG. 4) associated with the particular users. The user profile permissions field 404 may illustrate permissions assigned like, all access 410 associated to the user John, John, telephonic communication device 412 associated to the user Jane, browser application 422 associated to the user Jose, emergency calls associated with the user Ray.
The rules field 406 may illustrate five seconds total time 418 associated to the user John, designated region on touchscreen 108 rule associated to the user John, simultaneous and serial 424 rules associated to the user Jane and Jose, multiple distinct 426 rules associated to the user Jose, the hold at bottom of gesture one second duration 428 rules associated to the user Raj, correct unlocking gesture associated with the user Ray. The user profile personalized settings field 408 may illustrate the contact list 414, and greeting message 416 associated to the user John, contact list 414 and greeting message associated to the user Jane, media playlist 401, bookmarks, customized browser settings 420 associated to the user Jose, no setting associated to the user Raj, bookmarks associated to the user John, no setting associated to the user Ray.
The tolerance field 430 may illustrate possible variations and tolerance associated with security gesture field 402. The unlocked state field 432 may illustrate running applications like, telephonic communication device 412 associated to the user John and Jane, media player 434 application associated to the user Jose and Raj, browser application 422 associated to the user John. Emergency calls only 438 application associated to the user Ray. The initial state 436 may illustrate the battery conservation mode 440 associated with the user John, Jane, and Raj, certain functions disabled associated with the users Jose, John and Ray, according to one embodiment.
FIG. 5 is a flow chart of a process of a cell phone touch screen unlocking using a tactile force/gesture, according to one embodiment. In operation 502, the touchscreen 108 with no visual aid may be provided. In operation 504, the tactile force 106 may be recognized. In operation 506, another or next tactile force may be associated (e.g., using the association module 304 of FIG. 3) with unlocking gesture. In operation 508, a condition may be determined (e.g., using the determination module 316 of FIG. 3) that another or next tactile force may be unique but within an acceptance range of associability with the unlocking gesture when associating the another or next tactile force with the unlocking gesture. If operation 508 outcome is true then operation 512 may be performed, else operation 510 may be performed.
In operation 510, the next tactile force may be allowed. In operation 512, the mobile device 100 from initial state to an unlocked state based on the association between the another tactile force and the unlocking gesture may be transformed (e.g., using the transform module 308 of FIG. 3). In operation 514, the tactile force may be recognized as an unlocking gesture. In operation 516, a condition may be determined (e.g., using the determination module 316 of FIG. 3) that the unlocking gesture may be similar to the stored gesture beyond tolerable value and/or requesting different gesture to be stored when determination may be made that the unlocking gesture may be similarly beyond the tolerance value.
If operation 516 outcome is true then operation 514 may be performed, else operation 518 may be performed. In operation 518, the unlocking gesture may be stored (e.g., using the store module 306 of FIG. 3) to the memory of the mobile device 100. In operation 520, the mobile device 100 may be transformed (e.g., using the transform module 308 of FIG. 3) from the initial state to locked state based on determination that the next tactile force may be unrelated with the unlocking gesture. In operation 522, the emergency calls may be allowed in the locked state.
In one embodiment, the tactile force 106 may be recognized on the touch screen (e.g., the touchscreen 108 of FIG. 1) without a visual aid as an unlocking gesture. The unlocking gesture may be stored (e.g., using the store module 306 of FIG. 3) to a memory of the mobile device 100. Another tactile force on the touchscreen 108 (e.g., using the association module 304 of FIG. 3) may be associated with the unlocking gesture. The mobile device 100 may be transformed (e.g., using the transform module 308 of FIG. 3) from an initial state to an unlocked state based on the association between the another tactile force and the unlocking gesture.
The set of bookmarks may be generated based on the user profile of the telephonic communication device associated with the unlocking gesture (e.g., using the unlock module 312 of FIG. 3) to enable customized settings on a browser application of the mobile device 100. The tactile force 106 may be placed at multiple distinct locations on the touchscreen 108 and may be determined (e.g., using the determination module 316 of FIG. 3) while recognizing the tactile force 106 as the unlocking gesture.
FIG. 6 is a flow chart of a process of a cell phone touch screen unlocking, according to one embodiment. In operation 502, the touchscreen 108 may be provided with no visual aid. In operation 504, the tactile gesture may be recognized. In operation 602, a condition may be determined whether the tactile force 106 on the touchscreen 108 without a visual aid on the touchscreen 108 may be associated with a security gesture. If the outcome of operation 602 is true then operation 604 may be performed, else operation 606 may be performed. In operation 604, access to a set of applications of the mobile device 100 may be permitted when an association may be made between the tactile force 106 and the security gesture. In operation 606, access to the set of applications of the mobile device 100 may be defined when the association fails to be made between the tactile force 106 and the security gesture.
In one embodiment, the tactile force 106 may be determined (e.g., using the determination module 316 of FIG. 3) on the touchscreen 108 without any visual aid on the touchscreen 108 may be associated with a security gesture. The access may be permitted (e.g., using the permit module 318 of FIG. 3) to a set of applications of the mobile device 100 when an association may be made between the tactile force 106 and the security gesture. The access may be denied (e.g., using the deny module 314 of FIG. 3) to the set of applications of the mobile device 100 when the association fails to be made between the tactile force 106 and the security gesture.
FIG. 7 is a table view illustrating example rules/reference gestures, accepted gestures, and rejected gestures, according to one embodiment. Particularly, FIG. 7 illustrates a rule/reference gesture 702, accepted gestures 704, and rejected gestures 706, according to one embodiment.
The rule/reference gesture 702 may be various rules/references that may enable the user to unlock the mobile device 100 through use of tactile force/security gestures. The accepted gestures 704 may be the gestures that may be accepted after determining the match between another tactile force and unlocking gesture may be under matching conditions (e.g., may be approximately). The rejected gestures 706 may be the gestures that may be rejected after determining the match between another tactile force and the unlocking gesture may not be within the matching conditions.
In example embodiment of FIG. 7 the rule/reference gesture 702 column may illustrate that the “unlocking gesture must be located completely within the designated region” in first row, “another tactile force must match shape of unlocking gesture, but not size or position within designated area 104” in second row, “another tactile force must match shape but not size of unlocking gesture, but not size or position within designated area 104” in third row, “another tactile must satisfy a threshold parameter (e.g., may be curves, bends, etc. as illustrated in FIG. 7) in fourth row, “another tactile force must be completed within one second” in fifth row, and “another tactile force must be in the proper sequence” in the sixth row. The accepted gestures 704 column may illustrate possible gestures (e.g., may be approximately similar, or similar itself) that may be accepted which are associated to the rule/reference gesture 702. The rejected gestures 706 may be the gestures (e.g., may vary drastically compared to rule/reference gesture) that may be rejected with reference to the rule/reference gesture 702.
FIG. 8A is a process of recognizing a tactile force (e.g., the tactile force 106 of FIG. 1) on the touchscreen 108 without a visual aid as an unlocking gesture, according to one embodiment. In operation 802, the tactile force 106 may be recognized (e.g., using the recognition module 300 of FIG. 3) on a touch screen (e.g., the touchscreen 108 of FIG. 1) without a visual aid as an unlocking gesture. In operation 804, the unlocking gesture may be stored (e.g., using the store module 306 of FIG. 3) to a memory (e.g., memory card, etc.) of the mobile device 100.
In operation 806, another tactile force on the touchscreen 108 may be associated (e.g., using the association module 304 of FIG. 3) with the unlocking gesture. In operation 808, the mobile device 100 may be transformed (e.g., using the transform module 308 of FIG. 3) from an initial state to an unlocked state based on the association between the another tactile force and the unlocking gesture. In operation 810, the mobile device 100 may be transformed (e.g., using the transform module 308 of FIG. 3) to operate as a telephonic communication device in the unlocked state (e.g., using the unlock module 312 of FIG. 3). In operation 812, a contact list and a greeting message based on a user profile of the telephonic communication device associated (e.g., using the association module 304 of FIG. 3) with the unlocking gesture may be generated (e.g., may be because of user settings, etc.) to transform the mobile device 100 (e.g., using the transform module 308 of FIG. 3) to operate as the telephonic communication device.
In operation 814, a media playlist based on the user profile of the telephonic communication device (e.g., using the user module 320 of FIG. 3) associated with the unlocking gesture may be generated (e.g., may be using the user settings, etc.) to transform the mobile device 100 to operate as a media player.
FIG. 8B is a continuation of process flow of FIG. 8A, illustrating additional operations, according to one embodiment. In operation 816, a set of bookmarks based on the user profile of the telephonic communication device associated (e.g., using the association module 304 of FIG. 3) with the unlocking gesture may be generated (e.g., using the unlock module 312 of FIG. 3) to enable customized settings on a browser application of the mobile device 100. In operation 818, the tactile force 106 may be placed at multiple distinct locations on the touchscreen 108 and may be determined (e.g., using the transform module 308 of FIG. 3) while recognizing the tactile force 106 (e.g., using the recognition module 300 of FIG. 3) as the unlocking gesture.
In operation 820, a region of the touchscreen 108 as available (e.g., using the region module 322 of FIG. 3) may be designated to receive the another tactile force, such that the another tactile force may be algorithmically determinable to be the unlocking gesture when recognized (e.g., using the recognition module 300 of FIG. 3) in the designated region 104. In operation 822, a duration (e.g., five seconds, one second as assigned in rules, etc.) of the another tactile force may be determined (e.g., using the determination module 316 of FIG. 3) at a particular location of the touchscreen 108 to determine whether it may be the unlocking gesture. In operation 824, a total time may be determined (e.g., using the determination module 316 of FIG. 3) to create the another tactile force and may be within a permitted amount of time when determining whether it may be the unlocking gesture.
In operation 826, the mobile device 100 in the initial state may be operated such that certain functions may be disabled in the initial state to conserve battery consumption of the mobile device 100 (e.g. using the initial state module 310 of FIG. 3) through a power management circuitry of the mobile device 100. The memory may be a local memory of the mobile device 100 that may be internal to the mobile device 100. In operation 828, it may be determined (e.g., using the determination module 316 of FIG. 3) that a next tactile force may be unrelated with the unlocking gesture.
FIG. 8C is a continuation of process flow of FIG. 8B, illustrating additional operations, according to one embodiment. In operation 830, the mobile device 100 may be transformed from the initial state to a locked state (e.g., using the transform module 308 of FIG. 3) based on the determination that the next tactile force may be unrelated with the unlocking gesture. In operation 832, the mobile device 100 may be permitted to communicate with an emergency service provider (e.g., using the permit module 318 of FIG. 3) even when in the locked state. In operation 834, it may be determined (e.g., using the determination module 316 of FIG. 3) that the unlocking gesture may be similar to a stored gesture beyond a tolerance value.
In operation 836, a different gesture may be requested to be stored (e.g., using the store module 306 of FIG. 3) when the determination may be made that the unlocking gesture may be similar beyond the tolerance value. In operation 838, it may be determined (e.g., using the determination module 316 of FIG. 3) that the another tactile force may be unique but within an acceptance range of as sociability with the unlocking gesture when associating the another tactile force with the unlocking gesture (e.g., using the unlock module 312 of FIG. 3).
FIG. 9 is a process flow of an opening a particular application of the mobile device 100 when the association is made between the tactile force 106 and the security gesture, according to one embodiment. In operation 902, a tactile force (e.g., the tactile force 106 of FIG. 1) may be determined (e.g., using the determination module 316 of FIG. 3) on a touch screen (e.g., the touchscreen 108 of FIG. 1) without any visual aid on the touchscreen 108 and may be associated with a security gesture. In operation 904, access may be permitted (e.g., using the permit module 318 of FIG. 3) to a set of applications of the mobile device 100 when an association may be made between the tactile force 106 and the security gesture. In operation 906, access may be denied (e.g., using the deny module 314 of FIG. 3) to the set of applications of the mobile device 100 when the association fails to be made between the tactile force 106 and the security gesture. In operation 908, a particular application of the mobile device 100 may be directly opened when the association is made between the tactile force 106 and the security gesture.
Although the present embodiments have been described with reference to specific example embodiments, it will be evident that various modifications and changes may be made to these embodiments without departing from the broader spirit and scope of the various embodiments. For example, the various devices, modules, analyzers, generators, etc. described herein may be enabled and operated using hardware circuitry (e.g., CMOS based logic circuitry), firmware, software and/or any combination of hardware, firmware, and/or software (e.g., embodied in a machine readable medium). For example, the various electrical structure and methods may be embodied using transistors, logic gates, and electrical circuits (e.g., application specific integrated (ASIC) circuitry and/or in Digital Signal Processor (DSP) circuitry).
Particularly, the security module 110, the recognition module 300, the tactile force module 302, the association module 304, the store module 306, the transform module 308, the initial state module 310, the unlock module 312, the deny module 314, the determination module 316, the permit module 318, the user module 320, and the region module 322, and other modules of FIGS. 1-9 may be enabled using software and/or using transistors, logic gates, and electrical circuits (e.g., application specific integrated ASIC circuitry) such as a security circuit, a recognition circuit, a tactile force circuit, an association circuit, a store circuit, a transform circuit, an initial state circuit, an unlock circuit, a deny circuit, a determination circuit, a permit circuit, an user circuit, a region circuit, and other circuits.
In addition, it will be appreciated that the various operations, processes, and methods disclosed herein may be embodied in a machine-readable medium and/or a machine accessible medium compatible with a data processing system (e.g., a computer system), and may be performed in any order (e.g., including using means for achieving the various operations). Accordingly, the specification and drawings are to be regarded in an illustrative rather than a restrictive sense.

## Claims

1. A method of a mobile device comprising:
entering an applied tactile force comprising touches on a touch screen of the mobile device, wherein the applied tactile force has a shape;
determining whether the shape of the applied tactile force matches within a tolerance the shape of a user-defined gesture, wherein determining does not comprise detecting whether the touches are on predetermined contact areas on the touch screen in a given order; and
transforming the mobile device from a first state to a second state if the shape of the applied tactile force matches within a tolerance the shape of the user-defined gesture.

2. The method of claim 1 wherein the touch screen does not display an unlock image with respect to which the applied tactile force is to be performed.

3. The method of claim 1 wherein the user-defined gesture is selected from a set of template gestures by a user of the mobile device.

4. The method of claim 1 wherein matches within a tolerance the shape of the user-defined gesture comprises having a shape that is similar to the user-defined gesture within a tolerance value.

5. The method of claim 1 wherein determining does not comprise both matching the size of the user-defined gesture with the size of the applied tactile force and matching the position of the user-defined gesture with the position of the applied tactile force.

6. The method of claim 1 wherein the first state is one of: a battery conservation mode, a state with certain functions disabled, a locked state, an unlocked state, an emergency service state, and an initial state.

7. The method of claim 1 wherein the second state is one of: an unlocked state, a telephonic communications device, access to a browser application, a media player, allowing emergency calls, access to a set of applications, opening a particular application, access to a contact list, access to a greeting message, access to a media playlist, access to bookmarks, and a locked state.

8. The method of claim 1 further comprising: maintaining the mobile device in the first state if the shape of the applied tactile force does not match within a tolerance the shape of the user-defined gesture.

9. The method of claim 1 further comprising: transitioning the mobile device to a third state if the shape of the applied tactile force does not match within a tolerance the shape of the user-defined gesture.

10. A non-transitory computer-readable storage medium with an executable program stored thereon, wherein the executable program instructs a processor to perform the method:
accepting an applied tactile force comprising touches on a touch screen of the mobile device, wherein the applied tactile force has a shape;
determining whether the shape of the applied tactile force matches within a tolerance the shape of a user-defined gesture, wherein determining does not comprise detecting whether the touches are on predetermined contact areas on the touch screen in a given order; and
transforming the mobile device from a first state to a second state if the shape of the applied tactile force matches within a tolerance the shape of the user-defined gesture.

11. The method of claim 10 wherein the touch screen does not display an unlock image with respect to which the applied tactile force is to be performed.

12. The method of claim 10 wherein the user-defined gesture is selected from a set of template gestures by a user of the mobile device.

13. The method of claim 10 wherein matches within a tolerance the shape of the user-defined gesture comprises having a shape that is similar to the user-defined gesture within a tolerance value.

14. The method of claim 10 wherein determining does not comprise both matching the size of the user-defined gesture with the size of the applied tactile force and matching the position of the user-defined gesture with the position of the applied tactile force.

15. The method of claim 10 wherein the first state is one of: a battery conservation mode, a state with certain functions disabled, a locked state, an unlocked state, an emergency service state, and an initial state.

16. The method of claim 10 wherein the second state is one of: an unlocked state, a telephonic communications device, access to a browser application, a media player, allowing emergency calls, access to a set of applications, opening a particular application, access to a contact list, access to a greeting message, access to a media playlist, access to bookmarks, and a locked state.

17. The method of claim 10 further comprising: maintaining the mobile device in the first state if the shape of the applied tactile force does not match within a tolerance the shape of the user-defined gesture.

18. The method of claim 10 further comprising: transitioning the mobile device to a third state if the shape of the applied tactile force does not match within a tolerance the shape of the user-defined gesture.

19. A mobile device, comprising:
a touch screen;
a processor that recognizes an applied tactile force comprising touches on the touch screen, wherein the applied tactile force has a shape;
a security module interfaced with the processor, wherein the security module makes a determination of whether the shape of the applied tactile force matches within a tolerance the shape of a user-defined gesture and allows access to a set of features on the mobile device if the shape of the applied tactile force matches within a tolerance the shape of the user-defined gesture, wherein the determination does not comprise detecting whether the touches are on predetermined contact areas on the touch screen in a given order.

20. The mobile device of claim 19 wherein the determination does not comprise both matching the size of the user-defined gesture with the size of the applied tactile force and matching the position of the user-defined gesture with the position of the applied tactile force.