Professional Documents
Culture Documents
Charging Management by SCP
Charging Management by SCP
Charging Management by SCP
7.1
© Alcatel University - 8AS 90200 0746 VT ZZA Ed.01
▼ Program
Page
▼ Description 7.3
▼ Call duration management 7.5
▼ Management of AoC data 7.10
▼ SCP charging information to be included in the CDR 7.13
▼ Request information concerning the call at the end of the call 7.16
▼ Data structure 7.19
7.2
Description
7.3
© Alcatel University - 8AS 90200 0746 VT ZZA Ed.01
7.4
7.5
© Alcatel University - 8AS 90200 0746 VT ZZA Ed.01
▼ For each call segment, the SCP supplies the MSC(RCP), via the "Apply
Charging" message, with the following mandatory parameters:
z AchBillingChargingCharacteristics, which contains the following information:
– Segment duration: mandatory parameter: TimeDurationCharging /
MaxCallDurationPeriod (Tcp).
– Behaviour of call handling on expiry of this time: call release or wait for
new instructions from the SCP: optional parameter:
TimeDurationCharging / ReleaseIfDurationExceeded:
' If the call handling behaviour on expiry of this time is "release call",
the tone which should be sent before the release (within a time
delay defined by a PLMN parameter at the
RCP [TONE_INSERT_TIME]: by default 30 s), to notify the
subscriber of the imminent end of the call.
– Time to next change of tariff: optional parameter:
TimeDurationCharging / TariffSwitchInterval (TSW).
z PartyToCharge, which identifies the leg to be charged (leg1 by default).
7.6
▼ MaxCallDurationPeriod (Tcp):
z that is, the time for which a call can progress before the Apply_Charging_Report message must be sent to the SCF.
z This period starts either on response (Call answering), or immediately the preceding leg is completed.
▼ ReleaseIfDurationExceeded:
z this information indicates the action that must be taken by GSM_SSF when the period expires:
Î if the parameter is present, it indicates the tone to be sent before release to alert the subscriber (n seconds
(PLMN data) before MaxCallDuration expires):
ª to the called part in the TC case (at the GMSC).
ª to the calling part in the OC case (at the VMSC).
Î and the call is released.
Î otherwise, the call continues!
▼ TariffSwitchInterval (TSW):
z this parameter indicates to the GSM_SSF, the interval expressed in seconds until the next change of tariff:
Î on an OC call, if "ApplyCharging" was received during the call and depending on options F-CA-013 and F-CA-
020, this information is stored in the CDR on each change.
▼ TimeIfNoTariffSwitch:
z in the case where no change of tariff has occurred since answer.
z it is expressed in units of 100 ms since receipt of the answer.
▼ TimeIfTariffSwitch:
z TimeSinceLastTariffSwitch:
Î in the case where a change of tariff has occurred either via the called part or via an IP during a temporary
connection.
Î expressed in units of 100 ms since detection of the last tariff.
z TimeSwitchInterval:
Î only if a change has occurred during the current leg or during a temporary connection
Î expressed in units of 100 ms between:
ª detection of answer and the last change of tariff.
ª detection of the second last and last changes of tariff.
7.8
Tcp1 duration of
Tcp1 and TSW2 until tariff 2 Called party
segment 1
TSI 11 answer
< Change of tariff
TSI 21
TSI 21 TSI 11 TSI 22
Key:
Tcp2 of next segment TSI 23
Tcp2 duration
of segment 2
Apply Charging
TSI 22
TSI 24 Tariff 2
Apply Charging
of segment 3
Tcp3 and TSW3 until tariff 3 Report
Tcp3 dur.
TSI 23 TSW3
of segment 4
Tcp4 of next segment < Change of tariff
Tcp4 dur.
7.9
7.10
© Alcatel University - 8AS 90200 0746 VT ZZA Ed.01
▼ If subscriber does not have the AOC service, the SCI message is disregarded.
▼ Depending on functional options F-CA-013 and F-CA-020, this data can be stored
in the CDR on each change of tariff.
7.11
▼ AoC management for subscribers of approved PLMNs is offered when option F_AOC_001 "AoC function" has been enabled
in the PLMN (PLMN data initialised from the commissioning MPI).
▼ The RCP has a number of tables (operational data modifiable by operator command) to generate the AoC data:
z one table (see FEX PMROAM) defines the charging elements E"i" for each authorised PLMN ("j") and for each basic
service ("k") used. This table is created using the CREPMN command. Five Ei are managed:
Î E1 represents the number of charge units to be charged within the period,
Î E2 represents the period,
Î E3 represents a multiplying factor to convert units of the visited PLMN into units of the home PLMN,
Î E4 represents the number of charge units to be charged at the start of a call,
Î E7 represents the initial period.
z E3 is defined in the RCP tables for terminating and originating calls.
z The other Ei elements are defined in the RCP tables for terminating calls, calculated on the basis of information
received from the SSP for originating calls.
▼ The RCP therefore contains a set of values Ei(j,k), E1(2,5), typically representing the number of charge units to be allocated
within the period when the visited PLMN is PLMN nº2 and when the basic service used is bearer service nº 5.
z A table (see FEX PMRERAB) defines the charging area linked to a given cell. This table is created using the
CREREV command.
z A table (see FEX PMROAM) defines the charging category according to the category of mobile, the PLMN allowed
and the bearer or teleservice used. This table is created using the CREPMN command.
RCF
SSP SCF
OCH_MSC GSM_SSF
SET-UP
DP_O_COLLECTED_INFO
INITIAL_DP
APPLY_CHARGING (Tcp1, TSW2)
ALERTING
TSW2
ANM EVENT (ANM)
DP_O_ANSWER
REPORT_EVENT_BCSM
CONTINUE
CONNECT (ej parameters) Int_CONTINUE
CONNECT_ACK
FACILITY TSI 11
FACILITY (ek parameters)
FACILITY
TSI 21
Tcp 1
TARIFF 2
7.12
7.13
© Alcatel University - 8AS 90200 0746 VT ZZA Ed.01
▼ The RCP can receive from the SCP, in the same dialogue, up to two FCI
messages concerning two different legs of the call.
▼ Similarly, the RCP can receive, for the same leg, two FCI messages concerning
two different dialogues (activation of a T_CSI service and of an O_CSI service).
▼ At the end of the call, this field is stored unchanged by the RCP in the CDRs with
no check.
▼ The RCP can therefore store, at the end of the call, up to four FCI information
elements in its CDR.
7.14
RCF
SSP SCF
OCH_MSC GSM_SSF
SET-UP
DP_O_COLLECTED_INFO
INITIAL_DP
FURNISH_CHARGING_INFORMATION
REQUEST_REPORT_BCSM_EVENT
CONNECT
Int_CONNECT
IAM CREATE
ALERTING
CONNECT
CONNECT_ACK
REL EVENT (REL)
FURNISH_CHARGING_INFORMATION
DP_O_DISCONNECT
REPORT_EVENT_BCSM
RELEASE_CALL
Int_RELEASE
REL FREE
7.15
7.16
© Alcatel University - 8AS 90200 0746 VT ZZA Ed.01
▼ This request can be made independently for the calling part and the called
part.
7.17
RCF
SSP SCF
OCH_MSC GSM_SSF
SET-UP
DP_O_COLLECTED_INFO
INITIAL_DP
CALL_INFORMATION_REQUEST (LegID=Called)
REQUEST_REPORT_BCSM_EVENT
CONNECT
Int_CONNECT
IAM CREATE
CONNECT_ACK
REL EVENT (REL)
DP_O_DISCONNECT
CALL_INFORMATION_REPORT
REPORT_EVENT_BCSM
CALL_INFORMATION_REQUEST (LegID=Called)
CONNECT
Int_CONNECT
IAM CREATE
7.18
Data structure
7.19
© Alcatel University - 8AS 90200 0746 VT ZZA Ed.01
▼ F-CA-013 enables CAMEL phase 2 information to be stored in the CDR in CAMEL phase 2
specific fields.
▼ Field values:
z TRUE: The CAMEL phase 2 specific information is stored in the call data records in
the CAMEL phase 2 fields.
– This option is meaningful only if the CAMEL phase 2 service is offered, that is,
if the functional option F-CA-012 is set to TRUE, which means that the CAMEL
phase 1 service is also offered, that is, that functional option F-CA-001 is set
to TRUE.
z FALSE: Even if the CAMEL phase 2 service is offered, that is, if F-CA-012 is set to
TRUE, the CAMEL phase 2 specific information is not stored in the call data records
in the CAMEL phase 2 specific fields.
– However, the CAMEL phase 2 information restricted in CAMEL phase 1 is
placed in the CAMEL phase 1 specific fields if option F-CA-023 is set to TRUE
or no CAMEL phase 2 information is placed in the call data record if F-CA-023
is set to FALSE.
7.20
▼ F-CA-014 is used to place in the call data record the information received from the SCP
CAMEL server in the FCI (Furnish Charging Information) operation.
▼ Field values:
z TRUE: The information received from the SCP CAMEL server in the FCI operation is
placed in the call data record by the RCP.
– This option is meaningful only if the CAMEL phase 2 service is offered, that is,
if option F-CA-012 is set to TRUE, and the CAMEL phase 2 specific information
is stored in the call data records, that is, option F-CA-013 is also active.
z FALSE: Even if the CAMEL phase 2 service is offered and the CAMEL phase 2
specific information is placed in the call data records, that is, options F-CA-012 and
F-CA-013 are both set to TRUE, the information received from the SCP CAMEL
server in the FCI operation is not placed in the call data record by the RCP.
7.21
▼ F-CA-020 is used to place in the CDR the information (Ei-parameters + TSW) received from
the SCP CAMEL server in the SCI (Send Charging Information) operation.
▼ Field values:
z TRUE: The information received from the SCP CAMEL server in the SCI operation is
placed in the call data record by the RCP.
– If functional options F-CA-013 "CAMEL phase 2 charging information in
CDRs" and F-CA-020 are both enabled, this AOC information, and the
corresponding changes of tariff, are included in the CDRs.
– For functional option F-CA-020 to be enabled, it is essential for functional
options F-CA-013 and F-CA-025 "Accept ei-parameters received from the SCF"
to be enabled as well.
z FALSE: The information received from the SCP CAMEL server in the SCI operation
is not placed in the call data record by the RCP.
7.22
7.23
▼ Field values:
z TRUE : When F-CA-024 is active, the Supplementary Service
(CH,ECT,MPTY) invocation is accepted even if the current
established call is an IP call.
z FALSE : When F-CA-024 is not active, the Supplementary Service
(CH,ECT,MPTY) invocation is refused if the current established call
is an IP call.
7.24
▼ Field values:
z TRUE : When F-CA-025 is active, the SCI is accepted and ei-
parameters received from the SCF are handled as described in the
GSM.
z FALSE : When F-CA-025 is not active, the operation containing ei-
parameters received on the MSC-SCF dialogue (namely Send
Charging Information operation or SCI) is refused.
7.25
7.26
7.27