# US 2021/0243247 A1 · Service mesh offload to network devices

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

- Number: US 2021/0243247 A1
- Document ID: US20210243247A1
- Status: Published application
- Kind: A1
- Application number: 17/238,960
- Filed: 2021-04-23
- Published: 2021-08-05
- Earliest claimed: 2021-04-23
- Assignees: Intel Corporation
- Applicants: Intel Corporation
- Inventors: Shaopeng HE; Cunming LIANG; Haitao KANG; Hongjun NI; Jiang YU; Ziye YANG; Anjali Singhai JAIN; Daniel DALY; Yadong LI; Ping YU; Bo CUI; Jingjing WU; Liang MA; Changpeng LIU
- Web page: https://patentgrep.com/patent/US20210243247A1

## CPC

- H04L 41/5054: Automatic deployment of services triggered by the service manager, e.g. service implementation by automatic configuration of network components
- H04L 67/10: in which an application is distributed across nodes in the network (software deployment G06F8/60; multiprogramming arrangements G06F9/46)
- H04L 41/40: using virtualisation of network functions or resources, e.g. SDN or NFV entities
- H04L 67/51: Discovery or management thereof, e.g. service location protocol [SLP] or web services
- H04L 67/63: Routing a service request depending on the request content or context
- H04L 67/1001: for accessing one among a plurality of replicated servers
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

Examples described herein relate to a switch comprising a programmable data plane pipeline, wherein the programmable data plane pipeline is configured to provide microservice-to-microservice communications within a service mesh. In some examples, to provide microservice-to-microservice communications within a service mesh, the programmable data plane pipeline is to perform a forwarding operation for a communication from a first microservice to a second microservice. In some examples, to perform a forwarding operation for a communication from a first microservice to a second microservice, the programmable data plane pipeline is to utilize a reliable transport protocol.

## Claims

### Claim 1

A system comprising:
a switch comprising a programmable data plane pipeline, wherein the programmable data plane pipeline is configured to provide microservice-to-microservice communications within a service mesh.

### Claim 2 (depends on 1)

The system of claim 1, wherein to provide microservice-to-microservice communications within a service mesh, the programmable data plane pipeline is to perform a forwarding operation for a communication from a first microservice to a second microservice.

### Claim 3 (depends on 2)

The system of claim 2, wherein to perform a forwarding operation for a communication from a first microservice to a second microservice, the programmable data plane pipeline is to utilize a reliable transport protocol.

### Claim 4 (depends on 1)

The system of claim 1, wherein the programmable data plane pipeline is to select a processor, virtual machine, or container to execute an instance of a target microservice based on hardware resource availability.

### Claim 5 (depends on 1)

The system of claim 1, wherein the programmable data plane pipeline is configured to program at least one programmable data plane pipeline in at least one network device associated with a target microservice within the service mesh, wherein to program at least one programmable data plane pipeline in at least one network device comprises program one or more of: a reliable transport protocol, encryption and decryption scheme, and/or telemetry reporting.

### Claim 6 (depends on 1)

The system of claim 1, wherein the programmable data plane pipeline is configured to provide microservice-to-microservice communications within a service mesh by communication with a service mesh controller and wherein the communication with a service mesh controller comprises communication between an instance of Istio with an Envoy application program interface (API).

### Claim 7

A method comprising:
in programmable packet processing pipelines of network devices associated with a service mesh of microservices, performing selection of microservices for execution and providing communication within the service mesh of microservices.

### Claim 8 (depends on 7)

The method of claim 7, wherein the network devices comprise a switch that includes a programmable packet processing pipeline and wherein the programmable packet processing pipeline of the switch performs microservice load balancing and traffic management.

### Claim 9 (depends on 7)

The method of claim 7, wherein the network devices comprise a network interface controller that includes a programmable packet processing pipeline and wherein the programmable packet processing pipeline of the network interface controller communicates messages between microservices using a reliable transport protocol.

### Claim 10 (depends on 7)

The method of claim 7, wherein the network devices comprise a network interface controller that includes a programmable packet processing pipeline, wherein the programmable packet processing pipeline of the network interface controller is associated with a gateway to a service mesh, and wherein the packet processing pipeline of the network interface controller associated with a gateway performs one service-to-one port binding, implementation of a reliable transport protocol, packet encryption or decryption, and telemetry reporting.

### Claim 11 (depends on 7)

The method of claim 7, comprising:
configuring the programmable packet processing pipelines of network devices associated with a service mesh of microservices by communication with a service mesh controller, wherein the communication with a service mesh controller comprises communication between an instance of Istio with an Envoy application program interface (API).

### Claim 12 (depends on 7)

The method of claim 7, comprising:
receiving a request to perform a service at a gateway among the network devices associated with a service mesh of microservices, wherein the gateway performs protocol translation and provides the request to a switch among the network devices associated with a service mesh of micro services.

### Claim 13 (depends on 12)

The method of claim 12, comprising:
at the switch:
selecting an instance of a microservice to execute;
sending a request to execute the selected microservice; and
receiving a response to the request to execute the selected microservice, wherein the response comprises data to forward or a request to perform a second microservice.

### Claim 14 (depends on 7)

The method of claim 7, wherein the microservices of the mesh of microservices execute on a server, a network device, and/or an infrastructure processing unit (IPU).

### Claim 15

A non-transitory computer-readable medium comprising instructions, that if executed by one or more processors, cause the one or more processors to:
configure a data plane of a switch to:
select a microservice to execute in response to a service request received at a service mesh and
configure at least one network device associated with the service mesh to apply a reliable transport protocol to communicate with the switch, wherein the configure at least one network device associated with the service mesh to apply a reliable transport protocol to communicate with the switch comprises configure at least one data plane of the at least one network device to apply a reliable transport protocol to communicate with the switch.

### Claim 16 (depends on 15)

The computer-readable medium of claim 15, wherein the switch is to perform load balancing of microservice execution and traffic management within the service mesh.

### Claim 17 (depends on 15)

The computer-readable medium of claim 15, wherein the at least one network device associated with the service mesh comprises a network interface controller and/or an infrastructure processing unit (IPU).

### Claim 18 (depends on 15)

The computer-readable medium of claim 15, wherein the reliable transport protocol to communicate with the switch is based on Address Family of eXpress Data Path (AF_XDP) socket queues for acknowledgment of packet receipt and received packet re-ordering.

### Claim 19 (depends on 15)

The computer-readable medium of claim 15, comprising instructions stored thereon, that if executed by one or more processors, cause the one or more processors to:
configure a gateway network device to perform protocol translation to a transport protocol used in the service mesh and provide the received service request to the switch.

### Claim 20 (depends on 15)

The computer-readable medium of claim 15, wherein the microservice executes on a server, a network device, and/or an infrastructure processing unit (IPU).
