CN101068378B - Method, system and equipment for realizing multimedia information service system disaster recovery - Google Patents

Method, system and equipment for realizing multimedia information service system disaster recovery Download PDF

Info

Publication number
CN101068378B
CN101068378B CN2007101094523A CN200710109452A CN101068378B CN 101068378 B CN101068378 B CN 101068378B CN 2007101094523 A CN2007101094523 A CN 2007101094523A CN 200710109452 A CN200710109452 A CN 200710109452A CN 101068378 B CN101068378 B CN 101068378B
Authority
CN
China
Prior art keywords
mmsc
address
disaster tolerance
disaster
message
Prior art date
Legal status (The legal status 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 status listed.)
Expired - Fee Related
Application number
CN2007101094523A
Other languages
Chinese (zh)
Other versions
CN101068378A (en
Inventor
汪洋
程卫明
张志远
史以兵
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies Co Ltd
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 Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Priority to CN2007101094523A priority Critical patent/CN101068378B/en
Publication of CN101068378A publication Critical patent/CN101068378A/en
Application granted granted Critical
Publication of CN101068378B publication Critical patent/CN101068378B/en
Expired - Fee Related legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

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/07—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail characterised by the inclusion of specific contents
    • H04L51/10—Multimedia information
    • 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/214—Monitoring or handling of messages using selective forwarding
    • 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/58—Message adaptation for wireless communication

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Multimedia (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

A disaster tolerating method of multimedia message service system includes revising IP address in corresponding relation of prestored MMSC to be IP address of corresponding disaster-tolerant MMSC when disaster occurred on MMSC is confirmed and sending message required to be sent to said MMSC to said disaster-tolerant MMSC by querying IP address corresponding to said MMSC. The system and device used for realizing said method are also disclosed.

Description

Realize method, system and the equipment of multimedia information service system disaster recovery
Technical field
The present invention relates to the multimedia messaging service, MMS technology, be specifically related to method, system and the equipment of a kind of realization multimedia messaging service, MMS (MMS, Multimedia Message Service) system disaster tolerance.
Background technology
Along with telecommunication service more and more depends on computer system, computer system also becomes the core of telecom business support system when for the telecommunication service fast development technical foundation framework being provided.Because when realizing various telecommunication service, user profile memory device and transaction processing system high concentration cause telecom business support system to have the hidden danger of a lot of data disasters.
The data disaster is meant that large-scale interruption has appearred in data handling procedure; And can not recover within a certain period of time; For example; Natural causes such as fire, explosive incident, earthquake, floods, and non-natural cause such as mechanical disorder, human factor causes computer system to break down, and the disaster that causes.Here, describe for ease, " data disaster " abbreviated as " disaster ".
MMS is further developing of SMS service (SMS, Short Message Service) and enhanced message service, EMS (EMS, Enhanced Message Service), for the service of personal multi-media mobile communication provides complete end-to-end solution.Multimedia messaging service, MMS center (MMSC; Multimedia Message Service Center) system comprises a plurality of MMSC office point; Each office point is used for controlling the submission of the user message that belongs to the site respectively in real time and issuing, and user profile, Multimedia Message and session information are stored in the memory device of this MMSC office point.In case disaster takes place in a certain office point in the MMSC system; Will make the user profile that belongs to the site lose; And can cause the professional interruption of the site MMSC, or even can't recover professional for a long time, thereby make the user who belongs to this MMSC office point can't use MMS; When having influenced user's service quality, also can cause great economic loss to operator.
Fig. 1 is the structural representation of existing multimedia information service system.Referring to Fig. 1, existing multimedia information service system comprises electronic code name server (Enum DNS, ElectronicNumbering Domain Name Server), gateway and MMSC office point.
Below be the operation principle of this system of example explanation with the multimedia messaging service, MMS of realizing terminal-to-terminal service.Wherein, gateway is Wireless Application Protocol Gateway (WAP GW, Wireless Application ProtocolGateway).
Wherein, the MMSC office point comprises MMSC and database server.
MMSC is used to receive multimedia message sent by sending, the session information of preserving this Multimedia Message and handling this Multimedia Message; The Query Database server; According to the recipient who obtains and the user profile of transmit leg, will carry procotol (IP, InternetProtocol) propelling movement of address (Push) notice of this MMSC through WAP GW; Be message informing request (MM1_Notification.req), send to the recipient; And after receiving the message extraction request (MM1_retrieve.req) of recipient, MM delivery is arrived recipient WAP GW through WAP GW transmission.
Wherein, session information comprises sign, transmit leg and the information such as recipient's information, MMSCID of this Multimedia Message.
Database server is used to preserve user profile, comprising: subscriber blacklist, user's customized information, or this user information such as arrearage whether.
The user profile that MMSC obtains recipient and transmission is meant that MMSC in database server, inquire about the recipient and whether transmit leg is in the blacklist, whether arrearage, or through inquiring about some customized informations of this user's setting of acquisition.For example, if inquire transmit leg and the recipient is arranged in blacklist or arrearage list, then Multimedia Message is not sent in the MMSC selection; If inquiring the user is provided with customized information, then, carry out the processing of multimedia messaging service, MMS according to user's customized information.
Enum DNS, (ID Identifier) and the corresponding relation of MMSC IP address, supplies WAP GW and MMSC office point to inquire about to be used to preserve the sign of MMSC domain name, Subscriber Number section, MMSC.
WAP GW is used to receive the message submission request that professional recipient sends, and is forwarded to MMSC; And the message informing request of carrying MMSC IP address of reception MMSC transmission; Recipient's message extraction request is forwarded to this MMSC; And transmit the Multimedia Message that MMSC issues to the recipient.
WAP GW also is used for the message confirmation request (MM1_Acknowledgement.req) that the recipient sends is forwarded to MMSC.MMSC sends charge information to accounting server after the message confirmation request that receives recipient's transmission; The MMSC office point further comprises accounting server, is used for behind the charge information that receives the MMSC transmission, generates and also preserves ticket.
Charge information can comprise: caller information, recipient's information, Multimedia Message flow etc. supply accounting server to generate ticket, and the information of chargeing.
Gateway shown in Fig. 1 can also comprise MMS Proxy-Relay (MMSG, MultimediaMessaging Service Gateway), is used to realize communicating by letter of service provider (SP, Service Provider) and MMSC.
Fig. 2 is the method flow diagram of existing realization terminal-to-terminal service multimedia messaging service, MMS.As shown in Figure 2, this method may further comprise the steps:
Step 200: sending side terminal sends message to transmit leg WAP GW and submits request (MM1_Submit.req) to, wherein carries Multimedia Message and recipient's number that will send.
Step 201～step 203: transmit leg WAP GW inquiry Enum DNS, obtain the MMSC information of transmit leg ownership after, transmit message to this MMSC and submit request to.
Step 204～step 207: this MMSC is at the MMSC of Enum DNS inquiry transmit leg and recipient's number home.
Step 208～step 209: this MMSC judges that the MMSC of transmit leg ownership is himself, then submits to response (MM1_Submit.res) to send to transmit leg message through transmit leg WAP GW.
This step has received the Multimedia Message that transmit leg is submitted to notice transmit leg MMSC.
Step 210～step 211:MMSC judges that the MMSC of recipient's ownership is himself, and the message informing request (MM1_Notification.req) that then will carry the IP address of this Multimedia Message and this MMSC sends to recipient WAP GW; Be forwarded to the recipient by recipient WAP GW.
In this step, if MMSC judges that the MMSC of recipient's ownership is not himself, then with forwarding recipient MMSC to before the message submission request; To carry the message informing request of Multimedia Message and himself IP address by recipient MMSC, send to the recipient.
Step 212～step 215: recipient WAP GW is after the message informing response (MM1_Notification.res) that receives recipient's transmission, at the MMSC of Enum DNS inquiry recipient ownership; And the response of this message informing is forwarded to this MMSC.
Step 216～step 219: the recipient is carried on the MMSC IP address in the message informing request in the message extraction request (MM1_Retrieve.req), sends to MMSC through WAP GW; MMSC sends the message extraction response (MM1_Retrieve.res) of carrying Multimedia Message through WAP GW to the recipient.
Step 220～step 223: the recipient replys message confirmation request (MM1_Acknowledgement.req) to recipient WAP GW after receiving Multimedia Message; Recipient WAP GW inquires about recipient's ownership MMSC, and this message confirmation request is forwarded to this MMSC.
MMSC sends to accounting server with charge information after receiving message confirmation request, generate ticket by accounting server, and the preservation ticket is used for chargeing.
If transmit leg and recipient be not in consolidated network; Then the MMSC of recipient's ownership is sending to the recipient with Multimedia Message; And after receiving the message confirmation request that the recipient sends to; MMSC to the transmit leg ownership replys delivery report request (MM4_DeliverReport.req), and the MMSC recipient who belongs to the notice transmit leg successfully receives Multimedia Message.
In the said method flow process, step 200～step 209 receives the process of Multimedia Message for MMSC; Step 210～step 219 is the process of MMSC to recipient's transmitting multimedia message; Step 220～223 receive the process of message authentication for MMSC.
Can be known that by above description MMSC is responsible for the office point receiving and transmitting multimedia message, as the media between transmit leg and the recipient, in case disaster takes place in the MMSC office point, then this MMSC office point can't receive and handle new information; Step 215, step 217 and step 218 can't be carried out among Fig. 2, and the user who obtains the Push notice can't extract message; Step 223 can't be carried out among Fig. 2, makes the user who successfully obtains message return messages to confirm request, thereby can't generate ticket; Not in the situation of consolidated network, the MMSC that the recipient belongs to network can't repeat multimedia news to the disaster MMSC that transmit leg belongs to network, makes the recipient can't receive the message of transmit leg for recipient and transmit leg; After if the recipient successfully obtains message, disaster takes place in the MMSC that the recipient belongs to network, and then this MMSC can't belong to the MMSC transmission delivery report request of network to transmit leg, makes the MMSC of transmit leg place network can't generate ticket.
In sum, the method that existing multimedia information service system and multimedia messaging service, MMS are realized does not have the disaster tolerance function; After the data disaster takes place, do not take remedial measure, therefore,, then can influence user's use in case the data disaster takes place, also operator is caused great economic loss.
Summary of the invention
In view of this, the embodiment of the invention provides a kind of method that realizes multimedia information service system disaster recovery, makes that the MMSC system can operate as normal after disaster takes place.
The embodiment of the invention provides a kind of system that realizes multimedia information service system disaster recovery, makes that the MMSC system can operate as normal after disaster takes place.
The present invention provides a kind of net control device, makes that service provider (SP, Service Provider) server still can use MMS when disaster takes place MMSC.
The present invention provides a kind of electronic code name server, makes that the MMSC system can operate as normal when disaster takes place MMSC.
For achieving the above object, the technical scheme of the embodiment of the invention is achieved in that
A kind of method that realizes the multimedia messaging service, MMS disaster tolerance comprises:
When disaster takes place in definite MMSC; Electronic code name server Enum DNS is under the control of net control device, with the IP address of the IP address modification in the corresponding relation of the Internet protocol IP address of ID that comprises the Subscriber Number section that belongs to said MMSC, said MMSC that is stored in the said MMSC among the Enum DNS in advance and said MMSC for corresponding disaster tolerance MMSC;
Inquire about the corresponding IP address of said MMSC through gateway, the message that needs is sent to said MMSC sends to said disaster tolerance MMSC.
A kind of system that realizes multimedia information service system disaster recovery comprises multimedia messaging service, MMS center MMSC, corresponding disaster tolerance MMSC, gateway, electronic code name server Enum DNS and net control device,
Said MMSC is used to handle himself multimedia messaging service, MMS;
Said disaster tolerance MMSC is used for when disaster takes place said MMSC, handling the multimedia messaging service, MMS of said MMSC;
Said Enum DNS is used to preserve the corresponding relation of Internet protocol IP address of ID and the said MMSC of the Subscriber Number section that belongs to said MMSC comprising of said MMSC, said MMSC; When disaster takes place for said MMSC, under the control of net control device, be the IP address of the disaster tolerance MMSC of correspondence with the IP address modification in this MMSC corresponding relation;
Said net control device is used for when confirming that disaster takes place said MMSC, and controlling the said EnumDNS IP address modification that said MMSC is corresponding is the IP address of said disaster tolerance MMSC;
Said gateway, the IP address in the corresponding relation of the said MMSC that is used for preserving through inquiry Enum DNS, the message that needs is sent to said MMSC sends to said disaster tolerance MMSC.
A kind of net control device comprises memory module, timing module and transceiver module,
Memory module is used to preserve the time-out time that is provided with in advance, the IP address of the procotol IP address of multimedia messaging service, MMS center MMSC and the disaster tolerance MMSC of correspondence;
Transceiver module is used for after submitting Multimedia Message to MMSC, sending the triggering signal that picks up counting to timing module; After the response that receives this MMSC transmission, to timing module transmission stopping timing trigger message; After receiving the triggering signal of timing module, submit Multimedia Message to the IP address of the disaster tolerance MMSC of MMSC;
Timing module is used to receive and picks up counting after the triggering signal, picks up counting; Receive stop the timing triggering signal after, stop timing; Surpass the time-out time of memory module preservation in timing after, send triggering signal to transceiver module.
A kind of electronic code name server comprises: memory module is used to preserve the corresponding relation of Internet protocol IP address of ID and the said MMSC of the Subscriber Number section that belongs to said MMSC comprising of MMSC, said MMSC; And modified module, be used under the control of net control device, with the IP address modification in the said MMSC corresponding relation IP address of the disaster tolerance MMSC of correspondence.
Compared with prior art, when the technical scheme that the embodiment of the invention provided at definite MMSC disaster took place, the IP address modification that this MMSC is corresponding was the IP address of disaster tolerance MMSC, and the message that needs send to this MMSC is sent to disaster tolerance MMSC.Therefore; When disaster takes place in MMSC; All multimedia messaging service, MMSs that belong to the user of this MMSC all switch to corresponding disaster tolerance MMSC by disaster MMSC and handle; Thereby make that the MMSC system still can operate as normal, and can not cause the professional interruption of large tracts of land user MMS, avoid operator is caused economic loss.
Description of drawings
Fig. 1 is the structural representation of existing multimedia information service system;
Fig. 2 is the method flow diagram of existing realization terminal-to-terminal service multimedia messaging service, MMS;
Fig. 3 is a system configuration sketch map of realizing multimedia information service system disaster recovery in the embodiment of the invention;
Fig. 4 is the internal system structural representation in the embodiment of the invention;
Fig. 5 is the internal system structural representation again in the embodiment of the invention;
Fig. 6 switches the process chart of stylish submission message for disaster in the embodiment of the invention;
The process chart of the message that Fig. 7 is handling when switching for disaster in the embodiment of the invention;
The process chart of the delivery report that Fig. 8 is handling when switching for disaster in the embodiment of the invention;
Fig. 9 is the method flow diagram that SP submits message in the embodiment of the invention;
Figure 10 is the local SP business processing flow figure in the embodiment of the invention;
Figure 11 is another system configuration sketch map of realizing multimedia information service system disaster recovery in the embodiment of the invention;
Figure 12 is the another internal system structural representation in the embodiment of the invention.
Embodiment
Below in conjunction with accompanying drawing and specific embodiment the present invention is elaborated.
The method of realization multimedia messaging service, MMS disaster tolerance provided by the invention when disaster takes place definite MMSC, is the IP address of the disaster tolerance MMSC of correspondence with the IP address modification in this MMSC corresponding relation of storage in advance; And through the corresponding IP address of this MMSC of inquiry, the message that needs is sent to this MMSC sends to disaster tolerance MMSC.
Below the situation to complete geographical disaster tolerance is elaborated.
The corresponding relation of the ID of the Subscriber Number section belong to this MMSC and this MMSC at first is set at Enum DNS; And the corresponding relation of the ID of this MMSC and its IP address; When disaster takes place in this MMSC; In this corresponding relation, the IP address that disaster MMSC is corresponding, the IP address of being revised as corresponding disaster tolerance MMSC.
Fig. 3 is a system configuration sketch map of realizing multimedia information service system disaster recovery in the embodiment of the invention.Referring to Fig. 3, this system comprises Enum DNS, gateway, MMSC office point A and MMSC office point B.
Wherein, Enum DNS is used to preserve the corresponding relation of MMSC; The corresponding relation that comprises MMSC domain name, number segment, MMSC ID and IP address; When disaster took place MMSC, the IP address modification of the MMSC that this disaster MMSC domain name and Subscriber Number is corresponding be the IP address of the disaster tolerance MMSC of this MMSC correspondence.
For example, this corresponding relation can be for as shown in the table:
Figure S071A9452320070704D000081
The mapping table that table 1Enum DNS preserves
Gateway is used for Multimedia Message is sent to MMSC through load equalizer, and the Push notice of carrying the MMSC domain name is sent to the recipient; After receiving the message extraction request of carrying the MMSC domain name, the IP address in that Enum DNS inquires about the MMSC of this MMSC domain name and recipient's number correspondence is forwarded to the MMSC with this IP address with this message extraction request through load equalizer; MMSC is sent to the recipient through the Multimedia Message that load equalizer issues.
MMSC office point A comprises load equalizer A, MMSC A, database server A and accounting server A.
MMSC A comprises at least one MMSC service node, is used to receive Multimedia Message; Query Database server A, the user profile that obtains transmit leg and recipient be legal after, send the Push that carries this MMSC domain name to the recipient and notify; After receiving the message extraction request, to recipient's transmitting multimedia message; And in its disaster tolerance module Multimedia Message and the session information of backup MMSC B;
Load equalizer A is used to preserve the disaster tolerance IP address of virtual ip address and the MMSC office point B of MMSC office point A; The message of disaster tolerance IP address of IP address and the MMSC office point B of MMSC office point A is mail in reception, is forwarded to the MMSC service node of confirming according to its load-balancing algorithm, and the forwards of MMSC service node is gone out;
Database server A is used to preserve the user profile that belongs to MMSC office point A; And backup attaching is in the user profile of MMSC office point B;
Accounting server A is used to preserve the user's who belongs to MMSC office point A ticket; And the content of the accounting server B preservation among the backup MMSC office point B.
MMSC office point B comprises load equalizer B, MMSC B, database server B and accounting server B.
MMSC B comprises at least one MMSC service node, is used to receive Multimedia Message; Query Database server B, the user profile that obtains transmit leg and recipient be legal after, send the Push that carries this MMSC domain name through load equalizer to the recipient and notify; After receiving the message extraction request, through load equalizer to recipient's transmitting multimedia message; And in its disaster tolerance module Multimedia Message and the session information of backup MMSC office point A;
Load equalizer B is used to preserve the disaster tolerance IP address of virtual ip address and the MMSC office point A of MMSC office point B; The message of disaster tolerance IP address of IP address and the MMSC office point A of MMSC office point B is mail in reception, is forwarded to the MMSC service node of confirming according to its load-balancing algorithm, and the forwards of MMSC service node is gone out;
Database server B is used to preserve the user profile that belongs to MMSC office point B; And backup attaching is in the user profile of MMSC office point A;
Accounting server B is used to preserve the user's who belongs to MMSC office point B ticket; And the content of the accounting server A preservation among the backup MMSC office point A.
Database server A and database server B carry out in real time synchronously, under preserving self, the user profile of MMSC office point, also back up the user profile of MMSC office point B and the user profile of MMSC office point A respectively.
Accounting server A and accounting server B periodically carry out ticket and duplicate, and under preserving self, user's ticket of MMSC office point, also back up user's ticket of MMSC office point B and MMSC office point A respectively.
It is synchronous that MMSC A and MMSC B carry out real time bidirectional, for example, can periodically carry out synchronously, also can in a side preserves, have when upgrading, and in time backs up the opposing party.MMSC also backs up mutually except that the Multimedia Message and session information of preserving self, and promptly MMSC A and MMSC B back up Multimedia Message and the session information of MMSC B and MMSC A respectively.
In the practical application, this system can also comprise IP network, and Enum DNS, gateway are realized through this IP network with communicating by letter of MMSC office point.
Introduce the operation principle of system shown in Figure 3 in detail below in conjunction with Fig. 4.Fig. 4 is the internal system structural representation in the embodiment of the invention.Referring to Fig. 4; MMSC office point A and MMSC office point B comprise two MMSC service nodes respectively: node A1, node A2 and Node B 1, Node B 2; Each node all comprises two modules; This node processing module is used to preserve and handle the user's who belongs to this office point Multimedia Message and session information, and the disaster tolerance module is the disaster tolerance module of a service node in another office point.For example: node A1 comprises RG_A1 and two modules of RG_B1 '; RG_A1 and corresponding disk are used to preserve and handle the Multimedia Message and the session information of own service node; RG_B1 ' is the disaster tolerance module of Node B 1 with corresponding disk; The Multimedia Message and the session information that are used for backup node B1, and when disaster takes place B, handle the user's who belongs to disaster MMSC Multimedia Message and session information in the MMSC office point; In like manner the service node of MMSC office point B also has two modules, and a processing that is used to preserve belongs to the user's of this office point Multimedia Message and session information, and another is used for backing up the Multimedia Message and the session information of a service node of MMSC office point A.Under the normal condition, the disaster tolerance module of each office point does not start, and just backs up the Multimedia Message and the session information of another office point at the disk space that is used for disaster tolerance.
Each office point also comprises database server and disaster tolerance database server; Database server is used to preserve the user profile that belongs to self office point; The disaster tolerance database server is the disaster tolerance database of another MMSC office point, is used for the user profile of backup attaching in another office point.For example, MMSC office point A comprises DB_A and DB_B ', and wherein DB_A is used to preserve the user profile that belongs to MMSC office point A, and DB_B ' is the disaster tolerance database of MMSC office point B, is used for the user profile of backup attaching in MMSC office point B.
The accounting server of each office point also comprises two (not shown)s, and accounting server is used to preserve the ticket of self MMSC office point, and the disaster tolerance accounting server is the disaster tolerance accounting server of another MMSC office point, is used to back up the ticket of another MMSC office point.
Therefore, MMSC office point A and MMSC office point B disaster tolerance each other.
When two MMSC office points all during operate as normal, two MMSC office points are respectively the user who belongs to self simultaneously provides MMS, and outer net is shown as two multimedia messaging service, MMS centers.The load equalizer of each MMSC office point has all been preserved two virtual IP addresses (VIP, Virtual Internet Protocol) address, and one of them is self IP address to outer net, and second is the disaster tolerance IP address of another office point.For example the load equalizer A of MMSC office point A has VIP-A and two IP addresses of VIP-B ', and VIP-A is the IP address of MMSC office point A to outer net, and VIP-B ' is the disaster tolerance IP address of MMSC office point B.At this moment, the MMSC ID that preserves on the Enum DNS and the corresponding relation of IP address are:
MMSC?ID?A<--->VIP?A
MMSC?ID?B<--->VIP?B。
When disaster took place MMSC office point A, the disaster tolerance module of MMSC office point A, disaster tolerance database server and disaster tolerance accounting server started, and disaster tolerance module RG_A1 ' and RG_A2 ' startup with the MMSC ID that preserves on the Enum DNS and the corresponding relation of IP address are:
MMSC?ID?A<--->VIP?A′
MMSC?ID?B<--->VIP?B。
Disaster tolerance module RG_A1 ' and RG_A2 ' read in Multimedia Message and the session information of MMSC office point A from corresponding disk, continue to handle the MMS of MMSC office point A.Thereby make the user who belongs to MMSC still can use MMS, and can not cause the interruption of large tracts of land user MMS, avoided the economic loss of operator.
The method of revising corresponding relation on the Enum DNS comprises:
Free hand modification, promptly when disaster took place MMSCA, with in the corresponding relation of preserving on the Enum DNS, the IP address modification that MMSC ID A is corresponding was its disaster tolerance IP address by artificially;
Perhaps; Show the information that it is in proper working order by MMSC to the disaster tolerance MMSC of correspondence transmission; If disaster tolerance MMSC in predefined a period of time, does not receive the information that it is in proper working order that shows of MMSC transmission, then disaster tolerance MMSC confirms that disaster takes place corresponding MMSC.Specifically, by MMSC A and MMSC B exchange heartbeat message or heartbeat response, when MMSC B in a period of time that is provided with in advance; When not receiving heartbeat message that MMSC A sends or heartbeat response; Think that then disaster takes place MMSC office point A, at this moment, MMSC B starts the disaster tolerance module; Send the message of upgrading corresponding relation by this disaster tolerance module to Enum DNS, the IP address modification that MMSC ID A is corresponding is its disaster tolerance IP address.That is to say disaster tolerance MMSC as net control device, after disaster takes place definite MMSC, send the information that the IP address of upgrading disaster MMSC in the corresponding relation is the disaster tolerance MMSC IP address of correspondence to Enum DNS;
Net control device perhaps is set separately; Detect the operating state of MMSC periodically; In case find MMSC generation disaster, then start corresponding disaster tolerance MMSC, and send the information that the IP address of upgrading disaster MMSC in the corresponding relation is the disaster tolerance MMSC IP address of correspondence to Enum DNS.
In the practical application, if the traffic carrying capacity of MMSC system is less, also working load equalizer not, two service nodes in each MMSC office point only move one, and another is as the disaster tolerance module of other MMSC office point.When disaster took place in other MMSC office point, another service node of this MMSC office point started, and continued to handle the business that belongs to disaster MMSC.
In the practical application; Also can the MMSC office point that be specifically designed to disaster tolerance be set for the MMSC office point; Disaster tolerance MMSC does not start during operate as normal in the MMSC office point, and only backs up the user profile of MMSC office point, content, Multimedia Message and the session information that accounting server is preserved; When disaster took place in the MMSC office point, disaster tolerance MMSC office point started, and the user that will belong to disaster MMSC switches to disaster tolerance MMSC office point and carries out the processing of multimedia messaging service, MMS.
Fig. 5 is an internal system structure chart again in the embodiment of the invention; Referring to Fig. 5, MMSC office point A comprise node A and Node B ', wherein node A is used to handle the Multimedia Message of this office point; And Node B ' when being used for the Node B generation disaster of the B in the MMSC office point; As disaster tolerance MMSC node, continue to handle the multimedia messaging service, MMS of MMSC B, thereby avoid MMSC that disaster takes place and have influence on the use of user MMS.At this moment, in the corresponding relation of preserving on the Enum DNS, the IP address corresponding with domain name, phone number section, the MMSC ID B of MMSC B is its disaster tolerance IP address by the IP address modification of disaster MMSC: the IP address of MMSC A.
Below with the MMSC office point A of recipient ownership disaster to take place be example, specify in the embodiment of the invention handling process of new submission message, the message of handling, the delivery report of handling and SP local service when switching for disaster.
Fig. 6 switches the process chart of stylish submission message for the disaster in the embodiment of the invention.Referring to Fig. 6, this handling process may further comprise the steps:
Step 600～step 609: transmit leg WAP GW receives from the message of transmit leg and submits request to, to the MMSC of Enum DNS inquiry sender number home, obtains the IP address of MMSC A '; Submit to request to send to MMSC A ' this message then; The MMSC that MMSC A ' inquires transmit leg and recipient ownership is himself, and the Query Database server B, the user profile that obtains transmit leg and recipient be legal after, reply message through transmit leg WAP GW to transmit leg and submit to and respond.
Above step is the step that transmit leg is submitted Multimedia Message to.When the MMSC of transmit leg WAP GW inquiry recipient ownership; Because disaster takes place in the MMSC A of recipient's ownership; Its disaster tolerance MMSCA ' startup; The IP address of the MMSC of recipient's ownership of preserving on the Enum DNS is the disaster tolerance IP address of disaster MMSC: the IP address of MMSC A ', therefore, transmit leg WAP GW will be somebody's turn to do the new message of submitting to and send to MMSC A '.
Step 610～step 611:MMSC A ' sends the message informing request of carrying its MMSC domain name through recipient WAP GW to the recipient.
Step 612～step 615: the recipient replys message informing response, inquire the MMSC A ' of recipient's ownership by recipient WAP GW after, this message informing response is sent to MMSC A '.
Step 616～step 621: the message extraction request that the recipient will carry this MMSC domain name sends to recipient WAP GW; Recipient WAP GW is at this MMSC domain name of Enum DNS inquiry and the corresponding MMSC of recipient's number, obtain the IP address of MMSC A ' after, this message extraction request is sent to MMSC A '; MMSC A ' sends the message extraction response of carrying Multimedia Message through recipient WAP GW to the recipient.
Step 621～step 625: the recipient after receiving Multimedia Message, through recipient WAPGW to MMSC A ' answer message confirmation request.
MMSC A ' sends charge information to disaster tolerance accounting server B after receiving message confirmation request, generate ticket by disaster tolerance accounting server B, and preserves.
This shows that when disaster took place MMSC A, the embodiment of the invention can be handled the disaster tolerance MMSC that newly submits to message directly to send to MMSC A, thereby makes the user who belongs to MMSC office point A still can use MMS.And because the disaster tolerance database of database server A, backed up the user profile of MMSC office point A among the database server B, therefore, after disaster tolerance switches, MMSCA ' also not can owing to inquiry less than user profile, and interrupt processing to message.Simultaneously, accounting server B has backed up the ticket of accounting server A, therefore, and can be owing to the ticket of losing MMSC office point A yet, and can not the user who belong to MMSC office point A be chargeed.
Pass through the new message of submitting to of MM4 interface for mail server through MM3 interface and other MMSC office point; It is identical with prior art to remove the process that receives Multimedia Message; Outside this repeats no more; After other comprised that MM delivery and user receive Multimedia Message, the process of confirming was identical with step 610～step 625, also repeats no more at this.
The process chart of the message that Fig. 7 is handling when switching for embodiment of the invention disaster.Referring to Fig. 7, this handling process may further comprise the steps:
Step 700～step 709: transmit leg WAP GW receives from the message that comprises Multimedia Message and recipient's number of transmit leg and submits request to, to the MMSC of Enum DNS inquiry transmit leg and recipient's ownership, obtains the IP address of MMSC A; Submit to request to send to MMSC A this message then; MMSC A Query Database server A, the user profile that obtains transmit leg and recipient be legal after, reply message through transmit leg WAP GW to transmit leg and submit to and respond.
Step 710～step 711:MMSC A sends the message informing request of carrying its MMSC domain name through recipient WAP GW to the recipient.
Step 712: after the recipient receives the message informing request, reply the message informing response.
Disaster takes place in step 713:MMSC A; The disaster tolerance module MMSC A ' startup of MMSC A; Simultaneously that the MMSC ID A that preserves on the Enum DNS is corresponding IP address modification is the disaster tolerance IP address of MMSC A; Be the IP address of MMSC A ', and send message that the data of notice EnumDNS are upgraded to each network element.
Being about to the corresponding IP address modification of MMSC ID A is the disaster tolerance IP address of MMSC A.
Step 714～step 716: recipient WAP GW obtains the IP address of MMSC A ' at the MMSC of Enum DNS inquiry recipient ownership; Then the message informing response is forwarded to MMSCA '.
Step 717～step 726 is identical with step 616～step 625, repeats no more at this.
Can know that by the above when switching owing to disaster, Enum DNS is with the corresponding IP address of MMSC that disaster takes place in the corresponding relation of its preservation; Be revised as the IP address of disaster tolerance MMSC, therefore, when disaster takes place in MMSC A; The message that MMSC A is handling; Can from the disaster tolerance module of MMSC office point B, read the Multimedia Message and the session information of backup by MMSC A ', proceed to handle, and can not cause the multimedia messaging service, MMS of handling to interrupt or the situation of information drop-out.And, can't know that disaster has taken place the MMSC of its ownership for the user.Simultaneously, accounting server B has backed up the ticket of accounting server A, therefore, and can be owing to the ticket of losing MMSC office point A yet, and can not the user who belong to MMSC office point A be chargeed.
The process chart of the delivery report that Fig. 8 is handling when switching for disaster in the embodiment of the invention.Referring to Fig. 8, this handling process may further comprise the steps:
Step 800～step 809: transmit leg WAP GW receives from the message that comprises Multimedia Message and recipient's number of transmit leg and submits request to; MMSC to Enum DNS inquiry transmit leg and recipient's number home; The MMSC that obtains the transmit leg ownership is himself, the IP address of the MMSC of recipient's ownership; And the Query Database server B, the user profile that obtains transmit leg and recipient be legal after, reply message through transmit leg WAP GW to transmit leg and submit to and respond.
Step 810～step 811:MMSC A sends message forwarding request (MM4_Forward.req) to recipient MMSC, after recipient MMSC receives, replys message forwarding response (MM4_Forward.res).
Disaster takes place in step 812:MMSC A, the disaster tolerance module MMSC A ' startup of MMSC A; Simultaneously the Enum DNS number segment that belongs to MMSC A that will be kept at himself changes to and belongs to MMSC A ', and sends message to each network element, and the data of notice Enum DNS are upgraded.
Step 813～step 816: recipient MMSC is at the MMSC of Enum DNS inquiry transmit leg and recipient's ownership, and the MMSC that obtains the transmit leg ownership is MMSC A ', and the MMSC of recipient's ownership is himself.
Step 817～step 832 is identical with step 610～step 625, just the Multimedia Message center is changed to recipient MMSC.
Step 833: recipient MMSC sends success with notice MMSC A ' by repeating multimedia news before it to MMSC A ' transmission delivery report request (MM4_DeliverReport.req), and MMSC A ' can generate ticket.
In this step; Recipient MMSC can directly send to the delivery report request disaster tolerance MMSC of MMSC A; Be because when disaster takes place MMSC A; The IP address that Enum DNS is corresponding with the MMSC ID A that self preserves changes to the IP address of MMSC A ', and notifies the data of each network element Enum DNS to upgrade.As recipient MMSC during to the MMSC of Enum DNS inquiry transmit leg ownership, what inquire promptly is the IP address of MMSC A ', and recipient MMSC preserves the corresponding relation of transmit leg and this IP address get off.Therefore, recipient MMSC can directly be forwarded to MMSC A ' according to sender number after receiving the delivery report request.Thereby the MMSC that disaster make to take place can not issuing and chargeing and generate influence the Multimedia Message of preceding turning out.
The WAP GW that more than describes except that having the module that has existed in the prior art, also comprises receiver module, sending module and enquiry module.Wherein, receiver module is used to receive the message extraction request of carrying MMSC domain name and professional recipient's number; Enquiry module inquires the corresponding IP address of this MMSC domain name and professional recipient's number in the corresponding relation that Enum DNS preserves; By sending module this message extraction request is sent to the MMSC with this IP address.
The Enum DNS that more than describes comprises: memory module is used to preserve the corresponding relation of MMSC; And modified module, be used under the control of net control device, with the IP address modification in the MMSC corresponding relation IP address of the disaster tolerance MMSC of correspondence.
The Multimedia Message handling process of the embodiment of the invention below is described when transmit leg is SP.
When SP passed through MMSG to MMSC submission message, its commit method flow process was as shown in Figure 9.Fig. 9 submits message flow chart to for embodiment of the invention SP, and referring to Fig. 9, this flow process may further comprise the steps:
Step 900～step 901:SP sends message to MMSG and submits request (MM7_Submit.req) to, and MMSG receives the back and submits response (MM7_Submit.res) to SP answer message.
The MMSC that step 902～step 903:MMSG inquiry Enum DNS obtains recipient's number home is MMSCA '.
Step 904:MMSG will submit request to MMSC A ' transmission message.
MMSC A ' is after receiving message submission request, and is identical to handling process and the step 604～step 625 of Multimedia Message, repeats no more at this.
MMSG can know by the above, owing to when receiving the Multimedia Message of SP submission, at first will arrive the MMSC of Enum DNS inquiry recipient number home.When disaster took place MMSC B, the IP address modification of the disaster MMSC that preserves on the Enum DNS was its disaster tolerance IP address.Therefore, when MMSG inquired about, what obtain was the disaster tolerance IP address of the MMSC that belongs to of recipient, thereby had avoided because MMSC disaster takes place and to the influence that MMS causes, makes SP user continue normally to use MMS.
When SP directly was submitted to MMSC with Multimedia Message, the handling process in the embodiment of the invention was shown in figure 10.Figure 10 is local SP business processing flow figure when disaster is switched in the embodiment of the invention.Referring to Figure 10, this handling process may further comprise the steps:
Step 1000:SP sends message to MMSC A and submits request to, and picks up counting.
Step 1001: after timing time reached the time that is provided with in advance, SP submitted request to MMSC A ' transmission message again.
In this step, SP is provided with two IP addresses in advance, and one is the IP address of the MMSC of this SP ownership, and another is the disaster tolerance IP address of ownership MMSC.When SP sends after message submits to request to pick up counting to MMSC A, if SP does not receive that MMSC is successfully receiving message and submitting to the message of returning after the request to submit response in the time that is provided with in advance, then SP thinks that disaster takes place MMSC A.Then, SP sends message to the disaster tolerance IP address of MMSC A again and submits request to.
Step 1002:MMSC A ' replys message to SP and submits response to, and stops timing.
Step 1003～step 1004:MMSC A ' is himself at the MMSC that Enum DNS inquiry obtains recipient's ownership; And it is legal to inquire recipient's user profile at database server.
Step 1005～step 1020 is identical with step 610～step 620, repeats no more at this.
Step 1021～step 1022:SP receives MMSC A ' after sending the Multimedia Message success, and the message of answer is sent report request (MM7_DeliveryReport.req), and return messages are sent report response (MM7_DeliveryReport.res).
Above-mentioned handling process is to be realized by the net control device that is arranged in the SP server; This net control device comprises memory module, timing module and transceiver module, wherein, and memory module; Be used to preserve the time-out time that is provided with in advance, the IP address of the IP address of MMSC and the disaster tolerance MMSC of correspondence; Transceiver module is used for after submitting Multimedia Message to MMSC, sending the signal that picks up counting to timing module, and timing module picks up counting after receiving this signal; When transceiver module receives the response of MMSC answer, send the signal that stops timing to timing module, timing module stops timing after receiving this signal; If transceiver module does not receive the response of MMSC, then timing module is because the time-out time that timing surpass to be preserved, and sends triggering signal to transceiver module; Transceiver module can resubmit message to the disaster tolerance IP address of the MMSC that preserves.
Can know that by the above professional for local SP, the embodiment of the invention is provided with IP address and the disaster tolerance IP address thereof of this SP ownership MMSC in advance at SP, and time-out time is set; After if SP submits new information to, within the time-out time that is provided with in advance, do not receive message and submit response to, then resubmit message to the disaster tolerance IP address of MMSC.Therefore, the embodiment of the invention guarantees that local SP business can not receive the influence of MMSC disaster.
In sum; When disaster takes place at MMSC in the technical scheme that present embodiment provides; Can continue by the disaster tolerance MMSC of disaster MMSC to handle for new submission message, the message of handling, the delivery report of handling and local SP business; Thereby, make the professional influence that can not receive the MMSC disaster, guaranteed that the user who belongs to disaster MMSC still can send or receive Multimedia Message.
Below specify multi-media messaging system structure and method of work flow process thereof when realizing the User Information Database disaster tolerance.
Figure 11 is another system configuration sketch map of realizing multimedia information service system disaster recovery in the embodiment of the invention.Referring to Figure 11, this system comprises Enum DNS, gateway, MMSC office point A and MMSC office point B.
Wherein, Enum DNS is used to preserve the corresponding relation of number segment, MMSC domain name, MMSC ID and IP address, and when disaster took place MMSC, the IP address modification that this disaster MMSC domain name is corresponding was the disaster tolerance IP address of this MMSC.
Gateway is used for Multimedia Message is sent to MMSC through load equalizer, and the Push notice of carrying the MMSC domain name is sent to the recipient; After receiving the message extraction request of carrying the MMSC domain name,, this message extraction request is forwarded to the MMSC with this IP address through load equalizer in the corresponding IP address of this MMSC domain name of Enum DNS inquiry; MMSC is sent to the recipient through the Multimedia Message that load equalizer issues.
MMSC office point A comprises load equalizer A, MMSC A, database server A and accounting server A.
MMSC A comprises at least one MMSC service node, is used to receive Multimedia Message; Query Database server A, the user profile that obtains transmit leg and recipient be legal after, send the Push that carries this MMSC domain name to the recipient and notify; After receiving the message extraction request, to recipient's transmitting multimedia message;
Load equalizer A is used to preserve the disaster tolerance IP address of virtual ip address and the MMSC office point B of MMSC office point A; The message of disaster tolerance IP address of IP address and the MMSC office point B of MMSC office point A is mail in reception, is forwarded to the MMSC service node of confirming according to its load-balancing algorithm, and the forwards of MMSC service node is gone out;
Database server A is used to preserve the user profile that belongs to MMSC office point A; And backup attaching is in the user profile of MMSC office point B;
Accounting server A is used for preserving the user's who belongs to MMSC office point A ticket.
MMSC office point B comprises load equalizer B, MMSC B, database server B and accounting server B.
MMSC B comprises at least one MMSC service node, is used to receive Multimedia Message; Query Database server B, the user profile that obtains transmit leg and recipient be legal after, send the Push that carries this MMSC domain name through load equalizer to the recipient and notify; After receiving the message extraction request, through load equalizer to recipient's transmitting multimedia message;
Load equalizer B is used to preserve the disaster tolerance IP address of virtual ip address and the MMSC office point A of MMSC office point B; The message of disaster tolerance IP address of IP address and the MMSC office point A of MMSC office point B is mail in reception, is forwarded to the MMSC service node of confirming according to its load-balancing algorithm, and the forwards of MMSC service node is gone out;
Database server B is used to preserve the user profile that belongs to MMSC office point B; And backup attaching is in the user profile of MMSC office point A;
Accounting server B is used to preserve the user's who belongs to MMSC office point B ticket.
Database server A and database server B carry out in real time synchronously, under preserving self, the user profile of MMSC office point, also back up the user profile of MMSC office point B and the user profile of MMSC office point A respectively.
The difference of Figure 11 and system shown in Figure 4 operation principle is; Present embodiment only carries out the backup of user profile; Break down or during disaster, can visit the disaster tolerance database that is positioned at disaster tolerance MMSC, and can not cause at the database server of MMSC owing to user profile is lost the problem of interrupting MMS.And when disaster takes place MMSC, can the business that belong to this disaster MMSC be switched to disaster tolerance MMSC, the user who proceeds to belong to disaster MMSC newly submits the processing of message to.Therefore, the present embodiment cost is low, realizes simply, and can realize the quick switching of disaster MMSC.
Specify the operation principle of system shown in Figure 11 below in conjunction with Figure 12.Figure 12 is the another internal system structural representation in the embodiment of the invention.Referring to Figure 10; MMSC office point A and MMSC office point B comprise two MMSC service nodes respectively: node A1, node A2 and Node B 1, Node B 2; Each node comprises the module of self node; For example: node A1 comprises RG_A1, and RG_A1 and corresponding disk are used to preserve the Multimedia Message and the session information of own service node.
Each office point also comprises two database servers, and first database server is used to preserve the user profile that belongs to self office point, and second database server is the disaster tolerance database of another MMSC office point, is used for the user profile of backup attaching in another office point.First database and second database are synchronous in real time.For example, MMSC office point A comprises DB_A and DB_B ', and wherein DB_A is used to preserve the user profile that belongs to MMSC office point A, and DB_B ' is the disaster tolerance database of MMSC office point B, is used for the user profile of backup attaching in MMSC office point B.
Each office point also comprises accounting server respectively, is used to preserve the user's who belongs to self MMSC office point ticket.
When two MMSC office points all during operate as normal, two MMSC office points are respectively the user who belongs to self simultaneously provides MMS, and outer net is shown as two multimedia messaging service, MMS centers.At this moment, the corresponding relation of the MMSC ID of the last preservation of EnumDNS and IP address is:
MMSC?ID?A<--->VIP?A
MMSC?ID?B<--->VIP?B。
When the database server generation disaster of MMSC office point A, for example, disaster takes place in DB_A; Since the disaster tolerance DB Backup of MMSC office point A all user profile of office point A; Therefore, when MMSC A needs the accessing database server, only need the DB_A ' of visit MMSC office point B to get final product.Thereby, realized the disaster tolerance of user profile making that the MMSC office point can be owing to interrupting the processing of MMS by the accessing database server.
When disaster took place MMSC office point A, MMSC B was as the disaster tolerance MMSC of MMSC A, and the MMSC ID that on Enum DNS, preserves and the corresponding relation of IP address are:
MMSC?ID?A<--->VIP?B
MMSC?ID?B<--->VIP?B。
At this moment, MMSC office point B also provides MMS professional for the terminal that belongs to MMSC office point A when for the user who belongs to MMSC office point B MMS being provided.When MMSC office point B when receiving the new message of submitting to of user, at first visit the database D B_B of himself, if do not find corresponding user profile, then visit again the disaster tolerance database D B_A ' of MMSC office point A.Thereby make the user who belongs to MMSC office point A still can use MMS, and can not cause the interruption of large tracts of land user MMS, avoided the economic loss of operator.
Wherein, confirm that disaster takes place MMSC, and change Enum DNS goes up method and the above description identical of the corresponding relation of preservation, repeat no more at this.
In the practical application, can also can therefore, repeat no more with described above identical with of the prior art identical at this for the business processing flow of new submission message.But, then can in disaster MMSC, lose owing to disaster takes place in the MMSC office point less than backup for message and the session information that is handling disaster MMSC office point.
Professional for local SP, except that the disaster tolerance IP address of MMSC is revised as the VIP B by VIP A ', therefore its handling process and described above identical, repeats no more at this.
In the practical application, if the traffic carrying capacity of MMSC system hour, then can be omitted load equalizer, at this moment, in two service nodes of MMSC office point, only move one, another service node is as the disaster tolerance module of other MMSC office point.When disaster took place in other MMSC office point, another service node of this MMSC started, and handled and belonged to the customer service of disaster MMSC, can be owing to disaster makes MMS interrupt thereby guaranteed.At this moment, the Multimedia Message handling process of system repeats no more at this with above-described identical.
In the practical application, also can be for the MMSC office point is provided with the MMSC office point be specifically designed to disaster tolerance, disaster tolerance MMSC does not start during operate as normal in the MMSC office point, and only backs up the user profile of MMSC office point; When disaster took place in the MMSC office point, disaster tolerance MMSC office point began to start, and it is professional to handle the new Multimedia Message of submitting to of user and the local SP that belong to the MMSC office point.
Can find out that by the above the technical scheme that the embodiment of the invention provided is when disaster takes place definite MMSC; With the IP address modification in this MMSC corresponding relation is the IP address of the disaster tolerance MMSC of correspondence, and through the corresponding IP address of this MMSC of inquiry, the message that needs is sent to this MMSC sends to this disaster tolerance MMSC; Therefore; When disaster took place MMSC, the multimedia messaging service, MMS that belongs to the user of this MMSC changes to be handled by disaster tolerance MMSC, thereby made that the MMSC system still can operate as normal; Make the MMSC system continual multimedia messaging service, MMS can be provided, finally can not use MMS to impact the user for all users.
Further, the complete geographical disaster tolerance of embodiment of the invention utilization makes between the MMSC disaster tolerance each other; Multimedia Message and session information etc. is backed up in realtime to disaster tolerance MMSC; When disaster takes place in a certain MMSC, start disaster tolerance MMSC fast, proceed professional processing; Thereby realized the professional quick switching of disaster MMSC, and can the Multimedia Message of handling not interrupted.For the user, the MMSC that disaster takes place can not exert an influence to its multimedia messaging service, MMS.
The above is merely preferred embodiment of the present invention, is not to be used to limit protection scope of the present invention.All within spirit of the present invention and principle, any modification of being done, be equal to replacement, improvement etc., all should be included within protection scope of the present invention.

Claims (17)

1. a method that realizes the multimedia messaging service, MMS disaster tolerance is characterized in that, this method comprises:
When disaster takes place in definite MMSC; Electronic code name server Enum DNS is under the control of net control device, with the IP address of the IP address modification in the corresponding relation of the Internet protocol IP address of ID that comprises the Subscriber Number section that belongs to said MMSC, said MMSC that is stored in the said MMSC among the Enum DNS in advance and said MMSC for corresponding disaster tolerance MMSC;
Inquire about the corresponding IP address of said MMSC through gateway, the message that needs is sent to said MMSC sends to said disaster tolerance MMSC.
2. the method for claim 1 is characterized in that, said definite MMSC disaster takes place comprises:
The SP server picks up counting after said MMSC submits Multimedia Message to;
The SP server does not receive the response message that said MMSC replys after reaching the time-out time that is provided with in advance in said timing, confirms that then disaster takes place said MMSC.
3. the method for claim 1 is characterized in that, said definite MMSC disaster takes place comprises:
Said MMSC sends to the disaster tolerance MMSC of correspondence and shows the information that it is in proper working order;
If said disaster tolerance MMSC does not receive the information that it is in proper working order that shows of said MMSC transmission in the predefined time, confirm that then disaster takes place said MMSC.
4. the method for claim 1 is characterized in that, the said message that needs is sent to said MMSC through the corresponding IP address of inquiry MMSC sends to disaster tolerance MMSC and comprises:
The transmit leg gateway is in said corresponding relation, and the corresponding MMSC of inquiry multimedia messaging service, MMS recipient is forwarded to the corresponding MMSC of said professional recipient with the Multimedia Message that receives.
5. the method for claim 1 is characterized in that, further comprises the MMSC domain name in the said corresponding relation;
The said message that needs is sent to said MMSC through the corresponding IP address of inquiry MMSC sends to disaster tolerance MMSC and comprises:
The MMSC of said professional recipient's ownership sends the propelling movement Push notice of carrying this MMSC domain name through recipient's gateway to professional recipient;
Recipient's gateway receives the message extraction request of carrying this MMSC domain name from professional recipient; The corresponding IP address of the said MMSC domain name of inquiry and professional recipient's number in said corresponding relation; And this message extraction request is forwarded to the MMSC with this IP address.
6. the method for claim 1 is characterized in that, the said message that needs is sent to said MMSC through the corresponding IP address of inquiry MMSC sends to disaster tolerance MMSC and comprises:
The MMSC of said professional recipient's ownership inquires about said corresponding relation, and the IP address that obtains the MMSC of professional transmit leg ownership is the IP address of its disaster tolerance MMSC;
The MMSC of said professional recipient's ownership sends the successful report of sending down service according to the IP address to the disaster tolerance MMSC of said professional transmit leg ownership.
7. a system that realizes multimedia information service system disaster recovery is characterized in that, this system comprises disaster tolerance MMSC, gateway, electronic code name server Enum DNS and the net control device of multimedia messaging service, MMS center MMSC, correspondence,
Said MMSC is used to handle himself multimedia messaging service, MMS;
Said disaster tolerance MMSC is used for when disaster takes place said MMSC, handling the multimedia messaging service, MMS of said MMSC;
Said Enum DNS is used to preserve the corresponding relation of Internet protocol IP address of ID and the said MMSC of the Subscriber Number section that belongs to said MMSC comprising of said MMSC, said MMSC; When disaster takes place for said MMSC, under the control of net control device, be the IP address of the disaster tolerance MMSC of correspondence with the IP address modification in this MMSC corresponding relation;
Said net control device is used for when confirming that disaster takes place said MMSC, and controlling the said EnumDNS IP address modification that said MMSC is corresponding is the IP address of said disaster tolerance MMSC;
Said gateway, the IP address in the corresponding relation of the said MMSC that is used for preserving through inquiry Enum DNS, the message that needs is sent to said MMSC sends to said disaster tolerance MMSC.
8. system as claimed in claim 7 is characterized in that, said system further comprises:
Database server is used to preserve the user profile that belongs to said MMSC, supplies said MMSC when processing multimedia message service, to inquire about;
The disaster tolerance database server is used to back up the user profile of said database server, supplies said disaster tolerance MMSC when processing belongs to user's the multimedia messaging service, MMS of said MMSC, to inquire about.
9. system as claimed in claim 7 is characterized in that, said system further comprises:
Accounting server is used for according to charge information, generates and preserve the user's who belongs to this MMSC ticket;
The disaster tolerance accounting server is used to back up the ticket that said accounting server is preserved.
10. like any described system in the claim 7 to 9; It is characterized in that; Said net control device can be arranged among the said disaster tolerance MMSC; Be used for when confirming that disaster takes place said MMSC, send the information of IP address that the IP address of upgrading said MMSC be the disaster tolerance MMSC of correspondence to Enum DNS;
Said Enum DNS is further used for after the IP address that receives the said MMSC of renewal that disaster tolerance MMSC sends is the information of IP address of disaster tolerance MMSC, upgrading the IP address of said MMSC.
11. system as claimed in claim 10 is characterized in that, said MMSC is further used for showing the information that it is in proper working order to said disaster tolerance MMSC transmission;
Said disaster tolerance MMSC is further used for preserving the time period that is provided with in advance; Do not receive in the said time period that said MMSC sends show its information in proper working order after, confirm that disaster takes place said MMSC.
12., it is characterized in that the session information that said disaster tolerance MMSC preserves when being further used for backing up the multimedia messaging service, MMS of said MMSC and handling this multimedia messaging service, MMS like any described system in the claim 7 to 9; When disaster takes place in said MMSC, read the Multimedia Message and the session information of said backup, continue to handle the multimedia messaging service, MMS that said MMSC is handling.
13. like any described system in the claim 7 to 9, it is characterized in that, further comprise the MMSC domain name in the said corresponding relation;
Said MMSC is used for when handling the multimedia messaging service, MMS of self, in the propelling movement Push notice of sending, carries said MMSC domain name;
Said gateway further comprises: receiver module is used to receive the message extraction request of carrying MMSC domain name and professional recipient's number;
Enquiry module is used for the corresponding relation in Enum DNS preservation, inquires about the corresponding IP address of this MMSC domain name and recipient's number;
And sending module, be used for transmitting said message extraction request to this IP address.
14., it is characterized in that said disaster tolerance MMSC further handles the multimedia messaging service, MMS of himself like any described system in the claim 7 to 9;
Said MMSC further when disaster takes place said disaster tolerance MMSC, handles the multimedia messaging service, MMS of said disaster tolerance MMSC;
Said system further comprises load equalizer, is used to preserve the virtual ip address of the MMSC that is provided with in advance, and supplies said disaster tolerance MMSC to carry out the IP address of disaster tolerance; Realize communicating by letter between Enum DNS and the said MMSC;
Said system further comprises the disaster tolerance load equalizer, is used to preserve the virtual ip address of the said disaster tolerance MMSC that is provided with in advance, and supplies said MMSC to carry out the IP address of disaster tolerance; Realize communicating by letter between Enum DNS and the said disaster tolerance MMSC.
15. system as claimed in claim 7 is characterized in that, said net control device comprises memory module, timing module and transceiver module,
Memory module is used to preserve in advance the procotol IP address of the time-out time that is provided with, multimedia messaging service, MMS center MMSC and the IP address of corresponding disaster tolerance MMSC;
Transceiver module is used for after submitting Multimedia Message to MMSC, sending the triggering signal that picks up counting to timing module; After the response that receives this MMSC transmission, to timing module transmission stopping timing trigger message; After receiving the triggering signal of timing module, submit Multimedia Message to the IP address of the disaster tolerance MMSC of MMSC;
Timing module is used to receive and picks up counting after the triggering signal, picks up counting; Receive stop the timing triggering signal after, stop timing; Surpass the time-out time of memory module preservation in timing after, send triggering signal to transceiver module.
16. a net control device is characterized in that said net control device comprises memory module, timing module and transceiver module,
Memory module is used to preserve the time-out time that is provided with in advance, the IP address of the procotol IP address of multimedia messaging service, MMS center MMSC and the disaster tolerance MMSC of correspondence;
Transceiver module is used for after submitting Multimedia Message to MMSC, sending the triggering signal that picks up counting to timing module; After the response that receives this MMSC transmission, to timing module transmission stopping timing trigger message; After receiving the triggering signal of timing module, submit Multimedia Message to the IP address of the disaster tolerance MMSC of MMSC;
Timing module is used to receive and picks up counting after the triggering signal, picks up counting; Receive stop the timing triggering signal after, stop timing; Surpass the time-out time of memory module preservation in timing after, send triggering signal to transceiver module.
17. an electronic code name server is characterized in that, this electronic code name server comprises memory module and modified module,
Said memory module is used to preserve the corresponding relation of Internet protocol IP address of the ID that comprises the Subscriber Number section that belongs to said MMSC, said MMSC and the said MMSC of multimedia messaging service, MMS center MMSC;
Said modified module is used under the control of net control device, is the IP address of the disaster tolerance MMSC of correspondence with the procotol IP address modification in the said MMSC corresponding relation.
CN2007101094523A 2007-06-21 2007-06-21 Method, system and equipment for realizing multimedia information service system disaster recovery Expired - Fee Related CN101068378B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN2007101094523A CN101068378B (en) 2007-06-21 2007-06-21 Method, system and equipment for realizing multimedia information service system disaster recovery

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN2007101094523A CN101068378B (en) 2007-06-21 2007-06-21 Method, system and equipment for realizing multimedia information service system disaster recovery

Publications (2)

Publication Number Publication Date
CN101068378A CN101068378A (en) 2007-11-07
CN101068378B true CN101068378B (en) 2012-07-04

Family

ID=38880783

Family Applications (1)

Application Number Title Priority Date Filing Date
CN2007101094523A Expired - Fee Related CN101068378B (en) 2007-06-21 2007-06-21 Method, system and equipment for realizing multimedia information service system disaster recovery

Country Status (1)

Country Link
CN (1) CN101068378B (en)

Families Citing this family (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101577867B (en) * 2008-05-08 2011-08-03 中国移动通信集团公司 Method, device and system for sending push messages in multimedia message service
CN101330664B (en) * 2008-07-21 2012-07-25 华为技术有限公司 Method, system and apparatus for realizing multimedia business
CN101730318B (en) * 2008-10-10 2012-04-04 华为软件技术有限公司 Implementing method for multimedia message service, communication system and multimedia message service router
CN101741604A (en) * 2008-11-10 2010-06-16 华为技术有限公司 Disaster-tolerant method, system and device
CN101668019B (en) * 2009-09-30 2013-06-05 中兴通讯股份有限公司 Gateway ensuring method, device and message transmitting method and system thereof
CN101695057A (en) * 2009-10-20 2010-04-14 中兴通讯股份有限公司 Method and equipment for sending multimedia message and domain name resolution server
CN102404697B (en) * 2010-09-14 2014-10-01 中国移动通信集团河南有限公司 Multi-media message service system, method and device
CN102572808B (en) * 2010-12-31 2015-07-15 上海博泰悦臻电子设备制造有限公司 Third generation (3G) wireless network-based address treatment method of PUSH system and system applying same
CN102917322B (en) * 2011-08-01 2015-08-19 中国移动通信集团公司 A kind of method and device realizing multimedia information service system disaster recovery
CN105451196A (en) * 2014-08-26 2016-03-30 中国移动通信集团公司 Multimedia message routing method, multimedia message routing device and multimedia message routing system
CN109962991B (en) * 2017-12-26 2022-06-14 中国移动通信集团四川有限公司 Internet of things fault processing method, device, equipment and medium
CN113497764B (en) * 2021-08-02 2023-04-07 中国电信股份有限公司 Service routing method, system, computer storage medium and electronic device

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1700678A (en) * 2004-05-21 2005-11-23 华为技术有限公司 Processing method for implementing multimedia message service single-node access
CN1829337A (en) * 2005-03-01 2006-09-06 中兴通讯股份有限公司 Mobile soft switching server disaster recovery method

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1700678A (en) * 2004-05-21 2005-11-23 华为技术有限公司 Processing method for implementing multimedia message service single-node access
CN1829337A (en) * 2005-03-01 2006-09-06 中兴通讯股份有限公司 Mobile soft switching server disaster recovery method

Also Published As

Publication number Publication date
CN101068378A (en) 2007-11-07

Similar Documents

Publication Publication Date Title
CN101068378B (en) Method, system and equipment for realizing multimedia information service system disaster recovery
JP5246332B2 (en) Enhanced messaging platform
CN102100042B (en) A message delivery mechanism
JP4291366B2 (en) Message management
KR100686382B1 (en) Messenger Notification System and Method Using Synchronization Server
US8719397B2 (en) Method and system for email and PIM synchronization and updating
US7587210B2 (en) Universal short code administration facility
US6832246B1 (en) Dynamic electronic forwarding system
US20090181705A1 (en) Mail transmission system and method and push mail server
US20060064307A1 (en) Method and system for session management wherein a client session identifier is used
CN1582011A (en) Methods and apparatus for alternative routing of text based messages on a cellular telephone network
US7580983B2 (en) E-mail forwarding system having archival database
CN100372391C (en) Multimedia message system and method for transmitting multimedia message
CN101370159B (en) Method, device and system for recognizing service
US20080242327A1 (en) System and method for sending sms and text messages
CN101317408B (en) Method and system for providing asynchronous communication through internet
KR20060112350A (en) Notification system and method using messenger
CN101389065B (en) Data disaster tolerant backup method and apparatus in multimedia message service system
WO2003058909A2 (en) Multimedia load balancing architecture
CN100558188C (en) Message processing device, system and method
CN102572696A (en) Method for processing service request, apparatus and system thereof
CN101026785A (en) Method for realizing for programme for mobile termianl to transmit multimedia message to Internet
CN101026787A (en) Method for transmitting short message given to telephone numbers to Inter net programme
US9641646B1 (en) Distributed multimedia system for IP networks
CN113612812B (en) Implementation of distributed group server and data synchronization method thereof

Legal Events

Date Code Title Description
C06 Publication
PB01 Publication
C10 Entry into substantive examination
SE01 Entry into force of request for substantive examination
C14 Grant of patent or utility model
GR01 Patent grant
C17 Cessation of patent right
CF01 Termination of patent right due to non-payment of annual fee

Granted publication date: 20120704

Termination date: 20130621