# US 2025/0158956 A1 · Network address translation between networks

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

- Number: US 2025/0158956 A1
- Document ID: US20250158956A1
- Status: Published application
- Kind: A1
- Application number: 18/955,692
- Filed: 2024-11-21
- Published: 2025-05-15
- Earliest claimed: 2020-12-21
- Assignees: Oracle International Corporation
- Applicants: Oracle International Corporation
- Inventors: Shreyas Vinayakumar; Abhiman Yashpala Karkera; Siddharth Rampura Chandraprabhuraju; Saurabh Agarwal; Soumya Kailasa
- Web page: https://patentgrep.com/patent/US20250158956A1

## CPC

- H04L 61/2503: Translation of Internet protocol [IP] addresses
- H04L 61/2514: between local and global IP addresses
- H04L 61/2517: using port numbers
- H04L 61/255: Maintenance or indexing of mapping tables
- H04L 61/5007: Internet protocol [IP] addresses
- H04L 61/5061: Pools of addresses
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

Techniques for performing NAT operations to send packets between networks are described. In an example, a network device receives a packet that comprises a header. The header indicates a source address of a first computing resource in a first network and a destination address of a second computing resource in a second network. The network device determines a pool of identifiers allocated for the first network and the second computing resource and identifies a packet flow based on the header. The network device also determines that no identifier from the pool of identifiers has been allocated for the packet flow and determines an identifier available to allocate for the packet flow from the pool of identifiers. The network device performs a NAT operation on the packet based on the identifier.

## Claims

### Claim at position 1

1-20. (canceled)

### Claim 21

A method comprising:
receiving, by a database from a network device configured to perform network address translation (NAT) operations, an identifier allocation request to determine if a flow identifier is allocable to a packet flow, wherein the identifier allocation request includes the flow identifier and packet flow information associated with the packet flow, wherein the flow identifier is from a first pool of flow identifiers of a plurality of pools, wherein each pool of the plurality of pools is available for NAT operations between a source network and a target computing resource in a target network, and wherein each flow identifier of the first pool is specific to a first packet flow between a first computing resource of a first network and a second computing resource of a second network and is usable to determine NAT information related to the first packet flow;
determining, by the database, whether the flow identifier is allocable; and
in response to determining the flow identifier is allocable, updating, by the database, an entry table to associate the flow identifier with the packet flow information.

### Claim 22 (depends on 21)

The method of claim 21, further comprising, in response to determining the flow identifier is allocable, transmitting, by the database to the network device, an identifier allocation response including an indication that the flow identifier is allocable.

### Claim 23 (depends on 21)

The method of claim 21, further comprising, in response to determining the flow identifier is not allocable, transmitting, by the database to the network device, an identifier allocation response including an indication that the flow identifier is not allocable and a second flow identifier that is allocable.

### Claim 24 (depends on 23)

The method of claim 23, wherein the second flow identifier is from the first pool of flow identifiers.

### Claim 25 (depends on 23)

The method of claim 23, wherein the second flow identifier is from a second pool of flow identifiers of the plurality of pools.

### Claim 26 (depends on 25)

The method of claim 25, wherein the identifier allocation response includes an indication that the second flow identifier is from the second pool of flow identifiers, and wherein the identifier allocation response is configured to cause the network device to update a second entry table of the network device to associate the second flow identifier with the packet flow information.

### Claim 27 (depends on 23)

The method of claim 23, further comprising, in response to determining the flow identifier is not allocable determining, by the database, the second flow identifier from an allocable sequence of available flow identifiers.

### Claim 28 (depends on 27)

The method of claim 27, wherein determining the second flow identifier comprises selecting, by the database, the second flow identifier based on the second flow identifier being a next available flow identifier according to the allocable sequence.

### Claim 29 (depends on 21)

The method of claim 21, further comprising:
receiving, by the database from the network device, an entry table request for the entry table of the database, wherein the entry table of the database includes the flow identifier, the packet flow information, and the association between the flow identifier and the packet flow information; and
transmitting, by the database to the network device, an entry table response including at a least a portion of the entry table which includes the flow identifier, the packet flow information, and the association between the flow identifier and the packet flow information.

### Claim 30 (depends on 21)

The method of claim 21, further comprising:
receiving, by the database from a second network device configured to perform NAT operations, an entry table request for the entry table of the database, wherein the entry table of the database includes the flow identifier, the packet flow information, and the association between the flow identifier and the packet flow information; and
transmitting, by the database to the second network device, an entry table response including at a least a portion of the entry table which includes the flow identifier, the packet flow information, and the association between the flow identifier and the packet flow information.

### Claim 31

A database comprising:
one or more processors; and
one or more memories storing computer-readable instructions that upon execution by the one or more processors, configure the database to:
receive, from a network device configured to perform network address translation (NAT) operations, an identifier allocation request to determine if a flow identifier is allocable to a packet flow, wherein the identifier allocation request includes the flow identifier and packet flow information associated with the packet flow, wherein the flow identifier is from a first pool of flow identifiers of a plurality of pools, wherein each pool of the plurality of pools is available for NAT operations between a source network and a target computing resource in a target network, and wherein each flow identifier of the first pool is specific to a first packet flow between a first computing resource of a first network and a second computing resource of a second network and is usable to determine NAT information related to the first packet flow;
determine whether the flow identifier is allocable; and
in response to determining the flow identifier is allocable, update an entry table to associate the flow identifier with the packet flow information.

### Claim 32 (depends on 31)

The database of claim 31, wherein the one or more memories store additional instructions that upon execution by the one or more processors, further configure the database to, in response to determining the flow identifier is allocable, transmitting, by the database to the network device, an identifier allocation response including an indication that the flow identifier is allocable.

### Claim 33 (depends on 31)

The database of claim 31, wherein the one or more memories store additional instructions that upon execution by the one or more processors, further configure the database to, in response to determining the flow identifier is not allocable, transmitting, by the database to the network device, an identifier allocation response including an indication that the flow identifier is not allocable and a second flow identifier that is allocable.

### Claim 34 (depends on 33)

The database of claim 33, wherein the second flow identifier is from a second pool of flow identifiers of the plurality of pools.

### Claim 35 (depends on 34)

The database of claim 34, wherein the identifier allocation response includes an indication that the second flow identifier is from the second pool of flow identifiers, and wherein the identifier allocation response is configured to cause the network device to update a second entry table of the network device to associate the second flow identifier with the packet flow information.

### Claim 36

A system comprising:
a database comprising:
first one or more processors; and
first one or more memories storing first computer-readable instructions that upon execution by the first one or more processors, configure the database to:
receive, from a network device configured to perform network address translation (NAT) operations, an identifier allocation request to determine if a flow identifier is allocable to a packet flow, wherein the identifier allocation request includes the flow identifier and packet flow information associated with the packet flow, wherein the flow identifier is from a first pool of flow identifiers of a plurality of pools, wherein each pool of the plurality of pools is available for NAT operations between a source network and a target computing resource in a target network, and wherein each flow identifier of the first pool is specific to a first packet flow between a first computing resource of a first network and a second computing resource of a second network and is usable to determine NAT information related to the first packet flow;
determine whether the flow identifier is allocable; and
in response to determining the flow identifier is allocable, update an entry table to associate the flow identifier with the packet flow information.

### Claim 37 (depends on 36)

The system of claim 36, wherein the database includes further instructions that upon execution by the one or more processors, further configure the database to, in response to determining the flow identifier is allocable, transmitting, by the database to the network device, an identifier allocation response including an indication that the flow identifier is allocable.

### Claim 38 (depends on 36)

The system of claim 36, wherein the database includes further instructions that upon execution by the one or more processors, further configure the database to, in response to determining the flow identifier is not allocable, transmitting, by the database to the network device, an identifier allocation response including an indication that the flow identifier is not allocable and a second flow identifier that is allocable.

### Claim 39 (depends on 38)

The system of claim 38, wherein the second flow identifier is from a second pool of flow identifiers of the plurality of pools.

### Claim 40 (depends on 39)

The system of claim 39, wherein the identifier allocation response includes an indication that the second flow identifier is from the second pool of flow identifiers, and wherein the identifier allocation response is configured to cause the network device to update a second entry table of the network device to associate the second flow identifier with the packet flow information.
