Dynamically generating application-layer traffic optimization protocol maps

• US 9,413,847 B2
• Filed: 04/14/2014
• Issued: 08/09/2016
• Est. Priority Date: 12/01/2010
• Status: Expired due to Fees

• Current Assignee: Juniper Networks Incorporated
• Original Assignee: Juniper Networks Incorporated
• Inventors: Medved, Jan, Gredler, Hannes, Ward, David, Raghunath, Satish
• Primary Examiner(s): Patel, Chandrahas
• Assistant Examiner(s): TRUONG, LAN-HUONG
• Application Number:
  US14/252,526
• Publication Number:
  US 20140229581A1
• Time in Patent Office: 848 Days
• US Class Current: 1/1
• CPC Class Codes: H04L 45/02 Topology update or discovery
• CPC Class Codes: H04L 45/04 Interdomain routing, e.g. hierarchical routing
• CPC Class Codes: H04L 45/42 Centralised routing
• CPC Class Codes: H04L 45/64 using an overlay routing layer
• CPC Class Codes: 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
• CPC Class Codes: H04L 69/321 Interlayer communication protocols or service data unit [SDU] definitions; Interfaces between layers
• CPC Class Codes: H04L 69/329 in the application layer [OSI layer 7]

Abstract

In general, techniques are described for using routing information obtained by operation of network routing protocols to dynamically generate network and cost maps for an application-layer traffic optimization (ALTO) service. For example, an ALTO server of an autonomous system (AS) receives routing information from routers of the AS by listening for routing protocol updates outputted by the routers and uses the received topology information to dynamically generate a network map of PIDs that reflects a current topology of the AS and/or of the broader network that includes the AS. Additionally, the ALTO server dynamically calculates inter-PID costs using received routing information that reflects current link metrics. The ALTO server then assembles the inter-PID costs into a cost map that the ALTO server may provide, along with the network map, to clients of the ALTO service.

Claims

1. A method comprising:

receiving, by an application-layer traffic optimization (ALTO) server, a first layer 3 topology information advertisement that specifies a first one or more endpoints and includes a first Border Gateway Protocol (BGP) communities path attribute that specifies an attribute value for the first endpoints, wherein the first layer 3 topology information advertisement further includes a first next hop attribute that specifies a next hop for the first endpoints;

receiving, by the ALTO server, a second layer 3 topology information advertisement that specifies a second one or more endpoints and includes a second BGP communities path attribute that specifies an attribute value for the second endpoints, wherein the second layer 3 topology information advertisement further includes a second next hop attribute that specifies a next hop for the second endpoints,

wherein the attribute value for the first endpoints and the attribute value for the second endpoints are different, and

wherein the next hop for the first endpoints and the next hop for the second endpoints are the same;

aggregating, by the ALTO server, the first endpoints into a first provider-defined identifier (PID) of a plurality of PIDs based at least on a combination of the attribute value for the first endpoints and the next hop for the first endpoints, the attribute value for the first endpoints and the attribute value for the second endpoints each comprising one of a BGP community attribute value, a BGP extended community attribute value, and a combination of a BGP community attribute value and a BGP extended community attribute value;

aggregating, by the ALTO server, the second endpoints into a second PID of the plurality of PIDs based at least on the attribute value for the second endpoints and the next hop for the second endpoints, the first PID different from the second PID; and

generating, by the ALTO server, an ALTO network map for an ALTO service based at least on the first PID and the second PID and providing the ALTO service to a client device in accordance with the ALTO network map.

2. The method of claim 1, further comprising:

applying, by the ALTO server, a community attribute map to the attribute value to map the attribute value for the first endpoints to a PID identifier that identifies the first PID,

wherein aggregating the first endpoints into the first PID comprises aggregating the first endpoints based on the PID identifier.

3. The method of claim 1,

wherein the first layer 3 topology information advertisement further specifies an autonomous system path that specifies an autonomous system that originated the first layer 3 topology information advertisement,

wherein aggregating the first endpoints into the first PID comprises aggregating the first endpoints into the first PID based at least on a combination of the attribute value for the first endpoints and the autonomous system that originated the first layer 3 topology information advertisement.

4. The method of claim 1,

wherein the first layer 3 topology information advertisement further specifies an autonomous system path for the first endpoints, the autonomous system path specifying an autonomous system that originated the first layer 3 topology information advertisement,

wherein aggregating the first endpoints into the first PID comprises aggregating the first endpoints into the first PID based at least on a combination of the attribute value for the first endpoints and the autonomous system path, and

wherein the autonomous system path length affects an application layer cost between the first PID and at least one other PID of the plurality of PIDs.

5. The method of claim 1,

wherein the attribute value for the first endpoints identifies an endpoint type for the first endpoints, and

wherein the endpoint type for the first endpoints affects an application layer cost between the first PID and at least one other PID of the plurality of PIDs.

6. The method of claim 1, wherein the first layer 3 topology information advertisement comprises a Border Gateway Protocol UPDATE message.

7. The method of claim 1,

further comprising:

receiving, by ALTO server, a third layer 3 topology information advertisement that specifies a third one or more endpoints and an attribute value for the third endpoints, wherein the third layer 3 topology information advertisement further includes a third next hop attribute that specifies a next hop for the third endpoints, the attribute value for the third endpoints comprising one of a Border Gateway Protocol (BGP) community attribute value, a BGP extended community attribute value, and a combination of a BGP community attribute value and a BGP extended community attribute value; and

based at least on determining the attribute value for the third endpoints is the same as the attribute value for the first endpoints and the next hop for the third endpoint is different than the next hop for the first endpoint, aggregating, by the ALTO server, the third endpoints into a third PID of the plurality of PIDs,

wherein generating the ALTO network map comprises generating the ALTO network map based at least on the third PID.

8. The method of claim 1, wherein the client device comprises one of a peer-to-peer device, a content request router, and another ALTO server.

9. The method of claim 1, wherein providing the ALTO service further comprises one of sending the ALTO network map to the client device and selecting, based at least on the ALTO network map, one of the first endpoints of the first PID for a content request received by the ALTO server.

10. The method of claim 1, wherein aggregating the endpoints into the first PID comprises assigning the attribute value for the first endpoints to the first PID for comparison, by the ALTO server, with an attribute value specified in a subsequent layer 3 topology information advertisement.

11. The method of claim 1, further comprising:

computing, by the ALTO server, an application layer cost between the first PID and at least one other PID of the plurality of PIDs based at least on the attribute value for the first endpoints,

wherein providing the ALTO service comprises providing the ALTO service to the client device based at least on the application layer cost between the first PID and the at least one other PID.

12. An application-layer traffic optimization (ALTO) server comprising:

at least one processor operably coupled to a memory;

a protocol listener configured for execution by the at least one processor to receive a first layer 3 topology information advertisement that specifies a first one or more endpoints and includes a Border Gateway Protocol (BGP) communities path attribute that specifies an attribute value for the first endpoints, wherein the first layer 3 topology information advertisement further includes a first next hop attribute that specifies a next hop for the first endpoints,

wherein the protocol listener is configured to receive a second layer 3 topology information advertisement that specifies a second one or more endpoints and includes a second BGP communities path attribute that specifies an attribute value for the second endpoints, wherein the second layer 3 topology information advertisement further includes a second next hop attribute that specifies a next hop for the second endpoints,

wherein the attribute value for the first endpoints and the attribute value for the second endpoints are different, and

wherein the next hop for the first endpoints and the next hop for the second endpoints are the same;

a PID generator configured for execution by the at least one processor to aggregate the first endpoints into a first provider-defined identifier (PID) of a plurality of PIDs based at least on a combination of the attribute value for the first endpoints and the next hop for the first endpoints, the attribute value for the first endpoints and the attribute value for the second endpoints each comprising one of a BGP community attribute value, a BGP extended community attribute value, and a combination of a BGP community attribute value and a BGP extended community attribute value,

wherein the PID generator is configured to aggregate the second endpoints into a second PID of the plurality of PIDs based at least on the attribute value for the second endpoints and the next hop for the second endpoints, the first PID different from the second PID;

a network map module configured for execution by the at least one processor to generate an ALTO network map for an ALTO service based at least on the first PID and the second PID; and

a client interface configured for execution by the at least one processor to provide the ALTO service to a client device in accordance with the ALTO network map.

13. The ALTO server of claim 12, further comprising:

a community attribute map,

wherein the PID generator is further configured to apply the community attribute map to the attribute value to map the attribute value for the first endpoints to a PID identifier that identifies the first PID

wherein the PID generator, to aggregate the first endpoints into the first PID comprises aggregating the first endpoints based on the PID identifier.

14. The ALTO server of claim 12, wherein the first layer 3 topology information advertisement comprises a Border Gateway Protocol UPDATE message.

15. The ALTO server of claim 12, wherein providing the ALTO service further comprises one of sending the ALTO network map to the client device and selecting, based at least on the ALTO network map, one of the first endpoints of the first PID for a content request received by the ALTO server.

16. The ALTO server of claim 12, further comprising:

a cost map module configured for execution by the at least one processor to compute an application layer cost between the first PID and at least one other PID of the plurality of PIDs based at least on the attribute value for the first endpoints,

wherein the client interface is further configured to provide the ALTO service to the client device based at least on the application layer cost between the first PID and the at least one other PID.

17. A non-transitory computer-readable medium comprising instructions that, when executed, cause one or more processors to:

receive, by an application-layer traffic optimization (ALTO) server, a first layer 3 topology information advertisement that specifies a first one or more endpoints and includes a first Border Gateway Protocol (BGP) communities path attribute that specifies an attribute value for the first endpoints, wherein the first layer 3 topology information advertisement further includes a first next hop attribute that specifies a next hop for the first endpoints;

receive, by the ALTO server, a second layer 3 topology information advertisement that specifies a second one or more endpoints and includes a second BGP communities path attribute that specifies an attribute value for the second endpoints, wherein the second layer 3 topology information advertisement further includes a second next hop attribute that specifies a next hop for the second endpoints,

wherein the attribute value for the first endpoints and the attribute value for the second endpoints are different, and

wherein the next hop for the first endpoints and the next hop for the second endpoints are the same;

aggregate, by the ALTO server, the first endpoints into a first provider-defined identifier (PID) of a plurality of PIDs based at least on a combination of the attribute value for the first endpoints and the next hop for the first endpoints, the attribute value for the first endpoints and the attribute value for the second endpoints each comprising one of a BGP community attribute value, a BGP extended community attribute value, and a combination of a BGP community attribute value and a BGP extended community attribute value;

aggregate, by the ALTO server, the second endpoints into a second PID of the plurality of PIDs based at least on the attribute value for the second endpoints and the next hop for the second endpoints, the first PID different from the second PID; and

generate, by the ALTO server, an ALTO network map for an ALTO service based at least on the first PID and the second PID and providing the ALTO service to a client device in accordance with the ALTO network map.