# US 2014/0195287 A1 · Gesture based electronic signature > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 2014/0195287 A1 - Document ID: US20140195287A1 - Status: Published application - Kind: A1 - Application number: 12/545,553 - Filed: 2009-08-21 - Published: 2014-07-10 - Earliest claimed: 2009-08-21 - Inventors: Christopher Ian Fraser - Web page: https://patentgrep.com/patent/US20140195287A1 ## CPC - G06F 3/04883: for inputting data by handwriting, e.g. gesture or text - G06F 3/017: {Gesture based interaction, e.g. based on a set of recognized hand gestures (interaction based on gestures traced on a digitiser G06F3/04883)} - G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N) ## Abstract A business process management application provides a gesture based signature, and approval mechanism that associates a reply or assent from a remote device with the business process that sent it, thus providing assurances that the resulting approval or disapproval was properly obtained and records the reply for future accountability. A context identifier indicative of the business process that initiated the interactive request for action (action typically being approval, disapproval or acknowledgment) is generated, encoded to discourage tampering, and appended to the interactive request sent to the remote device. The reply received in response to the interactive request thus bears the context identifier allowing the received reply to be correlated to the business process that initiated it and stored for providing an audit trail. ## Claims ### Claim 1 A computer-implemented method comprising: performing by a business process management application executed by at least one electronic processor the following: determining an action of a business process to be completed at a remote device instead of at a device within a local business process context, the business process executed within the local business process context, and wherein the remote device lacks direct computational access to the local business process context; generating a context identifier, the context identifier corresponding to the business process context and the action; generating an email and appending the context identifier to the email, the email configured to request approval for an requested action of the business process; transmitting the email to the remote device; receiving a reply to the email from the remote device, the reply including the context identifier and a gesture-based signature, the reply comprising a reply email indicating approval of the requested action, correlating the received reply with the email using the context identifier and the gesture-based signature; and marking the action complete. ### Claim 2 (depends on 1) The method of claim 1, wherein each business process further defines a series of actions and exchanges, the actions defining a task for completion, and the exchanges defining assent to commencement or completion of an action in the task via the interactive request. ### Claim 3 (depends on 1) The method of claim 1 further comprising encoding, by the business process management application, the context identifier such that values in the context identifier are transformed. ### Claim 4 (depends on 1) The method of claim 1 wherein the context identifier includes a task ID, an action ID, and a process ID, the action ID denoting the action, further comprising: incrementing, by the business process management application, the action ID upon resolution of the action; incrementing, by the business process management application, the task ID upon completion of the task; and identifying, by the business process management application, a new process ID upon commencement of a new business process. ### Claim 5 (depends on 1) The method of claim 1 wherein the business process context defines a set of computing entities coupled so as to maintain process independence and common storage such that each of multiple business processes operate distinct from other business processes and each is accessible from within the context, such that each business process corresponds to at least one executable entity. ### Claim 6 (depends on 1) The method of claim 1 further comprising maintaining, by the business process management application, a repository of context identifiers, the repository storing data for reconciling received replies with a process, task and action to which the respective reply corresponds. ### Claim 7 (depends on 6) The method of claim 6 wherein the context identifier includes a task ID, action ID, and a process ID, such that: the task ID indicates a task; the action ID indicates the action; and the process ID denotes a business process. ### Claim 8 (depends on 7) The method of claim 7 wherein the interactive request corresponds to the action, further comprising: decoding, by the business process management application, the context identifier to determine the task ID, the action ID and the process ID; determining, by the business process management application and using the action ID, the action; identifying, by the business process management application and using the process ID, the business process corresponding to the task; and advancing, by the business process management application, the action ID. ### Claim 9 (depends on 8) The method of claim 8 further comprising, upon completion of all steps within the task, incrementing, by the business process management application, the task ID and resetting the action ID for initiation of a subsequent task in the business process. ### Claim 10 (depends on 3) The method of claim 3 wherein the encoding is configured to obfuscate the context identifier, but is not configured to perform certificate exchanges and third party authentication. ### Claim 11 (canceled) ### Claim 12 (canceled) ### Claim 13 An apparatus comprising: a processor and a memory, the processor configured to execute a business process management application by executing business processes; at least one business process configured to: determine an action of a business process to be completed at a remote device instead of at a device within a local business process context, the business process executed within the local business process context, and wherein the remote device lacks direct computational access to the local business process context; generate a context identifier, the context identifier corresponding to the business process context and the action, and generate an email and append the context identifier to the email, the email configured to request approval for an requested action of the business process; a network interface configured to: transmit the email to the remote device, and receive a reply to the email, the reply including the context identifier and a gesture-based signature, the reply comprising a reply email indicating approval of the requested action; and a repository having information for correlating, using the context identifier and the gesture-based signature, the received reply with the email, the business process management application further configured to mark the action complete. ### Claim 14 (depends on 13) The apparatus of claim 13 wherein each business process in the memory of the business process management application defines a series of actions and exchanges, the actions defining a task for completion, and the exchanges defining assent to commencement or completion of an action within the task via the interactive request. ### Claim 15 (depends on 14) The apparatus of claim 14 wherein the context identifier includes a task ID, an action ID, and a process ID, the action ID denoting the action, the processor further configured to: increment the action ID upon resolution of the action associated with the reply; increment the task ID upon completion of the task; and identify a new process ID upon commencement of a new business process. ### Claim 16 (depends on 14) The apparatus of claim 14 wherein the business process context defines a set of computing entities coupled so as to maintain process independence and common storage such that each of multiple business processes operate distinct from other business processes and each is accessible from within the business process context, such that each business process corresponds to at least one executable entity. ### Claim 17 (depends on 14) The apparatus of claim 14 wherein the business process management application is configured to maintain the repository. ### Claim 18 (depends on 17) The apparatus claim 17 wherein the interactive request corresponds to a step within a task, and further comprising: a decoder module configured for decoding the context identifier to determine the task ID, the action ID and the process ID, and wherein the at least one business process is further configured to: determining, using the action ID, the action associated with the received reply; identifying, from the process ID, the business process corresponding to the task; and advancing the action ID. ### Claim 19 (depends on 21) The apparatus of claim 21 wherein the encoder module is configured to obfuscate the context identifier, but is not configured to perform certificate exchanges and third party authentication. ### Claim 20 A computer program on a non-transitory computer readable storage medium encoded as a set of processor based instructions that, upon execution by a processor, cause the processor to: determine an action of a business process to be completed at a remote device instead of at a device within a local business process context, the business process executed within the local business process context, and wherein the remote device lacks direct computational access to the local business process context generate a context identifier, the context identifier corresponding to the a-business process context and the action; generate an email and append the context identifier to the email, the email configured to request approval for an requested action of the business process; transmit the email to the remote device; receive a reply to the email, the reply including the context identifier and a gesture-based signature, the reply comprising a reply email indicating approval of the requested action; correlate, using the context identifier and the gesture-based signature, the received reply with the email and a business process that initiated the email; and mark the action complete. ### Claim 21 (depends on 13) The apparatus of claim 13, further comprising an encoder module configured to obfuscate the context identifier such that values in the context identifier are transformed. ### Claim 22 (depends on 20) The computer program of claim 20 further comprising instructions that cause a processor to obfuscate the context identifier such that values in the context identifier are transformed.