# US 12,015,680 B1 · User demand-specific service mesh assembly of multi-tenant, single-tenant, and extension services > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 12,015,680 B1 - Document ID: US12015680B1 - Status: Granted - Kind: B1 - Application number: 18/298,661 - Filed: 2023-04-11 - Granted: 2024-06-18 - Earliest claimed: 2023-04-11 - Assignees: Sap SE - Applicants: Sap SE - Inventors: Peter Eberlein - Web page: https://patentgrep.com/patent/US12015680B1 ## CPC - G06F 9/5072: {Grid computing} - H04L 67/51: Discovery or management thereof, e.g. service location protocol [SLP] or web services - H04L 67/10: in which an application is distributed across nodes in the network (software deployment G06F8/60; multiprogramming arrangements G06F9/46) - H04L 67/30: Profiles - 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 In an implementation, a mesh assembler receives a request for a new cloud-computing application tenant, where the request includes an assembly profile. The mesh assembler calls a deployment manager for applications and services that need to be custom deployed according to the assembly profile. The mesh assembler calls a routing configurator, which looks up services with certain attributes and configures services with certain attributes into a service mesh. ## Claims ### Claim 1 A computer-implemented method, comprising: receiving, at a mesh assembler, a request for a new cloud-computing application tenant, wherein the request includes an assembly profile; calling, by the mesh assembler, a deployment manager for applications and services that need to be custom deployed according to the assembly profile; and calling, by the mesh assembler, a routing configurator, wherein the routing configurator looks up services with certain attributes, wherein the services with certain attributes are non-extension services, wherein the routing configurator configures the services with certain attributes and extension services into a service mesh, and wherein the routing configurator configures an invoked endpoint and credentials used when a component in the service mesh calls a service using a symbolic name. ### Claim 2 (depends on 1) The computer-implemented method of claim 1, wherein the assembly profile defines which applications and services will be deployed exclusively for the new cloud-computing application tenant and which can be shared with other tenants, and wherein extension services lack attributes in the assembly profile. ### Claim 3 (depends on 1) The computer-implemented method of claim 1, wherein the deployment manager performs on-demand deployment and running a service to a specific infrastructure to create a new service instance for integration into the service mesh and for providing its service to other applications or services. ### Claim 4 (depends on 1) The computer-implemented method of claim 1, comprising executing, by the deployment manager, a deployment of the applications and services that need to be custom deployed. ### Claim 5 (depends on 4) The computer-implemented method of claim 4, comprising recording, by the deployment manager, coordinates in a landscape directory, wherein the coordinates relate the deployment to the new cloud-computing application tenant. ### Claim 6 (depends on 5) The computer-implemented method of claim 5, comprising reading, by the routing configurator and as deployments, deployment coordinates for all applications and services of the assembly profile from the landscape directory. ### Claim 7 (depends on 6) The computer-implemented method of claim 6, comprising configuring, by the routing configurator, the service mesh, wherein the configuration permits the service mesh to route requests for the new cloud-computing application tenant to the deployments. ### Claim 8 A computer-implemented system, comprising: one or more computers; and one or more computer memory devices interoperably coupled with the one or more computers and having tangible, non-transitory, machine-readable media storing one or more instructions that, when executed by the one or more computers, perform one or more operations, comprising: receiving, at a mesh assembler, a request for a new cloud-computing application tenant, wherein the request includes an assembly profile; calling, by the mesh assembler, a deployment manager for applications and services that need to be custom deployed according to the assembly profile; and calling, by the mesh assembler, a routing configurator, wherein the routing configurator looks up services with certain attributes, wherein the services with certain attributes are non-extension services, wherein the routing configurator configures the services with certain attributes and extension services into a service mesh, and wherein the routing configurator configures an invoked endpoint and credentials used when a component in the service mesh calls a service using a symbolic name. ### Claim 9 (depends on 8) The computer-implemented system of claim 8, wherein the assembly profile defines which applications and services will be deployed exclusively for the new cloud-computing application tenant and which can be shared with other tenants, and wherein extension services lack attributes in the assembly profile. ### Claim 10 (depends on 8) The computer-implemented system of claim 8, wherein the deployment manager performs on-demand deployment and running a service to a specific infrastructure to create a new service instance for integration into the service mesh and for providing its service to other applications or services. ### Claim 11 (depends on 8) The computer-implemented system of claim 8, comprising executing, by the deployment manager, a deployment of the applications and services that need to be custom deployed. ### Claim 12 (depends on 11) The computer-implemented system of claim 11, comprising recording, by the deployment manager, coordinates in a landscape directory, wherein the coordinates relate the deployment to the new cloud-computing application tenant. ### Claim 13 (depends on 12) The computer-implemented system of claim 12, comprising reading, by the routing configurator and as deployments, deployment coordinates for all applications and services of the assembly profile from the landscape directory. ### Claim 14 A non-transitory, computer-readable medium storing one or more instructions executable by a computer system to perform operations, comprising: receiving, at a mesh assembler, a request for a new cloud-computing application tenant, wherein the request includes an assembly profile; calling, by the mesh assembler, a deployment manager for applications and services that need to be custom deployed according to the assembly profile; and calling, by the mesh assembler, a routing configurator, wherein the routing configurator looks up services with certain attributes, wherein the services with certain attributes are non-extension services, wherein the routing configurator configures the services with certain attributes and extension services into a service mesh, and wherein the routing configurator configures an invoked endpoint and credentials used when a component in the service mesh calls a service using a symbolic name. ### Claim 15 (depends on 14) The non-transitory, computer-readable medium of claim 14, wherein the assembly profile defines which applications and services will be deployed exclusively for the new cloud-computing application tenant and which can be shared with other tenants, and wherein extension services lack attributes in the assembly profile. ### Claim 16 (depends on 14) The non-transitory, computer-readable medium of claim 14, wherein the deployment manager performs on-demand deployment and running a service to a specific infrastructure to create a new service instance for integration into the service mesh and for providing its service to other applications or services. ### Claim 17 (depends on 14) The non-transitory, computer-readable medium of claim 14, comprising executing, by the deployment manager, a deployment of the applications and services that need to be custom deployed. ### Claim 18 (depends on 17) The non-transitory, computer-readable medium of claim 17, comprising recording, by the deployment manager, coordinates in a landscape directory, wherein the coordinates relate the deployment to the new cloud-computing application tenant. ### Claim 19 (depends on 18) The non-transitory, computer-readable medium of claim 18, comprising reading, by the routing configurator and as deployments, deployment coordinates for all applications and services of the assembly profile from the landscape directory. ### Claim 20 (depends on 19) The non-transitory, computer-readable medium of claim 19, comprising configuring, by the routing configurator, the service mesh, wherein the configuration permits the service mesh to route requests for the new cloud-computing application tenant to the deployments.