# US 10,313,483 B2 · Method and apparatus for providing a dynamic execution environment in network communication between a client and a server > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 10,313,483 B2 - Document ID: US10313483B2 - Status: Granted - Kind: B2 - Application number: 14/754,204 - Filed: 2015-06-29 - Published: 2015-10-22 - Granted: 2019-06-04 - Earliest claimed: 2012-06-06 - Assignees: Synactive, Inc. - Applicants: Synactive, Inc. - Inventors: Thomas Ewe - Web page: https://patentgrep.com/patent/US10313483B2 ## CPC - G06F 8/38: for implementing user interfaces - G06F 9/452: {Remote windowing, e.g. X-Window System, desktop virtualisation (protocols for virtual reality H04L67/131)} - G06F 9/541: {via adapters, e.g. between incompatible applications} - G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N) ## Abstract Example implementations disclosed herein are directed to systems and methods for providing an event-trapping mechanism in a dynamic execution environment. The systems and methods can include creating one or more execution blocks, each associated with a sequence of screen events of a user interface, from a function stored in a script; storing the one or more execution blocks as handlers; and executing the one or more handlers independently from each other, when the associated sequence of screen events for the handler is detected in network traffic. ## Claims ### Claim 1 A computer implemented method for providing an event-trapping mechanism in a dynamic execution environment comprising: creating one or more execution blocks, each associated with a sequence of screen events of a first user interface of a SAP database server, from a function stored in a script; storing the one or more execution blocks as handlers; and executing the one or more handlers independently from each other, when the associated sequence of screen events for the handler is detected in network traffic, to generate from the first user interface, a second user interface comprising the associated sequence of screen events for the handler detected in the network traffic, the second user interface configured for display on a mobile device communicatively coupled to the dynamic execution environment, the second user interface generated through execution of the one or more handlers independently from each other to provide the associated sequence of screen events to the mobile device; wherein the network traffic is traffic between the mobile device and the SAP database server such that the dynamic execution environment is an intermediary monitoring the network traffic; wherein the handlers are stored in a memory of the dynamic execution environment; and wherein the dynamic execution environment is a server communicatively coupled to the SAP database server and the mobile device. ### Claim 2 (depends on 1) The method of claim 1 wherein the sequence of screen events is one or more of an on-screen event, an on-error event or an on-message event. ### Claim 3 (depends on 1) The method of claim 1 wherein an entry event for the function is stored in an event array which associates events with functions. ### Claim 4 (depends on 1) The method of claim 1 wherein the one or more handlers exist in one or more sequences of screen events. ### Claim 5 (depends on 1) The method of claim 1 wherein the script contains goto statements for moving between the one or more handlers. ### Claim 6 (depends on 1) The method of claim 1 wherein the associated sequence of screen events are document object model events. ### Claim 7 A non-transitory computer readable medium storing instructions for providing an event-trapping mechanism in a dynamic execution environment, the instructions comprising: creating one or more execution blocks, each associated with a sequence of screen events of a first user interface of a SAP database server, from a function stored in a script; storing the one or more execution blocks as handlers; and executing the one or more handlers independently from each other, when the associated sequence of screen events for the handler is detected in network traffic, to generate from the first user interface, a second user interface comprising the associated sequence of screen events for the handler detected in the network traffic, the second user interface configured for display on a mobile device communicatively coupled to the dynamic execution environment, the second user interface generated through execution of the one or more handlers independently from each other to provide the associated sequence of screen events to the mobile device; wherein the network traffic is traffic between the mobile device and the SAP database server such that the dynamic execution environment is an intermediary monitoring the network traffic; wherein the handlers are stored in a memory of the dynamic execution environment; and wherein the dynamic execution environment is a server communicatively coupled to the SAP database server and the mobile device. ### Claim 8 (depends on 7) The non-transitory computer readable medium of claim 7 wherein the sequence of screen events is one or more of an on-screen event, an on-error event or an on-message event. ### Claim 9 (depends on 7) The non-transitory computer readable medium of claim 7 wherein an entry event for the function is stored in an event array which associates events with functions. ### Claim 10 (depends on 7) The non-transitory computer readable medium of claim 7 wherein the one or more handlers exist in one or more sequences of screen events. ### Claim 11 (depends on 7) The non-transitory computer readable medium of claim 7 wherein the script contains goto statements for moving between the one or more handlers. ### Claim 12 (depends on 7) The non-transitory computer readable medium of claim 7 wherein the associated sequence of screen events are document object model events.