2026-09-19T12:53:34Zhttps://dspace.mit.edu/server/oai/requestoai:dspace.mit.edu:1721.1/333382022-01-13T07:54:29Zcom_1721.1_7582com_1721.1_7581col_1721.1_131023
John V. Guttag.
Qureshi, Asfandyar
Massachusetts Institute of Technology. Dept. of Electrical Engineering and Computer Science.
Massachusetts Institute of Technology. Department of Electrical Engineering and Computer Science
2006-07-13T15:16:28Z
2006-07-13T15:16:28Z
2005
2005
http://hdl.handle.net/1721.1/33338
62391934
Thesis (M. Eng.)--Massachusetts Institute of Technology, Dept. of Electrical Engineering and Computer Science, 2005.
Includes bibliographical references (p. 157-161).
Inverse multiplexing, or network striping, allows the construction of a high-bandwidth virtual channel from a collection of multiple low-bandwidth network channels. Striping systems usually employ a packet scheduling policy that allows applications to be oblivious of the way in which packets are routed to specific network channels. Though this is appropriate for many applications, many other applications can benefit from an approach that explicitly involves the application in the determination of the striping policy. Horde is middleware that facilitates flexible striping over Wireless Wide Area Network (WWAN) channels. Horde is unusual in that it separates the striping policy from the striping mechanism. It allows applications to describe network Quality-of-Service (QoS) objectives that the striping mechanism attempts to satisfy. Horde can be used by a set of data streams, each with its own QoS policy, to stripe data over a set of WWAN channels. The WWAN QoS variations observed across different channels and in time, provide opportunities to modulate stream QoS through scheduling. The key technical challenge in Horde is giving applications control over certain aspects of the data striping operation while at the same time shielding the application from low-level details. Horde exports a set of flexible abstractions replacing the application's network stack. Horde allows applications to express their policy goals as succinct network-QoS objectives. Each objective says something, relatively simple, about the sort of network QoS an application would like for some data stream(s). We present the Horde architecture, describe an early implementation, and examine how different policies can be used to modulate the quality-of-service observed across different independent data streams. Through experiments conducted on real and simulated network channels, we confirm our belief that the kind of QoS modulation Horde aims to achieve is realistic for actual applications.
by Asfandyar Qureshi.
M.Eng.
161 p.
10306058 bytes
10313618 bytes
application/pdf
application/pdf
eng
Massachusetts Institute of Technology
M.I.T. theses are protected by copyright. They may be viewed from this source for any purpose, but reproduction or distribution in any format is prohibited without written permission. See provided URL for inquiries about permission.
http://dspace.mit.edu/handle/1721.1/7582
Electrical Engineering and Computer Science.
Flexible application driven network striping over Wireless Wide Area Networks
Thesis
application/pdf
false
Publication
unknown
unknown
<Publication xmlns="https://www.openaire.eu/cerif-profile/1.1/" id="40df162e-3fb9-4616-8c03-0d6d9b013435">
<Type xmlns="https://www.openaire.eu/cerif-profile/vocab/COAR_Publication_Types">http://purl.org/coar/resource_type/c_1843</Type>
<Language>eng</Language>
<Title>Flexible application driven network striping over Wireless Wide Area Networks</Title>
<PublishedIn>
<Publication>
</Publication>
</PublishedIn>
<PublicationDate>2005</PublicationDate>
<Authors>
<Author>
<DisplayName>Qureshi, Asfandyar</DisplayName>
<Affiliation>
<OrgUnit>
</OrgUnit>
</Affiliation>
</Author>
</Authors>
<Editors>
</Editors>
<Publishers>
<Publisher>
<DisplayName>Massachusetts Institute of Technology</DisplayName>
<OrgUnit />
</Publisher>
</Publishers>
<License>http://dspace.mit.edu/handle/1721.1/7582</License>
<Keyword>Electrical Engineering and Computer Science.</Keyword>
<Abstract>Inverse multiplexing, or network striping, allows the construction of a high-bandwidth virtual channel from a collection of multiple low-bandwidth network channels. Striping systems usually employ a packet scheduling policy that allows applications to be oblivious of the way in which packets are routed to specific network channels. Though this is appropriate for many applications, many other applications can benefit from an approach that explicitly involves the application in the determination of the striping policy. Horde is middleware that facilitates flexible striping over Wireless Wide Area Network (WWAN) channels. Horde is unusual in that it separates the striping policy from the striping mechanism. It allows applications to describe network Quality-of-Service (QoS) objectives that the striping mechanism attempts to satisfy. Horde can be used by a set of data streams, each with its own QoS policy, to stripe data over a set of WWAN channels. The WWAN QoS variations observed across different channels and in time, provide opportunities to modulate stream QoS through scheduling. The key technical challenge in Horde is giving applications control over certain aspects of the data striping operation while at the same time shielding the application from low-level details. Horde exports a set of flexible abstractions replacing the application's network stack. Horde allows applications to express their policy goals as succinct network-QoS objectives. Each objective says something, relatively simple, about the sort of network QoS an application would like for some data stream(s). We present the Horde architecture, describe an early implementation, and examine how different policies can be used to modulate the quality-of-service observed across different independent data streams. Through experiments conducted on real and simulated network channels, we confirm our belief that the kind of QoS modulation Horde aims to achieve is realistic for actual applications.</Abstract>
<Access xmlns="http://purl.org/coar/access_right"
>
</Access>
</Publication>