# US 2026/0154111 A1 · Sidecar deployment method and apparatus in service mesh, electronic device and storage medium

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

- Number: US 2026/0154111 A1
- Document ID: US20260154111A1
- Status: Published application
- Kind: A1
- Application number: 18/704,713
- Filed: 2022-10-09
- Published: 2026-06-04
- Earliest claimed: 2021-10-29
- Assignees: Zte Corporation
- Applicants: Zte Corporation
- Inventors: Jiange PU; Jin ZHANG; Qiang ZHANG
- Web page: https://patentgrep.com/patent/US20260154111A1

## CPC

- G06F 9/5027: {the resource being a machine, e.g. CPUs, Servers, Terminals}
- G06F 9/5072: {Grid computing}
- H04L 67/10: in which an application is distributed across nodes in the network (software deployment G06F8/60; multiprogramming arrangements G06F9/46)
- H04L 67/34: {involving the movement of software or configuration parameters (network booting or remote initial program loading [RIPL] G06F9/4416)}
- H04L 67/51: Discovery or management thereof, e.g. service location protocol [SLP] or web services
- G06F 2209/542: Intercept
- 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

The present disclosure provides a method for sidecar deployment in a service mesh, an electronic device and a storage medium. The method for sidecar deployment in a service mesh may include: determining, according to a resource requirement and a reliability requirement of a microservice, a sidecar type configured for the microservice, wherein the sidecar type comprises an exclusive sidecar and a shared sidecar; and deploying a sidecar for the microservice according to the sidecar type, and allocating a published port to the microservice. In response to the sidecar type configured for the microservice being the shared sidecar, the published port allocated to the microservice is different from a published port of another microservice sharing the sidecar.

## Claims

### Claim 1

A method for deploying a sidecar in a service mesh, comprising:
determining, according to a resource requirement and a reliability requirement of a microservice, a sidecar type configured for the microservice, wherein the sidecar type comprises an exclusive sidecar and a shared sidecar; and
deploying a sidecar for the microservice according to the sidecar type, and allocating a published port to the microservice,
wherein in response to the sidecar type configured for the microservice being the shared sidecar, the published port allocated to the microservice is different from a published port of another microservice sharing the sidecar.

### Claim 2 (depends on 1)

The method for deploying a sidecar in a service mesh of claim 1, wherein after determining a sidecar type configured for the microservice and prior to deploying a sidecar for the microservice according to the sidecar type, the method further comprises:
configuring a parameter of the sidecar for the microservice, wherein the parameter comprises one or any combination of:
an identifier (ID) of the sidecar, a name of the sidecar, a resource quota of the sidecar, and a quantity of sidecars.

### Claim 3 (depends on 2)

The method for deploying a sidecar in a service mesh of claim 2, wherein in response to the parameter of the sidecar comprising the ID of the sidecar, deploying a sidecar for the microservice according to the sidecar type comprises:
in response to the sidecar type configured for the microservice being the shared sidecar, determining, according to the ID of the sidecar, an existence status indicating whether a sidecar having an identical ID exists in the service mesh; and
deploying the sidecar for the microservice according to the existence status.

### Claim 4 (depends on 3)

The method for deploying a sidecar in a service mesh of claim 3, wherein deploying the sidecar for the microservice according to the existence status comprises:
associating the sidecar having the identical ID with the microservice, in response to the existence status indicating that the sidecar having the identical ID exists in the service mesh; or
creating a sidecar and associating the created sidecar with the microservice, in response to the existence status indicating that the sidecar having the identical ID does not exist in the service mesh.

### Claim 5 (depends on 1)

The method for deploying a sidecar in a service mesh of claim 1, wherein after allocating a published port to the microservice, the method further comprises:
disassociating the sidecar from the microservice in response to a need to uninstall the microservice, and in response to the sidecar type of the sidecar associated with the microservice being the shared sidecar, determining whether to delete the sidecar according to a number of microservices associated with the sidecar.

### Claim 6 (depends on 5)

The method for deploying a sidecar in a service mesh of claim 5, wherein determining whether to delete the sidecar according to a number of microservices associated with the sidecar comprises:
maintaining the sidecar in response to the number of microservices associated with the sidecar being greater than 0; or
deleting the sidecar in response to the number of microservices associated with the sidecar being not greater than 0.

### Claim 7 (depends on 1)

The method for deploying a sidecar in a service mesh of claim 1, wherein deploying a sidecar for the microservice according to the sidecar type comprises:
creating a sidecar and associating the created sidecar with the microservice, in response to the sidecar type configured for the microservice being the exclusive sidecar.

### Claim 8

(canceled)

### Claim 9

An electronic device, comprising:
at least one processor; and
a memory communicatively connected to the at least one processor, wherein:
the memory stores an instruction executable by the at least one processor which, when executed by the at least one processor, causes the at least one processor to perform a method for deploying a sidecar in a service mesh comprising:
determining, according to a resource requirement and a reliability requirement of a microservice, a sidecar type configured for the microservice, wherein the sidecar type comprises an exclusive sidecar and a shared sidecar; and
deploying a sidecar for the microservice according to the sidecar type, and allocating a published port to the microservice,
wherein in response to the sidecar type configured for the microservice being the shared sidecar, the published port allocated to the microservice is different from a published port of another microservice sharing the sidecar.

### Claim 10

A non-transitory computer-readable storage medium, storing a computer program which, when executed by a processor, causes the processor to perform a method for deploying a sidecar in a service mesh comprising:
determining, according to a resource requirement and a reliability requirement of a microservice, a sidecar type configured for the microservice, wherein the sidecar type comprises an exclusive sidecar and a shared sidecar; and
deploying a sidecar for the microservice according to the sidecar type, and allocating a published port to the microservice,
wherein in response to the sidecar type configured for the microservice being the shared sidecar, the published port allocated to the microservice is different from a published port of another microservice sharing the sidecar.

### Claim 11 (depends on 9)

The electronic device of claim 9, wherein after determining a sidecar type configured for the microservice and prior to deploying a sidecar for the microservice according to the sidecar type, the method further comprises:
configuring a parameter of the sidecar for the microservice, wherein the parameter comprises one or any combination of:
an identifier (ID) of the sidecar, a name of the sidecar, a resource quota of the sidecar, and a quantity of sidecars.

### Claim 12 (depends on 11)

The electronic device of claim 11, wherein in response to the parameter of the sidecar comprising the ID of the sidecar, deploying a sidecar for the microservice according to the sidecar type comprises:
in response to the sidecar type configured for the microservice being the shared sidecar, determining, according to the ID of the sidecar, an existence status indicating whether a sidecar having an identical ID exists in the service mesh; and
deploying the sidecar for the microservice according to the existence status.

### Claim 13 (depends on 12)

The electronic device of claim 12, wherein deploying the sidecar for the microservice according to the existence status comprises:
associating the sidecar having the identical ID with the microservice, in response to the existence status indicating that the sidecar having the identical ID exists in the service mesh; or
creating a sidecar and associating the created sidecar with the microservice, in response to the existence status indicating that the sidecar having the identical ID does not exist in the service mesh.

### Claim 14 (depends on 9)

The electronic device of claim 9, wherein after allocating a published port to the microservice, the method further comprises:
disassociating the sidecar from the microservice in response to a need to uninstall the microservice, and in response to the sidecar type of the sidecar associated with the microservice being the shared sidecar, determining whether to delete the sidecar according to a number of microservices associated with the sidecar.

### Claim 15 (depends on 14)

The electronic device of claim 14, wherein determining whether to delete the sidecar according to a number of microservices associated with the sidecar comprises:
maintaining the sidecar in response to the number of microservices associated with the sidecar being greater than 0; or
deleting the sidecar in response to the number of microservices associated with the sidecar being not greater than 0.

### Claim 16 (depends on 9)

The electronic device of claim 9, wherein deploying a sidecar for the microservice according to the sidecar type comprises:
creating a sidecar and associating the created sidecar with the microservice, in response to the sidecar type configured for the microservice being the exclusive sidecar.

### Claim 17 (depends on 10)

The non-transitory computer-readable storage medium of claim 10, wherein after determining a sidecar type configured for the microservice and prior to deploying a sidecar for the microservice according to the sidecar type, the method further comprises:
configuring a parameter of the sidecar for the microservice, wherein the parameter comprises one or any combination of:
an identifier (ID) of the sidecar, a name of the sidecar, a resource quota of the sidecar, and a quantity of sidecars.

### Claim 18 (depends on 17)

The non-transitory computer-readable storage medium of claim 17, wherein in response to the parameter of the sidecar comprising the ID of the sidecar, deploying a sidecar for the microservice according to the sidecar type comprises:
in response to the sidecar type configured for the microservice being the shared sidecar, determining, according to the ID of the sidecar, an existence status indicating whether a sidecar having an identical ID exists in the service mesh; and
deploying the sidecar for the microservice according to the existence status.

### Claim 19 (depends on 18)

The non-transitory computer-readable storage medium of claim 18, wherein deploying the sidecar for the microservice according to the existence status comprises:
associating the sidecar having the identical ID with the microservice, in response to the existence status indicating that the sidecar having the identical ID exists in the service mesh; or
creating a sidecar and associating the created sidecar with the microservice, in response to the existence status indicating that the sidecar having the identical ID does not exist in the service mesh.

### Claim 20 (depends on 10)

The non-transitory computer-readable storage medium of claim 10, wherein after allocating a published port to the microservice, the method further comprises:
disassociating the sidecar from the microservice in response to a need to uninstall the microservice, and in response to the sidecar type of the sidecar associated with the microservice being the shared sidecar, determining whether to delete the sidecar according to a number of microservices associated with the sidecar.

### Claim 21 (depends on 21)

The non-transitory computer-readable storage medium of claim 21, wherein determining whether to delete the sidecar according to a number of microservices associated with the sidecar comprises:
maintaining the sidecar in response to the number of microservices associated with the sidecar being greater than 0; or
deleting the sidecar in response to the number of microservices associated with the sidecar being not greater than 0.
