Lill Kristiansen

1
Implementing TINA IDEAS

• Lill Kristiansen
• Now IP and Multimedia Telephony, Ericsson
  AS96-97 TINA core-team member in the service
  stream

2
TINA2000, Paris, September 2000
A user centric architecture for multi media
telephony and how it supports TINA ideas
Lill Kristiansen Lill.Kristiansen_at_ericsson.no Eric
sson AS, Norway Product Unit IP Telephony
3
Outline of the talk

• TINA ideas we use
• Some features of the existing IPT2.0 system
• An example of a future hybrid service using
  both call and browser features
• The general architecture also for 3G

4
A TINA service picture (SA5.0 fig.7.2)
Might be compared with H.323 v1 (slow
start) Count roundtrips! ( hidden TCP
roundtrips)
5
TINA ideas we use (part 1)

• Co-operative solution for a competitive world
• SIP/H.323 for basic call in 3GPP/Tiphon
• XML, HTTP, CORBA etc for service control
• call/web/outlook integration (also on the move)
• virtual home environment (VHE)
• access to your own preferences when on the move

6
TINA ideas we use (part 2)

• Separation of users and terminals
• User mobility and terminal mobility sep.
• Ubiquitous access to services
• unlike TINA also from PSTN
• A business model supporting these separations
• some enhancements are made as well

7
TINA ideas we use (part 3)

• A layered architecture
• SIP/H.323 registrations different from e.g GPRS
  registrations
• Separation of sessions / layers
• access session (SIP/H.323 registration)
• service session (call setup call rel.
  services)
• communication session (media channels)

8
Outline of the talk

• TINA ideas we use
• Some features of the existing IPT2.0 system
• An example of a future hybrid service using
  both call and browser features
• The general architecture also for 3G

9
Evolution of IP Telephony to MultimediaPlayers,
market
Mobility/Wireless Integration
Next Generation Converged Networks
Integrated Services
Data/Voice Integration
/Multimedia
Low-cost telephony
Basic Voice
/Mobile
10
What is MMoIP / multimedia telephony

• It is VoIP and more! Multimedia!
• It is NOT everything
• not scheduled video broadcasting, pure email,
• It is instant personal communication,
• audio video call between 2 parties
• audio data (shared applic.)
• hybrid services
• call browsing or browsing call
• etc etc

11
It is realtime instant communication

• Choosing if/how/who you want to communicate with
• user preferences, several media options
• Quick call set-up times
• locating the other party
• reserving the needed resources
• counting roundtrips
• adding new media types on the fly etc.

12
Some features of the IPT2.0 system

• Supporting toll bypass
• i.e. PSTN as a short access
• basic call, no fancy user centric services
• Supporting also advanced users (user centric)
• multiple terminal registrations
• multiple access types GSM, PSTN, PC, PDA, 3G
• user specific profiles, personal call handling...
  

13
The IPT system exists today!

• For Toll-bypass traffic
• For advanced users
• corporate users
• intagration with GSMoverIP on the LAN
• same architecture! Already tackling mobility
• The architecture is future proof!
• Supporting H.323 today, SIPOSA tomorrow

14
Architecture, User-to-user call
Service Network
Home Site
Home Site
Service Agent
Service Agent
User-GK(S-CSCF)
User-GK(S-CSCF)
Access and Connectivity Network
Access Site
Access Site
Site-GK (P-CSCF)
Site-GK (P-CSCF)
Term. Agent
Term. Agent
Terminal
Terminal
PSTN GW
PSTN
PSTN GW
PSTN
15
GSM on the Net one user, several phones
From Ericsson Review No 04, 1998
http//www.ericsson.se/review/pdf/1998046.pdf
16
Virtual Home Environment (input to ETSI Tiphon)

• The user may log on from anywhere
• Visited GK control his own resource
• The visited GK contact home GK and routes the
  call (but not necessarily the media) via the home
  GK

I/f
Registration via visiting GK to home GK
Visited GK
17
A TINA service picture (SA5.0 fig.7.3)
Need access adaption and/or visiting entity!
Need access adaption and/or visiting entity!
Home service provider
Home service provider
PSTN
CATV
18
Outline of the talk

• TINA ideas we use
• Some features of the existing IPT2.0 system
• An example of a future hybrid service using
  both call and browser features
• The general architecture also for 3G

19
HTTP Based Service Control

• H.323 Annex K (in ver.4) (or similar ideas in
  SIP)
• Separate HTTP connection for service control
• Presentation level HTML, XML, Audio...
• Third party control
• A standard way to offer non-standard services
  (Ref. TINA slogan)

20
Non-Standardized Services??!!!

• Works without support in every node
• Allows Service Providers to differentiate
• Services can be made quicker
• Services can be made by non telephony experts

21
HTTP Based Service Control - details in H.323

• Service Provider sends a URL to client,
• e.g. in alerting
• Client retrieves content present
• User input goes directly over HTTP
• Provider receives input, translates to H.323/ SIP
  (basic call) actions.

22
Ex. Call Waiting Http service control
Terminal Browser
Terminal C
Terminal B
End-user C
Web-server
Im busy now, but you may 1. Wait - its
urgent, 2. Leave a message
Network
Notify B, its urgent
23
System overviewservice and call layers separated
Client
Service Provider
Service Control Plane
Network
Call Control Plane
Call ctr.H.323/(SIP)
Possiblly by using OSA interfaces
Standard interfaces between browser and plug-in
24
Example 1 Asynch. Call Completion at A-service
side
Web-server
A-Gatekeeper
Browser
Terminal A
Terminal B
Setup
Release Complete (busy)
Load(url)
Lill is busy now, but you may 1. Leave a
message 2. Be notified when shes available
Ill get back to you, when Lill becomes free
Starting to monitor on B hangs up e.g. via OSA
events
Release Complete
25
Countinued Asynchronous Call Completion
A-Gatekeeper
Browser
Terminal A
Terminal B
Web-server
Now B hangs up
Load(url)
Lill is available now. Call?
calltoLill
Call is active
26
Example 2 Asynch. Call Completion at
B-service side
B Client
A Client
B Service Provider
U-GK
U-GK
Call ctr.
Call ctr
Call ctr.
27
Tailored call control, competition

• B may offer different options to different
  A-users
• personalized services for the masses
• Bs service provider is independent of A-side,
  and of visited networks
• no additional service standards, quicker to
  introduce!
• This is due to the home-S-CSCF concept

28
Gimme more!

• Branding of services
• XML
• Adapt presentation to terminal capabilities
• Voice-rendering style sheet
• Not just for PC-phones
• Mobile WAP-HTTP gateway

29
Outline of the talk

• Short intro to VoIP / MMoIP
• TINA ideas we use
• Some features of the IPT2.0 system
• An example of a hybrid service using both call
  and browser features
• The general architecture also for 3G

30
Relations to 3GPP standards

• UMTS OSA Open Service Architecture
• VHE Virtual Home Environment
• Home-CSCF
• There is more in 3GPP then call related services

31
System topology - Next generation networks

• Today
• Separate Networks
• Separate Users
• Separate Services
• Tomorrow
• Separate Accesses
• Same Core network
• Same User on different accesses
• Same Services

Separate Services
Data/IP Networks
PLMN
PSTN/ISDN
CATV
Separate users
32
System topology - Next generation networks

• Today
• Separate Networks
• Separate Users
• Separate Services
• Tomorrow
• Separate Accesses
• Same Core network
• Same User on different accesses
• Same Services

Servers
Content
Content
Communication Control
Access Gateways
Access Gateways
Backbone Network
Access
Access
Access
Users
33

• Thank You!
• Lill.Kristiansen_at_ericsson.no