ABSTRACT

TCP smart framing, TCP-SF for short, enables the fast retransmit/recovery algorithm even when the congestion window is small. Without modifying the TCP congestion control based on the additive increase/multiplicative-decrease paradigm, TCP-SF adopts a novel segmentation algorithm, while classic TCP always tries to send fullsized segments, a TCP-SF source adopts a more flexible segmentation algorithm to try and always have a number of in-flight segments larger than three, so as to enable fast recovery.

OBJECTIVE AND SCOPE OF THE PROJECT

Balancing greediness and gentleness has always been the distinctive feature of congestion control in the TCP protocol [1]. Mindful of the presence of other traffic sharing the same network resources, TCP tries to grab as much bandwidth as possible, eventually causing congestion and data loss. Data lost by TCP is used as congestion signal, and cause the source to slow down its transmission rate. Thus, lost data can actually be seen as bandwidth used to control and regulate the network, since every segment the network discards is an indication that a TCP source has been congesting the network and should temporarily back off.

SYSTEM REQUIRMENT SPECFICATION Hardware Requirements Processor Clock speed Hard Disk RAM Cache Memory Operating System Monitor Keyboard Mouse Software Specifications : Pentium III : 550MHz : 20GB 128MB : 512KB : Windows 2000 Color Monitor 104 Keys 3 Buttons

: : :

Front-End Back End

: :

JAVA 1.4 MS-ACCESS

SYSTEM ANALYSIS TCP infers that a segment is lost whenever one of the following two events occurs: Retransmission Time Out expiration, or the arrival of three duplicate ACKs that triggers the Fast Retransmit algorithm. Of these two events, RTO is the most undesirable one as the RTO period is usually much larger than the Round Trip Time .1 Indeed, regardless of the actual amount of bytes transmitted, a coarse RTO expiration can be prevented only if enough segments are sent in the transmission window (i.e., at least three more following the lost segment). This situation can occur only if: 1) the congestion window is larger than 4 MSS (Maximum Segment Size) and 2) the flow is long enough to allow the transmission of at least 4 segments (i.e., it is not a so-called short-lived flow). Also, it should be pointed out that repeatedly forcing a shortlived connection into RTO often results in excessive penalty for the connection itself that would otherwise be finished in few more segments, rather than in actual network decongestion.

WITH CONGESTION OCCURRENCE When congestion occurs, the client sends zero (no) acknowledgements to the server. Hence server retransmits the data through fast recovery. The with congestion occurrence is depicted in Fig

SERVER

FAST RECOVERING

SEND THE SEGMENTED DATA

SEND THE ACK IS ZERO

CLIENT

SYSTEM DESIGN
The implementation of segmented data, fast retransmission and fast recovery in TCP is what the design is all about. The segmented data is a whole data unit, which is divided into fragments or packets. Unique number identifies each packet. Fragments are transmitted form server to client. If any data packet is lost that particular packet will be retransmitted to the client until the acknowledgement received by the server. The design technique involved in smart framing for developing smart frames of TCP data proceeds with the following methodologies.

DATAFLOW DIAGRAM FOR TCP-SF

Client

Send request

Server If Bursty data send

Send ACK Process REQ Send data

Data lost

Congestion Detection

Seg Alg Send seg data FRR Alg

SEQUENCE DIAGRAM FOR TCP-SF

Client

Server

Congestion Detection

Seg Algorithm

FRR Alg

Request CONG DETECT SEG ACTIVAT ED

DATA

Burst

FRR ACTIVAT ED

SEND THE SEGMENTED DATA

COLLABORATION DIAGRAM FOR TCP-SF

CLIENT

Congestion Detection Segmentation Algorithm 1 2 3 4 5

FRR ALG

SERVER

System Testing System testing is actually a series of different tests whose primary purpose is to fully exercise the computer-based system. Although each test has a different purpose, all work to verify that all system elements have been properly integrated and perform allocated functions.

System Implementation Implementation is the stage of the project where the theoretical design is turned into a working system. At this stage the main work load, the greatest upheaval and the major impact on the existing system shifts to the user department. If the implementation is not carefully planned it can cause chaos and confusion

SYSTEM MAINTENANCE AND EVALUATION System Maintenance The maintenance phase of the software cycle is the time in which a Software product performs useful work. After a system is successfully implemented, it should be maintained in a proper manner. System maintenance is an important aspect in the software development life cycle. The need for system maintenance is for it to make adaptable to the changes in the system environment. There may be social, technical and other environmental changes, which affect a system, which is being implemented.

SYSTEM MAINTENANCE AND EVALUATION System Maintenance The maintenance phase of the software cycle is the time in which a Software product performs useful work. After a system is successfully implemented, it should be maintained in a proper manner. System maintenance is an important aspect in the software development life cycle. The need for system maintenance is for it to make adaptable to the changes in the system environment. There may be social, technical and other environmental changes, which affect a system, which is being implemented.