1 / 19

QoS-enabled Information Transport: Yet Another Operator Service

QoS-enabled Information Transport: Yet Another Operator Service. Antonio Cuevas ( cuevas@rus.uni-stuttgart.de ). Index…. Introduction, state of the art and step beyond. Benefits Impact in NGN architectures. Implications of a universal IP network. Any device Any access technology

yitro
Télécharger la présentation

QoS-enabled Information Transport: Yet Another Operator Service

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. QoS-enabled Information Transport: Yet Another Operator Service Antonio Cuevas (cuevas@rus.uni-stuttgart.de)

  2. Index… • Introduction, state of the art and step beyond. • Benefits • Impact in NGN architectures

  3. Implications of a universal IP network • Any device • Any access technology • Any Application • Plus business aspects, Service platforms

  4. Aspects to be revisited • This complex ecosystem makes that aspects already settled need to be revisited: QoS, managing the network service (i.e. transporting bits end-to-end) • Maxisat in Finland provides QoS for triple play scenarios • Deustche Telekom CEO statement • Managing the information transport service in a finer way and integrated into the overall service delivery  IMS

  5. In IMS the CSCF-PCRF-PERF interaction assures that the flows receive tailored QoS CSCF (SIP Proxy) PCRF SIP signaling CDF/CGF HSS 3G UMTS network PERF as a GGSN Voice, Video

  6. Step forward • In IMS information transport service is subsidiary to the applications, a parameter of the applications,  bounded flexibility • PROPOSAL • Consider “information transport” as a service on its own, with its AAA characteristics and compose it with the other services using service composition techniques • Conceptual difference, but that brings many benefits

  7. Index… • Introduction, state of the art and step beyond. • Benefits • Impact in NGN architectures

  8. As a service, “information transport” can be opened to many parties Network operator IMS’ CSCFs Communication endpoints Proxies Service providers Entities setting up the “information transport” session parameters QoS-enabled network infrastructure

  9. More open to different business models • Operator provides “information transport” • In semi-walled garden scenarios, it is aware of the “application level” services • Operator sees: 1 + 0..n services, n=0 in the Internet case • In IMS, “information transport” is a parameter of the applications, not a service on its own, so n=0 not supported • In our case, “information Tx” service has its own AAA and can be composed with other services

  10. Service composition techniques to deal with complex business scenarios • news streaming service with discounts from 9:00pm to 7:00am • depending on a specific • data transport service with discounts from 8:00pm to 6:00am. • By considering data transport as any other service and by employing existing service composition techniques, this conflictive situation can easily be handled at a service broker level (typically the network operator).

  11. Many aspects affect QoE: service composition techniques to control them User control and pricing QoS in the IP networks forming the Internet and in the routers connecting them Transcoders QoS of the applications, e.g. negotiating the optimal codecs Tailoring to the Terminal (e.g. screen size) and context (driving, working)

  12. Index… • Introduction, state of the art and step beyond. • Benefits • Impact in NGN architectures

  13. Notion of session for the “information transport service” • A session is an instance of a service • Flow control in many NGN QoS architectures • RFC about setting up and tearing down “network reservations” using RSVP • We can think that a flow is a session of the “information transport” service • with QoS parameters or not • All flows need to be controlled, scalability concerns

  14. Flow state is not kept end-to-end… bundling these flows must be done DiffServ CN No access control, No session No need of flow-user association Bandwidth Broker IntServ like AN IntServ like AN, Access control, Sessions

  15. QoS-enabeld data transport system Bandwidth Broker COPS Decision outsourcing & configuration Transport session setup Transport session setup RSVP RSVP Router Router

  16. Operator’s AAA System User & Packet correspondance Service Logic entity Reserves network ressources tailored to applications QoS-enabled transport System Network and packets control Deals with packets parameters Divide and conquer technique

  17. Details about the AAA System function • Diameter NAS Application used to gain access to the network • Using e.g. IPSec user-packets correspondance is waranteed • IDEA • Divide “gain access to the network” and “information transport service” • Operator’s AAA System specialised in the first, network infraestructure in the second • Bundling must be provided

  18. Sessions: Network Access (NA), Transport (T) and Application (A) Transport System AAA System AAA System Transport System Bundling Sessions: NA and T Bundling Sessions: T and A T4 T3 NA1 NA2 T1 T2 A2 User A User B A1

  19. Thanks for your attentionQuestions?

More Related