HTTP Based Service Control

Document Sample
HTTP Based Service Control Powered By Docstoc
					       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
                         Lill.Kristiansen@ericsson.no
                                    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


                      Lill.Kristiansen@ericsson.no   3
  A TINA service picture (SA5.0 fig.7.2)




Might be compared with H.323 v1 (slow start)
Count roundtrips! (+ hidden TCP roundtrips)

                          Lill.Kristiansen@ericsson.no   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
                  Lill.Kristiansen@ericsson.no      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

                 Lill.Kristiansen@ericsson.no   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)

                 Lill.Kristiansen@ericsson.no    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


                      Lill.Kristiansen@ericsson.no   8
    Evolution of IP Telephony to Multimedia
    Players, market




                       Mobility/Wireless Integration
                                                               Next Generation
                                                               Converged Networks




                                                               Integrated Services
Data/Voice Integration /Multimedia


                                     Basic Voice                Low-cost telephony



                                                                       /Mobile

                                Lill.Kristiansen@ericsson.no                         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
                    Lill.Kristiansen@ericsson.no        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.

                   Lill.Kristiansen@ericsson.no   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...

                  Lill.Kristiansen@ericsson.no       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


                 Lill.Kristiansen@ericsson.no      13
  Architecture, “User-to-user call”
                                     Service Network
                     Home Site                                      Home Site

                     Service                                  Service
                      Agent                                    Agent



                   User-GK                                       User-GK
                   (S-CSCF)                                      (S-CSCF)




            Access                                                       Access
                       Site-GK                                 Site-GK
            Site                                                            Site
                      (P-CSCF)                                (P-CSCF)

           Term.                                                            Term.
Terminal                                                                            Terminal
           Agent                                                            Agent

 PSTN       PSTN                                                            PSTN     PSTN
             GW           Access and Connectivity Network                    GW


                               Lill.Kristiansen@ericsson.no                             14
GSM on the Net: one user, several phones




From Ericsson Review No 04, 1998 http://www.ericsson.se/review/pdf/1998046.pdf

                                  Lill.Kristiansen@ericsson.no                   15
Virtual Home Environment (input to ETSI Tiphon)
 •The user may log on from anywhere
                                                            Services
 •Visited GK control his own resource                                     User/
                                                                 I/f   subscriber
 •The visited GK contact home GK and                                    database
 routes the call (but not necessarily the
 media) via the home GK                                    Home GK




      Registration via visiting GK to home GK



                  Visited
                  GK


                            Lill.Kristiansen@ericsson.no                      16
A TINA service picture (SA5.0 fig.7.3)
       Need access adaption                                 Need access adaption
       and/or visiting entity!                              and/or visiting entity!



             Home service provider            Home service provider




PSTN

CATV




                             Lill.Kristiansen@ericsson.no                             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


                      Lill.Kristiansen@ericsson.no   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)



                Lill.Kristiansen@ericsson.no                               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




                  Lill.Kristiansen@ericsson.no   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.


                   Lill.Kristiansen@ericsson.no   21
  Ex. Call Waiting + Http service control
  End-user           Terminal Browser        Terminal C                    Terminal B   Web-server
     C




                                                  Setup
                                 Load(url)        Alerting (url)
                                                  callWaiting.invoke
                                                  GET url
                  Display                         Http 200 OK
                                                  (data)
I‟m busy now, but you
         may:                                                    Network
 1. Wait - it’s urgent,
2. Leave a message
                                                  GET url (I‟ll wait)

                                                                                        Notify B, its
                                                  Http 200 OK (data)                      urgent

                                                  Connect

                                        Lill.Kristiansen@ericsson.no                             22
 System overview:
 service and call layers separated
                      Client                             Service Provider

Service Control                                 HTTP
                   Web browser                           HTTP Server
Plane

                                               Network


Call Control                                             call Entity
                     Call Entity
Plane                                      Call ctr.     (End-Point or
                     (EndPoint)
                                          H.323/(SIP)    GK/CSCF)

        Possiblly by using OSA interfaces
        Standard interfaces between browser and plug-in
                       Lill.Kristiansen@ericsson.no                      23
       Example 1: Asynch. Call Completion
       at A-service side                                                                    B-
                                                                                        Gatekeeper
                      Browser       Terminal A             A-   Web-server                       Terminal B
                                                       Gatekeeper
                                           Setup
                                                               Setup
                                                                     Release Complete (busy)
                                         Alerting (url)
                            Load(url)
Lill is busy now, but you               GET url
may:
1. Leave a message                      Http 200 OK
2. Be notified when                     (data)
she’s available                         GET url (notify me)
                                        Http 200 OK
                                        (data)
         I‟ll get back to
         you, when Lill                                                  Starting to monitor on „B hangs
                                         Release Complete
         becomes free                                                    up‟ e.g. via OSA events




                                          Lill.Kristiansen@ericsson.no                                        24
      Countinued: Asynchronous Call Completion
                                                          A-
              Browser         Terminal A              Gatekeeper          Web-server        Terminal B
                                                                                         Now B hangs up
                                   ServiceControlIndication
                                            (url)
                    Load(url)      ServiceControlResponse
                                    GET url

                                    Http 200 OK (data)
Lill is available
   now. Call?


                    callto:Lill
                                           Setup                           Setup

                                           Alerting                           Alerting

                                           Connect                           Connect

                                           Call is active




                                           Lill.Kristiansen@ericsson.no                                   25
Example 2: Asynch. Call Completion ++
at B-service side
           (Access)                                         (Access)
A Client                                      B Service Provider          B Client

  Web                                         HTTP Server                       Web
                      HTTP                                         HTTP




                         U-GK                    U-GK                          call EP
 call EP     Call ctr.          Call ctr                           Call ctr.




                             Lill.Kristiansen@ericsson.no                             26
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



                    Lill.Kristiansen@ericsson.no      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



                 Lill.Kristiansen@ericsson.no     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


                      Lill.Kristiansen@ericsson.no   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


                Lill.Kristiansen@ericsson.no   30
System topology - Next generation networks

  Today
     • Separate Networks                                      Separate Services

     • Separate Users
     • Separate Services




                                                                           Data/IP Networks
                                                               PSTN/ISDN
                                                       PLMN
  Tomorrow




                                                                                              CATV
     • Separate Accesses
     • Same Core network
     • Same User on different
     accesses
     • Same Services                                          Separate users




                        Lill.Kristiansen@ericsson.no                                                 31
System topology - Next generation networks

  Today
     • Separate Networks                               Content
                                                                      Servers              Content
     • Separate Users
                                                            Communication        Control
     • Separate Services

                                                                      Backbone
  Tomorrow                                                             Network

     • Separate Accesses                                    Access                Access
                                                                        Access
     • Same Core network
     • Same User on different
     accesses
     • Same Services                                                   Users



                        Lill.Kristiansen@ericsson.no                                                 32
           Thank You!
Lill.Kristiansen@ericsson.no




        Lill.Kristiansen@ericsson.no   33

				
DOCUMENT INFO
Shared By:
Categories:
Stats:
views:7
posted:3/21/2011
language:English
pages:33