CN1302671C - Payment method for receiving multimedia short message by utilizing third side as receiving side - Google Patents

Abstract

The present invention discloses a payment method for receiving multimedia short messages by utilizing a third party as a receiving party. A third party paying agreement is signed between the third party and a value added application service provider (VASP), a carrier/operator or the receiving party. A third party account is arranged in a charging system of a carrier/operator network, and third party paying rules and correlative information are preserved. Multimedia short messages are sent to the multimedia short message service server/ a relaying server (MMS Relay/Sever) of the transmitter by a transmitter. The third party paying rules and correlative information are obtained by the MMS Relay/Sever of the transmitter. If the third party is required to be as the receiving party to receive multimedia short message pay, the multimedia short messages and the third party paying rules and correlative information are sent to the receiving party. After the receiving party receives the multimedia short messages, response messages are returned. The charging system of the carrier/operator is informed by the MMS Relay/Sever of the transmitter, and the MMS message of the time is paid by the third party. Correlative charge is subtracted from the third party account by the charging system of the carrier/operator.

Description

Method for a third party to pay for recipients to receive multimedia short messages

technical field

The present invention relates to the service payment problem in the mobile communication system, more precisely, relates to a method for a third party to pay for receiving a multimedia short message in the mobile communication system.

Background technique

Based on the second generation (2G) short message service, multimedia short message service (MMS) was introduced into the third generation mobile communication system. MMS can enable user terminals to send and receive various media forms including images, sounds, texts, animations The multimedia short message realizes the information transmission between mobile phones and mobile phones, and between mobile phones and the Internet.

For MMS, the Third Generation Partnership Project (3GPP) organization has formulated its business requirements and basic implementation framework. In the 3GPP MMS Phase 2 (TS23.140) standard, the network framework of MMS is shown in Figure 1. The interface between the MMS relay server/message server (MMSRelay/Server) 101 and the sender's MMS user agent (MMS User Agent) 102 in the figure is the MM1 interface; the interface between the MMS Relay 103 and the MMS Server 104 is the MM2 interface ; External Server (External Server) 105 can be the server that is used to send E-Mail, fax or UMS etc., the interface between MMS Relay/Server 101 and External Server 105 is MM3 interface; MMS Relay/Server 101 and different multimedia business The interface between the MMS Relay/Server 106 of environment (MMSE) is MM4 interface; The interface between MMS Relay/Server 101 and home location register (HLR) 107 is MM5 interface; MMS Relay/Server 101 and MMS subscriber database (MMS The interface between User Database) 108 is MM6 interface; the interface between MMS Relay/Server 101 and value-added application service provider (VASP) 109 is MM7 interface; the interface between MMS Relay/Server 101 and billing system (Billing System) 110 The interface between them is the MM8 interface.

If the user wants to send an MMS message, first edit it through the MMS User Agent 102, then submit or upload the edited MMS message to the MMS Relay/Server 101 through the MM1 interface, and the MMS Relay/Server 101 queries the HLR 107 for the receiver through the MM5 interface The address of the MMS Relay/Server where it is located, since the receiver can be a mobile phone user or an external server, it needs to be handled differently for different situations. For the situation that the receiving party is a mobile phone user, if the receiving party and the sending party are in MMS Relay/Server of different MMSEs, then the MMS message is sent to the MMS Relay/Server 106 where the receiving party is located through the MM4 interface, and the MMS message is sent by it through the MM1 interface The MMS message is sent to the MMS UserAgent 111 of the receiver; if the receiver and the sender are in the MMS Relay/Server of the same MMSE, the MMS message is directly sent to the MMS User Agent 111 of the receiver through the MM1 interface by the MMS Relay/Server. If the receiving party is an external server, the MMS Relay/Server where the receiving party is located sends the MMS message to the external server 105 through the MM3 interface, and then the external server 105 presents the MMS message edited by the sending end user to the receiving end user.

If VASP is used as the sender or receiver, since the interface between VASP and MMS Relay/Server is MM7, it is necessary to change the MM1 interface corresponding to the receiver in the above process to MM7 interface.

In the MMS function description stage 1 (TS22.140) standard, a third party that has a contract with a VASP, an operator, or a receiver can pay for the receiver to receive MMS messages, but in the MM1/MM7 interface, there is no requirement for the receiver how to The method of knowing that the third party has paid for itself is defined. Therefore, the receiver cannot directly know whether the received MMS message has been paid for by the third party.

Contents of the invention

In view of this, the main purpose of the present invention is to provide a method for a third party to pay for the receiver to receive MMS messages, so that when the third party pays for the receiver to receive the MMS message, the receiver can directly know whether the third party has paid for the receiver. Charges for received multimedia short messages.

In order to achieve the above object, the technical solution of the present invention is achieved in that a third party pays for receiving a multimedia short message by a third party, the method comprising the following steps:

a. The multimedia short message service (MMS) network sets and saves the rules and information of the third-party payment according to the third-party payment type, and sets the third-party account in the billing system at the same time;

b. The sender sends the multimedia short message to the sender's multimedia short message service server/relay server (MMS Relay/Sever) by submitting a request message, and the sender's MMS Relay/Sever obtains the third-party payment rules and information, and according to the rules Judging whether a third party pays for receiving the multimedia short message by the recipient, if not, then end this process, otherwise enter step c;

c. The sender's MMS Relay/Sever sends the third-party payment information and MMS message to the receiver's User Agent (UA) via the receiver's MMS Sever/Relay according to the receiver's address;

d. The sender MMS Relay/Sever notifies the sender that the MMS message has been sent, and informs the billing system that the MMS message is paid for by a third party, and the billing system deducts the relevant fees from the corresponding third party account.

Said step c further comprises:

c1. The sender's MMS Relay/Sever searches for the receiver's MMS Sever/Relay according to the receiver's address, and determines whether the sender's MMS Relay/Sever and the receiver's MMS Relay/Sever are in the same multimedia service environment (MMSE), and if so, Then go to step c3, otherwise go to step c2;

c2. The sender MMS Relay/Sever sends the third-party payment information and MMS message to the receiver UA through the receiver MMS Relay/Sever, and the receiver UA sends the message to the sender MMS Relay/Sever through the receiver MMS Relay/Sever after receiving the information Feedback message, enter step d;

c3. The sender MMS Relay/Sever directly sends the third-party payment information and MMS message to the receiver UA, and the receiver UA feeds back the message to the sender MMS Relay/Sever after receiving the information, and then enters step d.

The third-party payment information at least includes information notifying the receiver that the received MMS message is free.

The third-party payment information may further include at least a third-party identification.

The third-party payment information may further include at least third-party additional description information.

The submission request message described in step b contains third-party payment information, and the sending MMSRelay/Sever judges whether the third-party payment information in the submission request message is correct according to the obtained third-party payment rules, and if it is correct, continues to judge whether the payment is made by a third party. The receiving party receives the multimedia short message to pay; otherwise, the third-party payment information in the submission request message is set as the obtained third-party payment information, or returns a message that the third-party payment information in the submission request message is incorrect to the sender, End this process.

The third-party payment type is the payment type agreed between the third party and the operator, or the payment type agreed between the third party and the receiver, or the payment type agreed between the third party and the VASP.

The regulations and information of the third-party payment are stored in the home location register of the operator network; or in the home subscription server of the operator network; or in the MMS user database of the operator network; or in the VASP.

The sender is a mobile terminal, or a value-added application service provider (VASP).

The receiver is a mobile terminal, or a value-added application service provider (VASP).

The method of the present invention signs a third-party payment contract with the operator, the receiver or the VASP through the third party, so that when the sender sends the MMS message paid by the third party to the receiver, the operator network informs the receiver that the MMS message is free of charge through the third-party payment information. , can also let the receiver know the payer of the MMS message and the specific description information of the payer.

Description of drawings

FIG. 1 is a schematic diagram of a network framework of MMS in the prior art;

Fig. 2 is the flowchart that the present invention realizes the sending and receiving of the MMS message paid by a third party;

Fig. 3 is a sequence diagram of message flow in which a third party pays for receiving an MMS message by a receiver in the present invention.

Detailed ways

The technical solutions of the present invention will be further described in detail below in conjunction with the accompanying drawings and specific embodiments.

The method of the invention is realized based on the network framework provided by the TS23.140 standard in 3GPP, and adds the relevant information of third-party payment to the messages sent and received in the original sending and receiving MMS message processing flow.

If the third party wants to pay the receiver for receiving the MMS message sent by the specific sender, it can sign a third-party payment agreement with the operator, receiver or VASP, and ensure that the third-party account exists in the operator's billing system . If the third party has signed a third-party payment contract with the operator or the receiver, when the sender sends an MMS message to the receiver, the operator network informs the receiver that the MMS message is free, and can also pass the third party's identification information Inform the recipient who paid for the MMS message, and at the same time send the additional description information of the third party to the recipient; When sending a message, you need to inform the recipient that the MMS message is free, and you can also inform the recipient who paid for the MMS message through the identification information of the third party. At the same time, you can also send the third party’s additional description information to the recipient. Here The information obtained by the receiving party can be notified directly by the VASP or through the operator's network for the storage situation.

The rules for the third party to pay for the recipient are stipulated in the third-party payment agreement, and the relevant information is proposed or derived by the third-party payment agreement according to the rules. Since there are many possible situations for the third party to pay for the receiver, the third party and the operator sign a There are many types of third-party payment agreement rules, so according to different payment situations, the third-party payment rules and related information stored by the operator may be as follows. One is all the information received by the receiver. The rule that all MMS messages are paid by a third party and the corresponding related information, one is the rule that the receiver receives an MMS message from a specific sender and its corresponding related information is paid by a third party, and the information needs to have a specific sender The other is the rule that the receiver receives MMS from a specific sender within a specific time period to be paid by a third party and its corresponding related information. The related information requires the specific sender’s ID and time period information. The above rules are just examples, and may be a combination of the above rules, or other rules, that is, not limited to the above rules. If the operator network also informs the recipient that the MMS message is paid for by a third party, the information that the third party paid for the recipient stored by the operator also needs to include identification and description information of the third party.

The sender may be a mobile terminal or a VASP, and the mobile terminal is taken as an example below as a mobile phone user.

If the sender is a mobile terminal, the third party can sign a third-party payment contract with the operator or with the receiver, and the processing procedures for these two cases are the same. When a third party signs a third-party payment contract with the operator or the receiver, it must ensure that there is a third-party account in the operator's billing system, and the operator stores the third-party payment rules and related information in the MMS User Database or In HLR/HSS, it is used for billing and authentication.

If the sender is a VASP, the third party can sign a third-party payment contract with the VASP, operator or receiver. If the third party signs a third-party payment contract with the operator or the receiver, the two situations are similar to the process corresponding to the third party signing a third-party payment contract with the operator or receiver when the sender is a mobile phone user. In the original process, the MM1 interface corresponding to the sender is changed to the MM7 interface, and messages are sent and received through the MM7 interface.

If the third party signs a third-party payment agreement with VASP, there are rules and related information for third-party payment in VASP. It must be guaranteed that there is a third-party account in the billing system of the operator, but the third-party payment rules and related information may or may not be stored in MMS UserDatabase or HLR/HSS. If the third-party payment rules and related information are stored in the MMS User Database or HLR/HSS, the processing method is exactly the same as that of the third-party payment agreement signed by the third party with the operator or the receiver, and the third-party payment-related information is provided by the operator. The merchant network informs the receiver. If the third-party payment rules and related information are not stored in the MMS User Database or HLR/HSS, when the VASP as the sender sends an MMS message to the receiver, it needs to judge the third-party payment rules and related information based on the stored third-party payment rules and related information. Should the three parties pay for the corresponding receiver for the MMS message? If the third party should pay for the message, the VASP needs to add the third-party payment information in the message when sending the MM7_Submit_REQ message to the MMS Relay/Server where it is located, that is, The VASP tells the receiver that the MMS message is free, and can also inform the receiver who pays for the MMS message through the identification information of the third party, and can also send the third party's additional description information to the receiver. The remaining steps of this process are the same as the previous case. Similarly, if the receiver is also a VASP, it is also necessary to change the MM1 interface corresponding to the receiver to the MM7 interface, and send and receive messages through the MM7 interface.

The receiver can be a mobile terminal or a VASP. The process of sending and receiving MMS messages in these two cases is similar, the difference is that the sending and receiving of messages between the mobile terminal and the MMS Relay/Server is through the MM1 interface, and the sending and receiving of messages between the VASP and the MMS Relay/Server is through the MM7 interface . In the following, the mobile terminal is taken as a mobile phone user as an example.

Figure 2 shows the process of sending and receiving MMS messages after the third party signs a third-party payment agreement with the operator or the receiver when both the sender and the receiver are mobile phone users, corresponding to the following steps:

A. The operator stores the third-party payment rules and related information in the MMS User Database or HLR/HSS according to the third-party payment agreement.

B. The user agent (UA) of the sender submits or uploads the MMS message to be sent to the MMS Relay/Server where the sender is located through the submission request message (MM1_SUBMIT_REQ) of the MM1 interface, and the MMS Relay/Server where the sender is located sends the message to the sender The UA returns an MM1_SUBMIT_RES message, and the MM_SUBMIT_REQ message may include third-party payment information.

C. After the MMS Relay/Server where the sender is located receives the MM1_SUBMIT_REQ message, it obtains the third-party payment rules and related information from the HLR/HSS or MMS User Database.

If the third-party payment information and payment rules are stored in the HLR/HSS, obtain the third-party payment information and payment rules through the MM5 interface; if they are stored in the MMS User Database, obtain the third-party payment information and payment rules through the MM6 interface .

D. The MMS Relay/Server where the sender is located first judges whether the third party needs to pay for the receiver corresponding to the MMS message according to the obtained third-party payment information and payment rules. If not, proceed to step E. If necessary, proceed further Judging whether the recipient meets the payment rules determined by the third party, if not, then proceed to step E, and if so, then skip to step F.

If the MM1_SUBMIT_REQ message includes third-party payment information, first judge whether the third-party payment information in the MM1_SUBMIT_REQ message is correct according to the third-party payment information and payment rules obtained from the HLR/HSS or MMS User Database, and if correct, proceed to step D If it is not correct, you can update the third-party payment information in the MM1_SUBMIT_REQ message to the obtained third-party payment information, and then proceed to the judgment of step D, or return the wrong third-party payment information to the sender UA message, the sender UA resends the MMS message after receiving the message.

E. Send the MMS message according to the existing method for sending the MMS message, and end the process.

F. The MMS Relay/Server where the sender is located judges whether the receiver is in the MMS Relay/Server of the same MMSE according to the address of the receiver, if yes, then skip to step I, otherwise enter the next step.

G. The MMS Relay/Server where the sender is located sends the MM4 forward request message (MM4_FORWARD_REQ) containing the third-party payment information to the MMS Relay/Server where the receiver is located.

H. The MMS Relay/Server where the receiver is located notifies the receiver UA that there is an MMS message through the MM1_Notification_REQ message containing the third-party payment information. After receiving the MM1_Notification_REQ message, the receiver UA feeds back a notification response message (MM1_Notification_RES), and retrieves the request message through MM1 ( MM1_RETRIEVE_REQ) request to obtain the MMS message from the MMS Relay/Server where the receiver is located, and the MMS Relay/Server where the receiver is located sends the MMS message to the receiver UA through the MM1 retrieval response message (MM1_RETRIEVE_RES) containing the third-party payment information, and jumps to Go to step J.

I. The MMS Relay/Server where the sender is located informs the receiver UA that there is an MMS message through the MM1_Notification_REQ message containing the third-party payment information. After receiving the message, the receiver UA feeds back the MM1_Notification_RES message, and requests from the MMS Relay where the sender is located through the MM1_RETRIEVE_REQ message. The MMS message is obtained from the /Server, and the MMS Relay/Server where the sender is located sends the MMS message to the receiver UA through the MM1_RETRIEVE_RES message containing the third-party payment information.

J. The MMS Relay/Server where the sender is located informs the billing system that the fee for this MMS message will be paid by a third party, and the billing system deducts the relevant fee from the third-party account to complete the fee settlement for this MMS message.

As shown in Figure 3, when the sender and receiver are mobile phone users, and the sender and receiver are in the MMS Relay/Server of different MMSEs, the third party signs a third-party payment agreement with the operator and sends and receives MMS messages timing diagram.

The method of the present invention realizes that the third party pays for the receiver to receive the MMS message, and at the same time, it can ensure that the receiver knows that the received MMS message is free, and can let the receiver know the payer of the MMS message and the specific description information of the payer .

Claims (11)

1, a kind of third party is characterized in that may further comprise the steps at least for the recipient receives the method that multimedia short message is paid:

A. the rule and the information of network based third-party charging type setting of multimedia short message service MMS and preservation third-party charging are provided with third party's account simultaneously in charge system;

B. transmit leg sends to transmit leg multimedia short message service server/relay server MMS Relay/Sever by submitting request message to multimedia short message, transmit leg MMS Relay/Sever obtains the rule and the information of third-party charging, and be that the recipient receives this multimedia short message and pays whether by the third party according to rule judgment, if not, process ends then, otherwise enter step c;

C. transmit leg MMS Relay/Sever sends to recipient user agent UA via recipient MMS Sever/Relay with third-party charging information and MMS message according to the recipient address;

D. transmit leg MMS Relay/Sever notice transmit leg MMS message sends, and notifies this MMS message of charge system by third-party charging, and charge system is deducted correlative charges from corresponding third party's account.

2, method according to claim 1 is characterized in that step c further comprises:

C1. transmit leg MMS Relay/Sever is according to recipient's address search recipient MMS Sever/Relay, judge whether transmit leg MMS Relay/Sever and recipient MMS Relay/Sever are among the identical multimedia service environment MMSE, if, then enter step c3, otherwise, enter step c2;

C2. transmit leg MMS Relay/Sever sends to recipient UA with third-party charging information and MMS message by recipient MMS Relay/Sever, recipient UA passes through recipient MMS Relay/Sever to transmit leg MMS Relay/Sever feedback message after receiving information, enters steps d;

C3. transmit leg MMS Relay/Sever directly sends to recipient UA with third-party charging information and MMS message, and recipient UA receives after the information and to enter steps d then to transmit leg MMS Relay/Sever feedback message.

3, method according to claim 1 is characterized in that: described third-party charging information comprises the free information of MMS message of notifying the recipient to receive at least.

4, method according to claim 3 is characterized in that, described third-party charging information further comprises and contains third party's identification information at least.

5, method according to claim 4 is characterized in that, described third-party charging information further comprises third party's additional description information.

6, method according to claim 1, it is characterized in that: submit in the request message described in the step b and contain third-party charging information, whether send MMS Relay/Sever submits to the third-party charging information in the request message correct according to the third-party charging rule judgment of obtaining, if correct, then continuing to judge whether by the third party is that the recipient receives this multimedia short message paying; Otherwise, be the third-party charging information of being obtained with the third-party charging information setting in this submission request message.

7, method according to claim 1, it is characterized in that: submit in the request message described in the step b and contain third-party charging information, send MMS Relay/Sever and judge according to third-party charging rule of obtaining and information whether the third-party charging information of submitting in the request message is correct, if correct, then continuing to judge whether by the third party is that the recipient receives this multimedia short message paying; Otherwise, return the incorrect message of third-party charging information in the submission request message to transmit leg, finish this flow process.

8, method according to claim 1 is characterized in that: the payment type of described third-party charging type for arranging between the payment type of arranging between the payment type of arranging between third party and the operator or third party and the recipient or third party and the VASP.

9, method according to claim 1 is characterized in that: the regulation of described third-party charging and information are stored in the attaching position register of carrier network; Or be stored in the home subscribed services device of carrier network; Or be stored in the MMS customer data base of carrier network; Or be stored among the VASP.

10, method according to claim 1 is characterized in that: described transmit leg is a portable terminal, or is valued added applications service provider (VASP).

11, method according to claim 1 is characterized in that: described recipient is a portable terminal, or is valued added applications service provider (VASP).

Images