Knowledge

Sliding window protocol

Source 📝

40: 817: 1367: =2, the receiver will accept and store the final packet 0 (thinking it is packet 8 in the series), while requesting a retransmission of packet 7. However, it is also possible that the transmitter failed to receive any acknowledgments and has retransmitted packet 0. In this latter case, the receiver would accept the wrong packet as packet 8. 193:
total number of packets yet to be acknowledged by the receiver. The receiver informs the transmitter in each acknowledgment packet the current maximum receiver buffer size (window boundary). The TCP header uses a 16 bit field to report the receiver window size to the sender. Therefore, the largest window that can be used is 2 = 64 kilobytes.
928:
A stronger constraint is imposed by the receiver. The operation of the protocol depends on the receiver being able to reliably distinguish new packets (which should be accepted and processed) from retransmissions of old packets (which should be discarded, and the last acknowledgment retransmitted).
1166:
The transmitter alternately sends packets marked "odd" and "even". The acknowledgments likewise say "odd" and "even". Suppose that the transmitter, having sent an odd packet, did not wait for an odd acknowledgment, and instead immediately sent the following even packet. It might then receive an
192:
By placing limits on the number of packets that can be transmitted or received at any given time, a sliding window protocol allows an unlimited number of packets to be communicated using fixed-size sequence numbers. The term "window" on the transmitter side represents the logical boundary of the
188:
Conceptually, each portion of the transmission (packets in most data link layers, but bytes in TCP) is assigned a unique consecutive sequence number, and the receiver uses the numbers to place received packets in the correct order, discarding duplicate packets and identifying missing ones. The
211:
on the network is avoided. The application layer will still be offering data for transmission to TCP without worrying about the network traffic congestion issues as the TCP on sender and receiver side implement sliding windows of packet buffer. The window size may vary dynamically depending on
203:
If the window limit is 10 packets then in slow start mode the transmitter may start transmitting one packet followed by two packets (before transmitting two packets, one packet ack has to be received), followed by three packets and so on until 10 packets. But after reaching 10 packets, further
254:
mechanism reveals corruption, the packet will be ignored by the receiver and a negative or duplicate acknowledgement will be sent by the receiver. The receiver may also be configured to not send any acknowledgement at all. Similarly, the receiver is usually uncertain about whether its
1252:
The advantage, however, is that it is not necessary to discard following correct data for one round-trip time before the transmitter can be informed that a retransmission is required. This is therefore preferred for links with low reliability and/or a high bandwidth-delay product.
1377: ≤6. With this restriction, the receiver knows that if all acknowledgments were lost, the transmitter would have stopped after packet 5. When it receives packet 6, the receiver can infer that the transmitter received the acknowledgment for packet 0 (the transmitter's 204:
transmissions are restricted to one packet transmitted for one ack packet received. In a simulation this appears as if the window is moving by one packet distance for every ack packet received. On the receiver side also the window moves one packet for every packet received.
255:
acknowledgements are being received. It may be that an acknowledgment was sent, but was lost or corrupted in the transmission medium. In this case, the receiver must acknowledge the retransmission to prevent the data being continually resent, but must otherwise ignore it.
1226:≤7. This is because, after transmitting 7 packets, there are 8 possible results: Anywhere from 0 to 7 packets could have been received successfully. This is 8 possibilities, and the transmitter needs enough information in the acknowledgment to distinguish them all. 153:, to be sent without having to wait for an ACK. Each packet receives a sequence number, and the ACKs send back that number. The protocol keeps track of which packets have been ACKed, and when they are received, sends more packets. In this way, the window 1229:
If the transmitter sent 8 packets without waiting for acknowledgment, it could find itself in a quandary similar to the stop-and-wait case: does the acknowledgment mean that all 8 packets were received successfully, or none of them?
1192:=1. The receiver refuses to accept any packet but the next one in sequence. If a packet is lost in transit, following packets are ignored until the missing packet is retransmitted, a minimum loss of one 1400:
makes corruption equivalent to loss), but will never appear out of order. The protocol can be extended to support packet reordering, as long as the distance can be bounded; the sequence number modulus
134:. The paradigm is similar to a window sliding sideways to allow entry of fresh packets and reject the ones that have already been acknowledged. When the receiver verifies the data, it sends an 639:
Techniques for defining "reasonable delay" can be extremely elaborate, but they only affect efficiency; the basic reliability of the sliding window protocol does not depend on the details.
196:
In slow-start mode, the transmitter starts with low packet count and increases the number of packets in each transmission after receiving acknowledgment packets from receiver. For every
200:
received, the window slides by one packet (logically) to transmit one new packet. When the window threshold is reached, the transmitter sends one packet for one ack packet received.
1424: 1448:=1 and if a second packet is lost, no more packets are buffered. This gives most of the performance benefit of the full selective-repeat protocol, with a simpler implementation. 1408:
It is possible to not acknowledge every packet, as long as an acknowledgment is sent eventually if there is a pause. For example, TCP normally acknowledges every second packet.
145:
The time that it takes for the ACK signal to be received may represent a significant amount of time compared to the time needed to send the packet. In this case, the overall
142:
protocol (ARQ), the sender stops after every packet and waits for the receiver to ACK. This ensures packets arrive in the correct order, as only one may be sent at a time.
250:
A transmitter that does not get an acknowledgment cannot know if the receiver actually received the packet; it may be that it was lost or damaged in transmission. If the
160:
Sliding windows are a key part of many protocols. It is a key part of the TCP protocol, which inherently allows packets to arrive out of order, and is also found in many
845:
So far, the protocol has been described as if sequence numbers are of unlimited size, ever-increasing. However, rather than transmitting the full sequence number
1420:. Normally, they are each assigned maximum values that respect that limit, but the working value at any given time may be less than the maximum. In particular: 1167:
acknowledgment saying "expecting an odd packet next". This would leave the transmitter in a quandary: has the receiver received both of the packets, or neither?
247:, the receiver must acknowledge received packets. If the transmitter does not receive an acknowledgment within a reasonable time, it re-sends the data. 291:. The window sizes may vary, but in simpler implementations they are fixed. The window size must be greater than zero for any progress to be made. 1411:
It is common to inform the transmitter immediately if a gap in the packet sequence is detected. HDLC has a special REJ (reject) packet for this.
1286:
uses a 3-bit sequence number, and has optional provision for selective repeat. However, if selective repeat is to be used, the requirement that
914:+1 possible sequence numbers that could arrive at any given time. Thus, the transmitter can unambiguously decode the sequence number as long as 1150:
protocol is actually the simplest possible implementation of it. The transmit window is 1 packet, and the receive window is 1 packet. Thus,
697:, the receive sequence number is increased by 1, and possibly more if further consecutive packets were previously received and stored. If 22: 322:
is one more than the sequence number of the highest sequence number received. For simple receivers that only accept packets in order (
608:
In the absence of a communication error, the transmitter soon receives an acknowledgment for all the packets it has sent, leaving
223:(RTT). The limit on the amount of data that it can send before stopping to wait for an acknowledgment should be larger than the 149:
may be much lower than theoretically possible. To address this, sliding window protocols allow a selected number of packets, the
1065:
The additional insight is that the receiver does not need to distinguish between sequence numbers that are too low (less than
1086:). In either case, the receiver ignores the packet except to retransmit an acknowledgment. Thus, it is only necessary that 1416:
The transmit and receive window sizes may be changed during communication, as long as their sum remains within the limit of
1512:
Comer, Douglas E. "Internetworking with TCP/IP, Volume 1: Principles, Protocols, and Architecture", Prentice Hall, 1995.
374:
When the receiver receives a packet, it updates its variables appropriately and transmits an acknowledgment with the new
1242:. This requires a much more capable receiver, which can accept packets with sequence numbers higher than the current 1517: 1502: 1051:
different sequence numbers that the receiver can receive at any one time. It might therefore seem that we must have
788:, because there is no need to worry about receiving a packet that will never be transmitted; the useful range is 1 ≤ 219:, it is important that the transmitter is not forced to stop sending by the sliding window protocol earlier than one 83: 61: 54: 1331: =7, as is typically used with the go-back-N variant of HDLC. Further suppose that the receiver begins with 301:
is the next packet to be transmitted, i.e. the sequence number of the first packet not yet transmitted. Likewise,
197: 135: 1423:
It is common to reduce the transmit window size to slow down transmission to match the link's speed, avoiding
1441:=2 and buffers packets following a gap, but only allows a single lost packet; while waiting for that packet, 116: 107:. Sliding window protocols are used where reliable in-order delivery of packets is required, such as in the 1283: 1396:
The above examples assumed that packets are never reordered in transmission; they may be lost in transit (
554:: The highest packet sent is limited by the highest acknowledgement received and the transmit window size. 622:. If this does not happen after a reasonable delay, the transmitter must retransmit the packets between 750:
Whether the packet was accepted or not, the receiver transmits an acknowledgment containing the current
1553: 929:
This can be done given knowledge of the transmitter's window size. After receiving a packet numbered
733:
If the packet's number is not within the receive window, the receiver discards it and does not modify
189:
problem with this is that there is no limit on the size of the sequence number that can be required.
130:, along with additional data that allows the receiver to ensure it was received correctly, perhaps a 515:: The span of fully received packets cannot extend beyond the end of the partially received packets. 1470: 811: 309: 240: 139: 48: 224: 1548: 1460: 161: 65: 757:. (The acknowledgment may also include information about additional packets received between 112: 1434:
One common simplification of selective-repeat is so called SREJ-REJ ARQ. This operates with
228: 220: 492:: The highest acknowledgement received by the transmitter cannot be higher than the highest 1239: 315:
The receiver may also keep track of the highest sequence number yet received; the variable
104: 8: 1428: 208: 531:: The highest packet received cannot be higher than the highest packet yet to be sent. 1513: 1498: 1147: 101: 138:, or "ACK", back to the sender to indicate it can send the next packet. In a simple 18:
Type of error-detection protocol at the data link layer, and transport layer for TCP
1348:
Now suppose that the receiver sees the following series of packets (all modulo 8):
119:(TCP). They are also used to improve efficiency when the channel may include high 1397: 1196:. For this reason, it is inefficient on links that suffer frequent packet loss. 1193: 251: 227:
of the communications link. If it is not, the protocol will limit the effective
108: 690:.) If it falls within the window, the receiver accepts it. If it is numbered 1542: 1475: 1175: 381:. The transmitter keeps track of the highest acknowledgment it has received 244: 120: 26: 21:"Sliding window" redirects here. For use in natural language processing, see 872:
For example, the transmitter will only receive acknowledgments in the range
1465: 708:, the packet is stored until all preceding packets have been received. If 651:
is received, the receiver checks to see if it falls in the receive window,
126:
Packet-based systems are based on the idea of sending a batch of data, the
1204:
Suppose that we are using a 3-bit sequence number, such as is typical for
172:
as a way of improving efficiency compared to non-windowed protocols like
1384: ≥1), and thus the following packet numbered 0 must be packet 8. 866: 216: 146: 1146:
Although commonly distinguished from the sliding-window protocol, the
165: 1267:
lost packets that can be tolerated. Thus, small values are popular;
1006:
cannot be higher than the highest acknowledgment ever sent, which is
1495: 1154:= 2 possible sequence numbers (conveniently represented by a single 388:. The transmitter knows that all packets up to, but not including 131: 1532: 816: 563:
Whenever the transmitter has data to send, it may transmit up to
263:
The transmitter and receiver each have a current sequence number
177: 676:. (The simplest receivers only have to keep track of one value 173: 169: 1141: 983:
The lowest sequence number we will ever receive in future is
1205: 1013:. So the highest sequence number we could possibly see is 395:
have been received, but is uncertain about packets between
1155: 1238:
The most general case of the sliding window protocol is
308:
is the first packet not yet received. Both numbers are
1392:
There are many ways that the protocol can be extended:
1324: =2, but an unmodified transmitter is used with 774:
Note that there is no point having the receive window
1405:
must be expanded by the maximum misordering distance.
157:
along the stream of packets making up the transfer.
277:, respectively. They each also have a window size 1072:) or that are too high (greater than or equal to 805: 343:> 1. Note the distinction: all packets below 1540: 999:The receiver also knows that the transmitter's 433:The sequence numbers always obey the rule that 207:The sliding window method ensures that traffic 1529:RFC 1323 - TCP Extensions for High Performance 1370:The solution is for the transmitter to limit 849:in messages, it is possible to transmit only 1249:and store them until the gap is filled in. 577:. That is, it may transmit packet number 570:packets ahead of the latest acknowledgment 23:Sliding window based part-of-speech tagging 1494:Peterson, Larry L. & Davie, Bruce S. " 1142:The simplest sliding window: stop-and-wait 84:Learn how and when to remove this message 815: 558: 47:This article includes a list of general 1263:need only be larger than the number of 1062:. However, the actual limit is lower. 886:, inclusive. Since it guarantees that 239:In any communication protocol based on 1541: 1300: ≤ 8 must be maintained; if 1277: 1199: 25:. For Sliding Window Compression, see 1533:TCP window scaling and broken routers 642: 350:have been received, no packets above 258: 1178:is the sliding window protocol with 1161: 312:with time; they only ever increase. 33: 1233: 980:will never again be retransmitted. 771:, but that only helps efficiency.) 371:, some packets have been received. 13: 53:it lacks sufficient corresponding 14: 1565: 1523: 820:Sequence numbers modulo 4, with 781:larger than the transmit window 357:have been received, and between 183: 38: 1122:below), this can permit larger 1488: 1119: 806:Sequence number range required 1: 1481: 1387: 647:Every time a packet numbered 499:acknowledged by the receiver. 234: 117:Transmission Control Protocol 100:is a feature of packet-based 1170: 7: 1454: 1136: 1104:. As it is common to have 719:, the latter is updated to 10: 1570: 1497:", Morgan Kaufmann, 2000. 969:. Thus, packets numbered 933:, the receiver knows that 809: 329:= 1), this is the same as 294:As typically implemented, 20: 215:For the highest possible 1471:Serial number arithmetic 1314:must be decreased to 6. 812:serial number arithmetic 336:, but can be greater if 310:monotonically increasing 241:automatic repeat request 140:automatic repeat request 225:bandwidth-delay product 162:file transfer protocols 98:sliding window protocol 68:more precise citations. 1461:Federal Standard 1037C 1282:The extremely popular 842: 819: 559:Transmitter operation 221:round-trip delay time 136:acknowledgment signal 1240:Selective Repeat ARQ 907:, there are at most 115:) as well as in the 1307:is increased to 2, 1185:>1, but a fixed 1219:=1, we must limit 857:, for some finite 843: 643:Receiver operation 259:Protocol operation 1554:Data transmission 1278:Ambiguity example 1200:Ambiguity example 1162:Ambiguity example 1148:stop-and-wait ARQ 1044:Thus, there are 2 212:network traffic. 102:data transmission 94: 93: 86: 1561: 1505: 1492: 1256:The window size 1234:Selective repeat 1158:) are required. 958: >  937: <  918: >  89: 82: 78: 75: 69: 64:this article by 55:inline citations 42: 41: 34: 1569: 1568: 1564: 1563: 1562: 1560: 1559: 1558: 1539: 1538: 1526: 1509: 1508: 1493: 1489: 1484: 1457: 1446: 1439: 1398:error detection 1390: 1382: 1375: 1365: 1343: 1336: 1329: 1322: 1312: 1305: 1298: 1291: 1280: 1272: 1261: 1247: 1236: 1224: 1217: 1202: 1194:round-trip time 1190: 1183: 1173: 1164: 1144: 1139: 1129:within a fixed 1127: 1116: 1109: 1102: 1095: 1084: 1077: 1070: 1060: 1049: 1039: 1032: 1025: 1018: 1011: 1004: 995: 988: 978: 967: 956: 949: 942: 923: 912: 905: 898: 891: 884: 877: 853: mod  839: 832: 827:=1. Initially, 825: 814: 808: 800: 793: 786: 779: 769: 762: 755: 745: 738: 724: 717: 706: 695: 688: 681: 674: 667: 656: 645: 634: 627: 620: 613: 603: 596: 589: 582: 575: 568: 561: 552: 545: 538: 529: 522: 513: 506: 497: 490: 483: 473: 466: 459: 452: 445: 438: 428: 421: 414: 407: 400: 393: 386: 379: 369: 362: 355: 348: 341: 334: 327: 320: 306: 299: 289: 282: 275: 268: 261: 252:error detection 237: 186: 109:data link layer 90: 79: 73: 70: 60:Please help to 59: 43: 39: 30: 19: 12: 11: 5: 1567: 1557: 1556: 1551: 1537: 1536: 1530: 1525: 1524:External links 1522: 1521: 1520: 1507: 1506: 1486: 1485: 1483: 1480: 1479: 1478: 1473: 1468: 1463: 1456: 1453: 1452: 1451: 1450: 1449: 1444: 1437: 1432: 1414: 1413: 1412: 1406: 1389: 1386: 1380: 1373: 1363: 1358: 1357: 1352:0 1 2 3 4 5 6 1341: 1334: 1327: 1320: 1310: 1303: 1296: 1289: 1279: 1276: 1274:=2 is common. 1270: 1259: 1245: 1235: 1232: 1222: 1215: 1208:. This gives 1201: 1198: 1188: 1181: 1172: 1169: 1163: 1160: 1143: 1140: 1138: 1135: 1125: 1114: 1107: 1100: 1093: 1082: 1075: 1068: 1058: 1055: ≥ 2 1047: 1037: 1030: 1023: 1016: 1009: 1002: 993: 986: 976: 965: 954: 947: 940: 921: 910: 903: 896: 889: 882: 875: 837: 830: 823: 810:Main article: 807: 804: 798: 791: 784: 777: 767: 760: 753: 743: 736: 722: 715: 704: 693: 686: 679: 672: 665: 654: 644: 641: 632: 625: 618: 611: 601: 594: 587: 580: 573: 566: 560: 557: 556: 555: 550: 543: 536: 532: 527: 520: 516: 511: 504: 500: 495: 488: 481: 471: 464: 457: 450: 443: 436: 426: 419: 412: 405: 398: 391: 384: 377: 367: 360: 353: 346: 339: 332: 325: 318: 304: 297: 287: 280: 273: 266: 260: 257: 236: 233: 185: 182: 92: 91: 46: 44: 37: 17: 9: 6: 4: 3: 2: 1566: 1555: 1552: 1550: 1549:Communication 1547: 1546: 1544: 1534: 1531: 1528: 1527: 1519: 1518:0-13-216987-8 1515: 1511: 1510: 1504: 1503:1-55860-577-0 1500: 1496: 1491: 1487: 1477: 1476:TCP Fast Open 1474: 1472: 1469: 1467: 1464: 1462: 1459: 1458: 1447: 1440: 1433: 1430: 1426: 1422: 1421: 1419: 1415: 1410: 1409: 1407: 1404: 1399: 1395: 1394: 1393: 1385: 1383: 1376: 1368: 1366: 1355: 1351: 1350: 1349: 1346: 1344: 1337: 1330: 1323: 1317:Suppose that 1315: 1313: 1306: 1299: 1292: 1285: 1284:HDLC protocol 1275: 1273: 1266: 1262: 1254: 1250: 1248: 1241: 1231: 1227: 1225: 1218: 1212:=2=8. Since 1211: 1207: 1197: 1195: 1191: 1184: 1177: 1176:Go-Back-N ARQ 1168: 1159: 1157: 1153: 1149: 1134: 1132: 1128: 1121: 1117: 1110: 1103: 1096: 1090: ≥  1089: 1085: 1078: 1071: 1063: 1061: 1054: 1050: 1042: 1040: 1033: 1027: ≤  1026: 1019: 1012: 1005: 997: 996: 989: 981: 979: 972: 968: 961: 957: 950: 943: 936: 932: 926: 924: 917: 913: 906: 900: ≤  899: 892: 885: 878: 870: 868: 865:is usually a 864: 860: 856: 852: 848: 840: 833: 826: 818: 813: 803: 801: 794: 787: 780: 772: 770: 763: 756: 748: 746: 739: 731: 729: 725: 718: 711: 707: 700: 696: 689: 682: 675: 668: 661: 657: 650: 640: 637: 635: 628: 621: 614: 606: 604: 597: 590: 583: 576: 569: 553: 546: 539: 533: 530: 523: 517: 514: 507: 501: 498: 491: 484: 478: 477: 476: 474: 467: 460: 453: 446: 439: 431: 429: 422: 415: 408: 401: 394: 387: 380: 372: 370: 363: 356: 349: 342: 335: 328: 321: 313: 311: 307: 300: 292: 290: 283: 276: 269: 256: 253: 248: 246: 245:error control 242: 232: 231:of the link. 230: 226: 222: 218: 213: 210: 205: 201: 199: 194: 190: 184:Basic concept 181: 179: 175: 171: 167: 163: 158: 156: 152: 148: 143: 141: 137: 133: 129: 124: 122: 118: 114: 110: 106: 103: 99: 88: 85: 77: 67: 63: 57: 56: 50: 45: 36: 35: 32: 28: 27:LZ77 and LZ78 24: 16: 1490: 1466:Compound TCP 1442: 1435: 1417: 1402: 1391: 1378: 1371: 1369: 1361: 1359: 1353: 1347: 1339: 1332: 1325: 1318: 1316: 1308: 1301: 1294: 1287: 1281: 1268: 1264: 1257: 1255: 1251: 1243: 1237: 1228: 1220: 1213: 1209: 1203: 1186: 1179: 1174: 1165: 1151: 1145: 1130: 1123: 1112: 1105: 1098: 1091: 1087: 1080: 1073: 1066: 1064: 1056: 1052: 1045: 1043: 1035: 1028: 1021: 1014: 1007: 1000: 998: 991: 984: 982: 974: 970: 963: 959: 952: 945: 938: 934: 930: 927: 919: 915: 908: 901: 894: 887: 880: 873: 871: 862: 858: 854: 850: 846: 844: 835: 828: 821: 796: 789: 782: 775: 773: 765: 758: 751: 749: 741: 734: 732: 727: 720: 713: 709: 702: 698: 691: 684: 677: 670: 663: 659: 652: 648: 646: 638: 630: 623: 616: 609: 607: 599: 592: 585: 578: 571: 564: 562: 548: 541: 534: 525: 518: 509: 502: 493: 486: 479: 475:. That is: 469: 462: 455: 448: 441: 434: 432: 424: 417: 410: 403: 396: 389: 382: 375: 373: 365: 358: 351: 344: 337: 330: 323: 316: 314: 302: 295: 293: 285: 278: 271: 264: 262: 249: 238: 214: 206: 202: 195: 191: 187: 176:. See also 159: 154: 150: 144: 127: 125: 97: 95: 80: 71: 52: 31: 15: 1345: =0. 1265:consecutive 584:as long as 113:OSI layer 2 74:August 2010 66:introducing 1543:Categories 1482:References 1429:congestion 1425:saturation 1388:Extensions 1118:(e.g. see 867:power of 2 235:Motivation 217:throughput 209:congestion 198:ack packet 147:throughput 49:references 1171:Go-Back-N 1120:Go-Back-N 615:equal to 229:bandwidth 105:protocols 1455:See also 1360:Because 1338: = 1137:Examples 132:checksum 1354:(pause) 409:; i.e. 178:SEAlink 121:latency 62:improve 1535:, 2004 1516:  1501:  174:XMODEM 170:ZMODEM 166:UUCP-g 155:slides 151:window 128:packet 51:, but 951:, so 701:> 662:< 591:< 524:< 454:< 164:like 1514:ISBN 1499:ISBN 1206:HDLC 1111:< 861:. ( 764:and 730:+1. 629:and 402:and 364:and 284:and 270:and 243:for 168:and 1427:or 1156:bit 879:to 869:.) 740:or 1545:: 1133:. 1041:. 925:. 841:=0 802:. 795:≤ 747:. 658:≤ 636:. 605:. 547:+ 540:≤ 508:≤ 485:≤ 468:+ 461:≤ 447:≤ 440:≤ 430:. 423:≤ 416:≤ 180:. 123:. 96:A 1445:r 1443:w 1438:r 1436:w 1431:. 1418:N 1403:N 1381:a 1379:n 1374:t 1372:w 1364:r 1362:w 1356:0 1342:s 1340:n 1335:r 1333:n 1328:t 1326:w 1321:r 1319:w 1311:t 1309:w 1304:r 1302:w 1297:r 1295:n 1293:+ 1290:t 1288:n 1271:r 1269:w 1260:r 1258:w 1246:r 1244:n 1223:t 1221:w 1216:r 1214:w 1210:N 1189:r 1187:w 1182:t 1180:w 1152:N 1131:N 1126:t 1124:w 1115:t 1113:w 1108:r 1106:w 1101:r 1099:w 1097:+ 1094:t 1092:w 1088:N 1083:r 1081:w 1079:+ 1076:s 1074:n 1069:r 1067:n 1059:t 1057:w 1053:N 1048:t 1046:w 1038:t 1036:w 1034:+ 1031:s 1029:n 1024:t 1022:w 1020:+ 1017:r 1015:n 1010:r 1008:n 1003:a 1001:n 994:t 992:w 990:− 987:s 985:n 977:t 975:w 973:− 971:x 966:t 964:w 962:− 960:x 955:a 953:n 948:t 946:w 944:+ 941:a 939:n 935:x 931:x 922:t 920:w 916:N 911:t 909:w 904:t 902:w 897:a 895:n 893:− 890:t 888:n 883:t 881:n 876:a 874:n 863:N 859:N 855:N 851:x 847:x 838:r 836:n 834:= 831:t 829:n 824:r 822:w 799:t 797:w 792:r 790:w 785:t 783:w 778:r 776:w 768:s 766:n 761:r 759:n 754:r 752:n 744:s 742:n 737:r 735:n 728:x 726:= 723:s 721:n 716:s 714:n 712:≥ 710:x 705:r 703:n 699:x 694:r 692:n 687:s 685:n 683:= 680:r 678:n 673:r 671:w 669:+ 666:r 664:n 660:x 655:r 653:n 649:x 633:t 631:n 626:a 624:n 619:t 617:n 612:a 610:n 602:t 600:w 598:+ 595:a 593:n 588:t 586:n 581:t 579:n 574:a 572:n 567:t 565:w 551:t 549:w 544:a 542:n 537:t 535:n 528:t 526:n 521:s 519:n 512:s 510:n 505:r 503:n 496:r 494:n 489:r 487:n 482:a 480:n 472:t 470:w 465:a 463:n 458:t 456:n 451:s 449:n 444:r 442:n 437:a 435:n 427:s 425:n 420:r 418:n 413:a 411:n 406:s 404:n 399:a 397:n 392:a 390:n 385:a 383:n 378:r 376:n 368:s 366:n 361:r 359:n 354:s 352:n 347:r 345:n 340:r 338:w 333:r 331:n 326:r 324:w 319:s 317:n 305:r 303:n 298:t 296:n 288:r 286:w 281:t 279:w 274:r 272:n 267:t 265:n 111:( 87:) 81:( 76:) 72:( 58:. 29:.

Index

Sliding window based part-of-speech tagging
LZ77 and LZ78
references
inline citations
improve
introducing
Learn how and when to remove this message
data transmission
protocols
data link layer
OSI layer 2
Transmission Control Protocol
latency
checksum
acknowledgment signal
automatic repeat request
throughput
file transfer protocols
UUCP-g
ZMODEM
XMODEM
SEAlink
ack packet
congestion
throughput
round-trip delay time
bandwidth-delay product
bandwidth
automatic repeat request
error control

Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.