Intelligent

Networks

- Shruthi Kadambi

Agenda

IN Overview IN Implementation (SSF code)

Some IN Testing Tips

VLRSCP

Hi, I need Service A

MSCGMSC

We will take care Mr

John We will take care Mr Peter

I need Service A

MSCGMSC

I need Service B

We will take care Mr

JohnWe will take

care Mr Peter

CAP/INAP

Pre-IN Network Post-IN Network

Service A + B

GSM10

GSM10

GSM11

PLM

PLM

Design

Design

Service A

Hi, I need Service B

Service B

Service A + B

Service A

Service B

Pre-IN Network

Service 1 Logic

Service 2 Logic

Service 3 Log ic

Every service must be loaded into every switch’s software!

Post-IN network

IntelligentNetwork

Service 1 Logic

Service 2 Logic

Service 3 Logic

What is IN ?

Intelligent Networks is a concept whereby,in a switching network, service intelligence resides in a central node called an SCP and SSPs transfers control to this node at particular stages in a call so that appropriate service logic can be applied.

IN Services – Examples

Free phone Voice Assisted Dialing Universal Access Number Televoting Sponsored Cell/Sponsored Call Premium Rate Services Virtual Private Network (VPN) Pre-Paid Calling Card Home Zone Service Call completion to busy subscriber Pre-paid Service Personal Numbering Service

IN Advantages

Service Independence Multi-vendor Support Decrease in the time-to-market for new services Seamless multi-vendor environment

IN Nodes and Interfaces

HLR gsmSCFMAP

CAP

CAMELApplication Part

GSM Service Control Function -

GSM SCF Contains the service logic and provides

instructions on how to continue call processing

Home Location Register -HLR can store CAMEL

Subscription Information (CSI)on a per subscriber basis

VMSC/

GMSC

SSF

GSM Service SwitchingFunction - gsmSSF, suspends

call processing and takesinstructions from the SCF

Mobile Station - MSdoes not require anyCAMEL functionality

MAP

INAP

INApplication Part

Functional Elements of IN Network

Service Switching Function (SSF) Service Control Function (SCF) Specialized Resource Function (SRF) Call Control Function (CCF)

CCFSSF

MSC/SSPMessagingComponent

SCP

MSC/SSP IP

Functional Elements of IN Network - Contd

Mapping between functional and physical nodes

Service SwitchingFunction (SSF)

Call ControlFunction (CCF)

Specialized Resource Function (SRF)

Service ControlFunction (SCF)

Service SwitchingPoint (SSP)

Service ControlPoint (SCP)

IntelligentPeripheral (IP)

Service ManagementSystem (SMS)

Signalling TransferPoint (STP)

Service Creation Environment (SCE)

Types of IN Network

Off-Board IN NetworkCapability to route certain types of calls, received at an MSC, to

an off-board IN service provider or service node where the call is

further handled and possibly re-routed.

The routing is supported for following call types:

=> Mobile Subscriber (MS) originations into an MSC.

=>Terminations to a mobile subscriber at a Gateway MSC (GMSC).

ON-Board IN NetworkA network which is directly connected to the Intelligent Node or the

SCP(Service Control Point).

Off Board IN Architecture

ON Board IN Architecture

Differences b/n On-board and Off-board IN

Off-Board IN On-Board IN IN node is not directly connected to the MSC. There is no SSF on the MSC. There needs to be a dedicated IN Trunk always connected to the IN platform.

IN node is always connected to the MSC. SSF functionality is implemented in the MSC.

Different Protocols in IN

INAP (IN Application Part)

(We normally term it as INCS1-R)

CAP (CAMEL Application Part)

CAMEL Phase1

CAMEL Phase2

CAMEL Phase3

CAMEL Phase4 (Not yet implemented)

Note:

CAMEL: Customized Applications for Mobile Network Enhanced Logic

INCS1-R: Intelligent Networks Capability Set1 -Recommendations

IN Call Model

Originating BCSM for IN Terminating BCSM for IN

An IN Call model is an overlay of the basic call state

machine that consists of PICs(Point in Call) and

DPs(Detection Points).

PICs identify MSC activities associated with one or more basic call states of interest to SCP service logic.

DPs represent transitions between PICs and identifies points in call processing at which notifications (to the service logic) can occur and transfer of control (to the SCF) is possible.

Originating BCSM

Terminating BCSM

Types of DPs

TDP-R: Trigger Detection Point – RequestThis DP is statically armed and initiates a CAMEL control relationship when encountered. Processing is suspended when the DP is encountered.

EDP-R: Event Detection Point – RequestThis DP is dynamically armed within the context of a CAMEL control relationship. Processing is suspended awaiting instructions from the gsmSCF when encountering the DP.

EDP-N: Event Detection Point – NotificationThis DP is dynamically armed within the context of a CAMEL control relationship. Processing is not suspended when encountering the DP.

Arming of DPs

EDPs are armed when the SCF sends a RRBE operation to the SSF FSM. This component semantically checks the RRBE parameters as reported by the messaging component. The arming of EDPs is based on the parameters of the RRBE operation, the most important of which are mentioned below:

EventTypeBCSM: indicates which EDP (e.g. O-Answer) to arm or disarm. MonitorMode: indicates the manner in which the EDPs are armed –

EDP-R or EDP-N. It is also indicates disarming of previously armed

EDPs.

Different possible edps that can be armed

Originating side(DP2, DP3)

Terminating side(DP12)

DP4 - Route Select Failure DP5 – O-busy (only leg2) DP6 – O-no_answer (only leg2) DP7 – O- Answer (only leg2) DP9 – O-Disconnect (Can be armed for both leg1 and leg2) DP10 – O-Abandon (only leg1)

No equivalent for Terminating side DP13 – T-busy (only leg2) DP14 – T-no_answer (only leg2) DP15 – T- Answer (only leg2) DP17– T-Disconnect (Can be armed for both leg1 and leg2) DP18– T-Abandon (only leg1)

Note:The usage of “O” and “T” here may be a little confusing. What this actually means is that, eg:o-busy: Busy event is armed for an Originating Trigger. t-abandon: Abandon event is armed for Terminating Trigger.

User profile for Time Dependent Routing

entered into SCF

HLR

gsmSCF

Info sent to HLR toprovision CSI data for

TDR for this subscriber

I would like my callsto be directed to my mobile

every afternoon

Administrator

To provision CAMEL, CSI is provided by the HPLMN operator by administrator means.

OK

CAMEL Subscription Information (CSI)

HLR

ISUP

SRI Ack

SendRouting Info

GMSCB

SSF

VMSCA

VLRA

HLR sends CAMELprofile - CSI - in

SRI Ack to the GMSC

VMSCA

VLRA

SSF

ISUP

HLR

GMSCBSETUP

CSI in Location Update

Originating and Terminating CSI

• Originating-CSI identifies subscriber as having originating CAMEL Services. O-CSI is stored in the VLR as part of subscriber data for roaming subscriber in the VLR area.O-CSI always comes in the CC message from the VLR to MSC.

• Terminating-CSI identifies subscriber as having terminating CAMEL Services. T-CSI is fetched by the GMSC when the HLR of the called subscriber is being interrogated by the GMSC.• Originating-CSI is sent to the GMSC in SRI-ACk if there is a forwarding subscription also.

SSFA

Mobile Originated(DP2) Call setup with IN

MSCVMSC

VLRVLR

SIOC

ISUP IAM

SSF

MSCGMSCSET UP

Call Proc

Assgn Comp

Assgn Req

CC with CSI

VLRSCP

InitDP

Connect to ISUP

SIOC(No IN)

CC

Note:•Services Screened on first: SIOC COS, ODB, BAOC, CUG, IN.• Services screened on second SIOC: Remaining flavours of ODB and barring

MS AWith DP2 subscription

CompleteCall has come with DP2 Subscription. DP2 will be Triggered now and an InitDP query will be sent to the SCP.

SSFA

Mobile Originated(DP3) Call setup with IN

MSCVMSC

VLRVLR

SIOC

ISUP IAM

SSF

MSCGMSCSET UP DP3

number

Call Proc

Assgn Comp

Assgn Req

CC

VLRSCP

InitDP

Connect to ISUP

MS Adials DP3 number

The dialled number willnow be translated and will end in an IN query.

SSF

A

Mobile Terminated Call setup with IN

MSCGMSC

VLRHLR

SRIMS A

ISUP IAM (MS A)

SRI-Ack with CSI

VLRSCP

InitDP

Continue

SRI(No IN)

SRI(MSRN)

Note:•First SRI gets the IN subscription and no other services are checked.•Second SRI gets the MSRN (also, other subcriptions are checked).

Paging

MS A has DP12 subscription

IN messages

Connect Continue ContinueWithArgument ReleaseCall Establish Temporary Connection Connect To Resource Furnish Charge Information Send Charging Information

IN messages - Contd

Requests sent from SCP: Request Report BCSM ApplyCharging Call Information Request Cancel All

Reports sent from MSC : Event Report BCSM ApplyCharging Report Call Information Report

SSF

Disconnect Event DP (Notify)

MSCGMSC

VLRHLR

SRI

ISUP IAM

SRI-Ack with CSI

VLRSCP

SRI(No IN)

SRI(MSRN)

Note:•First SRI gets the IN subscription and no other services are checked.•Second SRI gets the MSRN (also, other subcriptions are checked).

ISUP ACM

ISUP ANM

ISUP IAM

ISUP ACM

ISUP ANM

InitDPRRBE edp-n

leg2 disc

Connect to ISUP

SSF

MSCVMSC

SSF

MSCVMSC

ERB for leg2 disc edp-n

ISUP REL

ISUP REL

SSF

Disconnect Event DP (Interrupted)

MSCGMSC

VLRHLR

SRI

ISUP IAM

SRI-Ack with CSI

VLRSCP

SRI(No IN)

SRI(MSRN)

ISUP ACM

ISUP IAM

ISUP ACM

ISUP ANM

InitDPRRBE edp-r

leg2 disc

Connect to ISUP

SSF

MSCVMSC

SSF

MSCVMSC

ERB for leg2 disc edp-r

Continue

ISUP ANM

ERB (leg2) is sent to SCP and The Call is suspended.The REL message will be Processed only after receiving theContinue from the SCP.

ISUP REL

ISUP REL

Basic Call Events

NU

AO

CI

IDLE State

SSF

WFI State

State Transitions – example with DP2

VLRSCP

InitialDP DP2

Continue

Setup(MS2)

MS A has DP2 Subscription.

MS A

Call Continues to MS2

State Transitions – example with EDP armed

IDLE State

VLRSCP

WFI State

InitialDP

RRBE disc leg2 edp-r

Apply Charging

Continue

Mon-PreAnswer State

Basic Call Events

Answer Event

Mon-PostAnswer State

Disc Event WFI-Post DisconnectState

ApplyCharging Report

Continue

Call Continues

ERB-disc leg2

State Transitions – example with ETC

IDLE State

VLRSCP

WFI State

InitialDP

RRBE disc leg2 edp-r

Apply Charging

ETC

WFETC PreAnswer State

Basic Call Events Answer

Event

WFETC Post Ans State

DFC

Call Continues to IP

Continue

ApplyChargingReport

IP call will be brought down

State Transitions – example ETC - contd

IDLE State

VLRSCP

WFI State

Continue

Mon-PreAnswer State

Basic Call Events

Answer Event

Mon-PostAnswer State

Disc Event WFI-Post DisconnectState

ApplyCharging Report

Continue

Call Continues

ERB-disc leg2

Here ends a Long

Class !!!