US2004059829A1PendingUtilityA1

Methods and devices for converting routing data from one protocol to another in a virtual private network

45
Priority: Sep 24, 2002Filed: Sep 24, 2002Published: Mar 25, 2004
Est. expirySep 24, 2022(expired)· nominal 20-yr term from priority
Inventors:Thomas P. ChuFrancis Robert MageeSteven Richman
H04L 45/00H04L 69/08H04L 69/085H04L 45/52H04L 12/4641
45
PatentIndex Score
0
Cited by
0
References
0
Claims

Abstract

Data (e.g., instructions) used to route Internet Protocol traffic is converted from one protocol to another (e.g., MPLS to Virtual Router) or vice-versa. This allows routers and other network devices based on either protocol to co-exist in the same network.

Claims

exact text as granted — not AI-modified
We claim:  
     
         1 .) A system for converting routing data in an Internet protocol based virtual private network (VPN), comprising: 
 a conversion section adapted to generate routing data in a first VPN protocol from routing data based on a second VPN protocol.    
     
     
         2 .) The system of  claim 1 , wherein the conversion section comprises a network controller.  
     
     
         3 .) The system of  claim 1 , wherein the conversion section comprises a router.  
     
     
         4 .) The system of  claim 1 , wherein the conversion section comprises a route reflector.  
     
     
         5 .) The system of  claim 1 , wherein the first VPN protocol comprises a Multi-Protocol Label Switching (MPLS)-based protocol and the second VPN protocol comprises a Virtual Router (VR)-based protocol.  
     
     
         6 .) The system of  claim 5 , wherein VR-based routing data comprises a combination of data selected from the group consisting of: a PE router Internet Protocol (IP) address; a customer site Identification (ID); a VR ID; a VPN customer ID; a local subnet address; a customer location subnet address; and an additional IP subnet address.  
     
     
         7 .) The system of  claim 5 , wherein the conversion section is further adapted to generate an MPLS-based NEXT HOP parameter based on a PE router IP address parameter.  
     
     
         8 .) The system of  claim 5 , wherein the conversion section is further adapted to generate an MPLS-based NLRI parameter based on a customer site ID parameter.  
     
     
         9 .) The system of  claim 5 , wherein the conversion section is further adapted to generate an MPLS-based route target (RT) parameter based on a VR ID parameter.  
     
     
         10 .) The system of  claim 1 , wherein the first VPN protocol comprises a VR-based protocol and the second VPN protocol comprises an MPLS-based protocol.  
     
     
         11 .) The system of  claim 10 , wherein MPLS-based data comprises a combination of data selected from the group consisting of: a NEXT HOP parameter; an NLRI field, an RT; and a route distinguisher.  
     
     
         12 .) The system of  claim 10 , wherein the conversion section is further adapted to generate a VR-based PE router IP address parameter based on a NEXT HOP parameter.  
     
     
         13 .) The system of  claim 10 , wherein the conversion section is further adapted to generate a VR-based customer site ID parameter based on a NLRI field.  
     
     
         14 .) The system of  claim 10 , wherein the conversion section is further adapted to generate a VR-based ID parameter based on a route target parameter.  
     
     
         15 .) The system of  claim 10 , wherein the conversion section is further adapted to generate a VR-based VPN customer ID parameter based on an RT parameter.  
     
     
         16 .) A method for converting routing data in an Internet protocol based virtual private VPN, comprising: 
 generating routing data in a first VPN protocol from routing data based on a second VPN protocol.    
     
     
         17 .) The method of  claim 16 , wherein the first VPN protocol comprises a MPLS-based protocol and the second VPN-based protocol comprises a VR-based protocol.  
     
     
         18 .) The method of  claim 17 , wherein VR-based routing data comprises a combination of data selected from the group consisting of: a PE router Internet Protocol (IP) address; a customer site Identification (ID); a VPN customer ID; a VR ID; a customer location subnet address; and an additional IP subnet address.  
     
     
         19 .) The method of  claim 17 , further comprising generating an MPLS-based NEXT HOP parameter based on a PE router IP address parameter.  
     
     
         20 .) The method of  claim 17  further comprising generating an MPLS-based NLRI parameter based on a customer site ID parameter.  
     
     
         21 .) The method of  claim 17 , further comprising generating an MPLS-based RT parameter based on a VR ID parameter.  
     
     
         22 .) The method of  claim 16 , wherein the first VPN protocol comprises a VR-based protocol and the second VPN protocol comprises an MPLS-based protocol.  
     
     
         23 .) The method of  claim 22 , wherein MPLS-based data comprises a combination of data selected from the group consisting of: a NEXT HOP parameter; an NLRI field, an RT; and a route distinguisher.  
     
     
         24 .) The method of  claim 22 , further comprising generating a VR-based PE router IP address parameter based on a NEXT HOP parameter.  
     
     
         25 .) The method of  claim 22 ,  4  further comprising generating a VR-based customer site ID parameter based on a NLRI field.  
     
     
         26 .) The method of  claim 22 , further comprising generating a VR-based ID parameter based on a route target parameter.  
     
     
         27 .) The method of  claim 22  further comprising generating a VR-based customer ID parameter based on an RT.

Join the waitlist — get patent alerts

Track US2004059829A1 — get alerts on status changes and closely related new filings.

We store only your email — no account needed. See our privacy policy.