Transcript Integration of IN and Internet

P909: Enabling technologies for IN evolution and INInternet integration
Integration of IN and Internet:
The balance between idealism and
current products realism
Michael Barry, Broadcom
Valerie Blavette, Eurescom(CNET)
Uwe Herzog, Eurescom(T-Nova)
Telma Mota, Portugal Telecom
Geir Gylterud
Telenor AS
[email protected]
Interworking 2000, Bergen
G. Gylterud, 03 October 2000
Outline
• Market evolution and trends
• Connecting IN and the Internet?
• Proposed solution for IN-Internet
convergence
• Use of existing standards and products
• Conclusions
Interworking 2000, Bergen
G. Gylterud, 03 October 2000
Trends, Problem statement
Trends:
• Tremendous growth of the Internet
• Shift from circuit switched to packet switched
networks
• Huge growth in the IP telephony market forecasted
What will be the consequence for IN?
• How can PSTN/IN and the Internet get connected?
• How can a joint service platform be realised?
• How can 3rd pty service providers get access?
Interworking 2000, Bergen
G. Gylterud, 03 October 2000
Putting IN and Internet together
• At Bearer control level
– a lot of effort on protocol development (ITU-T, IETF etc.)
– SIP/H.323 for VoIP
– MeGaCo/H.248 for controlling gateways
• At Service control level
Reasons for interworking:
– Providing services over heterogeneous networks
– Providing IN services to Internet users
– Facilitating Internet entities to start PSTN calls
– Access to data in the “opposite” domain
Interworking 2000, Bergen
G. Gylterud, 03 October 2000
Key factors for architecture defininition
P909 proposes integration at Service control level
by means of a unique Service Platform
• unique services and supporting functionalities over IN
and Internet
• evolving from current IN towards an open platform:
– strongly based on “middleware” solutions;
– supporting high levels of programmability and flexible
• having open and standardised API's for service
creation
Interworking 2000, Bergen
G. Gylterud, 03 October 2000
Service Platform functionalities
Transaction
High Availability
&
Recovery
Logging
xxx
Trader
Invitation
Log
Handling
Service
Naming
Selection
Notification
Handler
Notification
Life-Cycle
Call Control
Installation
&
Configuration
xxx
Management
Software
- deployment
Frameworks
- service etc.
Service
Session
Monitoring
Service Logic
Messaging
Mobility
Control
Interface
Authentication
Repository
DPE
Repository
Web Server
Concurrency
Control
User Profile
3Pty Interface
Charging
Billing
Directory
Security
Service
Legend:
SCP: Service Control Point
SSP: Service Switch. Point
VGW: Vocal Gateway
NAS: Network Access Server
PBX: Private Branch Exch.
Terminal
capabilities
Persistence
Adaptors
Distributed platform
SCP
EmailServer
VGW
SSP
PSTN/IN
NAS
Internet
Interworking 2000, Bergen
G. Gylterud, 03 October 2000
Private
Networks
PBX
Key functionalities of service level
• Call control/User interaction
– Provides an abstract API for call control and
User interaction on
PSTN, IP and hybrid networks
User Profile
Personal Data
Logical Identifiers
Authentication Data
Service Independent Preferences
• Message control
1
1
– Unique interface to send and handle various
types of messages in heterogenous networks
1
0..*
1
Personalization
• User profile
On-line Registrations
1
Default Configurations
Active Rule Group
– Only One! For Internet, IN
and other services, reusable
– Interfaces with directory services
via standard protocols (LDAP)
Services
1
Meeting Scheduler
Internet Call Waitg
Click-to-Dial
Virtual Presence
Distr. Call Centers
0..*
1..*
Registration
Rule Group
1..*
0..*
Rule
1..*
1..*
1..*
Event
0..*
Condition
Interworking 2000, Bergen
G. Gylterud, 03 October 2000
1..*
1
overrides
1..*
1..*
1
1..*
Action
Configuration
Key functionalities of adaptation level
Adaptors towards resources
• For Call Control and User Interaction
– SCP (proprietary)
Call Contro/User Interaction
– SSP (SS7-INAP)
– Vocal Gateways (MeGaCo/H.248
above proprietary APIs
SSP SCP VGTW PBX SIP IVR/
– Private Networks (JTAPI)
Srv
TTS
– SIP server
– IVR/TTS
• For Messaging Control
– Voicemail
– Email
– SMS
– Unified Messaging Servers
Interworking 2000, Bergen
G. Gylterud, 03 October 2000
Messaging Control
Email
Server
Vmail
Server
To prevent re-inventing the wheel...
•
P909 was looking at
and investigating related
standards, Architectures, APIs,
products ...
Interworking 2000, Bergen
G. Gylterud, 03 October 2000
Parlay can be used for...
Service Platform functionalities
T r a n s a c t io n
H ig h A v a i l a b il i t y
xxx
– to complicated for mass market end-user
access
– extension to access user profile data or
for access from advanced terminals (WAP, PDA etc.)
Logging
&
R e co v ery
Service
N a m in g
Selection
Invitation
Log
Handling
Notification
Handler
N o t ific a tio n
• starting point for platform interfaces
– Service i/f for Call Control, User interaction
– abstract interface for service developers
T ra de r
L ife - C y c le
Call Control
In s t a lla t io n
&
C o n fig u r a tio n
xxx
Management
S o ft w a re
- deployment
Fra m e w o rks
- service etc.
Service
Session
M o n it o r in g
Service Logic
M o b i l it y
Messaging
Control
I n te r fa c e
Authentication
R e p o s it o r y
D P E
Web Server
R e p o s it o r y
C o n cu rren cy
User
C o n tProfile
ro l
Terminal
capabilities
P e r s is t e n c e
Call Contro/User Interaction
SSP
SCP
VGTW
PBX
SIP
Srv
• Validation by service scenarios done
– Enhanced and distibuted call center, Virtual Presence, ICW
• Parlay is not really an architecture, but a set of
interfaces
– the architecture to provide them can be P909 Ref. Architecture
Interworking 2000, Bergen
G. Gylterud, 03 October 2000
3Pty Interface
• 3rd party interface
Charging
Billing
Directory
S e c u r it y
Service
IVR/
TTS
TINA can be used for...
TINA Consumer
TINA Service Architecture
UAP
Subs
Mgmt
IA
PA
UA
3Pty
User
Profile
IN-TINA IWU
SSM
UAP
GSC
PA
GSS
IUAP
ConS RP/Parlay-like
P909 Call Control, User Interaction & Messaging API
IN
Consumer
•
•
•
•
SSP
VGW
NAS
IVR
TTS/ASR
Message
Store(s)
Access Session, Service Session support in TINA (component reuse)
Use P909 CC I/f in place of ConS - support for multiple networks
Adoption of TINA-IN IWU from TINA-C
3Pty interface Parlay based
Interworking 2000, Bergen
G. Gylterud, 03 October 2000
JAIN can be used for...
• Ideas are there...
Jain - Service Logic Execution Environment Jain - Service Creation Environment
Parlay JAIN
Java Call Control
MAP
Mobile
Generic APIs
on top of each
of these.
INAP
TCAP
ISUP
MGCP
PSTN
SIP
H.323
Internet
• JCC: abstraction of underlying protocols (similar to
JTAPI)
• ...but JAIN prototypes will appear after start of P909
implementation activities
• Eurescom became member of JAIN consortium
• P909 has kept track of JAIN activities
Interworking 2000, Bergen
G. Gylterud, 03 October 2000
Results of product survey
• Product survey report provides an overall picture on
many products related to IN-Internet (PIR4.1)
http://www.eurescom.de/~pub-deliverables/P900-series/P909/D1/Annex4/p909d1annex4.pdf
• Signalling gateways towards PSTN (SS7)
– operational gateways available from various vendors
• Telephony and conferencing services over the
Internet
– H.323, SIP
• PSTN-Internet gateways
– H.323 gateways available
– gateway control protocol proposed (MeGaCo/H.248)
• Distributed platform (DPE)
– CORBA, DCOM, Java RMI
Interworking 2000, Bergen
G. Gylterud, 03 October 2000
Conclusions
• P909 Reference Architecture enables unique services
over IN and Internet
• Component based (OO) architecture and unique APIs
allow for extension of functionality and adaptation to
emerging network components
• 3Pty interface facilitates access of 3Pty Service
Providers and (mass market) Consumers
• P909 Reference Architecture can be built based on
existing specifications and (pre-)products
facilitates deployment in operational network scenarios
Interworking 2000, Bergen
G. Gylterud, 03 October 2000