13

APPENDIX 3 :
CAMEL SERVICES
8AS 90001 1892 VH ZZA Ed. 02 Page 13.2

APPENDIX 3 : CAMEL SERVICES

- Charging management by the SCP

The SCP can influence charging:
• by managing the duration of the call

• by sending "ei-parameters" to be sent to the mobile in relation to the AoC

function (for outgoing calls only),
• by giving tariff change times,

• by asking the RCP to send call information at the end of the current call,

• by asking for the CDR (Call Data Record) to include charging information
(up to 2x40 octets, for each RCP-SCP dialogue).

- Notification to the SCP of invocation of a Supplementary Service

RCP

MPTY SS_ Invocation_ Notification

MAP SCP
ECT V3

A CAMEL service can be notified on invocation of the ECT (explicit call transfer)
and/or MPTY (multiparty conference) supplementary services (see ECT and
MPTY sections).
This message is not acknowledged by the SCP.
This function requires use of the MODCAM command to assign the subscriber a
new, specific subscription data item, SS_CSI, to be sent to the VLR on location
updating or when the subscription data item is assigned to the subscriber.
SS_CSI contains:
• The list of SS_codes for which notification is required: ECT and/or MPTY.

• The E.164 address of the SCP to be notified.

©Alcatel University – June 2001

8AS 90001 1892 VH ZZA Ed. 02 Page 13.3

- In-band interchanges between the subscriber and the SCP via an IP

1
MSC SCP
CAP
V2
RCP 5
Restricted
CAP V2
IN
AP
V5
2
4

ISUP V2
Assisting ISUP V2
SSP SSP IP
3 6

SRF
1 Establish_Temporary_Connection
Create (SRF leg) 5 Play_Announcement or
2
Prompt_and_Collect_User_Information
3 IAM to SRF
6 IAM to IP
4 Assist_Request_Instruction

When a CAMEL service has been triggered, the SCP can ask for the
subscriber to be connected to an IP (Intelligent Peripheral):
• During the call setup phase.
• Following call setup failure.
• Following call release (example for "Follow On" management).
The SCP asks the RCP to connect the subscriber to the IP and, since the
RCP does not have the specialised resource function (SRF), it routes the
call to an SRF in the telephone network which sets up dialogue with the SCP
to place itself under its control.
Then the SCP directly manages the IP via the SRF function.

- Choice of alerting pattern by the SCP.

In a terminating call, an SCP can ask, for the current call, for a particular type
of alerting pattern for its CAMEL subscriber.
The SCP supplies a new parameter, “Alerting Pattern”, to the HLR, which
forwards it to the VLR (RCP) which sends it to the MSC (RCP/RCF). Then,
the MSC (RCP/RCF) forwards it to the MS in the “Alerting” DTAP message.
Lastly, on the MS side, locally, this “Alerting Pattern” must be linked to a
ringer.

©Alcatel University – June 2001

8AS 90001 1892 VH ZZA Ed. 02 Page 13.4

- Direct bidirectional MS-SCP communication, off call (USSD operations)

MAP MAP MAP

DTAP
MSC(RCF) VLR HLR SCP

RCP

A subscriber can communicate with his SCP or SCPs and the dialogue can be
initiated by the subscriber or by the SCP.
This function means that the USSD code received from the subscriber can be
compared with the list supplied by a U_CSI subscription parameter
(MODCAM command), so that the address of the SCP concerned can be
obtained.

- Registering a forwarded-to number without checking at the HLR

A CAMEL subscriber can register forwarded-to numbers in a format other
than E.164 (such as, for example, FTNs in a private numbering scheme). In
this case, there is no check on the validity of the FTN, or on interactions with
the GSM call forwarding and call barring services.
The TIFCSI parameter must then be set to YES in the MODCAM command to
enable registration without translation at the HLR.
This number will be sent unchanged:
• To the VLR on location updates,
• To the GMSC for TC calls (SRI_res),
• To the MS when the subscriber queries his call forwarding conditions.

©Alcatel University – June 2001