# US 2026/0303533 A1 · Version Based Stateless Caching to Deliver Cloud Enforcement Policy to User Devices

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

- Number: US 2026/0303533 A1
- Document ID: US20260303533A1
- Status: Published application
- Kind: A1
- Application number: 19/202,259
- Filed: 2025-05-08
- Published: 2026-10-01
- Earliest claimed: 2025-03-26
- Assignees: Zscaler, Inc.
- Applicants: Zscaler, Inc.
- Inventors: Ajit Singh; Ramneet Singh; Vivek Raman
- Web page: https://patentgrep.com/patent/US20260303533A1

## CPC

- H04L 47/125: by balancing the load, e.g. traffic engineering
- H04L 67/1031: Controlling of the operation of servers by a load balancer, e.g. adding or removing servers that serve requests
- H04L 67/568: Storing data temporarily at an intermediate stage, e.g. caching
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

Systems and methods for version based stateless caching to deliver cloud enforcement policy to user devices include receiving keep-alive signals from a plurality of agent applications, each agent application of the plurality of agent applications being associated with and identifying a corresponding user device; storing device details associated with the plurality of agent applications; intercepting a policy request from at least one agent application of the plurality of agent applications; and responsive to determining device details associated with the at least one agent application are stored, returning a response to the at least one agent application from a policy cache.

## Claims

### Claim 1

A method for delivering cloud enforcement policy to user devices from a cloud-based system, the method comprising steps of:
receiving keep-alive signals from a plurality of agent applications, each agent application of the plurality of agent applications being associated with and identifying a corresponding user device;
storing device details associated with the plurality of agent applications;
intercepting a policy request from at least one agent application of the plurality of agent applications; and
responsive to determining device details associated with the at least one agent application are stored, returning a response to the at least one agent application from a policy cache.

### Claim 2 (depends on 1)

The method of claim 1, wherein the steps comprise determining whether policy information associated with the policy request is stored in the policy cache, and responsive to the policy information being stored, returning a response to the agent application from the policy cache.

### Claim 3 (depends on 2)

The method of claim 2, wherein the steps further comprise determining whether the policy information in the policy cache is expired prior to the returning.

### Claim 4 (depends on 1)

The method of claim 1, wherein the steps comprise determining whether policy information associated with the policy request is stored in a policy cache, and responsive to the policy information not being stored and or is expired, forwarding the policy request to a mobile admin system and storing resulting policy information in the policy cache for subsequent use.

### Claim 5 (depends on 1)

The method of claim 1, wherein the steps are performed by a stateless cluster of reverse proxies adapted to intercept traffic between a plurality of user devices and a mobile admin system of a cloud-based system.

### Claim 6 (depends on 5)

The method of claim 5, wherein the steps comprise deploying a stateless cluster of reverse proxies, each reverse proxy including a device cache for storing device details and mappings of devices to policies, a policy cache for storing policy information, and a token cache for storing token information and mappings of tokens to policies.

### Claim 7 (depends on 5)

The method of claim 5, wherein the steps include batching, by the stateless cluster of reverse proxies, the keep-alive signals for subsequent forwarding to the mobile admin system over a persistent connection.

### Claim 8 (depends on 5)

The method of claim 5, wherein the stateless cluster of reverse proxies reduces load on the mobile admin system by batching keep-alive signals, caching policy information, and serving repeated requests without re-querying the mobile admin system.

### Claim 9 (depends on 5)

The method of claim 5, wherein each reverse proxy in the stateless cluster is configured to automatically scale up or down based on traffic load, thereby maintaining performance during varying demand levels in the cloud-based system.

### Claim 10 (depends on 5)

The method of claim 5, wherein the steps comprise monitoring performance metrics of the stateless cluster of reverse proxies, including cache hit rates, response times, and load distribution, and adjusting cache configurations or scaling parameters based on the monitored metrics.

### Claim 11

A non-transitory computer-readable medium comprising instructions for delivering cloud enforcement policy to user devices from a cloud-based system that, when executed, cause one or more processors to perform steps of:
receiving keep-alive signals from a plurality of agent applications, each agent application of the plurality of agent applications being associated with and identifying a corresponding user device;
storing device details associated with the plurality of agent applications;
intercepting a policy request from at least one agent application of the plurality of agent applications; and
responsive to determining device details associated with the at least one agent application are stored, returning a response to the at least one agent application from a policy cache.

### Claim 12 (depends on 11)

The non-transitory computer-readable medium of claim 11, wherein the steps comprise determining whether policy information associated with the policy request is stored in the policy cache, and responsive to the policy information being stored, returning a response to the agent application from the policy cache.

### Claim 13 (depends on 12)

The non-transitory computer-readable medium of claim 12, wherein the steps further comprise determining whether the policy information in the policy cache is expired prior to the returning.

### Claim 14 (depends on 11)

The non-transitory computer-readable medium of claim 11, wherein the steps comprise determining whether policy information associated with the policy request is stored in a policy cache, and responsive to the policy information not being stored and or is expired, forwarding the policy request to a mobile admin system and storing resulting policy information in the policy cache for subsequent use.

### Claim 15 (depends on 11)

The non-transitory computer-readable medium of claim 11, wherein the steps are performed by a stateless cluster of reverse proxies adapted to intercept traffic between a plurality of user devices and a mobile admin system of a cloud-based system.

### Claim 16 (depends on 15)

The non-transitory computer-readable medium of claim 15, wherein the steps comprise deploying a stateless cluster of reverse proxies, each reverse proxy including a device cache for storing device details and mappings of devices to policies, a policy cache for storing policy information, and a token cache for storing token information and mappings of tokens to policies.

### Claim 17 (depends on 15)

The non-transitory computer-readable medium of claim 15, wherein the steps include batching, by the stateless cluster of reverse proxies, the keep-alive signals for subsequent forwarding to the mobile admin system over a persistent connection.

### Claim 18 (depends on 15)

The non-transitory computer-readable medium of claim 15, wherein the stateless cluster of reverse proxies reduces load on the mobile admin system by batching keep-alive signals, caching policy information, and serving repeated requests without re-querying the mobile admin system.

### Claim 19 (depends on 15)

The non-transitory computer-readable medium of claim 15, wherein each reverse proxy in the stateless cluster is configured to automatically scale up or down based on traffic load, thereby maintaining performance during varying demand levels in the cloud-based system.

### Claim 20 (depends on 15)

The non-transitory computer-readable medium of claim 15, wherein the steps comprise monitoring performance metrics of the stateless cluster of reverse proxies, including cache hit rates, response times, and load distribution, and adjusting cache configurations or scaling parameters based on the monitored metrics.
