# US 2026/0122105 A1 · Providing protection for resources of a device

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

- Number: US 2026/0122105 A1
- Document ID: US20260122105A1
- Status: Published application
- Kind: A1
- Application number: 18/931,172
- Filed: 2024-10-30
- Published: 2026-04-30
- Earliest claimed: 2024-10-30
- Assignees: Juniper Networks, Inc.
- Applicants: Juniper Networks, Inc.
- Inventors: Erin C. MACNEIL; Prashant SINGH
- Web page: https://patentgrep.com/patent/US20260122105A1

## CPC

- H04L 63/1458: {Denial of Service}
- G06F 9/4486: {Formation of subprogram jump address}
- G06F 9/5005: {to service a request}
- G06F 9/5022: {Mechanisms to release resources}
- G06F 9/542: {Event management; Broadcasting; Multicasting; Notifications}
- G06F 9/545: {where tasks reside in different layers, e.g. user- and kernel-space}
- G06F 9/547: {Remote procedure calls [RPC]; Web services}
- G06F 21/6281: {at program execution time, where the protection is within the operating system}
- H04L 47/215: using token-bucket
- H04L 47/263: Rate modification at the source after receiving feedback
- H04L 63/0236: {Filtering by address, protocol, port number or service, e.g. IP-address or URL}
- G06F 2209/504: Resource capping
- G06F 2209/543: Local
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

A device may receive packets or an application programming interface (API) request associated with resources of the device. The device may apply, to the API request, an API hook that limits a request rate of a rate limiter of the device and protects the resources of the device. The device may perform one or more actions based on the API hook.

## Claims

### Claim 1

A method, comprising:
receiving, by a device, packets or an application programming interface (API) request associated with resources of the device;
applying, by the device and to the API request, an API hook that limits a request rate of a rate limiter of the device and protects the resources of the device; and
performing, by the device, one or more actions based on the API hook.

### Claim 2 (depends on 1)

The method of claim 1, further comprising:
rate limiting the packets based on referring to a local resource copy of the device.

### Claim 3 (depends on 2)

The method of claim 2, further comprising:
consuming a token for one of the packets not associated with an entry in the local resource copy.

### Claim 4 (depends on 2)

The method of claim 2, wherein the local resource copy includes resource keys associated with the resources of the device.

### Claim 5 (depends on 1)

The method of claim 1, wherein the resources are kernel resources of the device.

### Claim 6 (depends on 1)

The method of claim 1, wherein the API hook is an extended Berkeley packet filter API hook.

### Claim 7 (depends on 1)

The method of claim 1, wherein performing the one or more actions based on the API hook comprises one or more of:
recording an event associated with the device;
generating an alarm;
performing a resource cleanup; or
selectively rejecting particular API requests.

### Claim 8

A device, comprising:
one or more memories; and
one or more processors to:
receive packets or an application programming interface (API) request associated with resources of the device,
wherein the resources are kernel resources of the device;
apply, to the API request, an API hook that limits a request rate of a rate limiter of the device and protects the resources of the device; and
perform one or more actions based on the API hook.

### Claim 9 (depends on 8)

The device of claim 8, wherein the one or more processors are further to:
determine a total quantity of available tokens of the rate limiter at a next interval associated with a garbage collector of the device;
calculate a token rate for the next interval based on the total quantity of available tokens; and
update the rate limiter with the token rate.

### Claim 10 (depends on 9)

The device of claim 9, wherein the one or more processors are further to:
allow processing of one of the packets or the API request when a token is available from the rate limiter; and
update a local resource copy of the device based on allowing processing of one of the packets or the API request.

### Claim 11 (depends on 9)

The device of claim 9, wherein the one or more processors are further to:
drop subsequent packets and API requests based on tokens of the rate limiter being consumed.

### Claim 12 (depends on 9)

The device of claim 9, wherein the one or more processors, to calculate the token rate for the next interval based on the total quantity of available tokens, are to:
divide the total quantity of available tokens by the next interval to calculate the token rate.

### Claim 13 (depends on 9)

The device of claim 9, wherein the rate limiter utilizes the token rate to create tokens for the next interval.

### Claim 14 (depends on 9)

The device of claim 9, wherein the one or more processors are further to:
calculate, based on the total quantity of available tokens, another token rate for an interval that is less than the next interval; and
update the rate limiter with the other token rate.

### Claim 15

A non-transitory computer-readable medium storing a set of instructions, the set of instructions comprising:
one or more instructions that, when executed by one or more processors of a device, cause the device to:
receive packets or an application programming interface (API) request associated with resources of the device,
wherein the resources are tables of the device;
apply, to the API request, an API hook that limits a request rate of a rate limiter of the device and protects the resources of the device; and
perform one or more actions based on the API hook.

### Claim 16 (depends on 15)

The non-transitory computer-readable medium of claim 15, wherein the one or more instructions further cause the device to:
rate limit the packets based on referring to a local resource copy of the device; and
consume a token for one of the packets not associated with an entry in the local resource copy.

### Claim 17 (depends on 15)

The non-transitory computer-readable medium of claim 15, wherein the one or more instructions, that cause the device to perform the one or more actions based on the API hook, cause the device to one or more of:
record an event associated with the device;
generate an alarm;
perform a resource cleanup; or
selectively reject particular API requests.

### Claim 18 (depends on 15)

The non-transitory computer-readable medium of claim 15, wherein the one or more instructions further cause the device to:
determine a total quantity of available tokens of the rate limiter at a next interval associated with a garbage collector of the device;
calculate a token rate for the next interval based on the total quantity of available tokens; and
update the rate limiter with the token rate.

### Claim 19 (depends on 18)

The non-transitory computer-readable medium of claim 18, wherein the one or more instructions further cause the device to:
allow processing of one of the packets or the API request when a token is available from the rate limiter; and
update a local resource copy of the device based on allowing processing of one of the packets or the API request.

### Claim 20 (depends on 18)

The non-transitory computer-readable medium of claim 18, wherein the one or more instructions further cause the device to:
drop subsequent packets and API requests based on tokens of the rate limiter being consumed.
