Evaluating light-weight reliable multicast protocol extensions to the CORBA event service (original) (raw)

Augmented Reliable Multicast CORBA Event Service (ARMS): A QoS-Adaptive Middleware

2000

The CORBA Event Service specification lacks important features in terms of quality of service (QoS) characteristics required by multimedia information. The main objective of the work described in this paper is to augment the standard CORBA Event Service specification with a set of extensions, to turn it into an adaptable QoS middleware multimedia framework. To meet this, some extensions to the CORBA Event Service already developed with the aim of providing multicasting and reliability features have been enhanced in order to allow the close interaction with multicast transport protocols and with QoS monitoring mechanisms. The result was a QoS-aware middleware platform that actively adapts the quality of service required by the applications to the one that is provided by the underlying communication channel. The main quality of service features addressed by the platform - and discussed in the paper - are the support of sessions with different reliability levels, the provision of congestion control mechanisms and the capability to suppress jitter.

Extending the umiop specification for reliable multicast in corba

2005

Abstract. OMG has published an unreliable multicast specification for distributed applications developed in CORBA (UMIOP). This mechanism can be implemented based on IP Multicast, a best-effort protocol, which provides no guarantees about the message delivery. However, many fault-tolerant or groupware applications demand more restrictive agreement and ordering guarantees (for instance, reliable multicast with FIFO, causal or total ordering) from the available support for group communication.

RMTP: A Reliable Multicast Transport Protocol

1996

This paper describes the design and implementation of a multicast transport protocol called RMTP. RMTP provides sequenced, lossless delivery of bulk data from one sender to a group of receivers. RMTP achieves reliability by using a packet-based selective repeat retransmission scheme, in which each acknowledgment (ACK) packet carries a sequence number and a bitmap. ACK handling is based on a multi-level hierarchical approach, in which the receivers are grouped into a hierarchy of local regions, with a Designated Receiver (DR) in each local region. Receivers in each local region periodically send ACKs to their corresponding DR, DRs send ACKs to the higher-level DRs, until the DRs.in the highest level send ACKs to the sender, thereby avoiding the ACK-implosion problem. DRs cache received data and respond to retransmission requests of the receivers in their corresponding local regions, thereby decreasing end-toend latency and improving resource usage. This paper also provides the measurements of RMTP's performance with receivers located at various sites in the Intemet.

A Survey of Reliable Multicast Communication

2007 Next Generation Internet Networks, 2007

The paper reports on recent developments and challenges in reliable multicast communication, with special focus on reliable multicast communication at the application layer. The foundation of reliable multicast communication is given by several components, which are multicast communication, congestion control and error control. Our paper is providing a survey of these mechanisms in multicast environments.

Building a Reliable Multicast Service Based on Composite Protocols for Active Networks

2004

Active Networking embodies rapid development and deployment of new services. A network service typically consists of two or more cooperating protocols. In this paper, we describe a case study applying a composite protocol framework to developing a multicast network service. The composite protocol framework provides a rigorous mechanism to check protocol behavior before deployment. Our multicast serviced incorporates protocols for multicast routing, creation of spanning trees, reliable replication of multicast data and joining/leaving multicast groups. These protocols are built from re-usable components and communicate by means of global memory.

End to end reliable multicast transport protocol requirements for collaborative multimedia systems

1998

In order to provide guaranteed QoS multiparty collaborative multimedia applications require reliable transmission of data. The multimedia applications can vary from distributed games, shared whiteboard to interactive video conferencing. These applications often involve a large number of participants and are interactive in nature with participants dynamically joining and leaving the applications[Sudan95]. In order to provide many-to-many interaction when the number of participants is large IP multicast is a very good option for communication. IP multicast provides scalability and efficient routing but does not provide the reliability these multimedia applications may require. Though a lot of research has been done on reliable multicast transport protocol, it really seems that the only way of doing a reliable multicast is to build it for a given purpose like conference control in multimedia conferencing. This paper compares some of the available multicast transport protocols and analyses the most suitable features and functionalities provided by these protocols for a facet of conference control, floor control. The goal is to find or design a reliable multicast transport protocol which would scale to tens or hundreds of participants scattered across the Internet and deliver the control messages reliably.

TRACK Architecture: A Scalable Real-time Reliable Multicast Protocol

2000

1. Abstract One of the protocol instantiations the RMT WG is chartered to create is a TRee-based ACKnowledgement protocol (TRACK). Rather than create a set of monolithic protocol specifications, the RMT WG has chosen to break the reliable multicast protocols in to Building Blocks (BB) and Protocol Instantiations (PI). A Building Block is a specification of the algorithms of a single component, with an abstract interface to other BBs and PIs.

Building a Reliable Message Delivery System Using the CORBA Event Service

Lecture Notes in Computer Science, 2000

In this paper we study the suitability of the CORBA Event Service as a reliable message delivery mechanism. We first show that products built to the CORBA Event Service specification will not guarantee against loss of messages or guarantee order. This is not surprising, as the CORBA Event Service specification does not deal with Quality of Service (QoS) and monitoring issues. The CORBA Notification Service, although it provides much of the QoS features, may not be an option. Therefore, we examine application-level reliability schemes to build a reliable communication means over the existing CORBA Event Service. Our end-to-end reliability schemes are applicable to management applications where state resynchronization is possible and sufficient. The reliability schemes proposed provide resilience in the face of failures of the supplier, consumer, and the Event Service processes.

Reliable Multicast Transport Protocol (RMTP

IEEE Journal on Selected Areas in Communications, 1997

This paper presents the design, implementation, and performance of a reliable multicast transport protocol (RMTP). RMTP is based on a hierarchical structure in which receivers are grouped into local regions or domains and in each domain there is a special receiver called a designated receiver (DR) which is responsible for sending acknowledgments periodically to the sender, for processing acknowledgment from receivers in its domain, and for retransmitting lost packets to the corresponding receivers. Since lost packets are recovered by local retransmissions as opposed to retransmissions from the original sender, end-to-end latency is significantly reduced, and the overall throughput is improved as well. Also, since only the DR's send their acknowledgments to the sender, instead of all receivers sending their acknowledgments to the sender, a single acknowledgment is generated per local region, and this prevents acknowledgment implosion. Receivers in RMTP send their acknowledgments to the DR's periodically, thereby simplifying error recovery. In addition, lost packets are recovered by selective repeat retransmissions, leading to improved throughput at the cost of minimal additional buffering at the receivers. This paper also describes the implementation of RMTP and its performance on the Internet.