# US 2020/0396140 A1 · 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 2020/0396140 A1
- Document ID: US20200396140A1
- Status: Published application
- Kind: A1
- Application number: 16/443,740
- Filed: 2019-06-17
- Published: 2020-12-17
- Earliest claimed: 2019-06-17
- Assignees: Sap SE
- Applicants: Sap SE
- Inventors: Anubhav Bhatia; Patrick Brose
- Web page: https://patentgrep.com/patent/US20200396140A1

## 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:
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;
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;
receiving a request from the computing device to register the custom microservice comprising 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 the core microservices.

### Claim 2 (depends on 1)

The method of claim 1, wherein the template for the custom microservice is one of a plurality of templates.

### Claim 3 (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 4 (depends on 1)

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

### Claim 5

The method of claim wherein the template for the custom microservice further comprises a connectivity instance storing connectivity data defining how to connect to external systems for data or 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 microservices in a user interface of a second computing device requesting access to the custom microservice and core microservices.

### Claim 8

A system comprising:
a memory that stores instructions; and
one or more processors configured by the instructions to perform operations comprising:
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;
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;
receiving a request from the computing device to register the custom microservice comprising 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 the core microservices.

### Claim 9 (depends on 8)

The system of claim 8, wherein the template for the custom microservice is one of a plurality of templates.

### Claim 10 (depends on 8)

The system of claim 8, 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 11 (depends on 8)

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

### Claim 12 (depends on 8)

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

### Claim 13 (depends on 8)

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

### Claim 14 (depends on 8)

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

### Claim 15

A non-transitory computer-readable medium comprising instructions stored thereon that are executable by at least one processor to cause a computing device to perform operations comprising:
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;
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;
receiving a request from the computing device to register the custom microservice comprising 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 the core microservices,

### Claim 16 (depends on 15)

The non-transitory computer-readable medium of claim 15, wherein the template for the custom microservice is one of a plurality of templates.

### Claim 17 (depends on 15)

The non-transitory computer-readable medium of claim 15, 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 18 (depends on 15)

The non-transitory computer-readable medium of claim 15, wherein the template for the custom microservice further comprises an authorization and authentication instance for defining authorization and authentication for the custom microservice.

### Claim 19 (depends on 15)

The non-transitory computer-readable medium of claim 15, wherein the template for the custom microservice further comprises a connectivity instance storing connectivity data defining how to connect to external systems for data or microservices used by the custom microservice.

### Claim 20 (depends on 15)

The non-transitory computer-readable medium of claim 15, wherein registering the custom microservice comprises storing user interface components corresponding to the custom microservice.
