# US 2024/0205148 A1 · Data packet traffic using speculative unified flow

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

- Number: US 2024/0205148 A1
- Document ID: US20240205148A1
- Status: Published application
- Kind: A1
- Application number: 18/069,166
- Filed: 2022-12-20
- Published: 2024-06-20
- Earliest claimed: 2022-12-20
- Assignees: Microsoft Technology Licensing, LLC
- Applicants: Microsoft Technology Licensing, LLC
- Inventors: Harish SRINIVASAN; Tian TAN; Milan DASGUPTA; Denys GURZHII
- Web page: https://patentgrep.com/patent/US20240205148A1

## CPC

- H04L 45/74: Address processing for routing
- H04L 47/2441: relying on flow classification, e.g. using integrated services [IntServ]
- H04L 45/76: Routing in software-defined topologies, e.g. routing between virtual machines
- H04L 45/38: {Flow based routing}
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

A method is presented for processing directional data packet traffic. A main data packet, characterized by a plurality of main data packet characteristics including at least a first IP address representing a first source, and a second IP address representing a first destination, is received at a rule processing engine. Based on the main data packet characteristics, a set of rules for processing the main data packet is retrieved. A main direction unified flow for the main data packet, and a speculative reverse direction unified flow for a reverse direction data packet are generated based on the main data packet characteristics and the retrieved set of rules. The main data packet is processed based on the main direction unified flow. Responsive to receiving the reverse direction data packet, the reverse direction data packet is processed based on the speculative reverse direction unified flow.

## Claims

### Claim 1

A method for processing directional data packet traffic between a client device and a virtual machine, comprising:
receiving a main data packet at a rule processing engine, the main data packet characterized by a plurality of main data packet characteristics including at least a first internet protocol (IP) address representing a first source, and a second IP address representing a first destination;
based on the plurality of main data packet characteristics, retrieving a set of rules for processing the main data packet;
generating a main direction unified flow for the main data packet based on the main data packet characteristics and the retrieved set of rules;
generating a speculative reverse direction unified flow for a reverse direction data packet based on the main data packet characteristics and the retrieved set of rules;
processing the main data packet based on the main direction unified flow; and
responsive to receiving the reverse direction data packet, processing the reverse direction data packet based on the speculative reverse direction unified flow.

### Claim 2 (depends on 1)

The method of claim 1, wherein the reverse direction data packet is characterized by a plurality of reverse direction data packet characteristics including at least the first IP address representing a second destination and the second IP address representing a second source.

### Claim 3 (depends on 2)

The method of claim 2, wherein processing the reverse direction data packet based on the speculative reverse direction unified flow further comprises:
based on the plurality of reverse direction data packet characteristics, converting the speculative reverse direction unified flow to a standard reverse direction unified flow; and
processing the reverse direction data packet based on the standard reverse direction unified flow.

### Claim 4 (depends on 3)

The method of claim 3, wherein converting the speculative reverse direction unified flow to the standard reverse direction unified flow comprises adjusting one or more values in the speculative reverse direction unified flow based on the plurality of reverse direction data packet characteristics.

### Claim 5 (depends on 1)

The method of claim 1, wherein the main direction unified flow and the speculative reverse direction unified flow are associated via a common flow state entry.

### Claim 6 (depends on 5)

The method of claim 5, wherein the common flow state entry is a two-bit entry, indicating success or failure for each of the main direction unified flow and the speculative reverse direction unified flow.

### Claim 7 (depends on 5)

The method of claim 5, wherein an additional shared state for the main direction unified flow and the speculative reverse direction unified flow is indicated by the common flow state entry.

### Claim 8 (depends on 1)

The method of claim 1, wherein the first IP address is for the virtual machine.

### Claim 9 (depends on 1)

The method of claim 1, wherein the second IP address is for the virtual machine.

### Claim 10

A flow processing system for trafficking directional data packets between a source device and a destination device, comprising:
a memory; and
a rule processing engine, comprising:
one or more flow generation cores configured to:
receive a main data packet, the main data packet characterized by a plurality of main data packet characteristics including at least a first internet protocol (IP) address representing a first source, and a second IP address representing a first destination;
retrieve, from memory, a set of rules for processing the main data packet based on the plurality of main data packet characteristics;
generate a main direction unified flow for the main data packet based on the main data packet characteristics and the retrieved set of rules; and
generate a speculative reverse direction unified flow for a reverse direction data packet based on the main data packet characteristics and the retrieved set of rules; and
one or more flow processing cores configured to:
process the main data packet based on the main direction unified flow; and
responsive to receiving the reverse direction data packet, process the reverse direction data packet based on the speculative reverse direction unified flow.

### Claim 11 (depends on 10)

The flow processing system of claim 10, wherein the reverse direction data packet is characterized by a plurality of reverse direction data packet characteristics including at least the first IP address representing a second destination and the second IP address representing a second source.

### Claim 12 (depends on 11)

The flow processing system of claim 11, wherein processing the reverse direction data packet based on the speculative reverse direction unified flow further comprises:
at the one or more flow generation cores, based on the plurality of reverse direction data packet characteristics, convert the speculative reverse direction unified flow to a standard reverse direction unified flow; and
at the one or more flow processing cores, process the reverse direction data packet based on the standard reverse direction unified flow.

### Claim 13 (depends on 12)

The flow processing system of claim 12, wherein converting the speculative reverse direction unified flow to the standard reverse direction unified flow comprises adjusting one or more values in the speculative reverse direction unified flow based on the plurality of reverse direction data packet characteristics.

### Claim 14 (depends on 10)

The flow processing system of claim 10, wherein the main direction unified flow and the speculative reverse direction unified flow are associated via a common flow state entry stored in the memory.

### Claim 15 (depends on 14)

The flow processing system of claim 14, wherein the common flow state entry is a two-bit entry, indicating success or failure for each of the main direction unified flow and the speculative reverse direction unified flow.

### Claim 16 (depends on 14)

The flow processing system of claim 14, wherein an additional shared state for the main direction unified flow and the speculative reverse direction unified flow is indicated by the common flow state entry.

### Claim 17 (depends on 10)

The flow processing system of claim 10, wherein the first IP address is for a virtual machine.

### Claim 18 (depends on 10)

The flow processing system of claim 10, wherein the second IP address is for a virtual machine.

### Claim 19

A method for processing directional data packet traffic between a client device and a virtual machine, comprising:
receiving a main data packet at a network interface, the main data packet characterized by a plurality of main data packet characteristics including at least a first internet protocol (IP) address representing a first source, and a second IP address representing a first destination;
based on the plurality of main data packet characteristics, retrieving a set of rules for processing the main data packet, including a rule for modifying the second IP address to a third IP address;
generating a main direction unified flow for the main data packet based on the main data packet characteristics and the retrieved set of rules;
generating a speculative reverse direction unified flow for a reverse direction data packet based on the main data packet characteristics and the retrieved set of rules;
processing the main data packet based on the main direction unified flow at least by modifying the second IP address to the third IP address; and
responsive to receiving the reverse direction data packet, processing the reverse direction data packet based on the speculative reverse direction unified flow.

### Claim 20 (depends on 19)

The method of claim 19, wherein processing the reverse direction data packet based on the speculative reverse direction unified flow comprises at least modifying the third IP address to the second IP address.
