IP Library Patent Application 12118047
Patent Application
App. No. 12/118,047

User-Defined Enablement Protocol

Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US None
App. No.
12/118,047
Abstract

A user interface method is disclosed. For a particular interface, 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.

Claims (33)

1 . 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 id function by substantially reproducing said enablement protocol in the absence of spatial or temporal indication of at least a portion of said enablement protocol.

2 . A method according to claim 1 , wherein said enablement protocol comprises a single touch at a user-defined location on a touch-sensitive area of an interface.

3 . A method according to claim 1 , wherein said enablement protocol comprises multiple sequential or simultaneous touches at user-defined locations on a touchsensitive area of an interface.

4 . A 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 operatively associated with said electronic device; and

ii. recording and retaining said enablement protocol of said function, such that a user enables said function by substantially reproducing said enablement protocol in the absence of spatial or temporal indication of at least a portion of said enablement protocol.

5 . A user interface method according to claim 1 , wherein a user enables said function by substantially reproducing said enablement protocol in the absence of any spatial or temporal indication of said enablement protocol.

6 . A method for user-defined 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.

7 . 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 enablement protocol includes at least one user-defined touch of said interface;

ii. assigning said function to the recorded enablement protocol; 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.

8 . A method for user-defined 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 spatial or temporal indication of where at least a portion of said enablement protocol is to be received to execute or enable said function.

9 . A user interface method according to claim 2 , wherein said enablement protocol comprises one or more of 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.

10 . A method according to claim 6 , wherein said interface is without any spatial or temporal indication of where said enablement protocol is to be received to execute or enable said function.

11 . A method according to claim 2 , wherein said enablement protocol comprises a plurality of user-defined touches, wherein said function is enabled when user input meets a predefined number of spatial or temporal indications of said enablement protocol.

12 . 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 protocol including one or more user-defined touches on or near said touch-sensitive area, there being no spatial or temporal indication to said user of at least a portion of said enablement protocol.

13 . 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 userdefined 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 protocol, said enablement protocol additionally requires detection of an additional touch parameter.

14 . A user interface method according to claim 13 , wherein said additional parameter includes one or more of touch movement, direction of touch, timing or rhythm between touches, force of touch, number of sequential or simultaneous touches, and shape or change of shape of touch.

15 . A user interface method according to claim 14 , wherein said additional parameter includes the change of shape of a touch in the vertical and/or horizontal planes on approach or withdrawal of said touch.

Assignments (5)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Feb 7, 2013
From: RPO PTY LTD
To: TRINITY CAPITAL INVESTMENT LLC
Reel/Frame 029770/0739 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Feb 7, 2013
From: TRINITY CAPITAL INVESTMENT LLC
To: ZETTA RESEARCH AND DEVELOPMENT LLC - RPO SERIES
Reel/Frame 029770/0778 →
REASSIGNMENT AND RELEASE OF IP SECURITY INTEREST Recorded Aug 2, 2012
From: BRIDGE BANK, NATIONAL ASSOCIATION
To: RPO PTY LTD
Reel/Frame 028737/0963 →
SECURITY AGREEMENT Recorded Aug 17, 2010
From: RPO PTY LTD
To: BRIDGE BANK, NATIONAL ASSOCIATION
Reel/Frame 024838/0948 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jul 23, 2008
From: ATKINS, GRAHAM ROY; MAXWELL, IAN ANDREW
To: RPO PTY LIMITED
Reel/Frame 021279/0291 →