OVERLOAD CONTROL AND COORDINATION BETWEEN M2M SERVICE LAYER AND 3GPP NETWORKS

• US 20170019750A1
• Filed: 03/31/2015
• Published: 01/19/2017
• Est. Priority Date: 03/31/2014
• Status: Active Grant

• Current Assignee: IPLA Holdings Incorporated
• Original Assignee: Convida Wireless LLC
• Inventors: PALANISAMY, Suresh, STARSINIC, Michael F.
• Granted Patent: US 10,904,946 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: 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
• CPC Class Codes: 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
• CPC Class Codes: H04W 4/70 Services for machine-to-machine communication [M2M] or machine type communication [MTC]
• CPC Class Codes: H04W 76/36 for reassigning the resources associated with the released connections

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 3 GPP 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

1. A service layer node comprising a processor, a memory, and communication circuitry, the service layer node being connected to a core network via its communication circuitry, the service layer node further comprising computer-executable instructions stored in the memory of the service layer node which, when executed by the processor of the service layer node, cause the service layer node to:

receive an indication message associated with a congestion condition of the core network, the indication message including one or more parameters corresponding to the congestion condition;

select, based on the one or more parameters, an action to reduce activity on the core network; and

perform the selected action to reduce activity on the core network, thereby eliminating the congestion condition.

2. The service layer node as recited in claim 1, wherein the indication message is received from a machine type communication interworking function (MTC-IWF).

3. The service layer node as recited in claim 1, wherein the indication message is received from a policy and charging rules function (PCRF).

4. The service layer node as recited claim 1, wherein the service layer node performs the selected action by reducing a user plane data rate associated with a device connected to the core network.

5. The service layer node as recited in claim 1, wherein the service layer node performs the selected action by suspending the creation of new sessions.

6. The service layer node as recited in claim 1, wherein the service layer node performs the selected action by providing the core network with a list of devices that can be disconnected from the core network.

7. The service layer node as recited in claim 1, wherein the service layer node performs the selected action by terminating or modifying at least one session established over an Rx interface.

8. The service layer node as recited in claim 1, wherein the service layer node performs the selected action by informing at least one device that the at least one device should reduce its user plane data rate, reduce its number of user plane connections, terminate at least one of its user plane connections, terminate its packet data network (PDN) connection until a backoff timer expires, or stop sending data over certain radio access technologies (RATs).

9. The service layer node as recited claim 1, wherein the service layer node further comprises computer executable instructions that further cause the service layer node to provide the core network with low access priority information associated with a first device connected to the core network, such that the core network can handle the first device in accordance with the low access priority information during the congestion condition.

10. The service layer node as recited in claim 1, wherein the service layer node further comprises computer executable instructions that further cause the service layer node to provide the core network with emergency information associated with a second device connected to the core network, such that the core network can handle the second device in accordance with the emergency information during the congestion condition.

11. The service layer node as recited in claim 1, wherein the one or more parameters corresponding to the congestion condition comprise at least one of an identity associated with the core network;

an IP address range indicative of a portion of the core network associated with the congestion condition;

a reduction parameter associated with an amount of congestion corresponding to the congestion condition;

a type of load indicative of the selected action for reducing the activity, and a time duration associated with the selected action.

12. A core network node comprising a processor, a memory, and communication circuitry, the core network node being part of a core network via its communication circuitry, the core network node further comprising computer-executable instructions stored in the memory of the core network node which, when executed by the processor of the core network node, cause the core network node to:

receive a first request associated with a congestion condition of a service layer node, the request including one or more parameters corresponding to the congestion condition;

based on the one or more parameters, determine a first device to disconnect from the service layer node; and

detach the first device from the service layer node.

13. The core network node as recited in claim 12, wherein the one or more parameters comprise an idle mode parameter that instructs the core network node to detach the first device.

14. The core network node as recited in claim 12, wherein the one or more parameters comprise a disconnection list that indicates a plurality of devices that should be immediately disconnected from the core network upon receipt of the first request, the disconnection list including the first device.

15. The core network node as recited in claim 12, wherein the one or more parameters comprise a vulnerability list that indicates a plurality of devices that can be detached from the core network to allow higher priority devices to access the service layer node, the vulnerability list including the first device.

16. The core network node as recited in claim 12, wherein the one or more parameters comprise a back off timer indicative of a time period after which the first device can attempt to reattach to the service layer node.

17. A service layer node comprising a processor, a memory, and communication circuitry, the service layer node being connected to a core network via its communication circuitry, the service layer node further comprising computer-executable instructions stored in the memory of the service layer node which, when executed by the processor of the service layer node, cause the service layer node to:

send a request that informs a node of the core network of an operation that the service layer node intends to perform, the operation requiring resources of the core network; and

based on the request, receive a message from the core network, the message indicating at least one of a time for the service layer node to perform the operation, a capability of the core network that can be used for the operation, or an indication that the required resources are reserved for the operation.

18. The service layer node as recited in claim 17, wherein the request is sent when the service layer node determines that the operation requires a data rate that is greater than a predetermined threshold.

19. The service layer node as recited in claim 17, wherein the request is sent when the service layer node determines that the operation triggers a number of devices that is greater than a predetermined threshold.

20. The service layer node as recited in claim 17, wherein the request includes an indication of at least one of:

a type of a procedure that the service layer node intends to perform, a number of devices on which the service layer node intends to perform the procedure, a data rate that will be required for the procedure, a geographic area where devices on which the service layer intends to perform the procedure are located, an access point name (APN) that will be used for the procedure, a delay tolerance of the procedure, or one or more resources that should be reserved for the procedure.

21. The service layer node as recited in claim 17, wherein the message is received from a Policy and Charging Rules Function (PCRF) or PGW.