GSM R6E Subscriber Related Event and Call Data Feat - Spec

FEATURE SPECIFICATIONS
ALCATEL GSM/DCS RCP, HLR
CHARGING
SUBSCRIBER RELATED EVENT AND CALL DATA

#3DR 20116 QMWW PTZZA 02
Alcatel Mobile Networks Division - MND Ref. 3DR 61691 GRWW UFZZA 02 - 06 1/61
30/11/2001 [3628]
All rights reserved. Passing on and copying of this document, use and communication of its contents, not permitted without written authorization
TABLE OF CONTENTS
1. INTRODUCTION .................................................................................................... 3
2. FEATURE DESCRIPTION ......................................................................................... 4

2.1. GENERAL......................................................................................................... 4
2.2. TRANSFER OF CHARGING INFORMATION WITHIN THE LOCAL PLMN ............. 4
2.3. TICKETS CONTENT .......................................................................................... 6
2.4. INTERACTIONS WITH OTHER SUPPLEMENTARY SERVICES .............................. 10
2.5. HANDOVER INTER-MSC TICKET..................................................................... 11
2.6. INTERMEDIATE TICKET FUNCTION ................................................................ 12
3. CALL RECORD GENERATION SCENARIOS ...........................................................14

3.1. LIST OF ABBREVIATION ................................................................................. 14
3.2. MS ORGINATING CALL TO FIXED NETWORK (WITH AND WITHOUT HOT
BILLING)........................................................................................................ 15
3.3. MS TERMINATING CALL FROM FIXED NETWORK ........................................... 15
3.4. MS TO MS (OF THE PLMN) CALL .................................................................... 16
3.5. TERMINATING CALL TO ANMS ROAMING OUTSIDE THE PLMN ..................... 17
3.6. MS TERMINATING CALL FORWARDED ........................................................... 17
3.7. INTER-MSC HANDOVER ................................................................................ 21
3.8. INTER-MSC HANDOVER FOLLOWED BY SUBSEQUENT HO TOWARD A
3TH MSC....................................................................................................... 22
3.9. SHORT MESSAGE SERVICE............................................................................. 23
3.10. CALL WITH IN-GSM INVOCATION ................................................................ 25
3.11. CALL WITH CAMEL INVOCATION .................................................................. 28
3.12. SUPPLEMENTARY SERVICE OPERATION......................................................... 54
3.13. MOBILE INITIATED USSD COMMAND........................................................... 55
3.14. NETWORK INITIATED USSD COMMAND........................................................ 56
3.15. CALLS WITH OPTIMAL ROUTING ................................................................... 57
3.16. MOBILE NUMBER PORTABILITY ...................................................................... 61
30/11/2001 [3628]
1. INTRODUCTION
Charging function in GSM 900/1800 systems is divided into two parts :

- Generation of Call Data Records (CDRs) by the MSCs involved in a call
- Charging and Billing of subscribers (using CDRs generated in the MSCs) in a
dedicated processor (not in the scope of GSM recommendations).
The purposes of the document are to describe the Alcatel implementation for :
- the transfer of charging information within local PLMN,
- the CDRs generation scenarii, including CDRs generated for IN and CAMEL
invocations.
It deals with charging function related to successful call attempts.
30/11/2001 [3628]
2. FEATURE DESCRIPTION
2.1. GENERAL
The Call Data Records (CDRs) are sent:

At the end of every originating / terminating completed call related to a
Mobile Subscriber (MS) of the PLMN or visiting the PLMN, optionally
including an IN or CAMEL invocation,
For short messages transfered related to a Mobile Subscriber (MS) of the
PLMN or visiting the PLMN,
During the call: for handover tickets and intermediate tickets,
At the end of successful non related call: Supplementary service operation,
USSD command,
At the end of the connection towards an IP (intelligent peripheral).
(From CAMEL Phase 2 a SCP (CAMEL server) may require to connect an IP
in order to offer specific announcement for instance.)
Handover tickets may be generated in the controlling and in the serving MSCs
when an inter-MSC handover is established , and when the functional options are
offered.
According to a functional option, for one or more type(s) of call(s), intermediate

tickets may be periodically generated for the calls which duration exceeds a defined
initial value. Further details are in the document Long call supervision.
Within a call establishment scenario, if the results of the EIR interrogation indicate a
black-listed equipment, the call is released and no CDR is generated. A
spontaneous message is emitted.
2.2. TRANSFER OF CHARGING INFORMATION WITHIN THE LOCAL PLMN
In the Alcatel solution, the CDR (charging tickets) are stored on disk at the MSC or
GMSC level and then sent by block to the CDR Collector. The CDR Collector (on
operator request) initiates the transfer. The protocol used between the MSC/VLR and
the CDR Collector is based on X.25; it relies on FTAM for normal subscribers, CMISE
for Hot Billing ones.
30/11/2001 [3628]
The CDR Collector handles the modification of the protocol (X25 IP) and then
sends the tickets to another functional entity for post-processing: the CCBS
(Customer Care and Billing System). The computation of charges is not performed by
the PLMN itself but by the CCBS.
Q3
RCP SSP
CDR X25
Collector
FTAM
FTP TCP/IP CMISE MSC/VLR
FTAM
IP
Billing Center
Note(s): If the OMC NSS is always used in the network, the procedure for the
transfer of the CDR with the MSC is the same as described above.
However the connection between the OMC NSS and the CCBS relies on
Q3 interface.
If Hot Billing function is offered, the procedure above described still applies, with
these specificities :
- the charging tickets are sent on a per-call basis, and not by blocks,
- as a consequence, the protocol between MSC/VLR and CDR Collector relies on
CMISE, instead of FTAM,
- the charging tickets related to the activities of that subscriber are discriminated
by the hot billing indicator and an additional Hot Billing specific handling is
performed.
For further details on the Hot Billing processing at NSS level in the Alcatel solution,
please refer to the document Hot Billing.
The space allocated on the disk, at the MSC, to store the CDR, before sending them
to the CDR Collector, depends on the size of the call data to be sent. It is also
function of the period during which this data have to be saved to face a possible
unavailability of the MSC/OS link. The period is 3 days (normal billing).
30/11/2001 [3628]
2.3. TICKETS CONTENT
The call data gathered in the CDRs include different parameters, the value of which
may vary according to the type of call as indicated in the following tables.
Definition of event types parameter of the following tables
OC Originating call radio
TC Terminating call radio
FW-G Forwarded TC at GMSC (unconditional)
FW-V Forwarded TC at VMSC
RR Rerouted TC
R-FW Rerouted forwarded TC call
HO-C Handover controlling MSC
HO-S Handover serving MSC
MT-V Short message mobile terminating at servicing MSC
MT-G Short message mobile terminating at GMSC
MO-V Short message mobile originating at servicing MSC
MO-IW Short message mobile originating at IWSMS
SS-OP Supplementary service operation or USSD commands
TT Transit call
IP Connection to a remote IP (when CAMEL is invoked)
30/11/2001 [3628]
POSSIBLE VALUE PER EVENT TYPE
PARAMETER POSSIBLE VALUES
OC TC FW-G FW-V RR R-FW HO-C HO-S MT-V MT-G MO-V MO-IW SS-OP TT IP
Emitting type MSC X X X X X X X X

GMSC X X X X X X
IWSMS X
MSC serving X
Hot billing 0 (charging) X X X X X X X X X X X X X X X
1 (hot billing) X X X X X X X X X X
Call type originating X X X
terminating X X
GMSC forwarded X
MSC forwarded X
rerouted TC X X
rerouted forward. X
handover X X
SS operation X
Transit X
IP X
Successful call normal clearing X X X X X X X X X X X X X X X
termination network failure X X X X X X X X X X
type local syst. fail. X X X X X X X X X X X
radio failure X X X X X X X X X
handover failure X X X X X X X X X X X
call duration overflow X X X X X X X X
intermediate tck X X X X X X X
ODB clearing X X X X X X X X
Intermediate ticket number X X X X X X X
ticket number
Call origin national X X X X X X X
termination international X X X X X X
manual national X X X X X X
manual internat. X X X X X X
not applicable X X X X X X X X
Charging no indication X X X X X X
(ACM charge X X X X X X
content) no charge X X X X X X
not applicable X X X X X X X X X
Required Teleservice X X X X X X X X X X
Basic service Bearer service X X X X X X
not applicable X X X X X
30/11/2001 [3628]
Circuit IAM emission X X X

allocation IAM receipt X X X X X X X
time stamp FSM result X X
RP ACK X
RP-MO-ACK X
REGISTER msg X
USSD command X
Call duration Duration
from call start X X X X X X X X X
from time expiry X X X X X X X
number of SM X X X X
Numb of msg/MS X
Serving HO duration X
Call time conversation
stamp
starting X X X X X X X X
terminating X X X X X X X X
Last ack receiv X X X X
Timer expiry X X X X X X X
HO termination X X
not applicable X
Mobile station IMEI calling MS X X X X
identity IMEI called MS X X X X
not applicable X X X X X X X X X
List of invoked IN-GSM X X X X X
suppl. CAMEL ph 1 X X X X X
services Call Hold X X
CUG X X X X X X
AoC X X X
ECT X X
MPTYM/MPTYS X X
DTMF X X X
Prefix X
dual services X X
OPE INTERV X X
FORWARD.REAS X X
CLIP X
SS operation X
USSD command X
CW info X X
Call Ref. & MSC-Id X X X X X X
Serial number X X X X X X X X X X X X X X X
Routeing SOR X X X
Routeing LOC X X X
Upstream carrier X X X X X X
Downstream carrier X X X X X X
30/11/2001 [3628]
Data compression X X
Camel ph 2 X X X X X
Portability MNP / SRF X X X
Incoming CIC X X X X X X X
Outgoing CIC X X X X X X X
SMOCalled-Number X
Link ISDN/calling X X X X X
information ISDN/called X X X X X X X
ISDN/forwarding X X X
HO number X
MS identity IMSI/calling X X X X X
IMSI/called X X X X X X X
IMSI/forwarding X X X
IMSI of the involved X X
MS
MSC identity RCF ISDN number X X X X X X X X X X X X X X X
call partner Id calling number X X X X X
original called X X X X
called number X X
SC address X X X
IWSMS address X
dialled number X
HO number X
forwarding nbr X
Not applicable X X
MS location cell id of the calling X X X X
MS
cell id of the called MS X X X
MSRN of called X X
ISDN number of
forwarded-to X X
ISDN number of X
serving MSC or SGSN
Calling number X
ISDN number of X X
controlling MSC
Not applicable X X X
Required full rate channel X X
bearer
capability: FR preferred and allo. X X
channel type FR preferred and HR X X
allo.
30/11/2001 [3628]
Required FR speech vers.1 X X

bearer
capability: FR speech vers.2 X X
speech FR speech vers.3 X X
version
chosen HR speech vers.1 X X
HR speech vers.2 X X
HR speech vers.3 X X
Link identity outgoing Trunk Group X X X X X X X
not applicable X X X X X X X X
Information incoming trunk G X X X X X X X
received from -charging of X X X X X X
international
the fixed and special
network communications
2.4. INTERACTIONS WITH OTHER SUPPLEMENTARY SERVICES
In case of Explicit call transfer, two call records are elaborated.

For example, if a MS A who has two calls with B and C, invokes ECT to connect his
two remote parties B and C, at the end of the B-C call, two Call records are built,
one concerning the A-B call and another concerning the A-C call with call types
either originating call radio or terminating call radio .
In case of Multi party call one call record is generated for each originating or
terminating call belonging to the conference and includes a service indication. The
last transaction of the conference includes in addition all the information relative to
the whole conference.
When a MS puts an active call on hold in order to originate a new call, a new call
record is to be generated for this new originating call, independently of the call
record generated for the held call.
In case of a call waiting, a call record is to be generated as for a new terminating

call, independently of the call record generated for the existing call.
30/11/2001 [3628]
2.5. HANDOVER INTER-MSC TICKET
2.5.1. CONTROLLING MSC
In case of inter-MSC handover, a ticket can be generated, either for every handover
inter-MSC or for handover using discriminated outgoing trunk group (i.e.: PSTN) or
never, according to the value of the corresponding functional options.
The controlling MSC generates a charging ticket with the ticket type handover and
the following main information:
J the controlling MSC identity
J the handover number
J IMSI of the involved MS
J the handover duration
J the handover end time stamp
J the circuit allocation time stamp.
J Outgoing trunk group and optionally the CIC number.
2.5.2. SERVING MSC
According to a functional option, the serving MSC may generate a charging ticket.
This feature will be used in the scope of 2G / 3G handover between 2 PLMN
operators for accounting purpose.
The CDR contains the main following information:
MSC Identity = ISDN number of the serving MSC and emitting entity type = MSC
serving,
J Call type = handover,
J IMSI of the MS,
J ISDN number of the controlling MSC,
J handover number,
J successful Call termination type,
J time stamps, handover duration,
J incoming trunk group and optionally the CIC number.
30/11/2001 [3628]
2.6. INTERMEDIATE TICKET FUNCTION
Intermediate tickets are sent periodically for the calls which duration exceeds a
defined initial value.
Initial value and period are system parameters. The initial value and the period can
be chosen shorter for a Hot Billing subscriber than for a non Hot Billing subscriber. In
case of MS to MS call with MS1 is a Hot Billing subscriber and MS2 is not a Hot
Billing subscriber, intermediate tickets will be elaborated for MS1 and MS2 in the
same MSC, so the initial delay and the period will be both unique and each one
equal to the respective smallest value.
2.6.1. DESCRIPTION
According to a PLMN functional option:

Case1:
The data collected in intermediate tickets are the same as the one collected for CDR
with the following precisions:
call duration is the duration from conversation starting till last timer expiry.
time stamp: instant of conversation starting.
successful termination type: intermediate CDR
intermediate CDR number is stored in unefficiency cause field. The numbers
are sequential.
At the end of the call a charging CDR is emitted as usual with the information related
to the call.
Beginning of
T1 T2 T3 Tn End of
the call .
call
CDR1
CDR2
CDR3
Global CDR
30/11/2001 [3628]
Case2:
The intermediate CDR is used to charge each part of the call:
from the beginning of the call till the first timer expiry,
between two timers expiry,
from the last timer expiry to the end of the call.
For that purpose the time and date information are related to the part of the call for
which the intermediate CDR has been emitted.
The CDR emitted at the end of the call is related to the last part of the call.
1. call duration is the duration applicable to the intermediate CDR:
It is the intial delay or the period for all intermediate CDR except the last one
It is the time between the last timer expiry and the end of the call for the last
intermediate CDR
2. time stamp:
It is the instant of conversation starting for the first intermediate CDR,
It is the instant of the timer expiry which has caused the previous intermediate
CDR for the otherintermediate CDR,
3. Successful termination type: intermediate CDR except for the last CDR for which
the usual termination of the call is stored.
The intermediate CDR number is stored in unefficiency cause field. The
numbers are sequential or according to a functional option, the last CDR can
have a specific value.
Beginning of
T1 T2 T3 Tn End of
the call .
call
CDR1
CDR2
CDR3
Last CDRx
Note(1) : When a service is invoked during the call, the information related to this
service will be stored in the intermediate CDR, in the field list of invoked
services, if the corresponding functional option is active. This information
will be present in all the following intermediate CDR.
30/11/2001 [3628]
3. CALL RECORD GENERATION SCENARIOS
3.1. LIST OF ABBREVIATION
BCSM Basic Call State Model

CAP CAMEL Application Part
CRN Call Reference Number
DFC Disconnect Forward Connection (CAP operation)
ETC Establish Temporary Connection (CAP operation)
FCI Furnish Charging Information (CAP operation)
IDP Initial-DP (CAP operation)
ISD Insert Subscriber Data (MAP operation)
MNP Mobile Number Portability
REB Report Event BCSM (CAP operation)
SCI Send Charging Information (CAP operation)
SRF Signalling relay function (linked to Mobile Number
Portability)
SRI Send Routing Information (MAP operation)
30/11/2001 [3628]
3.2. MS ORGINATING CALL TO FIXED NETWORK (WITH AND WITHOUT HOT
BILLING)
Fixed
Network GMSC MSC_A MS_A
Originating call
End of call
CDR
Call Type:
Originating call radio
3.3. MS TERMINATING CALL FROM FIXED NETWORK
Fixed
Terminating call
End of call End of call

(1)
CDR1 CDR2
Call Type: Call Type:
rerouted TC Terminating call radio
(1) If the MS_A is a foreign subscriber, GMSC should be considered as

pertaining to the foreign PLMN, so CDR1 generation is not to be considered
in that case (foreign PLMN matter).
N.B. In the case of a call waiting, a CDR is to be generated as for a new

terminating call, independently of the CDR generated for the existing
call.
30/11/2001 [3628]
3.4. MS TO MS (OF THE PLMN) CALL
Fixed MSC_A
Network (= GMSC) MS_A MSC_B MS_B
Originating call (to MS_B)
Terminating call
End of call
End of call
CDR1
Call Type: CDR3
Originating call radio Call Type:
Terminating call radio
CDR2
Call Type:
rerouted TC
N.B. If MS_B pertains to the same MSC as MS_A, the CDR3 (related to the "terminating call
radio" type) is generated in MSC_A, and the call partner id. (calling number received) is
MSISDN nbr (MS_A).
N.B. If MS_B was a foreign subscriber roaming in the PLMN, originating call to MS_B should
be considered as a call to Fixed Network (GMSC being considered as different from MSC_A
and pertaining to the foreign PLMN), and terminating call to MS_B, at MSC_B, should be
considered as a call from Fixed Network. So, CDR2 generation should not be considered in
that case (foreign PLMN matter).
30/11/2001 [3628]
3.5. TERMINATING CALL TO AN MS ROAMING OUTSIDE THE PLMN
Fixed
Network GMSC (1) HLR
Call to MS_A
Fixed Network MSRN(MS_A) (pertaining to VPLMN)

or another MS
Terminating call to MS_A in VPLMN
End of call
CDR
Call Type:
rerouted TC
(1) The GMSC should be considered as pertaining to the HPLMN of the

called MS.
3.6. MS TERMINATING CALL FORWARDED
3.6.1. CALL FORWARDED AT GMSC TO FIXED NETWORK
Fixed
Network GMSC HLR MSC-A MS-A MSC-B MS-B
Call to MS_A
Call forwarded (to Fixed Network) (1)
End of call
CDR
Call Type:
GMSC forwarded TC
(1) If the call from Fixed Network is already forwarded, MS forwarding is only possible towards
a voice mail box (i.e. the forwarded to number given by the HLR and stored in the CDR is the
voice mail box number).
30/11/2001 [3628]
3.6.2. CALL UNCONDITIONALY FORWARDED TO ANOTHER MS OF THE PLMN
Fixed
Network GMSC1 MSC_A MS_A MSC_B MS_B
Call to MS_A
HLR GMSC2 SSP
Call forwarded
(MSISDN nbr (MS_B))
(1)
CDR1
MSRN (MS_B) (2)
or call forwarded (voice

mail box number) Terminating call
End of call
CDR2
Call Type:
rerouted TC or CDR3
rerouted forwarded (2)
or GMSC forwarded TC Call Type:
CDR1
Call Type:
GMSC forwarded TC
(1) Multiply HLR interrogations are not treated in the same transaction.
The forwarded-to number is transaled in the RCP and is routed towards the SSP.
N.B. If the MS_B was a foreign subscriber (MS from another PLMN of the same country),
the call should be considered as a call unconditionally forwarded to Fixed network.
(2) If the MS_B is an MS from the HPLMN who is roaming outside the HPLMN, CDR3 generation
is not to be considered (VPLMN matter).
N.B. If MS_B was a foreign subscriber roaming in the PLMN, terminating call to MS_B,
at MSC_B, should be considered as a call from Fixed Network.
30/11/2001 [3628]
3.6.3. CALL CONDITIONALY FORWARDED TO FIXED NETWORK
Fixed
Terminating call
VLR_A
Forwarding condition
Forwarded-to nbr
(Fixed Netw. nbr)
Call forwarded to Fixed Nertwork
End of call End of call

(1)
CDR1 CDR2 (2)

rerouted TC MSC forwarded TC
(1) If the MS_A is a foreign subscriber, GMSC should be considered as pertaining

to the foreign PLMN, so CDR1 generation is not to be considered in that case
(foreign PLMN matter).
(2) In case of Call conditionally forwarded detected at the HLR (for example a CF
not reachable) CDR2 is not relevant : there is only a ticket "GMSC forwarded TC"
at GMSC.
30/11/2001 [3628]
3.6.4. CALL CONDITIONALY FORWARDED TO ANOTHER MS OF THE PLMN
Fixed
Network GMSC MSC_A MS_A MSC_B MS_B
Terminating call
VLR_A SSP
Forwarding condition
Forwarded-to nbr (MSISDN nbr(B))

End of call
(1)
End of call
(5)
GMSC2
HLR
MSRN (MS_B) or call forwarded (voice mail box number)
Terminating call
End of call
CDR1 End of call
Call Type:
rerouted TC CDR4
CDR2 Call Type:

Call Type: CDR3
MSC forwarded TC
Call Type:
rerouted TC
or rerouted forwarded TC
or GMSC forwarded TC (5)
(1) If the MS_A is a foreign subscriber, GMSC should be considered as pertaining to the foreign PLMN,
so CDR1 generation is not to be considered in the case (foreign PLMN matter).
(2) The forwarded-to number is recognized as an MS ISDN number of the PLMN.
N.B. If the MS_B was a foreign subscriber (MS from another PLMN of the same country), the call should
be considered as a call conditionally forwarded to Fixed Network.
The forwarded-to number is translated in the RCP and is routed towards the SSP.
(3) (CDR4 is not relevant in the case of MS_B forwarding towards a voice mail box).
(4) If the MS_B is an MS from the HPLMN who is roaming outside HPLMN, CDR4 generation is not to be
considered (VPLMN matter).
N.B. If MS_B was a foreign subscriber roaming in the PLMN, terminating call to MS_B, at MSC_B,
should be considered as a call from Fixed Network.
(5) In case of Call conditionally forwarded detected at the HLR (for example a CF not reachable) CDR2 is not
relevant. There is only a ticket "GMSC forwarded TC" at GMSC.
30/11/2001 [3628]
3.7. INTER-MSC HANDOVER
controlling target/serving
BSC MSC-A MSC_B BSC
handover
end of call or
subsequent handover end of call or
subsequent handover
CDR1 CDR2
Call Type:
handover Call Type:
handover
3.7.1. GENERATION OF HANDOVER TICKET AT CONTROLLING MSC
On reception of an ANM (answer) event corresponding to the external HO leg

creation, the RCF records the reception of this event and the following informations:
IAM date, ANM date, outgoing trunkgroup, called number, ho_number and on
option the IMSI of the involved MS.
On reception of an event leading to free the call (TC_ABORT from serving/target
MSC, channel release, external HO leg release) or on old external HO leg release in
case of subsequent handover, the RCF checks if an ANM has been received.
If it is the case, the informations received on ANM are completed (terminating time
stamp registered at release event, release cause) and the handover ticket is
generated.
3.7.2. GENERATION OF HANDOVER TICKET AT SERVING MSC
On sending of the ANM corresponding to the external HO leg creation, the RCF
prepares the CDR with the following informations: IAM date, ANM date, incoming
trunkgroup, HO_number, calling number, MSC number of controlling and the IMSI
of the involved MS.
On reception of an event leading to free the call (TC_ABORT from controlling MSC,
Send End Signal result(TC_END) or EVENT(REL) ) or in case of subsequent handover
on EVENT(REL) or Send End Signal result (TC_END) receipt, the RCF checks if an
ANM has been sent.
If it is the case, the information stored on ANM sending are completed (terminating
time stamp registered at release event, release cause) and the handover ticket is
generated.
30/11/2001 [3628]
3.8. INTER-MSC HANDOVER FOLLOWED BY SUBSEQUENT HO TOWARD A 3TH
MSC
controlling serving target MS

BSC MSC-A MSC_B BSC MSC_C BSC
handover
Subsequent HO
CDR1
CDR2
CDR generated at release
of HO leg between MSC A CDR generated at release
and B of HO leg between MSC A
and B
handover
CDR3 CDR4
CDR generated at the CDR generated the
call release call release
30/11/2001 [3628]
3.9. SHORT MESSAGE SERVICE
3.9.1. SHORT MESSAGE SERVICE MOBILE TERMINATING
SMS-C HLR VMSC_B MS_B

SRI
SRI res
Forward Short Message
RP Data
RP-ACK
FSM result
End of procedure
CDR
Call Type:
Depending on a functional option, Call Records are generated or not in case of SMS
MT/PP reception..
3.9.2. SHORT MESSAGE SERVICE MOBILE ORIGINATING
MS-A VMSC_A SMC_C
SMS-MO
Forward Short Message
End of FSM result

procedure
CDR
Call Type:
originating call radio
Depending on a functional option, Call Records are generated or not in case of SMS
MO/PP sending.
30/11/2001 [3628]
3.9.3. EMERGENCY CALL WITH IMEI
Fixed
Network MSC_A MS_A
Originating call = Emergency call
End of call
CDR
Call Type:
The mobile Subscriber is identified by its IMEI stored in the ticket.
30/11/2001 [3628]
3.10. CALL WITH IN-GSM INVOCATION
3.10.1. ORIGINATING CALL WITH IN-GSM INVOCATION
IN
A B Connect (C)
Fixed
HLR RCF/VLR SCP Network
ISD (A)
At location updating
(OSS, cat)
Call to MS-B
IDP
Connect (C)
End of call
CDR
Call Type:
30/11/2001 [3628]
3.10.2. TERMINATING CALL WITH IN-GSM INVOCATION
IN
A B Connect (C)
Fixed Fixed
Network GMSC HLR SCP Network
terminating call (to MS-B)

SRI
SRIres (MSRN, OSS, category)
IDP
Connect (C)
(1)
End of call
CDR
Call Type:
rerouted TC
(1) If the SCP sends a MSISDN of the HPLMN, then call is not given
to the HLR but is sent towards the SSp for routing purpose.
30/11/2001 [3628]
3.10.3. CALL FORWARDED WITH IN-NETWORK INVOCATION
Fixed
Network GMSC HLR
Call to MS_B
Call forwarded
(forwarded-to-nbr + OSSS)
(IN-Network function)
called nbr = access server + fw-to-nbr
End of call
CDR
Call Type:
GMSC forwarded TC
30/11/2001 [3628]
3.11. CALL WITH CAMEL INVOCATION
CAMEL INVOCATION IN CAP V1
3.11.1. OC WITH CAMEL INVOCATION (OCSI) - CONNECT
CAMEL
A (B) Connect (C)
Fixed
HLR RCP SCP Network
ISD (A)
At location updating OCSI
Call to B
IDP
Connect (C)
End of call
CDR
Call Type:
30/11/2001 [3628]
3.11.2. OC WITH CAMEL INVOCATION (OCSI) - CONTINUE
CAMEL
A (B) Continue (B)
Fixed
HLR RCP SCP Network
ISD (A)
At location updating OCSI
Call to B
IDP
Continue
End of call
CDR1
Call Type:
3.11.3. OC WITH CAMEL AND IN-GSM INVOCATION - CONNECT

CAMEL IN
A (B ) C o n tin u e C o n n e c t (C )
H LR RCP SCP
F ix e d
(C A M E L )
N e tw o rk
IS D (M S -A , O S C I)
A t lo c a tio n u p d a tin g
SCP
C a ll to B
(IN )
ID P
C o n tin u e
E n d o f c a ll ID P
C o n n e c t (C )
CDR
C a ll T y p e :
o rig in a tin g c a ll ra d io
30/11/2001 [3628]
3.11.4. TC WITH CAMEL INVOCATION (TCSI) - CONNECT AND OCSI INVOCATION
CAMEL CAMEL
A (B) Connect (C) Connect (D) or Continue
Fixed Fixed
Call to B SRI (B)
SRI res (TCSI)

IDP (TCSI)
Connect (C) APPLY-OCSI
IDP (OCSI)
Connect (D) or Continue
CDR
Call Type:
rerouted TC
30/11/2001 [3628]
3.11.5. TC WITH CAMEL INVOCATION (TCSI) - CONNECT
CAMEL
A (B) Connect (C)
Fixed Fixed
Call to B SRI (B)
SRI res (TCSI)

IDP
Connect (C)
CDR
Call Type:
rerouted TC
30/11/2001 [3628]
3.11.6. TC WITH CAMEL INVOCATION (TCSI) - CONTINUE
CAMEL
A (B) Connect (B)
Fixed
Network GMSC HLR VLR SCP MSC-B MS-B
Call to B SRI1 (B)
SRI res1 (TCSI)

IDP
Continue
SRI2 (B) and Call Reference Number and MSC-id
SRI res2 (MSRN (B))
end of call
CDR1 (1) CDR2

rerouted TC Terminating call radio
(1) CDR2 has the same value as the CDR described with the case MS terminating call from fixed
Network with the same value of Call Reference Number and MSC-Id of the CDR1 (on GMSC).
30/11/2001 [3628]
3.11.7. TC WITH CAMEL INVOCATION + FORWARDING AT GMSC - CONNECT
CAMEL CF CAMEL
A (B) Connect (B) C Connect (D)
Fixed Fixed
Call to MS (B) SRI1 (B)
SRI res1 (TCSI)

IDP
Continue (B)
SRI2 (B)
SRI res2 (CFC (C), OCSI)

IDP
Connect (D)
CDR
Call Type:
GMSC forwarded TC
30/11/2001 [3628]
3.11.8. TC WITH CAMEL INVOCATION - FORWARDING AT GMSC - CONNECT AND
IN-GSM
CAMEL CF CAMEL IN
A (B) Connect (B) C Connect (D) Connect (F)
Fixed Fixed
SRI res1 (TCSI)

IDP
Continue (B)
SRI2 (B)

IDP
Connect (D)
SCP IN
IDP
Connect (F)
CDR
Call Type:
GMSC forwarded TC
30/11/2001 [3628]
3.11.9. TC WITH CAMEL INVOCATION + FORWARDING AT GMSC - CONTINUE
CAMEL CF CAMEL
A (B) Continue (B) C Continue (C)
Fixed Fixed
SRI res1 (TCSI)

IDP
Continue (B)
SRI2 (B)

IDP
Continue
CDR
Call Type:
GMSC forwarded TC
30/11/2001 [3628]
3.11.10. TC WITH CAMEL INVOCATION + FORWARDING AT GMSC - CONTINUE AND
IN-GSM
CAMEL CFU CAMEL IN

A (B) Continue (B) C Continue (D) Connect (D)
Fixed Fixed
SRI res1 (TCSI)

IDP
Continue (B)
SRI2 (B)

IDP
Continue
SCP IN
IDP
Connect (D)
CDR
Call Type:
GMSC forwarded TC
30/11/2001 [3628]
3.11.11. TC WITH CAMEL INVOCATION + FORWARDING AT VMSC - CONNECT
CFC CAMEL
A (B) Connect (C)
Fixed
HLR VLR RCF SCP Network
ISD (MS-A, OSCI)

At location updating OSCIOCSI)
CFC (network busy, S-INF_IC_I

no paging resp
roaming not allowed)
or
CFC (user busy,

no reply)
complete call
CF-CHECK-I F-CON-F-AD-I
IDP
Connect (C)
F-CON-F-AD-R
CDR
Call Type:
MSC forwarded TC
30/11/2001 [3628]
3.11.12. TC WITH CAMEL INVOCATION + FORWARDING AT VMSC - CONNECT AND
IN-GSM
CFC CAMEL IN-GSM

A (B) Connect (C) Connect (D)
Fixed
ISD (MS-A, OSCI)

no paging resp
or
CFC (user busy,

no reply)
complete call
SCP
IDP (IN)
Connect (C)
IDP
Connect (D)
F-CON-F-AD-R
CDR
Call Type:
MSC forwarded TC
30/11/2001 [3628]
3.11.13. TC WITH CAMEL INVOCATION + FORWARDING AT VMSC - CONTINUE
CFC CAMEL
A (B) Continue (C)
Fixed
ISD (MS-A, OCSI)


no paging resp
or
CFC (user busy,

no reply)
complete call
IDP
Continue (C)
F-CON-F-AD-R
CDR
Call Type:
MSC forwarded TC
30/11/2001 [3628]
3.11.14. TC WITH CAMEL INVOCATION + FORWARDING AT VMSC - CONTINUE AND
IN-GSM
CFC CAMEL IN
A (B) Continue (C) Connect (D)
Fixed
ISD (MS-A, OCSI)


no paging resp
or
CFC (user busy,

no reply)
complete call
IDP
Continue (C)
SCP (IN)
IDP
Connect (D)
F-CON-F-AD-R
CDR
Call Type:
MSC forwarded TC
30/11/2001 [3628]
CAMEL INVOCATION WITH CAP V2
3.11.15. OC WITH CAMEL INVOCATION (OCSI) FOLLOW ON CASE
CAMEL CAMEL CAMEL CAMEL

A (B) Continue Connect (C) Connect (D) Release
HLR RCP SCP

Fixed
At location updating OCSI ISD (A) Network
Call to B IDP
Continue
IAM
REL (normal release)
REB
Connect (C)
End of A-B call
IAM
CDR1 REB
Connect (D)
Call Type :
End of A-C call
IAM
CDR2 REL (normal release)
Call Type : REB

Release
End of A-D call
CDR3
Call Type :
30/11/2001 [3628]
3.11.16. OC WITH CAMEL INVOCATION (OCSI) UNSUCCESSFUL CASE
CAMEL CAMEL CAMEL CAMEL

A (B) Continue Connect (C) Connect (D) Release
HLR RCP SCP

Fixed
Call to B IDP
Continue
IAM
REL (user busy)
REB
Connect (C)
IAM
REL (other cause)
REB
Connect (D)
IAM
REB
CDR
Release
End of A-D call
Call Type :
30/11/2001 [3628]
3.11.17. OC WITH CAMEL INVOCATION (OCSI) TEMPORARY CONNECTION
ESTABLISHING
CAMEL CAMEL CAMEL

A (B) ETC Continue Release
HLR RCP SCP

Fixed
IP
Call to B IDP
ETC
IAM
DFC
End of Temporary Connection
Continue
IAM
REB
CDR-IP
End of A-B call Release
Call Type :
IP
CDR1
Call Type :
30/11/2001 [3628]
3.11.18. OC WITH CAMEL INVOCATION (OCSI) TEMPORARY CONNECTION
ESTABLISHING ON RELEASE
CAMEL CAMEL CAMEL

A (B) Continue ETC Release
HLR RCP SCP

Fixed
Call to B IDP
Continue
IAM
REB
IP
ETC
IAM
DFC
End of Temporary Connection
Release
End of A-B call
CDR-IP
Call Type :
IP CDR1
Call Type :
30/11/2001 [3628]
3.11.19. OC WITH CAMEL INVOCATION (OCSI) INCLUSION OF FCI
CAMEL CAMEL
CAMEL
A (B) Continue Connect (C) Release
FCI#1, FCI#2 FCI#3, FCI#4
HLR RCP SCP

Fixed
Call to B IDP
Continue
IAM
FCI#1 (leg1)
FCI#2(leg2)
REB
Connect (C)
End of A-B call
IAM
FCI#3 (leg1)
CDR1
FCI#4 (leg2)
Call Type :
REB
Release
End of A-C call
CDR2
Call Type :
30/11/2001 [3628]
3.11.20. OC WITH CAMEL INVOCATION (OCSI) INCLUSION OF SCI
CAMEL CAMEL
A (B) Continue -SCI Release
HLR RCP SCP

Fixed
Call to B IDP
SCI
Continue
IAM
ACM
Ei parameter
ANM

End of A-C call
CDR
Call Type :
30/11/2001 [3628]
3.11.21. TC WITH CAMEL INVOCATION (TCSI) CONNECT AND OCSI INVOCATION
CAMEL CAMEL CAMEL

A (B) Connect (C) Connect (D) Connect (E)
Fixed Fixed
GMSC HLR SCP SCP
Network Network
Call to B SRI (B)
SRI res (TCSI)
IDP (TCSI)
Connect (C) APPLY-OCSI
FCI #1 leg1
IDP (OCSI)
Connect (D)
FCI #2 leg1
IAM
REB
End of A-D call Connect (E)
FCI #3 leg1
IAM
CDR1
Call Type:
Rerouted TC REB
ReleaseCall
REB
ReleaseCall
End of A-E call
CDR2
Call Type:
Rerouted TC
30/11/2001 [3628]
3.11.22. TC WITH CAMEL INVOCATION (TCSI) CONNECT (FOLLOW-ON CASE)
CAMEL CAMEL
A (B) Connect (C) Connect (D)
Fixed Fixed
GMSC HLR SCP
Network Network
Call to B SRI (B)
SRI res (TCSI)
IDP
Connect (C)
IAM
REB
Connect (D)
IAM

CDR1
Call Type:
Rerouted TC
CDR2
Call Type:
Rerouted TC
30/11/2001 [3628]
3.11.23. TC WITH CAMEL INVOCATION (TCSI) CONTINUE (FOLLOW-ON CASE)
CAMEL CAMEL
A (B) Continue (B) Connect (C)
Fixed Fixed
GMSC HLR VLR SCP MSC-B
Network Network
Call to B SRI 1 (B)
SRI res 1 (TCSI)
IDP
Continue
SRI 2 (B) and Call Reference Number and MSC-Id
SRI res 2 (MSRN(B))

IAM
REL (normal cause)
REB
Connect (D)
IAM
REL (normal cause)

CDR1
REB
Call Type:
Rerouted TC
CDR2 (1)
CDR3 Call Type:

Terminating Call radio
Call Type:
Rerouted TC
(1) : CDR2 has the same value as the CDR described with the case MS terminating call from fixed
network with the same value of Call Reference Number and MSC-Id of the CDR1 (On GMSC).
30/11/2001 [3628]
3.11.24. TC WITH CAMEL INVOCATION (TCSI) CONNECT TO THE ORIGINAL CALLED
NUMBER (FOLLOW-ON CASE)
CAMEL CAMEL
A (B) Connect (C) Connect (B)
Fixed
Fixed
GMSC HLR SCP MSC-B
Network
Network
Call to B SRI (B)
SRI res (TCSI)
IDP
Connect (C)
IAM
REB
Connect (B)
(1)
SRI (B)
CDR1
SRI res (MSRN B)
Call Type:
IAM
Rerouted TC
CDR2
CDR3
Call Type:
Call Type:
Rerouted TC
Terminating Call radio
(1) : when the GMSC recognizes the original called number , it performs a new HLR interrogation : in
this case the HLR returns the MSRN and the call is rerouted to MSC B.
30/11/2001 [3628]
3.11.25. TC WITH CAMEL INVOCATION (TCSI) CONNECT TO THE ORIGINAL CALLED
NUMBER (FOLLOW-ON CASE) AND FORWARDING
CAMEL CAMEL CAMEL

A (B) Connect (C) Connect (B) D
Fixed
Fixed
GMSC HLR SCP
Network
Network
Call to B SRI (B)
SRI res (TCSI)
IDP
Connect (C)
IAM
REB
Connect (B)
(1)
SRI (B)
CDR1
SRI res (FTN-D)
Call Type:
IAM
Rerouted TC
CDR2
Call Type:
GMSC forwarded TC
(1) : when the GMSC recognizes the original called number , it performs a new HLR interrogation : in
this case the HLR returns the forwarded-to number (D) and the call is forwarded to D.
30/11/2001 [3628]
3.11.26. TC WITH CAMEL INVOCATION (TCSI) CONTINUE (TEMPORARY
CONNECTION ESTABLISHING)
CAMEL CAMEL
A (B) ETC Continue (B)
Fixed
GMSC HLR VLR SCP MSC-B IP
Network
Call to B SRI 1 (B)
SRI res1 (TCSI)
IDP
ETC
IAM
CON
DISCONNECT-FORWARD-CONNECTION
REL (normal cause)
Continue
CDR-IP SRI 2 (B) and Call Reference Number and MSC-Id
Call Type:
IP SRI res 2 (MSRN (B))
IAM
REL (normal cause)
REB
RELEASE CALL
CDR2 (1)
CDR1
Call Type:
Call Type:
Terminating Call Radio
Rerouted TC
network with the same value of Call Reference Number and MSC-Id of the CDR1 (on GMSC).
30/11/2001 [3628]
3.11.27. TC WITH CAMEL INVOCATION (TCSI) CONTINUE (INCLUSION OF FCI)
CAMEL CAMEL
A (B) Continue (B)-FCI#1-FCI#2 Connect (C)-FCI#3 - FCI#4
Fixed Fixed
GMSC HLR VLR SCP MSC-B
Network
Network
Call to B SRI 1 (B)
SRI res1 (TCSI)
IDP
Continue
SRI 2 (B) and Call Reference Number and MSC-Id
SRI res 2 (MSRN (B))

IAM
FCI#1 (leg 1)
FCI#2 (leg 2)
REL (normal cause)
REB
CDR1 Connect (C)
IAM
Call Type:
Rerouted TC FCI#3 (leg 1)
FCI#4 (leg 1)
REL (normal cause)
REB
CDR2 (1)
CDR3
Call Type:
Call Type:
Terminating Call Radio
Rerouted TC
network with the same value of Call Reference Number and MSC-Id of the CDR1 (on GMSC).
30/11/2001 [3628]
3.12. SUPPLEMENTARY SERVICE OPERATION
MS MSC VLR HLR
Register (SS operation request)
MAP-REGISTER-SS
MAP-ERASE-SS
MAP-ACTIVATE-SS
MAP-DEACTIVATE-SS
MAP-INTERROGATE-SS
MAP-REGISTER-PASSWORD
MAP-ERASE-CC-ENTRY
(eventually)
(eventual GET-PASSWORD procedure)
MAP-XXX-result If successful
Release Complete (result)
CDR
Call Type:
SS operation
30/11/2001 [3628]
3.13. MOBILE INITIATED USSD COMMAND
MS MSC VLR HLR
Register (USSD command)
MAP-PROCESS-UNSTRUCTURED-SS-REQUEST (phase2)
MAP-PROCESS-UNSTRUCTURED-SS-DATA (phase1)
(USSD-Request)
(USSD-Notify)
MAP-XXX-result If successful
Release Complete (result)
CDR
Call Type:
SS operation
30/11/2001 [3628]
3.14. NETWORK INITIATED USSD COMMAND
MS MSC VLR HLR
USSD-Request / USSD-Notify
Register (Facility USSD-Request /USSD Notify)
Facility (USSD-Request ack. /USSD Notify ack.)
result
(USSD-Request)
(USSD-Notify)
Release Complete
If successful
CDR
Call Type:
SS operation
30/11/2001 [3628]
3.15. CALLS WITH OPTIMAL ROUTING
3.15.1. OPTIMAL ROUTING FOR BASIC MS TO MS CALLS (SUCCESSFUL CASE)
MS_B is roaming in the country of its Home PLMN or in the country of MS_A PLMN.
MS_A sets up a call to the MS_B.
Fixed MSC_A MS_A MSC_B MS_B

network
and GMSC
OR Terminating Call
End of Call
End of Call
CDR1 CDR3
Originating Call Radio Terminating Call Radio
CDR2
Call Type:
Rerouted TC
30/11/2001 [3628]
3.15.2. OPTIMAL ROUTING FOR BASIC MS TO MS CALLS (UNSUCCESSFUL CASE)
If the GMSC does not recognize MS_B as belonging to an authorized PLMN or if

charging requirements fail, the GMSC routes the call with the MSISDN. At the end of
these calls, the GMSC sends a "transit" ticket.
Fixed MSC_A MS_A SSP Network

network
and GMSC
OR
End of Call
CDR1
Call Type:
Originating Call Radio
CDR2
Call Type:
Transit
30/11/2001 [3628]
3.15.3. OPTIMAL ROUTING WITH EARLY CALL FORWARDING
MS_A sets up a call to MS_B, B is forwarded to a C subscriber.
Fixed MSC_A MS_A HLR_B FTNW_C

network
and GMSC
Call forwarded to C
OR Terminating Call
End of Call
CDR1
Call Type:
CDR2
Call Type:
GMSC forwarded TC
30/11/2001 [3628]
3.15.4. OPTIMAL ROUTING WITH LATE CALL FORWARDING
MS_A sets up a call to MS_B, B is forwarded to a C subscriber.
Fixed MSC_A MS_A MSC_B MS_B FTNW_C

network
and GMSC
Terminating Call
OR
Resume Call Handling (FTN-C)
Release End of Call
Forwarded Call
OR
End of Call
NO CDR
CDR1
Call Type:
CDR2
Call Type:
GMSC forwarded TC
30/11/2001 [3628]
3.16. MOBILE NUMBER PORTABILITY
3.16.1. TERMINATING CALL TO A PORTED MS MNP/SRF METHOD
External
network GMSC MNP/SRF MNP/SRF GMSC
Call to MS_A SRI invk (MSISDN)

SRI invk (MSISDN)
SRI ack (routeing number)
Call to MS A
CDR at the CDR at the

end of the end of the
call call
Number Range Subscription Network

Owner Network
30/11/2001 [3628]

GSM R6E Subscriber Related Event and Call Data Feat - Spec

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

GSM R6E Subscriber Related Event and Call Data Feat - Spec

Uploaded by

Copyright:

Available Formats

FEATURE SPECIFICATIONS

ALCATEL GSM/DCS RCP, HLR

SUBSCRIBER RELATED EVENT AND CALL DATA

SUBSCRIBER RELATED EVENT AND CALL DATA

2. FEATURE DESCRIPTION ......................................................................................... 4

3. CALL RECORD GENERATION SCENARIOS ...........................................................14

SUBSCRIBER RELATED EVENT AND CALL DATA

Charging function in GSM 900/1800 systems is divided into two parts :

SUBSCRIBER RELATED EVENT AND CALL DATA

The Call Data Records (CDRs) are sent:

According to a functional option, for one or more type(s) of call(s), intermediate

2.2. TRANSFER OF CHARGING INFORMATION WITHIN THE LOCAL PLMN

SUBSCRIBER RELATED EVENT AND CALL DATA

SUBSCRIBER RELATED EVENT AND CALL DATA

SUBSCRIBER RELATED EVENT AND CALL DATA

Emitting type MSC X X X X X X X X

SUBSCRIBER RELATED EVENT AND CALL DATA

Circuit IAM emission X X X

SUBSCRIBER RELATED EVENT AND CALL DATA

SUBSCRIBER RELATED EVENT AND CALL DATA

Required FR speech vers.1 X X

2.4. INTERACTIONS WITH OTHER SUPPLEMENTARY SERVICES

In case of Explicit call transfer, two call records are elaborated.

In case of a call waiting, a call record is to be generated as for a new terminating

SUBSCRIBER RELATED EVENT AND CALL DATA

2.5.1. CONTROLLING MSC

2.5.2. SERVING MSC

SUBSCRIBER RELATED EVENT AND CALL DATA

According to a PLMN functional option:

SUBSCRIBER RELATED EVENT AND CALL DATA

SUBSCRIBER RELATED EVENT AND CALL DATA

3.1. LIST OF ABBREVIATION

BCSM Basic Call State Model

SUBSCRIBER RELATED EVENT AND CALL DATA

3.3. MS TERMINATING CALL FROM FIXED NETWORK

End of call End of call

(1) If the MS_A is a foreign subscriber, GMSC should be considered as

N.B. In the case of a call waiting, a CDR is to be generated as for a new

SUBSCRIBER RELATED EVENT AND CALL DATA

SUBSCRIBER RELATED EVENT AND CALL DATA

Fixed Network MSRN(MS_A) (pertaining to VPLMN)

(1) The GMSC should be considered as pertaining to the HPLMN of the

3.6. MS TERMINATING CALL FORWARDED

3.6.1. CALL FORWARDED AT GMSC TO FIXED NETWORK

Call forwarded (to Fixed Network) (1)

SUBSCRIBER RELATED EVENT AND CALL DATA

HLR GMSC2 SSP

MSRN (MS_B) (2)

or call forwarded (voice

SUBSCRIBER RELATED EVENT AND CALL DATA

Call forwarded to Fixed Nertwork

End of call End of call

CDR1 CDR2 (2)

(1) If the MS_A is a foreign subscriber, GMSC should be considered as pertaining

SUBSCRIBER RELATED EVENT AND CALL DATA

Forwarded-to nbr (MSISDN nbr(B))

MSRN (MS_B) or call forwarded (voice mail box number)

CDR2 Call Type:

(2) The forwarded-to number is recognized as an MS ISDN number of the PLMN.

SUBSCRIBER RELATED EVENT AND CALL DATA

3.7.1. GENERATION OF HANDOVER TICKET AT CONTROLLING MSC

On reception of an ANM (answer) event corresponding to the external HO leg

3.7.2. GENERATION OF HANDOVER TICKET AT SERVING MSC