MECHANISM TO PREVENT LOAD IN 3GPP NETWORK DUE TO MTC DEVICE TRIGGERS

• US 20160337781A1
• Filed: 12/14/2015
• Published: 11/17/2016
• 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
• Granted Patent: US 9,820,080 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/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. One or more non-transitory computer readable media with executable instructions stored thereon that, when executed, cause a machine type communications interworking function (MTC-IWF) to:

initiate load control of signals received by the MTC-IWF to avoid signaling overload;

receive a device trigger request message comprising a priority parameter from a Services Capability Server (SCS), the device trigger request message to trigger a user equipment (UE) to initiate communication with the SCS;

identify the priority parameter in the device trigger request message;

transmit a subscriber information request;

receive a subscriber information response;

determine whether the SCS is authorized to trigger the UE; and

transmit a device trigger report to the SCS.

2. The media of claim 1, further storing instructions to transmit a cause value with the device trigger report to the SCS.

3. The media of claim 2, wherein the cause value indicates that the device trigger was not transmitted to the UE.

4. The media of claim 1, further storing instructions to adjust the load control of signals received by the MTC-IWF based on receiving the device trigger request.

5. The media of claim 1, wherein the load control is performed in compliance with 3^rd Generation Partnership Project (3GPP) Release 11 Long Term Evolution Advanced (LTE).

6. The media of claim 1, further storing instructions to reject a trigger request if a back-off timer has been applied.

7. The media of claim 6, further storing instructions to receive a second device trigger request message before the timer expires and rejecting the second device trigger request message.

8. A user equipment (UE) adapted for machine type communications (MTC) with a Services Capability Server (SCS) in a mobile network, the UE comprising:

at least one antenna; and

a receiver to receive a device trigger from at least one MTC interworking function (MTC-IWF) to prompt the UE to take an action in response to the device trigger, wherein the SCS is adapted to transmit a device trigger request with a priority parameter to the MTC-IWF for the MTC-IWF to determine;

whether to send the device trigger to the UE; and

whether the SCS is authorized to request the device trigger for the UE, wherein the MTC-IWF is further adapted to transmit a device trigger report comprising a cause value to the SCS.

9. The UE of claim 8, wherein the user equipment (UE) is a device selected from the group consisting of a tablet, smartphone, platform, netbook, laptop, ultrabook, and mobile device.

10. The UE of claim 8, wherein the MTC-IWF comprises a load control mechanism to control an ingress rate of trigger requests from the SCS.

11. The UE of claim 10, wherein the MTC-IWF further comprises a back-off timer to determine whether the device trigger can be sent to the UE.

12. The UE of claim 11, wherein the receiver is adapted to receive the device trigger from the MTC-IWF through an evolved NodeB (eNB).

13. The UE of claim 8, wherein the UE is selected from the group consisting of a smartphone, tablet, netbook, laptop, ultrabook, personal computer, cell phone and handheld device.

14. The UE of claim 8, further comprising processing circuitry and a transmitter.

15. A machine type communications interworking function (MTC-IWF) to communicate a device trigger in a mobile network, the MTC-IWF comprising circuitry to receive a device trigger request comprising a priority parameter from a Services Capability Server (SCS), the SCS to transmit the device trigger request to trigger a user equipment (UE) to take an action in response to the device trigger, wherein the circuitry is further adapted to identify the priority parameter associated with the device trigger request, to determine whether the SCS is authorized to send the device trigger request for the UE, and to transmit a device trigger report to the SCS.

16. The MTC-IWF of claim 15, the circuitry further adapted to initiate a back-off timer to reject a subsequent device trigger request during a back-off time duration.

17. The MTC-IWF of claim 16, the circuitry further adapted to indicate the back-off time duration in the device trigger report.

18. The MTC-IWF of claim 15, further comprising an overload handling function (OHF).

19. The MTC-IWF of claim 18, wherein the OHF is adapted to gauge a level of overload determined by the OHF.

20. The MTC-IWF of claim 19, wherein the OHF is further adapted to receive an overload start message to indicate an overload condition at a network element selected from the group consisting of a Home Location Register (HLR), a Home Subscriber Server (HSS), a mobile management entity (MME), a Serving GPRS (General Packet Radio Service) Support Node (SGSN), and a packet gateway (P-GW).