Title of Invention

METHOD FOR POST DATING A SHORT MESSAGING SERVICE (SMS) MESSAGE IN A WIRELESS TELECOMMUNICATION SYSTEM

Abstract A method and system for Post Dated / deferred SMS with Network side support is explained in the present invention. If the SMS sender wants some message to be delayed / deferred or if he/she wants to send the message repeatedly in a periodic or non periodic interval, the message is stored in a Short Message Service Center (SMSC). The network should have a specific storage allocation for the SMS sender. The SMSC forwards the message to the mobile station at the predetermined time as specified. Implementation of the system uses a new User Data Header to achieve this functionality, which has the deferred date, time, frequency & other information which can be predetermined by the sender.
Full Text FIELD OF INVENTION
The present invention, in general, relates to the wireless telecommunications field and, in particular, to the forwarding of short text messages to mobile subscribers in a cellular communications system. More particularly, the present invention relates to a system and method for Post Dated / deferred SMS with Network side support.
DESCRIPTION OF RELATED ART
The SMS enables the mobile networks to route short text messages, each up to 160 alphanumeric characters long, over the signaling channels to or from mobile stations. If the SMS sender wants some message to be delayed / deferred or if he/she wants to send the message repeatedly in a periodic or non periodic interval, the message is stored in a Short Message Service Center (SMSC). The SMSC forwards the message to the mobile station at the pre-determined time as specified.
At the present scenario SMS is sent immediately to the SMS receiver's User Equipment (UE). There is no network side implementation so that the delivery can be delayed / deferred at the SMSC, till a pre determined time.
Without the concept of post dated / deferred SMS at the network side (this has neither been implemented in 3GPP nor in 3GPP2), a user would not be able to send an SMS at a later date / time and / or with a prescribed frequency (such as weekly, daily, monthly, etc.)
LIMITATIONS
However the post dated / deferred SMS concept is now being implemented at the UE itself, which has certain limitations some of which are listed below:
1) If the Sender is on roaming, he will be charged as per the roaming charges,
2

which will be usually higher than the normal charges.
2) If the UE is not in the coverage area, then the very purpose would not be served.
SUMMARY OF THE INVENTION
The primary objective of this invention is, therefore, to provide a system and method for facilitating post dated / deferred SMS implemented from the network. The present invention provides for post dated / deferred SMS implementation in 3GPP networks, where the network has the flexibility to and provides to the sender the option of configuring the specific time and date, when the SMS is to be sent including the details such as how often the message has to be send (whether daily, weekly, etc.).
The network should have a specific storage allocation for the SMS sender, until the network sends to the final recipient on the scheduled day / time. Accordingly, the invention proposed herein, on implementation, would be a fair source of income for the operator and would provide flexibility to the user. The present invention would provide for sending of SMS even if the sender’s UE is switched off at the particular instance of the message being sent by the network. Further, if the user is on Roaming mode, the charges would be comparatively higher than being able to set up a network based deferred SMS before the user leaves the home network.
Accordingly this invention explains a method for facilitating post dated / deferred SMS implementation in network wherein the network has the flexibility to and provides to a sender the option of configuring a specific time and date, when the SMS is to be sent including the details such as how often the message has to be send. The network has a specific storage allocation for the SMS sender.
Accordingly, this invention explains a method for facilitating post dated / deferred
3

SMS implementation using the 3GPP protocol comprising the steps of:
(a) achieving the functionality of deferred date, time, frequency and other information implementation using a new User Data Header; and
(b) achieving the functionality of deferred date, time, frequency and other information implementation using the reserved values & different interpretation of Validity period.
Once a Post dated SMS is submitted, the sender can request the network to delete any Post dated SMS from its storage and after submitting the Post Dated SMS, the sender can fetch any of the already submitted Post Dated SMS from the network & modify it & submit it again to the network with a same reference id. Fetching the Post Dated SMS from the network is based on the TP-MR where the network should have a method for the indication when the Post Dated SMS limit has been reached. Fetching the Post Dated SMS is achieved by getting the entire UDH corresponds to some valid TP-MR, which is stored in the UE or by some notification sent by the server.
The fields used for the implementation are:
1) Validity Period (TP-VP)
2) Protocol Identifier (TP-PID)
3) Some modifications in the SMS_SUBMIT
4) Command Type (TP-CT) in the SMS_COMMAND and
5) Message Number (TP-MN).
The Validity Period (TP-VP) is used by the network to mention the deferred date, time. The Protocol Identifier (TP-PID) consists of a pool of reserved values where a new Protocol Identifier, can denote a Post - dated message. The SMS_SUBMIT includes modifications which includes modifications in
a) TP-RD (Reject duplicates) for modifying the post dated message;
b) TP-SRR (Status report) fields;
c) Validity period and
4

d) Validity-Period-Format (TP-VPF).
SMS-SUBMIT TPDU includes parameters:
TP-Message-Type-Indicator;
TP-Reject-Duplicates;
TP-Validity-Period-Format;
TP-Reply-Path;
TP-User-Data-Header-Indicator;
TP-Status-Report-Request;
TP-Message-Reference;
TP-Destination-Address;
TP-Protocol-Identifier;
TP-Data-Coding-Scheme;
TP-Validity-Period;
TP-User-Data-Length; and
TP-User-Data.
wherein SMS_COMMAND includes changes in parameters:
TP-Message-Type-Indicator
TP-User-Data-Header-Indication;
TP-Status-Report- Request; TP-Message Reference;
TP-Protocol- Identifier;
TP-Command-Type;
TP-Message-Number;
TP-Destination-Address;
TP-Command-Data-Length; and
TP-Command-Data.

5

TP-Validity Period comprises 7 octets and the first octet indicates the way in which the following 6 octets are used where Octet 1 is TP-VP functionality indicator having:
Bit 7 as Extension bit;
Bit 6 as Single shot SM;
Bits 5, 4, 3 kept Reserved; and
Bits 2, 1, 0 as Validity Period Formats.
The TP-MN (Message Number) is the value of Message, which is supposed to be deleted or modified. For DELETING already sent Post Dated SMS, SMS_COMMAND packet shall be sent which can have the User Data - the TP-MR of the message which is to be deleted. Where a TP-Command is to delete any already submitted Post Dated short message Known by the combination of TP-CT, TP-MN, the SC shall send a Status Report indicating that the SM has been deleted if the original Submit SM request, requested a status Report. For MODIFYING already sent Post Dated SMS, first DELETING Step is performed then Clear it from the ME and then perform steps required for Adding.
Accordingly, this invention further explains a method of facilitating post dated / deferred SMS implementation in network using a new User Data Header where the fields used for the implementation are:
1) Validity Period (TP-VP);
2) Protocol Identifier (TP-PID);
3) Some modifications in the SMS_SUBMIT;
4) A new UDH. (TP-UD);
5) TP-Command Type (TP-CT) in the SMS_COMMAND; and
6) Message Number (TP-MN).
6

The Validity Period (TP-VP) for the new implementation is set to MAXIMUM. The Protocol Identifier (TP-PID) consist of a pool of reserved values were any one value represent a new Protocol Identifier, which can denote a Post - dated message. The SMS_SUBMIT includes modifications which includes modifications in:
TP-RD (Reject duplicates);
TP-UDHI (User-Date-Header-Indicator) field;
TP-SRR (Status report) fields;
Data compression needs; and
New UDH data.
The new UDH (TP-UD) includes parameters:
DATA ENCODING SCHEME PRESENT;
REOCCURRENCE; REOCCURRENCEFREQ;
DATA ENCODING SCHEME;
SENDING DATE; SENDING TIME;
MESSAGEID;
MESSAGE RETENTION DAYS; and
MESSAGE LENGTH.
Changes in SMS_COMMAND includes changes in parameter
TP-Message-Type-Indicator
TP-User-Data-Header-Indication;
TP-Status-Report- Request; TP-Message Reference;
TP-Protocol- Identifier;
TP-Command-Type; TP-Message-Number;
TP-Destination-Address;
7

TP-Command-Data-Length;
and TP-Command-Data.
Accordingly, this invention further explains a system for facilitating post dated deferred SMS implementation in network wherein the network has the flexibility to and provides to a sender the option of configuring a specific time and date, when the SMS is to be sent including the details such as how often the message has to be send.
These and other objects, features and advantages of the present invention will become more apparent from the ensuing detailed description of the invention taken in conjunction with the accompanying drawings.
DETAILED DESCRIPTION OF THE INVENTION
The preferred embodiments of the present invention will now be explained with reference to the accompanying drawings. It should be understood however that the disclosed embodiments are merely exemplary of the invention, which may be embodied in various forms. The following description and drawings are not to be construed as limiting the invention and numerous specific details are described to provide a thorough understanding of the present invention, as the basis for the claims and as a basis for teaching one skilled in the art how to make and/or use the invention. However in certain instances, well-known or conventional details are not described in order not to unnecessarily obscure the present invention in detail.
Post dated SMS implementation is done using the 3GPP protocol. Implementation uses a new User Data Header to achieve this functionality, which has the deferred date, time, frequency (no. of times to be sent by network automatically) & other information. It can also be achieved using the reserved values & different interpretation of Validity period where the deferred date, time frequency (no. of
8

times to be sent by network automatically) & other information. Once the Post dated SMS is submitted, the sender can request the network to delete any Post dated SMS from its storage. After submitting the Post Dated SMS, the sender can fetch any of the already submitted Post Dated SMS from the network & modify it & submit it again to the network with the same reference id.
Fetching the Post Dated SMS from the network can be based on the TP-MR (Message Reference). Network should have a method for the indication when the Post Dated SMS limit has been reached. Fetching the Post Dated SMS can be achieved by getting the entire UDH corresponds to some valid TP-MR, which is stored in the UE. It can also be fetched by some notification sent by the server, for example, the same way as a WAP push for MMS (Multimedia Messaging Service) indication. Network should able to delete all the Post Dated SMS, on the request raised by the sender. Post Dated SMS can be used for giving Wake up calls also.
An attempt has been made hereunder to illustrate the working of the present invention trying in a 3GPP scenario based on TS 23.040 specification. This illustration explains the implementation of the present invention in 3GPP. Similar implementation is possible in 3GPP2 technology also.
In 3GPP, the following fields can be used for the implementation of this invention.
7) Validity Period (TP-VP)
8) Protocol Identifier (TP-PID)
9) Some modifications in the SMS_SUBMIT
10) Command Type (TP-CT) in the SMS_COMMAND
11) Message Number (TP-MN)
The following section explains the in fields in detail.
2) Validity Period (TP-VP) - This should be used by the network to mention the deferred date, time. Its value can be 05 H. (A reserved value). The
9

interpretation of this is explained later in this document.
3) Protocol Identifier (TP-PID) - There is a pool of reserved values (starting from 01001000 - 01011101). We can take any one value say (48H) as a new Protocol Identifier, which can denote a Post - dated message.
4) Few modifications in SMS_SUBMIT - These modifications can include
a) TP-RD (Reject duplicates) can be set to 0, because the maximum number of message possible are 28-1 (255), & user can modify the post dated message.
b) TP-SRR (Status report) fields should be set to 1
c) Validity period - Using the reserved values, so that it can be interpreted in enhanced format.
d) Validity-Period-Format (TP-VPF) - The value will be 01H, i.e. enhanced format.
SMS-SUBMITTPDU
10





TP-VP (Enhanced format)
The TP-Validity Period comprises 7 octets. The presence of all octets is mandatory although they may not all be used. The first octet indicates the way in which the following 6 octets are used. Any reserved/unused bits or octets must be set to zero.
Octet 1 TP-VP functionality indicator
Bit 7 - Extension bit
Set to 1 if the TP-VP functionality indicator is to be extended to another octet. A setting of 0 indicates that there are no more TP-VP functionality indicator extension octets to follow. Any such extension octet shall immediately follow the previous TP-VP functionality indicator.
Bit 6 - Single shot SM
Set to 1 if the SC is required to make up to one delivery attempt. The TP-Validity Period, where present, shall be applicable to the Single shot SM.
12

Bits 5, 4, 3 - Reserved
Bits 2, 1, 0 -Validity Period Formats.
Value 2 1 0
bits
0 0 0 No Validity Period specified
0 0 1 Validity Period is as specified for the relative case. The following octet contains the TP-VP value as described in 9.2.3.12.1
0 1 0 Validity period is relative in integer representation and the following octet contains the TP-VP value in the range 0 to 255 representing 0 to 255 seconds. A TP-VP value of zero is undefined and reserved for future use.
0 1 1 Validity period is relative in semi-octet representation. The following 3 octets contain the relative time in Hours, Minutes and Seconds giving the length of the validity period counted from when the SMS-SUBMIT is received by the SC. The representation of time uses the same representation as the Hours, Minutesand Seconds in the TP-Service-Centre-Time-Stamp.
1 0 0 Reserved
1 0 1 Reserved
1 1 0 Reserved
1 1 1 Reserved
The SC shall reject any Unsupported/ Reserved values received by returning the TP-VP not supported' TP-FCS value in the Submit SM Report for RP-Error
13

The Octet 1 will have:

The frequency is determined by bit 3,4,5.
Bit 3 Bit 4 Bit 5
0 0 1 Daily
0 1 0 Every week same day (After Every 7 days)
0 1 1 Bi weekly
1 1 1 INVALID Message..
Other values Reserved
Octet 2 will have the value 244. Which will be interpreted as 52 weeks? This is the relative format (which is suggested by Octet 1 - Bit 1, 2 with the values 0, 1 respectively.)
Octet 3, 4, 5 will be used to mention - DD, MM, YY
Octet 6, 7 will be used to mention HH:MM (in 24hrs format).
5) Changes in SMS_COMMAND
14




6) TP-MN (Message Number) - In Case of Post Dated SMS, TP-sMessage-Number should be the value of Message, which is supposed to be deleted or modified.
One example how the Post dated SMS can be added/modified/deleted...
Ø For ADDING new postdated SMS, The new TP-PID (similar sto SMS_SUBMIT packet) shall have the following changes.
v Octet 1: Bit 2 (TP - RD) - Set to 0. (Reject Duplicates = 0).
v Octet 1: Bit 3,4(TP - VPF) - Set to 01 (Enhanced Format).
v Octet 1: Bit 5 (TP - SRR) - Set to 1.( Status Report Request = 1)
v Octet 1: Bit 6 (TP - UDH) - Set to 0. ( User Date Header Present)
v New TP-PID value:-Set to 48 H
Once SMS-SUBMIT has been sent, the UE should store the Post Dated SMS in the sent folder with the TP-MR as the unique identifier.
If UE receives RP-ERROR, then the Post Dated SMS which is just now stored in the Sent folder should be deleted.
16

If UE receives RP-ACK, it shows that the network has received the SMS.
Ø For DELETING already sent Post Dated SMS, SMS_COMMAND packet shall be sent which can have the User Data - the TP-MR of the message which I want to delete (Taking the Reference from the Post Dated SMS, stored in the ME and TP-CT (Command Type) can be 04H (the Reserved value).
Ø In the case where the case where a TP-Command is to Delete any already submitted Post Dated short message (Known by the combination of TP-CT, TP-MN, the SC shall send a Status Report indicating that the SM has been deleted if the original Submit SM request requested a status Report
Ø For MODIFYING already sent Post Dated SMS, First perform DELETING Steps. Clear it from the ME also & then perform steps required for Adding.
Alternatives
This is an alternative implementation, which uses a new User Data Header. It gives the flexibility to have more features in the future.
6) Validity Period (TP-VP)
7) Protocol Identifier (TP-PID)
8) Some modifications in the SMS_SUBMIT
9) A new UDH. (TP-UD)
10)TP-Command Type (TP-CT) in the SMS_COMMAND
12)Message Number (TP-MN)
a. Validity Period (TP-VP) - For the new implementation, this value can be set to MAXIMUM.
b. Protocol Identifier (TP-PID) - There is a pool of reserved values
17

(starting from 01001000 - 01011101). We can take any one value say (48H) as a new Protocol Identifier, which can denote a Post - dated message.
c. Few modifications in SMS_SUBMIT - These modifications can include
i. TP-RD (Reject duplicates) can be set to 0, because the maximum
number of message possible are 28-1 (255), & user can modify the
post dated message, so duplicates are possible,
ii. TPJJDHI (User-Date-Header-Indicator) field should be set to 1, because we include a new UDH, which contains the necessary
information for the post dated message,
iii. TP-SRR (Status report) fields should be set to 1 iv. If any data compression needs to be acted upon the message, that also is very well possible
v. New UDH data.
d. A new UDH. (TP-UD) –
18


DATA ENCODING SCHEME PRESENT - This parameter shall be set to ZERO to specify that there is no Data encoding scheme is used.
REOCCURRENCE - This parameter shall be set to ZERO if the message has to be sent
only ONCE, ie. On the date specified.
REOCCURRENCEFREQ - If the REOCCURRENCE
bit is set to ONE, then the REOCCURRENCEFREQ will tell what the frequency is:
Bit 7 6 5 Meaning
0 0 1 Daily
0 1 0 every week same day (After
Every 7 days)

19

0 1 1 Biweekly
1 1 1 INVALID Message.
Other values Reserved
DATA ENCODING SCHEME If the DATA ENCODING SCHEME PRESENT bit is set to ONE, then this octet, will mention the type of encoding scheme used. It must be as per the specification, which is already in use.
SENDING DATE - The final delivery date In absolute format.
SENDING TIME - The exact Time (Optional), HH:MM format
MESSAGEID - The Message Reference value.
MESSAGE RETENTION DAYS - Validity Period (in Days) - SEND
DATE (in days), will be in term of total no of days. If the REOCCURRENCE FREQ is 1, then this value remains intact, if REOCCURRENCE FREQ is 2, MESSAGE RETENTION DAYS /= 7; if REOCCURRENCE FREQ is 3, MESSAGE RETENTION DAYS /= 14; Once the Message RETENTION DAYS . Once This value becomes ZERO. Stop sending further. Do not delete from the SERVER. Once the Validity Period is EXPIRED, the ME and the SERVER

20



should clean it up. Otherwise the DELETE should happen when the ME triggers the DELETE / MODIFY.
MESSAGE LENGTH - The message length.
7) Changes in SMS_COMMAND

21





8) TP-MN (Message Number) - In Case of Post Dated SMS, TP-Message-Number should be the value of Message, which is supposed to be deleted or modified.
One example how the Post dated SMS can be added/modified/deleted...
Ø For ADDING new post dated SMS, The new TP-PID (similar to SMS_SUBMIT packet) shall have the following changes.
v Octet 1: Bit 5 (TP - SRR) - Set to 1.( Status Report Request = 1)
v Octet 1: Bit 6 (TP - UDH) - Set to 1.( User Date Header Present)
v Octet 1: Bit 2 (TP - RD) - Set to 0. (Reject Duplicates = 0).
v New TP-PID value:-Set to 48 H
Once SMS-SUBMIT has been sent, the UE should store the Post Dated SMS in the sent folder with the TP-MR as the unique identifier.
If UE receives RP-ERROR, then the Post Dated SMS which is just now stored in the Sent folder should be deleted.
23

If UE receives RP-ACK, it shows that the network has received the SMS.
Ø For DELETING already sent Post Dated SMS, SMS_COMMAND packet shall be sent which can have the User Data - the TP-MR of the message which I want to delete (Taking the Reference from the Post Dated SMS, stored in the ME and TP-CT (Command Type) can be 04H (the Reserved value).
Ø In the case where a TP-Command is to Delete, any already submitted Post Dated short message (Known by the combination of TP-CT, TP-MN, the SC shall send a Status Report indicating that the SM has been deleted if the original Submit SM request requested a status Report
For MODIFYING already sent Post Dated SMS, First perform DELETING Steps. Clear it from the ME also & then perform steps required for Adding.
ADVANTAGES
a) Backward compatibility - As per the TS 23.040, Section 9.2.3.9
“The MS will interpret reserved or unsupported values as the value 00000000 but shall store them exactly as received. The SC may reject messages with a TP-Protocol - Identifier containing a reserved value or one which is not supported”
So the backward compatibility is achieved.
b) Interoperability ensured.
c) Value added service for the operator, so it’s a source of income.
d) Flexibility for the user, a good experience.
e) Considerably beneficial, when the user is in roaming or out of coverage area.
f) Even if the sender's mobile is switched off, there won’t be any problem.

24

It will also be obvious to those skilled in the art that other control methods and apparatuses can be derived from the combinations of the various methods and apparatuses of the present invention as taught by the description and the accompanying drawings and these shall also be considered within the scope of the present invention. Further, description of such combinations and variations is therefore omitted above. It should also be noted that the host for storing the applications include but not limited to a microchip, microprocessor, handheld communication device, computer, rendering device or a multi function device.
Although the present invention has been fully described in connection with the preferred embodiments thereof with reference to the accompanying drawings, it is to be noted that various changes and modifications are possible and are apparent to those skilled in the art. Such changes and modifications are to be understood as included within the scope of the present invention as defined by the appended claims unless they depart there from.

25

GLOSSARY OF TERMS AND DEFINITIONS THEREOF
ME - Mobile Equipment – The equipment used to send the SMS
UE - User Equipment
SMS - Short Message Service
UDH - User Data Header
SC - Service Centre

Documents:

0316-che-2006 abstract duplicate.pdf

0316-che-2006 claims duplicate.pdf

0316-che-2006 description(complete) duplicate.pdf

0316-che-2006 drawings duplicate.pdf

316-CHE-2006 CORRESPONDENCE OTHERS 18-01-2013.pdf

316-CHE-2006 CORRESPONDENCE OTHERS 10-04-2013.pdf

316-CHE-2006 FORM-1 09-05-2013.pdf

316-CHE-2006 FORM-1 18-01-2013.pdf

316-CHE-2006 POWER OF ATTORNEY 09-05-2013.pdf

316-CHE-2006 POWER OF ATTORNEY 18-01-2013.pdf

316-CHE-2006 AMENDED PAGES OF SPECIFICATION 09-05-2013.pdf

316-CHE-2006 AMENDED CLAIMS 09-05-2013.pdf

316-CHE-2006 AMENDED CLAIMS 31-12-2012.pdf

316-CHE-2006 AMENDED PAGES OF SPECIFICATION 31-12-2012.pdf

316-CHE-2006 CORRESPONDENCE OTHERS 09-05-2013.pdf

316-CHE-2006 EXAMINATION REPORT REPLY RECEIVED 31-12-2012.pdf

316-CHE-2006 FORM-1 31-12-2012.pdf

316-CHE-2006 FORM-13 31-12-2012.pdf

316-CHE-2006 FORM-18.pdf

316-CHE-2006 OTHER PATENT DOCUMENT 31-12-2012.pdf

316-CHE-2006 POWER OF ATTORNEY 31-12-2012.pdf

316-che-2006-abstract.pdf

316-che-2006-claim.pdf

316-che-2006-correspondence-others.pdf

316-che-2006-description-complete.pdf

316-che-2006-description-provisional.pdf

316-che-2006-form 1.pdf

316-che-2006-form 26.pdf

316-che-2006-form 5.pdf


Patent Number 256205
Indian Patent Application Number 316/CHE/2006
PG Journal Number 20/2013
Publication Date 17-May-2013
Grant Date 16-May-2013
Date of Filing 24-Feb-2006
Name of Patentee SAMSUNG INDIA SOFTWARE OPERATIONS PRIVATE LIMITED
Applicant Address BAGMANE LAKEVIEW, BLOCK 'B', NO. 66/1 BAGMANE TECH PARK, CV RAMAN NAGAR, BYRASANDRA, BANGALORE -560093.
Inventors:
# Inventor's Name Inventor's Address
1 RAJESH CHALLA EMPLOYED AT SAMSUNG INDIA SOFTWARE OPERATIONS PVT. LTD., HAVING ITS OFFICE AT, BAGMANE LAKEVIEW, BLOCK 'B', NO. 66/1 BAGMANE TECH PARK, CV RAMAN NAGAR, BYRASANDRA BANGALORE-560093.
PCT International Classification Number H04L 12/00
PCT International Application Number N/A
PCT International Filing date
PCT Conventions:
# PCT Application Number Date of Convention Priority Country
1 NA