Device trigger recall/replace feature for 3GPP/M2M systems

• US 9,554,296 B2
• Filed: 08/02/2013
• Issued: 01/24/2017
• Est. Priority Date: 08/03/2012
• Status: Active Grant

• Current Assignee: Apple Inc.
• Original Assignee: Intel Corporation
• Inventors: Rao, Varun, Jain, Puneet
• Primary Examiner(s): Sheikh, Ayaz
• Assistant Examiner(s): Ghafoerkhan, Faiyazkhan
• Application Number:
  US14/124,984
• Publication Number:
  US 20150181564A1
• Time in Patent Office: 1,271 Days
• Field of Search: None
• US Class Current: 1/1
• CPC Class Codes: H04B 17/27 for locating or positioning the transmitter
• CPC Class Codes: H04L 1/0013 Rate matching, e.g. puncturing or repetition of code symbols
• CPC Class Codes: H04L 41/0659 by isolating or reconfiguring faulty entities
• CPC Class Codes: H04L 41/082 the condition being updates or upgrades of network functionality
• CPC Class Codes: H04L 41/0836 to enhance reliability, e.g. reduce downtime
• CPC Class Codes: H04L 43/0811 by checking connectivity
• CPC Class Codes: H04L 45/306 Route determination based on the nature of the carried application
• CPC Class Codes: H04L 65/1104 Session initiation protocol [SIP]
• CPC Class Codes: H04L 65/613 for the control of the source by the destination control signals issued by the client directed to the server or network components specially adapted for selective content distribution H04N21/637
• CPC Class Codes: H04L 65/80 Responding to QoS
• CPC Class Codes: H04L 67/51 Discovery or management thereof, e.g. service location protocol [SLP] or web services
• CPC Class Codes: H04L 67/75 Indicating network or usage conditions on the user display
• CPC Class Codes: H04N 21/23439 for generating different versions
• CPC Class Codes: H04N 21/25825 involving client display capabilities, e.g. screen resolution of a mobile phone optimising the visualisation of content during browsing in the Internet G06F16/9577; processing of terminal status or physical abilities in wireless networks H04W8/22; authentication in wireless network security H04W12/06
• CPC Class Codes: H04W 12/06 Authentication
• CPC Class Codes: H04W 16/18 Network planning tools
• CPC Class Codes: H04W 16/28 using beam steering
• CPC Class Codes: H04W 24/02 Arrangements for optimising operational condition
• CPC Class Codes: H04W 24/04 Arrangements for maintaining operational condition
• CPC Class Codes: H04W 4/02 Services making use of location information
• CPC Class Codes: H04W 4/70 : Services for machine-to-machine communication [M2M] or machine type communication [MTC]
• CPC Class Codes: H04W 40/20 : based on geographic position or location
• CPC Class Codes: H04W 40/246 : Connectivity information discovery
• CPC Class Codes: H04W 48/14 : using user query or user detection
• CPC Class Codes: H04W 48/18 : Selecting a network or a communication service
• CPC Class Codes: H04W 52/00 : Power management, e.g. TPC [Transmission Power Control], power saving or power classes gain control in transmitters or power amplifiers H03G3/3042
• CPC Class Codes: H04W 52/0209 : in terminal devices terminal devices per se H04W88/02
• CPC Class Codes: H04W 52/0212 : managed by the network, e.g. network or access point is master and terminal is slave
• CPC Class Codes: H04W 52/0216 : using a pre-established activity schedule, e.g. traffic indication frame
• CPC Class Codes: H04W 52/0229 : where the received signal is a wanted signal
• CPC Class Codes: H04W 52/0258 : controlling an operation mode according to history or models of usage information, e.g. activity schedule or time of day
• CPC Class Codes: H04W 76/10 : Connection setup
• CPC Class Codes: H04W 76/11 : Allocation or use of connection identifiers
• CPC Class Codes: H04W 76/14 : Direct-mode setup
• CPC Class Codes: H04W 76/15 : Setup of multiple wireless link connections
• CPC Class Codes: H04W 76/16 : Involving different core network technologies, e.g. a packet-switched [PS] bearer in combination with a circuit-switched [CS] bearer
• CPC Class Codes: H04W 76/28 : Discontinuous transmission [DTX]; Discontinuous reception [DRX]
• CPC Class Codes: H04W 88/06 : adapted for operation in multiple networks or having at least two operational modes, e.g. multi-mode terminals
• CPC Class Codes: Y02D 30/70 : in wireless communication networks

Abstract

Embodiments for managing device trigger action requests are generally described herein. The device trigger action requests may include a recall or replacement Device-Action Request. In some embodiments, a Device-Action Request command is received at a network entry point node from an external services capability server with an action type attribute value pair set to indicate a device trigger action request for performing an action on an old device trigger request, the network entry point node determines a status of the old device trigger request from the external services capability server and the network entry point node sends a Device-Action Answer command to the external services capability server with a request-status type attribute value pair to report a status of the old device trigger request in response to the device trigger action request for performing an action on the old device trigger request.

Claims

1. A method for managing device trigger action requests, comprising:

receiving, at a network entry point node, a Device-Action Request command from an external services capability server with an action type attribute value pair set to indicate a device trigger action request for performing an action on an old device trigger request;

determining, by the network entry point node, a status of the old device trigger request from the external services capability server; and

sending, by the network entry point node, a response message to the external services capability server indicating a status of device trigger action request,

wherein the sending the response message comprises sending a Device-Action Answer command having a cause value set to report a status of the device trigger action request.

2. The method of claim 1, wherein the sending the Device-Action Answer command having a cause value set to report a status of the device trigger action request comprises sending a Device-Action Answer command having a cause value set to report success of a replace request for the old device trigger request, the old device trigger being replaced with a new trigger provided in the Device-Action Request.

3. The method of claim 1, wherein the sending the Device-Action Answer command having a cause value set to report a status of the device trigger action request comprises sending a Device-Action Answer command having a cause value set to report failure of a replace request for the old device trigger request, the old device trigger being requested to be replaced with a new trigger provided in the Device-Action Request.

4. The method of claim 1, wherein the sending the response message comprises sending a device trigger report associated with the old device trigger request indicating a status of the old device trigger request in response to the device trigger action request.

5. The method of claim 1, wherein the sending the response message comprises sending a device trigger confirm message having a cause value set to indicate the Device-Action Request exceeds a limitation on a parameter associated with the external services capability server.

6. The method of claim 1, further comprising sending from the network entry point node to a store and forward center, based on the Device-Action Request, a submit trigger replace request including an old device trigger reference number for identifying the old device trigger request and a new trigger reference number identifying a substitute trigger request.

7. The method of claim 6 further comprising receiving, at the network entry point node, one selected from a group consisting of:

a submit trigger replace response message indicating success or failure of the submit trigger replace request, and

a trigger delivery report associated with the old device trigger request from the store and forward center indicating the old device trigger request has been replaced.

8. The method of claim 1 further comprising sending from the network entry point node to a store and forward center, based on the Device-Action Request, a submit trigger recall request including an old device trigger reference number for identifying the old device trigger request.

9. The method of claim 8 further comprising receiving, at the network entry point node, a submit trigger recall response message indicating success or failure of the submit trigger recall request and a trigger delivery report associated with the old device trigger request from the store and forward center indicating the old device trigger request has been recalled.

10. The method of claim 1, wherein:

the receiving the Device-Action Request command with the action type attribute value pair set to indicate the device trigger action request comprises receiving a device trigger replace request, and

the method further comprises, in response to determining that the old device trigger request is pending at the network entry point node or has been unsuccessfully sent to a user equipment;

deleting the old device trigger request,

storing a new trigger request provided by the Device-Action Request command, and

delivering the new trigger request when the user equipment becomes available.

11. The method of claim 10, wherein the method further comprises:

determining, in response to determining that the old device trigger request has been successfully sent to the user equipment or the old device trigger request has expired, that the device trigger replace request has failed, and

after determining that the device trigger replace request has failed, delivering the new trigger request to the user equipment when the user equipment becomes available.

12. The method of claim 1, wherein:

the receiving the Device-Action Request command with the action type attribute value pair set to indicate the device trigger action request comprises receiving a device trigger recall request, and

the method further comprises, in response to determining that an old device trigger request is pending at the network entry point node or has been unsuccessfully sent to a user equipment;

deleting the old device trigger request,

de-registering from a user equipment reachability notification at a management database and considering that the old device trigger request has successfully been deleted, and

determining, in response to determining that the old device trigger request has been successfully sent to the user equipment or the old device trigger request has expired, that the device trigger recall request has failed.

13. A network entry point node, comprising:

a transceiver arranged to establish a connection with core network entities and an external services capability server providing machine type communication for user equipment supported by the core network entities, the transceiver arranged to receive a Device-Action Request command from an external services capability server with an action type attribute value pair set to indicate a device trigger action request for performing an action on an old device trigger request; and

a processor arranged to determine a status of the old device trigger request from the external services capability server and to send a response message to the external services capability server indicating status of device trigger action request,

wherein the response message comprises one selected from a group comprising;

a Device-Action Answer command having a cause value set to report a status of the device trigger action request,

a device trigger report associated with the old device trigger request indicating a status of the old device trigger request in response to the device trigger action request, and

a device trigger confirm message having a cause value set to indicate the Device-Action Request exceeds a limitation on a parameter associated with the external services capability server.

14. The network entry point node of claim 13, wherein the response message comprises a Device-Action Answer command having a cause value set to report a status of the device trigger action request.

15. The network entry point node of claim 14, wherein the Device-Action Answer command comprises:

a cause value set to report success of a recall request for the old device trigger request when the old device trigger request is deleted,

a cause value set to report failure of the recall request for the old device trigger request when the old device trigger request has been successfully delivered to a user equipment or has already expired,

a cause value set to report success of a replace request for the old device trigger request when the old device trigger request is replaced with a new trigger request provided in the Device-Action Request, and

a cause value set to report failure of the replace request for the old device trigger request when the old device trigger request has been successfully delivered to a user equipment or has already expired, the old device trigger request being requested to be replaced with the new trigger request provided in the Device-Action Request.

16. The network entry point node of claim 13, wherein the response message comprises one selected from a group comprising:

a device trigger report associated with the old device trigger request indicating a status of the old device trigger request in response to the device trigger action request, and

a device trigger confirm message having a cause value set to indicate the Device-Action Request exceeds a limitation on a parameter associated with the external services capability server.

17. The network entry point node of claim 13, wherein the processor is arranged to:

send to a store and forward center send via the transceiver, based on the Device-Action Request;

a submit trigger replace request including an old device trigger reference number for identifying the old device trigger request and a new trigger reference number identifying a substitute trigger request, and

a submit trigger recall request including the old device trigger reference number for identifying the old device trigger request, and

receive via the transceivers;

a submit trigger replace response message indicating success or failure of the submit trigger replace request,

a submit trigger recall response message indicating success or failure of the submit trigger recall request, and

a trigger delivery report associated with the old device trigger request from the store and forward center indicating the old device trigger request has been recalled.

18. The network entry point node of claim 13, wherein the processor is arranged to:

process a received device trigger replace request, and in response to determining that an old device trigger request is pending at the network entry point node or has been unsuccessfully sent to a user equipment;

delete the old device trigger request,

store a new trigger request provided by the Device-Action Request command, and

deliver the new trigger request when the user equipment becomes available.

19. The network entry point node of claim 18, wherein the processor is further arranged to:

determine, when the old device trigger request has been successfully sent to the user equipment or the old device trigger request has expired, that the device trigger replace request failed, and

after determining that the device trigger replace request has failed, deliver the new device trigger request to the user equipment when the user equipment becomes available.

20. The network entry point node of claim 13, wherein the processor is arranged to:

process a received device trigger recall request, and in response to determining that an old device trigger request is pending at the network entry point node or has been unsuccessfully sent to a user equipment;

delete the old device trigger request,

de-register from a user equipment reachability notification at a management database when the old device trigger request has successfully been deleted, and

determine that the device trigger recall request failed when the old device trigger request has been successfully sent to the user equipment or the old device trigger request has expired.

21. At least one non-transitory machine readable medium comprising instructions that, when executed by the machine, cause the machine to perform operations for managing device trigger action requests, the operations comprising:

receiving, at a network entry point node, a Device-Action Request command from an external services capability server with an action type attribute value pair set to indicate a device trigger action request for performing an action on an old device trigger request;

determining, by the network entry point node, a status of the old device trigger request from the external services capability server; and

sending, by the network entry point node, a response message to the external services capability server indicating status of device trigger action request,

wherein the sending the response message comprises;

sending a device trigger report associated with the old device trigger request indicating a status of the old device trigger request in response to the device trigger action request, and

sending a device trigger confirm message having a cause value set to indicate the Device-Action Request exceeds a limitation on a parameter associated with the external services capability server.

22. The at least one non-transitory machine readable medium of claim 21, wherein:

the sending the response message comprises sending a Device-Action Answer command having a cause value set to report a status of the device trigger action request, and

the sending the Device-Action Answer command having a cause value set to report a status of the device trigger action request further comprises;

sending a Device-Action Answer command having a cause value set to report success of a recall request for the old device trigger request,

sending a Device-Action Answer command having a cause value set to report failure of the recall request for the old device trigger request,

sending a Device-Action Answer command having a cause value set to report II all success of a replace request for the old device trigger request, the old device trigger being replaced with a new device trigger provided in the Device-Action Request, and

sending a Device-Action Answer command having a cause value set to report failure of the replace request for the old device trigger request, the old device trigger being requested to be replaced with a new device trigger provided in the Device-Action Request.

23. The at least one non-transitory machine readable medium of claim 21 further comprising:

sending from the network entry point node to a store and forward center, based on the Device-Action Request, a submit trigger replace request including an old device trigger reference number for identifying the old device trigger request and a new device trigger reference number identifying a substitute trigger request,

receiving, at the network entry point node, a submit trigger replace response message indicating success or failure of the submit trigger replace request, and

receiving, at the network entry point node, a trigger delivery report associated with the old device trigger request from the store and forward center indicating the old device trigger has been replaced.