1999
DOI: 10.1117/12.373538
|View full text |Cite
|
Sign up to set email alerts
|

<title>Adaptive middleware architecture for a distributed omnidirectional visual tracking system</title>

Abstract: In different areas of applications such as education, entertainment, medical surgery, or space shuttle launching, distributed visual tracking systems are of increasing importance. In this paper we describe the design, implementation and evaluation of OmniTrack, a distributed omni-directional visual tracking system, developed at the University of Illinois at Urbana-Champaign, with an Adaptive Middleware Architecture as the core of the system. With respect to both operating systems and network connections, adapt… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
9
0

Year Published

2004
2004
2009
2009

Publication Types

Select...
7

Relationship

0
7

Authors

Journals

citations
Cited by 9 publications
(9 citation statements)
references
References 10 publications
0
9
0
Order By: Relevance
“…Agilos (17] is about creating agile, adaptive middleware architecture to support application-aware QoS adaptation. One of its key components is called adaptor which monitors both [n comparison to our replicated client-server model, these related runtime adaptation systems have the following three limitations given unpredictability and instability in resource conditions and usage patterns.…”
Section: B Adaptation Methods and Limitationsmentioning
confidence: 99%
“…Agilos (17] is about creating agile, adaptive middleware architecture to support application-aware QoS adaptation. One of its key components is called adaptor which monitors both [n comparison to our replicated client-server model, these related runtime adaptation systems have the following three limitations given unpredictability and instability in resource conditions and usage patterns.…”
Section: B Adaptation Methods and Limitationsmentioning
confidence: 99%
“…Starting from the home DS to which a query is submitted (step 1), if no service ad (or summarized service ad -if it is a higher level DS) matches the query, the DS will forward the query up to its parent DS, and so on (steps 2, 3). If there is a match, the DS will forward the query downward to the children DS(es) which originally sent up this qualified summarized service ad (steps 4,5). From this point, the query may be coming down along multiple 'paths' in the hierarchy, because there may exist multiple qualified service ads.…”
Section: Basic Service Discovery Mechanismmentioning
confidence: 99%
“…However, in order to be understood by the DSes which are service-independent, the QoS level definition should conform to the following simple rule: the higher the QoS level, the better the QoS observed. Our experience with a Video-on-Demand service [12] and a Distributed Visual Tracking service [5], which have very different definitions of QoS levels, demonstrates the feasibility of implementing client-side software components in this fashion.…”
Section: Enhancement To Service Clientsmentioning
confidence: 99%
“…A distributed video stream server [41] needs to maintain a specific frame rate and can do so by altering the levels of fidelity for the video data. Similarly, distributed visual tracking systems [38] need on-the-fly adaptation as the available bandwidth varies. Real-Time Visualization: Large scale volume rendering involves an increasing amount of data, which makes interactive rendering infeasible.…”
Section: Target Applicationsmentioning
confidence: 99%