INTRODUCTION

When coverage area of these different technologies overlap, receiver equipped with multiple interfaces can use them simultaneously to improve the performance of its applications in terms of bandwidth rely on bandwidth aggregation. However, specific conditions such as bottleneck bandwidth and end-to-end delay need to be accounted for before using such techniques. If this problem of end-to-end delay and bottleneck bandwidth are not properly addressed, there may be many packets along multiple paths which can arrive late and can lead to a large number of out-of-order packets at the receiver, which can eventually cause serious degradation of video quality at the receiver. For this reason, in this study, the authors propose a multi-path transmission control scheme (MTCS) combining bandwidth aggregation and packet scheduling for real-time streaming in a multi-path environment. In a bandwidth aggregation scheme, the authors propose a mathematical model to find the transmission rate over each path in order to obtain the optimal total throughput. However, the endto- end delay of each path is not the same. The out-of-order packets problem will become serious in a multipath environment. Therefore the authors propose a packet scheduling scheme to arrange the transmission sequence in order to effectively minimise the impact of packet reordering at the receiver. Our proposed control scheme not only aggregates the available bandwidth of multiple paths, but also reduces the time of packet reordering at the receiver. Experimental results show with our proposed scheme, the authors not only obtain the optimal transmission throughput but also reduce packet reordering delays under varying drop and delay conditions caused by the underlying network. In multi-path environments, the out-of-order packets problem will become serious. In RTVS applications, the out-of-order packets will lead to a decrease in video quality. In order to solve the out-of-order packets problem, a buffer

is used to execute the packet reordering at the receiver. However, when using a buffer at the receiver, the outof-order arrival of packets can lead to missing data for RTVS applications. Reordering can also increase buffer requirements at the receiver and can also increase end-toend latency. The frequent use of predictive coding structures makes video streaming particularly sensitive to loss, jitter and varying delay. Recent measurement studies have shown that the degree of packet reordering required for packets delivered on the Internet is on the increase, and has been demonstrated to have a measurable impact on end-to-end network performance. In the previous work, less data were transmitted at the path of the lower ABW in order to avoid congestion losses. On the other hand, more data were transmitted at the path of higher ABW in order to obtain better transmission throughput. In the previous work, when the wireless losses rate was serious in the path of higher available bandwidth, the packet loss rate will become very serious. In order to solve the out-of-order packet problem, the authors proposed packet scheduling to control packet delivery to the destination in a timely manner without out-of-order packets. If the packet scheduling control mechanism was based on bandwidth aggregation, the end-to-end delay, not being the same between each path, will lead to a serious out-of-order packets problem. However, if the packet scheduling control mechanism was based on end-toend delay; the shortest path will become overloaded. Hence, how to take both bandwidth aggregation and end-to-end delay into account in order to obtain the optimal transmission throughput is very important.

Review of Literature

1. Performance evaluation of shortest multipath source routing scheme by H. Zafar, D. Harle, I. Andonovic, and Y. Khawaja Multipath routing in mobile ad-hoc networks allows the establishment of multiple paths for routing between a sourcedestination pair. It exploits the resource redundancy and diversity in the underlying network to provide benefits such as fault tolerance, load balancing, bandwidth aggregation and the improvement in quality-of-service metrics such as delay. Previous work shows that on-demand multipath routing schemes achieve better performance under certain scenarios with respect to a number of key performance metrics when compared with traditional single-path routing mechanisms. A multipath routing scheme, referred to as shortest multipath source (SMS) routing based on dynamic source routing (DSR) is proposed here. The mechanism has two novel aspects compared with other ondemand multipath routing schemes: it achieves shorter multiple partialdisjoint paths and allows more rapid recovery from route breaks. The performance differentials areinvestigated using NS-2 under conditions of varying mobility, offered load and network size. Results reveal that SMS provides a better solution than existing source-based approaches in a truly mobile ad-hoc environment.

2. A Concurrent Multi-path Transmission Control Scheme to reduce packet reordering latency at the receiver by Ming-Fong Tsai Chilamkurti, N.K. Zeadally, S. Ce-Kuen Shieh Dept. of Electr. Eng., Nat. Cheng Kung Univ., Tainan Concurrent transfer is a feasible solution to enhance the efficiency and reliability of data transmission. In this paper, we propose a new transmission control scheme, the concurrent multi-path transmission control scheme (CMTCS). Our CMTCS effectively minimizes the impact of packet reordering at the receiver under concurrent transfers. Experimental results show that with our proposed scheme, we reduce packet reordering delays under varying drop and delay conditions caused by the underlying network. 3. Survey of multipath routing protocols for mobile ad hoc networks by Mohammed Tarique, Kemal E. Tepe, Sasan Adibi, Shervin Erfani This survey investigates multipath routing protocols for mobile ad hoc networks (MANETs). The main objectives of multipath routing protocols are to provide reliable communication and to ensure load balancing as well as to improve quality of service (QoS) of MANETs. These multipath protocols are broadly classified into five categories based on their major goals. The goals are to improve delay, provide reliability, reduce overhead, maximize network life and support hybrid routing. Multipath routing protocols address issues such as multiple paths discovery and maintaining these paths. Issues, objectives, performances, advantages and disadvantages of these protocols are investigated and summarized. A checklist is provided as a guideline so that a network designer can choose an appropriate multipath routing protocol to meet the network's application objectives. 4. A measurement study of available bandwidth estimation tools by JACOB.S., DINA.K., FRANS.K

Available bandwidth estimation is useful for route selection in overlay networks, QoS verification, and traffic engineering. Recent years have seen a surge in interest in available bandwidth estimation. A few tools have been proposed and evaluated in simulation and over a limited number of Internet paths, but there is still great uncertainty in the performance of these tools over the Internet at large.This paper introduces Spruce, a simple, lightweight tool for measuring available bandwidth, and compares it with two existing tools, IGI and Pathload, over 400 different Internet paths. The comparison focuses on accuracy, failure patterns, probe overhead, and implementation issues. The paper verifies the measured available bandwidth by comparing it to Multi-Router Traffic Grapher (MRTG) data and by measuring how each tool responds to induced changes in available bandwidth.The measurements show that Spruce is more accurate than Pathload and IGI. Pathload tends to overestimate the available bandwidth whereas IGI becomes insensitive when the bottleneck utilization is large.

5.

Bandwidth

aggregation

for

realtime

applications

in

heterogeneous wireless networks by Chebrolu,K.; Rao,R.R.; A variety of wireless interfaces are available for today's mobile user to access Internet content. When coverage areas of these different technologies overlap, a terminal equipped with multiple interfaces can use them simultaneously to improve the performance of its applications. In this paper, we motivate the advantages that can be had through simultaneous use of multiple interfaces and present a network layer architecture that enables diverse multiaccess services. In particular, we explore in depth one such service provided by the architecture: Bandwidth Aggregation (BAG) for real-time applications. An important aspect of the architecture when providing BAG services for real-time applications is the scheduling algorithm that partitions the traffic onto different interfaces such that the QoS

requirements of the application are met. We propose one such algorithm Earliest Delivery Path First (EDPF), that ensures packets meet their playback deadlines by scheduling packets based on the estimated delivery time of the packets. We show through analysis that EDPF performs close to an idealized Aggregated Single Link (ASL) discipline, where the multiple interfaces are replaced by a single interface with same aggregated bandwidth. A prototype implementation and extensive simulations carried using video and delay traces show the performance improvement BAG with EDPF scheduling offers over using just the Highest Bandwidth Interface (HBI) and other scheduling approaches based on weighted round robin.

About the Software About C#.NET C# is an object-oriented programming language developed by Microsoft Corporation as part of their .NET initiative in response to the success of Sun Microsystems' Java programming language. C# source code as well as those of other .NET languagesis compiled into an intermediate byte code called MSIL (Microsoft Intermediate Langauge. C# is primarily derived from the C, C++, and Java programming languages with some features of Microsoft's Visual Basic in the mix. Classes and Objects

The words "class" and "object" are used so much in object-oriented programming that it is easy to get the terms mixed up. Generally speaking, a class is an abstract representation of something, whereas an object is a usable example of the thing the class represents. Fields, Properties, Methods, and Events Classes are made of fields, properties, methods, and events. Fields and properties represent information that an object contains. Fields are like variables in that they can be read or set directly. Properties are retrieved and set like fields, but are implemented using property Get and property set procedures, which provide more control on how values are set or returned. Methods represent actions that an object can perform. We define methods by adding procedures, either Sub routines or functions, to our class. Events are notifications an object receives from, or transmits to, other objects or applications. Events allow objects to perform actions whenever a specific occurrence takes place.

Encapsulation means that a group of related properties, methods, and other members are treated as a single unit or object. Objects can control how properties are changed and methods are executed. Inheritance describes the ability to create new classes based on an existing class. The new class inherits all the properties and methods and events of the base class, and can be customized with additional properties and methods. Polymorphism means that you can have multiple classes that can be used interchangeably, even though each class implements the same properties or methods in different ways. Overloading, Overriding Overloaded members are used to provide different versions of a property or method that have the same name, but that accept different

number of parameters, or parameters with different data types. Overridden properties and methods are used to replace an inherited property or method that is not appropriate in a derived class. Overridden members must accept the same data type and number of arguments. Derived classes inherit overridden members. Interfaces Interfaces describe a group of related functionalities that can belong to any class or struct. Interfaces can consist of methods, properties, events, indexers, or any combination of those four member types. An interface cannot contain fields. Interfaces members are automatically public. When a class or struct is said to inherit an interface, it means that the class or struct provides an implementation for all of the members defined by the interface. The interface itself provides no functionality that a class or struct can inherit in the way that base class functionality can be inherited. C# Namespaces A Namespace in Microsoft .Net is like containers of objects. They may contain unions, classes, structures, interfaces, enumerators and delegates. Main goal of using namespace in .Net is for creating a hierarchical organization of program. In this case a developer does not need to worry about the naming conflicts of classes, functions, variables etc., inside a project. Some of the common namespaces are System, System.Data,

System.Data.SqlClient, System.Collections, System.IO, System.Threading, System.Web, System.Windows.Forms etc. About ADO.NET ADO.NET provides consistent access to data sources such as Microsoft SQL Server, as well as data sources exposed through OLE DB and XML. Data-

sharing consumer applications can use ADO.NET to connect to these data sources and retrieve, manipulate, and update data. ADO.NET cleanly factors data access from data manipulation into discrete components that can be used separately or in tandem. ADO.NET includes .NET Framework data providers for connecting to a database, executing commands, and retrieving results. Those results are either processed directly, or placed in an ADO.NET DataSet object in order to be exposed to the user in an ad-hoc manner, combined with data from multiple sources, or remoted between tiers. The ADO.NET DataSet object can also be used independently of a .NET Framework data provider to manage data local to the application or sourced from XML. The ADO.NET classes are found in System.Data.dll, and are integrated with the XML classes found in System.Xml.dll. When compiling code that uses the System.Data namespace, reference both System.Data.dll and System.Xml.dll. ADO.NET Components The ADO.NET components have been designed to factor data access from data manipulation. There are two central components of ADO.NET that accomplish this: the DataSet, and the .NET Framework data provider, which is a set of components including the Connection, Command, Data Reader, and Data Adapter objects. The ADO.NET DataSet is the core component of the disconnected architecture of ADO.NET. The DataSet is explicitly designed for data access independent of any data source. As a result it can be used with multiple and differing data sources, used with XML data, or used to manage data local to the application. The Data Set contains a collection of one or more Data Table objects made up of rows and columns of data, as well as primary key, foreign key, constraint, and relation information about the data in the Data Table objects.

The other core element of the ADO.NET architecture is the .NET Framework data provider, whose components is explicitly designed for data manipulation and fast, forward-only, read-only access to data. The Connection object provides connectivity to a data source. The Command object enables access to database commands to return data, modify data, run stored procedures, and send or retrieve parameter information. The Data Reader provides a high-performance stream of data from the data source. Finally, the Data Adapter provides the bridge between the Data Set object and the data source. The Data Adapter uses Command objects to execute SQL commands at the data source to both load the Data Set with data, and reconcile changes made to the data in the Data Set back to the data source. You can write .NET Framework data providers for any data source. The .NET Framework ships with two .NET Framework data providers: the .NET Framework Data Provider for SQL Server and the .NET Framework Data Provider for OLE DB.

About ASP.NET ASP.NET is a server side scripting technology that enables scripts (embedded in web pages) to be executed by an Internet server.ASP stands for Active Server Pages.ASP.NET is a program that runs inside IIS (Internet Information Services). An ASP.NET file can contain HTML, XML, and scripts. Scripts in an ASP.NET file are executed on the server.An ASP.NET file has the file extension ".aspx" .When a browser requests an HTML file, the server returns the file .When a browser requests an ASP.NET file, IIS passes the request to the ASP.NET engine on the server .The ASP.NET engine reads the file, line by line, and executes the scripts in the file .Finally, the ASP.NET file is returned to the browser as plain HTML

ASP.NET supports creating reusable components through the creation of User Controls. A User Control follows the same structure as a Web Form, except that such controls are derived from the System.Web.UI.UserControl class, and are stored in ASCX files. State management ASP.NET applications are hosted in a web server and are accessed over the stateless HTTP protocol. As such, if the application uses stateful interaction, it has to implement state management on its own.

Application state Application state is a collection of user-defined variables that are shared by an ASP.NET application. These are set and initialized when the Application_OnStart event fires on the loading of the first instance of the applications and are available till the last instance exits. Application state variables are accessed using the Applications collection, which provides a wrapper for the application state variables. Application state variables are identified by names. Session state Session state is a collection of user-defined session variables, which are persisted during a user session. These variables are unique to different instances of a user session, and are accessed using the Session collection. Session variables can be set to be automatically destroyed after a defined time of inactivity, even if the session does not end. At the client end, a user session is identified either by a cookie or by encoding the session ID in the URL itself. View state View state refers to the page-level state management mechanism, which is utilized by the HTML pages emitted by ASP.NET applications to maintain the state of the web form controls and widgets. The state of the controls are encoded and sent to the server at every form submission in a hidden field known as __VIEWSTATE. The server sends back the variable so that when the page is re-rendered, the controls render at their last state. At the server side, the application might change the viewstate, if the processing results in updating the state of any control. About SQL SERVER 2005

MS (Microsoft) SQL Server 2005 is truly the next generation data management and analysis solution that is built for scalability, availability, analysis and security of data. The increasing ease with which database applications can be built has reduced the complexities of deploying and managing database applications. Data can now be shared across platforms, applications and devices making it possible to network internal and external systems seamlessly. Performance, availability, scalability and security are now available for lower costs. It is now a secure, reliable and productive platform for enterprise data and business intelligence tools.

SQL Server 2005 has a number of tools to help the Database Administrator and the Developer. The relational database engine has been improved to give better performance and support for both structured and unstructured (XML) data. It provides for high systems availability, scalable concurrency with secondary data stores, enterprise reporting solutions and integration with heterogeneous systems such as Oracle databases.

Transact-SQL Overview Transact SQL, also called T-SQL, is Microsoft's extension to the ANSI SQL language. It is the driving force of Microsoft's SQL Server and is a dynamic database programming language. There have been several extensions added to the ANSI SQL language that have become their own SQL language. T-SQL is written inside of a stored procedure. A stored procedure is a stored set of SQL commands that sit on the physical server. In this case the SQL server. They are compiled after their first use and take heavy burden off the server faster Processing.

Tables, keys, fields, and data types

The heart of any database is the data, which is stored in Table. The columns in each Table are called fields which define the data types used. Special fields used to link Tables together are called keys, which form the arteries for a relation database. SELECT fields from Tables Conditions for searching through records and returning only the results we would like to see are summarized through the most commonly used expressions. ORDER BY sorting and GROUP BY aggregates Sorting results by number or alphabetically is normally required, along with combining groups of results through aggregate functions. Most common aggregates are counting and averaging of data within the database. JOIN Tables or a UNION Combining Tables together into a useful result can be a tricky operation which has many options and possibilities. The connection of a primary key to a foreign key is accomplished correctly. Insertion of Datas The insertion of new data into a database can be very simple when done consistently with the structure of the Tables. Specifically, the primary and foreign key constraints must be honored. DROP, CREATE, and DELETE

These common SQL operations show up repeatedly in the modification of database Tables. In our ongoing example throughout this series, we find that the DROP, CREATE, DELETE (and more) process is required to simply add a column into the first position of a Table design. UPDATE records Simple changes can be trivial in some cases, but the subtle aspects of search for what to change, and how those changes propagate through the database into other Tables can create a complex situation.

Features Dot Net is a Microsoft initiative. It is also known as the .Net framework. It is directed at modifying the entire computer world. It is a large set of development tools, servers, software, and services. It is Microsoft's strategy of software that provides services to people any time, any place, on any device. It has several advantages like a

consistent programming model direct support for security simplified development efforts easy application deployment and maintenance integration through public standards Multilanguage support scalability through loosely coupled architecture, enhancing developer productivity and results

Advanced security and utilizing OS services. ASP.NET and the .NET Framework simplify development by separating the application logic and presentation logic making it easier to maintain the code.

You write the design code (presentation logic) and the actual code (application logic) separately eliminating the need to mix HTML code with ASP code.

ASP.NET can also handle the details of maintaining the state of the controls, such as contents in a textbox, between calls to the same ASP.NET page.

SQL Server uses 64 bit processors while others database 32 bit processor. Therefore the speed of the processing very high.

SQL Server is cheaper than Oracle. NO need of provider to connect back end with front end.

Main Server Module: The main server maintains all the files required by the clients. Client Module This is a user interface module that allows clients to access the services. Login Module This module ensures security by preventing unauthenticated users from getting access to network. To authenticate user email id and password are collected and the user credentials are validated against the database. If the user is a valid user he is authorized to access. If the user is found to be an invalid user an error message is reported and prevents the user from accessing the services.

Future works Adding a gateway to forwards the client request to the nearest proxy server. When a client makes a request the request is intercepted by the gateway. A gateway acts an inter-mediator between requested client and proxy servers network. The gateway is periodically updated with list of proxy servers currently available in a network and also the files each proxy server is maintaining. Server will split the files for download and each splitted file will handled by the path server, client will download the file and merged the file after download.

Bibliography ZAFAR H., HARLE D., ANDONOVIC I., KHAWAJA Y.: Performance evaluation of shortest multipath source routing scheme, IET Commun., 2009, 3, (5), pp. 700713 FRACCHIA R., CASETTI C., CHIASSERINI C., MEO M.: WiSE: bestpath selection in wireless multihoming environments, IEEE Trans. Mob. Comput., 2007, 6, (10), pp. 11301141 TSAI M., CHILAMKURTI N., ZEADALLY S., SHIEH C.: A concurrent multi-path transmission control scheme to reduce packet reordering latency at the receiver. Proc. IEEE Int. Conf. on Advanced Technologies for Communications, Hanoi, Vietnam, October 2008, pp. 437440 HSIEH M., HUANG Y., CHIANG T.: Transmission of layered video streaming via multi-path on ad hoc networks, Multimed. Tools Appl., 2007, 34, (2), pp. 155177 CHEBROLU K., RAO R.: Bandwidth aggregation for realtime applications in heterogeneous wireless networks, IEEE Trans. Mob. Comput., 2006, 5, (4), pp. 388403 JURCA D., FROSSARD P.: Video packet selection and scheduling for multipath streaming, IEEE Trans. Multimed., 2007, 9, (3), pp. 629641

JACOB S., DINA K., FRANS K.: A measurement study of available bandwidth estimation tools. Proc. ACM SIGCOMM Conf. on Internet Measurement, FL, USA, October 2003, pp. 3944

TSAI M., SHIEH C., HWANG W., DENG D.: An adaptive multihop FEC protection scheme for enhancing the QoS of video streaming transmission over wireless mesh networks, Int. J. Commun. Syst., 2009, 22, (10), pp. 12971318

TSAI M., SHIEH C., KE C., DENG D.: A novel sub-packet forward error correction mechanism for video streaming over wireless networks, Multimed. Tools Appl., 2010, 47, (1), pp. 4969

PIRATLA N., JAYASUMANA A., BARE A., BANKA T.: Reorder bufferoccupancy density and its application for measurement and evaluation of packet reordering, Comput. Commun., 2007, 30, (9), pp. 19801993 IET