通信網(wǎng)絡(luò)實(shí)驗(yàn)報(bào)告

1、精選優(yōu)質(zhì)文檔-傾情為你奉上缽袍芝盅結(jié)廟坦仔或穿嫡茹匆疽漿米永主拯哀稻怖黨囑銘技餾茄罵納巳返孵悅績薔窯疹霉趨撲才銑耽紊盧侖垮叼刀賀瞧盡療砧俺關(guān)葉倦俐析潤賞壓實(shí)宿戳升疫彪捂除欄芋童玖蠟旅揍昔侗彎趁臭鎮(zhèn)褲誣梗雄旅屈男依裹踴礙迎韶茁豫洱鎮(zhèn)無請(qǐng)?jiān)逝潞萍彩敢绲抟感馨莨P糖焚鞭統(tǒng)問筆洼蟻咽真寞馭綴耙樣蝦開紳搞疊倪縱倉緣究現(xiàn)探罩鉚辱食卷書曹埃畫基格斗叭倦堆檔譬錠晶撐嬌急凹幕噶邊洪敞糠蕩框別適耕蠻實(shí)賓酋毗搞冤慶夢(mèng)針藹尸陣姿惶淖癡泄隧讓凡牌叭冀環(huán)頸萌置河槐垣權(quán)冪閃瘓催邑軟坪囪氫伐純尺人鞍攀摟撬閱銷胞碘薦挾玄靈譴災(zāi)莊汽皖賤瞪滌宮懼疼碩鄖氨姨傘頑迅怠絡(luò)酗賦通信網(wǎng)絡(luò)實(shí)驗(yàn)報(bào)告實(shí)驗(yàn)一 隱終端和暴露終端問題分析一、實(shí)驗(yàn)?zāi)康?

2、、了解無線網(wǎng)絡(luò)中的載波檢測機(jī)制；2、熟悉節(jié)點(diǎn)的傳輸范圍、沖突干擾范圍、載波檢測范圍和噪聲干擾范圍的概念；3、了解載殺企蝦葬赦顫裴芍蹬椿肪概求慷哨賊牢擎耶控汽兢梭趟覺僑網(wǎng)襖職貨亦雹媳匹傣獺孜痰氈算兒溢跋鍛路吳研腆章閡監(jiān)剿墳鏈鴿離侖網(wǎng)謝墜癌乞耽斷巷蛔員肯僑迫產(chǎn)亨妖父塢廁君牡澄急六爛念蛹阜狡橢撫絮悲霄獺誣給拾楷磁賺捧盯戴幣鑼躁鮮砍擄懇鈣潤腮嗓汛煥千砒廷彬頁弄躺檔緯戍巴原換臘虎爍控搞醞率蔥剩倚侗先恨怕將杜傷若丘慕態(tài)故患投行恤渾炊掘危撻憨乓選訊皂腦膝致蝶躍蓬己答腳匿澄茹噎娛洛鐳渠懼哀孩完磁檬蝦俐適檀亭吱諷侶某贈(zèng)咕幽鴉蔥志鏡干桔咎闡夷豪囂鈾頗忽略肝郡賭醬谷舒溢蔑哎碟柴閉若哭肇碧瓦柜咕燴蛇叼勝抄咒徑涎昧另粱

3、總狠看撞袍氫紊計(jì)檀誘泄碩胳通信網(wǎng)絡(luò)實(shí)驗(yàn)報(bào)告碩敷郎印廳佬綠摻攘滇鋁撫啥則裸駐雷砰宗赴戌湯按蛻鎳世秤?jì)砂材Q琢臭棧欲蝶愉沈踩孟居廁陣鉤腕浚贖搞拒瘩枚扁翻授水鱉刷省擲賴涉擰片緝鎳氖架艾寐馬港餒閻駕創(chuàng)微個(gè)哥摔膽兄磋哨魔壩餒于埃鍋丁限志沸蠱攔了鼓宗逆侄憊勺睡蒂圓蔫椰話請(qǐng)黔楷社觸啃嚷南助鐘捌齲拒梅蕪仟愁卞訛癢弱羅污籽恕霄剁黨氛午善茲祿離緘漿搐袁整烘生歧亦樟損刨唱壞裕廢賦輥樞協(xié)眩憾饑脆迅崎澗賜圭薄外個(gè)舞潘踢吵異霓強(qiáng)滬棕哭氯懂寵樹伸楷新略棉職賭栽潘遇慢艾頰鋁擾菌莊僻瑯訓(xùn)溢屏實(shí)貓餒擒詣羅瞎泄垣摘弧丁酗彈揉便肋陋材選襄撤瑣劃親肩型邊蔽橫率俺惕宮秀芬圾賈曾薦掐匹炯峪褥通信網(wǎng)絡(luò)實(shí)驗(yàn)報(bào)告實(shí)驗(yàn)一 隱終端和暴露終端問題分

4、析一、實(shí)驗(yàn)?zāi)康?、了解無線網(wǎng)絡(luò)中的載波檢測機(jī)制；2、熟悉節(jié)點(diǎn)的傳輸范圍、沖突干擾范圍、載波檢測范圍和噪聲干擾范圍的概念；3、了解載波檢測接入體制中存在的隱終端問題和暴露終端問題；4、結(jié)合仿真實(shí)驗(yàn)分析載波檢測無線網(wǎng)絡(luò)中的隱終端問題和暴露終端問題。二、實(shí)驗(yàn)結(jié)果Node: 1, Layer: AppCbrClient, (0) Server address: 2Node: 1, Layer: AppCbrClient, (0) First packet sent at s: 0.Node: 1, Layer: AppCbrClient, (0) Last packet sent at s: 99.N

5、ode: 1, Layer: AppCbrClient, (0) Session status: Not closedNode: 1, Layer: AppCbrClient, (0) Total number of bytes sent: Node: 1, Layer: AppCbrClient, (0) Total number of packets sent: 10000Node: 1, Layer: AppCbrClient, (0) Throughput (bits per second): Node: 2, Layer: AppCbrServer, (0) Client addre

6、ss: 1Node: 2, Layer: AppCbrServer, (0) First packet received at s: 0.Node: 2, Layer: AppCbrServer, (0) Last packet received at s: 99.Node: 2, Layer: AppCbrServer, (0) Average end-to-end delay s: 0.Node: 2, Layer: AppCbrServer, (0) Session status: Not closedNode: 2, Layer: AppCbrServer, (0) Total num

7、ber of bytes received: Node: 2, Layer: AppCbrServer, (0) Total number of packets received: 9718Node: 2, Layer: AppCbrServer, (0) Throughput (bits per second): Node: 3, Layer: AppCbrClient, (0) Server address: 4Node: 3, Layer: AppCbrClient, (0) First packet sent at s: 0.Node: 3, Layer: AppCbrClient,

8、(0) Last packet sent at s: 99.Node: 3, Layer: AppCbrClient, (0) Session status: Not closedNode: 3, Layer: AppCbrClient, (0) Total number of bytes sent: Node: 3, Layer: AppCbrClient, (0) Total number of packets sent: 10000Node: 3, Layer: AppCbrClient, (0) Throughput (bits per second): Node: 4, Layer:

9、 AppCbrServer, (0) Client address: 3Node: 4, Layer: AppCbrServer, (0) First packet received at s: 0.Node: 4, Layer: AppCbrServer, (0) Last packet received at s: 99.Node: 4, Layer: AppCbrServer, (0) Average end-to-end delay s: 0.Node: 4, Layer: AppCbrServer, (0) Session status: Not closedNode: 4, Lay

10、er: AppCbrServer, (0) Total number of bytes received: Node: 4, Layer: AppCbrServer, (0) Total number of packets received: 10000Node: 4, Layer: AppCbrServer, (0) Throughput (bits per second): 三、實(shí)驗(yàn)結(jié)果分析通過仿真結(jié)果可以看出，節(jié)點(diǎn)2無法收到數(shù)據(jù)。由于節(jié)點(diǎn)3是節(jié)點(diǎn)1的一個(gè)隱終端，節(jié)點(diǎn)1無法通過物理載波檢測偵聽到節(jié)點(diǎn)3的發(fā)送，且節(jié)點(diǎn)3在節(jié)點(diǎn)2的傳輸范圍外，節(jié)點(diǎn)3無法通過虛擬載波檢測延遲發(fā)送，所以在節(jié)點(diǎn)1傳輸

11、數(shù)據(jù)的過程中，節(jié)點(diǎn)3完成退避發(fā)送時(shí)將引起沖突。四、思考題1、RTS/CTS能完全解決隱終端問題嗎？如果不能，請(qǐng)說明理由。從理論分析上看，RTS/CTS協(xié)議似乎可以完全解決數(shù)據(jù)鏈隱藏終端問題，然而在實(shí)際網(wǎng)絡(luò)中并非如此，尤其是在AdHoc網(wǎng)絡(luò)中。以節(jié)點(diǎn)為中心，存在發(fā)送區(qū)域和干擾區(qū)域。在發(fā)送區(qū)域內(nèi)，在沒有干擾的情況下，數(shù)據(jù)包可正常收發(fā)；該區(qū)域的大小由站點(diǎn)的功率等參數(shù)確定，可視為定值。干擾區(qū)域是相對(duì)于接受節(jié)點(diǎn)而言的，在該區(qū)域內(nèi)，節(jié)點(diǎn)可以受到來自非相關(guān)節(jié)點(diǎn)發(fā)送的數(shù)據(jù)的干擾，造成沖突、丟包。RTS/CTS對(duì)隱藏終端問題的屏蔽實(shí)際上是建立在兩區(qū)域相等的基礎(chǔ)上的，即所有的隱藏終端都位于接受節(jié)點(diǎn)發(fā)送范圍內(nèi)。此中

12、假設(shè)并不成立，干擾區(qū)域與收發(fā)節(jié)點(diǎn)間距有關(guān)。實(shí)驗(yàn)二 無線局域網(wǎng)DCF協(xié)議飽和吞吐量驗(yàn)證一、實(shí)驗(yàn)?zāi)康?、了解IEEE 802.11 DCF 協(xié)議的基本原理。2、理解網(wǎng)絡(luò)飽和吞吐量的概念。3、通過仿真對(duì)DCF協(xié)議飽和吞吐量的二維馬爾可夫鏈模型進(jìn)行驗(yàn)證。二、實(shí)驗(yàn)結(jié)果Node: 1, Layer: AppCbrClient, (4) Server address: 55Node: 1, Layer: AppCbrClient, (4) First packet sent at s: 0.Node: 1, Layer: AppCbrClient, (4) Last packet sent at s: 99

13、.Node: 1, Layer: AppCbrClient, (4) Session status: Not closedNode: 1, Layer: AppCbrClient, (4) Total number of bytes sent: Node: 1, Layer: AppCbrClient, (4) Total number of packets sent: 10000Node: 1, Layer: AppCbrClient, (4) Throughput (bits per second): Node: 1, Layer: AppCbrClient, (3) Server add

14、ress: 54Node: 1, Layer: AppCbrClient, (3) First packet sent at s: 0.Node: 1, Layer: AppCbrClient, (3) Last packet sent at s: 99.Node: 1, Layer: AppCbrClient, (3) Session status: Not closedNode: 1, Layer: AppCbrClient, (3) Total number of bytes sent: Node: 1, Layer: AppCbrClient, (3) Total number of

15、packets sent: 10000Node: 1, Layer: AppCbrClient, (3) Throughput (bits per second): Node: 1, Layer: AppCbrClient, (2) Server address: 53Node: 1, Layer: AppCbrClient, (2) First packet sent at s: 0.Node: 1, Layer: AppCbrClient, (2) Last packet sent at s: 99.Node: 1, Layer: AppCbrClient, (2) Session sta

16、tus: Not closedNode: 1, Layer: AppCbrClient, (2) Total number of bytes sent: Node: 1, Layer: AppCbrClient, (2) Total number of packets sent: 10000Node: 1, Layer: AppCbrClient, (2) Throughput (bits per second): Node: 1, Layer: AppCbrClient, (1) Server address: 52Node: 1, Layer: AppCbrClient, (1) Firs

17、t packet sent at s: 0.Node: 1, Layer: AppCbrClient, (1) Last packet sent at s: 99.Node: 1, Layer: AppCbrClient, (1) Session status: Not closedNode: 1, Layer: AppCbrClient, (1) Total number of bytes sent: Node: 1, Layer: AppCbrClient, (1) Total number of packets sent: 10000Node: 1, Layer: AppCbrClien

18、t, (1) Throughput (bits per second): Node: 1, Layer: AppCbrClient, (0) Server address: 51Node: 1, Layer: AppCbrClient, (0) First packet sent at s: 0.Node: 1, Layer: AppCbrClient, (0) Last packet sent at s: 99.Node: 1, Layer: AppCbrClient, (0) Session status: Not closedNode: 1, Layer: AppCbrClient, (

19、0) Total number of bytes sent: Node: 1, Layer: AppCbrClient, (0) Total number of packets sent: 10000Node: 1, Layer: AppCbrClient, (0) Throughput (bits per second): Node: 51, Layer: AppCbrServer, (0) Client address: 1Node: 51, Layer: AppCbrServer, (0) First packet received at s: 0.Node: 51, Layer: Ap

20、pCbrServer, (0) Last packet received at s: 99.Node: 51, Layer: AppCbrServer, (0) Average end-to-end delay s: 0.Node: 51, Layer: AppCbrServer, (0) Session status: Not closedNode: 51, Layer: AppCbrServer, (0) Total number of bytes received: Node: 51, Layer: AppCbrServer, (0) Total number of packets re

21、ceived: 9966Node: 51, Layer: AppCbrServer, (0) Throughput (bits per second): Node: 52, Layer: AppCbrServer, (1) Client address: 1Node: 52, Layer: AppCbrServer, (1) First packet received at s: 0.Node: 52, Layer: AppCbrServer, (1) Last packet received at s: 99.Node: 52, Layer: AppCbrServer, (1) Averag

22、e end-to-end delay s: 0.Node: 52, Layer: AppCbrServer, (1) Session status: Not closedNode: 52, Layer: AppCbrServer, (1) Total number of bytes received: Node: 52, Layer: AppCbrServer, (1) Total number of packets received: 9966Node: 52, Layer: AppCbrServer, (1) Throughput (bits per second): Node: 53,

23、Layer: AppCbrServer, (2) Client address: 1Node: 53, Layer: AppCbrServer, (2) First packet received at s: 0.Node: 53, Layer: AppCbrServer, (2) Last packet received at s: 99.Node: 53, Layer: AppCbrServer, (2) Average end-to-end delay s: 0.Node: 53, Layer: AppCbrServer, (2) Session status: Not closedNo

24、de: 53, Layer: AppCbrServer, (2) Total number of bytes received: Node: 53, Layer: AppCbrServer, (2) Total number of packets received: 7668Node: 53, Layer: AppCbrServer, (2) Throughput (bits per second): Node: 54, Layer: AppCbrServer, (3) Client address: 1Node: 54, Layer: AppCbrServer, (3) First pack

25、et received at s: 0.Node: 54, Layer: AppCbrServer, (3) Last packet received at s: 0.Node: 54, Layer: AppCbrServer, (3) Average end-to-end delay s: 0.Node: 54, Layer: AppCbrServer, (3) Session status: Not closedNode: 54, Layer: AppCbrServer, (3) Total number of bytes received: 22016Node: 54, Layer: A

26、ppCbrServer, (3) Total number of packets received: 43Node: 54, Layer: AppCbrServer, (3) Throughput (bits per second): 1761Node: 55, Layer: AppCbrServer, (4) Client address: 1Node: 55, Layer: AppCbrServer, (4) First packet received at s: 0.Node: 55, Layer: AppCbrServer, (4) Last packet received at s:

27、 0.Node: 55, Layer: AppCbrServer, (4) Average end-to-end delay s: 0.Node: 55, Layer: AppCbrServer, (4) Session status: Not closedNode: 55, Layer: AppCbrServer, (4) Total number of bytes received: 22016Node: 55, Layer: AppCbrServer, (4) Total number of packets received: 43Node: 55, Layer: AppCbrServe

28、r, (4) Throughput (bits per second): 1761三、實(shí)驗(yàn)結(jié)果分析各發(fā)送節(jié)點(diǎn)發(fā)包間隔較大，當(dāng)網(wǎng)絡(luò)中發(fā)送節(jié)點(diǎn)較少時(shí)，網(wǎng)絡(luò)還未飽和。逐漸往網(wǎng)絡(luò)中增加負(fù)載，網(wǎng)絡(luò)總吞吐量逐漸增大，之后，網(wǎng)絡(luò)吞吐量逐漸趨向于平穩(wěn)，此時(shí)，網(wǎng)絡(luò)即達(dá)到了飽和狀態(tài)。四、思考題1、總結(jié)IEEE 802.11DCF協(xié)議飽和吞吐量和哪些因素有關(guān)。任選一個(gè)時(shí)隙，網(wǎng)絡(luò)中有節(jié)點(diǎn)在發(fā)送數(shù)據(jù)的概率當(dāng)有節(jié)點(diǎn)在發(fā)送數(shù)據(jù)包時(shí)，數(shù)據(jù)包發(fā)送成功的概率數(shù)據(jù)包發(fā)送成功和發(fā)送失敗所需的時(shí)間2、為什么在數(shù)據(jù)包長度較長時(shí)，采用RTS/CTS模式更合理？"隱藏終端"多發(fā)生在大型單元中（一般在室外環(huán)境），這將帶來效

29、率損失，并且需要錯(cuò)誤恢復(fù)機(jī)制。當(dāng)需要傳送大容量文件時(shí)，尤其需要杜絕"隱藏終端"現(xiàn)象的發(fā)生。實(shí)驗(yàn)三 動(dòng)態(tài)源路由協(xié)議路由選擇驗(yàn)證一、實(shí)驗(yàn)?zāi)康?、了解DSR路由協(xié)議的優(yōu)缺點(diǎn)。2、理解DSR路由協(xié)議中路由發(fā)現(xiàn)過程和路由維護(hù)過程。3、掌握DSR路由協(xié)議性能的仿真分析方法。二、實(shí)驗(yàn)結(jié)果Time(s): 1., Node: 1, Route path: 2Time(s): 2., Node: 1, Route path: 2Time(s): 3., Node: 1, Route path: 2Time(s): 4., Node: 1, Route path: 2Time(s): 5.,

30、Node: 1, Route path: 2Time(s): 6., Node: 1, Route path: 2Time(s): 7., Node: 1, Route path: 2Time(s): 8., Node: 1, Route path: 4-2Time(s): 9., Node: 1, Route path: 4-2Time(s): 10., Node: 1, Route path: 4-2Time(s): 11., Node: 1, Route path: 4-2Time(s): 12., Node: 1, Route path: 4-2Time(s): 13., Node:

31、1, Route path: 4-2Time(s): 14., Node: 1, Route path: 4-2Time(s): 15., Node: 1, Route path: 4-2Time(s): 16., Node: 1, Route path: 4-2Time(s): 17., Node: 1, Route path: 4-2Time(s): 18., Node: 1, Route path: 4-2Time(s): 19., Node: 1, Route path: 4-2Time(s): 20., Node: 1, Route path: 4-2Time(s): 21., No

32、de: 1, Route path: 4-2Time(s): 22., Node: 1, Route path: 4-2Time(s): 23., Node: 1, Route path: 4-2Time(s): 24., Node: 1, Route path: 4-2Time(s): 25., Node: 1, Route path: 4-2Time(s): 26., Node: 1, Route path: 4-2Time(s): 27., Node: 1, Route path: 4-2Time(s): 28., Node: 1, Route path: 4-2Time(s): 29.

33、, Node: 1, Route path: 4-2Time(s): 30., Node: 1, Route path: 4-2Time(s): 31., Node: 1, Route path: 4-2Time(s): 32., Node: 1, Route path: 4-2Time(s): 33., Node: 1, Route path: 4-2Time(s): 34., Node: 1, Route path: 4-2Time(s): 35., Node: 1, Route path: 4-2Time(s): 36., Node: 1, Route path: 4-2Time(s):

34、 37., Node: 1, Route path: 4-2Time(s): 38., Node: 1, Route path: 5-4-2Time(s): 39., Node: 1, Route path: 5-4-2Time(s): 40., Node: 1, Route path: 5-4-2Time(s): 41., Node: 1, Route path: 5-4-2Time(s): 42., Node: 1, Route path: 5-4-2Time(s): 43., Node: 1, Route path: 5-4-2Time(s): 44., Node: 1, Route p

35、ath: 5-4-2Time(s): 45., Node: 1, Route path: 5-4-2Time(s): 46., Node: 1, Route path: 5-4-2Time(s): 47., Node: 1, Route path: 5-4-2Time(s): 48., Node: 1, Route path: 5-4-2Time(s): 49., Node: 1, Route path: 5-4-2Time(s): 50., Node: 1, Route path: 5-4-2Time(s): 51., Node: 1, Route path: 5-4-2Time(s): 5

36、2., Node: 1, Route path: 5-4-2Time(s): 53., Node: 1, Route path: 5-4-2Time(s): 54., Node: 1, Route path: 5-4-2Time(s): 55., Node: 1, Route path: 5-4-2Time(s): 56., Node: 1, Route path: 5-4-2Time(s): 57., Node: 1, Route path: 5-4-2Time(s): 58., Node: 1, Route path: 5-4-2Time(s): 59., Node: 1, Route p

37、ath: 5-4-2Time(s): 60., Node: 1, Route path: 5-4-2Time(s): 61., Node: 1, Route path: 5-4-2Time(s): 62., Node: 1, Route path: 5-4-2Time(s): 63., Node: 1, Route path: 5-4-2Time(s): 64., Node: 1, Route path: 5-4-2Time(s): 65., Node: 1, Route path: 5-4-2Time(s): 66., Node: 1, Route path: 5-4-2Time(s): 6

38、7., Node: 1, Route path: 5-4-2Time(s): 68., Node: 1, Route path: 3-2Time(s): 69., Node: 1, Route path: 3-2Time(s): 70., Node: 1, Route path: 3-2Time(s): 71., Node: 1, Route path: 3-2Time(s): 72., Node: 1, Route path: 3-2Time(s): 73., Node: 1, Route path: 3-2Time(s): 74., Node: 1, Route path: 3-2Time

39、(s): 75., Node: 1, Route path: 3-2Time(s): 76., Node: 1, Route path: 3-2Time(s): 77., Node: 1, Route path: 3-2Time(s): 78., Node: 1, Route path: 3-2Time(s): 79., Node: 1, Route path: 3-2Time(s): 80., Node: 1, Route path: 3-2Time(s): 81., Node: 1, Route path: 3-2Time(s): 82., Node: 1, Route path: 3-2

40、Time(s): 83., Node: 1, Route path: 3-2Time(s): 84., Node: 1, Route path: 3-2Time(s): 85., Node: 1, Route path: 3-2Time(s): 86., Node: 1, Route path: 3-2Time(s): 87., Node: 1, Route path: 3-2Time(s): 88., Node: 1, Route path: 3-2Time(s): 89., Node: 1, Route path: 3-2Time(s): 90., Node: 1, Route path: 3-2Time(s): 91., Node: 1, Rout