I.N. ELEMENTS (I): SCP.

Inés Gil Turón

Telefónica Móviles España, S.A.

Madrid, 3 - 4 Septiembre 2001
 Index
• Who is SCP?
• How to understand SCP?
• I.N Conceptual Model.
• I.N. Distributed Functional Plane.
• Physical Nodes.
• State Machine.
• SCP Protocol Stacks
• Services in SCP
• I. N Service Example.
Telefónica Móviles España, S.A.
Madrid, 3 - 4 Septiembre 2001
 Who is SCP?

• I.N. Brain.
• Leader of all functions which compose IN.
• Manager of every step of a IN call.
• Node which hosts IN services.
• Translator of events and operations.

Telefónica Móviles España, S.A.

Madrid, 3 - 4 Septiembre 2001
 How to understand SCP? (I)
• Place in IN Architecture: SCF is one of the
functional entities in the distributed functional plane.
• Tools to manage every call: SCF counts on call
models which allow him interrupting and directing a call
in any point. This is the state machine which must be known
by every entity of the IN Architecture.
• SCP interfaces: As SCP is the brain of IN, needs as
many interfaces as functional entities exist.

Telefónica Móviles España, S.A.

Madrid, 3 - 4 Septiembre 2001
 How to understand SCP? (II)
• SCP Protocols: In every interface, the SCP can
manage at least one protocol. Depending on this protocol
we can guess which capabilities are available.
• SCE and SMS: A service loaded in the SCP is
composed by logic and data.
SCE is in charge of logic and SMS of the data.

Telefónica Móviles España, S.A.

Madrid, 3 - 4 Septiembre 2001
 IN Conceptual model (I)
• Analysis of the tasks and means neccesary to establish a
telephony communication channel
• As a result, we distinguish several planes. Each one implies
a different level of abstraction.
• Physical plane
• Distributed Functional plane
• Global Functional plane
• Service Plane

Telefónica Móviles España, S.A.

Madrid, 3 - 4 Septiembre 2001
 I.N. Conceptual model (II)
Services
and Service
Service Plane Features

Service
Independent
Building
Global Functional Plane Blocks

Functional
Entities and
Distributed Functional Plane Information
Flows

Physical
Nodes and
Protocol
Physical Plane Interfaces

Telefónica Móviles España, S.A.

Madrid, 3 - 4 Septiembre 2001
 I.N. Conceptual model (III)
FreePhone Call Forward
Services
and Service Reverse Time of Day Calling Party
Features Charging Originating Service Plane
Location

Service Translation
Independent Call Model
Building User Global Functional Plane
Blocks Interaction

Functional
Entities and FEA 1 FEA 3
FEA 4 Distributed Functional Plane
Information FE A FEA 2 FE B FE C
Flows

Physical
Nodes and
Protocol SCP Physical Plane
SSP
Interfaces

Telefónica Móviles España, S.A.

Madrid, 3 - 4 Septiembre 2001
I.N. Distributed functional plane
Service Management
Control Relationship
SMF SCEF
IN Control Relationship

Non-IN Control Relationship

SDF
SCF
Bearer Connection
Control Relationship
SRF

SSF

CCAF CCF CCF CCAF

Telefónica Móviles España, S.A.

Madrid, 3 - 4 Septiembre 2001
 IN Entities: CCF
• Call Control Function
• Is the Call connection function in the network, that provides
call/connection processing and control.
• Controls the establishment of any communication and
detects if it must be controlled by the I.N.
• Provides trigger mechanism to access IN functionality
• Supervises the overall perspective of the call or connection
instance and manipulates this instances as requested by the
CCAF.

Telefónica Móviles España, S.A.

Madrid, 3 - 4 Septiembre 2001
 IN Entities: CCAF
• Call Communication Agent Function
• The interface between the user and the network call control
functionalities.
• Manages the call legs, creating or finishing different
conections, according to the orders received form SCF.
• Maintains call/service state information as perceived by CCF

Telefónica Móviles España, S.A.

Madrid, 3 - 4 Septiembre 2001
 IN Entities: SSF
• Service Switching Function
• Associated to the CCF provides the set of functions required
for interaction between the CCF and a service control
function
• Manages the signalling between the CCF and the SCF
• Extends the logic of CCF to include recognition of service
control triggers and to interact with the SCF
• Modifies call/connection processing functions (In the CCF)
as required to process requests for IN provided service
usage under the control of SCF
Telefónica Móviles España, S.A.
Madrid, 3 - 4 Septiembre 2001
 IN Entities: SCF
• Service Control Function
• Commands call control functions in the processing of IN
services requests
• Interfaces with SSF, SRF and SDF to obtain the necesary
information about the call or the service, or to access to
additional logic.
• Contains the logic and processing capabilities required to
handle IN provided service attempts.

Telefónica Móviles España, S.A.

Madrid, 3 - 4 Septiembre 2001
 IN Entities: SDF
• Service Data Function
• Contains customer and network data for real time access by
the SCF in the execution of an IN provided service
• Interfaces and interacts with other SDFs, if necessary.
• Interfaces and interacts with SCFs, as required

Telefónica Móviles España, S.A.

Madrid, 3 - 4 Septiembre 2001
 IN Entities: SRF
• Specialized Resource Function
• Provides the specialized resources required for User
interaction (digit receivers, announcements,...)
• Interacts with CCF, SSF, SCF
• May contain the logic and processing capability to
receive/send and convert information received from users
• May contain functionality similar to the SCF to manage
bearer connections to the specialized resources.

Telefónica Móviles España, S.A.

Madrid, 3 - 4 Septiembre 2001
Service creation/management IN Entities:
SCEF
• Service Creation Environment function
• Allows services provided in an intelligent network to be
defined, developed, tested and input to the SMF.
• Its output includes:
• Service logic
• Service management logic
• Service data template
• Service trigger information

Telefónica Móviles España, S.A.

Madrid, 3 - 4 Septiembre 2001
Service creation/management IN Entities:
SMF
• Service Management Function
• Allows deployment and provision of IN provided services as
well as the support of ongoing operation

Telefónica Móviles España, S.A.

Madrid, 3 - 4 Septiembre 2001
 Physical nodes
• IN main features:
• Differentiation of functionalities
• Specification of well-defined interfaces and protocols
between them.
• It’s possible to deploy these functions on specialized nodes,
the most suitable ones for each task.
• SDP Realtime oriented database+multiple interfaces
• SSP Switching + signalling
• SCP Logic execution + signalling
• IP Switching+announcement management

Telefónica Móviles España, S.A.

Madrid, 3 - 4 Septiembre 2001
 State Machine (I)
• Basic Call State Model: Its aim is to model any
call. All functional entities must manage the same state
machine. It will be the reference to request or to notify any
action in the call progress.
• IN standard: Every IN Standard has its own state
machine. It defines which kind of service can be offered by
the SCP, depending on the protocol or standard that it uses.

In voice calls, IN success key is the ease

to follow a call by means of BCSM
Telefónica Móviles España, S.A.
Madrid, 3 - 4 Septiembre 2001
 State Machine (II)
• Detection Points (DP): Points in the call at which events
are detected. They are reported to the SCP by the SSP.
• Point In Call: State in a call. One PIC is reached when the
proper DP has been identified by a functional entity.

DP1

PIC1

In the figure, when the event DP1 is detected the call advances till the state PIC1.

Telefónica Móviles España, S.A.

Madrid, 3 - 4 Septiembre 2001
 State Machine (III)
• Kinds of Detection Points:
Δ Static: Also known byTrigger Detection Points (TDP).
They are armed by provisioning (HLR) and data
exchange (Trigger Tables in SSF).
Δ Dynamic: Called Event Detection Point (EDP). They
are requested by SCP, following service logic instructions,
to the SSF in two ways:
· EDP - Request. SSF interrupts the call progress waiting for SCP
instructions
· EDP - Notify. SSF goes ahead the call progress when DP is reached

Telefónica Móviles España, S.A.

Madrid, 3 - 4 Septiembre 2001
 State Machine (IV)
• Originating BCSM. O_Null O_Exception
Origination_Attempt_DP Origination_denied

Authorize_ Origination_Att.
O_Abandon DP
Origination_Attempt_Authorized_DP
Collect_failure
Collected Information
Collected_Information_DP Invalid_information

Analyze_Information
Analyzed_Information_DP Route_Select_Failure DP

Select_Route
Route failure Authorize_failure
Authorize_Call_Setup
O_Called_Party_Busy DP
O_Mid_Call DP
Call Send
O_Disconnect_Complete DP
O_Term_Seized_DP O_No_Answer DP

O_Alerting
O_Mid_Call DP
O_Answer_DP O_conn_failure
O_Disconnect DP O_Active
O_Mid_Call DP
O_Disconnect

Telefónica Móviles España, S.A.

Madrid, 3 - 4 Septiembre 2001
 State Machine (V)
• Terminating BCSM.
T_Null T_Exception
Termination_Attempt_DP Termination_denied

Authorize_ Termination_Att.
T_Abandon DP
Termination_Attempt_Authorized_DP
T_Called_Party_Busy_DP
Select_Facility
Facility_Selected_and_Available_DP Presentation_Failure

Present_Call
Call_Accepted_DP T_No_Answer_DP

T_Alerting
T_Mid_Call_DP
T_Answer_DP T_Active_Failure DP

T_Active
T_Disconnect DP
T_Disconnect_Complete DP
T_Disconnect O_Term_Seized_DP

Telefónica Móviles España, S.A.

Madrid, 3 - 4 Septiembre 2001
 State Machine (VI)
OBCSM DP CS1+ CAP1 CAP2 CAP3
Origination_Attempt_DP
Origination_Attempt_Authorized_DP
Collected_Information_DP
Analyzed_Information_DP
Origination_Denied_DP
Collect_Failure_DP
Invalid_Information_DP
Route_Select_Failure_DP
Authorize_Failure_DP
O_Called_Party_Busy_DP
O_No_Answer_DP
O_Term_Seized_DP
O_Answer_DP
O_Conn_Failure_DP
Route_Failure_DP
O_Mid_Call_DP
O_Disconnect_DP
O_Disconnect _Complete_DP
O_Abandon_DP

Telefónica Móviles España, S.A.

Madrid, 3 - 4 Septiembre 2001
 State Machine (VII)
TBCSM DP CS1+ CAP1 CAP2 CAP3
Termination_Attempt_DP
Termination_Attempt_Authorized_DP
Facility_Selected_and_Available_DP
Call_Accepted_DP
Termination_Denied_DP
T_Called_Party_Busy_DP
Presentation_Failure_DP
T_No_Answer_DP
T_Answer_DP
T_Mid_Call_DP
T_Active_Failure_DP
T_Disconnect_DP
T_Disconnect_Complete_DP
T_Abandon_DP

Telefónica Móviles España, S.A.

Madrid, 3 - 4 Septiembre 2001
 State Machine (VIII)
• CS1+
– Provide enough tools to monitor a call.
– SCP can interrupt a call in any step, as there
are DPs which describe any event.
– On-line charging supplied.
– Typical services: Prepaid, VPN, Personal
Number, Voice Mail, IVR services.

Telefónica Móviles España, S.A.

Madrid, 3 - 4 Septiembre 2001
 State Machine (IX)
• CAP phase 1
– Basic service: mobile originating, forwarded
and terminating calls.
– SCP is just reported in case of Answer or
Disconnect.
– CAP1 provides services based on rerouting.

Telefónica Móviles España, S.A.

Madrid, 3 - 4 Septiembre 2001
 State Machine (X)
• CAP phase 2
– Additional DPs that supply more services.
• On-line charging.
• Call duration control.
– Call monitoring: SCP gets any information about
connection result and calling party behaviour.
Prepaid
VPN
Voice Mail.
IVR services.
Telefónica Móviles España, S.A.
Madrid, 3 - 4 Septiembre 2001
 State Machine (XI)
• CAP phase 3
– Additional TDP: SCP can be invoked once information
had been analyzed.
– New State Machine: GPRS and SMS are modeled
by state machines SCP can offer new services.
– Mobility Management Support.

Telefónica Móviles España, S.A.

Madrid, 3 - 4 Septiembre 2001
 State Machine (XII)
• We have seen the main BCSM, owned by
SCP and SSF.
• There are simpler state machines:
– Leg.
– SRF Interactions.
– Supplementary Services.
– GPRS.
– SMS

Telefónica Móviles España, S.A.

Madrid, 3 - 4 Septiembre 2001
 State Machine (XIII)
• GPRS state machines Idle

PDP Context Disconnection

Points of Association

PDP Context Establised

C_Exception

Detached PDP_Context_Setup
Detach

AD_Exception PDP Context Establised ACK

Attach

Attached PDP_Context_Establ

Change of position session

Change of position session

Attach/Detach in SGSN PDP Context in SGSN

Telefónica Móviles España, S.A.

Madrid, 3 - 4 Septiembre 2001
 State Machine (XIV)
• SMS state machine.

SMS Null&Start&Authorize SMS_Exception

O_SMS_Collected_Info_DP

SMS Analyse & Routing

O_SMS_Failure_DP

O_SMS_Submitted_DP

Telefónica Móviles España, S.A.

Madrid, 3 - 4 Septiembre 2001
 State Machine (XV)
• This hard standardization guarantees
interoperability, which can be considered
a lack in newer implementations.
• An IN solution doesn’t need the global
IN implementation: a subset of the standards
can be enough We must be aware and
check capabilities when evaluating vendors.

Telefónica Móviles España, S.A.

Madrid, 3 - 4 Septiembre 2001
 SCP Protocol Stacks
SDP

TCP/IP?
CS1+ MAP
SMS/SCE Non-Standardized TCAP SDP/HLR
SCCP
MTP
SCP

CS1+ CAP INAP CAP

TCAP TCAP
SSF SCCP SCCP
SRF
MTP MTP

Telefónica Móviles España, S.A.

Madrid, 3 - 4 Septiembre 2001
 Services in SCP (I)
• We can divide services into two parts:
Logic and Data.
• Logic:
– Set of operations executed along an IN call.
– Implementation:
• SIBBs. Logic modules for each operation.
Function reusing
• Any programming language (C, C++, etc.)

Telefónica Móviles España, S.A.

Madrid, 3 - 4 Septiembre 2001
 Services in SCP (II)
• Data.
– Global Data.
• Affecting every part of the logic.
• They allow a service to be used by several
operators Market adaptations.
– Local Data.
• Affecting just a part of logic.
• They allow reusing logic.
– Customer Data.
• They define customer characteristics for the service

Telefónica Móviles España, S.A.

Madrid, 3 - 4 Septiembre 2001
 IN service Example
IDP
SSF IDP

IN user ETC
detected Req. SCF
ETC
Dial CON
Req.
900123123 CCF
CON
SS7 SDF
CCAF ARI

P&C
Customer Data
IAM
ARI P&C
ACK

P&C Subscription 900123123

91456789
P&C Location A
SRF ACK Alerting Location B 93123456
91456789

Telefónica Móviles España, S.A.

Madrid, 3 - 4 Septiembre 2001