# US 2021/0176816 A1 · Overload control and coordination between m2m service layer and 3gpp networks

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2021/0176816 A1
- Document ID: US20210176816A1
- Status: Published application
- Kind: A1
- Application number: 17/124,741
- Filed: 2020-12-17
- Published: 2021-06-10
- Earliest claimed: 2014-03-31
- Assignees: Convida Wireless, LLC
- Applicants: Convida Wireless, LLC
- Inventors: Suresh Palanisamy; Michael F. Starsinic
- Web page: https://patentgrep.com/patent/US20210176816A1

## CPC

- H04W 76/36: for reassigning the resources associated with the released connections
- H04W 4/70: Services for machine-to-machine communication [M2M] or machine type communication [MTC]
- H04W 28/0215: {based on user or device properties, e.g. MTC-capable devices (services for machine-to-machine communication [M2M] or machine type communication [MTC] H04W4/70; wireless resource selection or allocation plan definition based on terminal or device properties H04W72/51)}
- H04W 28/0289: {Congestion control (load shedding arrangements in network planning H04W16/08; performing reselection for handling the traffic H04W36/22; wireless traffic scheduling H04W72/12)}
- H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72)

## Abstract

Various issues with existing congestion and overload control mechanisms are recognized and described herein. Described herein, in accordance with various embodiments, are various mechanisms in which core networks, such as 3GPP networks for example, and an M2M service layer can coordinate and share information to efficiently and intelligently manage each other's congestion and overload states.

## Claims

### Claim 1

A method performed by an apparatus at a first core network node, the method comprising:
receiving, from a second core network node, a first congestion report comprising a congestion level and a list of entities that are impacted by a congestion; and
sending, based the first congestion report and to an Application Function/Service Capability Server, AF/SCS, a second congestion report comprising the congestion level and the list of entities.

### Claim 2 (depends on 1)

The method of claim 1, wherein the first core network node comprises an interworking function.

### Claim 3 (depends on 1)

The method of claim 1, wherein the first core network node is a Service Capability Exposure Function, SCEF, or a Policy and Charging Rules Function, PCRF.

### Claim 4 (depends on 1)

The method of claim 1, wherein the list of entities identifies one or more affected User Equipments, UEs.

### Claim 5 (depends on 1)

The method of claim 1, wherein the second congestion report comprises an affected IP domain or Packet Data Network (PDN) or uplink data rate or downlink data rate or required percentage/volume of data rate reduction.

### Claim 6

A method performed by an apparatus at a first core network node, the method comprising sending, to a second core network node, a congestion report comprising a congestion level and a list of entities that are impacted by a congestion.

### Claim 7 (depends on 6)

The method of claim 6, wherein the second core network node comprises an interworking function or a Policy and Charing Rules Function, PCRF.

### Claim 8 (depends on 6)

The method of claim 6, wherein the second core network node comprises a Service Capability Exposure Function, SCEF.

### Claim 9 (depends on 6)

The method of claim 6, wherein the list of entities identifies one or more affected User Equipments, UEs.

### Claim 10

A method performed by an Application Function/Service Capability Server, AF/SCS, the method comprising:
receiving, from a core network node, a congestion report comprising a congestion level and a list of entities that are impacted by a congestion; and
in response to the congestion report, mitigating the congestion by one or more of reducing downlink traffic and modifying a session property.

### Claim 11 (depends on 10)

The method of claim 10, wherein the core network node comprises a Service Capability Exposure Function, SCEF.

### Claim 12 (depends on 10)

The method of claim 10, wherein the core network node comprises an Interworking Function, IF, or a Policy and Charing Rules Function, PCRF.

### Claim 13 (depends on 10)

The method of claim 10, wherein mitigating the congestion comprises applying a downlink rate limit.

### Claim 14 (depends on 10)

The method of claim 10, wherein mitigating the congestion comprises limiting a future downlink rate to a percentage of a current downlink rate.

### Claim 15 (depends on 10)

The method of claim 10, wherein mitigating the congestion comprises applying a downlink packet drop rate.

### Claim 16 (depends on 10)

The method of claim 10, wherein mitigating the congestion comprises sending an application layer message to command one or more UEs to take an action to reduce congestion.

### Claim 17 (depends on 10)

The method of claim 10, wherein the congestion report comprises an affected IP domain or Packet Data Network (PDN) or uplink data rate or downlink data rate or required percentage/volume of data rate reduction.
