IP Library Granted Patent US 12,212,449
Granted Patent B2
US 12,212,449 · App. 18/415,364 · Granted Jan 28, 2025

System and method for resilient wireless packet communications

Inventors: Alain Hourtane (San Francisco, CA); Sergio Licardie (Cupertino, CA); Chaoming Zeng (Milpitas, CA)
Assignee: Aviat U.S., Inc.
H04L41/0627H03M13/09H04L1/004H04L12/42H04L41/0654H04L41/0663H04L45/00H04L45/28H04W24/04
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,212,449
App. No.
18/415,364
Granted
Jan 28, 2025
Kind
B2
Abstract

Rapid failure detection and recovery in wireless communication networks is needed in order to meet, among other things, carrier class Ethernet transport channel standards. Thus, resilient wireless packet communications is provided using a hardware-assisted rapid transport channel failure detection algorithm and a Gigabit Ethernet data access card with an engine configured accordingly. In networks with various topologies, this is provided in combination with their existing protocols, such as rapid spanning tree and link aggregation protocols, respectively.

Claims (53)

1. A network link method comprising:

receiving, by a first data transmission device, a first packet transmitted from a second data transmission device over a wireless network link;

determining, by the first data transmission device based on the first packet received, a first receive status for the wireless network link;

sending, by the first data transmission device in response to determining the first receive status for the wireless network link, a second packet to the second data transmission device, the second packet comprising a header that indicates the first receive status;

receiving, by the first data transmission device, a sequence of packets transmitted from the second data transmission device over the wireless network link, each of the packets of the sequence of packets including a header comprising a cyclic redundancy check (CRC) value and indicating the first receive status;

determining, by the first data transmission device, that a given number of the packets of the sequence of packets comprise a header having a first type of CRC value;

determining, by the first data transmission device in response to determining that a given number of the packets of the sequence of packets comprise a header having a first type of CRC value, a second receive status for the wireless network link; and

sending, by the first data transmission device in response to determining the second receive status for the wireless network link, a third packet to the second data transmission device, the third packet comprising a header that indicates the second receive status.

2. The method of claim 1 , wherein:

the indication of the first receive status is configured to cause the second data transmission device to transmit packets with a header indicating the first receive status, and

the indication of the second receive status is configured to cause the second data transmission device to transmit packets with a header indicating the second receive status.

3. The method of claim 1 , wherein determining the first receive status for the wireless network link comprises determining a traffic alignment error related to payload traffic of the wireless network link.

4. The method of claim 1 , wherein determining the first receive status for the wireless network link comprises determining a packet received timeout related to payload traffic of the wireless network link.

5. The method of claim 1 , wherein determining the first receive status for the wireless network link comprises determining a CRC threshold related to payload traffic of the wireless network link has been met or exceeded.

6. The method of claim 1 , wherein the first data transmission device is one of a plurality of wireless network nodes in a wireless network ring.

7. The method of claim 1 , wherein the given number is a preconfigured CRC validation threshold number.

8. The method of claim 1 , further comprising performing link aggregation.

9. A network data transmission device comprising:

a network interface configured to receive packets via a wireless network link; and

circuitry configured to perform the following operations:

receiving, by a first data transmission device via the network interface, a first packet transmitted from a second data transmission device over a wireless network link;

determining, based on the first packet received, a first receive status for the wireless network link;

sending, in response to determining the first receive status for the wireless network link, a second packet to the second data transmission device, the second packet comprising a header that indicates the first receive status;

receiving a sequence of packets transmitted from the second data transmission device over the wireless network link, each of the packets of the sequence of packets including a header comprising a cyclic redundancy check (CRC) value and indicating the first receive status;

determining that a given number of consecutive ones of the packets of the sequence of packets comprise a header having a first type of CRC value;

determining, in response to determining that a given number of consecutive ones of the packets of the sequence of packets comprise a header having a first type of CRC value, a second receive status for the wireless network link; and

sending, in response to determining the second receive status for the wireless network link, a third packet to the second data transmission device, the third packet comprising a header that indicates the second receive status.

10. The device of claim 8 , wherein:

the indication of the first receive status is configured to cause the second data transmission device to transmit packets with a header indicating the first receive status, and

the indication of the second receive status is configured to cause the second data transmission device to transmit packets with a header indicating the second receive status.

11. The device of claim 9 , wherein determining the first receive status for the wireless network link comprises determining a traffic alignment error related to payload traffic of the wireless network link.

12. The device of claim 9 , wherein determining the first receive status for the wireless network link comprises determining a packet received timeout related to payload traffic of the wireless network link.

13. The device of claim 9 , wherein determining the first receive status for the wireless network link comprises determining a CRC threshold related to payload traffic of the wireless network link has been met or exceeded.

14. The device of claim 9 , wherein the first data transmission device is one of a plurality of wireless network nodes in a wireless network ring.

15. The device of claim 9 , wherein the given number is a preconfigured CRC validation threshold number.

16. The device of claim 9 , the operations further comprising performing link aggregation.

17. A network data transmission device comprising:

circuitry configured to perform the following operations:

receiving, by a first data transmission device via a network interface, a first packet transmitted from a second data transmission device over a wireless network link;

determining, based on the first packet received, a first receive status for the wireless network link;

sending, in response to determining the first receive status for the wireless network link, a second packet to the second data transmission device, the second packet comprising a header that indicates the first receive status;

receiving a sequence of packets transmitted from the second data transmission device over the wireless network link, each of the packets of the sequence of packets including a header comprising a cyclic redundancy check (CRC) value and indicating the first receive status;

determining that a given number of consecutive ones of the packets of the sequence of packets comprise a header having a first type of CRC value;

determining, in response to determining that a given number of consecutive ones of the packets of the sequence of packets comprise a header having a first type of CRC value, a second receive status for the wireless network link; and

sending, in response to determining the second receive status for the wireless network link, a third packet to the second data transmission device, the third packet comprising a header that indicates the second receive status.

18. The device of claim 17 , wherein:

the indication of the first receive status is configured to cause the second data transmission device to transmit packets with a header indicating the first receive status, and

the indication of the second receive status is configured to cause the second data transmission device to transmit packets with a header indicating the second receive status.

19. The device of claim 17 , wherein determining the first receive status for the wireless network link comprises determining a traffic alignment error related to payload traffic of the wireless network link.

20. The device of claim 17 , wherein determining the first receive status for the wireless network link comprises determining a packet received timeout related to payload traffic of the wireless network link.

21. The device of claim 17 , wherein determining the first receive status for the wireless network link comprises determining a CRC threshold related to payload traffic of the wireless network link has been met or exceeded.

22. The device of claim 17 , wherein the first data transmission device is one of a plurality of wireless network nodes in a wireless network ring.

23. The device of claim 17 , wherein the given number is a preconfigured CRC validation threshold number.

Assignments (3)
MERGER AND CHANGE OF NAME Recorded Feb 21, 2024
From: STRATEX NETWORKS, INC.; STRATEX MERGER CORP.
To: HARRIS STRATEX NETWORKS OPERATING CORPORATION
Reel/Frame 066516/0294 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Feb 21, 2024
From: HOURTANE, ALAIN; LICARDIE, SERGIO; ZENG, CHAOMING
To: STRATEX NETWORKS, INC.
Reel/Frame 066642/0987 →
CHANGE OF NAME Recorded Feb 21, 2024
From: HARRIS STRATEX NETWORKS OPERATING CORPORATION
To: AVIAT U.S., INC.
Reel/Frame 066643/0236 →
Continuity (9)
Continuation 18097089 · Jan 13, 2023
Continuation 17516213 · Nov 1, 2021
Continuation 16702386 · Dec 3, 2019
Continuation 16150192 · Oct 2, 2018
Continuation 15653485 · Jul 18, 2017
Continuation 14611534 · Feb 2, 2015
Continuation 14183376 · Feb 18, 2014
Continuation 11351983 · Feb 10, 2006
Related Publication 20240214260A1 · Jun 27, 2024
References Cited (94)
US 4941089A · Fischer · 1990 [cited by applicant]
US 6434165B1 · Sherer et al. · 2002 [cited by applicant]
US 6501749B1 · Alexander, Jr. et al. · 2002 [cited by applicant]
US 6512742B1 · Alexander, Jr. et al. · 2003 [cited by applicant]
US 6535489B1 · Merchant et al. · 2003 [cited by applicant]
US 6625152B1 · Monsen et al. · 2003 [cited by applicant]
US 6675243B1 · Bastiani et al. · 2004 [cited by applicant]
US 6850486B2 · Saleh et al. · 2005 [cited by applicant]
US 6901048B1 · Wang et al. · 2005 [cited by applicant]
US 6910149B2 · Perloff et al. · 2005 [cited by applicant]
US 6928056B2 · Evans · 2005 [cited by applicant]
US 6952401B1 · Kadambi et al. · 2005 [cited by applicant]
US 7006500B1 · Pedersen et al. · 2006 [cited by applicant]
US 7010607B1 · Bunton · 2006 [cited by applicant]
US 7023797B2 · Tagore-Brage · 2006 [cited by applicant]
US 7145866B1 · Ting et al. · 2006 [cited by applicant]
US 7230925B2 · Li et al. · 2007 [cited by applicant]
US 7266079B2 · Fan · 2007 [cited by applicant]
US 7529180B1 · Karl et al. · 2009 [cited by applicant]
US 7551616B2 · Devi et al. · 2009 [cited by applicant]
US 7613110B1 · Blair · 2009 [cited by applicant]
US 7639614B2 · Nakagawa et al. · 2009 [cited by applicant]
US 7787370B1 · Aweya et al. · 2010 [cited by applicant]
US 7804761B2 · Rosenhouse et al. · 2010 [cited by applicant]
US 7876747B2 · Elangovan et al. · 2011 [cited by applicant]
US 7898959B1 · Arad · 2011 [cited by applicant]
US 7911953B1 · Prestor et al. · 2011 [cited by applicant]
US 8018843B2 · Dunbar et al. · 2011 [cited by applicant]
US 8094559B1 · Bly et al. · 2012 [cited by applicant]
US 8264953B2 · Licardie et al. · 2012 [cited by applicant]
US 8693308B2 · Hourtane · 2014 [cited by examiner]
US 8774000B2 · Licardie et al. · 2014 [cited by applicant]
US 9294943B2 · Licardie et al. · 2016 [cited by applicant]
US 9521036B2 · Licardie et al. · 2016 [cited by applicant]
US 9712378B2 · Hourtane · 2017 [cited by examiner]
US 9929900B2 · Licardie et al. · 2018 [cited by applicant]
US 10091051B2 · Hourtane · 2018 [cited by examiner]
US 10164874B2 · Licardie et al. · 2018 [cited by applicant]
US 10498584B2 · Hourtane · 2019 [cited by examiner]
US 10505841B1 · Licardie et al. · 2019 [cited by applicant]
US 11165630B2 · Hourtane · 2021 [cited by examiner]
US 11558285B2 · Licardie et al. · 2023 [cited by applicant]
US 11570036B2 · Hourtane · 2023 [cited by examiner]
US 11831412B2 · Licardie et al. · 2023 [cited by applicant]
US 11916722B2 · Hourtane · 2024 [cited by examiner]
US 20020054567A1 · Fan · 2002 [cited by applicant]
US 20020097681A1 · Treister · 2002 [cited by examiner]
US 20020105949A1 · Shinomiya et al. · 2002 [cited by applicant]
US 20020136268A1 · Gan · 2002 [cited by examiner]
US 20020159023A1 · Swab · 2002 [cited by applicant]
US 20020167898A1 · Thang et al. · 2002 [cited by applicant]
US 20030054829A1 · Moisio · 2003 [cited by applicant]
US 20030117945A1 · Zboril · 2003 [cited by applicant]
US 20030128706A1 · Mark et al. · 2003 [cited by applicant]
US 20040085894A1 · Wang et al. · 2004 [cited by applicant]
US 20040208552A1 · Harney et al. · 2004 [cited by applicant]
US 20040228278A1 · Bruckman et al. · 2004 [cited by applicant]
US 20050063701A1 · Ovadia et al. · 2005 [cited by applicant]
US 20050152369A1 · Ambe et al. · 2005 [cited by applicant]
US 20050157759A1 · Ohno et al. · 2005 [cited by applicant]
US 20050169294A1 · Tseng et al. · 2005 [cited by applicant]
US 20050193309A1 · Grilli et al. · 2005 [cited by applicant]
US 20050213547A1 · Meier · 2005 [cited by applicant]
US 20050281204A1 · Karol et al. · 2005 [cited by applicant]
US 20050281220A1 · Stanwood et al. · 2005 [cited by applicant]
US 20060031482A1 · Mohan et al. · 2006 [cited by applicant]
US 20060045031A1 · Hickey · 2006 [cited by examiner]
US 20060098573A1 · Beer et al. · 2006 [cited by applicant]
US 20060159023A1 · Hickey · 2006 [cited by examiner]
US 20060203780A1 · Terry · 2006 [cited by examiner]
US 20060203847A1 · Toyoda · 2006 [cited by applicant]
US 20060221974A1 · Hilla et al. · 2006 [cited by applicant]
US 20060251106A1 · Nakagawa et al. · 2006 [cited by applicant]
US 20070189154A1 · Hourtane et al. · 2007 [cited by applicant]
US 20070237172A1 · Zelig et al. · 2007 [cited by applicant]
US 20070280258A1 · Rajagopalan et al. · 2007 [cited by applicant]
US 20080068983A1 · Dunbar et al. · 2008 [cited by applicant]
US 20080291843A1 · Sonnenberg et al. · 2008 [cited by applicant]
US 20080305743A1 · Aithal et al. · 2008 [cited by applicant]
US 20100142560A1 · Sharivker et al. · 2010 [cited by applicant]
US 20100215058A1 · Yakov et al. · 2010 [cited by applicant]
CN 1848767 · 2006 [cited by applicant]
CN 1949724 · 2007 [cited by applicant]
WO 0072531 · 2000 [cited by applicant]
Brown, Andrew, “IEEE 802.17 Resilient Packet Ring (RPR) Standards Update,” 27th Meeting of the North American Network Operators' Group (NANOG), Feb. 2003. [cited by applicant]
Cisco Systems, Inc., “Understanding Rapid Spanning Tree Protocol (802.1w),” white paper, Document ID: 24062, pp. 1-19, Sep. 1, 2005. [cited by applicant]
IEEE Computer Society, “IEEE Standard for Information Technology—Telecommunications and Information Exchange Between Systems—Local and Metropolitan Area Networks—Specific Requirements—Part 3: Carrier Sense Multiple Acce… [cited by applicant]
Light Reading Inc., “Making Sonet Ethernet-Friendly,” Mar. 25, 2003 [retrieved online at http://www.lightreading.com/document.asp?doc_id=30194 on Aug. 14, 2007]. [cited by applicant]
SysKonnect GmbH, “Link Aggregation According to IEEE Standard 802.3ad,” white paper, v. 1.10, Oct. 10, 2002. [cited by applicant]
European Patent Application Serial No. 08795867.4, Search Report dated Oct. 25, 2010. [cited by applicant]
European Patent Application Serial No. 08829704.9, Search Report dated Jan. 3, 2012. [cited by applicant]
International Application No. PCT/US2006/006722, International Search Report and Written Opinion dated Sep. 21, 2007. [cited by applicant]
International Application No. PCT/US2008/064600, International Search Report and Written Opinion dated Jul. 28, 2008. [cited by applicant]
International Application No. PCT/US2008/075618, International Search Report and Written Opinion dated Nov. 24, 2008. [cited by applicant]