Enhanced multicast forwarding cache (eMFC)

• US 20050175009A1
• Filed: 02/08/2005
• Published: 08/11/2005
• Est. Priority Date: 02/09/2004
• Status: Abandoned Application

• Current Assignee: Fred Bauer
• Original Assignee: Fred Bauer
• Inventors: Bauer, Fred
• Application Number:
  US11/054,034
• Publication Number:
  US 20050175009A1
• Time in Patent Office: Days
• US Class Current: 370/390
• CPC Class Codes: H04L 12/2854 Wide area networks, e.g. public data networks
• CPC Class Codes: H04L 63/04 for providing a confidential data exchange among entities communicating through data packet networks
• CPC Class Codes: H04L 63/08 for authentication of entities cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32

Abstract

An Enhanced Multicast Forwarding Cache (eMFC) supports multicast transmissions in mobile mesh networks. The enhanced MFC is designed to support mesh node mobility, quality of service, and security requirements that are particular to mesh networks. To achieve these goals, the enhanced MFC draws from a global state maintained by a unicast routing protocol, multicast aware applications, and distributed services. The eMFC distributes this derived global state through the use of an eMFC-specific multicast packet header. Information contained within the eMFC header is also used to collect and derive multicast traffic statistics at each mesh node. To maintain backwards compatibility, multicast traffic without the eMFC-specific header is also honored by the MFC. Mobile mesh network specific interfaces, such as radio interfaces, as well as conventional interface types are supported. Security is maintained through the use of authentication and encryption techniques.

Claims

1. A node operating in a mesh network, comprising:

a processor operating an enhanced multicast forwarding protocol that provides a Multicast Forwarding Header (MFH) for multicast packets transmitted over the mesh network, the MFH including a device identifier for a sending node and being independent of any Internet Protocol (IP) address associated with the sending node and further including a multicast group identifier identifying nodes in the mesh network associated with a same multicast group.

2. The node according to claim 1 wherein the processor:

uses the multicast group identifier to identify multicast groups for the received packets;

uses the identified multicast groups and the source identifier to identify which nodes in the identified multicast groups need to be forwarded the received multicast packets; and

forwards the multicast packets to the identified nodes.

3. The node according to claim 1 including a sequence number in the MFH used by the processor in combination with the device identifier and the multicast group identifier to identify and drop duplicate multicast packets that have been transmitted by the processor and then received back from another node in the mesh network.

4. The node according to claim 1 wherein the processor identifies downstream nodes in the mesh network and sends the multicast packets to the identified downstream nodes even when the downstream nodes are not identified nodes in the multicast group.

5. The node according to claim 1 including a traffic category in the MFH that identifies different traffic categories for the multicast packets.

6. The node according to claim 5 including a priority table that is used in combination with the traffic category in the MFH to prioritize the processing of the multicast packets.

7. The node according to claim 6 wherein the processor prioritizes the multicast packets according to the traffic category, priority table, device identifier, multicast group identifier and a sequence number in the MFH.

8. The node according to claim 7 wherein the priority table and a multicast routing table used by the processor for prioritizing multicast packet processing are automatically distributed to the node.

9. The node according to claim 8 wherein the processor maintains packet processing metrics for the multicast packets according to the traffic category.

10. An ad-hoc mesh network, comprising:

multiple mobile nodes that conduct logical point-to-point wireless communications with their neighbors within the mesh network and further provide hops for forwarding messages between other nodes in the mesh network, the nodes providing a mesh multicast protocol that forwards multicast packets between different nodes according to both a mesh network routing table and a mesh based multicast header in the multicast packets.

11. The network according to claim 10 including a device identifier in the multicast header associated with a particular device sending the multicast packets that does not change when the device moves to different locations in and out of the mesh network.

12. The network according to claim 11 including a source router ID, multicast destination address and port address in the multicast header that identifies nodes in the mesh network that are members of a same multicast group.

13. The network according to claim 11 including a sequence number in the multicast header used in combination with the device identifier to identify duplicate multicast packets sent from and returned back to the same node.

14. The network according to claim 10 including a traffic category in the multicast header used by the nodes to prioritize the processing and forwarding of packets to other nodes in the mesh network.

15. The network according to claim 14 including a priority table and a multicast routing table that are automatically distributed to the different nodes in the mesh network that are used in combination with a device identifier, a sequence number, a multicast group address and the traffic category in the multicast header to prioritize the processing and forwarding of the multicast packets.

16. A method for distributing multicast packets in the ad-hoc mesh network, comprising:

using a Multicast Forwarding Cache (MFC) to identify mobile nodes in the mesh network that require forwarding of wirelessly received multicast packets;

receiving multicast packets that contain a multicast header that is adapted for multicast operations in the mesh network; and

using the MFC in combination with the multicast header to forward the multicast packets to other nodes in the mesh network.

17. The method according to claim 16 including selectively dropping received duplicate multicast packets according to a device identifier, sequence number, and multicast group identifier in the multicast header.

18. The method according to claim 17 including:

using the multicast header to identify a multicast group associated with a received multicast packet; and

repeating the multicast packet to any nodes in or out of the multicast group that are associated with a downstream mesh interface in the mesh network.

19. The method according to claim 16 including receiving multicast packets from nodes in the mesh network and prioritizing the processing and forwarding of the multicast packets according to a traffic category identified in the multicast header.

20. The method according to claim 19 including maintaining processing metrics on the multicast packets according to the identified traffic category.