IP Library Granted Patent US 8,099,117
Granted Patent B2
US 8,099,117 · App. 12/476,184 · Granted Jan 17, 2012

SMS message delivery over broadband data networks

View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 8,099,117
App. No.
12/476,184
Granted
Jan 17, 2012
Kind
B2
Abstract

Broadband messaging gateways, SMS-C's, and associated methods are disclosed that attempt to deliver SMS messages over a broadband data network as opposed to a voice network. When a mobile device sends a Mobile Originated (MO) SMS message, the mobile device sends the MO SMS message to a broadband data network instead of the voice network. The broadband data network then routes the MO SMS message to the appropriate SMS-C. When an SMS-C receives a Mobile Terminated (MT) SMS message destined for a mobile device, the SMS-C forwards the MT SMS message to the broadband data network instead of the voice network. Thus, SMS messages are offloaded from the voice network to the broadband data network.

Claims (53)

1. An apparatus comprising:

a session database configured to store session information for a mobile device that has established a data session over a broadband data network;

an interface configured to receive a Mobile Originated (MO) Short Message Service (SMS) message from the mobile device; and

a message processor configured to verify that the MO SMS message is valid by comparing header information of the MO SMS message with the session information stored in the session database, to identify a Short Message Service Center (SMS-C) for the MO SMS message if the MO SMS message is valid, and to route the MO SMS message to the identified SMS-C through the interface, wherein the message processor is further configured to send an error message over the broadband network to the mobile device to cause the mobile device to attempt to send the MO SMS message over a voice network as a fail over when the MO SMS message is invalid.

2. The apparatus of claim 1 wherein:

the interface is further configured to receive a notification message from an Authentication, Authorization, and Accounting (AAA) server in the broadband data network that the data session has been set up involving the mobile device; and

the message processor is further configured to process the notification message to identify the session information included in the notification message, to validate the session information, and to store the session information for the mobile device in the session database if valid.

3. The apparatus of claim 1 wherein:

the message processor is further configured to validate the MO SMS message by comparing a mobile IP (MIP) address in a header of the MO SMS message with a MIP address of the mobile device as stored in the session database.

4. The apparatus of claim 1 wherein:

the message processor is further configured to validate the MO SMS message by comparing a mobile directory number (MDN) in a header of the MO SMS message with an MDN of the mobile device as stored in the session database.

5. The apparatus of claim 1 wherein:

the message processor is further configured to validate the MO SMS message by comparing a session setup timestamp in a header of the MO SMS message with a session setup timestamp as stored in the session database.

6. The apparatus of claim 1 wherein:

the SMS-C is configured to receive a Mobile Terminated (MT) SMS message destined for the mobile device, to store the MT SMS message, to determine whether the mobile device has broadband data capabilities, and to forward the MT SMS message to the broadband data network responsive to a determination that the mobile device has broadband data capabilities.

7. The apparatus of claim 6 wherein:

the SMS-C is configured to identify a pre-provisioned address for the broadband messaging gateway, to check the availability of the broadband messaging gateway, and to forward the MT SMS message to the broadband messaging gateway based on the pre-provisioned address if the broadband messaging gateway is available.

8. The apparatus of claim 6 wherein:

the SMS-C is configured to receive an error message from the broadband messaging gateway indicating that the MT SMS message cannot be delivered over the broadband data network, and to forward the MT SMS message to the voice network in response to the error message as a fail over.

9. The apparatus of claim 1 wherein:

the interface is further configured to receive a MT SMS message destined for the mobile device; and

the message processor is further configured to verify a status of the data session involving the mobile device in the broadband data network, to identify a mobile IP (MIP) address for the mobile device if the status of the data session is active, and to route the MT SMS message to the mobile device through the interface based on the MIP address.

10. A method comprising:

storing session information in a broadband messaging gateway for a mobile device that has established a data session over a broadband data network;

receiving a Mobile Originated (MO) Short Message Service (SMS) message in the broadband messaging gateway from the mobile device;

verifying that the MO SMS message is valid by comparing header information of the MO SMS message with the stored session information;

identifying a Short Message Service Center (SMS-C) for the MO SMS message if the MO SMS message is valid;

and routing the MO SMS message to the identified SMS-C; and

sending an error message over the broadband to the mobile device to cause the mobile device to attempt to send the MO SMS message over a voice network as a fail over when the MO SMS message is invalid.

11. The method of claim 10 further comprising:

receiving a notification message in the broadband messaging gateway from an Authentication, Authorization, and Accounting (AAA) server in the broadband data network that the data session has been set up involving the mobile device;

processing the notification message to identify the session information included in the notification message;

validating the session information; and

storing the session information for the mobile device if valid.

12. The method of claim 10 wherein verifying that the MO SMS message is valid comprises:

comparing a mobile IP (MIP) address in a header of the MO SMS message with a stored MIP address of the mobile device.

13. The method of claim 10 wherein verifying that the MO SMS message is valid comprises:

comparing a mobile directory number (MDN) in a header of the MO SMS message with a stored MDN of the mobile device.

14. The method of claim 10 wherein verifying that the MO SMS message is valid comprises:

comparing a session setup timestamp in a header of the MO SMS message with a stored session setup timestamp.

15. The method of claim 10 further comprising:

receiving a Mobile Terminated (MT) SMS message destined for the mobile device in the SMS-C;

storing the MT SMS message;

determining whether the mobile device has broadband data capabilities; and

forwarding the MT SMS message to the broadband data network responsive to a determination that the mobile device has broadband data capabilities.

16. The method of claim 14 further comprising:

receiving an error message in the SMS-C from the broadband messaging gateway indicating that the MT SMS message cannot be delivered over the broadband data network; and

forwarding the MT SMS message to a voice network in response to the error message as a fail over.

17. The method of claim 10 further comprising:

receiving a Mobile Terminated (MT) SMS message destined for the mobile device in the broadband messaging gateway;

verifying a status of the data session involving the mobile device in the broadband data network;

identifying a mobile IP (MIP) address for the mobile device if the status of the data session is active; and

routing the MT SMS message to the mobile device based on the MIP address.

Assignments (8)
PATENT SECURITY AGREEMENT Recorded Aug 6, 2024
From: RPX CORPORATION; RPX CLEARINGHOUSE LLC
To: BARINGS FINANCE LLC, AS COLLATERAL AGENT
Reel/Frame 068328/0674 →
RELEASE OF LIEN ON PATENTS Recorded Aug 5, 2024
From: BARINGS FINANCE LLC
To: RPX CORPORATION
Reel/Frame 068328/0278 →
PATENT SECURITY AGREEMENT Recorded Apr 22, 2023
From: RPX CORPORATION
To: BARINGS FINANCE LLC, AS COLLATERAL AGENT
Reel/Frame 063429/0001 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Dec 28, 2021
From: PROVENANCE ASSET GROUP LLC
To: RPX CORPORATION
Reel/Frame 059352/0001 →
RELEASE OF SECURITY INTEREST Recorded Nov 30, 2021
From: CORTLAND CAPITAL MARKETS SERVICES LLC
To: PROVENANCE ASSET GROUP HOLDINGS LLC; PROVENANCE ASSET GROUP LLC
Reel/Frame 058983/0104 →
RELEASE OF SECURITY INTEREST Recorded Nov 30, 2021
From: NOKIA US HOLDINGS INC.
To: PROVENANCE ASSET GROUP HOLDINGS LLC; PROVENANCE ASSET GROUP LLC
Reel/Frame 058363/0723 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Nov 22, 2011
From: ALCATEL-LUCENT USA INC.
To: ALCATEL LUCENT
Reel/Frame 027269/0694 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jun 1, 2009
From: BHATT, JAY; CAI, YIGANG; CURTIS, ALAN; MORGAN, RUSSELL; SHANKER, GYAN
To: ALCATEL-LUCENT USA INC.
Reel/Frame 022762/0557 →