IP Library Granted Patent US 9,124,567
Granted Patent B2
US 9,124,567 · App. 13/342,637 · Granted Sep 1, 2015

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

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 9,124,567
App. No.
13/342,637
Granted
Sep 1, 2015
Kind
B2
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 (15)

1. A system for converting data in an Internet protocol based virtual private network (VPN), comprising:

a conversion section adapted to generate data based on a first VPN forwarding protocol, where the first VPN forwarding protocol is a Multi-Protocol Label Switching (MPLS)-based protocol that comprises MPLS-based data or a Virtual Router (VR)-based protocol that comprises VR-based data from data based on a second VPN forwarding protocol, where the second VPN forwarding protocol is a VR-based protocol or a MPLS-based protocol, respectively,

wherein VR-based data comprises a provider edge (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 and MPLS-based data comprises a NEXT HOP parameter, a Network Layer Reachability Information (NLRI) field, a route target (RT) and a route distinguisher, and

wherein the conversion section is adapted to:

generate an MPLS-based NEXT HOP parameter based on a PE router IP address parameter, generate an MPLS label parameter based on a customer site ID parameter, generate an MPLS-based NLRI parameter based on a customer location IP subnet address parameter, and generate an MPLS-based RT parameter based on a VR ID parameter, and

generate a VR protocol PE router IP address parameter based on an MPLS-based NEXT HOP parameter, generate a VR protocol customer site ID parameter based on an MPLS label, generate a VR ID parameter and a VPN ID based on an RT lookup table or by decomposing an RT field into VR and VPN customer subfields, and generate a customer location local IP subnet address based on an NLRI field.

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. A method for converting data in an Internet protocol based virtual private VPN using a conversion section, comprising:

generating data based on a first VPN forwarding protocol, where the first VPN forwarding protocol is a Multi-Protocol Label Switching (MPLS)-based protocol that comprises MPLS-based data or a Virtual Router (VR)-based protocol that comprises VR-based data from data based on a second VPN forwarding protocol, where the second VPN forwarding protocol is a VR-based protocol or a MPLS-based protocol, respectively,

wherein VR-based data comprises a provider edge (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 and MPLS-based data comprises a NEXT HOP parameter, a Network Layer Reachability Information (NLRI) field, a route target (RT) and a route distinguisher, and

wherein generating data based on the first VPN forwarding protocol comprises:

generating an MPLS-based NEXT HOP parameter based on a PE router IP address parameter, generating an MPLS label parameter based on a customer site ID parameter, generating an MPLS-based NLRI parameter based on a customer location IP subnet address parameter, and generating an MPLS-based RT parameter based on a VR ID parameter, and

generating a VR protocol PE router IP address parameter based on an MPLS-based NEXT HOP parameter, generating a VR protocol customer site ID parameter based on an MPLS label, generating a VR ID parameter and a VPN ID based on an RT lookup table or by decomposing an RT field into VR and VPN customer subfields, and generating a customer location local IP subnet address based on an NLRI field.

Assignments (9)
RELEASE OF SECURITY INTEREST Recorded Jun 3, 2021
From: TERRIER SSC, LLC
To: WSOU INVESTMENTS, LLC
Reel/Frame 056526/0093 →
SECURITY INTEREST Recorded Jun 1, 2021
From: WSOU INVESTMENTS, LLC
To: OT WSOU TERRIER HOLDINGS, LLC
Reel/Frame 056990/0081 →
RELEASE OF SECURITY INTEREST Recorded May 21, 2019
From: OCO OPPORTUNITIES MASTER FUND, L.P. (F/K/A OMEGA CREDIT OPPORTUNITIES MASTER FUND LP
To: WSOU INVESTMENTS, LLC
Reel/Frame 049246/0405 →
SECURITY INTEREST Recorded May 20, 2019
From: WSOU INVESTMENTS, LLC
To: BP FUNDING TRUST, SERIES SPL-VI
Reel/Frame 049235/0068 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 25, 2017
From: ALCATEL LUCENT
To: WSOU INVESTMENTS, LLC
Reel/Frame 044000/0053 →
SECURITY INTEREST Recorded Sep 21, 2017
From: WSOU INVESTMENTS, LLC
To: OMEGA CREDIT OPPORTUNITIES MASTER FUND, LP
Reel/Frame 043966/0574 →
RELEASE OF SECURITY INTEREST Recorded Oct 9, 2014
From: CREDIT SUISSE AG
To: ALCATEL-LUCENT USA INC.
Reel/Frame 033949/0016 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Apr 16, 2014
From: ALCATEL-LUCENT USA INC.
To: ALCATEL LUCENT
Reel/Frame 032685/0837 →
SECURITY INTEREST Recorded Mar 7, 2013
From: ALCATEL-LUCENT USA INC.
To: CREDIT SUISSE AG
Reel/Frame 030510/0627 →