240 likes | 331 Vues
Explore the end-to-end quality of service (QoS) in distributed information systems at the QUTE’98 workshop, including present issues, trends, and possible solutions like CME and EURESCOM projects. Delve into QoS parameters, uncertainties, trends, classes, charging, and methodologies for managing QoS. Discover the CME Project's architecture, features, and QoS model layers, along with a proposed new EURESCOM project on QoS. Uncover the open issues, objectives, and stakeholders focusing on integrated QoS measurement, management, and charging.
E N D
End-to-End Quality of Service in Distributed Information Systems Marco Alfano Marco.Alfano@cselt.it QUTE’98 Workshop Heidelberg, 14-15 October 1998
Outline • QoS Present Issues • Qos Trends • Possible QoS Solutions: • The CME project • A possible new EURESCOM project on QoS • Conclusions
QoS Present Issues • Present technology makes implementation of QoS feasible • Main costs involved are not fixed costs (lines, devices) but recurring costs (signalling, routing, policy, billing, accounting, etc.) • QoS parameters should be minimised • it is complex specifying them, monitoring them, enforcing them, etc. • Still high uncertainty on QoS cost/benefit ratio
Edge Network Edge Network Backbone Network QoS Trends • Performance guarantees on the edge networks (e.g., RSVP) • Prioritisation of traffic on the backbone (e.g., IETF differentiated services)
QoS Trends (cont’d) • Services/applications characterised by a few QoS classes • QoS classes mapped to network-service classes (e.g., IETF differentiated services) • Different classes must entail different prices Charging can make QoS to become a reality!
Possible QoS Solutions • Cooperative Multimedia Environment (CME) Project (ICSI, Berkeley, 1996) • A potential new EURESCOM project on QoS: QoS methodologies and solutions within the service framework: Measuring, managing and charging QoS (September 1998)
CME Project: Motivations • World-wide collaboration: Universities, research institutes, companies • Videoconferences and shared applications (e.g., Mbone Tools) • Problems: • No common user interface • No integrated management • No QoS guarantees
CME Project: Main Features • A Cooperative Multimedia Environment (CME): • Common graphical user interface • Support of QoS requirements • Application sharing and audio/video communication • Integrated management of host and network resources
User User Connection Interface Manager Media Service 1 User Host COMMA QoS Mapper/ Service Host Media Service 2 Controller Manager COMMA Network . . Resource . User Monitor/Controller Media Service n Host COMMA CME Project: CME Architecture COMMA : Cooperative MultiMedia Application
User High or Low Quality Video Application Video Frame Rate Network Host % CPU Bandwidth CME Project: QoS Model • Users must be able to express QoS requirements in familiar terms • A three layers model
CME Project: QoS Model • User level • User expectations should be expressed in quantitative terms • Analysis on user expectations is highly subjective • A five-level scale can be used for quality rating • The scale is based on double stimulus methods
CME Project: QoS Model • User level • One global requirement, Quality, for each media (e.g., video quality) • Quality is a repository of more specific requirements (e.g., spatial and temporal vision quality) • User-Application Mapping • Tests must be executed to rate quality of video and audio sequences • Application-Resource Mapping • Only an estimation is possible
CME Project: QoS Mapping • User-Application Mapping Video (JPEG) Audio
CME Project: QoS Mapping • User-Application-Resource Mapping Video (JPEG) Audio
CME Project: CME Prototype • Connection Manager • Unix Sockets • Resource Monitoring • Iostat for CPU load • RTP for network bandwidth • Distributed Platform • Sun Solaris and TCP/IP • COMMA Database • Mini SQL • Media Services • MBone Tools (vic, vat, wb) • User Interface • Tcl/Tk
CME Project: CME Prototype • User Interface for connection mangement
CME Project: CME Prototype • User interface for session control
Open Issues • Better understanding of user requirements • QoS specification by the user in terms of QoS Classes? • Mapping of user requirements into application parameters and system resources • How network (and hosts) guarantee the QoS levels (classes)? • QoS charging
A possible new EURESCOM project on QoS • QoS methodologies and solutions within the service framework: Measuring, managing and charging QoS • The title should become: • QUASIMODO (QUAlity of ServIce MethODOlogies and solutions): Measuring, managing and charging QoS
User QoS Classes Application Measurements Application Resource Measurements Network Host Project Proposal: Objectives • QoS model definition • Different QoS Classes for different applications, users
Project Proposal: Objectives • Parameters correlation for some meaningful applications • Methodologies and tools for QoS measurement and management • Charging methodologies and policies for QoS charging • Experimental evaluation and validation of QoS solutions Integrated QoS measurement, management and charging
PPD Supporting Shareholders • CSELT (IT) • Deutsche Telekom AG (DT) • Telecom Ireland (TI) • Finnet Group (AF) • Portugal Telecom (PT) • MATAV Hungarian Telecom (HT) • British Telecom (BT)
Conclusions • QoS present issues • QoS trends • A Cooperative Multimedia Environment (CME) • QoS specifications by the user • A potential new EURESCOM project on QoS • A three layers QoS model • Integrated QoS measurement, management and charging
For Further Information • CME Project • Web Site: http://www.icsi.berkeley.edu/~alfano/cme/cme.html • Paper: Design and Implementation of a Cooperative Multimedia Environment with QoS Control, Computer Communications, Vol. 21, pp 350-361 • PP9212 (PPD) • QoS methodologies and solutions within the service framework: Measuring, managing and charging QoS