System and method for implementing a universal messaging gateway (UMG)

• US 7,447,219 B2
• Filed: 09/29/2003
• Issued: 11/04/2008
• Est. Priority Date: 09/29/2003
• Status: Active Grant

• Current Assignee: Redknee Inc.
• Original Assignee: Redknee Inc.
• Inventors: Meisl, Armin, Fiouzi, Leila
• Primary Examiner(s): Pezzlo; John
• Application Number:
  US10/671,798
• Publication Number:
  US 20050068971A1
• Time in Patent Office: 1,863 Days
• Field of Search: 370352-356, 370/400, 370/401, 370/466, 370/467, 370/278, 370/282, 370/252, 370/328, 370/329, 370/331, 455/466, 455/412.1
• US Class Current: 370/401
• CPC Class Codes: H04L 41/0213 Standardised network management protocols, e.g. simple network management protocol [SNMP]
• CPC Class Codes: H04L 51/066 Format adaptation, e.g. format conversion or compression
• CPC Class Codes: H04L 51/58 Message adaptation for wireless communication

Abstract

The system and method for implementing a Universal Messaging Gateway (UMG) disclosed herewith provides telecommunications Network Operators (NO) and like related parties with innovative and flexible art for delivering domestic and foreign network originated Multi-Media traffic and/or, more generally, interactive and/or synchronous mobile text and related telecommunications messaging or information services to a large number of related receiving telecommunications network equipment (as ESMEs and/or SMS-Cs in relation to SMS traffic).

Claims

1. A middleware platform system comprising:

at least one external short message entity (ESME);

at least one short message service center (SMSC);

a universal message gateway including a first common interface for connecting to said at least one ESME and a second common interface for connecting to said at least one SMSC;

said universal message gateway further including a home location register module and a mobile switching center module;

said home location register module and said mobile switching center module being configured to receive short message service traffic from said at least one SMSC; and

said universal message gateway being configured to direct said short message service traffic to a virtual mobile station address associated with said at least one ESME, wherein said universal message gateway is configured to implement a security and network management algorithm for blocking incoming said traffic based upon the SMSC from which said traffic was relayed or originated.

2. The system of claim 1, comprising a plurality of SMSCs wherein at least two of said SMSCs are disparate in design.

3. The system of claim 2, wherein at least one of said SMSCs sends domestic network originated telecommunications messaging traffic to said universal message gateway and another one of said SMSCs sends foreign network originated telecommunications messaging traffic to said universal message gateway.

4. The system of claim 1, where said first common interface includes a first receiver manager which interacts with said ESME, and said second common interface includes a second receiver manager which interacts with said SMSCs.

5. A computer program stored on a computer readable media when executed by a computer, said computer program comprising:

instructions for a universal message gateway having a first common interface for connecting to at least one external short message entity (ESME), a second common interface for connecting to at least one short message service center (SMSC), and a home location register module and a mobile switching center module configured to receive telecommunications messaging traffic from said at least one SMSC,

wherein the instructions configure said universal message gateway to direct said telecommunications messaging traffic to a virtual mobile station address associated with said at least one ESME, and wherein the instructions also configure said universal message gateway to implement a security and network management algorithm for blocking incoming said traffic based upon the SMSC from which said traffic was relayed or originated.

6. A middleware platform system comprising:

at least one external short message entity (ESME);

at least one short message service center (SMSC);

a universal message gateway including a first common interface for connecting to said at least one ESME and a second common interface for connecting to said at least one SMSC;

said universal message gateway further including a home location register module and a mobile switching center module;

said home location register module and said mobile switching center module being configured to receive short message service traffic from said at least one SMSC; and

said universal message gateway being configured to direct said short message service traffic to a virtual mobile station address associated with said at least one ESME,

wherein said common interfaces are configured to implement a throttling parameter defining a number of short message service messages that are permitted to be received from one of said SMSCs or directed to said ESME within a configurable time frame by said universal message gateway.

7. A universal message gateway comprising:

a first common interface for connecting to at least one external short message entity (ESME);

a second common interface for connecting to at least one short message service center (SMSC);

a home location register module and a mobile switching center module configured to receive telecommunications messaging traffic from said at least one SMSC; and

a routing engine connected to said first common interface, said second common interface, said home location register module, and said mobile switching center module;

wherein said routing engine is configured to direct said telecommunications messaging traffic to a virtual mobile station address associated with said at least one ESME, and wherein said common interfaces are configured to implement a throttling parameter defining a number of short message service messages that are permitted to be received from one of said SMSCs or directed to said ESME within a configurable time frame by said universal message gateway.

8. The gateway of claim 7, where telecommunications messaging traffic includes at least one of Multi-Media traffic, interactive and/or synchronous mobile text, and short message service traffic.

9. The universal message gateway of claim 7, wherein said at least one ESME is associated with an application service provider (ASP).

10. The universal message gateway of claim 7 wherein said telecommunications messaging traffic is routed to said at least one ESME within at least one of parameter selected from the group consisting of SMSC Connection ID, Termination TON/NPI/MSISDN, Origination TON/NPI/MSISDN, protocol ID, data coding scheme, and SMSC address.

11. The universal message gateway of claim 7 wherein said first common interface is based on the short message peer to peer (SMPP) protocol.

12. The universal message gateway of claim 7 wherein said routing engine is further configured to perform at least one of a throttling function, a queuing function, and a buffering function.

13. The universal message gateway of claim 7 further comprising an SMS reply server configured to generate a response message to confirm a successful delivery of a message to said at least one ESME.