# US 8,543,091 B2 · Secure short message service (SMS) communications

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 8,543,091 B2
- Document ID: US8543091B2
- Status: Granted
- Kind: B2
- Application number: 12/341,987
- Filed: 2008-12-22
- Published: 2009-12-10
- Granted: 2013-09-24
- Earliest claimed: 2008-06-06
- Assignees: eBay Inc.
- Applicants: Upendra Mardikar
- Inventors: Upendra Mardikar
- Web page: https://patentgrep.com/patent/US8543091B2

## CPC

- H04W 12/06: Authentication
- H04L 9/0643: {Hash functions, e.g. MD5, SHA, HMAC or f9 MAC}
- H04L 9/14: using a plurality of keys or algorithms
- H04L 9/302: {involving the integer factorization problem, e.g. RSA or quadratic sieve [QS] schemes}
- H04L 9/304: {based on error correction codes, e.g. McEliece}
- H04L 9/3242: {involving keyed hash functions, e.g. message authentication codes [MACs], CBC-MAC or HMAC}
- H04L 9/3249: {using RSA or related signature schemes, e.g. Rabin scheme}
- H04L 9/3263: {involving certificates, e.g. public key certificate [PKC] or attribute certificate [AC]; Public key infrastructure [PKI] arrangements (network architectures or network communication protocols for supporting authentication of entities using certificates in a packet data network H04L63/0823)}
- H04L 51/58: Message adaptation for wireless communication
- H04L 63/0464: {using hop-by-hop encryption, i.e. wherein an intermediate entity decrypts the information and re-encrypts it before forwarding it}
- H04L 63/06: {for supporting key management in a packet data network (cryptographic mechanisms or cryptographic arrangements for key management H04L9/08)}
- H04L 63/0853: {using an additional device, e.g. smartcard, SIM or a different communication terminal (cryptographic mechanisms or cryptographic arrangements for entity authentication involving additional secure or trusted devices H04L9/3234)}
- H04L 63/0861: {using biometrical features, e.g. fingerprint, retina-scan (cryptographic mechanisms or cryptographic arrangements for entity authentication using biological data H04L9/3231)}
- H04L 63/0876: {based on the identity of the terminal or configuration, e.g. MAC address, hardware or software configuration or device fingerprint}
- H04W 4/14: Short messaging services, e.g. short message services [SMS] or unstructured supplementary service data [USSD]
- H04W 12/02: Protecting privacy or anonymity, e.g. protecting personally identifiable information [PII]
- H04W 12/033: of the user plane, e.g. user's traffic
- H04W 12/04: Key management, e.g. using generic bootstrapping architecture [GBA]
- H04L 63/083: {using passwords (cryptographic mechanisms or cryptographic arrangements for entity authentication using a predetermined code H04L9/3226)}
- H04L 2463/082: applying multi-factor authentication
- H04W 12/61: Time-dependent
- H04W 12/71: Hardware identity
- H04W 12/72: Subscriber identity
- H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72)
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

Embodiments of the present disclosure provide systems and methods for secure Short Message Service (SMS) communications. According to an embodiment, a method of providing secure Short Message Service (SMS) communications comprises requesting that SMS data to be sent from a client device to a remote location be encrypted. The method also comprises encrypting the SMS data by processing the SMS data with a Message Authentication Code (MAC) and a timestamp and/or counter along with second factor authentication information. The method further comprises sending the encrypted SMS data to the remote location by a secure SMS application via a regular SMS channel of the client device.

## Claims

### Claim 1

A method of providing secure Short Message Service (SMS) communications comprising:
requesting, by a secure SMS application loaded inside a client device, that SMS data to be sent from the client device to a remote location be encrypted internally by a Crypto component in the client device, wherein the secure SMS application is in communication with the Crypto component;
encrypting, internally by the Crypto component in the client device, the SMS data by processing the SMS data with a Message Authentication Code (MAC) and a timestamp and/or counter along with second factor authentication information;
sending the encrypted SMS data to the remote location by the secure SMS application via a regular SMS channel of the client device;
receiving encrypted SMS data from the remote location via the regular SMS channel of the client device; and
decrypting and reading the received encrypted data using the secure SMS application of the client device, wherein the decrypting and reading further comprises:
receiving an HMAC timestamp and/or counter with the received encrypted SMS data;
comparing the received HMAC timestamp and/or counter with a pre-determined appropriate timestamp and/or counter to determine veracity;
once the received HMAC timestamp and/or counter is verified, processing a pre-registered unique identifier associated with the remote location that is known by the client device so that a position of such identifier is proven.

### Claim 2 (depends on 1)

The method of claim 1, wherein the encrypting the SMS data further comprises generating an HMAC and the timestamp and/or counter in a component of the client device.

### Claim 3 (depends on 2)

The method of claim 2, wherein the encrypting the SMS data further comprises combining the second factor authentication information with the timestamp and/or counter and then processing such combination with the HMAC.

### Claim 4 (depends on 3)

The method of claim 3, wherein the second factor authentication information further comprises one or more pre-registered unique identifiers including a Secure Element number or identification (ID), the client device's International Mobile Equipment Identity (IMEI) number, or a user-associated International Mobile Subscriber Identity (IMSI) unique number that may be stored in a component inside the client device.

### Claim 5 (depends on 2)

The method of claim 2, wherein the component of the client device further comprises a Secure Element, a UICC with a SIM card and/or a smart card inside the client device in communication with the secure SMS application.

### Claim 6 (depends on 1)

The method of claim 1, wherein the encrypting the SMS data further comprises using Elliptic Curve Cryptography or an RSA algorithm that is preloaded in the client device.

### Claim 7 (depends on 1)

The method of claim 1, wherein the sending further comprises using an Over the Air (OTA) SMS channel.

### Claim 8 (depends on 1)

The method of claim 1, wherein the client device further comprises a wireless telephone, a personal computer, a Personal Digital Assistant (PDA), a smart card, a notebook computer or a keyfob.

### Claim 9 (depends on 1)

The method of claim 1, wherein the remote location further comprises a second client device.

### Claim 10 (depends on 1)

The method of claim 1, wherein the remote location further comprises a secure SMS service provider.

### Claim 11 (depends on 10)

The method of claim 10, further comprising uniquely pre-registering the client device or a user with the secure SMS service provider.

### Claim 12 (depends on 10)

The method of claim 10, further comprising:
receiving the encrypted SMS data at the remote location via the regular SMS channel of the client device;
decrypting and re-encrypting the received SMS data at the remote location; and
sending the re-encrypted SMS data to a second client device.

### Claim 13 (depends on 1)

The method of claim 1, wherein the secure SMS application further comprises a Secure Element, a UICC with a SIM card or a smart card inside the client device.

### Claim 14 (depends on 1)

A machine-readable medium comprising a plurality of machine-readable instructions which when executed by one or more processors of a server are adapted to cause the server to perform the method of claim 1.

### Claim 15

A client device comprising:
one or more processors; and
one or more memories adapted to store a plurality of machine-readable instructions which when executed by the one or more processors are adapted to cause the client device to:
request, by a secure SMS application loaded inside the client device, that SMS data to be sent from the client device be encrypted internally by a Crypto component in the client device, wherein the secure SMS application is in communication with the Crypto component;
encrypt, internally by the Crypto component in the client device, the SMS data by processing the SMS data with a Message Authentication Code (MAC) and a timestamp and/or counter along with second factor authentication information;
send the encrypted SMS data to a remote location by the secure SMS application via a regular SMS channel of the client device;
receive an HMAC timestamp and/or counter along with received encrypted SMS data from the remote location via the regular SMS channel of the client device;
compare the received HMAC timestamp and/or counter with a pre-determined appropriate timestamp and/or counter to determine veracity;
once the received HMAC timestamp and/or counter is verified, process a pre-registered unique identifier associated with the remote location that is known by the client device so that a position of such identifier is proven; and
decrypt and read the received encrypted SMS data using the secure SMS application of the client device.

### Claim 16 (depends on 15)

The client device of claim 15, wherein the client device further comprises a plurality of components loaded inside the client device in communication with each other.

### Claim 17 (depends on 16)

The client device of claim 16, wherein the components further comprise a Secure Element, a UICC with a SIM card and/or a smart card.

### Claim 18 (depends on 15)

The client device of claim 15, wherein the machine-readable instructions when executed by the one or more processors are adapted to cause a component of the client device to encrypt the SMS data by generating an HMAC and a timestamp and/or counter.

### Claim 19 (depends on 18)

The client device of claim 18, wherein the machine-readable instructions when executed by one or more processors are adapted to cause the component of the client device to encrypt the SMS data by using an ECC or an RSA algorithm preloaded in the component therein.

### Claim 20 (depends on 18)

The client device of claim 18, wherein the machine-readable instructions when executed by the one or more processors are adapted to cause the component of the client device to encrypt the SMS data by combining the second factor authentication information with the timestamp and/or counter and then processing the combination with the HMAC.

### Claim 21 (depends on 15)

The client device of claim 15, wherein the remote location further comprises a secure SMS service provider.

### Claim 22 (depends on 15)

The client device of claim 15, wherein the remote location further comprises another client device.

### Claim 23 (depends on 15)

The client device of claim 15, wherein the client device comprises a wireless telephone, a personal computer, a Personal Digital Assistant (PDA), a smart card, a notebook computer or a keyfob.

### Claim 24

A secure SMS system comprising:
a client device in communication with a remote location via a network;
one or more processors; and
one or more memories adapted to store a plurality of machine-readable instructions which when executed by the one or more processors are adapted to cause the secure SMS system to:
encrypt, internally by a Crypto component in the client device, SMS data to be sent from the client device by generating a Hash Message Authentication Code (HMAC) using an encryption algorithm and applying the HMAC to a combination of a timestamp and/or counter with second factor authentication information internally in the Crypto component of the client device;
send encrypted SMS data via a secure SMS application using a regular SMS channel of the client device to the remote location, wherein the secure SMS application is in communication with the Crypto component;
receive an HMAC timestamp and/or counter with received encrypted SMS data from the remote location via the regular SMS channel of the client device;
compare the received HMAC timestamp and/or counter with a pre-determined appropriate timestamp and/or counter to determine veracity;
once the received HMAC timestamp and/or counter is verified, process a pre-registered unique identifier associated with the remote location that is known by the client device so that a position of such identifier is proven; and
decrypt and read the received encrypted SMS data using the secure SMS application of the client device.

### Claim 25 (depends on 24)

The secure SMS system of claim 24 wherein the plurality of machine-readable instructions which when executed by the one or more processors are further adapted to cause the secure SMS system to:
receive the encrypted SMS data at the remote location;
decrypt and re-encrypt the received SMS data at the remote location;
send the re-encrypted SMS data to a second client device;
receive the re-encrypted SMS data at the second client device via a regular SMS channel of the second client device; and
decrypt and read the received SMS data by a secure SMS application of the second client device.

### Claim 26 (depends on 24)

The secure SMS system of claim 24, wherein the network further comprises the Internet, one or more intranets, landline networks and/or wireless networks.

### Claim 27 (depends on 24)

The secure SMS system of claim 24, wherein the client device further comprises a wireless telephone, a personal computer, a Personal Digital Assistant (PDA), a smart card, a notebook computer or a keyfob.

### Claim 28 (depends on 24)

The secure SMS system of claim 24, wherein the remote location further comprises a second client device.

### Claim 29 (depends on 24)

The secure SMS system of claim 24, wherein the plurality of machine-readable instructions which when executed by the one or more processors are further adapted to cause the secure SMS system to encrypt the SMS data using Elliptic Curve Cryptography or an RSA algorithm that is preloaded in the client device.
