# US 2012/0250682 A1 · Frameworks and interfaces for offload device-based packet processing

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

- Number: US 2012/0250682 A1
- Document ID: US20120250682A1
- Status: Published application
- Kind: A1
- Application number: 13/076,347
- Filed: 2011-03-30
- Published: 2012-10-04
- Earliest claimed: 2011-03-30
- Assignees: Amazon Technologies, Inc.
- Inventors: Pradeep Vincent; Matthew D. Klein; Samuel J. McKelvie
- Web page: https://patentgrep.com/patent/US20120250682A1

## CPC

- G06F 9/45558: {Hypervisor-specific management and integration aspects}
- H04L 12/4633: {Interconnection of networks using encapsulation techniques, e.g. tunneling}
- H04L 41/082: the condition being updates or upgrades of network functionality
- H04L 45/74: Address processing for routing
- H04L 63/0272: {Virtual private networks}
- H04L 63/20: {for managing network security; network security policies in general (filtering policies H04L63/0227)}
- G06F 2009/45595: {Network integration; Enabling network access in virtual machine instances}
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

High-speed processing of packets to, and from, a virtualization environment can be provided while utilizing hardware-based segmentation offload and other such functionality. A hardware vendor such as a network interface card (NIC) manufacturer can enable the hardware to support open and proprietary stateless tunneling in conjunction with a protocol such as single root I/O virtualization (SR-IOV) in order to implement a virtualized overlay network. The hardware can utilize various rules, for example, that can be used by the NIC to perform certain actions, such as to encapsulate egress packets and decapsulate packets.

## Claims

### Claim 1

A framework for processing data packets in a multi-tenant environment, comprising:
at least one processor; and
memory including instructions that, when executed by the processor, enable the framework to:
communicate with one or more distributed services to load one or more per-tenant network specifications;
instruct at least one offload device to execute the loaded per-tenant network specifications;
manage a set of rules for the at least one offload device when the at least one offload device is unable to concurrently store all of the set of rules; and
deliver data packets to an appropriate destination for each of a plurality of traffic types.

### Claim 2 (depends on 1)

The framework of claim 1, wherein the framework provides a software management interface operable to execute in a trusted host domain.

### Claim 3 (depends on 2)

The framework of claim 2, wherein the software management interface is further operable to manage packets that require special processing.

### Claim 4 (depends on 3)

The framework of claim 3, wherein the packets that require special processing include multicast packets, broadcast packets, and address resolution protocol (ARP) packets.

### Claim 5 (depends on 2)

The framework of claim 2, wherein the software management interface is further operable to manage functionality including at least one of domain name service (DNS), security interfacing, and web server interfacing.

### Claim 6 (depends on 2)

The framework of claim 2, wherein the software management interface is operable to configure network statistics that need to be collected, and statistics to be maintained, by the offload device.

### Claim 7 (depends on 1)

The framework of claim 1, wherein the per-tenant network specifications include specifications for at least one of throttling data packets, operating security groups, and communicating between partner components.

### Claim 8 (depends on 1)

The framework of claim 1, wherein the per-tenant network specifications are SR-IOV network specifications.

### Claim 9 (depends on 1)

The framework of claim 1, wherein the per-tenant network specifications are processed in real time as the specifications change.

### Claim 10 (depends on 1)

The framework of claim 1, wherein manage a set of rules for the at least one offload device includes loading a first subset of rules in an offload device while processing a second subset of rules using software strapping.

### Claim 11 (depends on 10)

The framework of claim 10, wherein the first subset of rules is utilized more often than the second subset of rules.

### Claim 12 (depends on 1)

The framework of claim 1, wherein the per-tenant specifications enable a hardware vendor to support multiple protocols without obtaining specific information about those multiple protocols.

### Claim 13 (depends on 1)

The framework of claim 1, wherein the traffic types include at least one of traffic destined for a trusted host platform and traffic destined for a virtual tenant.

### Claim 14

An offload device, comprising:
a processor; and
memory storing instructions that, when executed by the processor, enable the offload device to:
expose the offload device as a hardware device;
perform at least a portion of processing of a user data packet received to a physical function associated with the offload hardware device, the processing including at least stripping an inner and outer header of the data packet, performing any packet modification, and forwarding the user data packet to an internal virtual function, the internal virtual function operable to deliver the user data packet to a guest virtual machine

### Claim 15 (depends on 14)

The offload device of claim 14, wherein the processing includes removing at least one outer encapsulation header from the user data packet.

### Claim 16 (depends on 14)

The offload device of claim 14, wherein the offload device is a network interface card (NIC).

### Claim 17 (depends on 14)

The offload device of claim 14, wherein the offload device is operable to support multiple protocols without obtaining specific information about those multiple protocols.

### Claim 18

A method for processing data packets in a multi-tenant environment, comprising:
communicating with one or more distributed services to load one or more per-tenant network specifications;
instructing at least one offload device to execute the loaded per-tenant network specifications;
managing a set of rules for the at least one offload device when the at least one offload device is unable to concurrently store all of the set of rules; and
delivering data packets to an appropriate destination for each of a plurality of traffic types.

### Claim 19 (depends on 18)

The method of claim 18, further comprising:
exposing a software management interface operable to execute in a trusted host domain.

### Claim 20 (depends on 19)

The method of claim 19, wherein the software management interface is further operable to manage functionality including at least one of domain name service (DNS), security interfacing, and web server interfacing.

### Claim 21 (depends on 19)

The method of claim 19, wherein the offload device operates according to SR-IOV network specifications.
