WO2011113397A2

WO2011113397A2 - Call callback billing method and service control equipment

Info

Publication number: WO2011113397A2
Application number: PCT/CN2011/073471
Authority: WO
Inventors: 丁鹏
Original assignee: 华为技术有限公司
Priority date: 2011-04-28
Filing date: 2011-04-28
Publication date: 2011-09-22
Also published as: WO2011113397A3; CN102217339A

Abstract

The embodiments of the present invention provide a call callback billing method and a service control equipment. Wherein, the call callback billing method includes: receiving a bridging success notification or a callee connection failure notification from a switching equipment, and recording the reception time of the bridging success notification or the called successive failure notification (102); receiving an initial billing request from the switching equipment, adjusting the session duration carried in the initial billing request according to the reception time of the bridging success notification or the called successive failure notification, and sending a billing notification containing the adjusted session duration to a billing equipment in order to enable the billing equipment to bill according to the adjusted session duration (104). The embodiments of the present invention can reduce the billing errors for the caller terminal in the Unstructured Supplementary Service Data CallBack (UCB) service effectively.

Description

Call callback charging method and service control device

The present invention relates to communication charging technologies, and in particular, to a call back call charging method and a service control device.

Background technique

UCB (based on USSD (Unstructured Supplementary Service Data) call forwarding service, USSD CallBack) is implemented by the calling terminal's HLR (Home Location Register) in response to the calling terminal initiating UCB. The call request notifies the corresponding SCP (Service Control Point) of the calling terminal's home network to establish an MT (Mobile Terminated) call for the calling terminal and the called terminal, and then bridges the two calls. To implement a call between the calling terminal and the called terminal.

In the specific implementation process of the UCB service, there is a certain error in the charging of the calling terminal. The reason is that the charging of the calling terminal often starts when the calling terminal of the calling terminal is established, but at this time, both parties The call may not have started yet. For example, if the ΜΤ call of the calling terminal is first established, and the ΜΤ call of the called terminal is started after the ΜΤ call setup of the calling terminal is completed, the calling party has started in the process of establishing the called terminal ΜΤ call. The terminal performs charging (that is, the charging for the calling terminal has started after the call setup of the calling terminal is completed), and thus will cause a problem that the charging has been generated for the calling terminal even though the call has not yet started. There is a certain degree of error in the billing of the calling terminal.

Summary of the invention

In view of the above, it is necessary to provide a call back call charging method and a service control device to solve the problem that the existing UCB service has a certain degree of error in charging the calling terminal.

According to an aspect of the present invention, a call back call charging method is provided, including: Receiving a bridging success notification or a called connection failure notification from the switching device, and recording a receiving time of the bridging success notification or the called connection failure failure notification;

Receiving an initial charging request from the switching device, and calibrating the duration of the call carried in the initial charging request based on the receiving time of the bridge success notification or the called connection failure notification, and issuing a calibration to the charging device The billing notification of the subsequent call duration, so that the billing device performs billing according to the calibrated call duration.

According to another aspect of the present invention, a service control device is provided, including:

Transceiver module

a recording module, configured to receive, by the transceiver module, a bridge success notification or a call connection failure notification from the switching device, and record the receiving time of the bridge success notification or the called connection failure notification;

a calibration module, configured to receive, by using the transceiver module, an initial charging request from the switching device, and perform, according to the bridging success notification or the receiving time of the called connection failure notification, the duration of the call carried in the initial charging request For calibration, the charging and receiving module sends a charging notification including the calibrated call duration to the charging device, so that the charging device performs charging according to the calibrated call duration.

In the embodiment of the present invention, the duration of the call carried in the initial charging request is calibrated based on the receiving time of the bridge success notification or the called connection failure notification, so as to charge the calling terminal based on the calibrated call duration. Therefore, it can be known that the charging of the calling terminal starts at the time when the bridge success notification or the called connection failure notification is received, and the MT call establishment of the calling terminal is completed, thereby effectively reducing the calling in the UCB service. The billing error of the terminal.

DRAWINGS

1 is an exemplary flowchart of a call back call charging method in accordance with a preferred embodiment of the present invention; FIG. 2 is an exemplary signaling diagram of a call back call charging method in accordance with a preferred embodiment of the present invention; An exemplary signaling diagram of a call back call charging method in accordance with another preferred embodiment of the present invention; 4 is a schematic diagram showing an exemplary logical structure of a service control device in accordance with a preferred embodiment of the present invention.

detailed description

1 is an exemplary flow diagram of a call back call charging method 100 in accordance with a preferred embodiment of the present invention.

As shown in FIG. 1, step 102, receiving a bridging success notification or a called connection failure notification from the switching device, and recording the receiving time of the bridging success notification or the called connection failure failure notification;

Step 104: Receive an initial charging request from the switching device, and calibrate the duration of the call carried in the initial charging request according to the receiving time of the bridging success notification or the called connection failure notification, and send the charging duration to the charging device. The charging notification includes the calibrated call duration, so that the charging device performs charging according to the calibrated call duration.

It is known from the technical problems existing in the prior art described in the prior art that the charging error to the calling terminal is caused by the fact that the call has not yet started but the calling terminal has been charged. In a specific implementation process, from the start of charging to the calling terminal to the call between the calling and called terminals, the charging data generated in this time interval is often the first ACR message sent by the switching device ( Apply Charging Report, Billing Request Report). Therefore, in the specific implementation process, only the duration of the call carried in the first ACR message needs to be calibrated, and the first ACR message is the initial charging request.

In a specific implementation process, the initial charging request further includes a call start time, and the calibrating the call duration in the initial charging request based on the receiving time of the bridging success notification or the called connection failure notification includes: :

Calculating the connection duration according to the call start time and the receiving time of the bridge success notification or the called connection failure notification, where

Connection duration = reception time of bridge success notification or called connection failure notification - call start time;

Calculating the calibrated call duration according to the connection duration and the duration of the call, where Call duration after calibration = call duration - connection duration.

In the specific implementation process, the bridging success notification may be successful bridging.

( PORTS — BRIDGED ) message.

In a specific implementation process, the called connection failure notification may be a Release (Rel) message.

In a specific implementation process, the charging notification is a CCR (Credit Control Request, Credit-Control-Request) message.

2 is an exemplary signaling diagram of a call back call charging method 200 in accordance with a preferred embodiment of the present invention.

As shown in FIG. 2, in step 202, after the calling terminal initiates a call back call operation, the switching device of the network where the calling terminal is currently located is the MSC (Mobile Switching Center) / VLR (Visitor Location Register). Visiting location register) Initiating a call back request to the calling terminal home HLR (Home Location Register), that is, the calling home HLR.

In the specific implementation process, the above call callback request can be implemented by using a USSD Req message. Step 204: The calling home HLR sends a call back control request to the relevant SCP in the calling home network (that is, the SCP in the calling home network that is responsible for controlling the UCB service), that is, the calling home SCP, to request the main The home SCP is called to control the call back process.

In a specific implementation process, the calling home HLR may request the calling home SCP to control the call back process by forwarding the USSD Req message to the calling home SCP, that is, the call back control request may pass the US SD Req message is implemented. Step 206: The calling home SCP sends a calling connection notification to the calling home MSC/SSP (Service Switching Point) to notify the calling home MSC/SSP to connect to the calling terminal.

Specifically, the calling home MSC/SSP is the switching device described in FIG.

In the specific implementation process, the above caller connection notification can be implemented by an ICA (Initiate Call Attempt) message.

Step 208: The calling home MSC/SSP sends a connection calling request to the calling location MSC/VLR to connect to the calling terminal.

In the specific implementation process, the foregoing caller request can be implemented by using an IAM (Initial Address Message).

Step 210: After the calling MSC/VLR successfully connects to the calling terminal, the calling MSC/SSP notifies the calling MSC/SSP that the calling party successfully connects.

In the specific implementation process, the time when the calling home MSC/SSP receives the notification of the successful connection of the calling party is the call starting time carried in the initial charging request. In addition, the calling location MSC/VLR can notify the calling home MSC/SSP of the successful connection of the calling party through the ACM (Address Complete Message).

Step 212: The calling home MSC/SSP notifies the calling home SCP that the calling party successfully connects.

In the specific implementation process, the calling home MSC/SSP can notify the calling home SCP of the successful connection by the ERB (BC Call (Basic Call State Model) Event Report, Event Report BCSM) message.

Step 214: The calling home SCP sends the called continuation notification to the calling home MSC/SSP.

In the specific implementation process, the above-mentioned called connection notification can be implemented by using an ICA message.

Step 216: The calling home MSC/SSP sends a connection called request to the called MSC/VLR. In the specific implementation process, the foregoing connection request is implemented by IAM.

Step 218: After the called MSC/VLR successfully connects to the called terminal, the MSC/SLR of the called party informs the calling MSC/SSP that the called party successfully connects.

In the specific implementation process, the called MSC/VLR can notify the calling home MSC/SSP through the ACM that the called party successfully connects.

Step 220: The calling home MSC/SSP notifies the calling home SCP that the called party successfully connects.

In the specific implementation process, the calling home MSC/SSP can notify the calling home SCP of the called party to successfully connect through the ERB message.

Step 222: The calling home attribution SCP notifies the calling home MSC/SSP to bridge the primary and called calls.

In the specific implementation process, the calling home SCP can notify the calling home MSC/SSP to bridge the primary and called calls through the BRIDGEPORTS message.

Step 224: The calling home MSC/SSP succeeds in bridging the master and the called party, and successfully reports to the calling party's home SCP.

In the specific implementation process, the above bridging success notification can be implemented by a bridging success (PORTS BRIDGED) message.

After receiving the bridging success notification from the calling home MSC/SSP, the calling home SCP records the receiving time of the bridging success notification.

Step 226: The calling home MSC/SSP sends the first ACR to the calling home SCP, where the first ACR is the initial charging request described in FIG.

Step 226: The calling home SCP reports the CCR to the Online Charging Report (OCS) according to the first ACR.

Specifically, the calling home SCP calibrates the duration of the call carried in the first ACR according to the receiving time of the bridging success notification, and sends a CCR including the calibrated call duration to the OCS, so that the OCS is based on the calibrated call duration. Performing billing, where OCS is as described in Figure 1. Billing equipment. Further, the first ACR carries a call start time, and the call start time is the time when the calling home MSC/SSP receives the notification that the calling party successfully connects in step 210. The calibration of the duration of the call carried in the first ACR according to the receiving time of the successful notification of the bridging includes:

Calculating the connection duration according to the call start time and the reception time of the bridge success notification, wherein the connection duration = the reception time of the bridge success notification - the call start time;

Calculating the calibrated call duration according to the connection duration and the duration of the call, where

Call duration after calibration = call duration - duration of connection.

The embodiment of the present invention calibrates the duration of the call carried in the initial charging request based on the receiving time of the bridging success notification, so as to charge the calling terminal based on the calibrated call duration. Therefore, it can be known that the charging for the calling terminal starts at the time when the success notification of the bridge is received, and when the calling terminal succeeds, the charging error of the calling terminal in the UCB service can be effectively reduced.

3 is an exemplary signaling diagram of a call back call charging method 300 in accordance with another preferred embodiment of the present invention.

As shown in FIG. 3, in step 302, after the calling terminal initiates a call back call operation, the switching device of the network where the calling terminal is currently located, that is, the calling location MSC/VLR initiates a call to the calling terminal home HLR, that is, the calling home HLR. Callback request.

In the specific implementation process, the above call callback request can be implemented by using a USSD Req message. Step 304: The calling home HLR sends a call back control request to the relevant SCP in the calling home network (that is, the SCP in the calling home network that is responsible for controlling the UCB service), that is, the calling home SCP, to request the main The home SCP is called to control the call back process.

In a specific implementation process, the calling home HLR may request the calling home SCP to control the call back process by forwarding the USSD Req message to the calling home SCP, that is, the call back control request may pass the US SD Req message is implemented.

Step 306: The calling home SCP sends a calling connection notification to the calling home MSC/SSP to notify the calling home MSC/SSP to connect to the calling terminal. Specifically, the calling home MSC/SSP is the switching device described in FIG. In the specific implementation process, the foregoing call forwarding notification can be implemented by using an ICA message.

Step 308: The calling home MSC/SSP sends a connection calling request to the calling location MSC/VLR to connect to the calling terminal.

In the specific implementation process, the foregoing caller request can be implemented by using IAM.

Step 310: After the calling MSC/VLR successfully connects to the calling terminal, the calling MSC/SSP notifies the calling MSC/SSP that the calling party successfully connects.

In the specific implementation process, the time when the calling home MSC/SSP receives the notification of the successful connection of the calling party is the call starting time carried in the initial charging request. In addition, the location of the caller

The MSC/VLR can notify the calling home MSC/SSP through the ACM that the calling party successfully connects.

Step 312: The calling home MSC/SSP notifies the calling home SCP that the calling party successfully connects.

In the specific implementation process, the calling home MSC/SSP can notify the calling home SCP of the successful connection by the ERB message.

Step 314: The calling home SCP sends the called continuation notification to the calling home MSC/SSP.

Step 316: The calling home MSC/SSP sends a connection called request to the called MSC/VLR.

In the specific implementation process, the foregoing connection request is implemented by IAM.

Step 318: The called MSC/VLR notifies the calling home MSC/SSP that the called party fails to succeed after the connected terminal fails (for example, the called terminal is busy or the called terminal does not answer for a long time).

In the specific implementation process, the notification that the called terminal fails to connect may be carried by a Release (Rel) message indicating that the call is required to be released.

Step 320: The calling home MSC/SSP notifies the calling home SCP that the connection is failed to be connected. In a specific implementation process, the calling home MSC/SSP may notify the calling home SCP that the calling party fails to connect through the ERB message.

After receiving the notification of the connection failure of the called originating MSC/SSP, the calling home SCP records the receiving time of the notification that the called connection fails.

Step 322: The calling home MSC/SSP sends the first ACR to the calling home SCP, where the first ACR is the initial charging request described in FIG.

Step 324: The calling home SCP reports the CCR to the Online Charging Report (OCS) according to the first ACR.

Specifically, the calling home SCP calibrates the duration of the call carried in the first ACR according to the receiving time of the notification of the connection failure, and sends a CCR containing the calibrated call duration to the OCS, so that the OCS is based on the calibration. The duration of the call is charged, and the OCS is the charging device described in FIG. Further, the first ACR carries a call start time, and the call start time is the time when the calling home MSC/SSP receives the notification of the successful connection of the call in step 310. The calibration of the duration of the call carried in the first ACR according to the receiving time of the notification of the connection failure of the called party includes:

Calculating the connection duration according to the call start time and the reception time of the notification of the called connection failure, wherein

The duration of the connection = the reception time of the notification of the connection failure failure - the call start time; the duration of the calibration call is calculated according to the connection duration and the duration of the call, wherein

Call duration after calibration = call duration - duration of connection.

In the embodiment of the present invention, the duration of the call carried in the initial charging request is calibrated based on the receiving time of the called connection failure notification, so as to charge the calling terminal based on the calibrated call duration. Therefore, it can be known that the charging for the calling terminal starts at the time when the called connection failure notification is received, and when the calling terminal fails to succeed, the charging error of the calling terminal in the UCB service can be effectively reduced.

4 is a schematic diagram showing an exemplary logical structure of a service control device 400 in accordance with a preferred embodiment of the present invention. As shown in FIG. 4, the service control device 400 includes a transceiver module 402 and a recording module 404. And calibration module 406.

The recording module 404 is configured to receive, by the transceiver module 402, a bridge success notification or a called connection failure notification from the switching device, and record a receiving time of the bridge success notification or the called connection failure notification;

The calibration module 406 is configured to receive, by the transceiver module 402, an initial charging request from the switching device, and perform a call carried in the initial charging request based on a receiving time of the bridging success notification or a called connection failure notification. The duration is calibrated, and the charging and receiving module 402 sends a charging notification including the calibrated call duration to the charging device, so that the charging device performs charging according to the calibrated call duration.

In the specific implementation process, the initial charging request also carries a call start time, and the calibration module 406 specifically includes:

a first calculating module, configured to calculate a connection duration according to the call start time and the receiving time of the bridge success notification or the called connection failure notification, where the connection duration=the bridge success notification or the reception time of the called connection failure notification- Call start time;

The second calculating module is configured to calculate, according to the connection duration and the duration of the call, the duration of the calibrated call, wherein the calibrated call duration = the duration of the call - the duration of the connection.

In a specific implementation process, the bridging success notification is a PORTS_BRIDGED message; the called connection failure failure notification is a Rel message.

In a specific implementation process, the initial charging request is an ACR message.

In a specific implementation process, the charging notification is a CCR message.

It will be apparent to those skilled in the art that all or part of the above steps may be passed through a program. The instructions are related to hardware completion, and the program can be stored in a computer readable storage medium such as a ROM, a RAM, an optical disk, or the like.

In conclusion, the above is only a preferred embodiment of the present invention and is not intended to limit the scope of the present invention. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and scope of the invention are intended to be included within the scope of the invention.

Claims

Claim

A call back call charging method, which is characterized in that:

Receiving a bridging success notification or a called connection failure notification from the switching device, and recording the receiving time of the bridging success notification or the called connection failure failure notification;

2. The call back call charging method according to claim 1, wherein the initial charging request further carries a call start time, and the receiving is based on the bridging success notification or the called connection failure notification. The calibrating the duration of the call in the initial charging request includes: calculating the connection duration according to the call start time and the receiving time of the bridge success notification or the called connection failure notification, where

Calculating the calibrated call duration according to the connection duration and the call duration, wherein the calibrated call duration = call duration - connection duration.

The call back call charging method according to claim 1 or 2, wherein the bridge success notification is a bridge success PORTS_BRIDGED message; and the called connection failure notification is a release Rel message.

The call back call charging method according to claim 3, wherein the initial charging request is an accounting request report ACR message.

The call back call charging method according to claim 4, wherein the charging notification is a credit control request CCR message.

6. A service control device, comprising:

Transceiver module a recording module, configured to receive, by the transceiver module, a bridge success notification or a called connection failure notification from the switching device, and record a receiving time of the bridge success notification or the called connection failure notification;

The service control device according to claim 6, wherein the initial charging request further includes a call start time, and the calibration module specifically includes:

The service control device according to claim 6 or 7, wherein the bridge success notification is a bridge success PORTS_BRIDGED message; and the called connection failure notification is a release Rel message.

9. The service control device according to claim 8, wherein the initial charging request is an accounting request.

The service control device according to claim 9, wherein the charging notification is a credit control request CCR message.