12.053GPPSubscriber Related Call and Event DataTS
Figure B.4.18 illustrates an incoming call from a fixed network subscriber "A" to a mobile CAMEL subscriber "B". The call is subsequently redirected to a second fixed network subscriber "C" by CAMEL initiated redirection.
The incoming call is routed to the GMSC (1). The GMSC shall create an incoming gateway record for fixed network accounting purposes.
The GMSC interrogates the HLR of the called subscriber in order to fetch the T-CSI (2) and the O-CSI (2). The HLR shall create an HLR interrogation record.
Since subscriber "B" has an active T-CSI and the trigger criterias are met the GMSC requests instructions from the gsmSSF which passes the CAMEL service key to a gsmSCF to indicate which service logic it should apply (3). A terminating CAMEL interrogation record is generated in the GMSC for invoking the terminating CAMEL call handling.
The gsmSCF may interrogate the HLR for subscriber information. As a network option, the operator may refuse to provide the requested information.
The gsmSCF returns a modified destination routing address to the GMSC (without the option "apply O-CSI"). Therefore for the redirection leg (B-C) the CAMEL feature is not invoked.
The GMSC redirects the call to the fixed network subscriber "C" (4). For fixed network accounting purposes the GMSC shall generate an outgoing gateway record as described in subclause B.4.1.
The generated records are subsequently transferred to the OS (A) either as event reports following the release of the connection or when collected by the OS.
The following records are generated in HPLMN in this call scenario:
Incoming gateway record
HLR interrogation record
Terminating CAMEL interrogation record
Outgoing gateway record
Figure B.18: Incoming call handled by CAMEL with redirection initiated and by CAMEL feature
Annex C (normative):
Observed IMEI tickets