Upload
rajababhu
View
29
Download
12
Tags:
Embed Size (px)
Citation preview
1
© Konsultointi Martikainen Oy 1999
Intelligent Networks
2
© Konsultointi Martikainen Oy 1999
Preface
• 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
© Konsultointi Martikainen Oy 1999
Contents
• 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
© Konsultointi Martikainen Oy 1999
Contents
• Service Creation and Management124
• IN Markets 132• Future of Telecommunications :
– TMN135
– CAMEL136
– Broadband and Mobile IN 141– MBS
143
5
© Konsultointi Martikainen Oy 1999
Intelligent Network (IN)
• 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
© Konsultointi Martikainen Oy 1999
Value of Telecom Services
1990 20051995 2000
VALUE
Digital
Mobile
Broadband
CONNECTIVITY SERVICES
VANS AND MOBILE SERVICES
DIGITAL MEDIA
7
© Konsultointi Martikainen Oy 1999
Telecom Discontinuities
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
© Konsultointi Martikainen Oy 1999
Computer Controlled Services
TMN = Telecommunication Management NetworkIN = Intelligent Network
TM N
INLogical subscribers Logical services
Narrowband Broadband
Dynamic numbering / networks
Local Mobile Business
Differentiation
*** open techno logy ***
* ** custom er segm ents * * *
9
© Konsultointi Martikainen Oy 1999
Separation of IN and Basic Services
NODE A NODE B NODE C
IN Service LogicIN Service Logic
Basic andsupplementaryservicesoffered to customers
Basic call processing
Basic call processing
Basic call processing
Basic call processing
Basic call processing
Basic call processing
Hooks Hooks Hooks
10
© Konsultointi Martikainen Oy 1999
Intelligent Network terminology
Functional Entity Definition Related productsCall Control Access Function (CCAF)
Provides the means for user to access the CCF; handles call setup, termination, hold-on etc... can also provide user w ith CLASS (Custom Local Area Signalling Services) properties
Service Sw itching Point (SSP), Netw ork Access Point (NAP)
Call Control Function (CCF) Provides the means for establishing and controlling bearer services on behalf netw ork users; the CCF refers to call and connection handling in classical sense
Service Sw itching Point (SSP)
Service Sw itching Function (SSF)
Provides the means to recognise calls requiring IN service processing, and to interact w ith call processing and service logic on behalf of these calls
Service Sw itching Point (SSP)
Service Control Function (SCF)
Provides the logical control applied to a call requiring IN service and handles service related processing activities, e.g. analysis translattion, screenig, routing; in other w ords the SCF contains the IN service logic
Service Control Point (SCP), adjuct (AD), Service Node (SN)
Service Data Function (SDF) Handles the access to service-related and netw ork data and provides a logical view of the data to the SCF
Service Control Point (SCP), adjuct (AD), Service Node (SN)
Specialised Resource Function (SRF)
Provides end-user interaction w ith the IN-structured netw ork through control over resources such as DTMF receivers, voice, recognation capabilities, protocol conversion, announcements etc.
Service Node (SN), Intelligent Peripheral (IP)
Service Management Function (SMF)
Provides service provisioning deployment and management control; the SMF allow s access to all IN functional entities for the transfer of information related to service logic and service data
Service Management System (SMS)
Service Creation Environment Function (SCEF)
provides the capability for the creation, verif ication and testing of new IN services
Service Creation Environment (SCE)
11
© Konsultointi Martikainen Oy 1999
History of Intelligent Networks
1960
SPCsElectro-mechanicalRelayswitches
1970
Support forMgmt
1980
Centralizeddatabases,CC and800 -services
1985
FeatureNode
IN/1
1990
IN/1+
AINRel 0.1IN/2
CS
1995
CS1AINRel 0.2
CS2
AINRel 1
“Intelligence”
Time
12
© Konsultointi Martikainen Oy 1999
History of Intelligent Networks
• 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)
13
© Konsultointi Martikainen Oy 1999
History of Intelligent Networks
• 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
14
© Konsultointi Martikainen Oy 1999
History of Intelligent Networks
• ‘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
15
© Konsultointi Martikainen Oy 1999
History of Intelligent Networks
– 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
16
© Konsultointi Martikainen Oy 1999
History of Intelligent Networks
• 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
17
© Konsultointi Martikainen Oy 1999
History of Intelligent Networks
• 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-8CS (Capability Sets), ITU-T, ETSI 1989 -
• European equivalent to AIN• Define basic IN-services (e.g. freephone,
premium rate and UPT)
18
© Konsultointi Martikainen Oy 1999
History of Intelligent Networks
• 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– CS2 specifies management
interfaces and call-unrelated switching functions
– CS3 focus on mobility management (e.g. GSM 2+ and 3 integration) and Interoperability of IN and other networks (e.g. CAMEL)
CS1
CS2
CS3
19
© Konsultointi Martikainen Oy 1999
Intelligent Network Standards
11
22
33
IN Concept and Modeling
Definition of next CS
Recommendation for CSx
Time
Capability sets
CSx
CS2
CS1
T1 T2 Tx
1111
1111
2222
22
3333
33
20
© Konsultointi Martikainen Oy 1999
Structure of IN Standards
Q.12XY with X and Y as follows:X Y00 - General10 - CS1 1 - Principles, Introduction20 - CS2 2 - Service Plane (not included for CS1)30 - CS3 3 - Global Functional Plane40 - CS4 4 - Distributed Functional Plane50 - CS5 5 - Physical Plane60 - CS6 6 - For future use70 - CS7 7 - For future use80 - CS8 8 - Interface Recommendations90 - Vocabulary 9 - Intelligent Network Users Guide
21
© Konsultointi Martikainen Oy 1999
Intelligent Network Standards
Recommendation Q.1200 Q-Series Intelligent Network Recommendations StructureRecommendation Q.1201 Principles of Intelligent Network ArchitectureRecommendation Q.1202 Intelligent Network - Service Plane ArchitectureRecommendation Q.1203 Intelligent Network - Global Functional Plane ArchitectureRecommendation Q.1204 Intelligent Network - Distributed Functional Plane
ArchitectureRecommendation Q.1205 Intelligent Network - Physical Plane ArchitectureRecommendation Q.1208 Intelligent Network - Application Protocol General AspectsRecommendation Q.1211 Intelligent Network - Introduction to Intelligent Network
Capability Set 1Recommendation Q.1213 Intelligent Network - Global Functional Plane for CS1Recommendation Q.1214 Intelligent Network - Distributed Functional Plane for CS1Recommendation Q.1215 Intelligent Network - Physical Plane for CS1Recommendation Q.1218 Intelligent Network - Intelligent Network Interface
SpecificationsRecommendations Q.1219 Intelligent Network Users guide for Capability Set 1
22
© Konsultointi Martikainen Oy 1999
IN Architecture
• 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
© Konsultointi Martikainen Oy 1999
IN Architecture
SSP SSCP
SSF SSF
CCF CCF
SDF
SCF
SN
SCF
SDF
SRF
SSF
CCF
SRF
IP
SS#7 network
SCPSCF
SDPSDF
AD SDF
SCF
SCESCEF
Signaling
Management
SignalingTransferPoint (STP)
CCAF
NAP
CCAF
CCF
CCAF
SRF
Transport
Optional FE
SMPSMF
24
© Konsultointi Martikainen Oy 1999
IN architecture evolution
•Separation of switching and intelligence in the pre-IN, switch-based networks
Control logic (intelligence) Local switch Transit switch
Calling subscribers
Called subscriber
25
© Konsultointi Martikainen Oy 1999
IN architecture evolution
•Centralized intelligence in the network, phase one in IN-evolution
Service Control Point, SCP Local switch Service Switching Point, SSP
Calling subscribers
Called subscriber
26
© Konsultointi Martikainen Oy 1999
IN architecture evolution
•Flexible intelligence allocation in the network, phase two in IN-evolution
Service Control Point, SCPLocal switch Service Switching Point, SSP
Service X in local service point
Service Y in centralized service point
Service Z in user terminal ie. phone
Control logic (intelligence)
Mobile services(GSM, PCS)
Mobile ServicesSwitching Center
Home Location Register
X
Base Station System
27
© Konsultointi Martikainen Oy 1999
IN architecture evolution
•Intelligence on demand
Service Control Point, SCP Local switch Broadband Service Switching Point,BSSP (ATM-switch)
Some of the service intelligenceresides in the user terminal
Intelligence required for a serviceis downloaded to the nearest control point
Broadband IP, Media Server
Control logic (intelligence)
Future mobile services(UMTS, FPLMS, MBS)
Media stream
Control stream
X
28
© Konsultointi Martikainen Oy 1999
IN Services
• Services are the core of IN• Rapid service creation and deployment• 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
© Konsultointi Martikainen Oy 1999
IN Services
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
© Konsultointi Martikainen Oy 1999
IN Services
• 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
© Konsultointi Martikainen Oy 1999
IN Services
• 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
Mass market services
Profiled services
Custom services
1980 1990 2000
ServiceComplexity /Value to customers
32
© Konsultointi Martikainen Oy 1999
IN Services
• 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
© Konsultointi Martikainen Oy 1999
IN Services
• 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
© Konsultointi Martikainen Oy 1999
IN Services
– 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
© Konsultointi Martikainen Oy 1999
IN Services
• 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
© Konsultointi Martikainen Oy 1999
IN Services
• 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
© Konsultointi Martikainen Oy 1999
IN services in Europe
0
2
4
6
8
10
12
14
1995 1996 1997 1998 1999 2000
Mrd ECU
Others
UPT
Calling Card
Televoting
VPN
Premium Rate
Feephone
IN Services
38
© Konsultointi Martikainen Oy 1999
Signaling System no.7
Secure Fault-Tolerant
Speech and DataTransmission Network
Signaling System no.7 NetworkSTP (Signaling Transfer Point)
XX
XUNI(User Network Interface)
NNI( Network Node Interface)
SP(Signaling Point)
NNI
39
© Konsultointi Martikainen Oy 1999
Signaling System no.7
Physical
Data link
Network
Transport
Session
Presentation
Application
MTP Level 1
MTP Level 2
MTP Level 3
SCCP
User PartsTUPISUPMUP
INAP
TCAP
NULL
OSI-RM SS7
OSI Reference model and Signaling System no. 7
NetworkLayers
NetworkPart
ApplicationLayers
User / ApplicationParts
40
© Konsultointi Martikainen Oy 1999
• 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
Signaling System no.7
41
© Konsultointi Martikainen Oy 1999
• 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
Signaling System no.7
42
© Konsultointi Martikainen Oy 1999
• 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
Signaling System no.7
43
© Konsultointi Martikainen Oy 1999
• 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)
Signaling System no.7
STP
STP
STP
STP
SS7 SS7
SS7 SS7
Signalling Link (SL)
SSP Signalling Point (SP)
SCP SSCP
IP
44
© Konsultointi Martikainen Oy 1999
Signaling System no.7
• 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
© Konsultointi Martikainen Oy 1999
Signaling System no.7
• 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
© Konsultointi Martikainen Oy 1999
Signaling System no.7
• 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
© Konsultointi Martikainen Oy 1999
Signaling System no.7
• 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
© Konsultointi Martikainen Oy 1999
Signaling System no.7
• 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
© Konsultointi Martikainen Oy 1999
SAO = Single Association ObjectSACF = Single Association Control FunctionMACF = Multiple Association Control FunctionASE = Association Service Element
a) Single Interaction
Application process
SAO
SAC
F
MTP
SCCP
TCAP
ASE1
ASE2
b) Multiple Coordinated Interaction
Application process
SAO
SAC
FMTP
SCCP
TCAP
ASE1
ASE2
SAO
SAC
F
MTP
SCCP
TCAP
ASE1
ASE2
MACF
Signaling System no.7
INAP Architecture
50
© Konsultointi Martikainen Oy 1999
IN Conceptual Model
• 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
51
© Konsultointi Martikainen Oy 1999
IN Conceptual Model objectives
• 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
52
© Konsultointi Martikainen Oy 1999
IN Conceptual Model Planes
serviceplane
globalfunctional
plane
distributedfunctional
plane
physicalplane -
protocolsand
processing
global service logic
GSL1
GSL2
GSLn
POI
POR
SIB1
SIB2
SIBn
BCP
service1 service2
SF1
SF2
SFn
PE1
PEn
PE2
P1 P2
Pn
FE1FE2
FE1
FE2
FEA
EF
EF
EF
EF
FEA
53
© Konsultointi Martikainen Oy 1999
Service Plane
• 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
© Konsultointi Martikainen Oy 1999
IN CS.1 Services
Automatic Alternative Billing (AAB)
Abbreviated Dialing (ABD)
Account Card Calling (ACC)Credit Card Calling (CCC)
Call Distribution (CD)Call Forwarding (CF)
– Comp. of Call to Busy Subscriber
– Conference Calling (CON)Call Rerouting Distribution (CRD)Destination Call Routing (DCR)Follow-Me-Diversion (FMD)
Freephone (FPH)
Mass Calling (MAS)Malicious Call Identification (MCI)Premium Rate (PRM)Security Screening (SEC)Selective Call Forward on Busy/Don’t
Answer (SCF)Split Charging (SPL)Televoting (VOT)Terminating Call Screening (TCS)User-Defined Routing (UDR)Universal Access Number (UAN)Universal Personal Telecommunications
(UPT)Virtual Private Network (VPN)
55
© Konsultointi Martikainen Oy 1999
IN CS.1 Service Features
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
© Konsultointi Martikainen Oy 1999
Example: Freephone
• 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
© Konsultointi Martikainen Oy 1999
Example: Freephone Service
SSP IP/SN SCP SDP
SWITCH
PBX
Routing
12
A1
A1
A1
PBX
Routing Detect
Connect
Service Logic
Data Function
Service Logic
C1
3
4
5
6
Charging
Service Logic 9
8
7
1. Dialling service number 0800 123 456
2. IN-Call Detection from B-number
3. Service Logic function. Database
query (from SDP)
4. SDP returns programmed charging
information and C-number.
5. SCP sends INAP message to switch
(including charging information)
6. Switch saves special charging
information
7. SCP sends INAP message to switch
(including new number)
8. Switch connects call to new number
9. Alarming
58
© Konsultointi Martikainen Oy 1999
Example: Premium Rate
• 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
© Konsultointi Martikainen Oy 1999
Example: PRM (cont.)
• 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
© Konsultointi Martikainen Oy 1999
Example: Premium Rate Service
SSP IP/SN SCP SDP
SWITCH
PBX
Routing
12
A1
A1
A1
PBX
Routing Detect
Connect
Service Logic
Data Function
Service Logic
C1
3
4
5
Charging
Service Logic
6
9
8
11
7
10
Connect IP
Announcment
Service Logic
1. Dialling service number 0700 123 456
2. IN-Call Detection from B-number
3. Service Logic function. Database
query (from SDP)
4. SDP returns programmed charging
information and C-number.
5. SCP sends INAP message to switch
(for playing announcment)
6. Switch connects IP-device to sub-
scriber line.
7. IP device plays announcment
8. SCP sends INAP message to switch
(including charging information)
9. Switch saves special charging
information
10. SCP sends INAP message to switch
(including new number)
11. Switch connects call to new number
61
© Konsultointi Martikainen Oy 1999
Example: Virtual Private Network
• 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
© Konsultointi Martikainen Oy 1999
Example: VPN (cont.)
• 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
© Konsultointi Martikainen Oy 1999
Example: VPN (cont.)
• 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
© Konsultointi Martikainen Oy 1999
Example: VPN Service(with PNP service features)
SSP IP/SN SCP SDP
SWITCH
PBX
Routing
12
A1
A1
A1
PBX
Routing Detect
Connect
Service Logic
Data Function
Service Logic
C1
3
4
5
6
Charging
Service Logic
6
98
7
7
1. Dialling short number (fromVPN to VPN) or
company number with subnumber (to VPN)
2. IN-Call Detection from B-number
3. SCP sends message to SDP (db query)
4. SDP returns “Calling Plan etc.”
5. SCP sends INAP message to switch
(including charging information)
6. Switch saves charging information
7. SCP sends message to switch
(Connet line to VPN number)
8. Switch connects line
65
© Konsultointi Martikainen Oy 1999
Example: Credit Card Calling
• 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
66
© Konsultointi Martikainen Oy 1999
Example: Universal Personal Telephony
• 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
© Konsultointi Martikainen Oy 1999
Example: UPT (cont.)
• 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.
68
© Konsultointi Martikainen Oy 1999
Example: Service mappings
Service Feature FPH CCC VPN UPTABD o o C = CoreATT o O = OptionalAUTZ C o C (not all O’s here)AUT oCD oLOG o o o oQUE o oTRA oCUG oCOC oCPM o o oCRA o o oCRG o oDUP o oFMD o CONE COUP o C o oPN CPNP CREVC CSPLC CTDR o o o
69
© Konsultointi Martikainen Oy 1999
Global Functional Plane
• 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
© Konsultointi Martikainen Oy 1999
Global Functional Plane
Global Functional Plane Model:
BCP
GSLPOI
POR
SIB1
SIB2
SIB3
71
© Konsultointi Martikainen Oy 1999
Service Independent Building Blocks
• 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
© Konsultointi Martikainen Oy 1999
SIB chains in a Service
SIB1SIB1 SIB2SIB2 SIB3SIB3 SIB6SIB6
SIB4SIB4 SIB5SIB5
POI Basic Call Process POR POR
73
© Konsultointi Martikainen Oy 1999
Service Independent Building Blocks
Algorithm ScreenCharge Service Data
ManagementCompare Status NotificationDistribution TranslateLimit User InteractionLog Call Verify
Information Queue
74
© Konsultointi Martikainen Oy 1999
SIB graphical representation
SIB
CID
SSD SSDparameters
Logicstart
Logicend
CID inputparameters
CID outputparameters
75
© Konsultointi Martikainen Oy 1999
SIB inputs and outputs
• 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
© Konsultointi Martikainen Oy 1999
Example: The Queue SIB
77
© Konsultointi Martikainen Oy 1999
Example: Automatic Alternative Billing
• 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
© Konsultointi Martikainen Oy 1999
Example: AAB (Cont.)
• 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.
79
© Konsultointi Martikainen Oy 1999
IN Automatic Alternative Billing
POI PORPORBasic Call ProcessAddressAnalysed
Clear Call Proceedwith New Data
MATCH
NO MATCHScreenVerifyUserInteraction
Translate Charge
UserInteraction
PORPOI
1
2 3 4
5
6
7 8
9
80
© Konsultointi Martikainen Oy 1999
Example: AAB
1 Basic Call Processinput POI Call Arrival
CID 1) dialed number 2) calling line id
2 User Interaction SIBinput SSD 1) announcement parameters 2) collected info
CID calling line idoutput CID collected info.
End Ok
3 Verify SIBinput SSD 1) min. and max. of numbers 2) format
CID collected infooutput End Ok
81
© Konsultointi Martikainen Oy 1999
Example: AAB
4 Screen SIBinput SSD screenlist indicator
CID collected infooutput End 1) Match or 2) No Match
IF "No Match":
5 User Interaction SIBinput SSD announcement parameters
CID calling line idoutput End Ok
6 Basic Call Processinput POR Clear Calloutput CID calling line id
82
© Konsultointi Martikainen Oy 1999
Example: AAB
IF "Match":
7 Translate SIBinput SSD 1) Type 2) Filename
CID dialed numberoutput CID called number
End Ok
8 Charge SIBinput SSD Account CodeList.
CID Account Codeoutput End Ok
9 Basic Call Processoutput POR Proceed with New Data
CID called number
83
© Konsultointi Martikainen Oy 1999
Distributed Functional Plane
• 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
© Konsultointi Martikainen Oy 1999
Functional Entities (FEs)
SSF
CCAF CCF CCF CCF CCAF
SSF
SCF
SDF
SRF
SMF
SMAF
SCEF
Service managementService controlCall and Resource controlBearer control (below)
85
© Konsultointi Martikainen Oy 1999
Functional Entities
• 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
© Konsultointi Martikainen Oy 1999
Functional entities
• 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
© Konsultointi Martikainen Oy 1999
Functional Entities
– 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
© Konsultointi Martikainen Oy 1999
Functional Entities
• 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
© Konsultointi Martikainen Oy 1999
Functional Entities
– 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
© Konsultointi Martikainen Oy 1999
Functional Entities
• 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
© Konsultointi Martikainen Oy 1999
Functional Entities
– 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;
92
© Konsultointi Martikainen Oy 1999
Service Switching Function Model
IN local resource data
Bearer control
Basic call resource datamanager
Basic call resource dataCCAF
IN local resource datamanager
SCF access manager
IN Switching Manager
Feature interactionmanager/call manager
Basic call manager
Non-IN feature manager
SSF
CCF
SRF
CCAF
IN switching statemodel instance
SCF SLPI A
93
© Konsultointi Martikainen Oy 1999
Originating Basic Call State Model
1. O_Null & Authorize Origination attempt
2. Collect Info
1
3. Analyze Info
2
4. Routing & Alerting
5. O_Active
7
3
4
5
6
8
9
106. Exception
Orig. Attempt_Authorized
Collected_Info
O_Abandon
Analyzed_Info
O_Disconnect
O_Mid_Call
Route_Select_Failure
O_Called_Party_Busy
O_No_Answer
Key: Transition
Detection Point (DP)
Point in Call (PIC)
94
© Konsultointi Martikainen Oy 1999
Functional Entities
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
© Konsultointi Martikainen Oy 1999
Functional Entities
– contains the logic and processing capability required to handle IN provided service attempts;
– interfaces and interacts with other SCFs, if necessary;
– is managed, updated and/or otherwise administered by an SMF;
96
© Konsultointi Martikainen Oy 1999
Service Control Function Model
SLP library
Service logic execution environment (SLEE)SLP Manager
Service logicexecution manager
Functional entity access manager
Functional routinelibrary, includes
functional routines
Service data objectdirectory
IN network-wideresource data
Functionalroutine
manager
SCF dataaccess
manager
Servicelogic
selection /interactionmanager
Resourcemanager
SLP programinstances
SSFSMF SRF SDF
97
© Konsultointi Martikainen Oy 1999
Functional Entities
• 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;– is managed, updated and/or otherwise
administered by an SMF;
98
© Konsultointi Martikainen Oy 1999
Service Data Function Model
SDFdata
manager
Functional entity access manager
Dynamic data
SMF SCFSDF
Service data object directory
Static data with large volume
Exclusive controlmanager
99
© Konsultointi Martikainen Oy 1999
Functional Entities
• 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);
– is managed, updated and/or otherwise administered by an SMF;
100
© Konsultointi Martikainen Oy 1999
Functional Entities
– 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;
101
© Konsultointi Martikainen Oy 1999
Service Resource Function Model
SRF resourcemanager
Functional entity access manager
Resources
SSF/CCF UserSCFSMF
102
© Konsultointi Martikainen Oy 1999
Functional Entities
• 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
© Konsultointi Martikainen Oy 1999
Functional Entities
• 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
© Konsultointi Martikainen Oy 1999
Relating GFP to DFP
SIB SSF/SCF SCF SRF SDFAlgorithm *Charge * *Compare *Distribution *Limit * *Log Call Information * * *Queue * * *Screen * *Service Data Management * *Status notification * * *Translate * *User Interaction * * *Verify *Basic Call Process * *
105
© Konsultointi Martikainen Oy 1999
Example: The Queue SIB
QueueQueue
SSD
Max ActiveMax NumberMax TimeAnnouncement ParameterCIDFP - ResourceCIDFP - Error
Call ReferenceResource
CID
Resource Available
Call Party Abandon
Q Timer Expiry
Q Full
Error
Time spent on QueueError Cause
106
© Konsultointi Martikainen Oy 1999
SIB as a combination of Fees
• 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
107
© Konsultointi Martikainen Oy 1999
Example: Queue with announcement
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)
2077
2073
9073
3071
2076
9071
SRF SCF CCF/SSF
Serv. Logic
PLAYANN
REQREPBCSM
CONNTORES
DISCFWDCONN
resource free
108
© Konsultointi Martikainen Oy 1999
INAP operation description
xyz OPERATIONARGUMENT {Parameter1, Parameter2,...}RESULT {Parameter1, Parameter2,...}LINKED {operation3, operation4,...}ERRORS {error1, error2,...}
error1 ERRORPARAMETER {Parameter6, Parameter7,...} etc
To Peer
OperationsResultsErrors
INAP User ASEs
To Peer
To PeerINVOKERETURN RESULTRETURN ERRORREJECT
BEGINCONTINUEENDABORTUNIDIRECTIONAL
COMPONENT SUBLAYER
TRANSACTION SUBLAYER
Connectionless SCCP
ROSE PDUs
TCAP ASE
109
© Konsultointi Martikainen Oy 1999
Example INAP operation
ConnectToResource ::= OPERATIONARGUMENT
ConnectToResourceArgERRORS {
MissingParameterSystemFailureTaskRefusedUnexpectedComponentSequenceUnexpectedDataValueUnexpectedParameter}
• Connects a call from SSP to IP with SRF
110
© Konsultointi Martikainen Oy 1999
ASN.1 example: ConnectToResourceArg
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
© Konsultointi Martikainen Oy 1999
ETSI Core INAP
• 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
© Konsultointi Martikainen Oy 1999
Physical Plane
• 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
© Konsultointi Martikainen Oy 1999
Physical Plane
SSP SSCP
SSF SSF
CCF CCF
SDF
SCF
SN
SCF
SDF
SRF
SSF
CCF
SRF
IP
SS#7 network
SCPSCF
SDPSDF
AD SDF
SCF
SCESCEF
Signaling
Management
SignalingTransferPoint (STP)
CCAF
NAP
CCAF
CCF
CCAF
SRF
Transport
Optional FE
SMPSMF
114
© Konsultointi Martikainen Oy 1999
Physical Entities (PEs)
• 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
© Konsultointi Martikainen Oy 1999
Physical Entities
• 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
© Konsultointi Martikainen Oy 1999
Physical Entities
• 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
© Konsultointi Martikainen Oy 1999
Physical Entities
• 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
© Konsultointi Martikainen Oy 1999
Physical Entities
• 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
© Konsultointi Martikainen Oy 1999
Physical Entities
• 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
© Konsultointi Martikainen Oy 1999
Physical Entities
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
© Konsultointi Martikainen Oy 1999
Physical Entities
– 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
© Konsultointi Martikainen Oy 1999
Physical Entities
• 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
123
© Konsultointi Martikainen Oy 1999
Relating DFP to Physical Plane
PE:s SCF SSF/CCF SDF SRFSCP C * C *SN C C C CAD C * C *SSP O C O OIP / SRP * * * CSDP * * C *SSCP C C C ONAP * C (CCF only) * *
C: CoreO: Optional*: Not allowed
124
© Konsultointi Martikainen Oy 1999
IN Service Creation
Service Description
Service Analysis
Service Testing
Service Deployment
Service Management
Service Modeling
Service Development
Service creation process for IN services
Service Maintenance
125
© Konsultointi Martikainen Oy 1999
Operations Support System
IN Service Deployment
Product development Requirements
SPECS IF : IF + : SLP: SDF: Physical plane
fault management
billing charging
delivery customer service
New services
SLP SDF
Building
Production
R&DPilots
( IF )
(IF+ )
Service Creation
X2
X1
XN
126
© Konsultointi Martikainen Oy 1999
IN Service Management
BUILDING
SUPPORT
Customer service
DELIVERY BILLING
PRODUCTION CHARGING
FAULT MANAGEMENTSCP
Delivery
system Filter Sort
Filter Sort
Filter Sort
Product configur-
ation VIEW
Service Management
SDP
CDB
FaultBase
Prices
Billing DB
EventBase
127
© Konsultointi Martikainen Oy 1999
Example of IN Service Creation
• 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
128
© Konsultointi Martikainen Oy 1999
Example of IN Service Creation
• 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
129
© Konsultointi Martikainen Oy 1999
Example of IN Service Creation
• 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
130
© Konsultointi Martikainen Oy 1999
Example of IN Service Creation
700-Number Beginning Time C-number Tariff / min700-408408408 09.00am +358 53 624 3270 1,5700-408408408 07.00pm +358 53 624 3271 3,5
From relational model . . .
to object model . . .
700-Numbers Use prohibited Restrictions700-408408408 No700-3584754837 Yes
700-numbers
Use prohibited
Restrictions
700-number
Beginning time
C-number
Tariff / min
• 700-service data modeling
131
© Konsultointi Martikainen Oy 1999
Example of IN Service Creation
mes s ageId=123Start
(wfDbTimer)
Not OK
wf_nt_res p
Yes
Play
Announcement
db_nt_reques t
Not in us e
Connec tTo
Res ource
idle
Re leas eCall
700-s ervice?
InitialDP
idle
idle
Re leas eCall
• Service logic design with SDL and coding with C(* CVOPS state-automaton for 700-service *)(* state input actions *)
idle InitialDP {
(* Call c-function that checks calledPartyNumber *) result=numberTranslationService() if(result==700SERVICE){ (* send query to database and wait for reply *) db_nt_request start(wfDbTimer) to(wf_nt_resp) } else if(result==SERVICE_NOT_IN_USE){ (* Play annoucement to user *) ConnectToResource messageId=123 PlayAnnouncement ReleaseCall to(idle) } else{ (* error *) ReleaseCall to(idle) }}
wf_nt_resp db_nt_resp {
stop(wfDbTimer) if(dbStatus==OK){ ...
132
© Konsultointi Martikainen Oy 1999
IN Markets
• 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
© Konsultointi Martikainen Oy 1999
IN Markets
• 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
© Konsultointi Martikainen Oy 1999
IN technology in Europe
0
1
2
3
4
5
1995 1996 1997 1998 1999 2000
MrdECU
Platforms
Applications
Projects
OSS
IN Markets
135
© Konsultointi Martikainen Oy 1999
Future of Telecommunications: Beyond IN .
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
136
© Konsultointi Martikainen Oy 1999
Future of Telecommunications: Beyond IN .
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
137
© Konsultointi Martikainen Oy 1999
Future of Telecommunications: Beyond IN .
• 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
138
© Konsultointi Martikainen Oy 1999
Future of Telecommunications: Beyond IN .
BCSM Basic Call State ModelDP Detection PointEDP Event Detection PointGMSC Gateway MSCgsmSCF GSM Service Control FunctiongsmSSF GSM Service Switching FunctionHPLMN Home PLMNIPLMN Interrogating PLMNO-CSI Originating CAMEL Subscription InformationOSS Operator Specific ServiceSLPI Service Logic Program InstanceTDP Trigger Detection PointVPLMN Visited PLMN
CAMEL Abbreviations
139
© Konsultointi Martikainen Oy 1999
Future of Telecommunications: Beyond IN .
HLRHLR gsmSCFgsmSCF
HPLMN
MAP
MAP CAP MAP CAP
IPLMN VPLMN
GMSC
GSSF VLRVSSF
VMSC
HLRHLR
CAMEL Architecture
140
© Konsultointi Martikainen Oy 1999
Future of Telecommunications: Beyond IN .
• 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)
141
© Konsultointi Martikainen Oy 1999
• 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
Future of Telecommunications: Beyond IN .
142
© Konsultointi Martikainen Oy 1999
– 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
Future of Telecommunications: Beyond IN .
143
© Konsultointi Martikainen Oy 1999
• 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
Future of Telecommunications: Beyond IN .
144
© Konsultointi Martikainen Oy 1999
Intelligent Network - Summary
• Intelligent Network, IN offers• Open standards, vendor independence• Rapid service creation and deployment• 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