Mechanism to prevent load in 3GPP network due to MTC device triggers

• US 9,215,552 B2
• Filed: 09/12/2014
• Issued: 12/15/2015
• Est. Priority Date: 10/03/2011
• Status: Active Grant

• Current Assignee: Daedalus Prime LLC (Daedalus Group LLC)
• Original Assignee: Intel Corporation
• Inventors: Jain, Puneet, Kedalagudde, Meghashree Dattatri, Venkatachalam, Muthaiah
• Primary Examiner(s): Jung, Min
• Application Number:
  US14/485,080
• Publication Number:
  US 20150029845A1
• Time in Patent Office: 459 Days
• Field of Search: None
• 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/0247 based on conditions of the access network or the infrastructure network central resource management H04W28/16
• 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 48/06 based on traffic conditions
• CPC Class Codes: H04W 88/16 Gateway arrangements

Abstract

Embodiments of methods and apparatus to manage MTC device trigger load in a wireless network are described herein. Other embodiments may be described and claimed.

Claims

1. At least one non-transitory computer-readable storage medium comprising a set of instructions that, in response to being executed at a machine-type communication interworking function (MTC-IWF) node, cause the MTC-IWF node to:

identify a device trigger request comprising a request of a services capability server (SCS) for a device trigger to be sent to user equipment (UE), the MTC-IWF node to terminate a Tsp interface between the MTC-IWF node and the SCS;

apply an MTC-IWF load control mechanism in response to the device trigger request;

determine whether to accept the device trigger request; and

send a message to report whether the device trigger has been accepted.

2. The at least one non-transitory computer-readable storage medium of claim 1, comprising instructions that, in response to being executed at the MTC-IWF node, cause the MTC-IWF node to reject the device trigger request in response to a determination that an overload condition exists, the sent message to comprise a value to indicate the existence of the overload condition.

3. The least one non-transitory computer-readable storage medium of claim 1, the device trigger request to contain a value to indicate a priority of the device trigger.

4. The least one non-transitory computer-readable storage medium of claim 1, comprising instructions that, in response to being executed at the MTC-IWF node, cause the MTC-IWF node to:

send a subscriber information request to retrieve subscription information associated with the device trigger request;

identify a subscriber information response in response to the subscriber information request; and

determine, based on the subscriber information response, whether the SCS is authorized to request device triggering of the UE.

5. The least one non-transitory computer-readable storage medium of claim 4, comprising instructions that, in response to being executed at the MTC-IWF node, cause the MTC-IWF node to determine not to accept the device trigger request in response to a determination that the SCS is not authorized to request device triggering of the UE.

6. The least one non-transitory computer-readable storage medium of claim 1, comprising instructions that, in response to being executed at the MTC-IWF node, cause the MTC-IWF node to:

initiate delivery of the device trigger in response to a determination to accept the device trigger request; and

send a message to report a delivery status of the device trigger.

7. A node comprising a machine-type communication interworking function (MTC-IWF) element, the node comprising:

logic, at least a portion of which is in hardware, the logic to identify a device trigger request comprising a request of a services capability server (SCS) to trigger user equipment (UE), send a subscriber information request to authorize the SCS to request triggering of the UE, identify a subscriber information response in response to the subscriber information request, and determine whether to accept the device trigger request based on the subscriber information response, the MTC-IWF element to terminate a Tsp interface between the MTC-IWF element and the SCS.

8. The node of claim 7, the subscriber information response to contain subscription information associated with the device trigger request.

9. The node of claim 7, the logic to determine to accept the device trigger request based at least in part on a determination that the subscriber information response indicates that the SCS is authorized to request triggering of the UE.

10. The node of claim 7, the logic to apply an MTC-IWF load control mechanism in response to receipt of the device trigger request.

11. The node of claim 10, the logic to determine to reject the device trigger request in response to a determination that an overload condition exists at the node.

12. The node of claim 7, the device trigger request to comprise a parameter specifying a priority associated with the device trigger request.

13. The node of claim 7, comprising one or more memory devices.

14. A node comprising a machine-type communication interworking function (MTC-IWF) element, the node comprising:

logic, at least a portion of which is in hardware, the logic to identify a device trigger request comprising a request of a services capability server (SCS) for a device trigger to be sent to user equipment (UE), the device trigger request to comprise a value to indicate a priority of the device trigger, the logic to apply an MTC-IWF load control mechanism in response to the device trigger request, determine whether to accept the device trigger request, and send a message to report whether the device trigger has been accepted, the MTC-IWF element to terminate a Tsp interface between the MTC-IWF element and the SCS.

15. The node of claim 14, the logic to reject the device trigger request in response to a determination that an overload condition exists.

16. The node of claim 15, the sent message to comprise a value to indicate the existence of the overload condition.

17. The node of claim 14, the logic to send a subscriber information request to retrieve subscription information associated with the device trigger request and identify a subscriber information response in response to the subscriber information request.

18. The node of claim 17, the logic to determine, based on the subscriber information response, whether the SCS is authorized to request device triggering of the UE.

19. The node of claim 18, the logic to determine not to accept the device trigger request in response to a determination that the SCS is not authorized to request device triggering of the UE.

20. At least one non-transitory computer-readable storage medium comprising a set of instructions that, in response to being executed at a machine-type communication interworking function (MTC-IWF) node, cause the MTC-IWF node to:

identify a device trigger request comprising a request of a services capability server (SCS) to trigger user equipment (UE), the device trigger request to comprise a parameter specifying a priority associated with the device trigger request, the MTC-IWF node to terminate a Tsp interface between the MTC-IWF node and the SCS;

send a subscriber information request to authorize the SCS to request triggering of the UE;

identify a subscriber information response in response to the subscriber information request;

and determine whether to accept the device trigger request based on the subscriber information response.

21. The at least one non-transitory computer-readable storage medium of claim 20, comprising instructions that, in response to being executed at the MTC-IWF node, cause the MTC-IWF node to determine to accept the device trigger request based at least in part on a determination that the subscriber information response indicates that the SCS is authorized to request triggering of the UE.

22. The at least one non-transitory computer-readable storage medium of claim 20, comprising instructions that, in response to being executed at the MTC-IWF node, cause the MTC-IWF node to apply an MTC-IWF load control mechanism in response to receipt of the device trigger request.

23. The at least one non-transitory computer-readable storage medium of claim 22, comprising instructions that, in response to being executed at the MTC-IWF node, cause the MTC-IWF node to determine to reject the device trigger request in response to a determination that an overload condition exists at the MTC-IWF node.

24. The at least one non-transitory computer-readable storage medium of claim 20, comprising instructions that, in response to being executed at the MTC-IWF node, cause the MTC-IWF node to initiate a device trigger delivery procedure to trigger the UE in response to a determination to accept the device trigger request.

25. The at least one non-transitory computer-readable storage medium of claim 24, comprising instructions that, in response to being executed at the MTC-IWF node, cause the MTC-IWF node to send a device trigger report comprising a cause value to indicate an outcome of the device trigger delivery procedure.