Intelligent Networks: © Konsultointi Martikainen Oy 1999

1
Konsultointi Martikainen Oy 1999
Intelligent Networks
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.
Contents
Introduction and rationale History of IN IN Architecture IN Architecture Evolution IN Services Introduction to Signaling System no. 7 IN Conceptual Model Service Plane Global Functional Plane Distributed Functional Plane Physical Plane
5 11 22 24 28 38 50 53 69 83 112
Contents
Service Creation and Management IN Markets Future of Telecommunications : TMN CAMEL Broadband and Mobile IN MBS
124 132
135 136 141 143
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
Value of Telecom Services

Broadband
VALUE Mobile
Digital
DIGITAL MEDIA VANS AND MOBILE SERVICES
CONNECTIVITY SERVICES 1990 1995 2000 2005
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
Computer Controlled Services

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 Basic Services

IN Service Logic
Basic and supplementary services offered to customers
Hooks Basic call processing
NODE A
NODE B
NODE C
Intelligent Network terminology

Functional Entity
Call Control A ccess Function (CCA F) Call Control Function (CCF)
10
Definition
Related products
Provides the means f or user to access the CCF; handles call setup, Service Sw itching Point (SSP), 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 Provides the means f or establishing and controlling bearer services on behalf netw ork users; the CCF ref ers 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 Control Function Provides the logical control applied to a call requiring IN service and (SCF) handles service related processing activities, e.g. analysis 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 provides a logical view of the data to the SCF Specialised Resource Provides end-user interaction w ith the IN-structured netw ork Function (SRF) through control over resources such as DTMF receivers, voice, recognation capabilities, protocol conversion, announcements etc. Service Management Provides service provisioning deployment and management control; 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 Function (SCEF) new IN services
Service Sw itching Point (SSP)
Service Control Point (SCP), adjuct (A D), Service Node (SN)
Service Control Point (SCP), adjuct (A D), Service Node (SN) Service Node (SN), Intelligent Peripheral (IP) Service Management System (SMS)
Service Creation Environment (SCE)
History of Intelligent Networks

Intelligence
11
CS2 CS1 CS AIN Rel 0.1 AIN Rel 0.2 AIN Rel 1
IN/2 IN/1+ IN/1 Feature Node
SPCs Electromechanical Relay switches
Support for Mgmt
Centralized databases, CC and 800 -services
1960
1970
1980
Time
1985
1990
1995
12
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
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 (preVPN) Term Intelligent Network, Bellcore 1984
14
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
15
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
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 equipmentindependent IN-systems
17
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
18
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 CS3, design started 1997 CS2 specifies management CS2 interfaces and call-unrelated CS1 switching functions CS3 focus on mobility management (e.g. GSM 2+ and 3 integration) and I nteroperability of IN and other networks (e.g. CAMEL)
Intelligent Network Standards

Capability sets 1 1 1 1 CS1 2 3 2 3 2 3
19
CSx
CS2
T1
1 2 3
T2
Tx
Time
IN Concept and Modeling Definition of next CS Recommendation for CSx
20
Structure of IN Standards
Q.12XY with X and Y as follows:
X 00 - General 10 - CS1 20 - CS2 30 - CS3 40 - CS4 50 - CS5 60 - CS6 70 - CS7 80 - CS8 90 - Vocabulary Y
1 - Principles, Introduction 2 - Service Plane (not included for CS1) 3 - Global Functional Plane 4 - Distributed Functional Plane 5 - Physical Plane 6 - For future use 7 - For future use 8 - Interface Recommendations 9 - Intelligent Network Users Guide
Intelligent Network Standards

Recommendation Q.1200 Recommendation Q.1201 Recommendation Q.1202 Recommendation Q.1203 Recommendation Q.1204 Recommendation Q.1205 Recommendation Q.1208 Recommendation Q.1211 Recommendation Q.1213 Recommendation Q.1214 Recommendation Q.1215 Recommendation Q.1218 Recommendations Q.1219
21
Q-Series Intelligent Network Recommendations Structure Principles of Intelligent Network Architecture Intelligent Network - Service Plane Architecture Intelligent Network - Global Functional Plane Architecture Intelligent Network - Distributed Functional Plane Architecture Intelligent Network - Physical Plane Architecture Intelligent Network - Application Protocol General Aspects Intelligent Network - Introduction to Intelligent Network Capability Set 1 Intelligent Network - Global Functional Plane for CS1 Intelligent Network - Distributed Functional Plane for CS1 Intelligent Network - Physical Plane for CS1 Intelligent Network - Intelligent Network Interface Specifications Intelligent Network Users guide for Capability Set 1
22
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
IN Architecture
SMP
SMF
SCE SDP
SCEF
SCP
SCF
SDF
SN
SSF SRF SCF SDF
SS#7 network
AD
SCF
SDF
CCF
IP
SRF Signaling Transfer Point (STP)
SSP
CCF
SSCP
CCAF SCF SSF
SRF CCF SDF
NAP
CCAF SSF
CCAF
Optional FE Signaling Transport Management
CCF
24
IN architecture evolution
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 network, phase two in IN-evolution
Service X in local service point
Mobile services (GSM, PCS)

Mobile Services Switching Center
X
Base Station System Home Location Register
Service Y in centralized service point Service Z in user terminal ie. phone

Local switch Control logic (intelligence) Service Switching Point, SSP
27
Intelligence on demand
Intelligence required for a service Some of the service intelligence is downloaded to the nearest control point resides in the user terminal
Future mobile services (UMTS, FPLMS, MBS)
Media stream
Broadband IP, Media Server
Control stream
Service Control Point, SCP Control logic (intelligence)
Local switch
Broadband Service Switching Point, BSSP (ATM-switch)
28
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
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 SIBbased
30
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
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
Custom services Service Complexity / Value to customers Mass market services
Profiled services
1980
1990
2000
32
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
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
IN Services
usage for switched voice, switched data or both single interface for all domestic and international needs e.g.Soneras 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
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
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
IN Services
IN services in Europe
Mrd ECU 14 12 10 8 6 4 2 0 1995 1996 1997 1998 1999 2000
Others UPT Calling Card Televoting VPN Premium Rate Feephone
38
Signaling System no.7
Secure Fault-Tolerant
Signaling System no.7 Network STP (Signaling Transfer Point)
NNI
Speech and Data Transmission Network
X
SP
UNI
(User Network Interface) (Signaling Point)
NNI
( Network Node Interface)
39
OSI Reference model and Signaling System no. 7

INAP
Application
TCAP
Application Layers
Presentation Session Transport Network
NULL
User Parts TUP ISUP MUP
User / Application Parts
Network Layers
Data link Physical
SCCP MTP Level 3 MTP Level 2 MTP Level 1
Network Part
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 STP SS7 STP SS7 SS7 STP
SSP
Signalling Point (SP)
IP
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 ASE1 SAO ASE1 SAO ASE1
SACF
SACF
ASE2 TCAP
ASE2 TCAP
SACF
ASE2 TCAP
SCCP
SCCP
SCCP
MTP a) Single Interaction
MTP
MTP
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
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 objectives
51
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 Planes

s erv ic e1 S F 1 S F n S F 2 s erv ic e2
52
s erv ic e p lan e
g lo b a l s e rv ic e lo g ic P O I S IB 1 B C P S IB 2 P O R S IB n G S L n G S L 2 g lo b a l fu n c tio n a l p lan e G S L 1
F E 1 F E A E F E F
F E 2 F E A E F d istrib u te d fu n c tio n a l p lan e
E F
P E 2 P 1 P E 1 P n P 2 P E n F E 1 F E 2 p h y s ica l p lan e p ro to c o ls a n d p ro c e ss in g
53
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 servicerelated 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
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/Dont 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
IN CS.1 Service Features

Abbreviated Dialing (ABD) Attendant (ATT) Authentication (AUTC) Authorization Code (AUTZ) Automatic Call Back (ACB) Call Distribution (CD) Call Forwarding (CF) Call Forwarding on Busy (CFC) Call Gapping (GAP) Call Hold with Announcement (CHA) Call Limiter (LIM) Call Logging (LOG) Call Queuing (QUE) Call Transfer (TRA) Call Waiting (CW) Closed User Group (CUG) Consultation Calling (COC) Customer Profile Management (CPM)
Customized Recorded Announcement (CRA) Customized ringing (CRG) Destinating User Prompter (DUP) Follow-Me Diversion (FMD) Mass Calling (MAS) Meet-Me Conference (MMC) Multiway Calling (MWC) Off-Net Access (OFA) Off-Net Calling (ONC) One Number (ONE) Origin Dependent Routing (ODR) Originating Call screening (OCS) Originating User Prompter (OUP) Personal Numbering (PN) Private Numbering Plan (PNP) Reverse Charging (REVC) Split Charging (SPLC)
56
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
Example: Freephone Service
SWITCH SSP A1 1 PBX Routing A1 A1 PBX Routing Service Logic IP/SN SCP SDP
2
Detect
3 4
Data Function
5 6
Charging Service Logic
7
Service Logic
8 9
C1 Connect
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
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
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 multisite 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

SWITCH SSP A1 1 PBX Routing A1 PBX IP/SN SCP SDP
2
Detect
3
Service Logic
Routing A1
4
Data Function
5 6
Connect IP Service Logic
7
Announcment
8
Service Logic
9
Charging
10
Service Logic
11
Connect C1
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 subscriber 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
Example: Virtual Private Network
61
VPN permits to build a private network by using the public network resources. The subscribers 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.)
VPN the use of public network resources to provide private network capabilities without necessarily using dedicated network resources. The subscribers 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 plans digit sequences, structures and meaning.
63
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.
Example: VPN Service

(with PNP service features)
64
SWITCH SSP A1 1 PBX IP/SN SCP SDP
2
Detect
Routing
A1 A1
PBX
Routing
6 7
3
Service Logic
4
Data Function
5 6
Charging Service Logic
7
Service Logic
9
C1
Connect
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
Example: Credit Card Calling
65
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 Personal Telephony
66
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.)
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 mappings

Service Feature ABD ATT AUTZ AUT CD LOG QUE TRA CUG COC CPM CRA CRG DUP FMD ONE OUP PN PNP REVC SPLC TDR FPH CCC o C VPN o o o o o o o o o o o o o o C o C o C C o o C o UPT C
68
C = Core O = Optional (not all Os here)
o o
o o o o
o o o C o C
69
Global Functional Plane
The Global Functional Plane (GFP) models the IN-structured network as a single entity. Contained in this view is a global (networkwide) 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

Global Functional Plane Model:
GSL
POI BCP SIB1
POR
SIB2
SIB3
Service Independent Building Blocks
71
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
SIB1
SIB2
SIB3
SIB6
SIB4
SIB5
POI
Basic Call Process
POR POR
Service Independent Building Blocks

Algorithm Charge Compare Distribution Limit Log Call Information Queue
73
Screen Service Data Management Status Notification Translate User Interaction Verify
SIB graphical representation
74
SSD
SSD parameters
Logic start
SIB
Logic end
CID input parameters
CID
CID output parameters
75
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
Example: The Queue SIB
Example: Automatic Alternative Billing
77
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.)
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 Billing

M ATCH Translate 2 User Interaction 3 Verify 4 Screen 7 NO MATCH 5 User Interaction Charge 8
79
1 POI POI Address Analysed
9 POR POR Proceed with New Data
Basic Call Process
Clear Call
80
Example: AAB
1 Basic Call Process input POI CID 2 User Interaction SIB input SSD CID output CID End 3 Verify SIB input output Call Arrival 1) dialed number 2) calling line id
1) announcement parameters 2) collected info calling line id collected info. Ok
SSD CID End
1) min. and max. of numbers 2) format collected info Ok
81
Example: AAB
4 Screen SIB input output IF "No Match": SSD CID End screenlist indicator collected info 1) Match or 2) No Match
5 User Interaction SIB input SSD CID output End

6 Basic Call Process input POR output CID
announcement parameters calling line id Ok
Clear Call calling line id
82
Example: AAB
IF "Match": 7 Translate SIB input output
SSD CID CID End
1) Type 2) Filename dialed number called number Ok
8 Charge SIB input output
SSD CID End
Account CodeList. Account Code Ok
9 Basic Call Process output POR CID
Proceed with New Data called number
Distributed Functional Plane
83
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)

SMAF SMF SCEF SDF SCF SRF
SSF CCAF CCF
SSF CCF CCF CCAF
Service management Service control Call and Resource control Bearer control (below)
85
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
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
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
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
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
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
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;
Service Switching Function Model

SCF SLPI A SSF SCF access manager
92
IN local resource data manager
IN Switching Manager IN switching state model instance
IN local resource data
Non-IN feature manager
Feature interaction manager/call manager
CCF SRF Basic call resource data manager Basic call manager
CCAF
Basic call resource data
Bearer control
CCAF
Originating Basic Call State Model

O _A b an d o n 10 1 . O _ N u ll & A u th o r iz e O r i g i n a ti o n a tte m p t 6 . E x c e p tio n 1 O r i g . A tte m p t_ A u th o r i z e d
93
2 . C o l l e c t I n fo
C o lle c te d _ In fo
3 . A n a l y z e I n fo
A n a ly z e d _ In fo 4
4 . R o u ti n g & A l e r ti n g
R o u t e _ S e l e c t _ F a i lu r e
5
O _ D is c o n n e c t
9
7 5 . O _ A c tiv e
O _ C a lle d _ P a r ty _ B u s y
6 O _N o _A n sw er 8 O _ M id _ C a ll
K ey:
T r a n s itio n D e te c tio n P o in t (D P ) P o i n t i n C a l l (P I C )
94
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
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;
Service Control Function Model

SLP library
96
SLP Manager Service logic execution manager Service logic selection / interaction manager SLP program instances
Service logic execution environment (SLEE) Functional routine library, includes functional routines
Functional routine manager SCF data access manager
Service data object directory IN network-wide resource data
Resource manager
Functional entity access manager
SMF
SSF
SRF
SDF
97
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;
Service Data Function Model

Exclusive control manager SDF data manager Dynamic data
98
Static data with large volume
Service data object directory
SMF
SDF
SCF
99
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
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;
Service Resource Function Model
101
SRF resource manager
Resources
SSF/CCF
SMF
SCF
User
102
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
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
Relating GFP to DFP

SIB SSF/SCF Algorithm Charge * Compare Distribution Limit Log Call Information * Queue * Screen Service Data Management Status notification * Translate User Interaction Verify Basic Call Process * SCF * * * * * * * * * * * * SRF SDF
* * * * * * * * *
* *
105
Example: The Queue SIB

Max Active Max Number Max Time Announcement Parameter CIDFP - Resource CIDFP - Error
SSD
Resource Available Call Party Abandon
Queue
Q Timer Expiry Q Full Error
Call Reference Resource
CID
Time spent on Queue Error Cause
SIB as a combination of Fees
106
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 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)
107
SRF
SCF
Serv. Logic 9071
CCF/SSF
REQREPBCSM 2076 CONNTORES 2073
PLAYANN 3071 resource free 9073 DISCFWDCON N
2077
108
INAP operation description

INAP User ASEs xyz OPERATION ARGUM ENT {Parameter1, Parameter2,...} RESULT {Parameter1, Parameter2,...} LINKED {operation3, operation4,...} ERRORS {error1, error2,...} error1 ERROR PARAM ETER {Parameter6, Parameter7,...} etc
To Peer
Operations Results Errors
TCAP ASE
To Peer
COM PONENT SUBLAYER ROSE PDUs TRANSACTION SUBLAYER

To Peer
INVOKE RETURN RESULT RETURN ERROR REJECT BEGIN CONTINUE END ABORT UNIDIRECTIONAL
Connectionless SCCP
109
Example INAP operation

ConnectToResource ::= OPERATION ARGUMENT ConnectToResourceArg ERRORS { MissingParameter SystemFailure TaskRefused UnexpectedComponentSequence UnexpectedDataValue UnexpectedParameter }
Connects a call from SSP to IP with SRF
ASN.1 example: ConnectToResourceArg

ConnectToResourceArg ::= SEQUENCE {
CHOICE { ipRoutingAddress legId both
110
none }, extensions },
[0] IPRoutingAddres [1] LegId [2] SEQUENCE { ipRoutingAddress [0] IPRoutingAddres legId [1] LegId }, [3] NULL [4] SEQUENCE SIZE (0..MAX) OF ExtensionField OPTIONAL
111
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
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 INstructured networks. It also indicates which functional entities are implemented in which physical entities.
113
Physical Plane
SMP
SMF
SCE SDP
SCEF
SCP
SCF
SDF
SN
SSF SRF SCF SDF
SS#7 network
AD
SCF
SDF
CCF
IP
SRF Signaling Transfer Point (STP)
SSP
CCF
SSCP
CCAF SCF SSF
SRF CCF SDF
NAP
CCAF SSF
CCAF
Optional FE Signaling Transport Management
CCF
114
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
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
Physical Entities
Service Switching Point, SSP
PSTN exchange modified to recognize INservices 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
Physical Entities
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
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
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
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
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
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
Relating DFP to Physical Plane

PE:s SCP SN AD SSP IP / SRP SDP SSCP NAP
C: Core O: Optional *: Not allowed
123
SCF C C C O * * C *
SSF/CCF * C * C * * C C (CCF only)
SDF C C C O * C C *
SRF * C * O C * O *
124
IN Service Creation
Service Description
Service creation process for IN services
Service Analysis
Service Modeling
Service Testing Service Maintenance
Service Development
Service Deployment Service Management
125
IN Service Deployment
Service Creation
fault management
Operations Support System
billing
(IF+ ) ( IF )
Production
Product development
Requirements SPECS
charging delivery customer service
R&D Pilots
IF : IF + : SLP: SDF: Physical plane
SLP
New services
SDF
Building
126
IN Service Management
Service Management
Customer service
VIEW
BILLING DELIVERY
Delivery system
CDB
Prices
Product configuration
Billing DB
Filter Sort
BUILDING
CHARGING PRODUCTION
Filter Sort
Event Base
SDP SCP
FAULT MANAGEMENT SUPPORT
Filter Sort
Fault Base
Example of IN Service Creation
127
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
128
write definitions and service specific dbactions 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
129
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
130
700-Numbers Use prohibited 700-408408408 No 700-3584754837 Yes
Restrictions
From relational model . . .

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

idle
131
Service logic design with SDL and coding with C

(* CVOPS state-automaton for 700-service *)
(* state input actions *) idle
InitialDP
700-s e rvic e ?
Ye s db_nt_re que s t
No t in us e Co nne c tTo Re s o urc e
No t OK Re le as e Call
Start (wfDbTime r)
me s s ag e Id=123
idle
wf_nt_re s p
Play Anno unc e me nt
Re le as e Call
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) } }
{ stop(wfDbTimer) if(dbStatus==OK){ ...
wf_nt_resp db_nt_resp
idle
132
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
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
IN Markets
IN technology in Europe
Mrd 5 ECU 4 3 2 1 0 1995 1996 1997 1998 1999 2000
Platforms Applications Projects OSS
Future of Telecommunications: Beyond IN

.
135
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
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
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
CAMEL Abbreviations
BCSM DP EDP GMSC gsmSCF gsmSSF HPLMN IPLMN O-CSI OSS SLPI TDP VPLMN Basic Call State Model Detection Point Event Detection Point Gateway MSC GSM Service Control Function GSM Service Switching Function Home PLMN Interrogating PLMN Originating CAMEL Subscription Information Operator Specific Service Service Logic Program Instance Trigger Detection Point Visited PLMN

.
139
CAMEL Architecture
HPLMN
HLR
MAP IPLMN CAP
MAP
gsmSCF
MAP CAP VPLMN
GSSF GMSC
VLR
VSSF
VMSC

.
140
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
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

.
142
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

.
143
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 Summary

Intelligent Network, IN offers

144
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

Intelligent Networks: © Konsultointi Martikainen Oy 1999

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

Intelligent Networks: © Konsultointi Martikainen Oy 1999

Uploaded by

Copyright:

Available Formats

1

Konsultointi Martikainen Oy 1999

Konsultointi Martikainen Oy 1999

Konsultointi Martikainen Oy 1999

Konsultointi Martikainen Oy 1999

Intelligent Network (IN)

Konsultointi Martikainen Oy 1999

Value of Telecom Services

Konsultointi Martikainen Oy 1999

CONNECTIVITY SERVICES 1990 1995 2000 2005

Konsultointi Martikainen Oy 1999

Second Wave (2000-2006)

Third Wave (2006 - )

Computer Controlled Services

Konsultointi Martikainen Oy 1999

Separation of IN and Basic Services

Konsultointi Martikainen Oy 1999

Basic and supplementary services offered to customers

Hooks Basic call processing

Hooks Basic call processing

Hooks Basic call processing

Intelligent Network terminology

Konsultointi Martikainen Oy 1999

Service Sw itching Function (SSF)

Service Sw itching Point (SSP)

Service Control Point (SCP), adjuct (A D), Service Node (SN)

Service Creation Environment (SCE)

History of Intelligent Networks

Konsultointi Martikainen Oy 1999

IN/2 IN/1+ IN/1 Feature Node

SPCs Electromechanical Relay switches

Support for Mgmt

Centralized databases, CC and 800 -services

History of Intelligent Networks

Konsultointi Martikainen Oy 1999

History of Intelligent Networks

Konsultointi Martikainen Oy 1999

History of Intelligent Networks

Konsultointi Martikainen Oy 1999

Feature Node concept 1985 (Ameritech)

IN/1, Bellcore 1986 Centralized architecture

History of Intelligent Networks

Konsultointi Martikainen Oy 1999

IN/2, Bellcore 1987 Expanded IN/1 functionality

History of Intelligent Networks

Konsultointi Martikainen Oy 1999

Service-, switch- and equipmentindependent IN-systems

History of Intelligent Networks

Konsultointi Martikainen Oy 1999

Stepwise development via number of releases

History of Intelligent Networks

Konsultointi Martikainen Oy 1999

Intelligent Network Standards

Konsultointi Martikainen Oy 1999

IN Concept and Modeling Definition of next CS Recommendation for CSx

Konsultointi Martikainen Oy 1999

Intelligent Network Standards

Konsultointi Martikainen Oy 1999

Konsultointi Martikainen Oy 1999

Konsultointi Martikainen Oy 1999

SRF CCF SDF

Optional FE Signaling Transport Management

Konsultointi Martikainen Oy 1999