RU2359428C2 - Method for transfer of mm4 interface messages in system of multimedia messages - Google Patents

Abstract

FIELD: physics, communication.

SUBSTANCE: invention is related to communication engineering. Method is suggested to transfer MM4 interface messages in system of multimedia messages, comprising the following steps: connections of Simple Mail Transfer Protocol (SMTP) are detected, which are controlled by initial Multimedia Message Service Center (MMSC), to end centres of MMSC; MM4 interface messages are distributed, which are created by initial centre of MMSC, by categories in compliance with addresses of end centres MMSC, to which it is required to sent mentioned messages of MM4 interface; and MM4 interface messages distributed in categories are sent to corresponding end centres of MMSC via SMTP connections separated for corresponding end centres of MMSC.

EFFECT: elimination of problem of frequent switchover of connections between different end centers of MMSC with the possibility to use resources in optimal manner.

12 cl, 4 dwg

Description

The present invention relates to multimedia message processing technologies and, in particular, to a method for transmitting MM4 interface messages in a multimedia message system.

BACKGROUND OF THE INVENTION

The Multimedia Messaging Service (MMS) is the further development of the Short Message Service (SMS) and the Advanced Message Service (EMS); it provides a comprehensive system solution for personal mobile multimedia services. MMS service not only supports the transfer of information between different terminals and between terminals and applications, but also provides the ability to send messages with the content of various types. Moreover, the information transmitted via MMS may contain graphic information, voice information, images, data, text and any combination of the above types. Being an open platform for accessing multimedia data, MMS, thanks to the interaction between mobile service subscribers and Internet content providers, brings a wide variety to content service applications.

Figure 1 shows the architecture of a multimedia messaging system, which contains: Agent 101 MMS user, network, Center 103 Multimedia Messaging Services (CMS (MMSC), database 104 MMS users and applications 105 Additional Paid Services (VAS) Multimedia Messaging Services ( MMS). The network may be a 2G mobile network 1021, a 3G mobile network 1022, or an Internet / IP network 1023.

CMS (MMSC) 103, which contains the MMS repeater 1031 and the MMS server 1032, is designed to perform protocol conversion, content adaptation, storage and schedule management of multimedia messages, so that it enables the transmission of multimedia messages between different multimedia devices.

With the development of MMS, the number of its subscribers is constantly increasing. As a rule, a telecom operator, in order to ensure the implementation of MMS services for subscribers, creates several MMSC centers in the multimedia messaging system, while each of the MMSC centers serves certain subscribers. Figure 2 shows the architecture of a multimedia messaging system, in which there are many connected to each other CMS (MMSC); moreover, the system comprises a CMS center (MMSC) 201, a Wireless Device Protocol (WAP) gateway 202, a wireless network 203, a user terminal 204, an IP network 205, an email server 206, and a Service Provider / Content Provider (SP / CP) 207.

As illustrated in FIG. 2, the MMSC centers communicate with each other via the IP network 205. The relevant protocols define that the communication interface between the MMSC centers (MMSC) is an MM4 interface that uses the Simple Protocol as the carrier protocol Mail Transfer (SMTP). Therefore, hereinafter, messages transmitted between the CMS (MMSC) centers will be called MM4 interface messages.

In practice, telecom operators can set the number of CMS centers (MMSC) depending on the number of subscribers. If there is a sufficiently large number of CMS (MMSC) centers, since different CMS (MMSC) centers process a different number of messages, the total number of messages transmitted to different CMS (MMSC) centers must be balanced in the MM4 interface, which will guarantee the sending of all multimedia messaging as soon as possible.

According to the state of the art, two methods can be used to transmit messages of the MM4 interface. In the description below, if the message of the MM4 interface is transmitted from one TsUMS center (MMSC) to another TsUMS center (MMSC), then the TsUMS center (MMSC), which transmits the message of the MM4 interface, is called the original TsUMS center (MMSC), and the TsUMS center ( MMSC), which receives an MM4 interface message, is designated as the MMSC end center. The source center TsUMS (MMSC) can send various messages interface MM4 to the end center TsUMS (MMSC) "i", where "i" is an arbitrary integer between 1 and N, i.e. the source center of the MSC (MMSC) may be associated with the "N" end centers of the MSC (MMSC).

According to the first method known from the prior art, if the source CMS center (MMSC) is to transmit an MM4 interface message to the CMS center (MMSC), the MMS relay module in the CMS source center (MMSC) establishes an SMTP protocol connection between these two CMS centers ( MMSC) for transmitting an MM4 interface message. When the transmission of the MM4 interface message is complete, the SMTP connection must be disconnected. The SMTP connection established according to this method is a short-term connection, and it should be interrupted after the completion of the message transmission.

However, in the case of commercial CMS (MMSC) centers, support for a continuous SMTP connection is required, therefore this method does not meet the requirements for commercial services. In this case, a long SMTP connection is called maintaining a long time SMTP connection, designed to perform many data services. During the connection period, both parties involved in the communication session should send communication packets to each other if no data packets are being sent.

According to the second method known from the prior art, the MMS repeater module of the source CMS (MMSC) center is divided into the following elements: a pool of messages to be sent, a distribution and message management module, a SMTP connection pool of an MM4 interface. As illustrated in FIG. 3, the method for transmitting MM4 interface messages comprises the following steps:

Step 301: after creating the MM4 interface message by the source TsUMS center (MMSC), the MMS repeater module of the source TsUMS center (MMSC) saves this message in the pool of messages intended for sending, where this message is awaiting transmission.

Step 302: the message distribution and management module determines whether the standby connection is present in the MM4 interface SMTP connection pool; if there is no such connection, then the distribution and message management module should repeat the search process; if a connection in standby mode is detected, the message distribution and management module retrieves the message of the MM4 interface from the pool of messages intended for sending and transmits this message for transmission to a free SMTP connection.

The second method has the following characteristics:

1. The distribution and message management module distributes messages of the MM4 interface only with the calculation of the presence of an free SMTP connection. Therefore, it is impossible to guarantee that if a new message transfer task is assigned to the SMTP connection, then the MMSC terminal center for the new MM4 interface message intended for transmission over this SMTP connection will be the same as the MMSC terminal center for the previous MM4 interface message sent over this SMTP connection. In this case, the SMTP connection with the previous MMSC end center must be disconnected and it must be switched to the new MMSC end center every time a new message sending task is assigned to this connection.

You can see that the second method also implements short-term connections. In this method, the benefits of a long SMTP connection are not fully utilized, and the overall message transfer efficiency of the MM4 interface is relatively low. Experimental data show that transmission efficiency with a short-term connection is 25% lower than with a long-term connection.

2. The number of SMTP connections allocated to the various end-user centers (MMSC) is not effectively controlled. If the majority of SMTP connections are allocated for one MMSC endpoint center and the reception speed of MM4 interface messages in this MMSC center is reduced due to some kind of malfunction, then the overall transmission speed of the MM4 interface messages from the original MMSC center can be also reduced, moreover, the operation of the MM4 interface of the source center TSUMS (MMSC) can be paralyzed.

SUMMARY OF THE INVENTION

In the embodiments of the present invention described herein, there is provided a method for transmitting MM4 interface messages in a multimedia messaging system that takes full advantage of SMTP connections, i.e. SMTP connections can be maintained for a long time, which ensures the fastest transfer of messages from the MM4 interface from the MMSC center.

The method for transmitting MM4 interface messages in a multimedia messaging system comprises the following steps:

allocate SMTP connections managed by the source TsUMS center (MMSC) for various terminal centers TsUMS (MMSC);

distribute the messages of the MM4 interface created by the source CMS (MMSC) into categories in accordance with the addresses of the end centers of the CMS (MMSC) to which the specified messages of the MM4 interface must be sent; and

The categories of messages of the MM4 interface are categorized and sent to the corresponding MMSC end centers via SMTP connections dedicated to the corresponding MMSC end centers.

The Multimedia Messaging Service Center (MMSC) for transmitting MM4 interface messages containing one or more nodes designed to perform the following:

distribution by categories of messages of the MM4 interface created by the TsUMS center (MMSC), in accordance with the addresses to which these messages of the MM4 interface should be sent;

Allocation of SMTP connections managed by the CMS (MMSC) center to the messages of the MM4 interface in accordance with the categories of these messages of the MM4 interface; and

sending MM4 interface messages through SMTP connections allocated to this category of MM4 interface messages.

From the above technical solution, it can be seen that according to this method of transmitting messages of the MM4 interface in the multimedia message system proposed in the embodiment of the present invention, the messages of the MM4 interface are categorized and stored in accordance with the addresses of the MMSC end centers, some SMTP connections are allocated for the corresponding TsUMS terminal center (MMSC), and then the messages of the MM4 interface intended for sending to some terminal TsUMS center (MMSC) are transmitted to SMTP connections allocated The second one is for transmission to the indicated end center of the CMS (MMSC). Thus, upon receipt of a new task for sending a message, it is not necessary to disconnect SMTP connections with previously connected CMS (MMSC) end centers. This method allows you to significantly increase the utilization rate of SMTP connections for sending messages to the MM4 interface, as well as solve the existing problem, which consists in the need to frequently switch the SMTP connection between different terminal centers of MMS (MMS).

In addition, in embodiments of the present invention, the number of SMTP connections allocated to each MMSC end center is dynamically adjusted in accordance with message parameters of the MM4 interface;

so that the number of SMTP connections allocated to each CMSC endpoint (MMSC) can be maintained within the appropriate framework, which will allow the transmission of MM4 interface messages in a shorter period and will avoid blocking the MM4 interface in the event of a malfunction that may occur when the MM4 interface messages are received terminal center TSUMS (MMSC). In practical tests, it was found that, compared with the current level of technology, the transmission efficiency of MM4 interface messages in embodiments of the present invention is increased by an average of 20-25%.

Brief Description of the Drawings

1 is a block diagram illustrating the architecture of a multimedia messaging system according to the state of the art.

2 is a block diagram illustrating the architecture of a multimedia messaging system comprising several MMSC centers connected to each other according to the state of the art.

FIG. 3 is a flowchart illustrating a method for transmitting MM4 interface messages according to the state of the art.

4 is a flowchart illustrating a method for transmitting MM4 interface messages according to an embodiment of the present invention.

Embodiments of the invention

The following is a detailed description of the present invention with reference to the accompanying drawings, as well as its implementation options.

4 is a flowchart illustrating a method for transmitting MM4 interface messages to MMSC source centers according to an embodiment of the present invention. In this implementation, the MMS repeater module of the source TsUMS (MMSC) center creates for each terminal TsUMS (MMSC) a message pool of the TsUMS (MMSC) center and allocates a certain number of SMTP connections to each terminal TsUMS (MMSC), i.e. splits the SMTP connection pool for the MM4 interface into several connection sub-pools, each of which corresponds to a specific MMSC end center. Each connection sub-pool transmits MM4 interface messages through the SMTP connections allocated for it, provided that the SMTP connection data between the source MMSC and the corresponding MMSC has already been established.

Step 401: after the source MMSC center creates an MM4 interface message, the MMS repeater module of the original MMSC center stores this MM4 interface message in the pool of messages to be sent. After that, the MMS repeater module sends this message of the MM4 interface, waiting to be sent, to the corresponding message pool of the MMSC center in accordance with the address of the MMSC end center.

For example, if the source TsUMS center (MMSC) creates an MM4 interface message that must be sent to the terminal center TsUMS (MMSC) "i", where "i" is an arbitrary integer from 1 to "N", then the source center TsUMS (MMSC) must create in advance "N" message pools of the CMS centers (MMSC) for storing messages of the MM4 interface intended for sending to the corresponding end centers of the CMS (MMSC).

Step 402: after receiving the message of the MM4 interface, the message center of the TsUMS center (MMSC) sends this message to the MM4 interface to the corresponding sub-pool of connections. The connection sub-pool transmits this MM4 interface message through the SMTP connection it manages.

In the above-described method for transmitting messages, the number of SMTP connections allocated for each sub-pool of connections is dynamically adjusted based on the message parameters of the MM4 interface of the corresponding message center center (MMSC). It is preferable that a periodic adjustment scheme be applied to the above method, which means that the number of SMTP connections allocated to any sub-pool of connections needs to be adjusted at regular intervals. The interval value can be set arbitrarily, and if the interval value is zero, then the adjustment is performed in real time. Also, the number of SMTP connections allocated for any connection sub-pool can be configured according to the instructions of the system administrator or remotely according to the instructions from other devices on the network. The message parameters of the MM4 interface of this message pool of the TsUMS center (MMSC) contain: the number of messages of the MM4 interface, the length of messages, the index for increasing / decreasing the volume of messages, the index for the speed of message transmission, the index for increasing the speed of message transmission, etc.

If at the first time point the number of messages in the message pool of some end i-center of the MMSCi, namely, in the message pool of the MMSCi center, is Ni, and the number of messages in the pool of messages to be sent is Nsum. and the message length in the message pool of this TSUMSi center (MMSCi) is Si, and the message length in the pool of messages destined for sending messages is Ssum, then the ratio of the LKNi parameter is equal to the number of SMTP connections allocated for the connection pool of this TSUMSi center (MMSCi) in the first time point, to the LKNsum parameter, equal to the total number of SMTP connections related to this source center of the CMS (MMSC), is represented by the expression (1):

where µN is the weight of the number of messages, µs is the weight of the length of the messages, and µN + µs = 1. Both of these weights can be formed and adjusted as needed. For example, it can be specified that µN = 0.6 and µs = 0.4. In addition, the sum of µN and µs may be less than unity, in which case some compounds are reserved for future use. The message length Si is the total length of all messages in the message pool of this center TSUMS1 (MMSCi), and Ssum is the total length of all messages in the pool intended for sending messages.

From equation (1), we can conclude that if the parameter Ni, which is equal to the number of messages in the message pool of a certain TSUMSi center (MMSCi), increases, while the remaining parameters do not change, then the parameter LKNi, which is equal to the number of SMTP connections allocated for of this pool of connections, the center of this center TSUMSi (MMSCi)) will increase accordingly.

The calculation of the index increase / decrease the volume of messages Δi is as follows. If Nj is the number of messages at the second time point, and Ni is the number of messages at the first time point, then the parameter NIi, equal to the increase / decrease in the number of messages for the period from the second time point to the first, is Ni-Nj. In this case, the first time point is the current point in time, the second time point is the previous time point before the first time point. When the number of messages to be sent at the first time point exceeds the number of such messages at the second time point, then NIi has a positive value; if the number of messages to be sent at the first time point is less than the number of such messages at the second time point, then NIi has a negative value. In addition, if SIi is an increase / decrease in the length of messages, then the index of increase / decrease in the volume of messages Δi for the message pool of a certain TSUMSi center (MMSCi) can be obtained from expression (2):

where Slsum = ΣSIi, NIsum = ΣNIi and the numerical value Δi lies in the range [0, 1].

When calculating the Vi message rate index, the period from the second time point to the first is designated as the first time period, and if NDi is the number of messages sent in the first time period, and SDi is the length of these sent messages, then the Vi message rate index for the message pool of a certain TsUMSi center (MMSCi) can be obtained from equation (3):

where SDsum = ΣSDi, NDsum = ΣNDi and the numerical value of Vi lies in the range [0, 1].

In the formation of LKNi, i.e. the number of SMTP connections allocated to the connection pool of a certain TSUMSi center (MMSCi), both parameters, Δi and Vi, can be taken into account. In this case, the ratio of the parameter LKNi to the parameter LKNsum, i.e. to the total number of SMTP connections related to the source center TSUMS (MMSC), is presented in equation (4):

where µΔ is the value of the increase / decrease index of the number of messages, and µv is the value of the message rate index. Typically, µΔ = µv.

When calculating the index of increasing the message transfer rate σai, the period from the third time point to the second time point is called the second time period. In this case, the third time point precedes the second time point. If Vij is the index of the message transmission rate of the first time period, and Vij-1 is the similar index of the second time period, then the speed increment between the first time period and the second time period can be expressed by the equation ai = ΔVi = Vij-Vij-1, a asum = I | ai | represents the sum of the absolute values of the velocity increments of all the end centers of the TSUMS (MMSC). Thus, the index of increasing the message transfer rate σai of this message pool of the TsUMSi center (MMSCi) can be obtained from equation (5), and the numerical value oai lies in the range [0, 1].

Therefore, the parameter σai can then be taken into account in determining LKNi, i.e. the number of SMTP connections allocated for this connection pool of the TSUMSi center (MMSCi), and the ratio of the LKNi parameter to the LKNsum parameter, i.e. to the total number of SMTP connections related to the source center TSUMS (MMSC), is presented in equation (6):

where µσ is the weight coefficient of the message rate increase index. The weighting coefficients in equation (6) can be set arbitrarily, for example, μΔ = 0.3, μv = 0.3 and μσ = 0.2, etc.

Based on equation (6), we can conclude that with an increase in the index of increase / decrease in message volume Δi, while other parameters remain the same, LKNi, i.e. the number of SMTP connections allocated to the connection pool of a certain TSUMSi center (MMSCi) will increase accordingly; and if there occurs a decrease in the message rate index Vi, with other parameters unchanged, then LKNi, i.e. the number of SMTP connections allocated for a given connection pool of the TSUMSi center (MMSCi) will decrease accordingly. A decrease in the message speed index Vi of the connection pool of a certain TsUMSi center (MMSCi) indicates that there may be problems with this terminal center of the TsUMSi (MMSCi), so the number of connections in the connection pool of this TsUMSi center (MMSCi) should be reduced, and the SMTP communication resources , which are limited, it is necessary to allocate for other end CMS (MMSC) centers in order to avoid, as far as possible, unnecessary resource costs when channel overload.

From the implementation described above, it can be seen that according to embodiments of the present invention, a certain number of SMTP connections are allocated to each end of the MMSC center for sending MM4 interface messages in the multimedia messaging system, and sending messages of the MM4 interface to the final MMSC center is realized through the connections SMTPs corresponding to this endpoint of the CMS (MMSC); thus, the problem of frequent switching of SMTP connections between the various MMSC end centers has been resolved. In addition, according to this method, the number of SMTP connections allocated to each end of the MMSC center can be adjusted dynamically, which allows optimal use of resources.

It should be appreciated that those skilled in the art may make modifications and changes to the present invention that will also be consistent with the technical scheme and idea of the present invention and, therefore, such modifications and changes should also be included within the scope of patent protection as defined in the claims of the present invention.

Claims (12)

1. A method for transmitting MM4 interface messages in a multimedia messaging system, comprising the following steps:
allocate Simple Mail Transfer Protocol (SMTP) connections managed by the source Multimedia Messaging Service Center (MMSC), the end centers of the Multimedia Messaging Center (MMSC);
distribute the messages of the MM4 interface created by the source CMS (MMSC) into categories in accordance with the addresses of the end centers of the CMS (MMSC) to which the specified messages of the MM4 interface must be sent; and
send the categorized messages of the MM4 interface to the corresponding end CMS (MMSC) centers through the SMTP connections allocated to the corresponding end CMS (MMSC) centers. 2. The method according to claim 1, in which the step of allocating SMTP connections includes the following: the source center MSC (MMSC) dynamically allocates SMTP connections in accordance with the message settings of the interface MM4 end centers MSC (MMSC) at the first time point. 3. The method according to claim 2, wherein the step of dynamically allocating SMTP connections comprises the following: the source MMSC center calculates the number of SMTP connections allocated to each end MMSC center according to instructions or at regular intervals and allocates the connections SMTP in accordance with the calculation results. 4. The method according to claim 2 or 3, in which the message parameters of the interface MM4 of the end center of the CMS (MMSC) contain the number of messages and the length of messages intended to be sent to the specified end center of the CMS (MMSC); and
the step of allocating SMTP connections for MMSC end centers contains the following: for each MMSC end center, the number of SMTP connections is determined depending on the number of messages and message length at the first time point, as well as depending on the weighting factors corresponding to the number of messages and message length, respectively. 5. The method according to claim 4, in which the sum of the weight of the number of messages and the weight of the length of the messages is 1. 6. The method according to claim 4, in which, the message parameters of the MM4 interface further comprise an index for increasing / decreasing the volume of messages and an index for the message rate; and
the step of allocating SMTP connections for MMSC end centers contains the following: for each MMSC end center, the number of SMTP connections is determined in accordance with the number of messages, message length, message increase / decrease index and message rate index, as well as according to weights corresponding to the four parameters described above, respectively. 7. The method according to claim 6, in which the index of increase / decrease in the volume of messages is determined in accordance with the change between the number intended for sending messages to the end center of the MMSC at the first time point and the same number at the second time point, as well as in accordance with the increment between the length of messages destined for sending to the MMSC end center (MMSC) at the first time point and the same length at the second time point, the second time point preceding the first time point. 8. The method according to claim 6, in which the message rate index is determined in accordance with the number of messages and the length of messages sent to the terminal center TSUMS (MMSC). 9. The method according to claim 6, in which the message parameters of the MM4 interface further comprise an index of change in the message rate; and the step of allocating SMTP connections for the MMSC end centers (MMSC) comprises the following: determining the number of SMTP connections for each MMSC end center depending on the number and length of messages destined to be sent to the MMSC end center (MMSC) at the first time point, from the index of increase / decrease in the volume of messages, from the index of the speed of message transmission and from the index of the acceleration of message transmission, as well as from the weight coefficients that correspond to the five above parameters, respectively. 10. The method according to claim 9, in which the message transfer acceleration index is determined depending on the change between the message transmission speed index in the first time period and the same index in the second time period, the first time period being the period between the first time point and the second time point, the second time period is the period between the second time point and the third time point, and the third time point precedes the second time point. 11. The Multimedia Messaging Service Center (MMSC) for transmitting messages of the MM4 interface, containing one or more nodes designed to perform the following actions:
distribution by categories of messages of the MM4 interface in accordance with the addresses to which these messages of the MM4 interface should be sent; allocation of SMTP connections for messages of the MM4 interface in accordance with the categories of these messages of the MM4 interface; and
sending MM4 interface messages through SMTP connections allocated for this category of MM4 interface messages. 12. CMS (MMSC) according to claim 11, in which one or more nodes are configured to dynamically allocate SMTP connections in accordance with the message parameters of the MM4 interface, and the message parameters of the MM4 interface contain at least one of the following values: the number of messages, message length, message increase / decrease index, message rate index, and message acceleration index.

Images