計算機網(wǎng)絡(luò)參考tanenbaum英文chapter6_第1頁
計算機網(wǎng)絡(luò)參考tanenbaum英文chapter6_第2頁
計算機網(wǎng)絡(luò)參考tanenbaum英文chapter6_第3頁
計算機網(wǎng)絡(luò)參考tanenbaum英文chapter6_第4頁
計算機網(wǎng)絡(luò)參考tanenbaum英文chapter6_第5頁
已閱讀5頁,還剩61頁未讀, 繼續(xù)免費閱讀

下載本文檔

版權(quán)說明:本文檔由用戶提供并上傳,收益歸屬內(nèi)容提供方,若內(nèi)容存在侵權(quán),請進行舉報或認領(lǐng)

文檔簡介

1、The Transport LayerChapter 6The Transport ServiceServices Provided to the Upper LayersTransport Service PrimitivesBerkeley SocketsAn Example of Socket Programming: An Internet File ServerServices Provided to the Upper LayersThe network, transport, and application layers.Transport Service PrimitivesT

2、he primitives for a simple transport service.Transport Service Primitives (2)The nesting of TPDUs, packets, and frames.Transport Service Primitives (3)A state diagram for a simple connection management scheme. Transitions labeled in italics are caused by packet arrivals. The solid lines show the cli

3、ents state sequence. The dashed lines show the servers state sequence. Berkeley SocketsThe socket primitives for TCP.Socket Programming Example:Internet File ServerClient code using sockets.6-6-1Socket Programming Example:Internet File Server (2)Client code using sockets.Elements of Transport Protoc

4、olsAddressingConnection EstablishmentConnection ReleaseFlow Control and BufferingMultiplexingCrash RecoveryTransport Protocol(a) Environment of the data link layer.(b) Environment of the transport layer.AddressingTSAPs, NSAPs and transport connections.Connection EstablishmentHow a user process in ho

5、st 1 establishes a connection with a time-of-day server in host 2.Connection Establishment (2)(a) TPDUs may not enter the forbidden region.(b) The resynchronization problem.Connection Establishment (3)Three protocol scenarios for establishing a connection using a three-way handshake. CR denotes CONN

6、ECTION REQUEST. (a) Normal operation, (b) Old CONNECTION REQUEST appearing out of nowhere. (c) Duplicate CONNECTION REQUEST and duplicate ACK.Connection ReleaseAbrupt disconnection with loss of data.Connection Release (2)The two-army problem.Connection Release (3)Four protocol scenarios for releasin

7、g a connection. (a) Normal case of a three-way handshake. (b) final ACK lost.6-14, a, bConnection Release (4)(c) Response lost. (d) Response lost and subsequent DRs lost.6-14, c,dFlow Control and Buffering(a) Chained fixed-size buffers. (b) Chained variable-sized buffers. (c) One large circular buff

8、er per connection.Flow Control and Buffering (2)Dynamic buffer allocation. The arrows show the direction of transmission. An ellipsis () indicates a lost TPDU.Multiplexing(a) Upward multiplexing. (b) Downward multiplexing.Crash RecoveryDifferent combinations of client and server strategy.A Simple Tr

9、ansport ProtocolThe Example Service PrimitivesThe Example Transport EntityThe Example as a Finite State MachineThe Example Transport EntityThe network layer packets used in our example.The Example Transport Entity (2)Each connection is in one of seven states:1.Idle Connection not established yet.2.W

10、aiting CONNECT has been executed, CALL REQUEST sent.3.Queued A CALL REQUEST has arrived; no LISTEN yet.4.Established The connection has been established.5.Sending The user is waiting for permission to send a packet.6.Receiving A RECEIVE has been done.7.DISCONNECTING a DISCONNECT has been done locall

11、y.The Example Transport Entity (3)The Example Transport Entity (4)The Example Transport Entity (5)The Example Transport Entity (6)The Example Transport Entity (7)The Example Transport Entity (8)The Example Transport Entity (9)The Example Transport Entity (10)The Example as a Finite State MachineThe

12、example protocol as a finite state machine. Each entry has an optional predicate, an optional action, and the new state. The tilde indicates that no major action is taken. An overbar above a predicate indicate the negation of the predicate. Blank entries correspond to impossible or invalid events.Th

13、e Example as a Finite State Machine (2)The example protocol in graphical form. Transitions that leave the connection state unchanged have been omitted for simplicity.The Internet Transport Protocols: UDPIntroduction to UDPRemote Procedure CallThe Real-Time Transport ProtocolIntroduction to UDPThe UD

14、P header.Remote Procedure CallSteps in making a remote procedure call. The stubs are shaded.The Real-Time Transport Protocol(a) The position of RTP in the protocol stack. (b) Packet nesting.The Real-Time Transport Protocol (2)The RTP header.The Internet Transport Protocols: TCPIntroduction to TCPThe

15、 TCP Service ModelThe TCP ProtocolThe TCP Segment HeaderTCP Connection EstablishmentTCP Connection ReleaseTCP Connection Management ModelingTCP Transmission PolicyTCP Congestion ControlTCP Timer ManagementWireless TCP and UDPTransactional TCPThe TCP Service ModelSome assigned ports.PortProtocolUse21

16、FTPFile transfer23TelnetRemote login25SMTPE-mail69TFTPTrivial File Transfer Protocol79FingerLookup info about a user80HTTPWorld Wide Web110POP-3Remote e-mail access119NNTPUSENET newsThe TCP Service Model (2)(a) Four 512-byte segments sent as separate IP datagrams.(b) The 2048 bytes of data delivered

17、 to the application in a single READ CALL.The TCP Segment HeaderTCP Header.The TCP Segment Header (2)The pseudoheader included in the TCP checksum.TCP Connection Establishment(a) TCP connection establishment in the normal case.(b) Call collision.6-31TCP Connection Management ModelingThe states used

18、in the TCP connection management finite state machine.TCP Connection Management Modeling (2)TCP connection management finite state machine. The heavy solid line is the normal path for a client. The heavy dashed line is the normal path for a server. The light lines are unusual events. Each transition

19、 is labeled by the event causing it and the action resulting from it, separated by a slash.TCP Transmission PolicyWindow management in TCP.TCP Transmission Policy (2)Silly window syndrome.TCP Congestion Control(a) A fast network feeding a low capacity receiver.(b) A slow network feeding a high-capac

20、ity receiver.TCP Congestion Control (2)An example of the Internet congestion algorithm.TCP Timer Management(a) Probability density of ACK arrival times in the data link layer. (b) Probability density of ACK arrival times for TCP.Wireless TCP and UDPSplitting a TCP connection into two connections.Tra

21、nsitional TCP(a) RPC using normal TPC.(b) RPC using T/TCP.Performance IssuesPerformance Problems in Computer NetworksNetwork Performance MeasurementSystem Design for Better PerformanceFast TPDU ProcessingProtocols for Gigabit NetworksPerformance Problems in Computer NetworksThe state of transmitting

22、 one megabit from San Diego to Boston(a) At t = 0, (b) After 500 sec, (c) After 20 msec, (d) after 40 msec.Network Performance MeasurementThe basic loop for improving network performance.1.Measure relevant network parameters, performance.2.Try to understand what is going on.3.Change one parameter.System Design for Better PerformanceRules:1.CPU speed is more important than network speed.2.Reduce packet count to reduce software overhead.3.Minimiz

溫馨提示

  • 1. 本站所有資源如無特殊說明,都需要本地電腦安裝OFFICE2007和PDF閱讀器。圖紙軟件為CAD,CAXA,PROE,UG,SolidWorks等.壓縮文件請下載最新的WinRAR軟件解壓。
  • 2. 本站的文檔不包含任何第三方提供的附件圖紙等,如果需要附件,請聯(lián)系上傳者。文件的所有權(quán)益歸上傳用戶所有。
  • 3. 本站RAR壓縮包中若帶圖紙,網(wǎng)頁內(nèi)容里面會有圖紙預(yù)覽,若沒有圖紙預(yù)覽就沒有圖紙。
  • 4. 未經(jīng)權(quán)益所有人同意不得將文件中的內(nèi)容挪作商業(yè)或盈利用途。
  • 5. 人人文庫網(wǎng)僅提供信息存儲空間,僅對用戶上傳內(nèi)容的表現(xiàn)方式做保護處理,對用戶上傳分享的文檔內(nèi)容本身不做任何修改或編輯,并不能對任何下載內(nèi)容負責(zé)。
  • 6. 下載文件中如有侵權(quán)或不適當(dāng)內(nèi)容,請與我們聯(lián)系,我們立即糾正。
  • 7. 本站不保證下載資源的準(zhǔn)確性、安全性和完整性, 同時也不承擔(dān)用戶因使用這些下載資源對自己和他人造成任何形式的傷害或損失。

評論

0/150

提交評論