Charging Management by SCP

Alcatel 900/1800 NSS
CAMEL function in the RCP and HLR
CHARGING MANAGEMENT BY THE

SCP AT THE RCP
7.1
© Alcatel University - 8AS 90200 0746 VT ZZA Ed.01
© Alcatel University - 8AS 90200 0746 VH ZZA Ed.01 Page 7.1

Charging management by the SCP at the RCP
Session presentation
▼ Objective: to be able
z to resolve problems concerning charging management by the SCP at
the RCP.
▼ 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

Description
▼ The SCP can manage all call charging with the help of the RCP
▼ The CAP messages (version 2) are used by the SCP to send instructions to the
RCP (MSC) concerning charging:
z call duration management:
– "Apply Charging" message: SCP -> RCP
(MSC)
– "Apply Charging Report" message: RCP (MSC) -> SCP
z management of AoC data (EI-parameters) to be sent to the MS:
– "Send Charging Information" message: SCP -> RCP (MSC)
z SCP charging information to be included in the CDR of the RCP (MSC):
– "Furnish Charging Information" message: SCP -> RCP (MSC)
z Request to the RCP for information concerning the call at the end of the
call:
– "Call Information Request" message: SCP -> RCP (MSC)
– "Call Information Report" message: RCP (MSC) -> SCP
7.4

Call duration management
7.5

SCP policy
▼ The call is divided into call segments by the SCP.
▼ 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.
▼ TONE_INSERT_TIME: PLMN data described in session OC CAMEL invocation.

RCP report
▼ On expiry of the segment duration, or when the call is released, the MSC(RCP)
informs the SCP via the "Apply Charging Report" message, with the following
mandatory parameter:
z CallResult which contains in the TimeDurationChargingResult field, the
following values:
– Leg to be charged: mandatory parameter: PartyToCharge
– Elapsed time (TSI):
' since receiving called party answer: mandatory parameter:
TimeIfNoTariffSwitch: if no change of tariff has taken place since
receiving the called party answer.
' since the last tariff change: mandatory parameter:
TimeIfTariffSwitch / TimeSinceLastTariffSwitch: if a change of
tariff has taken place since receiving the called party answer.
' between receiving the called party answer and last change of
tariff or between the second last change of tariff and the last
change of tariff: TimeIfTariffSwitch / TimeSinceLastTariffSwitch
and TimeSwitchInterval: if a change of tariff has taken place during
the current segment.
– A release indication or a call continuation: mandatory parameter:
CallActive
7.7
▼ PartyToCharge: the leg to be charged as it was received in the AC.
▼ 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.

SCP action
▼ In the case of a call continuation indication, the SCP:

z releases the call, or
z returns new information for a new call segment.
7.8

Timing diagram
RCP Start of call
SCP TSW2 Tariff 1
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.
TSI 24 TSI 31 TSI 31 Tariff 3

On-hook
7.9

Management of AoC data
7.10

Ei-parameters to be sent to the MS
▼ In the case of an OC call only, the SCP can send AOC data (ei_parameters: e1,
e2, e3, e4 and e7) to the RCP via the message
SEND_CHARGING_INFORMATION.
▼ Before the called party answers:

z AOC data to be sent on called party answer, if no change of tariff occurs in the
meantime.
z AOC data to be sent on called party answer, if a change of tariff occurs in the
meantime, or on the next change of tariff.
▼ After the called party answers:

z AOC data to be sent on the next change of tariff or immediately if there is no change
of tariff.
z Time to next change of tariff (if not sent in a previous Apply Charging message).
▼ 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.

Message interchanges
RCF
SSP SCF
OCH_MSC GSM_SSF
SET-UP
DP_O_COLLECTED_INFO
INITIAL_DP
APPLY_CHARGING (Tcp1, TSW2)
SEND_CHARGING_INFORMATION (ej parameters, ek parameters)

REQUEST_REPORT_BCSM_EVENT
CONNECT
Int_CONNECT
IAM CREATE
TARIFF 1 ACM EVENT (ACM)
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
APPLY_CHARGING_REPORT (TSI 11, TSI 21)
7.12

SCP charging information to be included

in the CDR
7.13

Information to be included in the CDR : Policy
▼ At the end of the call, or during the call, the SCP can send charging data to the
RCP to be included in its call data record CDR via the
"Furnish_Charging_Information" message.
▼ This information comprises a field of up to 40 octets in a free format.
▼ 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.
▼ This function is subject to functional option F-CA-014, "FCI information in CDR".
7.14

Information to be included in the CDR : Message interchanges
RCF
SSP SCF
OCH_MSC GSM_SSF
SET-UP
DP_O_COLLECTED_INFO
INITIAL_DP
FURNISH_CHARGING_INFORMATION
CONNECT
Int_CONNECT
IAM CREATE
ACM EVENT (ACM)
ALERTING
ANM EVENT (ANM)
CONNECT
CONNECT_ACK
REL EVENT (REL)
FURNISH_CHARGING_INFORMATION
DP_O_DISCONNECT
REPORT_EVENT_BCSM
RELEASE_CALL
Int_RELEASE
REL FREE
7.15

Request to the RCP for information

concerning the call at the end of the call
7.16

Information concerning the call at the end of the call : Policy
▼ The SCP can ask the RCP (in the Call_Information_Request message) to
send it, at the end of the call, information concerning the call (for generation
of CDRs at the SCP) (Call_Information_Report message):
z Call setup time: time between the CAP operation to set up the call
(Connect or Continue) and receipt of the called party answer.
z Call release time.
z Conversation time: duration between receipt of the called party answer
and call release.
z Call release cause.
▼ This request can be made independently for the calling part and the called
part.
▼ In the case of reconnection, it must be repeated for each new call.
7.17

Information concerning the call at the end of the call : Message interchanges
RCF
SSP SCF
OCH_MSC GSM_SSF
SET-UP
DP_O_COLLECTED_INFO
INITIAL_DP
CALL_INFORMATION_REQUEST (LegID=Called)
CONNECT
Int_CONNECT
IAM CREATE
Ý ANM EVENT (ANM)

CONNECT
CONNECT_ACK
REL EVENT (REL)
DP_O_DISCONNECT
CALL_INFORMATION_REPORT
REPORT_EVENT_BCSM
CALL_INFORMATION_REQUEST (LegID=Called)
CONNECT
Int_CONNECT
IAM CREATE
Ý ANM EVENT (ANM)

DISCONNECT
DP_O_DISCONNECT
CALL_INFORMATION_REPORT
REPORT_EVENT_BCSM
RELEASE_CALL
FREE Int_RELEASE
REL
7.18

Data structure
7.19

F-CA-013
▼ F-CA-013
z Sys. Par.: PARNAME = P2B_F_CA_013, BOOLVAL
z RTDMS database: RELNAME = PYR_SY2B, attribute: D_CA_013
▼ 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
▼ F-CA-014
▼ 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
▼ F-CA-020
▼ 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

F-CA-023
▼ F-CA-023
▼ F-CA-023 is used, in the case of a call with a CAMEL phase 2 dialogue, to place data
restricted to CAMEL phase 1 in the call data record in the area relating to CAMEL phase 1.
The CAMEL phase 2 specific data is lost.
▼ Field values:
z TRUE: If the conditions set out below are satisfied:
– 1) the CAMEL phase 1 service is offered, that is, option F-CA-001 is set to TRUE
– 2) the CAMEL phase 1 data is placed in the call data record, that is, option F-CA-
002 is set to TRUE
– 3) the CAMEL phase 2 service is offered, that is, option F-CA-012 is set to TRUE
– 4) the CAMEL phase 2 information is not placed in the call data record in the
CAMEL 2 specific fields, that is, option F-CA-013 is not set to TRUE
ª then the information concerning CAMEL phase 2 restricted to CAMEL
phase 1 is placed in the CAMEL phase 1 field.
z FALSE: The information concerning CAMEL phase 2 is not placed in the call data
record given the conditions listed in the TRUE state. Note:
– This option can be used pending adaptation of the billing centre to the CAMEL
phase 2 data, that is, to take account of the interface break in call data records
between CAMEL phase 1 and CAMEL phase 2.
7.23

F-CA-024
▼ F-CA-024
z Sys. Par.: PARNAME = unknown, BOOLVAL
z RTDMS database: RELNAME = unknown, attribute: unknown
▼ F-CA-024 accept SS invocation on an IP "call"

z This option is meaningful when F-CA-012 is active.
▼ 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

F-CA-025
▼ F-CA-025
z Sys. Par.: PARNAME = unknown, BOOLVAL
z RTDMS database: RELNAME = unknown, attribute: unknown
▼ F-CA-025 accept ei-parameters received from the SCF during a Mobile

Originating Call concerning a subscriber who has subscribed to Aoc
▼ 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

TONE_INSERT_TIME
▼ INTSYR / MODSYR : PARNAME =
z TONE_INSERT_TIME : time remaining before the call is cut off

when notifying the subscriber that the cut-off time is imminent.
– DECVAL or HEXVAL type value: 5 to 60, scaling factor =5
– Default value: 30
7.26

Evaluation
▼ Objective: to be able to resolve

problems concerning charging
management by the SCP at the RCP.
Thank you for answering

the self-assessment
of the objectives sheet
7.27

Charging Management by SCP

Încărcat de

Informații document

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Charging Management by SCP

Încărcat de

Drepturi de autor:

Formate disponibile

Alcatel 900/1800 NSS

CAMEL function in the RCP and HLR

CHARGING MANAGEMENT BY THE

© Alcatel University - 8AS 90200 0746 VH ZZA Ed.01 Page 7.1

© Alcatel University - 8AS 90200 0746 VH ZZA Ed.01 Page 7.2

© Alcatel University - 8AS 90200 0746 VH ZZA Ed.01 Page 7.3

© Alcatel University - 8AS 90200 0746 VH ZZA Ed.01 Page 7.4

Call duration management

© Alcatel University - 8AS 90200 0746 VH ZZA Ed.01 Page 7.5

▼ TONE_INSERT_TIME: PLMN data described in session OC CAMEL invocation.

© Alcatel University - 8AS 90200 0746 VH ZZA Ed.01 Page 7.6

▼ PartyToCharge: the leg to be charged as it was received in the AC.

© Alcatel University - 8AS 90200 0746 VH ZZA Ed.01 Page 7.7

▼ In the case of a call continuation indication, the SCP:

© Alcatel University - 8AS 90200 0746 VH ZZA Ed.01 Page 7.8

RCP Start of call

SCP TSW2 Tariff 1

TSI 24 TSI 31 TSI 31 Tariff 3

© Alcatel University - 8AS 90200 0746 VH ZZA Ed.01 Page 7.9

Management of AoC data

© Alcatel University - 8AS 90200 0746 VH ZZA Ed.01 Page 7.10

▼ Before the called party answers:

▼ After the called party answers:

© Alcatel University - 8AS 90200 0746 VH ZZA Ed.01 Page 7.11

SEND_CHARGING_INFORMATION (ej parameters, ek parameters)

TARIFF 1 ACM EVENT (ACM)

APPLY_CHARGING_REPORT (TSI 11, TSI 21)

© Alcatel University - 8AS 90200 0746 VH ZZA Ed.01 Page 7.12

SCP charging information to be included

© Alcatel University - 8AS 90200 0746 VH ZZA Ed.01 Page 7.13

▼ This information comprises a field of up to 40 octets in a free format.

▼ This function is subject to functional option F-CA-014, "FCI information in CDR".

© Alcatel University - 8AS 90200 0746 VH ZZA Ed.01 Page 7.14

ACM EVENT (ACM)

ANM EVENT (ANM)

© Alcatel University - 8AS 90200 0746 VH ZZA Ed.01 Page 7.15

Request to the RCP for information

© Alcatel University - 8AS 90200 0746 VH ZZA Ed.01 Page 7.16

▼ In the case of reconnection, it must be repeated for each new call.

© Alcatel University - 8AS 90200 0746 VH ZZA Ed.01 Page 7.17

Ý ANM EVENT (ANM)

Ý ANM EVENT (ANM)

© Alcatel University - 8AS 90200 0746 VH ZZA Ed.01 Page 7.18

© Alcatel University - 8AS 90200 0746 VH ZZA Ed.01 Page 7.19

© Alcatel University - 8AS 90200 0746 VH ZZA Ed.01 Page 7.20

© Alcatel University - 8AS 90200 0746 VH ZZA Ed.01 Page 7.21

© Alcatel University - 8AS 90200 0746 VH ZZA Ed.01 Page 7.22

© Alcatel University - 8AS 90200 0746 VH ZZA Ed.01 Page 7.23

▼ F-CA-024 accept SS invocation on an IP "call"

© Alcatel University - 8AS 90200 0746 VH ZZA Ed.01 Page 7.24

▼ F-CA-025 accept ei-parameters received from the SCF during a Mobile

© Alcatel University - 8AS 90200 0746 VH ZZA Ed.01 Page 7.25

▼ INTSYR / MODSYR : PARNAME =

z TONE_INSERT_TIME : time remaining before the call is cut off

© Alcatel University - 8AS 90200 0746 VH ZZA Ed.01 Page 7.26

▼ Objective: to be able to resolve

Thank you for answering

© Alcatel University - 8AS 90200 0746 VH ZZA Ed.01 Page 7.27

S-ar putea să vă placă și