Functional decomposition of a router to support virtual private network (VPN) services

• US 20040255028A1
• Filed: 05/30/2003
• Published: 12/16/2004
• Est. Priority Date: 05/30/2003
• Status: Abandoned Application

• Current Assignee: Lucent Technologies, Inc. (Nokia Corporation)
• Original Assignee: Lucent Technologies, Inc. (Nokia Corporation)
• Inventors: Richman, Steven Howard, Trivedi, Bhadrayu J., Magee, Francis Robert Jr., Chu, Thomas P.
• Application Number:
  US10/449,549
• Publication Number:
  US 20040255028A1
• Time in Patent Office: Days
• US Class Current: 709/227
• CPC Class Codes: H04L 63/0272 Virtual private networks

Abstract

A method and apparatus for providing virtual private network (VPN) connectivity between at least two customer sites. Each of a plurality of PE routers includes at least one access module adapted for connectivity to at least one customer site. The access modules are generated automatically for each PE router associated with a VPN, wherein customer sites, which are associated with said VPN and have an identical export route target (RT) value and import RT value, are connected to a common access module. Otherwise, customer sites associated with the PE router that do not have identical export and import RT values are coupled to their own respective access modules at the PE router. Each access module generates an ingress-forwarding table for routing packetized information between the at least two customer sites.

Claims

1. In a service provider (SP) network comprising a plurality of provider edge (PE) routers and customer sites each having a respective customer edge (CE) router, a method for providing virtual private network (VPN) connectivity between at least two customer sites, comprising:

automatically generating at least one access module for each PE router associated with a VPN, such that customer sites that are associated with said VPN and have an identical export route target (RT) value and import RT value, are connected to a common access module;

generating an ingress-forwarding table for each access module; and

routing packetized information between said at least two customer sites via at least one label switched path.

2. The method of claim 1, wherein said automatically generating said at least one access module at each PE router further comprises connecting customer sites, which are associated with said VPN without having identical export and import RT values, to their own respective access modules.

3. The method of claim 1, wherein prior to automatically generating said at least one access module, said method further comprises:

specifying a routing protocol, route target (RT) import and export lists, an IP address respectively associated with each VPN route, and access interfaces for each said customer site; and

advertising VPN routes between peer PE routers.

4. The method of claim 3, wherein each said import and export RT lists respectively comprises import and export RT values, wherein said specified import RT lists and export RT lists are based on a desired network topology.

5. The method of claim 4, wherein said advertising step further comprises distributing routes between said peer PE routers using border gateway protocol with multi-protocol extension (BGP-MP).

6. The method of claim 1, wherein said generating said ingress-forwarding table for each access module comprises comparing received RT values from route advertisements to said export RT list of said access module.

7. The method of claim 6 further comprising, in an instance where any advertised RT values from an RT import list of an access module of a peer PE router having an identical RT value to any RT values in the export RT list associated with said access module, an entry is created in said ingress-forwarding table of the access module.

8. The method of claim 6, wherein an entry in said ingress-forwarding table comprises:

an IP address associated with a destination advertising a route;

an interior MPLS label from said route advertisement

an exterior MPLS label determined from said IP address of said destination advertising the route; and

a grade of service of said VPN.

9. The method of claim 6 further comprising, in an instance where any RT values in an import list of an access module of have an identical RT value to any RT values in an export RT list of said common access module, an entry is created in said ingress-forwarding table of the common access module, thereby allowing said customer sites connecting to said common access module to send packets to each other.

10. The method of claim 6 further comprising, in an instance where any RT values from an RT import list of a first access module of a PE router have any identical RT values to any RT values in an export RT list associated with a second access module in said PE router, an entry is created in said ingress-forwarding table of said second access module, thereby allowing packets to be sent to said first access module.

11. The method of claim 5, wherein customer sites belonging to the same access module are assigned a common route distinguisher (RD) in an instance where the import RT list matches the export RT list;

and

otherwise, assigning different route distinguishers in an instance where the import RT list and the export RT list differ.

12. The method of claim 4, wherein in an instance said network topology changes, said method further comprises:

removing a site from said VPN;

modifying the import RT and export RT lists of said site; and

in an instance where it is desirable to add a new customer site to said VPN, adding said new customer site to said VPN.

13. A provider edge (PE) router comprising:

at least one access module adapted for connectivity to at least one customer site in a VPN, wherein customer sites associated with a particular VPN having any identical export route target (RT) values and import RT values are connected to a common access module; and

customer sites associated with said PE router that do not have identical export and import RT values are coupled to their own respective access modules at said PE router.

14. The router of claim 13, further comprising an aggregation module connected to each of said at least one access modules, wherein said aggregation module is adapted for providing connectivity between at least two access modules in a common PE router.

15. The route of claim 14, wherein said aggregation module is adapted for providing connectivity between peer PE routers in said VPN.

16. The router of claim 13, wherein said PE router complies with Internet Engineering Task Force Request For Comments (IETF-RFC) specification 2547 for providing virtual VPN services.

17. The router of claim 13, wherein said PE router communicates with other PE routers using a VPN routing protocol to exchange VPV information.

18. The router of claim 17, wherein the VPN routing protocol comprises Border Gateway Protocol with Multi-Protocol extension (MP-BGP).

19. The router of claim 13, wherein customer sites, which are associated with said VPN and have an identical export route target (RT) value and import RT value, are connected to a common access module.

20. The router of claim 19, wherein customer sites, which are associated with said VPN without having identical export and import RT values, are connected to their own respective access modules.

21. The router of claim 13, wherein each access module comprises an ingress-forwarding table for routing incoming packets.

22. The router of claim 21, wherein said ingress-forwarding table is constructed automatically by said PE router based on route information from at least one of peer routers in the network and other access modules generated in said PE router.

23. The router of claim 22, wherein said ingress-forwarding table comprises:

an ingress-forwarding table entry, in an instance where said access module can import a route target associated with a route.

24. The router of claim 23, wherein each said ingress-forwarding table entry comprises:

an internet protocol (IP) address of a route;

a type of the connection to one of a peer PE router, another access module in the same router, and a different site associated with said access module;

an identifier of an egress device; and

an interior MPLS label associated with the route.

25. In a service provider (SP) network comprising a plurality of provider edge (PE) routers and customer sites each having a respective customer edge (CE) router, an apparatus for providing virtual private network (VPN) connectivity between at least two customer sites, comprising:

means for automatically generating at least one access module for each PE router associated with a VPN, such that customer sites that are associated with said VPN and have an identical export route target (RT) value and import RT value, are connected to a common access module;

means for generating an ingress-forwarding table for each access module; and

means for routing packetized information between said at least two customer sites via at least one label switched path.