Granted Patent B2

US 12,363,029 · App. 17/811,243 · Granted Jul 15, 2025

Inventors: Tulasi Movva (Trumbull, CT); Alexander Littleton (Chicago, IL); Hannah Dorfman (Brooklyn, NY); Palka S. Patel (Jersey City, NJ); Robert Franklin Gossett (New York, NY)

Assignee: JPMORGAN CHASE BANK, N.A.

H04L45/127H04L45/16H04L45/22

Abstract

Claims (39)

1. A method for contextual messaging and information routing in a distributed ledger network, comprising:

receiving, at a distributed application executed by a sending entity node in a distributed ledger network, a message or communication from a sending entity;

identifying, by the distributed application, a context for the message or communication;

retrieving, by the distributed application, and from each of the other nodes in the distributed ledger network, an identification of payment systems supported by the other nodes in the distributed ledger network;

identifying, by the distributed application, potential receiving entities for the message or communication based on the context and the identification of the payment systems supported by the other nodes;

retrieving, by the distributed application, routing preferences for the sending entity;

applying, by the distributed application, the routing preferences for the sending entity to identify a receiving entity from the potential receiving entities; and

sending, by the distributed application, the message or communication to a receiving node for the receiving entity using the routing preferences, wherein the message is sent using Transmission Control Protocol (TCP)/Remote Procedure Call (RPC).

2. The method of claim 1 , wherein the receiving node is configured to apply routing preferences for the sending entity node to the message.

3. The method of claim 1 , wherein the message is sent to a distributed application at the receiving node.

4. The method of claim 1 , wherein the message is communicated using a permissioned access route.

5. The method of claim 1 , wherein the receiving node is configured to route the message or communication to the receiving entity using routing preferences for the receiving entity.

6. The method of claim 1 , wherein the context comprises a subject and/or an account from the message.

7. The method of claim 6 , wherein the routing preferences for the sending entity are based on the subject of the message.

8. The method of claim 6 , wherein the routing preferences are based on the account in the message.

9. A system, comprising:

a distributed ledger network; and a plurality of nodes in the distributed ledger network, each node executing a distributed application;

wherein: a sending node distributed application receives a message or communication from a sending entity;

the sending node distributed application identifies a context for the message or communication;

the sending node distributed application retrieves, from each of the other nodes in the distributed ledger network, an identification of payment systems supported by the other nodes in the distributed ledger network;

the sending node distributed application identifies potential receiving entities for the message or communication based on the context and the identification of the payment systems supported by the other nodes;

the sending node distributed application retrieves routing preferences for the sending entity;

the sending node distributed application applies the routing preferences for the sending entity to identify a receiving entity from the potential receiving entities; and

the sending node distributed application sends the message or communication to a receiving node for the receiving entity using the routing preferences, wherein the message is sent using Transmission Control Protocol (TCP)/Remote Procedure Call (RPC).

10. The system of claim 9 , wherein the message is sent to a distributed application at the receiving node.

11. The system of claim 9 , wherein the message is communicated using a permissioned access route.

12. The system of claim 9 , wherein the receiving node is configured to route the message or communication to the receiving entity using routing preferences for the receiving entity.

13. The system of claim 9 , wherein the context comprises a subject and/or an account from the message.

14. The system of claim 13 , wherein the routing preferences for the sending entity are based on the subject of the message.

15. The system of claim 13 , wherein the routing preferences for the sending entity are based on the account in the message.

16. A non-transitory computer readable storage medium, including instructions stored thereon, which when read and executed by one or more computer processors, cause the one or more computer processors to perform steps comprising:

receiving a message or communication from a sending entity;

identifying a context for the message or communication;

retrieving from each of the other nodes in a distributed ledger network an identification of payment systems supported by the other nodes in a distributed ledger network;

identifying potential receiving entities for the message or communication based on the context and the identification of the payment systems supported by the other nodes;

retrieving routing preferences for the sending entity;

applying the routing preferences for the sending entity to identify a receiving entity from the potential receiving entities; and

sending the message or communication to a receiving node for the receiving entity using the routing preferences, wherein the message is sent using Transmission Control Protocol (TCP)/Remote Procedure Call (RPC).

17. The non-transitory computer readable storage medium of claim 16 , wherein the message is communicated using a permissioned access route.

Assignments (1)

Continuity (2)

References Cited (12)