# US 2024/0004739 A1 · Microservice platform message management system

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

- Number: US 2024/0004739 A1
- Document ID: US20240004739A1
- Status: Published application
- Kind: A1
- Application number: 17/855,676
- Filed: 2022-06-30
- Published: 2024-01-04
- Earliest claimed: 2022-06-30
- Assignees: Mastercard International Incorporated
- Applicants: Mastercard International Incorporated
- Inventors: Ajinkya SAWANT; Gopinatha JOSHI; Matthew RAMELLA
- Web page: https://patentgrep.com/patent/US20240004739A1

## CPC

- G06F 9/5072: {Grid computing}
- G06F 9/547: {Remote procedure calls [RPC]; Web services}
- G06F 9/54: Interprogram communication
- G06F 9/541: {via adapters, e.g. between incompatible applications}
- G06F 9/546: {Message passing systems or structures, e.g. queues}
- G06F 21/44: Program or device authentication
- G06F 21/606: {by securing the transmission between two devices or processes}
- H04L 63/0807: {using tickets, e.g. Kerberos (cryptographic mechanisms or cryptographic arrangements for entity authentication using tickets or tokens H04L9/3213)}
- H04L 63/123: {received data contents, e.g. message integrity}
- H04L 67/133: Protocols for remote procedure calls [RPC]
- H04L 67/63: Routing a service request depending on the request content or context
- 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 disclosure herein describes receiving and routing a remote procedure call (RPC) message from an external source. A microservice platform receives an RPC message from a source via an RPC interface, wherein the RPC message includes a header structure and a payload structure. The RPC message is validated based on security data in the header structure and the identity of the source is authenticated based on identity data in the header structure. A service interface function is triggered based on routing data in the payload structure and a multi-layer route and one of a plurality of microservices are identified. Payload data of the payload structure is routed through each of the ordered plurality of layers of the multi-layer route to the identified microservice, wherein each of the ordered plurality of layers and the microservice are configured to perform an operation using the payload data.

## Claims

### Claim 1

A system comprising:
at least one processor of a microservice computing platform; and
at least one memory comprising computer program code, the at least one memory and the computer program code configured to, with the at least one processor, cause the at least one processor to:
receive a remote procedure call (RPC) message from a source device via an RPC interface, the RPC message including a header structure and a payload structure;
validate the RPC message based on security data in the header structure;
authenticate an identity of the source based on identity data in the header structure;
trigger a service interface function of the microservice computing platform based on routing data in the payload structure;
based on execution of the service interface function, identify a multi-layer route and one of a plurality of microservices, the multi-layer route including an ordered plurality of layers; and
route payload data of the payload structure through each of the ordered plurality of layers to the identified one of the plurality of microservices, wherein each of the ordered plurality of layers and the one of the plurality of microservices are configured to perform an operation using the payload data.

### Claim 2 (depends on 1)

The system of claim 1, wherein a microservice is added to the plurality of microservices and wherein the at least one memory and the computer program code are configured to, with the at least one processor, further cause the at least one processor to update the microservice platform with a service interface function corresponding to the added microservice.

### Claim 3 (depends on 1)

The system of claim 1, wherein the header structure includes region data; and
wherein identifying the multi-layer route is further based on the region data.

### Claim 4 (depends on 1)

The system of claim 1, wherein the at least one memory and the computer program code are configured to, with the at least one processor, further cause the at least one processor to:
based on routing payload data of the payload structure through each of the ordered plurality of layers to the identified one of the plurality of microservices, generate a response RPC message; and
send the generated response RPC message to the source via the RPC interface.

### Claim 5 (depends on 1)

The system of claim 1, wherein validating the RPC message based on security data in the header structure includes validating a session-based token of the security data, wherein the received RPC message is one of a plurality of RPC messages from the source during a session.

### Claim 6 (depends on 1)

The system of claim 1, wherein the routing data includes a service type indicator, and the triggered service interface function is associated with a service indicated by the service type indicator.

### Claim 7 (depends on 1)

The system of claim 1, wherein the plurality of microservices include at least one of the following: transaction authorization services, transaction reversal services, transaction processing services, fee collection services, process verification services, key exchange services, network gateway services, credit transfer services, and blockchain-based services.

### Claim 8

A computerized method comprising:
receiving, by a processor of a microservice platform, a remote procedure call (RPC) message from a source via an RPC interface, the RPC message including a header structure and a payload structure;
validating, by the processor, the RPC message based on security data in the header structure;
authenticating, by the processor, an identity of the source based on identity data in the header structure;
triggering, by the processor, a service interface function of the microservice platform based on routing data in the payload structure;
based on execution of the service interface function, identifying, by the processor, a multi-layer route and one of a plurality of microservices, the multi-layer route including an ordered plurality of layers; and
routing, by the processor, payload data in the payload structure through each of the ordered plurality of layers to the identified one of the plurality of microservices, wherein each of the ordered plurality of layers and the one of the plurality of microservices are configured to perform an operation using the payload data.

### Claim 9 (depends on 8)

The computerized method of claim 8, wherein a microservice is added to the plurality of microservices and further comprising updating the microservice platform with a service interface function corresponding to the added microservice.

### Claim 10 (depends on 8)

The computerized method of claim 8, wherein the header structure includes region data; and
wherein identifying the multi-layer route is further based on the region data.

### Claim 11 (depends on 8)

The computerized method of claim 8, further comprising:
based on routing payload data in the payload structure through each of the ordered plurality of layers to the identified one of the plurality of microservices, generate a response RPC message; and
send the generated response RPC message to the source via the RPC interface.

### Claim 12 (depends on 8)

The computerized method of claim 8, wherein validating the RPC message based on security data in the header structure includes validating a session-based token of the security data, wherein the received RPC message is one of a plurality of RPC messages from the source during a session.

### Claim 13 (depends on 8)

The computerized method of claim 8, wherein the routing data includes a service type indicator, and the triggered service interface function is associated with a service indicated by the service type indicator.

### Claim 14 (depends on 8)

The computerized method of claim 8, wherein the plurality of microservices include at least one of the following: transaction authorization services, transaction reversal services, transaction processing services, fee collection services, process verification services, key exchange services, network gateway services, credit transfer services, and blockchain-based services.

### Claim 15

One or more computer storage media having computer-executable instructions that, upon execution by a processor of a microservice platform, cause the processor to at least:
receive a remote procedure call (RPC) message from a source via an RPC interface, the RPC message including a header structure and a payload structure;
validate the RPC message based on security data in the header structure;
authenticate an identity of the source based on identity data in the header structure;
trigger a service interface function of the microservice platform based on routing data in the payload structure;
based on execution of the service interface function, identify a multi-layer route and one of a plurality of microservices, the multi-layer route including an ordered plurality of layers; and
route payload data in the payload structure through each of the ordered plurality of layers to the identified one of the plurality of microservices, wherein each of the ordered plurality of layers and the one of the plurality of microservices are configured to perform an operation using the payload data.

### Claim 16 (depends on 15)

The one or more computer storage media of claim 15, wherein a microservice is added to the plurality of microservices and wherein the computer-executable instructions, upon execution by the processor, further cause the processor to at least update the microservice platform with a service interface function corresponding to the added microservice.

### Claim 17 (depends on 15)

The one or more computer storage media of claim 15, wherein the header structure includes region data; and
wherein identifying the multi-layer route is further based on the region data.

### Claim 18 (depends on 15)

The one or more computer storage media of claim 15, wherein the computer-executable instructions, upon execution by the processor, further cause the processor to at least:
based on routing payload data in the payload structure through each of the ordered plurality of layers to the identified one of the plurality of microservices, generate a response RPC message; and
send the generated response RPC message to the source via the RPC interface.

### Claim 19 (depends on 15)

The one or more computer storage media of claim 15, wherein validating the RPC message based on security data in the header structure includes validating a session-based token of the security data, wherein the received RPC message is one of a plurality of RPC messages from the source during a session.

### Claim 20 (depends on 15)

The one or more computer storage media of claim 15, wherein the routing data includes a service type indicator, and the triggered service interface function is associated with a service indicated by the service type indicator.
