# US 2020/0394030 A1 · Installing, updating or reconfiguring an application without disabling a write filter

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

- Number: US 2020/0394030 A1
- Document ID: US20200394030A1
- Status: Published application
- Kind: A1
- Application number: 16/438,301
- Filed: 2019-06-11
- Published: 2020-12-17
- Earliest claimed: 2019-06-11
- Assignees: Dell Products L.P.
- Applicants: Dell Products L.P.
- Inventors: Gokul Thiruchengode Vajravel; Jyothi Bandakka
- Web page: https://patentgrep.com/patent/US20200394030A1

## CPC

- G06F 8/65: Updates (security arrangements therefor G06F21/57)
- G06F 8/61: Installation
- G06F 9/44505: {Configuring for program initiating, e.g. using registry, configuration files}
- G06F 12/0875: with dedicated cache, e.g. instruction or stack
- G06F 2212/45: Caching of specific data in cache memory
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

An application can be installed, updated or reconfigured without disabling a write filter. When a package is to be deployed to a client terminal to install, update or reconfigure an application, an overlay optimizer can be instructed to start a session. During the session, the overlay optimizer can analyze I/O requests to identify any I/O request that pertains to the deployment of the package. The overlay optimizer can then redirect the identified I/O requests to a session overlay that the overlay optimizer has created for the session rather than passing the I/O requests to the write filter. As a result, the artifacts that are affected by the deployment of the package will be stored in the session overlay rather than the write filter's overlay. Once the session is completed, the overlay optimizer can copy the artifacts from the session overlay to the write filter's overlay and commit them.

## Claims

### Claim 1

A method, performed by an overlay optimizer on a client terminal that includes a write filter, for installing, updating or reconfiguring an application without disabling the write filter, the method comprising:
receiving a session start request that indicates that a package is to be deployed on the client terminal to install, update or reconfigure an application;
in response to the session start request, creating a session overlay in an overlay cache;
analyzing I/O requests to determine whether the I/O requests pertain to the deployment of the package;
for each of a plurality of I/O requests that are determined to pertain to the deployment of the package, redirecting the I/O request to the overlay cache;
after receiving a session stop request, accessing artifacts that have been stored in the overlay cache as a result of redirecting each of the plurality of I/O requests; and
causing the artifacts to be copied to an overlay of the write filter and then causing the artifacts to be committed by the write filter.

### Claim 2 (depends on 1)

The method of claim 1, wherein the session start request identifies an expected overlay size of the package, and wherein the overlay optimizer creates the session overlay based on the expected overlay size.

### Claim 3 (depends on 2)

The method of claim 2, wherein the overlay optimizer creates the session overlay when the expected overlay size exceeds an amount of free space available in the overlay.

### Claim 4 (depends on 1)

The method of claim 1, wherein the overlay optimizer creates the session overlay by creating a dummy file in the overlay cache.

### Claim 5 (depends on 4)

The method of claim 4, wherein creating the dummy file includes setting a size of the dummy file to match an expected overlay size of the package.

### Claim 6 (depends on 5)

The method of claim 5, wherein, for at least some of the plurality of I/O requests, redirecting the I/O request to the overlay cache includes reducing the size of the dummy file by an amount that is based on a size of an artifact that the I/O request will create in the session overlay.

### Claim 7 (depends on 1)

The method of claim 1, further comprising:
in response to the session stop request, ceasing the analysis of the I/O requests.

### Claim 8 (depends on 1)

The method of claim 1, wherein causing the artifacts to be copied to the overlay comprises creating I/O requests that cause the write filter to write the artifacts to the overlay.

### Claim 9 (depends on 1)

The method of claim 1, wherein the plurality of I/O requests include at least one I/O request that deletes a particular artifact, the method further comprising:
maintaining a delete entry in a log, the delete entry identifying the particular artifact;
after receiving the session stop request, creating an I/O request to cause the particular artifact to be deleted and then committing the delete.

### Claim 10 (depends on 1)

The method of claim 1, wherein the artifacts are accessed, copied to the overlay and then committed immediately in response to the session stop request.

### Claim 11 (depends on 1)

The method of claim 1, wherein the artifacts are accessed, copied to the overlay and then committed at a next reboot of the client terminal.

### Claim 12 (depends on 1)

The method of claim 1, wherein determining whether the I/O requests pertain to the deployment of the package comprises determining whether the I/O requests are associated with an agent.

### Claim 13 (depends on 1)

The method of claim 1, further comprising:
receiving a second session start request that indicates that a second package is to be deployed on the client terminal to install, update or reconfigure an application;
determining that an expected overlay size of the second package is less than an amount of free space available in the overlay;
analyzing I/O requests received after the second session start request to determine whether the I/O requests pertain to the deployment of the second package;
for each of a second plurality of I/O requests that are determined to pertain to the deployment of the second package, maintaining a log of artifacts that are targeted by the second plurality of I/O requests;
in response to a second session stop request, employing the log to cause the write filter to commit each of the artifacts.

### Claim 14

A method, performed by an overlay optimizer on a client terminal that includes a write filter, for installing, updating or reconfiguring an application without disabling the write filter, the method comprising:
starting a session during which a package is to be deployed on the client terminal to install, update or reconfigure an application, the package having an expected overlay size;
comparing the expected overlay size to an amount of free space available to an overlay of the write filter;
when the expected overlay size exceeds the amount of free space available to the overlay, creating a session overlay in an overlay cache;
during the session, analyzing I/O requests to determine whether the I/O requests pertain to the deployment of the package;
for each of a plurality of I/O requests that are determined to pertain to the deployment of the package, redirecting the I/O request to the session overlay when the session overlay has been created or passing the I/O request to the write filter when the session overlay has not been created; and
after the package has been deployed, causing artifacts that were created, modified or deleted by the plurality of I/O requests to be committed by the write filter.

### Claim 15 (depends on 14)

The method of claim 14, wherein the overlay optimizer causes the artifacts that were created, modified or deleted by the plurality of I/O requests to be committed by the write filter immediately in response to receiving a session stop request.

### Claim 16 (depends on 14)

The method of claim 14, wherein passing the I/O request to the write filter when the session overlay has not been created includes logging an artifact that is targeted by the I/O request.

### Claim 17 (depends on 16)

The method of claim 16, wherein causing the artifacts that were created, modified or deleted by the plurality of I/O requests to be committed by the write filter comprises issuing a request to commit each logged artifact.

### Claim 18 (depends on 14)

The method of claim 14, wherein redirecting the I/O request to the session overlay when the session overlay has been created includes causing at least some of the artifacts to be stored in the session overlay.

### Claim 19 (depends on 18)

The method of claim 18, wherein causing the artifacts that were created, modified or deleted by the plurality of I/O requests to be committed by the write filter comprises reading each artifact stored in the session overlay and then writing each artifact to thereby cause the artifact to be stored in the overlay.

### Claim 20

One or more computer storage media storing computer executable instructions which when executed on a client terminal that includes a write filter implement an overlay optimizer that is configured to perform a method for installing, updating or reconfiguring an application without disabling the write filter, the method comprising:
receiving a session start request that indicates that a package is to be deployed on the client terminal to install, update or reconfigure an application;
in response to the session start request, creating a session overlay in an overlay cache;
after receiving the session start request, commencing an analysis of I/O requests to determine whether the I/O requests pertain to the deployment of the package;
for each of a plurality of I/O requests that are determined to pertain to the deployment of the package, redirecting the I/O request to the overlay cache to thereby cause an artifact that is a target of the I/O request to be stored in the session overlay;
receiving a session stop request;
in response to the session stop request, ceasing the analysis;
after receiving the session stop request, causing each artifact that is stored in the session overlay to be stored in an overlay of the write filter; and
causing the write filter to commit each artifact.
