Granted Patent B2

US 12,574,305 · App. 18/594,471 · Granted Mar 10, 2026

Inventors: Sabine Randriamasy (Meudon, FR); Bernard Sales (Biewart/Fernelmont, BE); Frédéric Faucheux (Paris, FR)

Assignee: Nokia Solutions and Networks Oy

H04L43/065H04L43/04H04L67/1008H04L67/101

Abstract

Claims (64)

1 . In a system comprising an application client selectively connectable to any one of multiple edge servers by a routing network comprising (i) an ingress edge router connected to the application client and (ii) multiple egress edge routers connected variously to the multiple edge servers, a method for identifying one of the multiple edge servers for the application client, each edge server of the multiple edge servers represented by a corresponding service contact point, the method comprising:

receiving an initial list of Internet Protocol (IP) addresses for the application client from a name resolution function of the system;

generating, for each IP address in the initial list, a global utility value based on (i) a corresponding set of one or more network metrics and (ii) a corresponding set of one or more compute metrics; and

re-ordering the initial list based on corresponding global utility values to generate a re-ordered list of the IP addresses for the application client, wherein an edge server for the client application is selectable based on the re-ordered list, wherein generating the global utility value for each IP address in the initial list comprises:

generating a corresponding relative network utility measure based on the corresponding set of one or more network metrics;

generating a corresponding relative compute utility measure based on the corresponding set of one or more compute metrics:

generating a corresponding joint utility vector based on the corresponding relative network utility measure and the corresponding relative compute utility measure;

generating a corresponding weighted joint utility vector based on the corresponding joint utility vector; and

generating the global utility value based on the corresponding weighted joint utility vector.

2 . The method of claim 1 , wherein:

each item in the re-ordered list is an IP address pair comprising (i) an IP address for one of the multiple egress edge routers and (ii) an IP address for one of the multiple edge servers; and

an egress edge router and the edge server for the client application are selectable based on the re-ordered list.

3 . The method of claim 1 , wherein, for each IP address in the initial list:

the corresponding set of one or more network metrics comprises two or more different network metrics;

the corresponding relative network utility measure is generated using the two or more different network metrics as vector elements in a network-metric-vector-based evaluation;

the corresponding set of one or more compute metrics comprises two or more different compute metrics;

the corresponding relative compute utility measure is generated using the two or more different compute metrics as vector elements in a compute-metric-vector-based evaluation; and

the network-metric-vector-based evaluation is separate from the compute-metric-vector-based evaluation.

4 . The method of claim 1 , wherein, for each IP address in the initial list:

the corresponding joint utility vector is generated by:

generating a normalized network utility measure based on (i) the corresponding relative network utility measure and (ii) a best relative network utility measure for all of the IP addresses in the initial list; and

generating a normalized compute utility measure based on (i) the corresponding relative compute utility measure and (ii) a best relative compute utility measure for all of the IP addresses in the initial list;

the corresponding weighted joint utility vector is generated by:

multiplying the normalized network utility measure by a network weight factor; and

multiplying the normalized compute utility measure by a compute weight factor; and

the global utility value is generated based on length of the corresponding weighted joint utility vector.

5 . The method of claim 1 , wherein the method is performed by an off-path function of the system.

6 . The method of claim 5 , wherein the off-path function (i) selects the edge server for the application client based on a first item in the re-ordered list and (ii) sends a message to the application client identifying the selected edge server.

7 . The method of claim 5 , wherein the off-path function (i) selects an egress edge router and the edge server for the application client based on a first IP address pair in the re-ordered list, (ii) sends a message to the application client with the initial list of IP addresses, and (iii) sends a message to the ingress edge router identifying the selected egress edge router and the selected edge server or a corresponding routing policy.

8 . The method of claim 5 , wherein the off-path function sends the re-ordered list to the application client.

9 . The method of claim 5 , wherein the method is performed upon receipt of a request sent by an in-path client implemented at the ingress edge router.

10 . An apparatus for a system comprising an application client selectively connectable to any one of multiple edge servers by a routing network comprising (i) an ingress edge router connected to the application client and (ii) multiple egress edge routers connected variously to the multiple edge servers, each edge server of the multiple edge servers represented by a corresponding service contact point, the apparatus comprising:

at least one processor; and

at least one memory storing instructions that, upon being executed by the at least one processor, cause the apparatus at least to:

receive an initial list of Internet Protocol (IP) addresses for the application client from a name resolution function of the system;

generate, for each IP address in the initial list, a global utility value based on (i) a corresponding set of one or more network metrics and (ii) a corresponding set of one or more compute metrics; and

re-order the initial list based on corresponding global utility values to generate a re-ordered list of the IP addresses for the application client, wherein an edge server for the client application is selectable based on the re-ordered list, wherein generating the global utility value for each IP address in the initial list comprises:

generating a corresponding relative network utility measure based on the corresponding set of one or more network metrics;

generating a corresponding relative compute utility measure based on the corresponding set of one or more compute metrics;

generating a corresponding joint utility vector based on the corresponding relative network utility measure and the corresponding relative compute utility measure;

generating a corresponding weighted joint utility vector based on the corresponding joint utility vector; and

generating the global utility value based on the corresponding weighted joint utility vector.

11 . The apparatus of claim 10 , wherein:

each item in the re-ordered list is an IP address pair comprising (i) an IP address for one of the multiple egress edge routers and (ii) an IP address for one of the multiple edge servers; and

an egress edge router and the edge server for the client application are selectable based on the re-ordered list.

12 . The apparatus of claim 10 , wherein, for each IP address in the initial list:

the corresponding set of one or more network metrics comprises two or more different network metrics;

the apparatus is adapted to generate the corresponding relative network utility measure using the two or more different network metrics as vector elements in a network-metric-vector-based evaluation;

the corresponding set of one or more compute metrics comprises two or more different compute metrics;

the apparatus is adapted to generate the corresponding relative compute utility measure using the two or more different compute metrics as vector elements in a compute-metric-vector-based evaluation; and

the network-metric-vector-based evaluation is separate from the compute-metric-vector-based evaluation.

13 . The apparatus of claim 10 , wherein, for each IP address in the initial list:

the apparatus is adapted to generate the corresponding joint utility vector by:

generating a normalized network utility measure based on (i) the corresponding relative network utility measure and (ii) a best relative network utility measure for all of the IP addresses in the initial list; and

generating a normalized compute utility measure based on (i) the corresponding relative compute utility measure and (ii) a best relative compute utility measure for all of the IP addresses in the initial list;

the apparatus is adapted to generate the corresponding weighted joint utility vector by:

multiplying the normalized network utility measure by a network weight factor; and

multiplying the normalized compute utility measure by a compute weight factor; and

the apparatus is adapted to generate the global utility value based on length of the corresponding weighted joint utility vector.

14 . The apparatus of claim 10 , wherein the apparatus is adapted to operate as an off-path function of the system.

15 . The apparatus of claim 14 , wherein the off-path function is adapted to (i) select the edge server for the application client based on a first item in the re-ordered list and (ii) send a message to the application client identifying the selected edge server.

16 . The apparatus of claim 14 , wherein the off-path function is adapted to (i) select an egress edge router and the edge server for the application client based on a first IP address pair in the re-ordered list, (ii) send a message to the application client with the initial list of IP addresses, and (iii) send a message to the ingress edge router identifying the selected egress edge router and the selected edge server or a corresponding routing policy.

17 . The apparatus of claim 14 , wherein the off-path function is adapted to send the re-ordered list to the application client.

18 . The apparatus of claim 14 , wherein the off-path function is adapted to operate upon receipt of a request sent by an in-path client implemented at the ingress edge router.

Assignments (4)

Continuity (1)

References Cited (32)