KR20060130939A - Instant message billing method and system - Google Patents

Abstract

An IM(Instant Message) charging method and a system thereof are provided to enable a terminal which performs IM communication to give qualifications for IM charging exemption to another terminal, so that the terminal can charge for an IM service of another terminal, thus the IM service of another terminal is automatically charged to the terminal. A random one of plural terminals is set to a target terminal for charging for an IM service, and the other terminal is set to a target terminal exempted from the IM service(101,103). During IM communication between the random terminal and the other terminal, an IM service charging process occurring by the other terminal is charged to the random terminal(105-113). If a charging rejection request is received from one of the terminals, the setup of the target terminals is canceled(111,115).

Description

INSTANT MESSAGE BILLING METHOD AND SYSTEM

1 is a diagram showing a configuration of an instant messaging service system to which the present invention is applied;

2 is a diagram illustrating an operation flow of an instant message (IM) server according to an embodiment of the present invention.

2A is a diagram illustrating an operation flow of an IM server according to a process in which an arbitrary terminal requests a charging burden of another user terminal according to an embodiment of the present invention.

FIG. 2B is a diagram illustrating an operation flow of an IM server according to a process in which an arbitrary terminal requests another user terminal to charge his / her account according to one embodiment of the present invention; FIG.

3 is a diagram illustrating a flow of a transaction when an IM charging request is made according to an embodiment of the present invention;

4 is a view showing a transaction flow when notification of subject to IM charging exemption according to an embodiment of the present invention;

5 is a diagram illustrating a transaction flow when an IM charging request is requested according to an embodiment of the present invention;

6 is a diagram illustrating a transaction flow when notifying an IM charging burden target person according to an embodiment of the present invention;

7 is a diagram illustrating a transaction flow when an IM charging charge rejection request is performed according to an embodiment of the present invention;

8 is a view showing a flow of a transaction upon notification of chargeback of IM charging according to an embodiment of the present invention;

9 is a diagram illustrating an operation flow of an IM server when a system inquiry request is made according to an embodiment of the present invention;

10 is a view showing a transaction flow when an entitlement list request according to an embodiment of the present invention;

11 is a view showing a transaction flow when requesting an entitlement subscription list according to one embodiment of the present invention;

12 is a view showing a transaction flow when a billing history request of a specific terminal according to an embodiment of the present invention;

13 is a diagram illustrating a transaction flow according to a billing process according to an embodiment of the present invention.

TECHNICAL FIELD The present invention relates to an instant messaging service, in which a messaging service can be provided as a premium service, and more particularly, to a method and system that bears the charges incurred as an instant messaging service is executed.

In a conventional instant messaging service, an instant message (hereinafter, referred to as "IM") user must bear communication charges for IM transmitted from his terminal. That is, when user A and user B communicate with each other, both user A and user B are required to bear IM charging from the instant messaging service provider. However, there may be a case where one of two users A wants to pay user B's IM billing for user B by placing a value on user B's relationship in IM communication with user B. In this case, there is currently no service that can automatically meet the needs of users. In other words, given the current requirements of the billing system, User A is cumbersome because he has no choice but to attempt to reimburse User B's IM charges directly while presenting the actual receipts from the instant messaging service provider. It's not good.

In addition, since an individual user of the terminal performing IM communication bears his own billing, instant message communication with another user may not be possible even when the user's credit status cannot be charged. Accordingly, the service provider may lose the income opportunity, and the problem is that the recovery of the already charged fee is not smooth.

It is an object of the present invention to provide a method and system for charging IM for an instant messaging service, in which one user of terminals performing instant message communication can bear the IM charging for another communication terminal.

An object of the present invention is to provide an IM charging method and system that can increase the traffic flow of instant messages.

An object of the present invention is to provide an IM charging method and system that can increase the revenue of an instant messaging service provider.

The present invention for achieving the above object, the first process of setting any terminal of the plurality of terminals as the instant message billing target terminal, the other terminal as the instant message charging exemption target terminal, and the arbitrary terminal And a second process of charging an instant message charge generated by the other terminal during the instant message communication between the terminal and the other terminal.

In addition, the present invention sets a plurality of terminals, any terminal of the plurality of terminals as the instant message charging target terminal, another terminal as an instant message charging exemption target terminal, the arbitrary terminal and the other terminal And an instant message server for charging an instant message charge generated by the other terminal in the instant message communication between the arbitrary terminals.

Hereinafter, exemplary embodiments of the present invention will be described in detail with reference to the accompanying drawings. Note that the same components in the drawings are represented by the same reference numerals and symbols as much as possible even though they are shown in different drawings. In addition, in describing the present invention, when it is determined that a detailed description of a related known function or configuration may unnecessarily obscure the subject matter of the present invention, the detailed description thereof will be omitted.

According to the present invention, an IM that is generated due to the counterpart terminal is provided by a terminal performing an instant message communication (“IM”) according to an instant messaging service. You pay the bill instead. The IM charging is a charging generated by performing an instant messaging service. The IM charging exemption qualification status and status are notified to other communication terminals in a timely manner, and users of both communication terminals can clearly understand the IM charging burden agreement. The user of the communication terminal granting the IM charging exemption eligibility or receiving the IM charging exemption may retrieve the charge exemption burden details at any time.

Referring to Fig. 1, an instant messaging service system to which the present invention described above is applied will be described. 1 is a diagram showing a configuration of an instant messaging service system to which the present invention is applied. Referring to FIG. 1, an instant messaging service system includes an instant message server (hereinafter referred to as an “IM server”) 40, a mobile communication network 30, and a plurality of mobile communication terminals 10, 20. ).

The mobile communication network 40 supports a general mobile communication service to a mobile communication terminal existing in a service area.

The plurality of mobile communication terminals 10 and 20 are first mobile communication terminals (hereinafter referred to as "first terminals") 10 and second mobile communication terminals (hereinafter referred to as "second terminals"). It includes. The first terminal 10 and the second terminal 20 is connected to the mobile communication network 30, performs a mobile communication, performing the instant messaging service provided by the IM server 40 in accordance with the present invention It is possible. In the embodiment of the present invention, the first terminal 10 and the second terminal 20 perform IM communication according to an instant messaging service.

Although not illustrated, the first terminal 10 and the second terminal 20 include a controller, a transmitter, a receiver, and a display. According to an embodiment of the present invention, the controller sets the charge exemption target terminal and the charge exemption request information according to a user request, and sets the charge exemption target setting cancellation request information for the charge exemption target terminal. The transmitter transmits the request information to the IM server 40 under the control of the controller. The receiving unit receives a notification from the IM server 40 that the terminal is set as a charging exemption target terminal. The display unit displays the notification contents under the control of a controller when it is notified that the terminal is set as the exemption target terminal or displays the notification contents when the terminal for exempt charging is canceled.

The IM server 40 is a server that provides an instant messaging service to mobile communication terminals connected to the mobile communication network 30 through the mobile communication network 30, and processes instant messages transmitted and received between any mobile communication terminal. Then, billing generated by IM transmission and reception is processed according to the present invention.

In the instant messaging service system configured as described above, the process of processing the billing according to the present invention is as follows. First, an arbitrary terminal transmits an IM charging burden request to the IM server 40 that he / she will bear the IM charging of the counterpart terminal which will perform the IM communication. Upon receiving the IM charging burden request, the IM server 40 checks whether the user of the arbitrary terminal has the IM charging capability, and sets the IM charging burden target if the IM charging capability is available. And granting a charge exemption qualification to the counterpart terminal and notifying the arbitrary terminal that the charge exemption qualification has been successfully performed. Thereafter, the IM server 40 notifies the counterpart terminal of being set as an IM charging exemption target. The arbitrary terminal bears the IM charging generated by the counterpart terminal according to the IM communication between the arbitrary terminal and the counterpart terminal.

The above process may be performed when the arbitrary terminal and the counterpart terminal log in to the IM server 40 to perform IM communication, or may be performed after the login process is completed.

In addition, the arbitrary terminal may stop the IM charging burden of the counterpart terminal. This is possible by the arbitrary terminal sending the charge rejection request to the IM server 40. That is, when receiving the charge rejection request from any terminal, the IM server 40 releases the IM charge burden target person set in the arbitrary terminal, and withdraws the IM charging exemption qualification granted to the counterpart terminal. This informs each terminal of this.

The charge rejection request may be made by the counterpart terminal. That is, when the user of the counterpart terminal no longer wishes the user of the arbitrary terminal to bear the IM charging, by sending the charge rejection request to the IM server 40, the normal charging process is performed. can do. When the counterpart terminal is notified that the IM charging exemption target is set by the IM server 40, the counterpart terminal may reject the IM charging exemption target by transmitting the charge rejection request.

According to an embodiment of the present invention, the arbitrary terminal may request the counterpart terminal to bear its own IM charging. That is, the arbitrary terminal transmits an IM charging burden solicitation request to the IM server 40 inviting the counterpart terminal to charge its own IM charging. Upon receiving the IM charging burden solicitation request, the IM server 40 sets the counterpart terminal as an IM charging burden target by confirming the charging capability and grants an IM charging exemption qualification to the arbitrary terminal. . Thereafter, the IM server 40 notifies the arbitrary terminal that the IM charging exemption target is set. The counterpart terminal bears the IM charging generated by the counterpart terminal according to the IM communication between the arbitrary terminal and the counterpart terminal.

The above process may be performed when the arbitrary terminal and the counterpart terminal log in to the IM server 40 to perform IM communication, or may be performed after the login process is completed.

Rejection of the counterpart terminal to bear the IM charging of an arbitrary terminal is made through the charging rejection request, as described above.

2 shows an operation process of the IM server 40 according to the IM charging process performed as described above. FIG. 2 is a flowchart illustrating an operation of an IM server according to an embodiment of the present invention. FIG. 2A illustrates an IM server according to a process in which an arbitrary terminal requests charging of another user terminal according to an embodiment of the present invention. 2B is a diagram illustrating an operation flow of FIG. 2B is a diagram illustrating an operation flow of an IM server according to a process in which an arbitrary terminal requests another user terminal to charge its own billing according to an embodiment of the present invention. 3 to 8 illustrate a flow of a transaction according to an embodiment of the present invention. FIG. 3 is a diagram illustrating a flow of a transaction when an IM charging fee is requested according to an embodiment of the present invention. In accordance with an embodiment of the present invention IM transaction exemption subject notification is a diagram illustrating a transaction flow. FIG. 5 is a diagram illustrating a transaction flow when an IM charging request is requested according to an embodiment of the present invention, and FIG. 6 is a diagram illustrating a transaction flow when an IM charging person is notified according to an embodiment of the present invention. 7 is a diagram illustrating a transaction flow when an IM charging charge rejection request is performed according to an embodiment of the present invention, and FIG. 8 is a diagram illustrating a transaction flow when IM charging charge rejection notification is performed according to an embodiment of the present invention.

Hereinafter, referring to FIGS. 1 to 8, an operation process of the IM server 40 according to the present invention in the process of performing IM communication between the first terminal 10 and the second terminal 20, and each process Describe the transaction used. In one embodiment of the present invention, the first terminal 10 is a terminal requesting an IM charging burden or an IM charging burden recommendation, and the second terminal 20 is connected to the request of the first terminal 10. Accordingly, the terminal is set to be eligible for IM charging exemption or set as an IM charging burden subject by being granted IM charging exemption.

Referring to FIG. 2A, in step 101, if an IM server 40 receives an IM charging fee request for another user terminal to be IM communication target from any terminal, the IM server 40 proceeds to step 103. Proceeds to ① and proceeds to step 201 of Figure 2b. At this time, the IM charging request for the other user terminal is made by transmitting a charging charge request message (Charge_Authorization_Request Message) of the charge exemption qualification transaction (Charge_Authorization_Transaction). The charge exemption entitlement transaction consists of a charge request message and a charge charge request response message (Charge_Authorization_Status Message). The charge burden request message is configured as shown in Table 1 below.

Field types Field description Message_type = CARQ Primitive message type Transaction Id Transaction identifier Session Id Instant messaging session identifier User Id Charge Waiver Identifier

* .CARQ-Charge Authorization Request

In step 101, the IM server 40 that receives the IM charging burden request for the other user terminal through the charging entitlement transaction, the ID of the other user terminal, that is, the ID included in the user ID field of Table 1 in step 103. Check the validity of the. In addition, the accounting capability of the IM accounting burden requester is checked, and if the accounting capability is available, the IM billing requester is set as a billing target. The charging capacity can be confirmed through, for example, inquiry of credit information of the IM charging requester. Thereafter, the IM charging exemption is granted to another user terminal, and the charging exemption target is set, and the process proceeds to step 105. In step 105, the IM server 40 transmits the charging request request response message indicating that the IM charging request has been successfully sent to the terminal requesting the IM charging request, and transmits the IM charging request request response to step 107. .

At this time, the charge burden request response message is made as shown in Table 2.

Field types Field description Message_type = status Primitive message type Transaction Id Transaction identifier Session Id Instant messaging session identifier User Id Charge Waiver Identifier result Show billing request results

The result field of the charge request request message is a field indicating a result of the charge request. If the IM charge requester does not have the charge payability in step 103, the charge request failed in the result field of the charge request request message. The meaning is attached. And a service error is also indicated by the IM server 40 in the result field. Some examples of service errors include unknown user identifiers, unsupported services, and denied services. If the IM charging burden request fails due to the service error or the like, steps 109 to 117 below are not performed.

3 illustrates a transaction flow between the IM charging request terminal and the IM server 40 in steps 101 to 105. When the first terminal 10 is a terminal requesting to charge the IM charging of the second terminal 20, as shown in FIG. 3, the first terminal 10 sends a charging charge request message (Charge_Authorization_Request Message). In step 301, the data is transmitted to the IM server 40. The IM server 40 performs the same operation as in step 103 of FIG. 2A and transmits a charging charge request response message (Charge_Authorization_Status Message) to the first terminal 10 in step 303.

2A, the IM server 40 notifies the other user terminal that the charge exemption target is set in step 107 after step 105 and proceeds to step 109. In step 109, the IM server 40 receives a charge exemption subject notification response from another user terminal and proceeds to step 111.

Steps 109 to 111 are performed through a charge exemption notification transaction (Charge_Authorization_Notification_Transaction). The charge exemption notification transaction includes a charge exemption subject set notification message (Charge _Authorization_Notification Message) and the charge exemption subject notification message (Charge _Authorization_Notification_Status Message). The charge exemption subject setting notification message is made as shown in Table 3 below.

Field types Field description Message_type = CANRQ Primitive message type Transaction Id Transaction identifier Session Id Instant messaging session identifier User Id Charged Person Identifier

* .CANRQ-Charge Authorization Notification Request

The charge exemption subject notification message is made as shown in Table 4 below.

Field types Field description Message_type = status Primitive message type Transaction Id Transaction identifier Session Id Instant messaging session identifier User Id Charged Person Identifier result Show results of requesting notification of rate eligibility

The result field of the billing exempt person notification response message includes a status code and a description.

4 illustrates a transaction flow between the IM server 40 and the other user terminal in steps 107 to 109. When the first terminal 10 is a terminal requesting the IM charging of the second terminal 20, as shown in FIG. 4, the IM server 40 notifies that the charging exemption target is set in step 311. The charging exemption subject set notification message (Charge _Authorization_Notification Message) is transmitted to the second terminal (20). The second terminal 20 transmits the charge exemption subject notification message (Charge _Authorization_Notification_Status Message) to the IM server 40 in step 313 in response to the charge exemption subject setting notification message.

2A, the IM server 40 determines whether there is a chargeback denial request from the billing target terminal or the billing exemption target terminal in step 111 after step 109, and if there is no chargeback rejection request, in step 113. Proceed. In step 113, the IM server 40 bears the charges generated by the billing exemption subject to the billing burden subject according to the IM communication, and proceeds to step 111 above.

The chargeback rejection request is possible from both sides of the chargeable terminal or the chargeable terminal, and substantially cancels the charging exempt state of the terminal. If the chargeback denial is requested from the chargeback target terminal, it means that the other terminal will not be charged the charge, and if received from the chargeback target terminal, it means that it is not necessary to bear the charge instead. . Therefore, the chargeback denial request may be requested in the initial meaning of the chargeback agreement process, or may be requested to normalize the chargeback process after a certain chargeback process is performed. And the chargeback denial request may be made by the IM server (40). For example, the IM server 40 treats the chargeback denial request as if the charge status of the terminal user who is in charge of the IM charging of another user terminal can no longer be charged.

Meanwhile, in step 111, the IM server 40 proceeds to step 115 when a chargeback denial request is made from the chargeable target terminal or the charge-exempt target terminal. In step 115, the IM server 40 revokes the IM charge waiver eligibility of the person who is subject to the charge waiver, transmits a chargeback rejection request response, and proceeds to step 117.

The process according to step 111 and step 115 is performed through a charge exemption eligibility transaction (Charge_Unauthorization_Transaction). The charge exemption eligibility transaction includes a charge charge reject request message (Charge_ Unauthorization_Request message) and a charge charge reject request message (Charge_ Unauthorization_status Message). The configuration of the chargeback denial request message is shown in Table 5 below.

Field types Field description Message_type = CURQ Primitive message type Transaction Id Transaction identifier Session Id Instant messaging session identifier Outgoing User Id Charged Person Identifier Incoming User Id Charge Waiver Identifier

* .CURQ-Charge_ Unauthorization_Request

The configuration of the chargeback denial request response message is shown in Table 6 below.

Field types Field description Message_type = status Primitive message type Transaction Id Transaction identifier Session Id Instant messaging session identifier User Id Charge Waiver Identifier result Show chargeback request

The service error is indicated by the IM server 40 in the result field. Some examples of service errors include unknown user identifiers, unsupported services, denied services, and so on. If, for the same reason as the service error, the charge reject request fails, step 117 is not performed.

7 illustrates a flow of transactions between the chargeback denial request terminal and the IM server 40 in step 111 and step 115. When the first terminal 10 is a terminal requesting to bear the IM charge of the second terminal 20, and the second terminal 20 rejects the charge exemption qualification, as shown in FIG. The terminal 20 transmits a charging charge reject request message (Charge_Unauthorization_Request Message) to the IM server 40 in step 341. In step 343, the IM server 40 transmits a charge charge reject request request message (Charge_Unauthorization_status Message) to the second terminal 20 in response to the charge charge reject request message.

Returning to FIG. 2A, in step 117, the IM server 40 receives the chargeback rejection notification response from the chargeback charge requester and the chargeback charge requester, and terminates the operation process. The charging charge rejection notification is transmitted to the counterpart terminal of the terminal requesting the charging charge rejection.

The process according to step 117 is performed through a charge_unauthorization_notification_transaction. The charging charge rejection notification transaction includes a charging charge rejection notification message (Charge_Unauthorization_ Notification_Request Message) and a charging charge rejection notification response message (Charge_Unauthorization_ Notification_status Message). The chargeback denial notification message is made as shown in Table 7 below.

Field types Field description Message_type = CUNRQ Primitive message type Transaction Id Transaction identifier Session Id Instant messaging session identifier Outgoing User Id Chargeback Charge Requester Identifier Incoming User Id Charge Waiver Identifier

* .CUNRQ-Charge Unauthorization Notification_Request

The called user Id field of the chargeback denial notification message includes an identifier of a chargeable subject when the chargeback rejection requester is the IM server 40.

The charging charge rejection notification response message is made as shown in Table 8.

Field types Field description Message_type = status Primitive message type Transaction Id Transaction identifier Session Id Instant messaging session identifier User Id Chargeback Charge Requester Identifier result Charge burden denial notice result

8 illustrates a transaction flow between the IM server 40 and the counterpart terminal of the terminal requesting the chargeback denial in step 117. The first terminal 10 is a terminal requesting to bear the IM charge of the second terminal 20, and when the second terminal 20 rejects the charge exemption eligibility to notify the first terminal 10 of the above. As illustrated in FIG. 8, in step 351, the IM server 40 transmits a chargeback rejection notification message (Charge_Unauthorization_ Notification_Request Message) to the first terminal 10. The first terminal 10 transmits a charging charge rejection notification response message (Charge_Unauthorization_ Notification_status Message) to the IM server 40 in step 353.

On the other hand, if the IM server 40 of Figure 2a does not receive the IM charging burden request in step 101 proceeds to ①, in step 201 of Figure 2b any terminal will bear the IM charging to other user terminal Verify that a request to invite a request has been received. As a result of the check, the IM server 40 proceeds to step 203 when the IM charging burden solicitation request is received from the other user terminal. In step 203, the IM server 40 checks the ID validity and the charging capability of the other user terminal, sets the other user terminal as the IM charging burden target, grants the charge exemption to the IM charging burden requestor, and then applies the charge exemption target. Set and proceed to step 205. In step 205, the IM server 40 transmits a response to the IM charging burden solicitation request to any terminal, and proceeds to step 207.

Steps 201 and 205 are performed through a charging burden solicitation transaction (Charge_ Subscription_Transaction). The charging charge solicitation transaction includes a charging charge solicitation request message (Charge_Subscription_Request Message) and a charging charge solicitation request response message (Charge_Subscription_Status Message). The charging burden solicitation request message is configured as shown in Table 9 below.

Field types Field description Message_type = CSRQ Primitive message type Transaction Id Transaction identifier Session Id Instant messaging session identifier User Id Charged Person Identifier

*. CSRQ-Charge Subscription Request

The charging burden request request response message is made as shown in Table 10 below.

Field types Field description Message_type = status Primitive message type Transaction Id Transaction identifier Session Id Instant messaging session identifier User Id  Charged Person Identifier result Charge burden solicitation request result

The result field of the charging burden request request response message is a field indicating a result of the charging burden solicitation request. If the IM charge burden target person has no charge burden capability in step 203, a charge burden request is made in the result field of the charging burden solicitation request response message. Attached to indicate that this failed. And a service error is also indicated by the IM server 40 in the result field. Some examples of service errors include unknown user identifiers, unsupported services, and denied services. If the reason for charging the charge request, such as the service error, fails, steps 207 to 209 are not performed.

5 illustrates a transaction flow between the IM charging burden request terminal and the IM server 40 in steps 201 to 205. When the first terminal 10 is a terminal requesting the second terminal 20 to charge its own IM charging, as shown in FIG. 5, the first terminal 10 may include a charging request request message ( Charge_Subscription_Request message) is transmitted to the IM server 40 in step 321. The IM server 40 performs the same operation as in step 203 of FIG. 2B, and transmits a charging burden solicitation request response message (Charge_Subscription_Status Message) to the first terminal 10 in step 323.

Returning to FIG. 2B, the IM server 40 notifies the other user terminal of being set as the IM charging burden target in step 207 and proceeds to step 209. In step 209, the IM server 40 receives the IM charge burden subject notification response, proceeds to step ③, and proceeds to step 111 of FIG. 2A to perform steps 111 to 117.

The process of steps 207 to 209 is performed through a charge_subscription_Notification_Transaction. The billing party notification transaction includes a billing party notification message (Charge_SubscriptionRequest_Notification_Message) and a billing party notification message (Charge_SubscriptionRequest_Notification_Status Message). The chargeable subject notification message is made as shown in Table 11 below.

Field types Field description Message_type = CSNRQ Primitive message type Transaction Id Transaction identifier Session Id Instant messaging session identifier User Id Charge Waiver Identifier

*. CSNRQ-Charge SubscriptionRequest Notification Request

The charging burden subject notification message is made as shown in Table 12 below.

Field types Field description Message_type = Status Primitive message type Transaction Id Transaction identifier Session Id Instant messaging session identifier User Id Charge Waiver Identifier result Charge burden person notice result

6 illustrates a transaction flow between the IM server 40 and the other user terminal in steps 207 to 209. When the first terminal 10 is a terminal requesting the second terminal 20 to pay its own IM charge, as shown in FIG. 6, the IM server 40 is set as a chargeable target in step 331. In order to be notified, a charging charge subject set notification message (Charge_Subscription_Notification Message) is transmitted to the second terminal 20. The second terminal 20 transmits the chargeable subject notification message (Charge_Subscription_Notification_Status Message) to the IM server 40 in step 333 in response to the chargeable subject setup notification message.

According to the above process, when an arbitrary terminal performs IM communication with another user terminal, it may be required to bear the IM charging caused by the other user terminal, or to request the other user terminal to pay its own IM charging, and receive its own charge. The user terminal may be burdened. And according to an embodiment of the present invention, the terminals can query the IM charging details. For example, if the IM server 40 requests the list of the subjects who have granted the charge exemption qualification to any terminal, the list of the subjects to which the arbitrary terminal has granted the charge exemption, and the billing details for the specific terminal, the IM server 40 40 searches for the list and provides it to the requesting terminal. This is shown in FIG. 9 is a diagram illustrating an operation flow of the IM server 40 when a system inquiry request is performed according to an embodiment of the present invention.

Referring to FIG. 9, when a system inquiry request is received from an arbitrary terminal in step 401, the IM server 40 analyzes the received system inquiry request and proceeds to step 403 or 405 or 407 according to its type. The system inquiry request is a request for providing information related to the IM charging details. The IM server 40 proceeds to step 403 if the system inquiry request received in step 401 is a list of other user terminals to which the arbitrary terminal has granted a charge exemption, that is, a charge exemption qualification list request. In step 403, the IM server 40 searches for and provides a list of subjects to which the requester has granted the charge exemption so far, and ends the operation process. Through the above process, any terminal may identify another user terminal currently paying for IM charging instead.

This process is performed through a charge exemption authorization list request transaction (Charge_Authorization_List_Request_Transaction) according to an embodiment of the present invention. The charge exemption entitlement list request transaction includes a charge exemption entitlement list request message (Charge_AuthList_Request Message) and a charge exemption entitlement list request response message (Charge_AuthList_Response Message). The charging exemption qualification list request message is configured as shown in Table 13 below.

Field types Field description Message_type = CALRQ Primitive message type Transaction Id Transaction identifier Session Id Session identifier Maximum entitlement list Maximum number allowed for charge exemption entitlement list: 0-show all List index Index from where to retrieve billing waiver entitlement list for maximum number

 * .CALRQ-Charge Authorization List Request

The charging exemption qualification list request response message is configured as shown in Table 14 below.

Field types Field description Message_type = CALRP Primitive message type Transaction Id Transaction identifier Session Id Session identifier Entitlement_list List of Eligible Eligible Persons

* .CALRP-Charge Authorization List Response

A service error for the transaction occurs when the service is either unsupported or rejected.

10 illustrates a transaction flow between the IM server 40 and an arbitrary terminal in steps 401 to 403. When the first terminal 10 is a terminal requesting the IM server 40 for a list of other user terminals entitled to the charge exemption, as shown in FIG. 10, the first terminal 10 is charged at step 361. The authorization list request message (Charge_AuthList_Request Message) is transmitted to the IM server 40. The IM server 40 searches for the target list to which the first terminal 10 has granted the charge exemption so far and includes it in the charge exemption entitlement list request response message (Charge_AuthList_Response Message). To send).

9, if the system inquiry request received in step 401 is a list of other user terminals that have granted the charge exemption qualification to the arbitrary terminal, that is, a billing subscription list request, 405. Proceed to step. In step 405, the IM server 40 searches for and provides a list of subjects to which the requester has been entitled to exemption of charging so far and ends the operation process. Through the above process, any terminal may identify another user terminal currently paying its own IM charging instead.

This process is performed through a charging subscription list request transaction (Charge_Subscription_List_Request_Transaction) according to an embodiment of the present invention. The billing subscription list request transaction includes a billing subscription list request message (Charge_SubscriptionList_Request Message) and a billing subscription list request response message (Charge_SubscriptionList_Response Message). The subscription list request message is configured as shown in Table 15 below.

Field types Field description Message_type = CSLRQ Primitive message type Transaction Id Transaction identifier Session Id Session identifier Max_subscription_list Maximum number allowed for subscription list: 0–show all List index Index from where to retrieve subscription list for maximum number

 * .CSLRQ-Charge Subscription List Request

The charging subscription list request response message is configured as shown in Table 16 below.

Field types Field description Message_type = CSLRP Primitive message type Transaction Id Transaction identifier Session Id Session identifier Subscription_List List of people who have qualified the requester

* .CSLRP-Charge Subscription List Response

A service error for the transaction occurs when the service is either unsupported or rejected.

11 illustrates a transaction flow between the IM server 40 and an arbitrary terminal in steps 401 and 405. As shown in FIG. 11, when the first terminal 10 requests the IM server 40 for a list of other user terminals that have granted the charge exemption, the first terminal 10 proceeds to step 371. Billing Subscription List Request

The message (Charge_SubscriptionList_Request Message) is transmitted to the IM server 40. The IM server 40 requests the billing subscription list by searching the list of subjects to which the first terminal 10 is entitled to the charge exemption so far.

The message is included in the response message (Charge_SubscriptionList_Response Message), and is transmitted to the first terminal 10 in step 373.

On the other hand, returning to FIG. 9, the IM server 40, if the system inquiry request received in step 401 is a request for the IM billing details of a specific terminal among other user terminals that any terminal bears the charging, step 407. Proceed to In step 407, the IM server 40 retrieves and provides an IM charging history list for the specific terminal and ends the operation process.

This process is performed through a charge details request transaction (Charge_Detail_Request_Transaction) according to an embodiment of the present invention. The charge details request transaction includes a charge details request message (Charge_Detail_Request Message) and a charge details request response message (Charge_Detail_Response Message). The charging history request message is configured as shown in Table 17 below.

Field types Field description Message_type = CDRQ Primitive message type Transaction Id Transaction identifier Session Id Session identifier User Id Charge Waiver Identifier

 * .CDRQ-Charge Detail Request

The charging details request response message is configured as shown in Table 18 below.

Field types Field description Message_type = CDRP Primitive message type Transaction Id Transaction identifier Session Id Session identifier User Id Charge Waiver Identifier Price breakdown Pricing history for current billing waiver entitlement session

* .CDRP-Charge Detail Response

A service error for the transaction occurs when the service is either unsupported or rejected.

12 illustrates a transaction flow between the IM server 40 and an arbitrary terminal in steps 401 and 407. When the first terminal 10 requests the IM server 40 for the IM charging details related to a specific terminal among other user terminals entitled to the charge exemption, as shown in FIG. 12, the first terminal 10 In step 381, the charge details request message (Charge_Detail_Request Message) is transmitted to the IM server 40. The IM server 40 retrieves the IM charging details of the specific terminal from the first terminal 10 and includes it in the charging details request response message (Charge_Detail_Response Message), and transmits it to the first terminal 10 in step 383.

As described above, the user may retrieve the IM charging details according to the present invention.

In the above description of the present invention, specific embodiments have been described, but various modifications may be made without departing from the scope of the present invention. For example, in the above-described embodiment, the present invention has been described in the case of operating in a proactive environment which is set in advance so as to always allow a billing request of another user, but may be configured to operate in a reactive environment. The proactive environment is an environment in which an arbitrary user terminal requests an IM charging burden of the opposite terminal, a charge exemption qualification is granted to the opposite terminal without any other consent process of the opposite terminal, and the arbitrary terminal is set as a charge burden target. . The reactive environment is an environment requiring permission of a corresponding terminal to request an IM charging burden of an arbitrary terminal. That is, in the reactive mode, when an arbitrary terminal requests an IM charging burden of the counterpart terminal, the counterpart exemption qualification is granted to the counterpart terminal by granting that the counterpart terminal bears its IM billing. The arbitrary terminal is set as the charging burden target terminal. Accordingly, the agreement process of the counterpart terminal may be additionally configured when the IM charge burden request is made, and a corresponding transaction may be configured. It is also possible to use the transaction described above.

Therefore, the scope of the present invention should not be defined by the described embodiments, but should be determined by the equivalent of claims and claims.

As described above, according to the present invention, the terminal performing the instant message communication according to the instant messaging service grants the partner terminal an eligibility of the IM charging exemption, so that the partner automatically bears the IM charging generated by the counterpart terminal. The terminal may be charged, and the IM service provider may generate more income. In addition, even if the user of any one terminal lacks the charging capability, IM communication can be made possible by the communication counterpart burdening the IM charging instead.

Claims (28)

In the instant messaging billing method of the instant messaging system, A first process of setting an arbitrary terminal among a plurality of terminals as an instant message charging target terminal and setting another terminal as an instant message charging exemption target terminal; And a second process of charging an instant message charge generated by said another terminal to said arbitrary terminal during instant message communication between said arbitrary terminal and said other terminal. 2. The method of claim 1, further comprising: canceling a charging charge target setting of the arbitrary terminal and an instant message charging exemption setting of the other terminal when receiving a chargeback denial request from any one of the arbitrary terminal and the other terminal. Further comprising three steps. The method according to claim 2, wherein if there is a request for charging entitlement list from any one of the arbitrary terminal and the other terminal, the fourth process of providing a list of terminals for which one of the terminals has exempted the instant message charging up to now; And further comprising. The method of claim 2, wherein if there is a billing subscription list request from any one of the terminal and the other terminal, a fifth process of providing a list of terminals exempt from charging the instant message of the terminal until now. Method further comprising a. According to claim 2, If any one of the terminal and the other terminal of the terminal has any one of the terminal exempted from the instant message charge, if there is a charge history request of the specific terminal, Instant messaging charge history of the specific terminal The method further comprises a sixth process for providing. The terminal of claim 1, wherein the first process sets the one terminal as the instant message charging target terminal according to the request for the burden of the instant message charging generated by the other terminal of the one terminal, and sets the other terminal. The instant message charging exemption target terminal characterized in that the process of setting. The method of claim 6, wherein the first process is A first step of the one terminal requesting a burden for the instant message charging generated by the other terminal; And a second step of setting one terminal as an instant message charging target terminal and setting another terminal as an instant message charging exemption terminal if the one terminal has a charging capability according to the request. How to. The method of claim 7, wherein the first process further comprises a third step of notifying the other terminal that the terminal has been set as a charge exemption target. The terminal of claim 1, wherein the first process requests the other terminal to bear the instant message charging generated by the other terminal, and thus, the terminal is transferred to the instant message charging target terminal. And setting another terminal as an instant message exemption target terminal. The method of claim 9, wherein the first process A first step of requesting, by the other terminal, the one terminal to bear the instant message charging generated by the other terminal; A second step of setting one terminal as an instant message charging burden terminal and setting another terminal as an instant message charging exemption terminal if the one terminal has a charging capability according to the request. Way. The method of claim 10, wherein the first process further comprises a third step of notifying the other terminal that the terminal has been set as a charge exemption target. In the instant messaging billing system of the instant messaging system, A plurality of terminals, Set any one of the plurality of terminals as an instant message charging target terminal, set another terminal as an instant message charging exempt target terminal, and when the instant message communication between the arbitrary terminal and the other terminal by the other terminal And an instant message server, which charges an instant message charge generated to the arbitrary terminal. The method of claim 12, wherein the instant message server receives a chargeback denial request from any one of the arbitrary terminal and the other terminal, the chargeback target setting of the arbitrary terminal and the instant message charging exemption target of the other terminal. A system characterized by canceling the setting. The method of claim 13, wherein the instant message server provides a list of terminals to which one terminal has exempted from charging instant messages if there is a request for charging entitlement list from any one of the terminal and the other terminal. System characterized in that. The terminal of claim 13, wherein the instant message server is configured to list a list of terminals exempted from charging an instant message of any one terminal if a charging subscription list request is received from any one of the terminal and the other terminal. Providing a system. The method of claim 13, wherein the instant message server is further configured to request the billing history of a specific terminal from among any one of the terminal and the other terminal, from which one terminal is exempted from charging the instant message. The system characterized in that it provides an instant message charge history of the terminal. The mobile terminal of claim 12, wherein the instant message server sets the one terminal as an instant message charging target terminal according to the request for the burden of the instant message charging generated by the other terminal of the one terminal, and sets the other terminal. Instant message billing exemption target terminal system characterized in that it is set. The terminal of claim 12, wherein the instant message server requests the one terminal to bear the instant message charges generated by the other terminal, and thus, the one terminal to the instant message charging target terminal. And setting another terminal as an instant message exemption target terminal. The system as claimed in claim 12, wherein the instant message server notifies the other terminal that the terminal is configured to be charged for exemption. What is claimed is: 1. A method of charging an instant message by a mobile terminal in an instant messaging system. Setting a terminal subject to charge exemption; Transmitting a signal including information on the target terminal and charge exemption request information to an instant message server; The method of claim 20, further comprising: transmitting a signal including information for canceling the charge exemption target setting to the server when the target terminal is the charge target exemption terminal. 21. The method of claim 20, further comprising the step of displaying the notification when the notification has been set as the terminal to be charged for exemption. 22. The method of claim 21, further comprising the step of displaying the contents of the notification when notified that the charge exemption target setting has been cancelled. A mobile terminal for paying instant messages in an instant messaging system, A controller for setting a charge exemption target terminal and charge exemption request information; The mobile terminal comprising a transmitting unit for transmitting the request information. The mobile terminal of claim 24, wherein the controller sets request information for canceling the charge exemption target setting for the charge exemption target terminal. The mobile terminal of claim 24, further comprising a receiver configured to be notified that the target terminal is set as a charging exemption target terminal. The mobile terminal of claim 24, further comprising a display unit which displays the contents of the notification when the target terminal is informed that the target terminal is set as a charging exemption target terminal. The mobile terminal of claim 25, further comprising a display unit which displays the notification contents when the terminal to be charged for exemption has been informed that the setting for charging to be exempted is cancelled.

Images