CN100512521C - Apparatus and method for multimedia message processing - Google Patents

Abstract

The invention discloses a multimedia message processing device and method. The multimedia message processing device is applied to a multimedia message processing system. The device is located between a service provider server (SP) and a multimedia message service center (MMSC). Buffer the multimedia messages submitted by the SP, and forward the buffered multimedia messages to the MMSC. A method for processing a multimedia message, the method includes: buffering the multimedia message submitted by the SP into a storage device, and forwarding the stored multimedia message according to the capability received by the MMSC. The device and method solve the problem that it is impossible to ensure that all the messages submitted by the SP application are successfully received by the MMSC when the amount of messages submitted by the SP application is large or when there is a surge of messages submitted by the SP application.

Description

Device and method for multimedia message processing

technical field

The invention relates to a processing technology for multimedia messages, in particular to a device and method for processing multimedia messages.

Background technique

With the further development of Short Message Service (SMS) and Enhanced Message Service (EMS), Multimedia Message Service (MMS) is applied to the communication field. MMS provides a complete end-to-end solution for personal multimedia mobile communication services. In terms of communication, multimedia messages include images, audio, video, and data; in terms of functions, multimedia message services include terminal-to-terminal, terminal-to-application, and application-to-terminal multimedia message communication. Therefore, MMS not only realizes the information transfer between terminals, between terminals and applications, but also realizes the diversity of content, including various combinations of pictures, voices, images, data and texts. As an open media access platform, MMS can generate more colorful content service applications under the interaction between mobile users and Internet content providers.

The general architecture of the multimedia message service is shown in Figure 1, and its specific description is as follows:

MMS can be implemented in cellular networks, the Internet and fixed networks, and it can also be implemented when communicating between different types of network connections or different network connections based on the Internet Protocol and its related messages. agreement provided. Terminals with MMS must communicate with Multimedia Message Service Center (MMSE). MMSE can cover cellular network, Internet and fixed network. MMSE provides all necessary business elements. For example, the functions of transmitting MMS, storing MMS, and notifying terminals to send and receive MMS can be implemented in one network type or in one network, or distributed in several networks or in different network types.

MMS can also be implemented on second generation (2G) and third generation (3G) networks.

Existing service provider (SP) applies to the flow process of point-to-point sending and receiving message as shown in Figure 2, and its concrete description is: the system that SP applies to point sending and receiving message is by a plurality of SP servers, namely SP application, Internet (internet), Composed of firewall and MMSC, the message submitted by SP is directly sent to the multimedia messaging system through the internet and the firewall, regardless of whether the MMSC system is in a busy state.

The SP application-to-point sending and receiving message provided in the prior art has the following disadvantages: 1. When the SP application-to-point traffic is relatively large, the MMSC is busy processing, and the processing of the message submitted by the SP application is slow, which will cause the MMSC to partially SP The message submitted by the application fails to be received. Second, when the SP sends messages intensively within the same period of time, it will cause a surge. Since the peak speed at which the MMSC can process messages is limited, the amount of messages sent by the SP application is within a certain range. When the time period increases sharply, the MMSC will fail to receive the messages submitted by some SP applications.

Therefore, how to ensure that all messages submitted by SP applications are successfully received by MMSC, especially when the amount of messages submitted by SP applications is large or when there is a surge of messages submitted by SP applications, how to ensure that all messages submitted by SP applications are successfully received by MMSC , is an urgent problem to be solved.

Contents of the invention

In view of this, an aspect of the present invention provides a device for processing multimedia messages, which is used for buffering messages submitted by SP applications and forwarding them to MMSC.

Another aspect of the present invention provides a method for processing multimedia messages, which solves the problem that when the amount of messages submitted by SP applications is large or when there is a surge of messages submitted by SP applications, it is impossible to ensure that all messages submitted by SP applications are successfully received by MMSC The problem.

According to above-mentioned purpose, technical scheme of the present invention is achieved like this:

A device for multimedia message processing, applied to a multimedia message processing system, the device is located between a service provider server (SP) and a multimedia message service center (MMSC), at least including:

The load negotiator module receives the load information from the MMSC, and sends an accommodation load signal to the SP-side message receiver module and a load speed signal to the MMSC-side message transmitter module;

The SP end message receiver module receives the multimedia message submitted by the SP, and sends the multimedia message submitted by the SP to the multimedia message buffer pool module under the control of the accommodation load signal;

The multimedia message buffer pool module caches the multimedia message sent by the message receiver module at the SP end;

The MMSC end message sender module sends the multimedia message in the multimedia message buffer pool module to the MMSC under the control of the load speed signal;

The delivery report sender module receives the message of the permanent failure of sending the multimedia message from the message sender module of the MMSC, and sends the message of the permanent failure of sending the multimedia message to the SP service provider.

The message redirector module receives the multimedia message from the SP-side message receiver module and redirects it to the MMSC.

The device is a module inside the MMSC.

There is also a firewall between the SP and the device.

A method for multimedia message processing, the method comprising:

A. Judging whether the current state of the MMSC to accommodate the load is normal or overloaded, if the state of the MMSC to accommodate the load is normal, turn to step B, otherwise, turn to step C;

B. Redirect after receiving the multimedia message to the storage device and send it to the MMSC, and end the method;

C, cache the received multimedia message in the storage device, judge whether the speed at which the current MMSC receives the multimedia message is 0, if yes, stop sending the multimedia message to the MMSC, otherwise, send the multimedia message from the storage device to the MMSC according to the current speed at which the MMSC receives the multimedia message Send buffered multimedia messages sequentially.

The redirecting sending of multimedia messages to MMSC in Step B further includes: collecting the multimedia messages sent by the SP, and then sending them to the MMSC.

The multimedia message is sent to the MM7 port of the MMSC.

Redirecting the received multimedia message to the storage device and sending it to the MMSC further includes: the storage device sends an MM7 port submission request message to the MMSC, and the MMSC receives the multimedia message after receiving the request message and sends an MM7 port submission response message.

The buffering of the received multimedia message further includes: the SP sends a storage request message to the storage device, and the storage device buffers the multimedia message after receiving the request message, and if the storage is successful, sends a storage success response message to the SP, and if the storage is unsuccessful, sends Store failure response message to SP.

The multimedia message sent by the C buffer further includes: the storage device sends the MM7 port submission request message to the MMSC, and the MMSC receives the multimedia message after receiving the request message, and if the reception is successful, sends the request message to delete the multimedia message to the storage device, and deletes the multimedia message. Multimedia message; if the temporary reception is unsuccessful, send the request message to move the multimedia message to the top of the storage device pool to the storage device, and move the multimedia message to the top of the storage device pool; if the permanent reception is unsuccessful, send the request message to delete the multimedia message to the storage device, delete the multimedia message, and send a delivery report to the SP.

The C sending the buffered multimedia messages in order further includes: sending the buffered multimedia messages in a first-in-first-out order.

The present invention provides an MM Pool device between the firewall and the MMSC, the device receives and stores the multimedia message sent by the SP application, and decides whether to send the multimedia message and at what speed according to the current running state of the MMSC : When the current running state of MMSC is idle, direct redirection to send multimedia messages to MMSC; when the current running state of MMSC is busy, send multimedia messages according to the acceptable sending rate of MMSC; when the current running state of MMSC is busy and reaches the limit, stop sending multimedia messages Messages, the equipment and method provided by the present invention fundamentally solve the problem that the messages submitted by SP applications cannot be guaranteed to be successfully received by MMSC when the amount of messages submitted by SP applications is large or when there is a surge of messages submitted by SP applications.

Description of drawings

Figure 1 is a general architecture diagram of a multimedia messaging service.

FIG. 2 is a structural diagram of an existing service provider (SP) application to send and receive messages from a point.

FIG. 3 is a structural diagram of the SP application to send and receive messages to peers according to the present invention.

Figure 4a is a diagram of an embodiment of the MM PooL functional module.

Fig. 4b is a diagram of another embodiment of the MM PooL functional module.

Fig. 5 is a flow chart of the present invention for implementing the SP application to send and receive messages.

FIG. 6 is a flow chart of sending multimedia messages with low traffic in the present invention.

Fig. 7 is a flow chart of the present invention for sending multimedia messages with high traffic.

Fig. 8 is the flow chart of the MM Pool of the present invention sending a message to the MMSC.

Fig. 9 is the flow chart when the MM Pool of the present invention sends a message to the MMSC when a permanent error occurs.

Detailed ways

In order to make the object, technical solution and advantages of the present invention clearer, the present invention will be further described in detail by citing the following embodiments and referring to the accompanying drawings.

The present invention adds a buffer processing device (MM PooL) between the firewall and the MMSC. The MM PooL is used for buffering excessive SP application multimedia messages. It can be a separate device or can be integrated in the MMSC as an internal MMSC functional module.

When multimedia messages are to be sent, all multimedia messages sent from the SP application are first sent to the MM Pool through the Internet and the firewall. If the amount of multimedia messages currently received is low and has not reached the limit of the MMSC's receiving capacity, the multimedia message will be redirected directly to the MMSC; if the amount of currently received multimedia messages has reached the limit of the MMSC's receiving capacity, The multimedia message buffering mechanism will be started, and subsequent multimedia messages will be placed in the multimedia message buffer pool, and at the same time, the multimedia messages that first enter the buffer pool will be ready to be sent to the MMSC. Once the load of the MMSC decreases, the messages in the buffer pool will be sent to the MMSC. The sending speed is limited to the maximum ability of the MMSC to receive messages at present, and it can change dynamically with the load of the MMSC currently processing messages.

As shown in Fig. 3, Fig. 3 is the system diagram of point-to-point message sending and receiving for SP application after applying the present invention, and its specific description is: this system comprises a plurality of SP, Internet (internet), firewall, MM PooL and MMSC, and SP submits After the message passes through the Internet (internet) and the firewall, it is forwarded to the multimedia message system through MM PooL.

The internal structure of the MM PooL system is shown in Figure 4a, and Figure 4a is an embodiment diagram of the MM PooL functional module, and its specific description is: the MM PooL system consists of an SP-side message receiver (SP-Receiver) module, an MMSC-side message It consists of a sender (MMSC-Sender) module, a multimedia message buffer pool (Pool) module, a load negotiator (Load-Negotiater) module and a delivery report sender (Reporter) module.

Fig. 4 b is another embodiment diagram of MM PooL functional module, in this embodiment, there are more message redirector (Redirector) modules than the MM PooL system internal structure described in Fig. 4a, and all the other modules are identical with Fig. 4a.

The working principle is described below with the internal structure of the MM PooL system described in Figure 4b.

SP end message receiver (SP_Receiver) module, this module is used for receiving the multimedia message from SP:

When the SP sends a multimedia message to the MMSC, the message will first be sent to the SP-side message receiver (SP_Receiver) module. The SP-side message receiver (SP_Receiver) module determines the follow-up processing of the message according to the current load of the MMSC.

Regarding the load situation of the current MMSC, the SP-side message receiver (SP_Receiver) module can be obtained from the load negotiator (Load_Negotiater) module inside the MM Pool. The load information here can be expressed as a capacity load signal (Recipient_Capability_Status), which takes two status values of "Normal" and "Overload".

If MMSC has not yet reached the limit of receiving messages and is in a "normal" state, and there is no message in the multimedia message buffer pool (Pool), the SP end message receiver (SP_Receiver) module will receive the multimedia message through the SP end message receiver ( Redirector) module is directly redirected to the MM7 interface of MMSC; If MMSC reaches the limit of receiving messages, when it is in an "overload" state or there are messages in the multimedia message buffer pool (Pool), the SP end message receiver (SP_Receiver) module will receive The received multimedia message is sent to the pool top of the Pool for temporary storage, and then the message receiver (SP_Receiver) module sends a successful reception response to the SP's multimedia service message server, indicating that the message is "received to be processed".

MMSC end message sender (MMSC_Sender) module, this module is used for sending the multimedia message cached in the Pool to MMSC:

As long as the MMSC-side message sender (MMSC_Sender) module finds that there are multimedia messages accumulated in the multimedia message buffer pool (Pool), it decides at what speed to send multimedia messages to the MMSC according to the current load of the MMSC.

Regarding the current MMSC load situation, the MMSC-side message sender (MMSC_Sender) module can be obtained from the load negotiator (Load_Negotiater) module inside the MM Pool. The load information here can be expressed as a Recipient_Capability_Speed signal at which the MMSC can still receive the SP multimedia message currently.

If accommodate the load speed (Recipient_Capability_Speed) signal value "not zero", then the MMSC end message sender (MMSC_Sender) module refers to the MMSC receiving speed parameter that accommodates the load speed (Recipient_Capability_Speed) signal to send to the MMSC from the multimedia message buffer pool ( Pool) extracts multimedia messages from the bottom of the Pool; in extreme cases, the value of the Recipient_Capability_Speed signal is "zero", and the MMSC-side message sender (MMSC_Sender) module stops sending multimedia messages to the MMSC.

Multimedia message buffer pool (Pool) module, this module is used for storing multimedia message:

The multimedia message buffer pool (Pool) module receives and stores the message submitted by the SP end message receiver (SP_Receiver) module, and can store all information of the source message without omission or pruning, so that the MMSC end message sender (MMSC_Sender) module sends The MMSC sends a multimedia message that is completely consistent with the content of the original message.

Regarding the storage capacity of the multimedia message buffer pool (Pool) module and the speed of storing/retrieving messages: the storage capacity depends on the configuration of physical equipment and operational requirements; the storage speed is based on the maximum message receiver (SP_Receiver) module at the SP end The speed is based on; the reading speed is based on the maximum speed at which the MMSC can receive messages.

The message redirector (Redirector) module, which is used to directly redirect the message to the MM7 interface of the MMSC, "redirect" means that the message redirector (Redirector) module completes the collection of the original message information, and then sends it directly to MMSC.

Load negotiator (Load_Negotiater) module, which receives load information from MMSC and converts it into an internal representation for use by the SP-side message receiver (SP_Receiver) module and message redirector (Load_Negotiater) module inside the MM Pool .

MMSC and the message redirector (Load_Negotiater) module establish a set of interaction mechanism, and the MMSC periodically sends the MMSC load parameters to the message redirector (Load_Negotiater) module, and the sending time interval is preferably within 1 second.

The message redirector (Load_Negotiater) module provides the load parameter (Recipient_Capability_Status) regularly sent by the MMSC to the SP-side message receiver (SP_Receiver) module for access by the SP-side message receiver (SP_Receiver) module. When the load parameter sent by the MMSC indicates that the MMSC can still receive messages, this parameter is set to "normal"; when the load parameter sent by the MMSC indicates that the MMSC cannot receive messages, this parameter is set to "overload".

The message redirector (Load_Negotiater) module provides the MMSC-side message sender (MMSC_Sender) module with the load parameters sent regularly by the MMSC: accommodate the load speed (Recipient_Capability_Speed) signal, that is, the message redirector (Load_Negotiater) module sends the load sent by the MMSC The parameter is converted into the speed at which the MMSC can still receive SP messages currently, and the speed at which the MMSC can currently receive SP messages is used as the value of the load capacity (Recipient_Capability_Speed).

Delivery report sender (Reporter) module, when MM Pool sends the multimedia message MMSC in the buffer pool to permanent failure, the delivery report of message delivery failure is generated by this module to the message source sender SP.

When working with the internal structure of the MM PooL system described in Figure 4a, because this MM PooL system lacks the message redirector (Load_Negotiater) module, all multimedia messages submitted by the SP are all stored in the multimedia message buffer pool (Pool) module Module and then forwarded to MMSC.

It can be seen that the equipment provided by the present invention has the following functions:

Capable of receiving multimedia messages from SP applications;

Ability to send multimedia messages to the multimedia message center;

Able to redirect the multimedia message sent by the SP application to the multimedia message center;

Ability to issue a response (success or failure response) to the SP application receiving the message;

Ability to send a delivery report message to the SP application;

Ability to temporarily store multimedia messages;

The load information of the current multimedia message center can be obtained.

The present invention not only provides MM Pool equipment, but also provides a method for MM Pool equipment to process multimedia messages, which is specifically described as follows.

As shown in Figure 5, Figure 5 is a flow chart of the present invention realizing that the SP application sends and receives messages at a point:

Step 500, judging whether the load state of the current MMSC is normal or overloaded, if the load state of the current MMSC is normal, then proceed to step 501, if the load state of the current MMSC is overloaded, then proceed to step 502;

Step 501 realizes that the received multimedia message is directly redirected and sent to MMSC;

Step 502,503, the multimedia message cache that sends is come over, judges whether the speed that current MMSC receives multimedia message is 0, if yes, stops sending multimedia message to MMSC, otherwise, proceeds to step 504;

Step 504: Receive the multimedia messages in the first-in-first-out order according to the current speed at which the MMSC receives the multimedia messages.

When the SP service message was in low message flow, as shown in Figure 6, Figure 6 is a successful flow chart of low flow sending multimedia message of the present invention:

Steps 600, 601, 602, SP sends MM7 port submission request message (MM7_Submit.Req) to MMSC through SP_Receiver and Redirector;

Steps 603, 604, and 605, after the MMSC receives the MM7_Submit.Req message, it sends a multimedia message and sends the MM7 port submission response message (MM7_Submit.Res) to the SP through SP_Receiver and Redirector. At this time, the MM Pool device just starts transparently transmitting the multimedia The role of the message.

When the SP service message is in the high message flow, as shown in Figure 7, Figure 7 is a flow chart of the high flow sending multimedia message of the present invention:

Step 700, SP sends MM7 port submission request message (MM7_Submit.Req) to SP_Receiver;

Step 701, because the SP service message is in high message traffic, so SP_Receiver converts MM7_Submit.Req into a storage request message (Store.Req) and sends it to Pool;

Step 702, when Pool receives the Store.Req message, store the message and send a storage response message (Store.Res) to Pool;

Step 703, after the Pool receives the Store.Res message, it converts the Store.Res message into an MM7 port submission response message (MM7_Submit.Res) and sends it to the SP. The MM7_Submit.Res contains the information or multimedia messages stored successfully in the multimedia Store failed information.

When MM Pool sends message to MMSC, as shown in Figure 8, Fig. 8 is the flow chart of MM Pool of the present invention sends message to MMSC:

Step 800, MMSC_Sender sends an acquisition request (Pick_Up.Req) message to Pool;

Step 801, after the Pool receives the Pick_Up.Req message, it returns to the MMSC_Sender to send an acquisition response (Pick_Up.Req) message;

Steps 802 and 803, MMSC_Sende sends MM7_Submit.Req message to MMSC, MMSC receives the multimedia message after receiving the MM7_Submit.Req message, and sends MM7_Submit.Res message to MMSC_Sender, the message contains the message of successful reception or temporary error message ;

Steps 804 and 805, when the MM7_Submit.Res contains a successful message, the MMSC_Sender sends a delete request (Delete.Req) message to the Pool, and the Pool deletes the multimedia message after receiving it and sends a delete response (Delete.Res) message to the MMSC_Sender ; When the MM7_Submit.Res contains a message receiving a temporary error, the MMSC_Sender sends a Move_To_Tail.Req message to the Pool. After receiving it, the Pool moves the multimedia message to the top of the pool and sends a move To the pool top response (Move_To_Tail.Res) message to MMSC_Sender.

When the MM Pool sends a message to the MMSC, when a permanent error occurs in the submitted message, as shown in Figure 9, Figure 9 is a flow chart when the MM Pool of the present invention sends a message to the MMSC and a permanent error occurs:

Step 900, MMSC_Sender sends a message to Pool;

Step 901, after the Pool receives the Pick_Up.Req message, it returns to the MMSC_Sender to send an acquisition response (Pick_Up.Req) message;

Step 902, 903, MMSC_Sende sends MM7_Submit.Req message to MMSC, MMSC receives the multimedia message after receiving this MM7_Submit.Req message, and sends MM7_Submit.Res message to MMSC_Sender, and this message contains the message of receiving permanent error;

Steps 904, 905, and 906, MMSC_Sende sends a report request (Report.Req) message to Reporter, and the Report.Req message includes the submitted multimedia message as a permanent error, and Reporter sends a report response (Report.Res) message back to MMSC_Sende , and send the MM7 port delivery report request (MM7_Deliverr_Report.Req) to the SP, and the MM7_Deliverr_Report.Req includes a refusal to receive the multimedia message;

In steps 907 and 908, when MMSC_Sende and Reporter exchange messages, MMSC_Sender sends a delete request (Delete.Req) message to Pool, and after receiving it, Pool deletes the multimedia message and sends a delete response (Delete.Res) message to MMSC_Sender.

The present invention not only solves the problem that when the service volume of the SP application to the point is relatively large, the processing of the multimedia message system is busy, and the processing of the message submitted by the SP application is slow, which will cause the multimedia message system to fail to receive the message submitted by some SP applications. Ensure that when the SP application-to-point service volume is relatively large, the multimedia message system can receive the SP application submission request message, preventing the SP application submission message from being lost and receiving failure; and solving the problem of SP application-to-point service. The surge problem has achieved very good results.

The above descriptions are only preferred embodiments of the present invention, and are not intended to limit the present invention. Any modifications, equivalent replacements and improvements made within the spirit and principles of the present invention should be included in the scope of the present invention. within the scope of protection.

Claims (11)

1. A device for multimedia message processing, applied to a multimedia message processing system, characterized in that the device is located between a service provider server (SP) and a multimedia message service center (MMSC), and at least includes: The load negotiator module receives the load information from the MMSC, and sends an accommodation load signal to the SP-side message receiver module and a load speed signal to the MMSC-side message transmitter module; The SP end message receiver module receives the multimedia message submitted by the SP, and sends the multimedia message submitted by the SP to the multimedia message buffer pool module under the control of the accommodation load signal; The multimedia message buffer pool module caches the multimedia message sent by the message receiver module at the SP end; The MMSC end message sender module sends the multimedia message in the multimedia message buffer pool module to the MMSC under the control of the load speed signal; The delivery report sender module receives the message of the permanent failure of sending the multimedia message from the message sender module of the MMSC, and sends the message of the permanent failure of sending the multimedia message to the SP service provider. 2. The device according to claim 1, further comprising: a message redirector module, which receives the multimedia message from the SP-side message receiver module and redirects it to the MMSC. 3. The device according to claim 1, characterized in that the device is a module inside the MMSC. 4. The device according to claim 1, characterized in that there is a firewall between the SP and the device. 5. A method for multimedia message processing, characterized in that the method comprises: A. Judging whether the current state of the MMSC to accommodate the load is normal or overloaded, if the state of the MMSC to accommodate the load is normal, turn to step B, otherwise, turn to step C; B. Redirect after receiving the multimedia message to the storage device and send it to the MMSC, and end the method; C, cache the received multimedia message in the storage device, judge whether the speed at which the current MMSC receives the multimedia message is 0, if yes, stop sending the multimedia message to the MMSC, otherwise, send the multimedia message from the storage device to the MMSC according to the current speed at which the MMSC receives the multimedia message Send buffered multimedia messages sequentially. 6. The method according to claim 5, characterized in that the redirecting sending of the multimedia message to the MMSC in step B further comprises: collecting the multimedia message sent by the SP, and then sending it to the MMSC. 7. The method according to claim 5, wherein the multimedia message is sent to the MM7 port of the MMSC. 8. The method according to claim 5, wherein the redirection of the received multimedia message to the storage device and sending it to the MMSC further comprises: the storage device sends an MM7 port submission request message to the MMSC, and the MMSC receives the request message Then receive the multimedia message and send out the MM7 port submission response message. 9. The method according to claim 5, wherein said caching the received multimedia message further comprises: the SP sends a storage request message to the storage device, and the storage device caches the multimedia message after receiving the request message, and if the storage is successful , sending a storage success response message to the SP, and if the storage is unsuccessful, sending a storage failure response message to the SP. 10. The method according to claim 5, wherein the C sending the buffered multimedia message further comprises: the storage device sends an MM7 port submission request message to the MMSC, and the MMSC receives the multimedia message after receiving the request message, and if it receives If successful, send a request message to delete the multimedia message to the storage device, and delete the multimedia message; if the temporary reception is unsuccessful, send a request message to move the multimedia message to the top of the storage device pool to the storage device, and move the multimedia message to the storage device pool IM; if the permanent reception is unsuccessful, send a request message to delete the multimedia message to the storage device, delete the multimedia message, and send a delivery report to the SP. 11. The method according to claim 5, wherein said C sending the buffered multimedia messages in order further comprises: sending the buffered multimedia messages in a first-in-first-out order.

Images