These three topics \u2013 LANs<\/a>, IP<\/a> and TCP<\/a> \u2013 are often called layers; they constitute the Link layer, the Internetwork layer, and the Transport layer respectively. Together with the Application layer (the software you use), these form the \u201cfour-layer model\u201d for networks. A layer, in this context, corresponds strongly to the idea of a programming interface or library, with the understanding that a given layer communicates directly only with the two layers immediately above and below it. An application hands off a chunk of data to the TCP library, which in turn makes calls to the IP library, which in turn calls the LAN layer for actual delivery. An application does not interact directly with the IP and LAN layers at all.<\/p>\n The LAN layer is in charge of actual delivery of packets, using LAN-layer-supplied addresses. It is often conceptually subdivided into the \u201cphysical layer\u201d dealing with, eg, the analog electrical, optical or radio signaling mechanisms involved, and above that an abstracted \u201clogical\u201d LAN layer that describes all the digital \u2013 that is, non-analog \u2013 operations on packets (Section 2.1.4). The physical layer is generally of direct concern only to those designing LAN hardware; the kernel software interface to the LAN corresponds to the logical LAN layer.<\/p>\n Any one network connection \u2013 eg at the LAN layer \u2013 has a data rate: the rate at which bits are transmitted. In some LANs (eg Wi-Fi) the data rate can vary with time. Throughput refers to the overall effective transmission rate, taking into account things like transmission overhead, protocol inefficiencies and perhaps even competing traffic. It is generally measured at a higher network layer than the data rate.<\/p>\n The term bandwidth can be used to refer to either of these, though we here use it mostly as a synonym for data rate. The term comes from radio transmission, where the width of the frequency band available is proportional, all else being equal, to the data rate that can be achieved.<\/p>\n In discussions about TCP, the term goodput is sometimes used to refer to what might also be called \u201capplication-layer throughput\u201d: the amount of usable data delivered to the receiving application. Specifically, retransmitted data is counted only once when calculating goodput but might be counted twice under some interpretations of \u201cthroughput\u201d.<\/p>\n Data rates are generally measured in kilobits per second (kbps) or megabits per second (Mbps); the use of the lower-case \u201cb\u201d here denotes bits. In the context of data rates, a kilobit is 10 bits (not 2 ) and a megabit is 10 bits. Somewhat inconsistently, we follow the tradition of using kB and MB to denote data volumes of 2 and 2 bytes respectively, with the upper-case B denoting bytes. The newer abbreviations KiB<\/a> and MiB would be more precise, but the consequences of confusion are modest.<\/p>\n","protected":false},"excerpt":{"rendered":"Data Rate, Throughput and Bandwidth<\/h3>\n