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

US9301083B2 · US · B2

Patent metadata
FieldValue
Publication numberUS-9301083-B2
Application numberUS-201414483620-A
CountryUS
Kind codeB2
Filing dateSep 11, 2014
Priority dateJan 6, 2014
Publication dateMar 29, 2016
Grant dateMar 29, 2016

How to read this patent

A practical reading order for non-experts. Skip the full description unless you need deep technical detail.

  1. Title

    What the patent document calls the invention.

  2. Abstract

    A short plain-language summary of the technical disclosure.

  3. Assignees and inventors

    Who owns or filed the patent and who is credited as inventor.

  4. Key dates

    Filing, priority, publication, and grant dates set the timeline.

  5. First independent claim

    The legal scope of protection — read this for what is actually claimed.

  6. CPC / IPC classifications

    Technology tags used to group this patent with similar filings.

  7. Citations and related patents

    Prior art links and similar publications in this corpus.

Abstract

Official abstract text for this publication.

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.

First claim

Opening claim text (preview).

What is claimed is: 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 p

Assignees

Inventors

Classifications

  • H04W4/12Primary

    Messaging; Mailboxes; Announcements · CPC title

  • Processing or transfer of terminal data, e.g. status or physical capabilities · CPC title

  • H04W4/005Primary

    Electricity · mapped topic

  • Provisioning of proxy services (store-and-forward switching systems in data switching networks H04L12/54) · CPC title

  • H04L67/125Primary

    involving control of end-device applications over a network · CPC title

Patent family

Related publications grouped by family.

External sources

Frequently asked questions

Answers are generated from the same data shown on this page.

What does patent US9301083B2 cover?
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 devic…
Who is the assignee on this patent?
Intel Ip Corp
What technology area does this patent fall under?
Primary CPC classification H04W4/12. Mapped technology areas include Electricity.
When was this patent published?
Publication date Tue Mar 29 2016 00:00:00 GMT+0000 (Coordinated Universal Time) (B2). Legal status and post-grant events are not shown on this page.
What related patents are in patentsdb?
We list 1 related publication on this page (citations in our corpus or others sharing the same primary CPC).