TECHNIQUES FOR COMMUNICATION BETWEEN INTERWORKING FUNCTION AND SHORT MESSAGE SERVICE NODES FOR DEVICE TRIGGER REPLACEMENT/RECALL

• US 20150195718A1
• Filed: 12/27/2014
• Published: 07/09/2015
• Est. Priority Date: 01/06/2014
• Status: Abandoned Application

• Current Assignee: Intel Corporation
• Original Assignee: Intel Corporation
• Inventors: Jain, Puneet K.
• Application Number:
  US14/583,654
• Publication Number:
  US 20150195718A1
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: H04L 67/125 involving control of end-device applications over a network
• CPC Class Codes: H04W 24/02 Arrangements for optimising operational condition
• CPC Class Codes: H04W 4/12 Messaging; Mailboxes; Announcements
• CPC Class Codes: H04W 4/14 Short messaging services, e.g. short message services [SMS] or unstructured supplementary service data [USSD]
• CPC Class Codes: H04W 4/70 Services for machine-to-machine communication [M2M] or machine type communication [MTC]

Abstract

Techniques to support device trigger replacement and/or recall are described. In one embodiment, for example, a machine-type communication interworking function (MTC-IWF) node may comprise logic, at least a portion of which is in hardware, the logic to receive a trigger adjustment request comprising a stored trigger identifier (ID), the trigger adjustment request constituting a request to adjust a stored device trigger associated with the stored trigger ID, select a trigger adjustment procedure for the stored device trigger based on the trigger adjustment request, and send a first T4 interface command over a T4 interface connection to initiate the selected trigger adjustment procedure. Other embodiments are described and claimed.

Claims

1. A machine-type communication interworking function (MTC-IWF) node, comprising:

logic, at least a portion of which is in hardware, the logic to receive a Device-Action-Request Diameter command comprising a device trigger replacement request, the Device-Action-Request Diameter command to contain a reference number for a device trigger to be replaced, the logic to transfer the device trigger replacement request by sending a Device-Trigger-Request Diameter command over a T4 interface, the Device-Trigger-Request Diameter command to comprise an Old-Reference-Number attribute-value pair (AVP) containing the reference number for the device trigger.

2. The MTC-IWF node of claim 1, the Device-Trigger-Request Diameter command to include an operation type AVP that contains a value indicating that the Device-Trigger-Request Diameter command constitutes a device trigger replacement request.

3. The MTC-IWF node of claim 1, the Device-Trigger-Request Diameter command to comprise a Reference-Number AVP containing a reference number for a new device trigger by which the device trigger is to be replaced.

4. The MTC-IWF node of claim 1, the logic to receive a Device-Trigger-Answer Diameter command over the T4 interface in response to the Device-Trigger-Request Diameter command.

5. The MTC-IWF node of claim 4, the Device-Trigger-Answer Diameter command to comprise an AVP containing a value indicating whether the device trigger has been successfully replaced.

6. The MTC-IWF node of claim 5, the AVP comprising a Result-Code AVP or an Experimental-Result AVP.

7. The MTC-IWF node of claim 4, the Device-Trigger-Answer Diameter command to comprise the Old-Reference-Number AVP.

8. The MTC-IWF node of claim 1, the logic to transfer the device trigger replacement request to a short message service (SMS) service center (SMS-SC) node by sending the Device-Trigger-Request Diameter command to the SMS-SC node via the T4 interface.

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

transfer a received device trigger recall request by sending a Device-Trigger-Request command over a T4 interface connection, the Device-Trigger-Request command to comprise a Reference-Number attribute-value pair (AVP) containing a reference number for a device trigger to be recalled;

receive a Device-Trigger-Answer command over the T4 interface connection in response to the Device-Trigger-Request command; and

determine whether the device trigger has been successfully recalled based on the Device-Trigger-Answer command.

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

receive a Device-Action-Request command comprising the device trigger recall request; and

send the Device-Trigger-Request command in response to the Device-Action-Request command.

11. The at least one non-transitory computer-readable storage medium of claim 10, the Device-Action-Request command to comprise the reference number for the device trigger to be recalled.

12. The at least one non-transitory computer-readable storage medium of claim 9, the Device-Trigger-Request command to comprise an operation type AVP containing a value to indicate that the Device-Trigger-Request command constitutes a request to recall the device trigger.

13. The at least one non-transitory computer-readable storage medium of claim 12, the operation type AVP to comprise a Trigger-Action AVP.

14. The at least one non-transitory computer-readable storage medium of claim 12, the Device-Trigger-Answer command to comprise the operation type AVP.

15. The at least one non-transitory computer-readable storage medium of claim 9, the Device-Trigger-Answer command to comprise an AVP containing a value that indicates whether the device trigger has been successfully recalled, the AVP comprising a Result-Code AVP or an Experimental-Result AVP.

16. The at least one non-transitory computer-readable storage medium of claim 9, the Device-Trigger-Answer command to comprise the reference number for the device trigger.

17. A short message service (SMS) service center (SMS-SC) node, comprising:

logic, at least a portion of which is in hardware, the logic to receive a Device-Trigger-Request command over a T4 interface connection, the Device-Trigger-Request to comprise a request to replace a first device trigger with a second device trigger and to contain a reference number of the first device trigger and a reference number of the second device trigger, the logic to determine whether the first device trigger is pending and, in response to a determination that the first device trigger is pending, delete the first device trigger and store the second device trigger.

18. The SMS-SC node of claim 17, the Device-Trigger-Request command to comprise an Old-Reference-Number attribute-value pair (AVP) and a Reference-Number AVP, the Old-Reference-Number AVP to contain the reference number of the first device trigger, the Reference-Number AVP to contain the reference number of the second device trigger.

19. The SMS-SC node of claim 17, the Device-Trigger-Request command to comprise an operation type attribute-value pair (AVP) containing a value to indicate that the Device-Trigger-Request constitutes a device trigger replacement request.

20. The SMS-SC node of claim 17, the logic to send a Device-Trigger-Answer command over the T4 interface connection in response to the Device-Trigger-Request command.

21. The SMS-SC node of claim 20, the Device-Trigger-Answer command to comprise an attribute-value pair (AVP) containing a value to indicate whether the first device trigger has been successfully replaced with the second device trigger.

22. The SMS-SC node of claim 21, the AVP to comprise a Result-Code AVP or an Experimental-Result AVP.

23. The SMS-SC node of claim 20, the Device-Trigger-Answer command to comprise the reference number of the first device trigger.

24. The SMS-SC node of claim 23, the Device-Trigger-Answer command to comprise an Old-Reference-Number attribute-value pair (AVP) that contains the reference number of the first device trigger.

25. The SMS-SC node of claim 20, the Device-Trigger-Answer command to comprise a operation type attribute-value pair (AVP) containing a value corresponding to device trigger replacement.