Abstract:
A method and system are provided for remotely deleting short message service messages stored on the remote mobile communication device, by initiating a delete command, or setting a message lifespan when creating a SMS message, from a sender mobile communication device.

Description:
CROSS-REFERENCES TO RELATED APPLICATIONS 
       [0001]    This application is a non-provisional application of and claims the benefit of U.S. Provisional Application No. 61/461,439, filed on Jan. 18, 2011 by the present inventor. 
     
    
     BACKGROUND  
     Prior Art 
       [0002]    The following is a tabulation of some prior art that presently appears relevant: 
         [0000]    
       
         
               
             
               
               
               
               
               
             
           
               
                   
               
               
                 U.S. patents 
               
             
          
           
               
                   
                 Pat. No. 
                 Kind Code 
                 Issue Date 
                 App or Patentee 
               
               
                   
                   
               
               
                   
                 0,108,621 
                 A1 
                 May 19, 2005 
                 Kim et al. 
               
               
                   
                   
               
             
          
         
       
     
         [0003]    Existing deletion solutions have solely depended on a timing mechanism, set and controlled by a central location. The sender of the text message had no control, or knowledge of the text message existence, after it has been sent. Existing systems do not make the mobile sender aware of the successful completion of the deletion of the sent text message. The life cycle of the mobile sender&#39;s text message is left to the strength, or weakness of a central system in use, enterprise policy, the receiving end user device, and or the action of message receiver. Transmission of discrete messages, while being secure in the transient state, are left vulnerable when received and stored on the receiver&#39;s mobile device. 
         [0004]    Accordingly, what is desired is a method for enabling message senders, such as SMS message senders, to have the capability to set, at their own convenience, the life cycle of their sent messages, once the remote devices has received the messages. 
       FIELD OF THE INVENTION 
       [0005]    The present invention generally relates to methods and a message delivery system, and more particularly, to methods and a message delivery system for remotely deleting short message service messages stored on the remote mobile communication device, by initiating a delete command, or setting a message lifespan when creating a SMS message, from a sender mobile communication device. 
       BACKGROUND OF INVENTION 
       [0006]    Concerns about exposure of what was assumed to be confidential exchanges of information, has been the subject of debates aired over the media. It has become obvious that information, once transmitted, may be viewed by third parties along the message communication pathway and by others, the message receiver may choose to disclose to. Many forms of message and communication encryption strategies address the communication pathway disclosure issue, but the end user receiver disclosure still exists. In the mobile space, this problem is magnified several times, due to the obvious transient nature of end users. For example, the sender of a text message has no control or knowledge of the text message&#39;s existence, after it has been sent. The life cycle of the mobile sender&#39;s text message is left to the message recipient, the strength, or weakness of system in use, and/or enterprise policy. This scenario adds to the problem of information leakage, which remains an issue even if the line of transmission is secure. 
         [0007]    Elaborate security schemes are available to ensure confidentiality is ensured. However, the mobile recipient is not considered to be a member of the group of links, in the security chain, that may pose as a concern. For example, a sender transmits an encrypted text message to a mobile receiver, who successfully open and reads the message. This discrete message is unreadable to everyone except the sender and recipient, thus maintaining confidentiality. However, if the receiver decides, on his own, to disclose the content of the message, later to a third party, the sender receiver confidentiality will be compromised. 
         [0008]    Therefore, improvements for a mobile communication and a method for managing sent SMS messages, by a message sender, or owner, are needed in the industry to address the aforementioned deficiency. 
       BRIEF SUMMARY OF THE INVENTION 
       [0009]    Embodiments of the present invention provide techniques that enable a sender, using a mobile device, to delete, at any time, a sent text message residing on a receiver&#39;s mobile device. After sending a text message to the receiver, the sender will be notified of the opening and reading of the text message located on the receiver&#39;s mobile device. With this alert, the sender may chose to delete the remotely located text message. Alternatively, the sender may set a relative time and send a message that will automatically get deleted, at the relative amount of time, after it is opened and read, or at the relative amount of time after it arrives on the device. 
         [0010]    A further understanding of the nature and advantages of the invention herein may be realized by reference of the remaining portions in the specifications and the attached drawings. 
     
    
     
       BRIEF DESCRIPTION OF THE DRAWINGS 
         [0011]    The accompanying drawings, which are incorporated herein and form a part of the specification, illustrate embodiments of the present invention and, together with the description, further serve to explain the principles of the invention and to enable a person skilled in the relevant art to make and use the invention. 
           [0012]      FIG. 1  illustrates a mobile sender initiated SMS deletion network, in accordance with an embodiment of the present invention. 
           [0013]      FIG. 2  illustrates communication channels in a mobile sender initiated SMS deletion network, in accordance with an embodiment of the present invention. 
           [0014]      FIG. 3  illustrates a mobile sender initiated SMS deletion message delivery system, in accordance with an embodiment of the present invention. 
           [0015]      FIG. 4  illustrates additional modules of a mobile sender initiated SMS deletion message delivery system, in accordance with an embodiment of the present invention. 
           [0016]      FIG. 5  is a flowchart depicting steps in the operation of a mobile sender initiated SMS deletion message delivery system, in accordance with an embodiment of the present invention. 
           [0017]      FIG. 6  is a flowchart depicting steps in the operation the security manager residing in a mobile sender initiated SMS deletion message delivery system, in accordance with an embodiment of the present invention. 
           [0018]      FIG. 7  illustrates an SMS service module for a mobile sender initiated SMS deletion message delivery system, in accordance with an embodiment of the present invention. 
           [0019]      FIG. 8A  and  FIG. 8B  combined, is a flowchart depicting steps of a client service for a mobile sender initiated SMS deletion message delivery system, in accordance with an embodiment of the present invention. 
           [0020]      FIG. 9  is a flowchart depicting steps of the flagging process of messages, of type relative open time for automatic lifespan, in a client service for a mobile sender initiated SMS deletion message delivery system, in accordance with an embodiment of the present invention. 
           [0021]      FIG. 10  is a flowchart depicting steps of the deletion background process of a client service for a mobile sender initiated SMS deletion message delivery system, in accordance with an embodiment of the present invention. 
       
    
    
     DETAILED DESCRIPTION OF THE INVENTION 
     I. INTRODUCTION 
       [0022]    The following detailed description of the present invention refers to the accompanying drawings that illustrate exemplary embodiments consistent with this invention. Other embodiments are possible, and modifications can be made to the embodiments within the spirit and scope of the invention. Therefore, the detailed description is not meant to limit the invention. Rather, the scope of the invention is defined by the appended claims. 
         [0023]    It would be apparent to one of skill in the art that the present invention, as described below, can be implemented in many different embodiments of software, hardware, firmware, and/or the entities illustrated in the figures. Any actual software code with the specialized control of hardware to implement the present invention is not limiting of the present invention. Thus, the operational behavior of the present invention will be described with the understanding that modifications and variations of the embodiments are possible, given the level of detail presented herein. 
         [0024]      FIG. 1  is a network  100  depicting a mobile sender initiated SMS deletion network, in accordance with an embodiment of the present invention. The network  100  includes a user device  102 , a carrier wireless network  104 , and a message delivery system  106 . As used in this specification, user device  102  will commonly be a cellular telephone having data communication capabilities, although one skilled in the relevant arts will readily appreciate that any communication device, or device having communication capabilities, can be substituted. Similarly, network  104  will commonly be a carrier wireless network throughout this specification, although one skilled in the relevant arts will likewise appreciate that, depending on the capabilities of user device  102 , other network types, to include wired networks of any type, or wireless technology of any type (e.g., Bluetooth, cellular, ad hoc, etc.), can be substituted for wireless network  104 . 
         [0025]    Message delivery system  106  eases the communications between sender and receiver user devices  102 , by routing messages from sender user device  102  to receiver user device  102 , as further disclosed below, in accordance with an embodiment of the present invention. Furthermore, message delivery system  106  includes logic for establishing communications with user device  102  over carrier wireless network  104 , in accordance with an embodiment of the present invention. Carrier wireless network  104  is, in accordance with an additional embodiment of the present invention, a cellular communications network. 
       II. NETWORK COMMUNICATIONS 
       [0026]      FIG. 2  is a network  200  illustrating communication channels in a mobile sender initiated SMS deletion network, in accordance with an embodiment of the present invention. As previously disclosed, a user device  102  is operable to connect to a message delivery system  106  over carrier wireless network  104  in order to send and receive messages. One skilled in the relevant arts will recognize that a user device  102 , such as a cellular phone, can communicate using a number of different protocols over a carrier wireless network  104 , such as a cellular communications network. 
         [0027]    In accordance with an embodiment of the present invention, user device  102  is configured to transmit data conforming to the Short Message Service (“SMS”) protocol  202  over carrier wireless network  104 . An SMS gateway  204  is used to receive the SMS data  202  communications from carrier wireless network  104  and forward the communications to message delivery system  106 , in accordance with an embodiment of the present invention. In accordance with an additional embodiment of the present invention, SMS gateway  204  is the Sybase  365 ™ system provided by Sybase Inc., an SAP company, of Dublin, Calif. One skilled in the relevant arts will recognize that the precise configuration of the SMS gateway  204  as shown in  FIG. 2  need not exist in every system, where instead other means for forwarding the SMS data  202  communications to message delivery system  106  are implemented. 
         [0028]    In accordance with an embodiment of the present invention, user device  102  transmits SMS data  202  to SMS gateway  204  through the use of a special “short code” assigned to the message delivery system  106 , in order to allow SMS gateway  204  to properly route the SMS data  202  to the message delivery system  106 . 
       III. MESSAGE DELIVERY SYSTEM 
       [0029]      FIG. 3  is a network  300  illustrating additional features of message delivery system  106 , in accordance with an embodiment of the present invention. As previously illustrated in  FIG. 2 , message delivery system  106  is capable of receiving SMS data  202 . Message delivery system comprises a connector manager  302  for managing communications over one or more data channels, such as the connector associated with SMS data  202 , in accordance with an embodiment of the present invention. The SMS connection is handled by SMS service module  304  for interfacing with SMS data  202 , in accordance with an embodiment of the present invention. One skilled in the relevant arts will appreciate that the capabilities of SMS service module  304  need not be centralized in a single module, and can instead be optionally distributed throughout connection manager  302 . 
         [0030]    Connector manager  302  further comprises a security manager  306  for authenticating a user or a user device  102 , in accordance with an embodiment of the present invention. The security manager  306  determines if a user device  102  is a valid provisioned user before delivery of a message from a user received through a service module, such as service modules  304 , by authenticating the user or user device, and enabling the processing of the message if authentication is achieved, in accordance with an embodiment of the present invention. 
         [0031]    Connector manager  302  further comprises a delivery manager  308 , in accordance with an embodiment of the present invention. Connector manager  302  facilitates the communication of messages received from a sender user device  102  through SMS service module  304  to a receiver user device  102  through a SMS service module  304 , which is fully discussed below, in accordance with an embodiment of the present invention. One skilled in the relevant arts will appreciate that the capabilities of delivery manager  308  need not be centralized in a single module, and can instead be optionally distributed throughout connector manager  302 . In accordance with an embodiment of the present invention, the capabilities of delivery manager  308  are localized within SMS service module  304 . In accordance with a further embodiment of the present invention, the connector manager  302  is part of the delivery manager  308 . 
         [0032]    Delivery manager  308  enables connector manager  302  to route, an authenticated sender user&#39;s or sender user device&#39;s  102  message to a receiver user or user device through a SMS service module, such as service module  304 , in accordance with an embodiment of the present invention. The functionality of the delivery manager  308  is achieved by utilizing an extracted, intended destination user or user device  102  from some received SMS data  202 , to then forward a received SMS data  202  to an intended destination user or user device  102 , by use of a service modules, such as SMS service module  304 , in accordance with an embodiment of the present invention. 
       IV. ADDITIONAL FUNCTIONALITY OF THE MESSAGE DELIVER SYSTEM 
       [0033]      FIG. 4  illustrates a network  400  including message delivery system  106 , in accordance with an embodiment of the present invention. As before, message delivery system  106  includes connector manager  302 , but also includes additional modules for enhancing the functionality of message delivery system  106 . These additional modules are described in more detail below. 
         [0034]    Audit module  402  provides a mechanism for storing events and messages that pass through message delivery system  106 , in accordance with an embodiment of the present invention. In accordance with an embodiment of the present invention, audit module  402  is configured to store all messages received from a user device  102  in connector manager  302 . One skilled in the relevant arts will recognize that audit module  402  can be configured to log any communications occurring within message delivery system  106 , in accordance with an embodiment of the present invention. 
         [0035]    Notification module  404  is configured to send messages to the user device related to a notification condition, in accordance with an embodiment of the present invention. For example, message delivery system  106  can provide a notification to the user device  102  through notification module  404  if a user&#39;s account becomes disabled. 
       V. OPERATION OF THE MESSAGE DELIVERY SYSTEM 
       [0036]      FIG. 5  is a flowchart  500  depicting an operational flow of message delivery system  106 , in accordance with an embodiment of the present invention. Flowchart  500  is described with continued reference to network  300  of  FIG. 3 . The method begins at step  501  and proceeds to step  502 , where the message delivery system  106  receives a SMS data  202  from the user device  102 . At step  504 , the message delivery system  106  performs authentication on the sender user or user device  102 , then process proceeds to step  506 . If authentication was unsuccessful  506 , the method proceeds to step  518  where processing ends. If authentication was successful  506 , the method continues to step  508 . 
         [0037]    At step  508  of flowchart  500 , the message delivery system  106 , the SMS data  202  is parsed, in accordance with an embodiment of the present invention, at SMS service module  304  in message delivery system  106 . In the process of parsing the SMS data  202 , the intended destination user or user device  102  from some received SMS data  202  is extracted  510 . Once extraction  510  is complete, step  512  of the message delivery system  106  performs authentication on the destination user or user device  102 , then process proceeds to step  514 . If authentication was unsuccessful  514 , the method proceeds to step  518  where processing ends. If authentication was successful  514 , the method continues to step  516 . 
         [0038]    At step  516  of flowchart  500 , the message delivery system  106 , the parsed SMS data  202  is then repackaged into the SMS data  202  format, and transmitted to the intended destination user or user device  102  by use of a service modules, such as SMS service module  304 , and the method ends at step  518 , in accordance with an embodiment of the present invention. 
         [0039]    With continued reference to flowchart  500  of  FIG. 5 , network  300  of  FIG. 3 , and network  200  of  FIG. 2 , an example user interaction with message delivery system  106  is disclosed, in accordance with an embodiment of the present invention. A user enters an SMS message (or “text message”), at user device  102  to be delivered to a remote user device  102 . In this example, the user enters the message “Hello World”. The user then sends this SMS message to the remote user mobile number  102  by entering a mobile number associated with the remote user mobile number  102 . In accordance with an embodiment of the present invention, the SMS message is sent to a short code, such as  21221 , that uniquely identifies message delivery system  106 . 
         [0040]    At step  502  of flowchart  500 , the message delivery system  106  receives the SMS message  202 , and at steps  504  and  512  the message delivery system  106  performs any necessary authentication, as will be fully disclosed herein. If authentication are unsuccessful  506  and  514 , the process proceeds to step  518 . If authentication are successful  506  and  514 , the process continues to step  508  and  516 , respectively. 
         [0041]    At step  508  of flowchart  500 , the message delivery system  106  begins parsing the SMS message to identify one token in the aforementioned message, which represents the destination user or user device  102  from some received SMS data  202 , in accordance with an embodiment of the present invention. Next, this token is extracted  510  and step  512  of the message delivery system  106 , performs authentication on the destination user or user device  102 . If authentication was unsuccessful  514 , the method proceeds to step  518  where processing ends. If authentication was successful  514 , the method continues to step  516 . 
         [0042]    At step  516  of flowchart  500 , the message delivery system  106 , the parsed SMS message is then formatted to fit within the limitations of an SMS message, and transmitted to the intended destination user or user device  102  by use of a service modules, such as SMS service module  304 , and the method ends at step  518 . For the aforementioned example, the transmitted SMS message would be, in accordance with an embodiment of the present invention. 
         [0043]    In accordance with an additional embodiment of the present invention, if the authentication of steps  506  and  514  fails, the process flow is terminated. In accordance with a further embodiment of the present invention. 
       VI. OPERATION OF THE SECURITY MANAGER 
       [0044]      FIG. 6  is a flowchart  600  depicting an operational flow of security manager  306 , in accordance with an embodiment of the present invention. The method begins at step  601  and proceeds to step  602  where a search is performed in order to determine if the received unique property can be found. The result is passed to step  604 , in accordance with an embodiment of the present invention. At step  604 , it is determined if the result is a valid user, by returning success  606  if indeed the result is a valid user. Step  604  returns failure  608 , if the result is determined not to be a valid user, in accordance with an embodiment of the present invention. The process then proceeds to step  610 , where it ends. 
         [0045]    One skilled in the relevant arts will appreciate that additional means for authentication can be used, and the aforementioned means are described by way of example and not limitation. For example, the SMS message could include a unique password for providing authentication. 
       VII. ADDITIONAL FUNCTIONALITY OF SERVICE MODULES 
       [0046]      FIG. 7  illustrates a network  700  including SMS service module  304 , in accordance with an embodiment of the present invention. As previously disclosed, user device  102  is operable to communicate over wireless network  104  with SMS gateway  204  in order to transmit SMS messages to the the message delivery system. SMS messages received by the the message delivery system are handled by SMS service module  304 , in accordance with an embodiment of the present invention. 
         [0047]    SMS service module  304  includes SMS listener  702 , which is configured to receive SMS messages from SMS gateway  204 , in accordance with an embodiment of the present invention. SMS service module  304  additionally includes includes SMS message parser  704 , which is described in more detail below. 
         [0048]    SMS listener  702  captures SMS messages from SMS gateway  210 , in accordance with an embodiment of the present invention. In accordance with an additional embodiment of the present invention, SMS listener  702  is configured to receive asynchronous message acknowledgements from SMS gateway  210 . In accordance with a further embodiment of the present invention, SMS listener  702  is configured as a bi-directional communications module, and additionally handles the transmission of messages from message delivery system  106  to user device  102  through SMS gateway  210 . In accordance with another embodiment of the present invention, the transmission of messages from message delivery system  106  to user device  102  through SMS gateway  210  is handled by a separate SMS Sender Service. One skilled in the relevant arts will appreciate that additional communication configuration exist, and the aforementioned configurations are presented by way of example, and not limitation. 
         [0049]    SMS service module  304  includes SMS Message Parser  704 , which parses the destination user device  102  from the received SMS data  202 , in accordance with an embodiment of the present invention. One skilled in the relevant arts will appreciate that additional communication configuration exist, and the aforementioned configurations are presented by way of example, and not limitation. 
       VIII. USER DEVICE CLIENT SERVICE 
       [0050]      FIG. 8A  and  FIG. 8B  combined, is a flowchart  800  depicting an operational flow of client service on the user device  102 , in accordance with an embodiment of the present invention, of transmitting and receiving short message service (SMS) messages, where by a sender user device  102  can delete a sent SMS data  202 , on a remote receiver user device  102 . The method begins in  FIG. 8A  at step  801  and proceeds to step  802 , where the user device  102  receives a SMS message  202  from a sender user device  102 . At step  802 , the remote receiver user device  102  performs a check to verify if a SMS data  202  was received. If no SMS data  202  was received, the method proceeds to step  804 . If a SMS data  202  was received, the proceeds to step  816 , which is described in more detail below, in accordance with an embodiment of the present invention. 
         [0051]    At step  804  of flowchart  800 , the client service, on the user device  102 , verifies if create a new message option is selected, in accordance with an embodiment of the present invention. If it was not selected, step  804  continues to step  802 . If it was selected, the method proceeds to step  806 . At step  806 , a new message is created, in accordance with an embodiment of the present invention. Once the message is created, the method continues to step  808 . 
         [0052]    At step  808  of flowchart  800 , the client service, on the user device  102 , verifies if a manual delete is to be performed on the new SMS data  202  when it arrives on the remote user device  102 , in accordance with an embodiment of the present invention. If a manual delete is to be performed, message lifespan is set to manual, then the method continues to step  812 , which is described in more detail below, in accordance with an embodiment of the present invention. If a manual delete is not to be performed, the method continues to step  810 . 
         [0053]    At step  810  of flowchart  800 , the client service, on the user device  102 , set the lifespan of the SMS data  202  to be sent, to automatic of type relative open time, or of type relative arrive time, in accordance with an embodiment of the present invention. The method then continues to step  812 . 
         [0054]    At step  812  of flowchart  800 , the client service, on the user device  102 , formats the lifespan, any flags that may be set and message into SMS data  202 , and transmits it to the carrier wireless network  104 , in accordance with an embodiment of the present invention. The process then proceeds to step  814 , where it ends. 
         [0055]    At step  816  of flowchart  800 , the client service, on the user device  102 , verifies if the received SMS data  202  is an alert that a remote receiver user device  102  has performed an action on a previously sent SMS data  202 , in accordance with an embodiment of the present invention. If the received SMS data  202  is an alert, the process then proceeds to step  818 , which is described in more detail below. If the received SMS data  202  is not an alert, the process then proceeds to step  822 . 
         [0056]    At step  822  of flowchart  800 , the client service, on the user device  102 , signals that a SMS data  202  has been received and stores the received SMS data  202 . One skilled in the relevant arts will recognize that step  822  can be accomplished by various methods within user device  102 , in accordance with an embodiment of the present invention. The process then proceeds to step  824 , as will be illustrated in  FIG. 8B . 
         [0057]    At step  818  of flowchart  800 , the the client service, on user device  102 , extract the open flag and unique identifier from the alert of the received SMS data  202 . One skilled in the relevant arts will recognize that step  818  can be accomplished by various methods within user device  102 , in accordance with an embodiment of the present invention. If the flag is determined not to be a set open flag, the process proceeds to step  842 , which is described in more detail below. If the flag is determined to be a set open flag, the process proceeds to step  840 . 
         [0058]    At step  840  of flowchart  800 , the client service, on the user device  102 , verifies the unique identifier of the manual lifespan SMS data  202  to be deleted on the remote receiver user device, in accordance with an embodiment of the present invention. If, the uniquely identified manual lifespan SMS data  202  is to be deleted on the remote receiver user device, the process proceeds to step  820 , which is described in more detail below. If, the uniquely identified manual lifespan SMS data  202  is to be not deleted on the remote receiver user device, the process proceeds to step  814  where processing ends. 
         [0059]    At step  820  of flowchart  800 , the client service, on the user device  102 , sets the delete flag, the unique identifier and an non restrictive lifespan, in accordance with an embodiment of the present invention, and is forwarded to step  812 . One skilled in the relevant arts will recognize that step  820  can be accomplished by various methods within user device  102 , in accordance with an embodiment of the present invention. 
         [0060]    At step  842  of flowchart  800 , the client service, on the user device  102 , extracts the deletion complete flag and unique identifier from the alert of the received SMS data  202 . One skilled in the relevant arts will recognize that step  842  can be accomplished by various methods within user device  102 , in accordance with an embodiment of the present invention. If the flag is determined to be a set deletion complete flag, the process proceeds to step  844 , which is described in more detail below. If the flag is determined not to be a set deletion complete flag, the process proceeds to step  846 . 
         [0061]    At step  846  of flowchart  800 , the client service, on the user device  102 , extracts the delete flag and unique identifier from the alert of the received SMS data  202 . One skilled in the relevant arts will recognize that step  846  can be accomplished by various methods within user device  102 , in accordance with an embodiment of the present invention. If the flag is determined to be a set delete flag, the process proceeds to step  848 , which is described in more detail below. If the flag is determined not to be a set delete flag, the process proceeds to step  812 , which is described in more detail above. 
         [0062]    At step  844  of flowchart  800 , the client service, on the user device  102 , utilizes the unique identifier from the alert of the SMS data  202 , and flags the sender&#39;s copy of the manual lifespan SMS data  202  for deletion. One skilled in the relevant arts will recognize that step  844  can be accomplished by various methods within user device  102 , in accordance with an embodiment of the present invention. Deletion of sender&#39;s copy of the manual lifespan SMS data  202 , may be performed at any time, of the sender&#39;s own choosing. The process proceeds to step  812 , which is described in more detail above. 
         [0063]    At step  848  of flowchart  800 , the client service, on the user device  102 , utilizes the unique identifier from the alert of the SMS data  202 , and sets a delete flag of the uniquely identified manual lifespan SMS data  202 , on the receiver user device  102 . One skilled in the relevant arts will recognize that step  848  can be accomplished by various methods within user device  102 , in accordance with an embodiment of the present invention. The process proceeds to step  814  where processing ends. 
         [0064]    The method continues in  FIG. 8B  at step  822  of flowchart  800 , the client service, on the user device  102 , signals that a SMS data  202  has been received and stores the received SMS data  202 , as previously illustrated in  FIG. 8A . The process then proceeds to step  824 . 
         [0065]    At step  824  of flowchart  800 , the client service, on the user device  102 , may display the received manual lifespan SMS data  202 , which takes the process to step  826 , which is described in more detail below, in accordance with an embodiment of the present invention. If the user device  102  does not display the received manual lifespan SMS data  202 , the process proceeds to step  814  where processing ends, as previously illustrated in  FIG. 8A . 
         [0066]    At step  826  of flowchart  800 , the client service, on the user device  102 , opens the received manual lifespan SMS data  202 , displays its message content, flags the manual lifespan SMS data  202  as an opened message, than stores the manual lifespan SMS data  202 . One skilled in the relevant arts will recognize that step  826  can be accomplished by various methods within user device  102 , in accordance with an embodiment of the present invention. The process then proceeds to step  828 . In accordance with an additional embodiment of the present invention, received SMS data  202  with automatic lifespan is discussed. 
         [0067]    At step  828  of flowchart  800 , the client service, on the user device  102 , removes message content of manual lifespan SMS data  202  from the display, then proceeds to step  830 , in accordance with an embodiment of the present invention. 
         [0068]    At step  830  of flowchart  800 , the client service, on the user device  102 , verifies if the received manual lifespan SMS data  202  delete flag was set by the sender user device  102 , in accordance with an embodiment of the present invention. If received manual lifespan SMS data  202  delete flag was set, the process proceeds to step  832 , which is described in more detail below. If received manual lifespan SMS data  202  delete flag was not set, the process proceeds to step  836 . 
         [0069]    At step  836  of flowchart  800 , the client service on the user device  102  sets a open flag, a unique identifier and an non restrictive lifespan, for the received manual lifespan SMS data  202 , in accordance with an embodiment of the present invention, is forwarded to step  812 , which is illustrated above in  FIG. 8A . 
         [0070]    At step  832  of flowchart  800 , the client service, on the user device  102 , deletes the received manual lifespan SMS data  202  from the user device  102  storage. One skilled in the relevant arts will recognize that step  826  can be accomplished by various methods within user device  102 , in accordance with an embodiment of the present invention. The process then proceeds to step  834 . 
         [0071]    At step  834  of flowchart  800 , the client service, on the user device  102 , sets a deletion complete flag, a unique identifier and an non restrictive lifespan, for the received manual lifespan SMS data  202 , in accordance with an embodiment of the present invention, is forwarded to step  812 , which is illustrated above in  FIG. 8A . 
       IX. USER DEVICE CLIENT SERVICE AUTOMATIC LIFESPAN MESSAGE FLAGGING 
       [0072]      FIG. 9  is a flowchart  800  depicting an operational flow of flagging process of automatic lifespan messages, of type relative open time, of the client service on the user device  102 , in accordance with an embodiment of the present invention, for the handling of received SMS data  202  that have an automatic lifespan of type relative open time, meaning sender user device  102  has preset the lifespan. As previously illustrated in  FIG. 8A , operational flow of the client service on the user device  102 , step  822  signals that a SMS data  202  has been received and stores the received SMS data  202 . One skilled in the relevant arts will recognize that step  822  can be accomplished by various methods within user device  102 , in accordance with an embodiment of the present invention. The process then proceeds to step  902 . 
         [0073]    At step  902  of flowchart  900 , the flagging process of automatic lifespan messages, of type relative open time, of the client service on the user device  102 , may display the received SMS data  202 , which takes the process to step  904 , which is described in more detail below, in accordance with an embodiment of the present invention. If the user device  102  will not display the received SMS data  202 , the process proceeds to step  910  where processing ends. 
         [0074]    At step  904  of flowchart  900 , the flagging process of automatic lifespan messages, of type relative open time, of the client service on the user device  102 , opens the stored automatic lifespan SMS data  202 , of type relative open time, and displays its message content. The process then proceeds to step  906 . In accordance with an additional embodiment of the present invention, received SMS data  202  with automatic lifespan is discussed. 
         [0075]    At step  906  of flowchart  900 , the flagging process of automatic lifespan messages, of type relative open time, of the client service on the user device  102 , flags the automatic lifespan SMS data  202 , of type relative open time, as an opened message, then stores the SMS data  202 . One skilled in the relevant arts will recognize that step  904  can be accomplished by various methods within user device  102 , in accordance with an embodiment of the present invention. The process then proceeds to step  908 . 
         [0076]    At step  908  of flowchart  900 , the flagging process of automatic lifespan messages, of type relative open time, of the client service on the user device  102 , removes message content of SMS data  202  from the display, then proceeds to the end at step  910 , in accordance with an embodiment of the present invention. 
       X. USER DEVICE CLIENT SERVICE DELETION BACKGROUND PROCESS 
       [0077]      FIG. 10  is a flowchart  1000  depicting an operational flow of deletion background process, of a client service on the user device  102 , in accordance with an embodiment of the present invention, of expired automatic lifespan and delete flagged manual lifespan SMS data  202 . The method begins at step  1001  and proceeds to step  1002 , where the process  1002  selects a SMS message from the user device&#39;s  102  store, that is the smallest expired automatic lifespan of type relative open time, smallest manual lifespan that has been flagged as delete, or expired automatic lifespan of type relative arrival time. One skilled in the relevant arts will recognize that step  1002  can be accomplished by various methods within user device  102 , in accordance with an embodiment of the present invention. The process then proceeds to step  1004 . 
         [0078]    At step  1004  of flowchart  1000 , the deletion background process, of a client service on the user device  102 , deletes the selected SMS message from the user device  102  storage. One skilled in the relevant arts will recognize that step  1004  can be accomplished by various methods within user device  102 , in accordance with an embodiment of the present invention. The process then proceeds to step  1006 , where the process ends. 
       XI. ADVANTAGES 
       [0079]    From the description above, a number of advantages of some embodiments of my sender initiated deletion method become evident: 
         [0080]    (a) The message sender has full control of the life span of text message. 
         [0081]    (b) The message sender has knowledge that message was deleted. 
         [0082]    (c) The message sender is made aware that message was opened and or read. 
         [0083]    (d) The message sender can limited the exposure of a sent message to third parties, once the message has been received. 
       XII. CONCLUSION 
       [0084]    While various embodiments of the present invention have been described above, it should be understood that they have been presented by way of example only, and not limitation. It will be understood by those skilled in the relevant art(s) that various changes in form and details may be made therein without departing from the spirit and scope of the invention as defined in the appended claims. It should be understood that the invention is not limited to these examples. The invention is applicable to any elements operating as described herein. Accordingly, the breadth and scope of the present invention should not be limited by any of the above-described exemplary embodiments, but should be defined only in accordance with the following claims and their equivalents.