Bridge routing module

Patent metadata

Field	Value
Publication number	US-9414070-B2
Application number	US-201414228598-A
Country	US
Kind code	B2
Filing date	Mar 28, 2014
Priority date	Nov 3, 2010
Publication date	Aug 9, 2016
Grant date	Aug 9, 2016

Abstract

A bridge routing module can be incorporated into a closed network fabric, such as a vehicular network. The bridge routing module includes an interface circuit to be coupled to other elements of the closed network fabric, for example other bridge routing modules or switch modules. The bridge routing module includes memory to store information associating packet content types with packet routing parameters, among other things. A processing module included in the bridge routing module analyzes packets to identify the type of content carried by the packets, and determines packet routing parameters based on the packet's content type. Ingress and egress of the packet are controlled in accordance with the packet routing parameters determined by the processing module.

First claim

What is claimed is:

1. A bridge-routing module comprising:
interface circuitry configured for communication within an intra-vehicular network;
packet ingress/egress circuitry configured to receive packets from and transmit packets to the interface circuitry;
memory; and
processing circuitry coupled to the packet ingress/egress circuitry and to the memory and configured to:
analyze a packet to identify a packet content type to determine whether the packet is a vehicle safety packet;
when the packet is a vehicle safety packet and the packet is received from a packet source, add an indication to a header of the packet to identify the packet as a vehicle safety packet;
determine a packet routing parameter based on the packet content type; and
control ingress/egress of the packet in accordance with the packet routing parameter.

2. The bridge-routing module of claim 1 , wherein the interface circuitry is configured for communication with at least one of a switch module and another bridge-routing module via the intra-vehicular network.

3. The bridge-routing module of claim 1 , the interface circuitry comprising:
a plurality of ports;
switching circuitry coupled to the plurality of ports; and
link management circuitry coupled to the processing circuitry and to the switching circuitry and configured to control the switching circuitry to select an active port of the plurality of ports.

4. The bridge-routing module of claim 3 , wherein the link management circuitry is further configured to:
deselect the active port when failing to meet performance criteria; and
control the switching circuitry to select a different port of the plurality of ports as the active port.

5. The bridge-routing module of claim 1 , wherein:
the packet ingress/egress circuitry comprises an ingress buffer configured to store packets received from the interface circuitry; and
the processing circuitry is further configured to control placement of packets in the ingress buffer based, at least in part, on priority of the packets.

6. The bridge-routing module of claim 1 , wherein:
the packet ingress/egress circuitry comprises a plurality of egress queues configured to store respective packet content types; and
the processing circuitry is further configured to:
control placement of packets in the plurality of egress queues based, at least in part, on a priority of the packets; and
select an egress queue from which a next packet is to be transmitted by the packet ingress/egress circuitry.

7. The bridge-routing module of claim 6 , further comprising bypass circuitry coupled to bypass the plurality of egress queues when delivering priority packets.

8. The bridge-routing module of claim 7 , wherein the processing circuitry is further configured to store a state of the egress queues prior to the bypass circuitry delivering the priority packets.

9. A method for intra-vehicular network communications comprising:
receiving a packet within an intra-vehicular network;
analyzing the packet to identify a packet content type to determine whether the packet is a vehicle safety packet;
when the packet is a vehicle safety packet and the packet is received from a packet source, adding an indication to a header of the packet to identify the packet as a vehicle safety packet;
determining a packet routing parameter based on the packet content type; and
controlling ingress/egress of the packet in accordance with the packet routing parameter.

10. The method of claim 9 , further comprising selecting an active port of a plurality of ports available for packet ingress/egress.

11. The method of claim 10 , further comprising:
deselecting the active port when failing to meet performance criteria; and
selecting a different port of the plurality of ports as the active port.

12. The method of claim 9 , further comprising:
storing packets in an ingress buffer; and
controlling placement of the packets in the ingress buffer based, at least in part, on priority of the packets.

13. The method of claim 9 , wherein:
controlling placement of packets in a plurality of egress queues based, at least in part, on a priority of the packets; and
selecting an egress queue from which a next packet is to be transmitted.

14. The method of claim 13 , further comprising bypassing the plurality of egress queues when delivering priority packets.

15. A bridge-routing module comprising:
interface circuitry configured for communication within an intra-vehicular network and including both a wired interface and a wireless interface;
packet ingress/egress circuitry configured to receive packets from and transmit packets to the interface circuitry;
memory; and
processing circuitry coupled to the packet ingress/egress circuitry and to the memory and configured to:
analyze a packet to identify a packet content type to determine whether the packet is a mission critical packet;
when the packet is a mission critical packet and the packet is received from a packet source, add an indication to a header of the packet to identify the packet as a mission critical packet;
determine a packet routing parameter based, at least in part, on the packet content type;
determine whether to use at least one of a wired link and a wireless link to communicate the packet via the interface circuit; and
control ingress/egress of the packet in accordance with the packet routing parameter via at least one of the wired link and the wireless link.

16. The bridge-routing module of claim 15 , wherein the interface circuitry is configured for communication with at least one of a switch module and another bridge-routing module via the intra-vehicular network.

17. The bridge-routing module of claim 15 , the interface circuitry comprising:
a plurality of ports;
switching circuitry coupled to the plurality of ports; and
link management circuitry coupled to the processing circuitry and to the switching circuitry and configured to control the switching circuitry to select an active port of the plurality of ports.

18. The bridge-routing module of claim 17 , wherein the link management circuitry is further configured to:
deselect the active port when failing to meet performance criteria; and
control the switching circuitry to select a different port of the plurality of ports as the active port.

19. The bridge-routing module of claim 17 , wherein:
the packet ingress/egress circuitry comprises an ingress buffer configured to store packets received from the interface circuitry; and
the processing circuitry is further configured to control placement of packets in the ingress buffer based, at least in part, on priority of the packets.

20. The bridge-routing module of claim 17 , wherein:
the packet ingress/egress circuitry comprises a plurality of egress queues configured to store respective packet content types; and
the processing circuitry is further configured to:
control placement of packets in the plurality of egress queues based, at least in part, on a priority of the packets; and
select an egress queue from which a next packet is to be transmitted by the packet ingress/egress circuitry.

Assignees

• Broadcom Corp

Inventors

• Yousefi Nariman
• Kim Yongbum
• Walley John
• Chen Sherman (Xuemin)
• Diab Wael W
• Ilyadis Nicholas

Classifications

• H04W4/44

  for communication between vehicles and infrastructures, e.g. vehicle-to-cloud [V2C] or vehicle-to-home [V2H] · CPC title

• G07C5/085

  using electronic data carriers · CPC title

• G07C5/008

  communicating information to a remotely located station (transmission systems for measured values G08C) · CPC title

• H04W4/46

  for vehicle-to-vehicle communication [V2V] · CPC title

• H04W72/541

  using the level of interference · CPC title