Method and apparatus for detecting a gesture

Information

  • Patent Grant
  • 9207860
  • Patent Number
    9,207,860
  • Date Filed
    Friday, May 25, 2012
    12 years ago
  • Date Issued
    Tuesday, December 8, 2015
    8 years ago
Abstract
A method includes detecting a swipe gesture from an initial touch location on a touch-sensitive display of an electronic device; determining touch attributes for the swipe gesture; and performing a lock function if the touch attributes correspond to a stored swipe gesture associated with the lock function. Further lock functions may be activated by detection of attributes of a further stored swipe gesture.
Description
FIELD OF THE TECHNOLOGY

The present disclosure relates to electronic devices, including but not limited to, portable electronic devices having touch-sensitive displays and their control.


BACKGROUND

Electronic devices, including portable electronic devices, have gained widespread use and may provide a variety of functions including, for example, telephonic, electronic messaging and other personal information manager (PIM) application functions. Portable electronic devices include, for example, several types of mobile stations such as simple cellular telephones, smart phones, wireless personal digital assistants (PDAs), and laptop computers with wireless 802.111 or Bluetooth capabilities.


Portable electronic devices such as PDAs or smart telephones are generally intended for handheld use and ease of portability. Smaller devices are generally desirable for portability. A touch-sensitive display, also known as a touchscreen display, is particularly useful on handheld devices, which are small and have limited space for user input and output. The information displayed on the touch-sensitive displays may be modified based on the functions and operations being performed.





BRIEF DESCRIPTION OF DRAWINGS


FIG. 1 is a block diagram of a portable electronic device in accordance with the disclosure.



FIG. 2 is a front view of an example of a smartphone in accordance with the disclosure.



FIG. 3 is a front view of an example of a tablet computer in accordance with the disclosure.



FIG. 4 illustrates an example of touch attributes of a swipe gesture in accordance with the disclosure.



FIG. 5 illustrates a further example of touch attributes of a swipe gesture in accordance with the disclosure.



FIG. 6 illustrates a further example of touch attributes of a swipe gesture in accordance with the disclosure.



FIG. 7 is a flowchart illustrating a method of the disclosure.





DETAILED DESCRIPTION

The following describes an apparatus for and method of locking a device based on input received from a touch-sensitive display.


For simplicity and clarity of illustration, reference numerals may be repeated among the figures to indicate corresponding or analogous elements. Numerous details are set forth to provide an understanding of the examples described herein. The examples may be practiced without these details. In other instances, well-known methods, procedures, and components are not described in detail to avoid obscuring the examples described. The description is not to be considered as limited to the scope of the examples described herein.


The disclosure generally relates to an electronic device, such as a portable electronic device or non-portable electronic device. Examples of portable electronic devices include mobile, or handheld, wireless communication devices such as pagers, cellular phones, cellular smart-phones, wireless organizers, personal digital assistants, wirelessly enabled notebook computers, tablet computers, mobile internet devices, electronic navigation devices, and so forth. The portable electronic device may be a portable electronic device without wireless communication capabilities, such as handheld electronic games, digital photograph albums, digital cameras, media players, e-book readers, and so forth. Examples of non-portable electronic devices include desktop computers, electronic white boards, smart boards utilized for collaboration, built-in monitors or displays in furniture or appliances, monitors, displays, televisions and so forth.


A block diagram of an example of an electronic device 100 is shown in FIG. 1. The electronic device 100 includes multiple components, such as a processor 102 that controls the overall operation of the electronic device 100. Communication functions, including data and voice communications, are performed through a communication subsystem 104. Data received by the electronic device 100 may be decompressed and decrypted by a decoder 106. The communication subsystem 104 receives messages from and sends messages to a wireless network 150. The wireless network 150 may comprise any type of wireless network, including, but not limited to, data wireless networks, voice wireless networks, and networks that support both voice and data communications. A power source 142, such as one or more rechargeable batteries or a port to an external power supply, powers the electronic device 100.


The processor 102 interacts with other components, such as a Random Access Memory (RAM) 108, memory 110, a touch-sensitive display 118, one or more actuators 120, one or more force sensors 122, an auxiliary input/output (I/O) subsystem 124, a data port 126, a speaker 128, a microphone 130, short-range communications 132 and other device subsystems 134. The touch-sensitive display 118 includes a display 112 and touch sensors 114 that are coupled to at least one controller 116 that is utilized to interact with the processor 102. Input via a graphical user interface is provided via the touch-sensitive display 118. Information, such as text, characters, symbols, images, icons, and other items that may be displayed or rendered on an electronic device, is displayed on the touch-sensitive display 118 via the processor 102. The processor 102 may also interact with an accelerometer 136 that may be utilized to detect direction of gravitational forces or gravity-induced reaction forces.


To identify a subscriber for network access, the electronic device 100 may utilize a Subscriber Identity Module, a Removable User Identity Module (SIM/RUIM) card 138, or alternatively a Universal Integrated Circuit Card (UICC) or an embedded Universal Integrated Circuit Card (eUICC), for communication with a network, such as the wireless network 150. Alternatively, user identification information may be programmed into memory 110.


The electronic device 100 includes an operating system 146 and software programs, applications, or components 148 that are executed by the processor 102 and are typically stored in a persistent, updatable store such as the memory 110. Additional applications or programs may be loaded onto the electronic device 100 through the wireless network 150, the auxiliary I/O subsystem 124, the data port 126, the short-range communications subsystem 132, or any other suitable subsystem 134. Short-range communications subsystem 132 may include any or all of Bluetooth®, Radio-frequency identification (RFID) & near field communications (NFC) technologies. The electronic device may, therefore, in at least some example embodiments, include a near field communications (NFC) subsystem. The NFC subsystem is configured to communicate with other electronic devices and/or tags, using an NFC communications protocol. NFC is a set of short-range wireless technologies which typically require a distance of 4 cm or less for communications. The NFC subsystem may include an NFC chip and an NFC antenna. In at least some example embodiments, the short-range communication subsystem may be a wireless bus protocol compliant communication mechanism such as a Bluetooth® communication module or a Wi-Fi module to provide for communication with similarly-enabled systems and devices. Any one, any combination, or all of these wireless communications technologies may be included in communications sub-system 104, or short-range communications subsystem 132.


A received signal such as a text message, an e-mail message, or web page download is processed by the communication subsystem 104 and input to the processor 102. The processor 102 processes the received signal for output to the display 112 and/or to the auxiliary I/O subsystem 124. A subscriber may generate data items, for example e-mail messages, which may be transmitted over the wireless network 150 through the communication subsystem 104. For voice communications, the overall operation of the electronic device 100 is similar. The speaker 128 outputs audible information converted from electrical signals, and the microphone 130 converts audible information into electrical signals for processing.


The touch-sensitive display 118 may comprise any suitable touch-sensitive display, such as a capacitive, resistive, infrared, surface acoustic wave (SAW) touch-sensitive display, strain gauge, optical imaging, dispersive signal technology, acoustic pulse recognition, and so forth. A capacitive touch-sensitive display includes one or more capacitive touch sensors 114. The capacitive touch sensors may comprise any suitable material, such as indium tin oxide (ITO).


One or more touches, also known as touch contacts or touch events, may be detected by the touch-sensitive display 118. The processor 102 may determine attributes of the touch, including a location of the touch. Touch location data may include data for an area of contact or data for a single point of contact, such as a point at or near a center of the area of contact. The location of a detected touch may include x and y components, e.g., horizontal and vertical components, respectively, with respect to one's view of the touch-sensitive display 118. For example, the x location component may be determined by a signal generated from one touch sensor, and the y location component may be determined by a signal generated from another touch sensor. A touch may be detected from any suitable input member, such as a finger, thumb, appendage, or other objects, for example, a stylus (active or passive), pen, or other pointer, based on the nature of the touch-sensitive display 118. Multiple simultaneous touches may be detected.


One or more gestures may also be detected by the touch-sensitive display 118. A gesture, such as a swipe, also known as a flick, is a particular type of touch on a touch-sensitive display 118 and may begin at an origin point and continue to an end point, for example, a concluding end of the gesture. A gesture may be identified by attributes of the gesture, including the origin point, the end point, the distance travelled, the duration, the velocity, and the direction, for example. A gesture may be long or short in distance and/or duration. Two points of the gesture may be utilized to determine a direction of the gesture. A gesture may also include a hover. A hover may be a touch at a location that is generally unchanged over a period of time or is associated with the same selection item for a period of time.


The optional actuator(s) 120 may be depressed or activated by applying sufficient force to the touch-sensitive display 118 to overcome the actuation force of the actuator 120. The actuator(s) 120 may be actuated by pressing anywhere on the touch-sensitive display 118. The actuator(s) 120 may provide input to the processor 102 when actuated. Actuation of the actuator(s) 120 may result in provision of tactile feedback.


Optional force sensors 122 may be disposed in conjunction with the touch-sensitive display 118 to determine or react to forces applied to the touch-sensitive display 118. The force sensor 122 may be disposed in line with a piezo actuator 120. The force sensors 122 may be force-sensitive resistors, strain gauges, piezoelectric or piezoresistive devices, pressure sensors, quantum tunneling composites, force-sensitive switches, or other suitable devices.


The touch-sensitive display 118 includes a display area in which information may be displayed, and a non-display area extending around the periphery of the display area. The display area generally corresponds to the area of the display 112. Information is not displayed in the non-display area by the display, which non-display area is utilized to accommodate, for example, electronic traces or electrical connections, adhesives or other sealants, and/or protective coatings around the edges of the display area. The non-display area may be referred to as an inactive area and is not part of the physical housing or frame of the electronic device. Typically, no pixels of the display are in the non-display area, thus no image can be displayed by the display 112 in the non-display area. Optionally, a secondary display, not part of the primary display 112, may be disposed under the non-display area. Touch sensors may be disposed in the non-display area, which touch sensors may be extended from the touch sensors in the display area or distinct or separate touch sensors from the touch sensors in the display area. A touch, including a gesture, may be associated with the display area, the non-display area, or both areas. The touch sensors may extend across substantially the entire non-display area or may be disposed in only part of the non-display area.


A front view of an example electronic device 100 that is a portable electronic device 201 is illustrated in FIG. 2. A front view of an example electronic device 100 that is a tablet computer 301 is illustrated in FIG. 3.


Touch sensors 114 detect touch input, thus providing the device 100 with an interface to identify gestures based on detected touch locations, series of consecutive touch locations and swipe gestures having certain attributes as described above. The resolution of the touch sensors 114 in electronic devices 100 may be an imprecise indication of the actual location of the touch. The touch location has an associated amount of uncertainty, for example approximately 1 mm to approximately 9 mm based on the spacing of touch sensors 114 and other factors.



FIG. 4 shows a device 100 to which a gesture is applied by a user 400. An example of a method according to the invention will now be described in relation to FIGS. 4 to 6. FIG. 4 shows a user 400 applying a swipe gesture from an initial touch location. In the illustrated case, the initial touch location is at a perimeter of the touch sensitive display 118. Touch sensitive display 118 may comprise a display 112 and the touch sensitive area 118 may further extend outside of the display 112. Further, the touch sensitive area may be provided on a separate part of device 100 adjacent the display 112. For the purposes of this disclosure, a touch sensitive display 118 includes any touch sensitive area substantially adjacent display 112. On detection of a gesture beginning at an initial touch location, device 100 determines touch attributes of the gesture. These touch attributes can include the initial touch location, along with any other touch attributes discussed above. In the illustrated example, device 100 compares touch attributes of the detected gesture with touch attributes of a stored gesture. The stored gesture may be associated with a lock function of the device 100. The stored touch attributes may include an initial touch location on the touch sensitive display 118. The stored initial touch location may be defined at any point on touch sensitive display 118 of device 100. In one embodiment, the stored initial touch location may be defined as a touch location at, or adjacent to, a perimeter of the touch sensitive display, as illustrated in FIG. 4. The touch attributes for the stored gesture may include a second touch location. The second touch location may be defined as a point at a predefined distance from the initial touch location. The predefined distance may be a distance along a certain predefined axis of the display, or may be a predefined distance having a predefined magnitude in any direction on the display. Further, as in the example of FIG. 4, the gesture may begin at the initial touch location of the gesture made by the user 400 and progress away from the initial touch location, for example, in a direction of arrow 410. A threshold value of any other suitable touch attribute may alternatively or additionally be used to define the stored gesture. Although in the example described, the swipe gesture is illustrated as having a generally upward direction beginning at an example initial location at or adjacent to the lower perimeter of the device, other directions and other initial locations may be used.



FIG. 5 illustrates an example where the gesture includes a swipe from the touch location of FIG. 4 to that illustrated by touch location 450 and/or touch area 460. Touch attributes of the gesture may therefore be the initial location shown in FIG. 4 and the further touch location 450 illustrated in FIG. 5.



FIG. 5 shows a touch location 450 and a corresponding touch area 460. A touch area 460 may compensate for inherent imprecision of determination of a touch location 450.


The touch area 460 may be derived from touch data received from the touch sensors 114 for a detected touch. A touch area 460 may alternatively be a virtual area around the touch location 450, such as the touch area 460.


The size of the virtual touch area 460 may be based on known characteristics, e.g., uncertainties and inaccuracies, of the touch sensors 114. For example, when the resolution for a touch location 450 is 6 mm, the device 100 may generate a 6 mm radius virtual touch area 460 around a touch location to compensate.


Although a circle is utilized for the touch area 460 in the examples herein, other shapes may be utilized. For example, a custom shape that more accurately represents the contact shape of a finger or stylus touching a touch-sensitive display may be utilized. Other input data may determine the shape or size of the touch area 460. For example, the shape of the touch area 460 may be angled based on orientation information received from the accelerometer 136 because the orientation of the device 100 may affect the angle of contact with the touch-sensitive display 118.


For example, in FIG. 4, a touch location 450 is detected and an associated circular touch area 460 is generated. When the touch location 450 changes to another location, information may be provided as to the angle of the touch input. Adjusting for the angle may reduce uncertainty of touch location perpendicular to direction of change of location of the touch. The touch area may optionally be updated to reflect the direction of change.


An attribute of the stored gesture may be a threshold value T1. In the illustrated example, T1 is defined as a threshold value in the direction of a Y-axis of display 100 and the threshold is therefore illustrated as a straight line 420 across the touch sensitive display 118 of device 100. Therefore, if the gesture includes a second touch location beyond threshold T1, then a process in the device may compare these touch attributes and decide that the touch attributes correspond to a stored swipe gesture. This swipe gesture may be associated with a lock function of the device 100. Therefore, a swipe gesture from an initial touch location illustrated in FIG. 4, to a further touch location, beyond a threshold value T1 from the initial touch location, can activate a lock function of the device 100.


It may be desirable to allow a user to activate a plurality of different lock functions of device 100, depending upon touch attributes relating to a distance between an initial touch location of the gesture and a further touch location of the gesture. In this way, device 100 may select one of a plurality of lock functions depending upon the distance of a touch location of the gesture from the initial touch location of the gesture. In this way, device 100 may activate a first lock function after the gesture passes threshold T1. However, the user may continue the gesture beyond threshold T1 in the direction of arrow 430 and a further lock function may be activated when a touch location of the gesture exceeds a second threshold, such as T2 shown in FIG. 6.



FIG. 6 illustrates further threshold T2, which may be a further distance from the initial touch location illustrated in FIG. 4. Here, the threshold T2 is illustrated by a straight line 440 across touch sensitive display 118. Threshold T2 may however be defined as a magnitude of a distance between an initial touch location and a further touch location of the gesture, by a total distance along a path followed by the gesture or by a threshold value of any other suitable touch attribute. In general, the further threshold T2 may be any touch attribute having a magnitude greater than threshold T1. Upon detecting that a touch attribute has exceeded threshold T2, the device may activate a second lock function, different from the first lock function activated after threshold T1 is passed.


Device 100 may activate the relevant lock function only when a release of the gesture is detected beyond threshold T1 or T2. In this way, if a user continues the gesture in a reverse direction such that the threshold T1 is no longer exceeded before releasing the gesture, then the device may not activate the lock function associated with threshold T1. The same may apply to the threshold T2.


Upon passing either of thresholds T1 or T2, the device may further set display 112 to display a lock function indicator 470. Lock function indicator 470 may further define a lock function touch area. Detection of a touch at the lock function touch area, defined in relation to lock function indicator 470, may activate a further lock function of the device 100. The lock function indicator 470 may only be displayed for a predetermined period and then be removed from the display, along with the lock function touch area. The lock function indicator may change appearance, or disappear, on detection of a touch at the lock function indicator.


A further threshold T3 may be defined. T3 may be defined as a touch location at a perimeter substantially opposite the perimeter at which an initial touch location is defined. Therefore, a gesture beginning at a first perimeter of the display 112 and ending at a second, optionally opposite, perimeter of the display 112 or 118 may cause the device 100 to initiate a locking function of the device. Further thresholds Tn may be implemented to define further lock functions of the device at further thresholds Tn of touch attributes of the device. As such, any number of thresholds Tn may be defined as corresponding to any number of different locking functions of device 100.


Further visual indications of the device having detected the gesture as having touch attributes associated with a lock function may be implemented to give an indication to the user that a lock function may be activated upon release of the gesture. One example can be described in relation to the areas each side of line 420 in FIG. 5, or line 440 in FIG. 6. The device 100 may adjust the display 112 as the progression of the touch location 450 of the gesture is updated. The display may be updated to adjust display parameters of the part of the display between the initial touch location and the current touch location, so that the appearance of the area between the initial touch location and the current touch location is different to the area beyond the current touch location. As an example, the screen may be darkened in the area between the initial touch location and the current touch location, so that as the gesture progresses along display 112 in a y-direction, the display is progressively darkened. This can provide a clear indication to the user that the device considers a gesture associated with a lock function to have been detected. Such progressive adjustment of display properties can also help to indicate to the user when any of thresholds T1, T2 or T3 is considered reached by the gesture as detected by device 100.


It can therefore be seen that touch attributes of a swipe gesture applied to a touch sensitive display of a device 100 can be associated with multiple lock functions and, by use of a single gesture, a user can initiate one or more lock functions in device 100 without a need for multiple touches or multiple gestures. Further touches may be provided to activate further locking function options if desired.


Locking functions may include any of the following: activating a screen lock, activating a device lock, and activating a lock of certain functionality of the device. A screen lock may comprise setting a mode of the device wherein at least some touch input from the touch sensitive display is ignored. All touch input may be ignored when a screen lock is activated, unless touch input is required to unlock the screen, in which case only certain gestures may be used to unlock the screen. This advantageously avoids inadvertent “pocket dialing” wherein an unintended phone call is made or other touch events inadvertently occur while the device is in a user's pocket or purse, etc. This advantageously further avoids the potential costs associated with an accidental phone call or other accidental action. This advantageously further avoids other undesirable consequences, such as embarrassment or breach of confidentiality resulting from a conversation that is inadvertently overheard or a message that is inadvertently forwarded as a result of accidental touch inputs. In embodiments in which the device comprises a keyboard and/or other keys or buttons, inputs such as key or button presses may be ineffective while screen lock (which may also be referred to as a keyboard lock) is active. This advantageously avoids unintentional key presses while the device is in a user's pocket or purse, etc. Certain keys or buttons may be allowed to function while the screen lock (or keyboard lock) is active, such as a key or button used to make an emergency phone call, or a key or button used to power off the device, etc. The display may further be darkened, dimmed or switched off when the screen lock is active. Darkening, dimming or switching off the display advantageously reduces power consumption and extends battery life. In some embodiments, the device may display a screensaver or status information such as the date and time, etc. while screen lock is active. The device may also enter a standby mode or low-power mode when the screen lock is activated.


Locking functions may further include activating a device lock. A device lock may do any of the following: lock one or more services of the device, prevent access to the device over certain RF or wired links such as Bluetooth or USB access, and add security measures, such as requiring a password, PIN-code, biometric data, or other authentication token for accessing the device. If a password or other token is required to unlock a locked device, the locking function may be referred to as a password lock. A device lock may be considered an extension of the screen lock function, adding additional security beyond the screen lock and so to allow the user to lock the device as an extension of a gesture used to lock the screen provides a more convenient user interface. In one example of a device lock, which may sometimes be referred to as a partial device lock, certain applications or services or other resources of the device are inaccessible, while others are accessible. In one example of a partial device lock which may sometimes be referred to as a perimeter lock, wherein a perimeter generally refers to a logical group of resources that share a common management scheme governing their use, one or more perimeters of the device are locked while one or more perimeters of the device are unlocked. A device may comprise multiple perimeters, such as a work or enterprise perimeter, and a personal or recreational perimeter. A work perimeter may comprise work-related data and applications (such as customer relationship software, enterprise collaboration software, etc.) and other resources classified as work-related, and a personal perimeter may comprise personal-related data and applications (such as social networking applications, games, etc.) and other resources classified as personal. The perimeter lock may provide for the user to lock certain functions or resources of the device, such as those associated with a work or enterprise perimeter, with a gesture having a first set of touch attributes, and lock certain other functions or resources of the device, such as those associated with a personal or recreational perimeter of the device, if the gesture has a second set of touch attributes. The ability to provide such multiple locking functions can be desirable in particular in light of the increasing use of personal devices for work functions and there is therefore an increasing need for the ability to lock certain functions of the device more quickly, more easily, or more regularly than others.


The lock function may only be recognized by the device when the home screen is displayed. The detection of the gestures described herein for locking the device may therefore be disabled when the device is not showing the home screen. This can be beneficial, since a user often returns to the home screen before locking the device. A similar gesture may be used to return to the home screen as for locking the device, which provides a simple combination of similar gestures to both return to the home screen and to lock the device. Therefore, the same detection steps described herein in relation to a lock function may be used to activate a function which returns the user to the home screen. The method steps may further be applied to other non-locking functions of the device if desired.


A flowchart illustrating a method of detecting gestures associated with a lock function or functions is shown in FIG. 7. The method may be carried out by software executed, for example, by the processor 102. Coding of software for carrying out such a method is within the knowledge of a person of ordinary skill in the art given the present description. The method may contain additional or fewer processes than shown and/or described, and may be performed in a different order. Computer-readable code executable by at least one processor of the portable electronic device to perform the method may be stored in a computer-readable medium, which may be a non-transitory or tangible storage medium.


When a touch is detected 710 by the touch-sensitive display 118, touch data, including a touch location, is provided to the processor 102. For example, the touch location may be an x, y coordinate and may include additional touch information such as a time stamp, pressure information or other attributes obtainable from touch sensors 114. An initial touch location of a swipe gesture is determined 720 based on the received touch location. The touch location may be determined based on the raw touch input data or by establishing a virtual touch location, or a virtual touch area, based at least on the touch input data.


The initial touch location for the swipe gesture is compared 730 with a stored initial touch location for a locking function. Here, if the initial touch location does not correspond to the stored initial touch location for a locking function, then the process ends. If the detected initial touch location is the same as the stored initial touch location, then touch attributes are determined 740 for the gesture. The touch attributes determined at 740 are then compared 750 with stored touch attributes for a gesture corresponding to a lock function. This may be done after a delay, and/or repeated until either a gesture corresponding to a lock function is detected, or until a release of the gesture is detected. If the touch attributes for the gesture do not correspond to the stored touch attributes for a gesture associated with a lock function, then the process may end. However, if the touch attributes determined for the gesture do correspond to a stored gesture for the lock function, then the lock function is performed 760. It is then determined 770 whether the gesture has ended if this has not already been established. The gesture usually finishes with a release of the touch and so if the touch has been released, then the gesture is considered to have ended and the process ends. However, if the gesture has not ended and a touch is still detected, then the method may optionally compare 780 the gesture with a second set of touch attributes stored for a second gesture associated with a second lock function at 780. If the detected attributes correspond to stored attributes for a gesture associated with a second lock function, then the second lock function will be performed 790. If the detected attributes do not correspond to stored attributes for a gesture associated with the second lock function, then the process ends without performing a second lock function. Further instances of comparison step 780 and locking function performing step 790 may be included for further locking functions if desired. As set out above, it may be desirable to repeat steps 740 and 750 until either a release is detected or touch attributes corresponding to a lock function are detected, so that attributes of the gesture may be compared at multiple steps before ending the process. This may allow a sufficient number of iterations for the user to have described the gesture which is associated with a lock function before the process is ended. Alternatively or additionally, a delay may be provided between steps 730 and 740 so that a user has time to describe a suitable gesture before comparison step 750 is executed.


The implementation described is an illustrative example of one of many possible implementations envisioned by this disclosure. Other implementations may choose a different ordering, different weightings, and different combinations. Modifications to the examples may be made utilizing techniques to improve the efficiency and reduce computation or provide other advantages.


The present disclosure may be embodied in other specific forms without departing from its spirit or essential characteristics. The described examples are to be considered in all respects only as illustrative and not restrictive. The scope of the disclosure is, therefore, indicated by the appended claims rather than by the foregoing description. All changes that come within the meaning and range of equivalency of the claims are to be embraced within their scope.

Claims
  • 1. A method comprising: receiving a swipe gesture from an initial touch location on a touch-sensitive display of an electronic device;determining touch attributes for the swipe gesture, the touch attributes comprising a touch location of the swipe gesture;performing a first lock function when the swipe gesture progresses to a first touch location on the touch-sensitive display that is beyond a first threshold from the initial touch location, wherein the first lock function locks a first set of functionalities of the electronic device; andperforming a second lock function when the swipe gesture progresses to a second touch location on the touch-sensitive display that is beyond a second threshold from the initial touch location, wherein the second lock function locks a second, different set of functionalities of the electronic device and the second threshold is beyond the first threshold.
  • 2. The method of claim 1, wherein the initial touch location is substantially at or substantially adjacent to an edge of the touch-sensitive display.
  • 3. The method of claim 1, wherein the first lock function and the second lock function are associated with respective stored touch attributes each comprising a stored initial touch location, and wherein the initial touch location of the swipe gesture corresponds to the initial touch location stored for the first lock function and to the initial touch location stored for the second lock function.
  • 4. The method of claim 3, further comprising: comparing the determined touch attributes to the touch attributes stored for the first lock function; andcomparing the determined touch attributes to the touch attributes stored for the second lock function.
  • 5. The method of claim 1, wherein at least one of the first and second thresholds is defined by a distance along an axis of the touch-sensitive display from the initial touch location.
  • 6. The method of claim 1, wherein at least one of the first and second thresholds is defined by a distance along a path followed by the swipe gesture from the initial touch.
  • 7. The method of claim 1, further comprising visually altering a graphical output of the touch-sensitive display as the swipe gesture proceeds, to provide a visual indication of the impending activation of the lock function.
  • 8. The method of claim 1, wherein detecting a release of the swipe gesture activates the first lock function and the second lock function.
  • 9. The method of claim 1, wherein the second lock function adds additional security to the first lock function.
  • 10. The method of claim 9, wherein at least one of the first and second lock functions comprises at least one of: locking a service, locking an application, a device lock, a partial device lock, or a perimeter lock.
  • 11. The method of claim 1, wherein the first threshold defines a swipe having a first length, and the second threshold defines a swipe having a second length longer than the first length.
  • 12. The method of claim 1, wherein the first lock function comprises a screen lock.
  • 13. The method of claim 1, wherein the second lock function comprises a device lock.
  • 14. The method of claim 1, further comprising presenting a lock function indicator on the display if at least one stored swipe gesture is detected.
  • 15. The method of claim 14, further comprising activating a lock function upon receiving a touch input at the lock function indicator.
  • 16. An electronic device configured to perform a method comprising: receiving a swipe gesture from an initial touch location on a touch-sensitive display of an electronic device;determining touch attributes for the swipe gesture, the touch attributes comprising a touch location of the swipe gesture;performing a first lock function when the swipe gesture progresses to a first touch location on the touch-sensitive display that is beyond a first threshold from the initial touch location, wherein the first lock function locks a first set of functionalities of the electronic device; andperforming a second lock function when the swipe gesture progresses to a second touch location on the touch-sensitive display that is beyond a second threshold from the initial touch location, wherein the second lock function locks a second, different set of functionalities of the electronic device and the second threshold is beyond the first threshold.
  • 17. The electronic device of claim 16, wherein the initial touch location is substantially at or substantially adjacent to an edge of the touch-sensitive display.
  • 18. The electronic device of claim 16, wherein the first lock function and the second lock function are associated with respective stored touch attributes each comprising a stored initial touch location, and wherein the initial touch location of the swipe gesture corresponds to the initial touch location stored for the first lock function and to the initial touch location stored for the second lock function.
  • 19. The electronic device of claim 16, wherein the method further comprises: comparing the determined touch attributes to the touch attributes stored for the first lock function; andcomparing the determined touch attributes to the touch attributes stored for the second lock function.
  • 20. The electronic device of claim 16, wherein at least one of the first and second thresholds is defined by a distance along an axis of the touch-sensitive display from the initial touch location.
  • 21. The electronic device of claim 16, wherein at least one of the first and second thresholds is defined by a distance along a path followed by the swipe gesture from the initial touch location.
  • 22. The electronic device of claim 16, wherein the method further comprises visually altering a graphical output of the touch-sensitive display as the swipe gesture proceeds, to provide a visual indication of the impending activation of the lock function.
  • 23. The electronic device of claim 16, wherein detecting a release of the swipe gesture activates the first lock function and the second lock function.
  • 24. The electronic device of claim 16, wherein the second lock function adds additional security to the first lock function.
  • 25. The electronic device of claim 16, wherein the first threshold defines a swipe having a first length, and the second threshold defines a swipe having a second length longer than the first length.
  • 26. The electronic device of claim 16, wherein the first lock function comprises a screen lock.
  • 27. The electronic device of claim 16, wherein the second lock function comprises a device lock.
  • 28. The electronic device of claim 16, wherein at least one of the first and second lock functions comprises at least one of: locking a service, locking an application, a device lock, a partial device lock, or a perimeter lock.
  • 29. The electronic device of claim 16, wherein the method further comprises presenting a lock function indicator on the display if at least one stored swipe gesture is detected.
  • 30. The electronic device of claim 29, further comprising activating a lock function upon receiving a touch input at the lock function indicator.
  • 31. A non-transitory computer-readable storage medium having computer-readable code executable by at least one processor of a portable electronic device to perform operations comprising: receiving a swipe gesture from an initial touch location on a touch-sensitive display of an electronic device;determining touch attributes for the swipe gesture, the touch attributes comprising a touch location of the swipe gesture;performing a first lock function when the swipe gesture progresses to a first touch location on the touch-sensitive display that is beyond a first threshold from the initial touch location, wherein the first lock function locks a first set of functionalities of the electronic device; andperforming a second lock function when the swipe gesture progresses to a second touch location on the touch-sensitive display that is beyond a second threshold from the initial touch location, wherein the second lock function locks a second, different set of functionalities of the electronic device and the second threshold is beyond the first threshold.
  • 32. The non-transitory computer-readable storage medium of claim 31, wherein the initial touch location is substantially at or substantially adjacent to an edge of the touch-sensitive display.
  • 33. The non-transitory computer-readable storage medium of claim 31, wherein the first lock function and the second lock function are associated with respective stored touch attributes each comprising a stored initial touch location, and wherein the initial touch location of the swipe gesture corresponds to the initial touch location stored for the first lock function and to the initial touch location stored for the second lock function.
  • 34. The non-transitory computer-readable storage medium of claim 33, wherein the operations further comprise: comparing the determined touch attributes to the touch attributes stored for the first lock function; andcomparing the determined touch attributes to the touch attributes stored for the second lock function.
  • 35. The non-transitory computer-readable storage medium of claim 31, wherein at least one of the first and second thresholds is defined by a distance along an axis of the touch-sensitive display from the initial touch location.
  • 36. The non-transitory computer-readable storage medium of claim 31, wherein at least one of the first and second thresholds is defined by a distance along a path followed by the swipe gesture from the initial touch.
  • 37. The non-transitory computer-readable storage medium of claim 31, wherein the operations further comprise visually altering a graphical output of the touch-sensitive display as the swipe gesture proceeds, to provide a visual indication of the impending activation of the lock function.
  • 38. The non-transitory computer-readable storage medium of claim 31, wherein detecting a release of the swipe gesture activates the first lock function and the second lock function.
  • 39. The non-transitory computer-readable storage medium of claim 31, wherein the second lock function adds additional security to the first lock function.
  • 40. The non-transitory computer-readable storage medium of claim 39, wherein at least one of the first and second lock functions comprises at least one of: locking a service, locking an application, a device lock, a partial device lock, or a perimeter lock.
  • 41. The non-transitory computer-readable storage medium of claim 31, wherein the first threshold defines a swipe having a first length, and the second threshold defines a swipe having a second length longer than the first length.
  • 42. The non-transitory computer-readable storage medium of claim 31, wherein the first lock function comprises a screen lock.
  • 43. The non-transitory computer-readable storage medium of claim 31, wherein the second lock function comprises a device lock.
  • 44. The non-transitory computer-readable storage medium of claim 31, wherein the operations further comprise presenting a lock function indicator on the display if at least one stored swipe gesture is detected.
  • 45. The non-transitory computer-readable storage medium of claim 44, wherein the operations further comprise activating a lock function upon receiving a touch input at the lock function indicator.
US Referenced Citations (268)
Number Name Date Kind
3872433 Holmes et al. Mar 1975 A
4408302 Fessel et al. Oct 1983 A
5261009 Bokser Nov 1993 A
5664127 Anderson et al. Sep 1997 A
5832528 Kwatinetz et al. Nov 1998 A
5963671 Comerford et al. Oct 1999 A
6002390 Masui Dec 1999 A
6064340 Martin et al. May 2000 A
6094197 Buxton et al. Jul 2000 A
6223059 Haestrup Apr 2001 B1
6226299 Henson May 2001 B1
6351634 Shin Feb 2002 B1
6421453 Kanevsky et al. Jul 2002 B1
6573844 Venolia et al. Jun 2003 B1
6621424 Brand Sep 2003 B1
6646572 Brand Nov 2003 B1
6801190 Robinson et al. Oct 2004 B1
7061403 Fux Jun 2006 B2
7098896 Kushler et al. Aug 2006 B2
7107204 Liu et al. Sep 2006 B1
7216588 Suess May 2007 B2
7259752 Simmons Aug 2007 B1
7277088 Robinson et al. Oct 2007 B2
7292226 Matsuura et al. Nov 2007 B2
7382358 Kushler et al. Jun 2008 B2
7394346 Bodin Jul 2008 B2
7443316 Lim Oct 2008 B2
7479949 Jobs et al. Jan 2009 B2
7487461 Zhai et al. Feb 2009 B2
7526316 Shimizu Apr 2009 B2
7530031 Iwamura et al. May 2009 B2
7661068 Lund Feb 2010 B2
7671765 Fux Mar 2010 B2
7698127 Trower, II et al. Apr 2010 B2
7886233 Rainisto et al. Feb 2011 B2
7934156 Forstall et al. Apr 2011 B2
8023930 Won Sep 2011 B2
8059101 Westerman et al. Nov 2011 B2
8065624 Morin et al. Nov 2011 B2
8201087 Kay et al. Jun 2012 B2
8225203 Unruh Jul 2012 B2
8289283 Kida et al. Oct 2012 B2
8326358 Runstedler et al. Dec 2012 B2
8490008 Griffin et al. Jul 2013 B2
8516386 Adam et al. Aug 2013 B2
8542206 Westerman et al. Sep 2013 B2
20020080186 Frederiksen Jun 2002 A1
20020097270 Keely et al. Jul 2002 A1
20020154037 Houston Oct 2002 A1
20020180797 Bachmann Dec 2002 A1
20040111475 Schultz Jun 2004 A1
20040135818 Thomson et al. Jul 2004 A1
20040140956 Kushler et al. Jul 2004 A1
20040153963 Simpson et al. Aug 2004 A1
20040201576 Shimada et al. Oct 2004 A1
20050017954 Kay et al. Jan 2005 A1
20050024341 Gillespie et al. Feb 2005 A1
20050039137 Bellwood et al. Feb 2005 A1
20050052425 Zadesky et al. Mar 2005 A1
20050093826 Huh May 2005 A1
20050162407 Sakurai et al. Jul 2005 A1
20050195173 McKay Sep 2005 A1
20050244208 Suess Nov 2005 A1
20050275632 Pu et al. Dec 2005 A1
20060022947 Griffin et al. Feb 2006 A1
20060026521 Hotelling et al. Feb 2006 A1
20060033724 Chaudhri et al. Feb 2006 A1
20060053387 Ording Mar 2006 A1
20060176283 Suraqui Aug 2006 A1
20060209040 Garside et al. Sep 2006 A1
20060239562 Bhattacharyay et al. Oct 2006 A1
20060253793 Zhai et al. Nov 2006 A1
20060265648 Rainisto et al. Nov 2006 A1
20060265668 Rainisto Nov 2006 A1
20060279548 Geaghan Dec 2006 A1
20070015534 Shimizu Jan 2007 A1
20070046641 Lim Mar 2007 A1
20070061753 Ng et al. Mar 2007 A1
20070150842 Chaudhri et al. Jun 2007 A1
20070156394 Banerjee et al. Jul 2007 A1
20070157085 Peters Jul 2007 A1
20070229476 Huh Oct 2007 A1
20070256029 Maxwell Nov 2007 A1
20070263932 Bernardin et al. Nov 2007 A1
20080033713 Brostrom Feb 2008 A1
20080100581 Fux May 2008 A1
20080122796 Jobs et al. May 2008 A1
20080126387 Blinnikka May 2008 A1
20080136587 Orr Jun 2008 A1
20080141125 Ghassabian Jun 2008 A1
20080158020 Griffin Jul 2008 A1
20080168366 Kocienda et al. Jul 2008 A1
20080184360 Kornilovsky et al. Jul 2008 A1
20080189605 Kay et al. Aug 2008 A1
20080195388 Bower et al. Aug 2008 A1
20080231610 Hotelling et al. Sep 2008 A1
20080259040 Ording et al. Oct 2008 A1
20080266261 Idzik Oct 2008 A1
20080273013 Levine et al. Nov 2008 A1
20080281583 Slothouber et al. Nov 2008 A1
20080304890 Shin et al. Dec 2008 A1
20080309644 Arimoto Dec 2008 A1
20080316183 Westerman et al. Dec 2008 A1
20080318635 Yoon et al. Dec 2008 A1
20090002326 Pihlaja Jan 2009 A1
20090006991 Lindberg et al. Jan 2009 A1
20090025089 Martin et al. Jan 2009 A1
20090058823 Kocienda Mar 2009 A1
20090058830 Herz et al. Mar 2009 A1
20090066668 Kim et al. Mar 2009 A1
20090077464 Goldsmith et al. Mar 2009 A1
20090085881 Keam Apr 2009 A1
20090094562 Jeong et al. Apr 2009 A1
20090125848 Keohane et al. May 2009 A1
20090132576 Miller et al. May 2009 A1
20090144667 Christoffersson et al. Jun 2009 A1
20090150785 Asami et al. Jun 2009 A1
20090160800 Liu et al. Jun 2009 A1
20090167700 Westerman et al. Jul 2009 A1
20090174667 Kocienda et al. Jul 2009 A1
20090193334 Assadollahi Jul 2009 A1
20090213081 Case, Jr. Aug 2009 A1
20090228792 Van Os et al. Sep 2009 A1
20090228842 Westerman et al. Sep 2009 A1
20090237361 Mosby et al. Sep 2009 A1
20090247112 Lundy et al. Oct 2009 A1
20090251410 Mori et al. Oct 2009 A1
20090254818 Jania et al. Oct 2009 A1
20090259962 Beale Oct 2009 A1
20090265669 Kida et al. Oct 2009 A1
20090267909 Chen et al. Oct 2009 A1
20090284471 Longe et al. Nov 2009 A1
20090295737 Goldsmith et al. Dec 2009 A1
20090307768 Zhang et al. Dec 2009 A1
20090313693 Rogers Dec 2009 A1
20100020033 Nwosu Jan 2010 A1
20100020036 Hui et al. Jan 2010 A1
20100026650 Srivastava et al. Feb 2010 A1
20100045705 Vertegaal et al. Feb 2010 A1
20100050121 Shin Feb 2010 A1
20100052880 Laitinen Mar 2010 A1
20100070908 Mori et al. Mar 2010 A1
20100079413 Kawashima et al. Apr 2010 A1
20100095238 Baudet Apr 2010 A1
20100097321 Son et al. Apr 2010 A1
20100115402 Knaven et al. May 2010 A1
20100127991 Yee May 2010 A1
20100131900 Spetalnick May 2010 A1
20100141590 Markiewicz et al. Jun 2010 A1
20100156813 Duarte et al. Jun 2010 A1
20100156818 Burrough et al. Jun 2010 A1
20100161538 Kennedy, Jr. et al. Jun 2010 A1
20100197352 Runstedler et al. Aug 2010 A1
20100199176 Chronqvist Aug 2010 A1
20100225599 Danielsson et al. Sep 2010 A1
20100235726 Ording et al. Sep 2010 A1
20100253620 Singhal Oct 2010 A1
20100257478 Longe et al. Oct 2010 A1
20100257490 Lyon et al. Oct 2010 A1
20100259482 Ball Oct 2010 A1
20100259561 Forutanpour et al. Oct 2010 A1
20100265181 Shore Oct 2010 A1
20100269040 Lee Oct 2010 A1
20100277424 Chang et al. Nov 2010 A1
20100287486 Coddington Nov 2010 A1
20100292984 Huang et al. Nov 2010 A1
20100293475 Nottingham et al. Nov 2010 A1
20100295801 Bestle et al. Nov 2010 A1
20100313127 Gosper et al. Dec 2010 A1
20100313158 Lee et al. Dec 2010 A1
20100315266 Gunawardana et al. Dec 2010 A1
20100325721 Bandyopadhyay et al. Dec 2010 A1
20100333027 Martensson et al. Dec 2010 A1
20110010655 Dostie et al. Jan 2011 A1
20110018812 Baird Jan 2011 A1
20110029862 Scott et al. Feb 2011 A1
20110035696 Elazari et al. Feb 2011 A1
20110041056 Griffin et al. Feb 2011 A1
20110043455 Roth et al. Feb 2011 A1
20110060984 Lee Mar 2011 A1
20110061029 Yeh et al. Mar 2011 A1
20110063231 Jakobs et al. Mar 2011 A1
20110074704 Causey et al. Mar 2011 A1
20110078613 Bangalore Mar 2011 A1
20110086674 Rider et al. Apr 2011 A1
20110090151 Huang et al. Apr 2011 A1
20110099505 Dahl Apr 2011 A1
20110099506 Gargi et al. Apr 2011 A1
20110105193 Lee et al. May 2011 A1
20110119623 Kim May 2011 A1
20110130170 Han et al. Jun 2011 A1
20110148572 Ku Jun 2011 A1
20110171617 Yeh et al. Jul 2011 A1
20110179355 Karlsson Jul 2011 A1
20110193797 Unruh Aug 2011 A1
20110201387 Paek et al. Aug 2011 A1
20110202835 Jakobsson et al. Aug 2011 A1
20110202876 Badger et al. Aug 2011 A1
20110209087 Guyot-Sionnest Aug 2011 A1
20110233407 Wu et al. Sep 2011 A1
20110239153 Carter et al. Sep 2011 A1
20110242138 Tribble Oct 2011 A1
20110248945 Higashitani Oct 2011 A1
20110249076 Zhou et al. Oct 2011 A1
20110256848 Bok et al. Oct 2011 A1
20110285656 Yaksick et al. Nov 2011 A1
20110302518 Zhang Dec 2011 A1
20110305494 Kang Dec 2011 A1
20120005576 Assadollahi Jan 2012 A1
20120023447 Hoshino et al. Jan 2012 A1
20120029910 Medlock et al. Feb 2012 A1
20120030566 Victor Feb 2012 A1
20120030623 Hoellwarth Feb 2012 A1
20120030624 Migos Feb 2012 A1
20120036469 Suraqui Feb 2012 A1
20120053887 Nurmi Mar 2012 A1
20120062465 Spetalnick Mar 2012 A1
20120062494 Hsieh et al. Mar 2012 A1
20120068937 Backlund et al. Mar 2012 A1
20120079373 Kocienda et al. Mar 2012 A1
20120084734 Wilairat Apr 2012 A1
20120092278 Yamano Apr 2012 A1
20120110518 Chan et al. May 2012 A1
20120117506 Koch et al. May 2012 A1
20120119997 Gutowitz May 2012 A1
20120144330 Flint Jun 2012 A1
20120149477 Park et al. Jun 2012 A1
20120159317 Di Cocco et al. Jun 2012 A1
20120162081 Stark Jun 2012 A1
20120166696 Kallio et al. Jun 2012 A1
20120167009 Davidson et al. Jun 2012 A1
20120174042 Chang Jul 2012 A1
20120200514 Allen Aug 2012 A1
20120223959 Lengeling Sep 2012 A1
20120284673 Lamb et al. Nov 2012 A1
20120284789 Kim et al. Nov 2012 A1
20120306772 Tan et al. Dec 2012 A1
20120311437 Weeldreyer et al. Dec 2012 A1
20130007606 Dolenc Jan 2013 A1
20130061317 Runstedler et al. Mar 2013 A1
20130063356 Martisauskas Mar 2013 A1
20130067411 Kataoka et al. Mar 2013 A1
20130104068 Murphy et al. Apr 2013 A1
20130120266 Griffin et al. May 2013 A1
20130120267 Pasquero et al. May 2013 A1
20130120268 Griffin et al. May 2013 A1
20130125034 Griffin et al. May 2013 A1
20130125036 Griffin et al. May 2013 A1
20130125037 Pasquero et al. May 2013 A1
20130176228 Griffin et al. Jul 2013 A1
20130187858 Griffin et al. Jul 2013 A1
20130187868 Griffin et al. Jul 2013 A1
20130222249 Pasquero et al. Aug 2013 A1
20130222255 Pasquero et al. Aug 2013 A1
20130222256 Pasquero et al. Aug 2013 A1
20130246329 Pasquero et al. Sep 2013 A1
20130263038 Griffin et al. Oct 2013 A1
20130271375 Griffin et al. Oct 2013 A1
20130271385 Griffin et al. Oct 2013 A1
20130275923 Griffin et al. Oct 2013 A1
20130285916 Griffin et al. Oct 2013 A1
20130314331 Rydenhag et al. Nov 2013 A1
20130342452 Kuo et al. Dec 2013 A1
20140002363 Griffin et al. Jan 2014 A1
20140062886 Pasquero et al. Mar 2014 A1
20140062923 Thorsander et al. Mar 2014 A1
20140063067 Compton et al. Mar 2014 A1
20140067372 Pasquero et al. Mar 2014 A1
Foreign Referenced Citations (69)
Number Date Country
2688204 Jul 2010 CA
2812457 Oct 2013 CA
2813393 Oct 2013 CA
2819839 Dec 2013 CA
2820997 Jan 2014 CA
101021762 Aug 2007 CN
0844571 May 1998 EP
0880090 Nov 1998 EP
0880090 Nov 1998 EP
1847917 Oct 2007 EP
1847917 Oct 2007 EP
1850217 Oct 2007 EP
1909161 Apr 2008 EP
1939715 Jul 2008 EP
1942398 Jul 2008 EP
2077491 Jul 2009 EP
2109046 Oct 2009 EP
2128750 Dec 2009 EP
2146271 Jan 2010 EP
2184686 May 2010 EP
2214118 Aug 2010 EP
2256614 Dec 2010 EP
2282252 Feb 2011 EP
2293168 Mar 2011 EP
2320312 May 2011 EP
2336851 Jun 2011 EP
2381384 Oct 2011 EP
2386976 Nov 2011 EP
2402846 Jan 2012 EP
2420925 Feb 2012 EP
2431842 Mar 2012 EP
2400426 Mar 2013 EP
2618248 Jul 2013 EP
2631758 Aug 2013 EP
2653955 Oct 2013 EP
2660696 Nov 2013 EP
2660697 Nov 2013 EP
2660699 Nov 2013 EP
2660727 Nov 2013 EP
2703955 Mar 2014 EP
2703956 Mar 2014 EP
2703957 Mar 2014 EP
2011-197782 Oct 2011 JP
2012-68963 Apr 2012 JP
KR20120030652 Mar 2012 KP
03029950 Apr 2003 WO
03054681 Jul 2003 WO
2004001560 Dec 2003 WO
2005064587 Jul 2005 WO
2006100509 Sep 2006 WO
2007068505 Jun 2007 WO
2007076210 Jul 2007 WO
2007134433 Nov 2007 WO
WO2008030974 Mar 2008 WO
WO2008057785 May 2008 WO
WO2008085741 Jul 2008 WO
2009019546 Feb 2009 WO
2010035574 Apr 2010 WO
2010035585 Apr 2010 WO
WO2010035574 Apr 2010 WO
WO2010099835 Sep 2010 WO
WO2010112841 Oct 2010 WO
2011073992 Jun 2011 WO
WO2011073992 Jun 2011 WO
2011098925 Aug 2011 WO
WO2011113057 Sep 2011 WO
2012043932 Apr 2012 WO
2013163718 Nov 2013 WO
2013164013 Nov 2013 WO
Non-Patent Literature Citations (152)
Entry
“Features Included in the T-Mobile G1”, http://www.t-mobileg1.com/T-Mobile-G1-Features.pdf, 2009.
BlackBerry Seeker—Freeware—Pattern Lock v1.0.7, http://www.blackberryseeker.com/applications/preview/Pattern-Lock-v107.aspx, Jul. 28, 2009.
Chong et al., Exploring the Use of Discrete Gestures for Authentication, IFIP International Federation for Information Processing, 2009.
Conveniently select text, images, annotations, etc. In a PDF or any other text format on a touch based mobile/tablet device, IP.com Journal, Mar. 1, 2011, XP013142665, (10 pages).
DROID X by Motorola © 2010 Screen shots.
DROID X by Motorola © 2010 User Manual (72 pages).
European Search Report dated Feb. 28, 2011, issued in European Patent Application No. 10160590.5.
Extended European Search Report dated Aug. 24, 2012, issued in European Application No. 12166115.1 (5 pages).
Extended European Search Report dated Aug. 31, 2012, issued in European Application No. 12166170.6 (7 pages).
Extended European Search Report dated Oct. 9, 2012, issued in European Application No. 12166244.9 (6 pages).
Extended European Search Report dated Sep. 10, 2012, issued in European Application No. 12166246.4 (6 pages).
Extended European Search Report dated Sep. 10, 2012, issued in European Application No. 12166247.2 (8 pages).
Extended European Search Report dated Sep. 21, 2012, issued in European Application No. 12164240.9 (6 pages).
Extended European Search Report dated Sep. 25, 2012, issued in European Application No. 11192713.3 (7 pages).
Extended European Search Report dated Sep. 3, 2012, issued in European Application No. 12164300.1 (7 pages).
Google Mobile Help—Editing text, http://support.google.com/mobile/bin/answer.py?hl=en&answer=168926, date of access: Jun. 6, 2012 (2 pages).
GSMArena—Samsung announce s5600 & s5230 full touch midrange phones, http://www.gsmarena.com/samsung—announce—s5600—and—s5230 full—touch—midrange—phones-news-825.php, Mar. 10, 2009.
Hardware Sphere—Samsung s5600 & s5230 Touchscreen phones, http://hardwaresphere.com/2009/03/09/samsung-s5600-s5230-touchscreen-phones/, Mar. 9, 2009.
International Search Report and Written Opinion issued in International Application No. PCT/EP2012/057944, on Oct. 12, 2012, (10 pages).
International Search Report and Written Opinion issued in International Application No. PCT/IB2011/003273, on Jun. 14, 2012, (8 pages).
International Search Report and Written Opinion mailed Sep. 10, 2012, issued for International Application No. PCT/EP2012/057945 (11 pages).
iPhone User Guide—For iPhone OS 3.1 Software, 2009 (217 pages).
Madhvanath, Sriganesh, HP-Gesture based computing interfaces, Mar. 2008.
Manual del usuario Samsung Moment • with Google • dated May 20, 2012 (224 pages).
Merrett, Andy, “iPhone OS 3.0: How to cut, copy and paste text and images”, http://www.iphonic.tv/2009/06/iphone—os—30—how—to—cut—copy—a.html, Jun. 18, 2009, XP002684215, (8 pages).
Mobile Tech News—Samsung launches new Gesture Lock touchscreen handsets, http://www.mobiletechnews.com/info/2009/03/11/124559.html, Mar. 11, 2009.
Partial European Search Report; Application No. 10160590.5; Sep. 16, 2010.
Sprint Support Tutorial Set the Screen Lock Pattern—Samsung Moment, http://support.sprint.com/support/tutorial/Set—the—Screen—Lock—Pattern—Samsung—Moment/10887-171, date of access: May 31, 2012 (9 pages).
Sprint Support Tutorial Unlock a Forgotten Lock Pattern—Samsung Moment, http://supportsprint.com/support/tutorial/Unlock—a—Forgotten—Lock—Pattern—Samsung—Moment/10887-339, date of access: May 31, 2012 (7 pages).
Support—Sprint Cell Phones SPH-M900—Samsung Cell Phones, http://www.samsung.com/us/support/owners/product/SPH-M900?tabContent-content2, date of access: May 31, 2012 (1 page).
T-Mobile Forum—Help & How to—Hidden Pattern, http://forums.t-mobile.com/tmbl/board/message?board.id=Android3&message.id=3511&query.id=52231#M3511, Oct. 23, 2008.
T-Mobile Forum—Help & How to—Screen Unlock Pattern, http://forums.t-mobile.com/tmbl/board/message?board.id=Android3&message.id=6015&query.id=50827#M6015, Oct. 22, 2008.
T-Mobile launches the highly anticipated T-Mobile G1, Oct. 22, 2008.
U.S. Office Action dated Oct. 15, 2012, issued in U.S. Appl. No. 13/560,270 (15 pages).
U.S. Office Action dated Oct. 17, 2012, issued in U.S. Appl. No. 13/563,943 (17 pages).
U.S. Office Action dated Oct. 18, 2012, issued in U.S. Appl. No. 13/563,182 (12 pages).
U.S. Office Action dated Oct. 23, 2012, issued in U.S. Appl. No. 12/764,298 (41 pages).
U.S. Office Action dated Oct. 25, 2012, issued in U.S. Appl. No. 13/459,732 (15 pages).
U.S. Office Action dated Oct. 5, 2012, issued in U.S. Appl. No. 13/447,835 (20 pages).
U.S. Office Action dated Sep. 10, 2012, issued in U.S. Appl. No. 13/524,678 (12 pages).
U.S. Office Action dated Sep. 28, 2012, issued in U.S. Appl. No. 13/494,794 (14 pages).
U.S. Office Action for U.S. Appl. No. 12/764,298, dated Jul. 20, 2012, (38 pages).
U.S. Office Action for U.S. Appl. No. 13/482,705, dated Aug. 7, 2012, (10 pages).
User Guide Samsung Moment(TM) with Google(TM), dated Dec. 4, 2009 (122 pages).
User Guide Samsung Moment(TM) with Google(TM), dated Mar. 2, 2010 (218 pages).
“Windows Mobile Café—Software (Freeware): Touchpal, Let's Try Tabbing Up to 300 Chars/Min”, Nov. 4, 2007, retrieved from URL:http://windows-mobile-cafe.blogspot.nl/2007/11/software-freeware-touchpal-lets-try.html, accessed online Jan. 18, 2013 (2 pages).
Canadian Office Action dated Aug. 8, 2012, issued in Canadian Application No. 2,688,204 (3 pages).
Canadian Office Action dated Mar. 27, 2013, issued in Canadian Application No. 2,737,314 (3 pages).
Distinctive Touch: Gesture-based lightweight identification for touchscreen displays, Electronic Max, Dec. 7, 2004, http://courses.media.mit.edu/2004fall/mas622j/04.projects/students/VanKleek/; accessed online Apr. 27, 2009, pp. 1-11.
European Examination Report dated Apr. 5, 2013, issued in European Application No. 12180190.6 (7 pages).
European Partial Search Report dated Jan. 16, 2013, issued in European Application No. 12182612.7 (5 pages).
European Partial Search Report dated Mar. 7, 2013, issued in European Application No. 12184574.7 (5 pages).
Extended European Search Report dated Aug. 24, 2012, issued in European Application No. 12172458.7 (6 pages).
Extended European Search Report dated Aug. 27, 2012, issued in European Application No. 12169649.6 (7 pages).
Extended European Search Report dated Feb. 28, 2013, issued in European Application No. 12182610.1 (7 pages).
Extended European Search Report dated Jan. 25, 2013, issued in European Application No. 12166520.2 (8 pages).
Extended European Search Report dated Jun. 26, 2013, issued in European Application No. 12184574.7 (10 pages).
Extended European Search Report dated Mar. 8, 2013, issued in European Application No. 12182611.9 (8 pages).
Extended European Search Report dated May 6, 2009, issued in European Application No. 09151723.5 (7 pages).
Extended European Search Report dated Nov. 22, 2012, issued in European Application No. 12172892.7 (7 pages).
Extended European Search Report dated Nov. 28, 2011, issued in European Application No. 11180985.1 (4 pages).
Extended European Search Report dated Sep. 25, 2012, issued in European Application No. 12176453.4 (7 pages).
Extended European Search Report dated Sep. 25, 2012, issued in European Application No. 12180190.6 (8 pages).
Final Office Action dated Apr. 25, 2013, issued in U.S. Appl. No. 13/564,697 (11 pages).
Final Office Action dated Apr. 4, 2013, issued in U.S. Appl. No. 13/447,835 (20 pages).
Final Office Action dated Feb. 1, 2013, issued in U.S. Appl. No. 13/563,943 (17 pages).
Final Office Action dated Feb. 28, 2013, issued in U.S. Appl. No. 13/524,678 (21 pages).
Final Office Action dated Jan. 18, 2013, issued in U.S. Appl. No. 13/482,705 (18 pages).
Final Office Action dated Jul. 9, 2013, issued in U.S. Appl. No. 13/564,070 (26 pages).
Final Office Action dated Jul. 25, 2013, issued in U.S. Appl. No. 13/560,796 (19 pages).
Final Office Action dated Jul. 30, 2013, issued in U.S. Appl. No. 13/459,301 (27 pages).
Final Office Action dated Mar. 15, 2013, issued in U.S. Appl. No. 13/572,232 (36 pages).
Final Office Action dated May 10, 2013, issued in U.S. Appl. No. 13/459,301 (16 pages).
Final Office Action dated May 15, 2013, issued in U.S. Appl. No. 13/563,182 (21 pages).
Final Office Action dated May 2, 2013, issued in U.S. Appl. No. 13/564,687 (17 pages).
Final Office Action dated May 29, 2012, issued in U.S. Appl. No. 12/362,536 (16 pages).
Final Office Action dated Oct. 26, 2011, issued in U.S. Appl. No. 12/362,536 (21 pages).
iPhone J.D. Typing Letters or Symbols That Are Not on the iPhone Keyboard dated Mar. 19, 2010, accessed “http://www.iphonejd.com/iphone—jd2010/03/typing-letters-or-symbols-that-are-not-on-the-iphone-keyboard.html” on Feb. 26, 2013 (3 pages).
Notice of Allowance dated Mar. 15, 2013, issued in U.S. Appl. No. 13/373,356 (25 pages).
Office Action dated Dec. 28, 2012, issued in U.S. Appl. No. 13/459,301 (22 pages).
Office Action dated Jan. 22, 2013, issued in U.S. Appl. No. 13/564,687 (19 pages).
Office Action dated Jan. 29, 2013, issued in U.S. Appl. No. 13/563,182 (19 pages).
Office Action dated Jan. 7, 2013, issued in U.S. Appl. No. 13/564,070 (21 pages).
Office Action dated Jan. 7, 2013, issued in U.S. Appl. No. 13/564,697 (19 pages).
Office Action dated Jun. 8, 2011, issued in U.S. Appl. No. 12/362,536 (19 pages).
Office Action dated Mar. 12, 2013, issued in U.S. Appl. No. 13/560,796 (22 pages).
Office Action dated May 30, 2013, issued in U.S. Appl. No. 13/572,232 (49 pages).
Office Action dated Nov. 14, 2012, issued in U.S. Appl. No. 13/572,232 (24 pages).
Office Action dated Nov. 16, 2012, issued in U.S. Appl. No. 13/554,583 (21 pages).
Office Action dated Nov. 8, 2012, issued in U.S. Appl. No. 13/373,356 (18 pages).
Office Action dated Oct. 26, 2012, issued in U.S. Appl. No. 13/554,436 (22 pages).
PCT International Search Report and Written Opinion dated Jan. 24, 2013, issued in International Application No. PCT/CA2012/050274 (9 pages).
PCT International Search Report and Written Opinion dated Nov. 7, 2012, issued in International Application No. PCT/CA2012/050362 (9 pages).
PCT International Search Report and Written Opinion dated Nov. 8, 2012, issued in International Application No. PCT/CA2012/050405 (12 pages).
Swype Product Features, accessed online at http://www.swype.com/about/specifications/ on Feb. 25, 2013 (2 pages).
Through the Magic Window—Magic Window word processor for the Apple II, Artsci Publishing, 1980, http://www.artscipub.com/history/magicwindow, accessed May 21, 2013 (5 pages).
U.S. Appl. No. 13/601,736, filed Aug. 31, 2012 (44 pages).
U.S. Appl. No. 13/616,423, filed Sep. 14, 2012 (30 pages).
U.S. Appl. No. 13/773,812, filed Feb. 22, 2013 (94 pages).
Wang, Feng, et al., “Detecting and Leveraging Finger Orientation for Interaction with Direct-Touch Surfaces”, UIST '09, Oct. 4-7, 2009, Victoria, British Columbia, Canada (10 pages).
Office Action issued in EP 12169649.6 dated Mar. 12, 2014.
Enable or Disable SureType with a RIM BlackBerry Pearl Using Handheld Software, version 4.x, “http://www.wireless.att.com/support—static—files/KB/KB72601.html”, at least as early as Feb. 8, 2008 (3 pages).
European Examination Report dated Aug. 22, 2013, issued in European Application No. 12166520.2, (4 pages).
European Examination Report dated Aug. 22, 2013, issued in European Application No. 12173818.1, (6 pages).
European Examination Report dated Dec. 9, 2013, issued in European Application No. 12172458.7 (4 pages).
Extended European Search Report dated Dec. 21, 2012, issued in European Application No. 12173818.1, (8 pages).
Final Office Action dated Dec. 13, 2013, issued in U.S. Appl. No. 13/572,232, (30 pages).
Final Office Action dated Feb. 10, 2014, issued in U.S. Appl. No. 13/485,723, (19 pages).
Notice of Allowance dated Aug. 12, 2013, issued in U.S. Appl. No. 13/564,687, (10 pages).
Notice of Allowance mailed Oct. 11, 2013, issued in U.S. Appl. No. 13/563,943, (20 pages).
Office Action dated Dec. 6, 2013, issued in U.S. Appl. No. 13/564,697, (22 pages).
Office Action dated Jan. 31, 2014, issued in U.S. Appl. No. 13/534,101, (38 pages).
Office Action dated Mar. 12, 2014, issued in U.S. Appl. No. 13/616,423, (21 pages).
Office Action dated Nov. 22, 2013, issued in U.S. Appl. No. 13/447,704, (47 pages).
Office Action dated Oct. 17, 2013, issued in U.S. Appl. No. 13/485,723, (28 pages).
Touchpal (combination of two sources: first, youtube video on touchpal at url: http://www.youtube.com/watch?v=eJUWFEXxJal, dated on Dec. 1, 2011, with screen captures shown below; second, TimesofIndia website article on touchpal at url: http://articles.timesofindia.indiatimes.com/2012-01-29/computing/30673975—1—swype-android-market-qwerty).
U.S. Appl. No. 13/459,301, filed Apr. 30, 2012, (87 pages).
U.S. Appl. No. 13/459,716, filed Apr. 30, 2012, (63 pages).
U.S. Appl. No. 13/459,761, filed Apr. 30, 2012, (35 pages).
U.S. Appl. No. 13/459,872, filed Apr. 30, 2012, (35 pages).
U.S. Appl. No. 13/459,980, filed Apr. 30, 2012, (35 pages).
U.S. Appl. No. 13/525,576, filed Jun. 18, 2012, (87 pages).
U.S. Appl. No. 13/529,182, filed Jun. 21, 2012, (24 pages).
U.S. Appl. No. 13/534,101, filed Jun. 27, 2012, (85 pages).
U.S. Appl. No. 13/601,864, filed Aug. 31, 2012, (23 pages).
U.S. Appl. No. 13/601,898, filed Aug. 31, 2012, (28 pages).
Canadian Office Action dated Jun. 12, 2014, issued in Canadian Application No. 2,818,720, (3 pages).
Canadian Office Action dated Jun. 12, 2014, issued in Canadian Application No. 2,821,772, (2 pages).
Canadian Office Action dated Jun. 19, 2014, issued in Canadian Application No. 2,821,814, (3 pages).
Canadian Office Action dated Jun. 2, 2014, issued in Canadian Application No. 2,812,033, (3 pages).
Canadian Office Action dated Jun. 25, 2014, issued in Canadian Application No. 2,812,457, (5 pages).
Canadian Office Action dated Jun. 30, 2014, issued in Canadian Application No. 2,819,839, (3 pages).
Canadian Office Action dated May 13, 2014, issued in Canadian Application No. 2,789,827, (4 pages).
Canadian Office Action dated May 5, 2014, issued in Canadian Application No. 2,803,192, (4 pages).
European Examination Report dated Apr. 11, 2014, issued in European Application No. 12182612.7, (5 pages).
European Examination Report dated Apr. 16, 2014, issued in European Application No. 11192713.3, (7 pages).
European Examination Report dated Jun. 2, 2014, issued in European Application No. 12166142.5, (4 pages).
European Examination Report dated Jun. 3, 2014, issued in European Application No. 12172458.7, (5 pages).
Final Office Action dated Apr. 11, 2014, issued in U.S. Appl. No. 13/447,704, (18 pages).
Final Office Action dated Jul. 2, 2014, issued in U.S. Appl. No. 13/534,101, (20 pages).
Final Office Action dated Mar. 26, 2014, issued in U.S. Appl. No. 13/564,697, (9 pages).
Office Action dated Apr. 11, 2014, issued in U.S. Appl. No. 13/572,232, (38 pages).
Office Action dated Apr. 18, 2014, issued in U.S. Appl. No. 13/524,678, (29 pages).
Office Action dated Apr. 21, 2014, issued in U.S. Appl. No. 13/601,736, (33 pages).
Office Action dated Jun. 11, 2014, issued in U.S. Appl. No. 13/563,182, (12 pages).
Office Action dated Jun. 18, 2014, issued in U.S. Appl. No. 13/601,898, (27 pages).
Office Action dated Mar. 14, 2014, issued in U.S. Appl. No. 13/569,000, (25 pages).
Office Action dated Mar. 26, 2014, issued in U.S. Appl. No. 13/548,469, (46 pages).
Office Action dated May 15, 2014, issued in U.S. Appl. No. 13/482,705, (19 pages).
Office Action dated May 2, 2014, issued in U.S. Appl. No. 13/459,301, (25 pages).
Office Action dated May 21, 2014, issued in U.S. Appl. No. 13/485,723, (18 pages).
Canadian Office Action in Canadian Application No. 2,816,754, dated Jan. 27, 2015, 3 pages.
Related Publications (1)
Number Date Country
20130314331 A1 Nov 2013 US