session viib in and computer telephony+81 492 78 7510 (fax) [email protected] 2tina’99 oahu,...

1

Session VIIb: IN and Computer Telephony

Chair: Frans Panken, Lucent Technologies

1 TINA’99 Oahu, Hawaii VIIb: IN and Computer Telephony E. Utsunomiya

TINA-like solutions for implementingcomputer telephony services

Eiji Utsunomiya† Hiroki Horiuchi Toshikane OdaKDD R&D Laboratories Inc.

2-1-15 Ohara

Kamifukuoka, Saitama 356, JAPAN

+81 492 78 7341 (voice)

+81 492 78 7510 (fax)

[email protected]


Outline

• Background– Telephony services on TINA

• Computer telephony services– Click-to-Dial service

• Designing Click-to-Dial service– Basic Framework– Service software configuration– Sample service scenarios

• Evaluations and considerations


What is target service of TINA ?

• TINA supports a wide range of telecom services;– especially, TINA is effective in multimedia related

services, such as• Multimedia conference services,• On-line shopping services,• Video-on-demand services, etc.

– Is TINA effective in simple telecom service such asordinary telephony services?

• Answer is ‘YES’, however,• TINA is too heavy-weight for the such simple services.

– We have studied how to apply TINA-like solutions forcontrol and management of ordinary telephony service.


Why telephony services ?

• Computer Telephony (CT) services appeared.– CT services are composed of:

• Simple telecommunication services,• Supplementary applications.

– CTI techniques have changed telephony services• From a simple conversation method,• Into an intelligent business tool.

• CTI techniques give solutions simpletelecommunication services for integrating them.


Outline






Examples of CT services

• Typical examples of CT services– Call Center Service (see next slide)

• Simpler Switching Board Service• On-line Catalogue Shopping Service• Reservation Service etc...


Examples of CT services (�� Center)

End-user(customer)

PSTN

(retrieving)

(call indication)

(call setup)

Operator ( representative)

PhoneController

(PBX)

Call CenterServer

DatabaseServer

(displaying)

(call incoming)


Examples of CT services

• Typical examples of CT services– Call Center Service (see next slide)

• Simpler Switching Board Service• On-line Catalogue Shopping Service• Reservation Service etc...

– Unified Messaging Service• Allows viewing and sending of every types of messages to

users.• Supports media transformation from one media to another.

– Click-to-Dial Service• Basic service in the CT field.• Target service of our study.


Why chose Click-to-Dial service ?

• Click-to-Dial service– Characterized by call setup triggering

• Direct type Click-to-Dial service– Phone call is initiated and established by calling party’s terminal

(such as the PC).

– Same setup process as in an ordinary phone service.

• Callback type Click-to-Dial service– Phone call is initiated by calling party, however, Call is established

by Click-to-Dial service provider.

– In this case,Calling party requests to initiate phone call on its own,but calling party invites phone call from Click-to-Dial serviceProvider.


Callback type Click-to-Dial Service

Caller(end-user)

IP network

PSTN/IP network

(call setup)

(call setup)

(call setup)

Callee(sales representative)

PhoneController

Click-to-DialService Server


Why chose Click-to-Dial service, again ?

• In Callback type Click-to-Dial service,– Service provider has responsibility of making phone call.– Gives service providers the ability to make up new

supplementary services.

• Potential of Callback type Click-to-Dial service– Security Potential

• Concealing phone number from calling party.

– Accounting and Billing Potential• Divided charging, I.e. rates of fifty-fifty, seventy-thirty.

– QoS Potential• Selecting suitable route or circuit using QoS information.


Outline






Basic Framework (Network Activities)

• Three types of Network Activities for CT services– Phone services

• PSTNs/IP networks

– Offer services• IP networks• WWW

– Supplement services• DPE• CT Applications

Supplementary Services(CT Applications)

Phone Services Offer Services

Interworking/Interacting

IP NetworkPSTN/IP Ne twork

DPE


Basic Framework (DPE)

DPE

CT Applications(Click-to-Dial

Service)DPE DPE

DPE DPE

Kernel Transport Network

PSTN/IP Network(Telephone Service)

IP Network

End-userA

End-userB

DatabaseApplications

Phone CallM anagement

Accessing Service(WWW Server)

Java-DPEInterworking


Configuration of Service Software

• Some concepts of TINA service architecture wereapplied.– Domain separation (User domain/Provider domain)– Session concepts– Information model– Computational model

• Click-to-Dial service software is composed ofmultiple functional components.– see next figure

1

Ap ril 15 , 1 999

pa ge 1 /22C orpora te R esearch C en te r

S oftware D epartm en tU A A/L /99 /

A lb an C o utu rie r

A lca tel C R C

A lb an .C o utu rie r@ a lca te l.fr

A T IN A un ified servicelayer fo r IN and V oIP

TIN A ’99

Ap ril 15 , 1 999



O utline

▼O verview▼From IN A P to R eta ile r R eferen ce P oint▼A new serv ice architec ture fo r the netw ork in te lligence▼Th e p la tfo rm▼C o nclus ion

2

Ap ril 15 , 1 999



M otivation s fo r T IN A m igration

▼IN draw b acks• lack o f inte rw ork in g stan d ard s• IN se rv ices d es ig n ed o n ly fo r IN sw itch es

▼U sing T IN A p rinc ip les• O O T• d is trib utio n• b u s in ess m o d e l• S erv ice a rch itectu re

▼Is th ere m o re than o nly prin c ip les? ..

PSTN

IN-TINA Adaptation Unit

TINA services

TINA i/f

INAP

S C F

Ap ril 15 , 1 999



C h oice o f th e T IN A in terface

▼IN A P cap ab ilities:• u ser au th entica tio n , se rv ices d isco very , access to co n ten t/u ser’s

p ro file , accep ta tio n o f a ca ll, pro v is io n o f ro u tin g an d ch arg in gin fo rm atio n s

▼C o un terparts in T IN A :• T IN A access sess io n m ech an ism s• n o n sp ec ified reso u rce co ntrol (g e t/se t/p lay /reco rd /sto p … )• in v ita tio n , 3 typ es :

– en d u ser-> S S M -> u ser ag en t->en d u ser• N F E P reso lu tio n

▼N eed o f a c lear in terface:• to h ave a c lea r an d flexib le S C F O O m o d e l• to reu se th e T IN A fram ew o rk as it is: a u nified se rv ice pla tfo rm , o r an

en h an ced co m m u n ica tio n p la tfo rm

3

Ap ril 15 , 1 999



Th e End U ser P roxy

▼ T IN A R et R P• + ad ap ta tio n s?

▼Th e End U ser P roxy (E U P)• rep resen ts o n e IN u ser in th e A U• s ta rts R et access and u sag e• p ro v id es th e in it ia tin g “end u ser” ap p lica tio n

– th e u ser in te rface A P I is IN A P

TIN A E U P TIN A re ta ile r

IA

U A

ss-U A P

P AS SP IN A P

R et-R PD S S 1

E ndus er A cc es s prov id er S e rvice prov id er

A U

U S M

Ap ril 15 , 1 999



▼O verv iew

▼From IN A P to R etaile r R eferenceP o int

▼A new serv ice architec ture fo r the netw ork in te lligence▼Th e p la tfo rm▼C o nclus ion

4

Ap ril 15 , 1 999



SSP IP AU IA namedUA

IDP

ETC

EUP

ARI

PCUI(name?)

PCUI(PIN?)

requestNamedAccesssetupAccessSession

setUserCtxt()

A ccess sess ion

Ap ril 15 , 1 999



IN A P m app in g to u sag e 1 /2

▼A "te lecom m u nicatio n serv ice" ca ll: serv ice sess ion• s ta rtin g th e sess io n• an inv ita tio n to the called p arty

– if re fu sed : p oss ibility o f a playA n no u n cem en t...• E stab lish m en t o f a s tream b in d in g

– th e vo te co u ld be u sed

▼N o tice: the serv ice sess ion can be to ta lly preserved• T IN A serv ice sess io n m o d el featu re set:

– M an d ato ry : B as icF S , M u ltip artyF S : in vita tio n s , P artic ip an tS B F S :S tream b in d in g s

– O p tio n n a l, n o t alw ays u sefu l: B as icE x tFS , M ultiP artIn d F S , V o ting F S ,C o n tro lS R F S , P artic ip an tS B In d F S

– in te rfaces : 3 fo r th e E U P , 3 fo r th e S ess io n M an ager• th e S A is kep t u n to uch ed

5

Ap ril 15 , 1 999



IN A P m app in g to u sag e 2 /2

▼C o m m un ication sess ion• T h e S S M in tan c iates a "n o rm a l" C S M : it h as an extra b ehav ior• Q u ery C ap ab ilities -> IN con tex t d e tec ted

• H ere , th e C S M ad o p ts th e IN b eh av io r– th e co s t o f a c lass ica l m ech an ism is h igh– IN is sim p le

• T h e IN co n n ec tio n : a T IN A te rm in a l flo w co n n ectio n– n o n eed o f Q o S– s im ple c o n n e ctio n : S F E P (T C ID ) w ith N F E P (E .1 6 4 )– A te rm in a l con n ec tio n is s im p le , an d th e term in a l is s till sp lit in to

th e p ho n e , th e S S P an d th e A U– very lig h t ch an ge in th e C S M to ado p t an a lte rna tive b eh av io r

Ap ril 15 , 1 999



Th e co m m un ication sess ion

ssUAP TCSM SSM CSM Called Party

setupFlowCommSession

addProviderPASBReq

joinPartyPaSBExe

return(sfep)

queryCapabilities

return: IN capabilities

return(capabilities)

queryCapabilities

2 selectCapabilities2 return(NFEP)

setupTFC(E.164number)

return(answer)

6

Ap ril 15 , 1 999



M appin g d iscussion

▼Th e class ical T IN A co m m un ication co uld h ave b eenfollow ed

• C S M T C S M d ia lo g u e w ith n o va lu ab le in fo rm atio n exch an g e for th e A U• C o n S u se• IN L N C an d T C o n im p lem en tin g a s im p le "co n n ec t"• T im e an d reso u rce con su m in g fo r on ly the g en eric C S M

▼Th e IN co nn ection is d one, bu t a T IN A N FC can b eneed ed

• T h e C S M th en ac ts n o rm ally (n eed o f a m ed ia g atew ay )

▼Th e w h ole serv ice arch itecture can b e fu lly used• T h e ch o ice is p rag m atic an d takes ad van tag e o f T IN A S A

Ap ril 15 , 1 999



EUP host layer

EUP

PA UAP TCSM

Th e EU P h ost layer

▼Th e EU P h ost layer im plem en ts:• th e C C I fo r se rv ice d eve lo p ers an d p rov id ers (n o t on ly o p era to r)• a m an ag em en t in te rface fo r th e n etw o rk o p era to r

▼A secure access to externa l im p lem enters• n o t a d irec t IN A P /C O R B A• n etw o rk to po lo g y h id d en• p rim itives /p aram ete rs a re sim p lified o r h id d en :

– h a lf o f th e IN A P prim itives h ave a s im p lif ied an d secu re co u nte rp artin C C I

▼A s im p le A P I• to b e lig h tw e igh t an d avo id o verh ead

w ith th e T IN A u sage o b jec ts• easy to be im p lem en ted

EUP

PA UAP TCSM

EUP

PA UAP TCSM

CCI

Ret

7

Ap ril 15 , 1 999



▼O verv iew▼From IN A P to R eta ile r R eferen ce P oint

▼A new serv ice arch itectu re fo r thenetw ork in te lligence

▼Th e p la tfo rm▼C o nclus ion

Ap ril 15 , 1 999



W eb brow s erJa va v irtu al

m ac hin e

Th e IN /in ternet ca ll

UA SSM

IN AUEUP

PA UAP

Ret R

P

TINA platform

UA SSM

Ret R

P

TINAappli

800PAUA

CSM CC adapter

M ed ia g atew ay

UAP

In tern et

▼IN to T IN A

8

Ap ril 15 , 1 999



Th e ph one to p hon e ca ll

▼W h at is IN ?• T h e u ser d eleg ates its ch o ices to th e n etw o rk in tellig en ce

– d u m b te rm in a l• n o p o ssib ilities to accep t or n ot a ca ll• n o p o ssib ilities to giv es its N F EP /ro u tab le n u m b ers

– d u m b n e tw o rk• n um b erin g p lan

• IN se rv ices a re fea tu res if th e b as ic T IN A sess io n• c lass ica l IN is p ro xy b ased

▼W h at is 3rd Party IN ?• T h e u ser h as n ow ad van ced te rm in a l

– W eb bro w ser p lu s (T IN A ) ap p le t– th e u ser is a h o t lin e se rv ice w ith exclu s ive N F E P kn o w ledg e

• T h e c lass ica l sub scrib er p ro xy is in ano th er d om ain

Ap ril 15 , 1 999



TIN A p la tform m echanism

▼Th e T IN A p la tform• th e ca ll tr ig g ers an E U P in stan tiatio n• au th en ticatio n p erfo rm ed b y th e E U P• th e E U P lau n ch es a T IN A access sess io n• T h e E U P lau n ch es th e se rv ice sess io n• E U P sen d s an in v ita tio n to th e S erv ice S ess io n M an ag er (S S M )• th e S S M re tr ieves th e ca lled p arty U ser A g en t (U A ) re fe rence an d

fo rw ards th e in v ita tio n• … N o w th e se rv ice b eg in s

▼Th e su bscrib er the U A forw ards the inv ita tion to th eca lled p arty PA

• th e U P T /follo w m e /... a re eas ily p erfo rm ed b y ssU A P /TC S M

9

Ap ril 15 , 1 999



W h ere is the serv ice?

▼In the EU P• h o w to d ea l w ith an IP in T IN A ?

– T echn o lo g y d epen d an t, u ser in terface• Is it ch ang ed fo r a n ew serv ice?

– If th e h ear an d fee l ch an g es• T h e A U sh o u ld b e im p le m e n ted w ith a s e t o f E U P s c la s s e s in o rd e r to

p ro v id e a s tab le E U P b ase• T IN A o p ens th e S C E

▼In the sub scriber p ro xy• im p lem en t th e fo llo w m e, ca ll sc reen in g , ca ll lo g /n o tif ica tio n b eh in d th e

s tan d ard i/f• N o t in th e co re o f th e p la tform , easy to ch an g e

▼In the ca lled p arty dom ain• an access sess io n has been lau n ch ed

Ap ril 15 , 1 999



▼O verv iew▼From IN A P to R eta ile r R eferen ce P oint▼A new serv ice architec ture fo r the netw ork in te lligence

▼The p latfo rm▼C o nclus ion

10

Ap ril 15 , 1 999



T-IN A P

▼TIN A IN A P is R et R P:• an sw ering in v ita tio ns• accep tin g s tream b in d in g• g iv ing N F E P

▼Th e T IN A p la tform : a m iddlew are foradvan ced te leph on y serv ices

• co n n ec ts th e A U to the serv ice layer• T IN A in tegra te th e IN (u ser h as n o t access ) w ith

in te rn e t se rv ices (u ser h as an access )

▼Th e serv ice layer• su b scrib er-o rien ted• o n to p o f n e tw o rk tech n o lo g y in d ep en d en t

in te rface• co u p led w ith V oIP reg is tra tio n

IN AUEUP

PA UAP

Ret R

PUA

SSM CSM

TCSM

UA

Ret R

P

subscriber

PA UAP TCSM

Mgnt

Ap ril 15 , 1 999



Th e T IN A serv ice p la tform

▼TIN A o ffers the enh anced co m m un ication services:• tech n o lo g y in d ep en d en ce• u n iversa l in v ita tio n /m essag in g p latfo rm• co n tro l o f d ifferen t tran sp o rt n etw o rks

▼Th e IN serv ices are on to p of th e p la tfo rm

▼TIN A m ust be exten ded for in form atio n serv ices• ex ten s io n o f th e T IN A serv ice sess io n m o d el fo r u nified m essag in g

serv ice : the m essag e bo x is a reso u rce o f th e serv ice• a lte rn a tive se rv ice sess io n m o d el fo r in form atio n se rvices

11

Ap ril 15 , 1 999



A layered n etw ork in te lligence

INAP1 stack MGC/GKINAP 2 stack

abstractionabstractionabstraction

call control I/F

AccessTINA usage Alternative usage

generic platformRet

AccessUsage Alternative usage

PASSM Informationservices

800 Internet call waiting

Equipmentand networkspecific

vocalpresentation

AA, federation

Universal INservices

Ret

AU

Ap ril 15 , 1 999



C o nclus ion

▼TIN A in IN :• fro m p rin cip les to en h ancem en ts o f T IN A (o r IN ) p la tfo rm

▼A new netw ork in te lligence can be defined

▼TIN A o ffers an sw ers for IN evo lution• D is trib u tion , O O T• B u s in ess m o d e l• S erv ice a rch itectu re fo r an y tech n o lo g y

– serv ice layerin g– IN to H .323 , IN to T IN A , ...

▼TIN A h e lps!

1

U w e H e rzo g, F E1 3d , T Z D arm s tad t T IN A´9 9 co nfe ren ce, 12 -15 A p ril,H a w aii

1

A T IN A S erv ice P la tfo rm in tegra tedw ith curren t In te lligen t N etw ork

system s

C arla C a pellm an nD eu tsche T elekom A G

T Z D a rm stad t

Jean-M arc P ageo tF rance T e lecomC N E T Lann ion

U w e H erzogD eu tsche T elekom A G

T Z D a rm stad t

O n beha lf o f S A TIN p ro ject-team


2

O utlook• Project objectives

• Scenario: Migration step, Platform, Interoperability

• SATIN Architecture, components, RP-details

• Service description and demo

• Satin Lab equipment

• Experiences and conclusions

2


3

O bjectives o f S A T IN• To define and implement a prototype service platform

at DT/FT sides, interworking with current IN systems

• Interoperability between DT and FT platforms

• Introduction of TINA concepts

• Reuse of existing IN infrastructure

• Taking into account existing results (e.g. EURESCOMproject P508)


4

M igra tion scenario

SSFCCF

SSP

SS7 network

SDFSCF

SCPSMP

SMF

INAP

6HUYLFH�3ODWIRUP

IIOP

$GDSWDWLRQ�8QLW

3


5

P la tfo rm In te roperab ility

SSP

AU

DPE

SSP

AU

DPE

Service Application Service Application

FT INAP T-INAP

Inter -ORB Communication

=====!"§DeutscheTelekom

TINA RP

TINA RP TINA RP


6

The S erv ice : U P T D e luxe• A UPT service with additional notification feature

• Registration by phone

• Full profile modification by web-/phone-based CSC

• Incoming Call

• Outgoing Call

• CallLector (email, SMS, Fax)

4


7

3671

CORBA/ IIOPTINA - DPE

SSP

RtR-RP

TINA - DPE

TINAService Platform

,QWHUQHW


AdaptationUnit

PMS

,1$3Web

basedCSC

Ret-RP

Ret-RP

Ret-RP


8

D eta ils on R tR -R P• Registration:• requestNamedAccess (userId=PUI, userProperties: PASSWORD=PIN) [NamedAccessIR, asId, asSecretId]• registerAtTerminal (asSecretId, termId {seq(name, value)} )

• Incoming Call: Setup RtR Access Session• requestNamedAccess (userId =“FT-Platform”, userProperties: PASSWORD =FTsPlf_psswd) [namedAccessIR of FT UA, asSecretId, asId]

• Incoming Call: Setup Access Session On User Behalf• requestAccessOnUserBehalf (asSecretId = RtRasSId, userId = PUI) on UA of FT-Retailer [NamedAccessIR, asId, asSecretId = UPTasSId ]

• listSubscribedServices (asSecretId = UPTasSId, desiredProperties {seq(name=ServiceName,value=“UPT”)} [services { seq( serviceId=182, ..., (registeredTerminal, value(NAPAddr)>),

(callLectorActivation, <value(boolean)>), (emailAddress, <value(string)>)

5


9

+LV�SHUVRQDO�QXPEHU�LV��

'LDOV��

837�'HOX[H�FXVWRPHU�ZDQWV�WR�UHJLVWHU

S erv iceprefix reg istra tion

P ersonal num ber

P IN


10

��

6


11

��

7KLV�SHUVRQ�WULHV�WR�FDOOWKH�837�'HOX[H�FXVWRPHUZLWK�KLV�SHUVRQDO�QXPEHU

'LDOV��

S erv ice pre fixP ersonal num ber

&DOO�WR�D�837�'HOX[H�FXVWRPHU

3671


12

��

7KH�FDOO�ZDV�VXFFHVVIXOO\�URXWHG�WR�WKH�FXUUHQW�WHUPLQDO�RI�WKH�837�'HOX[H�FXVWRPHU��

3671

7


13


SSP

PBX

RtR-RP

TINA - DPE


��

��


AdaptationUnitRet-RP

PMS

��

,1$3

837�VHUYLFH�UHTXHVW�IRU�)7

FXVWRPHU5HTXHVW�IRUXVHU�SURILOH


14

��

$�EXVLQHVV�SDUWQHU�WULHV�WR�FDOO�WKH�837�'HOX[H�FXVWRPHUZLWK�KLV�SHUVRQDO�QXPEHU

'LDOV��

S erv ice pre fixP ersonal num ber

&DOO�WR�D�837�'HOX[H�FXVWRPHU

1R�RQH·V�WKHUH��

3671

8


15

��

[email protected]

,QIR�

'DWH��WLPH&DOOLQJ�/LQH�,GHQWLW\

3671

,QWHUQHW


16


PBX

RtR-RP

TINA - DPE


,QWHUQHW

��

��


AdaptationUnitRet-RP

PMS

��

1R�$QVZHU�6HQGLQJ�(PDLO

WR��

SSP

,1$3

9


17

S A TIN Lab equ ipm ent• DT

– Orbix 2.3, C++

– HP 9000 Enterprise Server, PC Win NT4.0

• FT

– Visibroker 3.1 for Java (JDK 1.1)

– Orbix 2.3, C++ (reuse of TTT components)

– Solaris 2.6

• Platforms interconnected using TCP/IP over ISDN


18

E xperiences• TINA specs are large, sometimes difficult, missing guidelines for

practical work

• Reference Points– only spec. of Ret-RP was available– no templates (MSCs) for major use cases of Ret-RP

• Products– Interoperability problems between different ORBs– Missing source code

• Adaptation Unit– under investigation, Goal: no code modif. for new services– Service independent Call Control Interface (INAP, H.323 etc.)– Joint DT-FT response to TINA-IN-WG Rfp on TINA-IN-AU

10


19

C onclus ions• Difficult, but successful work

• IN can benefit from using TINA, proven by prototype

• TINA has potential for integrating networks and technologies,promoting opening of network interfaces

• TINA concepts still be seen as guidelines for the futuretelecommunication market

• TINA specs may partly lose their importance in being aconformity criteria

session viib in and computer telephony+81 492 78 7510 (fax) [email protected] 2tina’99 oahu,...

Documents