In Imp

1
© Konsultointi Martikainen Oy 1999
Intelligent Networks
2
Preface © Konsultointi Martikainen Oy 1999
• Intelligent Network (IN) is one concept to specify

telecom services, and it has emerged from technical,
business and protocol engineering point of view.
• Intelligent Networks are used by teleoperators for

creation and management of value added services in
telecom networks.
• Originally, IN has been applied in telephone and voice

services, but today its meaning is also growing in the
service integration of mobile and fixed telephone
networks and as gateway to Internet based networks.
3
Contents © Konsultointi Martikainen Oy 1999
• Introduction and rationale 5

• History of IN 11
• IN Architecture 22
• IN Architecture Evolution 24
• IN Services 28
• Introduction to Signaling System no. 7 38
• IN Conceptual Model 50
– Service Plane 53
– Global Functional Plane 69
– Distributed Functional Plane 83
– Physical Plane 112
4
Contents © Konsultointi Martikainen Oy 1999
• Service Creation and Management 124

• IN Markets 132
• Future of Telecommunications :
– TMN 135
– CAMEL 136
– Broadband and Mobile IN 141
– MBS 143
5
Intelligent Network (IN) © Konsultointi Martikainen Oy 1999
• Intelligent Network offers added value

• Open standards, vendor independence
• Rapid service creation and deployment
• Customized services to users
• Centralized service management
• New opportunities to make business i.e. new
services, markets and customers
• Rapid adaptation to market needs and competition
 source of Competitive Advantage
6
Value of Telecom Services © Konsultointi Martikainen Oy 1999
Broadband
VALUE
Mobile
Digital
DIGITAL MEDIA
VANS AND MOBILE SERVICES
CONNECTIVITY SERVICES
1990 1995 2000 2005

7
Telecom Discontinuities © Konsultointi Martikainen Oy 1999
First Wave (1994-2000)

– Network operators and Service Providers
– Alliance building, fight for market share
– Mobile and Value Added growth (IN, data)
– Internet becomes the Middleware
Second Wave (2000-2006)
– Broadband access technology solved
– Service and Content Providers
– Third generation mobile technology
Third Wave (2006 - )
– New service and content control based
architectures
8
Computer Controlled Services © Konsultointi Martikainen Oy 1999
TMN = Telecommunication Management Network

IN = Intelligent Network
Differentiation
* * * c u s to m e r s e g m e n ts * * *
Dynamic numbering / networks
Local Mobile Business
TM N
N a r r o w b a n d
B r o a d b a n d
IN
Logical subscribers Logical services
*** o p e n te c h n o lo g y ***
Separation of IN and 9
Basic Services © Konsultointi Martikainen Oy 1999
IN Service Logic
Basic and Hooks Hooks Hooks

supplementary
services Basic call Basic call Basic call
offered
processing processing processing
to customers
NODE A NODE B NODE C

Intelligent Network 10
terminology © Konsultointi Martikainen Oy 1999
Functional Entity Definition Related products

Call Control A ccess Function Provides the means f or user to access the CCF; handles call setup, Service Sw itching Point (SSP),
(CCA F) termination, hold-on etc... can also provide user w ith CLA SS Netw ork A ccess Point (NA P)
(Custom Local A rea Signalling Services) properties
Call Control Function (CCF) Provides the means f or establishing and controlling bearer services Service Sw itching Point (SSP)
on behalf netw ork users; the CCF ref ers to call and connection
handling in classical sense
Service Sw itching Function Provides the means to recognise calls requiring IN service Service Sw itching Point (SSP)
(SSF) processing, and to interact w ith call processing and service logic on
behalf of these calls
Service Control Function Provides the logical control applied to a call requiring IN service and Service Control Point (SCP), adjuct
(SCF) handles service related processing activities, e.g. analysis (A D), Service Node (SN)
translattion, screenig, routing; in other w ords the SCF contains the IN
service logic
Service Data Function (SDF) Handles the access to service-related and netw ork data and Service Control Point (SCP), adjuct
provides a logical view of the data to the SCF (A D), Service Node (SN)
Specialised Resource Provides end-user interaction w ith the IN-structured netw ork Service Node (SN), Intelligent
Function (SRF) through control over resources such as DTMF receivers, voice, Peripheral (IP)
recognation capabilities, protocol conversion, announcements etc.
Service Management Provides service provisioning deployment and management control; Service Management System (SMS)
Function (SMF) the SMF allow s access to all IN f unctional entities f or the transf er of
inf ormation related to service logic and service data
Service Creation Environment provides the capability f or the creation, verif ication and testing of Service Creation Environment (SCE)
Function (SCEF) new IN services
History of Intelligent 11
Networks © Konsultointi Martikainen Oy 1999
“Intelligence”
CS2
AIN
CS1 Rel 1
AIN
CS
Rel 0.2
AIN
IN/2 Rel 0.1
IN/1+
IN/1
Feature
Centralized Node
databases,
Support for CC and
Mgmt 800 -services
SPCs
Electro-
mechanical
Relay
switches
1960 1970 1980 1985 1990 1995

Time
• SPC (Stored Program Control) exchanges in

1960s
• Computer technology and telephone
network merged
• Routing intelligence in switches
• Offered services call waiting and traditional
PBX (AT&T)
• Mid-1970s support for management and
maintenance through Operations Support
System (OSS)
• Databases located at network control points

• Value added services practical and
economical to offer
• Centralized databases in 1980s (AT&T)
• First calling card and 800-services
• AT&T Software Defined Network (“pre-
VPN”)
• Term ‘Intelligent Network’, Bellcore 1984
• ‘Feature Node’ concept 1985 (Ameritech)

– total separation of services and switching
– vendor independence
– new services quickly and economically
– services offered by third party
• IN/1, Bellcore 1986
• Centralized architecture
– SCP only a simple “number translator”
– in service provision both SSP and SCP had to
be updated
– SS#7 as common channel

• IN/2, Bellcore 1987
• Expanded IN/1 functionality
– no switch dependency
– rapid deployment of new services
– IP concept was introduced
– project timescales discovered unrealistic
• IN/1+, Bellcore 1988
• Interim, downsized solution to IN/2
• Timescales unrealistic, too
• Both IN/2 and IN/1+ were rejected

• AIN (Advanced IN), Bleacher 1989
• Influenced by IN/2
• In co-operation with other organizations
– solid industry standard
– better interoperability with different systems
– foundation for ideal IN-systems
• Service-, switch- and equipment-
independent IN-systems
• Stepwise development via number of

releases
– AIN Rel. 0.1, IN/1-based implementations
– AIN Rel. 0.2, additional specifications for Rel. 0.1
– AIN Rel. 1, target AIN-architectures
• AIN Rel. 1 is due out 1995-8
CS (Capability Sets), ITU-T, ETSI 1989 -
• European equivalent to AIN
• Define basic IN-services (e.g. freephone,
premium rate and UPT)
• Service independent building blocks, SIBs

– basic IN-service functional entities (e.g. digit collect and
analyze, time and date functions)
– ideal service creation by grouping SIBs
• Development in phases
– CS1, published 1993
– CS2, published 1999
– CS3, design started 1997 CS3
– CS2 specifies management CS2
interfaces and call-unrelated
switching functions
CS1
– CS3 focus on mobility management
(e.g. GSM 2+ and 3 integration) and I
nteroperability of IN and other networks (e.g. CAMEL)
Standards © Konsultointi Martikainen Oy 1999
Capability sets
1
CSx
1
2
CS2 1
1 2
3
CS1 2
3
3
T1 T2 Tx Time
1 IN Concept and Modeling
2 Definition of next CS
3 Recommendation for CSx
20
Structure of IN Standards © Konsultointi Martikainen Oy 1999
Q.12XY with X and Y as follows:

X Y
00 - General
10 - CS1 1 - Principles, Introduction
20 - CS2 2 - Service Plane (not included for CS1)
30 - CS3 3 - Global Functional Plane
40 - CS4 4 - Distributed Functional Plane
50 - CS5 5 - Physical Plane
60 - CS6 6 - For future use
70 - CS7 7 - For future use
80 - CS8 8 - Interface Recommendations
90 - Vocabulary 9 - Intelligent Network Users Guide
Standards © Konsultointi Martikainen Oy 1999
Recommendation Q.1200 Q-Series Intelligent Network Recommendations Structure

Recommendation Q.1201 Principles of Intelligent Network Architecture
Recommendation Q.1202 Intelligent Network - Service Plane Architecture
Recommendation Q.1203 Intelligent Network - Global Functional Plane Architecture
Recommendation Q.1204 Intelligent Network - Distributed Functional Plane
Architecture
Recommendation Q.1205 Intelligent Network - Physical Plane Architecture
Recommendation Q.1208 Intelligent Network - Application Protocol General Aspects
Recommendation Q.1211 Intelligent Network - Introduction to Intelligent Network
Capability Set 1
Recommendation Q.1213 Intelligent Network - Global Functional Plane for CS1
Recommendation Q.1214 Intelligent Network - Distributed Functional Plane for CS1
Recommendation Q.1215 Intelligent Network - Physical Plane for CS1
Recommendation Q.1218 Intelligent Network - Intelligent Network Interface
Specifications
Recommendations Q.1219 Intelligent Network Users guide for Capability Set 1
22
IN Architecture © Konsultointi Martikainen Oy 1999
• The key question is: How Intelligence is

provided and distributed in the network
• IN Conceptual Model (INCM) gives a
framework which will be presented here
• Other models may emerge, most probably
from voice, multimedia and mobile value
added services in Intranet and Extranet
• Future broadband intelligence standards will
be chosen by the market
23
IN Architecture © Konsultointi Martikainen Oy 1999
SCE
SMP
SMF SDP SCEF
SCP SDF
SCF
SN
SDF
SS#7 network AD SDF
SSF
SCF
SRF CCF
SCF
IP SSP SSCP SRF

CCF CCAF
SRF CCF
SCF
Signaling NAP CCAF
Transfer CCAF SSF SDF
Optional FE SSF
Point (STP)
Signaling CCF
Transport
Management
24
IN architecture evolution © Konsultointi Martikainen Oy 1999
•Separation of switching and intelligence in the

pre-IN, switch-based networks
Calling subscribers
Called subscriber
Control logic (intelligence) Local switch Transit switch

25
•Centralized intelligence in the network, phase one

in IN-evolution
Calling subscribers
Called subscriber
Service Control Point, SCP Local switch Service Switching Point, SSP
26
•Flexible intelligence allocation in the Mobile services

network, phase two in IN-evolution (GSM, PCS)
Service X in local service point Mobile Services

Switching Center
X
Base Station System
Home Location Register
Service Y in centralized service point

Service Z in user terminal ie. phone
Service Control Point, SCP

Local switch Service Switching Point, SSP
Control logic (intelligence)
27
Future mobile services

• Intelligence on demand (UMTS, FPLMS, MBS)
Intelligence required for a service

Some of the service intelligence is downloaded to the nearest control point
resides in the user terminal
Media stream
Control stream
Broadband IP, Media Server
Service Control Point, SCP Local switch Broadband Service Switching Point,
BSSP (ATM-switch)
Control logic (intelligence)
28
IN Services © Konsultointi Martikainen Oy 1999
• Services are the core of IN

• Time to market the competitive advantage
• Different services for different needs
• Ideally services facilitate
• the profiling of existing services as well as
the provision of custom services
requirements
• third party service provision
• service creation by the end users
29
Service Creation ideally SIB-based

• Easy to use
• Fast to implement and test
• Flexible provision in different networks
through standard interfaces (TCAP/INAP)
• Reuse of SIB-components
• However, present SCEs are not all SIB-
based
30
• Service categories
• Mass market services
– well-defined set of ‘basic’ service features
– no customer differentiation
– e.g. 800, premium rate, VPN, mobile services
• Profiled services
– same features as in mass market services
– user data can be easily and rapidly modified by
the service subscriber or the users
– e.g. 800 service with dynamic routing, UPT,
chaining of fixed and mobile services
31
• Custom services
– tailored services for specific user needs
– service creation and management by users
– e.g. personal assistants, VPN and mobility in
Intranet, voice and media integration
Custom services
Service
Complexity / Profiled services
Value to
customers
Mass market services
1980 1990 2000

32
• Mass market services

• 800-service i.e. freephone
– the oldest and most widely used IN-service
– business to consumer or business to business
– the service subscriber is charged, not users
– based on pure number translation with or without
intelligent routing e.g.
• call distribution
• call queuing
• time and date dependencies
33
• Premium rate
– 700-service (also 600-service in Finland)
– user is charged for the network and services
– typically provision of information, direct selling,
chat lines and televoting
• Virtual Private Network, VPN
– defined as a logical closed user group,
implemented over public switched
telecommunications facilities
– provision of private numbering plan
– call charging on the basis of duration of usage
34
– usage for switched voice, switched data or both

– single interface for all domestic and international
needs e.g.Sonera’s 02040 xxxx -countrywide
numbering plan
• Mobile/cellular services
– IN with capability of dynamic location tracking of
the mobile subscriber
– the fullest mobile-IN realization with GSM
– Universal Personal Telephony (UPT)
• communication between people, not devices
• “just-in-time communications”
35
• Profiled services
• Dynamic 800 call routing
– control of the service data in call routing via
switching environment
– subscriber can have own SMS to gather
information of the service usage
• Bank account query
– DTMF coded user ID and password
• Personal Communications Service (PCS)
– users have unique PINs (Personal identification Number)
– network access terminal independence
36
• Custom services
• Pure customized IN-services not yet exist
• Possible scenario towards sophisticated
interactive voice and multimedia services
• Requires complete IN-system management,
which encompasses
– service management
– network element management
– customer management
37
IN services in Europe
Mrd ECU
14
12 Others
10 UPT
Calling Card
8
Televoting
6
VPN
4 Premium Rate
2 Feephone
0
1995 1996 1997 1998 1999 2000
38
Signaling System no.7 © Konsultointi Martikainen Oy 1999
Secure
Fault-Tolerant
Signaling System no.7 Network

STP (Signaling Transfer Point)
NNI
Speech and Data

X
X Transmission Network
SP
UNI X (Signaling Point)
(User Network NNI
Interface) ( Network Node
Interface)
39
OSI Reference model and Signaling System no. 7
INAP
Application User Parts
TCAP
TUP User /
Application Presentation ISUP
MUP
Application
Layers Session NULL Parts
Transport
SCCP
Network
MTP Level 3
Network Data link MTP Level 2
Network
Layers Part
Physical MTP Level 1
OSI-RM SS7
40
• ITU-T Recommendations Q-series

• Common channel outband signaling
system (CCSS7, CCS7, SS7, SS#7)
• signaling separated from payload (voice,
data) to its own network
• Outband signaling enables separation of
switching and control intelligence in
telecommunications network
41
• Major benefits include

• improves the speed and flexibility of call
setup
• allows processors to exchange information
rapidly for a call requiring special routing or
handling
• enables operation companies to access
customer information stored in network
databases to deliver advanced
telecommunications services networkwide
42
• provides the originating switch or customer

with detailed progress and processing
information about the call as it is established
• SS7 is an OSI-RM compliant protocol
• network part is responsible for network
related functions (connection setups,
routing, transport, error detection)
• user/application part includes the service
specific functions
43
• Components of SS7 network

• Signaling Link, SL (MTP1-MTP2)
• Signaling Transfer Point, STP (MTP1-MTP3)
• Signaling Point, SP (MTP1-SCCP, includes
one or more user/application parts)
SCP SSCP
STP
Signalling Link (SL)
SS7 SS7
STP STP SSP Signalling Point (SP)
SS7 SS7
IP
STP
44
• MESSAGE TRANSFER PART (MTP)

• Provides reliable connectionless service
for routing messages through SS7 network
• MTP1 (signaling data link)
– physical layer of OSI model
– physical and electrical characteristics
• MTP2 (signaling link)
– provides reliable sequenced delivery of data
across signaling data link
– layer 2 of OSI model
45
• MTP3 (signaling network)

– provides functions for routing data across
multiple STPs between signaling points
– message handling
• routing (determines the signaling link to be used)
• distribution (determines the user part to which
message should be delivered)
– network management
• objective is to overcome link failures or link congestion
46
• three categories:
• 1) signaling traffic management
• 2) signaling link management
• 3) signaling route management
• SCCP (Signaling Connection and Control
Part)
– equivalent to OSI network layer
– addressing capability with PC (Point Code) and
SSN (Sub System Number)
• Destination Point Code
• Originating Point Code
– message delivery management
47
• TCAP (Transaction Capabilities Application

Part)
– distributed SS7 processes’ dialogue
management (comparable to OSI ROSE)
– interfaces directly with SCCP-layer
– component sub-layer
• manages service remote procedure call parameter
coding and decoding
– transaction sub-layer
• manages TC-users’ communication (queries and
responses)
48
• INAP (Intelligent Network Application Part)

– set of different functional service elements
• OPERATION-elements
• ERROR-elements
• RESULT-elements
– OSI ROSE user-protocol (TC-user)
– INAP-services are defined with ASN.1 (Abstract
Syntax Notation One)- language
– INAP ASN.1 descriptions are compiled to coding/
decoding entities
– CS-services are defined with INAP-interfaces
49
INAP Architecture
Application process Application process
MACF
SAO SAO SAO
ASE1 ASE1 ASE1

SACF
SACF
SACF
ASE2 ASE2 ASE2
TCAP TCAP TCAP
SCCP SCCP SCCP
MTP MTP MTP
a) Single Interaction b) Multiple Coordinated Interaction
SAO = Single Association Object

SACF = Single Association Control Function
MACF = Multiple Association Control Function
ASE = Association Service Element
50
IN Conceptual Model © Konsultointi Martikainen Oy 1999
• The IN Conceptual Model (INCM) was

designed to serve as a modeling tool for
the Intelligent Network. It is defined in
the CCITT Recommendation Q.1201.
• INCM is divided into four planes:
– Service plane
– Global functional plane
– Distributed functional plane
– Physical plane
IN Conceptual Model 51
objectives © Konsultointi Martikainen Oy 1999
• INCM forms the basis for the

standardization work and it forms design
guidelines for the IN architecture to meet
the following main objectives:
– service implementation independence
– network implementation independence
– vendor and technology independence
• INCM is the first complete approach to
modular telecom service development
IN Conceptual Model 52
Planes © Konsultointi Martikainen Oy 1999
s e rv ic e 1 s e rv ic e 2
S F 1
S F n
s e rv ic e
S F 2 p la n e
g l o b a l s e r v ic e l o g i c
P O I
S IB 1 G S L 1
B C P
G S L 2 g lo b a l
S IB 2
fu n c tio n a l
P O R p la n e
S IB n
G S L n
F E 1
F E 2
F E F E F
F
E E
A d istrib u te d
E F A
E F fu n c tio n a l
p la n e
P E 2
P E n
P 1 P 2 p h y s ic a l
P E 1 F E 1 p la n e -
p ro to c o ls
F E 2 a n d
P n p ro c e s sin g
53
Service Plane © Konsultointi Martikainen Oy 1999
• The Service Plane represents an exclusively

service-oriented view. This view contains no
information whatsoever regarding the
implementation of the services in the network.
What is perceived is the network's service-
related behavior as seen, for example, by a
service user. Services are composed of one
or more Service Features (SFs), which
represent the "lowest level" of services.
54
IN CS.1 Services © Konsultointi Martikainen Oy 1999
Automatic Alternative Billing (AAB) Mass Calling (MAS)

Abbreviated Dialing (ABD) Malicious Call Identification (MCI)
Account Card Calling (ACC) Premium Rate (PRM)
Credit Card Calling (CCC) Security Screening (SEC)
Call Distribution (CD) Selective Call Forward on Busy/Don’t
Call Forwarding (CF) Answer (SCF)
– Comp. of Call to Busy Split Charging (SPL)
Subscriber Televoting (VOT)
– Conference Calling (CON) Terminating Call Screening (TCS)
Call Rerouting Distribution (CRD) User-Defined Routing (UDR)
Destination Call Routing (DCR) Universal Access Number (UAN)
Follow-Me-Diversion (FMD) Universal Personal Telecommunications
(UPT)
Freephone (FPH) Virtual Private Network (VPN)
55
IN CS.1 Service Features © Konsultointi Martikainen Oy 1999
Abbreviated Dialing (ABD) Customized Recorded Announcement (CRA)

Attendant (ATT) Customized ringing (CRG)
Authentication (AUTC) Destinating User Prompter (DUP)
Authorization Code (AUTZ) Follow-Me Diversion (FMD)
Automatic Call Back (ACB) Mass Calling (MAS)
Call Distribution (CD) Meet-Me Conference (MMC)
Call Forwarding (CF) Multiway Calling (MWC)
Call Forwarding on Busy (CFC) Off-Net Access (OFA)
Call Gapping (GAP) Off-Net Calling (ONC)
Call Hold with Announcement (CHA) One Number (ONE)
Call Limiter (LIM) Origin Dependent Routing (ODR)
Call Logging (LOG) Originating Call screening (OCS)
Call Queuing (QUE) Originating User Prompter (OUP)
Call Transfer (TRA) Personal Numbering (PN)
Call Waiting (CW) Private Numbering Plan (PNP)
Closed User Group (CUG) Reverse Charging (REVC)
Consultation Calling (COC) Split Charging (SPLC)
Customer Profile Management (CPM)
56
Example: Freephone © Konsultointi Martikainen Oy 1999
• FPH allows reverse charging, the subscriber accepting

to receive calls at its expenses and being charged for
the whole cost of the call
• FPH allows the served user having one or several

installations to be reached from all part of the country,
or internationally as appropriate, with a freephone
number and to be charged for this kind of call
57
Example: Freephone Service © Konsultointi Martikainen Oy 1999
1. Dialling service number 0800 123 456

SWITCH
SSP IP/SN SCP SDP 2. IN-Call Detection from B-number
PBX
2 3. Service Logic function. Database
1
A1
Routing Detect
3 query (from SDP)
PBX
A1
Routing Service Logic 4 4. SDP returns programmed charging
A1
Data Function
information and C-number.
5
5. SCP sends INAP message to switch
6 Service Logic
(including charging information)
Charging 7
6. Switch saves special charging
8 Service Logic
9
information
Connect
C1 7. SCP sends INAP message to switch
(including new number)
8. Switch connects call to new number
9. Alarming
58
Example: Premium Rate © Konsultointi Martikainen Oy 1999
• PRM service allows to pay back a part of the call cost to the
called party, considered as an added value service provider.
• PRM allows the served user having one or several

installations to be reached from all or part of the country, or
internationally as appropriate, with a premium rate number.
The calling party will be charged with a premium rate for this
kind of call.
• It is a service that can be available in the public telephone

network whereby, a service provider having connections to
the public network can be allocated a special telephone
number by a network operator, known as a Premium Rate
number.
59
Example: PRM (cont.) © Konsultointi Martikainen Oy 1999
• The provider is able to earn revenue for each call

successfully made to his premium rate number. In return he
provides callers with some form of information service via
the call connection. Calls to the premium rate number are
charged to the caller at special rates to cover the price of
the call and the price of the information service. The
network operator administration collects the revenue for
each call and shares it with the provider.
• The geographical location of the provider is unrelated to his

premium rate number i.e., he can be located anywhere in
the network. The provider may specify the catchment area
from which he wishes to receive calls. In the case of multi-
site providers, the site to which the caller is connected can
depend on the catchment area in which the call originated.
60
Example: Premium Rate Service © Konsultointi Martikainen Oy 1999
1. Dialling service number 0700 123 456

SWITCH
SSP IP/SN SCP SDP 2. IN-Call Detection from B-number
PBX
2 3. Service Logic function. Database
1
A1
Routing Detect
3 query (from SDP)
PBX
A1
Routing Service Logic 4 4. SDP returns programmed charging
A1
Data Function
information and C-number.
5
6 Service Logic
(for playing announcment)
Connect IP
7 6. Switch connects IP-device to sub-
Announcment 8 scriber line.
9 Service Logic 7. IP device plays announcment
Charging 10 8. SCP sends INAP message to switch
11 Service Logic
(including charging information)
Connect 9. Switch saves special charging
C1
information
(including new number)
11. Switch connects call to new number
Example: Virtual Private 61
Network © Konsultointi Martikainen Oy 1999
• VPN permits to build a private network by using the

public network resources. The subscriber’s lines,
connected on different network switches, constitute a
virtual PABX, including a number of PABX capabilities,
such as Private Numbering Plan, call transfer, call
hold, and so on.As an option, to each private user,
either a class of service or specific rights and
privileges may be attributed. As another option, a
private user may access his private network from any
point in the network keeping, after authentication, his
class of service or his specific rights and privileges.
62
Example: VPN (cont.) © Konsultointi Martikainen Oy 1999
• VPN the use of public network resources to provide

private network capabilities without necessarily using
dedicated network resources. The subscriber’s lines,
connected to different network switches, constitutes a
virtual private network that may include private
network capabilities, such as dialing restrictions,
Private Numbering Plan (PNP), hold, call transfer, and
so on.A PNP may provide a group of users the
capability to place call by using digit sequences having
different structures and meaning than provided by the
public numbering plan, or PNP may utilize the public
numbering plan’s digit sequences, structures and
meaning.
63
Example: VPN (cont.) © Konsultointi Martikainen Oy 1999
• VPN allows a subscriber to define and use a PNNP for

communication across one or more networks between
nominated user access interfaces. A PNP provides a
group of users the capability to place calls by using
digit sequences having different structures and
meanings than provided by the public numbering plan.
64
Example: VPN Service
(with PNP service features) © Konsultointi Martikainen Oy 1999
SWITCH
SSP IP/SN SCP SDP
2
1. Dialling short number (fromVPN to VPN) or
1 PBX
A1
Routing Detect
company number with subnumber (to VPN)
3
PBX
6 2. IN-Call Detection from B-number
A1
Routing Service Logic 4
7 3. SCP sends message to SDP (db query)
A1
5 Data Function 4. SDP returns “Calling Plan etc.”
6 Service Logic 5. SCP sends INAP message to switch
Charging 7 (including charging information)
8 Service Logic 6. Switch saves charging information
9 7. SCP sends message to switch
Connect
C1
(Connet line to VPN number)
8. Switch connects line
Example: Credit Card 65
Calling © Konsultointi Martikainen Oy 1999
• The CCC service allows subscribers to place calls

from any normal access interface to any destination
number and have the cost of those calls charged to
the account specified by the CCC number.
• The service allows the caller to be automatically

charged on a bank card account, for any type of
outgoing call. The caller has to dial his card number
and a PIN (Personal Identification Number), then the
called number. As an option forward calls may be
allowed, without dialing again card number and PIN
Example: Universal 66
Personal Telephony © Konsultointi Martikainen Oy 1999
• UPT is a mobility service which enables subscribers to

make use of telecommunications services on the basis
of a unique Personal Telecommunications Number
(PTN) across multiple networks at any network
access. The PTN will be translated to an appropriate
destination number for routing based on the
capabilities subscribed to by each Service Subscriber
(SS).
• UPT provides personal mobility by enabling a user to
initiate any type of service and receive any type of call
on the basis of a unique and personal
67
Example: UPT (cont.) © Konsultointi Martikainen Oy 1999
• network-independent number, across multiple

networks, at any user-network access (fixed, movable
or mobile), irrespective of geographic location, limited
only by terminal and network capabilities.
Example: Service 68
mappings © Konsultointi Martikainen Oy 1999
Service Feature FPH CCC VPN UPT

ABD o o C = Core
ATT o O = Optional
AUTZ C o C (not all O’s here)
AUT o
CD o
LOG o o o o
QUE o o
TRA o
CUG o
COC o
CPM o o o
CRA o o o
CRG o o
DUP o o
FMD o C
ONE C
OUP o C o o
PN C
PNP C
REVC C
SPLC C
TDR o o o
69
Global Functional Plane © Konsultointi Martikainen Oy 1999
• The Global Functional Plane (GFP) models

the IN-structured network as a single entity.
Contained in this view is a global (network-
wide) Basic Call Processing (BCP) SIB, the
Service Independent Building blocks (SIBs),
and Point of Initiation (POI) and Point of
Return (POR) between the BCP and a chain of
SIBs. The Global Service Logic (GSL)
describes how service features are built using
SIBs.
70
Global Functional Plane © Konsultointi Martikainen Oy 1999
Global Functional Plane Model:
GSL
POI SIB1
BCP
POR SIB2
SIB3
Service Independent 71
Building Blocks © Konsultointi Martikainen Oy 1999
• SIBs are independent from any physical

architecture considerations
• Each SIB has an interface with one or
more inputs and one or more outputs
• SIBs are reusable modular building
blocks, describing a single complete
activity, and used by the service designer
to create services
72
SIB chains in a Service © Konsultointi Martikainen Oy 1999
SIB1 SIB2 SIB3 SIB6
SIB4 SIB5
POI Basic Call Process POR POR

Service Independent 73
Building Blocks © Konsultointi Martikainen Oy 1999
Algorithm Screen
Charge Service Data Management
Compare Status Notification
Distribution Translate
Limit User Interaction
Log Call Verify
Information
Queue
74
SIB graphical representation © Konsultointi Martikainen Oy 1999
SSD SSD
parameters
Logic Logic
start SIB end
CID input CID CID output

parameters parameters
75
SIB inputs and outputs © Konsultointi Martikainen Oy 1999
• Logical start (input)

• Service Support Data, SSD (input)
– Fixed Parameters (depend on the SIB type)
– CID Field Pointers (CIDFP)
• Call Instance Data, CID (input)
• Call Instance Data, CID (output)
– Dynamic parameters (depend on call instance)
Logical end (output)
76
Example: The Queue SIB © Konsultointi Martikainen Oy 1999

Example: Automatic 77
Alternative Billing © Konsultointi Martikainen Oy 1999
• The AAB service enables a user to make a call from any

telephone and for the call charge to be billed to the user's account
which is specific to this service, and which does not refer either to
the calling line or to the called line. An account code and PIN are
allocated to the service user by service management procedure.
• To invoke the service, the user dials an access code as a free
call. Different access codes could be used to identify the
language to be used. The user then receives announcements
asking for him to dial his account code and PIN. The account
code and PIN are validated, and a check could be made for
expired credit limits.
• NOTE: Account/credit card calling is similar, with the account No.
being supplied using a card wipe.
78
Example: AAB (Cont.) © Konsultointi Martikainen Oy 1999
• The AAB service allows a user to call another user and ask him to
receive the call at his expenses. Two steps may be defined: the
calling party is welcomed to record a brief message giving the
caller's name and explaining the call reason, then the called party
is alerted, receives the recorded message and is asked to accept
to be charged for that call.
IN Automatic Alternative 79
Billing © Konsultointi Martikainen Oy 1999
MATCH
Translate Charge
2 3 4 7 8
User
Verify Screen NO MATCH
Interaction
5
User
Interaction
1 6 9
POI
POI Basic Call Process POR POR
Address Clear Call Proceed
Analysed with New Data
80
Example: AAB © Konsultointi Martikainen Oy 1999
1 Basic Call Process

input POI Call Arrival
CID 1) dialed number 2) calling line id
2 User Interaction SIB

input SSD 1) announcement parameters 2) collected info
CID calling line id
output CID collected info.
End Ok
3 Verify SIB
input SSD 1) min. and max. of numbers 2) format
CID collected info
output End Ok
81
4 Screen SIB
input SSD screenlist indicator
CID collected info
output End 1) Match or 2) No Match
IF "No Match":
5 User Interaction SIB

input SSD announcement parameters
CID calling line id
output End Ok

input POR Clear Call
output CID calling line id
82
IF "Match":
7 Translate SIB
input SSD 1) Type 2) Filename
CID dialed number
output CID called number
End Ok
8 Charge SIB
input SSD Account CodeList.
CID Account Code
output End Ok

output POR Proceed with New Data
CID called number
Distributed Functional 83
Plane © Konsultointi Martikainen Oy 1999
• The Distributed Functional Plane (DFP)

models a distributed view of an IN-structured
network by defining Functional Entities (FEs).
Each Functional Entity may perform a variety
of Functional Entity Actions (FEAs). SIBs can
be then described by a collection of FEAs in
different functional entities and information
flows between FEAs. A given FEA may not be
distributed across functional entities.
84
Functional Entities (FEs) © Konsultointi Martikainen Oy 1999
SMAF
SMF
SCEF
SDF
SCF
SRF
SSF SSF
CCAF CCF CCF CCF CCAF
Service management
Service control
Call and Resource control
Bearer control (below)
85
Functional Entities © Konsultointi Martikainen Oy 1999
• CCAF (Call Control Agent Function)

• CCF (Call Control Function)
• SSF (Service Switching Function)
• SCF (Service Control Function)
• SDF (Service Data Function)
• SRF (Service Resource Function)
• SMF (Service Management Function)
• SMAF (Service Management Access Function)
• SCEF (Service Creation Environment Function)
86
Functional entities © Konsultointi Martikainen Oy 1999
• Call Control Agent Function

• the interface between user and network call
control functions. It has the following
characteristics:
– provides for user access, interacting with the
user to establish, maintain, modify and release,
as required, a call or instance of service;
– accesses the service-providing capabilities of
the Call Control Function, using service;
87
– requests (e.g. setup, transfer, hold, etc.) for the

establishment, manipulation and release of a call
or instance of service;
– receives indications relating to the call or service
from the CCF and relays them to the user as
required;
– maintains call/service state information as
perceived by this functional entity;
88
• Call Control Function

• The CCF is the Call Control Function in the
network that provides call/connection
processing and control.
– establishes, manipulates and releases call/
connection instances as “requested” by the
CCAF;
– provides the capability to associate and relate
CCAF functional entities that are involved in a
particular call and/or connection instance (that
may be on SSF requests);
89
– manages the relationship between CCAF

functional entities involved in a call (e.g.
supervises the overall perspective of the call
and/or connection instance);
– provides trigger mechanism to access IN
functionality (e.g. passes events to the SSF);
– managed, updated and/or otherwise
administered for its IN-related functions (i.e.
trigger mechanisms) by the Service
Management Function SMF;
90
• Service Switching Function

• the Service Switching Function, which,
associated with the CCF, provides the set of
functions required for interaction between
the CCF and Service Control Function
– extends the logic of the CCF to include
recognition of service control triggers and to
interact with the SCF;
91
– manages signaling between the CCF and the

SCF;
– modifies call/connection processing functions (in
the CCF) as required to process requests for IN
provided service usage under the control of the
SCF;
– is managed, updated and/or otherwise
administered by an SMF;
Service Switching 92
Function Model © Konsultointi Martikainen Oy 1999
SCF SLPI A
SSF SCF access manager
IN local resource data IN Switching Manager

manager
IN switching state
model instance
IN local resource data
Non-IN feature manager Feature interaction

manager/call manager
CCF
Basic call resource data

SRF Basic call manager
manager
CCAF Basic call resource data Bearer control CCAF

Originating Basic Call 93
State Model © Konsultointi Martikainen Oy 1999
O _Abandon
1 . O _ N u ll & A u th o r iz e 6 . E x c e p tio n
10 O r ig in a t io n a t t e m p t
O r ig . A tt e m p t_ A u th o r iz e d
1
2 . C o lle c t In f o
2 C o lle c t e d _ In f o
3 . A n a ly z e In fo
3 A n a ly z e d _ In f o
4
4 . R o u t in g & A le r t in g
R o u t e _ S e le c t _ F a ilu re
5
O _ D is c o n n e c t 7
O _ C a lle d _ P a r t y _ B u s y
9 5 . O _ A c t iv e
6
O _No_Answ er
8
O _ M id _ C a ll
K ey: T r a n s itio n
D e t e c t io n P o in t ( D P )
P o in t in C a ll (P IC )
94
Service Control Function

• The SCF commands call control functions in
the processing of IN provided and/or custom
service requests. The SCF may interact with
other functional entities to access additional
service logic or obtain information (service
or user data) required to process a call or
service logic instance
– interfaces and interacts with SSF/CCF, SRF and
SDF functional entities;
95
– contains the logic and processing capability

required to handle IN provided service attempts;
– interfaces and interacts with other SCFs, if
necessary;
Service Control Function 96
Model © Konsultointi Martikainen Oy 1999
SLP library
SLP Manager Service logic execution environment (SLEE)
Service logic Functional routine

execution manager Functional library, includes
routine functional routines
Service manager
logic SLP program
selection / instances
SCF data Service data object
interaction
access directory
manager
manager
IN network-wide
Resource
resource data
manager
Functional entity access manager
SMF SSF SRF SDF

97
• Service Data Function

• The SDF contains customer and network
data for real time access by the SCF in the
execution of IN provided services.
– interfaces and interacts with SCF as required;
– interfaces and interacts with other SDFs, if
necessary;
Service Data Function 98
Model © Konsultointi Martikainen Oy 1999
Exclusive control Dynamic data

manager
SDF
data Static data with large volume
manager
Service data object directory
SMF SDF SCF

99
• Service Resource Function

• The SRF provides the specialized resources
required for the execution of IN provided
services (e.g. digit receivers,
announcements, conference bridges, etc.)
– interfaces and interacts with SCF and SSF (and
with the CCF);
100
– may contain the logic and processing capability

to receive/send and convert information received
from users;
– may contain functionality similar to the CCF to
manage bearer connections to the specialized
resources;
Service Resource 101
Function Model © Konsultointi Martikainen Oy 1999
SRF
resource Resources
manager
SSF/CCF SMF SCF User

102
• Service Management Function

• This function allows deployment, provision
and support of IN provided services.
Particularly, for a given service, it allows the
coordination of different SCF and SDF
instances
– billing and statistic information are received from
the Scoffs;
– modifications in service data are distributed in
SDKs;
103
• Service Management Access Function

– This function provides an interface between
service managers and the SMF.
• Service Creation Environment Function
– This function allows services to be defined,
developed and tested. Output of this
function would include service logic, service
management logic, service data template
and service trigger information.
104
Relating GFP to DFP © Konsultointi Martikainen Oy 1999
SIB SSF/SCF SCF SRF SDF

Algorithm *
Charge * *
Compare *
Distribution *
Limit * *
Log Call Information * * *
Queue * * *
Screen * *
Service Data Management * *
Status notification * * *
Translate * *
User Interaction * * *
Verify *
Basic Call Process * *
105
Example: The Queue SIB © Konsultointi Martikainen Oy 1999
Max Active
Max Number
Max Time
SSD Announcement Parameter
CIDFP - Resource
CIDFP - Error
Resource Available
Call Party Abandon
Queue Q Timer Expiry
Q Full
Error
Call Reference
CID Time spent on Queue
Resource Error Cause
SIB as a combination of 106
Fees © Konsultointi Martikainen Oy 1999
• Sibs are described using FEAs and

information flows between them
• FEAs are numbered with XYYZ where
• X presents the FE
– CCF/SSF = 2, SRF = 3, SDF = 4, SCF = 9
• YY presents the SIB
– BCP = 0, Algorithm = 1, ... , Verify = 13
• Z distinguishes the FEAs with common XYY
Example: Queue with 107
announcement © Konsultointi Martikainen Oy 1999
Information flows between FEAs are INAP operations:

Request Report BCSM req.ind (REQREPBCSM)
Connect to Resource req.ind (CONNTORES)
Play Announcement req.ind (PLAYANN)
Disconnect Forward Connection req.ind (DISCFWDCONN)
SRF SCF CCF/SSF
Serv. Logic
9071
REQREPBCSM
2076
CONNTORES
2073
PLAYANN
3071
resource free
9073
DISCFWDCON
N
2077
108
INAP operation description © Konsultointi Martikainen Oy 1999
INAP User ASEs
xyz OPERATION
ARGUM ENT {Parameter1, Parameter2,...}
RESULT {Parameter1, Parameter2,...}
LINKED {operation3, operation4,...}
ERRORS {error1, error2,...}
Operations
Results
error1 ERROR To Peer Errors
PARAM ETER {Parameter6, Parameter7,...}
etc
TCAP ASE
To Peer
INVOKE
RETURN RESULT
COM PONENT SUBLAYER RETURN ERROR
REJECT
ROSE PDUs
BEGIN
TRANSACTION SUBLAYER CONTINUE
END
To Peer
ABORT
UNIDIRECTIONAL
Connectionless SCCP
109
Example INAP operation © Konsultointi Martikainen Oy 1999
ConnectToResource ::= OPERATION

ARGUMENT
ConnectToResourceArg
ERRORS {
MissingParameter
SystemFailure
TaskRefused
UnexpectedComponentSequence
UnexpectedDataValue
UnexpectedParameter
}
• Connects a call from SSP to IP with SRF
ASN.1 example: 110
ConnectToResourceArg © Konsultointi Martikainen Oy 1999
ConnectToResourceArg ::= SEQUENCE {

CHOICE {
ipRoutingAddress [0] IPRoutingAddres
legId [1] LegId
both [2] SEQUENCE {
ipRoutingAddress [0] IPRoutingAddres
legId [1] LegId
},
none [3] NULL
},
extensions [4] SEQUENCE SIZE (0..MAX) OF
ExtensionField OPTIONAL
},
111
ETSI Core INAP © Konsultointi Martikainen Oy 1999
• ETS 300 374-1 (Sept 1994) defines the

INAP for support of CS-1
• Supports interactions between SSF, SCF
and SRF
• Interactions with SDF missing in Part 1
• Contains simplifications to in ITU-T
Q.1214 (several operations replaced by InitialDP
and EventReportBCSM)
112
Physical Plane © Konsultointi Martikainen Oy 1999
• The Physical Plane models the physical

aspects of IN-structured networks. The model
identifies the different Physical Entities (PEs)
and protocols that may exist in real IN-
structured networks. It also indicates which
functional entities are implemented in which
physical entities.
113
Physical Plane © Konsultointi Martikainen Oy 1999
SCE
SMP
SMF SDP SCEF
SCP SDF
SCF
SN
SDF
SS#7 network AD SDF
SSF
SCF
SRF CCF
SCF
IP SSP SSCP SRF

CCF CCAF
SRF CCF
SCF
Signaling NAP CCAF
Transfer CCAF SSF SDF
Optional FE SSF
Point (STP)
Signaling CCF
Transport
Management
114
Physical Entities (PEs) © Konsultointi Martikainen Oy 1999
• Network Access point (NAP)

• Service Switching Point (SSP)
• Service Control Point (SCP)
• Service Data Point (SDP)
• Adjunct (AD)
• Intelligent Peripheral (IP)
• Service Node (SN)
• Service Management System (SMS)
• Service Creation Environment (SCE)
115
Physical Entities © Konsultointi Martikainen Oy 1999
• Network Access Point, NAP

• is a Physical Entity that includes only the
CCAF and CCF functional entities and it has
the ability to determine when IN processing
is required. It must send calls requiring IN
processing to an SSP.
116
• Service Switching Point, SSP

• PSTN exchange modified to recognize IN-
services
• Can have dialogues with different SCPs
– trigger point defines required service in calls
– interconnections via Signaling Transfer Points
• Dialogues with SCPs based on SS7
signaling - no actual payload is transmitted
• SSP+”SCF”+”SDF” = SSCP, Service
Switching and Control Point
117
• Service Control Point, SCP

• Service logic is controlled by Service Logic
Processing Program (SLP)
• Services are run in Service Logic Execution
Environment e.g. OS, runtime modules,
management procedures etc.
• Service data can be located in Service Data
Point ie. (relational) database
– usually integrated to SCP
– can be a commercial product (Oracle,Sybase)
118
• Service interfaces to SSP abstracted with

TCAP and INAP (OSI application layer)
• Fault tolerance with doubled and/or mated
pair systems
• Adjunct, AD
• Functionally equivalent to SCP, but has
– direct communications link to SSP
– supports one-to-one relationship with SSP
– usually small geographical coverage
119
• Intelligent Peripheral, IP or Service

Resource Point, SRP (from CS.2 onwards to separate
from Internet Protocol, IP)
• Connected to SSP over a high speed bus
• Manages resources such as
– announcements
– speech recognition
– digit collection
– protocol conversions
• Controlled by SSP or SCP (or SN)
– interface to SSP incl. both signaling and data,
120
but to SCP (or SN) only signaling

• Service Node, SN
• Complete set of resources and services for
advanced IN services
– can have the functionality of both SCP and IP
– point-to-point connection to SSPs (via STPs)
• Service Management System, SMS
• Supports both commercial and technical IN
service management
– service users can e.g. change PIN (Personal
Identification Number) in UPT-service
121
– service subscriber to an 800-service can

configure call routing
– operator can load new services to the SCP
– operator can gather statistics and billing data to
the OSS (Operations Support System)
• Handles service management in the
distributed IN systems
– data consistency in SCPs’ databases (SDPs)
• Usually closely coupled with the SCP
– no standard SMS-SCP interface protocols exist
122
• Service Creation Environment, SCE

• Framework for defining, developing and
testing SLPs e.g.
– graphical SIB-based ‘drag and drop’
– graphical SDL-based
– high level, 4GL language based
– low level C-language based with special
resources e.g. libraries and runtimes
– proprietary graphic and/or text based
• Services are loaded via SMS to SCPs
Relating DFP to Physical 123
Plane © Konsultointi Martikainen Oy 1999
PE:s SCF SSF/CCF SDF SRF

SCP C * C *
SN C C C C
AD C * C *
SSP O C O O
IP / SRP * * * C
SDP * * C *
SSCP C C C O
NAP * C (CCF only) * *
C: Core
O: Optional
*: Not allowed
124
IN Service Creation © Konsultointi Martikainen Oy 1999
Service creation process for IN services

Service Description
Service Analysis Service Modeling
Service Testing Service Development
Service Maintenance
Service Deployment
Service Management
125
IN Service Deployment © Konsultointi Martikainen Oy 1999
Service Creation Operations Support

fault
management
System
(IF+ )
billing
charging
Product development
Requirements
delivery ( IF )
customer
SPECS service
R&D IF : Production
IF + :
Pilots SLP:
SDF:
Physical plane
SLP SDF
New services
Building
X1
X 2
X N
126
IN Service Management © Konsultointi Martikainen Oy 1999
Service Management
Customer
service BILLING
DELIVERY Product Billing
VIEW
CDB configur- DB
Delivery ation
Prices
system Filter
Sort
CHARGING
BUILDING PRODUCTION
Filter Event
Sort Base
SDP
SCP
FAULT MANAGEMENT
SUPPORT Filter Fault

Sort Base
Example of IN Service 127
Creation © Konsultointi Martikainen Oy 1999
• Core INAP compliant service creation

process
• service analysis and modeling
– evaluation of interfaces between SLP and SSP/IP
– service logic design
– database structure and service data definitions
– definition of managed service data
– design of management user interfaces
– CASE tools recommended
• service data functions

– write definitions and service specific db-
actions for managed service data
– service database creation
• service logic programming
– service logic described with SDL
– low level functions with C-language (e.g.
string operations, operating system services
...)
• service testing
– SSP simulator, traffic generator and phones
• A very simple 700-service

• simple number translation service
depending on the time of day e.g.
– 9.00am - 7.00pm 700-hothothot calls are routed
to number +358 53 6243270
– 7.00pm - 9.00am 700-hothothot calls are routed
to number +358 53 6243271
• if the service is not in use, an
announcement is played
• billing is implemented in SSP
• 700-service data modeling

700-Numbers Use prohibited Restrictions
700-408408408 No
700-3584754837 Yes
From relational model . . .

700-Number Beginning Time C-number Tariff / min
700-408408408 09.00am +358 53 624 3270 1,5
700-408408408 07.00pm +358 53 624 3271 3,5
700-numbers 700-number
to object model . . . Beginning time
Use prohibited
C-number
Restrictions Tariff / min
• Service logic design with SDL and coding with C

(* CVOPS state-automaton for 700-service *)
idle
(* state
input
actions *)
idle
InitialDP InitialDP {
(* Call c-function that checks
calledPartyNumber *)
result=numberTranslationService()
700-s e rvic e ? if(result==700SERVICE){
(* send query to database
and wait for reply *)
db_nt_request
start(wfDbTimer)
Ye s No t in us e No t OK to(wf_nt_resp)
}
Co nne c tTo else
db_nt_re que s t Re le as e Call
Re s o urc e if(result==SERVICE_NOT_IN_USE){
(* Play annoucement to user *)
ConnectToResource
Start messageId=123
me s s ag e Id=123 idle PlayAnnouncement
(wfDbTime r)
ReleaseCall
to(idle)
Play }
else{
wf_nt_re s p Anno unc e me nt (* error *)
ReleaseCall
to(idle)
}
}
Re le as e Call
wf_nt_resp
db_nt_resp {
stop(wfDbTimer)
idle if(dbStatus==OK){
...
132
IN Markets © Konsultointi Martikainen Oy 1999
• Market projections (OVUM Ltd, 1993)

• IN services will compromise in excess 30 % of
Telco revenues by the year 2000
• Revenues from mobile services 25 - 33 % of
total IN service revenues
• In fixed network 800, premium rate and VPN
excess 75-80 % of IN service revenues
• The total market for IN equipment will reach
US$7,9 billion in USA and US$4.8 billion in
Europe by the year 2000
133
• The vast majority of capital will be spent on

SSF/CCF functionality and SCP-related
products
– competition rises prices fall dramatically
– expect strategic partnerships and alliances
• Personal mobility (PCS) killer application ?
• Liberation of Telco industry in Europe 1998
will fierce the competition
• In the 21th century revenues from service
content, not access or transport network
134
IN technology in Europe
Mrd 5
ECU
4
Platforms
3 Applications
2 Projects
OSS
1
0
1995 1996 1997 1998 1999 2000
Future of Telecommunications: 135
Beyond IN . © Konsultointi Martikainen Oy 1999
TMN (Telecommunications Management

Network)
• Total service, network element and customer
management through open standard
interfaces
• Supports distributed network management
• IN+TMN+ODP = TINA (Telecommunications
Information Network Architecture)
– supports customer oriented distributed services in
open distributed network
CAMEL (Customized Applications for Mobile network

Enhanced Logic)
• GSM was originated before Intelligent Network (IN) and
hence Intelligent Network features have been added to
GSM later
• CAMEL is not a service but new architecture that
enables creation of IN based services in GSM
• CAMEL architecture supports GSM phase 2+ and adds
some Intelligent Network features to GSM network
• Supports Operator Specific Services globally and
enables service roaming
• CAMEL is a Working Group relating to GSM, under

the control of two Sub Technical Committees SMG3
WPC and SMG1 WPA in ETSI
• CAMEL is standardized in two phases
– Phase 1 supports fast service creation and induces
limited call control features (subset of CS.1)
– Phase 2 supports extended features (including full CS.1)
• In the first phase CAMEL feature supports
– Mobile originated and forwarded calls
– Mobile terminating calls
– Any time interrogation
– Suppression of announcements
CAMEL Abbreviations
BCSM Basic Call State Model

DP Detection Point
EDP Event Detection Point
GMSC Gateway MSC
gsmSCF GSM Service Control Function
gsmSSF GSM Service Switching Function
HPLMN Home PLMN
IPLMN Interrogating PLMN
O-CSI Originating CAMEL Subscription Information
OSS Operator Specific Service
SLPI Service Logic Program Instance
TDP Trigger Detection Point
VPLMN Visited PLMN
CAMEL Architecture
HPLMN
MAP
HLR gsmSCF
MAP CAP MAP CAP
IPLMN VPLMN
GSSF VLR
VSSF
GMSC VMSC
• CAMEL Application Part (CAP) is a subset of ETSI

Core INAP (CS.1) specified by ETS 300 374-1 on top
of SS#7 TCAP
• CAP includes basic Mobile Application Part (MAP)
operations
• CAP is used for call control between (V/G)SSF and
gsmSCF
• CAP is specified by
– Single/Multiple Association Control Function Rules
(SACF/MACF) for the protocol
– Operations transferred between entities (given in
ASN.1)
– Actions taken at each entity (given in SDL)
• Broadband and mobile IN

• ATM-switched networks
– ATM-switch can be considered as Broadband
SSP, BSSP
– SCP or SN manages virtual channels and paths
– framework for sophisticated interactive services
• UMTS (Universal Mobile
Telecommunications System)
– third generation mobile system (post
DECT/GSM)
– integrates data services for mobile usage
– hierarchical cell structure

• in-building ‘pico cells’, tens of meters
• neighborhood ‘micro cells’, hundreds of meters
• suburban ‘macro cells’, kilometers
• global ‘satellite’, unlimited reach
– up to 2 Mbit/s throughput at 2 GHz band (pico)
– routes IP-packets or ATM-cells to mobile users’
terminals
– real implementations in 2001
• MBS (Mobile Broadband System)

– evolutionary follow-up to UMTS (not a
replacement)
– real broadband access for the mobile users
– 34 Mbit/s at 60 GHz band
– mobile interactive multimedia services
Intelligent Network - 144
Summary © Konsultointi Martikainen Oy 1999
• Intelligent Network, IN offers

• Open standards, vendor independence
• Total network and customer management
• Customized services to users
• New opportunities to make business ie. new
markets and customers
• Rapid adaptation to market needs and
competition
 Competitive edge

In Imp

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

In Imp

Uploaded by

Copyright:

Available Formats

1

© Konsultointi Martikainen Oy 1999

Preface © Konsultointi Martikainen Oy 1999

• Intelligent Network (IN) is one concept to specify

• Intelligent Networks are used by teleoperators for

• Originally, IN has been applied in telephone and voice

Contents © Konsultointi Martikainen Oy 1999

• Introduction and rationale 5

Contents © Konsultointi Martikainen Oy 1999

• Service Creation and Management 124

Intelligent Network (IN) © Konsultointi Martikainen Oy 1999

• Intelligent Network offers added value

Value of Telecom Services © Konsultointi Martikainen Oy 1999

VANS AND MOBILE SERVICES

1990 1995 2000 2005

Telecom Discontinuities © Konsultointi Martikainen Oy 1999

First Wave (1994-2000)

Computer Controlled Services © Konsultointi Martikainen Oy 1999

TMN = Telecommunication Management Network

Dynamic numbering / networks

Local Mobile Business

Basic Services © Konsultointi Martikainen Oy 1999

Basic and Hooks Hooks Hooks

NODE A NODE B NODE C

terminology © Konsultointi Martikainen Oy 1999

Functional Entity Definition Related products

Networks © Konsultointi Martikainen Oy 1999

1960 1970 1980 1985 1990 1995

Networks © Konsultointi Martikainen Oy 1999

• SPC (Stored Program Control) exchanges in

Networks © Konsultointi Martikainen Oy 1999

• Databases located at network control points

Networks © Konsultointi Martikainen Oy 1999

• ‘Feature Node’ concept 1985 (Ameritech)

Networks © Konsultointi Martikainen Oy 1999

– SS#7 as common channel

Networks © Konsultointi Martikainen Oy 1999

• Both IN/2 and IN/1+ were rejected

Networks © Konsultointi Martikainen Oy 1999

• Stepwise development via number of

Networks © Konsultointi Martikainen Oy 1999

• Service independent building blocks, SIBs

Standards © Konsultointi Martikainen Oy 1999

Structure of IN Standards © Konsultointi Martikainen Oy 1999

Q.12XY with X and Y as follows:

Standards © Konsultointi Martikainen Oy 1999

Recommendation Q.1200 Q-Series Intelligent Network Recommendations Structure

IN Architecture © Konsultointi Martikainen Oy 1999

• The key question is: How Intelligence is

IN Architecture © Konsultointi Martikainen Oy 1999

IP SSP SSCP SRF

IN architecture evolution © Konsultointi Martikainen Oy 1999

•Separation of switching and intelligence in the

Control logic (intelligence) Local switch Transit switch

IN architecture evolution © Konsultointi Martikainen Oy 1999

•Centralized intelligence in the network, phase one

IN architecture evolution © Konsultointi Martikainen Oy 1999

•Flexible intelligence allocation in the Mobile services

Service X in local service point Mobile Services

Home Location Register

Service Y in centralized service point

Service Control Point, SCP

IN architecture evolution © Konsultointi Martikainen Oy 1999