IP Library Granted Patent US 7,505,472
Granted Patent B1
US 7,505,472 · App. 10/600,192 · Granted Mar 17, 2009

Method and apparatus for agnostic PPP switching

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 7,505,472
App. No.
10/600,192
Granted
Mar 17, 2009
Kind
B1
Abstract

A method and apparatus for agnostic PPPoE switching is described. A method in a network element comprises converting Point to Point Protocol (PPP) protocol data units (PDUs) encapsulated according to different protocols into PPP PDUs with a uniform encapsulation, and transmitting the uniformly encapsulated PPP PDUs.

Claims (43)

1. A method in a network element comprising:

receiving link layer traffic encapsulated according to a link layer protocol at a link layer port;

demultiplexing the link layer traffic received via the link layer port into Point to Point Protocol over Ethernet (PPPoE) traffic, PPP over non-Ethernet (PPPoX) traffic, and non-PPP-traffic at a link layer demultiplexer;

forwarding non-PPP traffic received from the link layer demultiplexer using a virtual router coupled with the link layer demultiplexer;

converting PPPoX traffic received from the link layer demultiplexer into PPPoE traffic and converting PPPoE traffic received from a PPPoE multiplexer/demultiplexer into PPPoX traffic using a PPPoX proxy module;

switching PPPoE traffic received from the link layer demultiplexer and from the PPPoE multiplexer/demultiplexer using a PPPoE switch module; and

multiplexing PPPoE traffic received from the PPPoE switch module and the PPPoX proxy module using the PPPoE multiplexer/demultiplexer coupled with the PPPoX proxy module and the PPPoE switch module; and

demultiplexing PPPoE traffic into different traffic flows according to their session identifier using the PPPoE multiplexer/demultiplexer.

2. A network element comprising:

a link layer port to receive link layer traffic encapsulated according to a link layer protocol;

a link layer demultiplexer to demultiplex link layer traffic received via the link layer port into Point to Point Protocol over Ethernet (PPPoE) traffic, PPP over non-Ethernet (PPPoX) traffic, and non-PPP traffic;

a virtual router coupled with the link layer demultiplexer, to forward non-PPP traffic received from the link layer demultiplexer;

a Point to Point Protocol (PPP) switch module having,

a PPPoX proxy module to convert PPPoX traffic received from the link layer demultiplexer into PPPoE traffic and to convert PPPoE traffic received from a PPPoE multiplexer/demultiplexer into PPPoX traffic;

a PPPoE switch module to switch PPPoE traffic received from the link layer demultiplexer and from the PPPoE multiplexer/demultiplexer; and

the PPPoE multiplexer/demultiplexer coupled with the PPPoX proxy module and the PPPoE switch module, the PPPoE multiplexer/demultiplexer to multiplex PPPoE traffic received from the PPPoE switch module and the PPPoX proxy module and to demultiplex PPPoE traffic into different traffic flows according to their session identifier.

3. A machine readable storage medium storing machine executable instructions, which when executed by a set of one or more processors, cause said set of processors to perform operations in a network element comprising:

receiving link layer traffic encapsulated according to a link layer protocol at a link layer port;

demultiplexing the link layer traffic received via the link layer port into Point to Point Protocol over Ethernet (PPPoE) traffic, PPP over non-Ethernet (PPPoX) traffic, and non-PPP-traffic at a link layer demultiplexer;

forwarding non-PPP traffic received from the link layer demultiplexer using a virtual router coupled with the link layer demultiplexer;

converting PPPoX traffic received from the link layer demultiplexer into PPPoE traffic and converting PPPoE traffic received from a PPPoE multiplexer/demultiplexer into PPPoX traffic using a PPPoX proxy module;

switching PPPoE traffic received from the link layer demultiplexer and from the PPPoE multiplexer/demultiplexer using a PPPoE switch module; and

multiplexing PPPoE traffic received from the PPPoE switch module and the PPPoX proxy module using the PPPoE multiplexer/demultiplexer coupled with the PPPoX proxy module and the PPPoE switch module; and

demultiplexing PPPoE traffic into different traffic flows according to their session identifier using the PPPoE multiplexer/demultiplexer.

4. The method of claim 1 , wherein the converting is performed by matching an entry in a data structure that provides a PPPoE session identifier for each PPP PDU to be converted.

5. The method of claim 4 , wherein the data structure is not created until a proxy module within the network element attempts to create an entry in the data structure.

6. The method of claim 4 , wherein the data structure is modified to indicate that a subscriber side flow is active once a PPP session is opened.

7. The method of claim 1 , further comprising:

receiving PPP PDUs with the uniform encapsulation at a set of one or more aggregator side ports; and

converting the PPP PDUs with the uniform encapsulation back into PPP PDUs encapsulated according to different protocols.

8. The method as in claim 1 , wherein the network element is agnostic of the encapsulation of the PPP PDUs to be converted.

9. The network element of claim 2 , wherein the PPPoX proxy module is to convert the PPPoX traffic by matching an entry in a data structure that provides a PPPoE session identifier for the PPPoX traffic to be converted.

10. The network element of claim 9 , wherein the data structure is not created until the PPPoX proxy module attempts to create an entry in the data structure.

11. The network element of claim 9 , wherein the data structure is modified to indicate that the PPPoX traffic is active once a PPP session is opened.

12. The network element as in claim 2 , wherein the network element is agnostic of the encapsulation of the PPPoX traffic received at the link layer port.

13. The machine storage medium of claim 3 , wherein the uniform encapsulation is PPPoE encapsulation.

14. The machine storage medium of claim 3 , wherein the converting is performed by matching an entry in a data structure that provides a PPPoE session identifier for each PPP PDU to be converted.

15. The machine storage medium of claim 14 , wherein the data structure is not created until a proxy module within the network element attempts to create an entry in the data structure.

16. The machine storage medium of claim 14 , wherein the data structure is modified to indicate that a subscriber side flow is active once a PPP session is opened.

17. The machine storage medium of claim 3 that provides instructions, which when executed by a set of one or more processors, cause said set of processors to perform operations further comprising:

receiving PPP PDUs with the uniform encapsulation at a set of one or more aggregator side ports; and

converting the PPP PDUs with the uniform encapsulation back into PPP PDUs encapsulated according to different protocols.

18. The machine storage medium of claim 3 , wherein the network element is agnostic of the encapsulation of the PPP PDUs to be converted.

Assignments (3)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Feb 26, 2010
From: REDBACK NETWORKS INC.
To: ERICSSON AB
Reel/Frame 024002/0363 →
SECURITY AGREEMENT Recorded Apr 7, 2004
From: REDBACK NETWORKS INC.
To: SILICON VALLEY BANK
Reel/Frame 014499/0957 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 8, 2003
From: HOF, ONNO MARK BECKER; OUISSAL, SAID
To: REDBACK NETWORKS INC.
Reel/Frame 014578/0793 →