通訊網(wǎng)絡(luò)實驗報告實驗一隱終端和裸露終端問題剖析一、實驗?zāi)康?、認識無線網(wǎng)絡(luò)中的載波檢測體制；2、熟習節(jié)點的傳輸范圍、矛盾擾亂范圍、載波檢測范圍和噪聲擾亂范圍的觀點；3、認識載波檢測接入體系中存在的隱終端問題和裸露終端問題；4、聯(lián)合仿真切驗剖析載波檢測無線網(wǎng)絡(luò)中的隱終端問題和裸露終端問題。二、實驗結(jié)果Node:1,Layer:AppCbrClient,(0)Serveraddress:2Node:1,Layer:AppCbrClient,(0)Firstpacketsentat[s]:Node:1,Layer:AppCbrClient,(0)Lastpacketsentat[s]:Node:1,Layer:AppCbrClient,(0)Sessionstatus:NotclosedNode:1,Layer:AppCbrClient,(0)Totalnumberofbytessent:5120000Node:1,Layer:AppCbrClient,(0)Totalnumberofpacketssent:10000Node:1,Layer:AppCbrClient,(0)Throughput(bitspersecond):409600Node:2,Layer:AppCbrServer,(0)Clientaddress:1Node:2,Layer:AppCbrServer,(0)Firstpacketreceivedat[s]:Node:2,Layer:AppCbrServer,(0)Lastpacketreceivedat[s]:Node:2,Layer:AppCbrServer,(0)Averageend-to-enddelay[s]:Node:2,Layer:AppCbrServer,(0)Sessionstatus:NotclosedNode:2,Layer:AppCbrServer,(0)Totalnumberofbytesreceived:4975616Node:2,Layer:AppCbrServer,(0)Totalnumberofpacketsreceived:9718Node:2,Layer:AppCbrServer,(0)Throughput(bitspersecond):398078Node:3,Layer:AppCbrClient,(0)Serveraddress:4Node:3,Layer:AppCbrClient,(0)Firstpacketsentat[s]:Node:3,Layer:AppCbrClient,(0)Lastpacketsentat[s]:Node:3,Layer:AppCbrClient,(0)Sessionstatus:NotclosedNode:3,Layer:AppCbrClient,(0)Totalnumberofbytessent:5120000Node:3,Layer:AppCbrClient,(0)Totalnumberofpacketssent:10000Node:3,Layer:AppCbrClient,(0)Throughput(bitspersecond):409600Node:4,Layer:AppCbrServer,(0)Clientaddress:3Node:4,Layer:AppCbrServer,(0)Firstpacketreceivedat[s]:Node:4,Layer:AppCbrServer,(0)Lastpacketreceivedat[s]:Node:4,Layer:AppCbrServer,(0)Averageend-to-enddelay[s]:Node:4,Layer:AppCbrServer,(0)Sessionstatus:NotclosedNode:4,Layer:AppCbrServer,(0)Totalnumberofbytesreceived:5120000Node:4,Layer:AppCbrServer,(0)Totalnumberofpacketsreceived:10000Node:

4,Layer:

AppCbrServer,(0)Throughput(bitspersecond):409612三、實驗結(jié)果剖析經(jīng)過仿真結(jié)果能夠看出，節(jié)點

2沒法收到數(shù)據(jù)。因為節(jié)點

3是節(jié)點

1的一個隱終端，節(jié)點

1沒法經(jīng)過物理載波檢測偵聽到節(jié)點

3的發(fā)送，且節(jié)點

3在節(jié)點

2的傳輸范圍外，節(jié)點3沒法經(jīng)過虛構(gòu)載波檢測延緩發(fā)送，因此在節(jié)點

1傳輸數(shù)據(jù)的過程中，節(jié)點

3達成退避發(fā)送時將惹起矛盾。四、思慮題1、RTS/CTS能完整解決隱終端問題嗎？假如不可以，請說明原因。從理論剖析上看，RTS/CTS協(xié)議仿佛能夠完整解決數(shù)據(jù)鏈隱蔽終端問題，但是在實質(zhì)網(wǎng)絡(luò)中并不是這樣，特別是在AdHoc網(wǎng)絡(luò)中。以節(jié)點為中心，存在發(fā)送地區(qū)和擾亂區(qū)域。在發(fā)送地區(qū)內(nèi)，在沒有擾亂的狀況下，數(shù)據(jù)包可正常收發(fā)；該地區(qū)的大小由站點的功率等參數(shù)確立，可視為定值。擾亂地區(qū)是有關(guān)于接受節(jié)點而言的，在該地區(qū)內(nèi)，節(jié)點能夠遇到來自非有關(guān)節(jié)點發(fā)送的數(shù)據(jù)的擾亂，造成矛盾、丟包。RTS/CTS對隱蔽終端問題的屏蔽其實是成立在兩地區(qū)相等的基礎(chǔ)上的，即全部的隱蔽終端都位于接受節(jié)點發(fā)送范圍內(nèi)。其中假定其實不可立，擾亂地區(qū)與收發(fā)節(jié)點間距有關(guān)。實驗二無線局域網(wǎng)DCF協(xié)議飽和吞吐量考證一、實驗?zāi)康?、認識IEEEDCF協(xié)議的基來源理。2、理解網(wǎng)絡(luò)飽和吞吐量的觀點。3、經(jīng)過仿真對DCF協(xié)議飽和吞吐量的二維馬爾可夫鏈模型進行考證。二、實驗結(jié)果Node:1,Layer:AppCbrClient,(4)Serveraddress:55Node:1,Layer:AppCbrClient,(4)Firstpacketsentat[s]:Node:1,Layer:AppCbrClient,(4)Lastpacketsentat[s]:Node:1,Layer:AppCbrClient,(4)Sessionstatus:NotclosedNode:1,Layer:AppCbrClient,(4)Totalnumberofbytessent:5120000Node:1,Layer:AppCbrClient,(4)Totalnumberofpacketssent:10000Node:1,Layer:AppCbrClient,(4)Throughput(bitspersecond):409600Node:1,Layer:AppCbrClient,(3)Serveraddress:54Node:1,Layer:AppCbrClient,(3)Firstpacketsentat[s]:Node:1,Layer:AppCbrClient,(3)Lastpacketsentat[s]:Node:1,Layer:AppCbrClient,(3)Sessionstatus:NotclosedNode:1,Layer:AppCbrClient,(3)Totalnumberofbytessent:5120000Node:1,Layer:AppCbrClient,(3)Totalnumberofpacketssent:10000Node:1,Layer:AppCbrClient,(3)Throughput(bitspersecond):409600Node:1,Layer:AppCbrClient,(2)Serveraddress:53Node:1,Layer:AppCbrClient,(2)Firstpacketsentat[s]:Node:1,Layer:AppCbrClient,(2)Lastpacketsentat[s]:Node:1,Layer:AppCbrClient,(2)Sessionstatus:NotclosedNode:1,Layer:AppCbrClient,(2)Totalnumberofbytessent:5120000Node:1,Layer:AppCbrClient,(2)Totalnumberofpacketssent:10000Node:1,Layer:AppCbrClient,(2)Throughput(bitspersecond):409600Node:1,Layer:AppCbrClient,(1)Serveraddress:52Node:1,Layer:AppCbrClient,(1)Firstpacketsentat[s]:Node:1,Layer:AppCbrClient,(1)Lastpacketsentat[s]:Node:1,Layer:AppCbrClient,(1)Sessionstatus:NotclosedNode:1,Layer:AppCbrClient,(1)Totalnumberofbytessent:5120000Node:1,Layer:AppCbrClient,(1)Totalnumberofpacketssent:10000Node:1,Layer:AppCbrClient,(1)Throughput(bitspersecond):409600Node:1,Layer:AppCbrClient,(0)Serveraddress:51Node:1,Layer:AppCbrClient,(0)Firstpacketsentat[s]:Node:1,Layer:AppCbrClient,(0)Lastpacketsentat[s]:Node:1,Layer:AppCbrClient,(0)Sessionstatus:NotclosedNode:1,Layer:AppCbrClient,(0)Totalnumberofbytessent:5120000Node:1,Layer:AppCbrClient,(0)Totalnumberofpacketssent:10000Node:1,Layer:AppCbrClient,(0)Throughput(bitspersecond):409600Node:51,Layer:AppCbrServer,(0)Clientaddress:1Node:51,Layer:AppCbrServer,(0)Firstpacketreceivedat[s]:Node:51,Layer:AppCbrServer,(0)Lastpacketreceivedat[s]:Node:51,Layer:AppCbrServer,(0)Averageend-to-enddelay[s]:Node:51,Layer:AppCbrServer,(0)Sessionstatus:NotclosedNode:51,Layer:AppCbrServer,(0)Totalnumberof5102592Node:51,Layer:AppCbrServer,(0)Totalnumberof9966Node:51,Layer:AppCbrServer,(0)Throughput(bitspersecond):408219Node:52,Layer:AppCbrServer,(1)Clientaddress:1Node:52,Layer:AppCbrServer,(1)Firstpacketreceivedat[s]:Node:52,Layer:AppCbrServer,(1)Lastpacketreceivedat[s]:Node:52,Layer:AppCbrServer,(1)Averageend-to-enddelay[s]:Node:52,Layer:AppCbrServer,(1)Sessionstatus:NotclosedNode:52,Layer:AppCbrServer,(1)Totalnumberof5102592Node:52,Layer:AppCbrServer,(1)Totalnumberof

bytesreceived:packetsreceived:bytesreceived:packetsreceived:9966Node:52,Layer:AppCbrServer,(1)Throughput(bitspersecond):408233Node:53,Layer:AppCbrServer,(2)Clientaddress:1Node:53,Layer:AppCbrServer,(2)Firstpacketreceivedat[s]:Node:53,Layer:AppCbrServer,(2)Lastpacketreceivedat[s]:Node:53,Layer:AppCbrServer,(2)Averageend-to-enddelay[s]:Node:53,Layer:AppCbrServer,(2)Sessionstatus:NotclosedNode:53,Layer:AppCbrServer,(2)Totalnumberofbytesreceived:3926016Node:53,Layer:AppCbrServer,(2)Totalnumberofpacketsreceived:7668Node:53,Layer:AppCbrServer,(2)Throughput(bitspersecond):314112Node:54,Layer:AppCbrServer,(3)Clientaddress:1Node:54,Layer:AppCbrServer,(3)Firstpacketreceivedat[s]:Node:54,Layer:AppCbrServer,(3)Lastpacketreceivedat[s]:Node:54,Layer:AppCbrServer,(3)Averageend-to-enddelay[s]:Node:54,Layer:AppCbrServer,(3)Sessionstatus:NotclosedNode:54,Layer:AppCbrServer,(3)Totalnumberofbytesreceived:22016Node:54,Layer:AppCbrServer,(3)Totalnumberofpacketsreceived:43Node:54,Layer:AppCbrServer,(3)Throughput(bitspersecond):1761Node:55,Layer:AppCbrServer,(4)Clientaddress:1Node:55,Layer:AppCbrServer,(4)Firstpacketreceivedat[s]:Node:55,Layer:AppCbrServer,(4)Lastpacketreceivedat[s]:Node:55,Layer:AppCbrServer,(4)Averageend-to-enddelay[s]:Node:55,Layer:AppCbrServer,(4)Sessionstatus:NotclosedNode:55,Layer:AppCbrServer,(4)Totalnumberofbytesreceived:22016Node:55,Layer:AppCbrServer,(4)Totalnumberofpacketsreceived:43Node:55,Layer:AppCbrServer,(4)Throughput(bitspersecond):1761三、實驗結(jié)果剖析各發(fā)送節(jié)點發(fā)包間隔較大，當網(wǎng)絡(luò)中發(fā)送節(jié)點較少時，網(wǎng)絡(luò)還未飽和。逐漸往網(wǎng)絡(luò)中增添負載，網(wǎng)絡(luò)總吞吐量逐漸增大，以后，網(wǎng)絡(luò)吞吐量逐漸趨勢于安穩(wěn)，此時，網(wǎng)絡(luò)即達到了飽和狀態(tài)。四、思慮題1、總結(jié)IEEE協(xié)議飽和吞吐量和哪些要素有關(guān)。任選一個時隙，網(wǎng)絡(luò)中有節(jié)點在發(fā)送數(shù)據(jù)的概率當有節(jié)點在發(fā)送數(shù)據(jù)包時，數(shù)據(jù)包發(fā)送成功的概率數(shù)據(jù)包發(fā)送成功和發(fā)送失敗所需的時間2、為何在數(shù)據(jù)包長度較長時，采納RTS/CTS模式更合理？隱蔽終端"多發(fā)生在大型單元中（一般在室外環(huán)境），這將帶來效率損失，并且需要錯誤恢復體制。當需要傳遞大容量文件時，特別需要根絕"隱蔽終端"現(xiàn)象的發(fā)生。實驗三動向源路由協(xié)議路由選擇考證一、實驗?zāi)康?、認識DSR路由協(xié)議的優(yōu)弊端。2、理解DSR路由協(xié)議中路由發(fā)現(xiàn)過程和路由保護過程。3、掌握DSR路由協(xié)議性能的仿真剖析方法。二、實驗結(jié)果Time(s):,Node:1,Routepath:2Time(s):,Node:1,Routepath:2Time(s):,Node:1,Routepath:2Time(s):,Node:1,Routepath:2Time(s):,Node:1,Routepath:2Time(s):,Node:1,Routepath:2Time(s):,Node:1,Routepath:2Time(s):,Node:1,Routepath:4-2Time(s):,Node:1,Routepath:4-2Time(s):,Node:1,Routepath:4-2Time(s):,Node:1,Routepath:4-2Time(s):,Node:1,Routepath:4-2Time(s):,Node:1,Routepath:4-2Time(s):,Node:1,Routepath:4-2Time(s):,Node:1,Routepath:4-2Time(s):,Node:1,Routepath:4-2Time(s):,Node:1,Routepath:4-2Time(s):,Node:1,Routepath:4-2Time(s):,Node:1,Routepath:4-2Time(s):,Node:1,Routepath:4-2Time(s):,Node:1,Routepath:4-2Time(s):,Node:1,Routepath:4-2Time(s):,Node:1,Routepath:4-2Time(s):,Node:1,Routepath:4-2Time(s):,Node:1,Routepath:4-2Time(s):,Node:1,Routepath:4-2Time(s):,Node:1,Routepath:4-2Time(s):,Node:1,Routepath:4-2Time(s):,Node:1,Routepath:4-2Time(s):,Node:1,Routepath:4-2Time(s):,Node:1,Routepath:4-2Time(s):,Node:1,Routepath:4-2Time(s):,Node:1,Routepath:4-2Time(s):,Node:1,Routepath:4-2Time(s):,Node:1,Routepath:4-2Time(s):,Node:1,Routepath:4-2Time(s):,Node:1,Routepath:4-2Time(s):,Node:1,Routepath:5-4-2Time(s):,Node:1,Routepath:5-4-2Time(s):,Node:1,Routepath:5-4-2Time(s):,Node:1,Routepath:5-4-2Time(s):,Node:1,Routepath:5-4-2Time(s):,Node:1,Routepath:5-4-2Time(s):,Node:1,Routepath:5-4-2Time(s):,Node:1,Routepath:5-4-2Time(s):,Node:1,Routepath:5-4-2Time(s):,Node:1,Routepath:5-4-2Time(s):,Node:1,Routepath:5-4-2Time(s):,Node:1,Routepath:5-4-2Time(s):,Node:1,Routepath:5-4-2Time(s):,Node:1,Routepath:5-4-2Time(s):,Node:1,Routepath:5-4-2Time(s):,Node:1,Routepath:5-4-2Time(s):,Node:1,Routepath:5-4-2Time(s):,Node:1,Routepath:5-4-2Time(s):,Node:1,Routepath:5-4-2Time(s):,Node:1,Routepath:5-4-2Time(s):,Node:1,Routepath:5-4-2Time(s):,Node:1,Routepath:5-4-2Time(s):,Node:1,Routepath:5-4-2Time(s):,Node:1,Routepath:5-4-2Time(s):,Node:1,Routepath:5-4-2Time(s):,Node:1,Routepath:5-4-2Time(s):,Node:1,Routepath:5-4-2Time(s):,Node:1,Routepath:5-4-2Time(s):,Node:1,Routepath:5-4-2Time(s):,Node:1,Routepath:5-4-2Time(s):,Node:1,Routepath:3-2Time(s):,Node:1,Routepath:3-2Time(s):,Node:1,Routepath:3-2Time(s):,Node:1,Routepath:3-2Time(s):,Nod