Charging

A900/1800 NSS - PLMN setting in RCP and HLR
9 Charging
9.1
© Alcatel University - 8AS 90200 0729 VT ZZA Ed.01
© Alcatel University - 8AS 90200 0729 VH ZZA Ed.01 Page 9.1

7 Defence
Session presentation
▼ Objective: to manage PLMN common data related

to call data records
9.2

Charging
Session presentation
▼ Program:
z 9 Charging
Î 9.1 Generation of CDRs
Î 9.2 Intermediate CDR
Î 9.3 Hot Billing
Î 9.4 Type and format
Î 9.5 Unsolicited messages
Î 9.6 appendix
9.3

9 Charging
9.1 Generation of CDR’s
9.4

9.1 Generation of CDRs
▼ For each OC, TC, Transit call, the MSC generates CDRs and sends them
via the Q3 interface to the OMC (if F-CG-003 is active).
z A CDR is generated only if the appropriate functional option is
activated (F_CG_xxx).
z The CDRs are normally generated at the end of a call, but they can
also be generated during a call, in the case of handovers or for
intermediate CDRs.
z Normally, the RCP generates the CDRs and stores them on disk,
before sending them periodically to the OMC.
▼ The SSP can also transfer CDRs to the OMC.
z These transit tickets are used to calculate compensation payments
between operators.
▼ The SCP has the capability to generate CDRs for IN services.
9.5

▼ The tickets are generated according to two transfer modes:

z Periodic file transfer (BDC mode), used for standard CDRs.
This transfer is initiated by the OMC.
z Transfer on the fly (TDS mode) used to transfer hot billing
CDRs and intermediate CDRs (very short transfer mode;
approximately 3 ms between the RCP and the billing
centre).
▼ Charging data comprises the call detail records generated by

RCPs (and in some cases by SSPs).
9.6

Other NEs
DPC
ACQUISITION SERVER function
ACQUISITION Offline or (EQM0)
(ESC0)
(ESA0) real-time
transfer
Flip-flop files data
Q3
Bulk data processing
ISO centre
collection Data server
function function
TRABFL
RCP xx OS
▼ The " bulk data collection " function :
z This function collects the The " data server " function :
"normal" data at regular This function sends charging files to a Data
Processing Centre. The connection data needed
intervals in offline file mode.
for the process between the function and the DPC
The period is a site setting . is site data that cannot be accessed by the
z "Hot-billing" data is collected operator. However, the operator defines the file
in real time. transfer method: automatic or manual
(MODDIS).
9.7

9 Charging
9.2 Intermediate CDR
9.8

Call types associated with intermediate CDRs
▼ An intermediate CDR is generated for each call type if the

appropriate functional option is activated:
z F-CG-007 : OC call
z F-CG-008 : TC call
z F-CG-009 : Rerouted call
z F-CG-010 : Call forwarding to the VMSC
z F-CG-011 : Call forwarding to the GMSC
z F-CG-012 : Rerouted forwarded call (with F-CG-20 also
activated)
z F-CG-043 : Transit call
9.9

Generation of Intermediate CDRs
▼ Generation of intermediate CDRs

z The intermediate CDRs are generated in the case of calls for which
the duration exceeds a certain value defined by CG-F-ITM-TIM and
then periodically according to CG-P-ITM-TIM.
▼ At the end of the call, an "overall" charging CDR is generated.
Beginning of call F P P P End of call
Intermediate CDR1
Intermediate CDR2
Intermediate CDR3
Global CDR
9.10

Generation of Intermediate CDRs
▼ Generation of intermediate CDRs

z If F-CG-063 is active, the intermediate CDRs are used to charge
each section (period) of the call. The last CDR generated at the end
of the call is also an intermediate CDR concerning the last period.
z Intermediate CDR numbers are sequential if F-CG-064 is active.
Beginning of call F P P P End of call
Intermediate CDR1
Intermediate CDR2
Intermediate CDR3
Intermediate CDRn
9.11

Programmable data
Used to generate intermediate call data records with a call duration that must match the applicable period for the call data
F-CG-063 :
record in question.
Sys. Par.: PARNAME = P2B_F_CG_063, NUM = BOOL, RTDMS Database: RELNAME = PYR_SY2B, ATR =
D_CG_063
Concerned processing :
F-CG-063 is applicable if F-CG-007 or F-CG-012 or F-CG-043 is set to TRUE.
F-CG-063 and F-CG-013 are exclusive.
State meaning:
TRUE : The time the call began and its duration are for intermediate call data record output.
FALSE : Each intermediate call data record gives the exact start time of the call and its duration relative to the start time;
the call data record sent at the end of the call is not an intermediate call data record.
See also : F-CG-064
Defines counting mode for intermediate call data records. Intermediate call data records are numbered sequentially (from
F-CG-064 :
1 to 254).
D_CG_064
Concerned processing :
F-CG-064 is applicable if F-CG-063 is set to TRUE.
State meaning:
TRUE : Intermediate call data records are numbered sequentially.
If the last intermediate call data record is number 254 and does not indicate the end of the call, the call is released.
FALSE : Intermediate call data records are numbered sequentially except for the last intermediate call data record (end of
call) of which the number is given by D_LCDRNB. If the last intermediate call data record has the number given by
D_LCDRNB and does not indicate the end of the call, the call is released.
9.12

Programmable data
Contains the time delay, after transmission of an intermediate call data record for a
CG-P-ITM-TIM-HB : subscriber having the "Hot Billing" category, waiting for the next call data record to be sent.
Sys. Par.: PARNAME = CG_P_ITM_TIM_HB, NUM = NUM, RTDMS Database:

RELNAME = PYR_SYSG, ATR = D_TTIPHB
Example = D'300/ H'0000012C Unit=1Second
Contains the time delay waiting for transmission of the first intermediate call data record for
CG-F-ITM-TIM HB : a subscriber having the Hot Billing category.
Sys. Par.: PARNAME = CG_F_ITM_TIM_HB, NUM = NUM, RTDMS Database:

RELNAME = PYR_SYSG, ATR = D_TTIHB
Example = D'180/ H'000000B4 Unit=1Second
9.13

Programmable data
Is used to set the time delay to wait between two transmissions of intermediate call data
CG_P_ITM_TIM : records for subscribers without the Hot Billing category.
Sys. Par.: PARNAME = CG_P_ITM_TIM, NUM = NUM, RTDMS Database: RELNAME =
PYR_SYSG, ATR = D_TTIPCG
Relevant process:
This parameter is meaningful only if an intermediate call data record is generated, that is, if
one of the following options :
F-CG-007, F-CG-008, F-CG-009, F-CG-010 , F-CG-011 or F-CG-012 is set to TRUE.
Example = D' 300/ H'0000012C . Unit= 1 Second
Is used to set the time delay waiting before sending the first intermediate call data record
CG_F_ITM_TIM : for a mobile that does not having the "Hot Billing" category.
Sys. Par.: PARNAME = CG_F_ITM_TIM, NUM = NUM, RTDMS Database: RELNAME =
PYR_SYSG, ATR = D_TTICG
Relevant process:
This parameter is meaningful only if an intermediate call data record is generated, that is, if
one of the following options :
F-CG-007, F-CG-008, F-CG-009, F-CG-010 , F-CG-011 or F-CG-012 is set to TRUE.
Example = D'180/ H'000000B4
9.14

Programmable data
Terminating calls forwarded at the VMSC

F-CG-012 : Used to generate intermediate call data records for calls forwarded and rerouted from the GMSC to the VMSC.
Sys. Par.: PARNAME = PB_F_CG_012, NUM = BOOL, RTDMS Database: RELNAME = PYR_SYSB, ATR =
D_FCG012
Field values:
VRAI (TRUE): For calls forwarded and rerouted from the GMSC to the VMSC, the intermediate call data records are
generated periodically when the call duration exceeds an initial delay period.
The initial duration CG-F-ITM-TIM and the period of timer CG-P-ITM-TIM may differ from those of "hot billing",
respectively CG-F-ITM-TIM-HB and CG-P-ITM-TIM-HB.
F-CG-012 is meaningful only if a call data record of this type is generated, that is if F-CG-020 is set to TRUE.
FAUX (FALSE): No intermediate call data record is generated periodically when the call duration exceeds an initial
delay.
Example = FAUX / H'0
F-CG-020 : When a call is rerouted at GMSC or VMSC, this option acts on the type ‘Rerouted TC ‘ or ‘Rerouted forwarded TC ‘ of
the generated CRD.
D_FCG020
Field values:
VRAI (TRUE) : A special mark is placed in the ‘Access Information’ parameter of the INAP_CREATE message. The
call comes back to RCP after transit in SSP loop, and a CDR of type ‘Rerouted Forwarded TC’ is generated.
FAUX (FALSE) : No mark is generated in INAP_CREATE message to SSP.
The call comes back to RCP after transit in SSP loop, and a CDR of type ‘Rerouted TC’ is generated
9.15

Programmable data
Terminating calls forwarded at the VMSC
F-CG-010 : Used to generate intermediate call data records for calls forwarded at the VMSC.
Sys. Par.: PARNAME = PB_F_CG_010, NUM = BOOL, RTDMS Database: RELNAME =
PYR_SYSB, ATR = D_FCG010
Field values:
VRAI (TRUE): For calls forwarded at the VMSC, intermediate call data records are generated
periodically when the call duration exceeds an initial delay.
The initial duration CG-F-ITM-TIM and the period of timer CG-P-ITM-TIM may differ from those of
the "hot billing" function, respectively CG-F-ITM-TIM-HB and CG-P-ITM-TIM-HB.
FAUX (FALSE): No intermediate call data record is generated periodically when the call duration
exceeds an initial delay for calls forwarded at the VMSC.
9.16

Programmable data
Terminating calls forwarded at the GMSC
F-CG-011 : Used to generate intermediate call data records for terminating calls forwarded at the GMSC.
Sys. Par.: PARNAME = PB_F_CG_011, NUM = BOOL, RTDMS Database: RELNAME = PYR_SYSB,
ATR = D_FCG011
Field values:
VRAI (TRUE): For calls forwarded at the GMSC, intermediate call data records are generated
Initial duration CG-F-ITM-TIM and the timer period CG-P-ITM-TIM may differ from those for "hot billing",
respectively CG-F-ITM-TIM-HB and CG-P-ITM-TIM-HB.
FAUX (FALSE): No intermediate call data record is generated periodically when the call duration
exceeds an initial delay for calls forwarded at the GMSC.
9.17

Programmable data
Terminating calls not forwarded
F-CG-008 : Used to generate an intermediate call data record for terminating calls.
Sys. Par.: PARNAME = PB_F_CG_008, NUM = BOOL, RTDMS Database:

RELNAME = PYR_SYSB, ATR = D_FCG008
Field values:
VRAI (TRUE): For terminating calls, an intermediate call data record is

generated periodically when the call duration exceeds an initial delay.
FAUX (FALSE): No intermediate call data record is generated for terminating
calls.
9.18

Programmable data
Calls rerouted to the GMSC
F-CG-009 : Used to generate intermediate call data records for calls rerouted from the
GMSC to the VMSC.
Field values:
VRAI (TRUE): For calls rerouted from the GMSC to the VMSC, intermediate call
data records are generated periodically when the call duration exceeds an initial
delay.
FAUX (FALSE): No intermediate call data record is generated for calls rerouted
from the GMSC to the VMSC.
9.19

Programmable data
Originating calls
F-CG-007 : Used to generate intermediate call data records for originating calls.

Field values:
VRAI (TRUE): An intermediate call data record is generated periodically when a
call duration timer times out for originating calls.
FAUX (FALSE): There is no intermediate call data record generated for
originating calls.
9.20

Programmable data
Transit calls
F-CG-043 : Used to generate an intermediate call data record for transit calls.

Field values:
VRAI (TRUE): For transit calls, an intermediate call data record is generated
This option is meaningful only if call data records are generated for transit calls,
that is, if F-CG-035 is set to TRUE.
FAUX (FALSE): For transit calls, no intermediate call data record is generated.
9.21

Programmable data
Dedicated session
F-CG-013 : Used to generate intermediate call data records on a dedicated session.

Field values:
VRAI (TRUE): The intermediate call data records are generated on a dedicated
session.
This option is meaningful only if an intermediate call data record is generated,
that is, if one of the following options:
F-CG-007, F-CG-008, F-CG-009, F-CG-010 , F-CG-011 or F-CG-012 is set to
TRUE.
FAUX (FALSE): The intermediate call data records are not generated on a
dedicated session, they are sent on the charging session.
9.22

9 Charging
9.3 Hot Billing
9.23

9.3 Hot Billing
Introduction
▼ The hot billing function is reserved for subscribers who have the HB (Hot
Billing) category.
z It enables a service provider, such as a car rental agency or a hotel,
to make mobile phones available to its clients and bill them for each
call less than five minutes after the end of the call.
▼ The RCP sends this type of CDR on the hot billing session. This
supplementary session means that CDRs arrive faster in the OMC.
▼ The service " Hot Billing " is managed by F-HB-001
9.24

9.3 Hot Billing
Programmable data
F-HB-001 : Indicates whether the "Hot Billing" service is available in the RCP.
Sys. Par.: PARNAME = PB_F_HB_001, NUM = NUM, RTDMS Database: RELNAME =

PYR_SYSB, ATR = D_HOTBIL
Sys. Par.: PARNAME = HLS_F_HB_001, NUM = BOOL, RTDMS Database: RELNAME

= HYR_HLS, ATR = HY_U_HLR
Relevant process:
The "Hot Billing" function is used to collect charging data for a call from a subscriber with
the "Hot Billing" category, and transfer the data in real time to the operator's billing centre.
Field values:
VRAI (TRUE): The service is available.
The service must be declared in the PYR_SUPP table.
FAUX (FALSE): The service is not available.
It must not be declared in the PYR_SUPP table.
9.25

9.3 Hot Billing
Programmable data
F-HB-002 (RCP) : Conditions the generation of a "Hot Billing" CDR by the GMSC.
Sys. Par.: PARNAME = PB_F_HB_002, NUM = BOOL, RTDMS Database:

RELNAME = PYR_SYSB, ATR = D_FHB002
Relevant process:
The hot billing function is a means of collecting and transferring to the operator
the billing data concerning a mobile leased out by a Service Provider (car rental
agency, hotel, etc).
To generate a "Hot Billing" CDR, the GMSC needs to know the subscriber's
category. For this, the category must be given by the HLR in the
MAP_SEND_ROUTING_INFO_res message.
Field values:
VRAI (TRUE): The GMSC generates a "Hot Billing" CDR if the category
received in the MAP_SEND_ROUTING_INFO_res message contains the
subscriber's category and this equals "Hot Billing".
The state of this option is meaningful only if F-HB-001 is set to the TRUE state.
FAUX (FALSE): The GMSC does not generate "Hot Billing" CDRs.
9.26

9.3 Hot Billing
Programmable data
F-HB-002 (HLR) : Conditions the presence of the subscriber's category in the

Sys. Par.: PARNAME = HLS_F_HB_002, NUM = BOOL, RTDMS Database:
RELNAME = HYR_HLS, ATR = HY_U_HLR
Relevant process:
To generate a "Hot Billing" CDR, the GMSC needs to know the subscriber's category.
For this, the category must be given by the HLR in the
"MAP_SEND_ROUTING_INFO_res" message.
Field values:
VRAI (TRUE): The subscriber's category is sent by the HLR in the

"MAP_SEND_ROUTING_INFO_res" message whatever the state of options
F_TC_003 and F-IN-001.
The state of this option is meaningful only if F-HB-001 is set to the TRUE state.
FAUX (FALSE): The HLR does not give the subscriber's category in the
If the state of this option is FALSE, the CFU (Call forwarding unconditional) service
cannot be subscribed to by a subscriber with the "Hot Billing" category.
9.27

9 Charging
9.4 Type and format
9.28

9.4Type and format
CDR version - Programmable data
▼ There are two possible versions for a CDR :

z version 00, concerning functions prior or equal to technical
release R3,
z version 04 which concerns functions later than release R3.
F-CG-016 : Indicates the version of the call data record format.

Field values:
VRAI (TRUE): The call data record format is R4.

FAUX (FALSE): The call data record format is R3.
Note: The choice depends on the capabilities of the operator's billing

subsystem.
9.29

9.4Type and format
Time and serial number - Programmable data
Is used to place the call start time in the call data record instead of the call end time
RB_TISTMP :
(call time stamp field).
Sys. Par.: PARNAME = RB_TISTMP, NUM = NUM, RTDMS Database: RELNAME
= RYR_SYSB, ATR = D_TISTMP
Field values:
1: The call end time is placed in the call data record.
0: The call start time is placed in the call data record instead of the call end time.
Example = D'1/ H'01
Used to send, in the "serial number" field of the call data record, the CDR's serial
F-CG-033 :
number.
Sys. Par.: PARNAME = P2B_F_CG_033, NUM = BOOL, RTDMS Database:
RELNAME = PYR_SY2B, ATR = D_CG_033
Field values:
VRAI (TRUE): A call data record serial number is placed in the "serial number" field.
FAUX (FALSE): The call data record's serial number is not stored in the "serial
number" field.
9.30

9.4Type and format
Speech encoding type - Programmable data
Allows the speech encryption type (speech version), used when a radio channel is allocated, to be stored in the
F-CG-023 :
CDRs.
D_FCG_023
Field values:
TRUE:
The speech encryption type used for the first speech channel allocation is stored in the CDR.
FALSE:
The ‘GSM speech full rate version 1’ speech encryption type is stored in the call data record.
See also: F-RM-005
Allows to store AMR function Informations in the CDR

F-CG-056 :
D_CG_056
Field values:
TRUE :
F-RM-001 is set to TRUE.
F-CG-056 is significant if F-RM-005 and F-RM-013 are set to TRUE.
The CDR includes the following information:
- the type of radio channel: choice left to the BSC between full rate and half rate with or without preference.
- the choice proposed to the BSC, half rate or full rate with or without preference.
- rate retained by the BSC
- the speech encoding type: speech version 3
- for each rate (half rate and full rate), the best Speech version supported by the mobile (Speech V3 considered
better than V2, which is considered better than V1).
FALSE :
If F_RM_013 is set to TRUE, GSM speech full rate version 1 type speech encoding is stored in the CDR. 9.31

9.4Type and format
Incoming circuit group - Programmable data
Used to set the name of the incoming circuit group provided by the SSP in the CDRs
F-CG-005 :
("Information received from the fixed network" field).
Sys. Par.: PARNAME = PB_F_CG_005, NUM = BOOL, RTDMS Database: RELNAME =
PYR_SYSB, ATR = D_FCG005
Field values:
VRAI (TRUE): The name of the incoming circuit group is placed in the call data record if
received from the SSP.
FAUX (FALSE): The name of the incoming circuit group is not placed in the call data
records.
9.32

9.4Type and format
Charging prefix - Programmable data
▼ Charging prefix
z In an originating call, the RCP's translator recognises a particular prefix
at the start of the number dialled (before the national or, where
appropriate, international prefix) and stores a certain number of digits
(given as translation result) in the CDR.
z This prefix is then deleted by the translator before the called party
number is sent to the SSP.
z This function is typically used by a subscriber to signal, by presence of
the prefix, that the call is set up for private or business use, and take this
into account in the billing.
F-CG-014 : Used to place in the call data record the prefix resulting from translation.
Sys. Par.: PARNAME = PB_F_CG_014, NUM = BOOL, RTDMS Database: RELNAME = PYR_SYSB,
ATR= D_FCG014
Field values:
VRAI (TRUE): The prefix resulting from translation (charging prefix CGPREF parameter) of the called
party number in an originating call is placed in the CDR in the "List of invoked services" field. This is not
necessarily the prefix dialled. The prefix is a means enabling the operator to differentiate, for example, a
business call from a private call.
FAUX (FALSE): The prefix resulting from translation is not stored in the call data record.
9.33

9 Charging
9.5 Unsolicited messages
9.34

9.5 Unsolicited messages
▼ PMLX/6003 : The "standard" CDRs concerning a call have not

been acknowledged.
▼ PMLX/6014 : The hot billing ticket concerning a call has not

been acknowledged.
▼ PMLX/6060 : An intermediate ticket concerning a call has not

been acknowledged.
▼ PMLX/6061 : The handover ticket concerning a call has not been

acknowledged.
9.35

9 Charging
Evaluation
▼ Objective: to be able to manage PLMN

common data related to Charging
Thank you for answering

the self-assessment
of the objectives sheet
9.36

Charging

Hochgeladen von

Dokumentinformationen

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Charging

Hochgeladen von

Copyright:

Verfügbare Formate

A900/1800 NSS - PLMN setting in RCP and HLR

© Alcatel University - 8AS 90200 0729 VH ZZA Ed.01 Page 9.1

▼ Objective: to manage PLMN common data related

© Alcatel University - 8AS 90200 0729 VH ZZA Ed.01 Page 9.2

© Alcatel University - 8AS 90200 0729 VH ZZA Ed.01 Page 9.3

9.1 Generation of CDR’s

© Alcatel University - 8AS 90200 0729 VH ZZA Ed.01 Page 9.4

© Alcatel University - 8AS 90200 0729 VH ZZA Ed.01 Page 9.5

▼ The tickets are generated according to two transfer modes:

▼ Charging data comprises the call detail records generated by

© Alcatel University - 8AS 90200 0729 VH ZZA Ed.01 Page 9.6

© Alcatel University - 8AS 90200 0729 VH ZZA Ed.01 Page 9.7

9.2 Intermediate CDR

© Alcatel University - 8AS 90200 0729 VH ZZA Ed.01 Page 9.8

▼ An intermediate CDR is generated for each call type if the

© Alcatel University - 8AS 90200 0729 VH ZZA Ed.01 Page 9.9

▼ Generation of intermediate CDRs

Beginning of call F P P P End of call

© Alcatel University - 8AS 90200 0729 VH ZZA Ed.01 Page 9.10

▼ Generation of intermediate CDRs

© Alcatel University - 8AS 90200 0729 VH ZZA Ed.01 Page 9.11

© Alcatel University - 8AS 90200 0729 VH ZZA Ed.01 Page 9.12

Sys. Par.: PARNAME = CG_P_ITM_TIM_HB, NUM = NUM, RTDMS Database:

Example = D'300/ H'0000012C Unit=1Second

Sys. Par.: PARNAME = CG_F_ITM_TIM_HB, NUM = NUM, RTDMS Database:

Example = D'180/ H'000000B4 Unit=1Second

© Alcatel University - 8AS 90200 0729 VH ZZA Ed.01 Page 9.13

© Alcatel University - 8AS 90200 0729 VH ZZA Ed.01 Page 9.14

Terminating calls forwarded at the VMSC

© Alcatel University - 8AS 90200 0729 VH ZZA Ed.01 Page 9.15

Terminating calls forwarded at the VMSC

© Alcatel University - 8AS 90200 0729 VH ZZA Ed.01 Page 9.16

Terminating calls forwarded at the GMSC

© Alcatel University - 8AS 90200 0729 VH ZZA Ed.01 Page 9.17

Terminating calls not forwarded

Sys. Par.: PARNAME = PB_F_CG_008, NUM = BOOL, RTDMS Database:

VRAI (TRUE): For terminating calls, an intermediate call data record is

© Alcatel University - 8AS 90200 0729 VH ZZA Ed.01 Page 9.18

Calls rerouted to the GMSC

© Alcatel University - 8AS 90200 0729 VH ZZA Ed.01 Page 9.19

Sys. Par.: PARNAME = PB_F_CG_007, NUM = BOOL, RTDMS Database:

© Alcatel University - 8AS 90200 0729 VH ZZA Ed.01 Page 9.20

Sys. Par.: PARNAME = PB_F_CG_043, NUM = BOOL, RTDMS Database:

© Alcatel University - 8AS 90200 0729 VH ZZA Ed.01 Page 9.21

F-CG-013 : Used to generate intermediate call data records on a dedicated session.

Sys. Par.: PARNAME = PB_F_CG_013, NUM = BOOL, RTDMS Database:

© Alcatel University - 8AS 90200 0729 VH ZZA Ed.01 Page 9.22

9.3 Hot Billing

© Alcatel University - 8AS 90200 0729 VH ZZA Ed.01 Page 9.23

▼ The service " Hot Billing " is managed by F-HB-001

© Alcatel University - 8AS 90200 0729 VH ZZA Ed.01 Page 9.24

Sys. Par.: PARNAME = PB_F_HB_001, NUM = NUM, RTDMS Database: RELNAME =

Sys. Par.: PARNAME = HLS_F_HB_001, NUM = BOOL, RTDMS Database: RELNAME

© Alcatel University - 8AS 90200 0729 VH ZZA Ed.01 Page 9.25

Sys. Par.: PARNAME = PB_F_HB_002, NUM = BOOL, RTDMS Database:

Example = FAUX / H'0

© Alcatel University - 8AS 90200 0729 VH ZZA Ed.01 Page 9.26

F-HB-002 (HLR) : Conditions the presence of the subscriber's category in the

VRAI (TRUE): The subscriber's category is sent by the HLR in the

© Alcatel University - 8AS 90200 0729 VH ZZA Ed.01 Page 9.27

9.4 Type and format

© Alcatel University - 8AS 90200 0729 VH ZZA Ed.01 Page 9.28

▼ There are two possible versions for a CDR :

F-CG-016 : Indicates the version of the call data record format.