Read Receipt for Short Messages
Permalink
Bookmark
Share
Twitter
Digg
Reddit
Facebook
Stumbleupon
Del.icio.us| IP.com Number | IPCOM000139432D |
|
|
|---|---|---|---|
| Dated | Sep 25, 2006 UTC | ||
| Size | 1 page(s) (32.6 KB) | ||
| Disclosed by |
|
||
Publication Summary
Currently the sender of Short Messages (e.g. SMS) only gets a delivery report for the message but not a read receipt. The following idea gives a technical solution for the implementation of sending read receipts for short messages: If subscriber A sends a Short Message to subscriber B, the message is first send to SMSC (SMSC, Short Message Service Center) of subscriber A. The optional element "Read Receipt Required" has to be integrated into mobiles. If "Read Receipt Required" is selected, this order will be sent to the SMS-GMSC (GMSC, Gateway Mobile Switching Centre). After receiving the SMS and the "Read Receipt Required" order, the SMS-GMSC triggers a USSD (USSD, Unstructured Supplementary Services) notification towards subscriber B. This USSD notification only includes information, that a read receipt is required. The mobile of subscriber B receives the USSD notification, processes and stores the incoming information from subscriber A. Once the message is read by subscriber B, his mobile initiates a SMS-Command-PDU (PDU, Protocol Data Unit) to the SMSC of subscriber B automatically. Subscriber B has the choice of triggering the SMS-Command-PDU after reading the message. The SMSC of subscriber A now triggers a short message towards subscriber A that includes a written "read receipt". Subscriber B shall not be charged for the read receipt SMS.| Country | India |
|---|---|
| Language | English (United States) |
| Related Person(s) |
(CONTACT) Juergen Carstens |
| Copyright | SIEMENS AG 2006 |
About this Publication
This document was submitted to IP.com's Prior Art Database and this preview is designed to provide you with information regarding the contents of this document by displaying up to the first four pages of the document as scaled page renderings and displaying a limited amount of text which was extracted from the document on the Text Preview Tab.
To find out more on how to obtain the entire document, click the Download tab. There is a charge for downloading some Prior Art Database documents; please examine carefully whether you believe this document fills your needs before purchasing.
For more information about the Prior Art Database, visit the Learn section of this website. Thank you for visiting IP.com's Prior Art Database! You may wish to check out our Global Patent Search website before you leave.
S
Read Receipt for Short Messages
Idea: Aman Sharma, IN-Bangalore
Currently the sender of Short Messages (e.g. SMS) only gets a delivery report for the message but not a read receipt. The following idea gives a technical solution for the implementation of sending read receipts for short messages:
If subscriber A sends a Short Message to subscriber B, the message is first send to SMSC (SMSC, Short Message Service Center) of subscriber A. The optional element "Read Receipt Required" has to be integrated into mobiles. If "Read Receipt Required" is selected, this order will be sent to the SMS- GMSC (GMSC, Gateway Mobile Switching Centre). After receiving the SMS and the "Read Receipt Required" order, the SMS-GMSC triggers a USSD (USSD, Unstructured Supplementary Services) notification towards subscriber B. This USSD notification only includes information, that a read receipt is required. The mobile of subscriber B receives the USSD notification, processes and stores the incoming information from subscriber A. Once the message is read by subscriber B, his mobile initiates a SMS-Command-PDU (PDU, Protocol Data Unit) to the SMSC of subscriber B automatically. Subscriber B has the choice of triggering the SMS-Command-PDU after reading the message. The SMSC of subscriber A now triggers a short message towards subscriber A that includes a written "read r...