Patent Application
20080240117
Not Applicable
Not Applicable
Not Applicable
This invention relates to radio telecommunication systems. More particularly, and not by way of limitation, the invention is directed to a system, method, and interworking function for interfacing the Multimedia Messaging Service (MMS) and the IP Multimedia Subsystem (IMS) messaging systems.
MMS is a standard telephony messaging system that enables users to send messages that includes multimedia objects (for example, images, audio, video, or rich text) in addition to plain text messages as in the earlier developed Short Message Service (SMS). MMS is mainly deployed in cellular networks along with other messaging systems like SMS, Mobile Instant Messaging, and Mobile E-Mail. The MMS addressing scheme utilizes ISDN or E.164 numbers (for example, 0015143457900) in the TO and FROM fields of packet headers.
IMS is an architectural framework originally designed by the Third Generation Partnership Project (3GPP) for evolving mobile networks beyond GSM and delivering IP multimedia services to end users. In its original form, IMS provided an approach for delivering “Internet Services” over GPRS. This vision was subsequently updated by 3GPP, 3GPP2, and TISPAN by providing requirements for support of networks other than GPRS such as Wireless LAN, CDMA2000, and Fixed Line.
To ease the integration with the Internet, the IMS as far as possible utilizes Internet Engineering Task Force (IETF) protocols such as the Session Initiation Protocol (SIP). Therefore, the IMS addressing scheme uses SIP Uniform Resource Identifiers (URIs) (for example, sip:usera@domain1.com) in the TO and FROM fields of packet headers. A problem arises, therefore, when an IMS user and an MMS user desire to communicate because the MMS addressing scheme is not compatible with the IMS addressing scheme. There is presently no known solution for making these addressing schemes compatible.
What is needed in the art is a system, method, and interworking function for interfacing the Multimedia Messaging Service (MMS) and the IP Multimedia Subsystem (IMS), thereby enabling IMS and MMS messages to be transported to users in the other system. The present invention provides such a system, method, and interworking function.
The present invention enables the sending of IMS messages to MMS users and the sending of MMS messages to IMS users between two different operator domains. Installed Multimedia Messaging Service Centers (MMSCs) can be upgraded with the present invention to interwork with IMS systems.
Thus, in one aspect, the present invention is directed to a system for providing interoperability between the Multimedia Messaging Service (MMS) and the IP Multimedia Subsystem (IMS). The system includes logic within a multimedia messaging service center for determining whether a received MMS message includes an indication that the MMS message is destined for an IMS user; and routing logic within the multimedia messaging service center for selectively routing the MMS message to either an email server or an interworking function. The MMS message is routed to the email server if the MMS message does not include an indication that the MMS message is destined for an IMS user, and the MMS message is routed to the interworking function if the MMS message includes an indication that the MMS message is destined for an IMS user. The system also includes logic within the interworking function for converting a destination address in the MMS message to a destination address for the IMS user that is routable through a Session Initiation Protocol (SIP) core network; and an output interface for sending the converted MMS message to the SIP core network for routing to the IMS user.
The interworking function may also include an input interface for receiving through the SIP core network, an IMS message destined for an MMS user; mapping logic for converting a source address of the received IMS message from a SIP address to an MMS address; and a second output interface for sending the converted IMS message to the multimedia messaging service center for forwarding to the MMS user.
In another aspect, the present invention is directed to a method of interfacing the MMS and the IMS messaging systems. The method includes the steps of determining within a multimedia messaging service center whether a received MMS message includes an indication that the MMS message is destined for an IMS user; and selectively routing the MMS message from the multimedia messaging service center to either an email server or an interworking function, wherein the MMS message is routed to the email server if the MMS message does not include an indication that the MMS message is destined for an IMS user, and the MMS message is routed to the interworking function if the MMS message includes an indication that the MMS message is destined for an IMS user. The method also includes converting by the interworking function, a destination address in the MMS message to a destination address for the IMS user that is routable through a Session Initiation Protocol (SIP) core network; and sending the converted MMS message from the interworking function to the SIP core network for routing to the IMS user.
In another aspect, the present invention is directed to a multimedia messaging service center for providing seamless communications between MMS users and IMS users. The multimedia messaging service center includes address resolution logic for determining whether a received MMS message is addressed to a destination MMS user or a destination IMS user; and routing logic for selectively routing the MMS message to the destination MMS user or the destination IMS user based on a determination by the address resolution logic.
The address resolution logic may include logic for detecting an indication that the destination address is not in standard MMS format, and logic for detecting a SIP prefix prior to a destination address in a TO field of the received MMS message, wherein the SIP prefix indicates the MMS message is addressed to a destination IMS user. The routing logic is adapted to route the MMS message to a SIP core network when the address resolution logic detects the SIP prefix. The multimedia messaging service center may also include logic for selectively mapping the MMS message to either a SIP MESSAGE format or a Message Session Relay Protocol (MSRP) format when the MMS message is routed to the SIP core network.
In the following, the essential features of the invention will be described in detail by showing preferred embodiments, with reference to the attached figure in which:
In one embodiment, the present invention is an MMS-IMS interworking function (IWF) providing address conversion for IMS messages destined for MMS users, and providing address conversion and routing services for MMS messages destined for IMS users. The IWF performs the normal functions of a conventional Multimedia Messaging Service Center (MMSC) (for example, storing and forwarding MMS messages sent between MMS users) while also solving several problems which prevent interoperability between MMS and IMS users. For example, the logic in a conventional MMSC supports receiving an MMS message that is destined for MM1, MM3, MM4, and MM7 but not a SIP destination. Therefore, if a conventional MMSC receives an MMS message addressed to an IMS user (i.e., the TO field contains a SIP URI instead of an E.164 number), the MMSC will reject the message outright because the SIP URI is not a legal/standard MMS address. Additionally, if the prior art MMSC receives an MMS message addressed to an MMS user from an IMS user (i.e., the FROM field contains a SIP URI instead of an E.164 number), the MMSC cannot send the message to the MMS user because the MMS client in the MMS user's User Equipment (UE) does not support having a SIP URI in the FROM field of a received MMS message.
For illustrative purposes,
In this embodiment, UE-B 19 modifies the TO address of the MMS message from the conventional MMS format to indicate to the MMSC 16 that the message requires routing analysis. Any suitable methodology may be utilized to indicate that the message requires routing analysis. For example, a specific bit may be set as an indicator flag, or the normal MMS format may be otherwise altered. In one embodiment, the entire TO field may be put in quotes (i.e., “TO FIELD”) to indicate to the MMSC 16 that the address field is in a different format. Additionally, a “sip:” prefix may be placed in front of UE-A's address to tell the MMSC that the address is actually a SIP URI. In this case, the routing logic 27 in the MMSC routes the message to the IWF 17 where it is converted for transport through the SIP Core network 13. It should be noted that the address identifier that comes after the “sip:” prefix may be an E.164 number (i.e., 0015143457900) or string alias address such as “jojo”.
For example, the MMS TO field may read:
Alternatively the MMS TO field may read:
The MMS FROM field may read:
When the MMSC receives the MMS message 41, the routing logic 27 in the MMSC determines the proper message routing. The MMSC stores the MMS message in the MFS 26 and attempts to perform an address resolution on the TO address field. If a conventional MMS message is received (i.e., an MMS message addressed to another MMS user), the MMSC will route the message to the MTA 23 (
The MMSC is modified in this embodiment of the present invention to recognize that the TO field contains an address field that is encapsulated in quotes and also begins with the “sip:” prefix. Therefore, the MMSC 16 detects that the message is not destined for an MMS user, but rather for an IMS user, and selects the SIP route to send the message. The modified MMSC automatically stops any further address analysis and at step 43 passes the MMS reply message to the IWF 17. The IWF removes the quotes from the TO field, and removes the “/TYPE=PLMN” from the TO field, if present. At block 44, logic in the PMM 18a then utilizes the SIP Stack 18b to decompose the MMS message and perform header mapping from the MMS format to either SIP MESSAGE or Message Session Relay Protocol (MSRP) format. The selected format depends on the size of the overall message received. If the message is 1300 bytes or less, then the SIP MESSAGE format may be utilized. If the message is more than 1300 bytes, MSRP may be the selected format.
The IWF 17 sends the SIP MESSAGE or MSRP formatted message 45 to the SIP Core network 13. Once the message is successfully sent, the IWF 17 receives a 200 OK or 202 ACCEPTED message in response (not shown). The IWF informs the MMSC 16, which removes the message from the MFS 26. The SIP Core network receives the SIP MESSAGE or MSRP formatted message and utilizes the TO address field (or the Request-URI) to route the message internally to the proper Call State Control Function (CSCF) for UE-A 11. In this case, Operator-A's CSCF (not shown) receives the message. At step 46 (
Thus, to enable MMS to IMS redirection, specifically in a reply scenario, the present invention introduces several new features in the MMSC 16. The invention masquerades the FROM field to contain a SIP URI instead of an E.164 number for the purposes of routing back to the IMS user. The invention also introduces the IWF 17, with its PMM 18a and SIP Stack 18b (which may be implemented in the MMSC or separately) to enable routing to the SIP Core network 13 in addition to the existing interfaces. The invention also introduces logic in the MMSC to properly route a received MMS message based on the recipient's TO field. For example, the existing functionality may be extended so that when the MMSC receives an MMS message that has a TO field in the format “sip:user@domain.com”, the MMSC recognizes that this is an IMS user and routes the call to the SIP Core network.
At step 57, the IWF 17 reformats the MMS message to SIP MESSAGE or MSRP format, and at step 58 sends the reformatted message to the SIP core network 13. At step 59, the step core network routes the reformatted message to the CSCF for UE-A 11. At step 60, the CSCF sends the message to the IM AS 14. At step 61, the IM AS converts the message and creates a new IMS message and returns it to the CSCF. At step 62, the CSCF routes the IMS message to UE-A.
In this embodiment, all message header conversions (IMS to MMS, MMS to IMS, and the like) take place in the IWF 17, under the control of the MMSC 16. This means that the MMSC controls the routing and the address conversion functions of all MMS messages originating within the service area of Operator-B 15. Conventional MMS messages destined for other MMS users are routed to the MTA 23 while unconventional MMS messages are routed to the IWF 17.
Although preferred embodiments of the present invention have been illustrated in the accompanying drawings and described in the foregoing Detailed Description, it is understood that the invention is not limited to the embodiments disclosed, but is capable of numerous rearrangements, modifications, and substitutions without departing from the scope of the invention. The specification contemplates any all modifications that fall within the scope of the invention defined by the following claims.
