Layer 4+ switching with QoS support for RTP and HTTP

Harbaum, Till; Zitterbart, Martina; Griffoul, F.; Röthig, Jürgen; Schaller, Sibylle; Stüttgen, Heinrich J.

doi:10.1109/glocom.1999.830048

Cited by 11 publications

(4 citation statements)

References 11 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Several generic VMs have also been developed, allowing the programmer to use general purpose languages like Java, Python, or even LISP [15,6,4,12]. The smallest official Java standard is the Connected Device Limited Configuration [27], but since it targets devices with at least a 16 or 32-bit CPU and 160-512KB of flash memory available, it is still too large for most sensor nodes.…”

Section: Related Workmentioning

confidence: 99%

Improved Ahead-of-time Compilation of Stack-based JVM Bytecode on Resource-constrained Devices

Reijers¹,

Shih²

2019

ACM Trans. Sen. Netw.

View full text Add to dashboard Cite

Many virtual machines exist for sensor nodes with only a few KB RAM and tens to a few hundred KB flash memory. They pack an impressive set of features, but suffer from a slowdown of one to two orders of magnitude compared to optimised native code, reducing throughput and increasing power consumption.Compiling bytecode to native code to improve performance has been studied extensively for larger devices, but the restricted resources on sensor nodes mean most modern techniques cannot be applied. Simply replacing bytecode instructions with predefined sequences of native instructions is known to improve performance, but produces code several times larger than the optimised C equivalent, limiting the size of programmes that can fit onto a device. This paper identifies the major sources of overhead resulting from this basic approach, and presents optimisations to remove most of the remaining performance overhead, and over half the size overhead, reducing them to 69% and 91% respectively. While this increases the size of the VM, the break-even point at which this fixed cost is compensated for is well within the range of memory available on a sensor device, allowing us to both improve performance and load more code on a device.

show abstract

Section: Related Workmentioning

confidence: 99%

Improved Ahead-of-time Compilation of Stack-based JVM Bytecode on Resource-constrained Devices

Reijers¹,

Shih²

2019

ACM Trans. Sen. Netw.

View full text Add to dashboard Cite

show abstract

“…By using ASCII configuration tables we believe that our approach simplifies the configuration of a DiffServ router by human users. Our implementation also allowed to integrate a layer-4 flow detection mechanism [12]. In addition, special queuing disciplines for ATM have been implemented that allow to replace software shaping and policing by ATM hardware [17].…”

Section: Related Workmentioning

confidence: 99%

A Linux Implementation of a Differentiated Services Router

Braun

Einsiedler

Scheidegger

et al. 2000

Next Generation Networks. Networks and Services for the Information Society

View full text Add to dashboard Cite

Abstract. The Internet Engineering Task Force (IETF) is currently working on the development of Differentiated Services (DiffServ). DiffServ seems to be a promising technology for next-generation IP networks supporting Quality-ofServices (QoS). Emerging applications such as IP telephony and time-critical business applications can benefit significantly from the DiffServ approach since the current Internet often can not provide the required QoS. This paper describes an implementation of Differentiated Services for Linux routers and end systems. The implementation is based on the Linux traffic control package and is, therefore, very flexible. It can be used in different network environments as first-hop, boundary or interior router for Differentiated Services. In addition to the implementation architecture, the paper describes performance results demonstrating the usefulness of the DiffServ concept in general and the implementation in particular.

show abstract

“…The radio technologies employed for wireless access were IEEE 802.11 and Bluetooth. For QoS provisioning as well as generation of metering records required for billing, we used an implementation of reconfigurable L4+ systems by NEC Europe, Network Laboratories (Harbaum et al, 1999), which are essentially DiffServ-enabled IP routers with additional capabilities for flow monitoring and record generation based on transport and application layer information.…”

Section: Platform Prototypementioning

confidence: 99%