Differential forwarding in address-based carrier networks

• US 9,356,862 B2
• Filed: 09/05/2014
• Issued: 05/31/2016
• Est. Priority Date: 04/06/2004
• Status: Expired due to Fees

• Current Assignee: RPX Clearinghouse LLC (RPX Corporation)
• Original Assignee: RPX Clearinghouse LLC (RPX Corporation)
• Inventors: Friskney, Robert, Bragg, Nigel, Parry, Simon, Ashwood-Smith, Peter, Allan, David, Brueckheimer, Simon
• Primary Examiner(s): Lee, Andrew
• Application Number:
  US14/478,001
• Publication Number:
  US 20150016262A1
• Time in Patent Office: 634 Days
• US Class Current: 1/1
• CPC Class Codes: H04L 12/4641 Virtual LANs, VLANs, e.g. virtual private networks [VPN] LAN interconnection over a bridge based backbone H04L12/462; encapsulation techniques H04L12/4633; routing of packets H04L45/00; packet switches H04L49/00; virtual private networks for security H04L63/0272
• CPC Class Codes: H04L 12/4645 Details on frame tagging routing of packets H04L45/00; support for virtual LAN H04L49/354
• CPC Class Codes: H04L 45/54 Organization of routing tables
• CPC Class Codes: H04L 45/64 using an overlay routing layer
• CPC Class Codes: H04L 45/66 Layer 2 routing, e.g. in Ethernet based MAN's
• CPC Class Codes: H04L 45/74 Address processing for routing
• CPC Class Codes: H04L 47/122 by diverting traffic away from congested entities
• CPC Class Codes: H04L 49/205 Quality of Service based
• CPC Class Codes: H04L 49/253 using establishment or release of connections between ports
• CPC Class Codes: H04L 49/254 Centralised controller, i.e. arbitration or scheduling
• CPC Class Codes: H04L 49/351 for local area network [LAN], e.g. Ethernet switches
• CPC Class Codes: H04L 49/354 for supporting virtual local area networks [VLAN]

Abstract

The invention relates to enabling differential forwarding in address-based carrier networks such as Ethernet networks. There is described a method of and connection controller for establishing connections (76, 77) in a frame-based communications network comprising nodes (71-75 and 78) such as Ethernet switches. The connections are established by configuring, in various of the nodes, mappings for forwarding data frames, such as Ethernet frames. The mappings are from a combination of a) a destination (or source) address corresponding to a destination (or source) node (73) of the connection and b) an identifier, such as a VLAN tag. The mappings are to selected output ports of the various nodes. By using the combination of destination (or source) address AND identifier, the mappings enable data frames belonging to different connections (76, 77) to be forwarded differentially (ie forwarded on different output ports) at a node (75) despite the different connections having the same destination node. This enables flexibility in routing connections and the ability to perform traffic engineering.

Claims

1. A carrier Ethernet network configured for providing a Virtual Private LAN Service (VPLS), the carrier Ethernet network comprising:

a first node configured;

to receive a frame from a customer, the frame having a first customer MAC address as a customer source MAC address and a second customer MAC address as a customer destination MAC address;

to encapsulate the frame for transport across the carrier Ethernet network with a VLAN identifier, an encapsulating source MAC address and an encapsulating destination MAC address, the encapsulating source MAC address being a MAC address of the first node; and

to forward the encapsulated frame across the carrier Ethernet network based on the combination of the VLAN identifier and the encapsulating destination MAC address; and

a second node configured;

to receive the encapsulated frame;

to configure a mapping between the customer source MAC address of the frame and the MAC address of the first node, the MAC address of the first node being learned from the encapsulating source MAC address of the frame; and

to forward the frame to the customer based on the customer destination MAC address.

2. The network of claim 1, wherein:

the first node is configured;

to store association data associating a service instance identifier, a customer attachment interface terminating a customer service and a combination of a VLAN identifier and the encapsulating destination MAC address; and

to further encapsulate the frame for transport across the carrier Ethernet network by including the service instance identifier in the encapsulated frame; and

the second node is configured to forward the frame to the customer identified by the service instance identifier in the encapsulated frame.

3. The network of claim 2, configured to associate a first service instance identifier with a first customer and a second service instance identifier with a second customer, wherein:

the first node is configured;

to encapsulate a first frame from a first customer attachment interface associated with the first customer with a VLAN identifier, an encapsulating destination MAC address and the first service instance identifier;

to encapsulate a second frame from a second customer attachment interface associated with the second customer with the VLAN identifier, the encapsulating destination MAC address and the second service instance identifier; and

to forward the encapsulated first and second frames across the carrier Ethernet network based on the combination of the VLAN identifier and the encapsulating destination MAC address; and

the second node is configured;

to receive and decapsulate the encapsulated first and second frames; and

to forward the decapsulated first and second frames to the first and second customers respectively based on the first and second service instance identifiers received in the encapsulated first and second frames respectively.

4. The network of claim 1, wherein the second node is configured:

to receive a frame from the customer, the frame having the first customer MAC address as a customer destination MAC address; and

to use the mapping between the first customer MAC address and the MAC address of the first node and the VLAN identifier to encapsulate the frame for transport across the carrier Ethernet network with the VLAN identifier, an encapsulating source MAC address and an encapsulating destination MAC address, the encapsulating source MAC address being the MAC address of the second node.

5. The network of claim 4, wherein the mapping between the customer source MAC address of the frame and the MAC address of the first node comprises a mapping between the customer source MAC address of the frame and a combination of the MAC address of the first node and the VLAN identifier.

6. The network of claim 1, further configured to establish a connection through the carrier Ethernet network by, without Ethernet unknown destination address forwarding and source address learning:

determining a path for the connection through the Ethernet carrier network;

selecting a VLAN for association with the connection, the VLAN having a VLAN identifier;

selecting an encapsulating MAC address for association with the connection; and

configuring, in at least one intermediate node along the connection, a respective mapping for use by the intermediate node in forwarding data frames carrying the VLAN identifier of the selected VLAN and the selected encapsulating MAC address as a destination address, each respective mapping associating a combination comprising the selected encapsulating MAC address and the VLAN identifier with a selected output port of the intermediate node;

wherein forwarding the encapsulated frame based on the combination of the VLAN identifier and the encapsulating MAC address comprises forwarding the frame on the established connection.

7. The network of claim 1, wherein the mapping between the customer source MAC address of the frame and the MAC address of the first node comprises a mapping between the customer source MAC address of the frame and a combination of the MAC address of the first node and the VLAN identifier.

8. A carrier Ethernet network configured for forwarding customer data frames, the network comprising:

at least one connection controller configured to establish a connection through the carrier Ethernet network by, without Ethernet unknown destination address forwarding and source address learning;

determining a path for the connection through the Ethernet carrier network;

selecting a VLAN for association with the connection, the VLAN having a VLAN identifier;

selecting an Ethernet MAC address for association with the connection; and

forwarding packets associated with the selected VLAN and the selected Ethernet MAC address at nodes on the path based on the combination of the VLAN identifier and the Ethernet MAC address without changing the VLAN identifier; and

a node identified by the Ethernet MAC address selected for a particular connection configured;

to receive a customer data frame over the particular connection, the customer data frame having a particular customer source address;

in response to receipt of the customer data frame, to configure a mapping between the particular customer source address and a source Ethernet MAC address of the received frame;

to receive further customer data frames at the node, the further customer data frames having a customer destination address equal to the particular customer source address; and

to forward the further customer data frames over a connection associated with the Ethernet MAC address to which the customer destination address is mapped by the mapping.

9. The network of claim 8, configured:

to associate at least one respective service instance identifier with each of a plurality of customers;

to associate one of the respective service instance identifiers with each data frame associated with a customer;

to forward customer data frames associated with different customers over the particular connection based on the VLAN identifier and the Ethernet MAC address of the particular connection; and

at the node identified by the Ethernet MAC address, to forward the customer data frames to appropriate customers based on the respective service instance identifiers in each data frame.

10. The network of claim 9, wherein the plurality of connections comprises establishing a mesh of connections in the carrier Ethernet network.

11. The network of claim 9, configured:

to configure mappings of customer destination addresses to respective connections at nodes of the carrier Ethernet network; and

to forward customer data frames over respective connections determined based on the mappings.

12. The network of claim 8, configured to establish a plurality of connections by establishing at least one hub and spoke pattern of connections in which multiple spoke nodes have connections to a hub node.

13. The network of claim 12, having:

mappings configured at the spoke nodes to establish respective connections between the spoke nodes and the hub node to enable the spoke nodes to forward customer data frames from the spoke nodes over the respective connections to the hub node based on the mappings; and

mappings configured at the hub node to establish respective connections to the spoke nodes to enable the hub node to forward customer data frames from the hub node to respective spoke nodes based on the mappings.

14. The network of claim 13, configured:

to forward customer data frames from a respective ingress spoke node to the hub node based on mappings configured at the ingress spoke node; and

to forward customer data frames from the hub node to a respective egress spoke node based on mappings configured at the hub node.

15. The network of claim 8, configured to implement a virtual private LAN service (VPLS).

16. The network of claim 8, configured:

to reserve a first plurality of VLANs for use in establishing a plurality of connections through the carrier Ethernet network without Ethernet unknown destination address forwarding and source address learning; and

to reserve a second plurality of VLANs for use in Ethernet forwarding using conventional Ethernet unknown destination address forwarding and source address learning, the second plurality being distinct from the first plurality.

17. The network of claim 16, configured to disable broadcast-on-unknown-destination-address and Ethernet source-address-learning functionality for data frames associated with the first plurality of VLANs but not for data frames associated with the second plurality of VLANs.

18. The network of claim 17, wherein the first plurality of VLANs is configured with a higher forwarding priority than the second plurality of VLANs.

19. The network of claim 16, configured to communicate control plane metrics from the first plurality of VLANs to the second plurality of VLANs.

20. The network of claim 19, wherein spanning trees of the second plurality of VLANs are configured to avoid links heavily loaded by the first plurality of VLANs.