Effective Transmission of Data through RBPH for

Group Communication

INTRODUCTION
Pragmatic General Multicast (PGM) is a departure from previous end to end
reliable protocols that exploit Internet Multicast. It has both end system and
router elements to the protocol. This is an attempt to overcome the scaling
problems of protocol reliability techniques (ACK or NAK, retransmission)
when operating them over intermittently lossy IP Networks. PGM is targeted at
one to many applications, but of course could be used for many to many simply
by using multiple sessions.
i) Add IP router alert option handling in the IP packet processing
ii) Add PGM processing


"Pragmatic General Multicast (PGM) is a reliable multicast transport protocol
mainly aimed for applications that require ordered, duplicate-free, multicast
data delivery from multiple sources to multiple receivers. The advantage of
PGM over traditional multicast protocols is that it guarantees that a receiver in
the group either receives all data packets from transmissions and
retransmissions, or is able to detect unrecoverable data packet loss. PGM is
specifically intended as a workable solution for multicast applications with
basic reliability requirements. Its central design goal is simplicity of operation
with due regard for scalability and network efficiency".



Multicast protocols
Multicast is one-to-many communication. There are numerous applications
today that involve communications between one or more sources and many
receivers. These applications include push technologies and multimedia
applications as well as shared whiteboard applications, data conferencing,
software distribution etc.
Multicasting is a technique that enables a single packet transmission to reach
one or more destinations or group. The primary benefits of a packet reaching
multiple destinations from a single transmission are the following: bandwidth
minimization, parallelism in the network, and optimization of transmitter costs.

The requirements of multicast protocols are:
Multicast group formation
Assignment of multicast group addresses
Dynamic and rapid configuration of multicast groups
Full range of reliability: reliable Vs semi-reliable Vs unreliable
Adaptation to network congestion

Reliable Multicast
The Transmission Control Protocol (TCP) meets the general requirements for
reliable, ordered delivery of packets for unicast transmission. However such
general-purpose protocol for multicast transmission does not exist yet.
With the term reliable it is meant that the protocol is able to achieve:
Loss Recovery
Ordered delivery
No duplicates
Isolation of independent failures
Reliable multicast communication is becoming increasingly important,
especially for applications such as multimedia conferencing, replicated file
servers, and distributed interactive simulation and many others. Due to the fact
that group communication applications have a wide variety of reliability
requirements, many different reliable multicast protocols have been developed,
none of which are dominant standards as TCP is for reliable unicast.
Group communication can be one-to-many or many-to-many with small or
large group sizes. Some applications require packets to be delivered in order,
while others do not. Some applications require stability (the fact that the sender
knows that a packet has been received), while others do not. Different protocols
provide different levels of reliability depending on their particular application.
The protocol reliability can be sender-initiated or receiver-initiated. That is,
either of two is responsible for the detection of lost packets.
A sender-initiated reliability protocol places the burden of loss detection on the
sender. A positive acknowledgement (ACK) is required from every receiver for
every packet sent. A lost packet is detected when the sender fails to receive an
ACK from every receiver within some time limit. When a loss is detected, the
packet is retransmitted and the sender again waits for an ACK from every
receiver.
A receiver-initiated reliability protocol requires the individual receivers to
detect if any packets are lost. Receivers generate a negative acknowledgement
(NAK) when they detect a lost packet. The packet is retransmitted in response
to one or more NAKs. NAK implosion is still possible if a large number of
receivers lose the same packet. Suppression mechanisms can be used to
minimize the number of duplicate NAKs produced when such correlated losses
occur. Similar suppression mechanisms can be used to prevent a flood of
retransmissions when any member with the appropriate data may respond to a
NAK.

Abstract:
Pragmatic General Multicast (PGM) is a reliable multicast transport
protocol that runs over a best effort datagram service, such as IP multicast.
PGM obtains scalability via hierarchy, forward error correction, NAK
elimination, and NAK suppression. It employs a novel polling scheme for NAK
delay tuning to facilitate scaling up and down. This article describes the
architecture of PGM, and discusses performance and security issues. We show
that PGM supports asymmetric networks, achieves high network utilization,
and is capable of high-speed (> 100 Mb/s) operation. PGM is currently an IETF
experimental RFC that has been implemented in both commercial and
academic settings.
Pragmatic General Multicast (PGM) is a reliable multicast transport
protocol for applications that require multicast data delivery from a single
source to multiple receivers. PGM guarantees that a receiver in the group
either receives all data packets from transmissions and repairs, or is able to
detect (rare) unrecoverable data packet loss. It obtains excellent scalability via
hierarchy, forward error correction, NAK (negative acknowledgement)
elimination, and NAK suppression. PGM is now an IETF experimental RFC. This
paper describes the architecture of PGM and provides some analysis of its
performance.
PGM does not require the receiver to multicast, making it applicable to
networks that are only multicast capable from sender to receivers. PGM also
makes efficient use of back-channel bandwidth making it well-suited to
asymmetric networks that have a high capacity channel from the sender to
receivers, but have a constrained back-channel from the receivers to the sender.

PROBLEM FORMULATION
Description of Problem
The main objective of this system is to focus on fuzzy techniques for
image filtering. Already several fuzzy filters for noise reduction have been
developed. Those technique deals with fat-tailed noise like impulse noise and
median filter. Most fuzzy techniques are not specifically designed for Gaussian
(-like) noise or do not produce convincing results when applied to handle this
type of noise.



Objectives
The following are the objectives of the Database Migration,
To provide better service to clients at various location.
To reduce administrative costs.
To decrease the paperwork and implement more streamlined
information gathering and client services.
To lower error rates.
To increase productivity.

HARDWARE SPECIFICATION

Processor : Any Processor above 500 Mhz.
Ram : 128Mb.
Hard Disk : 10 Gb.
Compact Disk : 650 Mb.
Input device : Standard Keyboard and Mouse.
Output device : VGA and High Resolution Monitor.

SOFTWARE SPECIFICATION
Operating System : Windows 2000 server Family.
Pages developed using: Java Server Pages and HTML.
Techniques : Apache Tomcat Web Server 4.0, J2SDK1.4
Web Browser : Microsoft Internet Explorer.
Data Bases : Microsoft Access, SQL Server