WO2012062051A1

WO2012062051A1 - Method and system for delivering multimedia messages

Info

Publication number: WO2012062051A1
Application number: PCT/CN2011/070442
Authority: WO
Inventors: 陶长标; 余湛悦
Original assignee: 中兴通讯股份有限公司
Priority date: 2010-11-11
Filing date: 2011-01-20
Publication date: 2012-05-18
Also published as: CN101986733A

Abstract

A method for delivering multimedia messages is disclosed by the present invention, which includes that: after sending a notification short message to a mobile terminal, a Short Message Service Center (SMSC) sends a delivering state message to a Multimedia Message Service Center (MMSC); when according to a delivering state code in the delivering state message the MMSC determines that the notification short message is delivered successfully, the MMSC finds the multimedia message according to the message identifier of the notification short message in the delivering state message and sends the multimedia message to the SMSC; a system for delivering multimedia message is also disclosed by the present invention. According to the technical solution of the present invention, the accuracy rate and success rate for delivering multimedia messages are improved.

Description

Method and system for delivering multimedia messages

The present invention relates to the field of multimedia message transmission, and in particular, to a method and system for delivering a multimedia message. Background technique

With the rapid development of mobile communication technology, especially the 3G service in the communication market, the proliferation of rich multimedia messages has become more and more popular, such as various mobile phone newspaper services, music on demand services, etc. More and more users are accepted, the value-added service of multimedia messages is growing rapidly every year, which puts higher and higher requirements on the success rate and accuracy of multimedia messages delivered to users' mobile terminals.

1 is a schematic structural diagram of a system of a multimedia message service center in the prior art, and FIG. 2 is a schematic flowchart of a multimedia message delivered in the prior art. As shown in FIG. 1 and FIG. 2, the current multimedia message service center (MMSC, Multimedia) The Messaging Service Center) uses the three steps specified in the multimedia messaging service specification when delivering multimedia messages:

The first step, the submission process: submitting the multimedia message to the MMSC by the provider's mobile terminal, or the service provider, or other value-added service system of the multimedia message;

In the second step, the notification process is sent: the MMSC sends a short message notification message to the mobile terminal of the receiver through the Short Message Service Center (SMSC), and informs the mobile terminal of the receiver that the multimedia message needs to be received.

The third step is the acquisition process: the mobile terminal of the receiver actively takes the multimedia message to the MMSC. In these three steps, in addition to mobile terminals, networks, etc., the maximum impact on the success rate and accuracy of multimedia message reception is the second step, because the current MMSC delivery notification process has the following two defects: The first defect is: The MMSC sends a notification SMS message to the SMSC. When the SMSC receives the message, it responds with an acknowledgment message to the MMSC, and informs the MMSC to receive the notification SMS message. After receiving the confirmation message, the MMSC determines that the notification SMS message has been received. The delivery is successful, and the subsequent operations are continued; however, the actual situation is that the SMSC does not immediately send the notification message to the receiving party after receiving the notification SMS message sent by the MMSC, but uses the store-and-forward method (short message protocol specification). The stipulations in the process are performed in the queue. After the actual delivery, the SMSC will not reply the final result to the SSMC. Therefore, whether the multimedia message is actually delivered successfully is unknown to the MMSC, which will result in some multimedia messages. The success rate of the multimedia message delivery is reduced because the mobile terminal of the receiver is not forwarded to the mailbox or expires.

The second defect is: When the SMSC sends the notification SMS message through the SMSC, it does not authenticate the number of the mobile terminal of the receiver, so there will be if the number of the mobile terminal of the receiver is an empty number or an abnormal number (for example 120), the MMSC still issues a notification short message, thereby affecting the accuracy rate of the delivery of the multimedia message, and once the multimedia message is expired, once the mail is successfully forwarded to the Dreamnet mailbox, the user also needs to deduct the fee.

At present, the MMSC has the above two defects in the processing of multimedia messages, which makes it difficult to achieve an ideal ratio of the accuracy and success rate of multimedia message reception. In addition, there are also problems such as an empty number deduction, which may cause users to Complaint. Summary of the invention

In view of this, the main purpose of the present invention is to provide a method and system for delivering a multimedia message, which can improve the accuracy and success rate of multimedia message delivery.

In order to achieve the above object, the technical solution of the present invention is achieved as follows:

The present invention provides a method for delivering a multimedia message, including:

After the short message center (SMSC) sends the notification short message to the mobile terminal, the delivery status message is sent to the multimedia message service center (MMSC);

When the MMSC determines, according to the delivery status code in the delivery status message, the notification short message is delivered to During the operation, the multimedia message is found according to the message identifier of the notification short message in the delivery status message, and is sent to the SMSC.

In the above method, the method further includes:

When the MMSC determines that the notification short message delivery fails according to the delivery status code in the delivery status message, it determines whether the delivery status of the short message is abnormal according to the error code in the delivery status message; if abnormal, the MMSC suspends the subsequent normal processing flow of the multimedia message. The destination number abnormality log is generated; if not abnormal, the MMSC initiates a resend process of the multimedia message; if it is in another state, the MMSC terminates the subsequent normal processing flow of the multimedia message, and generates a delivery failure log.

In the above method, after the SMSC sends the notification short message to the mobile terminal, and before sending the delivery status message to the MMSC, the method further includes:

The MMSC generates a message identifier of the multimedia message, and sends a notification message message to the SMSC; the SMSC generates a message identifier for notifying the short message, and sends the message identifier to the MMSC through the confirmation message; the MMSC saves the correspondence between the message identifier of the multimedia message and the message identifier of the notification SMS message. .

In the above method, the resending process of the MMSC to initiate the multimedia message is: the MMSC initiates a resend process of the multimedia message, and resends the notification message message to

The SMSC, until the notification SMS message is successfully sent to the recipient's mobile terminal, or the number of retransmissions reaches the preset retransmission threshold.

In the above method, the message identifier of the MMSC to generate the multimedia message is:

After receiving the multimedia message submitted by the mobile terminal of the provider, the MMSC caches the multimedia message, and generates a transaction number for the multimedia message, and generates a message identifier corresponding to the multimedia message according to the transaction number.

In the above method, the message identifier of the SMSC to generate the notification short message is:

After receiving the notification SMS message sent by the MMSC, the SMSC generates a notification message message for the notification message message. The transaction number, according to the transaction number, generates a message identifier corresponding to the notification short message.

In the above method, the correspondence between the message identifier of the MMSC to save the multimedia message and the message identifier of the notification short message is:

The MMSC parses the confirmation message sent by the SMSC and carries the message identifier of the notification short message, and obtains the message identifier of the notification SMS message. The MMSC finds the notification message corresponding to the SMS message according to the transaction number in the message identifier of the notification SMS message. And obtaining the multimedia message corresponding to the notification short message and the message identifier of the multimedia message; the MMSC saves the message identifier of the notification short message and the message identifier of the corresponding multimedia message to the memory table of the corresponding relationship created in advance.

The present invention also provides a system for delivering multimedia messages, including: SMSC, MMSC;

The SMSC is configured to send the delivery status message to the MMSC after sending the notification short message to the mobile terminal;

The MMSC is configured to: when the delivery of the notification short message is successful according to the delivery status code in the delivery status message, find the multimedia message according to the message identifier of the notification short message in the delivery status message, and send the multimedia message to the SMSC.

In the above system,

The MMSC is further configured to: when determining that the notification short message delivery fails according to the delivery status code in the delivery status message, determining, according to the error code in the delivery status message, whether the delivery status of the notification short message is abnormal; when abnormal, suspending the multimedia message The subsequent normal processing flow generates an abnormality log of the destination number; when the abnormality is not abnormal, the resending process of the multimedia message is initiated; when it is in another state, the subsequent normal processing flow of the multimedia message is terminated, and a delivery failure log is generated.

In the above system,

The MMSC is further configured to: generate a message identifier of the multimedia message, and send a notification short message to the SMSC; The SMSC is further configured to: generate a message identifier for notifying the short message, and send the message to the MMSC by using an acknowledgement message;

The MMSC is further configured to save a correspondence between a message identifier of the multimedia message and a message identifier of the notification short message.

The method and system for delivering a multimedia message provided by the present invention, after the SMSC sends a notification short message to the mobile terminal, the delivery status message is sent to the MMSC; when the MMSC determines that the short message delivery is successful according to the delivery status code in the delivery status message And, according to the message identifier of the notification short message in the delivery status message, the multimedia message is found and sent to the SMSC, and the MMSC can know whether the notification short message is actually delivered to the mobile terminal of the receiver, and the MMSC can according to the received delivery status message. Determining whether the delivery status of the notification short message is abnormal. When the MMSC determines that the delivery status of the notification short message is not abnormal and needs to resend the notification short message, the resend process of the multimedia message may be initiated, thereby avoiding that the mobile terminal does not acquire in time. The multimedia message is forwarded to the dream network mailbox or expired, which improves the success rate of the delivery of the multimedia message; when the MMSC determines that the delivery status of the notification short message is abnormal or other indeterminate state, the subsequent normal processing flow of the multimedia message is suspended. , Thus avoiding the number of the mobile terminal is a multimedia message is still delivered normally empty case abnormal numbers or numbers, issued to improve the accuracy of the multimedia message, the multimedia message provided to avoid side brings unnecessary economic losses. DRAWINGS

1 is a schematic structural diagram of a system of a multimedia message service center in the prior art;

2 is a schematic flowchart of sending a multimedia message in the prior art;

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

4 is a schematic flow chart of a method for implementing step 305 in FIG. 3 according to the present invention;

FIG. 5 is a schematic structural diagram of a system for implementing a multimedia cancellation according to the present invention. detailed description

The basic idea of the present invention is: After the short message center (SMSC) sends the notification short message to the mobile terminal, the delivery status message is sent to the multimedia message service center (MMSC); when the MMSC determines the notification according to the delivery status code in the delivery status message When the short message delivery is successful, the multimedia message is found according to the message identifier of the notification short message in the delivery status message, and is sent to the SMSC.

The invention will be further described in detail below with reference to the drawings and specific embodiments.

FIG. 3 is a schematic flowchart of a method for transmitting a multimedia message according to the present invention. As shown in FIG. 3, the method for sending a multimedia message according to the present invention includes the following steps:

Step 301: The MMSC generates a message identifier of the multimedia message, and sends a notification short message to the SMSC.

Specifically, after receiving the multimedia message submitted by the mobile terminal of the provider, the MMSC caches the multimedia message, and generates a transaction number for the multimedia message, and generates a message identifier corresponding to the multimedia message according to the transaction number. MmscMsglD; The message identifier MmscMsglD includes the transaction number, and includes the time of receiving the multimedia message and the serial number of the MMSC itself; meanwhile, the MMSC sends the notification short message corresponding to the multimedia message to the SMSC.

Step 302, the SMSC generates a message identifier for notifying the short message, and sends the message identifier to the MMSC through the confirmation message;

Specifically, after receiving the notification short message sent by the MMSC, the SMSC generates a transaction number for the notification short message, and generates a message identifier SmscMsgID corresponding to the notification short message according to the transaction number, and the message identifier corresponding to the notification short message The SmscMsgID includes the transaction number, and includes the time when the notification short message is received and the sequence number of the SMSC itself. The SMSC sends an acknowledgement message to the MMSC, where the acknowledgement message carries the message identifier SmscMsgID of the generated notification short message. Step 303: The MMSC saves a correspondence between a message identifier of the multimedia message and a message identifier of the notification short message message.

Specifically, in the service processing module of the MMSC, a memory table for storing a correspondence between the message identifier MmscMsgID of the multimedia message and the message identifier SmscMsgID of the notification short message message is created in advance; in an actual application, the memory table of the corresponding relationship may be queried. A more complex data structure implementation, such as a FLASH table, can perform operations such as query, insert, and delete on the corresponding memory table;

After receiving the acknowledgment message sent by the SMSC and carrying the message identifier SmscMsgID of the notification short message, the MMSC parses the acknowledgment message to obtain the message identifier SmscMsgID of the notification short message; and the MMSC notifies the message of the short message according to the received acknowledgment message. Identifying the transaction number in the SmscMsgID, and finding a notification short message corresponding thereto, thereby finding a multimedia message corresponding to the notification short message and a message identifier MmscMsgID of the multimedia message; the MMSC identifies the message identifier SmscMsgID of the notification short message message and the multimedia message corresponding thereto The message identifier MmscMsgID is saved to the memory table of the pre-created correspondence.

Step 304, after sending the notification short message to the mobile terminal, the SMSC sends the delivery status message to the MMSC;

Specifically, after receiving the notification short message sent by the MMSC, the SMSC forwards the notification short message to the mobile terminal of the receiving party; after the SMSC forwards the notification short message, the SMSC sends the delivery status message of the notification short message to the MMSC; The delivery status message includes a message identifier SmscMsgID for notifying the short message, a delivery status code star, and an error code err. The format of the delivery status information may be id: sub: SSS divrd: DDD submit date: YYMMDDhhmm done date : YYMMDDhhmm star : DDDDDDD err : E Text: ......

Step 305: The MMSC determines a subsequent process according to the delivery status message.

4 is a schematic flow chart of the method for implementing step 305 in FIG. 3, as shown in FIG. The method includes:

Step 401: The MMSC determines, according to the delivery status code in the delivery status message, whether the notification short message message is successfully delivered. If yes, step 402 is performed, and if no, step 403 is performed;

Specifically, the MMSC receives the delivery status message sent by the SMSC, and determines whether the notification short message sent by the SMSC is successfully delivered according to the delivery status code star in the delivery status message; the delivery status code star and its corresponding description are as shown in Table 1:

Table 1

When the delivery status code star is DELIVERED or ACCEPTED, indicating that the short message delivery is successful, step 402 is performed; when the delivery status code star is ENROUTE/

When -D, it indicates that the notification SMS message delivery fails, and step 403 is performed.

Step 402: The MMSC finds the multimedia message according to the message identifier of the notification short message in the delivery status message, and sends the multimedia message to the SMSC to end the current processing flow.

Specifically, when the notification message message delivery is successful, the MMSC continues to perform the subsequent normal processing procedure of the multimedia message, that is, the message identifier SmscMsglD of the notification SMS message sent by the SMSC received by the MMSC, and the corresponding multimedia is found in the memory table of the corresponding relationship. The message identifier MmscMsgID of the message is found in the cache according to the message identifier MmscMsgID of the multimedia message, and is sent to the SMSC in the cache. The subsequent processing flow is the same as the prior art, and details are not described herein again. Step 403, the MMSC determines whether the delivery status of the short message is abnormal according to the error code in the delivery status message, if abnormal, step 404 is performed, if not, step 405 is performed, if it is another state, step 406 is performed;

Specifically, when the notification of the short message delivery fails, the MMSC determines, according to the error code err in the received delivery status message, whether the delivery status of the notification short message is abnormal. The error code err and its corresponding description are shown in Table 2. :

Error code error type description The device does not support the mobile terminal where the HLR does not support "mobile termination"

7 short message "; the error code in the test bench is 7, at ETSI

( facilityNotSupp

Defined as 21 in the GSM 0902 protocol

Orted )

The user's current location is not good enough to receive short messages. The user is not in the service area.

Interest rate

8 ( absentSubscribe

The error code in the test bench is 8, in ETSI GSM r)

Defined as 0 in the 0902 protocol

The SM failed to send the message to the service interface. The SMC sends a message to the SM.

10 Send failed; the error code in the test bench is 10, in

( sm-DeliveryFail

Defined as 32 in the ETSI GSM 0902 protocol

Ure ) The message waiting queue is full. Waiting for too many SMCs to send messages to the mobile terminal, causing the MDR queue of the HLR to overflow;

11 (Message Waitin has an error code of 11 and gListFull in ETSI GSM 0902) is defined as 33

System failure The error code in the test station is 12, at ETSI GSM

Defined in the 12 0902 Agreement as 34

( SystemFailure )

When the short message center sends a message to the network side, there is a required word. Data is lost.

13 segments are missing; the error code in the test bench is 13 at ETSI

( dataMissing )

Defined as 35 in the GSM 0902 protocol

MS side error: When sending a message, the mobile terminal has a software problem in receiving the protocol error; for example, after the mobile terminal restarts,

15 ( equipmentProto processing message part of the software is not initialized, it is not possible at this time

colError ) The message is processed frequently; the error code in the test bench is

15 is defined as 32(1) in the ETSI GSM 0902 protocol.

The MS is not equipped. The error code in the test bench is 16, at ETSI GSM.

0 ⁹ 0 ² is defined in the protocol as ³² ( ² )

16 ( equipmentNotS

M-Equipped ) Error code error type description Memory error value in the test station is 17, in ETSI GSM

Defined as 0 (0) in the 0902 protocol

17 ( memoryCapacit

yExceeded )

SC congestion The dispatch center is congested.

18 The error code in the test bench is 18, at ETSI GSM

( sc-Congestion ) 0 ⁹ 0 ² is defined in the protocol as ³² ( ⁴ )

MS non-SC user MS non-scheduling center user.

The error code in the test bench is 19, at ETSI GSM

19 ( subscriberNotS

Defined as 0 (6) in the 0902 protocol

C-Subscriber ) is incorrect 20,

SME address The error code in the test station is at ETSI GSM.

Defined as 0 (5) in the 0902 protocol

20 ( invalidSME-Ad

Dress ) unknown SC error code in the test station is 21 , in ETSI GSM

Defined as 0 (3) in the 0902 protocol

21 (unknownServic

eCentre ) illegal device The mobile terminal's international mobile station identity is illegal;

The error code in the test bench is 22, at ETSI GSM

22 (illegalEquipme

Defined as 0 in the 0902 protocol

Nt )

When the message is sent, the destination mobile terminal is receiving or sending the user busy.

Sending other messages, causing the message to fail to be delivered;

23 ( subscriberBusy

The error code in Taichung is 23 and is defined as 31 in the ETSI GSM 0902 Association ForMT-SMS.

When the message is sent, the destination mobile terminal is shut down, resulting in the cancellation.

24 user shutdown

Failure to send interest Error code error type description

HLR message decoding error The value of one of the data in the HLR message packet exceeds the range specified by the protocol.

Mistake

30 ( RP U DECO

DE DATA HLR

)

The MSC message is decoded incorrectly. The value of one of the data in the MSC message packet exceeds the range specified by the protocol.

Mistake

31 ( RP UNDECO

DE-DATA- MSC

)

INFORM—SC eliminates the value of a certain data in the message packet (INFORM-SC message) sent by the HLR.

32 ( RP UNDECO

DE- INFORM- SC

—HLR ) Not enough SMCs are not obtained enough routing information. Routing information

33 ( RP NOT ENO

UGH- ROUTING

INFO ) The accident from the HLR The value of one of the data in the message packet from the HLR exceeds the range specified by the protocol.

Data

34 ( RP U EXPEC

TED— DATA— VA

LUE HLR ) Error Code Error Type Description Unexpectedly from the MSC The value of one of the data packets from the MSC exceeds the range specified by the protocol.

Data

35 ( RP U EXPEC

TED— DATA— VA

LUE MSC ) Unknown from MSC Unknown error from MSC

Error

36 ( RP U KNOW

N—FAILURE— RE

ASON MSC )

Unknown from HLR Unknown error from HLR

Error

37 ( RP UNKNOW

N—FAILURE— RE

ASON HLR )

After the routing request is sent, the SMC sends a route query request, and the HLR does not answer.

40

HLR no answer After the set message is sent, the HLR does not answer after the SMC sends the set message.

41

HLR no response

MAP Server module MAP protocol version error

45

Version error

HLR version negotiation error HLR version negotiation error

46

Mistake

MSC no response MSC no response

48 ( RP MSC NOA

CK) Error code error type description

HLR no response HLR no response

49 ( RP HLR NOA

CK)

50 GIW module no answer GIW module (signaling gateway) no answer

The MSC rejects the message that the TCAP layer of the MSC is too heavy and returns after the flow control occurs.

51 ( RP MSC REF

USE )

HLR rejection is generally due to the HCAP's TCAP layer load is too large, after the flow control back to the message

52 ( RP HLR REF

USE )

53 GIW module refused GIW module refused

HLR system error is generally due to the overload of the MAP layer of the HLR.

56 Message returned after flow control

( HLR-systemFai

Lur ) :

Generally, the load on the MAP layer of the MSC is too large.

MSC system error message returned after flow control; in addition, if the switch is set

57 (The MSC system is set to authenticate every time a message is sent or received,

MSC

Error ) An authentication is not responding, which causes a return "system error" to the SMC.

61 The MAP Server failed to send a short message due to flow control.

The error is sent by the flow control. The MTI Server fails to send the short message because the flow control point or the signaling point or the signaling connection control point cannot transmit the message.

63 messages.

Make the transfer point impossible to pass

Send the message. The interface is not sent. The interface has no permission to send messages.

64

Permission Error code error type description After the message is delivered, the GIW module does not return to the SMSC.

65 GIW no response

Send success or failure information

Caused by temporary interface error (logged out or not logged in)

66 interface temporary error

Failure to send interest

67 invalid interface invalid interface

After the SMC sends a short message, the interface does not send a success or failure message to the SMSC.

After giving the business module, the industry

68

Service module timed out

Returning the answer Because the dispatch center and the dispatch center are disconnected from the L2cachedaemon module, the message to enter the secondary cache database is deleted.

L2cachedaemon

Module disconnection leads to

71

Into the second level cache data

The short message of the library is deleted

Except

The SMC sends a short message. When the SMC sends a message, the interface buffer is full.

77

When the interface buffer is full

The short message exceeds the maximum number of submissions of the calling party. The message is deleted after the message fails.

The maximum number of submissions for the party,

79

The short message is lost

After defeat, deleted

192 SMC busy SMC busy No SMC specified No SMC specified (signed).

193

(signing)

194 SMC system error SMC system error Extended short message entity Extended message entity address is invalid

195

Invalid address Error code error type description Short message entity banned message entity is forbidden to use

196

Use

The storage space in the SIM is short. The space for storing messages in the SIM is full.

208

Interest area

The SIM does not store the ability to store messages in the SIM.

209

Short message capability

210 MS error MS error Extended short message entity Extended message entity memory overflow

211

Memory overflow The caller of the forward message The preamble message is authenticated at the calling home short message center address.

231 Ownership Short Message Center failed

Authentication failure Undetermined error original Undetermined error cause

255

Cause

Table 2

When the error code err is 1/2/3/4/5/6/7/19/21/22, it indicates that the delivery status is abnormal, and step 404 is performed; when the error code err is 8/11/17/18/23 /24 hours, indicating that the delivery status is not abnormal, but the delivery fails and needs to be re-delivered, step 405 is performed; the other error code err indicates other status, the delivery fails and no re-delivery is required, and step 406 is performed.

Step 404: The MMSC suspends the subsequent normal processing procedure of the multimedia message, generates a destination number abnormality log, and ends the current processing flow. Specifically, because the number of the mobile terminal of the receiving party is abnormal, the MMSC suspends the subsequent normal processing flow of the multimedia message, and generates the purpose. The number exception log, the CDR record of the provider is not generated at this time. Step 405: The MMSC initiates a resend process of the multimedia message, and ends the current process.

Specifically, because the delivery fails and needs to be re-delivered, the MMSC initiates a resend process of the multimedia message, resends the notification short message to the SMSC, and performs step 304 until the notification short message is successfully sent to the recipient's mobile terminal, or resends. The number of times reaches the preset retransmission threshold; if the number of retransmissions reaches the preset retransmission threshold, the MMSC associates the message identifier MmscMsgID of the multimedia message with the message identifier SmscMsgID of the notification SMS message. The relationship is removed from the memory table of the corresponding relationship.

Step 406: The MMSC terminates the subsequent normal processing procedure of the multimedia message, and generates a delivery failure log.

Specifically, because the delivery fails and the re-delivery is not required for other reasons, the MMSC suspends the subsequent normal processing flow of the multimedia message, generates a delivery failure log, and does not generate a bill record of the provider.

In order to achieve the above method, the present invention further provides a system for transmitting a multimedia message, and FIG. 5 is a schematic structural diagram of a system for transmitting a multimedia message according to the present invention. As shown in FIG. 5, the system includes: SMSC51 and MMSC52;

SMSC51, configured to send the notification message to the mobile terminal, and send the delivery status message to the MMSC 52;

The MMSC 52 is configured to: when the notification short message delivery is successful according to the delivery status code in the delivery status message, find the multimedia message according to the message identifier of the notification short message in the delivery status message, and send the message to the SMSC 51.

The MMSC 52 is further configured to: when determining that the notification short message delivery fails according to the delivery status code in the delivery status message, determining, according to the error code in the delivery status message, whether the delivery status of the notification short message is abnormal; when abnormal, suspending the multimedia message The subsequent normal processing flow generates an abnormal log of the destination number; when not abnormal, initiates a resend process of the multimedia message; In the state, the subsequent normal processing flow of the multimedia message is terminated, and a delivery failure log is generated.

The MMSC 52 is further configured to: generate a message identifier of the multimedia message, and send a notification short message to the SMSC 51;

The SMSC 51 is further configured to: generate a message identifier for notifying the short message, and send the message to the MMSC 52 by using the confirmation message;

The MMSC 52 is further configured to save a correspondence between a message identifier of the multimedia message and a message identifier of the notification short message.

The process of resending the multimedia message initiated by the MMSC 52 is:

The MMSC 52 initiates a retransmission process of the multimedia message, and resends the notification SMS message to the SMSC until the notification SMS message is successfully sent to the recipient's mobile terminal, or the number of retransmissions reaches a preset retransmission threshold.

The message identifier of the MMSC 52 generating the multimedia message is:

After receiving the multimedia message submitted by the mobile terminal of the provider, the MMSC 52 caches the multimedia message, and generates a transaction number for the multimedia message, and generates a message identifier corresponding to the multimedia message according to the transaction number.

The message identifier of the SMSC 51 generating the notification short message is:

After receiving the notification short message sent by the MMSC 52, the SMSC 51 generates a transaction number for the notification short message, and generates a message identifier corresponding to the notification short message according to the transaction number.

The correspondence between the message identifier of the MMSC 52 storing the multimedia message and the message identifier of the notification SMS message is:

The MMSC 52 parses the confirmation message of the message identifier of the SMS message sent by the SMSC 51, and obtains the message identifier of the notification message message. The MMSC 52 finds the notification message corresponding to the SMS message according to the transaction number in the message identifier of the notification message message. And finding a multimedia message corresponding to the notification short message and a message identifier of the multimedia message; the MMSC 52 saves the message identifier of the notification short message and the message identifier of the corresponding multimedia message to the pre First create the corresponding relationship in the memory table.

The above description is only for the preferred embodiment of the present invention, and is not intended to limit the scope of the present invention. Any modifications, equivalent substitutions and improvements made within the spirit and principles of the present invention should be included. Within the scope of protection of the present invention.

Claims

Claim

A method for delivering a multimedia message, the method comprising: the short message center (SMSC) transmitting the notification short message to the mobile terminal, and transmitting the delivery status message to the multimedia message service center (MMSC);

When the MMSC determines that the notification short message delivery is successful according to the delivery status code in the delivery status message, the multimedia message is found according to the message identifier of the notification short message in the delivery status message, and is sent to the SMSC.

2. The method according to claim 1, wherein the method further comprises: when the MMSC determines that the notification short message delivery fails according to the delivery status code in the delivery status message, determining the notification short message according to the error code in the delivery status message. Whether the delivery status of the message is abnormal; if abnormal, the MMSC suspends the subsequent normal processing flow of the multimedia message to generate an abnormality log of the destination number; if not abnormal, the MMSC initiates a retransmission process of the multimedia message; if it is in another state, the MMSC terminates the multimedia The subsequent normal processing flow of the message generates a delivery failure log.

The method according to claim 1 or 2, wherein, after the SMSC sends the notification short message to the mobile terminal, and sends the delivery status message to the MMSC, the method further includes:

The method according to claim 2, wherein the resending process of the MMSC to initiate the multimedia message is:

The MMSC initiates a resend process of the multimedia message, and resends the notification short message to the SMSC until the notification short message is successfully sent to the recipient's mobile terminal, or resent The number of times the preset resend threshold has been reached.

The method according to claim 3, wherein the message identifier of the MMSC to generate the multimedia message is:

After receiving the multimedia message submitted by the mobile terminal of the provider, the MMSC caches the multimedia message, generates a transaction number for the multimedia message, and generates a message identifier corresponding to the multimedia message according to the transaction number.

The method according to claim 3, wherein the SMSC generates a message identifier for notifying the short message:

After receiving the notification short message sent by the MMSC, the SMSC generates a transaction number for the notification short message, and generates a message identifier corresponding to the notification short message according to the transaction number.

The method according to claim 3, wherein the correspondence between the message identifier of the MMSC holding the multimedia message and the message identifier of the notification short message is:

8. A system for delivering a multimedia message, the system comprising: an SMSC, an MMSC;

The MMSC is configured to: when the notification short message delivery is successful according to the delivery status code in the delivery status message, find the multimedia message according to the message identifier of the notification short message in the delivery status message, and send the multimedia message to the SMSC.

9. The system of claim 8 wherein:

10. A system according to claim 8 or claim 9 wherein:

The MMSC is further configured to: generate a message identifier of the multimedia message, and send a notification message message to the SMSC;

The SMSC is further configured to: generate a message identifier for notifying the short message, and send the message to the MMSC through the confirmation message;