System and method for a messaging gateway

• US 7,003,307 B1
• Filed: 01/30/2003
• Issued: 02/21/2006
• Est. Priority Date: 01/31/2002
• Status: Active Grant

• Current Assignee: Cellco Partnership, Inc. (Verizon Communications Inc.)
• Original Assignee: Cellco Partnership, Inc. (Verizon Communications Inc.)
• Inventors: Kupsh, Jerry, Chen, Xuming
• Primary Examiner(s): Tran, CongVan
• Application Number:
  US10/354,885
• Time in Patent Office: 1,118 Days
• Field of Search: 455/466, 455/403, 455/412, 455/414.1, 455/418, 455/424, 455/445, 455/454, 370355-360, 370/395.31, 370/395.1
• US Class Current: 455/466
• CPC Class Codes: H04L 51/58 Message adaptation for wireless communication
• CPC Class Codes: H04W 88/184 Messaging devices, e.g. message centre

Abstract

A system and method for routing a mobile message is presented. The method and system receive the mobile message at a mobile messaging gateway; and determine, at the mobile messaging gateway, the intended destination of the mobile message. The intended destination of the mobile message is one of an external messaging entity (ESME) and a Short Message Service Center (SMSC).

Claims

1. A mobile messaging gateway for routing mobile messages, comprising:

a first port for receiving from an External Short Messaging Entity (ESME), a mobile message destined for a Short Message Service Center (SMSC);

a second port for sending to an ESME, a mobile message sent from an SMSC;

a third port for receiving from an SMSC, a mobile message destined for an ESME;

a fourth port for sending to an SMSC, a mobile message sent from an ESME;

a web-based interface for providing administrative control of the gateway via a web browser; and

a micro-processor for controlling operation of the mobile messaging gateway, the operation including routing mobile messages from the ESME to the SMSC based on the identity of the ESME and from the SMSC to the ESME based on one of the identity of the destination of the mobile message and the identity of the SMSC.

2. The mobile messaging gateway of claim 1, including:

one or more routing tables, the one or more routing tables having entries identifying the route of mobile messages received by the mobile messaging gateway.

3. The mobile messaging gateway of claim 1, including:

a database, the database being programmed to record mobile message traffic passing through the mobile messaging gateway.

4. The mobile messaging gateway of claim 3, wherein the database is located remote from the mobile messaging gateway.

5. The mobile messaging gateway of claim 1, the mobile messaging gateway being programmed to emulate the operation of an ESME and an SMSC, whereby the first and second ports output data signals commensurate with data signals that are output by an SMSC and the third and fourth ports output data signals that are commensurate with data signals output by an ESME.

6. The mobile messaging gateway of claim 1, the mobile messaging gateway including memory storage for queuing one or more mobile messages destined for one of the ESME and SMSC when the one of the ESME and SMSC is not capable of receiving a mobile message from the mobile messaging gateway.

14. The method of claim 1, including the step of incrementing a charge balance associated with the ESME.

23. The messaging gateway as in claim 6 wherein the memory storage for queuing one or more mobile messages is RAM memory and a portion of said RAM memory is segmented as multiple FIFO queues, each FIFO queue associated with a different one of the ESME and SMSC.

7. A method for routing a mobile message, the method comprising the steps of:

receiving the mobile message at a mobile messaging gateway;

determining, at the mobile messaging gateway, the intended destination of the mobile message, wherein the intended destination of the mobile message is one of an external messaging entity (ESME) and a Short Message Service Center (SMSC); and

queuing one or more mobile messages destined for one of the ESME and SMSC when the one of the ESME and SMSC is not capable of receiving a moblie message from the mobile messaging gateway.

8. The method of claim 7, wherein the determination of the intended destination of the mobile message is based on the identity of the ESME when the mobile message is received from the ESME and is based on one of the identity of the intended destination of the mobile message and the identity of the SMSC when the mobile message is received from the SMSC.

9. The method of claim 7, wherein the step of determining the intended destination of the mobile message includes the step of referencing one or more routing tables.

10. The method of claim 7, including the step of recording the passage of the mobile message through the mobile messaging gateway.

11. The method of claim 10, including the step of utilizing the record of the passage of the mobile message through the mobile messaging gateway for controlling the rate of passage of mobile message traffic through the mobile messaging gateway.

12. The method of claim 7, including the steps of determining whether the intended destination of the mobile message is presently able to accept the mobile message.

13. The method of claim 12, including the step of queuing the mobile message if a determination is made that the intended destination is not presently able to accept the mobile message.

15. A method for controlling the flow of mobile message traffic between a mobile messaging center of a wireless network and a mobile messaging routing device located external to the wireless network, the method comprising the steps of:

receiving packetized data at a mobile messaging gateway, the packetized data including information to facilitate delivery of a mobile message, the mobile messaging gateway being disposed between the mobile messaging center and the external mobile messaging routing device;

determining the intended destination of the mobile message based on information contained in the data received at the mobile messaging gateway;

sending the mobile message to its intended destination;

recording the utilization of the mobile messaging gateway to send the mobile message to its intended destination;

determining the ability to send additional mobile messages to the intended destination by referencing the recorded utilization of the mobile messaging gateway.

16. The method of claim 15, including the step of preventing the sending of additional mobile messages to the intended destination upon determination that the intended destination is not presently capable of receiving additional mobile messages.

17. The method of claim 16, including the step of queuing the additional mobile messages until the intended destination is capable of receiving additional mobile messages.

18. The method of claim 15, wherein a wireless device operating on the wireless network originates the mobile message.

19. The method of claim 15, wherein a land-line-based device operating external to the wireless network, originates the mobile message.

20. The method of claim 19, including the step of sending an additional mobile message to a destination that is different from the intended destination upon determination that the intended destination is not presently capable of receiving additional mobile messages.

21. A mobile messaging gateway for routing mobile messages, comprising:

a first port for receiving from an External Short Messaging Entity (ESME), a mobile message destined for a Short Message Service Center (SMSC);

a second port for sending to an ESME, a mobile message sent from an SMSC;

a third port for receiving from an SMSC, a mobile message destined for an ESME;

a fourth port for sending to an SMSC, a mobile message sent from an ESME;

provisioning for a virtual private network for providing administrative control of the gateway via a private network connection; and

a micro-processor for controlling operation of the mobile messaging gateway, the operation including routing mobile messages from the ESME to the SMSC based on the identity of the ESME and from the SMSC to the ESME based on one of the identity of the destination of the mobile message and the identity of the SMSC.

22. The messaging gateway as in claim 21 wherein the private network is one of an intranet or internet.

24. The mobile messaging gateway of claim 21, including:

one or more routing tables, the one or more routing tables having entries identifying the route of mobile messages received by the mobile messaging gateway.

25. The mobile messaging gateway of claim 21, including:

a database, the database being programmed to record mobile message traffic passing through the mobile messaging gateway.

26. The mobile messaging gateway of claim 25, wherein the database is located remote from the mobile messaging gateway.

27. The mobile messaging gateway of claim 21, the mobile messaging gateway being programmed to emulate the operation of an ESME and an SMSC, whereby the first and second ports output data signals commensurate with data signals that are output by an SMSC and the third and fourth ports output data signals that are commensurate with data signals output by an ESME.

28. The mobile messaging gateway of claim 21, the mobile messaging gateway including memory storage for queuing one or more mobile messages destined for one of the ESME and SMSC when the one of the ESME and SMSC is not capable of receiving a mobile message from the mobile messaging gateway.