Method and system of implementing conversation-sensitive collection for a link aggregation group

• US 9,497,132 B2
• Filed: 12/19/2013
• Issued: 11/15/2016
• Est. Priority Date: 04/23/2013
• Status: Active Grant

• Current Assignee: Telefonaktiebolaget LM Ericsson
• Original Assignee: Telefonaktiebolaget LM Ericsson
• Inventors: Saltsidis, Panagiotis, Farkas, Jnos
• Primary Examiner(s): Shah, Chirag
• Assistant Examiner(s): Kang, Suk Jin
• Application Number:
  US14/134,966
• Publication Number:
  US 20140314094A1
• Time in Patent Office: 1,062 Days
• Field of Search: None
• US Class Current: 1/1
• CPC Class Codes: H04L 45/245 Link aggregation, e.g. trunking
• CPC Class Codes: H04L 47/32 by discarding or delaying data units, e.g. packets or frames
• CPC Class Codes: H04L 47/34 ensuring sequence integrity, e.g. using sequence numbers

Abstract

A method is executed by a network device for implementing conversation-sensitive collection for frames received on a port of a link of a link aggregation group. The network device executes an aggregator to collect the frames for aggregator clients, where each frame is associated with a service identifier and a conversation identifier. The service identifier identifies a data flow at a link level for a service. The conversation identifier identifies the data flow at a link aggregation group level, where each conversation data flow consists of an ordered sequence of frames, and where the conversation-sensitive collection maintains the ordered sequence by discarding frames of conversations not allocated to the port.

Claims

1. A method executed by a network device for implementing conversation-sensitive collection for frames received on a port of a link of a link aggregation group, where a conversation consists of an ordered sequence of frames, and where the conversation-sensitive collection maintains the ordered sequence by discarding frames of conversations not allocated to the port to prevent out of order delivery of the frames of the conversations, the method comprising the steps of:

receiving a frame over the link of the link aggregation group at the network device, wherein each frame is associated with a service identifier and a conversation identifier, the service identifier identifying the conversation at a link level for the service, the conversation identifier identifying the conversation at a link aggregation group level, and wherein the conversation is a data flow consisting of the ordered sequence of frames;

determining the conversation identifier for the frame, wherein determining the conversation identifier for the frame extracts the service identifier from the frame and translating the service identifier to the conversation identifier using a data structure that maps service identifiers to conversation identifiers;

comparing the conversation identifier with port conversation allocation, wherein comparing the conversation identifier with the port conversation allocation accesses a conversation mask for the port using the conversation identifier as an index, the conversation mask matching an operational conversation mask of an associated port at a partner network device that sent the frame on the link;

discarding the frame in response to a non-match of the conversation identifier with the port conversation allocation, wherein the frame is discarded at a link aggregation sublayer; and

forwarding the frame to an aggregator client in response to a match of the conversation identifier with the port conversation allocation.

2. The method of claim 1, further comprising the step of:

checking whether conversation-sensitive collection is enabled.

3. The method of claim 1, wherein receiving the frame over the link of the link aggregation group further comprises the step of:

receiving a frame pointer by a frame collector from an aggregation port that is associated with the link aggregation group.

4. The method of claim 1, wherein determining the conversation identifier for the frame further comprises the steps of:

determining a service identifier format and location by comparison of frame header information with frame conversation assignment configuration; and

retrieving the service identifier from the frame at the determined location.

5. The method of claim 1, wherein determining the conversation identifier further comprises the step of:

looking up the service identifier in a conversation service mapping table to obtain the conversation identifier.

6. The method of claim 3, wherein comparing the conversation identifier with port conversation allocation further comprises the step of:

accessing a conversation mask for the aggregation port using the conversation identifier as an index.

7. The method of claim 6, wherein the discarding of the frame is executed in response to finding a Boolean false at a location in the conversation mask identified by using the conversation identifier as the index.

8. A network device configured to implement conversation-sensitive collection for frames received on a port of a link of a link aggregation group, where the conversation consists of an ordered sequence of frames, and where the conversation-sensitive collection maintains the ordered sequence by discarding frames of conversations not allocated to the port, the network device comprising:

a set of aggregation ports configured to receive a frame over the link of the link aggregation group, wherein each frame is associated with a service identifier and a conversation identifier, the service identifier identifying the conversation at a link level for the service, the conversation identifier identifying the conversation at a link aggregation group level, and wherein the conversation is a data flow consisting of the ordered sequence of frames; and

a network processor coupled to the set of aggregation ports, the network processor configured to execute a link aggregation sublayer including a frame collector, the frame collector configured to determine the conversation identifier of the frame, wherein the frame collector determines the conversation identifier for the frame, extracts the service identifier from the frame and translates the service identifier to the conversation identifier using a data structure that maps service identifiers to conversation identifiers, compare the conversation identifier with port conversation allocation, wherein the frame collector compares the conversation identifier with the port conversation allocation by accessing a conversation mask for the port using the conversation identifier as an index, the conversation mask matching an operational conversation mask of an associated port at a partner network device that sent the frame on the link, discarding the frame in response to a non-match of the conversation identifier with the port conversation allocation, wherein the frame collector discards the frame at a link aggregation sublayer, and forwards the frame to an aggregator client in response to a match of the conversation identifier with the port conversation allocation.

9. The network device of claim 8, wherein the frame collector is further configured to check whether conversation-sensitive collection is enabled.

10. The network device of claim 8, wherein the frame collector is further configured to receive a frame pointer from an aggregation port that is associated with the link aggregation group.

11. The network device of claim 8, wherein the frame collector is further configured to determine the conversation identifier by determining a service identifier format and location by comparison of frame header information with frame conversation assignment configuration, and retrieving the service identifier from the frame at the determined location.

12. The network device of claim 8, wherein the frame collector is further configured to determine the conversation identifier by looking up the service identifier in a conversation service mapping table to obtain the conversation identifier, the network device further comprising:

a storage device to store the conversation service mapping table and the received conversation service mapping digests.

13. The network device of claim 10, wherein the frame collector is further configured to compare the conversation identifier with port conversation allocation by accessing a conversation mask for the aggregation port using the conversation identifier as an index.

14. The network device of claim 13, wherein the frame collector is further configured to discard the frame in response to finding a Boolean false at a location in the conversation mask identified by using the conversation identifier as the index.

15. A non-transitory computer-readable storage medium having instructions stored therein which when executed by a processor, causes the processor to perform operations for implementing conversation-sensitive collection for frames received on a port of a link of a link aggregation group, where the conversation consists of an ordered sequence of frames, and where the conversation-sensitive collection maintains the ordered sequence by discarding frames of conversations not allocated to the port, the operations comprising the steps of:

receiving a frame over the link of the link aggregation group at the network device, wherein each frame is associated with a service identifier and a conversation identifier, the service identifier identifying the conversation at a link level for the service, the conversation identifier identifying the conversation at a link aggregation group level, and wherein the conversation is a data flow consisting of the ordered sequence of frames;

determining the conversation identifier for the frame, wherein determining the conversation identifier for the frame extracts the service identifier from the frame and translating the service identifier to the conversation identifier using a data structure that maps service identifiers to conversation identifiers;

comparing the conversation identifier with port conversation allocation, wherein comparing the conversation identifier with the port conversation allocation accesses a conversation mask for the port using the conversation identifier as an index, the conversation mask matching an operational conversation mask of an associated port at a partner network device that sent the frame on the link;

discarding the frame in response to a non-match of the conversation identifier with the port conversation allocation, wherein the frame is discarded at a link aggregation sublayer; and

forwarding the frame to an aggregator client in response to a match of the conversation identifier with the port conversation allocation.