Transcript HTTP Based Service Control

Implementing TINA IDEAS
Lill Kristiansen
Now: IP and Multimedia Telephony, Ericsson AS
96-97 : TINA core-team member in the service stream
TINA2000, Paris, September 2000
A ‘user centric’ architecture for multi media telephony
and how it supports TINA ideas
Lill Kristiansen
[email protected]
Ericsson AS, Norway
Product Unit IP Telephony
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
[email protected]
3
A TINA service picture (SA5.0 fig.7.2)
Might be compared with H.323 v1 (slow start)
Count roundtrips! (+ hidden TCP roundtrips)
[email protected]
4
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
[email protected]
5
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
[email protected]
6
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)
[email protected]
7
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
[email protected]
8
Evolution of IP Telephony to Multimedia
Players, market
Mobility/Wireless Integration
Next Generation
Converged Networks
Integrated Services
Data/Voice Integration /Multimedia
Low-cost telephony
Basic Voice
98
99
´00 ´01 ´02 ´03 ´04 ´05 ´06 ´07 ´08
First Wave/NGT
Second Wave/Incumbent
[email protected]
Megaops /Mobile
9
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
[email protected]
10
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.
[email protected]
11
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...
[email protected]
12
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, SIP+OSA tomorrow
[email protected]
13
Architecture, “User-to-user call”
Service Network
Home Site
Service
Agent
Service
Agent
User-GK
(S-CSCF)
Access
Site
Home Site
User-GK
(S-CSCF)
Site-GK
(P-CSCF)
Site-GK
(P-CSCF)
Access
Site
Terminal
Term.
Agent
Term.
Agent
Terminal
PSTN
PSTN
GW
PSTN
GW
PSTN
Access and Connectivity Network
[email protected]
14
GSM on the Net: one user, several phones
From Ericsson Review No 04, 1998 http://www.ericsson.se/review/pdf/1998046.pdf
[email protected]
15
Virtual Home Environment (input to ETSI Tiphon)
•The user may log on from anywhere
Services
•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
User/
subscriber
database
Home GK
Registration via visiting GK to home GK
Visited
GK
[email protected]
16
A TINA service picture (SA5.0 fig.7.3)
Need access adaption
and/or visiting entity!
Home service provider
Need access adaption
and/or visiting entity!
Home service provider
PSTN
CATV
[email protected]
17
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
[email protected]
18
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)
[email protected]
19
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
[email protected]
20
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.
[email protected]
21
Ex. Call Waiting + Http service control
End-user
C
Terminal Browser
Terminal C
Terminal B
Web-server
Setup
Load(url)
Alerting (url)
callWaiting.invoke
GET url
Display
I’m busy now, but you
may:
1. Wait - it’s urgent,
2. Leave a message
Http 200 OK
(data)
Network
GET url (I’ll wait)
Http 200 OK (data)
Notify B, its
urgent
Connect
[email protected]
22
System overview:
service and call layers separated
Client
Service Control
Plane
Web browser
Service Provider
HTTP
HTTP Server
Network
Call Control
Plane
Call Entity
(EndPoint)
Call ctr.
H.323/(SIP)
call Entity
(End-Point or
GK/CSCF)
Possiblly by using OSA interfaces
Standard interfaces between browser and plug-in
[email protected]
23
Example 1: Asynch. Call Completion
at A-service side
Browser
Terminal A
AWeb-server
Gatekeeper
Setup
BGatekeeper
Terminal B
Setup
Release Complete (busy)
Alerting (url)
Load(url)
Lill is busy now, but you
may:
1. Leave a message
2. Be notified when
she’s available
I’ll get back to
you, when Lill
becomes free
GET url
Http 200 OK
(data)
GET url (notify me)
Http 200 OK
(data)
Release Complete
[email protected]
Starting to monitor on ‘B hangs
up’ e.g. via OSA events
24
Countinued: Asynchronous Call Completion
Browser
AGatekeeper
Terminal A
Load(url)
Web-server
ServiceControlIndication
(url)
ServiceControlResponse
Terminal B
Now B hangs up
GET url
Http 200 OK (data)
Lill is available
now. Call?
callto:Lill
Setup
Setup
Alerting
Alerting
Connect
Connect
Call is active
[email protected]
25
Example 2: Asynch. Call Completion ++
at B-service side
(Access)
(Access)
A Client
Web
call EP
B Client
B Service Provider
HTTP Server
HTTP
Call ctr.
U-GK
Call ctr
U-GK
[email protected]
HTTP
Call ctr.
Web
call EP
26
Tailored call control, competition
– B may offer different options to different Ausers
• personalized services for the masses
– B’s service provider is independent of Aside, and of visited networks
• no additional service standards, quicker to
introduce!
• This is due to the home-S-CSCF concept
[email protected]
27
Gimme more!
• Branding of services
• XML
– Adapt presentation to terminal capabilities
– Voice-rendering style sheet
• Not just for PC-phones
– Mobile: WAP-HTTP gateway
[email protected]
28
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
[email protected]
29
Relations to 3GPP standards
• UMTS OSA:
Open Service Architecture
• VHE: Virtual Home Environment
• Home-CSCF
• There is more in 3GPP then call related
services
[email protected]
30
System topology - Next generation networks
Today
• Separate Networks
• Separate Users
• Separate Services
• Separate Accesses
• Same Core network
• Same User on different
accesses
• Same Services
[email protected]
CATV
Data/IP Networks
Tomorrow
PSTN/ISDN
PLMN
Separate Services
Separate users
31
System topology - Next generation networks
Today
• Separate Networks
• Separate Users
• Separate Services
Content
Servers
Communication
Content
Control
Backbone
Network
Tomorrow
• Separate Accesses
• Same Core network
• Same User on different
accesses
• Same Services
[email protected]
Access
Access
Access
Users
32
Thank You!
[email protected]
[email protected]
33