Eurescom P909 View on IN

1
Eurescom P909 View onIN IP Interworking

• Paulo Chainho
• Portugal Telecom
• paulo.g.chainho_at_telecom.pt

2
Outline
? P909 Introduction

• ? P909 Introduction

? ? ? P909 Requirements
?IN - IP Interworking how to deal with IP
Telephony protocols proliferation?
? P909 Framework
? P909 Experimental scenarios
?Conclusions
3
P909 Introduction What is P909 about?
Call control Message control APIs APIs to
control resources APIs to open up IN to third
parties application
Service scenarios Requirements Architecture
Enabling technologies for IN evolution and
In-Internet integration
Selection/evaluation of products Definition of
experiments and testing criteria Perform and
evaluate experiments
4
P909 Introduction Project structure

• ? 8 companies (Telecom Operators)
• France Telecom, Deutsche Telekom, Telecom
  Italia/CSELT, Telefonica ID, Telenor, KPN
  Research, Portugal Telecom, Telecom Irelend

? Manpower 200 mm (130 mm in 1999 and 70 mm in
2000)
?Duration 21 months (starting from January 99)
5
P909 Introduction A Telco Perspective on NGN
New Generation Networks (NGN) what for ?
more attention should be paid to services!!!
A lot of work is going on, but ...
Reduction of Total Cost of Ownership
New Services Offering
6
Outline
? P909 Introduction
? ? ? P909 Requirements
?IN - IP Interworking how to deal with IP
Telephony protocols proliferation?
? P909 Framework
? P909 Experimental scenarios
?Conclusions
7
P909 Requirements New Services ...
Simply a Phone-to-Phone Service ?
8
P909 Requirements Target services

• Click-to-Dial
• Chat-and-Talk
• Internet Call Waiting Virtual Second Line
• Intelligent Internet Access
• Service Profile Management from the Internet
• Unified Billing between IN and Internet
• Unified Communication
• E-commerce Service
• Virtual Presence Service
• Enhanced Virtual Private Network Service
• Distributed and Enhanced Call Center
• Advanced Community Service
• Personal Information Services
• Advanced Agenda Service

9
P909 Requirements Some 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) that does not depend on the
  terminal/access network where I am currently
  logged on

• My Network secretary Call filtering depending
  on time of the day, CLI, caller. Predefined or
  customizable.

• Unified Support for synchronous (phone calls)
  and asynchronous (messages) communication.

• Cross Communication features, e.g.
• - to call the message sender directly from the
  message (by mouse click)
• - to answer a call by playing a message sent
  on-the-fly.

10
P909 Requirements Unified Internet-Telco
services provision

• defining an architecture that from current IN
  evolves towards an open platform
• strongly based on middleware solutions
• supporting high levels of programmability and
  flexible

• key factors for the construction of the
  middleware platform are
• - the increased terminal intelligence
• - the distributed intelligence architecture
• - the software architecture (e.g., adopting TINA
  principles).

The middleware must fully exploit the new
terminal capabilities and enable interactions
between public and private equipment
11
P909 Requirements Overall requirements

• Scalable(possible growth in PSTN/IN services
  provided via internet from 3rd party providers)
• Flexible(to cope with the ever changing needs
  for services)
• Reliable(e.g. call control services should be
  available anytime for services running in 3rd
  party domain)
• Secured (e.g.use of firewalls towards internet
  and internal ressources)
• Open to 3rd party service provisinongDistribution
  of service logic between IN and InternetData
  sharing between IN and InternetSecurity
  (firewalls towards Internet and internal PNO
  domain)Call control functionality3rd pty
  providers should be given access to IN Call
  Control internet and internal resources

12
Outline
? P909 Introduction
? ? ? P909 Requirements
?IN - IP Interworking how to deal with IP
Telephony protocols proliferation?
? P909 Framework
? P909 Experimental scenarios
?Conclusions
13
IN-IP Interworking Which protocols? Which
systems?
14
IN-IP Interworking Protocol Interworking?
Next Year
In 2/3Years
what about Applications?
Q.931
H.323
INAP CS3
We Live in a Plural World, but...
Today
INAP CS1
MeGaCo/H.248
Application Change for Every new protocol
interworking?
INAP CS2
SIP
ISUP
SPIRITS
INAP CS1
15
Keep Your Application Away from Protocols
IN-IP Interworking API - Protocol Interworking?
One Application Interface
Q.931
INAP
H.323
ISUP
SIP
MEGACO
16
IN-IP Interworking API Standardisation?(1)
Which API?
JAIN
Parlay
ECTF APIs
IN Forum
TINA Reference Points
17
IN-IP Interworking API Standardisation?(2)
Standardisation should be focused on open APIs
and APIs mappings to protocols
Resource Control
API
Resource Adapters
Q.931Terminal
SCP
H.323GK
ISUPSW
S100IVR
SIPServer
MGC
Keep Your Application Away from Low Level APIs
Resources
18
IN-IP Interworking API Standardisation? (3)
No Application Change
API
API
SpiritsServer
Q.931Terminal
SCP
H.323GK
ISUPSW
S100IVR
SIPServer
MGC
New Protocol or New API?
Do Protocol and API plug-in!!
19
Outline
? P909 Introduction
? ? ? P909 Requirements
?IN - IP Interworking how to deal with IP
Telephony protocols proliferation?
? P909 Framework
? P909 Experimental scenarios
?Conclusions
20
P909 Framework Overview
External Domain
Distributed Platform
Third Party Interface
Directory
Billing
Authentication
User Profile
Logging
Management
SCP
H.323GK
VGW
IVR/TTS/ASR
SIPServer
WebServer
21
P909 Framework Call Control (1)
The Call Control provides an abstract API for
call control on PSTN, IP and hybrid networks.
?It is based on Parlay specification -CC
interfaces.
? It is a powerful tool for service designer in
order to be independent from the underlying
transport network.
22
P909 Framework Call Control (2)
23
P909 Framework Call Control (3)
?capability to control heterogeneous legs in
heterogeneous (PSTN, IP) networks
?capability to start and control calls (i.e.,
third party call control capabilities).
?capability to control calls started by the IN
infrastructure (under the request of some network
elements)
?capability to connect mixed legs
?emission of events to notify the activation of a
new call that requires to be controlled. These
events should be processed by the notification
handler.
24
P909 Framework Messaging Control
?The Messaging Control provides a unique
interface for heterogeneous messaging resources,
such as Voicemail servers, Email servers, GSM/SMS
Gateways, etc.
? It provides unified management functionalities
over different types of messages hosted in
distributed Message Stores.
?It provides unified message composition
functionalities and transfer functionalities to
external messaging systems.
? It forwards new Incoming Message Events toward
the Application.
25
P909 Framework User Profile (1)
?The User Profile is a SINGLE component For
Internet, IN and other services, containing
?Personal Data (e.g. First Name and Last Name).
?Logical Identifiers (e.g. Logical Name, Personal
Number, Email Address).
?Authentication Data (e.g. Login/Password,
Personal Number/PIN, Voiceprint).
? Service Independent Preferences (e.g. Preferred
Language, Billing Info, User Model/Preferences,
and Payment Services).
?The User Profile is easily customizable and it
interfaces with directory services via standard
protocols (LDAP)
26
P909 Framework User Profile (2)
27
P909 Framework User Profile (3)
28
P909 Framework Areas/technologies
29
Outline
? P909 Introduction
? ? ? P909 Requirements
?IN - IP Interworking how to deal with IP
Telephony protocols proliferation?
? P909 Framework
? P909 Experimental scenarios
?Conclusions
30
Experimental scenario Virtual Presence
31
Experimental scenario ICW
32
Experimental scenario Unified Communication
33
Outline
? P909 Introduction
? ? ? P909 Requirements
?IN - IP Interworking how to deal with IP
Telephony protocols proliferation?
? P909 Framework
? P909 Experimental scenarios
?Conclusions
34
Conclusions (1)

• IN-IP Interworking will bring many advantages to
  Telcos business

? enabling new scenarios for application Network
Intelligence principles
? decreasing time-to-market of TLC services (it
could be comparable to Web service timing)
? promoting CSN traffic
? enabling new functionalities introduction with
few investments by re-using network systems,
information systems and generic distributed
components
The middleware must enable the co-operation
between network and edge intelligence
35
Conclusions(2)
But we need standards for IN and IP interworking
?? ? New IP Telephony Protocols proliferation
makes Standardisation for IP and CSN Protocol
Interworking, a hard task.
?? ? Applications should be supported on
high-level open APIs that are independent from
the Network protocols.
?? ? New Network protocols should be introduced
by a plug-in like mechanism
IN-IP interworking standardization should be
focused on high-level and open APIs
36
More Information About P909
http//www.eurescom.de/Public/Projects/p900-serie
s/p909/p909.htm