Differential forwarding in address-based carrier networks
View Patent ↗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.
1. A method of identifying data packets to be transported through a connection in an Ethernet-based carrier network providing communications services to customers, the method comprising the steps of:
storing association data associating:
a service instance identifier;
a customer attachment interface terminating a customer service, and
a connection in the network, the connection being defined by a combination of a MAC address and a Virtual Local Area Network (VLAN) identifier; and
using the association data to identify data packets corresponding to the customer service as being for transport through the connection.
2. A method according to claim 1 , wherein the step of identifying data packets as corresponding to the customer service comprises receiving the data packets at a port of a switch of the network, the port being associated with the customer attachment interface.
3. A method according to claim 1 , comprising:
forwarding the data packets over the connection.
4. A method according to claim 3 , comprising:
encapsulating the data packets with the service instance identifier, the MAC address and the VLAN identifier prior to forwarding the data packets over the connection.
5. A method according to claim 3 , comprising
applying the service instance identifier, the MAC address and the VLAN identifier to the data packets prior to forwarding the data packets over at least part of the connection.
6. A method according to claim 1 , wherein the association data comprises an association between a specific physical customer-facing port of a switch of the network, an encapsulation function and the connection.
7. A method according to claim 1 , wherein the association data comprises an association between a specific physical customer-facing port, a customer VLAN tag, an encapsulation function, a policer set to identify an acceptable quantity of traffic and the connection.
8. A method according to claim 1 , wherein the association data comprises a filter established by a layer 3-layer 7 switch identifying a SIP-signalled VolP flow to identify all of the packets of the flow and the connection.
9. A method according to claim 1 , wherein the association data comprises an association between an encapsulation function, a port of a virtual customer-address-space Ethernet switch instance and the connection.
10. A method according to claim 1 , wherein the association data comprises an association between a physical port of a node of the network, a VLAN tag application function at that node and the connection.
11. A method according to claim 1 , wherein the data packets are ones selected from the group consisting of: MAC frames transported over MAC frames and Pseudo-Wire frames transported over MAC frames.
12. A method according to claim 1 , wherein broadcast on unknown destination address functionality is disabled on Ethernet switches of the network.
13. A method according to claim 1 , wherein broadcast on unknown destination address functionality is rate limited on Ethernet switches of the network.
14. A method according to claim 1 , wherein the network is at least partially meshed.
15. A method according to claim 1 , wherein the customer attachment interface is identified using a service instance identifier.
16. A node for use in an Ethernet-based carrier network providing communications services to customers and arranged to identify data packets to be transported through a connection in the network, the node comprising:
a data store storing association data associating:
a service instance identifier;
a customer attachment interface terminating a customer service, and
a connection in the network, the connection being defined by a combination of a MAC address and a Virtual Local Area Network (VLAN) identifier; and
at least one processor arranged to identify data packets corresponding to the customer service as being for transport through the connection using the association data.
17. A node according to claim 16 , wherein the at least one processor arranged to identify packets as corresponding to the customer service is arranged to identify the packets on the basis of the data packets being received at a port of a switch of the network, the port being associated with the customer attachment interface.
18. A node according to claim 16 , wherein the association data comprises an association between a specific physical customer-facing port of a switch of the network, an encapsulation function and the connection.
19. A node according to claim 16 , wherein the association data comprises an association between a specific physical customer-facing port, a customer VLAN tag, an encapsulation function, a policer set to identify an acceptable quantity of traffic and the connection.
20. A node according to claim 16 , wherein the association data comprises a filter established by a layer 3-layer 7 switch identifying a SIP-signalled VoIP flow to identify all of the packets of the flow and the connection.
21. A node according to claim 16 , wherein the association data comprises an association between an encapsulation function, a port of a virtual customer-address-space Ethernet switch instance and the connection.
22. A node according to claim 16 , wherein the association data comprises an association between a physical port of a node of the network, a VLAN tag application function at that node and the connection.
23. A node according to claim 16 , the node being an Ethernet switch of the network having a port associated with the customer attachment interface.
24. A node according to claim 23 comprising:
an output for forwarding the data packets over the connection.
25. A node according to claim 24 wherein the at least one processor is arranged to apply the service instance identifier, the MAC address and the VLAN identifier to the data packets prior to forwarding the data packets over the connection.
26. A node according to claim 24 , wherein the at least one processor is arranged to encapsulate the data packets with the service instance identifier, the MAC address and the VLAN identifier prior to their being forwarded over the connection.
27. A method according to claim 1 , wherein the MAC address is a destination address.
28. A method according to claim 1 , wherein the MAC address is a source address.
29. A node according to claim 16 , wherein the MAC address is a destination address.
30. A node according to claim 16 , wherein the MAC address is a source address.
31. A node according to claim 16 , wherein the data packets are ones selectedfrom the group consisting of: MAC frames transported over MAC frames and Pseudo-Wire frames transported over MAC frames.
32. A node according to claim 16 , wherein broadcast on unknown destination address functionality is disabled on Ethernet switches of the network.
33. A node according to claim 16 , wherein broadcast on unknown destination address functionality is rate limited on Ethernet switches of the network.
34. A node according to claim 16 , wherein the network is at least partially meshed.
35. A node according to claim 16 , wherein the customer attachment interface is identified using a service instance identifier.