# US 11,444,852 B2 · Microservice generation system

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

- Number: US 11,444,852 B2
- Document ID: US11444852B2
- Status: Granted
- Kind: B2
- Application number: 17/335,262
- Filed: 2021-06-01
- Published: 2021-09-16
- Granted: 2022-09-13
- Earliest claimed: 2019-06-17
- Assignees: Sap SE
- Applicants: Sap SE
- Inventors: Anubhav Bhatia; Patrick Brose
- Web page: https://patentgrep.com/patent/US11444852B2

## CPC

- H04L 41/5048: {Automatic or semi-automatic definitions, e.g. definition templates}
- H04L 41/5045: {Making service definitions prior to deployment}
- H04L 63/08: {for authentication of entities (cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32)}
- H04L 63/101: {Access control lists [ACL]}
- H04L 41/5058: {Service discovery by the service manager}
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

Systems and methods are provided for receiving, from a computing device, a selection of a template for a custom microservice and configuration parameters for the custom microservice, generating the template for the custom microservice using the configuration parameters, the template for the custom microservice comprising defined interfaces for accessing core microservices, defined integration points for integration with a system providing the core microservices, and stubs for custom components for the custom microservice, and providing the template for the custom microservice to the computing device, wherein custom components for the custom microservice are added to the template via the computing device using the stubs for the custom components. The systems and methods further provide for registering the custom microservice to be exposed to and accessed by a tenant with authorization to access the custom microservice along with the core microservices.

## Claims

### Claim 1

A computer-implemented method comprising:
causing display, at a computing device, of a template selection user interface comprising a plurality of templates for selection to develop a custom microservice;
receiving, from the computing device, a selection of a template for a custom microservice from the plurality of templates for selection to develop a custom microservice;
causing display, at the computing device, of a user interface for entering configuration parameters for the custom microservice;
receiving, from the computing device, the entered configuration parameters for the custom microservice;
retrieving the template for the custom microservice, the custom template comprising stubs for custom components for the custom microservice;
populating associated parameters in the retrieved template for the custom microservice with the entered configuration parameters;
providing the populated template for the custom microservice to the computing device, wherein custom components for the custom microservice are added to the template via the computing device using the stubs in the populated template for the custom components; and
registering the custom software microservice to be exposed to and accessed by a tenant with authorization to access the custom microservice along with core software microservices.

### Claim 2 (depends on 1)

The method of claim 1, wherein the configuration parameters comprise at least one of a name for the custom microservice, a namespace for the custom microservice, an image for the custom microservice, or a description for the custom microservice.

### Claim 3 (depends on 1)

The method of claim 1, wherein the template for the custom microservice comprises stubs for custom components and the custom components are added to the template via the computing device using the stubs for custom components.

### Claim 4 (depends on 1)

The method of claim 1, wherein the template for custom microservices comprises an authorization and authentication instance for defining authorization and authentication for the custom microservice.

### Claim 5 (depends on 1)

The method of claim 1, wherein the template for the custom microservice comprises a connectivity instance storing connectivity data defining how to connect to external systems for data or software microservices used by the custom microservice.

### Claim 6 (depends on 1)

The method of claim 1, wherein registering the custom microservice comprises storing user interface components corresponding to the custom microservice.

### Claim 7 (depends on 1)

The method of claim 1, further comprising:
causing the custom microservice to be displayed along with the core software microservices in a user interface of a second computing device requesting access to the custom microservice and core software microservices.

### Claim 8 (depends on 1)

The method of claim 1, further comprising:
causing display on the computing device of a user interface comprising the custom microservice and the core software microservices in a selection list.

### Claim 9 (depends on 8)

The method of claim 8, wherein each of the custom microservice and the core software microservices is displayed as a tab in the selection list.

### Claim 10 (depends on 8)

The method of claim 8, wherein each of the custom microservice and the core software microservice is displayed as a visual card comprising at least one event associated with each of the custom microservice and core software microservices.

### Claim 11

A system comprising:
a memory that stores instructions; and
one or more processors configured by the instructions to perform operations comprising:
causing display, at a computing device, of a template selection user interface comprising a plurality of templates for selection to develop a custom microservice;
receiving, from the computing device, a selection of a template for a custom microservice from the plurality of templates for selection to develop a custom microservice;
causing display, at the computing device, of a user interface for entering configuration parameters for the custom microservice;
receiving, from the computing device, the entered configuration parameters for the custom microservice;
retrieving the template for the custom microservice, the custom template comprising stubs for custom components for the custom microservice;
populating associated parameters in the retrieved template for the custom microservice with the entered configuration parameters;
providing the populated template for the custom microservice to the computing device, wherein custom components for the custom microservice are added to the template via the computing device using the stubs in the populated template for the custom components; and
registering the custom microservice to be exposed to and accessed by a tenant with authorization to access the custom microservice along with core software microservices.

### Claim 12 (depends on 11)

The system of claim 11, wherein the configuration parameters comprise at least one of a name for the custom microservice, a namespace for the custom microservice, an image for the custom microservice, or a description for the custom microservice.

### Claim 13 (depends on 11)

The system of claim 11, wherein the template for the custom microservice comprises stubs for custom components and the custom components are added to the template via the computing device using the stubs for custom components.

### Claim 14 (depends on 11)

The system of claim 11, wherein the template for custom microservices comprises an authorization and authentication instance for defining authorization and authentication for the custom microservice.

### Claim 15 (depends on 11)

The system of claim 11, wherein the template for the custom microservice comprises a connectivity instance storing connectivity data defining how to connect to external systems for data or software microservices used by the custom microservice.

### Claim 16 (depends on 11)

The system of claim 11, wherein registering the custom microservice comprises storing user interface components corresponding to the custom microservice.

### Claim 17 (depends on 11)

The system of claim 11, further comprising:
causing the custom microservice to be displayed along with the core software microservices in a user interface of a second computing device requesting access to the custom microservice and core software microservices.

### Claim 18 (depends on 11)

The system of claim 11, further comprising:
causing display on the computing device of a user interface comprising the custom microservice and the core software microservices in a selection list, wherein each of the custom microservice and the core software microservices is displayed as a tab in the selection list.

### Claim 19 (depends on 11)

The system of claim 11, further comprising:
causing display on the computing device of a user interface comprising the custom microservice and the core software microservices in a selection list, wherein each of the custom microservice and the core software microservice is displayed as a visual card comprising at least one event associated with each of the custom microservice and core software microservices.

### Claim 20

A non-transitory computer-readable medium comprising instructions stored thereon that are executable by at least one processor to cause a computing system to perform operations comprising:
causing display, at a computing device, of a template selection user interface comprising a plurality of templates for selection to develop a custom microservice;
receiving, from the computing device, a selection of a template for a custom microservice from the plurality of templates for selection to develop a custom microservice;
causing display, at the computing device, of a user interface for entering configuration parameters for the custom microservice;
receiving, from the computing device, the entered configuration parameters for the custom microservice;
retrieving the template for the custom microservice, the custom template comprising stubs for custom components for the custom microservice;
populating associated parameters in the retrieved template for the custom microservice with the entered configuration parameters;
providing the populated template for the custom microservice to the computing device, wherein custom components for the custom microservice are added to the template via the computing device using the stubs in the populated template for the custom components; and
registering the custom microservice to be exposed to and accessed by a tenant with authorization to access the custom microservice along with core software microservices.
