# US 2022/0021656 A1 · Scalable proxy clusters

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

- Number: US 2022/0021656 A1
- Document ID: US20220021656A1
- Status: Published application
- Kind: A1
- Application number: 17/491,946
- Filed: 2021-10-01
- Published: 2022-01-20
- Earliest claimed: 2015-05-27
- Assignees: Ping Identity Corporation
- Applicants: Ping Identity Corporation
- Inventors: Udayakumar SUBBARAYAN; Bernard HARGUINDEGUY; Anoop Krishnan GOPALAKRISHNAN; Abdu Raheem POONTHIRUTHI
- Web page: https://patentgrep.com/patent/US20220021656A1

## CPC

- H04L 63/0281: {Proxies}
- G06F 9/546: {Message passing systems or structures, e.g. queues}
- H04L 41/0813: characterised by the conditions triggering a change of settings
- H04L 41/28: Restricting access to network management systems or functions, e.g. using authorisation function to access network configuration
- H04L 41/50: Network service management, e.g. ensuring proper service fulfilment according to agreements
- H04L 45/46: {Cluster building}
- H04L 45/56: {Routing software}
- H04L 45/58: Association of routers
- H04L 45/74: Address processing for routing
- H04L 47/125: by balancing the load, e.g. traffic engineering
- H04L 47/20: Traffic policing
- H04L 63/08: {for authentication of entities (cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32)}
- H04L 63/166: {at the transport layer}
- H04L 67/02: based on web technology, e.g. hypertext transfer protocol [HTTP]
- H04L 67/10: in which an application is distributed across nodes in the network (software deployment G06F8/60; multiprogramming arrangements G06F9/46)
- H04L 67/1014: based on the content of a request
- H04L 67/1068: {Discovery involving direct consultation or announcement among potential requesting and potential source peers}
- H04L 67/1095: Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
- H04L 67/12: specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
- H04L 67/145: avoiding end of session, e.g. keep-alive, heartbeats, resumption message or wake-up for inactive or interrupted session
- H04L 67/56: Provisioning of proxy services (store-and-forward switching systems in data switching networks H04L12/54)
- H04L 67/60: Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources (admission control or resource allocation H04L47/70)
- H04L 69/16: Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]
- H04L 69/329: in the application layer [OSI layer 7]
- H04L 69/40: for recovering from a failure of a protocol instance or entity, e.g. service redundancy protocols, protocol state redundancy or protocol service redirection (management of faults, events, alarms or notifications in data switching networks H04L41/06)
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

The invention enables high-availability, high-scale, high security and disaster recovery for API computing, including in terms of capture of data traffic passing through proxies, routing communications between clients and servers, and load balancing and/or forwarding functions. The invention inter alia provides (i) a scalable cluster of proxies configured to route communications between clients and servers, without any single point of failure, (ii) proxy nodes configured for implementing the scalable cluster (iii) efficient methods of configuring the proxy cluster, (iv) natural resiliency of clusters and/or proxy nodes within a cluster, (v) methods for scaling of clusters, (vi) configurability of clusters to span multiple servers, multiple racks and multiple datacenters, thereby ensuring high availability and disaster recovery (vii) switching between proxies or between servers without loss of session.

## Claims

### Claim 1

A method, comprising:
receiving, at a first proxy node to be included in a plurality of networked proxy nodes, address information of a second proxy node from the plurality of networked proxy nodes;
establishing, at the first proxy node and based on the address information of the second proxy node, a read-write connection with the second proxy node;
acquiring, at the first proxy node and via the read-write connection with the second proxy node, data states of the second proxy node, the data states of the second proxy node including address information of remaining proxy nodes from the plurality of proxy nodes, the remaining proxy nodes including each proxy node from the plurality of networked proxy nodes other than the first proxy node and the second proxy node;
establishing, at the first proxy node and based on the address information of the remaining proxy nodes, read-write connections with remaining proxy nodes from the plurality of networked proxy nodes;
acquiring, at the first proxy node and via the read-write connections with the remaining proxy nodes, data states of the remaining proxy nodes; and
synchronizing data states of the first proxy node with the data states of the second proxy node and the data states of the remaining proxy nodes.

### Claim 2 (depends on 1)

The method of claim 1, further comprising:
receiving, at the first proxy node an Application Programming Interface (API) request from a client device; and
routing the API request to a server from a plurality of servers based on information included in the API request and the data states of the first proxy node,
the data states of the first proxy node including information descriptive of a plurality of APIs implemented on the plurality of servers.

### Claim 3 (depends on 1)

The method of claim 1, wherein the data states of the first proxy node include:
server characteristic data including information descriptive of one or more characteristics of one or more servers;
session data including information descriptive of one or more client devices communicating with the one or more servers via at least one proxy node from the plurality of networked proxy nodes;
security data associated with one or more sessions between the one or more client devices and the one or more servers;
configuration data associated with routing API requests from the one or more client devices to the one or more servers; and
proxy node data including information descriptive of the plurality of networked proxy nodes.

### Claim 4 (depends on 1)

The method of claim 1, further comprising:
modifying one or more entries of a Domain Name System (DNS) server to include address information of the first proxy node such that the DNS server facilitates routing of API requests of one or more client devices to the first proxy node, the DNS server operatively coupled to the one or more client devices.

### Claim 5 (depends on 1)

The method of claim 1, further comprising:
sending, from the first proxy node, messages at periodic intervals to a third proxy node from the plurality of networked proxy nodes; and
in response to not receiving a response from the third proxy node after sending a predefined number of the messages, modifying proxy node data included in the data states of the first proxy node to: indicate that the third proxy node is inactive, or remove an identifier of the third proxy node from the proxy node data.

### Claim 6 (depends on 1)

The method of claim 1, wherein the synchronizing the data states of the first proxy node with the data states of the second proxy node and the data states of the remaining proxy nodes includes synchronizing the data states of the first proxy node with the data states of the second proxy node and the data states of the remaining proxy nodes at periodic intervals.

### Claim 7 (depends on 1)

The method of claim 1, further comprising:
receiving, via a command-line interpreter (CLI) or a RESTful API (REST API), an input to modify information included in the data states of the first proxy node;
modifying the data states of the first proxy node based on the input; and
sending, after the modifying the data states, the data states of the first proxy node to the second proxy node and the remaining proxy nodes such that the data states of the second proxy node and the data states of the remaining proxy nodes are synchronized with the data states of the first proxy node.

### Claim 8

A method, comprising:
receiving, from a first proxy node to be included in a plurality of networked proxy nodes and at a second proxy node from the plurality of networked proxy nodes, address information of the first proxy node;
modifying, at the second proxy node, proxy node data included in data states of the second proxy node to include the address information of the first proxy node;
sending, from the second proxy node, a broadcast message including the address information of the first proxy node to remaining proxy nodes from the plurality of networked proxy nodes such that each remaining proxy node from the remaining proxy nodes establishes read-write connections with the first proxy node based on the address information of the first proxy node to synchronize data states between the first proxy node and the remaining proxy nodes, the remaining proxy nodes including each proxy node from the plurality of networked proxy nodes other than the first proxy node and the second proxy node;
establishing, at the second proxy node, read-write connections with the first proxy node and the remaining proxy nodes; and
synchronizing, via the read-write connections with the first proxy node and the remaining proxy nodes, the data states of the second proxy node with the first proxy node and the remaining proxy nodes.

### Claim 9 (depends on 8)

The method of claim 8, further comprising:
detecting, at the second proxy node, a synchronization event including at least one of:
a proxy node being added to the plurality of networked proxy nodes;
a proxy node from the plurality of networked proxy nodes becoming active after a period of inactivity; or
an expiration of a predefined period of time,
the synchronizing the data states of the second proxy node with the first proxy node and the remaining proxy nodes being in response to detecting the synchronization event.

### Claim 10 (depends on 8)

The method of claim 8, further comprising:
receiving, at the second proxy node, an Application Programming Interface (API) request from a client device; and
routing the API request to a server from a plurality of servers based on information included in the API request and the data states of the second proxy node,
the data states of the second proxy node including information descriptive of a plurality of APIs implemented on the plurality of servers.

### Claim 11 (depends on 8)

The method of claim 8, wherein the data states of the second proxy node include:
server characteristic data including information descriptive of one or more characteristics of one or more servers;
session data including information descriptive of one or more client devices communicating with the one or more servers via at least one proxy node from the plurality of networked proxy nodes;
security data associated with one or more sessions between the one or more client devices and the one or more servers;
configuration data associated with routing of API requests from the one or more client devices to the one or more servers; and
proxy node data including information descriptive of the plurality of networked proxy nodes.

### Claim 12 (depends on 8)

The method of claim 8, further comprising:
receiving, via a command-line interpreter (CLI) or a RESTful API (REST API), an input to modify information included in the data states of the second proxy node;
modifying the data states of the second proxy node based on the input; and
sending, after the modifying the data states, the data states of the second proxy node to the first proxy node and the remaining proxy nodes such that each of the first proxy node and the remaining proxy nodes, in response to receiving the data states of the second proxy node, synchronizes the data states of that proxy node with the data states of the second proxy node.
