Legal claims defining the scope of protection. Each claim is shown in both the original legal language and a plain English translation.
1. A method for scheduling execution of a user-restricted process within a distributed computing system, the method comprising: receiving a runtime request to execute a user-restricted process within a distributed computing system, the runtime request received via a transaction page of a user application during a current runtime session of a user within the distributed computing system; determining one or more characteristics of the current runtime session of the user within the distributed computing system, the characteristics including a number of user-restricted processes previously initiated by the user during the current runtime session; and determining whether or not to permit execution of the user-restricted process based on (i) the user-restricted process, (ii) the user, and (iii) the number of user-restricted processes previously initiated by the user during the current runtime session, wherein determining whether or not to permit execution of the user-restricted process comprises: retrieving a previously stored threshold number of user-restricted processes permitted to be executed by the user per runtime session; comparing the previously stored threshold number to the number of user-restricted processes previously initiated by the user during the current runtime session; and in response to determining that the number of user-restricted processes previously initiated by the user during the current runtime session does not exceed the previously stored threshold number, determining that the execution of the user-restricted process is permitted and scheduling execution of the user-restricted process; and wherein scheduling execution of the user-restricted process comprises: retrieving data from the transaction page; and initiating execution of the user-restricted process on the distributed computing system, using the data retrieved from the transaction page.
The system controls user-restricted processes in a distributed computing environment. When a user requests to run a process from a webpage during their active session, the system checks if the user is allowed to run it. This check considers how many similar processes the user has already run during that session. The system retrieves a limit for the number of processes a user can run and compares it to the current count. If the user is within the limit, the system proceeds. To run the process, the system extracts necessary information from the webpage where the request originated and uses this data to start the process on the distributed computing system.
2. The method of claim 1 , wherein the one or more characteristics of the current runtime session further include a current level of network usage within the distributed computing system, and wherein the determination of whether or not to permit execution of the user-restricted process is further based on the current level of network usage within the distributed computing system.
Building upon the basic process control, the system also factors in network usage. In addition to the number of processes already run (as in the previous description), the system considers the current network load. The decision to allow a user-restricted process to execute is now based on the user's process count, the user himself, and the real-time network congestion within the distributed computing environment, preventing overload and ensuring a smoother experience for all users by throttling resource-intensive operations during peak times.
3. The method of claim 1 , wherein the one or more characteristics of the current runtime session further include a current processing load within the distributed computing system, and wherein the determination of whether or not to permit execution of the user-restricted process is further based on the current processing load within the distributed computing system.
Expanding on the core process control, the system also considers the current processing load. Similar to network usage (as described previously), the decision to permit execution of a user-restricted process is influenced by the overall system workload. Therefore, besides checking the number of processes a user has run and the user context, the system monitors the CPU and memory usage across the distributed environment, deferring or rejecting new process requests during periods of high utilization to maintain stability and responsiveness.
4. The method of claim 1 , wherein the one or more characteristics of the current runtime session further include an amount of time since the user has initiated the user-restricted processes within the distributed computing system, and wherein the determination of whether or not to permit execution of the user-restricted process is further based on the amount of time since the user has initiated the user-restricted processes within the distributed computing system.
Extending the process control, the system factors in the time elapsed since the user last initiated similar processes. In addition to the number of processes run (as in the initial description), the system considers the time interval between process initiations. The decision on whether to permit a new process considers this time elapsed, potentially restricting users who rapidly request multiple processes, preventing abuse or resource exhaustion within the distributed computing system.
5. The method of claim 1 , wherein the one or more characteristics of the current runtime session further include one or more transaction pages visited by the user during the current runtime session, and wherein the determination of whether or not to permit execution of the user-restricted process is further based on the transaction pages visited by the user during the current runtime session.
Complementing the existing process control, the system now incorporates the user's browsing history within the application. Along with the number of processes initiated (as in the initial description), the system tracks the specific webpages the user has visited during their current session. The decision to permit a new process considers these visited pages, enabling context-aware authorization or specialized handling based on the user's navigation path within the application, allowing more sophisticated security policies or resource allocation strategies.
6. The method of claim 1 , wherein scheduling execution of the user-restricted process further comprises: initiating the execution of the user-restricted process on the distributed computing system, using a predetermined set of process parameters that are not selectable by the user.
When scheduling a user-restricted process, the system uses predefined settings that the user cannot change. After deciding to permit the process based on user limits and session characteristics, the system starts the execution. Critically, the system employs a fixed set of parameters, preventing the user from modifying these parameters, thereby ensuring consistent and secure process execution, restricting potentially harmful customization.
7. The method of claim 1 , wherein scheduling execution of the user-restricted process further comprises: determining that one or more user-modifiable runtime variables are available for executing the user-restricted process; and modifying the transaction page with an interface to retrieve the one or more user-modifiable runtime variables.
The system can dynamically adjust the webpage to gather user-defined variables for process execution. If certain parameters for a user-restricted process can be configured by the user, the system automatically modifies the webpage to include input fields for those parameters. The system then retrieves these user-provided values and uses them when starting the process, allowing controlled customization of process behavior, only exposing certain runtime variables for tuning.
8. A computing system comprising: a processing unit comprising one or more processors; and memory coupled with and readable by the processing unit and storing therein a set of instructions which, when executed by the processing unit, causes the processing unit to schedule execution of a user-restricted process within the computing system by: receiving a runtime request to execute a user-restricted process within the computing system, the runtime request received via a transaction page of a user application during a current runtime session of a user within the computing system; determining one or more characteristics of the current runtime session of the user within the computing system, the characteristics including a number of user-restricted processes previously initiated by the user during the current runtime session; and determining whether or not to permit execution of the user-restricted process based on (i) the user-restricted process, (ii) the user, and (iii) the number of user-restricted processes previously initiated by the user during the current runtime session wherein determining whether or not to permit execution of the user-restricted process comprises: retrieving a previously stored threshold number of user-restricted processes permitted to be executed by the user per runtime session; comparing the previously stored threshold number to the number of user-restricted processes previously initiated by the user during the current runtime session; and in response to determining that the number of user-restricted processes previously initiated by the user during the current runtime session does not exceed the previously stored threshold number, determining that the execution of the user-restricted process is permitted and scheduling execution of the user-restricted process; and wherein scheduling execution of the user-restricted process comprises: retrieving data from the transaction page; and initiating execution of the user-restricted process on the computing system, using the data retrieved from the transaction page.
A computing system schedules user-restricted processes: When a user submits a process request from a webpage, the system determines if the user is authorized based on the number of processes already initiated during their session. A threshold for permitted processes is retrieved and compared against the user's current process count. If the count is below the threshold, execution proceeds. Data from the webpage is extracted and used to initiate the process on the computing system. The permission to run the process depends on the process itself, the user, and the current process count.
9. The computing system of claim 8 , wherein the one or more characteristics of the current runtime session further include a current level of network usage within the computing system, and wherein the determination of whether or not to permit execution of the user-restricted process is further based on the current level of network usage within the computing system.
The computing system from the previous process control description incorporates network usage considerations: The decision to execute a user-restricted process is also influenced by the current network load, alongside the number of processes initiated by the user. Therefore, the system accounts for real-time network conditions when determining whether to allow a new process, avoiding system overload.
10. The computing system of claim 8 , wherein the one or more characteristics of the current runtime session further include a current processing load within the computing system, and wherein the determination of whether or not to permit execution of the user-restricted process is further based on the current processing load within the computing system.
The computing system from the previous process control description also accounts for system processing load: The determination to execute a user-restricted process also depends on the system's current processing load, in addition to the user's process count, avoiding performance degradation under high utilization.
11. The computing system of claim 8 , wherein the one or more characteristics of the current runtime session further include an amount of time since the user has initiated the user-restricted processes within the computing system, and wherein the determination of whether or not to permit execution of the user-restricted process is further based on the amount of time since the user has initiated the user-restricted processes within the computing system.
The computing system from the previous process control description considers the time since the user last initiated similar processes: Besides the number of initiated processes, the time interval since the last process initiation influences the decision to permit a new user-restricted process.
12. The computing system of claim 8 , wherein the one or more characteristics of the current runtime session further include one or more transaction pages visited by the user during the current runtime session, and wherein the determination of whether or not to permit execution of the user-restricted process is further based on the transaction pages visited by the user during the current runtime session.
The computing system from the previous process control description also factors in user browsing history: The determination on whether to permit execution of a user-restricted process depends on the webpages visited by the user within the application during the current session, providing context-aware control.
13. A non-transitory computer-readable memory comprising a set of instructions stored therein which, when executed by a processor, causes the processor to schedule execution of a user-restricted process within a distributed computing system by: receiving a runtime request to execute a user-restricted process within a distributed computing system, the runtime request received via a transaction page of a user application during a current runtime session of a user within the distributed computing system; determining one or more characteristics of the current runtime session of the user within the distributed computing system, the characteristics including a number of user-restricted processes previously initiated by the user during the current runtime session; and determining whether or not to permit execution of the user-restricted process based on (i) the user-restricted process, (ii) the user, and (iii) the number of user-restricted processes previously initiated by the user during the current runtime session, wherein determining whether or not to permit execution of the user-restricted process comprises: retrieving a previously stored threshold number of user-restricted processes permitted to be executed by the user per runtime session; comparing the previously stored threshold number to the number of user-restricted processes previously initiated by the user during the current runtime session; and in response to determining that the number of user-restricted processes previously initiated by the user during the current runtime session does not exceed the previously stored threshold number, determining that the execution of the user-restricted process is permitted and scheduling execution of the user-restricted process; and wherein scheduling execution of the user-restricted process comprises: retrieving data from the transaction page; and initiating execution of the user-restricted process on the distributed computing system, using the data retrieved from the transaction page.
A non-transitory computer-readable memory stores instructions for scheduling user-restricted processes. When executed, the instructions cause a processor to determine user authorization based on the number of processes initiated within a session. A defined process limit is compared against the current count, and if the user is within the limit, the process execution proceeds by extracting data from the webpage and using that information to start the process within the distributed computing system. The permission to run the process depends on the process itself, the user, and the current process count.
14. The non-transitory computer-readable memory of claim 13 , wherein the one or more characteristics of the current runtime session further include a current level of network usage within the distributed computing system, and wherein the determination of whether or not to permit execution of the user-restricted process is further based on the current level of network usage within the distributed computing system.
The non-transitory computer-readable memory from the previous process control description also factors in network usage: The determination of whether to execute a user-restricted process is also influenced by the current network conditions within the distributed computing system.
15. The non-transitory computer-readable memory of claim 13 , wherein the one or more characteristics of the current runtime session further include an amount of time since the user has initiated the user-restricted processes within the distributed computing system, and wherein the determination of whether or not to permit execution of the user-restricted process is further based on the amount of time since the user has initiated the user-restricted processes within the distributed computing system.
The non-transitory computer-readable memory from the previous process control description incorporates time-based restrictions: The determination of whether to permit execution of a user-restricted process also depends on the time elapsed since the user last initiated similar processes within the distributed computing system.
16. The non-transitory computer-readable memory of claim 13 , wherein the one or more characteristics of the current runtime session further include one or more transaction pages visited by the user during the current runtime session, and wherein the determination of whether or not to permit execution of the user-restricted process is further on the transaction pages visited by the user during the current runtime session.
The non-transitory computer-readable memory from the previous process control description also incorporates the user's navigation history: The determination of whether to permit execution of a user-restricted process depends on the transaction pages visited by the user during the current runtime session.
Unknown
October 31, 2017
Browse 5M+ US patents with plain-English claim translations and AI-generated analysis.