# US 2024/0205197 A1 · Method and apparatus for metadata conversion with a flow identifier of a packet sequence in a tunnel-less sdwan

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

- Number: US 2024/0205197 A1
- Document ID: US20240205197A1
- Status: Published application
- Kind: A1
- Application number: 18/236,771
- Filed: 2023-08-22
- Published: 2024-06-20
- Earliest claimed: 2022-12-20
- Assignees: Versa Networks, Inc.
- Applicants: Versa Networks, Inc.
- Inventors: Fidelis Prashanth; Jayakrishnan Iyer; Apurva Mehta
- Web page: https://patentgrep.com/patent/US20240205197A1

## CPC

- H04L 45/28: using route fault recovery
- H04L 47/2483: involving identification of individual flows
- H04L 43/0847: {Transmission error}
- H04L 45/566: {Routing instructions carried by the data packet, e.g. active networks}
- H04L 47/34: ensuring sequence integrity, e.g. using sequence numbers
- H04L 63/029: {Firewall traversal, e.g. tunnelling or, creating pinholes}
- H04L 63/0428: {wherein the data content is protected, e.g. by encrypting or encapsulating the payload}
- H04L 2212/00: Encapsulation of packets
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

A flow identifier is described for packet sequences through a secure tunnel of an SD-WAN in a tunnel-less mode. A method includes receiving a sequence of packets from a first client at the first hub, the sequence of packets each having a same flow, facilitating a secure tunnel between the first hub and the second hub, assigning a flow identifier to the sequence of packets, converting fields from a header of the packet to a metadata supplement to the packet to form a reduced packet, encapsulating the reduced packet in a wrapper that includes the flow identifier, and sending the packet of the sequence of packets from the first hub to the second hub the secure tunnel.

## Claims

### Claim 1

A method to route traffic through a software-defined wide area network (SD-WAN) between a first hub and a second hub, the method comprising:
receiving a sequence of packets from a first client at the first hub, the sequence of packets each having a same flow;
facilitating a secure tunnel between the first hub and the second hub;
assigning a flow identifier to the sequence of packets;
converting fields from a header of the packet to a metadata supplement to the packet to form a reduced packet;
encapsulating the reduced packet in a wrapper that includes the flow identifier; and
sending the packet of the sequence of packets from the first hub to the second hub through the secure tunnel.

### Claim 2 (depends on 1)

The method of claim 1, wherein converting fields comprises:
removing the header;
combining the header and the flow identifier to form metadata; and
attaching the metadata to a payload of the reduced packet before encapsulating the reduced packet.

### Claim 3 (depends on 1)

The method of claim 1, further comprising
associating a packet reduction mode with the flow identifier,
wherein converting fields comprises converting fields from a header of the packet to a metadata supplement to the packet to form a reduced packet in accordance with the packet reduction mode.

### Claim 4 (depends on 3)

The method of claim 3, wherein the packet reduction mode includes a compression level configured to indicate an amount that the fields of the packet header are compressed in the metadata supplement.

### Claim 5 (depends on 3)

The method of claim 3, wherein the packet reduction mode includes an encryption level configured to indicate an amount of encryption applied to the fields in the metadata supplement.

### Claim 6 (depends on 5)

The method of claim 5, wherein the encryption level is configured to indicate no encryption.

### Claim 7 (depends on 1)

The method of claim 1, further comprising performing a capabilities exchange between the first hub and the second hub for the flow identifier before converting the fields.

### Claim 8 (depends on 7)

The method of claim 7, wherein the capabilities exchange includes determining a packet reduction mode.

### Claim 9 (depends on 1)

The method of claim 1, wherein establishing the secure tunnel comprises establishing a session, the method further comprising:
encapsulating a start packet of the sequence of packets in a wrapper that includes the flow identifier and the header of the encapsulated start packet;
sending the encapsulated start packet from the first hub to the second hub through the secure tunnel; and
receiving an acknowledgement of the flow identifier from the second hub and updating a state of the session with the acknowledgement.

### Claim 10 (depends on 1)

The method of claim 1, further comprising:
receiving a second flow identifier from the second hub through the secure tunnel;
saving the second flow identifier;
receiving reply encapsulated packets directed to a source address of the sequence of packets; and
using the second flow identifier to identify subsequent reply encapsulated packets received from the second hub.

### Claim 11 (depends on 10)

The method of claim 10, further comprising:
decapsulating the reply encapsulated packets;
recreating headers of the decapsulated reply encapsulated packets based on metadata supplements of the decapsulated reply packets and a packet reduction mode associated with the second flow identifier; and
forwarding the decapsulated reply packets to the source address of the sequence of packets.

### Claim 12 (depends on 1)

The method of claim 1, further comprising:
receiving an error message from the second hub including the flow identifier;
facilitating a secure tunnel again between the first hub and the second hub in response to receiving the error message;
assigning a second flow identifier to the sequence of packets;
encapsulating a second start packet of the sequence of packets in a wrapper, the wrapper including the second flow identifier; and
sending the encapsulated second start packet of the sequence of packets from the first hub to the second hub through the secure tunnel.

### Claim 13 (depends on 1)

The method of claim 1, wherein the sequence of packets each having a same flow each have a same 5-tuple.

### Claim 14 (depends on 1)

The method of claim 1, further comprising increasing a value of a maximum segment size parameter of a header of the reduced packet before encapsulating the reduced packet.

### Claim 15

A non-transitory computer-readable storage medium containing program instructions, which when executed by the computer cause the computer to perform operations comprising:
receiving a sequence of packets from a first client at a first hub, the sequence of packets each having a same flow;
facilitating a secure tunnel between the first hub and a second hub;
assigning a flow identifier to the sequence of packets;
converting fields from a header of the packet to a metadata supplement to the packet to form a reduced packet;
encapsulating the reduced packet in a wrapper that includes the flow identifier; and
sending the packet of the sequence of packets from the first hub to the second hub through the secure tunnel.

### Claim 16 (depends on 15)

The medium of claim 15, wherein converting fields comprises removing the header and combining the header and the flow identifier to form metadata attached to a payload of the reduced packet before encapsulating the reduced packet.

### Claim 17 (depends on 15)

The medium of claim 15, further comprising
associating a packet reduction mode with the flow identifier,
wherein converting fields comprises converting fields from a header of the packet to a metadata supplement to the packet to form a reduced packet in accordance with the packet reduction mode.

### Claim 18 (depends on 17)

The medium of claim 17, wherein the packet reduction mode includes a compression level configured to indicate an amount that the fields are compressed in the metadata supplement.

### Claim 19 (depends on 17)

The medium of claim 17, wherein the packet reduction mode includes an encryption level configured to indicate an amount of encryption applied to the fields in the metadata supplement.

### Claim 20

A network node comprising:
a communications interface configured to receive a sequence of packets from a first client at the network node, the sequence of packets each having a same flow;
a session management module configured to facilitate a secure tunnel and an associated session between the network node and the hub; and
a processor configured to assign a flow identifier to the sequence of packets, to convert fields from a header of the packet to a metadata supplement to the packet to form a reduced packet, and to encapsulate the reduced packet in a wrapper that includes the flow identifier,
wherein the communications interface is further to send the packet of the sequence of packets from the network node to the hub through the secure tunnel.

### Claim 21 (depends on 20)

The network node of claim 20, wherein the processor is further configured to perform a capabilities exchange between the network node and the hub for the flow identifier before converting the fields.

### Claim 22 (depends on 20)

The network node of claim 20, wherein:
the processor is further configured to encapsulate a start packet of the sequence of packets in a wrapper that includes the flow identifier, the header of the encapsulated start packet including the associated fields; and
the communications interface is further configured to send the encapsulated start packet from the network node to the hub through the secure tunnel, and to receive an acknowledgement of the flow identifier from the hub, the session management module updating a state of the session with the acknowledgement.
