TINA as a technology enabling INInternet integration EURESCOM P909 overview

1
TINA as a technology enabling IN-Internet
integration EURESCOM P909 overview

• Carlo Alberto Licciardi
• CSELT
• carlo.licciardi_at_cselt.it
• http//www.eurescom.de

2
Outline

• Objectives of P909
• Project organisation
• Milestones
• Drivers
• Target services and requirements
• Technologies and protocols
• Reference architecture functionalities
• Experimental scenario (1 example)
• P909 TINA
• Conclusions

3
What is P909 about?
Enabling technologies for IN evolution and
In-Internet integration
4
Project structure

• 8 companies (Telecom Operators)
• France Telecom, Deutsche Telekom, Telecom
  Italia/CSELT, Telefonica ID, Telenor, KPN
  Research, Portugal Telecom, Telecom
  IrelendRemark in red - proposing companies
• Manpower 200 mm (130 mm in 1999 and 70 mm in
  2000)
• Duration 18 months (starting from January 99)
• 5 Tasks
• task 0 Project Management (CSELT)
• task 1 Dissemination of results (DT)
• task 2 Architecture for IN and Internet
  integration (FT)
• task 3 Design and Prototype components for the
  experimental platform/system (Telenor)
• task 4 Experiments investigating IN evolution
  and IN/Internet integration (KPN)

5
Main Milestones

• Documents/experiments
• June 99 D1 What an IN system should be
• final version is available
• December 99 D2 Architecture and scenarios for
  IN Internet convergence
• March 00 D3 Prototypes components for the
  experimental platform(s) and system(s)
• June 00 D4 Evaluation of IN/Internet
  integration experiments
• June 00 D5 Final guidelines for evolution of
  netwok Intelligence
• Workshops
• 1, 2 December 1999 A-DOT workshop
• January 99 ICIN 2000 conference (3 papers)

6
Why? .Market trends

• Success of internet
• Growth of IP trafic (UM, Web enabled CC,
  e-commerce)
• Internet telephony
• Increase in IN service usage/offer
• Growth of mobile telephony
• Evolution of terminals
• Efficient billing

7
Where to go?

• A new class of services
• Is it only "voice over IP vs. switched voice" or
  the emerging of multimedia services ?
• Which new services? from click2dial to
  complexintegrated VPN services
• Which requirements are posed by new services ?
• The shape of things to come Trends in the
  evolution of Network Intelligence
• Does IN fit with the IP transport ?
• Needed enhancements to current control platforms
• Distributed Architecture for Enhanced Control
• Distribution of intelligent functions
• The role of middleware based solutions
• Protocols, APIs, and network programmability

8
A Telco Perspective on NGN
Next Generation Networks (NGN) what for ?
Reduction of Total Cost of Ownership
New Services Offering
more attention should be paid to services!!!
A lot of work is going on, but ...
9
New Services ...
Simply a Phone-to-Phone Service ?
10
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 Messaging
• 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

11
Integrated Services at which extent?
Control
Click-to-Dial
Chat-and-Talk
Internet Call Waiting
Service Profile Management
Intelligent Internet Access
Advanced call center
Enhanced VPN Service
Unified Messaging
Virtual Presence
Virtual Second Line
Unified Billing for IN and Internet
Personal Information Services
Call over POTS/IP
Data
Transport
12
Virtual Presence some 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 looged on
• My Network secretary Call filtering depending
  on time of the day, CLI, caller. Predefined or
  customizable
• I can register from / on heterogeneous terminals
• Unified Support for synchronous (phone calls) and
  asynchronous (messages) communication

13
Virtual presence user view
14
The Evolution of Services imposes a Set of
Requirements

• A control communication based on IP
• within the Service Layer Elements
• between Call Control and Service Layers
• APIs instead of protocols
• object oriented instead of procedural
• Distributed Environments

• Interoperability and Openness
• Services are to be provided
• ... over heterogeneous networks
• through different Providers
• by means of different terminals

Network Intelligence for Converged Networks

• A granular control over transportcapabilities
  and equipment
• a new Call Model for converged networks ?
• mobility (of terminals and users)
• (end-to-end) control of QoS
• multi-party communication
• accountability of network resources

• Customer Centered Services
• focus on the integration of Customer Profiles
  within the different network(s)
• focus on Service profiling for customers
  requirements
• programmability and specialization of functions

15
Some key issues

• Standardized and stable network protocols to
  build on
• SIP, MeGaCoP or H.248 (SGCP, IPDC, MGCP), H323
• Unified support for network control interfaces
• Definition of a common call control for
  heterogeneous networks (that abstract from INAP,
  H.248/MegacoP, SIP, Parlay-cc?
• Is there any commercial product/prototype
  supporting such protocols/interfaces ?
• Service level interfaces
• Equivalent to IN SCP-SCP interfaces
• For distributed call management and service
  interactions
• For distributed access to databases (LDAP, LTAP)
• APIs for interactions with 3rd parties (Parlay,
  TINA RP)
• APIs to be used by 3rd party sw application (in
  the same domain)

16
Which protocols? Which systems?
17
Service Platform functionalities
Legend SCP Service Control Point SSP Service
Switch. Point VGW Vocal Gateway NAS Network
Access Server PBX Private Branch Exch.
3Pty Interface
Adaptors
Distributed platform
Private Networks
SCP
VGW
PBX
SSP
Internet
NAS
PSTN/IN
18
Key functionality

• Call control
• it provides an abstract API for call control on
  PSTN, IP and hybrid networks
• it is based on Parlay specification -CC
  interfaces (v1.1 - upgrade to 1.2 foreseen)
• it is a powerful tool for service designer in
  order to be independent from the underlying
  transport network.
• Cooperation with JAIN consortium for a common
  definition (JCCJava Call Control)
• Message control
• User profile
• SINGLE!!!! For Internet, IN and other services
• Easily customizable
• It interfaces with directory services via
  standard protocols (LDAP)
• Re-usable for as many services as possible
• Adaptors towards resources (VGW, SCP, )
• API have been specified and are based on emerging
  protocols (H.248/Megaco)

19
Call Control
instances of
instances of
service n
service n
instances of
instances of
service 1
service 1
call control
call control
events
interface
CC Parlay API
- operations
- information
status of the calls
call control function
Adaptation Layer
control protocols (INAP, Megaco, Jtapi)
PSTN
IP
VG
network elements
20
Call Control Interface

• capability to control heterogeneous legs in
  heterogeneous (PSTN, IP) networks
• capability to connect mixed legs
• capability to control calls started by the IN
  infrastructure (under the request of some network
  elements)
• capability to start and control calls (i.e.,
  third party call control capabilities).
• And the 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.

21
User Profile
22
Adaptors

• They offer standard APIs/interfaces to the upper
  layers regardeless the underlaying products
• Network resources
• PBX
• Vocal Gateway with prop. APIs
• Lucent VGTW, Dialogic boards
• SCPs
• SSPs
• SIP servers
• LDAP servers (for directory)
• Messaging systems

23
Experimental scenario VP
Directory server
User Profile
Internet
Config.
Internet
UA Avatar
Person.
UA Avatar
VP-CC
Enhanced VP-UA
Registr.
CC
Auth.
IP Invitation Handling --------- SIP gateway
VGTW adapter
IWU-SCP
SCP
SIP server
VGTW
PSTN
PSTN
Internet
Internet
API
24
and the external world...

• Monitoring of related standardisation bodies
  activities by project-members involved in
  respective standards bodies activities
• Currently JAIN, Parlay, TINA-IN-WG, IETF,
  IN-Forum, ITU-T SG 11 and 16, OMG Telecom DTF,
  ETSI NA6
• in future. Parlay, 3GIP, MSF, TIPHON
• Feedback to P909 and alignment of project work,
  if necessary
• Input to standardisation bodies, fora etc. by
  individual project member companies with
  reference to EURESCOM project work

25
TINA to P909

• Common cultural background
• project proposal comesfrom TINA-IN members
• modelling concept
• information model
• computational model
• use of a distributed architecture
• Reuse and extension of TINA defined
  components/conceps
• user profile
• session model
• extensive use of reference points and APIs
  -defined in IDL

26
P909 to TINA (TINA-IN)

• Applying TINA architectures and concepts to P909
  reference architecture
• Use of TINA components and interfaces to
  implement P909 network services and service
  scenarios
• Mapping Identified Functionality to TINA
• Identification of new components
• TINA and P909 Call Control (Parlay)
• TINA and IN-Interworking
• TINA and Messaging
• Looking at messaging, Virtual Presence and C2D
  scenarios
• P909 Parlay WG report

27
Legend PA - Provider Agent IA - Initial Agent UA
- User Agent SSM - Service Session Manager GSC -
Global Session Control GSS - Global Service
Segment CSM - Communication Session Ctrl TCSM -
Terminal CSM UAP - User Application SCP - Service
Control Point SSP - Service Switching Point
Retailer
TINA Consumer
Ret RP
IA
PA
TCSM
3Pty
Connectivity Provider /Consumer
SCP
GSC
SSM
GSS
API
Ret RP /Parlay-like (frw)
CSM
Ret
ConS RP/Parlay-like (serv)
API
Call Control
Msg Control
TINA GTW
SSP
Connectivity Provider
28
Conclusions

• Introducing Internet/Web functionality in IN
  systems allows to open up IN to information
  systems (protocol, application and terminals)
• enabling new scenarios for application Network
  Intelligence principles
• decreasing time-to-market of TLC services (it
  could be comparable to Web service timing)
• Needed functionality should be introduced with
  few investments by re-using network systems and
  adding information systems and a distributed
  environment