Outbound request management

US10348636B2 · US · B2

Patent metadata
FieldValue
Publication numberUS-10348636-B2
Application numberUS-201615356347-A
CountryUS
Kind codeB2
Filing dateNov 18, 2016
Priority dateNov 18, 2016
Publication dateJul 9, 2019
Grant dateJul 9, 2019

How to read this patent

A practical reading order for non-experts. Skip the full description unless you need deep technical detail.

  1. Title

    What the patent document calls the invention.

  2. Abstract

    A short plain-language summary of the technical disclosure.

  3. Assignees and inventors

    Who owns or filed the patent and who is credited as inventor.

  4. Key dates

    Filing, priority, publication, and grant dates set the timeline.

  5. First independent claim

    The legal scope of protection — read this for what is actually claimed.

  6. CPC / IPC classifications

    Technology tags used to group this patent with similar filings.

  7. Citations and related patents

    Prior art links and similar publications in this corpus.

Abstract

Official abstract text for this publication.

The present disclosure is related to devices, systems, and methods for routing requests for an external service, originating from a plurality of cluster nodes, through an outbound request manager. An example method can include receiving a first request for an external service originating from a first cluster node having a first network address, receiving a second request for the external service originating from a second cluster node having a second network address, transmitting the first request with a particular network address to an address associated with the external service, and transmitting the second request with the particular network address to the address associated with the external service.

First claim

Opening claim text (preview).

What is claimed is: 1. A method, comprising: receiving, by an outbound request manager coupled to a first cluster node, a second cluster node, a first external service, and a second external service, a first request for the first external service originating from the first cluster node having a first network address; receiving, by the outbound request manager, a second request for the first external service originating from the second cluster node having a second network address; transmitting, by the outbound request manager, the first and second requests having a third network address instead of the first or second network address to an address associated with the first external service, wherein the third network address is associated with the outbound request manager and is different than the first and second network addresses; receiving, by the outbound request manager, a third request for a second external service originating from the first cluster node having the first network address; receiving, by the outbound request manager, a fourth request for the second external service originating from the second cluster node having the second network address; and transmitting, by the outbound request manager, the third and fourth requests having a fourth network address instead of the first or second network address to an address associated with the second external service, wherein the fourth network address is associated with the outbound request manager and is different than the first, second, and third network addresses. 2. The method of claim 1 , further comprising: caching, by the outbound request manager, information received in response to the first request; and utilizing, by the outbound request manager, the cached information in response to receipt of the second request. 3. The method of claim 1 , further comprising providing a service to clients via the first cluster node and the second cluster node. 4. The method of claim 1 , further comprising organizing network address translation (NAT) on the outbound request manager. 5. The method of claim 1 , wherein the method is performed by a third cluster node having a third network address that serves as the outbound request manager. 6. The method of claim 1 , further comprising: receiving, by the outbound request manager, a plurality of requests for the external service, including the first request and the second request, originating from a plurality of cluster nodes, including the first cluster node and the second cluster node, wherein the outbound request manager is coupled to the plurality of cluster nodes; and transmitting, by the outbound request manager, the plurality of requests with the particular network address from the plurality of cluster nodes to the address associated with the external service. 7. A system, comprising: a plurality of cluster nodes, wherein the plurality of cluster nodes provides a service to clients; and an outbound request manager configured to: transmit first requests for a first external service originating from any of the plurality of cluster nodes to an address associated with the first external service such that the first external service identifies the first requests as originating from a first network address associated with the outbound request manager; and transmit second requests for a second external service originating from any of the plurality of cluster nodes to an address associated with the second external service such that the second external service identifies the second requests as originating from a second network address associated with the outbound request manager. 8. The system of claim 7 , wherein each of the plurality of cluster nodes has a different network address. 9. The system of claim 7 , wherein the particular network address is a virtual Internet Protocol (IP) address different than a primary IP address of the outbound request manager. 10. The system of claim 7 , wherein at least one of the plurality of cluster nodes serves as the outbound request manager. 11. The system of claim 10 , wherein the particular network address is a network address of at least one of the plurality of cluster nodes serving as the outbound request manager. 12. The system of claim 10 , wherein the cluster node serving as the outbound request manager is a leader cluster node, wherein the leader cluster node is one of the plurality of cluster nodes with a greatest quantity of confidence votes from the plurality of cluster nodes. 13. The system of claim 10 , wherein the cluster node serving as the outbound request manager is a leader cluster node, wherein the leader cluster node is one of the plurality of cluster nodes with a greatest bandwidth. 14. The system of claim 10 , wherein the cluster node serving as the outbound request manager is predefined as a leader cluster node or chosen randomly during service runtime. 15. The system of claim 7 , wherein the outbound request manager is further configured to provide a network address translation (NAT) service such that network addresses of the plurality of cluster nodes are hidden from the first and second external services. 16. The system of claim 7 , wherein the outbound request manager is further configured to: cache an authentication associated with a previous request for the first or second external service originating from one of the plurality of cluster nodes; and retrieve the cached authentication in response to a subsequent request for the service originating from the one of the plurality of cluster nodes instead of authenticating via the first or second external service. 17. A non-transitory machine-readable medium storing instructions executable by a processing resource to cause a computing system to: assign a first network address to a request for a first external service originating from one of a plurality of cluster nodes, wherein the first network address is different than a network address of any of the plurality of cluster nodes; assign a second network address to a request for a second external service originating from one of a plurality of cluster nodes, wherein the second network address is different than the network address of any of the plurality of cluster nodes and the first network address; hide the network address of any of the plurality of cluster nodes via a network address translation (NAT); transmit the request for the first external service having the first network address to an address associated with the first external service; and transmit the request for the second external service having the second network address to an address associated with the second external service. 18. The medium of claim 17 , further comprising instructions to: assign the first network address to each of a plurality of requests for the first external service originating from any of the plurality of cluster nodes regardless of a quantity of the plurality of cluster nodes or a quantity of the plurality of requests for the first external service; and transmit the plurality of requests for the first external service to the address associated with the first external service. 19. The medium of claim 17 , further comprising instructions to cache, for the plurality of cluster nodes, information received in response to the request for the first external service. 20. The medium of claim 19 , further comprising instructions to: utilize the cached information in response to receipt of a subsequent request for the first external service originating from a

Assignees

Inventors

Classifications

  • Electricity · mapped topic

  • H04L47/70Primary

    Admission control; Resource allocation · CPC title

  • Electricity · mapped topic

  • Data redirection of data network streams · CPC title

  • using domain name system [DNS] · CPC title

Patent family

Related publications grouped by family.

External sources

Frequently asked questions

Answers are generated from the same data shown on this page.

What does patent US10348636B2 cover?
The present disclosure is related to devices, systems, and methods for routing requests for an external service, originating from a plurality of cluster nodes, through an outbound request manager. An example method can include receiving a first request for an external service originating from a first cluster node having a first network address, receiving a second request for the external servic…
Who is the assignee on this patent?
Vmware Inc
What technology area does this patent fall under?
Primary CPC classification H04L47/70. Mapped technology areas include Electricity.
When was this patent published?
Publication date Tue Jul 09 2019 00:00:00 GMT+0000 (Coordinated Universal Time) (B2). Legal status and post-grant events are not shown on this page.
What related patents are in patentsdb?
We list 2 related publications on this page (citations in our corpus or others sharing the same primary CPC).