Lill Kristiansen Now:IP and Multimedia Telephony, Ericsson AS :TINA core-team member in the service stream Implementing TINA IDEAS

Lill Kristiansen Ericsson AS, Norway Product Unit IP Telephony A ‘user centric’ architecture for multi media telephony and how it supports TINA ideas TINA2000, Paris, September 2000

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 Multimedia Players, market Low-cost telephony Integrated Services Next Generation Converged Networks Basic Voice Data/Voice Integration Mobility/Wireless Integration /Multimedia /Mobile

10 What is MMoIP / multimedia telephony It is VoIP and more! Multimedia! –It is NOT everything not: scheduled video broadcasting, pure , 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, SIP+OSA tomorrow

14 Home Site Access Site Access Site Architecture, “User-to-user call” Access and Connectivity Network Service Network PSTN GW PSTN Term. Agent Terminal Term. Agent PSTN GW PSTN Service Agent Home Site Service Agent User-GK (S-CSCF) Terminal User-GK (S-CSCF) Site-GK (P-CSCF) Site-GK (P-CSCF)

15 GSM on the Net: one user, several phones From Ericsson Review No 04,

16 Virtual Home Environment (input to ETSI Tiphon) Registration via visiting GK to home GK Home GK Services User/ subscriber database Visited GK 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

17 A TINA service picture (SA5.0 fig.7.3) Home service provider Need access adaption and/or visiting entity! PSTN CATV Need access adaption and/or visiting entity!

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 CTerminal B Setup End-user C GET url (I’ll wait) Connect Web-server Http 200 OK (data) Terminal Browser Alerting (url) callWaiting.invoke Load(url) I’m busy now, but you may: 1. Wait - it’s urgent, 2. Leave a message Notify B, its urgent Http 200 OK (data) Display GET url Network

23 System overview: service and call layers separated HTTP Call ctr. H.323/(SIP) Web browserCall Entity (EndPoint) Client HTTP Server call Entity (End-Point or GK/CSCF) Service Provider Service Control Plane Call Control Plane Possiblly by using OSA interfaces Standard interfaces between browser and plug-in Network

24 Example 1: Asynch. Call Completion at A-service side Terminal ATerminal B Web-server Browser Release Complete (busy) 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 Load(url) Http 200 OK (data) GET url Setup Alerting (url) GET url (notify me) Http 200 OK (data) Release Complete A- Gatekeeper B- Gatekeeper Setup Starting to monitor on ‘B hangs up’ e.g. via OSA events

25 Countinued: Asynchronous Call Completion Terminal ATerminal B ServiceControlResponse Web-server Browser Now B hangs up Lill is available now. Call? Load(url) Http 200 OK (data) GET url A- Gatekeeper ServiceControlIndication (url) callto:Lill Setup Alerting Connect Call is active

26 Example 2: Asynch. Call Completion ++ at B-service side HTTP Call ctr. Webcall EP A Client HTTP Server B Service Provider Webcall EP B Client U-GK Call ctr Call ctr. HTTP (Access) U-GK

27 Tailored call control, competition –B may offer different options to different A- users personalized services for the masses –B’s 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 Data/IP Networks PLMN PSTN/ISDN CATV Separate Services 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 Users Backbone Network Access Communication Control Content Access

33 Thank You!