PLAN: a packet language for active networks
ICFP '98 Proceedings of the third ACM SIGPLAN international conference on Functional programming
Lightweight network support for scalable end-to-end services
Proceedings of the 2002 conference on Applications, technologies, architectures, and protocols for computer communications
A Flexible Concast-Based Grouping Service
IWAN '02 Proceedings of the IFIP-TC6 4th International Working Conference on Active Networks
Concast: Design and Implementation of a New Network Service
ICNP '99 Proceedings of the Seventh Annual International Conference on Network Protocols
The ASP EE: An Active Network Execution Environment
DANCE '02 Proceedings of the 2002 DARPA Active Networks Conference and Exposition
Active Network Monitoring and Control: The SENCOMM Architecture and Implementation
DANCE '02 Proceedings of the 2002 DARPA Active Networks Conference and Exposition
SANDS: Specialized Active Networking for Distributed Simulation
DANCE '02 Proceedings of the 2002 DARPA Active Networks Conference and Exposition
IEEE Communications Magazine
Concast: design and implementation of an active network service
IEEE Journal on Selected Areas in Communications
| Hi-index | 0.00 |
The NodeOS and execution environment (EE) layers of the active network architectural framework are designed to offer a general purpose programming environment to active applications (AAs). However, the architecture suffers from the lack of higher-level APIs and services that would simplify AA code and could be shared by multiple AAs. We propose a modified architecture that introduces an Application Environment (AE) layer above the EE layer to fill the gap. The AE layer offers higher-level services to simplified User-define Processing Modules (UPMs). Together they replace the conventional AA and offer a higher-level API to code to. This paper discusses the issues that arise when breaking the existing AA layer into two layers, and presents our experiences implementing a concast service using the new architecture. We also present performance numbers for our concast service (running on the ASP EE) that show the additional overhead incurred is acceptable.