simula research laboratory lokaliteter & forskning simula.no
DESCRIPTION
Simula Research Laboratory Lokaliteter & Forskning www.simula.no. Hovedfagstudenter i Simula-senteret. Universitetet i Oslo. Simula Research Laboratory. Scientific Computing. Software Engineering. Institutt for informatikk. Networks and Distributed Systems. Software engineering. - PowerPoint PPT PresentationTRANSCRIPT
Simula Research Laboratory
Lokaliteter & Forskning
www.simula.no
2
Scientific
Computing
Software
Engineering
Networks andDistributed
Systems
Institutt for
informatikk
Universitetet i Oslo
Simula Research Laboratory
Hovedfagstudenter i
Simula-senteret
3
Networks andDistributed
Systems
Software
engineering
Scientific
computing
PhD-/post.doc-programs
Collaboration with industry!
Simula Research Laboratory
Software forcomputing and visualization
Computing in
medicine
Numerical
methods
OO analysis and
design
Planning, estimation
and risk analysis
Product quality and
development processes
QOS in adaptive
middleware
Network
QoS
Quality of service
management
4
UiO(25%), NTNU(25%),
UiB(15%), UiT(15%),
NR(10%), SINTEF(10%)
Simula Research Laboratory
Scientific
Computing
Software
Engineering
Networks andDistributed
Systems
BoardScientific
Advisory Board
5
Parkeringsbygg
Telenor
Utenlands-
terminalen
Terminalbygget
Simula Research Laboratory
(4 etg. nord/vest i terminalbygget)
Simula Research Laboratory
Department of Networks and Distributed
Systems
nd.simula.no
7
Research area of ND department:
• Quality of Service management for future distributed applications and services
• What is QoS?– QoS for distributed applications and services refers to their extra-
functional properties, such as the provided response time, bandwidth, privacy, safety, accuracy, media-quality (for continuous media).
• What is QoS management?– The planned allocation and scheduling of network and end-system
resources and software algorithms to meet the QoS needs of applications.
– Static QoS management
– Dynamic QoS management
8
Why QoS?• Increasing demand for quality of service guarantees in networking
and distributed applications– Telephony
– TV- and radio like applications
– Video-conferencing
– Distance education
– Surveillance & control systems (real time systems)
– Cooperative work over distance
– Interactive large scale simulations (grid computing)
– Telemedicine
• Convergence requires QoS
• Lack of QoS support in current Internet and de facto component-based software development standards (e.g. EJB, .NET)
9
Why are we focusing on QoS?
1
23
45
6
Network node resources- Buffer space- CPU scheduling
Network link resources:- Bandwidth- Error rate- Latency
End-system resources:- Buffer space- CPU scheduling - Disk I/O
End-system resources:- Buffer space- CPU scheduling - Screen resolution
• QoS is a cross-cutting concern through network layers, end-system (middleware) services, and applications.• Our research experience in networking technologies, middleware, and multimedia systems helps in understanding cross-cutting integration issues and to propose and evaluate relevant QoS management technologies.
10
QoS research challenges• QoS modeling and specification - changes our models
of computing
• Disentangling functional and QoS concerns - aspect oriented programming
• Mapping problem: how does subsystem QoS determine system QoS?
• Supporting end-to-end QoS guarantees over heterogeneous networks
• Market-driven QoS negotiation protocols
• Software development tools and methods
11
Research Goal of ND department• Become an internationally recognised contributor of
solutions for management of network and end-system resources to meet the Quality of Service (QoS) needs of distributed applications.
• Become internationally leading in selected areas of– QoS for networks: End-to-end support for QoS over
heterogeneous network technologies
– QoS for distributed application software: Support for management of real time QoS in component based software development technologies.
12
Two initial projects
• VINE: Vertical and horizontal interoperation of network quality of service mechanisms.
• QuA: Component architecture support for dynamic management of real time QoS.
13
• Motivation– Component architectures make it easier for developers to build reliable
distributed applications from reusable software components.
– The current de facto standards, EJB 2.0 and .NET, and standards like CCM, do not support applications with real-time constraints or other QoS requirements.
• Goal – investigate how to develop complex real-time applications on a component
architecture platform
– learn through experimentation how dynamic QoS management and adaptation can be supported in general-purpose component architectures
QUA
14
• Motivation– QoS mechanisms are developed separately at the IP level and at
the layer two network technologies, and general solutions to integration of these two fields is sparse. Even though descriptions of mappings, and of QoS architectures exist, thorough testing of the performance of the integrated heterogeneous systems are mostly absent.
• Goal– to contribute to the realization of end to end network Quality of
Service support by devicing solutions for integration of the different approaches to Quality of Service (QoS) that exist.
VINE
15
Spørsmål?