US11038804B2ActiveUtilityA1

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

55
Assignee: ERICSSON TELEFON AB L MPriority: Apr 23, 2013Filed: Sep 16, 2016Granted: Jun 15, 2021
Est. expiryApr 23, 2033(~6.8 yrs left)· nominal 20-yr term from priority
H04L 45/245H04L 47/32H04L 47/34
55
PatentIndex Score
0
Cited by
295
References
20
Claims

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

exact text as granted — not AI-modified
What is claimed is: 
     
       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, the method comprising:
 receiving a frame over the link of the link aggregation group at the network device, wherein each frame includes a service identifier and is associated with a conversation identifier; 
 determining the conversation identifier for the frame using the service identifier of the frame; 
 comparing the conversation identifier with port conversation allocation for the port of the link aggregation group; 
 discarding at a link aggregation sublayer the frame in response to a non-match of the conversation identifier with the port conversation allocation to maintain the ordered sequence of frames in the conversation; 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:
 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:
 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:
 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:
 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. The method of  claim 1 , wherein the service identifier identifies the conversation at a link level for the service, and the conversation identifier identifies the conversation at a link aggregation group level. 
     
     
       9. The method of  claim 6 , further wherein the conversation mask matches an operational conversation mask of an associated port at a partner network device that sent the frame on the link. 
     
     
       10. 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, 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 includes a service identifier and is associated with a conversation identifier; 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 a conversation identifier of the frame using the service identifier, to compare the conversation identifier with port conversation allocation for the port of the link aggregation group, to discard the frame in response to a non-match of the conversation identifier with the port conversation allocation to maintain the ordered sequence of frames in the conversation, and to forward the frame to an aggregator client in response to a match of the conversation identifier with the port conversation allocation. 
 
     
     
       11. The network device of  claim 10 , wherein the frame collector is further configured to check whether conversation-sensitive collection is enabled. 
     
     
       12. The network device of  claim 10 , wherein the frame collector is further configured to receive a frame pointer from an aggregation port that is associated with the link aggregation group. 
     
     
       13. The network device of  claim 10 , 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. 
     
     
       14. The network device of  claim 10 , 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. 
 
     
     
       15. The network device of  claim 12 , 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. 
     
     
       16. The network device of  claim 15 , 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. 
     
     
       17. The network device of  claim 10 , wherein the service identifier identifies the conversation at a link level for the service, and the conversation identifier identifies the conversation at a link aggregation group level. 
     
     
       18. The network device of  claim 15 , further wherein the conversation mask matches an operational conversation mask of an associated port at a partner network device that sent the frame on the link. 
     
     
       19. 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, the operations comprising:
 receiving a frame over the link of the link aggregation group at the network device, wherein each frame includes a service identifier and is associated with a conversation identifier; 
 determining the conversation identifier for the frame using the service identifier of the frame; 
 comparing the conversation identifier with port conversation allocation for the port of the link aggregation group; 
 discarding at a link aggregation sublayer the frame in response to a non-match of the conversation identifier with the port conversation allocation to maintain the ordered sequence of frames in the conversation; and 
 forwarding the frame to an aggregator client in response to a match of the conversation identifier with the port conversation allocation. 
 
     
     
       20. The non-transitory computer-readable medium of  claim 19 , wherein the service identifier identifies the conversation at a link level for the service, and the conversation identifier identifies the conversation at a link aggregation group level.

Cited by (0)

No later patents cite this yet.

References (0)

No backward citations on record.