# US 2022/0027219 A1 · Auto termination of applications based on application and user activity

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2022/0027219 A1
- Document ID: US20220027219A1
- Status: Published application
- Kind: A1
- Application number: 17/460,565
- Filed: 2021-08-30
- Published: 2022-01-27
- Earliest claimed: 2020-07-24
- Assignees: Citrix Systems, Inc.
- Applicants: Citrix Systems, Inc.
- Inventors: Daowen Wei; Hengbo Wang; Jian Ding; Feng Tao; Manbinder Pal Singh
- Web page: https://patentgrep.com/patent/US20220027219A1

## CPC

- G06F 9/485: {Task life-cycle, e.g. stopping, restarting, resuming execution (G06F9/4881 takes precedence)}
- G06F 9/544: {Buffers; Shared memory; Pipes}
- G06F 16/16: File or folder operations, e.g. details of user interfaces specifically adapted to file systems
- G06F 8/77: Software metrics
- G06F 2009/45575: {Starting, stopping, suspending or resuming virtual machine instances}
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

A system and method that automatically terminates an application. A method includes monitoring activity data points for an application launched by a client device within a workspace environment. The activity data points may include user interactions with a physical interface component. State data for each file associated with the application is monitored and, if a determination is made that the application is inactive based on the activity data points, the method determines if a file associated with the application includes unsaved content based on state data. If it is determined that no files for the application include unsaved content, the method forecasts whether the application will be inactive for a future period based on the activity data. The application is terminated if it is determined that no files for the application include unsaved content and the application is forecast to be inactive.

## Claims

### Claim 1

A method, comprising:
monitoring activity data points for an application launched by a client device, wherein the activity data points include user interactions with a physical interface component;
monitoring state data for each file associated with the application;
in response to a determination that the application is inactive during a current time period based on the activity data points, determining if at least one file associated with the application includes unsaved content based on the state data;
in response to determining that no files for the application include unsaved content, forecasting whether the application will be inactive for a future time period based on the activity data; and
in response to determining that no files for the application include unsaved content and the application is forecast to be inactive for the future time period, terminating the application.

### Claim 2 (depends on 1)

The method of claim 1, wherein the physical interface component includes at least one of: a keyboard, a mouse, a touchpad, a voice detection system, a gesture detector, or an image capture system.

### Claim 3 (depends on 1)

The method of claim 1, wherein the state data for each file indicates whether the file was saved based on a detection of at least one of: a click, tap or touch on a save command, a save keyboard shortcut, an interaction with a file dialog, or an auto-save.

### Claim 4 (depends on 1)

The method of claim 1, wherein the activity data points for the application launched by the client device further include background interactions occurring with the application.

### Claim 5 (depends on 4)

The method of claim 4, wherein the background interactions include interactions occurring between the application and at least one of: a network communication, a file input/output, a peripheral device access, a registry access, or a disk access.

### Claim 6 (depends on 5)

The method of claim 5, wherein the determination that the application is inactive during the current time period includes utilizing a machine learning model to determine whether the background interactions detected during the current time period indicate an active or inactive state.

### Claim 7 (depends on 1)

The method of claim 1, further comprising logging off the client device if no other active applications exist have been launched by the client device.

### Claim 8 (depends on 1)

The method of claim 1, wherein forecasting the application as inactive for the further time period includes:
obtaining a historical activity record for the application; and
applying a forecasting procedure on the historical activity record to determine a probability that the future time period will be inactive.

### Claim 9 (depends on 8)

The method of claim 8, wherein the forecasting procedure includes a machine learning model that is trained for at least one of: a specific user, a group of users, or a group of applications.

### Claim 10 (depends on 1)

The method of claim 1, wherein the step of terminating the application is further based on a criteria that includes at least one of: a role of the user, a type of application, a location of the client device, a location of where the application is running, and a level of security associated with running the application.

### Claim 11 (depends on 1)

The method of claim 1, wherein the state data includes:
a first indicator indicating whether the file is open;
a second indicator indicating whether the file, if open, has been saved; and
a time indicator indicating when the state data of the file was last updated.

### Claim 12

A system, comprising:
a computing device configured to:
monitor activity data points for an application launched by a client device, wherein the activity data points include user interactions with a physical interface component;
monitor state data for each file associated with the application;
in response to a determination that the application is inactive during a current time period based on the activity data points, determine if at least one file associated with the application includes unsaved content based on the state data;
in response to determining that no files for the application include unsaved content, forecast whether the application will be inactive for a future time period based on the activity data; and
in response to determining that no files for the application include unsaved content and the application is forecast to be inactive for the future time period, terminate the application.

### Claim 13 (depends on 12)

The system of claim 12, wherein the physical interface component includes at least one of: a keyboard, a mouse, a touchpad, a voice detection system, a gesture detector, or an image capture system.

### Claim 14 (depends on 12)

The system of claim 12, wherein the state data for each file indicates whether the file was saved based on a detection of at least one of: a click, tap or touch on a save command, a save keyboard shortcut, an interaction with a file dialog, or an auto-save.

### Claim 15 (depends on 12)

The system of claim 12, wherein the activity data points for the application launched by the client device further include background interactions occurring with the application.

### Claim 16 (depends on 15)

The system of claim 15, wherein the background interactions include interactions occurring between the application and at least one of: a network communication, a file input/output, a peripheral device access, a registry access, or a disk access.

### Claim 17 (depends on 15)

The system of claim 15, wherein the determination that the application is inactive during the current time period includes utilizing a machine learning model to determine whether the background interactions detected during the current time period indicate an active or inactive state.

### Claim 18 (depends on 12)

The system of claim 12, wherein the state data indicates whether a file was saved based on a detection of at least one of: a click, tap or touch on a save command, a save keyboard shortcut, an interaction with a file dialog, or an auto-save.

### Claim 19 (depends on 12)

The system of claim 12, wherein forecasting the application as inactive for the further time period includes:
obtaining a historical activity record for the application; and
applying a forecasting procedure on the historical activity record to determine a probability that the future time period will be inactive.

### Claim 20 (depends on 12)

The system of claim 12, wherein the state data includes:
a first indicator indicating whether the file is open;
a second indicator indicating whether the file, if open, has been saved; and
a time indicator indicating when the state data of the file was last updated.
