IP Library Granted Patent US 10,798,634
Granted Patent B2
US 10,798,634 · App. 15/969,572 · Granted Oct 6, 2020

Routing method and system for a wireless network

Inventors: Yong Kang (Palo Alto, CA); Changming Liu (Cupertino, CA)
Assignee: Extreme Networks, Inc.
H04W40/02H04L41/0893H04L45/00H04L45/18H04L45/20H04L45/245H04W4/06H04W40/24H04W40/246H04W40/36H04L45/02H04L45/22H04L69/22H04W40/30H04W84/005
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 10,798,634
App. No.
15/969,572
Granted
Oct 6, 2020
Kind
B2
Abstract

A method and system for selecting a route in a wireless network for the transmission of a data packet between wireless nodes in the network using a modified link-state routing algorithm. A subset of nodes called portal nodes within the network are elected to do the broadcasting for the entire network. A wireless node identifies a unicast route back to its root portal node, and sends a link-state register message to this portal node. These link-state register messages received by each portal node are aggregated by them and are broadcast to each of the wireless nodes for storage. When a data packet is thereafter received by a wireless node from a neighboring node, it detects if the data packet satisfies one of a plurality of predetermined conditions and rebroadcasts the data packet to neighboring wireless nodes if none of the conditions is satisfied.

Claims (46)

1. A method, comprising:

receiving, at a portal routing device, a packet including a destination network address assigned to a wireless device;

receiving, at the portal routing device, a link-state register message from each of a plurality of non-portal routing devices, the link-state register message comprising backhaul link information and client link information;

aggregating, by the portal routing device, the link-state register messages from the plurality of non-portal routing devices to generate a backhaul link data structure storing the backhaul link information from the plurality of non-portal routing devices and a client link data structure storing the client link information from the plurality of non-portal routing devices, the backhaul link data structure being stored separately from the client link data structure at the portal routing device;

based on the client link data structure, identifying, at the portal routing device, a first wireless non-portal routing device from among the plurality of non-portal routing devices connected to the wireless device;

based on the backhaul link data structure, identifying, at the portal routing device, a route from the portal routing device to the first wireless non-portal routing device; and

wirelessly forwarding the packet from the portal routing device to the wireless device via the first wireless non-portal routing device.

2. The method of claim 1 , further comprising dropping, at the portal routing device, the packet transmitted from a second wireless non-portal routing device in the route, after the packet has been forwarded from the portal routing device.

3. The method of claim 1 , further comprising updating the client link data structure based on a roaming message transmitted from a third wireless non-portal routing device to which the wireless device is newly connected.

4. The method of claim 1 , wherein the backhaul link data structure includes a network address of a second wireless non-portal routing device as a next-hop address for the portal routing device to forward the packet to the first wireless non-portal routing device.

5. The method of claim 1 , wherein the backhaul link data structure includes an identifier of an outgoing network interface of the portal routing device connected to a next wireless non-portal routing device for the portal routing device to forward the packet to the first wireless non-portal routing device.

6. The method of claim 1 , wherein the packet is forwarded in response to the wireless device roaming to the first wireless non-portal routing device from a second wireless non-portal routing device.

7. The method of claim 1 , wherein the backhaul link data structure is unchanged due to an update of the client link data structure in response to the wireless device roaming between a plurality of wireless non-portal routing devices.

8. The method of claim 1 , wherein the client link data structure is shared with the first and other wireless non-portal routing devices in the network.

9. The method of claim 1 , further comprising:

generating, by the portal routing device, a link-state-update message comprising the backhaul link information and the client link information of each of the plurality of non-portal routing devices; and

broadcasting, by the portal routing device, the link-state-update message to the plurality of non-portal routing devices, wherein each of the plurality of non-portal routing devices is configured to be synchronized with one another and the portal routing device based on the link-state-update message.

10. The method of claim 1 , wherein, for each of the plurality of non-portal devices, the backhaul link information comprises logical link information between the non-portal device and an adjacent node of the network and the client link information comprises link information indicating a connection between the non-portal device and the wireless device.

11. A system, comprising:

a plurality of wireless non-portal routing devices; and

a portal routing device configured to:

receive a packet including a destination network address assigned to a wireless device;

receive a link-state register message from each of the plurality of non-portal routing devices, the link-state register message comprising backhaul link information and client link information;

aggregate the link-state register messages from the plurality of non-portal routing devices to generate a backhaul link data structure storing the backhaul link information from the plurality of non-portal routing devices and a client link data structure storing the client link information from the plurality of non-portal routing devices, the backhaul link data structure being stored separately from the client link data structure at the portal routing device;

based on the client link data structure, identify a first wireless non-portal routing device from among the plurality of non-portal routing devices connected to the wireless device;

based on the backhaul link data structure, identify a route from the portal routing device to the first wireless non-portal routing device; and

wirelessly forward the packet from the portal routing device to the wireless device via the first wireless non-portal routing device.

12. The system of claim 11 , wherein the portal routing device is further configured to drop the packet transmitted from a second wireless non-portal routing device in the route, after the packet has been forwarded from the portal routing device.

13. The system of claim 11 , wherein the portal routing device is further configured to update the client link data structure based on a roaming message transmitted from third a wireless non-portal routing device to which the wireless device is newly connected.

14. The system of claim 11 , wherein the backhaul link data structure includes a network address of a second wireless non-portal routing device as a next-hop address for the portal routing device to forward the packet to the first wireless non-portal routing device.

15. The system of claim 11 , wherein the backhaul link data structure includes an identifier of an outgoing network interface of the portal routing device connected to a next wireless non-portal routing device for the portal routing device to forward the packet to the first wireless non-portal routing device.

16. The system of claim 11 , wherein the portal routing device forwards the packet in response to the wireless device roaming to the first wireless non-portal routing device from another wireless non-portal routing device.

17. The system of claim 11 , wherein the backhaul link data structure is unchanged due to an update of the client link data structure in response to the wireless device roaming between a plurality of wireless non-portal routing devices.

18. A portal routing device, comprising:

a processor; and

a memory coupled to the processor storing instructions that when executed cause the processor to:

receive a packet including a destination network address assigned to a wireless device;

receive a link-state register message from each of a plurality of non-portal routing devices, the link-state register message comprising backhaul link information and client link information;

aggregate the link-state register messages from the plurality of non-portal routing devices to generate a backhaul link data structure storing the backhaul link information from the plurality of non-portal routing devices and a client link data structure storing the client link information from the plurality of non-portal routing devices, the backhaul link data structure being stored separately from the client link data structure at the portal routing device;

based on the client link data structure, identify a first wireless non-portal routing device from among the plurality of non-portal routing devices connected to the wireless device;

based on the backhaul link data structure, identify a route from the portal routing device to the first wireless non-portal routing device; and

wirelessly forward the packet from the portal routing device to the wireless device via the first wireless non-portal routing device.

19. The portal routing device of claim 18 , wherein the instructions further cause the processor to:

generate a link-state-update message comprising the backhaul link information and the client link information of each of the plurality of non-portal routing devices; and

broadcast the link-state-update message to the plurality of non-portal routing devices, wherein each of the plurality of non-portal routing devices is configured to be synchronized with one another and the portal routing device based on the link-state-update message.

20. The portal routing device of claim 18 , wherein, for each of the plurality of non-portal devices, the backhaul link information comprises logical link information between the non-portal device and an adjacent node of the network and the client link information comprises link information indicating a connection between the non-portal device and the wireless device.

Assignments (4)
AMENDED SECURITY AGREEMENT Recorded Aug 18, 2023
From: EXTREME NETWORKS, INC.; AEROHIVE NETWORKS, INC.
To: BANK OF MONTREAL
Reel/Frame 064782/0971 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Apr 23, 2020
From: AEROHIVE NETWORKS, INC.
To: EXTREME NETWORKS, INC.
Reel/Frame 052473/0843 →
SECURITY INTEREST Recorded Aug 12, 2019
From: EXTREME NETWORKS, INC.; AEROHIVE NETWORKS, INC.
To: BANK OF MONTREAL
Reel/Frame 050023/0001 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded May 2, 2018
From: KANG, YONG; LIU, CHANGMING
To: AEROHIVE NETWORKS, INC.
Reel/Frame 045698/0460 →
Continuity (4)
Continuation 14610187 · Jan 30, 2015
Continuation 11903443 · Sep 21, 2007
Provisional Application 60926590 · Apr 27, 2007
Related Publication 20180249393A1 · Aug 30, 2018
Cited By (1)
US 12,355,657