Secure Messaging

• US 20130061289A1
• Filed: 03/01/2012
• Published: 03/07/2013
• Est. Priority Date: 03/01/2011
• Status: Abandoned Application

• Current Assignee: TeleCommunication Systems Inc (Comtech Telecommunications Corporation)
• Original Assignee: TeleCommunication Systems Inc (Comtech Telecommunications Corporation)
• Inventors: McFarland, Keith, Kesser, Doug, Pohutsky, Joseph
• Application Number:
  US13/409,695
• Publication Number:
  US 20130061289A1
• Time in Patent Office: Days
• US Class Current: 726/4
• CPC Class Codes: H04L 63/0428 wherein the data content is protected, e.g. by encrypting or encapsulating the payload
• CPC Class Codes: H04L 63/168 above the transport layer
• CPC Class Codes: H04W 12/02 Protecting privacy or anonymity, e.g. protecting personally identifiable information [PII]
• CPC Class Codes: H04W 12/033 of the user plane, e.g. user's traffic

Abstract

A secure messaging interface enables submission of messages to a messaging gateway via secure means over TLS. A destination mobile device(s) is notified of a pending secure message, and holds the secure message until it is retrieved by an authorized mobile device. The messaging gateway also provides push services for sending data to wireless devices. The secure messager enables sending devices to apply security to an individual message. Sending devices may include, e.g., an enterprise administration server; messages routed through an messaging gateway (MGW) portal; an user messaging application; or a user through a handset. The secured messages may include content as available today across any messaging protocol such as text, audio, video, binaries and images.

Claims

1. A method of providing a secure message securely to a mobile device, comprising:

receiving a reference ID and an alphanumeric code relating to a secure message, but not including said secure message, at a messaging gateway (MGW) server;

routing said reference ID, from said messaging access gateway server toward a destination mobile device;

accepting an authorized request to send said secure message, from said destination mobile device, said authorized request including said reference ID and a code authorizing receipt of said secure message; and

routing said secure message from said messaging access gateway server to said destination mobile device.

2. The method of providing a secure message securely to a mobile device according to claim 1, wherein:

said reference ID is routed from said messaging gateway server to said destination mobile device via a message distribution server (e.g. short message service center (SMSC)).

3. The method of providing a secure message securely to a mobile device according to claim 1, further comprising:

accepting a secure message at said messaging gateway server, from a sending device, via TLS using a secure messaging application.

4. The method of providing a secure message securely to a mobile device according to claim 1, further comprising:

accepting a secure message at said messaging gateway server, from a sending device, via any message source protocol (e.g. XML Send).

5. The method of providing a secure message securely to a mobile device according to claim 1, further comprising:

accepting a response from said destination mobile device at said messaging gateway server via TLS.

6. The method of providing a secure message securely to a mobile device according to claim 5, further comprising:

routing said response from said messaging access gateway server toward an initiating device via any messaging source protocol.

7. A method of passing a secure message securely between mobile devices, comprising:

receiving a reference ID relating to a secure message sent by a sending mobile device, but not including said secure message, at a messaging gateway (MGW) server;

routing said reference ID, from said messaging gateway server to a message distribution center;

routing said reference ID from said message distribution server toward a destination mobile device;

accepting an authorized request to send said secure message, from said destination mobile device, said authorized request including said reference ID and a code authorizing receipt of said secure message; and

routing said secure message from said messaging access gateway server to said destination mobile device.

8. The method of passing a secure message securely between mobile devices according to claim 7, wherein:

said message distribution server is a short message service center (SMSC), multimedia message center (MMSC) or Session Initiated Protocol Application Service (SIP AS).

9. The method of passing a secure message securely between mobile devices according to claim 7, further comprising:

accepting a secure message at said messaging gateway server, from said sending mobile device, via TLS.