Case 2:20-cv-00035-JRG Document 1-1 Filed 02/12/20 Page 1 of 17 PageID #: 9
`Case 2:20-cv-00035-JRG Document 1-1 Filed 02/12/20 Page 1 of 17 PageID #: 9
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`EXHIBIT A
`
`
`
`EXHIBIT A
`
`
`
`

`

`Case 2:20-cv-00035-JRG Document 1-1 Filed 02/12/20 Page 2 of 17 PageID #: 10
`
`USOO9696847B2
`
`(12) United States Patent
`Atkins et al.
`
`(10) Patent No.:
`(45) Date of Patent:
`
`US 9,696,847 B2
`*Jul. 4, 2017
`
`(54) USER-DEFINED GESTURE ENABLEMENT
`PROTOCOLS FOR TOUCH INPUT DEVICE
`
`(71) Applicant: ZETTA RESEARCH AND
`DEVELOPMENT LLC-RPO
`SERIES, Wilmington, DE (US)
`
`(72) Inventors: Graham Roy Atkins, Kaleen (AU);
`Ian Andrew Maxwell, New South
`Wales (AU)
`(73) Assignee: ZETTA RESEARCH AND
`DEVELOPMENT LLC-RPO
`SERIES, Wilmington, DE (US)
`Subject to any disclaimer, the term of this
`patent is extended or adjusted under 35
`U.S.C. 154(b) by 0 days.
`This patent is Subject to a terminal dis
`claimer.
`
`(*) Notice:
`
`(21) Appl. No.: 15/056,015
`(22) Filed:
`Feb. 29, 2016
`(65)
`Prior Publication Data
`US 2016/O253O32 A1
`Sep. 1, 2016
`
`Related U.S. Application Data
`(63) Continuation of application No. 13/473.961, filed on
`May 17, 2012, now Pat. No. 9,280.279, which is a
`continuation of application No. 12/118,047, filed on
`May 9, 2008, now abandoned.
`Foreign Application Priority Data
`
`(30)
`
`May 11, 2007 (AU) ................................ 2007902517
`May 11, 2007 (AU) ................................ 2007902519
`
`91
`
`
`
`(2006.01)
`(2013.01)
`
`(51) Int. Cl.
`G06F 3/04
`G06F 3/0488
`(52) U.S. Cl.
`CPC .......... G06F 3/0416 (2013.01); G06F 3/0488
`(2013.01); G06F 3/048.83 (2013.01)
`(58) Field of Classification Search
`None
`See application file for complete search history.
`
`(56)
`
`References Cited
`
`U.S. PATENT DOCUMENTS
`
`6,163,616 A * 12/2000 Feldman ............... GO6F 3/O395
`382,115
`8,311,530 B2 * 11/2012 Kornilovsky ......... G06F 3,0362
`345,173
`2004/O155870 A1* 8, 2004 Middleton ............. G04G 21.08
`345,173
`2005, 0122315 A1* 6, 2005 Chalk ................... G06F 1, 1626
`345,173
`2005/0210417 A1* 9, 2005 Marvit .................. G06F 1, 1613
`T15,863
`2007,0262964 A1* 11/2007 Zotov ................... G06F 3/0416
`345,173
`
`(Continued)
`Primary Examiner — Ryan A Lubit
`(74) Attorney, Agent, or Firm — Mattingly & Malur, PC
`
`ABSTRACT
`(57)
`A user interface method is disclosed. For a particular inter
`face, such as a touch input device, the method involves
`defining an enablement protocol for a function and recording
`and retaining the enablement protocol of said function, Such
`that a user enables the function by Substantially reproducing
`the enablement protocol in the absence of spatial or temporal
`indication of at least a portion of the enablement protocol.
`13 Claims, 7 Drawing Sheets
`
`

`

`Case 2:20-cv-00035-JRG Document 1-1 Filed 02/12/20 Page 3 of 17 PageID #: 11
`
`US 9,696,847 B2
`Page 2
`
`(56)
`
`References Cited
`
`U.S. PATENT DOCUMENTS
`
`2008/0012835 A1
`
`1/2008 Rimon .................... G06F 3/038
`345,173
`2008/0094370 A1* 4/2008 Ording ................ G06F 3/04883
`345,173
`2008/O168403 A1* 7/2008 Westerman ......... G06F 3/04883
`T15,863
`2008/0204428 A1* 8, 2008 Pierce ................... G06F 3/0202
`345,174
`
`* cited by examiner
`
`

`

`Case 2:20-cv-00035-JRG Document 1-1 Filed 02/12/20 Page 4 of 17 PageID #: 12
`
`U.S. Patent
`
`US 9,696,847 B2
`
`
`
`

`

`Case 2:20-cv-00035-JRG Document 1-1 Filed 02/12/20 Page 5 of 17 PageID #: 13
`
`U.S. Patent
`
`Jul. 4, 2017
`
`Sheet 2 of 7
`
`US 9,696,847 B2
`
`
`
`o
`
`o
`
`o
`
`S
`
`S.
`
`

`

`Case 2:20-cv-00035-JRG Document 1-1 Filed 02/12/20 Page 6 of 17 PageID #: 14
`
`U.S. Patent
`
`Jul. 4, 2017
`
`Sheet 3 of 7
`
`US 9,696,847 B2
`
`S.
`
`?h
`-
`n
`CC
`Z
`
`N
`
`
`
`

`

`Case 2:20-cv-00035-JRG Document 1-1 Filed 02/12/20 Page 7 of 17 PageID #: 15
`
`U.S. Patent
`
`Jul. 4, 2017
`
`Sheet 4 of 7
`
`US 9,696,847 B2
`
`
`
`

`

`Case 2:20-cv-00035-JRG Document 1-1 Filed 02/12/20 Page 8 of 17 PageID #: 16
`Case 2:20-cv-OOO35-JRG Document 1-1 Filed 02/12/20 Page 8 of 17 PageID #: 16
`
`US. Patent
`
`Jul. 4, 2017
`
`Sheet 5 of 7
`
`US 9,696,847 B2
`
`<
`l\
`.93
`u.
`
`g
`
`co
`l\
`.93
`u.
`
`E
`
`0
`l\
`.93
`LL
`
`D
`l\
`.23
`u.
`(__
`
`N
`N
`
`E
`
`E
`
`E
`
`E
`
`E
`
`2
`
`<
`(D
`.23
`LL
`
`m
`CO
`.23
`U.
`
`0
`CO
`.95
`U.
`
`D
`CO
`.93
`U.
`
`——)
`
`————>
`
`o‘)
`
`<——
`
`6 51 a 6
`
`61
`
`61
`
`61
`
`61
`
`

`

`Case 2:20-cv-00035-JRG Document 1-1 Filed 02/12/20 Page 9 of 17 PageID #: 17
`
`U.S. Patent
`
`Jul. 4, 2017
`
`Sheet 6 of 7
`
`US 9,696,847 B2
`
`
`
`

`

`Case 2:20-cv-00035-JRG Document 1-1 Filed 02/12/20 Page 10 of 17 PageID #: 18
`
`U.S. Patent
`
`Jul. 4, 2017
`
`Sheet 7 of 7
`
`US 9,696,847 B2
`
`O
`-
`n
`CC
`Z
`
`
`
`O
`O)
`O)
`
`?
`O)
`.9)
`
`

`

`Case 2:20-cv-00035-JRG Document 1-1 Filed 02/12/20 Page 11 of 17 PageID #: 19
`
`1.
`USER-DEFINED GESTURE ENABLEMENT
`PROTOCOLS FOR TOUCH INPUT DEVICE
`
`US 9,696,847 B2
`
`CROSS-REFERENCE TO RELATED
`APPLICATIONS
`
`This application is a continuation of U.S. patent applica
`tion Ser. No. 13/473,961, filed May 17, 2012, which is a
`continuation of U.S. patent application Ser. No. 12/118,047
`filed on May 9, 2008, now abandoned, which claims priority
`under the Paris Convention to Australian Provisional Patent
`Application No. 2007902519 filed on May 11, 2007 and
`Australian Provisional Patent Application No 2007902517
`filed on May 11, 2007, the contents of both of which are
`incorporated herein by reference.
`
`10
`
`15
`
`FIELD OF THE DISCLOSURE
`
`The present disclosure relates to user-defined enablement
`protocols for electronic devices. The disclosure has been
`developed primarily for providing an enhanced security
`means for enabling or executing functions of electronic
`devices through an interface Such as a touch-sensitive dis
`play, and will be described hereinafter with reference to this
`application. However it will be appreciated that the disclo
`sure is not limited to this particular field of use.
`
`25
`
`BACKGROUND OF THE DISCLOSURE
`
`Any discussion of the prior art throughout the specifica
`tion should in no way be considered as an admission that
`such prior art is widely known or forms part of the common
`general knowledge in the field.
`Electronic devices often require some form of enablement
`protocol to activate them or to enable a particular function.
`For example to activate a mobile phone or to log on to a
`computer system a user may need to enter an alphanumeric
`code e.g. “123. A known drawback here is that if an
`unauthorised person learns the alphanumeric code, it is
`simple for them to activate the mobile phone or log in to the
`computer system. If the device is equipped with a touch
`screen so that the alphanumeric keys can be shown on a
`display, an additional level of security is available in that the
`locations of the keys can be scrambled either before or
`during entry of the code, making it more difficult for another
`person to learn the code by observation. However once the
`code is known, it is once again simple for an unauthorised
`person to enter it. US Patent Publication No. 2008/00823015
`discloses a non-alphanumeric method for unlocking an
`electronic device whereby direction keys are used to traverse
`a path through a displayed maze, and the device is unlocked
`if the path matches a path preset by the user. Once again,
`there is no security once the unlock code (i.e. the path) is
`known, and the restriction to using direction keys limits the
`range and complexity of possible enablement protocols.
`Compared with a keyboard with hard keys, touch screens
`offer a much greater range of enablement protocols for an
`electronic device. Apart from the well-known touch to
`select operation mode where a user selects or enables a
`function by touching a displayed icon, a user can also
`provide gestural input in the form of one or more Swipes
`or taps for example. US Patent Publication No. 2007/
`O150842 for instance discloses a method for unlocking an
`electronic device whereby a person touches a displayed
`image and moves it along an indicated path. Besides unlock
`ing a device, many other functions can be enabled with
`gestures on a touch screen. US Patent Publication No.
`
`30
`
`35
`
`40
`
`45
`
`50
`
`55
`
`60
`
`65
`
`2
`2006/0026535 for instance discloses various mechanisms
`for interacting with one or more GUI (Graphical User
`Interface) elements based on a user interface mode and in
`response to one or more detected touches. The graphical
`elements that may be activated include a virtual scroll wheel,
`a virtual keyboard, a toolbar and a control panel. Functions
`applied include rotating, translating or re-sizing a displayed
`image, and scrolling through a list. U.S. Pat. Nos. 5,825.352
`and 5,943,043 disclose various two finger gestural inputs
`that emulate mouse functions, while US Patent Publication
`No. 2007/0177803 discloses the possibility of allowing a
`user to assign an arbitrary function to a predetermined
`gesture. However in all these cases the user is either guided
`by displayed material or the gesture is predetermined, so
`there is limited opportunity for altering the functionality
`provided by the device or the mechanisms by which those
`functions are enabled.
`The present disclosure overcomes or ameliorates at least
`one of the disadvantages of the prior art, and provides a
`useful alternative.
`
`SUMMARY OF THE DISCLOSURE
`
`In a first broad aspect, the present disclosure provides a
`user interface method, comprising the steps of
`i. defining an enablement protocol for a function; and
`ii. recording and retaining said enablement protocol of said
`function, such that a user enables said function by Substan
`tially reproducing said enablement protocol in the absence
`of spatial or temporal indication of at least a portion of said
`enablement protocol.
`In one embodiment, defining the enablement protocol for
`a function comprises user-engagement with an interface,
`which comprises rises one or more touches or near touches
`of a touch screen. However, it will be appreciated that a user
`may also define an enablement protocol by engaging other
`types or configurations of interfaces, for example a rectan
`gular frame Surrounding a space wherein adjacent borders of
`the frame include optical emitters and the opposing borders
`include photo-detectors, i.e. essentially a touch-sensitive
`screen apparatus minus the actual touch Surface. Alterna
`tively, or additionally, the enablement protocol may com
`prise Voice recognition of pre-defined commands (audible
`instructions), or the tracking of eye movements, or some
`other type of gesture of one or more parts of the human body.
`Whatever form a user's enablement protocol takes, the user
`will preferably define or record that protocol in the same
`form. For example if the enablement protocol is a sequence
`of touches with a particular rhythm at the top left corner of
`a touch screen, the user will usually define or record that
`protocol by actually performing the sequence of touches.
`Alternatively the user could define or record the protocol by
`other means, such as a spoken or typed description.
`In a second aspect, the present disclosure provides user
`interface method, comprising the steps of:
`i. defining an enablement protocol for a function of an
`electronic device, said enablement protocol comprising at
`least one user-defined touch on a touch-sensitive area opera
`tively associated with said electronic device; and
`ii. recording and retaining said enablement protocol of said
`function, such that a user enables said function by Substan
`tially reproducing said enablement protocol in the absence
`of spatial or temporal indication of at least a portion of said
`enablement protocol.
`It will be appreciated that the enablement protocol which
`comprises a plurality of spatial and temporal data points (i.e.
`touches and/or gestures) may be selected from one or more
`
`

`

`Case 2:20-cv-00035-JRG Document 1-1 Filed 02/12/20 Page 12 of 17 PageID #: 20
`
`US 9,696,847 B2
`
`3
`of the following non-exhaustive list of spatial or temporal
`indications: a simple touch, movement of touch, direction of
`touch, timing or rhythm between touches, force of touch,
`number of sequential or simultaneous touches, position of
`touch or shape or change of shape of touch, etc.
`According to a third aspect the disclosure provides a
`method for userdefined enablement of a function through an
`interface, said method comprising the steps of:
`i. recording an enablement protocol comprising at least one
`user-defined touch of said interface;
`ii. assigning said function to said enablement protocol; and
`iii. executing or enabling said function when one or more
`touches received on or near said interface Substantially
`coincide with the recorded enablement protocol, wherein
`said interface is without spatial or temporal indication of
`where at least a portion of said enablement protocol is to be
`received to execute or enable said function.
`It will be appreciated that the function can be enabled by
`one or more touches, and that the user is required to provide
`the enablement protocol without spatial or temporal indica
`tion of where the enablement protocol should be received to
`execute or enable the function. In one aspect, the enablement
`protocol may comprise a plurality of user-defined touches of
`the interface, and at least one spatial or temporal indication
`of the plurality of the user-defined touches of the enablement
`protocol is not shown or displayed on the interface. In Such
`embodiments, for example, the enablement protocol may
`comprise a Swipe of a touch screen with a 1 second dwell
`time at the conclusion of the Swipe. The screen may only
`show where the swipe should be received and not indicate
`that the user must hold their finger down at the end of the
`Swipe for 1 second. In this case only one of the two
`spatial/temporal indications is shown to the user.
`In another somewhat related aspect, the function may be
`enabled when the user input meets a predefined number of
`spatial or temporal indications. For example, the enablement
`protocol may comprise a partial Swipe of a touch screen, and
`then a 1 second dwell time, and then a further partial swipe,
`i.e. swipe--dwell--swipe. The function may be enabled if
`only two out of these three inputs are received, e.g. Swipe--
`dwell, or swipe--swipe, or dwell--swipe.
`According to a fourth aspect the present disclosure pro
`vides a method for enablement of a function through an
`interface, said method comprising the steps of:
`i. recording an enablement protocol Substantially according
`to a pre-defined enablement protocol, wherein said enable
`ment protocol includes at least one user-defined touch of
`said interface;
`ii. assigning said function to the recorded enablement pro
`tocol; and
`iii. executing or enabling said function when one or more
`touches received on or near said interface Substantially
`coincide with said recorded enablement protocol, wherein
`said interface is without spatial or temporal indication of
`where at least a portion of said enablement protocol is to be
`received to execute or enable said function.
`In this aspect, the user may be presented with a choice of
`Suggested enablement protocols from which they can choose
`and Substantially mimic, thereby recording their own spe
`cific and unique enablement protocol. The user can then
`assign a function to their unique recorded enablement pro
`tocol and execute or enable the function when they input an
`enablement protocol that substantially coincides with the
`recorded enablement protocol, wherein the interface is with
`out spatial or temporal indication of where at least a portion
`of the enablement protocol is to be received to execute or
`enable the function.
`
`4
`According to a fifth aspect the present disclosure provides
`a method for userdefined enablement of a function through
`an interface, said method comprising the steps of
`i. recording an enablement protocol comprising one or more
`user-defined touches of said interface; and
`ii. assigning said function to said enablement protocol,
`wherein in response to a user's request for execution or
`enablement of said function the user is prompted to perform
`said enablement protocol, wherein said function is executed
`or enabled when one or more touches received on or near
`said interface substantially coincide with the recorded
`enablement protocol, wherein said interface is without spa
`tial or temporal indication of where at least a portion of said
`enablement protocol is to be received to execute or enable
`said function.
`In this aspect the enablement protocol effectively acts as
`a gatekeeper or security password control over a particular
`function. Essentially, the user records an enablement proto
`col, assigns a function to the enablement protocol and then
`when wishing to execute or enable the function is prompted
`to input their unique enablement protocol which, if coincid
`ing with the recorded enablement protocol, allows the func
`tion to be executed or enabled.
`Prior art devices typically require touches or near touches
`within one or more pre-existing or specified areas to enable
`a particular pre-defined function. For instance, a simple
`keypad on a touch display provides alphanumeric material at
`specific predefined locations, and touches or near touches at
`these locations must be accomplished in a specific sequence
`to enable the function, e.g. to activate a device containing
`the touch display. However, the user-defined interface
`method according to the present disclosure has no Such
`spatial or temporal indication to a user of where touches or
`near touches should be received to enable the function,
`thereby allowing a user to have complete freedom in regard
`to defining how the functionality of an electronic device
`associated with the interface is enabled by touch.
`To explain, a simple embodiment may involve the acti
`vation of a personal electronic device such as PDA or mobile
`phone. Normally a security code (optionally user-defined) is
`required to enable the device. This security code is normally
`a series of alphanumeric keystrokes either on a keypad
`separate from the display or on the display itself.
`In one embodiment the present disclosure envisages no
`Such spatial or temporal indication to a user. Rather a user
`can define a security code or enablement protocol on the
`device or indeed on an apparatus separate from but opera
`tively associated with the device by defining one or more
`touches to enable the aforementioned function. One such
`touch may be for instance the touch of a thumb in the upper
`right hand corner of the screen or other touch sensitive area,
`or both. Alternatively, several touches at user-defined loca
`tions on the screen may enable the device. In another
`embodiment, a sequence of touches either at the user-defined
`locations or indeed anywhere on the screen can enable the
`functionality required. The timing or protocol (temporal
`sequence) of these touches must then be recreated to enable
`said function. In more complex arrangements both the
`spatial and temporal nature of the touches are examined to
`ensure that they meet the user-defined enablement protocol.
`In further arrangements, different types of touching bodies
`could enable different functions by performing otherwise
`identical enablement protocols. For example a Swipe down
`one side of a touch screen with a stylus enables function A,
`while the same swipe with a finger enables function B. This
`embodiment expands the range of functions that can be
`
`5
`
`10
`
`15
`
`25
`
`30
`
`35
`
`50
`
`55
`
`60
`
`65
`
`40
`
`45
`
`

`

`Case 2:20-cv-00035-JRG Document 1-1 Filed 02/12/20 Page 13 of 17 PageID #: 21
`
`US 9,696,847 B2
`
`10
`
`15
`
`6
`Touches or near touches may be detected by any known
`touch sensing technology including analogue resistive, Sur
`face capacitive, Surface acoustic wave, projected capacitive,
`optical and bending wave technologies, bearing in mind that
`some touch technologies are better suited than others for
`distinguishing multiple simultaneous touches, should these
`be part of an enablement protocol. Enablement protocols
`that include touch shape or change of shape will generally
`require high spatial resolution, such as may be offered by
`optical touch detection technologies disclosed in U.S. Pat.
`Nos. 5,914,709 and 7,352.940. However any known touch
`technology, including those mentioned above, can be
`applied with the present disclosure, with enablement proto
`cols defined within the limitations of that technology. Cer
`tain touch technologies, e.g. resistive and bending wave,
`require a direct touch for activation, whereas other touch
`technologies, such as optical touch where a sheet of light is
`established in front of a display, can also sense an object
`hovering close to the display. The principles of the present
`disclosure apply whether the touch sensitive device is acti
`vated by a touch or a near touch of an interface.
`In a further aspect the present disclosure provides a user
`interface device comprising: a touch sensitive area adapted
`to detect touches; a display device to display one or more
`functions; and a storage medium including a user-defined
`enablement protocol for enabling functions operatively
`associated with said display device, said enablement proto
`col including one or more user-defined touches on or near
`said touchsensitive area, there being no spatial or temporal
`indication to said user of at least a portion of said enable
`ment protocol.
`While it is preferred that the enablement protocol be
`performed on the display device, this is not absolutely
`necessary. One could envisage the enablement protocol
`being applied to a touch-sensitive area or protocol appara
`tus separate from the display device. The user would simply
`follow the defined enablement protocol and the protocol
`apparatus then communicates with the display device e.g.
`PDA or computer to enable the function held by that device.
`Indeed the function itself may be held by a third device, such
`that instigation of the enablement protocol, the display
`device and the various functions to be applied to the display
`device are all held separately.
`In another aspect of the present disclosure there is pro
`vided a user-defined interface method, comprising the steps
`of:
`i. defining for an electronic device an enablement protocol
`for a function of said device
`whereby said enablement protocol comprises one or more
`user-defined touches,
`ii. retaining said enablement protocol of said function, and
`iii. enabling said function by said one or more user-defined
`touches wherein, if a user is provided with spatial or
`temporal indication for a portion of said enablement proto
`col, said enablement protocol additionally requires detection
`of an additional touch parameter.
`Preferably the additional parameter required for the
`enablement protocol would include one or more of touch
`movement, direction of touch, timing or rhythm between
`touches i.e. temporal sequence, force of touch, number of
`sequential or simultaneous touches, shape and/or change of
`shape of touch including in different planes e.g. vertical and
`horizontal, on approach or withdrawal.
`To explain, Some devices may have a spatial or temporal
`indication for a portion of an enablement protocol. For
`instance, a mobile phone may have locations shown on the
`display that must be pressed in a certain sequence for partial
`
`5
`performed with a limited range of gestures, or alternatively
`provides an additional security feature.
`It can be seen then that any touch screen input device can
`have a series of functions which may only be enabled by the
`user who defined the aforementioned enablement protocol,
`since there is no spatial or temporal indication to assist
`another party who may wish to enable the aforementioned
`functions.
`In another embodiment, enablement protocols may be
`linked to the profiles of multiple users such that a single
`device may be enabled according to the profile of a user who
`defined a specific enablement protocol.
`As an example, user A defines touches in the upper and
`lower left hand corners of a display to initiate a device.
`When touches are provided in those upper and lower corners
`the device is activated according to user A's profile. User B
`may have an entirely separate profile and may wish the
`device to be set up according to their specific needs. They
`therefore define an enablement protocol different from that
`ofuser A; not only will other parties not be able to access the
`device without knowing the enablement protocol of either
`party, but once user B initiates their particular enablement
`protocol the device will be activated according to their
`specific profile.
`Indeed even if another person knew some aspects of an
`enablement protocol. Such as the locations to be touched or
`the particular gesture, other aspects such as the rhythm,
`pattern or sequence of the touches or their touch signature
`e.g. finger shape, will be different and therefore they will not
`be able to replicate the enablement protocol.
`The disclosure as described is particularly useful for users
`with some form of physical handicap that may prevent them
`from using conventional touch screen devices. By providing
`complete freedom to an individual user to define enablement
`protocols for the various functions of a device, they may
`define the touches in terms of spatial and temporal param
`eters that they can easily replicate.
`Since there is no spatial or temporal indication of the
`enablement protocol to a user, even a simple single touch or
`near touch at a specific location may be sufficient as an
`enablement protocol with enhanced security. This is to be
`distinguished from known fingerprint readers, which require
`a direct touch within a specific area.
`While enablement by a single touch or near touch is
`possible with the present disclosure it is generally preferred
`that two or more touches or near touches be used to define
`the enablement protocol. Touches and near touches may be
`detected in several ways, including a touch-down, move
`ment of touch, direction of touch, timing or rhythm (proto
`col) between touches i.e. temporal sequence, force of touch,
`number of sequential or simultaneous touches, position of
`touch, and shape or change of shape of touch approaching,
`contacting or leaving the touch sensitive area.
`One or more of these detection mechanisms may be used
`to complete the enablement protocol. For instance, if the
`touch location is correct but the shape of the touch is
`incorrect the protocol will not be satisfied (i.e. there is not
`substantial coincidence between the received and the
`recorded protocol) and the associated function will not be
`enabled. Similarly if the timing or rhythm between touches
`is correct but the force applied by those touches is incorrect,
`once again the protocol will not be satisfied. It will be
`appreciated that although only selected touch technologies
`can directly measure the force of an applied touch, certain
`other touch technologies, especially those with high spatial
`resolution, can indirectly measure touch force from defor
`mation of the touch object.
`
`25
`
`30
`
`35
`
`40
`
`45
`
`50
`
`55
`
`60
`
`65
`
`

`

`Case 2:20-cv-00035-JRG Document 1-1 Filed 02/12/20 Page 14 of 17 PageID #: 22
`
`US 9,696,847 B2
`
`7
`enablement of the protocol. One mechanism to complete the
`enablement protocol could be temporal i.e. the locations
`must be pressed in the precise timing and sequence required.
`In one alternative, if spatial and temporal data are provided
`e.g. by flashing of the locations, the size and shape of the 5
`touch may be detected to confirm enablement by an autho
`rised user. This detection of touch size and shape may be
`accomplished not only in the plane of the display or touch
`sensitive area but also in planes above the display e.g. the
`shape of the touch approaching or leaving the touch sensi- 10
`tive area, if the touch sensor can detect near touches. This
`touch signature is virtually impossible to replicate by
`another user and therefore provides a secure individual
`enablement protocol. It will be clear to a person skilled in the
`art that there are various other options available to confirm 15
`enablement.
`Accordingly it can be seen that according to several
`aspects of the present disclosure there is significant flexibil
`ity and security as compared with prior art systems. Unless
`the context clearly requires otherwise, throughout the 20
`description and the claims, the words comprise', 'compris
`ing, and the like are to be construed in an inclusive sense
`as opposed to an exclusive or exhaustive sense; that is to say,
`in the sense of including, but not limited to.
`The skilled person will appreciate that the term coincide, 25
`when used herein and when referring to a touch input being
`compared with a recorded or retained touch input, is meant
`to define that the inputs should substantially correspond. In
`one embodiment, as discussed above, the coincidence is
`substantial overlap in overall touch area, and in another 30
`embodiment may also include one or more other parameters,
`such as dwell time.
`In a further embodiment coincide may refer to a prede
`termined number of matches between the spatial and/or
`temporal data points of the touch or near touch and those of 35
`the enablement protocol.
`It will be appreciated that when referring to touch herein
`the term is also intended to encompass within its scope the
`term near touch.
`In one embodiment the touch-sensitive area is larger than 40
`the area of the display device and contains the display device
`within its borders. Generally, conventional touch-sensitive
`input devices include a display device that is at least as large
`as the touch-sensitive area. In one embodiment the touch
`sensitive area is larger than the display itself and includes the 45
`display device within its borders. This is highly unusual but
`provides advantages over conventional systems, for example
`the opportunity of producing a smaller display with conse
`quent power reduction. Also, by including the touch-sensi
`tive area outside the display, the display itself is not 50
`obscured while input is applied via the touch-sensitive area.
`The touch portions/locations may be located on a first face
`of the touch-sensitive area, generally the display side, and/or
`a second opposite face of the touch-sensitive area. In one
`particular embodiment the touch portions/locations for 55
`enablement of the functions are arranged on the first and
`second opposite faces of the touch-sensitive area in Such a
`way that they can be simultaneously operated by the thumb
`and fingers of a user.
`
`60
`
`BRIEF DESCRIPTION OF DRAWINGS
`
`Preferred embodiments of the disclosure will now be
`described, by way of example only, with reference to the
`accompanying drawings in which:
`FIGS. 1 and 2 illustrate conventional user interface
`devices according to the prior art;
`
`65
`
`8
`FIGS. 3A-3D illustrate a first embodiment of the present
`disclosure;
`FIGS. 4A-4C illustrate a second embodiment of the
`present disclosure;
`FIGS. 5A-5C illustrate a third embodiment of the present
`disclosure.
`FIGS. 6A-6D and 7A-7D illustrate touch signature rec
`ognition according to a fourth embodiment of the present
`disclosure;
`FIG. 8A-8C illustrate a fifth embodiment of the present
`disclosure; and
`FIGS. 9A-9C illustrate a sixth embodiment of the present
`disclosure.
`
`DETAILED DESCRIPTION OF THE
`DISCLOSURE
`
`FIGS. 1 and 2 provide illustrations of prior art function
`ality in conventional devices.
`FIG. 1 shows a mobile phone 10 with an alphanumeric
`keypad 11 and a display 12. In many instances the mobile
`phone can only be enabled when a user-defined security
`code is entered via the alphanumeric keypad 11. Alterna
`tively the alphanumeric keypad may be provided on a
`touch-sensitive display (i.e. a touch screen) but once again
`the conventional device comprises a pre-defined arrange
`ment of the enablement protocol such that if an unauthorised
`user were aware of the code e.g. 123, they could enable the
`device simply by engaging the predefined locations for
`numerals 1, 2 and 3.
`FIG. 2 is an illustration of an automatic teller machine 20
`with a touch sensitive display 21. This technology is similar
`to the mobile phone in FIG. 1, and in this instance various
`functions and spatial locations for enabling those functions
`are clearly defined on the display. The display includes
`indicia 22 describing the functions e.g. withdrawal, deposit
`and account balance, and the spatial locations for those
`functions are defined by the touch portio