# US 2022/0030058 A1 · Distributed service chain across multiple clouds

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

- Number: US 2022/0030058 A1
- Document ID: US20220030058A1
- Status: Published application
- Kind: A1
- Application number: 17/492,626
- Filed: 2021-10-03
- Published: 2022-01-27
- Earliest claimed: 2019-10-30
- Assignees: VMware, Inc.
- Applicants: VMware, Inc.
- Inventors: Jeremy Tidemann; Constantine Polychronopoulos; Marc-Andre Bordeleau; Edward Choh; Ojas Gupta; Robert Kidd; Raja Kommula; Georgios Oikonomou; Mingjie Zhao
- Web page: https://patentgrep.com/patent/US20220030058A1

## CPC

- H04L 67/1012: based on compliance of requirements or conditions with available server resources
- H04L 47/2441: relying on flow classification, e.g. using integrated services [IntServ]
- H04L 47/2475: for supporting traffic characterised by the type of applications
- H04L 47/2483: involving identification of individual flows
- H04L 67/51: Discovery or management thereof, e.g. service location protocol [SLP] or web services
- H04L 69/22: Parsing or analysis of headers
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

Some embodiments of the invention provide novel methods for performing services on data messages passing through a network connecting one or more datacenters, such as software defined datacenters (SDDCs). The method of some embodiments uses service containers executing on host computers to perform different chains (e.g., ordered sequences) of services on different data message flows. For a data message of a particular data message flow that is received or generated at a host computer, the method in some embodiments uses a service classifier executing on the host computer to identify a service chain that specifies several services to perform on the data message. For each service in the identified service chain, the service classifier identifies a service container for performing the service. The service classifier then forwards the data message to a service forwarding element to forward the data message through the service containers identified for the identified service chain. The service classifier and service forwarding element are implemented in some embodiments as processes that are defined as hooks in the virtual interface endpoints (e.g., virtual Ethernet ports) of the host computer's operating system (e.g., Linux operating system) over which the service containers execute.

## Claims

### Claim at position 1

1-20. (canceled)

### Claim 21

A method of performing services on a data message, the method comprising:
in a first datacenter,
identifying, for the data message, a service chain comprising a set of two or more services to perform on the data message, and a service path comprising a plurality of service machines in first and second datacenters for performing the services of the service chain;
using a first service machine executing in the first datacenter to perform a first service in the identified service chain;
using a service forwarding proxy to encapsulate the data message with an encapsulating header, to store in the encapsulating header an identifier that identifies the service path in the second datacenter, and to forward the encapsulated data message to the second datacenter for processing by a second machine to perform a second service in the identified service chain.

### Claim 22 (depends on 21)

The method of claim 21 further comprising
using a third service machine executing in the first datacenter to perform a third service in the identified service chain after the first service but before the second service,
wherein the service forwarding proxy forwards the encapsulated data message to the second datacenter after the third service is performed.

### Claim 23 (depends on 22)

The method of claim 22, wherein to perform the first and third services, the data message is not encapsulated as the data message is forwarded to the first and third service machines in the first datacenter.

### Claim 24 (depends on 21)

The method of claim 21 further comprising:
after identifying the service chain, forwarding the data message to a service forwarding element to forward the data message to the first service machine, said service forwarding element forwarding the data message to the first service machine without encapsulating the data message.

### Claim 25 (depends on 21)

The method of claim 21, wherein the service forwarding element uses a first type of forwarding to forward the data message to each service machine in the first datacenter, while the service forwarding proxy uses a different, second type of forwarding to forward the data message from the first datacenter to the second datacenter.

### Claim 26 (depends on 21)

The method of claim 21 further comprising using, for each service in the identified service chain, a service selector for that service to select a service machine to perform the service.

### Claim 27 (depends on 21)

The method of claim 21, wherein the identifier is a service path identifier, the method further comprising specifying the service path identifier that uniquely identifies the service path in both the first and second datacenters.

### Claim 28 (depends on 27)

The method of claim 27, wherein
the first and second datacenters are part of two different public clouds,
the service forwarding proxy is a cross-cloud forwarding proxy, and
the service path identifier uniquely identifies the service path in both public clouds.

### Claim 29 (depends on 21)

The method of claim 21, wherein a service classifier identifies the service chain, the method further comprising
at the service classifier:
identifying, for each service in the identified service chain, a service machine for performing the service;
specifying a first service path identifier that identifies a set of service machines in the first datacenter that has been identified for performing a group of services in the identified service chain;
at the service forwarding proxy converting the first service path identifier into the identifier that is stored in the encapsulating header and that uniquely identifies the service path in the second datacenter

### Claim 30 (depends on 31)

The method of claim 31, wherein the service forwarding proxy forwards data messages associated with a plurality of service chains to the second datacenter, and processes data messages received from the second datacenter for the plurality of service chains.

### Claim 31

A non-transitory machine readable medium storing a program for execution by a set of processors of a computer in a first datacenter to perform services on a data message, the program comprising sets of instructions for:
identifying, for the data message, a service chain comprising a set of two or more services to perform on the data message, and a service path comprising a plurality of service machines in first and second datacenters for performing the services of the service chain;
using a first service machine executing in the first datacenter to perform a first service in the identified service chain;
using a service forwarding proxy to encapsulate the data message with an encapsulating header, to store in the encapsulating header an identifier that identifies the service path in the second datacenter, and to forward the encapsulated data message to the second datacenter for processing by a second machine to perform a second service in the identified service chain.

### Claim 32 (depends on 31)

The non-transitory machine readable medium of claim 31, wherein the program further comprises a set of instructions for using a third service machine executing in the first datacenter to perform a third service in the identified service chain after the first service but before the second service, wherein the service forwarding proxy forwards the encapsulated data message to the second datacenter after the third service is performed.

### Claim 33 (depends on 32)

The non-transitory machine readable medium of claim 32, wherein to perform the first and third services, the data message is not encapsulated as the data message is forwarded to the first and third service machines in the first datacenter.

### Claim 34 (depends on 31)

The non-transitory machine readable medium of claim 31, wherein the program further comprises a set of instructions for forwarding, after identifying the service chain, the data message to a service forwarding element to forward the data message to the first service machine, said service forwarding element forwarding the data message to the first service machine without encapsulating the data message.

### Claim 35 (depends on 31)

The non-transitory machine readable medium of claim 31, wherein the service forwarding element uses a first type of forwarding to forward the data message to each service machine in the first datacenter, while the service forwarding proxy uses a different, second type of forwarding to forward the data message from the first datacenter to the second datacenter.

### Claim 36 (depends on 31)

The non-transitory machine readable medium of claim 31, wherein the program further comprises a set of instructions for using, for each service in the identified service chain, a service selector for that service to select a service machine to perform the service.

### Claim 37 (depends on 31)

The non-transitory machine readable medium of claim 31, wherein the identifier is a service path identifier, the method further comprising specifying the service path identifier that uniquely identifies the service path in both the first and second datacenters.

### Claim 38 (depends on 37)

The non-transitory machine readable medium of claim 37, wherein
the first and second datacenters are part of two different public clouds,
the service forwarding proxy is a cross-cloud forwarding proxy, and
the service path identifier uniquely identifies the service path in both public clouds.

### Claim 39 (depends on 31)

The non-transitory machine readable medium of claim 31, wherein a service classifier identifies the service chain, the method further comprising
at the service classifier:
identifying, for each service in the identified service chain, a service machine for performing the service;
specifying a first service path identifier that identifies a set of service machines in the first datacenter that has been identified for performing a group of services in the identified service chain;
at the service forwarding proxy converting the first service path identifier into the identifier that is stored in the encapsulating header and that uniquely identifies the service path in the second datacenter

### Claim 40 (depends on 31)

The non-transitory machine readable medium of claim 31, wherein the service forwarding proxy forwards data messages associated with a plurality of service chains to the second datacenter, and processes data messages received from the second datacenter for the plurality of service chains.
