Techniques for communication between service capability server and interworking function for device trigger recall/replace

• US 9,301,083 B2
• Filed: 09/11/2014
• Issued: 03/29/2016
• Est. Priority Date: 01/06/2014
• Status: Active Grant

• Current Assignee: Intel Corporation
• Original Assignee: Intel IP Corporation (Intel Corporation)
• Inventors: Jain, Puneet K.
• Primary Examiner(s): FILE, ERIN M
• Application Number:
  US14/483,620
• Publication Number:
  US 20150195672A1
• Time in Patent Office: 565 Days
• US Class Current: 1/1
• CPC Class Codes: H04L 67/125 involving control of end-device applications over a network
• CPC Class Codes: H04L 67/56 Provisioning of proxy services store-and-forward switching systems in data switching networks H04L12/54
• CPC Class Codes: H04W 4/12 Messaging; Mailboxes; Announcements
• CPC Class Codes: H04W 4/70 Services for machine-to-machine communication [M2M] or machine type communication [MTC]
• CPC Class Codes: H04W 8/22 Processing or transfer of terminal data, e.g. status or physical capabilities
• CPC Class Codes: H04W 84/042 Public Land Mobile systems, e.g. cellular systems

Abstract

Examples may include techniques for a device trigger recall or a device trigger replace procedure as implemented at a machine type communication-interworking function (MTC-IWF) in response to a command received from a service capability server (SCS). Examples may also include the SCS generating a command for a device trigger recall or a device replace to cause the MTC-IWF to implement the device trigger recall or device trigger replace procedure to either recall or replace a trigger message destined for user equipment. Both the MTC-IWF and the SCS may operate in compliance with one or more 3^rd Generation Partnership Project (3GPP) Long Term Evolution (LTE) standards.

Claims

1. An apparatus comprising:

a processor circuit for a machine type communication-interworking function (MTC-IWF) capable of operating in compliance with one or more 3^rd Generation Partnership Project (3GPP) Long Term Evolution (LTE) standards including LTE-Advanced (LTE-A);

a receive component for execution by the processor circuit to receive a Device-Action-Request (DAR) command from a service capability server (SCS) through a telecommunications service provider (Tsp) interface, the DAR command including a Device-Action attribute value pair (AVP) having an user equipment (UE) identifier to indicate an UE to receive a trigger message initiated by the SCS, an SCS-Identifier for the SCS, a Reference-Number AVP set to identify the trigger message and an Action-Type AVP set to a value to indicate a device trigger recall request to recall the trigger message;

a status component for execution by the processor circuit to determine a status of the device trigger recall request responsive to one of an initiation of a recall procedure with a short message service-service center (SMS-SC) or a rejection of the initiation of the recall procedure by the MTC-IWF or the SMS-SC; and

an answer component for execution by the processor circuit to send a Device-Action-Answer (DAA) command to the SCS through the Tsp interface, the DAA command including a Device-Notification AVP having the UE identifier, the SCS-Identifier, the Reference-Number AVP, the Action-Type AVP and a Request-Status AVP set to a value to indicate success or failure of the device trigger recall request.

2. The apparatus of claim 1, the UE identifier including at least one of an External-Id or a mobile subscriber integrated services digital network-number (MSISDN).

3. The apparatus of claim 1, the Device-Action AVP having an assigned AVP code of 3001, the Reference-Number AVP having an assigned AVP code of 3007, the Action-Type AVP having an assigned AVP code of 3005, the Device-Notification AVP having an assigned AVP code of 3002 and the Request-Status AVP having an assigned AVP code of 3008.

4. The apparatus of claim 1, the value to indicate the device recall request comprises the value set to 3.

5. The apparatus of claim 1, the value to indicate success or failure of the device trigger recall request comprises the value set to 0 for indicating success or the value set to 111 to indicate trigger recall failure or value set to 112 to indicated original trigger message already sent.

6. The apparatus of claim 1, comprising a digital display coupled to the processor circuit to present a user interface view.

7. A method comprising:

receiving, at a machine type communication-interworking function (MTC-IWF) capable of operating in compliance with one or more 3^rd Generation Partnership Project (3GPP) Long Term Evolution (LTE) standards including LTE-Advanced (LTE-A), a Device-Action-Request (DAR) command from a service capability server (SCS) through a telecommunications service provider (Tsp) interface, the DAR command including a Device-Action attribute value pair (AVP) having an user equipment (UE) identifier to indicate an UE to receive a trigger message initiated by the SCS, an SCS-Identifier for the SCS, a Reference-Number AVP set to identify the trigger message and an Action-Type AVP set to a value to indicate a device trigger recall request to recall the trigger message;

determining a status of the device trigger recall request responsive to one of an initiation of a recall procedure with a short message service-service center (SMS-SC) or a rejection of the initiation of the recall procedure by the MTC-IWF or the SMS-SC; and

sending a Device-Action-Answer (DAA) command to the SCS through the Tsp interface, the DAA command including a Device-Notification AVP having the UE identifier, the SCS-Identifier, the Reference-Number AVP, the Action-Type AVP and a Request-Status AVP set to a value to indicate success or failure of the device trigger recall request.

8. The method of claim 7, the UE identifier including at least one of an External-Id or a mobile subscriber integrated services digital network-number (MSISDN).

9. The method of claim 7, the Device-Action AVP having an assigned AVP code of 3001, the Reference-Number AVP having an assigned AVP code of 3007, the Action-Type AVP having an assigned AVP code of 3005, the Device-Notification AVP having an assigned AVP code of 3002 and the Request-Status AVP having an assigned AVP code of 3008.

10. The method of claim 7, the value to indicate the device recall request comprises the value set to 3.

11. The method of claim 7, the value to indicate success or failure of the device trigger recall request comprises the value set to 0 for indicating success or the value set to 111 to indicate trigger recall failure or value set to 112 to indicated original trigger message already sent.

12. At least one non-transitory machine readable medium comprising a plurality of instructions that in response to being executed on a system for a service capability server (SCS) capable of operating in compliance with one or more or more 3^rd Generation Partnership Project (3GPP) Long Term Evolution (LTE) standards including LTE-Advanced (LTE-A), causes the system to:

send a Device-Action-Request (DAR) command to a machine type communication-interworking function (MTC-IWF) through a telecommunications service provider (Tsp) interface, the DAR command including a Device-Action attribute value pair (AVP) having an user equipment (UE) identifier to indicate an UE to receive a trigger message initiated by the SCS, an SCS-Identifier for the SCS, a Reference-Number AVP set to identify the trigger message and an Action-Type AVP set to a value to indicate a device trigger recall request to recall the trigger message;

receive a Device-Action-Answer (DAA) command from the MTC-IWF through the Tsp interface, the DAA command including a Device-Notification AVP having the UE identifier, the SCS-Identifier, the Reference-Number AVP, the Action-Type AVP and a Request-Status AVP set to a value to indicate success or failure of the device trigger recall request; and

determine the status of the device trigger replace request based on the value set in the request-status AVP.

13. The at least one non-transitory machine readable medium of claim 12, the Device-Action AVP having an assigned AVP code of 3001, the Reference-Number AVP having an assigned AVP code of 3007, the Action-Type AVP having an assigned AVP code of 3005, the Device-Notification AVP having an assigned AVP code of 3002 and the Request-Status AVP having an assigned AVP code of 3008.

14. An apparatus comprising:

a processor circuit for a service capability server (SCS) capable of operating in compliance with one or more 3^rd Generation Partnership Project (3GPP) Long Term Evolution (LTE) standards including LTE-Advanced (LTE-A);

an action component for execution by the processor circuit to send a Device-Action-Request (DAR) command to a machine type communication-interworking function (MTC-IWF) through a telecommunications service provider (Tsp) interface, the DAR command including a Device-Action attribute value pair (AVP) having an user equipment (UE) identifier to indicate an UE to receive a first trigger message initiated by the SCS, an SCS-Identifier for the SCS, an Action-Type AVP set to a value to indicate a device trigger replace request to replace the first trigger message with a second trigger message, a Reference-Number AVP set to identify the second trigger message and an Old-Reference-Number AVP set to identify the first trigger message;

a receive component for execution by the processor circuit to receive a Device-Action-Answer (DAA) command from the MTC-IWF through the Tsp interface, the DAA command including a Device-Notification AVP having the UE identifier, the SCS-Identifier, the Reference-Number AVP, the Action-Type AVP and a Request-Status AVP set to a value to indicate success or failure of the device trigger replace request; and

a status component for execution by the processor circuit to determine the status of the device trigger replace request based on the value set in the Request-Status AVP.

15. The apparatus of claim 14, the UE identifier including at least one of an External-Id or a mobile subscriber integrated services digital network-number (MSISDN).

16. The apparatus of claim 14, the Device-Notification AVP also having a Validity-Time to indicate a time for which the device trigger replace request is valid.

17. The apparatus of claim 14, the Device-Notification AVP also having a Trigger-Data AVP that includes a Payload having data to be sent to the UE with the second trigger message, a Priority-Indication for the second trigger message and an Application-Port-Identifier to identify a triggering application at the UE to receive the second trigger message.

18. The apparatus of claim 17, the Trigger-Data AVP having an assigned AVP code of 3003, the Payload having an assigned AVP code of 3004, the Priority-Indication having an assigned AVP code of 3006 and the Application-Port-Identifier having an assigned AVP code of 3010.

19. The apparatus of claim 14, the value to indicate the device replace request comprises the value set to 4.

20. The apparatus of claim 14, the value to indicate success or failure of the device trigger replace request comprises the value set to 0 for indicating success or the value set to 110 to indicate trigger replace failure or value set to 112 to indicated original trigger message already sent.

21. The apparatus of claim 20, the value to indicate success or failure of the device trigger replace request is set to 0, the MTC-IWF arrange to release a given identifier used by the SCS to identify the first trigger message based on the value set to 0, the release given identifier available to the SCS for a third trigger message to the UE or another UE.

22. The apparatus of claim 14, comprising a digital display coupled to the processor circuit to present a user interface view.

23. At least one non-transitory machine readable medium comprising a plurality of instructions that in response to being executed on a system for a machine type communication-interworking function (MTC-IWF) capable of operating in compliance with one or more or more 3^rd Generation Partnership Project (3GPP) Long Term Evolution (LTE) standards including LTE-Advanced (LTE-A) causes the system to:

receive a Device-Action-Request (DAR) command from a service capability server (SCS) through a telecommunications service provider (Tsp) interface, the DAR command including a Device-Action attribute value pair (AVP) having an user equipment (UE) identifier to indicate an UE to receive a first trigger message initiated by the SCS, an SCS-Identifier for the SCS, an Action-Type AVP set to a value to indicate a device trigger replace request to replace the first trigger message with a second trigger message, a Reference-Number AVP set to identify the second trigger message and an Old-Reference-Number AVP set to identify the first trigger message;

forward the device trigger replace request to a short message service-service center (SMS-SC);

determine a status of the device trigger replace request responsive to an indication from the SMS-SC of a success or failure to replace the first trigger message with the second trigger message; and

send a Device-Action-Answer (DAA) command to the SCS through the Tsp interface, the DAA command including a Device-Notification AVP having the UE identifier, the SCS-Identifier, the Reference-Number AVP, the Action-Type AVP and a Request-Status AVP set to a value to indicate success or failure of the device trigger replace request.

24. The at least one non-transitory machine readable medium of claim 23, the Device-Action AVP having an assigned AVP code of 3001, the Reference-Number AVP having an assigned AVP code of 3007, the Old-Reference-Number AVP having an assigned AVP code of 3011, the Action-Type AVP having an assigned AVP code of 3005, the Device-Notification AVP having an assigned AVP code of 3002 and the Request-Status AVP having an assigned AVP code of 3008.

25. The at least one non-transitory machine readable medium of claim 23, the value to indicate success or failure of the device trigger replace request comprises the value set to 0 for indicating success or the value set to 110 to indicate trigger replace failure or value set to 112 to indicated original trigger message already sent, the value to indicate success or failure of the device trigger replace request is set to 0, the instructions to further cause the system to release a given identifier used to identify the first trigger message based on the value set to 0.