IP Library Patent Application 18056916
Patent Application
App. No. 18/056,916

Allocating Network Resources to a Mesh Access Point

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 None
App. No.
18/056,916
Abstract

A root access point (RAP) that allocates network resources (such as airtimes) to two or more mess access points (MAPs) via in a mesh network is described. During operation, the RAP receives communication information associated with operation of the two or more MAPs. Then, the RAP allocates the network resources in the mesh network to the two or more MAPs based at least in part on the communication information. Note that the network resources may include use of a shared wireless medium. For example, the network resources may include airtimes of the two or more MAPs. Moreover, a first airtime of a first MAP in the two or more MAPs may be different from a second airtime of a second MAP in the two or more MAPs and/or one or more clients (such as one or more electronic devices) of the RAP.

Claims (30)

1 . A root access point (RAP), comprising:

one or more interface circuits configured to communicate with at least two mesh access points (MAPs) in a mesh network and one or more electronic devices in a wired network, wherein the RAP is configured to:

receive communication information associated with operation of the two or more MAPs; and

allocate network resources in the mesh network to the two or more MAPs based at least in part on the communication information.

2 . The RAP of claim 1 , wherein the allocation is based at least in part on second communication information associated with operation of the RAP.

3 . The RAP of claim 1 , wherein the network resources comprise airtimes of the two or more MAPs.

4 . The RAP of claim 3 , wherein a first airtime of a first MAP in the two or more MAPs is different from a second airtime of a second MAP in the two or more MAPs.

5 . The RAP of claim 4 , wherein the first airtime and the second airtime ensure that clients of the first MAP and the second MAP have approximately the same or equal communication performance.

6 . The RAP of claim 1 , wherein the communication information is received from the two or more MAPs.

7 . The RAP of claim 1 , wherein the communication information is received from a controller of the RAP or from a computer.

8 . The RAP of claim 1 , wherein the RAP is configured to determine the allocation of the network resources based at least in part on the communication information.

9 . The RAP of claim 1 , wherein the RAP is configured to:

provide the communication information addressed to a controller of the RAP or a computer; and

receive information specifying the allocation from the controller or the computer.

10 . The RAP of claim 1 , wherein the communication information of a given MAP in the two or more MAPs comprises: a number of clients of the given MAP; a received signal strength of wireless signals associated with the RAP; modulation coding scheme (MCS) data rates; average throughput of the given MAP with clients of the given MAP; or a traffic type.

11 . The RAP of claim 1 , wherein the communication information is received from a given MAP via a beacon associated with the given MAP using a vendor specific attribute, or via a management frame or a control frame associated with the given MAP.

12 . The RAP of claim 11 , wherein the RAP is configured to request the communication information using a second beacon that includes a request for the communication information, or via a second management frame or a second control frame that includes a request for the communication information.

13 . A non-transitory computer-readable storage medium for use in conjunction with a root access point (RAP), the computer-readable storage medium storing program instructions, wherein, when executed by the RAP, the program instructions cause the RAP to perform operations comprising:

receiving communication information associated with operation of the two or more mesh access points (MAPs) in a mesh network; and

allocating network resources in the mesh network to the two or more MAPs based at least in part on the communication information.

14 . The non-transitory computer-readable storage medium of claim 13 , the network resources comprise airtimes of the two or more MAPs.

15 . The non-transitory computer-readable storage medium of claim 13 , wherein the communication information is received from the two or more MAPs, a controller of the RAP or from a computer.

16 . The non-transitory computer-readable storage medium of claim 13 , wherein the communication information of a given MAP in the two or more MAPs comprises: a number of clients of the given MAP; a received signal strength of wireless signals associated with the RAP; modulation coding scheme (MCS) data rates; average throughput of the given MAP with clients of the given MAP; or a traffic type.

17 . A method for allocating network resources in a mesh network, comprising:

by a root access point (RAP):

receiving communication information associated with operation of the two or more mesh access points (MAPs) in the mesh network; and

allocating the network resources in the mesh network to the two or more MAPs based at least in part on the communication information.

18 . The method of claim 17 , the network resources comprise airtimes of the two or more MAPs.

19 . The method of claim 17 , wherein the communication information is received from the two or more MAPs, a controller of the RAP or from a computer.

20 . The method of claim 17 , wherein the communication information of a given MAP in the two or more MAPs comprises: a number of clients of the given MAP; a received signal strength of wireless signals associated with the RAP; modulation coding scheme (MCS) data rates; average throughput of the given MAP with clients of the given MAP; or a traffic type.

Assignments (8)
SECURITY INTEREST Recorded Apr 8, 2026
From: ARRIS ENTERPRISES LLC; RUCKUS IP HOLDINGS LLC
To: CITIBANK, N.A., AS COLLATERAL AGENT
Reel/Frame 075476/0814 →
RELEASE OF SECURITY INTEREST AT REEL/FRAME 067620/0675 Recorded Jan 12, 2026
From: JPMORGAN CHASE BANK, N.A., AS COLLATERAL AGENT
To: RUCKUS IP HOLDINGS LLC
Reel/Frame 074593/0001 →
RELEASE OF SECURITY INTEREST AT REEL/FRAME 067620/0717 Recorded Dec 19, 2024
From: JPMORGAN CHASE BANK, N.A., AS COLLATERAL AGENT
To: RUCKUS IP HOLDINGS LLC
Reel/Frame 069743/0220 →
SECURITY INTEREST Recorded Dec 17, 2024
From: ARRIS ENTERPRISES LLC; COMMSCOPE TECHNOLOGIES LLC; COMMSCOPE INC., OF NORTH CAROLINA; OUTDOOR WIRELESS NETWORKS LLC; RUCKUS IP HOLDINGS LLC
To: APOLLO ADMINISTRATIVE AGENCY LLC
Reel/Frame 069889/0114 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Aug 30, 2024
From: MATTAPARTI, RAVI KIRAN
To: ARRIS ENTERPRISES LLC
Reel/Frame 068448/0724 →
PATENT SECURITY AGREEMENT (TERM) Recorded Jun 4, 2024
From: RUCKUS IP HOLDINGS LLC
To: JPMORGAN CHASE BANK, N.A., AS COLLATERAL AGENT
Reel/Frame 067620/0717 →
PATENT SECURITY AGREEMENT (ABL) Recorded Jun 4, 2024
From: RUCKUS IP HOLDINGS LLC
To: JPMORGAN CHASE BANK, N.A., AS COLLATERAL AGENT
Reel/Frame 067620/0675 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jan 12, 2024
From: ARRIS ENTERPRISES LLC
To: RUCKUS IP HOLDINGS LLC
Reel/Frame 066399/0561 →