Remote Session Utility Toolbox for Mobile Execution
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Users face challenges in accessing and utilizing specific functionalities of application programs due to their size and complexity, especially on mobile devices, where limited capabilities restrict the execution of certain actions during remote sessions, and there is a lack of awareness about available applications that can perform desired functions.
Innovation Solution
A system and method for executing utility applications in a remote session, where a remote session client on a client device determines whether to execute requested actions locally or on a remote server, utilizing a toolbox application that manages utility components and communicates with a remote application server to provide necessary functionalities, allowing users to access and execute applications and data from any device.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If users access remote applications on mobile devices, then they can work from any location, but the limited device capabilities restrict execution of certain actions
Solution Approach 1:
The patent introduces a toolbox application as an intermediary layer between the user and the remote application. This toolbox manages utility components and coordinates execution decisions, allowing users to access full functionality while the system handles the complexity of determining local vs. remote execution based on device capabilities
Solution Approach 2:
The patent segments utility functionality into separate utility components that can be independently managed. The toolbox application segments the decision-making process by evaluating each utility's execution requirements against device capabilities, allowing selective execution on appropriate platforms
2Ease of operation
If users need specific functionality from large application programs, then they can achieve desired tasks, but they may not be aware of available applications that can perform those functions
Solution Approach 1:
The toolbox application provides self-service by automatically detecting user needs and presenting relevant utility components without requiring users to search through application catalogs. The system proactively identifies suitable utilities and handles execution decisions automatically
Solution Approach 2:
The toolbox application serves multiple functions: it manages utility components, evaluates execution requirements, determines local vs. remote execution, and presents utilities to users. This multi-functional design consolidates what would otherwise require multiple separate systems into a single accessible interface
3Ease of operation
If users purchase large application programs to get specific functionality, then they can perform desired tasks, but the cost becomes prohibitive when only a few functions are needed
Solution Approach 1:
The patent extracts individual utility functions from large application programs and makes them available as separate, independently licensable components. Users can access and execute only the specific utilities they need through the toolbox, eliminating the need to purchase entire large applications
Solution Approach 2:
Instead of requiring users to purchase complete applications, the system allows partial access to individual utility functions. The toolbox enables users to execute only the necessary utilities for their specific tasks, avoiding payment for unnecessary functionality
4Adaptability or versatility
If utility applications execute on the remote server, then more functionalities are available, but the client device appears to lack execution capability
Solution Approach 1:
The toolbox application acts as an intermediary that transparently manages execution location decisions. It presents a unified interface to users where utility execution appears local, while automatically routing to appropriate platforms (local device or remote server) based on capabilities and requirements
Solution Approach 2:
Instead of the client device attempting to execute all utilities locally and failing when capabilities are insufficient, the system inverts the approach by having the toolbox evaluate execution requirements and select the most appropriate platform, making capability limitations invisible to the user
Data Source
AI summary
Disclosed are systems and methods for determining an execution location for a utility component. In an exemplary aspect, the systems and methods comprise receiving, at a client device, a request to execute the utility component that performs an action on a target component; determining the execution location of the utility component; determining whether the execution location is on the client device or on a remote application server; and responsive to determining the execution location is on the remote application server, transmitting the request to be executed within a remote session between the client device and the remote application server.