WO2012022074A1

WO2012022074A1 - User information query method and multimedia messaging service center

Info

Publication number: WO2012022074A1
Application number: PCT/CN2010/078045
Authority: WO
Inventors: 张剑
Original assignee: 中兴通讯股份有限公司
Priority date: 2010-08-19
Filing date: 2010-10-22
Publication date: 2012-02-23
Also published as: CN101909256B; CN101909256A

Abstract

The invention discloses a user information query method and a multimedia messaging service center (MMSC). The MMSC includes a service processing module and a retry module. The method includes the following steps: when the user information query fails, the service processing module determines to initiate a query retry process, and transmits a query retry message of the user information to the retry module; the retry module transmits, to the service processing module, a query retry message satisfying the predetermined trigger conditions among the received query retry messages; the service processing module re-initiates a process of querying the user information corresponding to the query retry message satisfying the predetermined trigger conditions. With the technical solution of the present invention, the success rate of distributing multimedia messages by MMSC is increased, thus the user experience is improved.

Description

The present invention relates to the field of communications, and in particular to a method for querying user information and a multimedia message center. BACKGROUND A Multimedia Messaging Service (MMS) is a messaging service capable of transferring multimedia content between a terminal (eg, a mobile phone) and a terminal, and between other applications such as a terminal and an email server. Compared with the very successful text message short message service currently applied, the multimedia message will provide users with message content including various media formats such as images and sounds, so that operators can provide users with very rich and personalized information. Month. For example, you can send beautiful scenery with background music to your friends and relatives in the distance, and send elaborate e-cards. When the multimedia message is sent to the mobile phone user, the user information of the mobile phone is stored in the HLR server, and the multimedia message center needs to query the HLR server through the MM5 message interface to obtain the user information of the mobile phone, and determine the delivery mode of the multimedia message according to the user information, if the user mobile phone If the status is normal, the multimedia message center sends a normal multimedia message notification message to the mobile phone user. However, when the multimedia message center fails to query the HLR server through the MM5 message interface, the multimedia message center cannot deliver the multimedia message to be submitted, which results in a lower success rate of delivering the multimedia message and greatly reduces the user experience. SUMMARY OF THE INVENTION A primary object of the present invention is to provide a method for querying user information and a multimedia message center to solve at least one of the above problems. According to an aspect of the present invention, a method of querying user information is provided. The method for querying the user information according to the present invention is applied to the MMSC. The MMSC includes: a service processing module and a retry module. The method includes: when the user information query fails, the service processing module determines to initiate a query retry process, and The test module sends a query retry message of the user information; The test module sends the query retry message that meets the predetermined trigger condition in the received query retry message to the service processing module. The service processing module re-initiates the process of querying the user information corresponding to the query retry message that meets the predetermined trigger condition. According to another aspect of the present invention, a multimedia message center is provided. The multimedia message center according to the present invention includes: a service processing module, configured to: when the user information query fails, determine to initiate a query retry process, send a query retry message of the user information to the retry module, and receive the query retry message. When the query retry message satisfying the predetermined trigger condition is met, the process of querying the user information corresponding to the query retry message is re-initiated. The retry module is configured to determine a query retry message that satisfies a predetermined trigger condition, and send the query retry message to the service processing module. After the MMSC fails to query the user information, in the case that the retry query is determined, the process of re-initiating the user information corresponding to the retry message satisfying the predetermined trigger condition in the query retry message is re-initiated. The problem that the success rate of the multimedia message sent by the MMSC in the related art is low is solved, and the success rate of the MMSC sending the multimedia message can be effectively improved, thereby improving the user experience. BRIEF DESCRIPTION OF THE DRAWINGS The accompanying drawings, which are set to illustrate,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,, In the drawings: FIG. 1 is a flowchart of a method for querying user information according to an embodiment of the present invention; FIG. 2 is a flowchart of a method for querying user information according to a preferred embodiment of the present invention; FIG. 4 is a structural block diagram of a multimedia message center according to a preferred embodiment of the present invention. FIG. BEST MODE FOR CARRYING OUT THE INVENTION Hereinafter, the present invention will be described in detail with reference to the accompanying drawings. It should be noted that the embodiments in the present application and the features in the embodiments may be combined with each other without conflict. FIG. 1 is a flowchart of a method for querying user information according to an embodiment of the present invention. The method is applied to the MMSC, and the MMSC includes: a service processing module and a retry module, as shown in FIG. The query method of the user information mainly includes the following processing: Step 4: S 102: When the user information query fails, the service processing module determines to initiate a query retry process, and sends a query retry message of the user information to the retry module; Step S104 The retry module sends the query retry message that meets the predetermined trigger condition in the received query retry message to the service processing module; Step S106: The service processing module re-initiates the query corresponding to the query retry message satisfying the predetermined trigger condition The flow of information. In the related art, when the multimedia message center fails to query the HLR server through the MM5 message interface, the multimedia message center cannot deliver the multimedia message to be submitted. By using the above method, the success rate of the multimedia message sent by the MMSC can be effectively improved, thereby improving the user's body-risk. The multimedia message center may include multiple functional modules: a service processing module, a proxy module, a retry module, and a service configuration module. In a preferred implementation process, after the multimedia message is submitted to the multimedia multimedia message center, the message is analyzed by the service processing module of the multimedia multimedia message center. If the terminating user is a mobile terminal (for example, a mobile phone), an MM5 for the terminating user is initiated. The query request message (ie, the user information query message) is sent to the proxy module. After receiving the query request, the proxy module firstly obtains the information of the HLR configured on the multimedia message service configuration module, obtains the network information of the HLR, and establishes a link to the HLR. If the link succeeds, the proxy module encodes the request message to The HLR initiates a ré 5 query request and waits for an HLR response. If the proxy module receives the query response from the HLR server, the proxy module decodes the response message and returns the query result to the service processing module. After the service processing module receives the MM5 query response, if the query is successful, the multimedia message submission process is continued. However, in one of the following cases, the user information query may fail. The first case: the proxy module of the MMSC fails to establish a link with the HLR that stores the user information; the second case: the HLR returns a response timeout; The third case: The HLR queries the user information incorrectly. Preferably, in step 4 S 102, the service processing module determines that initiating the query retry process may include the following processing:

(1) The service processing module receives a status code from the proxy module, where the status code is used to reflect the foregoing situation corresponding to the query failure;

(2) The service processing module determines whether it is necessary to initiate a query retry process according to the status code. In the preferred implementation process, if the user information query fails, the proxy module returns a status code that is queried by the service processing module, and each status code indicates an error condition, for example, a failure to establish a chain with the HLR server, and the HLR returns a response timeout. Incorrect, the HLR queries multiple error types such as the terminal mobile phone number error. Each error has a specified error code. However, these error states do not need to be retried each. Here, you need to configure the status code that needs to be retried. When a certain status code is configured, the RB 5 retry request is initiated when the service processing module receives the status code. In the first case above, that is, if the proxy module fails to establish a link with the HLR, the proxy module returns an error to the service processing module. If the service processing module receives the link failure response of the proxy module, the service processing module determines whether the situation is retried according to the configuration in the service configuration module of the MMSC. If the retry is required, the query is sent to the retry module. The test request retry module configuration information of the service configuration module to establish retry control information. If the proxy module successfully sends the MM5 query message, but if the response returned by the HLR is not received within the system setup time, the proxy module returns a failure response to the service processing module, and after receiving the response, the service processing module determines whether to perform heavy Try, if you need to retry, enter the retry process. If the proxy module receives the query response from the HLR, the proxy module decodes the response message and returns the query result to the service processing module. After receiving the MM5 query response, the service processing module continues the multimedia message submission process if the query is successful. If the query user information is incorrect, it is determined according to the status code whether it needs to be retried. If it needs to be retried, the retry process is entered. Preferably, the predetermined trigger condition in the step S104 above includes one of the following:

(1) receiving a notification message from the HLR indicating that the terminal is in an active state, where the notification message is consistent with the terminal identifier carried in the query retry message satisfying the predetermined trigger condition; (2) receiving a retry timing message from the service configuration module of the LSI, wherein the retry timing message is consistent with the terminal identifier carried in the query retry message satisfying the predetermined trigger condition. In the preferred implementation process, after the retry module establishes the MM5 retry mechanism, the retry request can be initiated by using two trigger modes. The first trigger mode is: the MM5A l er t message initiated by the HLR (that is, the foregoing notification message) The message indicates that the user is in the active state. When the retry module receives the message, it immediately initiates a restart request. The second trigger mode is: Retrying according to the retry policy configured in the service configuration module. For example, retry every five minutes, and when the scheduled time arrives, send a retry timing message to the service configuration module of the RIS SC to trigger the retry process. After receiving the foregoing notification message or retrying the timing message, the service processing module re-initiates the MM5 query, and notifies the multimedia message retry module to the query result. After receiving the retry message, the multimedia message service processing module re-initiates the MM5 query request. And follow the above steps to determine the subsequent process. Preferably, when the retry module sends the query retry message that meets the predetermined trigger condition to the service processing module, the following processing may be further included: the retry module deletes the query retry message that satisfies the predetermined trigger condition in the query retry message. Through the above processing, the retry module is only triggered by one of the retry timing message of the notification message and the retry message queue. For example, if the retry module first receives the retry timing message, the retry module sends the retry message to the service processing module, and the message is deleted from the retry queue, so that the notification message is not received after receiving the notification message. Will be triggered repeatedly. Preferably, the foregoing method may further include the following process: the retry module determines whether the current number of retries reaches a maximum number of times configured in the service configuration module of the MMSC; if yes, ends the user information query. In the preferred implementation process, if the current number of retries reaches the maximum number of times configured in the service configuration module, and the user information has not been successfully queried, the LSI fails to send the multimedia message. Through this processing, the MMSC can be effectively prevented from continuously querying user information, thereby saving system resources. The above preferred embodiment will be described below in conjunction with FIG. 2 is a flow chart showing a method for querying user information according to a preferred embodiment of the present invention. The method for querying the foregoing user information is described below with reference to FIG. 2, which mainly includes the following steps: Step 1: Configure MM5 query failure retry information in the service configuration module, where the letter The information mainly includes:

(1) Retry status code: If the MM5 query fails, the agent module (MM5 Agent) will return the status code of the query to the service processing module (MMS Relay). Each status code indicates an error status, for example, the proxy module and The HLR fails to establish a link, the HLR returns a response timeout error, the HLR queries the terminal for a mobile phone number error, and so on. Each type of error has a specified status code, but not all of these error statuses need to be retried. Configure the status code that needs to be retried. When a status code is configured, the MMS Relay will initiate an MM5 retry request when it receives the status code.

(2) MM5 retry mechanism (policy;): This contains the number of retries and the time interval between each retries. The number of retries indicates the total number of failed retries. If the number of retries is greater than the set value, the final retry fails. The retry time indicates the time interval between retries. The retry time and number of times can be arbitrarily combined. For example, try again three times, each time you pay attention to the interval of five minutes, this only retry twice, the first retry is five minutes, and the second retry is ten minutes.

(3) External trigger MM5 retry event: In configuration 2, the retry module actively initiates a retry strategy, but some retry attempts are triggered by an external server, for example, the above HLR server The MM5 Alert message is initiated by the MMS Relay. If the MMS Relay receives this type of message, the MMS Relay initiates the MM5 retry process. Step 2: The other MMS platform sends a multimedia message submission request to the MMS Relay, and the MMS Relay responds to the MMS platform reply MMS. After receiving the multimedia message, the MMS Relay finds that the terminating user is the mobile terminal and needs to query the HLR, and then initiates an MM5 query request and sends the message to the MM5 Agent module. Step 4: After receiving the query message, the MM5 Agent first reads the network information of the HLR configured in the service configuration module, and establishes a communication link with the HLR server. If the link fails, the specified status code is returned, MMS Relay The module queries whether the status code needs to be retried in the configuration information of the service configuration module. If necessary, the retry message is sent to the retry module, and step S208 is performed. If not, the multimedia message fails to be delivered. If the link establishment is successful, step S210 is performed. Step 4: After receiving the retry message, the retry module first reads the retry mechanism configured in the service configuration module. If the retry mechanism is configured in the status code, the first configuration according to the retry mechanism is configured. The retry time is inserted into the timing retry queue, and the time when the retry message is triggered is the first retry time in the configuration. And save the terminal number in the query message that needs to be queried, and then retry the module to enter the standby mode, waiting for the trigger of the MM5 timing retry queue. Step 5: When the MM5 Agent and the HLR are successfully established in step S206, the query message is encoded and sent to the HLR server. Step 6: After receiving the query response from the HLR server within the specified time, the MM5 Agent returns a failure message and a specified status code to the MMS Relay. After receiving the response message, the MMS Relay queries the configuration information whether the status code needs to be retried. If necessary, a retry message is sent to the MM5 retry module, and if not required, the multimedia message fails. Then the operation of step S208 is repeated. Step 7: After receiving the response from the HLR server, the MM5 Agent module returns a message to the MMS Relay module. If the MM5 query succeeds, the multimedia message submission process is continued. If the query fails, the MMS Relay module queries whether the status code needs to be retried in the configuration information, and if necessary, sends a retry message to the MM5 retry module, if not, the multimedia The message failed to be delivered. Then repeat step 4 to gather S208 operation. Step 8: After the MM5 query enters the retry process, the MM5 retry module enters the standby mode. If the MM5 Alert message triggers the retry mechanism in the service configuration module, the MM5 retry module waits for two trigger messages. One is MM5Alert. The message, one is the MM5 retry timing message. When the MM5 retry module receives any retry message, it discards another trigger message. Step 9: If the MM5 retry module first receives the MM5 Alert message from the HLR, the MM5 retry is triggered by the MM5Alert message, and the MM5 retry module queries all retry attempts in the retry message queue to carry the same terminal number as the MM5Alert message. The message is sent to the MMS Relay and the retry message in the retry queue is deleted. That is, in this case, the MM5 retry is only triggered by the MM5Alert message and will not be triggered by the timing message of the retry message queue. If the MM5 retry module first receives the MM5 retry timing message, the MM5 retry module sends the retry message to the MMS Relay, and the message is deleted from the retry queue, so that the MM5 Alert message can be guaranteed. It will not be triggered repeatedly. Step 10: After receiving the retry message, the MMS Relay module re-initiates the MM5 query message, and returns to the execution step 4 S206. Step 11: If the MM5 retries finally reaches the maximum configuration in the multimedia message service configuration, and the MM5 query has not been successful, the multimedia message submission fails, and the process ends. FIG. 3 is a structural block diagram of a multimedia message center in an embodiment of the present invention. As shown in FIG. 3, the multimedia message includes: a service processing module 30 and a retry module 32. The service processing module 30 is configured to: when the user information query fails, determine to initiate a query retry process, send a query retry message of the user information to the retry module, and retry the query that meets the predetermined trigger condition in receiving the query retry message. When the message is received, the process of querying the user information corresponding to the query retry message is re-initiated. The retry module 32 is configured to determine the query retry message that meets the predetermined trigger condition, and send the query retry message to the service processing module 30. In the foregoing MMSC, the service processing module 30 re-initiates the user information query process for the query retry message that meets the predetermined trigger condition determined by the retry module 32. The success rate of sending multimedia messages by the MMSC can be effectively improved, thereby improving the user experience. Preferably, as shown in FIG. 4, the foregoing MMSC may further include: a proxy module 34, configured to return a status code to the service processing module, where the status code is used to reflect a situation corresponding to the query failure, and the situation includes one of the following: The proxy module fails to establish the HLR of the user information, the HLR returns the response timeout, and the HLR queries the user information error. The service processing module 30 is further configured to receive the status code from the proxy module, and determine whether the query needs to be initiated according to the status code. Test process. Preferably, as shown in FIG. 4, the foregoing MMSC may further include: a service configuration module 36, configured to send a retry timing message to the retry module 32; and a retry module 32, further configured to be in the presentation terminal from the HLR When the notification message of the activation state or the retry timing message is consistent with the terminal identifier carried in the query retry message that satisfies the predetermined trigger condition, it is determined that the query retry message satisfying the predetermined trigger condition is transmitted. Preferably, as shown in FIG. 4, the retry module 32 is further configured to end the user information query process when it is determined that the current number of retries reaches the maximum number of times configured in the service configuration module. Preferably, as shown in FIG. 4, the retry module 32 is further configured to: when the query retry message satisfying the predetermined trigger condition is sent to the service processing module, delete the query retry message that satisfies the predetermined trigger condition from the query retry message. . Preferred embodiments in which the above modules are combined with each other are described below. After the multimedia message is submitted to the multimedia multimedia message center, the service processing module 30 analyzes the message. If the terminating call user is a mobile phone terminal, initiate a MM5 query for the terminating call user. Request a message, send the message to the proxy module. After receiving the query request, the proxy module 34 first obtains the network information of the HLR according to the information of the HLR configured on the service configuration module 36, and establishes a link request to the HLR. If the link is successfully established, the proxy module 34 encodes the request message. , initiating an MM5 query request to the HLR, and waiting for an HLR response; if the HLR link setup fails, an error is returned to the service processing module 30. If the service processing module 30 receives the link failure response of the proxy module, the service processing module determines whether the situation is retried according to the configuration in the service configuration module 36. If the retry is required, the MM5 is sent to the retry module 32. The trial request, retry module 32 establishes retry control information based on the configuration. If the proxy module 34 successfully sends the MM5 query message, but if the HLR response is not received within the system setup time, the proxy module 34 returns a failure response to the service processing module 30, and after receiving the response, the service processing module 30 determines whether to proceed according to the configuration. Retry, if you need to retry, enter the retry process. If the proxy module receives the query response from the HLR server, the proxy module decodes the response message and returns the query result to the service processing module. After receiving the MM5 query response, the service processing module 30 continues the multimedia message submission process if the query is successful; if the query fails, it determines whether the retry is required according to the status code, and if it needs to be retried, enters the retry process. After the retry module 32 establishes the MM5 retry mechanism, the retry request can be initiated according to the two retry modes. The first mode is an MM5 Alert message initiated by the HLR, and the message indicates that the user is in an active state. After receiving the message, the retry module immediately initiates a restart request; the second method is to retry according to the retry policy configured in the service configuration module. After receiving the MM5 query retry request, the service processing module 30 re-executes the MM5 query, and notifies the retry module of the query result. After receiving the retry message, the service processing module 30 re-initiates the MM5 query request, and determines according to the above steps. Follow-up process. If the MM5 retry query is successful within the MM5 retry policy specified by the service configuration module 36, the multimedia message submission fails. In summary, after the multimedia message center fails to query the user information, it returns to the failure state to determine whether to perform the MM5 retry query. If the query needs to be retried, then the multimedia cancellation is performed. The control information of the information center is retries by the MM5 query until the success or the final query fails. With the above embodiments provided by the present invention, the success rate of sending multimedia messages by the MMSC can be effectively improved, thereby greatly improving the user body risk. Obviously, those skilled in the art should understand that the above modules or steps of the present invention can be implemented by a general-purpose computing device, which can be concentrated on a single computing device or distributed over a network composed of multiple computing devices. Alternatively, they may be implemented by program code executable by the computing device, such that they may be stored in the storage device by the computing device and, in some cases, may be different from the order herein. The steps shown or described are performed, or they are separately fabricated into individual integrated circuit modules, or a plurality of modules or steps are fabricated as a single integrated circuit module. Thus, the invention is not limited to any specific combination of hardware and software. The above is only the preferred embodiment of the present invention, and is not intended to limit the present invention, and various modifications and changes can be made to the present invention. Any modifications, equivalent substitutions, improvements, etc. made within the scope of the present invention are intended to be included within the scope of the present invention.

Claims

The method for querying user information is applied to a multimedia message center MMSC, wherein the MMSC includes: a service processing module and a retry module, and the method includes:

When the user information query fails, the service processing module determines to initiate a query retry process, and sends a query retry message of the user information to the retry module;

The retry module sends the received query retry message that meets the predetermined trigger condition in the received query retry message to the service processing module;

And the service processing module re-initiates a process of querying the user information corresponding to the query retry message that meets the predetermined trigger condition. The method according to claim 1, wherein in the following case, the user information query fails:

The proxy module of the MMSC fails to establish a link with the HLR that stores the user information; the HLR returns a response timeout;

The HLR queries the user information for an error. The method according to claim 2, wherein the service processing module determines that the initiating query retry includes:

The service processing module receives a status code from the proxy module, where the status code is used to reflect the situation corresponding to a query failure;

The service processing module determines whether a query retry process needs to be initiated based on the status code. The method according to claim 1, wherein the predetermined trigger condition comprises one of the following:

Receiving a notification message from the HLR indicating that the terminal is in an active state, where the message is consistent with the terminal identifier carried in the query retry message satisfying the predetermined trigger condition;

Receiving a retry timing message from the service configuration module of the MMSC, where the message is consistent with the terminal identifier carried in the query retry message that meets the predetermined trigger condition.

The method according to claim 1, wherein when the retry module sends the query retry message that satisfies a predetermined trigger condition to the service processing module, the method further includes: The retry module deletes the query retry message that satisfies the predetermined trigger condition in the query retry message.

The method according to any one of claims 1 to 5, wherein the method further comprises:

The retry module determines whether the current number of retries reaches a maximum number of times configured in the service configuration module of the MMSC;

If yes, end the user information query process.

7. A multimedia message center MMSC, characterized in that it comprises:

a service processing module, configured to: when the user information query fails, determine a query retry process, send a query retry message of the user information to the retry module, and receive a query that meets the predetermined trigger condition in the query retry message When the message is tried, the process of querying the user information corresponding to the query retry message is re-initiated.

The retry module is configured to determine the query retry message that meets a predetermined trigger condition, and send the query retry message to the service processing module.

8. The MMSC of claim 7 wherein:

The MMSC further includes: a proxy module, configured to return to the service processing module ^! The status code is used to reflect the situation corresponding to the query failure, and the situation includes one of the following: the proxy module fails to establish an HLR with the user information, and the HLR returns a response timeout. The HLR queries the user information error;

The service processing module is further configured to receive the status code from the proxy module, and determine, according to the status code, whether a query retry process needs to be initiated.

9. The MMSC of claim 7 wherein:

The MMSC further includes: a service configuration module, configured to send a retry timing message to the retry module;

The retry module is further configured to retry the notification message or the retry timing message from the HLR indicating that the terminal is in an active state and the query that meets the predetermined trigger condition When the terminal identifiers carried by the information are consistent, it is determined to send the query retry message that satisfies the predetermined trigger condition.

The MMSC of claim 9, wherein the retry module is further configured to end the user information query process when it is determined that the current number of retries reaches a maximum number of times configured in the service configuration module.

The MMSC of claim 7, wherein the retry module is further configured to: when the query retry message satisfying a predetermined trigger condition is sent to the service processing module, The query retry message satisfying the predetermined trigger condition is deleted in the test message.