EP1757113A2

EP1757113A2 - Method to qualify multimedia message content to enable use of a single internet address domain to send messages to both short message service centers and multimedia message service centers

Info

Publication number: EP1757113A2
Application number: EP05746236A
Authority: EP
Inventors: Carl S. Johnson, Jr.; Mike Dewey; Nikhil Bhadange
Original assignee: TeleCommunication Systems Inc
Current assignee: TeleCommunication Systems Inc
Priority date: 2004-05-06
Filing date: 2005-05-06
Publication date: 2007-02-28
Also published as: EP1757113A4; WO2005109919A3; WO2005109919A2

Abstract

A multimedia messaging service (MMS) intelligent content evaluator gateway is provided to allow use of a single address mailbox and Internet domain for receipt of either an MMS or an SMS message. The MMS intelligent content evaluator gateway evaluates the content of a received message, and then forwards the same to the appropriate system for delivery. The MMS intelligent content evaluator gateway makes use of database tables containing subscriber information and message routing tables necessary to derive the MMS and SMS destination addresses for each subscriber or range of subscriber addresses. Tables may also be implemented indicating the capabilities of each subscriber’s handset, such as whether or not the handset can support MMS messages.

Description

METHOD TO QUALIFY MULTIMEDIA MESSAGE CONTENT TO ENABLE USE OF A SINGLE INTERNET ADDRESS DOMAIN TO SEND MESSAGES TO BOTH SHORT MESSAGE SERVICE CENTERS AND MULTIMEDIA MESSAGE SERVICE CENTERS

This application claims priority from U.S. Provisional Application No. 60/568,257, entitled "Method to Qualify Multimedia Message Context to Enable Use of a Single Internet Address Domain to Send Messages to Both Short Message Service Centers and Multimedia Message Service Centers" to Carle S. Johnson, Jr. et al.; and from U.S. Provisional Application No. 60/568,258, entitled "Gateway Application to Support Use of a Single Internet Address Domain for Routing Messages to Multiple Multimedia Service Centers" to Carle S. Johnson, Jr., et al., the entirety of both of which are expressly incorporated herein by reference.

BACKGROUND OF THE INVENTION

1. Field of the Invention This invention relates to wireless telecommunications, and in particular to multimedia messaging services (MMS) and/or to short messaging services (SMS).

2. Background of Related Art The world has been transformed by the emergence of electronic messaging. Initially, short messaging services (SMS) were developed to allow text messaging. Later, these text capabilities were expanded to include audio and images with multimedia messaging services (MMS). Wireless Service Providers (carriers) currently install a Short Messaging Service Center (SMSC) between the Internet and their wireless network to support plain text short messaging (SMS) to subscriber handsets. To support MMS services, carriers also install a Multimedia Messaging Service Center (MMSC) between the Internet and their wireless network. Conventional MMSCs do not support SMS text messaging. Fig. 7 depicts the current state of the art of an installation of an MMSC and an SMSC both serving a single subscriber but requiring two separate Internet addresses. In particular, as shown in Fig. 7, an MMSC 702 is given a presence on the Internet 700, as is an SMSC 704. Each presence is required to have its own Universal Resource Locator (URL). Through these connections to the Internet, a message sender may direct a short message (e.g., a text message) to a supported subscriber 800 via the their carrier's servicing SMSC 704, or may direct a multimedia message (MMS) to the same subscriber 800 via their carrier's servicing MMSC 702 (provided that the subscriber's mobile device is capable of receiving MMS content). Therefore a person desiring to send a message to a subscriber with both SMS and MMS capability is required to remember two addresses for the same subscriber and to manually determine which address to use based on the content of the message they wish to send. Thus, carriers providing Multimedia Messaging Services utilize an MMSC 702 to receive MMS messages for delivery to subscribers with MMS capability, and one or more SMSCs 704 to receive SMS messages for delivery to SMS subscribers (many of whom may also be MMS subscribers). To provide these multiple services (MMS and SMS), the carrier must use multiple domain names (one URL for the MMSC 702 to support Multimedia Messaging, and another URL for the SMSC 704 to support Short Message Service) for each subscriber 800 who desires both capabilities within a single carrier network. For information relating to components of the MMS standard, reference is made to 3GPP TS 23.140 v6.5.0 Technical Specification - 3^rd Generation Partnership Project; Technical Specification Group Terminals; Multimedia Messaging Service (MMS); Functional description; Stage 2 (Release 6). In order for an MMSC 702 and an SMSC 704 to both receive messages destined for the same handset 800, it is necessary for the MMSC 702 and the SMSC 704 to each be referenced by unique Internet domain names. This requires that when addressing a message, the sender must be aware of whether they are sending an SMS or an MMS message, and correspondingly which domain is appropriate through which to access the destination subscriber handset, based on the particular content of the message they are sending. Thus, the sender must remember two different Internet addresses for any particular addressee. The present inventors have appreciated that the need to remember at least two different Internet addresses for the same destination subscriber has a high likelihood of causing confusion for message senders as to which domain to use for which message type, and perhaps even what specific message type they are sending. If a message is sent to an MMSC for a particular subscriber instead of to their SMSC for a plain text short message, or vice versa for a multimedia message, loss of the message will likely result, causing lost revenue to the wireless service provider (carrier), not to mention disappointed subscribers. Moreover, subscriber information, routing information and reporting mechanisms must be duplicated in two systems. There is a need for techniques and architecture for SMS and MMS services which are simpler to implement from a sender's perspective, and which ensure maximum profitability from a carrier's perspective.

SUMMARY OF THE INVENTION In accordance with the principles of the present invention, a wireless carrier message gateway comprises a module to detect a message type of a received message addressed to a URL assigned to the wireless carrier message gateway. A routing module forwards at least a portion of the received message to a multimedia messaging service center (MMSC) if a message type of the received message is detected to be a multimedia (MMS) type message and the destination subscriber is registered in an internal database as having a handset with the capability to receive multimedia messages. A routing module also forward s the received message to a short message service center (SMSC) if the message type of the received message is detected to be a short message (SMS) type message. A method of providing a single domain name for multiple message types in a wireless network, in accordance with another aspect of the present invention, comprises detecting a message type of a received message addressed to a destination subscriber serviced through the single domain name. If a message type of the received message is detected to be a multimedia (MMS) type message, at least a portion of the received message is forwarded to a multimedia messaging service center (MMSC) servicing the destination subscriber. If the message type of the received message is detected to be a short message (SMS) type message, the received message is forwarded to a short message service center (SMSC) servicing the destination subscriber. If the message type of the received message is detected to be a multimedia (MMS) message, but it is determined by a database query that the handset of the destination subscriber cannot receive MMS messages, all non-text components of the MMS message are removed and the text portion is sent to the subscriber as an SMS message. Optionally, an MMS message to a non-MMS capable subscriber can be forwarded to an alternate address, such as a web page designed to allow the subscriber the ability to view the MMS message using an appropriate web browser.

BRIEF DESCRIPTION OF THE DRAWINGS Features and advantages of the present invention will become apparent to those skilled in the art from the following description with reference to the drawings, in which: Fig. 1 depicts an MMS gateway including an intelligent content evaluator requiring only a single Internet presence (URL), through which MMS messages are detected and routed to an MMSC for presentation to a subscriber, and SMS messages are detected and routed to an SMSC for presentation to the subscriber, in accordance with the principles of the present invention. Fig. 2 depicts an MMS gateway including an intelligent content evaluator requiring only a single Internet presence (URL) such as is shown in Fig. 1, included within an MMSC, in accordance with another embodiment of the present invention. Fig. 3 shows an exemplary embodiment of an MMS gateway network architecture, in accordance with the principles of the present invention. Fig. 4 shows another exemplary embodiment of an MMS gateway network architecture, in accordance with the principles of the present invention. Fig. 5 shows software functions in an MMS gateway supporting both MMS and SMS with an address to a single Internet domain, in accordance with the principles of the present invention. Fig. 6 shows an exemplary flow chart for relevant functions of an MMS intelligent content evaluator gateway in accordance with the principles of the present invention. Fig. 7 depicts the current state of the art of an installation of an MMSC and an SMSC both serving a single subscriber but requiring two separate Internet addresses.

DETAILED DESCRIPTION OF ILLUSTRATIVE EMBODIMENTS The present invention provides a method and technique for evaluating message content on messages received from both internal or external message sources and routing messages appropriately to SMSCs or MMSCs based on automated evaluation of the message content and the stored capabilities of the subecriber's client device. Currently, Multimedia Messaging Service Centers and Short Message Service Centers used in a single network require the sender to differentiate between message types, and to send each type to the appropriate domain address corresponding to a gateway capable of receiving that particular message type. The present invention provides the ability to use a single address mailbox and domain for both MMS and SMS messages. Thus, wireless carrier networks providing multimedia messaging and short message service may allow utilization of both the Multimedia Messaging Service Centers as well as the Short Message Service Centers in a manner which allows all messages to be sent addressed to a single Internet domain. Fig. 1 depicts an MMS gateway 100 including an intelligent content evaluator requiring only a single Internet presence (URL), through which MMS messages are detected and routed to an MMSC 702 for presentation to a subscriber 800, and through which SMS messages are detected and routed to an SMSC 704 for presentation to the subscriber 800, in accordance with the principles of the present invention. In particular, as shown in Fig. 1, an MMS Intelligent Content

Evaluator gateway 100 is interposed between the Internet 700 and both an otherwise conventional MMSC 702 and SMSC 704 in a carrier's wireless network. The MMS intelligent content evaluator gateway 100 includes appropriate methods, functions and features allowing it to detect message content type. Based on the detected message content type, routing is then determined to the appropriate MMSC 702 or SMSC 704 servicing the addressed subscriber 800. The MMS intelligent content evaluator gateway 100 then forwards messages to the appropriate system (MMSC 702 or SMSC 704) for delivery based on the detected message content type and the messaging capabilities of the destination subscriber's handset discovered via a database query. The MMS intelligent content evaluator gateway 100 presents a single Internet mail domain to the Internet, through which all messages (e.g., MMS and SMS) addressed to a particular subscriber serviced by the carrier's network can be directed. The disclosed MMS intelligent content evaluator gateway

100 includes software components required to receive and forward messages between the Internet 700 and both the carrier's network Multimedia Messaging Service Centers (MMSCs) 702 as well as the carrier's Short Message Service Centers (SMSC) 704. Fig. 2 depicts an MMS gateway including an intelligent content evaluator 100a included within an MMSC server 200, requiring only a single Internet presence (URL) such as is shown in Fig. 1, in accordance with another embodiment of the present invention. Thus, as shown in Fig. 2, the disclosed MMS gateway including an intelligent content evaluator 100a may be integrated with the MMSC 702a itself. In an alternative embodiment, the SMSC 704 may maintain the ability to be directly accessed from the Internet 700 (depicted by dotted line in Fig 2), though this feature is not required for implementation of the principles of the present invention. Fig. 3 shows an exemplary embodiment of an MMS gateway network architecture, in accordance with the principles of the present invention. In particular, as shown in Fig. 3, an MMS intelligent content evaluator gateway 100 is provided with a presence on the Internet 700 (e.g., capable of passing messages via SMTP protocol). As shown in Fig. 3, the MMS intelligent content evaluator gateway 100 provides a carrier with the ability to filter spam messages at a single point (e.g., within the MMS intelligent content evaluator gateway 100). Database user tables are preferably implemented in a suitable user information provisioning/handset type/routing tables database 304, which is accessible by the MMS intelligent content evaluator gateway 100. The user tables in the database 304 may contain, e.g., subscriber information and message routing tables necessary to derive appropriate MMS and SMS destination addresses for each subscriber, or range of subscriber addresses. The user tables in the database 304 also preferably indicate capabilities of the carrier's subscriber's handset. For instance, at a minimum, capabilities included in the tables should include information relating to whether or not the handset 800 can support MMS messages. The user tables in the database 304 may be provisioned through an appropriate application, or through a provisioning web page 310. When multimedia messages (MMS) are processed through the MMS intelligent content evaluator gateway 100, complex messages can be filtered down to the highest resolution that the subscriber's handset can display. For example, consider an inbound MMS message sent to a group with a mixed selection of phones, some of which are capable of handling MMS messages, others of which are capable of handling only SMS plain text type messages. The protocols required to connect MMSCs and SMSCs are varied and not specific for practice of the present invention. For instance, the MMSC can be addressed via MM3 (SMTP), MM4 (MMS Extended SMTP) and MM7 (SOAP) interfaces. SMSCs can be addressed by various protocols. The disclosed embodiments support SMPP, CDMP, TNPP & OIS protocols. Nevertheless, the particular protocol is not dictated by the present invention. MMS messages are routed to the MMSC 702 by the MMS intelligent content evaluator gateway 100. SMS messages are routed to the SMSC 704 by the intelligent content evaluator gateway 100. Other types of messages may be routed to appropriate gateways, preferably using protocols standard in a direct connection of the relevant gateway with the Internet 700. As shown in Fig. 3, MMS handsets 350 capable of displaying a complete MMS message receive the complete MMS message routed by the MMS intelligent content evaluator gateway 100 to the MMSC 702 that provides service to the MMS handset 350. Handsets 360 capable of displaying only plain text receive only the plain text portion of the message via the relevant SMSC 704. Fig. 4 shows another exemplary embodiment of an MMS gateway network architecture, in accordance with the principles of the present invention. In particular, as shown in Fig. 4, when all messages are addressed to and processed through a single domain name on the Internet, i.e., an MMS intelligent content evaluator gateway 100, multiple send attempts to determine resolution are unnecessary. Use of the disclosed MMS intelligent content evaluator gateway 100 reduces the content to that which is acceptable by the receiving handset. Fig. 5 also shows that messages may be filtered down from a full MMS message to a 'resolution' capable of being received by the relevant handset to which the message was addressed. This resolution may include e-mailing the plain text portion of an MMS message, and allowing the handset to download additional attachments should the handset be capable of receiving such attachment(s). Fig. 5 shows software functions in an MMS intelligent content evaluator gateway 100 supporting both MMS and SMS with an address to a single Internet domain, in accordance with the principles of the present invention. Fig 5 should be read in association with the following exemplary method in accordance with the principles of the present invention. Step 1. Receive an SMTP message at the MMS intelligent content evaluator gateway 100 for processing. Step 2. Qualify the message as having MMS content by examining the SMTP message DATA section for any header in the DATA section that starts with X-MMS. Exemplary headers include "X-Mms- Message-Type", "X-Mms-Transaction-ld", "X-Mms-Version", "X-Mms- Message-Class", "X-Mms-Priority", "X-Mms-Delivery-Report", "X-Mms- Read-Reply", "X-MMS-Content-Location", etc. Step 3. Further qualify the message as having MMS content by comparing the message (MIME content) for attachment types that are provisioned in a database table 304 (Figs. 3 and 4) of acceptable MMS content types. Step 4. Examine the destination subscriber's handset capability record in the database 304 to determine if the handset can receive MMS messages. Step 5. If the message contains only valid MMS content and the destination subscriber's handset supports MMS content, then route the message as an MMS message to the MMSC 702 serving the destination address. Step 6. If the message contains text and does not contain

MMS content, route the message as an SMS message to the SMSC 704 serving the destination address. Step 7. If the message contains non-text content that is not indicated as MMS content in the MMS content types list, remove all non- text content, preserve any existing text content, replace the non-text content with tag fields consisting of the attachment names or MIME type and route the resulting text as an SMS message to the SMSC serving the destination address. Step 8. If the message contains only valid MMS content but the destination subscriber handset does not support MMS, remove the non-text content, preserve any existing text content, replace the non-text content with tag fields consisting of the attachment names or MIME type and forward the resulting text as an SMS message to the SMSC 704 serving the destination address. Step 9. Optional to step 8, store the MMS content in a suitable central message storage/retrieval database 302 (Figs. 3 and 4) and send an SMS notification containing a URL address to the destination address instructing the destination subscriber on how to view the message from the Internet using a Web browser. Step 10. Optional behavior for text only MMS messages. If the message contains only text, but has headers indicating it is an MMS message, and it is determined that the text will fit into an SMS message, construct an SMS message using the text and forward the resulting message for delivery to the SMSC 704 serving the destination address. Step 11. Optional behavior for text only messages where the destination subscriber's handset supports MMS content and the configured maximum MMS message length for the handset is greater than the maximum SMS message length, route the message as a text only

MMS message to the MMSC 702 serving the destination address. Fig. 6 shows an exemplary flow chart for relevant functions of an MMS intelligent content evaluator gateway 100 in accordance with the principles of the present invention. In particular, as shown in step 602 of Fig. 6, a message received by the MMS intelligent content evaluator gateway 100 is evaluated, and the message type is detected. If the message type is MMS, the method passes toward the right in Fig. 6: if it's an SMS message the method passes toward the left in Fig. 6. Thus, in the case of an SMS message type having been received, in step 668 it is determined whether or not the destination subscriber has an MMS capable handset or not. If not, the method passes to step 680, where it is determined whether or not the received message can be fit into an SMS message (e.g., within 160 characters). If so, then the received message is send to the servicing SMSC 704 as an SMS message, as shown in step 684. If not, in step 682, the received message is truncated to the maximum SMS message size, and forwarded to the SMSC as an SMS message in step 684. If the destination subscriber's handset is MMS capable, as determined in step 668, then the method passes to step 670, where it is determined whether or not Enable SMS relay is desired. If so, then the method passes in essence to step 680, or as depicted in step 672. In step 674, it's determined whether or not the received message will fit into an MMS message. If so, the message is forwarded in step 678 to the MMSC 702 as an MMS message. If not, the message is rejected as shown in step 676. If the Enable SMS relay is not desired back in step 670, then the method passes directly to step 674. If the message type is determined in step 602 to have been an MMS type message, then the method passes to step 606, where it's determined whether or not the destination subscriber has an MMS capable handset. If so, then the method passes to step 630, which fits the received message into an MMS format, and sends it to the MMSC 702 servicing the destination subscriber as an MMS message, otherwise the message is rejected in step 646. If in step 606 the subscriber's handset was determined to not be MMS capable, even though the received message was an MMS type, then in step 614 it is determined in step 614 whether the subscriber is to be notified via an appropriate SMS message. If so, then the received message is fit into an MMS message in step 628, and the message is forwarded using Store or Send commands to the MMSC 702 as an MMS message in step 642; an SMS notification message is created in step 660, and in step 662 it's determined whether or not the notification message will fit into an SMS message. If so, then the notification message is sent to the subscriber's servicing SMSC 704 as an SMS message in step 666. Otherwise, the SMS notification message is truncated to the maximum SMS size in step 664, then forwarded to the SMSC 704 as an SMS message in step 666. If the message didn't fit into an MMS message format in step 628, then the message is rejected. If SMS notification is not to be used in step 614, then the received message is converted to all text, and attachments to tags, in step 620. The converted message is fit into an SMS format message in step 626, and sent to the SMSC 704 as an SMS message in step 658. Otherwise, if the converted message didn't fit into the SMS format message, then the message is truncated to the maximum SMS size in step 640, and then sent to the SMSC 704 as an SMS message in step 658. If, in step 602, the message is determined to be a 'mixed' message containing both SMS and MMS content, then the method passes to step 604, where it's determined whether or not the destination subscriber is capable of MMS message handling (i.e., display). If so, then it's determined if non-MMS elements are replaced in step 610, and if so then if non-MMS attachments are replaced in step 616. Then it is determined whether the message fits into an MMS format, in step 622. If so, then the message is sent to the servicing MMSC 702 as an MMS message, in step 634, otherwise the message is rejected in step 632. In step 610, if the non-MMS elements are not replaced, then in step 690 the message is converted to all text, and all attachments to tags to be accessed by the destination subscriber, e.g., in a WAP application. In step 692, it is determined if the message fits into an SMS format. If so, then th.e message is forwarded to the SMSC 704 as an SMS message in step 696; otherwise it's truncated to the maximum SMS message size in step 694, then passed to step 696. Back up at step 604, if the destination subscriber's handset is not MMS capable, then the method passes toward the right side of Fig. 6. In particular, it's determined whether an SMS notification message is to be sent in step 608. If not, then the method passes to step 620. If so, then in step 612 it's determined whether or not the non-MMS elements are replaced. If not, then the method passes to step 620. If so, then the method passes to step 618, where non-MMS attachments are replaced. Then, in step 624, it's determined if the message fits into an MMS format. If not, then the message is rejected in step 638. If it does, then the message is forwarded in step 636 as a Store or Sent as an MMS message to the MMSC 702. An SMS notification message is created in step 650, and in step 652 it is determined whether or not the message fits into an SMS format. If so, it's sent in step 656 to the SMSC 704 servicing the destination subscriber as an SMS message. If not, in step 654 the message is truncated to fit into an SMS message formatted message, e.g., to the maximum SMS size, and passed to step 656 for forwarding to the SMSC 704 as an SMS message. The principal benefit that this invention provides is that of enabling both MMS and SMS messages to be sent to a subscriber using a single address at a single Internet domain. Other benefits derive from the fact that the Multimedia Messaging intelligent content evaluator gateway 100 provides a single point to apply carrier initiated control processing such as anti-"spam" (unsolicited email) checks and subscriber or carrier defined message manipulation or message blocking by sender address for all messages entering the network. Also, the Multimedia Messaging intelligent content evaluator gateway 100 provides a store-and-forward capability that prevents message loss in the event that an MMSC is momentarily out of service. Moreover, the message storage facility of the Multimedia Messaging intelligent content evaluator gateway 100 can be utilized as a central inbox to facilitate Web reporting or to consolidate and accumulate overall network messaging statistics. The present invention also allows for the integration of MMSCs and SMSCs from multiple vendors. The envisioned market for the present invention includes all national and international wireless cell phone service providers and/or carriers offering or planning to offer Multimedia Messaging Services (MMS) in conjunction with Short Message Service (SMS). While the invention has been described with reference to the exemplary embodiments thereof, those skilled in the art will be able to make various modifications to the described embodiments of the invention without departing from the true spirit and scope of the invention.

Claims

What is claimed is: 1. A wireless carrier message gateway, comprising: a module to detect a message type of a received message addressed to a URL assigned to said wireless carrier message gateway; a routing module to forward at least a portion of said received message to a multimedia messaging service center (MMSC) if a message type of said received message is detected to be a multimedia

(MMS)' type message; and a routing module to forward said received message to a short message service center (SMSC) if said message type of said received message is detected to be a short message (SMS) type message.

2. The wireless carrier message gateway according to claim

1 , further comprising: a database table defining a particular subscriber destination routing address to which SMS messages to said particular subscriber are to be forwarded from said wireless carrier message gateway.

3. The wireless carrier message gateway according to claim 1, further comprising: a database table defining message capabilities of a subscriber's wireless device.

4. The wireless carrier message gateway according to claim 3, wherein said defined message capabilities include: a definition informing that said subscriber's wireless device is capable of displaying SMS type messages only.

5. The wireless carrier message gateway according to claim 3, wherein said defined message capabilities include: a definition informing that said subscriber's wireless device is capable of displaying MMS type messages.

6. The wireless carrier message gateway according to claim 1 , further comprising: an anti-spam filtering function within said wireless carrier message gateway operating on multiple message types intended for said destination subscriber.

7. The wireless carrier message gateway according to claim 6, wherein: said multiple message types include SMS messages and MMS type messages.

8. The wireless carrier message gateway according to claim 1, further comprising: a store and forward capability that prevents message loss in the event that said MMSC is momentarily out of service.

9. The wireless carrier message gateway according to claim 1, further comprising: a module located within said wireless carrier message gateway to facilitate, consolidate, and accumulate overall network messaging statistics.

10. A method of providing a single domain name for multiple message types in a wireless network, comprising: detecting a message type of a received message addressed to a destination subscriber serviced through said single domain name; if a message type of said received message is detected to be a multimedia (MMS) type message, forwarding at least a portion of said received message to a multimedia messaging service center (MMSC) servicing said destination subscriber; and if said message type of said received message is detected to be a short message (SMS) type message, forwarding said received message to a short message service center (SMSC) servicing said destination subscriber.

11. The method of providing a single domain name for multiple message types in a wireless network according to claim 10, wherein: said domain name is assigned a unique Universal Resource Locator (URL).

12. The method of providing a single domain name for multiple message types in a wireless network according to claim 10, further comprising: accessing a table entry to determine a message capability of said destination subscriber.

13. The method of providing a single domain name for multiple message types in a wireless network according to claim 12, wherein: said message capability for said destination subscriber relates that said subscriber's wireless device is capable of displaying SMS type messages only.

14. The method of providing a single domain name for multiple message types in a wireless network according to claim 12, wherein: said message capability for said destination subscriber relates that said subscriber's wireless device is capable of displaying MMS type messages.

15. Apparatus for providing a single domain name for multiple message types in a wireless network, comprising: means for detecting a message type of a received message addressed to a destination subscriber serviced through said single domain name; means for forwarding at least a portion of said received message to a multimedia messaging service center (MMSC) servicing said destination subscriber, if a message type of said received message is detected to be a multimedia (MMS) type message; and means for forwarding said received message to a short message service center (SMSC) servicing said destination subscriber, if said message type of said received message is detected to be a short message (SMS) type message.

16. The apparatus for providing a single domain name for multiple message types in a wireless network according to claim 15, wherein: said domain name is assigned a unique Universal Resource Locator (URL).

17. The apparatus for providing a single domain name for multiple message types in a wireless network according to claim 15, further comprising: means for accessing a table entry to determine a message capability of said destination subscriber.

18. The apparatus for providing a single domain name for multiple message types in a wireless network according to claim 17, wherein: said message capability for said destination subscriber relates that said subscriber's wireless device is capable of displaying SMS type messages only.

19. The apparatus for providing a single domain name for multiple message types in a wireless network according to claim 17, wherein: said message capability for said destination subscriber relates that said subscriber's wireless device is capable of displaying MMS type messages.