Uniting FDB lookups for encapsulated packets
View Patent ↗A method of communications at an encapsulating bridge includes receiving a packet having an unencapsulated-DA (destination address) and an associated encapsulation identifier. The unencapsulated-DA and the associated encapsulation identifier are used to determine a TxPort-unencapsulated network (unencapsulated network side transmit port) or an encapsulated-DA for the packet. This method reduces latency of processing by reducing lookups, thereby also increasing transmission bandwidth of the communications network. The invention also facilitates embodiments with reduced memory and processing requirements, as compared to conventional implementations. This method is particularly useful for MAC-in-MAC encapsulation.
1. A method of communications at an encapsulating bridge comprising the steps of:
(a) receiving a packet having an unencapsulated-DA (destination address) and an associated unencapsulated virtual network identifier (service virtual local area network identifier);
(b) providing, based on said associated unencapsulated virtual network identifier, an associated encapsulation identifier; and
(c) determining, based on said unencapsulated-DA and said associated encapsulation identifier:
1) a B-DA (backbone destination address), and 2) a TxPort-PNP (provider network port [PNP] side transmit port), for said packet,
wherein said determining is done at least in part via less than two lookups to a FDB (forwarding/filtering database).
2. The method of claim 1 wherein said packet is received from an unencapsulated network port and the encapsulating bridge is on an encapsulated network.
3. The method of claim 1 further including determining an encapsulated virtual network identifier from said unencapsulated virtual network identifier.
4. The method of claim 1 further comprising the step of:
(c) learning, based on an unencapsulated source address of said packet and said associated encapsulation identifier, an RxPort-unencapsulated network (unencapsulated network port side receive port) for said packet.
5. The method of claim 1 wherein said receiving is done at an I-Comp (service instance [I] component).
6. The method of claim 1 wherein:
(a) the encapsulating bridge is a BEB (backbone edge bridge);
(b) said unencapsulated-DA is a C-DA (customer destination address);
(c) said associated encapsulation identifier is an I-SID (backbone service instance identifier);
(d) said unencapsulated virtual network identifier being an S-VID (service virtual local area network [VLAN] identifier);
(e) said packet is received from an unencapsulated network port being a CNP (customer network port);
(f) the encapsulating bridge is on an encapsulated network being a PBBN (provider backbone bridged network);
(g) said packet has an encapsulated virtual network identifier being a B-VID (backbone VLAN identifier);
(h) said packet has an unencapsulated source address being a C-SA (customer source address);
(i) said packet has an RxPort-unencapsulated network being an RxPort-CNP (customer network port [CNP] side receive port); and
(j) encapsulation is MAC-in-MAC encapsulation.
7. A system for communications comprising:
(a) a processing system on an encapsulating bridge, said processing system containing a non-transitory computer-readable storage medium bearing computer-readable code for implementing:
(i) receiving a packet having a unencapsulated-DA and an associated unencapsulated virtual network identifier (service virtual local area network identifier);
(ii) providing, based on said associated unencapsulated virtual network identifier, an associated encapsulation identifier; and
(iii) determining, based on said unencapsulated-DA and said associated encapsulation identifier:
1) a B-DA (backbone destination address), and 2) a TxPort-PNP (provider network port [PNP] side transmit port), for said packet,
(b) a FDB (forwarding/filtering database) processing module,
wherein said computer-readable code implements said determining at least in part via less than two lookups to said FDB.
8. The system of claim 7 wherein said packet is received from an unencapsulated network port and said processing system is part of an encapsulating bridge on an encapsulated network.
9. The system of claim 7 wherein said processing system is further configured to: determining an encapsulated virtual network identifier from said unencapsulated virtual network identifier.
10. The system of claim 7 further configured to:
(iii) learn, based on an unencapsulated source address of said packet and said associated encapsulation identifier, an RxPort-unencapsulated network for said packet.
11. The system of claim 7 wherein at least a portion of said processing system is configured on an I-Comp of said encapsulating bridge.