US 12,255,809 B2
Resilient data communications with physical layer link aggregation, extended failure detection and load balancing
Sergio Licardie, Cupertino, CA (US); and Chaoming Zeng, Milpitas, CA (US)
Assigned to AVIAT NETWORKS, INC., Austin, TX (US)
Filed by Aviat Networks, Inc., Milpitas, CA (US)
Filed on Oct. 16, 2023, as Appl. No. 18/487,492.
Application 18/487,492 is a continuation of application No. 18/093,995, filed on Jan. 6, 2023, granted, now 11,831,412.
Application 18/093,995 is a continuation of application No. 16/709,231, filed on Dec. 10, 2019, granted, now 11,558,285, issued on Jan. 17, 2023.
Application 16/709,231 is a continuation of application No. 16/230,519, filed on Dec. 21, 2018, granted, now 10,505,841, issued on Dec. 10, 2019.
Application 16/230,519 is a continuation of application No. 15/937,785, filed on Mar. 27, 2018, granted, now 10,164,874, issued on Dec. 25, 2018.
Application 15/937,785 is a continuation of application No. 15/376,577, filed on Dec. 12, 2016, granted, now 9,929,900, issued on Mar. 27, 2018.
Application 15/376,577 is a continuation of application No. 15/077,785, filed on Mar. 22, 2016, granted, now 9,521,036, issued on Dec. 13, 2016.
Application 15/077,785 is a continuation of application No. 14/281,746, filed on May 19, 2014, granted, now 9,294,943, issued on Mar. 22, 2016.
Application 14/281,746 is a continuation of application No. 13/305,703, filed on Nov. 28, 2011, granted, now 8,774,000, issued on Jul. 8, 2014.
Application 13/305,703 is a continuation of application No. 12/205,791, filed on Sep. 5, 2008, granted, now 8,264,953, issued on Sep. 11, 2012.
Claims priority of provisional application 60/970,476, filed on Sep. 6, 2007.
Prior Publication US 2024/0113960 A1, Apr. 4, 2024
This patent is subject to a terminal disclaimer.
Int. Cl. H04L 12/703 (2013.01); H04L 1/00 (2006.01); H04L 12/40 (2006.01); H04L 41/0668 (2022.01); H04L 43/0811 (2022.01); H04L 43/0823 (2022.01); H04L 45/00 (2022.01); H04L 45/24 (2022.01); H04L 45/28 (2022.01); H04L 47/125 (2022.01); H04L 47/41 (2022.01); H04L 69/323 (2022.01); H04W 24/04 (2009.01); H04W 28/02 (2009.01); H04L 49/351 (2022.01)
CPC H04L 45/28 (2013.01) [H04L 1/0041 (2013.01); H04L 12/40182 (2013.01); H04L 41/0668 (2013.01); H04L 43/0811 (2013.01); H04L 43/0823 (2013.01); H04L 45/22 (2013.01); H04L 45/24 (2013.01); H04L 45/245 (2013.01); H04L 47/125 (2013.01); H04L 47/41 (2013.01); H04L 69/323 (2013.01); H04W 24/04 (2013.01); H04W 28/0231 (2013.01); H04L 49/352 (2013.01)] 18 Claims
OG exemplary drawing
 
1. A method of determining status of a receiving node of a wireless link of multiple wireless links in a wireless link aggregation group, the method comprising:
(a) determining, by a receiving node, that a first packet has not been received by the receiving node from a transmitting node over the wireless link, the wireless link at the receiving node having a transmit status and a receive status, and in response to determining that the first packet has not been received by the receiving node from the transmitting node over the wireless link:
(1) determining a time interval since last receipt of a packet from the transmitting node over the wireless link;
(2) determining, based on a time interval threshold, that the time interval fails a condition relative to the time interval threshold; and
(3) in response to determining that the time interval fails the condition relative to the time interval threshold, setting or maintaining the receive status of the wireless link at the receiving node as a negative status;
(b) determining, by a receiving node, that a second packet has been received by the receiving node from the transmitting node over the wireless link, and, in response to determining that the second packet has been received by the receiving node from the transmitting node over the wireless link:
(1) determining an integrity value of the second packet;
(2) determining an error of the integrity value of the second packet;
(3) in response to determining the error associated with the integrity value of the second packet:
(i) increasing an integrity error count;
(ii) determining, based on an integrity error threshold, that the integrity error count satisfies a condition relative to the integrity error threshold;
(iii) in response to determining that the integrity error count satisfies the condition relative to the integrity error threshold, setting or maintaining the receive status of the wireless link at the receiving node as a negative status; and
(c) determining, by the receiving node, that a third packet has been received by the receiving node from the transmitting node over the wireless link, and in response to determining that the third packet has been received by the receiving node from the transmitting node over the wireless link:
(1) determining an integrity value of the third packet;
(2) determining an error of the integrity value of the third packet;
(3) in response to determining the error of the integrity value of the third packet:
(i) increasing an integrity error count;
(ii) determining, based on an integrity error threshold, that the integrity error count fails to satisfy a condition relative to the integrity error threshold;
(iii) in response to determining that the integrity error count fails to satisfy the condition relative to the integrity error threshold, setting or maintaining the receive status of the wireless link at the receiving node as a positive status; and
(d) determining, by the receiving node, that a fourth packet has been received by the receiving node from the transmitting node over the wireless link, and in response to determining that the fourth packet has been received by the receiving node from the transmitting node over the wireless link:
(1) determining an integrity value of the fourth packet;
(2) determining that no error is associated with the integrity value of the fourth packet is correct;
(3) in response to determining that no error is associated with the integrity value of the fourth packet:
(i) resetting the integrity error count;
(ii) increasing an integrity correct count;
(ii) determining, based on an integrity correct threshold, that the integrity correct count satisfies a condition relative to the integrity correct threshold;
(iv) in response to determining that the integrity correct count satisfies a condition relative to the integrity correct threshold, setting or maintaining the receive status of the wireless link at the receiving node as a positive status;
(e) determining, by the receiving node, that a fifth packet has been received by the receiving node from the transmitting node over the wireless link, and in response to determining that the fifth packet has been received by the receiving node from the transmitting node over the wireless link:
(1) determining an integrity value of the fifth packet;
(2) determining that no error is associated with the integrity value of the fifth packet;
(3) in response to determining that no error is associated with the integrity value of the fifth packet:
(i) resetting the integrity error count;
(ii) increasing an integrity correct count;
(ii) determining, based on an integrity correct threshold, that the integrity correct count fails to satisfy a condition relative to the integrity correct threshold; and
(v) in response to determining that the integrity correct count fails to satisfy the condition relative to the integrity correct threshold, setting or maintaining the receive status of the wireless link at the receiving node as a negative status; and
(f) inserting a receive status of the wireless link at the receiving node in a header of a packet, and transmitting the packet to the transmitting node, the receive status of the wireless link at the receiving node for use by the transmitting node as the transmit status of the wireless link at the transmitting node.