US2023300678A1PendingUtilityA1
Systems and methods for load control of a user device during network congestion
Assignee: VERIZON PATENT & LICENSING INCPriority: Dec 10, 2020Filed: May 30, 2023Published: Sep 21, 2023
Est. expiryDec 10, 2040(~14.4 yrs left)· nominal 20-yr term from priority
H04L 43/08H04W 28/0289H04W 28/0967H04W 28/0942H04W 28/10H04L 47/125H04W 28/0268H04L 41/0894H04W 28/06
64
PatentIndex Score
0
Cited by
0
References
0
Claims
Abstract
Various aspects of the present disclosure generally relate to wireless communication. In some aspects, a device may receive traffic data associated with a coverage area and determine that there is network congestion. If there is network congestion, the device may identify a high-consumption user device. The device may perform a corrective action in connection with a load of the high-consumption user device, such as limit a throughput of the high-consumption user device. The device may perform a corrective action based on a policy obtained from a policy and control function.
Claims
exact text as granted — not AI-modifiedWhat is claimed is:
1 . A method, comprising:
identifying, by a first device, a congestion event based on processing unit usage at one or more network components; identifying, by the first device and based on identifying the congestion event, a second device with a load that satisfies a load threshold; and limiting, by the first device and based on a policy obtained from a policy and control function, the load of the second device based on a stepped-limiting mechanism associated with the processing unit usage.
2 . The method of claim 1 , wherein the load threshold is implemented based on identifying the congestion event.
3 . The method of claim 1 , further comprising:
causing a network component to obtain the policy.
4 . The method of claim 1 , wherein identifying the congestion event is based on determining whether traffic data satisfies a congestion threshold.
5 . The method of claim 1 , wherein limiting the load of the second device comprises:
causing a network component to drop packets for the second device.
6 . The method of claim 1 , wherein limiting the load of the second device comprises:
limiting a throughput associated with the second device.
7 . The method of claim 1 , further comprising:
determining a status associated with the second device; and wherein limiting the load of the second device is based on the status of the second device.
8 . A first device, comprising:
one or more processors configured to:
identify a congestion event based on processing unit usage at one or more network components;
identify, based on identifying the congestion event, a second device with a load that satisfies a load threshold; and
perform a corrective action, based on a policy obtained from a policy and control function, associated with the load of the second device based on using a stepped-limiting mechanism associated with the processing unit usage.
9 . The first device of claim 8 , wherein the policy includes one or more of:
an area capacity policy, a mobility policy, a density policy, or a guaranteed minimum data policy.
10 . The first device of claim 8 , wherein the one or more processors are further configured to:
provide, to a network component, information associated with the congestion event; and instruct the network component to obtain the policy.
11 . The first device of claim 8 , wherein the one or more processors, are further configured to:
identify a plurality of user devices impacted by the congestion event.
12 . The first device of claim 8 , wherein the one or more processors, to perform the corrective action, are configured to:
cause a serving gateway to notify a core network device that the second device is overloading a network component.
13 . The first device of claim 8 , wherein the one or more processors, to perform the corrective action, are configured to:
notify a core network device to limit throughput for the second device.
14 . The first device of claim 8 , wherein the one or more processors, to perform the corrective action, are configured to:
apply a quality of service parameter for the second device.
15 . A non-transitory computer-readable medium storing a set of instructions, the set of instructions comprising:
one or more instructions that, when executed by one or more processors of a first device, cause the first device to:
identify a congestion event based on processing unit usage at one or more network components;
identify, based on identifying the congestion event, a second device with a load that satisfies a load threshold; and
perform a corrective action, based on a policy obtained from a policy and control function, associated with the second device based on a stepped-limiting mechanism associated with the processing unit usage.
16 . The non-transitory computer-readable medium of claim 15 , wherein the one or more instructions, that cause the first device to perform the corrective action, cause the first device to:
enforce an aggregate maximum bit rate for the second device.
17 . The non-transitory computer-readable medium of claim 15 , wherein the one or more instructions, that cause the first device to perform the corrective action, cause the first device to:
enforce a maximum bit rate for the second device.
18 . The non-transitory computer-readable medium of claim 15 , wherein the one or more instructions, that cause the first device to perform the corrective action, cause the first device to:
limit an aggregate of data usage for all quality of service flows for the second device.
19 . The non-transitory computer-readable medium of claim 15 , wherein the one or more instructions further cause the device to:
instruct a network component to obtain a particular policy for addressing high consumption devices.
20 . The non-transitory computer-readable medium of claim 15 , wherein the one or more instructions further cause the device to:
obtain the policy from a network component,
wherein the policy indicates a limiting behavior for high consumption devices.Join the waitlist — get patent alerts
Track US2023300678A1 — get alerts on status changes and closely related new filings.
We store only your email — no account needed. See our privacy policy.