WO2010040292A1 - Procédé de mise en application de service de messagerie multimédia, système de communication et routeur de messages multimédias - Google Patents

Procédé de mise en application de service de messagerie multimédia, système de communication et routeur de messages multimédias Download PDF

Info

Publication number
WO2010040292A1
WO2010040292A1 PCT/CN2009/072586 CN2009072586W WO2010040292A1 WO 2010040292 A1 WO2010040292 A1 WO 2010040292A1 CN 2009072586 W CN2009072586 W CN 2009072586W WO 2010040292 A1 WO2010040292 A1 WO 2010040292A1
Authority
WO
WIPO (PCT)
Prior art keywords
mms
router
mmsc
address
detection
Prior art date
Application number
PCT/CN2009/072586
Other languages
English (en)
Chinese (zh)
Inventor
张志远
程卫明
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Publication of WO2010040292A1 publication Critical patent/WO2010040292A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
    • H04L51/21—Monitoring or handling of messages
    • H04L51/23—Reliability checks, e.g. acknowledgments or fault reporting
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/45—Network directories; Name-to-address mapping
    • H04L61/4505—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols
    • H04L61/4511—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols using domain name system [DNS]

Definitions

  • 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 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 is mainly used to control the submission and delivery of messages in real time, and store user data and multimedia messages.
  • the WAP GW 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.
  • IP Internet Protocol
  • the WAP GW sends a domain name request message to the local DNS, and queries the IP address corresponding to the domain name MMSdomain.
  • 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;
  • NS1 according to certain strategies (such as judging Local DNS and MMSC1/MMSC2
  • 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.
  • the TTL Time To Live
  • Local DNS feeds the WAP GW with a domain name response, and the domain name response includes
  • the WAP GW sends a message to the MMSC1.
  • 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 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 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
  • MMSC 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
  • the sending unit is configured to pass the detection
  • the MMSC sends the multimedia message.
  • the embodiments of the present invention have the following advantages:
  • 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.
  • FIG. 1 is a schematic diagram of a process for implementing a multimedia message service in the prior art
  • FIG. 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
  • FIG. 3 is a service flowchart of a method for implementing a multimedia message service according to an embodiment of the present invention
  • FIG. 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
  • FIG. 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.
  • FIG. 8 is a schematic diagram of an embodiment of a communication system according to an embodiment of the present invention.
  • FIG. 9 is a schematic diagram of a second embodiment of a communication system according to an embodiment of the present invention.
  • FIG. 10 is a schematic diagram of an embodiment of a multimedia message router according to an embodiment of the present invention.
  • FIG. 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.
  • the overall process of implementing a multimedia message service in the embodiment of the present invention includes:
  • the MMS router returns the IP address of the MMS router to the Local DNS.
  • 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.
  • 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.
  • 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.
  • the MMS router 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.
  • the MMS router 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.
  • 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.
  • 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 WAP GW initiates the MMS process as an example, and the specific SP initiates the MMS process.
  • the process of the MMS service in the embodiment of the present invention specifically includes:
  • the WAP GW sends a domain name service request to the Local DNS.
  • the user terminal When the user terminal needs to send a multimedia message, the user terminal sends a domain name service request to the WAP GW.
  • 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.
  • Local DNS sends a domain name query request to the MMS router.
  • the Local DNS 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.
  • 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.
  • 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.
  • 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,
  • 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.
  • the Local DNS needs to re-acquire a new address to the MMS router.
  • 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.
  • 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.
  • the Local DNS feeds back the address of the MMS router to the WAP GW.
  • the Local DNS 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.
  • the WAP GW submits the multimedia message.
  • the WAP GW After receiving the address sent by the Local DNS, the WAP GW sends the MMS to the corresponding MMS router.
  • the MMS router allocates the MMS according to the situation of heartbeat detection.
  • the MMS router needs to allocate the MMS based on some allocation principles to allocate load to each other.
  • the specific principles may include:
  • the MMS router 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;
  • the MMS router may choose to provide the corresponding MMSC for the number information
  • 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.
  • follow-up processes such as delivery reports, download requests, confirmation messages, etc.
  • 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.
  • the MMS router 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.
  • 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.
  • the MMS service process in addition to sending MMS, there are some follow-up processes, such as delivery reports, download requests, confirmation messages, etc.
  • 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 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. .
  • 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.
  • the MMS router can allocate the MMS according to different allocation principles, so that the MMSCs are loaded and binned, thereby improving the processing efficiency of each MMSC.
  • a method for implementing a multimedia message service is provided.
  • 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.
  • 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:
  • the WAP GW sends a domain name service request to the Local DNS.
  • the local DNS is queried for the IP address corresponding to the domain name MMSCdomain.
  • Local DNS sends a domain name query request to 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.
  • 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.
  • the WAP GW sends a MM1 submit request to the MMS router.
  • the MMS router sends an MM1 submission request to the MMSC.
  • 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.).
  • a prior allocation principle e.g., number information principle or average allocation principle, etc.
  • 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.
  • the MMSC feeds back to the MMS router that the MM1 submits a response.
  • 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.
  • the MMSC sends an MM1 notification request to the WAP GW.
  • 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.
  • the Uniform Resource Locator (Post) of the Push notification is the MMSC Domain of the MMSC.
  • the WAP GW sends an MM1 notification response to the MMS router.
  • the receiver 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.
  • the MMS router sends an MM1 notification response to the MMSC.
  • the MMS router 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.
  • 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 MMSCDomain received in step 409 is also carried in the message requested to be downloaded in this embodiment.
  • the MMS router sends a request download message to the MMSC.
  • the MMS router 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.
  • the MMSC feeds back the MM1 download response message to the MMS router.
  • the MMSC1 finds a corresponding message from the memory or the disk and returns it to the MMS router.
  • 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.
  • 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.
  • 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.
  • the MMS router sends an MM1 confirmation request message to the MMSC.
  • the MMS router 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.
  • step 416 and step 417 are the confirmation process after the terminal successfully downloads the message.
  • the MMSC sends an MM1 delivery report to the WAP GW.
  • 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.
  • the WAP GW sends the MM1 reading report to the MMS router.
  • 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.
  • the MMS router sends an MM1 reading report to the MMSC.
  • the MMS router 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.
  • the MMSC sends an MM1 read report response to the WAP GW.
  • 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 backup MMSC performs MMS service processing, so that disaster recovery between multiple MMSCs can be implemented.
  • 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 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 :
  • the mail server sends a domain name service request to the Local DNS.
  • Local DNS sends a domain name query request to the MMS router.
  • the TTL time has expired.
  • the query is obtained.
  • the name server of the domain name MMSCdomain is recorded as a MMS router.
  • 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.
  • 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.
  • the mail server sends an MM3 delivery request to the MMS router.
  • the MMS router sends an MM3 delivery request to the MMSC.
  • 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).
  • 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.
  • the MMSC feeds back the MM3 delivery response to the MMS router.
  • the MMS router feeds back the MM3 delivery response to the mail server.
  • 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.
  • the WAP GW sends a domain name service request to the Local DNS.
  • the Local DNS feeds back the domain name service response to the WAP GW.
  • the WAP GW sends an MM1 notification response to the MMS router.
  • the receiver 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.
  • the MMS router sends an MM1 notification response to the MMSC.
  • the MMS router 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.
  • 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.
  • the MMS router sends a request download message to the MMSC.
  • the MMS router 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.
  • 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.
  • the MMS router feeds back a download response message to the WAP GW.
  • 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.
  • the MMS router sends an MM1 confirmation request message to the MMSC.
  • the MMS router 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.
  • 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.
  • 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.
  • 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;
  • 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.
  • 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:
  • the foreign MMSC sends a domain name service request to the Local DNS.
  • the shell lj goes to the Local DNS to query the IP address corresponding to the domain name MMSCDomain.
  • Local DNS sends a domain name service request to the MMS router.
  • the name server of the domain name MMSCdomain is logged as a MMS router.
  • 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.
  • 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.
  • 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.
  • the foreign MMSC sends an MM4 submit request to the MMS router.
  • the MMS router sends an MM4 submission request to the MMSC.
  • 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).
  • 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.
  • the MMSC feeds back the MM4 delivery response to the MMS router.
  • the MMS router forwards the MMSC feedback MM4 delivery response
  • 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.
  • the WAP GW sends a domain name service request to the Local DNS.
  • the Local DNS feeds back the domain name service response to the WAP GW.
  • the WAP GW sends an MM1 notification response to the MMS router.
  • the receiver 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.
  • the MMS router sends an MM1 notification response to the MMSC.
  • the MMS router 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.
  • 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.
  • the MMS router sends a request download message to the MMSC.
  • the MMS router 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.
  • 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.
  • the MMS router feeds back the response message to the WAP GW.
  • 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.
  • the MMS router sends an MM1 confirmation request message to the MMSC.
  • the MMS router 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.
  • the MMSC sends an MM4 delivery report request to the external MMSC.
  • the foreign MMSC feeds back the MM4 delivery report response to the MMSC.
  • 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.
  • 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.
  • 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:
  • the SP sends a domain name service request to the Local DNS.
  • IP address of the domain name MMSCDomain is queried by the local DNS.
  • Local DNS sends a domain name service request to the MMS router.
  • the name server of the domain name MMSCdomain is logged as a MMS router.
  • 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.
  • 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.
  • 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.
  • SP sends a MM7 submission request to the MMS router
  • the MMS router sends an MM7 submission request to the MMSC.
  • 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).
  • 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.
  • the MMSC feeds back the MM7 delivery response to the MMS router.
  • the MMS router feeds back to the SP, and the MM7 delivers a response;
  • 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.
  • the WAP GW sends a domain name service request to the Local DNS.
  • the Local DNS feeds back the domain name service response to the WAP GW.
  • the WAP GW sends an MM1 notification response to the MMS router.
  • the receiver 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.
  • the MMS router 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.
  • 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.
  • the MMS router sends a request download message to the MMSC.
  • the MMS router 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.
  • 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.
  • the MMS router feeds back the response message to the WAP GW;
  • 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.
  • the MMS router sends an MM1 confirmation request message to the MMSC.
  • the MMS router 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.
  • the MMSC sends an MM7 delivery report request to the SP.
  • the SP feeds back the MM7 delivery report response to the MMSC.
  • 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.
  • 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 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.
  • 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.
  • the MMS router with normal heartbeat detection is one, the MMS router that passes the detection detects the normal MMS router for the heartbeat;
  • 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.
  • 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;
  • 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 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.
  • the first MMS router 803 can allocate the MMS according to different allocation principles, so that the MMSCs are load-shifted, thereby improving the processing efficiency of each MMSC.
  • 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.
  • the domain name in the related information is the first MMSC 903 domain name
  • the related information is sent to the first MMSC 903.
  • the domain name in the related information is the second MMSC 904 domain name
  • the related information is sent to the second MMSC 904.
  • the wireless application protocol gateway/service provider 901 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 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 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;
  • the address feedback unit 1006 feeds back the IP address of the normal MMS router to the local DNS.
  • 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 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;
  • 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.
  • the MMS router includes a detecting unit 1002, and can determine whether the first MMSC corresponding to the received MMS is faulty.
  • 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.
  • the MMS router 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 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.
  • the MMS router 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 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.
  • 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.
  • the MMS router 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.

Abstract

L’invention concerne un procédé de mise en application de service de messagerie multimédia, un système de communication et un routeur de messages multimédias. Ledit procédé comprend les étapes suivantes : la demande d’interrogation de noms de domaine envoyée par le serveur de noms de domaine local (DNS local) est reçue ; l’adresse du routeur de messages multimédias est renvoyée au serveur de noms de domaine local ; le routeur de messages multimédias reçoit le message multimédia et le transmet au centre de service de messagerie multimédia (MMSC) qui réussit les tests.
PCT/CN2009/072586 2008-10-10 2009-07-01 Procédé de mise en application de service de messagerie multimédia, système de communication et routeur de messages multimédias WO2010040292A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN2008101674824A CN101730318B (zh) 2008-10-10 2008-10-10 一种彩信业务实现方法及通讯系统以及彩信路由器
CN200810167482.4 2008-10-10

Publications (1)

Publication Number Publication Date
WO2010040292A1 true WO2010040292A1 (fr) 2010-04-15

Family

ID=42100209

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2009/072586 WO2010040292A1 (fr) 2008-10-10 2009-07-01 Procédé de mise en application de service de messagerie multimédia, système de communication et routeur de messages multimédias

Country Status (3)

Country Link
CN (1) CN101730318B (fr)
BR (1) BRPI0905252A2 (fr)
WO (1) WO2010040292A1 (fr)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101917679A (zh) * 2010-08-09 2010-12-15 华为技术有限公司 业务分流的方法、装置及系统
CN103379381A (zh) * 2012-04-17 2013-10-30 中兴通讯股份有限公司 基于wap网关的视频播放方法、wap网关及系统

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1666486A (zh) * 2002-06-28 2005-09-07 思科技术公司 用于使用域名服务锚定移动节点的方法和装置
CN1700678A (zh) * 2004-05-21 2005-11-23 华为技术有限公司 一种实现多媒体消息服务业务单节点接入的处理方法
CN1960521A (zh) * 2006-11-30 2007-05-09 华为技术有限公司 增大多媒体消息业务系统容量的方法及系统

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN100372391C (zh) * 2004-08-16 2008-02-27 华为技术有限公司 一种多媒体消息系统及转发多媒体消息的方法
CN101068378B (zh) * 2007-06-21 2012-07-04 华为技术有限公司 实现多媒体消息业务系统容灾的方法、系统及设备

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1666486A (zh) * 2002-06-28 2005-09-07 思科技术公司 用于使用域名服务锚定移动节点的方法和装置
CN1700678A (zh) * 2004-05-21 2005-11-23 华为技术有限公司 一种实现多媒体消息服务业务单节点接入的处理方法
CN1960521A (zh) * 2006-11-30 2007-05-09 华为技术有限公司 增大多媒体消息业务系统容量的方法及系统

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101917679A (zh) * 2010-08-09 2010-12-15 华为技术有限公司 业务分流的方法、装置及系统
CN103379381A (zh) * 2012-04-17 2013-10-30 中兴通讯股份有限公司 基于wap网关的视频播放方法、wap网关及系统
CN103379381B (zh) * 2012-04-17 2016-12-14 中兴通讯股份有限公司 基于wap网关的视频播放方法、wap网关及系统

Also Published As

Publication number Publication date
CN101730318B (zh) 2012-04-04
CN101730318A (zh) 2010-06-09
BRPI0905252A2 (pt) 2011-03-22

Similar Documents

Publication Publication Date Title
US9763084B2 (en) Secure location session manager
US8825060B2 (en) Methods, systems, and computer readable media for dynamically learning diameter binding information
US9444759B2 (en) Service provider registration by a content broker
US7415536B2 (en) Address query response method, program, and apparatus, and address notification method, program, and apparatus
US8122098B1 (en) Managing content delivery network service providers by a content broker
US7471679B2 (en) Method and apparatus for receivability and reachability test of explicit multicast
WO2009067921A1 (fr) Procédé, système et appareil de traitement d'un message commercial avec une pluralité de terminaux
US20210243170A1 (en) Methods for processing encrypted domain name server, dns, queries received from user equipment in a telecommunication network
US8032596B2 (en) System and method for managing e-mail messages
EP2187565A1 (fr) Procédé et dispositif de détection et de traitement de défaillance de n ud dans un réseau poste à poste
US8972587B1 (en) Arbitration server for determining remediation measures in response to an error message from a content provider
KR100693320B1 (ko) 소스 어드레스 선택시스템, 라우터장치, 라우터장치로서 컴퓨터를 기능시키기 위한 프로그램을 기록한 컴퓨터 독출가능한 기록매체, 통신노드 및 소스 어드레스 선택방법
CN102100042A (zh) 消息传递机制
WO2008135304A1 (fr) Procédé et appareil de partage de fichier de dispositif mobile
JP2005526470A (ja) Ｉｐドメインのｐｌｍｎメッセージングサービスの制御
WO2008064591A1 (fr) Procédé, système et dispositif pour augmenter la capacité d'un système de services de messagerie multimédia
WO2008020644A1 (fr) Serveur mandataire, système de communication, procédé de communication et programme
BRPI0514485B1 (pt) Sistema de mensagens de multimídia e método para o envio de mensagens de multimídia
WO2007112644A1 (fr) Procédé de récupération d'appel pendant une défaillance de réseau et système associé
US20040032865A1 (en) Apparatus and method for establishing a call connection state in a packet data communication system
WO2009024063A1 (fr) Procédé, dispositif et système pour identifier un service
WO2007112683A1 (fr) Procédé, appareil et système de récupération d'appel
WO2010040292A1 (fr) Procédé de mise en application de service de messagerie multimédia, système de communication et routeur de messages multimédias
US20160269496A1 (en) Method and application server for executing a service-related operation for a device user
WO2010009666A1 (fr) Procédé, système et dispositif pour implémenter un service multimédia

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 09818756

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 09818756

Country of ref document: EP

Kind code of ref document: A1