Supporting flexible deployment and migration of virtual servers via unique function identifiers
US-2015378772-A1 · Dec 31, 2015 · US
US2016337264A1 · US · A1
| Field | Value |
|---|---|
| Publication number | US-2016337264-A1 |
| Application number | US-201615152727-A |
| Country | US |
| Kind code | A1 |
| Filing date | May 12, 2016 |
| Priority date | May 15, 2015 |
| Publication date | Nov 17, 2016 |
| Grant date | — |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
Systems and methods are disclosed for processing a request for network resources in a network comprising at least one endpoint a first pool of destinations. According to certain embodiments, a first request is received from an endpoint. A determination of whether to validate a first destination identifier associated with the first request is made based on at least one of a first timestamp and a first pool identifier associated with the first request. If it is determined to validate the first destination identifier, a target destination identifier is determined, and the first request is forwarded based on the target destination identifier. The requested network resource is received, and is transmitted to the endpoint.
Opening claim text (preview).
What is claimed is: 1 . A method for processing request for network resources in a network comprising at least one endpoint and a first pool of destinations, the method, performed by an intermediate server, comprising: receiving a first request from the at least one endpoint; determining, from at least one of a first timestamp and a first pool identifier associated with the first request, whether to validate a first destination identifier associated with the first request; responsive to the determination to validate the first destination identifier; determining a target destination identifier, and forwarding the first request based on the target destination identifier; receiving a requested network resource associated with the target destination identifier; and transmitting the requested network resource to the at least one endpoint. 2 . The method of claim 1 , further comprising: responsive to the determination that the first destination identifier is valid, forwarding the first request based on the first destination identifier. 3 . The method of claim 1 , wherein the method further comprises: if the requested network resource is not received within a duration after forwarding the first request: forwarding the first request based on a second destination identifier, creating a second timestamp, and transmitting the second timestamp and the second destination identifier to the at least one endpoint. 4 . The method of claim 3 , wherein the first destination identifier and the second destination identifier are associated with the first pool of destinations. 5 . The method of claim 3 , wherein the transmission of the second timestamp and the second destination identifier enables the at least one endpoint to transmit a second request associated with the second destination identifier and the second timestamp. 6 . The method of claim 1 , wherein determining the target destination identifier comprises: acquiring configuration data that stores an association between the first pool identifier and one or more destination identifiers, wherein the one or more destination identifiers includes a second destination identifier; and determining the target destination identifier to be one of the first destination identifier and the second destination identifier, based on whether the first destination identifier is associated with the first pool identifier. 7 . The method of claim 1 , wherein the network further comprises a second pool of destinations; and wherein determining whether to validate the first destination identifier comprises determining, based on the first pool identifier, whether the first pool of destinations is configured to provide the requested network resource; and wherein determining a target destination identifier comprises: responsive to determining that the first pool of destinations is not configured to provide the requested network resource: determining the second pool of destinations, wherein the second pool of destinations is configured to provide the requested network resource and is associated with a second pool identifier; determining the target destination identifier to be a second destination identifier associated with a second destination included in the second pool of destinations; creating a second timestamp, and transmitting the second timestamp, the second pool identifier, and the second destination identifier to the at least one endpoint. 8 . The method of claim 1 , further comprising: receiving a second request not including any destination identifier from the at least one endpoint; responsive to receiving the second request, determining the first pool of destinations, wherein the first pool of destinations includes a first destination associated with the first destination identifier; creating the first timestamp; and transmitting, to the at least one endpoint, the first destination identifier, the first pool identifier, and the first timestamp; wherein the transmission of the first destination identifier, the first pool identifier, and the first timestamp enables the at least one endpoint to transmit the first request. 9 . The method of claim 1 , wherein the first destination identifier includes an Internet Protocol (IP) address and a port number. 10 . A server for processing request for network resources in a network comprising at least one endpoint and a first pool of destinations, wherein the server comprises at least one processor configured to: receive a first request from the at least one endpoint; determine, from at least one of a first timestamp and a first pool identifier associated with the first request, whether to validate a first destination identifier associated with the first request; responsive to the determination to validate the first destination identifier; determine a target destination identifier, and forward the first request based on the target destination identifier; receive a requested network resource associated with the target destination identifier; and transmit the requested network resource to the at least one endpoint. 11 . The server of claim 10 , wherein the at least one processor is further configured to: responsive to the determination that the first destination identifier is valid, forward the first request based on the first destination identifier. 12 . The server of claim 10 , wherein the at least one processor is further configured to: if the requested network resource is not received within a duration after the first request is forwarded: forward the first request based on a second destination identifier; create a second timestamp; and transmit the second timestamp and the second destination identifier to the at least one endpoint. 13 . The server of claim 10 , wherein the at least one processor is configured to determine the target destination identifier comprises the at least one processor being configured to; acquire configuration data that stores an association between the first pool identifier and one or more destination identifiers, wherein the one or more destination identifiers includes a second destination identifier; and determine the target destination identifier to be one of the first destination identifier and the second destination identifier, based on whether the first destination identifier is associated with the first pool identifier. 14 . The server of claim 10 , wherein the network further comprises a second pool of destinations; and wherein the at least one processor is configured to determine whether to validate the first destination identifier comprises the at least one processor being configured to determine, based on the first pool identifier, whether the first pool of destinations is configured to provide the requested network resource; and wherein the at least one processor is configured to determine a target destination identifier comprises the at least one processor being configured to: responsive to the determination that the first pool of destinations is not configured to provide the requested network resource: determine the second pool of destinations, wherein the second pool of destinations is configured to provide the requested network resource and is associated with a second pool identifier; determine the target destination identifier to be a second destination identifier associated with a second destination included in the second pool of destinations; create a second timestamp, and transmit the second timestamp, the second pool identifier, and the second destination identifier to the at least one endpoint. 15 . The server of claim 10 ,
Aggregation of resource allocation or reservation requests · CPC title
using time related information in packets, e.g. by adding timestamps · CPC title
Electricity · mapped topic
Routing a service request depending on the request content or context · CPC title
Session initiation protocol [SIP] · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.