Overload control and coordination between M2M service layer and 3GPP networks
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.
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:
send a request that informs a node of the core network of a data transfer that the service layer node intends to perform, the data transfer requiring data to be sent to a group of devices through one or more other nodes of the core network, the request comprising a delay tolerance and an expected data rate for the data transfer to the group of devices; and
based on the request, receive a message from the node of the core network, the message indicating a time for the service layer node to perform the data transfer, and a data transfer rate that can be provided by the one or more other nodes of the core network for the data transfer.
2. The service layer node as recited in claim 1 , wherein the request is sent when the service layer node determines that the data transfer requires a data transfer rate that is greater than a predetermined threshold.
3. The service layer node as recited in claim 1 , wherein the request is sent when the service layer node determines that the data transfer triggers a number of devices that is greater than a predetermined threshold.
4. The service layer node as recited in claim 1 , wherein the request includes an indication of at least one of: a type of a data transfer that the service layer node intends to perform, a number of devices on which the service layer node intends to perform the data transfer, a data transfer rate that will be required for the data transfer, a geographic area where devices on which the service layer node intends to perform the data transfer are located, or an access point name (APN) that will be used for the data transfer.
5. The service layer node as recited in claim 1 , wherein the message is received from a Policy and Charging Rules Function (PCRF), a Machine Type Communications Inter-Working Function (MTC-IWF) or PGW.
6. A core network node comprising a processor, a memory, and communication circuitry, the core network node being connected within 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 request that informs the core network node of a data transfer that a service layer node intends to perform, the data transfer requiring data to be sent to a group of devices through one or more other nodes of the core network, and the request comprising a delay tolerance and an expected data rate for the data transfer to the group of devices; and
based on the request, send a message to the service layer node, the message indicating a time for the service layer node to perform the data transfer, and a data transfer rate that can be provided by the one or more other nodes of the core network for the data transfer.
7. The core network node as recited in claim 6 , wherein the request is received when the service layer node determines that the data transfer requires a data transfer rate that is greater than a predetermined threshold.
8. The core network node as recited in claim 6 , wherein the request is received when the service layer node determines that the data transfer triggers a number of devices that is greater than a predetermined threshold.
9. The core network node as recited in claim 6 , wherein the request includes an indication of at least one of: a type of a data transfer that the service layer node intends to perform, a number of devices on which the service layer node intends to perform the data transfer, a data transfer rate that will be required for the data transfer, a geographic area where devices on which the service layer node intends to perform the data transfer are located, or an access point name (APN) that will be used for the data transfer.
10. The core network node as recited in claim 6 , the core network node further comprising a Policy and Charging Rules Function (PCRF) or PGW.
11. The core network node as recited in claim 6 , wherein the request is received, and the message is sent, via a service capability exposure function (SCEF).
12. A method performed in a system comprising a service layer node and a core network node within a core network, the method comprising:
receiving a request that informs the core network node of a data transfer that the service layer node intends to perform, the data transfer requiring data to be sent to a group of devices through one or more other nodes of the core network, and the request comprising a delay tolerance and an expected data rate for the data transfer to the group of devices; and
based on the request, sending a message to the service layer node, the message indicating a time for the service layer node to perform the data transfer, and a data transfer rate that can be provided by the one or more other nodes of the core network for the data transfer.
13. The method as recited in claim 12 , the method further comprising receiving the request when the service layer node determines that the data transfer requires a data transfer rate that is greater than a predetermined threshold.
14. The method as recited in claim 12 , the method further comprising receiving the request when the service layer node determines that the data transfer triggers a number of devices that is greater than a predetermined threshold.
15. The method as recited in claim 12 , wherein the request includes an indication of at least one of: a type of a data transfer that the service layer node intends to perform, a number of devices on which the service layer node intends to perform the data transfer, a data transfer rate that will be required for the data transfer, a geographic area where devices on which the service layer node intends to perform the data transfer are located, or an access point name (APN) that will be used for the data transfer.
16. The method as recited in claim 12 , wherein the message is sent by a Policy and Charging Rules Function (PCRF) or PGW.
17. The method as recited in claim 12 , wherein the request is received and the message is sent via a service capability exposure function (SCEF), the method further comprising:
receiving the request via a service capability exposure function (SCEF); and
sending the message via the SCEF.
18. The core network node as recited in claim 1 , wherein the request is sent, and the message is received, via a service capability exposure function (SCEF).