IP Library Granted Patent US 9,307,371
Granted Patent B2
US 9,307,371 · App. 12/016,260 · Granted Apr 5, 2016

Method and system for SMS/MMS messaging to a connected device

Inventors: Ashutosh K. Sureka (Irving, TX); Michael J. Naggar (Frisco, TX); Scott A. Evans (Carrollton, TX); Puneet Kalia (Kukkatpally, IN); Wei X. Liu (Flower Mound, TX); Gangadhar Rao Gogineni (Moulali, IN); Rahim Charania (Euless, TX); Shuchi R. Patel (Frisco, TX)
Assignee: Verizon Patent and Licensing Inc.
H04W4/14
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 9,307,371
App. No.
12/016,260
Granted
Apr 5, 2016
Kind
B2
Abstract

The method and system for SMS/MMS messaging to a connected device may be realized as a system comprising at least one server module. The at least one server module may be adapted to receive from a connected device an outbound messaging message through a packet-based network. The at least one server module may also be adapted to send the outbound messaging message to an external messaging network. The connected device may be communicatively coupled to the packet-based network. The outbound messaging message may be associated with a user account. The user account may be associated with a telephone number.

Claims (96)

1. A system comprising:

at least one server to:

receive, from a connected device and via a packet-based network, an outbound messaging message;

identify a contact identifier in the outbound messaging message;

replace the contact identifier with a telephone number in the outbound messaging message based on a user account associated with the outbound messaging message;

query at least one routing database to identify a network address of a recipient gateway associated with the telephone number,

the recipient gateway being at least one of a Short Message Service (SMS) gateway or a Multimedia Messaging Service (MMS) gateway; and

send, via an external messaging network, the outbound messaging message to the recipient gateway by using the network address,

the connected device being communicatively coupled to the packet-based network.

2. The system of claim 1 , wherein the connected device is one of a land-based telephony device, a VoIP telephony device, or a network connected digital device.

3. The system of claim 1 , wherein the at least one server is further to:

receive, from the external messaging network, an inbound messaging message; and

send the inbound messaging message to the connected device through the packet-based network.

4. The system of claim 1 , wherein the outbound messaging message is one of a Short Message Service (SMS) message or a Multimedia Messaging Service (MMS) message.

5. The system of claim 1 , wherein the at least one server is further to:

manage the outbound messaging message.

6. The system of claim 1 , wherein the at least one server is further to:

store the outbound messaging message in an outbox of the user account.

7. The system of claim 3 , wherein the at least one server is further adapted to:

manage the inbound messaging message in an inbox.

8. The system of claim 7 , wherein the inbox is managed for the user account.

9. The system of claim 8 ,

wherein a contact list is maintained for the user account, and

wherein the contact list includes the contact identifier.

10. The system of claim 1 ,

wherein the at least one server comprises a Simple Mail Transfer Protocol (SMTP) server communicatively coupled to the external messaging network, and

wherein the SMTP server is to:

receive an inbound messaging message from the external messaging network over a SMTP connection.

11. A system comprising:

at least one server to:

receive, from an external messaging network, an inbound messaging message;

identify an originating telephone number in the inbound messaging message;

determine that the originating telephone number is associated with a contact identifier in a contact list;

replace the telephone number with the contact identifier in the inbound messaging message based on determining that the telephone number is associated with the contact identifier;

send the inbound messaging message to a connected device through a packet-based network,

the connected device being communicatively coupled to the packet-based network;

receive, from the connected device, an outbound messaging message through the packet-based network;

query at least one routing database to identify a network address of a recipient gateway associated with a recipient telephone number,

the recipient telephone number being associated with the outbound messaging message, and

the recipient gateway being at least one of a Short Message Service (SMS) gateway or a Multimedia Messaging Service (MMS) gateway; and

send the outbound messaging message to the external messaging network using the network address.

12. The system of claim 11 , wherein the connected device is one of a land-based telephony device, a VoIP telephony device, or a network connected digital device.

13. The system of claim 11 , wherein the at least one server is further to:

manage the inbound messaging message in an inbox of a user account.

14. The system of claim 11 , wherein the at least one server is further to:

store the outbound messaging message in an outbox of a user account.

15. A method comprising:

receiving, by a first gateway server, an inbound message from an external network;

forwarding, by the first gateway server and via a packet-based network, the inbound message to a connected device communicatively coupled to the packet-based network;

receiving, by the first gateway server and from the connected device, an outbound messaging message via the packet-based network;

identifying, by the first gateway server, a contact identifier in the outbound messaging message;

replacing, by the first gateway server, the contact identifier with a telephone number in the outbound messaging message based on a user account associated with the outbound messaging message;

querying, by the first gateway server, at least one routing database to identify a network address of a second gateway server associated with the telephone number,

the second gateway server being at least one of a Short Message Service (SMS) gateway or a Multimedia Messaging Service (MMS) gateway; and

sending, by the first gateway server, the outbound messaging message to the external messaging network using the network address.

16. The method of claim 15 , wherein the connected device is one of a land-based telephony device, a VoIP telephony device, or a network connected digital device.

17. The method of claim 15 , further comprising:

storing the inbound message in an inbox of the user account,

wherein forwarding the inbound messaging message comprises:

sending a notice about the inbound message to the connected device;

receiving a request to retrieve the inbound message;

querying the inbox of the user account for the inbound message; and

providing the inbound message to the connected device.

18. The method of claim 16 , further comprising;

mapping the telephone number to a name in a contact list of the user account, the name being the contact identifier.

19. A non-transitory computer readable medium storing instructions, the instructions comprising:

one or more instructions that, when executed by at least one processor, cause the at least one processor to:

receive an outbound message from a connected device via a packet-based network,

the connected device being communicatively coupled to the packet-based network;

identify a contact identifier in the outbound messaging message;

replace the contact identifier with a telephone number in the outbound messaging message based on a user account associated with the outbound messaging message;

query at least one routing database to identify a network address of a recipient gateway associated with the telephone number,

the recipient gateway being at least one of a Short Message Service (SMS) gateway or a Multimedia Messaging Service (MMS) gateway; and

forward the outbound message to an external network using the network address.

20. The non-transitory computer readable medium of claim 19 , wherein the connected device is one of a land-based telephony device, a VoIP telephony device, or a network connected digital device.

21. The non-transitory computer readable medium of claim 19 , wherein the contact identifier is a name in a contact list of the user account.

22. A method comprising:

receiving, by a first gateway server, an inbound message from an external network;

identifying, by the first gateway server, an originating telephone number in the inbound message;

determining, by the first gateway server, that the originating telephone number is associated with a contact identifier in a contact list;

replacing, by the first gateway server, the telephone number with the contact identifier in the inbound message based on determining that the telephone number is associated with the contact identifier;

forwarding, by the first gateway server and via a packet-based network, the inbound message to a land-wired network connected device communicatively coupled to the packet-based network;

receiving, by the first gateway server and from the land-wired network connected device, an outbound messaging message via the packet-based network;

querying, by the first gateway server, at least one routing database to identify a network address of a second gateway server based on the outbound messaging message,

the second gateway server being at least one of a Short Message Service (SMS) gateway or a Multimedia Messaging Service (MMS) gateway; and

sending, by the first gateway server, the outbound messaging message to the external messaging network.

23. The method of claim 22 , further comprising:

storing the inbound message in an inbox of a user account,

where forwarding the inbound message comprises:

sending a notice about the inbound message to the land-wired network connected device;

receiving, from the land-wired network connected device, a request to retrieve the inbound message;

querying, based on the request, the inbox of the user account for the inbound message; and

providing the inbound message to the land-wired network connected device.

24. The method of claim 22 , further comprising:

identifying the contact identifier in the outbound messaging message after receiving the outbound messaging message; and

replacing the contact identifier with the telephone number before sending the outbound messaging message.

Assignments (8)
CORRECTIVE ASSIGNMENT TO REMOVE SERIAL NUMBER 11/505,281 PREVIOUSLY RECORDED AT REEL: 023420 FRAME: 0484. ASSIGNOR(S) HEREBY CONFIRMS THE ASSIGNMENT. Recorded Aug 15, 2014
From: VERIZON DATA SERVICES INDIA PRIVATE LIMITED
To: VERIZON PATENT AND LICENSING INC.
Reel/Frame 033549/0791 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 26, 2009
From: VERIZON DATA SERVICES INDIA PRIVATE LIMITED
To: VERIZON PATENT AND LICENSING INC.
Reel/Frame 023420/0484 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 18, 2009
From: VERIZON BUSINESS NETWORK SERVICES INC.
To: VERIZON PATENT AND LICENSING INC.
Reel/Frame 023250/0710 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 18, 2009
From: VERIZON DATA SERVICES LLC
To: VERIZON PATENT AND LICENSING INC.
Reel/Frame 023251/0278 →
CHANGE OF NAME Recorded Sep 14, 2009
From: VERIZON DATA SERVICES INC.
To: VERIZON DATA SERVICES LLC
Reel/Frame 023224/0333 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jan 18, 2008
From: KALIA, PUNEET; GOGINENI, GANGADHAR RAO
To: VERIZON DATA INDIA PRIVATE LIMITED VICEROY
Reel/Frame 020382/0194 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jan 18, 2008
From: EVANS, SCOTT
To: VERIZON BUSINESS NETWORK SERVICES, INC.
Reel/Frame 020382/0215 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jan 18, 2008
From: SUREKA, ASHUTOSH K.; PATEL, SHUCHI R.; NAGGAR, MICHAEL J.; LIU, WEI X.; CHARANIA, RAHIM
To: VERIZON DATA SERVICES INC.
Reel/Frame 020388/0262 →
Continuity (1)
Related Publication 20090186634A1 · Jul 23, 2009