Overload control and coordination between m2m service layer and 3gpp networks
US-2017019750-A1 · Jan 19, 2017 · US
US11553370B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-11553370-B2 |
| Application number | US-201816202083-A |
| Country | US |
| Kind code | B2 |
| Filing date | Nov 27, 2018 |
| Priority date | Nov 27, 2017 |
| Publication date | Jan 10, 2023 |
| Grant date | Jan 10, 2023 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
A method for congestion mitigation via admission control in a shared-backhaul telecommunications network is disclosed, comprising: assessing a congestion state in a multi-node radio access network having a shared backhaul connection, the congestion state based on congestion of the shared backhaul connection; retrieving an admission control policy based on the congestion state of the shared backhaul connection; performing a policy action of the admission control policy at a first base station acting as a gateway for the multi-node radio access network with respect to the shared backhaul connection; and sending the admission control policy to other nodes in the multi-node radio access network, thereby causing the other nodes to perform the policy action, wherein the policy action is denying a request from a user equipment to attach to the radio access network.
Opening claim text (preview).
The invention claimed is: 1. A method for congestion mitigation via admission control in a shared-backhaul telecommunications network, comprising: assessing, by a limiting link of the network having a shared backhaul connection a congestion state in a multi-node radio access network having a shared backhaul connection, the congestion state based on congestion of the shared backhaul connection; retrieving an admission control policy based on the congestion state determined by the limiting link, the admission control policy including an Allocation and Retention Priority (ARP); sending the admission control policy to other nodes in the multi-node radio access network; providing, by a coordinating server, coordination of ARP and admission control across multiple networks on a common physical infrastructure; performing a policy action of the admission control policy at the other nodes of the multi-node radio access network with respect to the shared backhaul connection; and performing a second policy action of a second admission control policy in response to a first escalated congestion state, wherein the second policy action is dropping existing connections to user equipments that have only non-prioritized data connections, wherein the policy action is denying a request from a user equipment to attach to the radio access network. 2. The method of claim 1 , further comprising performing a third policy action of a third admission control policy in response to a second escalated congestion state, wherein the third policy action is preempting existing prioritized user data connections in favor of higher-priority user data connections. 3. The method of claim 1 , further comprising performing a fourth policy action of a fourth admission control policy in response to a third escalated congestion state, wherein the fourth policy action is dropping users at random. 4. The method of claim 1 , further comprising escalating and de-escalating a congestion state based on periodically evaluating congestion of the shared backhaul connection. 5. The method of claim 1 , wherein congestion is one of errors, dropped packets, a high measured error rate, a high measured carried throughput that is close to theoretical peak throughput, or estimated future congestion. 6. The method of claim 1 , wherein the shared-backhaul telecommunications network is a mesh network and each node in the mesh network is a base station implementing the admission control policy. 7. The method of claim 1 , further comprising applying different policies to different UE connections. 8. The method of claim 1 wherein retrieving an admission control policy comprises retrieving an admission control policy including a set of rules for QoS, filtering, QoS class identifier (QCI)/QoS tagging, and admission control. 9. The method of claim 1 wherein the ARP is a parameter provisioned from a core network to a base station to tell the base station when a particular bearer or connection should be released or retained. 10. A gateway node configured to provide congestion mitigation, comprising: an inbound interface for receiving data from a plurality of base stations; an outbound backhaul interface for sending data toward a mobile operator core network; and a processor configured to: assess a congestion state in a multi-node radio access network having a shared backhaul connection, the congestion state based on congestion of the shared backhaul connection; retrieve an admission control policy based on the congestion state of the shared backhaul connection, the admission control policy including an Allocation and Retention Priority (ARP); send the admission control policy to other nodes in the multi-node radio access network; provide, by a coordinating server, coordination of ARP and admission control across multiple networks on a common physical infrastructure; perform a policy action of the admission control policy at the other nodes of the multi-node radio access network with respect to the shared backhaul connection; and perform a second policy action of a second admission control policy in response to a first escalated congestion state, wherein the second policy action is dropping existing connections to user equipments that have only non-prioritized data connections, wherein the policy action is denying a request from a user equipment to attach to the radio access network. 11. The gateway node of claim 10 , wherein the processor is further configured to perform a third policy action of a third admission control policy in response to a second escalated congestion state, wherein the third policy action is preempting existing prioritized user data connections in favor of higher-priority user data connections. 12. The gateway node of claim 10 , wherein the processor is further configured to perform a fourth policy action of a fourth admission control policy in response to a third escalated congestion state, wherein the fourth policy action is dropping users at random. 13. The gateway node of claim 10 , wherein the processor is further configured to escalate and de-escalate a congestion state based on periodically evaluating congestion of the shared backhaul connection. 14. The gateway node of claim 10 , wherein congestion is one of errors, dropped packets, a high measured error rate, a high measured carried throughput that is close to theoretical peak throughput, or estimated future congestion. 15. The gateway node of claim 10 , wherein the shared-backhaul telecommunications network is a mesh network and each node in the mesh network is a base station implementing the admission control policy. 16. The gateway node of claim 10 , wherein different policies are applied to different UE connections. 17. The gateway node of claim 10 wherein an admission control policy includes a set of rules for QoS, filtering, QoS class identifier (QCI)/QoS tagging, and admission control. 18. The gateway node of claim 10 wherein the ARP is a parameter provisioned from a core network to a base station to tell the base station when a particular bearer or connection should be released or retained.
detecting congestion or overload during communication (monitoring arrangements H04L43/00) · CPC title
between access point and backbone network device · CPC title
Self-organising networks, e.g. ad-hoc networks or sensor networks · CPC title
based on regulatory allocation policies · CPC title
using specific QoS parameters for wireless networks, e.g. QoS class identifier [QCI] or guaranteed bit rate [GBR] (negotiating SLA or negotiating QoS H04W28/24) · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.