QuO’s Runtime Support for Quality of Service in Distributed Objects

Vanegas, Rodrigo; Zinky, J.; Loyall, Joseph; Karr, David A.; Schantz, Richard; Bakken, David E.

doi:10.1007/978-1-4471-1283-9_13

Cited by 97 publications

(64 citation statements)

References 7 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…As QML, it is focused on the application layer. -QDL (Quality Description Language) has been proposed as a part of the QuO (Quality Objects) framework [5] that supports QoS on the CORBA object layer. With QDL, it is possible to specify QoS requirements on application layer and on resource layer, and to define QoS scaling.…”

Section: Related Workmentioning

confidence: 99%

Formalization of Network Quality-of-Service Requirements

Webel

Gotzhein

2007

Lecture Notes in Computer Science

View full text Add to dashboard Cite

Abstract. The provision of network Quality-of-Service (network QoS) is a major challenge in the development of future communication systems. Before designing and implementing these systems, the network QoS requirements are to be specified. Existing approaches to the specification of network QoS requirements are mainly focused on specific domains or individual system layers. In this paper, we present a holistic, comprehensive formalization of network QoS requirements, across layers. QoS requirements are specified on each layer by defining QoS domain, consisting of QoS performance, reliability, and guarantee, and QoS scalability, with utility and cost functions. Furthermore, we derive preorders on multi-dimensional QoS domains, and present criteria to reduce these domains, leading to a manageable subset of QoS values that is sufficient for system design and implementation. The relationship between layers is formalized by two kinds of QoS mappings. QoS domain mappings associate QoS domains of two abstraction levels. QoS scalability mappings associate utility and cost functions of two abstraction levels. We illustrate our approach by examples from the case study Wireless Video Transmission.

show abstract

Section: Related Workmentioning

confidence: 99%

Formalization of Network Quality-of-Service Requirements

Webel

Gotzhein

2007

Lecture Notes in Computer Science

View full text Add to dashboard Cite

show abstract

“…The TAO implementation of the CORBA Audio/Video (A/V) Streaming Service [14] is used to establish the video streams and to transport the data. We encode QoS measurement, control, and adaptation directives and policies via QuO contracts [23] that are distributed throughout the UAV application. These contracts are responsible for managing the resource and application/data adaptation necessary to achieve an appropriate end-to-end QoS matched to the circumstances relevant at that time.…”

Section: Applying Managed Qos To Dre Systems: the Uav Case Studymentioning

confidence: 99%

Controlling quality‐of‐service in distributed real‐time and embedded systems via adaptive middleware

Schantz¹,

Loyall²,

Rodrigues³

et al. 2006

Softw Pract Exp

Self Cite

View full text Add to dashboard Cite

show abstract

“…These mechanisms are not generic QoS management services, but a QoS manager can selectively invoke these specific mechanisms to achieve QoS goals as part of its QoS management responsibilities. We differentiate among three basic types of managed components [19]: (1) QoS-aware MCs that implement all messages defined by our QoS management middleware; (2) QoS-unaware MCs that are wrapped with component-specific software that implements messages sent by QoS management middleware; and (3) QoS-aware, multi-component services or subsystems consisting of multiple MCs and their own QoS management solution, such as a QuO-managed [14] subsystem for communications, command, and control applications.…”

Section: Managed Componentsmentioning

confidence: 99%

“…Others have proposed that all QoS service issues be managed by the application [14] or by end service systems [5,13,15,16]. QoS mechanisms that handle concrete resources, such as CPU time or disk bandwidth, must consider the particular properties of the resource, resulting in type-specific QoS management techniques and mechanisms that are not easily reusable.…”

Section: Introductionmentioning

confidence: 99%

Dynamic end-to-end QoS management middleware for distributed multimedia systems

et al. 2002

View full text Add to dashboard Cite

Abstract. In this paper, we present a separable, reusable middleware solution that provides coordinated, end-to-end QoS management over any type of service component, and can use existing (legacy) QoS management solutions (by using wrappers) in a distributed multimedia system. Our middleware solution incorporates strategic and tactical QoS managers, and supports protocols and messages between tactical managers and managed application components, and between QoS managers in the management hierarchy. Strategic QoS managers take a global view of QoS provided by a set of application components within the manager's policy domain. Tactical QoS managers provide local control over application components. We introduce the concept of QoS policy domains to scope the authority of a strategic QoS manager. We describe how the management hierarchy is dynamically configured and reconfigured based on runtime needs of the application.

show abstract

QuO’s Runtime Support for Quality of Service in Distributed Objects

Cited by 97 publications

References 7 publications

Formalization of Network Quality-of-Service Requirements

Formalization of Network Quality-of-Service Requirements

Controlling quality‐of‐service in distributed real‐time and embedded systems via adaptive middleware

Dynamic end-to-end QoS management middleware for distributed multimedia systems

Contact Info

Product

Resources

About