Role based multicast messaging infrastructure

• US 9,203,690 B2
• Filed: 03/14/2013
• Issued: 12/01/2015
• Est. Priority Date: 09/24/2012
• Status: Active Grant

• Current Assignee: Avago Technologies International Sales Pte Limited (Broadcom, Inc.)
• Original Assignee: Brocade Communications Systems, Inc. (Broadcom, Inc.)
• Inventors: Chin, Bill Ying, Retter, Dan N., Mahajan, Mayur, Ponnavaikko, Poongovan
• Primary Examiner(s): Walsh, John B
• Application Number:
  US13/827,641
• Publication Number:
  US 20140089484A1
• Time in Patent Office: 992 Days
• Field of Search: None
• US Class Current: 1/1
• CPC Class Codes: H04L 41/00 Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
• CPC Class Codes: H04L 45/16 Multipoint routing
• CPC Class Codes: H04L 45/60 Router architectures
• CPC Class Codes: H04L 47/15 in relation to multipoint traffic arrangements for broadcast or multicast in data networks H04L12/18
• CPC Class Codes: H04L 51/48 Message addressing, e.g. address format or anonymous messages, aliases

Abstract

Certain embodiments of the present invention provide techniques that enable messages to be sent to a processing entity within a computing device without knowing the network address of the processing entity. In certain embodiments, instead of using the network address of the processing entity, a message can be communicated to the processing entity using information indicative of a role or state or function performed by the processing entity.

Claims

1. A network device comprising:

a plurality of ports for receiving and forwarding data traffic;

a first processing entity and a second processing entity configurable to process the data traffic for forwarding;

the first processing entity further configurable to transmit a packet comprising destination information, the destination information comprising a destination identifier and role identification information, the destination identifier identifying a set of one or more destinations, the role identification information identifying a role;

the second processing entity further configurable to;

receive the packet;

determine, based upon the destination information of the packet, that the second processing entity is an intended recipient for the packet if the second processing entity is identified by the destination identifier and the second processing entity operates in a first role specified by role identification information; and

transmit an acknowledgment packet to the first processing entity, upon determining that the second processing entity is the intended recipient; and

the first processing entity further configurable to release resources associated with the packet after receiving the acknowledgement packet for the packet.

2. The network device of claim 1, further comprising

a third processing entity configurable to:

receive the packet; and

determine, based upon the destination information of the packet, that the third processing entity is an intended recipient for the packet if the third processing entity is identified by the destination identifier and the third processing entity operates in a second role specified by role identification information.

3. The network device of claim 2, wherein

the first role is an active role and the second processing entity is further configurable to perform a set of routing-related functions in the active role;

and

the second role is a standby role and the third processing entity is further configurable to not perform the functions of the active role in the standby role.

4. The network device of claim 1, wherein the first processing entity is further configurable to retransmit the packet upon receiving an error packet or an expiry of a timer threshold.

5. The network device of claim 1, further comprising

a third processing entity configurable to switch to the first role from a second role, wherein the second processing entity is no longer available to operate in the first role, the third processing entity further configurable to:

receive the packet; and

determine, based upon the destination information of the packet, that the third processing entity is an intended recipient for the packet if the third processing entity is identified by the destination identifier and the third processing entity operates in the first role specified by the role identification information.

6. The network device of claim 1, wherein the packet is transmitted using an Ethernet protocol implemented in a networking stack executing on the first processing entity.

7. The network device of claim 1, wherein the packet is assigned a priority class from a plurality of priority classes.

8. The network device of claim 7, wherein the packet is delivered in the same order relative to other packets within the same priority class to the second processing entity that the packet is transmitted from the first processing entity.

9. The network device of claim 1, wherein the second processing entity is further configurable to:

determine that a memory buffer assigned for the application for receiving the packet from the first processing entity is filled beyond a high threshold; and

generate a congestion notification packet for the first processing entity, in response to determining that the memory buffer is filled beyond the high threshold.

10. The network device of claim 1, wherein the second processing entity is further configurable to:

determine that a memory buffer assigned for an application for receiving packets from the first processing entity is cleared below a low threshold; and

generate a clear notification packet for the first processing entity, in response to determining that the memory buffer is cleared below the low threshold.

11. A method comprising:

generating, using a first processing entity, a packet comprising destination information, the destination information comprising a destination identifier and role identification information, the destination identifier identifying a set of one or more destinations, the role identification information identifying a role;

transmitting the packet from the first processing entity to a second processing entity;

determining, at the second processing entity, based upon the destination information of the packet, that the second processing entity is an intended recipient for the packet if the second processing entity is identified by the destination identifier and the second processing entity operates in a first role specified by the role identification information;

transmitting, by the second processing entity, an acknowledgment packet to the first processing entity, upon determining that the second processing entity is the intended recipient; and

releasing resources associated with the packet, by the first processing entity, after receiving the acknowledgement packet for the packet.

12. The method of claim 11, further comprising:

receiving, at a third processing entity, the packet; and

determining, by the third processing entity, based upon the destination information of the packet, that the third processing entity is an intended recipient for the packet if the third processing entity is identified by the destination identifier and the third processing entity operates in a second role specified by the role identification information.

13. The method of claim 12, wherein the first role is an active role, wherein the second processing entity performs the set of routing-related functions in the active role, and the second role is a standby role, wherein the third processing entity does not perform the functions of the active role in the standby role.

14. The method of claim 11 further comprises retransmitting the packet, by the first processing entity, upon receiving an error packet or an expiry of a timer threshold.

15. The method of claim 11, further comprising:

switching a third processing entity to operate in the first role from a second role, wherein the second processing entity is no longer available to operate in the first role;

receiving, at the third processing entity, the packet; and

determining, at the third processing entity, based upon the destination information of the packet, that the third processing entity is an intended recipient for the packet if the third processing entity is identified by the destination identifier and the third processing entity operates in the first role specified by the role identification information.

16. The method of claim 11, wherein the packet is assigned a priority class from a plurality of priority classes and wherein the packet is delivered, in the same order relative to other packets within the same priority class, to the second processing entity, that the packet is transmitted from the first processing entity.