Any time interrogation (ATI) enables a CAMEL service to obtain subscriber information through the HLR location information

tion and subscriber state subscriber is identified with IMSI or with MSISDN Example cases of ATI include: o Within the context of a call Real distance charging (RDC) RDC entails that the charge for an MO call is based on the location of the calling and called subscriber Home Zone a VPN that is controlling a call to a GSM subscriber may apply ATI to check whether the called party is in her home zone o Outside the context of a call Location server: a location server may request the subscribers location & state periodically or when requested by an application. Call completion: a call completion service may poll the subscribers state, to establish a call when a subscriber has become idle.

MAP messages for the VLRHLR interface Location update(LU) request the HLR of that subscriber for GSM subscription data Restore data(RD) VLR uses MAP RD when it needs to reload its subscription data Insert subscriber data (ISD) transfer of GSM subscription data to VLR, may be used in response to MAP LU or MAP RD Delete subscriber data (DSD) HLR uses MAP DSD to remove subscription data from the VLR Provide subscriber information (PSI) data that may be obtained with MAP PSI includes location information and subscriber state, Within the context of CAMEL, the HLR may use MAP PSI for the following procedures: (1) MT call handling ; (2) ATI ; optimal routing (OR) Provide roaming number (PRN) HLR uses MAP PRN to obtain a mobile station roaming number (MSRN) from the VLR; For MT calls that are subject to CAMEL handling HLR may include the call reference number (CRN) and GMSC address (GMSCA)

GMSCHLR interface Send routing information (SRI) GMSC uses MAP SRI for the purpose of MT call handling, includes an indication of the CAMEL phases that are supported by that GMSC

gsmSCFHLR Any time interrogation (ATI) request the HLR for subscriber information. ATI may be used at any moment, also outside the context of a call following subscriber data: Subscriber location and subscriber state

MAP messages for the MSCGMSC interface 1. Resume call handling (RCH) VMSC sends MAP RCH to the GMSC, in order to initiate ORLCF, it may include CAMEL subscription information, specifically O-CSI and D-CSI (CAMEL phase3+) Main features offered by CAMEL Phase 1

1. 2. 3. 4.

MOC MTC MFC ATI

1. MO calls that are established by a CAMEL subscriber may be subject to CAMEL control, except emergency calls. When the user enters 112 on the keypad, a TS12 service is started. When a subscriber establishes an MO call, the MSC will start a basic call handling process(checking whether the subscriber has a subscription, if not MSC rejects the call attempt before CAMEL is invoked) and check for call barring, check for O-CSI which indicates CAMEL service start. After basic call handling, MSC hand over call control to gsmSSF which invokes the subscribed CAMEL service, suspending gsmSFF while waiting for gsmSCF response. gsmSCF can send; Continue (CUE) the gsmSCF instructs the gsmSSF to establish the call to the dialled destination Connect (CON) the gsmSCF instructs the gsmSSF to establish the call to the destination that is contained in CAP CON Release call (RC) the gsmSCF instructs the gsmSSF to release the call If the gsmSCF uses CAP CUE or CAP CON, then the call processing in the MSC continues, and it sends ISUP IAM. Wheater the CAMEL service will remain actve depend on arming DPs in OBCSM. If armed it stays on, if not a single one is armed it treminates. CAMEL v1 is limited because it doesn't report events like busy, no reply, etc. Interntional VPN service, translates dialed short number into public number within the same VPN group. VPN service may ensure that the called party receives the calling partys VPN number on her display, instead of the calling partys public number. When dialling, short num is translated into public num, then the short num is transfered via CAP CON. When a call crosses an international boundary, numbers may not be is not transported in the ISUP signalling. 2. Mobile-terminated CallsWhen a call is established it is routed to the HPLMN of the destination subscriber. When the call arrives in the HPLMN of the called subscriber, GSMC analyses the destination of the call. The GMSC knows, by configuration, which number ranges represent MSISDN series of this operator. Hence, the GMSC can determine that this incoming call is destined for a subscriber of this network. If the call was established in an MSC of the same network, then the originating MSC, handling the MO call, may at the same time act as a GMSC for the MT call. since the GMSC does not know whether the called subscriber is a CAMEL subscriber, the GMSC is prepared to receive either MSRN (non-CAMEL call) or T-CSI (CAMEL call). This info is then used for CAMEL service invocation. GMSC forwards the T-CSI and other data such as location information, subscriber state and IMSI, to the gsmSSF and the sameprocedure as for MOC applies. Location information that is reported to the gsmSCF is, however, not the current location information, so the age of location parameter in the location information serves as an indication of the reliability of the location information. If CAMEL determins that the call can contimue the gsmSCF sends CAP CUE or CAP CON to the gsmSSF : CAP CUE the GMSC continues call establishment to the called MSISDN CAP CON when the CAMEL service uses CAP CON, the following applies o if the destination routing address in CAP CON argument is identical to the called party number in CAP IDP, then CAP CON is treated as CAP CUE with additional information

If the destination routing address in CAP CON argument differs from the called party number in CAP IDP, then CAP CON is treated as a call forwarding instruction

Before the CAMEL service sends CAP CUE or CAP CON, it may use CAP Request Report BCSM (RRB) to arm the answer event and the disconnect event. Double HLR interrogation mechanism : First interrogation the first MAP SRI sent from GMSC to HLR is the MAP SRI at the beginning of MT call handling. At this point, the GMSC does not know whether CAMEL will apply for the call. The GMSC may receive MSRN or T-CSI. The GMSC may also receive FTN from HLR Second interrogation the second MAP SRI sent from GMSC to HLR is the MAP SRI after the GMSC has received CAP CUE or CAP CON,the purpose is to obtain MSRN from HLR, not T-CSI, since MP SRI is stateless, it indicates in it that its the second SRI and applies T-CSI suppression. The HLR uses MAP PRN to obtain the MSRN from the VLR which in returned in MAP SRI-Res and enables the GMSC to complete the call.

After that, ISUP ACM is sent and ANM after that which can trigger Event report BCSM being sent to gsmSCF. ISUP REL can triger it also. Call set up Failure for MT Call Incoming call barring when the HLR determines that the call may not be established to the subscriber due to call barring or ODB Non-subscribed basic service when the subscriber does not have a subscription to the requested basic service for the call, e.g. data call Subscriber not registered in VLR presuming no call forwarding is active for this condition, the HLR will not return CAMEL data to the GMSC Subscriber detached the detached condition is normally not known in HLR; as a result, the HLR returns the T-CSI to the GMSC, but fails to deliver MSRN fron the VLR in the second interrogation Busy, no Reply, no paging response when the VLR has allocated an MSRN for the call to the subscriber and the GMSC has routed the call to the VMSC, the VMSC attempts to deliver the call to the called subscriber. The conditions no paging response, subscriber busy and no reply all lead to call establishment failure

3. Mobile-forwarded Calls Call forwarding occurs when the network has determined that a mobile terminating call cannot be delivered to the called subscriber and an alternative destination for that call is available. MT call handling in GSM is partly performed in GMSC and partly performed in VMSC. This two-fold handling of MT calls has resulted in the following grouping of call forwarding kinds: Early call forwarding early call forwarding takes place in the GMSC. When the HLR determines that call forwarding should be applied to a call, then the HLR sends the FTN to the GMSC Late call forwarding late call forwarding takes place in the VMSC. When the GMSC has received an MSRN from the HLR and has routed the call to the VMSC of the called subscriber, the VMSC may determine that call forwarding should be applied to this call. The VMSC will forward the call to the alternative destination, as indicated by the FTN that is present in the subscribers profile in VLR. A prerequisite for call forwarding from the VLR is that the HLR has previously sent the corresponding FTNs to the VLR, typically during location update.

Early call forwarding has an advantage over late call forwarding. In the case of early call forwarding, no ISUP traffic link is established from the GMSC to the VMSC. Call Forwarding Unconditional unconditional (CFU) is the situation that the subscriber has defined in the HLR that all incoming calls shall be forwarded to a particular destination; this destination is defined by the FTN unconditional (FTN-U). when the gsmSSF reports answer to the gsmSCF, this answer notification relates to the forwarded-to-destination, not to the called subscriber because the CAMEL service is not aware of CF.

Call Forwarding Not Reachable Subscriber marked as detached in HLR. The subscriber has not performed a location update in the VLR for a configurable period; the VLR has therefore purged the subscriber from its internal register and has informed the HLR. The HLR marks the subscriber as detached. If a call arrives for this subscriber, then the HLR returns the FTN-not reachable (FTN-NRc) to the GMSC. Hence, this form of CFNRc is early call forwarding Subscriber marked asdetached in VLR. The subscriber remains registered in theVLR but marked as detached. VLR does not inform the HLR.When the HLR receives the MAP SRI for this subscriber, it will not send the FTN-NRc to the GMSC. HLR returns T-CSI to GMSC, resulting in CAMEL service invocation. When the GMSC sends the second interrogation the HLR sends MAP PRN to the VLR. The VLR returns MAP PRN error to the HLR; the HLR sends the FTN-NRc to GMSC. The GMSC now performs the call forwarding. No paging response - When a call arrives for a subscriber and the call is delivered to the VMSC, then the VMSC will page the subscriber. If the VMSC does not get paging response, then the CFNRc condition occurs, provided that an FTN-NRc is registered in the VLR. The VMSC will now establish a call to the forwarded-to-destination. This forwarded call will be subject to a CAMEL service, provided that O-CSI is present in the VLR. This call forwarding is late call forwarding. The no paging response condition occurs when the subscriber is marked

as Idle in the VLR, but is temporarily out of radio coverage. If the subscriber is out of radio coverage for a certain duration, then the VLR marks the subscriber as Detached. Call Forwarding Busy If a subscriber busy condition occurs in the VMSC and the subscriber has an FTN-Busy (FTN-B) registered for the basic service of the incoming call, then Call Forwarding Busy (CFB) occurs. CFB is always late call forwarding. Network-determined user busy when the mobile terminated call arrives at the VMSC and the subscriber is engaged in a CS call, then the VMSC determines that the subscriber is busy. User-determined user busy when a subscriber receives a call and the call reaches the alerting phase, the subscriber may reject the incoming call (push the call away). The user determines that she is busy (not willing to answer the call), not the network.

Call Forwarding No Reply No reply occurs when a call that is offered to the subscriber is in the alerting phase, but the call is not answered within a pre-defined time. If the subscriber has an FTN-No Reply (FTN-NRy) registered for the basic service of the incoming call, then call forwarding No Reply (CFNRy) occurs. CFNRy is always late call forwarding. SCP-induced Early Call Forwarding When the CAMEL service induces call forwarding, it provides the following information to the GMSC in CAP CON : Original called party ID Redirecting Party ID Redirection Information

Optimal Routing of Late Call Forwarding pogledati ATI

Subscription Data
CAMEL phase 1 makes use of CAMEL subscription information (CSI) (Table 3.7). Subscription element O-CSI T-CSI Description Originating CSI Terminating CSI Used in which entity MSC/VLR, GMSC GMSC

O-CSI and T-CSI contain the following elements. gsmSCF Address - The gsmSCF Address identifies the location of the SCP where the CAMEL service resides. This address is in the format of a GT. the gsmSCF address may be used from any visited PLMN, to address a unique CAMEL service in the HPLMN of the served subscriber. If the MSC or GMSC invoking the CAMEL service resides in the HPLMN of the served subscriber, then the CAMEL service invocation request may be sent directly to a STP in that HPLMN If the MSC or GMSC invoking the CAMEL service resides in a PLMN which is not the HPLMN of the served subscriber, then the GT for this service is used to send the CAMEL service invocation request to a gateway STP of the PLMN, from where the service invocation request is forwarded to the HPLMN of the served subscriber.

Service Key The service key (SK) identifies the CAMEL service in the gsmSCF. The serving MSC or GMSC places the SK from O-CSI or T-CSI into CAP IDP. The SCP platform uses the SK to select the corresponding CAMEL service Trigger Detection Point The TDP identifies the point in the BCSM from where the CAMEL service is invoked. For CAMEL phase 1 (and phase 2), service triggering takes place at a defined point in the BCSM. These DPs are: mobile originated calls (O-BCSM) DP collected info; mobile terminated calls (T-BCSM) DP terminating attempt authorized

Default Call Handling The default call handling (DCH) parameter in O-CSI and T-CSI is used to define gsmSSF behaviour in the case of signalling failure between gsmSSF and gsmSCF. One of the following behaviours for the gsmSSF may be set in O-CSI or T-CSI: continue (without CAMEL) and release (release call).

Basic Call State Model

The BCSMs define the process in the MSC or GMSC, for the processing of a call. The O-BCSM is for the processing of MO and MF calls; the T-BCSM is for the processing of MT calls. It contains defined points in the state model where the MSC may interact with the gsmSSF. The gsmSSF may, in turn, interact with the gsmSCF at these points. Originating Basic Call State Model The DPs are the points in the call where interaction with the CAMEL service may take place. When the call is established, the BCSM is started in the state O Null; the CAMEL service is started from DP Collected Info Terminating Basic Call State Model The T-BCSM is started in the state T Null and the CAMEL service is started in DP terminating attempt authorized. O-BCSM DP Collected Info - When an MO call or MF call is established, the O-BCSM is started at this DP. If OCSI is available for the subscriber, then the MSC hands call control over to the gsmSSF, which invokes the CAMEL service. The call processing is suspended in this DP, until the gsmSCF has responded with a call continuation instruction. DP O Answer - When the MSC receives ISUP ANM or ISUP CON for the call, the O-BCSM transits to DP DP O Disconnect - When the call is cleared, the O-BCSM transits to DP O Disconnect T-BCSM has pretty much the same DPs TDP When a DP is statically armed as TDP, the BCSM, when transiting to that DP, invokes a CAMEL service. The presence of O-CSI in the MSC constitutes the static arming of DP Collected Info and the availability of T-CSI in the GMSC constitutes the static arming of DP Terminating Attempt Authorized. The other DPs for CAMEL phase 1 may not be armed as TDP. EDP A CAMEL service for an MO or MF call may arm DP O Answer and DP O Disconnect; a CAMEL service for an MT call may arm DP T Answer and DP T Disconnect. When the CAMEL service arms DP O Disconnect or DP T Disconnect, it specifies the call leg for which the arming applies. BCSM State Transitions Call handling process in (G)MSC transits from one PIC in the BCSM to the next PIC in the BCSM. The normal sequence for an MO call would be, for example, O Null analyse, routing and alerting O Active O Null. Not all calls follow the transitions that are defined for the BCSM. The SCP may at various places in the BCSM induce a call release. These state transitions are referred to as transitions beyond basic call.

gsmSSF Process The gsmSSF process acts as a relay between MSC and gsmSCF. The gsmSSF may report call-related events to the SCP. The gsmSSF may also suspend the call handling process in the MSC, in order to enable the CAMEL service to influence the call handling process. FSM states for the process: Idle - this state of the FSM indicates that no gsmSSF process is currently active for the call. Wait for Request (WFR) - this state applies when the MSC has invoked an instance of a gsmSSF process. The gsmSSF is now waiting for an indication from the MSC about the specific DP that was met Waiting for Instructions (WFI) - the gsmSSF has contacted the gsmSCF and has suspended the call handling process. The call handling process remains suspended until the gsmSSF has received an instruction from the gsmSCF regarding continuation of the call handling Monitoring (MON) - This state applies when call handling in the MSC is in progress and the gsmSSF has at least one DP armed for reporting

Tssf Timer The Tssf timer is a timer that is embedded within the gsmSSF process. Its function is to govern the response from the gsmSCF when the gsmSSF FSM is in the state WFI. This is to prevent the MSC keeping resources allocated when the gsmSCF would not respond, e.g. in the case of an SS7 communication problem. gsmSSF takes the following actions in that case: apply default call handling (DCH); place an indication in the CDR about the DCH event; close the CAMEL dialogue; terminate the gsmSSF process.

CAMEL Application Part

CAP operations are described on two levels in the CAMEL specifications: functional level and syntax level. Initial DP The gsmSSF sends CAP IDP to the gsmSCF to start a CAMEL service. The sending of CAP IDP results from successful TDP processing during call establishment. Subscriber-specific the parameter is obtained from the subscription data, MSC-generated the parameter is determined by the MSC or by the gsmSSF, Call-specific the parameter is obtained from the signalling flow in the access network Request Report BCSM Event Report BCSM Continue The CUE operation is used by the gsmSCF to instruct the gsmSSF to continue call handling

Connect The Connect (CON) operation may be used in response to CAP IDP. CAP CON enables the CAMEL service to define or modify specific parameters in the call flow. Destination routing address, Calling Partys Category (CPC), Generic number (GN), O-CSI applicable, Suppression of announcements (SoA), Original called party ID, Redirecting party ID, Redirection information. A gsmSSF may copy original called party ID, redirecting party ID and redirection information, when received in CAP CON, transparently to ISUP IAM for the outgoing call. Release Call The gsmSCF may use CAP release call (RC) to disallow call establishment or to tear down an ongoing call. CAP RC carries a mandatory parameter, cause, which may be used in the ISUP signalling to the calling party. Activity Test The activity test (AT) is used for testing the CAMEL dialogue between the gsmSCF and the gsmSSF. The SCP may send CAP AT at regular intervals to the gsmSSF, e.g. every 15 min. The only function of CAP AT is to verify the existence of the CAMEL dialogue.

Service Examples
Virtual Private Network Pre-paid Route Home Short Number Dialling with CLI Guarantee