LOGICAL BRIDGING SYSTEM AND METHOD

• US 20080225853A1
• Filed: 02/13/2008
• Published: 09/18/2008
• Est. Priority Date: 02/14/2007
• Status: Active Grant

• Current Assignee: Marvell Israel Limited (Marvell Technology Group Limited)
• Original Assignee: Marvell International Limited (Marvell Technology Group Limited)
• Inventors: MELMAN, David, BShara, Nafea, ARAD, Nir
• Granted Patent: US 7,796,594 B2
• Time in Patent Office: Days
• US Class Current: 370/392
• CPC Class Codes: H04L 12/46 Interconnection of networks
• CPC Class Codes: H04L 12/4625 Single bridge functionality, e.g. connection of two networks over a single bridge
• CPC Class Codes: H04L 45/00 Routing or path finding of packets in data switching networks routing or path finding in wireless networks H04W40/00
• CPC Class Codes: H04L 45/04 Interdomain routing, e.g. hierarchical routing
• CPC Class Codes: H04L 45/08 Learning-based routing, e.g. using neural networks or artificial intelligence
• CPC Class Codes: H04L 45/60 Router architectures
• CPC Class Codes: H04L 49/109 Integrated on microchip, e.g. switch-on-chip
• CPC Class Codes: H04L 49/351 for local area network [LAN], e.g. Ethernet switches

Abstract

A system and method of extending a standard bridge to enable execution of logical bridging functionality are disclosed. In some implementations, a logical bridge may assign source logical port information to a data packet based on characteristics of the data packet, employ the source logical port information to learn the source address and to forward the data packet to a logical egress port, and map the logical egress port to a physical egress port at which the data packet is to be egressed. A tunnel interface may optionally be applied to a data packet upon egress.

Claims

1. A bridge for routing data packets on a network, the bridge comprising:

a physical ingress port to receive a data packet from the network;

a classification engine to assign source logical port information to the data packet based on characteristics of the data packet, wherein an assigned logical ingress port is decoupled from the physical ingress port;

a bridging engine downstream of the classification engine to learn the source logical port information and to forward the data packet to a logical egress port based on a destination address of the data packet; and

a logical port mapping engine to map the logical egress port to a physical egress port at which the data packet is to be egressed.

2. The bridge of claim 1 wherein the classification engine provides an indication of the source logical port information in a packet descriptor that is associated with the data packet.

3. The bridge of claim 2 wherein the bridging engine further employs the source logical port information to learn a source address of the data packet.

4. The bridge of claim 3 wherein the bridging engine learns the source address based on the packet descriptor.

5. The bridge of claim 1 wherein the logical port mapping engine applies a tunnel interface to the data packet.

6. The bridge of claim 1 wherein the source logical port information is related to header information associated with the data packet

7. The bridge of claim 1 wherein the source logical port information is related to a media access controller address.

8. The bridge of claim 1 wherein the source logical port information is related to a virtual local area network identifier.

9. The bridge of claim 1 wherein the physical egress port is an interface for a plurality of logical egress ports.

10. A pipeline for routing data packets on a network, the pipeline comprising:

a network bridge to receive data packets originating from a wireless network and from a wired network;

a classification engine to assign a source logical port to a data packet, wherein the assignment is independent of whether the data packet originated on the wireless network or on the wired network, and wherein the source logical port is decoupled from physical ports in the bridge; and

a bridging engine downstream of the classification engine to forward the data packet to a logical egress port, wherein the bridging engine makes a forwarding decision based upon the source logical port.

11. The pipeline of claim 10 further comprising a logical port mapping engine to map the logical egress port to a physical egress port at which the data packet is to be egressed.

12. The pipeline of claim 10 wherein the classification engine provides an indication of the source logical port in a packet descriptor that is associated with the data packet.

13. The pipeline of claim 12 wherein the bridging engine employs the source logical port to learn a source address of the data packet.

14. The pipeline of claim 13 wherein the bridging engine learns the source address based on the packet descriptor source logical port.

15. The pipeline of claim 11 wherein the logical port mapping engine applies a tunnel interface to the data packet.

16. The pipeline of claim 10 wherein the source logical port is related to a header information associated with the data packet.

17. The pipeline of claim 10 wherein the source logical port is related to a media access controller address.

18. The pipeline of claim 10 wherein the source logical port is related to a virtual local area network identifier.

19. The pipeline of claim 11 wherein the physical egress port is an interface for a plurality of logical egress ports.

20. The pipeline of claim 10 wherein the network bridge further comprises a received signal strength indicator (RSSI) collection module to extract RSSI information from the data packets originating from the wireless network.

21. The pipeline of claim 20 wherein the network bridge is operative to compute a weighted average of the RSSI information.

22. The pipeline of claim 20 wherein the network bridge is operative to apply a tunnel interface to the data packets originating from the wireless network.

23. A bridge for routing data packets in a network, the bridge comprising:

a plurality of physical ingress ports to receive data packets originating from a wireless network and from a wired network, wherein the bridge is in communication with one or more wireless access points;

a plurality of egress ports;

a bridging engine that directs a data packet from an ingress port where it is received to one or more selected egress ports; and

a received signal strength indicator (RSSI) collection module to extract RSSI information from the data packets originating from the wireless network.

24. The bridge of claim 23 further comprising a processing engine to compute a weighted average of the RSSI information.

25. The bridge of claim 23 wherein the bridging engine is operative to apply a tunnel interface to the data packets originating from the wireless network.

26. The bridge of claim 23 wherein the bridge is in communication with at least two wireless access points.

27. The bridge of claim 24 wherein a weight used in computing the weighted average is applied on a per wireless station basis.

28. The bridge of claim 24 further comprising a database of RSSI information and wherein a weighted RSSI average for each wireless user is stored in the database.

29. The bridge of claim 24 wherein the processing engine is configured to provide an alert when an RSSI value is below a threshold.

30. A method of routing data packets on a network, the method comprising:

receiving a data packet from the network at a physical ingress port of a switch;

assigning source logical port information to the data packet based on characteristics of the data packet;

employing the source logical port information to transport the data packet to a logical egress port based on a destination address of the data packet; and

mapping the logical egress port to a physical egress port at which the data packet is to be egressed from the switch.

31. The method of claim 30 wherein the assigning comprises providing an indication of a source logical port in a packet descriptor that is associated with the data packet.

32. The method of claim 31 further comprising employing the source logical port information to learn a source address of the data packet.

33. The method of claim 31 further comprising employing the packet descriptor to learn a source address of the data packet.

34. The method of claim 30 further comprising applying a tunnel interface to the data packet.

35. The method of claim 30 further comprising extracting received signal strength indicator (RSSI) information from data packets determined to have originated from a wireless network.

36. The method of claim 35 further comprising computing a weighted average of the RSSI information.