System and method for routing inter-carrier short message service or multimedia message service messages

• US 7,746,864 B1
• Filed: 04/30/2008
• Issued: 06/29/2010
• Est. Priority Date: 04/30/2008
• Status: Active Grant

• Current Assignee: Cellco Partnership, Inc. (Verizon Communications Inc.)
• Original Assignee: Cellco Partnership, Inc. (Verizon Communications Inc.)
• Inventors: Roberts, Brandie Proctor, Asawa, Manjari
• Primary Examiner(s): Cho; Hong
• Assistant Examiner(s): Scheibel; Robert C
• Application Number:
  US12/149,311
• Time in Patent Office: 790 Days
• Field of Search: None
• US Class Current: 370/392
• CPC Class Codes: H04L 45/00 Routing or path finding of packets in data switching networks routing or path finding in wireless networks H04W40/00
• CPC Class Codes: H04L 51/214 using selective forwarding
• CPC Class Codes: H04L 51/48 Message addressing, e.g. address format or anonymous messages, aliases
• CPC Class Codes: H04L 51/58 Message adaptation for wireless communication
• CPC Class Codes: H04W 40/02 Communication route or path selection, e.g. power-based or shortest path routing

Abstract

A message originates from a mobile station which is operable within a wireless network. In disclosed examples, the wireless network has a Messaging Service Center (MSC). The MSC determines whether the MSC stores a Uniform Resource Identifier (URI) corresponding to a destination mobile directory number (MDN) that is inputted via the mobile station. Then, the MSC sends the message to the URI corresponding to the MDN if the first MSC stores the URI corresponding to the MDN. The MSC sends a request to find the URI corresponding to the destination MDN to an external tElephone NUmber Mapping (ENUM) server, if the first MSC does not store the URI corresponding to the destination MDN. The MSC sends the message to the URI corresponding to the destination MDN if the external ENUM server sends the URI corresponding to the destination MDN. The MSC also indicates charging policy for delivery of message based on a billing identification corresponding to the destination MDN or URI that is stored in the MSC in the same table.

Claims

1. A method for routing mobile messaging service (MMS) messages originating from any of a plurality of mobile stations which is operable within a wireless network of a carrier, the wireless network of the carrier having a mobile messaging service center (MMSC), comprising steps of:

(a) for each respective MMS message received at the MMSC from any of the mobile stations through the carrier'"'"'s wireless network, determining whether the MMSC stores a Uniform Resource Identifier (URI) corresponding to a destination mobile directory number (MDN), which is contained in the respective MMS message; and

(b) forwarding a first of the received MMS messages from the MMSC to a network of another carrier based on the URI stored in the MMSC corresponding to the MDN contained in the first MMS message, when the MMSC stores the URI corresponding to the MDN contained in the first MMS message;

(c) obtaining a URI corresponding to the destination MDN of a second of the received MMS messages from an external telephone number mapping (ENUM) server, when the MMSC does not store the URI corresponding to the destination MDN contained in the second MMS message; and

(d) forwarding the second MMS message from the MMSC to a network of another carrier based on the URI obtained from the external ENUM server.

2. The method of claim 1, wherein the step (b) includes:

forwarding the first MMS message to an inter-carrier gateway;

sending the first MMS message by the inter-carrier gateway to a second MMSC corresponding to the URI; and

sending the first MMS message by the second MMSC to a destination terminal corresponding to the URI.

3. The method of claim 1, further comprising:

charging for delivery of the first or second MMS message based on a billing identification corresponding to the destination MDN or URI stored in the first MMSC.

4. The method of claim 3, wherein the URI corresponding to the destination MDN and the billing identification corresponding to the destination MDN or URI are stored as a table in the first MMSC.

5. A multimedia messaging service (MMS) routing system for routing MMS messages received from any of a plurality of originating mobile stations which is operable within a wireless network of a carrier, the system comprising:

a multimedia messaging service center (MMSC) of the carrier'"'"'s network for routing each respective received MMS message based on a URI corresponding to a target mobile directory number (MDN) inputted via an originating mobile station contained in the respective MMS message;

a peer table having a routing domain field for defining URIs corresponding to MDNs stored the MMSC; and

an ENUM server for storing URIs corresponding to MDNs, coupled for communication with the MMSC,

wherein the MMSC is configured to;

refer to the peer table for finding a URI corresponding to the target MDN contained in a first of the respective received MMS messages and forward the first respective received MMS message to a network of another carrier based on the URI corresponding to the target MDN contained in the first respective received MMS message,

obtain from the ENUM server a URI corresponding to the target MDN contained in a second of the respective received MMS messages when the peer table does not have the URI corresponding to the target MDN contained in the second respective received MMS message, and

forward the second respective received MMS message to a network of another carrier based on the URI obtained from the ENUM server.

6. The system of claim 5, wherein the peer table includes billing identifiers corresponding to the MDNs or the returned URI for defining billing policy of carriers corresponding to the destination MDNs.

7. The system of claim 6, wherein the first MSC performs the charging for delivery of the message to the originating mobile station based on the billing identifiers stored in the peer table.

8. The system of claim 5, wherein the routing field in the peer table indicates the URI corresponding to the target MDN if available in the peer table or indicates to send a request to the ENUM server for translation of the target MDN to the corresponding URI.

9. The system of claim 5, further comprising:

a second MMSC corresponding to the URI obtained from the first MMSC;

an inter-carrier gateway for receiving the MMS message routed from the first MMSC and forwarding the MMS message to the second MMSC of a target carrier based on the URI obtained at the first MMSC.

10. An article, comprising:

a non-transitory machine readable storage medium; and

programming embodied in the non-transitory machine readable storage medium for execution by a programmable processor of a multimedia messaging service center (MMSC) of a wireless network of a carrier, for configuring the MMSC to perform functions comprising;

(a) receive mobile messaging service (MMS) messages originating from any of a plurality of mobile stations via the wireless network of the carrier;

(b) for each respective MMS message received at the MMSC from any of the mobile stations through the carrier'"'"'s wireless network, determine whether the MMSC stores a Uniform Resource Identifier (URI) corresponding to a destination mobile directory number (MDN), which is contained in the respective MMS message; and

(c) forward a first of the received MMS messages from the MMSC to a network of another carrier based on the URI stored in the MMSC corresponding to the MDN contained in the first MMS message, when the MMSC stores the URI corresponding to the MDN contained in the first MMS message;

(d) obtain a URI corresponding to the destination MDN of a second of the received MMS messages from an external telephone number mapping (ENUM) server, when the MMSC does not store the URI corresponding to the destination MDN contained in the second MMS message; and

(e) forward the second MMS message from the MMSC to a network of another carrier based on the URI obtained from the external ENUM server.