WO2010040292A1

WO2010040292A1 - Multimedia messaging service realizing method and communication system and multimedia message router

Info

Publication number: WO2010040292A1
Application number: PCT/CN2009/072586
Authority: WO
Inventors: 张志远; 程卫明
Original assignee: 华为技术有限公司
Priority date: 2008-10-10
Filing date: 2009-07-01
Publication date: 2010-04-15
Also published as: CN101730318A; BRPI0905252A2; CN101730318B

Abstract

A multimedia messaging service realizing method and a communication system and a multimedia message router are provided. The method includes: the domain name query request sent by the local domain name server Local DNS is received; the address of the multimedia message router is returned to the local domain name server Local DNS; the multimedia message router receives the multimedia message and sends the multimedia message to the multimedia messaging service center MMSC that passes the tests.

Description

A method for realizing a multimedia message service, a communication system, and a multimedia message router. The application is filed on October 10, 2008, and the application number is 200810167482.4. The invention is entitled "A MMS service implementation method and communication system and a multimedia message router". Priority is hereby incorporated by reference in its entirety. Technical field

The invention relates to the field of communication, and particularly relates to a method for implementing a multimedia message service, a communication system and a multimedia message router. Background technique

Multimedia Messaging Service (MMS) is a further development of Short Message Service (SMS) and Enhanced Message Service (EMS), providing a complete end-to-end for personal multimedia mobile communication services. solution. The Multimedia Messaging Service Center (MMSC) is mainly used to control the submission and delivery of messages in real time, and store user data and multimedia messages.

A method for implementing a multimedia message service in the prior art is:

When the wireless application protocol gateway (WAP GW, Wireless Application Protocol Gate Way) submits a message to the MMSC domain name MMSdomain.com, the WAP GW generally searches for the local host Hosts file (the Hosts file stores the address resolution correspondence) and Cache whether there is an Internet Protocol (IP) address corresponding to MMSdomain.com. If not, go to the Local Domain Name Server (Local DNS, Local Domain Name Server) for query. The specific business process is shown in Figure 1, as follows:

101. The WAP GW sends a domain name request message to the local DNS, and queries the IP address corresponding to the domain name MMSdomain. 102. Local DNS finds that there is no cache record of MMSdomain locally, and finds that MMSdomain corresponds to two authorization servers (name server), adopting random or priority mode (depending on the policy adopted by Local DNS), and selecting the name server (NS, Name Server) 1, send the message to the NS1 server;

103, NS1 according to certain strategies (such as judging Local DNS and MMSC1/MMSC2

If the IP address segment is used to determine that MMSC1 is closest to Local DNS, then MMSC1 is selected. If MMSC1 is selected, the IP address corresponding to MMSC1 is fed back to Local DNS. By default, the TTL (Time To Live) value is 172800 seconds. 2 days, indicating the effective time of its response record);

104. Local DNS feeds the WAP GW with a domain name response, and the domain name response includes

IP address of MMSC1;

105. The WAP GW sends a message to the MMSC1.

However, in the process of implementing the present invention, the inventor found that the prior art has the following defects: After the WAP GW queries the DNS once, it finds that the IP address corresponding to the MMS domain is MMSC1, which will be within the TTL time (generally two days), All the messages are sent to the MMSC1. When the MMSC1 fails, the WAP GW cannot submit the message and cannot implement the MMSC disaster recovery. Summary of the invention

The embodiment of the invention provides a method for implementing a multimedia message service, a communication system, and a multimedia message router, which can implement disaster tolerance between multiple MMSCs.

The method for implementing the MMS service provided by the embodiment of the present invention includes: receiving a domain name query request sent by the local DNS server Local DNS; returning the address of the MMS router to the Local DNS; the MMS router receives the MMS, and sends the MMS to the detected Multimedia Message Service Center MMSC.

The communication system provided by the embodiment of the present invention includes: a local DNS, configured to send a domain name query request to the first multimedia message router, and receive the second multimedia message router that is fed back by the first multimedia message router. The first MMS router is configured to receive a domain name query request sent by the local DNS, and feed back the address of the second MMS router to the Local DNS; the second MMS router is configured to receive the MMS message, and send the MMS message to the MMSC that passes the detection; The MMSC is configured to receive a multimedia message sent by the second multimedia message router.

The MMS router provided by the embodiment of the present invention includes: a request receiving unit, configured to receive

a domain name query request sent by the local DNS; an address feedback unit, configured to feed back the address of the second multimedia message router to the local DNS; a receiving unit, configured to receive the multimedia message, the multimedia message includes the receiver information; and the sending unit is configured to pass the detection The MMSC sends the multimedia message.

As can be seen from the above technical solutions, the embodiments of the present invention have the following advantages:

In the embodiment of the present invention, the MMS router feeds back the address of the MMS router to the Local DNS.

The local DNS sends the address of the MMS router to the service provider (SP, Service Provider) or WAP GW, and the SP or WAP GW sends the MMS to the MMS router, and the MMS router sends the MMS to the MMSC that passes the detection, thereby ensuring the MMS transmission process. The MMS router can send the MMS to the MMSC that has not failed yet. Therefore, when a certain MMSC fails, the MMSC that is backed up can be used for MMS service processing. Therefore, disaster recovery between multiple MMSCs can be implemented. DRAWINGS

In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the embodiments or the description of the prior art will be briefly described below. Obviously, the drawings in the following description are only It is a certain embodiment of the present invention, and other drawings can be obtained from those skilled in the art without any inventive labor.

1 is a schematic diagram of a process for implementing a multimedia message service in the prior art;

2 is a flowchart of a general implementation manner of a method for implementing a multimedia message service according to an embodiment of the present invention;

3 is a service flowchart of a method for implementing a multimedia message service according to an embodiment of the present invention;

4 is a flowchart of a first embodiment of a method for implementing a multimedia message service according to an embodiment of the present invention; FIG. 5 is a flowchart of a second embodiment of a method for implementing a multimedia message service according to an embodiment of the present invention;

6 is a flowchart of a third embodiment of a method for implementing a multimedia message service according to an embodiment of the present invention;

FIG. 7 is a flowchart of a fourth embodiment of a method for implementing a multimedia message service according to an embodiment of the present invention;

8 is a schematic diagram of an embodiment of a communication system according to an embodiment of the present invention;

9 is a schematic diagram of a second embodiment of a communication system according to an embodiment of the present invention;

10 is a schematic diagram of an embodiment of a multimedia message router according to an embodiment of the present invention;

11 is a schematic diagram of a second embodiment of a multimedia message router according to an embodiment of the present invention;

FIG. 12 is a schematic diagram of an embodiment of an MMSC according to an embodiment of the present invention. detailed description

The embodiment of the invention provides a method for implementing a multimedia message service, a communication system, and a multimedia message router, which are used to implement disaster tolerance between multiple MMSCs.

Referring to FIG. 2, the overall process of implementing a multimedia message service in the embodiment of the present invention includes:

201. Receive a domain name query request.

Receive the domain name query request sent by the local DNS server Local DNS.

202. Feedback the IP address of the MMS router;

The MMS router returns the IP address of the MMS router to the Local DNS. In this embodiment, an IP address is used as an example of the address. It can be understood that, in practical applications, other types of addresses, such as media access control, may also be used. MAC, Media Access Control) address.

203. Receive a multimedia message;

In this embodiment, the MMS router that feeds back to the Local DNS receives the MMS message sent by the SP or the WAP GW, and the MMS message includes the receiver information, which is used to indicate to which user the MMS message needs to be sent.

It should be noted that the MMS router in this embodiment may be a routing device in an actual application, or another network element having a routing function, and the specific implementation is not limited herein. 204. Send a multimedia message to the MMSC that passes the detection.

In this embodiment, after receiving the multimedia message, the MMS router queries which MMSC the MMS should process, and then determines whether the MMSC is faulty by means of heartbeat detection.

It should be noted that the specific judgment manner may be: After the system is built, the MMS router performs continuous heartbeat detection with the MMSC, and if an MMSC is found to be faulty, it records, and when receiving the MMS, it can directly It is judged according to the recorded information whether the corresponding MMSC has failed.

In this embodiment, the MMS router determines the MMSC that is detected by the heartbeat (that is, the MMSC that is currently working normally). If there is only one MMSC that passes the heartbeat detection, the MMS is sent to the MMSC. If the MMSC passes the heartbeat detection, the MMSC may be followed. The preset allocation principle assigns the MMS to one of the MMSCs that pass the heartbeat detection, and the specific allocation manner will be described in detail later.

In this embodiment, the MMS router feeds back the address of the MMS router to the Local DNS, the Local DNS sends the address of the MMS router to the SP or the WAP GW, and the SP or WAP GW sends the MMS to the MMS router, and the MMS router sends the MMS to the pass detection. The MMSC can ensure that the MMS router can send the MMS to the currently unfailed MMSC during the MMS transmission process. Therefore, when a certain MMSC fails, the MMSC can be switched to another MMSC for MMS service processing, so that multiple MMSCs can be implemented. Disaster tolerance.

The method for implementing the MMS service in the embodiment of the present invention is described. The following describes the MMS service flow in combination with the system architecture. In the following embodiment, the WAP GW initiates the MMS process as an example, and the specific SP initiates the MMS process. For example, the process of the MMS service in the embodiment of the present invention specifically includes:

301. The WAP GW sends a domain name service request to the Local DNS.

When the user terminal needs to send a multimedia message, the user terminal sends a domain name service request to the WAP GW. When receiving the domain name service request, the WAP GW sends a domain name service request to the local DNS to obtain an address of the MMSC that can process the multimedia message. 302. Local DNS sends a domain name query request to the MMS router.

After receiving the domain name service request sent by the WAP GW, the Local DNS requests the MMS router to obtain the address of the MMSC.

It should be noted that, in this embodiment, there may be two or more MMS routers in the system architecture, and the Local DNS may select a MMS router according to a certain policy, for example, a nearby selection, if the selected MMS router fails, Then the Local DNS sends a domain name service request to other MMS routers.

303. The MMS router feeds back the address of the MMS router to the Local DNS.

The MMS router detects all the MMS routers through heartbeat detection, and then selects the corresponding MMS router IP address according to the IP address of the Local DNS and the IP address segment of the MMS router through the heartbeat detection, and carries the MMS router IP address in the response. Feedback to Local DNS in the message.

In this embodiment, the MMS router determines the currently working MMS router through the heartbeat detection. If there is only one MMS router that is currently working normally, the IP address of the working MMS router is fed back to the Local DNS, if the current working normally If there are more than one MMS routers, further detection can be performed. For example, you can select the MMS router with the best performance or the closest to Local DNS. The specific method can be: According to the IP address of Local DNS and the IP address of the currently working MMS router. The relationship performs address detection on the currently working MMS router to select the MMS router closest to the Local DNS as the MMS router that passes the address detection, and provides the address of the MMS router to the Local DNS o.

The response message may further carry a TTL parameter, where the TTL parameter is used to indicate a valid time of the MMS router IP address in the response message, and the value of the TTL parameter is smaller than the default 172800 seconds, and the specific value may be determined according to an actual application, for example, In this embodiment, the TTL value can be set to 5 minutes, that is, the MMS router IP address fed back to the Local DNS is valid for 5 minutes. After the expiration date, the Local DNS needs to re-acquire a new address to the MMS router. In this step, the address that the MMS router feeds back to the Local DNS is not the IP address of the MMSC, but the IP address of itself or other MMS routers. When the subsequent WAP GW submits the MMS message, the MMS message is first submitted to the MMS router, and the MMS router can According to the fault condition of the MMSC, an appropriate MMSC is selected to process the MMS submitted by the WAP GW.

304. The Local DNS feeds back the address of the MMS router to the WAP GW.

After receiving the response message sent by the MMS router, the Local DNS extracts the IP address of the MMS router and sends the IP address of the MMS router to the WAP GW.

305. The WAP GW submits the multimedia message.

After receiving the address sent by the Local DNS, the WAP GW sends the MMS to the corresponding MMS router.

306. The MMS router allocates the MMS according to the situation of heartbeat detection.

In this embodiment, the case of two MMSCs is taken as an example. It can be understood that in actual applications, there may be more MMSCs.

If there is no fault in each MMSC, in order to maintain the load balance, the MMS router needs to allocate the MMS based on some allocation principles to allocate load to each other. The specific principles may include:

A. Number information principle:

In this mode, after receiving the MMS message sent by the WAP GW, the MMS router reads the number information of the sender and the receiver from the MMS, and the specific number information may be a number segment or a tail number;

After reading the number information, the MMS router may choose to provide the corresponding MMSC for the number information;

It should be noted that the MMS router can obtain the correspondence between the number information and the MMSC in advance, and the corresponding relationship can be stored in the MMS router or in other network elements. After obtaining the number information, the MMS router can query the information. The MMSC of the number information service distributes the MMS to the MMSC for processing. In the MMS service process, in addition to sending MMS, there are some follow-up processes, such as delivery reports, download requests, confirmation messages, etc. In order to ensure the normal operation of the MMS service, after a certain MMS is assigned to a certain MMSC for processing, The subsequent process of the MMS is also allocated to the MMSC for processing. Since all subsequent processes include corresponding number information, and all control information sent from the WAP GW passes through the MMS router, the MMS router can follow these subsequent processes. The number information is selected by the MMSC for processing.

B. The principle of average distribution:

In this mode, after receiving the MMS message sent by the WAP GW, the MMS router allocates the MMS to each MMSC according to the possible splitting, and the following processing manner may be adopted:

The MMS router detects each MMSC with normal heartbeat detection according to a preset sharing ratio to determine the MMSC that passes the detection.

In practical applications, the sharing ratio can be set by the administrator. For example, the sharing ratio of the first MMSC and the second MMSC can be set to 50%. After receiving a new MMS message, the MMS router will perform the sharing according to the sharing. The ratio determines whether the sharing ratio of the first MMSC and the second MMSC is 50%. If not, the MMSC with a small current sharing ratio is confirmed as the MMSC that passes the detection, and the MMS is sent to the MMSC.

In the MMS service process, in addition to sending MMS, there are some follow-up processes, such as delivery reports, download requests, confirmation messages, etc. In order to ensure the normal operation of the MMS service, after a certain MMS is assigned to a certain MMSC for processing, The subsequent process of the MMS must also be allocated to the MMSC for processing. Since each subsequent process includes a message identifier, and the MMS router also records the message identifier when the MMS is allocated, the MMS router can follow the subsequent process of assigning the subsequent process. The message identifies that the control information of a certain multimedia message is allocated to the MMSC that processes the multimedia message.

The above mentioned two allocation principles, the MMS router can perform MMS distribution according to the above-mentioned allocation principle. It can be understood that, in practical applications, in addition to the above two principles, other similar principles may be adopted, which are not limited herein. . In this embodiment, the MMS router feeds back the address of the MMS router to the Local DNS, the Local DNS sends the address of the MMS router to the SP or the WAP GW, and the SP or WAP GW sends the MMS to the MMS router, and the MMS router sends the MMS to the pass detection. The MMSC can ensure that the MMS router can send the MMS to the currently unfailed MMSC during the MMS transmission process. Therefore, when a certain MMSC fails, the MMSC can be switched to another MMSC for MMS service processing, so that multiple MMSCs can be implemented. Disaster tolerance

Secondly, since the MMS router can allocate the MMS according to different allocation principles, the number of MMSs processed between the MMSCs is roughly equal, so that the MMSCs are loaded and binned, thereby improving the processing efficiency of each MMSC.

The method for implementing the MMS service in the embodiment of the present invention is described in detail below:

In the embodiment of the present invention, a method for implementing a multimedia message service is provided. In this method, a multimedia message router can record which MMSC the multimedia message is sent to, and when the subsequent information about the multimedia message is received, the information can be directly sent. The MMSC is given to ensure that related messages in the same session are processed by the same MMSC.

For ease of understanding, the method for implementing the MMS service in the embodiment of the present invention is separately described according to the service type in the actual application:

I. Multimedia message (MM, Multimedia Message) 1 interface service flow: In this embodiment, the MM1 interface refers to the interface between the MMSC and the WAP GW. The specific process is shown in FIG. 4, and the MMS service is implemented in the embodiment of the present invention. The first embodiment of the method includes:

401. The WAP GW sends a domain name service request to the Local DNS.

In this embodiment, if the WAP GW does not have an IP address corresponding to the domain of the MMSC, the local DNS is queried for the IP address corresponding to the domain name MMSCdomain.

402. Local DNS sends a domain name query request to the MMS router.

If the local DNS finds that the IP address corresponding to the domain name MMSCdomain has expired (that is, exceeds the TTL time), and the name server that obtains the domain name MMSCdomain is logged as the MMS router, the MMS domain name is queried to the MMS router. 403. The MMS router returns the address of the MMS router that passes the detection to the Local DNS; the MMS router performs heartbeat detection on all the MMS routers. If there is only one MMS router that works normally, the IP address of the working MMS router is fed back to the Local DNS. If there are multiple MMS routers working normally, the appropriate MMS routers will be selected according to the number or the last number, for example, the MMS router closest to the Local DNS is selected.

404. The Local DNS feeds back the query result to the WAP GW.

The above steps 401 to 404 are processes for querying the MMS router address.

405. The WAP GW sends a MM1 submit request to the MMS router.

406. The MMS router sends an MM1 submission request to the MMSC.

In this embodiment, the MMS router submits the message to MMSC1 or MMSC2 according to a prior allocation principle (e.g., number information principle or average allocation principle, etc.).

It should be noted that, in this embodiment, the MMS of the connected MMSC can be detected by the MMS router to determine the currently working MMSC. If there is only one MMSC currently working normally, the MM1 submission request is sent to the working MMSC. If the current working MMSC is more than one, the MM1 submission request may be allocated to one of the currently working MMSCs according to a preset allocation principle, and the specific allocation manner is consistent with the allocation manner described in the foregoing method embodiment. I will not repeat them here.

407. The MMSC feeds back to the MMS router that the MM1 submits a response.

408. The MMS router feeds back to the WAP GW to submit a response to the MM1.

The above steps 405 to 408 submit a message procedure for the terminal.

409. The MMSC sends an MM1 notification request to the WAP GW.

In this embodiment, the MMSC that receives the MM1 submission request (assumed to be MMSC1) sends a push notification to the user, and the Uniform Resource Locator (Post) of the Push notification is the MMSC Domain of the MMSC.

410. The WAP GW sends an MM1 notification response to the MMS router.

After receiving the notification message, the receiver (the user terminal, WAP GW) can send the message to the MMS router. Feedback response (If the receiver is a user terminal, the user terminal feeds back a response to the MMS router through the WAP GW), the response carries the MMSCDomain received in step 409, and the response address is the information server address set by the terminal, and thus points to the MMS message. router.

411. The MMS router sends an MM1 notification response to the MMSC.

In this embodiment, after receiving the MM1 notification response sent by the WAP GW, the MMS router extracts the MMSCDomain from the response, and learns that the MMSC1 receives the previous MM1 submission request, and then notifies the MM1 to ensure the consistency of the session processing. The response is sent to MMSC1.

The above steps 409 to 411 are the transmission and response processes of the notification.

412. The WAP GW sends a request download message to the MMS router.

In this embodiment, the WAP GW sends the message that the terminal requests to download to the MMS router. It should be noted that the MMSCDomain received in step 409 is also carried in the message requested to be downloaded in this embodiment.

413. The MMS router sends a request download message to the MMSC.

In this embodiment, after receiving the message requested for download by the WAP GW, the MMS router extracts the MMSCDomain from the response, and learns that the MMSC1 receives the previous MM1 submission request, and then ensures the consistency of the session processing. The downloaded message is sent to MMSC 1.

414. The MMSC feeds back the MM1 download response message to the MMS router.

In this embodiment, the MMSC1 finds a corresponding message from the memory or the disk and returns it to the MMS router.

415. The MMS router feeds back the MM1 download response message to the WAP GW.

The above steps 412 to 415 are processes for the terminal receiver to acquire a message.

416. The WAP GW sends an MM1 confirmation request message to the MMS router.

The receiving party (WAP GW) delivers the message to the MMS router according to the information server address configured on the terminal, and the MM1 acknowledgment request message carries the message received in step 409. MMSCDomaino

417. The MMS router sends an MM1 confirmation request message to the MMSC.

In this embodiment, after receiving the MM1 acknowledgment request message sent by the WAP GW, the MMS router extracts the MMSCDomain from the response, and learns that the MMSC1 receives the previous MM1 submission request, so to ensure the consistency of the session processing, the MM1 A confirmation request message is sent to MMSC1.

The above step 416 and step 417 are the confirmation process after the terminal successfully downloads the message.

418. The MMSC sends an MM1 delivery report to the WAP GW.

If the sender terminal requests a delivery report and the MMSC allows the delivery of the report, the MMSC feeds back the message processing result (the recipient successfully received the message) to the sender.

The above step 418 is a delivery reporting process.

419. The WAP GW sends the MM1 reading report to the MMS router.

If the sender terminal requests to read the report, and the MMSC allows the report to be read, the receiver sends the read report (including its own feedback and the like) to the MMS router, and the MM1 read report carries the MMSCDomain received in step 409.

420. The MMS router sends an MM1 reading report to the MMSC.

In this embodiment, after receiving the MM1 reading report sent by the WAP GW, the MMS router extracts the MMSCDomain from the response, and learns that the MMSC1 receives the previous MM1 submission request, and then reads the MM1 to ensure the consistency of the session processing. The report is sent to MMSC 1.

421. The MMSC sends an MM1 read report response to the WAP GW.

The above steps 419 to 421 are reading the reporting process.

In this embodiment, the MMS router feeds back the address of the MMS router to the Local DNS, the Local DNS sends the address of the MMS router to the SP or the WAP GW, and the SP or the WAP GW sends the MMS to the MMS router, thereby ensuring that the MMS router can be used in the MMS transmission process. Send the MMS to the MMSC that has not failed yet, so when one MMSC fails, it can be replaced with other The backup MMSC performs MMS service processing, so that disaster recovery between multiple MMSCs can be implemented. Secondly, the MMSC that receives the MM1 submission request sends a Push notification to the user,

The URL notified by Push is the MMSC domain name of the MMSC, so the receiver (user or

The WAP GW may carry the domain name when transmitting the subsequent related message, so that the MMS router knows which MMSC has obtained the MM1 submission request, so that these subsequent messages can be sent to the MMSC, thereby ensuring that the same session will only be sent to the MMSC. The same MMSC.

Second, MM3 interface business process:

In this embodiment, the MM3 interface refers to an interface between the MMSC and an external device (such as a mail server, a fax server, etc.), and the specific process is shown in FIG. 5. The second embodiment of the method for implementing the multimedia message service in the embodiment of the present invention includes :

501. The mail server sends a domain name service request to the Local DNS.

If there is no IP address corresponding to the MMSCDomain in the mail server, go to the Local DNS to query the IP address corresponding to the domain name MMSCDomain.

502. Local DNS sends a domain name query request to the MMS router.

If the local DNS finds that the IP address corresponding to the domain name MMSCDomain has expired (ie

The TTL time has expired. The query is obtained. The name server of the domain name MMSCdomain is recorded as a MMS router. In this embodiment, a MMS router is used as an example. It can be understood that, in actual applications, multiple MMS routers may also be used. Then query the MMSDomain domain name to the MMS router.

503. The MMS router feeds back to the Local DNS through the detected address of the MMS router; the MMS router returns a domain name service response to the Local DNS, that is, the address of the MMS router detected.

The MMS router performs heartbeat detection on all MMS routers. If there is only one MMS router working normally, feedback the IP address of the working MMS router to Local DNS. If there are multiple MMS routers working normally, it will follow the number segment or Select the appropriate MMS router for the tail number, for example, select the MMS router closest to Local DNS. 504. The Local DNS feeds back the domain name service response to the mail server.

The domain name service response contains the IP address of the MMS router.

505. The mail server sends an MM3 delivery request to the MMS router.

506. The MMS router sends an MM3 delivery request to the MMSC.

In this embodiment, the MMS router distributes the message to the corresponding MMSC according to the number information of the receiver (if the average allocation of the original IJ is used, according to information such as the message identifier).

It should be noted that, in this embodiment, the MMS of the connected MMSC can be detected by the MMS router to determine the currently working MMSC. If there is only one MMSC currently working normally, the MM3 delivery request is sent to the working MMSC. If the number of MMSCs that are currently working normally exceeds one, the MM3 delivery request may be allocated to one of the currently working MMSCs according to a preset allocation principle, and the specific allocation manner is consistent with the allocation manner described in the foregoing method embodiment. I will not repeat them here.

507. The MMSC feeds back the MM3 delivery response to the MMS router.

508. The MMS router feeds back the MM3 delivery response to the mail server.

509. The MMSC sends an MM1 notification request to the WAP GW.

The MMSC receiving the MM3 delivery request (assumed to be MMSC1) sends a Push notification to the user, and the Push notification URL is the MMSCDomain domain name MMSCDomain.

510. The WAP GW sends a domain name service request to the Local DNS.

511. The Local DNS feeds back the domain name service response to the WAP GW.

512. The WAP GW sends an MM1 notification response to the MMS router.

After receiving the notification message, the receiver sends a feedback response, and the response carries the MMSCDomain received in step 509, and the response address is the information server address set by the terminal, and thus points to the multimedia router.

513. The MMS router sends an MM1 notification response to the MMSC.

In this embodiment, after receiving the MM1 notification response sent by the WAP GW, the MMS router extracts the MMSCDomain from the response, and then learns that the MMSC1 received the previous one. The MM3 delivers the request, and in order to ensure the consistency of the session processing, the MM1 notification response is sent to the MMSC1.

514. The WAP GW sends a request download message to the MMS router.

The WAP GW sends the message that the terminal requests to download to the MMS router. It should be noted that the message requested to be downloaded in this embodiment also carries the MMSCDomaino received in step 509.

515. The MMS router sends a request download message to the MMSC.

In this embodiment, after receiving the message requested to be downloaded by the WAP GW, the MMS router extracts the MMSCDomain from the response, and learns that the MMSC1 receives the previous MM3 delivery request, and then ensures the consistency of the session processing. The downloaded message is sent to MMSC1.

516. The MMSC sends a download response message to the MMS router.

The MMSC finds the corresponding message from the memory or the disk and returns it to the MMS router.

517. The MMS router feeds back a download response message to the WAP GW.

518. The WAP GW sends an MM1 confirmation request message to the MMS router.

The receiver delivers the message to the MMS router according to the information server address configured on the terminal, and the MMSCDomain received in step 509 is carried in the MM1 acknowledgment request message.

519. The MMS router sends an MM1 confirmation request message to the MMSC.

In this embodiment, after receiving the MM1 acknowledgment request message sent by the WAP GW, the MMS router extracts the MMSCDomain from the response, and learns that the MMSC1 receives the previous MM3 delivery request, so to ensure the consistency of the session processing, the MM1 A confirmation request message is sent to MMSC1.

In this embodiment, the step 519 further includes a response process, and the specific process is similar to the foregoing first embodiment, and details are not described herein again.

In this embodiment, the MMS router feeds back the address of the MMS router to the Local DNS, Local.

The DNS sends the address of the MMS router to the SP or WAP GW, and the SP or WAP GW sends the MMS message. To the MMS router, the MMS router sends the MMS to the MMSC that has not failed, so it can ensure that the MMS router can send the MMS to the currently unfailed MMSC during the MMS transmission process, so when a MMSC fails, it can be replaced with another backup. The MMSC performs MMS service processing, so that disaster tolerance between multiple MMSCs can be realized;

Second, since the MMSC that received the MM3 delivery request sends a Push notification to the user,

The URL of the Push notification is the MMSC domain of the MMSC, so the receiver (the user or the WAP GW) can carry the domain name when sending the subsequent related message, so that the MMS router knows which MMSC has obtained the MM3 delivery request, so that these Subsequent messages are sent to the MMSC, thereby ensuring that the same session will only be sent to the same MMSC.

Third, MM4 interface business process:

In this embodiment, the MM4 interface refers to the interface between the local MMSC and the foreign MMSC. The specific process is shown in FIG. 6. The third embodiment of the method for implementing the MMS service in the embodiment of the present invention includes:

601. The foreign MMSC sends a domain name service request to the Local DNS.

If there is no IP address corresponding to the MMSCDomain in the foreign MMSC, the shell lj goes to the Local DNS to query the IP address corresponding to the domain name MMSCDomain.

602. Local DNS sends a domain name service request to the MMS router.

If the local DNS finds that the IP address corresponding to the domain name MMSCDomain has expired (that is, the TTL time has expired), the name server of the domain name MMSCdomain is logged as a MMS router. In this embodiment, a MMS router is used as an example. In the actual application, there may be multiple MMS routers, and the MMSDomain domain name is queried to the MMS router.

603. The MMS router returns a domain name service response to the Local DNS, where the domain name service response includes an address of the MMS server that passes the detection;

The MMS router performs heartbeat detection on all MMS routers. If there is only one MMS router with normal heartbeat detection, the IP address of the working MMS router is fed back to the Local DNS. If there are multiple MMS routers working normally, the appropriate MMS routers will be selected according to the number or the last number, for example, the MMS router closest to the Local DNS is selected.

604. The Local DNS forwards the domain name service response to the MMSC.

The domain name service response contains the IP address of the MMS router.

605. The foreign MMSC sends an MM4 submit request to the MMS router.

606. The MMS router sends an MM4 submission request to the MMSC.

It should be noted that, in this embodiment, the MMS of the connected MMSC can be detected by the MMS router to determine the currently working MMSC. If there is only one MMSC currently working normally, the MM4 submission request is sent to the working MMSC. If the current working MMSC is more than one, the MM4 submission request may be allocated to one of the currently working MMSCs according to the preset allocation principle, and the specific allocation manner is consistent with the allocation manner described in the foregoing method embodiment. I will not repeat them here.

607. The MMSC feeds back the MM4 delivery response to the MMS router.

608, the MMS router forwards the MMSC feedback MM4 delivery response;

609. The MMSC sends an MM1 notification request to the WAP GW.

The MMSC that receives the MM4 submission request (assumed to be MMSC1) sends a Push notification to the user, and the Push notification URL is the MMSCDomain domain name of the MMSC1.

610. The WAP GW sends a domain name service request to the Local DNS.

611. The Local DNS feeds back the domain name service response to the WAP GW.

612. The WAP GW sends an MM1 notification response to the MMS router.

After receiving the notification message, the receiver sends a feedback response, and the response carries the MMSCDomain received in step 609, and the response address is the information server address set by the terminal, and thus points to the multimedia router.

613. The MMS router sends an MM1 notification response to the MMSC. In this embodiment, after receiving the MM1 notification response sent by the WAP GW, the MMS router extracts the MMSCDomain from the response, and learns that the MMSC1 receives the previous MM4 submission request, and then notifies the MM1 to ensure the consistency of the session processing. The response is sent to MMSC1.

614. The WAP GW sends a request download message to the MMS router.

The WAP GW sends the message that the terminal requests to download to the MMS router. It should be noted that the message requested to be downloaded in this embodiment also carries the MMSCDomain received in step 609.

615. The MMS router sends a request download message to the MMSC.

In this embodiment, after receiving the message requested for download by the WAP GW, the MMS router extracts the MMSCDomain from the response, and learns that the MMSC1 receives the previous MM4 submission request, and then ensures the consistency of the session processing. The downloaded message is sent to MMSC1.

616. The MMSC sends a download response message to the MMS router.

617. The MMS router feeds back the response message to the WAP GW.

618. The WAP GW sends an MM1 confirmation request message to the MMS router.

The receiver delivers the message to the MMS router according to the information server address configured on the terminal, and the MMSCDomain received in step 609 is carried in the MM1 acknowledgment request message.

619. The MMS router sends an MM1 confirmation request message to the MMSC.

In this embodiment, after receiving the MM1 acknowledgment request message sent by the WAP GW, the MMS router extracts the MMSCDomain from the response, and learns that the MMSC1 receives the previous MM4 submission request, so to ensure the consistency of the session processing, the MM1 A confirmation request message is sent to MMSC1.

620. The MMSC sends an MM4 delivery report request to the external MMSC.

621. The foreign MMSC feeds back the MM4 delivery report response to the MMSC. In this embodiment, the MMS router feeds back the address of the MMS router to the Local DNS, the Local DNS sends the address of the MMS router to the SP or the WAP GW, and the SP or the WAP GW sends the MMS to the MMS router, thereby ensuring that the MMS router can be used in the MMS transmission process. The MMS is sent to the MMSC that has not failed yet. When a certain MMSC fails, the MMSCs that are backed up can be used for the MMS service processing. Therefore, the disaster recovery between multiple MMSCs can be implemented. Secondly, the MM4 submission is received. The MMSC sends a Push notification to the user, and the URL of the Push notification is the MMSC domain of the MMSC. Therefore, the receiving party (the user or the WAP GW) can carry the domain name when sending the subsequent related message, so that the MMS router knows which MMSC is the MMSC. The MM4 submission request is obtained, so that these subsequent messages can be sent to the MMSC, thereby ensuring that the same session will only be sent to the same MMSC.

Fourth, MM7 interface business process:

In this embodiment, the MM7 interface is a value-added application interface, and is generally referred to as an interface between the MMSC and the SP. The specific process is shown in FIG. 7. The fourth embodiment of the method for implementing the MMS service in the embodiment of the present invention includes:

701. The SP sends a domain name service request to the Local DNS.

If there is no IP address corresponding to MMSCDomain in the SP, then the IP address of the domain name MMSCDomain is queried by the local DNS.

702. Local DNS sends a domain name service request to the MMS router.

703. The MMS router returns a domain name service response to the Local DNS, where the domain name service response includes an address of the MMS server that passes the detection;

The MMS router performs heartbeat detection on all MMS routers, if the heartbeat detects normal MMS roads. If there is only one router, the IP address of the working MMS router is fed back to the Local DNS. If there are multiple MMS routers working normally, the appropriate MMS router will be selected according to the number or the last number, for example, the nearest local DNS is selected. MMS router.

704. The local DNS returns a domain name service response to the SP.

The domain name service response contains the IP address of the MMS router.

705, SP sends a MM7 submission request to the MMS router;

706. The MMS router sends an MM7 submission request to the MMSC.

It should be noted that, in this embodiment, the MMS of the connected MMSC can be detected by the MMS router to determine the currently working MMSC. If there is only one MMSC currently working normally, the MM7 submit request is sent to the working MMSC. If the current working MMSC is more than one, the MM7 submission request may be allocated to one of the currently working MMSCs according to a preset allocation principle, and the specific allocation manner is consistent with the allocation manner described in the foregoing method embodiment. I will not repeat them here.

707. The MMSC feeds back the MM7 delivery response to the MMS router.

708. The MMS router feeds back to the SP, and the MM7 delivers a response;

709. The MMSC sends an MM1 notification request to the WAP GW.

The MMSC that receives the MM7 submission request (assumed to be MMSC1) sends a Push notification to the user, and the Push notification URL is the MMSCDomain domain name MMSCDomain.

710. The WAP GW sends a domain name service request to the Local DNS.

711. The Local DNS feeds back the domain name service response to the WAP GW.

712. The WAP GW sends an MM1 notification response to the MMS router.

After receiving the notification message, the receiver sends a feedback response, and the response carries the MMSCDomain received in step 709, and the response address is the information server address set by the terminal, and thus points to the MMS router. 713. The MMS router sends an MM1 notification response to the MMSC.

In this embodiment, after receiving the MM1 notification response sent by the WAP GW, the MMS router extracts the MMSCDomain from the response, and learns that the MMSC1 receives the previous MM7 submission request, and then notifies the MM1 to ensure the consistency of the session processing. The response is sent to MMSC1.

714. The WAP GW sends a request download message to the MMS router.

The WAP GW sends the message that the terminal requests to download to the MMS router. It should be noted that the message requested to be downloaded in the embodiment also carries the MMSCDomain received in step 709.

715. The MMS router sends a request download message to the MMSC.

In this embodiment, after receiving the message requested to be downloaded by the WAP GW, the MMS router extracts the MMSCDomain from the response, and learns that the MMSC1 receives the previous MM7 submission request, and then ensures the consistency of the session processing. The downloaded message is sent to MMSC 1.

716. The MMSC sends a download response message to the MMS router.

717. The MMS router feeds back the response message to the WAP GW;

718. The WAP GW sends an MM1 confirmation request message to the MMS router.

The receiver delivers the message to the MMS router according to the information server address configured on the terminal, and the MMSCDomain received in step 709 is carried in the MM1 acknowledgment request message.

719. The MMS router sends an MM1 confirmation request message to the MMSC.

In this embodiment, after receiving the MM1 acknowledgment request message sent by the WAP GW, the MMS router extracts the MMSCDomain from the response, and learns that the MMSC1 receives the previous MM7 submission request, so to ensure the consistency of the session processing, the MM1 A confirmation request message is sent to MMSC1.

720. The MMSC sends an MM7 delivery report request to the SP. 721. The SP feeds back the MM7 delivery report response to the MMSC.

In this embodiment, the MMS router feeds back the address of the MMS router to the Local DNS, the Local DNS sends the address of the MMS router to the SP or the WAP GW, and the SP or the WAP GW sends the MMS to the MMS router, thereby ensuring that the MMS router can be used in the MMS transmission process. The MMS is sent to the MMSC that has not been faulty. Therefore, when a certain MMSC fails, the MMSCs that are backed up can be used for the MMS service processing. Therefore, the disaster recovery between multiple MMSCs can be implemented. The MMSC that receives the MM7 submission request sends a Push notification to the user, and the URL of the Push notification is the MMSC domain name of the MMSC. Therefore, the receiver (the user or the WAP GW) can carry the domain name when sending the subsequent related message, so that the MMS router knows Which MMSC has obtained the MM7 submission request, so that these subsequent messages can be sent to the MMSC, thereby ensuring that the same session will only be sent to the same MMSC.

The following describes the embodiment of the communication system in the embodiment of the present invention. Referring to FIG. 8, the communication system in the embodiment of the present invention includes:

a multimedia message router 803/804, configured to receive the sent multimedia message, and send the multimedia message to the MMSC that passes the detection;

The MMSC 805/806 is configured to receive the multimedia message sent by the MMS router 803/804, and send the MMS to the corresponding receiver.

The MMSC includes at least a first MMSC 805 and a second MMSC 806. The MMS router may include a first MMS router 803 and a second MMS router 804.

The communication system in this embodiment may further include:

a wireless application protocol gateway/service provider 801, configured to send a multimedia message, where the multimedia message includes receiver information;

The wireless application protocol gateway/service provider 801 in this embodiment is only an example, and may also be another network element for transmitting a multimedia message in the actual application, which is not limited herein.

The communication system in this embodiment may further include: The local domain name server 802 is configured to receive a query request sent by the wireless application protocol gateway/service provider 801, send a domain name query request to the MMS router according to the query request, and receive an IP address fed back by the MMS router, to the The wireless application protocol gateway/service provider 801 sends the IP address, where the IP address is an IP address of the MMS router;

The MMS router 803/804 is further configured to receive a domain name query request sent by the local domain name server 802, and obtain an Internet Protocol IP address of the currently working MMS router through heartbeat detection; according to the IP address of the Local DNS and the working MMS The IP address segment of the router queries the MMS router corresponding to the Local DNS; the IP address of the corresponding MMS router is fed back to the Local DNS, and the lifetime parameter of the MMS router IP address is less than the default value.

It should be noted that, if the MMS router with normal heartbeat detection is one, the MMS router that passes the detection detects the normal MMS router for the heartbeat;

If the heartbeat detects more than one MMS router, the address of the normal MMS router is detected according to the relationship between the IP address of the local DNS and the IP address of the normal MMS router. The address of the MMS router that the DNS detects through the address.

The first multimedia message router 803 or the second multimedia message router 804 in this embodiment is further configured to allocate the multimedia message sent by the wireless application protocol gateway/service provider 801 to the first MMSC 805 or the second MMSC 806.

It should be noted that, if there are more than one MMSC with normal heartbeat detection, the MMS router detects the MMSCs with normal heartbeat detection according to the sender or the receiver's number segment or the tail number in the MMS to determine the MMSC that passes the detection;

Or, the MMS router detects each MMSC with normal heartbeat detection according to a preset sharing ratio to determine the MMSC that passes the detection.

The manner of determining the MMSC through the detection is consistent with the determination manner described in the foregoing method embodiment, and details are not described herein again. In this embodiment, the first multimedia message router 803 receives the multimedia message sent by the wireless application protocol gateway/service provider 801, and the first multimedia message router 803 determines whether the corresponding first MMSC 805 is faulty, so when the first MMSC 805 fails, the first An MMSC 805 can forward the MMS to the second MMSC 806 in a timely manner, and the MMSC 806 sends the MMS to the MMSC 806. Therefore, when a certain MMSC fails, the MMSC can be switched to another MMSC for MMS service processing, so that multiple MMSCs can be implemented. Disaster tolerance

Secondly, since the first MMS router 803 can allocate the MMS according to different allocation principles, the number of MMSs processed between the MMSCs is substantially equal, so that the MMSCs are load-shifted, thereby improving the processing efficiency of each MMSC.

The following describes a second embodiment of the communication system in the embodiment of the present invention. Referring to FIG. 9, the communication system in this embodiment includes:

a wireless application protocol gateway/service provider 901, configured to send a multimedia message, where the multimedia message includes receiver information, receive information of a first MMSC 903 domain name sent by the first MMSC 903, or receive a second MMSC 904 domain name sent by the second MMSC 904 Sending the MMS-related information (such as a download request, an acknowledgment response, etc.) to the MMS router 902, where the related information includes the first MMSC 903 domain name or the second MMSC 904 domain name;

The MMS router 902 is configured to receive the multimedia message sent by the wireless application protocol gateway/service provider 901, and send the multimedia message to the first MMSC 903 or the second MMSC 904 according to a preset allocation rule, and receive the wireless application protocol gateway/service providing The related information sent by the quotient 901 reads the domain name carried in the related information, and sends the related information to the corresponding first MMSC 903 or the second MMSC 904 according to the domain name.

If the domain name in the related information is the first MMSC 903 domain name, the related information is sent to the first MMSC 903. If the domain name in the related information is the second MMSC 904 domain name, the related information is sent to the second MMSC 904.

In the embodiment of the present invention, since the MMSC that receives the multimedia message sends its own domain name to the wireless application protocol gateway/service provider 901, the wireless application protocol gateway/service provider 901 is transmitting The domain name may be carried when the subsequent related message is sent, so that the MMS router 902 knows which MMSC has obtained the MMS, and can send these subsequent messages to the MMSC, thereby ensuring that the same session will only be sent to the same MMSC.

The following describes the embodiment of the MMS router in the embodiment of the present invention. Referring to FIG. 10, the embodiment of the MMS router in the embodiment of the present invention specifically includes:

The request receiving unit 1005 is configured to receive a domain name query request sent by the local DNS; the address feedback unit 1006 is configured to feed back, to the local DNS, an address of the second multimedia message router, where a lifetime parameter of the MMS router IP address is less than a default value;

The receiving unit 1001 is configured to receive a multimedia message, where the multimedia message includes receiver information.

The sending unit 1003 is configured to send the multimedia message to the MMSC that passes the detection.

The MMS router in this embodiment may further include:

The detecting unit 1002 is configured to determine, by the heartbeat detection, whether the MMS router is faulty, and determine, by using a heartbeat detection, whether the MMSC connected to the MMS router is faulty;

When the heartbeat router detects that the normal MMS router is one, the address feedback unit 1006 feeds back the IP address of the normal MMS router to the local DNS.

If the heartbeat detects more than one MMS router, the address feedback unit 1006 performs an address on the MMS detection normal MMS router according to the relationship between the Internet Protocol IP address of the Local DNS and the IP address of the normal MMS router. Detected to provide the IP address of the MMS router detected by the address to the Local DNS feedback.

The MMS router in this embodiment may further include:

The allocating unit 1004 is configured to: when the MMSC with normal heartbeat detection is more than one, detect each MMSC with normal heartbeat detection according to the sender segment or the tail number or the tail number of the MMS to determine the MMSC passing the detection, and pass the The detected MMSC sends a multimedia message;

Or, the MMSCs with normal heartbeat detection are detected according to the preset sharing ratio to determine the MMSC passing the detection, and the MMS is sent to the MMSC passing the detection.

The allocating unit 1004 in this embodiment may further include: The first allocating unit 10041 is configured to acquire the receiver and the sender number information in the multimedia message, where the number information includes at least a number segment or a tail number; select an MMSC that provides the MMS service for the number information; and send the MMSC to the MMSC Sending the MMS; or

The second allocating unit 10042 is configured to send the MMS to the first MMSC and the second MMSC in proportion, so that the number of MMS messages received by the first MMSC and the second MMSC is the same.

In this embodiment, the MMS router includes a detecting unit 1002, and can determine whether the first MMSC corresponding to the received MMS is faulty. When the first MMSC 805 fails, the MMS can be forwarded to the second MMSC in time. The MMSC sends the MMS, so when a certain MMSC fails, the MMSC that is backed up can be used for MMS service processing, so that disaster recovery between multiple MMSCs can be implemented.

Secondly, since the MMS router includes the allocating unit 1004, the MMS can be allocated according to different allocation principles. Therefore, the number of MMSs processed between the MMSCs is substantially equalized, so that the MMSCs are loaded and binned, thereby improving the processing efficiency of each MMSC.

The following describes the embodiment of the MMS router in the embodiment of the present invention. Referring to FIG. 11, the second embodiment of the MMS router in the embodiment of the present invention specifically includes:

The receiving unit 1101 is configured to receive a multimedia message sent by the SP or the WAP GW, where the multimedia message includes the receiver information, and receives related information sent by the WAP GW, where the related information includes the MMSC domain name;

The distribution unit 1102 is configured to allocate the multimedia message to the first MMSC or the second MMSC according to the preset allocation rule;

The reading unit 1103 is configured to read the MMSC domain name from the related information sent by the WAP GW;

The sending unit 1104 is configured to send the related information sent by the WAP GW to the corresponding MMSC according to the MMSC domain name read by the reading unit 1103, and send the related information to the first MMSC if the domain name is the first MMSC domain name. If the domain name is the second MMSC domain name, then The related information is sent to the second MMSC.

In this embodiment, since the MMS router includes the reading unit 1103, the MMS router can read the MMSC domain name, so as to know which MMSC has obtained the MMS, and can send subsequent related messages to the MMSC, thereby ensuring the same Sessions will only be sent to the same MMSC.

The following describes the embodiment of the multimedia message service center in the embodiment of the present invention. Referring to FIG. 12, the embodiment of the multimedia message service in the embodiment of the present invention specifically includes:

The domain name obtaining unit 1201 is configured to acquire an MMSC domain name.

The push notification sending unit 1202 is configured to send a push notification including the MMSC domain name to the WAP GW.

After the MMSC domain name is obtained, the MMSC domain name is carried in the push notification, so the related information sent by the subsequent WAP GW to the MMS router may carry the MMSC domain name, so that related information related to the MMS is sent to The same MMSC, and ensure that the same session is only sent to the same MMSC.

A person skilled in the art can understand that all or part of the steps of implementing the above embodiments can be completed by a program to instruct related hardware, and the program can be stored in a computer readable storage medium. , including the following steps:

Receiving a domain name query request sent by the local domain name server Local DNS; returning the address of the MMS router to the Local DNS; the MMS router receives the MMS, and sends the MMS to the MMSC that passes the detected multimedia message service center.

The above-mentioned storage medium may be a read only memory, a magnetic disk or an optical disk or the like.

The above is a detailed description of a method for implementing a multimedia message service, a communication system, and a multimedia message router provided by the present invention. For those skilled in the art, according to the idea of the embodiment of the present invention, there will be a specific implementation manner and application range. The details of the description are not to be construed as limiting the invention.

Claims

Claim

A method for implementing a multimedia message service, characterized in that:

Receiving a domain name query request sent by a local domain name server Local DNS;

Returning the address of the MMS router to the Local DNS;

The MMS router receives the MMS, and sends the MMS to the MMSC that passes the detected multimedia message service center.

2. The method according to claim 1, wherein the method further comprises: detecting a multimedia message router;

The address of the MMS router returned to the Local DNS is the address of the MMS router that passes the detection.

The method according to claim 2, wherein the checking the MMS router is: detecting the MMS router by using heartbeat detection;

If the MMS detection is normal, the MMS router that detects the heartbeat detects the normal MMS router for the heartbeat;

If the heartbeat detects more than one MMS router, the address detection is performed on the MMS router with normal heartbeat detection according to the relationship between the Internet Protocol IP address of the Local DNS and the IP address of the normal MMS router. The address of the MMS router that is provided to the Local DNS for address detection.

4. The method according to claim 1, further comprising:

Detection of MMSC by heartbeat detection;

When the MMSC with normal heartbeat detection is one, the MMSC that passes the detection detects the normal MMSC for the heartbeat.

5. The method of claim 4, wherein:

When the heartbeat detects more than one normal MMSC, the MMSCs whose heartbeat detection is normal are detected according to the sender or the receiver's number segment or the tail number in the MMS to determine the MMSC passing the detection; or The MMSCs with normal heartbeat detection are detected according to the preset sharing ratio to determine the MMSCs that pass the detection.

The method according to claim 1 or 2, wherein the method further comprises: the MMS router receiving the MMS related information, where the MMS related information includes the MMSC information that is detected;

Transmitting the MMS related information to the MMSC that passes the detection.

7. A communication system, comprising:

a local DNS, configured to send a domain name query request to the first multimedia message router, and receive a second multimedia message router address fed back by the first multimedia message router;

a first MMS router, configured to receive a domain name query request sent by a Local DNS, to the

Local DNS feeds back the address of the second MMS router;

a second multimedia message router, configured to receive the multimedia message, and send the multimedia message to the MMSC that passes the detection;

The MMSC is configured to receive a multimedia message sent by the second multimedia message router.

The communication system according to claim 7, wherein the first MMS router is further configured to perform heartbeat detection on all MMS routers;

If the heartbeat detects that the normal MMS router is one, the local DNS is fed back to the local DNS to detect the address of the normal MMS router;

If the heartbeat detects more than one MMS router, the address detection of the MMS router with normal heartbeat detection is performed according to the relationship between the Internet Protocol IP address of the Local DNS and the IP address of the normal MMS router. Local DNS feedback provides the address of the MMS router detected by the address.

The communication system according to claim 7 or 8, wherein the second multimedia message router is further configured to detect the MMSC by using heartbeat detection;

When the MMSC with normal heartbeat detection is one, the MMSC with normal heartbeat detection is the MMSC that passes the detection; When the number of MMSCs with normal heartbeat detection is more than one, the second MMS router detects each MMSC with normal heartbeat detection according to the number or tail number of the sender or the receiver in the MMS to determine the MMSC that passes the detection;

Or,

The second MMS router detects that each heartbeat detection is normal according to a preset sharing ratio.

The MMSC determines the MMSC that passes the test.

10. A multimedia message router, comprising:

a request receiving unit, configured to receive a domain name query request sent by a Local DNS;

An address feedback unit, configured to feed back, to the local DNS, an address of the second multimedia message router, and a receiving unit, configured to receive the multimedia message;

And a sending unit, configured to send the multimedia message to the MMSC that passes the detection.

The MMS router according to claim 10, wherein the MMS router further comprises:

The detecting unit is configured to detect whether the MMSC is normal by using a heartbeat detection.

The MMS router according to claim 11, wherein the MMS router further comprises:

The allocation unit is configured to: when the MMSC with normal heartbeat detection is more than one, detect each MMSC with normal heartbeat detection according to the sender or the receiver's number segment or the tail number in the MMS to determine the MMSC that passes the detection;

Or,

The MMSCs with normal heartbeat detection are detected according to the preset sharing ratio to determine the MMSCs that pass the detection.

The MMS router according to claim 12, wherein the detecting unit is further configured to: detect, by using a heartbeat detection, whether the MMS router is normal;

The allocating unit is further configured to: when the heartbeat detects more than one MMS router, according to

Local DNS Internet Protocol IP address and the heartbeat detection IP address of the normal MMS router The address relationship performs address detection on the MMS router with normal heartbeat detection to feed back the address of the MMS router that passes the address detection to the Local DNS.