Browse Prior Art Database

SMS/MMS Recall

IP.com Disclosure Number: IPCOM000022701D
Original Publication Date: 2004-Mar-25
Included in the Prior Art Database: 2004-Mar-25
Document File: 8 page(s) / 287K

Publishing Venue

Motorola

Abstract

If a mobile subscriber wants to recall the SMS/MMS request he/she has sent, it can not be done as the current SMS/MMS feature doesn’t support the recall mechanism. In this paper a method to recall SMS/MMS request is devised, which will be available on subscriber devices (inclusive of all messaging entities having SMS/MMS sending/receiving capability) and the delivery elements like SMSC/SMSN and MMS Server, which will enable a service of recalling an already sent Short/Multimedia message

This text was extracted from a Microsoft Word document.
At least one non-text object (such as an image or picture) has been suppressed.
This is the abbreviated version, containing approximately 32% of the total text.
SMS/MMS Recall

(Recalling MS/POTS/other Messaging Entities originated and terminated

Short/Multimedia messages)

N Sateendar - a16214 ( sateendar@motorola.com )

Motorola India Electronics Ltd. ( GSG – INDIA )

H.No. 6-3-1090, TSR Towers

Raj Bhavan Road, Somaji Guda

HYDERABAD – 500082, A.P., INDIA

Ph: # 91-40-23308090

Abstract

If a mobile subscriber wants to recall the SMS/MMS request he/she has sent, it can not be done as the current SMS/MMS feature doesn’t support the recall mechanism. In this paper a method to recall SMS/MMS request is devised, which will be available on subscriber devices (inclusive of all messaging entities having SMS/MMS sending/receiving capability) and the delivery elements like SMSC/SMSN and MMS Server, which will enable a service of recalling an already sent Short/Multimedia message

Problem

  • An SMS Request has been sent from source MS/POTS to destination MS/POTS/other Short Message Entities and source unit wants to recall the same
  • Short Message Entities (non MS/POTS) which broadcasts advertisements, availability of new features etc to different destinations(MS/POTS), wants to do a mass recall
  • Existing MS/POTS/Short Message Entities do not support SMS Recall functionality
  • An MMS request has been sent by an MMS Client and it wants to recall the same
  • Existing Multimedia Messaging Entities do not support MMS Recall functionality

Solution

 
The solution is being explained in two separate parts.

  • SMS recall
  • MMS recall

SMS Recall

The general SMS context diagram and brief functionality of the corresponding boxes is given below.

               
   

HLR

 
 
     
 

SME

 
 
     
 

SME

 
 
 
 

 


  • SME – Short message entity , to receive or send short messages. It may be located in a fixed network, a mobile station or another service center.
  • SMSC – Short Message Service Center, responsible for relay , store & forward a short message between SME and Mobile station
  • SMSN – Short Message Service Node, provides connection to other wireless networks.

(exists between Plain Old Telephone System and other destinations)

  • MS – Mobile Station ( Mobile Device )
  • POTS – Plain Old Telephone System

When a subscriber recalls an SMS request, the following things will take place.

 

  • Deletion of SMS Requests at SMSC / SMSN if they are not already delivered to the destination ( delivery failure or queued )
  • If SMSC / SMSN already delivered SMS Requests, it still sends the “recall request” to the destination ( MS / POTS / any other SME )
  • At the destination(MS/POTS/other SME), if the Short Message for which recall request received is unread still, it will get deleted before it is read
  • At the destination(MS/POTS/other SME), if the Short Message is read already, relevant action will be performed ( described in flow diagram )

To enable SMS Recall functionality, MS/POTS/other SME & SMSC/SMSN need to exchange two new control messages, “recall_sm” & “recall_sm_resp” (formats given below) . The flow diagrams showing the above operations are also given, following the message formats.

SMS recall mes...