Parlay Architecture and
NGN
Manfred Schneps-Schneppe Prof Dr CEO AbavaNet
Dmitry Namiot Ph D (math) CTO AbavaNet
ITU/ITC Regional Seminar on Network Evolution to
Next Generation Networks and Fixed Mobile Convergence
for CEE, CIS and Baltic States
Moscow (Russia), 27-30 April 2004
1
Outlook
1.
2.
3.
4.
What is Parlay
Parlay Standartization Process
Parlay for UMTS & 3GPP
Parlay Implementation
(Appium, Ericsson, HP, IBM)
5.
How to modernize Russian telecommunications
–
–
–
–
HP OpenCall
Intel NetStructure & ECMA CSTA
Parlay/OSA & JAIN
Application server AbavaNet
2
1
1.1 What is Parlay
( Zygmunt LozinskiParlay President & IBM STSM)
A bridge …
• From IT to telecommunications
• From application developer to
network operator
• From fixed to mobile
• From enterprise to service provider
• From today’s network to future
networks
3
1.2 The Parlay/OSA API
Application
OSA API
OSA Gateway
SGSN
MSC
PLMN
GSM/GPRS
(CS)
SSP
PSTN / ISDN
(CS)
S-CSCF
PLMN
UMTS
(PS/IMS)
PBX
Enterprise
4
2
1.3 The Parlay/OSA Framework
- control of access to the network
- integrity management
- discovery of network functionality
Client Application
1
Enterprise
Operator
Framework
4
3
2
2
Call
Control
Mobility
etc
Registered Services
- Application subscription
to services
- SCF registration
- support of multimulti-domain
5
1.4 How does the Parlay framework work ?
Application
4: authentication
5: request Discovery interface
6: discover Service
7: Select Service + sign SLA
10: return Service Manager
11: Use service
1: authentication
2: request Registration interface
Framework
3: register factory
Service
8: create Service Manager
9: return Service Manager
6
3
1.5 Open Service Access Example
Retrieving football scores…
Web
Web-based
-based
Sports
Sports
Program
Program
13: get scores
Client
Client
Application
Application
10: reportNotification
11: queryBalanceReq
1: register with Framework and
select services
12: queryBalanceRes
14: sendInfoReq (scores)
8: return Service Manager
interfaces
16: directDebitAmountReq
17: directDebitAmountRes
2: create Service Manager
3: return Service Manager
4: create Service Manager
5: return Service Manager
Framework
Account
Mgmt
SCF
Generic UI
SCF
Charging
SCF
6: create Service Manager
7: return Service Manager
9: Send message
to Sports Service
(USSD)
15: Receive scores (USSD)
7
2.1 Parlay Work Synchronization
2001
1Q
Parlay
2Q
2002
3Q
2.1
4Q
3.0
1Q
2Q
3Q
1Q
4Q
2003
2Q’ish
3.1
5.0
4.0
1.0
ETSI
1.1
3.0
2.0
3GPP
Release 4
4.0
4.1
4.2
4.3
Release 5
Release 6
5.0
5.1
5.2
5.3
6.0
= point of alignment between specifications
Freeze
march 04
8
4
2.2 ONE API for ONE developer community
1.) Requirements
introduced
by individual bodies
JAIN
3.) Results are
transferred back to
individual bodies
Joint
API
Group
n UMTS
n OSA (Open Service Access)
2.) create the API
that supports the superset
of all requirements.
(Joint meetings)
n NGN
n OSA (Open Service Access)
Current Workflow
Reference in ITU -T Roadmap
9
2.3 Current Parlay 4 SCFs (Jan 2003)
OSA
applications
Content based
Charging
Connectivity
Management
Generic
Messaging
Call
Control
Mobility
Management
Framework
User
Interaction
Terminal
Capabilities
Presence &
Availability
Policy
Management
Data
Session
Control
Account
Management
Key:
New
Enhanced
Unchanged
10
5
11
2.5 The Parlay-X Gateway
XML Script, Servlets, Java, C
C, Java, XML Script
Application
Server
Application
Server
Parlay X interface
Parlay-X
Gateway
The Parlay APIs
Parlay
Gateway
Network
Elements
Network
Elements
12
6
3.1 OSA/Parlay and 3GPP
3GPP
Radio Access Network
(RAN/GERAN)
Core Network
(CN)
CAMEL
SIP
...
Terminals
Services and
System
Aspects
OSA
OSA stage 3:
protocols
Services
Architecture
+coordination
Security
Codec
OSA stage 1:
stage 2:
requirements OSA
architecture
Telecom
mgmt
13
3.2 UMTS and Parlay (FOKUS, Germany)
3rd Party
Components
Portal
Mobility &
Profiles Presence
Adaptation
Modules
Streaming
SIP
Server
Server
Remote
3Gb Testbeds
Local
Application
Server
Remote
Application
Server
OSA/Parlay
Server
Measurements
(QoS)
Intranet
UMTS
Messaging
Server
WLAN
802.11b WLAN
802.11b
Your Application?
Internet
Call
Server
GPRS
DVB-- T
DVB
GSM
ISDN
IP-- Satellite
IP
14
7
4.1 Appium-GBox – Parlay SCE
Validation & Testing
Appium
App Templates
App
Appium
App Framework
App
App
Appium
App Framework
Call Control
Messaging
Notification
Mobility Mgnt
Voice Interaction
User Profile Mgnt
Personal Content
Appium TAS
Parlay/CORBA
Appium Lab Parlay GW
INAP CS1/2
Appium OAM Server
Software Components
Development
H.323
Tools
VoIP Net
VoIP clients / terminals
Borland JBuilder
Network Simulator
VoIP Parlay Lab
15
4.2 Ericsson Enterprise Service Platform
Enterprise Server
Platform
(SSP switch )
16
8
4.3 Ericsson Testing Environment
17
4.4 IBM WebSphere Telecom Appl Server & Parlay/OSA
18
9
4.5 IBM Products for Telecom
19
4.6 HP CMC (Content Mediati?n and Charging) and
Parlay Gateway
User
Repository
3rd Party
Applications
Balance Manager
Real-time Rating
Settlement
M- Payment
Transaction Manager
RT Mediation
Content
Mediation & Charging
Internal
Charging
API
External
Charging
API
OSA/
Parlay
Gateway
Service
Delivery
Platform
20
10
5.1 Russian telecom programs to be considered
Russian Telecom Modernization Program:
from 30M telephone lines in 2001
(25M lines, namely 17K obsolete exchanges)
to 47M lines in 2010 (to install over 30M lines in 10 years)
e-Russia: Internet for every school and local government
Universal Service:
All villages with payphones
(now more than 1/3 of villages without phones)
Internet-access for each village with 500 inhabitants
Federal Intelligent Network (national protocol INAP-R):
Several federal services (FPH, CCC, PRM,…) for each subscriber
BUT…40 million mobile subscribers
21
5.2 Russian IN Pilot (fragment)
SCP/SDP/SMP/SCEP
INXpress
Siemens
Tyumen Telecom
INAP-R
SSP
SS7
INAP-R
Rostelecom (Moscow)
INAP-R
SSPSSP
Svetets
Server
PSTN
EWSD
S-12
Alcatel
INAP-R
CT Server
Protei
(LONIIS)
IP
network
INAP-R
Sviazinform (Penza)
SCP/SDP/SMP/SCEP A1400
Uralsviazinform (Perm)
22
11
5.3 Approach 1. HP TMC (Telecom Media Card)
STM 1 =155 ? bps to SDH
2016 PCM channels ( 64 Kbps) = 63 E1
PCI bus for input-output
ECTF H100 bus (PCM standard)
DSP for fax, VoIP, SIP, H323, MGCP
ECTF S.410 call control
Η
SONET OC3 / SDH STM1 fiber
H.100 bus
PCI bus
23
5.4 Approach 1. Rural Service Node RUCOM
ADM
SDH-ring
Telephone Exchange
Urban telephone network
To toll exchange and
IN-controller SCP
ADM
SS7 and other signaling
STM1=155 Mbps=63 E1 =2016 trunks
RUCOM – NGN product
Zonal service node (rural-suburb node, Class 4 switch)
+ Local exchange (Class 4 switch)
+ SSP (for access to SCP and federal services)
+ SIP-server (for advanced IP-services)
CAS, R.1,5
Rural exchanges
Analog telephone
Call-center
regional services for
any subscriber
SIP-protocol
Remote Subscriber Unit
SIP -telephone
24
12
5.5 Approach 2. Russian Rural Communications
(based upon Intel Technologies and CSTA standards)
INAP-R
Regional
Service Node (
Intel
NetStructure
based)
Protocol
CSTA
Application
Server
AbavaNet
(Intel
NetMerge
based)
Protocol CSTA
for WSDL
Web services
Protocol CSTA
Local Network
Subscriber
Line
Contact
Center
25
5.6 Approach 3. Parlay Gateway as NGN
office: ISUP and SIP stacks, AbavaNet AS
Third-Party
Applications
Parlay GW
(modified)
AbavaNet
Appl
Server
Parlay/OSA
SCF
Parlay/OSA
Framework
Platform Services (Alarms, Measurements, Audit)
IN Call Model
SIP Call Model
Parlay Call Model
SS7 Stack
SIP Stack
ISUP Stack
SS7
Network
IP Network
SoftSwitch
SIP Proxy
Rural
Remote
Unit
26
13
5.7 Approach 3. JAIN BASED NETWORK
ARCHITECTURE ?
27
5.8 Approach 3. Application Server AbavaNet
(Open source based)
Application Server AbavaNet
Location
server JDBC
E- mail
SMTP
Web-brouser
HTTP
Jabber server
Presence
Jabber server
Instant
Messaging
28
14
5.9 RUCOM: Market estimate
Up to 1500 small transit exchanges in Russia
(so called rural-suburb nodes),
17K “obsolete” crossbar exchanges
1 RUCOM for 3 – 5 rural districts in Russia
= 300 RUCOM type systems
Each RUCOM up to 2K - 4K trunks
and 5K – 20 subscriber lines
Market abroad Russia (?)
29
5.10 Parlay Training in Russia
•
Parlay Course (Ericsson sponsored, in Russian) see www.sotovik.ru
(Parlay technology, 7 lectures)
•
Book “Parlay architecture and NGN” (in Russian, 2004) co-authorized
by M.Schneps-Schneppe, A.Kilin, M.Rodina, A.Chistov, D.Namiot
•
For contacts www.abavanet.ru
sneps@abavanet.ru
30
15