2 Advice of Charge (Charging) (AoCC)
24.0863GPPAdvice of Charge (AoC) supplementary servicesRelease 17Stage 3TS
2.1 Normal operation with successful outcome
On every successful request for an applicable telecommunications service, the served MS will be provided with charging information.
The network sends the Charge Advice Information (CAI) to the MS according to 3GPP TS 22.024, 3GPP TS 22.086 and 3GPP TS 23.086. With this information the MS is able to calculate the units associated with the requested service in real time. In the case where the served mobile is to be charged for multi party calls, separate processes within the MS are used to calculate units appropriate to each call. For unit calculation, each call is treated in the same way as a normal "two-party" call. Any change in the charging rate during a call may be indicated to the MS.
2.1.1 Call re-establishment
When the MS detects a radio link failure, the Chargeable Duration (CDUR) shall be suspended.
If a call re-establishment procedure is attempted, the MS shall resume the CDUR when:
– an MM connection has been successfully completed; and
– a TCH has been successfully seized in the appropriate mode.
2.1.2 MS originated call
For an MS originated call, charging information is transferred to the MS as shown in figure 2.1. The charging information is acknowledged in a FACILITY message only if the MS supports the AoCC functionality specified in 3GPP TS 22.024 and 3GPP TS 22.086. AoCC refers to the Advice of Charge (Charging) service.
MS Network
SETUP
————————————————————————————————————————>
etc.
CONNECT/FACILITY
<————————————————————————————————————————
Facility (Invoke = ForwardChargeAdvice (AoCC, ChargingInformation))
FACILITY/DISCONNECT
————————————————————————————————————————>
Facility (Return result)
Figure 2.1: Notification to the served mobile subscriber of the charging information
in case of an originated call set up
2.1.3 MS terminated call
For an MS terminated call, where required, charging information is transferred to the MS as shown in figure 2.2. The charging information is acknowledged only if the MS supports the AoCC functionality specified in 3GPP TS 22.024 and 3GPP TS 22.086.
MS Network
CONNECT
————————————————————————————————————————>
FACILITY
<————————————————————————————————————————
Facility (Invoke = ForwardChargeAdvice (AoCC, ChargingInformation))
FACILITY/DISCONNECT
————————————————————————————————————————>
Facility (Return result)
Figure 2.2: Notification to the served mobile subscriber of the charging information
in case of a terminated call set up
2.1.4 Change of charging information
To inform the MS of a change in charging information the procedure of figure 2.3 is performed. The charging information is acknowledged only if the MS supports the AoCC functionality specified in 3GPP TS 22.024 and 3GPP TS 22.086.
MS Network
FACILITY
<————————————————————————————————————————
Facility (Invoke = ForwardChargeAdvice (AoCC, ChargingInformation))
FACILITY/DISCONNECT
————————————————————————————————————————>
Facility (Return result)
Figure 2.3: Notification to the served mobile subscriber of a change in the charging information
2.2 Normal operation with unsuccessful outcome
If timer T(AoC) (see 3GPP TS 23.086) expires before the Charge Advice Information is acknowledged, the network shall release the call. The MS and network shall act in accordance with 3GPP TS 24.008 network initiated call clearing procedures (see figure 2.4).
MS Network
DISCONNECT/RELEASE/RELEASE COMPLETE
<————————————————————————————————————————
….Cause #69 (Requested facility not implemented)….
Figure 2.4: Network release due to unsuccessful operation of Advice of Charge (Charging) service
2.3 Accumulated Call Meter is equal to or greater than ACMmax
If the change stored in the Accumulated Call Meter (ACM) is equal to or greater than the maximum value specified by ACMmax, then the MS shall initiate call clearing giving a specific cause value for this situation as indicated in figure 2.5.
MS Network
DISCONNECT
————————————————————————————————————————>
….Cause #68 (ACM equal to or greater than ACMmax)….
Figure 2.5: Mobile station releases the call due to ACM being equal to or greater than ACMmax
2.4 Activation, deactivation and invocation
Activation, deactivation and invocation of the Advice of Charge (Charging) supplementary service are not applicable.
2.5 Interrogation, registration and erasure
Interrogation, registration and erasure of the Advice of Charge (Charging) supplementary service are not applicable.
Annex A (informative):
Change history
|
Change history |
|||||||
|
Date |
Meeting |
TDoc |
CR |
Rev |
Cat |
Subject/Comment |
New version |
|
Apr 1999 |
Transferred to 3GPP CN1 |
||||||
|
CN#03 |
Approved at CN#03 |
3.0.0 |
|||||
|
CN#11 |
Release 4 after CN#11 |
4.0.0 |
|||||
|
CN#16 |
References updated |
4.0.1 |
|||||
|
CN#16 |
Release 5 created after CN#16 |
5.0.0 |
|||||
|
CN#26 |
Release 6 created after CN#26 |
6.0.0 |
|||||
|
CT#36 |
Upgraded unchanged from Rel-6 |
7.0.0 |
|||||
|
CT#42 |
Upgraded unchanged from Rel-7 |
8.0.0 |
|||||
|
2009-12 |
Update to Rel-9 version (MCC) |
9.0.0 |
|||||
|
2011-03 |
Update to Rel-10 version (MCC) |
10.0.0 |
|||||
|
2012-09 |
Update to Rel-11 version (MCC) |
11.0.0 |
|||||
|
2014-09 |
Update to Rel-12 version (MCC) |
12.0.0 |
|||||
|
2015-12 |
Update to Rel-13 version (MCC) |
13.0.0 |
|||||
|
2017-03 |
Update to Rel-14 version (MCC) |
14.0.0 |
|||||
|
2018-06 |
Update to Rel-15 version (MCC) |
15.0.0 |
|||||
|
2020-07 |
Update to Rel-16 version (MCC) |
16.0.0 |
|||||
|
2022-03 |
– |
– |
– |
– |
– |
Update to Rel-17 version (MCC) |
17.0.0 |