Thursday, September 26, 2013
Differentiate between upward and downward multiplexing?
Posted by
Sunflower
at
9/26/2013 02:59:00 AM
0
comments
Labels: Address, Connection, Data, Destination, Downward multiplexing, Links, Multiplexing, Network, Process, Receiver, Segments, Sender, Source, Technique, Transmit, Transport layer, Upward Multiplexing
|
| Subscribe by Email |
|
Saturday, September 21, 2013
What are the services provided to upper layers by transport layer?
Posted by
Sunflower
at
9/21/2013 04:01:00 PM
0
comments
Labels: Applications, Communication, Components, Connection oriented, Connection-less, Data, Framework, Interface, Layers, Networking, Operating System, OSI, Protocol, Services, TCP/IP, Transport layer, Upper layers
|
| Subscribe by Email |
|
Wednesday, July 17, 2013
What are network layer design issues?
- Services
provided to the layer 4 i.e., the transport layer.
- Implementation
of the services that are connection oriented.
- Store
– and - forward packet switching
- Implementation
of the services that are not connection oriented.
- Comparison
of the data-gram sub-nets and the virtual circuits.
- They
should be independent of the router technology.
- Shielding
from the type, number and topology of the routers must be provided to the
transport layer.
- The
network addresses that are provided to the transport layer must exhibit a
uniform numbering plan irrespective of whether it’s a LAN or a WAN.
Posted by
Sunflower
at
7/17/2013 05:30:00 PM
0
comments
Labels: Communication, Connection, Data, Datagram, Design, Hosts, Issues, Layers, Model, Network, Network layer, OSI, Packets, Processes, Routes, Routing, subnet, Tasks, Transport layer, Virtual Circuits
|
| Subscribe by Email |
|
Monday, July 1, 2013
What is the difference between TCP and UDP?
Posted by
Sunflower
at
7/01/2013 12:25:00 PM
0
comments
Labels: Connection, Data, Errors, Layers, Messages, Operating System, Packets, Protocols, Reliable, Requirements, Server, TCP, Transmission Control Protocol, Transport layer, Transportation, UDP, User, User Datagram Protocol
|
| Subscribe by Email |
|
Saturday, March 20, 2010
UDP - User Datagram Protocol
The User Datagram Protocol (UDP) is a transport layer protocol defined for use with the IP network layer protocol.UDP is often used in videoconferencing applications or computer games specially tuned for real-time performance.
- UDP network traffic is organized in the form of data grams.A data-gram comprises one message unit. The first eight bytes of a data-gram contain header information and the remaining bytes contain message data.
- UDP can be used in networks where TCP is traditionally implemented.
- It does not guarantee reliability or the correct sequencing of data.
- UDP makes use of a simple communication model without implicit transmission checks for guaranteeing reliability, sequencing, or data-gram integrity.
- UDP considers that error checks and corrections should be carried out in the communicating application, and not at the network layer.
- UDP makes the protocol that much faster and more efficient because it does not have the overhead of checking whether the data has reached the destination every time it is sent.
- UDP is a stateless protocol. UDP is used for packet broadcast or multi-casting whereby the data is sent to all the clients in the network.
The UDP header consists of four fields each of 2 bytes in length :
- Source Port : Source port recognizes the sending port and should be understood to be the port to respond to if required. If not used, then its value should be zero.
- Destination Port : UDP packets from a client use this as a service access point (SAP) to indicate the service required from the remote server.
- UDP length : The number of bytes comprising the combined UDP header information and payload data.
- UDP Checksum : A checksum to verify that the end to end data has not been corrupted by routers or bridges in the network or by the processing in an end system.
Posted by
Sunflower
at
3/20/2010 07:32:00 PM
0
comments
Labels: Datagrams, Header, Network, Ports, Protocols, Transport layer, UDP, User Datagram Protocol
|
| Subscribe by Email |
|
Thursday, March 11, 2010
How to support a reliable communication in transport layer ?
At the Transport layer, each particular set of pieces flowing between a source application and a destination application is known as a conversation.To identify each segment of data, the Transport layer adds to the piece a header containing binary data. This header contains fields of bits. It is the values in these fields that enable different Transport layer protocols to perform different functions.
Reliability means ensuring that each piece of data that the source sends arrives at the destination. At the Transport layer the three basic operations of reliability are:
- tracking transmitted data.
- acknowledging received data.
- retransmitting any unacknowledged data.
This requires the processes of Transport layer of the source to keep track of all the data pieces of each conversation and the retransmit any of data that did were not acknowledged by the destination. The Transport layer of the receiving host must also track the data as it is received and acknowledge the receipt of the data. These reliability processes place additional overhead on the network resources due to the acknowledgement, tracking, and retransmission. To support these reliability operations, more control data is exchanged between the sending and receiving hosts. This control information is contained in the Layer 4 header.
Determining the Need for Reliability
Applications, such as databases, web pages, and e-mail, require that all of the sent data arrive at the destination in its original condition, in order for the data to be useful. Any missing data could cause a corrupt communication that is either incomplete or unreadable. Therefore, these applications are designed to use a Transport layer protocol that implements reliability.
Posted by
Sunflower
at
3/11/2010 01:28:00 PM
0
comments
Labels: Acknowledging, Destination, Layer 4, Models, Open System Interconnection Reference Model, OSI, Reliability, Retransmitting, Source, Tracking, Transport layer
|
| Subscribe by Email |
|
Wednesday, March 10, 2010
The Transport Layer - Layer 4 of OSI model
The Transport Layer of the OSI model is responsible for delivering messages between networked hosts. The Transport Layer should be responsible for fragmentation and reassembly.
- This layer converts the data received from the upper layers into segments and prepares them for transport.
- The Transport layer is responsible for end-to-end (source-to-destination) delivery of entire messages.
- It allows data to be transferred reliably and uses sequencing to make sure that the order of packets is maintained.
- It also provides services such as error checking and flow control.
- In case IP, lost packets arriving out of order must be reordered.
- The size and complexity of a transport protocol depends on the type of service it can get from the network layer.
- The transport layer can accept relatively large messages, but there are strict message size limits imposed by the network (or lower) layer.
- Two transport protocols, Transmission Control Protocol (TCP) and User Datagram Protocol (UDP), sits at the transport layer.
- TCP establishes connections between two hosts on the network through 'sockets' which are determined by the IP address and port number. It keeps a track of the packet delivery order and the packets that must be resent.
- UDP provides a low overhead transmission service, but with less error checking.
- The Transport layer protocols are either connectionless or connection-oriented.
- Connection-oriented means that a connection (a virtual link) must be established before any actual data can be exchanged. e.g. TCP.
- In Connectionless, the sender does not establish a connection before it sends data, it just sends it without guaranteeing delivery. e.g. UDP.
Data Segmentation
Data segmentation is the process by which the transport layer uniquely handles all data passed to and from different upper-level applications. For example, if a user is browsing the web and checking email at the same time, each program would be passing data and waiting for a reply on a unique port number. The Transport layer ensures that data is passed to the correct application.
Posted by
Sunflower
at
3/10/2010 01:04:00 PM
0
comments
Labels: Data, Data Segmentation, Layer 4, Layers, Models, Open Systems Interconnection, OSI, Protocols, TCP, Transport layer, UDP
|
| Subscribe by Email |
|
Saturday, August 1, 2009
Overview Of The Transport Layer
The transport layer is the key to understanding layered protocols. It provides various services, the most important of which is an end-to-end, reliable, connection-oriented byte stream from sender to receiver. It is accessed through service primitives that permit the establishment, use and release of connection.
Transport protocols must be able to do connection management over unreliable networks. Connection establishment is complicated by the existence of delayed duplicate packets that can reappear at inopportune moments. To deal with them, three-way handshakes are needed to establish connections. Releasing a connection is easier than establishing one, but is still far from trivial due to the two-army problem.
Even when the network layer is completely reliable, the transport layer has plenty of work to do. It must handle all the service primitives, manage connections and timers, and allocate and utilize credits.
The main Internet transport protocol is TCP. It uses a 20-byte header on all segments. Segments can be fragmented by routers within the Internet, so hosts must be prepared to do reassembly. A great deal of work has gone into optimizing TCP performance, using algorithms from Nagle, Clark, Jacobson, Karn and others.
ATM has four protocols in the AAL layer. All of them break messages into cells at the source and reassemble the cells into messages at the destination. The CS and SAR sublayers add their own headers and trailers in various ways, leaving from 44 to 48 bytes of cell payload.
Network performance is typically dominated by protocol and TPDU processing overhead, and the situation gets worse at higher speeds. Protocols should be designed to minimize the number of TPDUs, context switches, and times each TPDU is copied. For gigabit networks, simple protocols using rate, rather than credit, flow control are called for.
Posted by
Sunflower
at
8/01/2009 09:47:00 AM
0
comments
Labels: ATM, Computer networks, Protocols, Transport layer
|
| Subscribe by Email |
|