Abstract:
A method for processing the multimedia message, MM, includes: notifying, by the a multimedia message center, MMC, the home MMC of a recipient terminal, to receive the MM; requesting, by the recipient terminal according to the notification, to acquire the MM from the home MMC of the recipient terminal; sending, by the home MMC of the recipient terminal, the MM to the recipient terminal; and confirming with the MMC that the MM has been received according to the address delivered by the MMC, when the recipient terminal receives the MM. This method may prevent the bill evasion.

Description:
CROSS REFERENCE TO RELATED APPLICATION 
       [0001]    The present application is a continuation application of International Application No. PCT/CN2006/002676, filed on Oct. 12, 2006, which claims the benefit of Chinese Patent Application No. 200510100352.5, filed on Oct. 13, 2005, both of which are incorporated by reference herein in its entirety. 
     
    
     FIELD 
       [0002]    Embodiments of the present invention relate to the technical field of Multimedia Message, MM, and in particular, to a Multimedia Message Service Center, MMSC, terminal and a method for processing MM. 
       BACKGROUND 
       [0003]    In recent years, many telecom operators are deploying and operating multimedia message service, MMS, on the network. The MMS has been regarded as a spotlight after the short messages service, SMS, and enhanced message service. 
         [0004]    The processing procedures of multimedia message and short message are similar, and the greatest difference lies in that, when receiving SMS messages, the recipient terminal receives the short message pushed by the SMC; in MMS, originator MMSC is the home MMSC of the originator terminal, and recipient MMSC is the home MMSC of the recipient terminal. The recipient MMSC first pushes the address of the recipient MMSC through notification, then the recipient terminal initiatively downloads the multimedia message from the recipient MMSC according to the recipient MMSC address; after the download is finished, the recipient terminal sends a message to MMSC for confirmation. 
         [0005]    For multimedia message, the best charging trigger point is after receiving the MM. In the case of the deferred retrieval, the charging trigger point is after the recipient MMSC receives the confirmation, M-Acknowledge.ind, sent by the recipient terminal. In the case of immediate retrieval, the charging trigger point is after the recipient MMSC receives the response to notification, M-Notifyresp.ind, sent by the recipient terminal. In the process of receiving the MM, according to different receiving manners, e.g. the terminal-to-terminal deferred retrieval or terminal-to-terminal immediate retrieval, the destination address of the confirmation, M-Acknowledge.ind or M-Notifyresp.ind, returned by the recipient terminal to MMSC is based on the MMSC address set on the recipient terminal. In the above charging mode, some deliberate user of the recipient terminal may evade the MM charge by changing the address of the MMSC, which brings risks for the service operation. Referring to  FIG. 1 , in which transferring multimedia message occurs between terminal A and B, the MMSC address setting on the terminal A is right, the MMSC address setting on the terminal B is wrong, the procedure runs in the following way. 
         [0006]    In Step  10 , an originator terminal A sends an MM to the originator MMSC. Because the MMSC address configuration on the terminal A is right, the terminal A may successfully send the MM. 
         [0007]    In Step  11 , the originator MMSC forwards the MM to the recipient MMSC; the transferring process belongs to the communication process among the MMSCs, which may succeed under normal condition. 
         [0008]    In Step  12 , after the recipient MMSC receives the MM, the recipient MMSC sends the notification, M-Notification.ind, to the recipient terminal B; because the notification, carrying by the short message, locates the recipient terminal B according to the MSISDN number, so that the recipient terminal B may successfully receive the notification, M-Notification.ind. sent by the recipient MMSC. 
         [0009]    In Steps  13  and  14 , when the recipient terminal B acquires the MM from the recipient MMSC, the recipient terminal B may successfully download the MM according to the address of the MMSC in the notification. 
         [0010]    In Step  15 , when the recipient terminal B succeeds in receiving the MM, the recipient terminal B sends confirmation, which is M-Acknowledge.ind in the case of the deferred retrieval or M-Notifyresp.ind in the case of immediate retrieval, to the recipient MMSC. The address of the MMSC in the confirmation is the address set on the recipient terminal B; if the address set on the recipient terminal B is wrong, the confirmation may not be able to arrive at the recipient MMSC. Because the recipient MMSC does not receive the confirmation (M-Acknowledge.ind or M-Notification.ind), the recipient terminal B is taken for failed in the MM download, which leads to the failure in the billing for the user after the MM expires, or the bill rollback during the confirmation stage of the prepaid charge. 
         [0011]    In summary, the recipient could configure the wrong address deliberately in both the terminal-to-terminal or service provider to terminal service, causing the failure of the bill in the MMSC to escape from the charge, which leads to the loss of the service provider of the MMS. 
       SUMMARY 
       [0012]    This disclosure provides an MMSC, terminal and method for processing the MM to prevent the bill evasion. 
         [0013]    Embodiments of the present invention could be realized through the following method. 
         [0014]    When the recipient terminal receives the MM, the terminal confirms with the MMSC, whether the MM has been received. The confirmation is forced to return to the MMSC address delivered by the MMSC instead of the MMSC address configured in the user terminal; in this condition, even if the recipient terminal user changes the originally configured recipient MMSC address after the new MM is received, the recipient MMSC may still charge in response to the message so as to avoid the bill evasion. 
     
    
     
       BRIEF DESCRIPTION OF THE DRAWINGS  
         [0015]      FIG. 1  is a flowchart showing an MM transferring process in the prior art; 
           [0016]      FIG. 2  is a schematic flowchart showing the MM transferring method in an embodiment of the present invention; 
           [0017]      FIG. 3  is a schematic diagram showing the MMSC and the terminal in an embodiment of the present invention. 
       
    
    
     DETAILED DESCRIPTION  
       [0018]    The MMSC receiving method of an embodiment of the present invention is that the recipient MMSC, notifies the recipient terminal to receive the MM by sending the notification carrying the MMSC address when receiving the MM; the recipient terminal requests to obtain the MM from the recipient MMSC according to the notification, and then the recipient MMSC send the MM requested to the recipient terminal; in the end, the recipient terminal confirms with the recipient MMSC whether the MM has been received according to the MMSC address delivered by the recipient MMSC. The recipient terminal is forced to return the confirmation according to the MMSC address delivered by the recipient MMSC, so that even if the recipient terminal user changes the originally configured MMSC address, the recipient MMSC may still charge according to the received response message so as to avoid the bill evasion. 
         [0019]    Additionally, it is supposed to be made clear that the MM in embodiments of the present invention, which could either be the MM sent by the originator terminal or the service provider, does not concern the essence of embodiments of the present invention and will not be detailed. 
         [0020]    The following are detailed description of embodiments. 
         [0021]      FIG. 2  is a flowchart showing the terminal-to-terminal transferring method of one embodiment. 
         [0022]    The MM is transferred between an MSUA 1  terminal and an MSUA 2  terminal. Originator MMSC is the home MMSC of MSUA 1 , and Recipient MMSC is the home MMSC of the MSUA 2 ; the MM is forwarded between the terminal and the MMSC via WAP gateway and the transferring process is as follows: 
         [0023]    Steps  201   a  and  201   b:  The terminal MSUA 1  sends the request message for MM submission (MM 1 -submit. REQ) to the accessed WAP gateway via an MM interface, carrying the sent MM; the accessed WAP gateway sends back the MM submission response message (MM 1 -Submit.RES) to the terminal MSUA 1 . 
         [0024]    Steps  202   a  and  202   b:  The accessed WAP gateway sends submission request message (C 1 -Submit. REQ) to the Originator MMSC via an MM interface, carrying the MM to be sent; the originator MMSC returns the response message of the submission request (C 1 -Submit. RES) to the WAP gateway. 
         [0025]    Steps  203   a  and  203   b:  The originator MMSC sends an MM forwarding request message (MM 4 -Forward. REQ) to the recipient MMSC, carrying the MM to be sent; the recipient MMSC sends back the response message (MM 4 -Forward.RES) of the forwarding request by the originator MMSC. 
         [0026]    Steps  204   a  and  204   b:  The recipient MMSC sends an MM notification message (C 1 -Notification. REQ) to the WAP gateway, and the WAP gateway returns the response message of the MM notification (C 1 -Notification. RES). 
         [0027]    Steps  205   a  and  205   b:  The WAP gateway sends the notification message (C 2 -Notification. REQ) to an SMSC, and the SMSC sends back the response message of the MM notification message. 
         [0028]    Steps  206   a  and  206   b:  The SMSC sends the MM notification message (MM 1 -Notification. REQ) to the recipient terminal MSUA  2 , carrying the address of the recipient MMSC; the terminal MSUA  2  sends back the response message of the MM notification message (MM 1 -Notification. RES). 
         [0029]    Steps  207   a  and  207   b:  The recipient terminal MSUA  2  sends the MM delivery request message (MM 1 -Retrieve.REQ) to the WAP gateway; then the WAP gateway delivers the MM request confirmation message (MM 1 -Retrieve.RES) to the recipient terminal MSUA  2  after the recipient MMSC sends the MM to it. 
         [0030]    Steps  208   a  and  208   b:  The WAP gateway sends the MM request message (C 1 -Retrieve. REQ) to the recipient MMSC, and the recipient MMSC sends an MM (C 1 -Retrieve. RES) to the terminal MSUA 2  via the WAP gateway. 
         [0031]    Steps  209  and  210 : The recipient terminal MSUA  2  sends the MM receive confirmation message to the recipient MMSC via the WAP gateway, using the MM address which is sent by the recipient MMSC to recipient terminal MSUA 2  via the notification message. 
         [0032]    The rest Steps from  211   a  and  21 l b  to  214   a  and  214   b  are charge triggering and returning the delivery report to the originator terminal MSUA 1 , which will not be detailed here. 
         [0033]    In the above process, the recipient terminal MSUA 2  receives the notification, MM 1 -Nofication.REQ ,indicating the arrival of the MM and carrying the recipient MMSC address sent by recipient MMSC; and the recipient MMSC address is also in the retrieval response of the MM sent by the recipient MMSC to the recipient terminal MSUA 2 ; the address is stored in the storage area which can not be modified by the user; after the user retrieves the MM, the confirmation message has to be returned to the recipient MMSC according to the stored address; in this situation, even if the user changes the originally configured address set in the recipient terminal MSUA 2  after a new MM has been received, the recipient MMSC may still execute the bill charging according to the received response message, thereby avoiding the bill evasion. 
         [0034]    Embodiments of the present invention provide an MMSC and a terminal receiving the MM delivered by the MMSC; an embodiment is shown in  FIG. 3 , and the MMSC includes: 
         [0035]    an MM receiving module, adapted to receive the MM from the originator MMSC; 
         [0036]    an MM processing module, adapted to send the MM received by the MM receiving module, etc; 
         [0037]    an MM notification module, adapted to send the MM notification carrying the recipient MMSC address to the recipient terminal when the MM receiving module receives the MM; the elements in the notification message (MM 1 -notification. REQ) notifying the recipient terminal are extended as described in table 1. The extended elements are the recipient MMSC address: 
         [0000]    
       
         
               
               
               
             
           
               
                 TABLE 1 
               
               
                   
               
               
                 Element 
                 Attribute 
                 Description 
               
               
                   
               
             
             
               
                 Message 
                 Mandatory 
                 Identifies this message as 
               
               
                 Type 
                   
                 MM1_notification.REQ 
               
               
                 Transac- 
                 Mandatory 
                 The identification of the 
               
               
                 tion ID 
                   
                 MM1_notification.REQ/MM1_notification.RES 
               
               
                   
                   
                 pair. 
               
               
                 . . . 
                 . . . 
                 . . . 
               
               
                 Recipient 
                 Optional 
                 Recipient MMSC relay/server address 
               
               
                 MMSC 
               
               
                 address 
               
               
                   
               
             
          
         
       
     
         [0038]    The configurations of the terminal receiving the MM delivered by the MMSC are: 
         [0039]    a terminal processing module, adapted to perform the processing of receiving, sending, etc. the MM; and, 
         [0040]    an MM response module, adapted to send the notification response message to the MMSC according to the MMSC address when receiving the notification message carrying the MMSC address; the extended elements in the response message are described in table 2; the extended elements are the newly added recipient MMSC address: 
         [0000]    
       
         
               
               
               
             
           
               
                 TABLE 2 
               
               
                   
               
               
                 Element 
                 Configuration 
                 Description 
               
               
                   
               
             
             
               
                 Message Type 
                 Mandatory 
                 Identifies this message as 
               
               
                   
                   
                 MM1_retrieve.RES. 
               
               
                 . . . 
                 . . . 
                 . . . 
               
               
                 Recipient MMSC 
                 Optional 
                 Recipient MMSC relay/server address 
               
               
                 address 
               
               
                   
               
             
          
         
       
     
         [0041]    In summary, the recipient MMSC carries the recipient MMSC address when notifying the recipient terminal users or delivering the MM to the recipient terminal, and then the recipient terminal stores the recipient MMSC address in the storage area which can not be modified; the recipient terminal returns the MM receiving confirmation message to the recipient MMSC according to the address, thereby avoiding the bill evasion. 
         [0042]    Additional advantages and modifications will readily occur to those skilled in the art. Therefore, the invention in its broader aspects is not limited to the specific details and representative embodiments shown and described herein. Accordingly, various modifications and variations may be made without departing from the scope of the invention as defined by the appended claims and their equivalents.