1 Advice of Charge (Information) (AoCI)

03.863GPPAdvice of Charge (AoC) supplementary servicesStage 2TS

1.1 Advice of Charge (Information) MSC SDL diagram

The SDL diagram for the Advice of Charge (Information) supplementary service within the MSC is given in figure 1.1.

NOTE 1: AoC (Information) is not applicable to emergency calls.

NOTE 2: The request of generation of the Charge Advice Information (CAI) applies to AoC initiation or charge modification.

1.2 Advice of Charge (Information) mobile equipment SDL diagram

The SDL diagram for the Advice of Charge (Information) supplementary service within the mobile equipment is given in figure 1.2. This SDL indicates when charging calculations are started, amended and stopped, within the mobile equipment. The mobile equipment should start charging calculations as soon as possible after receiving the charging information. Charging calculations should be amended by the mobile equipment in accordance with GSM 02.24.

NOTE: The point at which the charging calculations are amended can occur before or after sending the AoC Acknowledge.

Charging calculations are stopped when the call ends for any reason.

The reception of the CAI shall be acknowledged only if the MS supports the AoCI functionality specified in GSM 02.24 and GSM 02.86, however the network does not action this acknowledgement in the AoC (Information) case.

1.3 Advice of Charge (Information) information flow diagram

The Advice of Charge (Information) information flow diagrams are shown in figure 1.3.

Figure 1.1: SDL diagram of advice of charge (information) in the MSC

Figure 1.2: SDL diagram of advice of charge (information) in the mobile equipment

Figure 1.3: Information flow for Advice of Charge (Information)

1.4 Information stored in the HLR

AoCI may have the following logical states (refer to GSM 03.11 for an explanation of the notation):

Provisioning State Registration State Activation State HLR Induction State

(Not Provisioned, Not Applicable, Not Active, Not Induced)

(Provisioned, Not Applicable, Active and Operative, Not Induced)

The HLR shall store the logical state of AoCI (which shall be one of the valid states listed above) on a per subscriber basis.

1.5 State transition model

The following figure shows the successful cases of transition between the applicable logic states of AoCI. The state changes are caused by actions of the service provider.

Note that error cases are not shown in the diagram as they normally do not cause a state change. Additionally, some successful requests may not cause a state change. Hence they are not shown in the diagram.

Figure 1.4: State transition model for AoCI

1.6 Transfer of Information from HLR to VLR

If the provisioning state for AoCI is "Provisioned" then when the served subscriber registers on a VLR the HLR shall send that VLR information about the logical state of AoCI.

If the logical state of AoCI is changed while a subscriber is registered on a VLR, then the HLR shall inform the VLR of the new logical state of AoCI.

1.7 Information stored in the VLR

For the supplementary service AoCI the VLR shall store the service state information received from the HLR.

1.8 Handover

Handover will have no impact on AoC control procedure.