Abstract:
The present invention discloses a method for implementing information transfer services, including: A. generating, by a sending terminal, an address of the information to be sent, and sending, by the sending terminal, the address via a Wireless Application Protocol (WAP) short message to a receiving device of the information; and B. obtaining, by the receiving device, the information from the sending terminal according to the received address. This invention also discloses a system for implementing information transfer services and a terminal. This invention makes it possible to realize simple and low-cost information transfer services and ensures the success rate of information transfer.

Description:
FIELD OF THE INVENTION  
       [0001]     The present invention relates to the field of information transfer technique in a wireless communication system, and more particularly, to a system, method and terminal for implementing information transfer services.  
       BACKGROUND OF THE INVENTION  
       [0002]     Multimedia Message Service (MMS) is a further evolution of Short Message Service (SMS) and Enhanced Message Service (EMS), which provides an integrated end-to-end solution for personal multimedia mobile communication services. In terms of communication contents, a multimedia message may include pictures, voices, video, data, and etc.  
         [0003]     The architecture of a system for implementing an MMS, email service and Enhanced MMS (EMMS) is shown in  FIG. 1 , in which the most important entities for implementing MMS include MMS User Agents (UA) and MMS Centers (MMSC). An MMS UA is an application module at a terminal. The module may be used for browsing, editing, and processing MMS messages in addition to transferring and receiving MMS messages as an agent of a user. An MMSC has functions of an MMS relay and an MMS Server for implementing protocol transformation, content adaptation, storage, and scheduling of MMS messages, and carrying out the delivering operation of MMS messages between different multimedia devices. Besides the MMS UA and MMSC, the system may further include an MMS database, an email server, an external enhanced application server, e.g., Service Provider/Content Provider (SP/CP), Redirector, etc. The MMS database may be for storing user information, customized information, interface information, etc; the email server may be for providing email services for terminals; the SP/CP may be for providing EMMS; and the Redirector may be for redirecting MSS messages between the MSS UA and MMSC such that the terminal may be able to allocate a submitted message to the terminal&#39;s home MMSC without being configured with a fixed MMSC address.  
         [0004]     A flowchart for implementing an MMS service in the related art is shown in  FIG. 2 . Supposing that the sending terminal is terminal  1  and the receiving terminal is terminal  3 , the flowchart includes the following specific steps:  
         [0005]     Step  201 : after constructing an MMS message, terminal  1  sends the constructed MMS message to its home MMSC via an M-Send.req message.  
         [0006]     Step  202 : after the MMSC to which terminal  1  belongs receives the MMS message, it returns an M-Send.conf message to terminal  1  so as to confirm that this MMS message has been received;  
         [0007]     Step  203 : the MMSC to which terminal  1  belongs transfers the MMS message to an MMSC of the receiving party, i.e., the MMSC to which terminal  3  belongs, via an MM4-Forward.req message.  
         [0008]     Step  204 : after the MMSC to which terminal  3  belongs receives this MMS message, it returns an MM4-Forward.res message to the MMSC to which terminal  1  belongs so as to confirm that the message has been received;  
         [0009]     Step  205 : the MMSC to which terminal  3  belongs sends to terminal  3  an M-Notification.ind message in a form of a short message;  
         [0010]     Step  206 : after terminal  3  receives the M-Notification.ind message, it returns an M-NotifyResp.ind message to the MMSC which terminal  3  belongs to;  
         [0011]     Step  207 : a while later, terminal  3  confirms that the MMS message has been received, and then sends a Get.req message to the MMSC which terminal  3  belongs to;  
         [0012]     Step  208 : after receiving the Get.req message, the MMSC to which terminal  3  belongs delivers the corresponding message to terminal  3  via an M-Retrieve.conf message;  
         [0013]     Step  209 : after downloading the MMS message successfully, terminal  3  sends its home MMSC an M-Acknowledge.ind message so as to inform the MMSC that the download of this MMS message is done;  
         [0014]     Step  210 : after the MMSC to which terminal  3  belongs receives the M-Acknowledge.ind message sent by terminal  3 , the MMSC sends an MM4-DeliverReport.req message to the MMSC terminal  1  belongs to, informing the MMSC that terminal  3  has received the MMS message;  
         [0015]     Step  211 : the MMSC to which terminal  1  belongs sends an MM4-DeliverReport.res message to the MMSC which terminal  3  belongs to, confirming that it has received a Delivery Report and notifying that it has learned that terminal  3  has received the MMS message;  
         [0016]     Step  212 : the MMSC to which terminal  1  belongs sends an M-Delivery.ind message to terminal  1 , notifying terminal  1  that terminal  3  has accomplished receiving the MMS message.  
         [0017]     Like the transferring method of the MMS, when a terminal sends an email to an email server or an EMMS message to an SP/CP, it is necessary in the related art to send the email or EMMS message to an MMSC first, and then the MMSC sends the email or EMMS message to the corresponding email server or SP/CP.  
         [0018]     As seen from the foregoing schemes, in the related art process of a terminal implementing the information transfer services such as the MMS, email service, and EMMS, the information has to be forwarded by an MMSC. So each MMSC has to transfer such a large amount of information that each MMSC is required to have more powerful processing abilities, which increases the system costs for implementing MMS services. If the network needs to accommodate large numbers of subscribers, it is necessary to set up more MMSCs to satisfy the demands, which leads to a big waste of devices;  
       SUMMARY  
       [0019]     The present invention discloses a method for implementing information transfer services, including:  
         [0020]     A. generating, by a sending terminal, an address of the information to be sent, and sending, by the sending terminal, the address via a Wireless Application Protocol (WAP) short message to a receiving device of the information; and  
         [0021]     B. obtaining, by the receiving device, the information from the sending terminal according to the received address.  
         [0022]     The present invention further discloses a system for implementing information transfer services, including:  
         [0023]     a sending terminal, configured to generate an address of the information to be sent, and send this address to a receiving device via a WAP short message;  
         [0024]     a WAP network gateway, configured to transfer information between the sending terminal and the receiving device, and  
         [0025]     a receiving device, configured to, receive the WAP short message from the sending terminal, and obtain the information via the WAP network gateway from the sending terminal according to the address contained in the WAP short message.  
         [0026]     The present invention further discloses a terminal, including:  
         [0027]     an Point-to-Point MMS UA module, configured to, browse, edit, and process information, generate an address of the information to be sent, output this address through a WAP PUSH short message to a WAP interface module; and  
         [0028]     a WAP interface module, configured to establish a connection between Point-to-Point MMS UA module and a WAP network gateway, and send the WAP PUSH short message to a receiving device via the WAP network gateway. 
     
    
     BRIEF DESCRIPTION OF THE DRAWINGS  
       [0029]     The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate the invention and together with the description, and serve to explain the principles of the invention.  
         [0030]     In the drawings,  FIG. 1  is an architecture map of a system for implementing an MMS service, email service, and EMMS in the related art;  
         [0031]      FIG. 2  is a flowchart of implementing the MMS service in the related art;  
         [0032]      FIG. 3  is a general flowchart of a method for implementing information transfer services according to a preferred embodiment of the present invention;  
         [0033]      FIG. 4  is an architecture map for implementing MMS services according to a preferred embodiment of the invention;  
         [0034]      FIG. 5  is a flowchart of implementing MMS services according to an preferred embodiment of the invention;  
         [0035]      FIG. 6  is a flowchart of implementing email services according to an preferred embodiment of the invention; and  
         [0036]      FIG. 7  is a flowchart of implementing EMMS according to a preferred embodiment of the invention. 
     
    
     DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS  
       [0037]     To make the objective, technique schemes and advantages of this invention clearer, this invention is further described in detail hereinafter with reference to the accompanying drawings.  
         [0038]     An embodiment of the invention is that, a sending terminal generates an address for information which is to be sent and sends the address to a receiving device of the information via a Wireless Application Protocol PUSH (WAP PUSH) short message, and then the receiving device obtains the information from the sending terminal according to the received address. In this way, an information transfer service is realized.  
         [0039]     The general flowchart of a method for implementing information transfer services according to a preferred embodiment of the present invention is shown in  FIG. 3 . The method includes the following steps:  
         [0040]     Step  301 : a sending terminal generates an address for information which is to be sent, and sends this address to a receiving device of the information via a WAP PUSH short message.  
         [0041]     Step  302 : the receiving device obtains the information from the sending terminal according to the received address.  
         [0042]     Detailed descriptions of this invention are provided by embodiments as follows.  
         [0043]     As shown in  FIG. 4 , architecture of a system for implementing an MMS service, mail service, and EMMS in an embodiment of this invention includes: terminal  1 , terminal  2 , terminal  3 , wireless networks, WAP network gateways, an IP network, a mail server, and an SP/CP.  
         [0044]     Terminal  1  contains a point-to-point (P2P) MMS UA module and a WAP interface module. The P2P MMS UA module can be for providing functions of browsing, editing, and processing MMS for users, sending an M-Notification.ind message to terminal  2 , and sending an MMS message to terminal  2  after receiving a Get.req message sent by terminal  2 . The method of the P2P MMS UA module providing functions of browsing, editing, and processing MMS for users may be the same as the one in the related art. The WAP interface module may be for establishing a connection with a WAP network gateway so that the P2P MMS UA module may exchange information with the WAP network gateway via the established connection.  
         [0045]     Terminal  2  may be either a terminal containing a P2P MMS UA module or the same terminal as the one in the related art, and it may be for receiving an MMS message from terminal  1  via the WAP network gateway after receiving an M-Notification.ind message from terminal  1 .  
         [0046]     The wireless network, WAP network gateway, and IP network are for providing network services for terminal  1  and/or terminal  2 , and for transferring messages between terminal  1  and terminal  2 .  
         [0047]     The email server and SP/CP are for getting the corresponding information according to the address contained in the WAP PUSH short message sent by a terminal.  
         [0048]     In the foregoing system, the procedure of terminal  1  sending an MMS message to terminal  2  is shown in  FIG. 5 . As the messages exchanged between terminal  1  and terminal  2  are first sent to the WAP network gateway by the sending terminal via the wireless network, then sent to the receiving terminal by the WAP network gateway via the wireless network gateway. Moreover, the realization of transferring information between terminals via the wireless network and WAP network gateway may be the same as that in the related art, so for brevity, the message exchanging between terminals via the wireless network and WAP network gateway in the following steps are directly described by the interaction between the terminals while the process of the wireless network and WAP network gateway is omitted. The procedure includes the following steps:  
         [0049]     Step  501 : after receiving a P2P MMS request from a user, the P2P MMS UA module of terminal  1  generates an address for an MMS message which is to be sent, includes this address in an M-Notification.ind message in a format of a WAP PUSH short message, and then sends this message to terminal  2  via a WAP interface module.  
         [0050]     In this step, generating an address for the MMS message which is to be sent refers to generating a link address of an M-Notification.ind message in a form of WAP PUSH, wherein the link address may be expressed as a Content Location, etc. In addition, the link address may be generated automatically according to the IP address allocated by the network side which may be obtained by the WAP interface module and the identifier of the MMS to be sent by a user which is configured on a terminal, e.g., HTTP://10.11.22.33:8080/12345, wherein HTTP://10.11.22.33 is the IP address of the terminal sending the MMS, 8080 refers to an interception port, and 12345 is the identifier of the MMS message configured on terminal  1 .  
         [0051]     In addition, in this step, if there are abundant IP resources in the network where terminal  1  is located, it is possible to make the terminal on line permanently. For instance, in an IPV6 network, as terminal  1  may own an IP address without application, its Hypertext Transfer Protocol (HTTP) service interception may start directly, and thus this step may be performed directly. However, if it is needed to allocate resources dynamically in the network where terminal  1  is located, e.g., in a GPRS network, before generating an M-Notification.ind message, terminal  1  needs to send a request for activating a GPRS context to the network side via a WAP interface first; and after the network side receives the request for activating a GPRS context, it opens a data network channel for terminal  1 , activates a GPRS context, allocates an IP address for terminal  1 , then sends the IP address to the WAP interface module in terminal  1 , and after allocating an interception port, the WAP interface module in terminal  1  starts an HTTP interception on this IP address.  
         [0052]     Step  502 : after receiving the M-Notification.ind message sent by terminal  1 , terminal  2  sends a Get.req message to terminal  1  according to the link address included in the M-Notification.ind message, such as a Content Location.  
         [0053]     Step  503 : after the P2P MMS UA module of terminal  1  receives the Get.req message from terminal  2  on the HTTP interception port via the WAP interface module, it reads the corresponding MMS message, encapsulates this MMS message into MMS Packet Data Units, and sends an M-Retrieve.conf message as the text of an HTTP response to terminal  2  via the WAP interface module.  
         [0054]     In step  503 , if the network where terminal  1  is located needs to allocate IP address resources dynamically, after finishing sending the MMS message, the WAP interface module in terminal  1  needs to disconnect the HTTP data link, deactivate the data link, and release the network resources such as the IP address etc. Since there is a confirmation mechanism for the reception of data packages in the Transportation Control Protocol (TCP) of the HTTP, after the WAP interface module makes sure that terminal  2  has finished receiving data packages based on the confirmation mechanism, it is confirmed that terminal  2  has finished sending the MMS message.  
         [0055]     In this embodiment, information server addresses may be set in a P2P MMS UA module as well, thus terminal  1  may be able to receive MMS messages from a related art terminal, of which the specific implementing procedure is the same as the flowchart shown in  FIG. 2 , so it is not necessary here to give a further description about this procedure.  
         [0056]     In this embodiment, the terminal with a P2P MMS UA module may also implement sending emails to an email server or EMMS messages to an SP/CP. The procedures of terminal  3  in  FIG. 4  sending an email to an email server and sending an EMMS message to an SP/CP are illustrated in  FIG. 6  and  FIG. 7 , respectively.  FIG. 6  is a flow chart of implementing email services in an embodiment of this invention. As shown in  FIG. 6 , the procedure of terminal  3  sending an email to an email server includes:  
         [0057]     Step  601 : after receiving a user request for sending an email, the P2P MMS UA module of terminal  3  generates a WAP PUSH short message which contains an address of an email to be sent, and sends the short message to the corresponding email server via a wireless network and WAP network gateway. Similar to Step  501 , the address of the email mentioned in this step includes: an IP address and interception port of terminal  3 , and an identifier of this email configured on terminal  3 .  
         [0058]     Step  602 : after receiving this WAP PUSH short message, the email server sends a request for getting an email to terminal  3  via the WAP network gateway and wireless network in turn according to the address included in this WAP PUSH short message.  
         [0059]     Step  603 : after receiving the request for getting an email from the email server, terminal  3  encapsulates the corresponding email into Packet Data Units, and then sends the Packet Data Units to the email server via the wireless network and WAP network gateway in turn.  
         [0060]      FIG. 7  is a flow chart of implementing EMMS in an embodiment of the invention. As shown in  FIG. 7 , the procedure of terminal  3  sending an EMMS message to an SP/CP includes:  
         [0061]     Step  701 : after receiving a user request for sending information to an SP/CP, the P2P MMS UA module of terminal  3  generates a WAP PUSH short message which contains an address of information to be sent, and sends this short message to the corresponding SP/CP via a wireless network and WAP network gateway. Similar to Step  501  and Step  601 , the address of the information mentioned above contains: an IP address and interception port of terminal  3 , and an identifier of the information to be sent configured on terminal  3 .  
         [0062]     Step  702 : after receiving the WAP PUSH short message, the SP/CP sends to terminal  3  a request for getting information via the WAP network gateway and wireless network according to the address of the information contained in the WAP PUSH short message.  
         [0063]     Step  703 : after receiving the request for getting information sent by the SP/CP, terminal  3  carries out Simple Object Access Protocol (SOAP) encoding for the information to be sent by a user to the SP/CP in a format of an MM7-Submit.req message, i.e., encapsulates this information into data of a SOAP encode format supported by the MM7 interface, and then sends the SOAP encode information to the corresponding SP/CP via the wireless network and WAP network gateway.  
         [0064]     The foregoing is a description of embodiments of this invention. Proper modifications may be conducted on the method during specific implementations of this invention so as to accommodate the needs of specific situations. Therefore, it is easy to understand that the embodiments based upon the invention are for demonstrations rather than for limiting the protection scope of the invention.