IP Library Granted Patent US 10,298,493
Granted Patent B2
US 10,298,493 · App. 14/610,965 · Granted May 21, 2019

Processing route data

View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 10,298,493
App. No.
14/610,965
Granted
May 21, 2019
Kind
B2
Abstract

Measures, including methods, systems and computer program products, for use in processing route data in a network comprising a plurality of autonomous systems. At a network device, route data defining at least one route for network traffic which is configured on at least one border network device is received from the at least one border network device. The at least one border network device is located at a border of an autonomous system in the plurality of autonomous systems. The network device processes the received route data according to a set of policies to generate modified route data. The network device transmits at least a part of the modified route data to the at least one border network device. The at least part of the modified route data is operable to instruct the at least one border network device to modify the behavior of the at least one route.

Claims (35)

1. A method for use in processing route data in a network comprising a plurality of autonomous systems, the method comprising:

at a network route data modification server, receiving, from at least one border network device in the network, route data defining at least one route for network traffic which is configured on the at least one border network device from which the route data was received, wherein the at least one border network device from which the route data was received is located at a border of an autonomous system in the plurality of autonomous systems;

at the network route data modification server, processing the route data received from the at least one border network device according to a set of policies to generate modified route data, wherein generating the modified route data comprises inserting metadata that defines one or more modifications to the at least one route into the received route data and inhibiting adding data indicating that the route data was previously received from the at least one border network device, wherein either (i) the modified route data includes a data field data that indicates where the route data was received from and the data field is left blank or is filled in with dummy data that does not identify the at least one border network device from which the route data was received or (ii) the modified route data does not include a data field that indicates where the route data was received from; and

at the network route data modification server, transmitting, to the at least one border network device from which the route data was received, the generated modified route data, wherein the metadata in the generated modified route data is operable to instruct the at least one border network device from which the route data was received to modify the behavior of the at least one route on the at least one border network device from which the route data was received by one or more of installing, withdrawing, promoting and demoting the at least one route.

2. The method of claim 1 , comprising, at the network route data modification server, transmitting, to at least one other border network device, the modified route data, wherein the modified route data is operable to instruct the at least one other border network device to modify the behavior of at least one route.

3. The method of claim 1 , wherein the set of policies comprises at least one of:

one or more network operator-defined static policies, and

one or more dynamic policies based at least in part on one or more of historical route data and externally sourced route data.

4. The method of claim 3 , comprising, at the network route data modification server, obtaining at least a part of the one or more historical route data and externally sourced route data from an Internet Route Registry (IRR) database located in the network.

5. The method of claim 1 , comprising configuring the network route data modification server to operate as a route reflector entity in the network, wherein the at least one border network device from which the route data was received is configured to operate as a route reflector client in the network, whereby the route data is received at the network route data modification server from the at least one border network device and the modified route data is transmitted from the network route data modification server to the at least one border network device from which the route data was received via a route reflector and route reflector client route data propagation mechanism.

6. The method of claim 5 , comprising, at the network route data modification server, transmitting, to at least one further border network device which is configured to operate as a route reflector client in the network, the modified route data, wherein the modified route data is operable to instruct the at least one further border network device to modify the behavior of at least one of its configured routes.

7. The method of claim 1 , wherein the route data received from the at least one border network device comprises route data for one or more preferred routes and route data for one or more less preferred routes.

8. The method of claim 1 , wherein the route data received from the at least one border network device comprises route data for all of the routes configured on the at least one border network device from which the route data was received.

9. The method of claim 1 , wherein the route data is received from the at least one border network device and the modified route data is transmitted from the network route data modification server using a mechanism which enables advertisement of multiple routes to the same destination prefix.

10. The method of claim 9 , wherein the mechanism which enables advertisement of multiple routes to the same destination prefix comprises one or more of:

the add-path extension to the Border Gateway Protocol (BGP), and

one or more internal Border Gateway Protocol (BGP) sessions.

11. The method of claim 1 , comprising configuring the network route data modification server to operate as a monitoring entity in the network, wherein the at least one border network device from which the route data was received is configured to recognize the network route data modification server as a route data monitoring entity, whereby the route data is received at the network route data modification server from the at least one border network device and the modified route data is transmitted from the network route modification server to the at least one border network device from which the route data was received via a route data monitoring protocol.

12. The method of claim 11 , comprising, at the network route data modification server, transmitting, to at least one further border network device which is configured to recognize the network route data modification server as a route data monitoring entity, the modified route data, wherein the modified route data is operable to instruct the at least one further border network device to modify the behavior of at least one of its configured routes.

13. The method of claim 1 , wherein the modified route data does not comprise data identifying an autonomous system in which the network route data modification server is located.

14. The method of claim 1 , wherein the processing does not comprise altering the next hop address of the at least one route.

15. The method of claim 1 , comprising configuring the network route data modification server to operate as a Resource Public Key Infrastructure (RPKI) server, wherein the at least one border network device from which the route data was received is configured to operate as a RPKI client in the network, whereby the route data is received at the network route data modification server from the at least one border network device and the modified route data is transmitted from the network route data modification server to the at least one border network device from which the route data was received via a RPKI query and response mechanism.

16. The method of claim 15 , comprising, at the network route data modification server, transmitting, to at least one further border network device which is configured to operate as a RPKI client in the network, the modified route data, wherein the modified route data is operable to instruct the at least one further border network device to modify the behavior of at least one of its configured routes.

17. A system for use in processing route data in a network comprising a plurality of autonomous systems, the system comprising at least one memory including computer program code; and at least one processor in data communication with the at least one memory, wherein the at least one processor is configured to:

at a network route data modification server, receive, from at least one border network device in the network, route data defining at least one route for network traffic which is configured on the at least one border network device from which the route data was received, wherein the at least one border network device from which the route data was received is located at a border of an autonomous system in the plurality of autonomous systems;

at the network route data modification server, process the route data received from the at least one border network device according to a set of policies to generate modified route data for the at least one route, wherein generating the modified route data comprises inserting metadata that defines one or more modifications to the at least one route into the received route data and inhibiting adding data indicating that the route data was previously received from the at least one border network device, wherein either (i) the modified route data includes a data field data that indicates where the route data was received from and the data field is left blank or is filled in with dummy data that does not identify the at least one border network device from which the route data was received or (ii) the modified route data does not include a data field that indicates where the route data was received from; and

at the network route data modification server, transmit, to the at least one border network device from which the route data was received, the generated modified route data, wherein the metadata in the generated modified route data is operable to instruct the at least one border network device from which the route data was received to modify the behavior of the at least one route on the at least one border network device from which the route data was received by one or more of installing, withdrawing, promoting and demoting the at least one route.

18. A non-transitory computer-readable storage medium comprising computer-executable instructions which, when executed by a processor, cause a computing device to perform a method for use in processing route data in a network comprising a plurality of autonomous systems, the method comprising:

at a network route data modification server, receiving, from at least one border network device in the network, route data defining at least one route for network traffic which is configured on the at least one border network device from which the route data was received, wherein the at least one border network device from which the route data was received is located at a border of an autonomous system in the plurality of autonomous systems;

at the network route data modification server, processing the route data received from the at least one border network device according to a set of policies to generate modified route data, wherein generating the modified route data comprises inserting metadata that defines one or more modifications to the at least one route into the received route data and inhibiting adding data indicating that the route data was previously received from the at least one border network device, wherein either (i) the modified route data includes a data field data that indicates where the route data was received from and the data field is left blank or is filled in with dummy data that does not identify the at least one border network device from which the route data was received or (ii) the modified route data does not include a data field that indicates where the route data was received from; and

at the network route data modification server, transmitting, to the at least one border network device from which the route data was received, the generated modified route data, wherein the metadata in the generated modified route data is operable to instruct the at least one border network device from which the route data was received to modify the behavior of the at least one route on the at least one border network device from which the route data was received by one or more of installing, withdrawing, promoting and demoting the at least one route.

19. A method for use in processing route data in a network comprising a plurality of autonomous systems, the method comprising:

at a border network device in the network, transmitting, to a network route data modification server, route data defining at least one route for network traffic which is configured on the border network device, wherein the border network device is located at a border of an autonomous system in the plurality of autonomous systems;

at the border network device, receiving, from the network route data modification server, modified route data, the modified route data having been generated at the network route data modification server by processing the route data transmitted from the border network device according to a set of policies, wherein generating the modified route data comprises inserting metadata that defines one or more modifications to the at least one route into the received route data and inhibiting adding data indicating that the route data was previously received from the at least one border network device, wherein either (i) the modified route data includes a data field data that indicates where the route data was received from and the data field is left blank or is filled in with dummy data that does not identify the at least one border network device from which the route data was received or (ii) the modified route data does not include a data field that indicates where the route data was received from; and

at the border network device, in response to receipt of the generated modified route data, modifying the behavior of the at least one route on the at least one border network device by one or more of installing, withdrawing, promoting and demoting the at least one route.

Assignments (5)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded May 13, 2026
From: MICROSOFT TECHNOLOGY LICENSING, LLC
To: ALIANZA, INC.
Reel/Frame 075645/0892 →
CHANGE OF NAME Recorded May 13, 2026
From: ALIANZA, INC.
To: ALIANZA, LLC
Reel/Frame 075646/0037 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded May 13, 2026
From: METASWITCH NETWORKS LTD.
To: MICROSOFT TECHNOLOGY LICENSING, LLC
Reel/Frame 075578/0155 →
SECURITY INTEREST Recorded May 6, 2025
From: ALIANZA, INC.; METASWITCH NETWORKS LTD
To: WELLS FARGO BANK, NATIONAL ASSOCIATION
Reel/Frame 071191/0228 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jul 7, 2015
From: LILJENSTOLPE, CHRISTOPHER DAVID; HARDWICK, JONATHAN ERIC; BERGER, JONATHAN RICHARD
To: METASWITCH NETWORKS LTD
Reel/Frame 036074/0180 →