Title: IN 2000, Cape Town
1A Service Platform for integrated IN-Internet
services
P909 Enabling technologies for IN evolution and
IN-Internet integration
Carlo A. Licciardi, CSELT Telma Mota, Portugal
Telecom
- Uwe Herzog
- Eurescom
- herzog_at_eurescom.de
2Introduction
- Trends
- Increase in IN service usage/offer
- 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?
3Problem statement
- How can PSTN/IN and the Internet get connected?
- How can common services be realised for both IN
and the Internet? - How to give access to 3rd pty service providers?
P909 proposes integration at Service control
level by means of a Service Platform unique for
both IN and the Internet
4Service Platform Functionality
Legend SCP Service Control Point SSP Service
Switch. Point VGW Vocal Gateway NAS Network
Access Server PBX Private Branch Exch.
Service Layer
3Pty Interface
Adaptation Layer
Adaptors
Distributed platform
Resource Layer
Private Networks
SCP
SSP
VGW
PBX
PSTN/IN
Internet
NAS
5To prevent re-inventing the wheel...
- P909 was looking at and
investigating related standards, Architectures,
APIs, products ...
6Parlay can be used for...
- 3rd party interface
- to complicated for mass market end-user access
- extension to access user profile data or for
access from advanced terminals (PDA etc.) - starting point for platform interfaces
- Service i/f for Call Control, User interaction
- abstract interface for service developers
- Parlay is no architecture, but a set of
interfaces - the architecture to provide them can be P909 Ref.
Architecture - Validation by service scenarios done
- Enhanced and distibuted call center, VPN, Unified
Messaging, Virtual presence
7TINA can be used for...
- 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
8JAIN can be used for...
- Ideas are there...
- 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 will keep track of further JAIN activities
9Results of product survey
- Product survey report provides an overall picture
on many products related to IN-Internet
http//www.eurescom.de - Signalling gateways towards PSTN (SS7)
- operational gateways available from various
vendors - Telephony and conferencing services over the
Internet - H.323, SIP still interoperability problems
- PSTN-Internet gateways
- H.323 gateways available
- gateway control protocol under definition
(MeGaCo) - Distributed platform (DPE)
- CORBA, DCOM, Java RMI
10Overall Computational Model
11Key functionalities of adaptation level
- Adaptors towards resources for
- Call Control
- SCP (proprietary)
- SSP (SS7-INAP)
- Vocal Gateways (MeGaCo/H.248 above proprietary
APIs - Private Networks (JTAPI)
- SIP-Server (JSIP)
- Messaging Control
- Voicemail, Email, SMS (IMAP4/POP3, SMTP)
- User Interaction Control
- Interactive Voice Response (S.100)
- Text-to-speech (SAPI)
12Virtual Presence service
- Service Features
-
- I am reachable (if I want) on any terminal
regardless who is calling and from which terminal - any-to-any communication
- use of heterogeneous terminals (PC, mobile,
phone) - heterogeneous networks (IP, PSTN)
- I have a Single identifier (personal number or
alias) - it does not depend on the terminal/access network
where I am currently logged on - Call filtering depending on time of the day, CLI,
caller. Predefined or customizable My Network
Secretary - I can register from/on heterogeneous terminals
- Unified Support for synchronous (phone calls) and
asynchronous (messages) communication
13Virtual Presence User view
14VP Example Scenario
Directory
User
Internet
server
Service Platform
Profile
UA
UA
Enhanced
VP-CC
Avatar
Avatar
VP-UA
CC
IWU-SCP
SCP
Invitation Handling
VGTW
adapter
SIP
server
PSTN
VGTW
Alice
Internet
Bob
15Conclusions
- P909 Reference Architecture enables services on a
unique service platform over IN and Internet - Component based (OO) architecture and use of
non-proprietary APIs allow for extension of
functionality and adaptation to emerging network
components - Experimental scenarios are about to show the
feasibility of the defined architecture - P909 Reference Architecture can be built based on
existing specifications and (pre-)products - facilitates deployment in operational network
scenarios - Results are submitted to standardisation in ETSI
(SPAN 6) and IETF (Spirits)